Skip to content

Conversation

@AdrianSoundy
Copy link
Member

@AdrianSoundy AdrianSoundy commented Dec 12, 2024

Description

Update M5stack project to support latest nanoFramework.System.IO.FileSystem with SDCard updates.

Motivation and Context

Build broken

How Has This Been Tested?

Builds locally

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue with code or algorithm)
  • New feature (non-breaking change which adds functionality to code)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Config and build (change in the configuration and build system, has no impact on code or features)
  • Dependencies (update dependencies and changes associated, has no impact on code or features)
  • Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
  • Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

  • My code follows the code style of this project (only if there are changes in source code).
  • My changes require an update to the documentation (there are changes that require the docs website to be updated).
  • I have updated the documentation accordingly (the changes require an update on the docs in this repo).
  • I have read the CONTRIBUTING document.
  • I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
  • I have added new tests to cover my changes.

Summary by CodeRabbit

  • New Features

    • Updated the nanoFramework.System.IO.FileSystem dependency version to 1.1.66 across multiple projects.
  • Bug Fixes

    • Resolved issues related to the previous version of the System.IO.FileSystem dependency.

@nfbot nfbot added the Type: enhancement New feature or request label Dec 12, 2024
@coderabbitai
Copy link

coderabbitai bot commented Dec 12, 2024

Walkthrough

The pull request includes updates to the packages.lock.json files for several projects within the nanoFramework ecosystem. Specifically, the version of the nanoFramework.System.IO.FileSystem dependency has been upgraded from 1.1.54 to 1.1.66 across multiple projects: nanoFramework.Fire, nanoFramework.M5Core, nanoFramework.M5Core2, nanoFramework.Tough, and various test applications. The updates affect the requested, resolved, and contentHash fields for this dependency, while all other dependencies remain unchanged.

Changes

File Path Change Summary
nanoFramework.Fire/packages.lock.json Updated nanoFramework.System.IO.FileSystem version from 1.1.54 to 1.1.66.
nanoFramework.M5Core/packages.lock.json Updated nanoFramework.System.IO.FileSystem version from 1.1.54 to 1.1.66.
nanoFramework.M5Core2/packages.lock.json Updated nanoFramework.System.IO.FileSystem version from 1.1.54 to 1.1.66.
nanoFramework.Tough/packages.lock.json Updated nanoFramework.System.IO.FileSystem version from 1.1.54 to 1.1.66.
Tests/FireTestApp/packages.lock.json Updated nanoFramework.System.IO.FileSystem version from 1.1.54 to 1.1.66.
Tests/M5Core2TestApp/packages.lock.json Updated nanoFramework.System.IO.FileSystem version from 1.1.54 to 1.1.66.
Tests/M5CoreTestApp/packages.lock.json Updated nanoFramework.System.IO.FileSystem version from 1.1.54 to 1.1.66.
Tests/ToughTestApp/packages.lock.json Updated nanoFramework.System.IO.FileSystem version from 1.1.54 to 1.1.66.

Possibly related PRs

Suggested labels

CI: Publish Release, Type: dependencies


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f3db4ae and 46f05fd.

⛔ Files ignored due to path filters (11)
  • Tests/FireTestApp/FireTestApp.nfproj is excluded by none and included by none
  • Tests/FireTestApp/packages.config is excluded by none and included by none
  • Tests/M5Core2TestApp/M5Core2TestApp.nfproj is excluded by none and included by none
  • Tests/M5Core2TestApp/packages.config is excluded by none and included by none
  • Tests/M5CoreTestApp/M5CoreTestApp.nfproj is excluded by none and included by none
  • Tests/M5CoreTestApp/packages.config is excluded by none and included by none
  • Tests/ToughTestApp/ToughTestApp.nfproj is excluded by none and included by none
  • Tests/ToughTestApp/packages.config is excluded by none and included by none
  • nanoFramework.M5Core.nuspec is excluded by none and included by none
  • nanoFramework.M5Core2.nuspec is excluded by none and included by none
  • nanoFramework.Tough.nuspec is excluded by none and included by none
📒 Files selected for processing (4)
  • Tests/FireTestApp/packages.lock.json (1 hunks)
  • Tests/M5Core2TestApp/packages.lock.json (1 hunks)
  • Tests/M5CoreTestApp/packages.lock.json (1 hunks)
  • Tests/ToughTestApp/packages.lock.json (1 hunks)
🔇 Additional comments (4)
Tests/ToughTestApp/packages.lock.json (1)

85-87: LGTM! Version update is consistent.

The update of nanoFramework.System.IO.FileSystem to version 1.1.66 aligns with the PR objectives for SDCard functionality updates.

Let's verify version consistency across all package files:

✅ Verification successful

Version consistency verified across all package files

All package files consistently use nanoFramework.System.IO.FileSystem version 1.1.66 with matching content hashes, confirming proper synchronization across the codebase.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify consistent version of nanoFramework.System.IO.FileSystem across all package files
# Expected: All files should show version 1.1.66

fd -e json -x grep -l "nanoFramework.System.IO.FileSystem" {} | xargs grep -A 2 '"requested": "\[1.1.66, 1.1.66\]"'

Length of output: 2602

Tests/M5CoreTestApp/packages.lock.json (1)

121-123: LGTM! Version update matches across test apps.

The nanoFramework.System.IO.FileSystem version 1.1.66 update is consistent with other test applications.

Tests/FireTestApp/packages.lock.json (1)

139-141: LGTM! Version update is consistent with other test apps.

The nanoFramework.System.IO.FileSystem version 1.1.66 update matches across all test applications, maintaining consistency in the ecosystem.

Let's verify the changelog for this version update:

Tests/M5Core2TestApp/packages.lock.json (1)

145-147: LGTM! Version update aligns with PR objectives.

The update of nanoFramework.System.IO.FileSystem from 1.1.54 to 1.1.66 matches the intended changes for SDCard functionality.

Let's verify version consistency across all projects:

✅ Verification successful

Version consistency verified across all projects

All projects that depend on nanoFramework.System.IO.FileSystem are consistently using version 1.1.66. The version update has been properly applied across:

  • nanoFramework.M5Core
  • nanoFramework.Tough
  • nanoFramework.Fire
  • nanoFramework.M5Core2
  • Tests/ToughTestApp
  • Tests/M5CoreTestApp
  • Tests/M5Core2TestApp
  • Tests/FireTestApp
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify nanoFramework.System.IO.FileSystem version consistency
# Expected: All projects should use version 1.1.66

# Find all packages.lock.json files and check the version
fd packages.lock.json --exec grep -A 2 '"nanoFramework.System.IO.FileSystem": {'

Length of output: 986


Script:

#!/bin/bash
# Let's get more context by showing the full path of each packages.lock.json file
# along with the version information
fd packages.lock.json -x sh -c 'echo "=== {} ===" && grep -A 3 "nanoFramework.System.IO.FileSystem" "{}"'

Length of output: 2062


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>, 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. (Experiment)
  • @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.

@networkfusion
Copy link
Member

networkfusion commented Dec 12, 2024

~~@AdrianSoundy , you probably need to update the .nuspec file to match the updated:

Found in nuspec, but declared dependency version doesn't match!
expecting '1.1.66' but found '1.1.54'.

e.g. here:

<dependency id="nanoFramework.System.IO.FileSystem" version="1.1.54" />

(but other spec files also need a similar update)~~

it seems you have already done it since I checked. sill, there are other projects in the solution that must be referencing FS 1.1.54

@networkfusion
Copy link
Member

@AdrianSoundy
image

@AdrianSoundy
Copy link
Member Author

AdrianSoundy commented Dec 13, 2024

@networkfusion
Yes I saw that but the main problem now is the GitVersion also changed yesterday. Decided to update other PR first then can update this PR when branch updated

@networkfusion
Copy link
Member

@networkfusion Yes I saw that but the main problem now is the GitVersion also changed yesterday. Decided to update other PR first then can update this PR when branch updated

Oh, I hate when that happens.

@AdrianSoundy
Copy link
Member Author

No need to complete this PR as another PR has resolved problem

@AdrianSoundy AdrianSoundy deleted the Update branch December 13, 2024 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants