-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Skipping because provider prefetch failed #9532
Comments
Thank you for reporting this @andryua , I saw you also opened an issue in the Chocolatey module. We will chat with the modules team and see if we can determine where the issue lies. |
Hi! Can you help me? I using chocolatey 0.15 or 1.31 not latest version. And one more - we configuring chocolatey by puppet and after update to 8.8.1 - puppet agent always rerewrited config.xml (chocolatey config file). now we using 8.7.0 - that version working ok. |
if i update to chocolatey lates version - error still exist on puppet agent 8.10.0 |
puppet-chocolatey breaks chocolatey.config when modified
|
after investigation - problem in REXML. Last working version is - 3.3.2. Newest version - puppet agent sending errors. (puppet agent 8.9.0 upgrated to rexml - 3.3.6) |
@andryua Thanks, could you provide a minimal XML reproduction that triggers the bug? |
this is config file (i renamed it into txt) i validated it on online xml validators - everything is ok |
The problematic config contains a byte order mark (BOM) maybe there was a regression in rexml with respect to stripping the BOM out?
|
Maybe. I don't know. So, what do You recommend me? |
Chocolatey support answered:
|
👋 Chocolatey Team Memer here. Just to expand further on this...
This was being discussed in our Discord channel here: https://discord.com/channels/778552361454141460/897088817293574154/1326489091021471789 The encoding of the chocolatey.config file is UTF-8-BOM (as can be seen here), and it has been for at least 11 years (April 16, 2014 which is the date of the last commit that I can easily see in the repository). So nothing has changed with the encoding on this configuration file from a Chocolatey perspective in that time. I tend to agree with this comment from @joshcooper:
If there is anything that we can do to help, please let me know. |
Hi! Maybe, I found how to resolve this issue: |
or
against
|
Migrated issue to PUP-12090 |
Hi @andryua I was not able to reproduce the problem using puppet-agent 8.10.0 and rexml 3.3.6 with the chocolatey config you provided. Both
I tried changing the active code page to 1251, but get the same result:
Are you sure you're running ruby from the puppet-agent package? Are you setting any environment variables like RUBY_OPTS that might change the Could you try the following?
Ruby's File.read(choco_config, encoding: 'bom|utf-8') |
Hi! I tried with BOM and without BOM - look at this different symbols, please
if in provider (like i said in upper post) use File.open - not File.read! - everything work fine!
or
|
and one more thing - I using Ukrainian language for Windows, not English |
Based on |
I using cp866 by default code page. And You can see if running your script - everithing work ok, but, if I using command - ruby.exe -e "puts File.read('c:\programdata\chocolatey\config\chocolatey.config')" - first symbol was a problem for puppet-chocolatey provider. |
Describe the Bug
After update puppet agent to 8.10.0 i have errors wit chocolatey provider (8.7.0 - working)
Steps to Reproduce
Steps to reproduce the behavior:
in powershell or cmd running command
puppet agent -t
Environment
Output:
The text was updated successfully, but these errors were encountered: