-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Feat: Add http/http keyword timeout option #2142
Conversation
src/pages/EditMonitor.vue
Outdated
@@ -606,6 +611,10 @@ export default { | |||
if (this.monitor.retryInterval === oldValue) { | |||
this.monitor.retryInterval = value; | |||
} | |||
// keep timeoutMs below interval, minding the unit conversion | |||
if (!this.monitor.timeoutMs || this.monitor.timeoutMs >= value * 1000) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could it be be better to limit to 80%
here? What are your thoughts? Your choice!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be a good idea to have some sort of limit to make sure that the previous request has definitely finished before the next one is sent
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you prefer less or equal than 80% of the interval seconds
I can change it at once ;)
Please let me know. (cc. @louislam asking for owner's opinion)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't add the English translations to non English files as it will fall back to the English translation if no other translation is found and will just cause merge conflicts later. I assume you ran npm run update-language-files
.
@louislam Should we perhaps change this script so it doesn't update all the files and instead only changes a specific one? I don't really see any situation where it it useful and it only seems to create work for contributers when they run it and commit the results, only to be told to revert it.
I see, let me update the PR to comply the best practice! |
This reverts commit 349331a.
I forgot to commit the updated en.js, just pushed one! 😼 ps: We're using Uptime Kuma @ https://status.mymusictaste.net/ |
Oh yes, the command is bad. |
Yeah, so I reverted all the artifacts that it created in this PR 😄 Since my team needs this feature and fixes a lot of pending issues is there something I could do to proceed with this PR? I'm sorry if I'm too attached to this feature but due to the fact our VPS network being flakey (like, losing a packet or few randomly) I really would like to use this feature in the stable version..! 😅 Thank you and ❤️ your work, |
Would love to see this feature merged. Is there anything that prevent it? I'm willing to help if I can :) |
@zenyr any docker image for this feature? or how to update docker image with this feature? I need this feature. thx. |
Hi. Any update on this PR and possibly when it will be merged? Thanks. |
Nevermind. I see now that it is part of the 1.20.0 milestone. Any due date for the release yet? Thanks. |
# Conflicts: # server/database.js # src/languages/en.js # src/languages/ko-KR.js
@lightingman117 you have written: "there is already a timeout notification" |
# Conflicts: # src/lang/ko-KR.json
src/pages/EditMonitor.vue
Outdated
// limit to 80% of interval | ||
const maxTimeout = this.monitor.interval * 0.8; | ||
// 0 will be treated as 80% of interval | ||
this.monitor.timeout = Math.Max(0, Math.min(timeout, maxTimeout)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a very amateur like mistake from my side. My bad!
Just resolved "Math.Max" typo for the PR. Sorry for the hassle! |
Sure! I will ping you again once I finish testing the code first, I had issues setting up dev env on a new device(for personal reasons) but definitely will do! |
Co-authored-by: Frank Elsinga <frank@elsinga.de>
# Conflicts: # server/database.js # server/server.js # src/pages/EditMonitor.vue
Tick the checkbox if you understand [x]:
Description
timeoutMs
to monitor and use ittimeout_ms
to sql patch listType of change
Checklist
(including JSDoc for methods)
Screenshots (if any)