suggestions
1.After generating the edit results, the default is that the user accepts the modifications; clicking the right arrow ➡ means not accepting the modifications. This is somewhat counterintuitive.
2.There is no latency statistics reaching the user side.
3.It is recommended to improve frontend error reporting, as having just an "× Coedpilot" does not help the user understand why no results were generated.(Distinguish between timeout and model error.)
Bug
1.When the user click “generate edits”, and during the “querying generator" process they can still click "predicts locations" and "generate edits", it seems to be a bug.
2.If there are files in the project that CodePilot cannot recognize, such as ".bashrc", an ERROR will occur during the location prediction process and edits generation.
suggestions
1.After generating the edit results, the default is that the user accepts the modifications; clicking the right arrow ➡ means not accepting the modifications. This is somewhat counterintuitive.
2.There is no latency statistics reaching the user side.
3.It is recommended to improve frontend error reporting, as having just an "× Coedpilot" does not help the user understand why no results were generated.(Distinguish between timeout and model error.)
Bug
1.When the user click “generate edits”, and during the “querying generator" process they can still click "predicts locations" and "generate edits", it seems to be a bug.
2.If there are files in the project that CodePilot cannot recognize, such as ".bashrc", an ERROR will occur during the location prediction process and edits generation.