Getting the following error message when calling composer install.
Fatal error: Declaration of Composer\IO\BaseIO::hasAuthentication($repositoryName) must be compatible with Composer\IO\IOInterface::hasAuthentication(string $repositoryName) in phar:///usr/local/psa/var/modules/composer/composer.phar/src/Composer/IO/BaseIO.php on line 20
This is occurring in our dev environment when we run the gitlab pipeline to build and deploy in our CI/CD pipeline. No changes have been made to this process that has been running flawlessly for years. My guess is that something has changed in the composer base code library in the last few days.
Anyone else having this same issue? Or does anyone have a clue on how to fix this issue?
Related
The exact error is:
[0328/091115.205:FATAL:v8_initializer.cc(447)] Error loading V8 startup snapshot file
Could you please help to fix and be able to use Cypress?
I tried (steps):
First: C:/inetpub/wwwroot/cypress-example>npm install
Second: C:/inetpub/wwwroot/cypress-example>npx cypress run
(both command using cmd.exe as administrator permission and I was running it in the file of the website example that I criated...C:/inetpub/wwwroot/cyrpress-teste)
exact error bellow:
Cypress failed to start.
This may be due to a missing library or dependency. https://on.cypress.io/required-dependencies
Please refer to the error below for more details.
[0328/091115.205:FATAL:v8_initializer.cc(447)] Error loading V8 startup snapshot file
Platform: win32-x64 (10.0.19044)
Cypress Version: 9.5.2
I got the same error in cypress v9.5.4
Solved this by installing older version.
Just uninstall the current version, write "cypress": "^8.4.1" and run npm i
I really need some help with what seems to be the most basic task (setting up the expo/react-native project). I've installed the expo-cli (v3.11.7), react-native (v2.0.1), watchman (v4.9.0) and node (v12.14.1). I've followed the tutorial up until the point where I need to run expo start and I get the following error:
Your project is in SDK version >= 33.0.0, but the expo package version seems to be older.
Error: node_modules directory is missing. Please run npm install in your project directory.
Couldn't start project. Please fix the errors and restart the project.
Set EXPO_DEBUG=true in your env to view the stack trace.
I've then run npm install and tried again but the same error pops up. I've removed the node_modules folder and that didn't work either.
Update:
When I npm install this is the error I'm seeing:
npm WARN deprecated core-js#1.2.7: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
npm ERR! code EPROTO
npm ERR! errno EPROTO
npm ERR! request to https://codeload.github.com/expo/react-native/tar.gz/sdk-36.0.0 failed, reason: write EPROTO 4521895360:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1544:SSL alert number 40
I've installed yarn (v1.21.1) and tried installing using this with the same error:
warning expo > fbemitter > fbjs > core-js#1.2.7: core-js#<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js#3.
error An unexpected error occurred: "https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz: write EPROTO 4356277696:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1544:SSL alert number 40
Can anyone advise?
I've managed to solve the problem. I was trying to install over my home network, which apparently has some proxy restrictions! No idea why.
Someone advised me to try again but connected to another network or my mobile hotspot. I tried this and it worked! Problem solved. So I guess for any others that may be experiencing the same problem, try connecting to another network and see if that helps.
If this fails, then I suppose looking at the proxy configuration and making changes there may help. But I wouldn't advise doing this unless you know exactly what you're doing.
I'm at a total loss here.
All I am trying to do is clone a Laravel Project onto my local mac machine and I've probably spent 10 - 12 hours on this and I keep getting the same errors over and over.
I've tried Homestead, MAMP and now I am on Valet.
I can load the app but all the links are broken so the CSS and JS don't load.
After I clone (via bitbucket) the project I hit the test site on my machine and I get this error:
Warning: require(/Users/henry/sites/nestdb2017/bootstrap/../vendor/autoload.php): failed to open stream: No such file or directory in /Users/henry/sites/nestdb2017/bootstrap/autoload.php on line 17
Fatal error: require(): Failed opening required '/Users/henry/sites/nestdb2017/bootstrap/../vendor/autoload.php' (include_path='.:/usr/local/Cellar/php/7.3.9_1/share/php/pear') in /Users/henry/sites/nestdb2017/bootstrap/autoload.php on line 17
The next thing I do is I try to install the missing vendor files by doing this:
composer update --no-scripts
which then throw the broken links.
Literally I'm going to have to throw the towel in here...
It's unbelievable how hard this is.
Is it because the source files are corrupt in the first instance??
Try
composer install
php artisan clear-compiled
Then
composer dumpautoload
Tell us the results.
Facing a weird issue with a React/Typescript setup.
Running webpack -p on OSX/Windows compiles just fine with no errors from the TypeScript/TSX compiler at all.
However, on Ubuntu it will throw a TypeScript specific error, specifically:
ERROR in [at-loader] ./src/scenes/Component.tsx:5:23
TS2307: Cannot find module 'History'.
The specific line which throws an error is:
import {History} from "History";
package.json has both normal and #types package for History:
"#types/history": "4.6.0",
"history": "4.7.2",
And again, I can run webpack -p with the exact same code, same webpack configuration and same version on OSX without it throwing an error. Process is the same! However, on Ubuntu the build will fail with the above error.
The sinner was awesome-typescript-loader(at-loader). #3.2.x it threw this error; downgrading to #3.1.3 made it go away. This happened after upgrading packages apparently - but again, only seems to affect Ubuntu.
I have been running on some problems since the last update (6.38.1). docpad seems to be broken on macosx the command "docpad run" or "docpad watch" returns the error (on the browser)
Error 15 (net::ERR_SOCKET_NOT_CONNECTED): Error unknown
when i try to access
http://localhost:9778
but "docpad server" works without problems, so maybe the error is the liverload module or other module for development... i'm not able to isolate this problem.
does anyone has the same problem and maybe a solution to share? i'm about to leave docpad because of this error :(