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

TextMatcherEnvelope should call asString() only once at all #132

Closed
victornoel opened this issue Jun 29, 2019 · 37 comments
Closed

TextMatcherEnvelope should call asString() only once at all #132

victornoel opened this issue Jun 29, 2019 · 37 comments

Comments

@victornoel
Copy link
Collaborator

All the Matcher<Text> that relies on TextMatcherEnvelope suffers from having asString() being called multiple times.

In some case it can be a problem, for example when a Text is based on an InputStream that can be read only once. See for example yegor256/cactoos#1145 (comment)

I believe TextMatcherEnvelope should wraps text into some kind of Sticky decorator to avoid any problem.

@0crat
Copy link
Collaborator

0crat commented Jun 29, 2019

@llorllale/z please, pay attention to this issue

@llorllale
Copy link
Owner

llorllale commented Jun 29, 2019

@victornoel funny - I was just reading this today. I'm closing this issue and deferring this conversation for later. I'll accept your PR in yegor256/cactoos#1145 as is

@0crat
Copy link
Collaborator

0crat commented Jun 29, 2019

Job gh:llorllale/cactoos-matchers#132 is not assigned, can't get performer

@0crat
Copy link
Collaborator

0crat commented Jun 29, 2019

This job is not in scope

@victornoel
Copy link
Collaborator Author

@llorllale I've read it too, I don't agree with the content personally. That being said, I don't think this issue is about caching or not caching, it is just about having a consistent behaviour of Text matchers, whatever the mean used to solve the problem.

@llorllale
Copy link
Owner

@victornoel what do you propose? Wrap it in Sticky in TextMatcherEnvelope#matchesSafely()?

@victornoel
Copy link
Collaborator Author

@llorllale I would have done something like that yes I think

@llorllale llorllale reopened this Jul 4, 2019
@llorllale
Copy link
Owner

@0crat in

@0crat
Copy link
Collaborator

0crat commented Jul 4, 2019

@llorllale/z please, pay attention to this issue

@0crat
Copy link
Collaborator

0crat commented Jul 4, 2019

@0crat in (here)

@llorllale Job #132 is now in scope, role is DEV

@0crat
Copy link
Collaborator

0crat commented Jul 4, 2019

Bug was reported, see §29: +15 point(s) just awarded to @victornoel/z

@0crat
Copy link
Collaborator

0crat commented Aug 6, 2019

The job #132 assigned to @umbrah/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

@0crat
Copy link
Collaborator

0crat commented Sep 11, 2019

The architect of the project has changed; @llorllale/z is not at this role anymore; @paulodamaso/z is the architect now

@victornoel
Copy link
Collaborator Author

@paulodamaso I'm blocked by this to solve other issues in cactoos, the fix is quite simple, can this be proactively assigned to somebody and a release made if possible?

@paulodamaso
Copy link
Contributor

@victornoel Can you do it for us?

@victornoel
Copy link
Collaborator Author

@paulodamaso yes

@paulodamaso
Copy link
Contributor

@0crat assign @victornoel

@paulodamaso
Copy link
Contributor

@victornoel Thanks!

@0crat
Copy link
Collaborator

0crat commented Sep 24, 2019

@0crat assign @victornoel (here)

@paulodamaso The job #132 assigned to @victornoel/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

@0crat
Copy link
Collaborator

0crat commented Sep 24, 2019

@0crat assign @victornoel (here)

@paulodamaso There is an unrecoverable failure on my side. Please, submit it here:

PID: 4@da69ffec-8968-43a0-8327-1386ee9c8dff, thread: pool-26-thread-2
com.zerocracy.claims.ClaimIn[198] java.lang.IllegalArgumentException: Parameter "age" not found in "Order was canceled" among: [comment, job, issue, repo, cause, _parent_sig, flow, login]

0.49.12: CID: 83a83d7a-f893-4ce9-9d24-3d070b7eb495, Type: "Order was canceled"

@0crat
Copy link
Collaborator

0crat commented Sep 24, 2019

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @paulodamaso/z

@0crat
Copy link
Collaborator

0crat commented Sep 24, 2019

It is strongly discouraged to assign jobs to their creators, see §19: -15 point(s) just awarded to @paulodamaso/z

@victornoel
Copy link
Collaborator Author

@0crat wait for #147

@0crat
Copy link
Collaborator

0crat commented Sep 24, 2019

@0crat wait for #147 (here)

@victornoel The impediment for #132 was registered successfully by @victornoel/z

@victornoel
Copy link
Collaborator Author

@paulodamaso can we get a new release of cactoos-matchers now that this has been merged?

@0crat
Copy link
Collaborator

0crat commented Oct 5, 2019

@sereshqua/z please review this job completed by @victornoel/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

@0crat
Copy link
Collaborator

0crat commented Oct 5, 2019

The job #132 is now out of scope

@sereshqua
Copy link

@victornoel we will need to make sure that problem reporter and problem solver are two different persons next time

@victornoel
Copy link
Collaborator Author

@sereshqua yes I agree

@sereshqua
Copy link

@0crat quality acceptable

@0crat
Copy link
Collaborator

0crat commented Oct 5, 2019

Quality review completed: +4 point(s) just awarded to @sereshqua/z

@0crat
Copy link
Collaborator

0crat commented Oct 5, 2019

Order was finished, quality is "acceptable": +30 point(s) just awarded to @victornoel/z

@paulodamaso
Copy link
Contributor

@

@paulodamaso can we get a new release of cactoos-matchers now that this has been merged?

@victornoel of course

@paulodamaso
Copy link
Contributor

@rultor release tag is 0.18

@rultor
Copy link
Collaborator

rultor commented Oct 6, 2019

@rultor release tag is 0.18

@paulodamaso OK, I will release it now. Please check the progress here

@rultor
Copy link
Collaborator

rultor commented Oct 6, 2019

@rultor release tag is 0.18

@paulodamaso Done! FYI, the full log is here (took me 11min)

@victornoel
Copy link
Collaborator Author

@paulodamaso thx

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

6 participants