This was a strange animal indeed. I went through and disabled all plugins to no avail. After digging through logs and much google-fu I found this post that apparently I missed before:
https://groups.google.com/d/msg/agilo/eSYrTvPPsS0/CbZFu850VbIJ That was my problem; I had played around with making the *actual* remaining time field on stories try to sum the hours from tasks below it. I had of course forgotten that I had done so until reading the above post. Simply removing that calculated field stopped the typeError from cropping up. While I understand (now) how the calculated field was blowing this up, this might be a great candidate for giving a meaningful error at some point in the chain, whether at the time of creation of the faulty field, or at the explosion that says "hey! you have a bad field here!" Just a suggestion. Thanks for the help on this. On Friday, November 27, 2015 at 2:23:51 AM UTC-7, Claudio Di Cosmo wrote: > > Hi sojrner, > > On 24 Nov 2015, at 17:42, sojrner <[email protected] <javascript:>> wrote: > > I've looked through this group and the agilo ticket list to no avail. > Apologies if I've missed something obvious... When editing *most* fields > in a user story, if there are any hours on tasks referencing it Agilo > throws the following error: > > "TypeError: expected string or buffer" > > We have tracked this to be only an issue when tasks still have hours, > which then show as remaining time on the story. We can also change the > story from "story" to "task" types without issue, but changing any other > data point results in that error. (including trying to change it back from > "task" to "story") If we move all hours of child tickets to zero, > everything is fine and editing can continue on the story. > > This seems like incorrect behavior, as I've read posts here about similar > issues that seem to confirm that a story should be able to be closed > regardless of task state. (makes sense when you don't use up all hours on a > task, but the story is fulfilled) I'm including the call list and other > system information for completeness. I appreciate all the help. > > > Thank you for using our Agilo for Trac. > > The issue that you are experiencing can be also related to the interaction > with other plugins that are installed on your trac instance. One test that > you can do is to disable all plugins not related to agilo for trac and > check if the error is still showing up. > Moreover, the trac version 1.0.5 is not supported/tested yet and we are > aware of some incompatibility issues for version greater then 1.0.2, so I > would recommend, if possible, to downgrade your version to the latest > supported one. > > Sorry for the inconvenience, > > Cheers, > > Claudio Di Cosmo > Software Engineer > Agilo Software GmbH > Gruenberger Str. 54 > 10245 Berlin, Germany > > [email protected] <javascript:> > http://www.agilosoftware.com > > Follow us on twitter: http://twitter.com/agiloforscrum, > http://twitter.com/agilofortrac > > Amtsgericht Charlottenburg: HRB 127146 > CEO Marion Eickmann, Andrea Tomasini > > -- -- Follow Agilo on Twitter: http://twitter.com/agilofortrac Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-trac http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Trac" Google Group. This group is focused on supporting Agilo for Trac users and is moderated by Agilo Software GmbH <http://www.agilosoftware.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo --- You received this message because you are subscribed to the Google Groups "Agilo for Trac" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
