Skip to content
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.

Add test to catch regression for #137 #138

Open
jacobheun opened this issue Jul 29, 2019 · 0 comments
Open

Add test to catch regression for #137 #138

jacobheun opened this issue Jul 29, 2019 · 0 comments
Assignees
@jacobheun
Labels
kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked

Comments

@jacobheun
Copy link
Contributor

We should add a test to ensure that we don't end up with a regression of the fix in #137, especially as we migrate to full async/await.
@jacobheun jacobheun self-assigned this Jul 29, 2019
@jacobheun jacobheun mentioned this issue Jul 29, 2019
Merged
@vasco-santos vasco-santos added kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked labels Jul 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jacobheun jacobheun

Labels
kind/enhancement A net-new feature or improvement to an existing feature P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jacobheun @vasco-santos