Skip to content

Conversation

@david-zlai
Copy link
Contributor

@david-zlai david-zlai commented Jan 27, 2025

Summary

The string formatting here was breaking zipline commands when I built a new wheel:

  File "/Users/davidhan/zipline/chronon/dev_chronon/lib/python3.11/site-packages/ai/chronon/repo/hub_uploader.py", line 73
    print(f"\n\nUploading:\n {"\n".join(diffed_entities.keys())}")
                                ^
SyntaxError: unexpected character after line continuation character

Checklist

  • Added Unit Tests
  • Covered by existing CI
  • Integration tested
  • Documentation update

Summary by CodeRabbit

  • Style
    • Improved string formatting and error message construction for better code readability
    • Enhanced log message clarity in upload process

Note: These changes are internal improvements that do not impact end-user functionality.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 27, 2025

Walkthrough

The pull request focuses on refining string handling in the hub_uploader.py file, specifically within two functions: _build_local_repo_hashmap and compute_and_upload_diffs. The changes involve improving string formatting and error message construction, emphasizing readability and consistency without altering the core functionality of the code.

Changes

File Change Summary
api/py/ai/chronon/repo/hub_uploader.py - Improved error message formatting in _build_local_repo_hashmap
- Enhanced print statement readability in compute_and_upload_diffs

Possibly related PRs

Suggested reviewers

  • chewy-zlai

Poem

🧵 Strings woven with care and grace,
Code refactored at a gentle pace
Formatting dance, a subtle art
Readability's delightful start!
Clarity blooms where chaos grew 🌱

Warning

Review ran into problems

🔥 Problems

GitHub Actions: Resource not accessible by integration - https://docs.github.com/rest/actions/workflow-runs#list-workflow-runs-for-a-repository.

Please grant the required permissions to the CodeRabbit GitHub App under the organization or repository settings.

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@david-zlai david-zlai marked this pull request as ready for review January 27, 2025 19:23
diffed_entities = _get_diffed_entities(root_dir, branch)
print(f"\n\nUploading:\n {"\n".join(diffed_entities.keys())}")
entity_keys_str = "\n".join(diffed_entities.keys())
log_str = "\n\nUploading:\n{entity_keys}".format(entity_keys=entity_keys_str)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit maybe just use f-strings?

log_str = f"\n\nUploading:\n{entity_keys_str}"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can change. I'm a an of f strings but I think the trust in them got us to this error

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

merging. but i can change it in a follow up

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
api/py/ai/chronon/repo/hub_uploader.py (2)

61-64: Use f-string for better readability

-                "The following files had exceptions during upload: \n"
-                + "\n".join(exceptions)
-                + "\n\n Consider deleting the files (safe operation) and checking "
-                + "your thrift version before rerunning your command."
+                f"The following files had exceptions during upload: \n"
+                f"{'\n'.join(exceptions)}\n\n"
+                f"Consider deleting the files (safe operation) and checking "
+                f"your thrift version before rerunning your command."

73-75: Consider f-string for modern Python

Fix looks good. For better readability:

 entity_keys_str = "\n".join(diffed_entities.keys())
-log_str = "\n\nUploading:\n{entity_keys}".format(entity_keys=entity_keys_str)
+log_str = f"\n\nUploading:\n{entity_keys_str}"
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 85bcf65 and de763fb.

📒 Files selected for processing (1)
  • api/py/ai/chronon/repo/hub_uploader.py (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: no_spark_scala_tests

@david-zlai david-zlai merged commit 7697215 into main Jan 27, 2025
5 checks passed
@david-zlai david-zlai deleted the davidhan/fix_wheel branch January 27, 2025 20:51
nikhil-zlai pushed a commit that referenced this pull request Feb 4, 2025
## Summary
The string formatting here was breaking zipline commands when I built a
new wheel:

```
  File "/Users/davidhan/zipline/chronon/dev_chronon/lib/python3.11/site-packages/ai/chronon/repo/hub_uploader.py", line 73
    print(f"\n\nUploading:\n {"\n".join(diffed_entities.keys())}")
                                ^
SyntaxError: unexpected character after line continuation character
```

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Style**
- Improved string formatting and error message construction for better
code readability
    - Enhanced log message clarity in upload process

Note: These changes are internal improvements that do not impact
end-user functionality.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
kumar-zlai pushed a commit that referenced this pull request Apr 25, 2025
## Summary
The string formatting here was breaking zipline commands when I built a
new wheel:

```
  File "/Users/davidhan/zipline/chronon/dev_chronon/lib/python3.11/site-packages/ai/chronon/repo/hub_uploader.py", line 73
    print(f"\n\nUploading:\n {"\n".join(diffed_entities.keys())}")
                                ^
SyntaxError: unexpected character after line continuation character
```

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Style**
- Improved string formatting and error message construction for better
code readability
    - Enhanced log message clarity in upload process

Note: These changes are internal improvements that do not impact
end-user functionality.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
kumar-zlai pushed a commit that referenced this pull request Apr 29, 2025
## Summary
The string formatting here was breaking zipline commands when I built a
new wheel:

```
  File "/Users/davidhan/zipline/chronon/dev_chronon/lib/python3.11/site-packages/ai/chronon/repo/hub_uploader.py", line 73
    print(f"\n\nUploading:\n {"\n".join(diffed_entities.keys())}")
                                ^
SyntaxError: unexpected character after line continuation character
```

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Style**
- Improved string formatting and error message construction for better
code readability
    - Enhanced log message clarity in upload process

Note: These changes are internal improvements that do not impact
end-user functionality.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary
The string formatting here was breaking zipline commands when I built a
new wheel:

```
  File "/Users/davidhan/zipline/chronon/dev_chronon/lib/python3.11/site-packages/ai/chronon/repo/hub_uploader.py", line 73
    print(f"\n\nUploading:\n {"\n".join(diffed_entities.keys())}")
                                ^
SyntaxError: unexpected character after line continuation character
```

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Style**
- Improved string formatting and error message construction for better
code readability
    - Enhanced log message clarity in upload process

Note: These changes are internal improvements that do not impact
end-user functionality.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai pushed a commit that referenced this pull request May 15, 2025
## Summary
The string formatting here was breaking zipline commands when I built a
new wheel:

```
  File "/Users/davidhan/zipline/chronon/dev_chronon/lib/python3.11/site-packages/ai/chronon/repo/hub_uploader.py", line 73
    print(f"\n\nUploading:\n {"\n".join(diffed_entities.keys())}")
                                ^
SyntaxError: unexpected character after line continuation character
```

## Checklist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Style**
- Improved string formatting and error message construction for better
code readability
    - Enhanced log message clarity in upload process

Note: These changes are internal improvements that do not impact
end-user functionality.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
chewy-zlai pushed a commit that referenced this pull request May 16, 2025
## Summary
The string formatting here was breaking zipline commands when I built a
new wheel:

```
  File "/Users/davidhan/zipline/chronon/dev_chronon/lib/python3.11/site-paour clientsages/ai/chronon/repo/hub_uploader.py", line 73
    print(f"\n\nUploading:\n {"\n".join(diffed_entities.keys())}")
                                ^
SyntaxError: unexpected character after line continuation character
```

## Cheour clientslist
- [ ] Added Unit Tests
- [ ] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Style**
- Improved string formatting and error message construction for better
code readability
    - Enhanced log message clarity in upload process

Note: These changes are internal improvements that do not impact
end-user functionality.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
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

Successfully merging this pull request may close these issues.

3 participants