-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
🐛Source Amazon Seller Partner: Fix GET_VENDOR_TRAFFIC_REPORT when reportPeriod=DAY #37732
🐛Source Amazon Seller Partner: Fix GET_VENDOR_TRAFFIC_REPORT when reportPeriod=DAY #37732
Conversation
…FIC_REPORT stream
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
what's the action that I need to take now? Should I update connector version? |
Did you test it on your data, everything is fine? Please update connector version in |
Does PR branch need to stay up-to-date with master in order to merge? @darynaishchenko |
Running tests @tianchen98 |
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.
@tianchen98 it looks some unit tests are failing. Can you fix them?
I can't really see the failed tests. It's returning Forbidden 403 |
@tianchen98, You can run
|
Test can be passed if I remove |
Yes, I understood. You are allowed to change unit tests implementation if source code was changed. |
Thanks for your contribution @tianchen98 the code was introduced in #38210. I'm going to close this now. |
What
issue: #37729
How
Added
availablity_sla_days=3
andfixed_period_in_days=1
to ensure that all data in the lookback window can be fetched and thatdataEndTime
doesn't violate Amazon Vendor Central's SLA, which is 72 hours after the close of the period.Review guide
streams.py
User Impact
Syncing
GET_VENDOR_TRAFFIC_REPORT
will not result in errorsCan this PR be safely reverted and rolled back?