-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whitelist kea-typegen folder in .dockerignore #1443
Conversation
Added DEBUG to dev.Dockerfile since the lack of it was causing a crash after the secret key PR was merged. Thought it'd be better here than a separate PR |
I'm still getting a Kea error though: $ kea-typegen write && echo "Building Webpack" && NODE_ENV=production webpack --config webpack.config.js && cp -a frontend/public/* frontend/dist/ && npm run copy-array
/code/node_modules/kea-typegen/node_modules/yargs/build/lib/yargs.js:1132
throw err;
^
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
at validateString (internal/validators.js:120:11)
at Object.dirname (path.js:1128:5)
at includeKeaConfig (/code/node_modules/kea-typegen/dist/cli/typegen.js:54:32)
at Object.handler (/code/node_modules/kea-typegen/dist/cli/typegen.js:15:44)
at Object.runCommand (/code/node_modules/kea-typegen/node_modules/yargs/build/lib/command.js:196:48)
at Object.parseArgs [as _parseArgs] (/code/node_modules/kea-typegen/node_modules/yargs/build/lib/yargs.js:1043:55)
at Object.get [as argv] (/code/node_modules/kea-typegen/node_modules/yargs/build/lib/yargs.js:986:25)
at Object.<anonymous> (/code/node_modules/kea-typegen/dist/cli/typegen.js:36:14)
at Module._compile (internal/modules/cjs/loader.js:1137:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10) {
code: 'ERR_INVALID_ARG_TYPE'
}
error Command failed with exit code 1.
|
Different error following the latest commit:
|
Let's try again :). I'm building docker-compose.e2e.yml locally, so it's taking some time before I see the error. |
Yup, Mac starts hissing quite a bit... |
Last commit worked for me! |
But I built with dev.yml - You might get a secret key issue with e2e.yml - think I need to add DEBUG to production.Dockerfile too |
Hm... For me it still kept giving errors even after the last changes. I think the last commit will fix it (still running locally to verify) |
Try now |
I'd do the same trick in |
Those two pictures above are from the same run. It's something that might need to be looked at more in-depth. But one thing that might be useful for this and other scenarios is a |
Suppressing warnings can lead to all sorts of hard to track bugs... In this case I'd just make a random secret key for There are a bunch of broken Cypress tests again that I'm trying to resolve for PR #1424. I propose they shouldn't be a blocker here, as they happen in every branch :/. |
No I'm not sure - It was pretty late and I probably missed. Think that was it. |
I still think |
We don't know what warnings it will suppress in the future though :)... and I fear it'll be surely abused by some people to get rid of the "annoying" debug/key warnings in production without understanding the full story nor implementing a proper fix. If needed, adding |
Yup makes sense! And now that you've updated the keys, this should be okay? Deployment failed though... |
I don't have access to Heroku so can't see what's going on |
Ok yeah - All Cypress tests are also failing so I guess it's completely unrelated |
Those are failing in other PRs as well. Looking at what's happening, I think it might somehow be related to an antd version upgrade. I'll try to debug this next. That's outside the scope of this PR though. |
Nice! |
Can you approve the PR? :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're good now.
TIL: Github works as a chat as well :D (apologies to the 47 people watching) |
Changes
Checklist