search

mumuki / mumuki-wollok-runner

MIT License
3 stars 2 forks source link

¿Loop de dependencias? #16

Closed faloi closed 5 years ago

faloi commented 5 years ago

Intenté instalarme el runner para hacer algunas pruebas contra el nuevo server de Wollok y el bundle install se queda Resolving dependencies.... por un largo rato. Investigué un poco y eso suele pasar cuando hay loop de dependencias.

Les paso una parte de la salida de DEBUG_RESOLVER=true bundle --verbose, que es lo que recomiendan acá para ver dónde puede estar el loop. El fragmento de Attempting to activate se repite todo el tiempo, con distintas versiones:

Creating possibility state for rake (>= 0.8.7) (1 remaining)

Attempting to activate [rake (0.9.0.beta.0), rake (0.9.0.beta.1), rake (0.9.0.beta.2), rake (0.9.0.beta.4), rake (0.9.0.beta.5), rake (0.9.3.beta.1), rake (0.9.3.beta.2), rake (0.9.3.beta.3), rake (0.9.3.beta.4), rake (10.0.0.beta.1), rake (10.0.0.beta.2), rake (10.1.0.beta.1), rake (10.1.0.beta.2), rake (10.1.0.beta.3), rake (12.0.0.beta1), rake (0.8.7), rake (0.9.0), rake (0.9.1), rake (0.9.2), rake (0.9.2.2), rake (0.9.3), rake (0.9.4), rake (0.9.5), rake (0.9.6), rake (10.0.0), rake (10.0.1), rake (10.0.2), rake (10.0.3), rake (10.0.4), rake (10.1.0), rake (10.1.1), rake (10.2.0), rake (10.2.1), rake (10.2.2), rake (10.3.0), rake (10.3.1), rake (10.3.2), rake (10.4.0), rake (10.4.1), rake (10.4.2), rake (10.5.0), rake (11.0.1), rake (11.1.0), rake (11.1.1), rake (11.1.2), rake (11.2.0), rake (11.2.2), rake (11.3.0), rake (12.0.0), rake (12.1.0), rake (12.2.0), rake (12.2.1), rake (12.3.0), rake (12.3.1), rake (12.3.2)]

Found existing spec ([rake (10.0.0), rake (10.0.1), rake (10.0.2), rake (10.0.3), rake (10.0.4), rake (10.1.0), rake (10.1.1), rake (10.2.0), rake (10.2.1), rake (10.2.2), rake (10.3.0), rake (10.3.1), rake (10.3.2), rake (10.4.0), rake (10.4.1), rake (10.4.2), rake (10.5.0)])
Creating possibility state for activesupport (= 3.1.12) (1 remaining)
Attempting to activate [activesupport (3.1.12)]
Found existing spec ([activesupport (5.2.1.1), activesupport (5.2.2)])
Unsatisfied by existing spec ([activesupport (5.2.1.1), activesupport (5.2.2)])
Unwinding for conflict: activesupport (= 3.1.12) to 60
Creating possibility state for railties (>= 3.1.0) (125 remaining)
Attempting to activate [railties (3.1.11)]
Activated railties at [railties (3.1.11)]
Requiring nested dependencies (rake (>= 0.8.7), thor (~> 0.14.6), rack-ssl (~> 1.3.2), rdoc (~> 3.4), activesupport (= 3.1.11), actionpack (= 3.1.11))

// Acá lo frené con Ctrl + C.

Finished resolution (1442 steps) (Took 38.734026048 seconds) (2019-02-27 21:21:20 -0300)
Unactivated: thor, rack-ssl, rdoc, actionpack
Activated: mumuki-wollok-runner, bundler, rake, rspec, codeclimate-test-reporter, mumukit-bridge, ruby, rubygems, mumukit, rest-client, rspec-core, rspec-expectations, rspec-mocks, mumukit-core, simplecov, rspec-support, diff-lcs, netrc, mime-types, http-cookie, activesupport, rack, i18n, concurrent-ruby, minitest, tzinfo, thread_safe, domain_name, docile, simplecov-html, json, mumukit-content-type, mumukit-directives, mumukit-inspection, mulang, excon, docker-api, puma, sinatra, rack-protection, tilt, mime-types-data, unf, unf_ext, md_emoji, redcarpet, rouge, railties