https://www.puppet.com/community logo
Join Slack
Powered by
This message was deleted.
# puppet
s
This message was deleted.
d
@edwin @binford2k?
b
@kn are you using a text mode email client?
and please let us know if that solves your problem
k
i read plain text mails in neomutt.
yes, manually fixing url encoding got me unstuck
please see my replies in the #C0W298S9G channel where mentioned all this
👍 1
b
well.... glad that got you unstuck. Not glad that it's still a problem. I'll make sure the ticket is reopened.
k
thanks, no idea how to open a ticket and where, did someone else do this and it got closed?
b
yeah, it was opened on an internal project. I'll take care of filing it. (we're reworking how our ticketing systems work at the moment, so it's probably best for me to just handle it this time.)
k
afaict, there are multiple issues: 1. text/plain message contains encoded urls instead of plain ones (plain 
&
would've been copied along and worked as-is) 2. the botched link did not error, but instead asks to resend the confirmation mail in case you did not get it, which is super confusing since the only way to get there was through the link in the confirmation mail, i.e. if the broken link would've just shown an error like 'sorry, your request is bogus', i would've immediately double checked that
3. there's no 'need help'/'there is a problem'/'give feedback' button or link anywhere in the process, neither in the signup or login form, nor in the confirmation mail sent so i click through forge.puppet.com searching for contact/support, but that just lands me on press contact/commercial support/puppet forum/etc. sites
i never used slack before, registered here and texted the first channel/whatever that I see, hoping to reach someone wrt. this issue
overall, i've wasted hours of my time on something that should've been a 3 minute signup/login process to continue actual work of hacking on forge modules
thanks a bunch for reopening the ticket and taking care of it
👍 1
it'd be super happy to know that the next person signing up via plain text mail will have a better time
b
I hear you about the frustration. We are working to make that better. (and to fix the mail bug)
quick question for you -- do you have a GitHub account already?
k
not really frustrated, stuff like this is broken all the time, just providing details, hoping for someone to take them into consideration whilst improving
yes, i am on github
👍 1
b
thanks. Lemme know how things go
k
afterall, once my login worked, the next step for me was to report PDK bug that renders 
pdk
unusable, so i can't submit modules as official guides showing how to do so tell me to work with PDK
b
oh ruby 3
closed it as a dupe. The team is working on Ruby 3 support. https://github.com/puppetlabs/pdk/issues/1171
it's coming soon though!
k
oh i see...
d
We're literally testing build candidates now
k
sounds good 🙂
a single sentence in puppetlabs/pdk README.md or a run-time 
sorry, your ruby is too new
would have safe me lots of time
i'm not a ruby person, and this ruby<3 (nice smiley pun) was absoloutely not obvious to me 😕
b
and the gemspec should constrain it to ❤️ hahaa 
<3
too
d
@Craig Gumbley
k
makes sense
@binford2k you closed my ticket as dup (right), but it also mentions conflicting synopsis in docs vs. usage output.
i guess pdk access both forms, but it looks like an error when official online docs/guides and 
--help
output don't agree on how to use the same tool
b
either should work.
👍 1
Open in Slack
PreviousNext
Powered by