-
Notifications
You must be signed in to change notification settings - Fork 9
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
Reporting started failing on CI #20
Comments
I'm having the same issue, it's failing because the I thought maybe the issue was from undici, but I did a quick test and it was working great 'use strict'
// import undici from 'undici'
const undici = require('undici')
async function getPackageMetadataFromRegistry() {
const { body } = await undici.request(
`https://registry.npmjs.org/${encodeURIComponent('classname')}`,
{
method: 'GET',
headers: {
'content-type': 'application/json'
}
}
)
const dataBuffer = []
for await (const data of body) {
dataBuffer.push(data)
}
const packageMetadata = Buffer.concat(dataBuffer).toString('utf8')
const packageMetadataObject = JSON.parse(Buffer.from(packageMetadata).toString('utf8'))
console.log(packageMetadataObject)
}
getPackageMetadataFromRegistry() OutputI'll keep debugging maybe I'll find a solution. Thank you |
The issue started happening when undici was updated to 5.10.0 so it might be an error there after all. Can you try with previous version and see if buffer is still empty? |
@meeroslav, it's working after updating undici to 5.10.0 👍🏻 |
Interesting why that happens. Thanks @meeroslav and @bscript for confirming. I'll merge the PR with the update next and publish a new version. |
We have a nightly audit check where we run
npx snync -d .
. Since last night this call started failing with the following error report:as seen here: https://github.com/nrwl/nx/runs/7992209443
Locally running
snync
works as expected (although locally we have all packages installed while on CI we only do checkout).Strangely,
classnames
hasn't been published for over a year, the next package that should be checked,cliui
hasb't been changed for over 2 years, and the difference betweensnync
1.3.3 and 1.3.2 seems to be only in README.md. Running with v1.3.2 explicitly (i.e.npx [email protected] -d .
) gives the same error.Output from https://registry.npmjs.org/classnames is valid JSON and the same goes for https://registry.npmjs.org/cliui.
Expected Behavior
Running
npx snync -d .
on CI not to crash.Current Behavior
Running
npx snync -d .
on CI crashes.Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: