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

session-file-store on Windows can sometimes have EPERM: operation not permitted rename errors #1811

Closed
lfdebrux opened this issue Nov 24, 2022 · 5 comments
Assignees
Labels
🐛 Bug Something isn't working the way it should (including incorrect wording in documentation) Submitted by user issues on behalf of users

Comments

@lfdebrux
Copy link
Member

lfdebrux commented Nov 24, 2022

Description of the issue

On Windows, a prototype will intermittently print errors similar to the following in the terminal:

EPERM: operation not permitted, rename 'C:\Users\lfdeb\Documents\prototypes\test-prototype\.tmp\sessions\ehaFpZQViD5Q~FAGIXwYAKFjsASLKJ.json.4283232820' -> 'C:\Users\lfdeb\Documents\prototypes\test-prototype\.tmp\sessions\ehaFpZQViD5Q~FAGIXwYAKFjsASLKJ.json.4283232820'

Steps to reproduce the issue

In a prototype with forms, click around the prototype, answer questions.

A nice and simple example is available at https://github.com/asmith-nhsx/prototypes/tree/main/rocket-licence

Actual vs expected behaviour

No errors in terminal.

Environment (where applicable)

  • Operating system: Windows
  • GOV.UK Prototype Kit version: 13.0.0
@lfdebrux lfdebrux added 🐛 Bug Something isn't working the way it should (including incorrect wording in documentation) Submitted by user issues on behalf of users awaiting triage labels Nov 24, 2022
@lfdebrux
Copy link
Member Author

Looking at the issues for session-file-store, this appears to be a known bug, but it's been open for some time with multiple attempts at fixing it 😟

valery-barysok/session-file-store#69

@joelanman
Copy link
Contributor

seeing this with both users in training on Windows

@HannahJMWood
Copy link
Contributor

HannahJMWood commented Apr 19, 2023

Read through the link that @lfdebrux shared in his comment above. This does seem to be a known bug with session-file-store. As it's not been fixed yet and our investigations have found that it doesn't effect our session storing functionality, we have decided to implement a suppression of these errors so that users don't see them and panic.

@HannahJMWood
Copy link
Contributor

Need to re-visit and test this to make sure that its not an issue anymore following the new implementation of the session file store

@HannahJMWood
Copy link
Contributor

@ollie-b-gds and I have tested this on a Windows VM. We're not seeing the errors anymore so we're happy to close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working the way it should (including incorrect wording in documentation) Submitted by user issues on behalf of users
Projects
None yet
Development

No branches or pull requests

5 participants