I am trying to upload images in ASW S3. But I get the error Class 'League\Flysystem\AwsS3v3\AwsS3Adapter' not found. So I tried to run composer require league/flysystem-aws-s3-v3 But it gives me error . The error is :
Problem 1
- league/flysystem-aws-s3-v3[2.0.0, ..., 2.x-dev] require league/flysystem ^2.0.0 -> found league/flysystem[2.0.0-alpha.1, ..., 2.x-dev] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- league/flysystem-aws-s3-v3[2.0.0-alpha.1, ..., 2.0.0-alpha.2] require league/flysystem 2.0.0-alpha.1 -> found league/flysystem[2.0.0-alpha.1] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- league/flysystem-aws-s3-v3[2.0.0-alpha.4, ..., 2.0.0-beta.1] require league/flysystem 2.0.0-alpha.3 -> found league/flysystem[2.0.0-alpha.3] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- league/flysystem-aws-s3-v3[2.0.0-beta.2, ..., 2.0.0-beta.3] require league/flysystem ^2.0.0-beta.1 -> found league/flysystem[2.0.0-beta.1, ..., 2.x-dev] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- league/flysystem-aws-s3-v3 2.0.0-RC1 requires league/flysystem ^2.0.0-RC1 -> found league/flysystem[2.0.0-RC1, 2.0.0, 2.x-dev] but the package is fixed to 1.1.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires league/flysystem-aws-s3-v3 ^2.0 -> satisfiable by league/flysystem-aws-s3-v3[2.0.0-alpha.1, ..., 2.x-dev].
My PHP version is : 7.4.11 and my Alaravel version is 7.30.0. Can someone please help me to resolve this?
You should try run this command in your terminal
composer require league/flysystem-aws-s3-v3 ^1.0
It works very well in my last experience using Laravel 7.30.3 (PHP v7.4)
Related
The problem I’m having is after the profiles.yml All checks passed! (the connection successful)
when i run dbt get this message
Configuration paths exist in your dbt_project.yml file which do not apply to any resources. There are 1 unused configuration paths:- models.dbt_project.example
when I run
dbt --version
Core: - installed: 1.4.1
- latest: 1.4.1 - Up to date!
Plugins: - sqlserver: 1.3.0 - Not compatible!
- synapse: 1.3.2 - Not compatible!
At least one plugin is out of date or incompatible with dbt-core.
You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation
The error message is telling you what is wrong. There is config in your dbt_project.yml file that does not apply to any files in your models directory.
When you run dbt init, it creates some example models (.sql files) in the models/example directory, like my_first_dbt_model.sql. It also adds some example config to dbt_project.yml that looks like this:
# towards the bottom...
models:
your_project_name:
# Config indicated by + and applies to all files under models/example/
example:
+materialized: view
You need to delete the example key, since you deleted that directory. You could also delete the keys above it, or keep them, since you'll probably add config at some point.
The OTHER error is probably because you installed dbt-core separately from dbt-synapse. You should delete your virtual environment and start over by just running pip install dbt-synapse, which will automatically install a compatible version of dbt-core. You should NEVER pin versions of dbt-core, only the version of your adapter (since the adapter will specify its compatible versions of dbt-core).
I try to install the package adldap2/adldap2-laravel with the command composer require adldap2/adldap2-laravel but I get these errors:
Info from https://repo.packagist.org: #StandWithUkraine
Using version ^6.1 for adldap2/adldap2-laravel
./composer.json has been updated
Running composer update adldap2/adldap2-laravel
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- adldap2/adldap2-laravel v6.1.6 requires adldap2/adldap2 ^10.1 -> satisfiable by adldap2/adldap2[v10.1.0, ..., v10.4.2].
- adldap2/adldap2-laravel[v6.1.0, ..., v6.1.1] require illuminate/support ~5.5|~6.0|~7.0 -> found illuminate/support[v5.5.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev] but these were not loaded, likely because it conflicts with another require.
- adldap2/adldap2-laravel[v6.1.2, ..., v6.1.5] require illuminate/support ~5.5|~6.0|~7.0|~8.0 -> found illuminate/support[v5.5.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
- adldap2/adldap2[v10.1.0, ..., v10.4.0] require psr/log ~1.0 -> found psr/log[1.0.0, ..., 1.1.4] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- adldap2/adldap2[v10.4.1, ..., v10.4.2] require psr/simple-cache ~1.0|~2.0 -> found psr/simple-cache[1.0.0, 1.0.1, 2.0.0, 2.x-dev] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires adldap2/adldap2-laravel ^6.1 -> satisfiable by adldap2/adldap2-laravel[v6.1.0, ..., v6.1.6].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require adldap2/adldap2-laravel:*" to figure out if any version is installable, or "composer require adldap2/adldap2-laravel:^2.1" if you know which you need.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
The laravel version is v9.3.8. I am not sure if I break something when I run composer require adldap2/adldap2-laravel --with-all-dependencies.
The issue is due to adldap2/adldap2 package requiring the psr/simple-cache 2.0.0 but the Laravel framework is using 3.0.0
Downgrading, the psr/simple-cache to 2.0.0 will not make an issue.
I executed composer require adldap2/adldap2-laravel --with-all-dependencies to enable composer to install, upgrade or downgrade the required required dependencies.
I need to install a specific RC1 version for a Drupal 8 module with composer.
Example: https://www.drupal.org/project/field_group (8.x-3.0-rc1)
I've tried to use the constraint: '8.x-3.0-rc1'.
composer require drupal/field_group:8.x-3.0-rc1
The error message:
[UnexpectedValueException]
Could not parse version constraint 8.x-composer: Invalid version string "8.x-composer"
You can specify the version of the module / theme you want to download as follows:
composer require drupal/<modulename>:<version>
For example:
composer require 'drupal/token:^1.5'
composer require 'drupal/simple_fb_connect:~3.0'
composer require 'drupal/ctools:3.0.0-alpha26'
composer require 'drupal/field_group:3.0-rc1'
composer require 'drupal/token:1.x-dev'
To avoid problems on different terminals/shells, surround the version in quotes as in the examples above. In these examples, the versions map as follows:
^1.5: maps to the latest stable 8.x-1.x release of the module.
~3.0: maps to the latest stable 8.x-3.x release of the module.
3.0.0-alpha26: maps to version 8.x-3.0-alpha26
3.0-rc1: maps to version 8.x-3.0-rc1
1.x-dev: maps to 8.x-1.x-dev
For more on version constraints with ~ (tilde) and ^ (caret) see Next Significant Release Operators.
I've recently upgraded to Protractor 5.1.1 and am facing some issues when setting cookies via browser.manage().addCookie()
The API has changed between versions 2 and 3 of Selenium-webdriver to expect an object rather than the previous 2..6 arguments. When I make the changes to my code to use the object, the typescript compiler complains saying that it expects 2..6 arguments.
old api:
browser.manage().addCookie('cookieName', 'cookieVal');
new api:
browser.manage().addCookie({name:'cookieName', value: 'cookieVal'});
I think this is because the #types/selenium-webdriver in the package.json of protractor v5.1.1 is pointing at version 2.53.39. The version of the actual selenium-webdriver the same package.json is referencing is 3.0.1.
Should this be the same value? Is anyone else experiencing problems with this?
Yup, this is happening because the type definitions was not written at the time.
workaround
Here is the workaround for now:
(browser.manage() as any).addCookie({name:'cookieName', value: 'cookieVal'});
We are setting browser.manage returned options object to any. Then we can give it the addCookie method.
OR
upgrade definitions
you could upgrade your #types/selenium-webdriver type definitions to version 3.
I'm having the same problem! I do know that the #types/selenium-driver is now updated to version 3.0.0.
I haven't had luck with this, but you could try installing it directly (i.e. npm install --save-dev #types/selenium-webdriver) and adding it to your list of types in your tsconfig.json file (i.e. types: [ "selenium-webdriver" ].
I updated the SQL file for my module - how do i get it to automatically run again without creating a new version of it?
I am working on my first module and just need to tweak this one so it works on a new install for someone else.
When Magento automatically runs a SQL file for a setup resource, it makes an entry in the core_resource table.
mysql> SELECT code,version,data_version FROM core_resource;
adminnotification_setup 1.0.0 1.0.0
admin_setup 0.7.2 0.7.2
amazonpayments_setup 0.1.2 0.1.2
api_setup 0.8.1 0.8.1
backup_setup 0.7.0 0.7.0
bundle_setup 0.1.11 0.1.11
...
You'll need to remove the single row in this table that corresponds to your module, and then clear your Magento cache. This will let you re-run your setup resource SQL file.
ONLY remove that single row — if you remove rows for the core modules, there will be much breaking and weeping.