Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Properly handle OverflowError in DurationField deserialization#8042

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

@peterthomassen
Copy link
Collaborator

Related:https://github.com/django/django/pull/8870/files

Note: Before submitting this pull request, please review ourcontributing guidelines.

Description

Properly handle OverflowError in DurationField deserialization. Solution is the same as for the corresponding Django form field.

@stale
Copy link

stalebot commentedApr 25, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stalestalebot added the stale labelApr 25, 2022
@peterthomassen
Copy link
CollaboratorAuthor

I think this is still current.

@stalestalebot removed the stale labelApr 25, 2022
@stale
Copy link

stalebot commentedJul 14, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stalestalebot added the stale labelJul 14, 2022
@peterthomassen
Copy link
CollaboratorAuthor

I think this is still current.

@stalestalebot removed the stale labelJul 14, 2022
@stale
Copy link

stalebot commentedSep 22, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stalestalebot added the stale labelSep 22, 2022
@peterthomassen
Copy link
CollaboratorAuthor

I think this is still current.

Copy link
Collaborator

@auvipyauvipy left a comment

Choose a reason for hiding this comment

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

we have recently merged an identical feature for another field#8725. can you cross check and make amendment accordingly to this PR?

@stalestalebot removed the stale labelNov 22, 2022
@peterthomassen
Copy link
CollaboratorAuthor

The code looks very similar to me. Which according amendments do you mean? (Would you like to change the logic, or the error message? (Number of days out of range, must be between {min_days} and {max_days}.)

@auvipy
Copy link
Collaborator

btw, having another look, it seems your code is quite right. can you please pull from master so that the CI triggers with latest changes?

@peterthomassenpeterthomassenforce-pushed the20210618_DurationField_validation branch from5c97c3b to86d46c9CompareNovember 22, 2022 15:43
@peterthomassenpeterthomassenforce-pushed the20210618_DurationField_validation branch fromc458456 toc6eb872CompareNovember 22, 2022 15:44
@peterthomassen
Copy link
CollaboratorAuthor

done

@auvipyauvipy added the Bug labelNov 24, 2022
@auvipyauvipy merged commit52f4139 intoencode:masterNov 24, 2022
@auvipy
Copy link
Collaborator

thank you for your patience

@peterthomassenpeterthomassen deleted the 20210618_DurationField_validation branchNovember 24, 2022 11:33
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@auvipyauvipyauvipy approved these changes

Assignees

No one assigned

Labels

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@peterthomassen@auvipy

[8]ページ先頭

©2009-2025 Movatter.jp