Conversation
|
Lets upgrade editor to 3.1.0 to resolve: inline-markdown-editor/package-lock.json Line 4947 in 12b3d1a |
|
Hmm... ok its very close to this issue: actions/setup-node#214 |
|
a5ccf9a resulted in an endless loop of tests oddly. Trying node 16 instead... |
|
node 16 worked but went into endless test loop. |
|
Solved recursive issue. Now getting: Prev this didn't happen: https://github.com/publiclab/inline-markdown-editor/runs/2969361193?check_suite_focus=true |
|
Unfortunately i think we may have an incorrectly written function somewhere in out tests? I'm not sure. Compare to similar error in this: https://stackoverflow.com/questions/36514468/jasmine-throws-one-error-error-timeout-async-callback-was-not-invoked#36514646 |
|
Noting that in plots2:
|
|
@jywarren Can you try adding a callback |
Thank you I'll try that! |
|
Hmm, i don't know why the Github Actions CI run isn't going, but i tried it manually in gitpod and got: ... so same issue. This is lower priority now but pretty annoying! |
|
@jywarren You didn’t add the done callback to the function declaration on line 3. |
| describe("Replacement functions", function() { | ||
|
|
||
| it("won't generate an editor for an ambiguous (duplicated) section, where replacement server side could apply to the wrong section", function() { | ||
| it("won't generate an editor for an ambiguous (duplicated) section, where replacement server side could apply to the wrong section", function(done) { |
There was a problem hiding this comment.
@TildaDares didn't i add it here? Or did I miss somewhere else too?
|
Just noting that we're getting a recursive loop of the tests running. Maybe we can search for this kind of error in the Jasmine forums or on StackOverflow. |
No description provided.