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

Missing null-check on StorageConnection after casting it to JobStorageConnection #345

Closed
burningice2866 opened this issue Apr 22, 2015 · 5 comments
Labels
Milestone

Comments

@burningice2866
Copy link
Contributor

In the Retries-page of the dashboard, there is a missing Null-check, after casting the current connection to JobStorageConnection. This is a problem if one is using a JobStorage which doesn't implement JobStorageConnection but only IStorageConnection

https://github.com/HangfireIO/Hangfire/blob/master/src/Hangfire.Core/Dashboard/Pages/RetriesPage.cshtml#L21

@odinserj
Copy link
Member

@burningice2866, got it! Would you like to make a PR and point it to the release-1.4.2 branch?

@burningice2866
Copy link
Contributor Author

I'll look at it... can we assume that making an empty JobIds list and pager with 0 records will do the trick?

@odinserj
Copy link
Member

I think we should show the message "Your storage currently does not support lalala and therefore we can't show this page" or so. Otherwise users may think retries aren't working, and ask a lot of questions on forum. On the other hand, if a pager shows this message for empty retries page (this is usual in normal circumstances), they will be sure retries aren't working. So, only null-check will work here, IMO.

@odinserj
Copy link
Member

Hi @burningice2866, any news? I'm planning to release this bug fix in 1.4.2.

@odinserj odinserj added this to the 1.4.2 milestone Apr 27, 2015
@odinserj odinserj added the t: bug label May 5, 2015
@odinserj
Copy link
Member

odinserj commented May 6, 2015

Added the following message:

image

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

No branches or pull requests

2 participants