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

Doesn't work in GitHub Codespaces #5

Open
ooovlad opened this issue Jun 3, 2024 · 2 comments
Open

Doesn't work in GitHub Codespaces #5

ooovlad opened this issue Jun 3, 2024 · 2 comments
Assignees

Comments

@ooovlad
Copy link

ooovlad commented Jun 3, 2024

This plugin tears down into pieces when being attempted to run in πŸ‘¨β€πŸ’» Codespaces:

  • Data Flow Tab is just blank;
  • Other tabs except history are blank too;
  • First analysis doesn't show all vulnerabilities;
  • After second analysis it doesn't show all vulnerabilities even if code has been modified just a bit;
  • Afted third analysis situation gets even worse even if code has been reverted to its original state;
  • After sixth analysis new attempts stop appearing in history tab;
  • Just doesn't work. Created Codespace twice, reload is also useless. Also tried to open python folder separately.

Could you clarify why doesn't it perform in Codespaces?
Is there a possible solution in the future?

Tested on this repo.

@ooovlad
Copy link
Author

ooovlad commented Jun 3, 2024

πŸ“œ Logs

Codespace configuration: 4-core β€’ 16GB RAM β€’ 32GB

πŸ“‚ Logdir:
/workspaces/fixathon-vulnerable-apps/python/.ai/Logs/Infrastructure/

πŸ‘ This one caught my eye, and it happens more than once:

ERROR  @PythonProcessor: Error "InsufficientMemory"(null) was received.

Also tried to run infr as advised here, but I don't know the arguments, --help doesn't help.

@alyadusov
Copy link
Collaborator

Hello!
Thank you for your report.

Unfortunately, we did not test this scenario - we did not even expect that the plugin in the code space would be alive in any form. However, now that I have researched it, I see that we can bring it to a working form. I added the task to the backlog.

At the moment, the main problem observed in codespace is incremental scanning. If you do a full scan every time it will work but slightly limited. "Command Pallet" -> "Start Full Scan"

image

As for the "InsufficientMemory" error, it does not break the work, but reduces the quality of the analysis. I suspect that there is something wrong with the RAM that the codespace allocates for the session.

For such a scenario, I recommend disabling the built-in resource consumption limit in the plugin settings.
image

@alyadusov alyadusov self-assigned this Jun 4, 2024
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

No branches or pull requests

2 participants