Skip to content

fix: fix for ci#2770

Merged
e2corporation merged 1 commit into
apache:mainfrom
merico-ai:issues/2744
Aug 22, 2022
Merged

fix: fix for ci#2770
e2corporation merged 1 commit into
apache:mainfrom
merico-ai:issues/2744

Conversation

@likyh
Copy link
Copy Markdown
Contributor

@likyh likyh commented Aug 18, 2022

Summary

fix some connection ci and skip pipeline ci

@e2corporation e2corporation self-requested a review August 22, 2022 12:27
Copy link
Copy Markdown
Contributor

@e2corporation e2corporation left a comment

Choose a reason for hiding this comment

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

@likyh Nice work, one small fix needed (rateLimit key) and rebase then LGTM.

expect(response.body[0]).to.have.property('storyPointField')
expect(response.body[0]).to.have.property('remotelinkCommitShaPattern')
expect(response.body[0]).to.have.property('proxy')
expect(response.body[0]).to.have.property('rateLimitPerHour')
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The response key from the API is actually just rateLimit. All property assertions for rate limit should be updated to rateLimit.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

image
The response is rateLimitPerHour. Is it changed in any unmerged PR?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@likyh After rebuilding main it looks like it has been changed to rateLimitPerHour on response as well. No change necessary in that case.

@e2corporation e2corporation merged commit 5db5739 into apache:main Aug 22, 2022
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.

2 participants