I am using window command prompt,When I update composer facing with below error
C:\xampp\htdocs\myproject>composer update
Warning: This development build of composer is over 60 days old. It is recommend
ed to update it by running "C:\ProgramData\ComposerSetup\bin\composer.phar self-
update" to get the latest version.
Loading composer repositories with package information
Updating dependencies (including require-dev)
Failed to decode response: zlib_decode(): data error
Retrying with degraded mode, check https://getcomposer.org/doc/articles/troubles
hooting.md#degraded-mode for more info
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for phalcon/incubator dev-master -> satisfiable by ph
alcon/incubator[dev-master].
- phalcon/incubator dev-master requires ext-phalcon >=2.0.4 -> the requested
PHP extension phalcon is missing from your system.
The last line should give you a clue: You haven't yet installed PhalconPHP on your system, which is required by the Incubator package.
Also, run a composer self-update as recommended.
Related
NuGet delivered the Microsoft.WindowsAppSDK v1.1.2 yesterday (2022-07-02). My updated WinUI 3 programs now produce the following message when run:
This application requires the Windows App Runtime Version 1.1
(MSIX package version >= 1002.543.1943.0)
I uninstalled previous versions of the runtime and ran the suggested installer (from an elevated PowerShell prompt):
Installing license: MSIX_MAINPACKAGE_LICENSE
Install result : 0x0
Installing license: MSIX_SINGLETONPACKAGE_LICENSE
Install result : 0x0
Deploying package: Microsoft.WindowsAppRuntime.1.1_1000.516.2156.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Deploying package: Microsoft.WindowsAppRuntime.1.1_1000.516.2156.0_x86__8wekyb3d8bbwe
Package deployment result : 0x0
Deploying package: MicrosoftCorporationII.WinAppRuntime.Main.1.1_1000.516.2156.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
Deploying package: MicrosoftCorporationII.WinAppRuntime.Singleton_1000.516.2156.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
Deploying package: Microsoft.WinAppRuntime.DDLM.1000.516.2156.0-x6_1000.516.2156.0_x64__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
Deploying package: Microsoft.WinAppRuntime.DDLM.1000.516.2156.0-x8_1000.516.2156.0_x86__8wekyb3d8bbwe
Package deployment result : 0x0
Provisioning result : 0x0
All install operations successful.
Although none of the package FullNames included the sought-for version number 1002.543.1943, this was the result:
(get-appxpackage micro*win*appruntime*).packagefullname
Microsoft.WindowsAppRuntime.1.1_1002.543.1943.0_x64__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.1.1_1002.543.1943.0_x86__8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Main.1.1_1002.543.1943.0_x64__8wekyb3d8bbwe
Microsoft.WinAppRuntime.DDLM.1000.516.2156.0-x6_1000.516.2156.0_x64__8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Singleton_1002.543.1943.0_x64__8wekyb3d8bbwe
Microsoft.WinAppRuntime.DDLM.1000.516.2156.0-x8_1000.516.2156.0_x86__8wekyb3d8bbwe
All of the components are of the required version except for the DDLM components (note that if you do not run the installer as an administrator, you only get the 1002 version of the principal runtime components. The .Main* and .Singleton* will be _1000.516.2156).
The problem is, the programs are looking for that DDLM module and they both have an MSIX version number of 1000.516.2156.0 (although they also have a dependency on Microsoft.WindowsAppRuntime.1.1_1002.543.1943.0_x??__8wekyb3d8bbwe).
Does anyone know where I can get an MSIX for the 1002.543.1943.0_x?? DDLM component of the runtime? Or a runtime installer that contains all of the components with the required version number?
Thanks for any help.
As of today (2022-07-05), the download links on the official Microsoft page (Downloads for the Windows App SDK) contain all of the correct versions for the latest update (v1.1.2) to the Windows App Runtime.
Just a note: I removed all of my prior installations of the runtime from a PowerShell prompt before running WindowsAppRuntimeInstall.exe. Running (get-appxpackage micro*win*appruntime*).packagefullname reported no packages but trying to install the new runtime still gave me an error (package already installed but has different contents than the installed version). Although I am the only user of this machine, previous installs added the runtime to system accounts.
To see all installations, run (get-appxpackage micro*win*appruntime* -AllUsers).packagefullname from an elevated PowerShell prompt. Look for versions of the runtime with versions of 1002., DDLM.1001, and DDLM.1000. These may be the culprit as they were all in various versions of the runtime installer (v1.1.2) after it first dropped on July 1st. To remove them from all users, run Remove-AppxPackage -AllUsers -PackageName {package full name}. After removing versions that might have been in the "naughty" packages, try running the new WindowsAppRuntimeInstall.exe again. Everything should work.
What I have learned (thanks #aturnbul) is that to ensure a correct framework package update:
Close the WinUI 3 gallery and any other app using the framework.
Using the PowerShell commands listed by aturnbul remove all older packages
Run WindowsAppRuntimeInstall.exe from an elevated command prompt, so you can see any error that it may throw.
Back in PS you can verify that the installation was complete.
// After a failed installation you get only a partial list of packages
PS C:\Windows\system32> (get-appxpackage micro*win*appruntime* -AllUsers).packagefullname
Microsoft.WindowsAppRuntime.1.1_1004.584.2120.0_x86__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.1.1_1004.584.2120.0_x64__8wekyb3d8bbwe
// After a successful installation you get all the packages
PS C:\Windows\system32> (get-appxpackage micro*win*appruntime* -AllUsers).packagefullname
Microsoft.WindowsAppRuntime.1.1_1004.584.2120.0_x86__8wekyb3d8bbwe
Microsoft.WindowsAppRuntime.1.1_1004.584.2120.0_x64__8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Main.1.1_1004.584.2120.0_x64__8wekyb3d8bbwe
MicrosoftCorporationII.WinAppRuntime.Singleton_1004.584.2120.0_x64__8wekyb3d8bbwe
Microsoft.WinAppRuntime.DDLM.1004.584.2120.0-x6_1004.584.2120.0_x64__8wekyb3d8bbwe
Microsoft.WinAppRuntime.DDLM.1004.584.2120.0-x8_1004.584.2120.0_x86__8wekyb3d8bbwe
I'm trying to do some work for a client, but cannot get their bigcommerce site running locally. I have installed stencil CLI (v3.1.1) and downloaded the theme from the bigcommerce dashboard (all files). from the root of the theme i ran "stencil init", then "npm i" and "stencil start".
when i run stencil start, it throws an error saying there's no config.json file.
this is the error i get
How do i generate the config.json file?
The only config file I see is config.stencil.json.
I have also tried running "stencil pull" in hopes that it would pull the config, but it throws another error: "not ok -- Error: Could not fetch active theme details for channel 1: Request failed with status code 404"
Stencil-cli version:
3.1.1
Node version:
12
NPM version:
6.14.15
OS:
mac big sur
Stencil 3.1.1 has been deprecated for some time now. I believe the current version is 3.8. As of 4 months ago, anything below 3.5 will not run (https://developer.bigcommerce.com/changelog#publications/required-stencil-cli-version-set-to-3-5-0).
If you don't have a config.json file in your project, you will need to get the one from the client's store. Try downloading their theme again. It should come through.
Edit: It is possibly the case that you need a new API token. Try making a new one for your store. Make sure the following scopes are set:
Themes: Modify
Settings & Information: Modify
Sites & Routes: Read-only (or Modify)
Documentation for creating a new API account: https://support.bigcommerce.com/s/article/Store-API-Accounts#creating
I have a bundled application say XYZ-1.0.0.1.exe, with applications A-2.2.0.1.exe and B-1.2.0.1.exe bundled in it. So when we install XYZ, we get A and B as well listed in Add Remove Programs. But when I upgrade XYZ-1.0.0.1 with XYZ-1.0.0.2, which has A-2.2.0.1.exe and B-1.2.0.2.exe, so that A is same and already installed and B needs upgrade. I actually skipped the installation of A by making the install condition false, since the same version is already installed and installed only B while upgrading.
After successfully upgrading I am not able to uninstall the application XYZ, it says some package error, also this happens only if the source file used for upgrading is removed from machine.Actually while uninstalling package has to be referred from program cache, I think since we skipped A package cache has problem.
The error that i get is as follows "Prompt for source of container: WixAttachedContainer, path: C:\Users\ABC\Desktop\XYZ-1.0.0.2.exe Failed to resolve source for file: C:\Users\ABC\Desktop\XYZ-1.0.0.2.exe, error: 0x80070002. Error 0x80070002: Failed while prompting for source (original path 'C:\Users\ABC\Desktop\XYZ-1.0.0.2.exe'). Failed to acquire container: WixAttachedContainer to working path: C:\Users\ABC\AppData\Local\Temp{b4a1c780-306c-40f0-83ad7}, error: 0x80070002. "
This error occurs only when i copy XYZ.exe to any path say desktop and after installation(skip installing A or B since same version of A or B bundled is already installed) and delete the setup file XYZ.exe from saved path ie here Desktop. I am not able to uninstall unless i uninstall A or B which was skipped independently.
Also there is another scenario.
I have a bundled application say XYZ-1.0.0.1.exe, with applications A-2.2.0.1.exe and B-1.2.0.1.exe bundled in it. XYZ-1.0.0.2.exe, which has A-2.2.0.1.exe and B-1.2.0.2.exe. Thes in both versions of XYZ we have the same version of A. When i install XYZ-1.0.0.1.exe i skipped the installation of A-2.2.0.1.exe by setting the install condition to false. So XYZ-1.0.0.1.exe is installed and B-1.2.0.1 is also installed. Further when i upgraded to XYZ-1.0.0.2, I need to install all of the A and B. Installation was successfull and now i have XYZ-1.0.0.2, A-2.2.0.1 and B-1.2.0.2. Now if i delete the installation file of XYZ-1.0.0.2.exe from original path and try to uninstall it breaks.
Initially i thought that the package cache issue arises since A-2.2.0.1.exe was not installed along with XYZ-1.0.0.2.exe since i skipped it as it is already available. But after the second scenario got to know that skipping was not the issue. Since in second scenario A-2.2.0.1.exe was installed along with XYZ-1.0.0.2.exe.
The same issue took huge amount of my time as well. Solved it using a work around. Since the issue is "Prompt for source of container: WixAttachedContainer, path: ", You can copy the exe file XYZ-1.0.0.2 while upgrading to program data or some other path with a default name xyz.exe. At first register for ResolveSource event,then add the following code.Assume the copied exe path is c:/XYZ/xyz.exe
private void OnResolveSource(object sender, ResolveSourceEventArgs e)
{
Application.Engine.SetLocalSource(e.PackageOrContainerId, e.PayloadId, "c:/XYZ/xyz.exe");
e.Result = Result.Retry;
}
If anybody know a better answer, please help.
I'm following the instructions here: https://github.com/osTicket/core-plugins to install the LDAP plugin for osticket 1.9.2.
I have the download in the correct place however when I run the command:
php make.php hydrate
I get loads of 'could not load...' messages and the main fatal one being:
Problem 1
- The requested package pear-pear/net_ldap2 could not be found in any version, there may be a typo in the package name.
Enabling the plugin within osTicket then works but obvious throws PHP Fatal errors about not finding the ldap files, as you would expect.
Does anyone know how to resolve it?
You need to install the pear package net_ldap2, either via pear or via composer.
Its been almost 3 hours and I'm not able to build this. Please can anybody provide the steps. All the documents suggest to use hcatalog-src-0.5.0-incuvating.tar.gz but this is not available anywhere on internet (ad far as I've searched). Then I downloaded the branch 0.5.0 but as per the documentation
http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.2.0/ds_HCatalog/install.pdf
of version 0.5.0 you have to build l=using command
ant_home/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=forrest_home tar
Now the problem is that the build.xml do not have a target named 'tar'. So I just browsed the build.xml and tried the same command using target as 'package'
ant_home/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=forrest_home package
but then its showing me error.
BUILD FAILED
C:\Users\admnilesh\Desktop\hcatalog-branch-0.5\build.xml:71: The following error
occurred while executing this line:
C:\Users\nilesh\Desktop\hcatalog-branch-0.5\build-support\ant\deploy.xml:67:
Unable to resolve artifact: Unable to get dependency information: Unable to read
the metadata file for artifact 'com.sun.jersey:jersey-core:jar': Cannot find pa
rent: net.java:jvnet-parent for project: com.sun.jersey:jersey-project:pom:1.9.1
for project com.sun.jersey:jersey-project:pom:1.9.1
com.sun.jersey:jersey-core:jar:1.9.1
from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
central (http://repo1.maven.org/maven2),
glassfish-repository (http://maven.glassfish.org/content/groups/glassfish),
datanucleus (http://www.datanucleus.org/downloads/maven2)
Path to dependency:
1) org.apache.hcatalog:webhcat:jar:0.5.0-SNAPSHOT
Please help me out.
We've been having the same trouble and discussing it over at the hcatalog-user mailing list for the last couple of days. You can have a look at https://issues.apache.org/jira/browse/HCATALOG-601 to see what's being done about this problem.
Quick summary though : Jersey 1.9 depended on a glassfish maven repo, which no longer exists. Bump your jersey dep version from 1.9 to 1.14 and you should be able to build.
Edit : One more thing - we're still going through the release process to release the 0.5.0 incubating candidate, the latest candidates are being put up currently on http://people.apache.org/~travis/ . We should see a public release in a couple of days. In the meanwhile, I suggest poking over at our hcatalog-user mailing list : http://incubator.apache.org/hcatalog/mailing_lists.html
I got the same error while giving target "tar". On specifying the target as "package", the build proceeds ahead but fails with following error:
satish#dev1$ /usr/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=/home/satish/work/forrest/apache-forrest-0.9 package
[artifact:dependencies] Unable to resolve artifact: Missing:
[artifact:dependencies] ----------
[artifact:dependencies] 1) org.apache.hcatalog:hcatalog-core:jar:0.5.0
[artifact:dependencies]
[artifact:dependencies]
[artifact:dependencies] Path to dependency:
[artifact:dependencies] 1) org.apache.hcatalog:hcatalog-pig-adapter:jar:0.5.0- incubating
[artifact:dependencies] 2) org.apache.hcatalog:hcatalog-core:jar:0.5.0
[artifact:dependencies] ----------
This issue got resolved by specifying project.version as "0.5.0-incubating" instead of "0.5.0" in build command line. The reason for error is that build installs hcatalog-core artifact as hcatalog-core-0.5.0-incubating.jar. However because of wrong project.version, the dependent projects were instead searching for hcatalog-core-0.5.0.jar.
Build succeeded with:
satish#dev1$ /usr/bin/ant -Dhcatalog.version=0.5.0-incubating -Dforrest.home=/home/satish/work/forrest/apache-forrest-0.9 package