fixed in both D1386 and D1387
Added a comment in D1386
new diff D1386 uploaded, build failed, how can i check that, I dont have access to jenkins
i can see that, but it tells me nothing https://hub.sealcode.org/harbormaster/build/6125/
Iāve re-run the test manually after restarting jenkins and it un-clogged Will do review soon
two tests are failing in sealious-playground:
/src/back/routes/todo.test.ts
AssertionError: Expected values to be strictly deep-equal:
+ actual - expected
Comparison {
+ name: 'SyntaxError'
- name: 'Error'
}
- Expected
+ Received
- Object {
- "name": "Error",
- }
+ [SyntaxError: Unexpected token 'o', "no access" is not valid JSON]
src/back/routes/logout.test.ts
doesn't crash
AssertionError: Expected values to be strictly deep-equal:
+ actual - expected
Comparison {
+ name: 'SyntaxError'
- name: 'Error'
}
- /src/back/routes/logout.test.ts:30:5
- /src/back/test_utils/with-prod-app.ts:66:3
- Expected
+ Received
- Object {
- "name": "Error",
- }
+ [SyntaxError: Unexpected token 'N', "Not Found" is not valid JSON]
Ah, sorry. Itās a post-merge issue, my bad for not testing it.
Iāve pushed a fixed version
new diffs for cr: D1407, D1408
they includes the same changes as the previous one, but on a new branches. I moved the old changes to new ones cuz I couldnāt fix the old versions after merge conflicts.
In such cases you donāt have to create new diffs. You can just create a new branch in your repo, create a new set of changes, and update those diffs (using the regular arc diff --update
workflow.
Please mark the two new diffs as Abandoned and update the old ones so itās all neat and clean
D1387 and D1386 updated
ready to land!
what if Iām on the new branch and I canāt make patch
$ arc patch 1386
Branch name arcpatch-D1386 already exists; trying a new name.
Branch name arcpatch-D1386_1 already exists; trying a new name.
Branch name arcpatch-D1386_2 already exists; trying a new name.
Branch name arcpatch-D1386_3 already exists; trying a new name.
Exception
Published to NPM as @sealcode/jdd@0.3.3