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
The atomic deploy logic doesn't properly handle the case where different artifact names are used in the same session, which will happen in a multi-module lein project (one that uses lein-modules, for example).
The failure manifests for the user as a 403 - Forbidden on the second module that is deployed.
The text was updated successfully, but these errors were encountered:
lein-module based projects will share an aether session when deploying,
but we want each module to have it's own session, so they will each have
their own atomic deploy. Without this change, the second and all
subsequent module deploys will fail.
The fix here is to store the tmp repos as a seq, and find the existing
one that matches the current upload, or creating a new one if none
match. This would allow interleaving files for different artifacts in
the same session, which none of the existing tooling does, but who knows
what craziness exists out there?
The atomic deploy logic doesn't properly handle the case where different artifact names are used in the same session, which will happen in a multi-module lein project (one that uses
lein-modules
, for example).The failure manifests for the user as a
403 - Forbidden
on the second module that is deployed.The text was updated successfully, but these errors were encountered: