-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Make filter poll lifetime configurable #5484
Comments
Hi @se3000, Do you think that using an |
|
Alright, i'll start working on it today. I'm thinking on looking for a |
@dawsonfi wouldn't it make more sense to put this with the rest of the configuration in the CLI and config.toml? |
Sounds good to me @rphmeier, i'll take a look at the CLI and see how can i do this. |
Toml makes sense to me, preferably with the rest of the config settings.
…On Wed, Oct 4, 2017 at 8:47 AM Dawson Freitas Israel < ***@***.***> wrote:
Sounds good to me @rphmeier <https://github.com/rphmeier>, i'll take a
look at the CLI and see how can i do this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5484 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjBgzVDyX1DlsIootXx-OYi1HiV5DdTks5so6h7gaJpZM4NDghQ>
.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 0.18 ETH (100.82 USD @ $560.13/ETH) attached to it.
|
... rather than it being a hard-coded constant. fixes openethereum#5484 .
... rather than it being a hard-coded constant. fixes openethereum#5484 .
... rather than it being a hard-coded constant. fixes openethereum#5484 .
... rather than it being a hard-coded constant. fixes #5484 .
I believe @gitcoinbot is wrong here. The issue is already resolved and the bounty belongs to @gnunicorn |
@gnunicorn Mind clicking both 'Start Work' and 'Submit Work' on Gitcoin here in order to claim the bounty? If you need a bit of ETH to make the submission, the Gitcoin Faucet can help! Removed the other Gitcoiner for now 🙂 |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Work has been started. These users each claimed they can complete the work by 8 months, 1 week ago. 1) marcleuenberger1987 has started work. What steps will you take to complete this task? Example:dfddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddddd Learn more on the Gitcoin Issue Details page. |
@marcleuenberger1987 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
5 similar comments
@marcleuenberger1987 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@marcleuenberger1987 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@marcleuenberger1987 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@marcleuenberger1987 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@marcleuenberger1987 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days |
@vs77bb could you disable the bot here? |
⚡️ A tip worth 0.18000 ETH (47.84 USD @ $265.77/ETH) has been granted to @gnunicorn for this issue from @vs77bb. ⚡️ Nice work @gnunicorn! Your tip has automatically been deposited in the ETH address we have on file.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done The funding of 0.18 ETH (47.84 USD @ $265.77/ETH) attached to this issue has been approved & issued.
|
@Tbaut Sorry about crazy Gitcoin Bot 😦 We introduced a new feature which allows us to pay out @gnunicorn without him 'submitting work', which is good. He has now been paid for his work here. |
Poll lifetime is currently hardcoded to 60 seconds. Scheduling software like cron runs at granularity of 60 seconds, and with high traffic, or a queue of filters to check, it's easy to exceed the 60 second lifetime.
Is it possible to make this configurable? Is there a downside?
The text was updated successfully, but these errors were encountered: