Edge table crashes on sorting of comments in newest dev

[jdanish]

View nodes table, sort by comments. It works.
Switch to edge table, sort by comments. It does not.

Note the TypeError error in this image as that appears in both local and DO runs. The web socket issue is only on DO and will be reported separately. It appears unrelated since that error does not appear on local runs.

[benloh]

I did see errors like this while developing. But generally quitting the server and restarting would fix the problem. Some of the server code is not auto-restarted with code changes (pulls). Try that first? (Sorting by comments on edge table works for me)

[jdanish]

Ok I’ll re-try and report back this afternoon thanks.

[jdanish]

Tried with running classroom, and it seems fine otherwise. Different error now from running locally, so re-posting.

Anything else I should try?

[jdanish]

OK, in case this helps: my new network (testing) I created by using ./nc.js with a new dataset name. Everything else works find. Comments still crashed. I added text to both comments. Now they sort fine. Could to be related to the issue where comments are not initially set correctly when empty, but only in the edge table? @benloh

[benloh]

Oh did you ever update your _default.template.toml file?
But yeah, you might be onto something. I'll see if I can reproduce it.

[jdanish]

Oh, no I just tried and get this error.

Other ideas? Also, I am not sure how likely it is anyone will remember to run ncRegenerateDefaultTemplate() so we might want a long-term alternative solution?

[benloh]

ncRegenerateDefaultTemplate was intended really only for developers and it only needs to be run when template-schema.js is changed. When we're done with this my plan was to commit and push _default.template.toml so this shouldn't be an issue in the future.

As for your error, check nc-logic.js:1228 -- there should be a JSCLI.AddFunction call with function ncRegenerateDefaultTemplate on the next line. Any chance you hadn't quit and restarted the server?

[jdanish]

OK, the issue was it only works if you do npm run dev, so I have done that. Seems it worked! And the problem is resolved.

[benloh]

Closing. All issues addressed.