Skip to content

fixed deps git protocol#145

Open
jywarren wants to merge 9 commits into
mainfrom
npm-fixes
Open

fixed deps git protocol#145
jywarren wants to merge 9 commits into
mainfrom
npm-fixes

Conversation

@jywarren

Copy link
Copy Markdown
Member

No description provided.

@jywarren

Copy link
Copy Markdown
Member Author

Lets upgrade editor to 3.1.0 to resolve:

"woofmark": "git://github.com/jywarren/woofmark.git#plots2",

@jywarren

Copy link
Copy Markdown
Member Author

Hmm... ok its very close to this issue: actions/setup-node#214

@jywarren

Copy link
Copy Markdown
Member Author

a5ccf9a resulted in an endless loop of tests oddly. Trying node 16 instead...

@jywarren

Copy link
Copy Markdown
Member Author

node 16 worked but went into endless test loop.

@jywarren

Copy link
Copy Markdown
Member Author

Solved recursive issue. Now getting:

12 specs in 0.[31](https://github.com/publiclab/inline-markdown-editor/runs/5602541469?check_suite_focus=true#step:7:31)4s.
>> 0 failures
Fatal error: Callback must be a function. Received undefined�
Error: Process completed with exit code 3.

Prev this didn't happen:

https://github.com/publiclab/inline-markdown-editor/runs/2969361193?check_suite_focus=true

@jywarren

Copy link
Copy Markdown
Member Author

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

@jywarren

Copy link
Copy Markdown
Member Author

Noting that in plots2:

However I'm not seeing this error in other recent plots2 PRs... very strange. So maybe we can drop this for now?

publiclab/plots2#10768 (comment)

@TildaDares

Copy link
Copy Markdown
Member

@jywarren Can you try adding a callback done to this function and calling it?

it("won't generate an editor for an ambiguous (duplicated) section, where replacement server side could apply to the wrong section", function() {

@jywarren

Copy link
Copy Markdown
Member Author

@jywarren Can you try adding a callback done to this function and calling it?

it("won't generate an editor for an ambiguous (duplicated) section, where replacement server side could apply to the wrong section", function() {

Thank you I'll try that!

@jywarren

Copy link
Copy Markdown
Member Author

Hmm, i don't know why the Github Actions CI run isn't going, but i tried it manually in gitpod and got:

12 specs in 0.002s.
>> 0 failures
Fatal error: Callback must be a function. Received undefined

... so same issue. This is lower priority now but pretty annoying!

@TildaDares

Copy link
Copy Markdown
Member

@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) {

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TildaDares didn't i add it here? Or did I miss somewhere else too?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh sorry I didn’t see that😅

@jywarren jywarren closed this Jul 26, 2022
@jywarren jywarren reopened this Jul 26, 2022
@jywarren

jywarren commented Aug 1, 2022

Copy link
Copy Markdown
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants