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

Crash in MailCheck #9

Closed
polonel opened this issue Aug 1, 2016 · 2 comments
Closed

Crash in MailCheck #9

polonel opened this issue Aug 1, 2016 · 2 comments
Assignees

Comments

@polonel
Copy link
Owner

polonel commented Aug 1, 2016

Server crash when trying to convert mail -> ticket in mailcheck.js

TypeError: Cannot read property '_id' of null
at /etc/trudesk/src/mailer/mailCheck.js:138:77
at Query. (/etc/trudesk/node_modules/mongoose/lib/query.js:2181:28)
at /etc/trudesk/node_modules/kareem/index.js:259:21
at /etc/trudesk/node_modules/kareem/index.js:127:16
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
---------------------------------------------
at Kareem.execPost (/etc/trudesk/node_modules/kareem/index.js:126:20)
at /etc/trudesk/node_modules/kareem/index.js:251:15
at Immediate. (/etc/trudesk/node_modules/mongoose/lib/query.js:1160:14)
at Immediate. (/etc/trudesk/node_modules/mquery/lib/utils.js:137:16)
at runCallback (timers.js:570:20)
at tryOnImmediate (timers.js:550:5)
at processImmediate [as _immediateCallback] (timers.js:529:5)
@polonel polonel added the bug label Aug 1, 2016
@polonel polonel self-assigned this Aug 1, 2016
@polonel
Copy link
Owner Author

polonel commented Aug 2, 2016

Default ticket type through MailCheck needs to be set through settings configuration. Currently the bug resides in a hard coded name of Issue as the ticket type. If That ticket type (name=issue) doesn't exist the server will crash.

polonel added a commit that referenced this issue May 11, 2017
@polonel polonel closed this as completed May 11, 2017
@polonel
Copy link
Owner Author

polonel commented Sep 27, 2018

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

No branches or pull requests

1 participant