Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Two warnings in date_time_parser.rb #1572

Closed
rubyFeedback opened this issue Mar 31, 2023 · 1 comment
Closed

Two warnings in date_time_parser.rb #1572

rubyFeedback opened this issue Mar 31, 2023 · 1 comment

Comments

@rubyFeedback
Copy link 

/root/.gem/gems/mail-2.8.1/lib/mail/parsers/date_time_parser.rb:837: warning: statement not reached
/root/.gem/gems/mail-2.8.1/lib/mail/parsers/date_time_parser.rb:691: warning: assigned but unused variable - testEof

Could the code be changed to suppress these warnings, if possible? Thank you for possibly considering this issue request.
@enescakir enescakir mentioned this issue Jun 8, 2023
Merged
enescakir added a commit to ubicloud/ubicloud that referenced this issue Jun 8, 2023
@enescakir
Ignore some warnings in mail gem while testing
81242ae 
These warnings make reading rspec results harder. mikel/mail gem has 3
years old issues at GitHub for them. But they aren't resolved.

mikel/mail#1384
mikel/mail#1424
mikel/mail#1572
enescakir added a commit to ubicloud/ubicloud that referenced this issue Jun 8, 2023
@enescakir
Ignore some warnings in mail gem while testing
a2f0b61 
These warnings make reading rspec results harder. mikel/mail gem has 3
years old issues at GitHub for them. But they aren't resolved.

mikel/mail#1384
mikel/mail#1424
mikel/mail#1572
eval added a commit that referenced this issue Jan 3, 2024
@eval
Solve warnings
b709cbb 
Fixes #1384, #1424, #1572
@eval eval mentioned this issue Jan 3, 2024
Closed
eval added a commit that referenced this issue Jan 3, 2024
@eval
Solve warnings
fefb854 
Fixes #1384, #1424, #1572
@rubyFeedback
Copy link
Author

Closing this as it appears to have been handled via the above changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rubyFeedback