API to look up source and package directory in Python

[edwardalee]

This PR adds a test for lf-lang/reactor-c#455

Summary by CodeRabbit

• New Features
  • Introduced functionality to test lf.source_directory() and lf.package_directory() functions in Python.

[coderabbitai]

Warning

Rate limit exceeded

@edwardalee has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 41 minutes and 46 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between b8e75f1 and 8c876c9.

Walkthrough

The recent updates primarily focus on two aspects: revising the subproject commit in the reactor-c library without altering exported or public entities, and introducing a new Python file PythonPaths.lf that tests specific functions within the Python test suite, namely lf.source_directory() and lf.package_directory(). These modifications ensure stability and added functionality in testing paths in the Python runtime environment.

Changes

File Path	Change Summary
core/src/main/resources/lib/c/reactor-c	Updated the subproject commit in the reactor-c library. No changes to exported or public entities.
test/Python/src/PythonPaths.lf	Introduced a new file to test lf.source_directory() and lf.package_directory() functions in Python. It compiles and runs without errors, printing the contents of the file twice.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 73e8c8a and b8e75f1.

Files selected for processing (2)

• core/src/main/resources/lib/c/reactor-c (1 hunks)
• test/Python/src/PythonPaths.lf (1 hunks)

Files skipped from review due to trivial changes (1)

• core/src/main/resources/lib/c/reactor-c

Additional comments not posted (3)

test/Python/src/PythonPaths.lf (3)

1-5: Documentation is clear and concise.

The comment block clearly explains the purpose and expected outcome of the test. This is crucial for maintainability and understanding the intent of the test.

---

8-8: Review of import statement.

The import statement for os is appropriate as it is used to construct paths in the states. This ensures that the code is modular and makes use of Python's standard library efficiently.

---

11-12: Correct use of lf.source_directory() and lf.package_directory().

The states source_path and package_path are correctly initialized using the lf functions. This demonstrates a good understanding of the functions' intended use and ensures that the paths are dynamically set based on the environment.

[lhstrh]

Let me clean up the revision history before merging this.