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

Naming Conflicts in Clojure 1.11 #16

Closed
skylee03 opened this issue Oct 19, 2023 · 5 comments · Fixed by #33
Closed

Naming Conflicts in Clojure 1.11 #16

skylee03 opened this issue Oct 19, 2023 · 5 comments · Fixed by #33
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@skylee03
Copy link
Collaborator

skylee03 commented Oct 19, 2023

Starting from Clojure 1.11, running the test program will generate the following warnings:

WARNING: update-vals already refers to: #'clojure.core/update-vals in namespace: clojure.tools.analyzer.utils, being replaced by: #'clojure.tools.analyzer.utils/update-vals
WARNING: update-keys already refers to: #'clojure.core/update-keys in namespace: clojure.tools.analyzer.utils, being replaced by: #'clojure.tools.analyzer.utils/update-keys
WARNING: update-vals already refers to: #'clojure.core/update-vals in namespace: clojure.tools.analyzer, being replaced by: #'clojure.tools.analyzer.utils/update-vals
WARNING: update-keys already refers to: #'clojure.core/update-keys in namespace: clojure.tools.analyzer, being replaced by: #'clojure.tools.analyzer.utils/update-keys
WARNING: update-vals already refers to: #'clojure.core/update-vals in namespace: clojure.tools.analyzer.passes, being replaced by: #'clojure.tools.analyzer.utils/update-vals
WARNING: update-vals already refers to: #'clojure.core/update-vals in namespace: clojure.tools.analyzer.passes.uniquify, being replaced by: #'clojure.tools.analyzer.utils/update-vals
WARNING: random-uuid already refers to: #'clojure.core/random-uuid in namespace: onyx.static.uuid, being replaced by: #'onyx.static.uuid/random-uuid
WARNING: random-uuid already refers to: #'clojure.core/random-uuid in namespace: onyx.peer.task-compile, being replaced by: #'onyx.static.uuid/random-uuid
WARNING: random-uuid already refers to: #'clojure.core/random-uuid in namespace: onyx.peer.read-batch, being replaced by: #'onyx.static.uuid/random-uuid
WARNING: random-uuid already refers to: #'clojure.core/random-uuid in namespace: onyx.peer.peer-group-manager, being replaced by: #'onyx.static.uuid/random-uuid
WARNING: random-uuid already refers to: #'clojure.core/random-uuid in namespace: onyx.peer.communicator, being replaced by: #'onyx.static.uuid/random-uuid
WARNING: random-uuid already refers to: #'clojure.core/random-uuid in namespace: onyx.api, being replaced by: #'onyx.static.uuid/random-uuid

This is because Clojure 1.11 introduced the update-keys and update-vals functions.

Update: Solved by upgrading Clojask.

@skylee03 skylee03 added this to the v1.0.0 milestone Oct 19, 2023
@skylee03 skylee03 self-assigned this Oct 19, 2023
@skylee03 skylee03 added the enhancement New feature or request label Oct 19, 2023
@skylee03
Copy link
Collaborator Author

WARNING: abs already refers to: #'clojure.core/abs in namespace: zero-one.geni.core.functions, being replaced by: #'zero-one.geni.core.functions/abs

Fixed in Geni but it is not released.

zero-one-group/geni#342

@skylee03
Copy link
Collaborator Author

Now can be fixed by upgrading Geni to v0.0.41 (to be released soon).

@skylee03
Copy link
Collaborator Author

The problem is not completely solved in v0.0.41. src/clojure/zero_one/geni/core/functions.clj should also be updated.

@skylee03
Copy link
Collaborator Author

Current solution:

  • Downgrade Clojure to v1.10.3
  • Users can still specify newer versions in their projects

@skylee03 skylee03 removed this from the v1.0.0 milestone Oct 30, 2023
@skylee03
Copy link
Collaborator Author

The problem is not completely solved in v0.0.41. src/clojure/zero_one/geni/core/functions.clj should also be updated.

It will be solved soon!

@skylee03 skylee03 added this to the v1.0.2 milestone Nov 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant