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

[e2e] Add non-go Flintlock client tests #472

Open
richardcase opened this issue Jun 27, 2022 · 3 comments
Open

[e2e] Add non-go Flintlock client tests #472

richardcase opened this issue Jun 27, 2022 · 3 comments
Labels
area/api Indicates an issue or PR relates to the APIs area/testing Indicates an issue related to test help wanted Requires help from contributors to get done kind/feature New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@richardcase
Copy link
Member

richardcase commented Jun 27, 2022 •
edited
Loading

Describe the solution you'd like:
We need to ensure that Flintlock works with clients that are not Go based. So, we should add some e2e tests where the client of the API is either Node or Python (or perhaps both).

Why do you want this feature:
Ensure that we aren't baking in anything that is Go client specific.

Anything else you would like to add:

This is a follow on to #468
@richardcase richardcase added kind/feature New feature or request help wanted Requires help from contributors to get done area/api Indicates an issue or PR relates to the APIs area/testing Indicates an issue related to test priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 27, 2022
@github-actions
Copy link
Contributor

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 19, 2023
@github-actions GitHub Actions
Copy link
Contributor

This issue was closed because it has been stalled for 365 days with no activity.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 18, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Closed in Liquid Metal Roadmap - Public May 18, 2024
@richardcase richardcase reopened this Jul 10, 2024
@richardcase richardcase removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Jul 10, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue is stale because it has been open 180 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/api Indicates an issue or PR relates to the APIs area/testing Indicates an issue related to test help wanted Requires help from contributors to get done kind/feature New feature or request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
No open projects
Liquid Metal Roadmap - Public
Status: Closed
Milestone
No milestone
Development

No branches or pull requests
1 participant
@richardcase