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

JM - (Production Bug) An Errno::ENOENT occurred in service_requests#c… #1002

Merged
merged 1 commit into from Jul 14, 2017

Conversation

jwiel86
Copy link
Contributor

@jwiel86 jwiel86 commented Jul 14, 2017

@amcates
Copy link
Collaborator

amcates commented Jul 14, 2017

Good fix but FYI, this only happens when I first deploy. Once the cronjob runs it creates the file. Another option would be to fire off the cronjob on deploy. This solution suites our needs so no need to look at my option.

@jwiel86
Copy link
Contributor Author

jwiel86 commented Jul 14, 2017

That's what Stuart was telling me, but when I talked to Wenjun it looked like it was happening several times a month.

@amcates
Copy link
Collaborator

amcates commented Jul 14, 2017

Yes, when we would deploy bug fixes. No worries, good fix. Makes it even better.

@Stuart-Johnson Stuart-Johnson merged commit ca9361a into v3.0.0 Jul 14, 2017
@Stuart-Johnson Stuart-Johnson deleted the jm-no-such-file-production-bug branch July 14, 2017 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants