-
Notifications
You must be signed in to change notification settings - Fork 30
refactor: log relative paths for file #1032
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
Conversation
|
Checked for |
|
Once the CI checks are enabled, I can verify if I have taken care of all logging statments. |
|
The typing annotations check does not fail for me locally. And this seems to be part of the code that I did not change so is there some issue with the CI? I have an older version of Python the build |
Yes. This PR fixes this typing error. Please rebase your branch on |
|
Thanks! Will rebase.
…________________________________
From: Behnaz Hassanshahi ***@***.***>
Sent: Monday, March 31, 2025 12:04:53 PM
To: oracle/macaron
Cc: Aman Sharma; Author
Subject: Re: [oracle/macaron] refactor: log relative paths for file (PR #1032)
The typing annotations check does not fail for me locally. And this seems to be part of the code that I did not change so is there some issue with the CI?
Yes. This PR<#1035> fixes this typing error. Please rebase your branch on staging once the PR is merged.
—
Reply to this email directly, view it on GitHub<#1032 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIMPTOMHZMDRCQOCNBJ3FY32XEHMLAVCNFSM6AAAAAB2BQMK7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRVG42TQMRUGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[behnazh-w]behnazh-w left a comment (oracle/macaron#1032)<#1032 (comment)>
The typing annotations check does not fail for me locally. And this seems to be part of the code that I did not change so is there some issue with the CI?
Yes. This PR<#1035> fixes this typing error. Please rebase your branch on staging once the PR is merged.
—
Reply to this email directly, view it on GitHub<#1032 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIMPTOMHZMDRCQOCNBJ3FY32XEHMLAVCNFSM6AAAAAB2BQMK7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRVG42TQMRUGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
d86b17b to
ef7968d
Compare
|
@behnazh-w I rebased and force-pushed. My unit tests were failing because of some coverage requirement so I was not able to push, but for now I disable the See error log: |
That's interesting. The unit tests seem to be passing on the CI, so there should be an issue with your local setup. |
|
Hi @algomaster99 It seems like there are more error messages for this issues. Could you please also include here any other error messages from pytest (if available) ? |
It was complaining about my outdated TOML file. I simply ran
Hopefully, I fixed it my new commit |
Thanks! Yes, we will squash the commits. |
|
Thanks for help @tromai @behnazh-w ! |
|
@algomaster99 Thanks for the changes and we are almost ready to merge the PR. The commits however miss the git commit --signoffPlease also rebase on |
1ce3676 to
78d80a6
Compare
Signed-off-by: Aman Sharma <[email protected]>
Signed-off-by: Aman Sharma <[email protected]>
Signed-off-by: Aman Sharma <[email protected]>
78d80a6 to
3654016
Compare
|
@behnazh-w signed-off my commits. I overlooked it because I already sign my commits but it seems there is a difference between "signing" and "signing off". I rebased too. |

Continuation of #1029