-
-
Notifications
You must be signed in to change notification settings - Fork 230
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
refactor: switch from Axios for Fetch API #840
Conversation
@@ -24,6 +24,7 @@ const UserWarnings: React.FC<UserWarningsProps> = ({ onClick }) => { | |||
let res = null; | |||
|
|||
//check if a user has warnings | |||
console.log(user); |
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.
Remove the console log
This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged. |
67529df
to
b6c7c6f
Compare
@Gauvino your fourth bug, is not a bug. You can't save because of our current email validation. That user needs a proper email in their email field then you can save |
We need help on this PR. Running into an issue where every now and then on not that slow but somewhat slow Internet like 30mbps etc. This might be related to the bugs that @Gauvino posted on their comment. Fetch request keeps timing out.
So we need input from someone who has any experience in solving this issue |
Hello, https://undici.nodejs.org/#/?id=network-address-family-autoselection |
Thanks for your response. For IPv6, we tried things like adding We'd be happy to try out other ideas. |
Thanks for your feedback. From the documentation if i'm not misleading the default configuration set To confirm the IPv6 issue I see some possibilities to try (I'm not a Node.js expert, so I might miss some steps.) :
Concerning the root cause, I suspect that Node.js detects your host supports IPv6, but it is misconfigured, which leads to this issue. |
@Gauvino we did some changes to try to fix this issue. Could you please try and see if it works now? |
Im gonna test this tonight, and will give feedback on everything ! |
Sorry for the news but nothing as change, all of the bugs are still there! Does I can provide some logs are something to investigate more? |
97c5e9c
to
eddbf2d
Compare
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.
LGTM!
🎉 This PR is included in version 2.0.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
This PR switch our codebase from the Axios library to the native Fetch API instead.
Screenshot (if UI-related)
To-Dos
yarn build
yarn i18n:extract
Issues Fixed or Closed