When using the current mysql 8.4.0 cookbook I receive a full screen of deprecation errors when deploying.
Deprecated features used!
rename install_method to new_resource.install_method at 1 location:
- /root/chef-solo/local-mode-cache/cache/cookbooks/mysql/libraries/mysql_service.rb:34:in `installation'
See https://docs.chef.io/deprecations_namespace_collisions.html for further details.
The github project does not show any outstanding issues related to the deprecation warnings.
Does anyone know how to get rid of these messages so I can have a clean deploy?
You'll have to wait until the cookbook fixes things, but it's only a warning so you don't need to worry. It's a new warning in Chef 13.2 so we're still working on getting things cleaned up. The feature won't actually be removed until Chef 14 in April 2018 so no rush :)
Related
I'm trying to initiate astro. When i don't choose a framework i get this error although i have git installed and fully working. Any help will be highly appreciated.
√ Which frameworks would you like to use? »
> Copying project files...
could not find commit hash for latest
This seems to be an issue with degit. Please check if you have 'git' installed on your system, and install it if you don't have (https://git-scm.com).
If you do have 'git' installed, please file a new issue here: https://github.com/withastro/astro/issues
It depends on your OS and environment.
For instance, withastro/astro issue 2144 reports the exact same error message, but on Windows, using Linux on WSL2 (Ubuntu 20.04.3 LTS).
Double-check your %PATH%/$PATH in your execution environment.
Update Oct. 2022, ten month later: withastro/astro issue 2144 is reported closed with the workaround by Matej Bunček:
As I was researching this seems to be a general issue with NPM for those who uses SSH.
There's an open issue here: npm/cli#2610 which is still far from being resolved and it's a huge thread.
Some folks might be interested in these workarounds to get it working.
git config --global url."https://github.com/".insteadOf git#github.com:
git config --global url."https://".insteadOf git://
Also I've tried yarn, npm and pnpm, all of them seems to have same problem so I believe it's core problem of node.
Also both npm 6 and 7 are not working.
Not a direct solution to your error message, but a general solution for those kinds of errors:
I would recommend doing the development inside docker containers, so called devcontainers.
Since you will develop in separate and isolated environments containing only the project's minimum dependencies and tools, it is a lot less likely to face OS specific issues in general.
Here are some resources to get started:
https://code.visualstudio.com/docs/remote/containers
https://microsoft.github.io/code-with-engineering-playbook/developer-experience/devcontainers/
https://github.com/microsoft/vscode-dev-containers
I am new to cloud functions and was testing this sample code https://github.com/firebase/functions-samples/tree/master/quickstarts/uppercase-firestore
This fails to execute due to an error from nanomatch. Looking at nanomatch repository on GitHub This is a listed issue and reverting back to 1.2.9 takes care of this error.
I am trying to fix this on my end - but how do I do this? Can somebody guide me on this. Thank you for the help.
TypeError: Cannot read property 'addQmark' of undefined
at Object.<anonymous> (/user_code/node_modules/firebase-admin/node_modules/nanomatch/lib/compilers.js:92:15)
at Object.visit (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:129:15)
at Object.mapVisit (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:143:12)
at Object.compile (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:168:10)
at Snapdragon.compile (/user_code/node_modules/firebase-admin/node_modules/snapdragon/index.js:156:32)
at /user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:786:23
at memoize (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:859:13)
at Function.micromatch.compile (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:783:10)
at create (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:686:25)
at /user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:695:16
THIS BUG WAS FIXED
The version that caused the bug was reverted right when this issue was reported on GitHub, which was within minutes of it being released. To get the fix, just reinstall. You might need to delete node_modules and/or lockfiles first, to ensure cached versions aren't used by NPM. This conversation belongs on GitHub, so that we can respond to user feedback. I found this by chance. StackOverflow is not for support).
Edit 2: it appears that firebase-admin itself needs to re-install dependencies as well. I'm looking into how to make that happen.
Please report and check issues on GitHub, where the codebase is and where this discussion belongs.
Visit https://github.com/micromatch/nanomatch/issues/15 for more info.
Faced the same problem "Thumbnail URL not saved to firestore. Cannot read property 'addQmark' of undefined"
Started today morning when I upgraded to the latest firebase-tools#3.19.1
At first thought was issue with my code, but after rollbacking my code the situation persisted.
Rolled back to firebase-tools#3.19.0 and the situation got fixed.
There is a bug in the latest firebase-tools
Use this:
npm install nanomatch#1.2.9 -S
just rollback to older version
npm install -g firebase-tools#3.19.0
Firebase team is probably/hopefully redeploying all functions without the broken nanomatch package, but for me following the advice from #abhi and redeploying immediately solved the issue!
npm install nanomatch#1.2.9 -S
firebase deploy --only functions
(npm install in the functions folder!)
We recently upgraded an old rails app from rails 3 to 4.2, along with many other gem updates. Now I can't get my rails app to load any pages. We were on JRuby 9.1.0.0 but upgraded to 9.1.8.0. However, I'm hitting the same problem on both versions.
Once we start tomcat with our latest .war, it runs all the way until I see the INFO: Server startup in 1234ms message. I've added some debug statements in my rails environment / initializers files to follow it through and it is hitting each of them. So once I see the startup message from tomcat, I figured it would be okay. However, it immediately spits out the following message quite a few times:
DEBUG: resetting rack response due exception
Every time I load a URL, it also shows that message in my logs.
I see that it's from this jruby-rack class but I have no idea how to debug or troubleshoot this further.
I assume that something in my configuration is causing a problem or that a class/module is somehow short-circuiting it but I'm not sure how to identify which one it is or isolate the issue.
Does anybody know of a way to get some more verbose logs or ways to figure out where the problem is happening?
Happy to post any config/gemfiles etc if it will help.
After receiving some great help from the #jruby IRC channel, they mentioned the error message was missing the specific exception message. I was using the latest version, v1.1.21 so I just made a hack-build that added some logging to identify my problem further. Turns out it was a runtime error because of some missing config.
I made an issue with jruby-rack and a PR which will hopefully make its way into the next release!
Out of the blue recently, I started receiving notifications that my Jekyll builds were failing on GitHub Pages:
Page build failed. For more information, see https://help.github.com/articles/troubleshooting-github-pages-builds/.
Besides that, there was no info given, and the site built fine on my local machine. I tried everything I could think of: I built the site locally (worked fine on my machine), I deleted the last few files that had been added (no improvement), and I reset the master branch to exactly as it was when I last had a successful build. I figured for sure the last tactic would work, but I kept getting build failures.
I eventually figured out the answer, which I'm going to write in a moment.
It turned out the problem was that GitHub upgraded their version of Jekyll. I had to come to the solution by two steps:
Upgrade the github-pages gem on my own computer:
$ bundle update github-pages
Discover an interesting new error message:
Liquid Exception: undefined method `gsub' for 1000:Fixnum in /_layouts/post.html
After some fiddling around (and using Jekyll's --verbose option to find where the build was choking), I discovered that this gsub error was caused by a post I had, which was titled "1,000". (It was about a sleepless night, where I tried to count my way to sleep, and gave up after 1,000.) Some updated parser was trying to parse this as a number, apparently. To fix it I changed
title: 1,000
to
title: "1,000"
And voilà, GitHub Pages was satisfied.
I'm having the following problem with Hudson after upgrading to 2.1.0:
After successfully creating the doxygen output, the following exception occurs:
Publishing Doxygen HTML results.
The determined Doxygen directory is 'C:/doxy/myDir'.
FATAL: error
hudson.util.IOException2: java.io.IOException: Unconnected pipe
The error did not occur with 2.0.1, unfortunately, downgrading does not work - Hudson tells me, that it can't read the job files anymore.
Does anyone know the best way to deal with this? Is there a simple solution to either make the doxygen plugin work in 2.1.0 or to successfully downgrade to 2.0.1?
Not sure what exactly the problem was, but migrating to the newest Jenkins release and using the HTML report publisher plugin instead of the Doxygen plugin is at least a work