Skip to content

Conversation

@ebyhr
Copy link
Contributor

@ebyhr ebyhr commented Aug 1, 2024

Description

Remove redundant code

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Configuration:

  • Firmware version:
  • Hardware:
  • Toolchain:
  • SDK:

Checklist:

Please delete options that are not relevant.

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • If adding new functionality, I have discussed my implementation with the community using the linked GitHub issue
  • I have signed and submitted the ICLA and if needed, the CCLA. See Contributing for details.

@annafil annafil requested a review from a team August 1, 2024 18:15
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks like a Snowflake specific string that arguably doesn't need to live here any more, but first I'd like to verify nothing we have internally depends on it before removing it. Let me check on that.

Copy link
Contributor

Choose a reason for hiding this comment

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

Confirmed, we still use these internally. Let me try to quickly remove our internal dependency on these and then we can move forward here.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry for the delay. This is all cleaned up on our side now.

@ebyhr ebyhr force-pushed the ebi/remove-unused-code2 branch from e3c4c71 to f63a744 Compare August 5, 2024 01:58
@ebyhr
Copy link
Contributor Author

ebyhr commented Aug 5, 2024

(Rebased on main to resolve conflicts)

@ebyhr ebyhr force-pushed the ebi/remove-unused-code2 branch from f63a744 to 70f8ca4 Compare August 5, 2024 10:51
Copy link
Contributor

@takidau takidau left a comment

Choose a reason for hiding this comment

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

LGTM, thank you for your patience!

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry for the delay. This is all cleaned up on our side now.

@takidau
Copy link
Contributor

takidau commented Aug 6, 2024

Apparently someone else needs to review now since I resolved against other changes... :-/ @snazy if you get a chance maybe?

Copy link
Member

@snazy snazy left a comment

Choose a reason for hiding this comment

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

Sure

@snazy snazy merged commit 74cfe50 into apache:main Aug 6, 2024
@ebyhr ebyhr deleted the ebi/remove-unused-code2 branch August 6, 2024 07:52
fabio-rizzo-01 pushed a commit to fabio-rizzo-01/polaris that referenced this pull request Jun 20, 2025
# This is the 1st commit message:

 apache#772 fixed integration tests and synched with main

Mypy did a new release 1.16.1 and it cause our CI to fail for about 20 minutes due to missing wheel (upload not completed)
```
 | Unable to find installation candidates for mypy (1.16.1)
    |
    | This is likely not a Poetry issue.
    |
    |   - 14 candidate(s) were identified for the package
    |   - 14 wheel(s) were skipped as your project's environment does not support the identified abi tags
    |
    | Solutions:
    | Make sure the lockfile is up-to-date. You can try one of the following;
    |
    |     1. Regenerate lockfile: poetry lock --no-cache --regenerate
    |     2. Update package     : poetry update --no-cache mypy
    |
    | If neither works, please first check to verify that the mypy has published wheels available from your configured source that are compatible with your environment- ie. operating system, architecture (x86_64, arm64 etc.), python interpreter.
    |

```
This PR temporarily restrict the mypy version to avoid the similar issue.

We may consider bring poetry.lock back to git tracking so we won't automatically update test dependencies all the time

# This is the commit message apache#48:

Remove `.github/CODEOWNERS` (apache#1902)

As per this [dev-ML discussion](https://lists.apache.org/thread/jjr5w3hslk755yvxy8b3z45c7094cxdn)
# This is the commit message apache#49:

Rename quarkus as runtime (apache#1695)

# This is the commit message apache#50:

parent 3185adf
author Mend Renovate <[email protected]> 1749165686 +0200
committer Rizzo Cascio, Fabio <[email protected]> 1749646499 +0100

# This is a combination of 2 commits.
# This is the 1st commit message:

Mutable objects used for immutable values apache#772: resolved conflicts

# This is the commit message apache#51:

Mutable objects used for immutable values apache#772: fixed integration tests

# This is the commit message apache#52:

parent 3185adf
author Mend Renovate <[email protected]> 1749165686 +0200
committer Rizzo Cascio, Fabio <[email protected]> 1749646499 +0100

# This is a combination of 2 commits.
# This is the 1st commit message:

Mutable objects used for immutable values apache#772: resolved conflicts

Mutable objects used for immutable values apache#772: added final to base and core fields

Mutable objects used for immutable values apache#772: fixed tests
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