Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix windows conda package upload and build ci #1792

Merged
merged 6 commits into from
Jun 4, 2024

Conversation

eberrigan
Copy link
Contributor

@eberrigan eberrigan commented Jun 3, 2024

Description

  • Using build_manual.yml to upload the Windows conda package.
  • Changed windows-2019 to windows-2022 in build.yml upload stages.
  • Removed unnecessary comment from build_ci.yml and tested the Build CI.

Types of changes

  • Bugfix
  • New feature
  • Refactor / Code style update (no logical changes)
  • Build / CI changes
  • Documentation Update
  • Other (explain)

Does this address any currently open issues?

  • The Windows OS in build.yml for the conda upload step was incorrect. This release v1.4.1a1 built but did not upload the Windows conda package.
  • The Build CI workflow did not work for Windows in this pull request Bump to 1.4.1a1 #1791 even though it worked in the previous pull requests (Build CI Actions) and only versions were changed in Bump to 1.4.1a1 #1791--nothing was changed in the build_ci.yml so I am not sure why it even ran. It is running without errors again.

Outside contributors checklist

  • Review the guidelines for contributing to this repository
  • Read and sign the CLA and add yourself to the authors list
  • Make sure you are making a pull request against the develop branch (not main). Also you should start your branch off develop
  • Add tests that prove your fix is effective or that your feature works
  • Add necessary documentation (if appropriate)

Thank you for contributing to SLEAP!

❤️

Summary by CodeRabbit

  • Documentation

    • Updated installation instructions to reflect the new version of SLEAP (1.4.1a1) for Windows, Linux, Mac OS X, and Apple Silicon.
  • Chores

    • Updated workflow configurations for Windows to use windows-2022.
    • Adjusted steps for uploading pip wheels and conda packages based on the operating system in the build workflows.
    • Removed an obsolete commented-out line in the CI build workflow.

Copy link

coderabbitai bot commented Jun 3, 2024

Walkthrough

The recent updates primarily focus on refining the CI/CD workflows and updating installation instructions. Changes to the GitHub Actions workflows involve adjusting operating system conditions and toggling steps for uploading packages. Additionally, the installation documentation has been updated to reflect the latest SLEAP version.

Changes

File Path Change Summary
.github/workflows/build.yml Updated OS conditions for logging into Anaconda and uploading conda packages on Windows.
.github/workflows/build_manual.yml Adjusted upload configurations for Ubuntu and Windows, including Anaconda login/logout steps.
.github/workflows/build_ci.yml Removed a commented-out line related to caching configuration.
docs/installation.md Updated installation commands for SLEAP from version 1.3.3 to 1.4.1a1.

Poem

In the realm of code so bright,
Workflows shift with new insight.
Windows, Ubuntu, all aligned,
Sleap's new version, finely designed.
Packages uploaded, tasks refined,
A seamless journey, redefined.
Hopping forward, swift and kind. 🐇✨


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

Copy link

@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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 61dbe62 and cf44276.

Files selected for processing (2)
  • .github/workflows/build.yml (2 hunks)
  • .github/workflows/build_manual.yml (5 hunks)
Additional comments not posted (6)
.github/workflows/build_manual.yml (4)

212-215: Logout step is crucial for security. Ensure it is correctly implemented.

This logout step is essential for maintaining security by ensuring that session tokens are not left active after the workflow completes.


63-70: The pip wheel upload step for Ubuntu is commented out.


191-196: Ensure the correct path and label are used for uploading the Windows conda package.


173-180: Ensure the Anaconda login command syntax is correct and secure.

.github/workflows/build.yml (2)

167-167: Ensure the condition for the Anaconda login step is correctly targeting the updated Windows version.

The update from windows-2019 to windows-2022 is correctly reflected here, aligning with the PR's objectives to fix issues related to the Windows build environment.


185-190: Check the conditions for uploading the conda package to ensure they correctly differentiate between main and dev releases.

Comment on lines 14 to 15
# - fakebranch
- elizabeth/Fix-windows-build-and-build-CI
Copy link

Choose a reason for hiding this comment

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

Branch name in the trigger paths seems to be specific to a user or feature branch.

Consider using more generic branch names or patterns (like feature/*) to avoid hardcoding specific user branches which might not be relevant in the future.

Copy link

@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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cf44276 and 80f7c27.

Files selected for processing (1)
  • .github/workflows/build_ci.yml (1 hunks)
Files skipped from review due to trivial changes (1)
  • .github/workflows/build_ci.yml

Copy link

@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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 80f7c27 and 8a0499b.

Files selected for processing (1)
  • .github/workflows/build_manual.yml (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • .github/workflows/build_manual.yml

@eberrigan eberrigan requested review from talmo and roomrys June 3, 2024 20:45
Copy link

@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

Outside diff range and nitpick comments (6)
docs/installation.md (6)

Line range hint 3-3: Correct the naming of Apple's operating system.

- Mac OS X, and Mac OS Apple Silicon
+ macOS, and macOS Apple Silicon

This change corrects the operating system name to "macOS," which is the official naming convention used by Apple.


Line range hint 43-43: Consider adding a comma for clarity.

- your terminal should give you two extra commands to run listed under **Next Steps**.
+ your terminal should give you two extra commands to run, listed under **Next Steps**.

Adding a comma after "run" improves the readability of the sentence.


Line range hint 183-183: Correct article usage before an acronym starting with a vowel sound.

- If you do not have a NVIDIA GPU
+ If you do not have an NVIDIA GPU

Using "an" before "NVIDIA" is grammatically correct as "NVIDIA" starts with a vowel sound.


Line range hint 238-238: Correct the naming of Apple's operating system.

- any OS except Apple silicon
+ any OS except Apple Silicon

This change corrects the capitalization of "Apple Silicon" to match the official naming convention.


Line range hint 410-410: Simplify language for clarity.

- what SLEAP is able to detect on your system
+ what SLEAP can detect on your system

Using "can" instead of "is able to" simplifies the sentence and improves readability.


Line range hint 416-416: Simplify language for clarity.

- If you were not able to get SLEAP installed
+ If you were unable to get SLEAP installed

Using "unable" instead of "were not able to" simplifies the sentence and improves readability.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8a0499b and 58393f2.

Files selected for processing (1)
  • docs/installation.md (1 hunks)
Additional context used
LanguageTool
docs/installation.md

[grammar] ~3-~3: The operating system from Apple is written “macOS”
Context: ...ackage on Windows, Linux, Mac OS X, and Mac OS Apple Silicon. SLEAP requires many com...


[uncategorized] ~43-~43: Possible missing comma found.
Context: ...l should give you two extra commands to run listed under Next Steps. ````{n...


[misspelling] ~183-~183: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ... -n sleap ``` If you do not have a NVIDIA GPU, then you should use the no ...


[grammar] ~238-~238: Did you mean the proper noun “Apple Silicon”?
Context: ... This works on **any OS except Apple silicon** and on **Google Colab**. {note...


[style] ~410-~410: As a shorter alternative for ‘able to’, consider using “can”.
Context: ...nning the diagnostics to see what SLEAP is able to detect on your system: ```bash sleap-d...


[style] ~416-~416: Consider using “unable” to avoid wordiness.
Context: ...`bash sleap-diagnostic ``` If you were not able to get SLEAP installed, activate the ma...

Markdownlint
docs/installation.md

31-31: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time


92-92: null
Bare URL used


295-295: Expected: fenced; Actual: indented
Code block style


314-314: Expected: fenced; Actual: indented
Code block style


333-333: Expected: fenced; Actual: indented
Code block style

Additional comments not posted (1)
docs/installation.md (1)

140-140: Update the installation commands to the latest version.

The update from sleap=1.3.3 to sleap=1.4.1a1 in the installation commands ensures users install the most recent version of SLEAP. This change aligns with the PR objectives to update the installation documentation.

Also applies to: 146-146

@talmo talmo merged commit 834c68a into develop Jun 4, 2024
@talmo talmo deleted the elizabeth/Fix-windows-build-and-build-CI branch June 4, 2024 03:08
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.

2 participants