Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
In article mpro.nszgmv00xukt901zy.li...@stevefryatt.org.uk, Steve Fryatt li...@stevefryatt.org.uk wrote: I'm not sure it's that odd. What is odd is that out of hundreds of zip files on the hard drive, only a very small number error in this way. -- Chris Johnson
Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
On 12 Aug, cj wrote in message 54f23593afch...@chris-johnson.org.uk: In article mpro.nszgmv00xukt901zy.li...@stevefryatt.org.uk, Steve Fryatt li...@stevefryatt.org.uk wrote: I'm not sure it's that odd. What is odd is that out of hundreds of zip files on the hard drive, only a very small number error in this way. It's /any/ Zipfile, StrongHelp manual or whatever once the 'owner' is running, isn't it? It usually is here, anyway. -- Steve Fryatt - Leeds, England http://www.stevefryatt.org.uk/
Re: Something went wrong between 2873 and 2874
In message 54f1ea25fbbbai...@argonet.co.uk Brian bbai...@argonet.co.uk wrote: In article 80739ff154.davem...@my.inbox.com, Dave Higton d...@davehigton.me.uk wrote: http://www.bbc.co.uk/sport/0/athletics/33867962 causes NS to silently evaporate from CI 2874 onwards - up to 2873 is OK. Evaporates with #2890, too. I have reported it. 2874 onwards also fails to view the report in Mantis - which gives another URL to try. Dave It's a JavaScript thing. This is with #2891. Recent NetSurfs start up with JavaScript enabled no matter what had been saved to Choices previously. As such the site crashes. Disable JavaScript and the site renders. Bug tracker updated. http://bugs.netsurf-browser.org/mantis/view.php?id=2344 -- David Pitt Raspberry Pi
Re: Something went wrong between 2873 and 2874
In article 80739ff154.davem...@my.inbox.com, Dave Higton d...@davehigton.me.uk wrote: http://www.bbc.co.uk/sport/0/athletics/33867962 causes NS to silently evaporate from CI 2874 onwards - up to 2873 is OK. Evaporates with #2890, too. I have reported it. 2874 onwards also fails to view the report in Mantis - which gives another URL to try. Dave
Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
In message 54f1f9a962ch...@chris-johnson.org.uk cj ch...@chris-johnson.org.uk wrote: In article cd18f7f154@abbeypress.net, Jim Nagel nets...@abbeypress.co.uk wrote: Warning from Netsurf The file could not be saved due to an error: 'ADFS::Drive2.$.2310d/zip' is a directory This is a common error and nothing to do with Netsurf as such. It is due to some oddity with SparkFS and handling of zip files, and seems to depend on how the original zip was produced (software). I get it from Filer_Action when running SyncDisc jobs. [snip] ... and the way to avoid it is to quit SparkFS using FS too.
Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
In article mpro.nsz8rv00ukqa700m9.nets...@ypical-daemon.co.uk, Fred Bambrough nets...@ypical-daemon.co.uk wrote: ... and the way to avoid it is to quit SparkFS using FS too. Agreed - that is why I have added a 'kill' facility to the version of SyncDiscs I use myself. -- Chris Johnson
Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
In article cd18f7f154@abbeypress.net, Jim Nagel nets...@abbeypress.co.uk wrote: Warning from Netsurf The file could not be saved due to an error: 'ADFS::Drive2.$.2310d/zip' is a directory This is a common error and nothing to do with Netsurf as such. It is due to some oddity with SparkFS and handling of zip files, and seems to depend on how the original zip was produced (software). I get it from Filer_Action when running SyncDisc jobs. (1) The wording of the warning seems inappropriate. A directory? SparkFS etc treats zip files as image files, so zips can appear as a directory containing files. (2) The text of the warning was not recorded by !Syslog (whose job is to make it easy for people submitting bug reports to quote the exact wording of an error message). I searched the whole log and found nothing from Netsurf. Netsurf uses its own logging and does not send anything to Syslog. *help wimplog says: The Wimplog module logs errors sent to Wimp_ReportError (ie, shown as error boxes on the screen) to a file using !Syslog. Wimplog intercepts the standard Wimp_ReportError wimp error messages. If Netsurf uses its own internal error reporting, then Wimplog will not see it. (I'm using Netsurf #2789 on Iyonix 5.18, Syslog 0.20, Wimplog 1.02) -- Chris Johnson
Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
On Wed, Aug 12, 2015 at 12:53:57PM +0100, cj wrote: *help wimplog says: The Wimplog module logs errors sent to Wimp_ReportError (ie, shown as error boxes on the screen) to a file using !Syslog. Wimplog intercepts the standard Wimp_ReportError wimp error messages. If Netsurf uses its own internal error reporting, then Wimplog will not see it. Correct. Wimp_ReportError is evil and NetSurf does not use it unless the event is cataclysmic. B.
Re: Do Netsurf's errors get logged? (Syslog, Wimplog)
On 12 Aug, cj wrote in message 54f1f9a962ch...@chris-johnson.org.uk: In article cd18f7f154@abbeypress.net, Jim Nagel nets...@abbeypress.co.uk wrote: Warning from Netsurf The file could not be saved due to an error: 'ADFS::Drive2.$.2310d/zip' is a directory This is a common error and nothing to do with Netsurf as such. It is due to some oddity with SparkFS and handling of zip files, and seems to depend on how the original zip was produced (software). I get it from Filer_Action when running SyncDisc jobs. I'm not sure it's that odd. If SparkFS has been seen and the zip file has the correct filetype, RISC OS will report the object to NetSurf as a directory, not a file (/some/ calls will report it as an image directory, but others won't). (1) The wording of the warning seems inappropriate. A directory? SparkFS etc treats zip files as image files, so zips can appear as a directory containing files. While undeniably clever, the whole image filing system concept has some really big holes in it. (2) The text of the warning was not recorded by !Syslog (whose job is to make it easy for people submitting bug reports to quote the exact wording of an error message). I searched the whole log and found nothing from Netsurf. Some confusion? There's no single SysLog log, so it isn't clear which whole log Jim searched... Netsurf uses its own logging and does not send anything to Syslog. Indeed. *help wimplog says: The Wimplog module logs errors sent to Wimp_ReportError (ie, shown as error boxes on the screen) to a file using !Syslog. Wimplog intercepts the standard Wimp_ReportError wimp error messages. If Netsurf uses its own internal error reporting, then Wimplog will not see it. NetSurf uses its own non-blocking error dialogues, so WimpLog won't ever see the errors reported. In terms of bug reporting, NetSurf's own log is far more detailed and far more useful. -- Steve Fryatt - Leeds, England http://www.stevefryatt.org.uk/
