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.

Sign up for GitHub

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

Jump to bottom

Plugin should ignore corrupted cache #13

Closed
ezolenko opened this issue Apr 18, 2017 · 1 comment
Closed

Plugin should ignore corrupted cache #13

ezolenko opened this issue Apr 18, 2017 · 1 comment
Assignees
@ezolenko
Labels
kind: bug Something isn't working properly solution: workaround available There is a workaround available for this issue

Comments

@ezolenko
Copy link
Owner

Sometimes cache gets corrupted, and plugin throws JSON exception (when build interrupted in wrong place).

[10:30:58] Error: ./.cache/0e05bd66949fbb4a048b752195b45acaa4973026/code/cache/1ebf05433ba5ed0b148851cac444c0fb84ba87c1: Unexpected end of JSON input
    at error (D:\source\scr\screeps-ts\node_modules\rollup\dist\rollup.js:170:12)
    at D:\source\scr\screeps-ts\node_modules\rollup\dist\rollup.js:8926:6
    at process._tickDomainCallback (internal/process/next_tick.js:129:7)

Should catch and fallback instead. Alternatively, use transactions.

Workaround -- cleaning cache and rebuilding.
@ezolenko ezolenko self-assigned this Feb 8, 2018
ezolenko added a commit that referenced this issue Feb 8, 2018
@ezolenko
- ignoring broken cache #13
4e82473
@ezolenko
Copy link
Owner Author

ezolenko commented Feb 13, 2018 •
edited by agilgur5

In 0.11.1 now

@agilgur5 agilgur5 added kind: bug Something isn't working properly solution: workaround available There is a workaround available for this issue labels May 7, 2022
Repository owner locked as resolved and limited conversation to collaborators May 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ezolenko ezolenko

Labels
kind: bug Something isn't working properly solution: workaround available There is a workaround available for this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ezolenko @agilgur5