search

trIAgelab / trIAge

An AI assistant for open-source communities
GNU General Public License v3.0
15 stars 1 forks source link

Was an Issue already answered in the README? #4

Open tsterbak opened 1 year ago

tsterbak commented 1 year ago

Check if an answer is already answered somewhere in the README (or other specified document in the repo). Give the answer here and point to the source file.

clstaudt commented 1 year ago

@tsterbak Should this be a True/False answer or would a "novelty" rating (0-10) also work? I think it would be possible to get a nuanced rating of the extent to which the issue is already covered by documentation.

clstaudt commented 1 year ago

@tsterbak

Bugs & problems with the flashing progress bar

trIAge.tell("Is the issue well described?")

The issue is partially well described, as it states the problem and provides clear information about the device (OnePlus One) and the error message encountered (adb: failed to read command: Success). However, it could benefit from the following improvements:

Detailed reproduction steps that led to the problem. Screenshots or a video recording showing the discrepancy between the TWRP progress bar and the OAI progress bar. Information on the specific OS and version being installed. By including these additional details, it would be easier for maintainers and contributors to understand and reproduce the problem, ultimately leading to a quicker resolution.

trIAge.rate_quality(an_issue)

6

trIAge.rate_novelty(an_issue)

8

trIAge.tell("Explain the novelty rating.")

I rated the novelty of this issue as an 8 because it seems to be a unique problem that is not directly addressed or discussed in the available documentation. The issue describes a discrepancy between the progress bars in TWRP and OAI, along with an error thrown in the advanced output. This specific issue appears to be new and not answered within the current documentation, hence the relatively high novelty rating.

clstaudt commented 1 year ago

@tsterbak Do you have an example of an issue that is not novel? Then the bot could retrieve the answer from the documentation.

tsterbak commented 1 year ago

@tsterbak Should this be a True/False answer or would a "novelty" rating (0-10) also work? I think it would be possible to get a nuanced rating of the extent to which the issue is already covered by documentation.

I guess, if the bot considers it already answered, it should give the answer and/or point to where to find it. So the novelity score could be used as a filter, but the action needs to be more than the score.

tsterbak commented 1 year ago

Closed issue #99 is a duplicate issue as well as basically answered in the readme. Issue #71 is also, at least partially answered in the readme but might need more details.

clstaudt commented 1 year ago

https://github.com/openandroidinstaller-dev/openandroidinstaller/issues/99

I rated the novelty of this issue as 6 because it is not directly answered or discussed in the documentation, but the problem seems to be related to running the application on a specific hardware (Macbook Pro "13 M1 2020) which suggests there could be a compatibility issue. Therefore, while it is not directly addressed in the documentation, it could be a known or expected issue when running the application on certain systems or configurations.

Is the issue already answered in the readme? If yes point to the answer.

No, the issue regarding the application not opening on a specific hardware (Macbook Pro "13 M1 2020) is not directly answered in the README. However, it's mentioned that Linux is currently the best-supported platform and there might be more issues on Windows and MacOS. The README does not discuss specific compatibility issues with M1 Apple Silicon.

What does the readme say about ARM based systems?

The README states, "So far there is no support for ARM-based systems." This implies that the OpenAndroidInstaller may not work properly or be supported on devices with ARM-based processors, such as Apple M1.

Hitting the reasoning limits of GPT-4 on this one...