-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fix intermittent CI build failures and add basic Angular functional tests #193
base: main
Are you sure you want to change the base?
Conversation
app.get("*", (request, response) => { | ||
response.sendFile(path.join(__dirname, "..", "browser", "index.html")); | ||
}); |
Check failure
Code scanning / CodeQL
Missing rate limiting High
a file system access
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.
Since this is a static, single file, not dynamic we can probably ignore this if express caches; else we should read into memory.
Something about the lru types is very broken ATM (see the build result of #190, #191, etc.), from local error messages it seems that they are passthrough now and not required... but that conflicts with the linked logs. Very flaky, regardless, this all seems to resolve on an NPM install and on CI we are skipping that on an NPM cache hit. IMO we should just call
npm ci
everytime right now, until we can figure out why the NPM cache step is insufficient / flaking.While I was working on reproducing this I noted that the way we were packing adapter-angular/simple-server was also confusing things (see run #9114734835), so I took a pass on fixing that.
npm ci
run even on npm cache hit