Mark Tse
Mark Tse
I was able to find a comment on a related issue that suggests this should work: https://github.com/zkat/npx/issues/112#issuecomment-416150324 The following commands ``` $ npx @vue/cli $ mono $ mono-sgen ``` result...
* [ ] Ignore `v4BreakingChanges` config and set it to always be true * [ ] Update changelog * [ ] Update readme * [ ] Release * [ ]...
The README says > The env resolution pattern follows the one used by Rail's dotenv and create-react-app But the code says https://github.com/neverendingqs/serverless-dotenv-plugin/blob/6fc076c692c2947951966967041e24e10fb4df01/index.js#L64-L72 and https://github.com/neverendingqs/serverless-dotenv-plugin/blob/6fc076c692c2947951966967041e24e10fb4df01/index.js#L84-L91 That last `.reduce()` call means we're...
Right now, all Lambda function environments are configured with all variables in the dotenv file(s). This can easily cause security issues by setting environment variables that contain secrets (e.g. `SENTRY_SECRET`...
It looks like this got missed in https://github.com/ghdna/athena-express/commit/7bd6429948508727e1128f18e6cad75a3e1d16dc#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519.
> the PR looks ok, but I'm a bit worried about growing nimber of options like yours. Maybe we should move to much simple api, for example `toNumber()` callback that...
The [S3 client for v3 of the SDK](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-s3/index.html) signature has changed when trying to create a read stream. The signature has changed so that instead of https://github.com/ZJONSSON/node-unzipper/blob/7f83183d4475abeaaa9251d3511c840647bca788/lib/Open/index.js#L86-L92, it would have...
This change will help with tools that do automated license checks by switching to the SPDX identifier for the Apache 2.0 license. --- https://docs.npmjs.com/cli/v6/configuring-npm/package-json#license says: > If you're using a...
Resolves https://github.com/serverless/serverless/discussions/10307#discussioncomment-1771918
### Describe the bug I think `CompletableFuture`s seems to always be on or reverts to the default shared `ForkJoinPool` even if an `Executor` is provided via `FUTURE_COMPLETION_EXECUTOR` when making `S3TransferManager`...