Getting errors about session file store when 2 prototypes have the same name

[joelanman]

Description of the issue

When running v13 I get this output in the terminal:

[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open '/Users/joelanman/projects/starter3/.tmp/sessions/FJWPmQnb3pF2KZVp5cfDxgcJpeHRgwFm.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open '/Users/joelanman/projects/starter3/.tmp/sessions/FJWPmQnb3pF2KZVp5cfDxgcJpeHRgwFm.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open '/Users/joelanman/projects/starter3/.tmp/sessions/FJWPmQnb3pF2KZVp5cfDxgcJpeHRgwFm.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open '/Users/joelanman/projects/starter3/.tmp/sessions/FJWPmQnb3pF2KZVp5cfDxgcJpeHRgwFm.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open '/Users/joelanman/projects/starter3/.tmp/sessions/FJWPmQnb3pF2KZVp5cfDxgcJpeHRgwFm.json'

It will try five times to find the file and then just create a new session, so the issue is just console warnings

Steps to reproduce the issue

• start a prototype in one folder, visit the home page, stop that prototype
• start another prototype and visit the homepage

Actual vs expected behaviour

Shouldn't get warnings in the terminal

Environment (where applicable)

• Operating system: MacOS
• Browser: Chrome
• GOV.UK Prototype Kit version: 13

[lfdebrux]

I think there is a step missing from 'steps to reproduce the issue': if I visit the page with an incognito browser or having cleared my cookies, the error won't appear. What is needed to reproduce this is start a prototype in one folder, visit the home page, stop that prototype, then start another prototype and visit the homepage for that.

The output we then see is the expected behaviour of session-file-store, because the browser cookies contain a session key for a session from another prototype. So I'm not sure whether we want to just suppress these warnings, or what?

Edit to add: the two prototypes also have to have the same service name, as we currently base the name of the cookie on the service name. If the two prototypes have different service names the sessions can happily coexist. So I guess we could fix this by using something other than the service name for generating the cookie name?

[joelanman]

thanks, I didn't know thats what was causing it, will update the steps to reproduce