https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • s

    smortex

    07/22/2022, 2:09 AM
    bundle exec rake reference
    to build it
  • b

    bastelfreak

    07/22/2022, 6:05 AM
    meh
  • b

    bastelfreak

    07/22/2022, 6:05 AM
    you also could have regenerated it + release it 😄
  • s

    smortex

    07/22/2022, 6:06 AM
    No, it failed 😕
  • s

    smortex

    07/22/2022, 6:08 AM
    I guess you have to fix the warning before it updates REFERENCE.md…
  • b

    bastelfreak

    07/22/2022, 6:08 AM
    where did it fail?
  • s

    smortex

    07/22/2022, 6:08 AM
    I remember this being less a PITA a while ago, but can't really tell when it started
  • s

    smortex

    07/22/2022, 6:09 AM
    bundle exec rake reference
    display the same message as above and does not update REFERENCE.md
  • b

    bastelfreak

    07/22/2022, 6:11 AM
    the
    release
    rake task invokes
    strings:validate:reference
    . That checks if the reference.md is up2date. to generate or update it, we use
    strings:generate:reference
  • b

    bastelfreak

    07/22/2022, 6:13 AM
    mhm, the REFERENCE.md is up2date
  • b

    bastelfreak

    07/22/2022, 6:13 AM
    where did it actually fail 🤔
  • s

    smortex

    07/22/2022, 6:13 AM
    Yeah…
    release
    wants to check it
  • s

    smortex

    07/22/2022, 6:14 AM
    bundle exec rake strings:validate:reference
  • s

    smortex

    07/22/2022, 6:14 AM
    Ah, works on this computer …
  • s

    smortex

    07/22/2022, 6:15 AM
    Weird, I am on FreeBSD now, but was at $WORK on Debian earlier…
  • s

    smortex

    07/22/2022, 6:24 AM
    So assuming the bundle was up-to-date on both case, maybe the version of Ruby cause a different behavior? For the record here I have
    ruby 3.0.4p208 (2022-04-12 revision 3fa771dded) [amd64-freebsd13]
  • s

    smortex

    07/22/2022, 6:24 AM
    My other machine is supposely at
    ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux-gnu]
  • b

    bastelfreak

    07/22/2022, 6:28 AM
    I guess https://github.com/voxpupuli/modulesync_config/pull/788 helps
  • b

    bastelfreak

    07/22/2022, 6:28 AM
    I guess https://github.com/voxpupuli/modulesync_config/pull/788 helps
  • b

    bastelfreak

    07/22/2022, 6:29 AM
    based on the slack history I don't see where the task actually failed for you on debian
  • s

    smortex

    07/22/2022, 6:29 AM
    I just gave a try on a Debian machine and I don't see the error, migth be tied to my environment…
  • b

    bastelfreak

    07/22/2022, 6:30 AM
    which error was it?
  • s

    smortex

    07/22/2022, 6:30 AM
    bundle exec rake release
    exit with 1 and the output of
    strings:validate:reference
  • s

    smortex

    07/22/2022, 6:31 AM
    I run
    bundle exec rake strings:validate:reference
    and got the same output + same exit code 1
  • b

    bastelfreak

    07/22/2022, 6:31 AM
    mhm
  • s

    smortex

    07/22/2022, 6:32 AM
    I should have something not good in my env… I'll give a look next time I am at $WORK… on tuesday 🙃
  • s

    smortex

    07/22/2022, 6:34 AM
    Sorry for the mess 😕
  • b

    bastelfreak

    07/22/2022, 6:35 AM
    na it's fine
  • b

    bastelfreak

    07/22/2022, 6:35 AM
    what confuses me is that the REFERENCE.md is in the release 😄
  • s

    smortex

    07/22/2022, 6:39 AM
    Yeah, maybe we need more "abstract" tasks, e.g. "prepare_release" and "release". Also if rake could highlight some tasks to make them more visible that would be great to have our "big tasks" very visible and the other tasks that do individual things still visible but you search in these only when you need.
1...110111112...648Latest