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

Bump compat of DimensionalData #3707

Merged
merged 4 commits into from
Mar 11, 2024
Merged

Bump compat of DimensionalData #3707

merged 4 commits into from
Mar 11, 2024

Conversation

odow
Copy link
Member

@odow odow commented Mar 10, 2024

We can fix the printing. But rafaqz/DimensionalData.jl#664 is a blocker.

Copy link

codecov bot commented Mar 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.35%. Comparing base (d7c45a9) to head (7686c35).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3707   +/-   ##
=======================================
  Coverage   98.35%   98.35%           
=======================================
  Files          43       43           
  Lines        5709     5709           
=======================================
  Hits         5615     5615           
  Misses         94       94           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@odow odow changed the title Bump compat of DimensionalData DNMY: Bump compat of DimensionalData Mar 10, 2024
@rafaqz
Copy link

rafaqz commented Mar 10, 2024

I forgot to up the lower bound. Its fixed and the other version will be yanked.

@odow
Copy link
Member Author

odow commented Mar 10, 2024

I forgot to up the lower bound

I don't really understand why this would help? It's failing on nightly, not on an older version like 1.6

the other version will be yanked.

There is no need to yank patch versions

@odow
Copy link
Member Author

odow commented Mar 10, 2024

@rafaqz
Copy link

rafaqz commented Mar 10, 2024

Thats nightly failing, for multiple reasons

@odow
Copy link
Member Author

odow commented Mar 10, 2024

Thats nightly failing

Sure, but I don't want to bump the compat because then JuMP will fail tests.

It looks like you added the problematic rafaqz/DimensionalData.jl#585 only yesterday? We shouldn't touch Base internals.

@rafaqz
Copy link

rafaqz commented Mar 10, 2024

To clarify the yank is for 1.8 and 1.9... they will also break for unrelated reasons (like effects system macros). I just forgot about them.

I misunderstood your comment as nightly will fail anyway for other reasons even if I fix that particular bug.

@rafaqz
Copy link

rafaqz commented Mar 10, 2024

DD unavoidably hits a few internals where Base doesnt let us pass through dimension types.

But that new one was probably a mistake, its just very tricky to get dispatch working. Im working around it now.

(Also this version bump is huge, like 40 closed issues. So might be messy for a few days as dust settles.)

@odow
Copy link
Member Author

odow commented Mar 10, 2024

I misunderstood your comment as nightly will fail anyway for other reasons even if I fix that particular bug.

It's okay if your tests fail because of printing, etc. But ideally, they shouldn't cause the basic tests in JuMP to fail:

https://github.com/jump-dev/JuMP.jl/blob/d7c45a979e01c6d91cd489873bbd8982ad2518d1/ext/test_DimensionalData.jl

@rafaqz
Copy link

rafaqz commented Mar 10, 2024

For sure. I will fix that asap.

Hopefuly the other ones out if my control dont affect your tests.

Project.toml Outdated Show resolved Hide resolved
docs/Project.toml Outdated Show resolved Hide resolved
@odow odow changed the title DNMY: Bump compat of DimensionalData Bump compat of DimensionalData Mar 11, 2024
@odow odow merged commit 0f917fa into master Mar 11, 2024
11 checks passed
@odow odow deleted the odow-patch-1 branch March 11, 2024 02:37
@odow odow mentioned this pull request Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants