Comments on: Mono Strange Behaviour (Bug!) http://www.alexandre-gomes.com/?p=435 Technology, programming, ideas and innovation are my preferred subjects. Working professionally on programming gives me plenty of new topics to write about, still my brain keeps popping out ideas in the most unexpected places. Wed, 25 Aug 2010 13:40:29 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: AdSense reports in a Gadget (iGoogle and Wave) « Alexandre Gomes http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33780 AdSense reports in a Gadget (iGoogle and Wave) « Alexandre Gomes Tue, 27 Oct 2009 03:02:33 +0000 http://www.alexandre-gomes.com/?p=435#comment-33780 [...] requests. Luckily, Mono behaved quite well after that last little problem I blogged about – Mono Strange Behaviour (Bug!). I also had to implement several security checks and encryption to make sure no data can be stolen [...] [...] requests. Luckily, Mono behaved quite well after that last little problem I blogged about – Mono Strange Behaviour (Bug!). I also had to implement several security checks and encryption to make sure no data can be stolen [...]

]]> By: alexmipego http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33756 alexmipego Fri, 23 Oct 2009 14:55:51 +0000 http://www.alexandre-gomes.com/?p=435#comment-33756 @Alan I've done it all. Patch, test case and bug report. https://bugzilla.novell.com/show_bug.cgi?id=549580 Please take a look at it, I've tested it to make sure the test is accurate and no regressions on the other tests were detected. I did a similar fix on my mono 2.4.3.2 sources on the production server (this machine) and everything started to work like it was supposed to. If you think its OK to commit to the Mono's trunk, let me know. I haven't done a Mono commit in a while and its kinda like candy for hackers :P I just love it. @Alan
I’ve done it all. Patch, test case and bug report. https://bugzilla.novell.com/show_bug.cgi?id=549580
Please take a look at it, I’ve tested it to make sure the test is accurate and no regressions on the other tests were detected. I did a similar fix on my mono 2.4.3.2 sources on the production server (this machine) and everything started to work like it was supposed to.

If you think its OK to commit to the Mono’s trunk, let me know. I haven’t done a Mono commit in a while and its kinda like candy for hackers :P I just love it.

]]> By: alexmipego http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33755 alexmipego Fri, 23 Oct 2009 14:51:22 +0000 http://www.alexandre-gomes.com/?p=435#comment-33755 It was a bit of an ugly hack really. I can't recall but at the time it was the best or fastest solution. Anyway, what I've done was create a small C app with this code: #include #include #include int main(void) { execl("/usr/bin/svn", "svn", "update", "/var/www/whotouchesnet", (const char *) NULL); return(EXIT_FAILURE); } Compile it with "gcc -o binname filename.c" and then "chmod a+x binname". After that you just might need to fine tune the permissions on the working copy a bit, just remember that the executable and the svn up command will be run with the apache's user credentials. Might not be the best solution but it is simple enough and works like a charm! Never fails, I commit and my sites are updated. Just a word of caution though, make sure you're using branches to manage the production/test versions of the site or service. Personally I've a production branch which goes life on www.domain.com and then I've the trunk/main branch going to a test.domain.com - that way I can test/debug freely without concerns about bugs. It was a bit of an ugly hack really. I can’t recall but at the time it was the best or fastest solution. Anyway, what I’ve done was create a small C app with this code:

#include
#include
#include
int main(void) { execl(“/usr/bin/svn”, “svn”, “update”, “/var/www/whotouchesnet”, (const char *) NULL); return(EXIT_FAILURE); }

Compile it with “gcc -o binname filename.c” and then “chmod a+x binname”. After that you just might need to fine tune the permissions on the working copy a bit, just remember that the executable and the svn up command will be run with the apache’s user credentials.

Might not be the best solution but it is simple enough and works like a charm! Never fails, I commit and my sites are updated. Just a word of caution though, make sure you’re using branches to manage the production/test versions of the site or service. Personally I’ve a production branch which goes life on http://www.domain.com and then I’ve the trunk/main branch going to a test.domain.com – that way I can test/debug freely without concerns about bugs.

]]> By: mat http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33754 mat Fri, 23 Oct 2009 13:12:21 +0000 http://www.alexandre-gomes.com/?p=435#comment-33754 Hiya, don't suppose you fancy sharing the subversion hook, would be dead handy? Hiya, don’t suppose you fancy sharing the subversion hook, would be dead handy?

]]> By: Alan http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33753 Alan Fri, 23 Oct 2009 12:11:29 +0000 http://www.alexandre-gomes.com/?p=435#comment-33753 It's not laziness or hatred of filing bugs, the reason I won't file this is because I have no way of verifying the fix works. Therefore how could I possibly mark the bug as fixed? If alex files it, I can notify him (by updating the bug) that a fix is in SVN. He can then test it and notify us (by updating the bug) if it resolved his issue or not. It's a paper trail which makes it much easier to ensure things get fixed :) Secondly, if there are 100 bugs in my area, pretty much everything with an attached testcase will be prioritised. If I have to 1) Find the bug, 2) Write a testcase, 3) Write a patch, 4) Check back with the original dev as to whether it fixed their issue or not, 5) Go back to 1 if it didn't, i waste a lot of time :) It’s not laziness or hatred of filing bugs, the reason I won’t file this is because I have no way of verifying the fix works. Therefore how could I possibly mark the bug as fixed? If alex files it, I can notify him (by updating the bug) that a fix is in SVN. He can then test it and notify us (by updating the bug) if it resolved his issue or not. It’s a paper trail which makes it much easier to ensure things get fixed :)

Secondly, if there are 100 bugs in my area, pretty much everything with an attached testcase will be prioritised. If I have to 1) Find the bug, 2) Write a testcase, 3) Write a patch, 4) Check back with the original dev as to whether it fixed their issue or not, 5) Go back to 1 if it didn’t, i waste a lot of time :)

]]> By: alexmipego http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33752 alexmipego Fri, 23 Oct 2009 12:10:54 +0000 http://www.alexandre-gomes.com/?p=435#comment-33752 Lol, personally I don't mind filling bug reports except that with Mono I'm a bit frustated due to past experiences. I did a lot of patches to fix SqlServer bugs, Dns Bugs and even did autocompletion on MonoDevelop 2 years before they implemented it - sad thing is that my work tends to go into a dark hole for years, even with my stalking on irc, personal mail and even blog posts lol. http://www.alexandre-gomes.com/?p=126 Anyway @Alan I've downloaded a Ubuntu VM and although I din't touch Mono's code for a long time I'm going to give it a shot, if nothing else its a nice test to check if my commit access is still up ;) Lol, personally I don’t mind filling bug reports except that with Mono I’m a bit frustated due to past experiences. I did a lot of patches to fix SqlServer bugs, Dns Bugs and even did autocompletion on MonoDevelop 2 years before they implemented it – sad thing is that my work tends to go into a dark hole for years, even with my stalking on irc, personal mail and even blog posts lol. http://www.alexandre-gomes.com/?p=126

Anyway @Alan I’ve downloaded a Ubuntu VM and although I din’t touch Mono’s code for a long time I’m going to give it a shot, if nothing else its a nice test to check if my commit access is still up ;)

]]> By: John http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33751 John Fri, 23 Oct 2009 11:53:50 +0000 http://www.alexandre-gomes.com/?p=435#comment-33751 Lol love how much developers don't like filing bugs... even those responsible for projects! Lol love how much developers don’t like filing bugs… even those responsible for projects!

]]> By: Alan http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33750 Alan Fri, 23 Oct 2009 10:53:48 +0000 http://www.alexandre-gomes.com/?p=435#comment-33750 Well, if you can get a patch in very soon and let me know, i can try my best to make sure it gets into 2.6. Well, if you can get a patch in very soon and let me know, i can try my best to make sure it gets into 2.6.

]]> By: alexmipego http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33749 alexmipego Fri, 23 Oct 2009 09:41:50 +0000 http://www.alexandre-gomes.com/?p=435#comment-33749 Hi, Thanks for the help, it was kinda obvious I guess... just didn't look on the right places. Anyway, currently I don't have a devel Linux box and making a patch/unit test would be kinda difficult. All my debugging was done directly on the server and thats far from recommended :D Hi,

Thanks for the help, it was kinda obvious I guess… just didn’t look on the right places. Anyway, currently I don’t have a devel Linux box and making a patch/unit test would be kinda difficult. All my debugging was done directly on the server and thats far from recommended :D

]]> By: Alan http://www.alexandre-gomes.com/?p=435&cpage=1#comment-33748 Alan Fri, 23 Oct 2009 09:36:19 +0000 http://www.alexandre-gomes.com/?p=435#comment-33748 Finally, this is the actual WebClient class. You were looking at the Silverlight one. http://anonsvn.mono-project.com/viewvc/trunk/mcs/class/System/System.Net/WebClient.cs?view=log The class is in the 'System' assembly in the 'System.Net' namespace. Finally, this is the actual WebClient class. You were looking at the Silverlight one.

http://anonsvn.mono-project.com/viewvc/trunk/mcs/class/System/System.Net/WebClient.cs?view=log

The class is in the ‘System’ assembly in the ‘System.Net’ namespace.

]]>