…p/semgrep-proprietary#2314)

Enables support for `requirements.pip` + minor edits/refactors to
lockfile related code.

synced from Pro 8380841df3138954b182d3345449ebf407a00a6a

…proprietary#2331)

Support truncated requirements lockfiles. Ex: `requirement.txt`,
`requirement-prod.txt`.

synced from Pro e1fa7e9cfb7512772077ad2ae91b9d0b116766eb

…oprietary#2335)

test plan:
```
$ osemgrep validate semgrep-rules/
[00.91][WARNING]: invalid YAML, ./stats/metacategory_to_support_tier.yml:1:0: missing rules entry as top-level key
[00.91][WARNING]: invalid YAML, ./stats/web_frameworks.yml:1:0: missing rules entry as top-level key
[00.91][WARNING]: invalid YAML, ./stats/cwe_to_metacategory.yml:1:0: missing rules entry as top-level key
[00.91][WARNING]: invalid YAML, ./.pre-commit-config.yaml:1:0: missing rules entry as top-level key
[00.91][WARNING]: invalid YAML, ./.github/workflows/num-rules.yml:3:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/update-semgrep-dev.yml:3:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/trigger-semgrep-scanner-initiate-scan.yaml:3:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/pre-commit.yml:3:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/update-semgrep-staging-dev.yml:3:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/validate-r2c-registry-metadata.yaml:8:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/semgrep-rules-test-historical.yml:2:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/trigger-pro-benchmark-scan.yaml:3:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/semgrep-rule-lints.yaml:3:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/semgrep-rules-test.yml:3:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/workflows/semgrep-rules-test-develop.yml:5:0: Not a valid key value pair
[00.91][WARNING]: invalid YAML, ./.github/stale.yml:1:0: missing rules entry as top-level key

┌─────────────┐
│ Scan Status │
└─────────────┘
  Scanning 1930 files tracked by git with 6 Code rules:

  Language   Rules   Files          Origin      Rules
 ──────────────────────────        ───────────────────
  yaml           6    1930          Community       6

Configuration is invalid - found 16 fatal errors, 0 skippable error(s), and 2003 rule(s).
(cli) [pad@thinkstation semgrep-rules ((4946ce98...))]$ echo $?
0
```

synced from Pro 0dc2e3c60ecf40d6b2d0dea1a8b691c5c25954fb

…/semgrep-proprietary#2333)

Please confirm correctness of the changes here and ensure all tests
pass. This PR was autogenerated by
.github/workflows/update-semgrep-rules.yml

Co-authored-by: GitHub Actions Bot <>

synced from Pro abed82c35f71703faf5744f0439ddff7ffffa09b

synced from Pro 0919e0a775ff1a17425493f9f40c254e226abe53

…mgrep-proprietary#2315)

Adjust logging level of timeout so that it appears with a debug label:
<img width="1117" alt="Screenshot 2024-09-23 at 4 00 32 PM"
src="https://github.com/user-attachments/assets/f2840e9b-be50-450a-b799-bb86b53323a7">

Test plan:
- Run `semgrep scan --timeout=1 --debug` on semgrep-app
- Run `semgrep scan --timeout=1` on semgrep-app
- Run `semgrep scan --timeout=1 --experimental` on semgrep-app

synced from Pro 5134d9cc489dc167d2fd57fb57171bc6a57e7463