You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that when yarn install installs selectize from the specified github commit, it produces the checksum 8718... if it's on my MacBook or RedHat 8 server; but it produces the checksum ba26... if run on the Github Runner (Ubuntu I think?).
From the git blame, it looks like 10 months ago the checksum changed in yarn.lock without any of the other information changing; guessing that's either this same issue or a related one.
Example application or steps to reproduce the problem
yarn install
selectize
changes, despite nothing else about the package changing:git diff
Context
Describe the problem in detail
It seems that when
yarn install
installsselectize
from the specified github commit, it produces the checksum8718...
if it's on my MacBook or RedHat 8 server; but it produces the checksumba26...
if run on the Github Runner (Ubuntu I think?).This may be due to some known issues with yarn checksums, as discussed in yarnpkg/berry#2399 / yarnpkg/berry#2774 (comment) .
From the git blame, it looks like 10 months ago the checksum changed in
yarn.lock
without any of the other information changing; guessing that's either this same issue or a related one.https://github.com/rstudio/shiny/blame/2e2114f99d42ee2bc9cd00073cdaeafba5339c1c/yarn.lock#L1847-L1866
The text was updated successfully, but these errors were encountered: