-
Notifications
You must be signed in to change notification settings - Fork 1
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(sl): fix error code #1366
Merged
+13
−3
Merged
fix(sl): fix error code #1366
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,24 +2,24 @@ | |
|
||
import { config } from "@config/config" | ||
|
||
export enum JobStatus { | ||
Ready = "READY", // Ready to run jobs | ||
Running = "RUNNING", // A job is running | ||
Failed = "FAILED", // A job has failed and recovery is needed | ||
} | ||
|
||
export enum SiteStatus { | ||
Empty = "EMPTY", // A site record site is being initialized | ||
Initialized = "INITIALIZED", | ||
Launched = "LAUNCHED", | ||
} | ||
|
||
export enum RedirectionTypes { | ||
CNAME = "CNAME", | ||
A = "A", | ||
} | ||
|
||
export enum CollaboratorRoles { | ||
Admin = "ADMIN", | ||
Contributor = "CONTRIBUTOR", | ||
IsomerAdmin = "ISOMERADMIN", | ||
|
@@ -30,7 +30,7 @@ | |
CollaboratorRoles.IsomerAdmin | ||
> | ||
|
||
export enum ReviewRequestStatus { | ||
Approved = "APPROVED", | ||
Open = "OPEN", | ||
Merged = "MERGED", | ||
|
@@ -76,6 +76,8 @@ | |
"18.138.108.8", | ||
"18.139.47.66", | ||
] | ||
export const ALLOWED_DNS_ERROR_CODES = ["ENOTFOUND", "ENODATA"] | ||
|
||
export const DNS_INDIRECTION_DOMAIN = "hostedon.isomer.gov.sg" | ||
export const DNS_INDIRECTION_REPO = "isomer-indirection" | ||
export const ISOMER_ADMIN_EMAIL = "[email protected]" | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Hmm
ENOTFOUND
seems to be a catch all actually, should we be including this in the list of acceptable error codes?From the node dns docs:
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.
do you know of any other way to capture no host name ah?
i agree that this is not the best way since we have a blind spot here, but their api does not seem to have an check for just the existence of a host name.
note that do have an error code for say timeout (
ERR_SOCKET_CONNECTION_TIMEOUT
), so was hopeful that this would enough to catch transient network errorsThere 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.
Does this happen on every site launch? Or is this an infrequent error caused by the agency not putting up their records in time? If it's infrequent there might be value in having to manually check, rather than possibly giving the agency a false positive
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 check happens once every site launch. But the error 'ENOTFOUND' is specifically thrown for every new domain that is being launched. We have had multiple incidents happen due to human error during SL (think one happened just this week with the pr to indirection layer iirc), so I am very inclined not to have manual checks. This PR's test plan has a sense check by running dns.promises on your docker for both resolve6 AND CAA for sites that have and dont have the above values. My stance is errors slip through will be rare, and as such the false positive is low enough to not affect operations.