Skip to content

Handle rented node in grace period #3742

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

Merged
merged 13 commits into from
Feb 24, 2025

Conversation

samaradel
Copy link
Contributor

@samaradel samaradel commented Dec 15, 2024

Description

Check if the rented node contract is in the grace period when listing the node.

Changes

image

Related Issues

Tested Scenarios

  • Navigate to the Node finder page.
  • Rent a dedicated node.
  • Leave it till it goes to the grace period.
  • Navigate to any solution.
  • Try to deploy an instance on the rented node.

Checklist

  • Tests included
  • Build pass
  • Documentation
  • Code format and docstrings
  • Screenshots/Video attached (needed for UI changes)

@samaradel
Copy link
Contributor Author

cpd from #3646

Copy link
Contributor

@0oM4R 0oM4R left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@samaradel
Copy link
Contributor Author

@0oM4R check it, it already fixed

Copy link
Contributor

@amiraabouhadid amiraabouhadid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no console err
image

@samaradel samaradel marked this pull request as ready for review February 2, 2025 21:23
Copy link
Contributor

@0oM4R 0oM4R left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on first if the node is selected;
we won't see any error but if you select another node then click on the graceperiod node will see the error

also the error must be handled

  • the node is not a valid node; so we shouldn't auto select it; need to handle this case as well

image

Comment on lines 239 to 242
setTimeout(() => {
reject(Error(err));
}, 2000);
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't think we need to add timeout here, not the auto one there is no toast overlap what do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

totally agree, removed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you removed timeout in the automatic on to, can you explain why I think ti is a better UX even if we set it to only one sec

@samaradel samaradel marked this pull request as draft February 16, 2025 14:47
@samaradel samaradel marked this pull request as ready for review February 17, 2025 10:43
@samaradel samaradel requested a review from 0oM4R February 17, 2025 11:02
Copy link
Contributor

@0oM4R 0oM4R left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

graceperiod

error still exsist if i select the grace period node

@samaradel
Copy link
Contributor Author

@0oM4R works with me, please make sure to have the latest update and build

@0oM4R
Copy link
Contributor

0oM4R commented Feb 18, 2025

recurcive.mov

@samaradel samaradel marked this pull request as draft February 18, 2025 12:55
@samaradel samaradel requested a review from 0oM4R February 18, 2025 19:30
@samaradel samaradel marked this pull request as ready for review February 18, 2025 19:30
Copy link
Contributor

@0oM4R 0oM4R left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we just need the changes in utils only; no need for the other changes

@samaradel samaradel marked this pull request as draft February 20, 2025 17:52
@samaradel samaradel requested a review from 0oM4R February 23, 2025 11:16
@samaradel samaradel marked this pull request as ready for review February 23, 2025 11:16
@samaradel samaradel marked this pull request as draft February 23, 2025 12:07
q
- Remove unwanted contract validation
- Early exit for check it node is rented and not in dedicated farm
- Remove the check only if dedicated filter is ON
@samaradel samaradel marked this pull request as ready for review February 23, 2025 13:35
Copy link
Contributor

@0oM4R 0oM4R left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dedicated nodes in shared farms are valid nodes
image

validation works fine on automatic finder

image

all works fine thanks.

image

@samaradel samaradel merged commit 8c936ef into development Feb 24, 2025
10 checks passed
@samaradel samaradel deleted the development_2.7_handle_rentedNode branch February 24, 2025 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants