last fixes
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 12 2023
create a very useful "tip generator"
use resolve() → resolvex() that natively throws a nice exception message
Thanks for the additional checking and docs!
Hi @Leon95: green light :)
Hoping to be useful I try to reset the Block from our kind Matthew since it was related to a past merge conflict
Thanks for addressing this issue
Thanks again
fix typo (sorry)
add minor inline documentation
I double-checked this multiple times and I think the approach is really the minimal necessary to achieve this goal in a safe way.
May 11 2023
To other reviewers: the related lint errors will be fixed also thanks to aklapper: D25209
I tested this patch locally following the test plan. No implosions.
I noticed that it exists a ExecFuture#resolvex() method that is the exact replacement of ExecFuture#resolve() but throws a CommandException.
May 10 2023
It hadn't happened in a while, so I guess it was something strange in my machine.
Seems reasonable and simple enough. Can we get a Blessed Committer to accept this?
I tried to write down the input domain:
Thanks again
Please see my inline comment, probably just adding 3 characters fixes, and that would be probably the approach from O1
Tested locally. Adding an email. Adding no email. Multiple fuzz tests. No implosions.
May 9 2023
In D25209#6204, @valerio.bozzolan wrote:Just to clarify, do you have an idea about the input domain of $a? (I will test this tomorrow)
So apparently this is not a problem in the unit test itself but just with T15375
Just to clarify, do you have an idea about the input domain of $a? (I will test this tomorrow)
I DON'T BELIEVE THIS