Release 1.161.0 - #3799
Conversation
…rt (#3782) Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
…umentation (#3783) Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Signed-off-by: Alex H <ahiguera@mit.edu>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
…g UUID (#3789) Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
OpenAPI ChangesShow/hide changesUnexpected changes? Ensure your branch is up-to-date with |
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9430286 | Triggered | Generic Password | 63ded11 | .github/workflows/ci.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
| member, | ||
| ], | ||
| ) | ||
| wait_ms = float(result) |
There was a problem hiding this comment.
Bug: The Redis Lua script returns a byte string, but the code attempts to call float() directly on it, which will raise a TypeError in Python 3.
Severity: CRITICAL
Suggested Fix
Decode the byte string returned from the Redis script before passing it to float(). For example, change float(result) to float(result.decode("utf-8")). Alternatively, configure the Redis connection with decode_responses=True to automatically handle decoding.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: hubspot_sync/rate_limiter.py#L93
Potential issue: The Redis client is not configured with `decode_responses=True`, so the
Lua script's return value `tostring(wait_ms)` is received as a bytes object (e.g.,
`b"0.0"`). The code at `hubspot_sync/rate_limiter.py:93` calls `float(result)` on this
byte string. In Python 3, this is invalid and raises a `TypeError`. Since
`wait_for_rate_limit()` is called for every HubSpot sync task, this will cause all sync
tasks to fail unconditionally at runtime.
Did we get this right? 👍 / 👎 to inform future reviews.
Nathan Levesque
Tobias Macey
cp-at-mit
Alex H
Muhammad Anas
Asad Ali