Closed marcellodesales closed 1 year ago
This repo is specifically for the python API client, I suggest you reach out to Synopsys support directly. You can raise a ticket via community.synopsys.com
Hello @marcellodesales
Did you get the resolution for the above problem? Recently I am also facing the similar problem with my repository. Let me know if you are able to solve the issue.
@Aniketvaidhya :) Yes, I switched to Dependabot
@marcellodesales Ok, thanks!
Since, we use aws code commit, I think this is not the expected solution for me.
As I suggested before, you should really reach our to synopsys support for anything product related.
This repo is for the community built & supported python client, nothing else.
On Mon, 11 Dec 2023, 07:49 Aniketvaidhya, @.***> wrote:
@marcellodesales https://github.com/marcellodesales Ok, thanks!
Since, we use aws code commit, I think this is not the expected solution for me.
— Reply to this email directly, view it on GitHub https://github.com/blackducksoftware/hub-rest-api-python/issues/224#issuecomment-1849490969, or unsubscribe https://github.com/notifications/unsubscribe-auth/AETT4XJB3TBQQLHZMPGWM5TYI23IRAVCNFSM6AAAAAAREVGEKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBZGQ4TAOJWHE . You are receiving this because you modified the open/close state.Message ID: @.*** com>
Hello
I have found the root cause of the issue. The issue was due to the compatibility between the sigma versions and the detect version. I was using the latest sigma version which was not compatible. I am now using the sigma 2022.6.0 version, which has resolved the issue!
I'd like to submit a new scan and tag the project scan with different tags at every scan as part of our CI/CD pipeline... We need to inform current versions and env where the version is intended to be deployed, among other tags...
I'm using tags to try to differentiate scans from multiple branches as part of the limitation on the number of versions to be submitted... Developers need to know if they have actually fixed a bug or not according to the reports...
This call fails with the following:
❓ What's the actual format allowed?