Prettier's "Contributing" guide is not clear.
https://github.com/prettier/prettier/blob/main/CONTRIBUTING.md says:
To get up and running, install the dependencies and run the tests:
yarn
yarn test
So I did this:
git clone https://github.com/prettier/prettier.git
cd prettier
yarn
The output of the yarn command was
ERROR: There are no scenarios; must have at least one.
What am I missing?
(I'm asking this on Stack Overflow because https://github.com/prettier/prettier/issues/new/choose says to do so.)
Related
After pruning with the command "docker system prune -a" nodejs wont build anymore beacuse trix.css is missing. I am assuming this was probably deleted while pruning. How can I resolve this error (see the error below)? Why is it not created again while building the container again since the file is in the docker file.
Required path doesn't exist: /code/bower_components/trix/dist/trix.css trix
[13:57:39] 'vendorcss' errored after 1.63 ms
[13:57:39] Error: Promise rejected without Error
at Domain.onError (/usr/local/lib/node_modules/gulp/node_modules/async-done/index.js:49:15)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
at Domain.emit (events.js:211:7)
at Domain._errorHandler (domain.js:134:21)
at process._fatalException (bootstrap_node.js:375:33)
[13:57:39] 'staging' errored after 41 ms
ERROR: Service 'nodejs' failed to build: The command '/bin/sh -c gulp staging' returned a non-
zero code: 1
Usually I use this command : "sudo docker-compose -f docker-compose-staging.yml build nodejs" when I want to build the container again. I am very new to this and would be greatfull for some help.
For me, this was the case:
The issue exists because trix.css was removed in the latest version. It has nothing to do with docker system prune as far as I understand.
You can compare the two versions here: https://github.com/basecamp/trix/compare/1.3.1...v2.0.0
Basically, in order to fix this issue, you need to do
yarn install
yarn build
inside bower_components. This is suggested in the official updated README of the trix repository: https://github.com/basecamp/trix.
Once done with that, you will have trix.css and trix.umd.min.js files for your perusal.
Following on from here, when using OpenSUSE Tumbleweed I cannot get flatpak-builder to compile submodule dependencies. I first noticed this issue when developing a console application within Gnome Builder using the Vala dependencies Gee and GXml.
As a test, I have installed org.gnome.Books.json and issued the following command (as documented here):
$ flatpak-builder --repo=repo books-app org.gnome.Books.json
The outcome is the same as I observed when developing my own application, the fatal error:
Initializing build dir
Committing stage init to cache
Starting build of org.gnome.Books
fuse: failed to exec fusermount: Permission denied
<more stuff>
Cloning into '/home/robin/Projects-CSim/org.gnome.books/.flatpak-builder/build/gnome-online-accounts-1/telepathy-account-widgets'...
Submodule path 'telepathy-account-widgets': checked out '7d944b79961dfb6291110ceb27597a224d329b36'
error: Build directory /home/<user>/Projects/org.gnome.books/.flatpak-builder/rofiles/rofiles-D4R4cZ not initialized, use flatpak build-init
Error: module gnome-online-accounts: module gnome-online-accounts: Child process exited with code 1
Effectively it fails to build the very first submodule. This is the same behaviour that I observed when invoked from Gnome-Builder on my project; it downloaded but failed to build the very first submodule - in that case it was libgee-0.8.
I've double checked the Flatpak (V0.10.4) installation here and cannot find a solution. I understand from the documentation that invoking flatpak-builder should automatically invoke flatpak build-init.
This is worrisome as Gnome-Builder seems be using Flatpak as the default packager. Any suggestions?
The problem is not Flatpak. It is a conflict between Flatpak and fuse. For some reason this was not occuring with valac or meson from the command line, only Flatpak.
From here we find a solution:
# chmod +x /usr/bin/fusermount
Is this a peculiarity of OpenSUSE Tumbleweed? In any case, after making this change, Flatpak builds submodules as expected. Magnificent!
Not sure about the security aspect of this, however - any comments would be welcomed.
I have Debian Linux(64-bit) in VirtualBox.
Ram: 8Gb (for Debian 4Gb)
CPU: i5-3470
If any other details are needed please tell me.
I have followed instructions written here, and here you can see the console log.
For some reason I am unable to to build phantomjs and I can't understand why its not working... Have searched a lot, but couldn't find any thread which would be about this error.
--- EDIT ---
When I executed this command:
./configure --with-openssl-includes=/usr/include/openssl-1.0/ --with-openssl-libraries=/usr/lib/openssl-1.0/
Output was this:
--with-openssl-includes=/usr/include/openssl-1.0/: invalid command-line switch
--with-openssl-libraries=/usr/lib/openssl-1.0/: invalid command-line switch
The output of the console has changed but I still get errors: https://pastebin.com/wbgi8syg
Looks like you are on stretch (or later) and that you are already aware of the libssl vs libssl1.0 case.
Therefore, if you don't have libssl-dev installed, this line will get you further:
python build.py --qt-config "-I /usr/include/openssl-1.0/ -L /usr/lib/openssl-1.0/"
If you already have it installed and my suggestion doesn't work, you can uninstall libssl-dev for the time to build phantomjs which will likely avoid having to play further with configuration related variables.
Building BioPerl
Reading skip patterns from 'INSTALL.SKIP'.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ERROR: Can't create '/usr/local/bin'
Do not have write permissions on '/usr/local/bin'
6. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I cannot install bioperl on my linux,It happened when I run command 11 below:
7. git clone https://github.com/bioperl/bioperl-live.git
8. cd bioperl-live
9. perl Build.PL
10. ./Build test
11. ./Build install
Do not have write permissions on '/usr/local/bin'
Looks like you need to run the build script as root, so use the 'sudo' command like
sudo ./Build install
On a separate note, is there a specific reason you need to compile Bioperl from source? Using your distro's package manager would be the easiest way to go about getting bioperl running with the least number of headaches. Check out https://bioperl.org/INSTALL.html for a number of options for installing.
I am not able to install a BioPerl Module via cpanm. With
sudo cpanm Bio::SeqIO
The output says:
--> Working on Bio::SeqIO
Fetching http://www.cpan.org/authors/id/C/CJ/CJFIELDS/BioPerl-1.6.922.tar.gz ... OK
Configuring BioPerl-1.006922 ... OK
Building and testing BioPerl-1.006922 ... FAIL
! Installing Bio::SeqIO failed. See /home/administrator/.cpanm/work/1398677477.16274/build.log for details. Retry with --force to force install it.
When adding --force it says:
--> Working on Bio::SeqIO
Fetching http://www.cpan.org/authors/id/C/CJ/CJFIELDS/BioPerl-1.6.922.tar.gz ... OK
Configuring BioPerl-1.006922 ... OK
Building and testing BioPerl-1.006922 ... FAIL
! Testing BioPerl-1.006922 failed but installing it anyway.
Successfully installed BioPerl-1.006922
1 distribution installed
So I am not sure whether I can use BioPerl now properly? Can I simply ignore that the testing failed?
I have already tried to reinstall CPAN with
o conf init
in the CPAN prompt, but the outcome was the same. I am working with Perl V5.14.2 and cpanm -v brings me:
cpanm (App::cpanminus) 1.6933 on perl 5.014002 built for x86_64-linux-gnu-thread-multi
Work directory is /home/administrator/.cpanm/work/1398677790.16651
You have make /usr/bin/make
You have LWP 6.05
You have /bin/tar: tar (GNU tar) 1.26
I am happy with any help, since I am a totally Linux newbie.
BioPerl uses many modules that you might not have installed. From BioPerl INSTALL file:
Remember that there are over 900 modules in BioPerl and the test
suite is running more than 12000 individual tests, a few failed tests
may not affect your usage of BioPerl
Most of the time you will not need these additional modules depending on what modules within BioPerl you are using. I'm sure that BioPerl has installed correctly on you system. I would work through http://www.bioperl.org/wiki/HOWTO:Beginners to learn BioPerl. If you get errors running these basic codes in the HOWTO, repost another question.
Good luck,
Paul