-
Notifications
You must be signed in to change notification settings - Fork 61
*: bump actix/actix-web to 0.8.3/1.0.2 #123
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
*: bump actix/actix-web to 0.8.3/1.0.2 #123
Conversation
f261276 to
5bf8a92
Compare
policy-engine/src/graph.rs
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will result in a client-controlled panic if len < 2, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed! where len < 2 means the query argument doesn't contain a =. In that case we should probably give a meaningful error to the client.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the processing of the query string isn't in the future chain it's not straight forward to generate an error for the user here. The current behavior in master is that such values are filled in with the empty string, so I'm opting for retaining that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lucab let me know if you agree, then I'll squash the fixup commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack. I agree it makes sense to either use an empty string, or filter-out valueless keys (assuming we'll never need a valueless key).
d3b4724 to
73d53d2
Compare
2b1c32a to
9b2b453
Compare
9b2b453 to
9bdd7ca
Compare
2984cd2 to
d0448ef
Compare
d0448ef to
8b51001
Compare
|
On local tests I noticed that the errors aren't reported as JSON strings to the client from the policy-engine. Instead the body is empty. I added some more tests to |
193b47d to
e1c1e1d
Compare
|
@lucab this one's ready for the next round. PTAL |
|
@steveej thanks for bumping it! I did another pass and only spot a few minor things, so I think this is mostly ready to land. There are some manifest+lockfile conflicts to adjust after the |
e1c1e1d to
0959f2d
Compare
0959f2d to
7ba092e
Compare
7ba092e to
1961401
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lucab, steveeJ The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
TODO