Andres, On Tue, Jun 28, 2011 at 6:48 PM, Andres Riancho <andres.rian...@gmail.com> wrote: > List, > > We had some issue that raised a "TypeError: > Gtk.MozEmbed.render_data() argument 3 must be string, not url_object", > I fixed in a while ago in revision "4300", and now it's appearing
r4300 is the right number? > again [0]. The strange thing is that the bug report says that they are > using the latest revision, which should have the bug already fixed; > AND in the traceback it shows the OLD version of that line of code > [1]. So... how can this w3af install be in revision 4346 but have that > old piece of code? > > @Javier: You worked on the auto-update, any hints? The only thing I can think of right now is that an error actually occurred when updating the code and yet w3af could be restarted (after displaying the user an error message). I've just checked the routine that reads from the svn file the current revision [0] and it takes as reference *only* the svn "entries" file in the project root. Also, this is possible with SVN: $:~/workspace/w3af$ svn info [...] Revision: 4331 [...] $:~/workspace/w3af$ cd plugins $:~/workspace/w3af/plugins$ svn info [...] Revision: 4347 [...] Meaning that different directories in the project can be updated to different revisions. So it seems that the get-revision routine doesn't warranty that the whole code is updated to the reported version. Javier [0] https://w3af.svn.sourceforge.net/svnroot/w3af/trunk/core/controllers/misc/get_w3af_version.py ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop
