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.

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

[1/n] Basic repo setup #2

Merged
merged 1 commit into from
Sep 13, 2023
Merged

[1/n] Basic repo setup #2

merged 1 commit into from
Sep 13, 2023

Conversation

saqadri
Copy link
Contributor

@saqadri saqadri commented Sep 5, 2023

[1/n] Basic repo setup

TSIA -- just getting things set up


Stack created with Sapling. Best reviewed with ReviewStack.

TSIA -- just getting things set up
@saqadri saqadri merged commit 4be027e into main Sep 13, 2023
rossdanlm pushed a commit that referenced this pull request Jan 12, 2024
… button should be disabled

I did a few things:

1. Create a new state id `runningPromptId` to check which prompt is running, making sure to set these correctly on run prompt actions
2. Read from this state in the AIConfigEditor and passed it as a prop down to the `RunPromptButton`

Question: Is there a better way of doing step #2 so that we don't need to keep piping it?

## Test Plan
Make sure that:
1. When you are running a prompt, you can still cancel it
2. When another prompt is running, you can't run any other prompt
3. When prompt is complete (or cancelled or errored), all the prompts can run again
rossdanlm pushed a commit that referenced this pull request Jan 12, 2024
… button should be disabled

I did a few things:

1. Create a new state id `runningPromptId` to check which prompt is running, making sure to set these correctly on run prompt actions
2. Read from this state in the AIConfigEditor and passed it as a prop down to the `RunPromptButton`

Question: Is there a better way of doing step #2 so that we don't need to keep piping it?

## Test Plan
Make sure that:
1. When you are running a prompt, you can still cancel it
2. When another prompt is running, you can't run any other prompt
3. When prompt is complete (or cancelled or errored), all the prompts can run again

https://github.com/lastmile-ai/aiconfig/assets/151060367/6e9a9cbf-6469-4ecb-ba74-1ede2ed1a292
rossdanlm pushed a commit that referenced this pull request Jan 12, 2024
… button should be disabled

I did a few things:

1. Create a new state id `runningPromptId` to check which prompt is running, making sure to set these correctly on run prompt actions
2. Read from this state in the AIConfigEditor and passed it as a prop down to the `RunPromptButton`

Question: Is there a better way of doing step #2 so that we don't need to keep piping it?

## Test Plan
Make sure that:
1. When you are running a prompt, you can still cancel it
2. When another prompt is running, you can't run any other prompt
3. When prompt is complete (or cancelled or errored), all the prompts can run again

https://github.com/lastmile-ai/aiconfig/assets/151060367/6e9a9cbf-6469-4ecb-ba74-1ede2ed1a292
rossdanlm pushed a commit that referenced this pull request Jan 13, 2024
… button should be disabled

I did a few things:

1. Create a new state id `runningPromptId` to check which prompt is running, making sure to set these correctly on run prompt actions
2. Read from this state in the AIConfigEditor and passed it as a prop down to the `RunPromptButton`

Question: Is there a better way of doing step #2 so that we don't need to keep piping it?

## Test Plan
Make sure that:
1. When you are running a prompt, you can still cancel it
2. When another prompt is running, you can't run any other prompt
3. When prompt is complete (or cancelled or errored), all the prompts can run again

https://github.com/lastmile-ai/aiconfig/assets/151060367/6e9a9cbf-6469-4ecb-ba74-1ede2ed1a292
rossdanlm pushed a commit that referenced this pull request Jan 13, 2024
… button should be disabled

I did a few things:

1. Create a new state id `runningPromptId` to check which prompt is running, making sure to set these correctly on run prompt actions
2. Read from this state in the AIConfigEditor and passed it as a prop down to the `RunPromptButton`

Question: Is there a better way of doing step #2 so that we don't need to keep piping it?

## Test Plan
Make sure that:
1. When you are running a prompt, you can still cancel it
2. When another prompt is running, you can't run any other prompt
3. When prompt is complete (or cancelled or errored), all the prompts can run again

https://github.com/lastmile-ai/aiconfig/assets/151060367/6e9a9cbf-6469-4ecb-ba74-1ede2ed1a292
rossdanlm added a commit that referenced this pull request Jan 13, 2024
…f button should be disabled (#907)

[2n] Disable Run Button: Create runningPromptId field to determine if
button should be disabled



I did a few things:

1. Create a new state id `runningPromptId` to check which prompt is
running, making sure to set these correctly on run prompt actions
2. Read from this state in the AIConfigEditor and passed it as a prop
down to the `RunPromptButton`

Question: Is there a better way of doing step #2 so that we don't need
to keep piping it?

## Test Plan
Make sure that:
1. When you are running a prompt, you can still cancel it
2. When another prompt is running, you can't run any other prompt
3. When prompt is complete (or cancelled or errored), all the prompts
can run again


https://github.com/lastmile-ai/aiconfig/assets/151060367/6e9a9cbf-6469-4ecb-ba74-1ede2ed1a292

---
Stack created with [Sapling](https://sapling-scm.com). Best reviewed
with
[ReviewStack](https://reviewstack.dev/lastmile-ai/aiconfig/pull/907).
* __->__ #907
* #905
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.

1 participant