Error on merging current blocked requesters
See original GitHub issueHello, using WAF Regional stack for a few days, and found this on LambdaWAFLogParserFunction log:
[merge_current_blocked_requesters] Calculate Last Update Age
[merge_current_blocked_requesters] Download current blocked IPs
[merge_current_blocked_requesters] Expire Block IP rules
[merge_current_blocked_requesters] Error merging 140.119.169.126 rule
can't subtract offset-naive and offset-aware datetimes
[merge_current_blocked_requesters] End
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Error on merging current blocked requesters · Issue #18 · aws ...
Hello, using WAF Regional stack for a few days, and found this on LambdaWAFLogParserFunction log: [merge_current_blocked_requesters] Calculate Last Update ...
Read more >git - Github - Merging is blocked (confusing/misleading error ...
This is what I'm currently dealing with. This is exactly why the message "Merging can be performed automatically once the requested changes are ......
Read more >Unclear merge widget message when MR is blocked ... - GitLab
In a situation where a merge request is ready to get merged, but blocked by another MR that it is depending on, the...
Read more >How to block the merge of Current PR if the previous CI build ...
I have two branches of master & dev in Azure Repo ....if i made a PR from dev to master...if the previous CI...
Read more >Merging tickets - Zendesk help
If you don't have ticket CCs enabled, you can only merge two tickets if they are from the same requester. The most recent...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
the problem comes from the
total_diff_min = ((now_timestamp - prev_updated_at).total_seconds())/60
lines. the prev_update_at does not have any timezone associated to it. I had to add the UTC timezone to it for it to work.Hi,
Thanks for the comment and recommendation about how to fix it.
The current version is supposed to use the same timezone. Here.