Potential parallel running issues

[jieran233]

Generally speaking, the ChatGPT Web API only allows one conversation to be held at the same time, however this Workflow may be triggered at any time and allowed to run in parallel, which will cause problems.

My idea is to add a lock mechanism, similar to the Linux package manager.

Feel free to comment here if you have any ideas.

[jieran233]

My current idea is to assume that one GitHub account uses one ChatGPT account and create a repository or gist under the GitHub account for Workflow to read/write "lock" files.

Within the Workflow, it will continuously wait until the "lock" file is in unlocked state before request to ChatGPT. Once the request begins, the Workflow will update the file to locked status, and upon completion, it will mark it as unlocked.

[jieran233]

Of course, there is a simpler solution. Since an account sending multiple ChatGPT requests at the same time will return failure, it can be solved by simply increasing the number of retries.

[jieran233]

I just found that my worries seemed to be unnecessary. I tried opening multiple Issues at the same time in the test repository, and tried to log in to the same ChatGPT account in the browser to send requests at the same time. They all worked well.

So I will close this issue, if anyone still encounters similar problems, please feel free to reopen this issue and participate in the discussion, thank you