Hello list! Since STIXfonts where released today I''m searching for a Wiki with easy MathML editing. I came across Instiki and started to play around with it. But it frequently crashes. I''ve attached messages printed to stdout from one crash. Instiki (instiki-svn.tar.gz from today) is used on Windows 7 (32bit) on Ruby 1.9.1. I really like Instiki and would very much use it for my daily work, but it''s no use to me if it crashes every couple of edits. :( Best Regards, Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: instiki.log Type: application/octet-stream Size: 13922 bytes Desc: not available URL: <http://rubyforge.org/pipermail/instiki-users/attachments/20100529/9fff4d29/attachment-0001.obj>
On May 28, 2010, at 8:41 PM, Martin Ammerm?ller wrote:> Since STIXfonts where released today I''m searching for a Wiki with > easy MathML editing. I came across Instiki and started to play around > with it. But it frequently crashes. I''ve attached messages printed to > stdout from one crash. > > Instiki (instiki-svn.tar.gz from today) is used on Windows 7 (32bit) > on Ruby 1.9.1.I''m not sure I''m reading the crash logs correctly. Did you install the itextomml gem, per the instructions: http://golem.ph.utexas.edu/wiki/instiki/show/Installation I assume you''re using the (default) sqlite3 database. I believe, under Ruby 1.9.x, that REQUIRES installing the sqlite3-ruby gem (again, mentioned in the above instructions).> > I really like Instiki and would very much use it for my daily work, > but it''s no use to me if it crashes every couple of edits. :(There is an unresolved issue with logging under Windows. See the workaround here: http://golem.ph.utexas.edu/wiki/instiki/show/Known+Bugs But I doubt that would be affecting you, right away. More likely, your database and/or itex2MML isn''t working right, because the relevant gems are not installed. JD -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 254 bytes Desc: This is a digitally signed message part URL: <http://rubyforge.org/pipermail/instiki-users/attachments/20100528/40aedc76/attachment.bin>
Thanks for the quick answer. 2010/5/29 Jacques Distler <distler at golem.ph.utexas.edu>:> > On May 28, 2010, at 8:41 PM, Martin Ammerm?ller wrote: > >> Since STIXfonts where released today I''m searching for a Wiki with >> easy MathML editing. I came across Instiki and started to play around >> with it. But it frequently crashes. I''ve attached messages printed to >> stdout from one crash. >> >> Instiki (instiki-svn.tar.gz from today) is used on Windows 7 (32bit) >> on Ruby 1.9.1. > > I''m not sure I''m reading the crash logs correctly. > > Did you install the itextomml gem, per the instructions: > > ? http://golem.ph.utexas.edu/wiki/instiki/show/InstallationYes, that''s exactly what i did. For sqlite3-ruby and itextomml. Just to be sure, i installed them again. But it didn''t help. I noticed that crashes seem to only occur when i try to edit/submit a page with Firefox. AFAIR it didn''t crash when editing/viewing is done with Chrome.> There is an unresolved issue with logging under Windows. See the workaround here: > > ? ?http://golem.ph.utexas.edu/wiki/instiki/show/Known+Bugs > > But I doubt that would be affecting you, right away. More likely, your database and/or itex2MML isn''t working right, because the relevant gems are not installed.log\production.log is only ~140KB big. Another thing: is it by design, that wiki words can only be us-ascii? Martin
On May 28, 2010, at 11:42 PM, Martin Ammerm?ller wrote:> > I noticed that crashes seem to only occur when i try to edit/submit a > page with Firefox. AFAIR it didn''t crash when editing/viewing is done > with Chrome.So it depends on what BROWSER you are using? That''s strange. I don''t see any evidence of a crash from the log you attached. Lots of chatter from Maruku (the Markdown processor), which is very verbose, but nothing even vaguely indicative of a crash. (Well, OK, I don''t see the log entry for the "show" action, after you saved the page, but perhaps you cut off the log early.) Aside from the Maruku chatter, is there anything in the log which looks like an error message?>> There is an unresolved issue with logging under Windows. See the workaround here: >> >> http://golem.ph.utexas.edu/wiki/instiki/show/Known+Bugs >> >> But I doubt that would be affecting you, right away. More likely, your database and/or itex2MML isn''t working right, because the relevant gems are not installed. > > log\production.log is only ~140KB big.Good! That eliminates that problem (though you may, later, encounter the log-rotation bug).> Another thing: is it by design, that wiki words can only be us-ascii?As you can see from http://golem.ph.utexas.edu/~distler/code/instiki/svn/annotate/head%3A/lib/wiki_words.rb that''s not true. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 254 bytes Desc: This is a digitally signed message part URL: <http://rubyforge.org/pipermail/instiki-users/attachments/20100529/5cf8d503/attachment.bin>
2010/5/29 Jacques Distler <distler at golem.ph.utexas.edu>:> > On May 28, 2010, at 11:42 PM, Martin Ammerm?ller wrote: > >> >> I noticed that crashes seem to only occur when i try to edit/submit a >> page with Firefox. AFAIR it didn''t crash when editing/viewing is done >> with Chrome. > > So it depends on what BROWSER you are using? That''s strange.Well, I''m not sure about that. Could be coincidence or bias on my part.> I don''t see any evidence of a crash from the log you attached. Lots of chatter from Maruku (the Markdown processor), which is very verbose, but nothing even vaguely indicative of a crash. (Well, OK, I don''t see the log entry for the "show" action, after you saved the page, but perhaps you cut off the log early.)Maybe it''s a problem with ruby itself. Every crash is accompanied by a "Application stopped working" dialogue for ruby. And these installers for Windows are only release candidates. I''ll try the 1.8.x ruby installer and installing by zip files. Maybe that will fix it.> Aside from the Maruku chatter, is there anything in the log which looks like an error message?I don''t think so. I''ve attached my production.log, if you want to have a look.>> Another thing: is it by design, that wiki words can only be us-ascii? > > As you can see from > > ? http://golem.ph.utexas.edu/~distler/code/instiki/svn/annotate/head%3A/lib/wiki_words.rb > > that''s not true.Interesting. ''Cause i got an "ArgumentError in WikiController#new" when i tried to create a new page via a wiki word that contained an umlaut (see attachment). Martin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/instiki-users/attachments/20100529/a040daa3/attachment-0001.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: production.7z Type: application/octet-stream Size: 9011 bytes Desc: not available URL: <http://rubyforge.org/pipermail/instiki-users/attachments/20100529/a040daa3/attachment-0001.obj>
On May 29, 2010, at 12:35 AM, Martin Ammerm?ller wrote:>> I don''t see any evidence of a crash from the log you attached. Lots of chatter from Maruku (the Markdown processor), which is very verbose, but nothing even vaguely indicative of a crash. (Well, OK, I don''t see the log entry for the "show" action, after you saved the page, but perhaps you cut off the log early.) > > Maybe it''s a problem with ruby itself. Every crash is accompanied by a > "Application stopped working" dialogue for ruby. And these installers > for Windows are only release candidates. I''ll try the 1.8.x ruby > installer and installing by zip files. Maybe that will fix it. > >> Aside from the Maruku chatter, is there anything in the log which looks like an error message? > > I don''t think so. I''ve attached my production.log, if you want to have a look.I see one encoding-mismatch error (discussed below), but nothing else out-of-the-ordinary. Weird.>>> Another thing: is it by design, that wiki words can only be us-ascii? >> >> As you can see from >> >> http://golem.ph.utexas.edu/~distler/code/instiki/svn/annotate/head%3A/lib/wiki_words.rb >> >> that''s not true. > > Interesting. ''Cause i got an "ArgumentError in WikiController#new" > when i tried to create a new page via a wiki word that contained an > umlaut (see attachment).That''s definitely a Ruby 1.9.x error. Rails and Ruby 1.9 is still a work-in-progress. (To explain: In Ruby 1.8, strings are just sequences of bytes; in Ruby 1.9, string are encoding-aware. On the one hand, that''s great, because methods that manipulate strings (count the number of characters, or reverse the characters in a string) need to be aware of multi-byte encodings, like utf-8, which is what Rails and Instiki use. On the other hand, all HELL breaks loose if two different libraries disagree about what the encoding of a given string is supposed to be. That''s what''s happening to cause your error message.) I have been running quite successfully with Ruby 1.9.2 (including creating pages with non-ASCII names). But I encountered problems with 1.9.1. On the other hand, I have users, who are running successfully on 1.9.1, so go figure .... For best stability, I''d still recommend Ruby 1.8.7. Seems to me that there''s something causing your Ruby 1.9.1 to die, quite apart from anything going wrong in Instiki itself. Let me know if Ruby 1.8.7 solves your problem. JD -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 254 bytes Desc: This is a digitally signed message part URL: <http://rubyforge.org/pipermail/instiki-users/attachments/20100529/a914327a/attachment.bin>