-
Notifications
You must be signed in to change notification settings - Fork 14
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
Update bookhound #410
Comments
Package source does not have a purs.json file. Creating one from your bower.json and/or spago.dhall files... |
Verifying package... |
{
"name": "bookhound",
"ref": "v0.1.4",
"compiler": "0.15.10"
} |
Package source does not have a purs.json file. Creating one from your bower.json and/or spago.dhall files... |
Verifying package... |
This is the exception happening in CI. I can take a look later on.
|
{
"name": "bookhound",
"ref": "v0.1.4",
"compiler": "0.15.10"
} |
Package source does not have a purs.json file. Creating one from your bower.json and/or spago.dhall files... |
Verifying package... |
It seems to be a V8 bug (still open). Reported in node as well: nodejs/node#47928 |
@f-f The message is making me suspicious that this is really us getting to the end of the stack but masquerading as this bug when allocating more memory. Trying a quick fix on a branch; {
"name": "bookhound",
"ref": "v0.1.4",
"compiler": "0.15.10"
} |
Package source does not have a purs.json file. Creating one from your bower.json and/or spago.dhall files... |
Verifying package... |
All right. I'll need to reproduce this in our test cases locally if it's possible to do so, but I won't be able to do that until tomorrow. |
I was able to reproduce and fix the issue. {
"name": "bookhound",
"ref": "v0.1.4",
"compiler": "0.15.10"
} |
Package source does not have a purs.json file. Creating one from your bower.json and/or spago.dhall files... |
Verifying package... |
Package is verified! Uploading it to the storage backend... |
Successfully uploaded package to the registry! 🎉 🚀 |
Successfully uploaded package docs to Pursuit! 🎉 🚀 |
Mirrored registry operation to the legacy registry. |
The text was updated successfully, but these errors were encountered: