Skip to content
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

"unrecognised content at end of stream" for Mac/Windows team #151

Open
varya opened this issue May 24, 2021 · 5 comments
Open

"unrecognised content at end of stream" for Mac/Windows team #151

varya opened this issue May 24, 2021 · 5 comments

Comments

@varya
Copy link
Contributor

varya commented May 24, 2021

The screenshots made under Unix (Mac) don't work on Windows. Every single story gave this error

[START:chrome.desktop:4468] Utilities/Typography/Link
[FAIL:chrome.desktop:4468] Utilities/Typography/Link
   Error: unrecognised content at end of stream
    at module.exports.SyncReader.process (node_modules\pngjs\lib\sync-reader.js:43:11)
    at module.exports (node_modules\pngjs\lib\parser-sync.js:68:10)
    at Object.exports.read (node_modules\pngjs\lib\png-sync.js:7:10)
    at compareImages (node_modules\creevey\lib\server\worker\chai-image.js:48:39)
    at assertImage (node_modules\creevey\lib\server\worker\chai-image.js:99:11)
    at Proxy.matchImage (node_modules\creevey\lib\server\worker\chai-image.js:107:28)
    at Context.storyTest (node_modules\creevey\lib\server\stories.js:43:5)

Screenshot_2021-05-24 Creevey

Perhaps it is related to pngjs/pngjs#235 ?

We use

node v14.15.4
npm 6.14.4
creevey 0.7.28

@hamitzor
Copy link

Having the same problem.

@hamitzor
Copy link

I strongly believe Git LFS has something to do with this, as @varya pointed out, because when I have PNGs that have not been interacted with Git LFS the error disappears.

@mwiemer-microsoft
Copy link

Yes, I got the same with an Azure Pipelines build when we used Git LFS in our repo. Removing Git LFS resolved the problem.

@blingerson
Copy link

I have this issue without git LFS being installed on our repo. Anyone have a workaround?

@srpalwaidynamite
Copy link

I have this issue without git LFS being installed on our repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants