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

No nautilus feedback of expired password #29

Closed
alexfelmeister opened this issue Jun 14, 2017 · 11 comments
Closed

No nautilus feedback of expired password #29

alexfelmeister opened this issue Jun 14, 2017 · 11 comments
Assignees

Comments

@alexfelmeister
Copy link
Collaborator

alexfelmeister commented Jun 14, 2017

screen shot 2017-06-14 at 11 30 25 am

@seg1129
Copy link
Collaborator

seg1129 commented Jun 15, 2017

When Nautilus password is expired there is not notification through the BRP. The user only sees an empty list of aliquots - see the example screenshot above.

@seg1129 seg1129 changed the title No nautilus feedback of associated aliquots (kits) No nautilus feedback of expired password Jun 15, 2017
@seg1129
Copy link
Collaborator

seg1129 commented Jun 20, 2017

@alexfelmeister, will this error message help?

screen shot 2017-06-20 at 4 57 34 pm

@alexfelmeister
Copy link
Collaborator Author

Absolutely! "Unable to communicate with Laboratory System, please contact the data coordinating center or eigsupport@email.chop.edu.

@alexfelmeister
Copy link
Collaborator Author

Unable to communicate with Laboratory System because of expired or incorrect credentials. Please contact the data coordinating center or eigsupport@email.chop.edu.

@seg1129
Copy link
Collaborator

seg1129 commented Jun 23, 2017

screen shot 2017-06-23 at 9 46 14 am

@seg1129 seg1129 self-assigned this Jul 10, 2017
@seg1129
Copy link
Collaborator

seg1129 commented Jul 18, 2017

Tyler - I created a release and updated the BRP wit the version number, however the change is still not reflected in production. Any thoughts as to what I missed?

@tjrivera
Copy link
Contributor

@seg1129 there is still no automatic deployment from master to production. You have to manually deploy the latest changes.

@seg1129
Copy link
Collaborator

seg1129 commented Jul 18, 2017

@tjrivera I deployed the BRP last night Jenkins run #148

@tjrivera
Copy link
Contributor

It looks like your last commit updates the requirements.txt but does not update the dependencies in the Dockerfile It is still using 1.0.4

@seg1129
Copy link
Collaborator

seg1129 commented Jul 18, 2017

Ah! Thank you! I knew I was missing something.

@seg1129
Copy link
Collaborator

seg1129 commented Jul 18, 2017

This issue is resolved with Datasources version 1.0.5

@seg1129 seg1129 closed this as completed Jul 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants