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.

Sign up for GitHub

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

Jump to bottom

Passing error upstream - introduction of error codes #88

Open
carmenfan opened this issue Feb 11, 2016 · 1 comment
Open

Passing error upstream - introduction of error codes #88

carmenfan opened this issue Feb 11, 2016 · 1 comment
Labels
enhancement Maintenance

Comments

@carmenfan
Copy link
Member

Error messages that occur within the bouncer needs to be passed back upstream all the way back to controller, so any clients can take the error message and produce whatever error warnings they wish
@carmenfan carmenfan added this to the 3drepobouncer 1.0b milestone Feb 11, 2016
@carmenfan carmenfan mentioned this issue Feb 11, 2016
Closed
@carmenfan carmenfan modified the milestones: 3drepobouncer 1.0b, Next Release Mar 21, 2016
@carmenfan carmenfan changed the title Error messages needs to be passed back upstream Passing error upstream - introduction of error codes Apr 18, 2016
@carmenfan
Copy link
Member Author

Instead of error messages + true/false for success/failure, we should move onto establishing an error code. The gui should probably represent the error in a user comprehensible way, which may not always be the same as what we want to dump on log file.

@carmenfan carmenfan removed this from the Next Release milestone Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Maintenance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@carmenfan