I was trying to update the serverless version for my project from 2.72 to 3.x. Hence I started working on the resolution of the deprecations warnings. All are gone except of the following.
Cannot resolve variable at "resources.Resources.ApiGatewayAcessLogsSubscriptionFilter.Properties.DestinationArn": String value consist of variable which resolve with non-string value
The variable inside the serverless.yml is referenced as follow
{self:custom.localEnvironment.logs-destination.${self:provider.region}}
The custom section of the serverless.yml is defined as follow:
custom:
localEnvironment:
logs-destination:
region-x: "**** destination log group"
Environment Information
Your Environment Information ---------------------------
Operating System: darwin
Node Version: 14.20.0
Framework Version: 2.72.3 (local)
Plugin Version: 5.5.4
SDK Version: 4.3.2
Components Version: 3.18.2
Note env says version is 2.72.3 but to enforce the new name resolver I am using the following in the file
variablesResolutionMode: 20210326
I looked for various resources on the serverless forums, didn't find something which match exactly with my situation. Though I have found the following un-answered question
https://forum.serverless.com/t/variables-resolution-errored/16999
P.S. New to the community please feel free to edit the question.
Related
I installed Phalcon PHP as described in https://docs.phalcon.io/3.4/en/webserver-wamp.
In this case the URL reads 3.4 because it applies alike for versions 4 and 5.
The WAMP server version is 3.2.6 configured with PHP 8.0.13
Everything was fine so far, so I continued installing the developer tools using composer as described in https://docs.phalcon.io/5.0/en/devtools.
Composer was installed globally and so were the developer tools, but when I type "phalcon" in the command window, the following error is shown:
C:\>phalcon
Fatal error: Uncaught Error: Class "Phalcon\Script" not found in C:\Users\Joachim\AppData\Roaming\Composer\vendor\phalcon\devtools\phalcon.php:38
Stack trace:
#0 {main}
thrown in C:\Users\Joachim\AppData\Roaming\Composer\vendor\phalcon\devtools\phalcon.php on line 38
C:\>
PSR and Phalcon extensions were successfully installed and I can see them in the WAMP Localhost page.
The Path environment variable contains the path to phalcon, composer, wamp, etc, nothing is missing as far as I can see.
Have anyone dealt with this error?
What could be the problem?
I'm a bit late answering this, but in case anyone else stumbles across it via Google the problem is that some namespaces have been altered between Phalcon4 and Phalcon5. I believe Phalcon\Config is one of those classes.
Until the devtools have been updated for Phalcon5, you'll either need to build the scaffolding manually, or copy an old Phalcon 3 or 4 project and update the namespaces.
The perils of using alpha/beta releases, unfortunately.
you didn't mention which phalcon version but since you are using php 8 the only version supporting php 8 is phalcon 5
your issue is most likely in your php.ini for the cli since wamp uses different files for apache and cli.
to fix the issue first remove the devtools package you installed globally then edit the cli php.ini in [wampDir]\bin\php\php8.0.13\php.ini and include psr and phalcon and install the devtools again using composer
you can also download the phar file here and test it in the cli
php phalcon.phar
Error: You might be seeing this error because you're using the wrong Compose file version. Either specify a supported version (e.g
"2.2" or "3.3") and place your service definitions under the
services key, or omit the version key and place your service
definitions at the root of the file to use version 1. For more on the
Compose file format versions, see
https://docs.docker.com/compose/compose-file/
Yaml:
You have a typo in the first line. Probably it should start with version: 3.3 link.
I was trying to deploy code on lambda using serverless deploy and got below error, tried multiple solutions available online but didn't work.
Error -
Serverless: Packaging service...
Serverless Error ---------------------------------------
The specified bucket does not exist
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com
Your Environment Information -----------------------------
OS: darwin
Node Version: 8.12.0
Serverless Version: 1.31.0
When you are deploying your Serverless application it uses the service attribute (defined in your serverless.yaml) as a unique identifier of your application in the CloudFormation.
Said so, you may have some conflict if you change the name of the bucket without removing the stack. Ex:
You deploy you application with the bucket called myBucket.
CloudFormation will be created considering this info.
You change this name to myBucketPlus and try to deploy.
Serverless will clean the mybucketPlus with the last deploy before pushing the new one.
But wait! myBucketPlus does not exist.
As you did not describe what exactly you did, I tried to give an example but it could be something else.
Also you could try removing and deploying again.
The best way to resolve this issue is -
Execute below command to see the lambda information which will also provide the S3 bucket name, region, endpoint info etc but you need only bucket name and region for this case.
sls info -v
Create the bucket in the intended region.
Done.
I just installed Dart version 2.0.0-dev.64.1 and when running tests in WebStorm using the Dart VM I get the error:
Snapshot not compatible with the current VM configuration: the snapshot requires 'release no-strong no-type_checks no-asserts no-error_on_bad_type no-error_on_bad_override no-sync_async no-reify_generic_functio' but the VM has 'release strong no-type_checks no-asserts no-error_on_bad_type no-error_on_bad_override sync_async reify_generic_functions use_field_guards use_osr x64-win'
Isolate creation failed
I did not have this problem with V2.0.0-dev.63.0.
Any suggestions for fixing this?
My guess is that Webstorm is running run the pub snapshot from the SDK at bin/snapshots/pub.dart.snapshot however it doesn't seem to run with the default configuration of the VM in this build (there's a pub2.dart.snapshot in the same folder which does work).
Based on this comment this is a temporary issue because this version ships Dart2-enabled VM but the pub snapshot is not v2. Sounds like the next dev version will correct this.
So for now your best bet is to roll back to an earlier dev build, and then try again when the next one is available.
I am trying to deploy an application to Google AppEngine using the beta deploy command: gcloud beta app deploy app.yaml and I have even tried to add: --verbosity=info to get more information.
Nevertheless I keep getting this error:
Failed parsing input: parser: bad import "unsafe" in golang.org/x/sys/unix/dirent.go
From what I can tell the error does not come from my code and the only external libraries I use is
gorilla/mux
sirupsen/logrus
Which from what I can tell also do not use any unsafe code. My local go version is go version go1.8.3 linux/amd64 and I am using a standard environment on Google AppEngine.
Furthermore, locally the code runs as it should.
Any ideas on what might be wrong?
The github.com/sirupsen/logrus package is using the golang.org/x/sys/unix package.
See: https://github.com/sirupsen/logrus/search?q=unix&type=Code
You can't use on Google AppEngine standard any package that uses unsafe or imports other package that use it.