Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Helmut Kian Rohrbacher
    @helmutkian
    Ah adding serverless-plugin-typescript to my plugins resolved the issue
    dl748
    @dl748
    if you use serverless-plugin-typescript then webpack isn't needed
    bregard
    @bregard
      Error --------------------------------------------------
    
      Error: Cannot find module 'serverless-offline/src/functionHelper'
      Require stack:
      - /Users/bregard/cartoon-play-api/source/nodejs/.serverless_plugins/plugin-local-invoke.js
      - /usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/lib/classes/PluginManager.js
      - /usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/lib/Serverless.js
      - /usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/scripts/serverless.js
      - /usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/bin/serverless.js
          at Function.Module._resolveFilename (internal/modules/cjs/loader.js:957:15)
          at Function.Module._load (internal/modules/cjs/loader.js:840:27)
          at Module.require (internal/modules/cjs/loader.js:1019:19)
          at require (internal/modules/cjs/helpers.js:77:18)
          at Object.<anonymous> (/Users/bregard/cartoon-play-api/source/nodejs/.serverless_plugins/plugin-local-invoke.js:3:26)
          at Module._compile (internal/modules/cjs/loader.js:1133:30)
          at Object.Module._extensions..js (internal/modules/cjs/loader.js:1153:10)
          at Module.load (internal/modules/cjs/loader.js:977:32)
          at Function.Module._load (internal/modules/cjs/loader.js:877:14)
          at Module.require (internal/modules/cjs/loader.js:1019:19)
          at require (internal/modules/cjs/helpers.js:77:18)
          at requireServicePlugin (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/lib/classes/PluginManager.js:21:14)
          at /usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/lib/classes/PluginManager.js:133:20
          at Array.map (<anonymous>)
          at PluginManager.resolveServicePlugins (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/lib/classes/PluginManager.js:130:8)
          at PluginManager.loadAllPlugins (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/lib/classes/PluginManager.js:117:15)
          at /usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/lib/Serverless.js:101:35
          at tryCatcher (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/util.js:16:23)
          at Promise._settlePromiseFromHandler (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:547:31)
          at Promise._settlePromise (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:604:18)
          at Promise._settlePromise0 (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:649:10)
          at Promise._settlePromises (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:729:18)
          at Promise._fulfill (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:673:18)
          at Promise._settlePromise (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:617:21)
          at Promise._settlePromise0 (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:649:10)
          at Promise._settlePromises (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:729:18)
          at Promise._fulfill (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:673:18)
          at Promise._resolveCallback (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:466:57)
          at Promise._settlePromiseFromHandler (/usr/local/Cellar/serverless/1.78.1/libexec/lib/node_modules/serverless/node_modules/bluebird/js/release/promise.js:559:17)
          at Promise._settlePromise (/usr/local/Cellar/server
    Just running serverless --version in my project... any ideas?
    version 6.5.0 of serverless-offline...
    John Noel Victorino
    @jnoelvictorino
    Hello, I have a question about accessing data from a Lambda Function (only without API Gateway) and Lambda Function (behind API Gateway). When I tried to access the JSON payload from behind an API Gateway, I can access it as event.body. But without an API Gateway (directly via Lambda), I can access the JSON payload as event. Would there be a way to access JSON payload as event.body only?
    Kevin Menhinick
    @kevbot-git
    Hi team, does anyone have any tips for contributing to serverless offline? I'm trying to make a test project use my locally-cloned serverless-offline but can't seem to get it to use my builds of it
    If anyone can take me through it I'd be happy to document the process in the Contributing section of the README
    Kevin Menhinick
    @kevbot-git
    Sorry, just found the file that tells me all about that :sweat_smile:
    Kevin Menhinick
    @kevbot-git
    If anyone does get a sec to checkout my small PR, would anyone recommend a way to test what I've changed? I'm struggling to figure out the tests dherault/serverless-offline#1064
    Kamil Dybicz
    @kdybicz
    Hey all! Quick question about an issue raised in dherault/serverless-offline#832 It looks like changes merged as a fix there were at some point reverted https://github.com/dherault/serverless-offline/blob/master/src/ServerlessOffline.js#L269 and it's no longer enough to set private: true on http events to make serverless-offline to generate an print out the x-api-key anymore. Was that done on purpose and I'm just missing something or it's a regression that I can help to patch up?
    Kamil Dybicz
    @kdybicz
    kwongkz
    @kwongkz
    Wanna ask is it serverless-offline after v6 no longer send X-Forwarded-Proto in Lambda-Proxy event request headers?
    David Hérault
    @dherault
    @kwongkz if so please open an issue :)
    @kdybicz merged thanks!
    Kamil Dybicz
    @kdybicz
    :+1:
    Matthew Kelch
    @kelchm
    Has anyone dug into #1080, #1081, #1083? These all seem to be related to changes in #1050
    Matthew Kelch
    @kelchm
    FYI, shared some of the results of my testing with v6.7.0 here: https://github.com/dherault/serverless-offline/issues/931#issuecomment-687234909
    Matthew Kelch
    @kelchm
    I've created a PR to try to address the above: dherault/serverless-offline#1090
    David Hérault
    @dherault
    Thanks @kelchm
    Dustin Goodman
    @dustinsgoodman
    image.png
    Hey @dherault, I upgraded to version 6.7.0 earlier today and am seeing the above anytime I run a function against my lambda. It's specific to version 6.7.0 as 6.6.0 is working fine. Trying to figure out more info for you still but wanted to toss this in here in case it's a known issue.
    Dustin Goodman
    @dustinsgoodman
    Looks like invocationRoute.js changed to return an async function but didn't properly fix the key-value mapping on the return object and might not be handling the await downstream. See https://github.com/dherault/serverless-offline/compare/v6.7.0...master#diff-c23f5dac27510ddbb5b7b60780e7571dR12
    Going to open a Github issue with the above for you to get to later.
    Dustin Goodman
    @dustinsgoodman
    David Hérault
    @dherault
    Guys I'm so sorry I did not see that comming. On it
    Dustin Goodman
    @dustinsgoodman
    No worries! Thank you :)
    David Hérault
    @dherault
    Does it crash the same way using v6.8.0?
    Dustin Goodman
    @dustinsgoodman
    Pulling it down now to test.
    All better in v6.8.0! :D
    Closed the above issue with the notes regarding resolution. Thanks for the fix!
    tan-t
    @tan-t

    hi!
    I'm using serverless-offline 6.5.0 in my project, and want to test my functions which don't have an HTTP events with invocation endpoint (via aws-cli).
    I remember when it was 5.10.0, the serverless-offline plugin just gave me invocation endpoint for all the functions like below:

    ...
    Serverless: Routes for helloworld:
    Serverless: POST /{apiVersion}/functions/myservice-dev-helloworld/invocations
    ...

    but with 6.5.0, it seems that the plugin isn't giving invocation endpoints unless the function has an HTTP event.
    I don't find any breaking changes or migration guides related to this in v6,
    but when I downgraded my serverless-offline to 5.10.0, it started to create endpoints, so I think it is a version problem.

    does anyone know how to make it create invocation endpoint for all the functions with serverless-offline v6?

    tan-t
    @tan-t
    sorry I've mistakenly thought that the plugin is not making endpoints but it turns out that it is making them silently. with SLS_DEBUG=* , I can see invocation endpoints and they are working nicely actually.
    David Hérault
    @dherault
    :thumbsup:
    Ross Coundon
    @rcoundon

    I have a serverless.yml with a collection of lambdas. There are currently some API Gateway triggered lambdas and one that is SQS triggered.
    The environment is set at the provider level.

    I'm running this using serverless-offline and for SQS I'm using the serverless-offline-sqs-esmq plugin.

    The peculiar thing is, for the API Gateway triggered lambdas, all the process.env values are set correctly. However, when the SQS triggered lambda runs, none of the environment variables set in serverless.yml are available. Serverless is setting something as I can see that the IS_OFFLINE property is set, just none of my own specified ones.

    There is no difference in config other than the event source for the two different types. I've also tried specifying the environment at the function level but this makes no difference.

    Has anyone seen this or know what it could be?

    Thanks

    Gurkiran Singh
    @Gurkiran-Singh

    Hi,
    I am new to Serverless.
    I just want to know if there is any way around that we can create s3 buckets using serverless if else plugin.

    What I am trying to achieve is that I want to create new s3 buckets as per Stage I gave in if else statement.

    Fr example if script(serverless.yml) runs in production stage it should create different s3 bucket and if script runs in development stage then it should create different bucket according to if else statement.

    Please let me know if there is any way around to achieve this.

    Vishesh M
    @visheshCuriousDev
    Hi guys !! Is there no hot reload for serverless offline ?
    I run "SLS_DEBUG=* sls offline start". It run in debug mode but any changes made to any of the handler files, it does not reload !!! Any idea ?
    Jack Fazackerley
    @JackFazackerley

    Hi I'm running serverless-offline v6.8.0, serverless v2.16.1, Go v1.15.5 and for some reason i can only GET, any time i POST it's as if serverless-offline is blocking me? The connection just hangs and there are no lo gs. The command i'm running is: `SLS_DEBUG=* sls --verbose offline start --useDocker. My serverless file looks like:

    service: example
    
    frameworkVersion: '2'
    
    plugins:
      - serverless-offline
    
    provider:
      name: aws
      runtime: go1.x
      stage: ${self:custom.stage}
      region: ${self:custom.region}
    
    custom:
      stage: ${opt:stage, 'develop'}
      region: ${file(env.yml):regions.${self:custom.stage}}
    
    package:
      individually: true
      exclude:
        - ./**
    
    functions:
      api:
        runtime: go1.x
        handler: bin/api
        events:
          - http:
              cors:
                origin: '*'
              path: api
              method: any
        package:
          include:
            - bin/api
        environment: ${file(env.yml):environment.example}.

    I'm unsure if i'm doing anything wrong or it's the versions?

    Ahmed Bayoumy
    @bayoumymac
    Hello, I have been running into this weird error on the second request after running sls offline start
    node[91757]: ../src/env-inl.h:1036:void node::Environment::AddCleanupHook(void (*)(void *), void *): Assertion `(insertion_info.second) == (true)' failed.
     1: 0x10009ce91 node::Abort() [/usr/local/bin/node]
     2: 0x10009cd1a node::AppendExceptionLine(node::Environment*, v8::Local<v8::Value>, v8::Local<v8::Message>, node::ErrorHandlingMode) [/usr/local/bin/node]
     3: 0x10001f6be node::Environment::AddCleanupHook(void (*)(void*), void*) [/usr/local/bin/node]
     4: 0x100008b00 node::AddEnvironmentCleanupHook(v8::Isolate*, void (*)(void*), void*) [/usr/local/bin/node]
     5: 0x107903206 WrappedRE2::Init() [/Users/Test/Documents/instagram-bot/serverless/node_modules/re2/build/Release/re2.node]
     6: 0x107903f23 node_register_module_v88 [/Users/Test/Documents/instagram-bot/serverless/node_modules/re2/build/Release/re2.node]
     7: 0x10007bf86 std::__1::__function::__func<node::binding::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&)::$_0, std::__1::allocator<node::binding::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&)::$_0>, bool (node::binding::DLib*)>::operator()(node::binding::DLib*&&) [/usr/local/bin/node]
     8: 0x10007ada9 node::binding::DLOpen(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
     9: 0x10021da46 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/usr/local/bin/node]
    10: 0x10021d0c9 v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node]
    11: 0x10021c8b0 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
    12: 0x1007fd979 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit [/usr/local/bin/node]
    Abort trap: 6
    that only occurs on the second request, the first request goes through just fine
    cdmpicker
    @cdmpicker
    anyone got serverless offline working with rollup?
    Zhani Baramidze
    @jbaramidze
    hi!,
    I've installed serverless offline plugin, all works good, port 3000 got exposed and handles fine, but for some reason it does not seem to expose 3002 to do Lambda invocations by hand. shouldn't it start working automatically?
    Andy Swanson
    @awswanson

    Hello, I have been running into this weird error on the second request after running sls offline start

    @bayoumymac Were you able to resolve this issue? The exact same thing is happening to me.

    Jack Howard
    @JackHowa
    is there a good way of mocking alb? I'm seeing urls that aren't matching what I would expect running serverless-offline?
    [offline] Lambda Invocation Routes (for AWS SDK or AWS CLI):
               * POST http://localhost:3002/2015-03-31/functions/x-api-sandbox-getBundles/invocations
    Jack Howard
    @JackHowa
    ^ this is related to issue dherault/serverless-offline#598 if any one is working on this. I saw someone try to bounty it I think
    Jack Howard
    @JackHowa
    also is there a way to specify a different serverless.yml file to run? I haven't been able to find the equivalent of --config equivalent to serverless. thanks for your help!
    looks like it's being tracked here by dherault/serverless-offline#1146
    Rafael Franco
    @rfoel
    How about releasing the support for nodejs14.x?