enter image description here
enter image description here
getting this error while expo eject
× Something went wrong installing JavaScript dependencies, check your yarn logfile or run yarn install again manually.
Related
I am working on a project with expo cli. last night I completed some of my work then in morning when I started my expo project it's giving this error which solution I have not found. I have tried making new project but when even on new project when I run command expo start it gives me same error. I reinstalled enter image description hereexpo cli & node when reset my npm cache.
I'm updating to the newest version of IBM DSX Desktop 1.1.7. The install process stalls and displays
"Downloading DSX... 0%".
The file desktop.log ends with lines
“The size is 83.85 and installsize is 14.73”
and
“Docker Storage Requirement Failed”.
The Docker app is up to date. I’ve tried the usual reboot, etc without success.
Any clue?
I work on the DSX Desktop team. You might be encountering a bug with the installation code. The good news is that it's a pretty simple fix if you are. Here's how to check:
Diagnosis & Fix
Open up your terminal or command prompt and run docker system df. Look for the entry that corresponds to IMAGE SIZE. If the unit is in kB or B, then you're encountering the bug.
To fix it, run docker pull busybox. Once the pull completes, you should be able to update DSX Desktop. After it successfully updates, you can run docker rmi busybox.
If the unit is in GB, then that means your existing images are taking up too much space. The limit is 60GB so make sure your IMAGE SIZE + installSize <= 60GB.
Explanation
There's a typo in the code that causes the installer to mistake kB and B for GB. Thus, if you have an IMAGE SIZE of 83.85kB, the installer will treat it as 83.85GB and will complain about being over the 60GB limit.
So to fix it, we pull a temporary image busybox, which updates our IMAGE SIZE to be in MB, allowing us to avoid the bug. After we successfully update DSX Desktop, we can remove the temporary image.
This has been patched and will be fixed in an upcoming release.
In my case, dsx-desktop.log has the following error:
[2017-11-04 19:52:03:0214] [error] exec error: Error: Command failed: eval $(docker-machine env ibm-dsx) && docker system df
docker: 'system' is not a docker command.
See 'docker --help'.
[2017-11-04 19:52:03:0214] [error] stderr: docker: 'system' is not a docker command.
See 'docker --help'.
It turns out "docker system" command is only available after Docker API version 1.25. Check your API version from the output of "docker version".
After I reinstalled a docker version with API version 1.33, it is able to download.
Using Refile gem to upload messages in my app to s3. My server is Ubuntu 16 and I am using Capistano and Nginx for deployment and server. Not sure why this error is coming up in production, but I am having trouble retrieving images in production from s3. It works fine in Dev, but in production, the images upload fine and I can see them in my s3 bucket, but they do not display when I try to retrieve them. The error message I get in the log files is:
Refile::App: Error -> ImageMagick/GraphicsMagick is not installed
I have installed imagemagick and graphicsmagick on my server but no change. Is anyone else having this issue and what could be missing?
This must solve your problem
sudo apt-get install imagemagick
if still problem exists this may work Click to go to documentation
I have a auto scaling Elastic Beanstalk app running Python where I want to use PIL. When I do, it says that my jpeg decoder is missing and that I need to install libjpeg.
So I follow AWS official guides for "configuration files" here:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-ec2.html
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers.html#customize-containers-format
But I can't get it working.
If I understand the guides correctly I should set up a directory called .ebextensions in my application folder. Inside my .ebextensions I should set up a foo.config file. In my case I name it python.config.
In this file I'm suppose to execute commands. The code of my .config file is:
packages:
yum:
libjpeg-devel: '6b'
I deploy my app and I can see in my Log Snapshots that its inflating and creating the file like this:
-------------------------------------
/var/log/eb-tools.log
-------------------------------------
creating: /opt/python/ondeck/app/.ebextensions/
inflating: /opt/python/ondeck/app/.ebextensions/python.config
inflating: /opt/python/ondeck/app/application.py
...
However, I can't find anything about actually executing the commands. I've been searching my log for "yum", "python.config", "jpeg", "libjpeg" and so on without any relevant traces. I restart the application server but still I get the same messages saying libjpeg is missing.
I have seen other people asking similar questions, about config files not working. But I have yet to see any answer.
I ran into the same issue, instead of setting up a completely new Elastic Beanstalk app, I connected to the EC2 instance via SSH and re-installed PIL (or Pillow).
On EC2 instance, I ran the following commands:
source /opt/python/run/venv/bin/activate
pip uninstall PIL
pip install PIL
Now PIL supports jpeg encoding =)
I "fixed" this by setting up a completely new Elastic Beanstalk app and deploying the exact same application there. It then successfully installed the libjpeg package.
I was never able to find out the answer to why it didnt work on the first Elastic Beanstalk App. But maybe it had something to do with PIL was first installed and then it couldnt install libjpeg after.
Error 402: App packaging failed: 'Failed synchronizing resource pool'
I got this error when deploy a node.js application to api.cloudfoundry.com.
the vmc I used is:
vmc 0.3.10
I want to know how does this error happened. Is there something wrong with my vmc? or something wrong with my node.js application?
Thank you.
You'll definitely want to upgrade to the latest vmc. "gem update" should refresh it to 0.3.18 for you but if not, "gem install vmc" to grab the newest.
What steps did you follow to deploy the app - did you just run vmc push and follow the prompts, did you have a manifest.yml file in place (probably not as vmc 0.3.10 may have pre-dated manifest support), did you provide additional parameters to vmc push?