When trying to run the command yarn install, the following error message is displayed:
"Internal Error: Expected an indexed object, got a string instead. Does your file follow Yaml's rules?"
My .yarnrc.yml is syntactically correct. What is the cause of the error?
Yarn v3.2.2
Node v16.14.0
Related discussion at github.com/yarnpkg/
Deleting the yarn.lock file from the same folder and running yarn install afterward solved the issue.
Related
When i use the command ipfs-update install v0.14.0
I get this error:
fetching go-ipfs version v0.14.0
binary downloaded, verifying…
install failed, reverting changes…
ERROR: install failed: test refs list: expected to see Qm…xxxx2 in the local refs!
Any help please?
Im on the v0.12.0 , ubuntu server
Error:
The style compilation failed, see the error below. Your recent actions may be the cause, please try reverting the changes you made.
Could not get content for /web_dialog_size/static/src/css/web_dialog_size.css defined in bundle 'web.assets_backend'.
When you get given error then follow the below steps:
Apps -> web_dialog_size -> uninstall module
If you need this module then again install it
I am new to Octave, coming from Matlab. I am trying to install a few packages, and so far none has worked. I have tried the download method from forge, then running the install command. But my question is about my latest attempt. There it is:
pkg install -global -forge io
csvconcat.cc:79:37: warning: result of comparison of constant 18446744073709551615 with expression of type
'unsigned int' is always true [-Wtautological-constant-out-of-range-compare]
while ((pos=str.find(prot, pos)) != str.npos) {
~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~~~~~
1 warning generated.
error: couldn't append to /Applications/Octave-4.4.1.app/Contents/Resources/usr/Cellar/octave-octave-app#4.4.1/4.4.1/share/octave/octave_packages
save: unable to open output file '/Applications/Octave-4.4.1.app/Contents/Resources/usr/Cellar/octave-octave-app#4.4.1/4.4.1/share/octave/octave_packages'
error: called from
install at line 254 column 7
pkg at line 437 column 9
Couldn't find any documentation on it, I am a bit lost.... (oh and btw, I can't find the config.log file! where is that gem?)
I am on MacOS catalina 10.15.7, and just followed that procedure https://flaviocopes.com/fix-xcrun-error-invalid-active-developer-path/, which solved the issues I had before which is described on that page.
cheers for any help
The error:
error: couldn't append to /Applications/Octave-4.4.1.app/Contents/Resources/usr/Cellar/octave-octave-app#4.4.1/4.4.1/share/octave/octave_packages
save: unable to open output file '/Applications/Octave-4.4.1.app/Contents/Resources/usr/Cellar/octave-octave-app#4.4.1/4.4.1/share/octave/octave_packages'
error: called from
install at line 254 column 7
pkg at line 437 column 9
basically says it's failing to save to that file. Probably a permissions issue. Check if the file /Applications/Octave-4.4.1.app/Contents/Resources/usr/Cellar/octave-octave-app#4.4.1/4.4.1/share/octave/octave_packages exists and its permissions. That file is a database of all packages installed globally, i.e., for all users in the system.
Fixing the permission issues is dependent on what is the permissions issue you have (probably you need to run octave as root to install a global package). But maybe try to install the package for your user only, i.e., install the package without the -global flag, like so:
pkg install -forge io
I just changed two lines of code in the Google cloud functions source code using inline statement, the two lines of code involve parsing date string using datetime library, no updates to anything else. This same deployment has been working for more than a year now.
All of a sudden I get two errors -
Error 1 -
(gcloud.functions.deploy) OperationError: code=3, message=Build
failed: {"error": {"canonicalCode": "INTERNAL", "errorMessage":
"pip_install_from_wheels had stderr
output:\n/opt/python3.7/bin/python3.7: No module named pip\n\nerror:
pip_install_from_wheels returned code: 1", "errorType":
"InternalError", "errorId": "ECB5F712"}}
Resolved that by removing pip from requirements.txt (again not sure why this is a problem now and not for over a year)
If I address 1, I get the following error -
Error 2 -
(gcloud.functions.deploy) OperationError: code=3, message=Build
failed: {"error": {"canonicalCode": "INTERNAL", "errorMessage":
"gzip_tar_runtime_package gzip /tmp/tmpGLHQx9.tar -1\nexited with
error [Errno 12] Cannot allocate memory\ngzip_tar_runtime_package is
likely not on the path", "errorType": "InternalError", "errorId":
"2A1581FF"}}
Memory is already at 2048 and nothing changed other than the two lines of code above.
Let me know if this has been happening and what is the resolution.
It looks like this has to do with packages than anything else. I deployed a dummy function and added each package from requirements.txt until it failed. It turns out the problem packages were
a. gpflow
b. tensorflow
Last deployment with these packages was successful as of Feb 20. Not sure why I can't install them without those errors anymore. regardless, tried using the versions that would have been consistent with Feb 20 timeline with no luck. So refactored my code and removed all the functionality that was using that and deployed successfully.
Request to Google Cloud Folks : Why this behavior ? Also "Invalid ARGUMENT" in logs (Stackdriver or google cloud logging whatever you call it) is misleading.
The first error, as explained in this post, is due to pip being defined in your requirements.txt file. Specifying pip as a dependency for the function causes message to appear. You did the right thing by removing it from the requirements.txt file.
The second error usually appears if the number of files or the size of the content that is being uploaded is too big and the instance used to deploy your code runs out of memory. You perhaps were using too many dependencies or static files, as explained here.
I am trying to run yum update on my machine and I get this error.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: boxgrinder-noarch. Please verify its path and try again
Any idea what is wrong?
I use Fedora 15
cd /etc/yum.repos.d/
perl -i -ape 's/https:/http:/g' *.repo
worked for me.
I have the same problem in Fedora 14.
When I changed the *.repo file in /etc/yum.repos.d, it works.
"Change all 'https' to 'http' in each *.repo file"
such as:
[fedora]
name=Fedora $releasever - $basearch
failovermethod=priority
baseurl=ftp://ftp.cru.fr/pub/linux/fedora/releases/11/Everything/x86_64/os/
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
#mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releasever&arch=$basearch
enabled=1
metadata_expire=7d
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearchthe
change is like this
"mirrorlist=https:"--->"mirrorlist=*http:*"
find out the repo which is causing a problem in your case it is
box-grinder, remove the repo or fix it.
cd /etc/yum.repos.d/
mv /etc/yum.repos.d/box-grinder.repo /etc/yum.repos.d/box-grinder.repo.disabled
I was able to get rid of this error by removing the boxgrinder repos
I removed these files
boxgrinder-nightly.repo boxgrinder-noarch.repo boxgrinder-x86_64.repo
from /etc/yum.repos.d/ directory.
[ percona ]
Attempting to get the percona-release-0.1-3.noarch.rpm
The issue I had:
http://repo.percona.com/release/6.6/RPMS/noarch/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: percona-release-noarch. Please verify its path and try again
What I did to fix the issue:
sed -i 's/$releasever/5/g' /etc/yum.repos.d/percona-release.repo
You won't see a response.
yum clean all
yum update
This should solve your problem
What this does? sed overwrites whatever the percona-release.repo file says with s/$releasever/5/g incase the yum clean all doesn't catch it or some other error occurs.
yum repo shell drupal percona fedora