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

Fix/issue #2: Lorem picsum client hangs #23

Merged
merged 2 commits into from
Oct 25, 2022
Merged

Fix/issue #2: Lorem picsum client hangs #23

merged 2 commits into from
Oct 25, 2022

Conversation

giulianopz
Copy link
Contributor

As said in the commit message:

It seems the only reasonable thing to do, since the service does not enforce rate limiting as per this blogpost: https://dmarby.se/blog/lorem-picsum/.
Only clients generating a very high load are blocked at their cache layer.

I don't know if the timeout should be configurable via flag.

It seems the only reasonable thing to do,
since the service does not enforce rate limiting as per this blogpost: https://dmarby.se/blog/lorem-picsum/.
Only clients generating a very high load are blocked at their cache layer.
@giulianopz giulianopz mentioned this pull request Oct 24, 2022
@enrichman
Copy link
Owner

Fair enough, I was looking for a golang Picsum client with no luck.

Did you reproduced the issue?

@giulianopz
Copy link
Contributor Author

I was not able to reproduce the issue. The differences with regard to response times seem quite normal:

giulianopz@machine:~/git/stegosecrets(fix/issue-2-lorem-picsum-client-hangs)$ while sleep 0.1; do /bin/time -f "\t%E clock-wall time ([hours:]minutes:seconds)" ./stego images; done
        0:03.88 clock-wall time ([hours:]minutes:seconds)
        0:02.15 clock-wall time ([hours:]minutes:seconds)
        0:02.98 clock-wall time ([hours:]minutes:seconds)
        0:03.10 clock-wall time ([hours:]minutes:seconds)
        0:01.81 clock-wall time ([hours:]minutes:seconds)
        0:01.47 clock-wall time ([hours:]minutes:seconds)
        0:02.41 clock-wall time ([hours:]minutes:seconds)
        0:02.31 clock-wall time ([hours:]minutes:seconds)
        0:01.74 clock-wall time ([hours:]minutes:seconds)
        0:01.73 clock-wall time ([hours:]minutes:seconds)
        0:02.00 clock-wall time ([hours:]minutes:seconds)
        0:02.12 clock-wall time ([hours:]minutes:seconds)
        0:02.35 clock-wall time ([hours:]minutes:seconds)
        0:10.84 clock-wall time ([hours:]minutes:seconds)
        0:01.81 clock-wall time ([hours:]minutes:seconds)
        0:02.02 clock-wall time ([hours:]minutes:seconds)
        0:04.81 clock-wall time ([hours:]minutes:seconds)
        0:02.78 clock-wall time ([hours:]minutes:seconds)
        0:02.00 clock-wall time ([hours:]minutes:seconds)
        0:04.20 clock-wall time ([hours:]minutes:seconds)
        0:02.62 clock-wall time ([hours:]minutes:seconds)
        0:02.63 clock-wall time ([hours:]minutes:seconds)
        0:06.90 clock-wall time ([hours:]minutes:seconds)

Nevertheless, setting a timeout makes still sense probably.

@enrichman
Copy link
Owner

Yes, agree. Let's merge this, we still have lot of improvements that we are going to add!

Thanks

@enrichman enrichman merged commit 30d1143 into enrichman:main Oct 25, 2022
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

Successfully merging this pull request may close these issues.

2 participants