This never got added. Can it get added?

By the way this StackOverflow question I posted is related

<!-- If you don't follow the issue template, your issue may be closed. Please note this is an issue tracker, not a support forum. For general questions, please use StackOverflow or Slack. -->

Issue Description

What was unclear/insufficient/not covered in the documentation

The documentation on the force parameter of the sync method states

If force is true, each Model will run DROP TABLE IF EXISTS, before it tries to create its own table

I take that to mean that every table will be dropped and recreated every time this runs. I am doing this with an in-memory sqlite db in my tests and am seeing that this is not the case. While everything happens as expected on the first test run, on the second nothing is dropped nor created.

I understand that this isn't technically incorrect as it hinges on the definition of the word "sync". The documentation says this method does

Sync all defined models to the DB.

However, there is no further discussion that I'm able to find on what exactly the "sync" operation entails and as I was confused by this, I assume others are as well.

If possible: Provide some suggestion on how we can enhance the docs

1. More details on what exactly sync does. Is there metadata about the current state of the model or db stored somewhere and compared against?
2. As others like me might be coming to the force parameter with a similar use case (wanting to recreate the db entirely for tests every time), can you link to an FAQ o something on how to accomplish that? Even if its just a "here's how you truncate all tables instead", that would also work.

Issue Template Checklist

<!-- Please answer the questions below. If you don't, your issue may be closed. -->

Is this issue dialect-specific?

Yes and no. The core docs issue isn't dialect specific, the context within which this is most likely to be relevant is sqlite

Would you be willing to resolve this issue by submitting a Pull Request?

<!-- Remember that first contributors are welcome! -->

• [ ] Yes, I have the time and I know how to start.
• [ ] Yes, I have the time but I don't know how to start, I would need guidance.
• [X] No, I don't have the time, although I believe I could do it if I had the time...
• [ ] No, I don't have the time and I wouldn't even know how to start.

I love yall, and react router does good work, but damn if all internal links on react router's docs being broken due to a react router error isn't a very funny joke

On a fresh clone:

~/code/cli-lambda-deploy $ npm i
npm notice created a lockfile as package-lock.json. You should commit this file.
added 46 packages from 507 contributors and audited 46 packages in 2.365s
found 1 low severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details
~/code/cli-lambda-deploy $ npm test

> [email protected] test /Users/gmauer/code/cli-lambda-deploy
> mocha --timeout 100000 -S -R spec --exit



  new-function JSON config
Lambda config not found (./test/res/new-function-json-v14.lambda )

/Users/gmauer/code/cli-lambda-deploy/node_modules/mocha/lib/runner.js:726
  err.uncaught = true;
               ^

TypeError: Cannot create property 'uncaught' on string 'process exit code 255'
    at Runner.uncaught (/Users/gmauer/code/cli-lambda-deploy/node_modules/mocha/lib/runner.js:726:16)
    at process.uncaught (/Users/gmauer/code/cli-lambda-deploy/node_modules/mocha/lib/runner.js:839:10)
    at process.emit (events.js:314:20)
    at process._fatalException (internal/process/execution.js:163:25)
npm ERR! Test failed.  See above for more details.
~/code/cli-lambda-deploy $ 

I am using localstack - this means setting the aws endpoint-url config. Is that achievable with this package?

Would you be interested in a pull request if not?

I take it the activity means that this is a legitimate issue? Is there a workaround for the time being?

Tried a python lambda as well. The exact same code and the exact same uploading and invocation scripts against real aws work, against localstack generate

localstack_1  | 2020-09-11T03:16:42:INFO:localstack.services.awslambda.lambda_api: Error executing Lambda function arn:aws:lambda:us-east-1:000000000000:function:python_lambda: Lambda process returned error status code: 1. Result: {"errorType":"Runtime.ImportModuleError","errorMessage":"Unable to import module 'handler': No module named 'handler'"}. Output:

Do lambdas not work at all in localstack?

I just checked, the exact same zip file deployed to real aws in the exact same manner worked just fine. This definitely makes me think the issue is with localstack

Type of request: This is a ...

[x] bug report

And potentially a feature request for more documentation since its likelier I'm doing something wrong rather than there is a bug with something so simple.

Detailed description

I am trying to deploy a very simple lambda to localstack and then invoke it

My localstack is set up with the following compose service

  localstack:
    image: localstack/localstack-full:latest
    depends_on:
      - db
    ports:
      - "4563-4599:4563-4599"
      - "8055:8080"
    environment:
      - SERVICES=s3,sqs,sns,lambda
      - LAMBDA_EXECUTOR=docker
      - LAMBDA_REMOTE_DOCKER=false
      - DEBUG=1
      - DATA_DIR=/tmp/localstack/data
    volumes:
      - "./.localstack:/tmp/localstack"
      - "/var/run/docker.sock:/var/run/docker.sock"

I create a file index.js

     exports.handler = async (event) => {
       console.log(`Localstack lambda`, JSON.stringify(event))
       return {
         statusCode: 200,
         body: JSON.stringify(`yo yo, from localstack lambda`)
       }
     }

I zip it up

     zip loggingLambda.zip index.js

I then create the function

     aws lambda create-function \
         --endpoint http://localhost:4566 \
         --function-name loggingLambda \
         --runtime nodejs12.x \
         --role arn:aws:iam::000000000000:role/lambda-ex \
         --zip-file fileb://loggingLambda.zip \
         --handler index.handler

and try to invoke it

     aws lambda invoke \
         --endpoint http://localhost:4566 \
         --function-name loggingLambda \
         out \
         --log-type Tail

Expected behavior

I expected the lambda to return and log

Actual behavior

Unfortunately it does not

   {
       "StatusCode": 200,
       "FunctionError": "Unhandled",
       "LogResult": "",
       "ExecutedVersion": "$LATEST"
   }

What shows up in the localstack log indicates that the issue is index.handler is undefined or not exported but it is!

localstack_1  | 2020-09-10T20:31:44:WARNING:localstack.services.awslambda.lambda_executors: Empty event body specified for invocation of Lambda "arn:aws:lambda:us-east-1:000000000000:function:loggingLambda"
localstack_1  | 2020-09-10T20:31:44:INFO:localstack.services.awslambda.lambda_executors: Running lambda cmd: docker run -i  -v "/tmp/localstack/zipfile.c9303c10":/var/task -e DOCKER_LAMBDA_USE_STDIN="$DOCKER_LAMBDA_USE_STDIN" -e LOCALSTACK_HOSTNAME="$LOCALSTACK_HOSTNAME" -e _HANDLER="$_HANDLER" -e AWS_LAMBDA_FUNCTION_TIMEOUT="$AWS_LAMBDA_FUNCTION_TIMEOUT" -e AWS_LAMBDA_FUNCTION_NAME="$AWS_LAMBDA_FUNCTION_NAME" -e AWS_LAMBDA_FUNCTION_VERSION="$AWS_LAMBDA_FUNCTION_VERSION" -e AWS_LAMBDA_FUNCTION_INVOKED_ARN="$AWS_LAMBDA_FUNCTION_INVOKED_ARN" -e NODE_TLS_REJECT_UNAUTHORIZED="$NODE_TLS_REJECT_UNAUTHORIZED"  --rm "lambci/lambda:nodejs12.x" "index.handler"
localstack_1  | 2020-09-10T20:31:45:DEBUG:localstack.services.awslambda.lambda_executors: Lambda arn:aws:lambda:us-east-1:000000000000:function:loggingLambda result / log output:
localstack_1  | {"errorType":"Runtime.HandlerNotFound","errorMessage":"index.handler is undefined or not exported"}
localstack_1  | > 2020-09-10T20:31:45.203Z	undefined	ERROR	Uncaught Exception 	{"errorType":"Runtime.HandlerNotFound","errorMessage":"index.handler is undefined or not exported","stack":["Runtime.HandlerNotFound: index.handler is undefined or not exported","    at Object.module.exports.load (/var/runtime/UserFunction.js:144:11)","    at Object.<anonymous> (/var/runtime/index.js:43:30)","    at Module._compile (internal/modules/cjs/loader.js:1138:30)","    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)","    at Module.load (internal/modules/cjs/loader.js:986:32)","    at Function.Module._load (internal/modules/cjs/loader.js:879:14)","    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)","    at internal/main/run_main_module.js:17:47"]}
localstack_1  | > START RequestId: 1f202203-3539-18dc-febd-292a260d803f Version: $LATEST
localstack_1  | > END RequestId: 1f202203-3539-18dc-febd-292a260d803f
localstack_1  | > REPORT RequestId: 1f202203-3539-18dc-febd-292a260d803f	Init Duration: 122.47 ms	Duration: 2.52 ms	Billed Duration: 100 ms	Memory Size: 1536 MB	Max Memory Used: 40 MB	
localstack_1  | 2020-09-10T20:31:45:INFO:localstack.services.awslambda.lambda_api: Error executing Lambda function arn:aws:lambda:us-east-1:000000000000:function:loggingLambda: Lambda process returned error status code: 1. Result: {"errorType":"Runtime.HandlerNotFound","errorMessage":"index.handler is undefined or not exported"}. Output:
localstack_1  | 2020-09-10T20:31:45.203Z	undefined	ERROR	Uncaught Exception 	{"errorType":"Runtime.HandlerNotFound","errorMessage":"index.handler is undefined or not exported","stack":["Runtime.HandlerNotFound: index.handler is undefined or not exported","    at Object.module.exports.load (/var/runtime/UserFunction.js:144:11)","    at Object.<anonymous> (/var/runtime/index.js:43:30)","    at Module._compile (internal/modules/cjs/loader.js:1138:30)","    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)","    at Module.load (internal/modules/cjs/loader.js:986:32)","    at Function.Module._load (internal/modules/cjs/loader.js:879:14)","    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)","    at internal/main/run_main_module.js:17:47"]}
localstack_1  | START RequestId: 1f202203-3539-18dc-febd-292a260d803f Version: $LATEST
localstack_1  | END RequestId: 1f202203-3539-18dc-febd-292a260d803f
localstack_1  | REPORT RequestId: 1f202203-3539-18dc-febd-292a260d803f	Init Duration: 122.47 ms	Duration: 2.52 ms	Billed Duration: 100 ms	Memory Size: 1536 MB	Max Memory Used: 40 MB	 Traceback (most recent call last):
localstack_1  |   File "/opt/code/localstack/localstack/services/awslambda/lambda_api.py", line 529, in run_lambda
localstack_1  |     result = LAMBDA_EXECUTOR.execute(func_arn, func_details, event, context=context,
localstack_1  |   File "/opt/code/localstack/localstack/services/awslambda/lambda_executors.py", line 166, in execute
localstack_1  |     return do_execute()
localstack_1  |   File "/opt/code/localstack/localstack/services/awslambda/lambda_executors.py", line 158, in do_execute
localstack_1  |     return _run(func_arn=func_arn)
localstack_1  |   File "/opt/code/localstack/localstack/utils/cloudwatch/cloudwatch_util.py", line 146, in wrapped
localstack_1  |     raise e
localstack_1  |   File "/opt/code/localstack/localstack/utils/cloudwatch/cloudwatch_util.py", line 142, in wrapped
localstack_1  |     result = func(*args, **kwargs)
localstack_1  |   File "/opt/code/localstack/localstack/services/awslambda/lambda_executors.py", line 151, in _run
localstack_1  |     raise e
localstack_1  |   File "/opt/code/localstack/localstack/services/awslambda/lambda_executors.py", line 139, in _run
localstack_1  |     result = self._execute(func_arn, func_details, event, context, version)
localstack_1  |   File "/opt/code/localstack/localstack/services/awslambda/lambda_executors.py", line 296, in _execute
localstack_1  |     result = self.run_lambda_executor(cmd, stdin, env_vars=environment, func_details=func_details)
localstack_1  |   File "/opt/code/localstack/localstack/services/awslambda/lambda_executors.py", line 203, in run_lambda_executor
localstack_1  |     raise Exception('Lambda process returned error status code: %s. Result: %s. Output:\n%s' %
localstack_1  | Exception: Lambda process returned error status code: 1. Result: {"errorType":"Runtime.HandlerNotFound","errorMessage":"index.handler is undefined or not exported"}. Output:
localstack_1  | 2020-09-10T20:31:45.203Z	undefined	ERROR	Uncaught Exception 	{"errorType":"Runtime.HandlerNotFound","errorMessage":"index.handler is undefined or not exported","stack":["Runtime.HandlerNotFound: index.handler is undefined or not exported","    at Object.module.exports.load (/var/runtime/UserFunction.js:144:11)","    at Object.<anonymous> (/var/runtime/index.js:43:30)","    at Module._compile (internal/modules/cjs/loader.js:1138:30)","    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10)","    at Module.load (internal/modules/cjs/loader.js:986:32)","    at Function.Module._load (internal/modules/cjs/loader.js:879:14)","    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)","    at internal/main/run_main_module.js:17:47"]}
localstack_1  | START RequestId: 1f202203-3539-18dc-febd-292a260d803f Version: $LATEST
localstack_1  | END RequestId: 1f202203-3539-18dc-febd-292a260d803f
localstack_1  | REPORT RequestId: 1f202203-3539-18dc-febd-292a260d803f	Init Duration: 122.47 ms	Duration: 2.52 ms	Billed Duration: 100 ms	Memory Size: 1536 MB	Max Memory Used: 40 MB	
localstack_1  | 

Ok, thanks, that managed to get me to a useful place.

I renamed the file to handler.js and the zip to handler.zip

Then it had to be --handler handler.handler

but I got back the expected response

Type of request: This is a ...

[ ] bug report [x ] feature request

But specifically for the documentation

Detailed description

So disclaimer in that all of AWS is new to me but I can't be the only person in this boat.

I'm having trouble figuring out from the documentation and other writing available online how I am supposed to create a lambda function.

I have a very simple lambda

     exports.handler = async (event) => {
       console.log(`Localstack lambda`, JSON.stringify(event))
       return {
         statusCode: 200,
         body: JSON.stringify(`yo yo, from localstack lambda`)
       }
     }

which I zip

     zip logging-lambda.zip logging-lambda.js

and then try to deploy

     aws lambda create-function \
         --endpoint http://localhost:4566 \
         --function-name loggingLambda \
         --runtime nodejs12.x \
         --role arn:aws:iam::000000000000:role/lambda-ex \
         --zip-file fileb://logging-lambda.zip \
         --handler index.handler

only to get the error

An error occurred (ValidationError) when calling the CreateFunction operation: Unable to find handler script (/tmp/localstack/zipfile.38f20074/index.js) in Lambda archive. Config for local mount, docker, remote: "False", "False", "False"

My docker container has the following environment variables set

      - SERVICES=s3,sqs,sns,lambda
      - LAMBDA_EXECUTOR=local
      - LAMBDA_REMOTE_DOCKER=false
      - DEBUG=1
      - DATA_DIR=/tmp/localstack/data

As best as I can read the docs I'm doing everything right, but clearly that's not the case and everything I can find online is all about using IDEs to upload (I'm in the command line)

Can we get some more info on what the recommended process for getting a lambda into localstack is top to bottom?

Specifically, I would like the ability to use this to sub out dynamically scoped variables in unit tests. Yet unit tests don't actually run when they are defined - I would need some way to setup a binding in a beforeEach and release it in an afterEach

What do you think? Take a PR for it?

If we're going to make a game, we need a builder to help us make levels. It's going to take forever otherwise

Thank you. I really appreciate the project and do plan to get more involved at some point

On Sat, Aug 8, 2020, 17:17 Leo Vivier [email protected] wrote:

I can reproduce this, and it's trivial to fix. I'll address this tomorrow.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/org-roam/org-roam/issues/1013#issuecomment-670979592, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQEZVQTR2JONBHGPACHETR7XFG3ANCNFSM4PY2LTOQ .

If my note is titled "Racket", in order to navigate to it with org-find-file I type "Racket" (or some part of that and select from helm of course). However, in the above scenario let's say I'm narrowed to the "Macros" sub heading. Searching "Racket" will not find it as it appears under "Macros"

On Sat, Aug 8, 2020, 15:55 Leo Vivier [email protected] wrote:

I'm not sure if I understand your point. If you mean that the title of the note is replaced by the heading to which you're narrowed in the completion-list for org-roam-find-file, it's not the case on my end, and I don't see anything in the codebase that would cause it.

If you mean that org-roam-find-file brings you to the narrowed buffer of the note, it's expected. We could force the buffer to be widened upon access, but that'd be going out of our way to fix a non-existing problem. org-roam-find-file and org-roam-switch-to-buffer are meant to make you jump quickly between your notes, and if you narrowed one of them, chances are you had a good reason for doing so in the first place. If you want to work on a narrowed version of a note, but want to preserve the original buffer when finding the file, consider using org-tree-to-indirect-buffer.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/org-roam/org-roam/issues/1013#issuecomment-670972968, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQEZQFQSXCN66VTDCP3XLR7W3U5ANCNFSM4PY2LTOQ .

Example

1. Create a note with a series of subheadings. For example I have one for Racket and subheadings Beautiful Racket, Fear of Macros, and Playground. Save it.
2. Flip to another buffer, do org-roam-find-file to find your note under its note title
3. Narrow the buffer to just one subheader.
4. Add some text, save your note.
5. Flip to another buffer
6. Ty to org-roam-find-file again. Note that it doesn't appear under its title! It appears under the subheading title

Expected Results

I would expect the note to always appear under the title of the note not of the heading I have things narrowed to. Worse this isn't even consistent. If you widen after saving (and before saving again) it will still appear under the subheading.

Environment

• Emacs: GNU Emacs 26.3 (build 1, x86_64-apple-darwin18.2.0, NS appkit-1671.20 Version 10.14.3 (Build 18D109)) of 2019-09-02
• Framework: Spacemacs
• Org: Org mode version 9.3.7 (9.3.7-15-gc9abb4-elpaplus @ /Users/gmauer/.emacs.d/elpa/develop/org-plus-contrib-20200727/)
• Org-roam: 1.2.1

Updated this PR once more - there is not really a point to having different value and output modes, both work just fine with top level define instead of a let. Instead did some cleanup on how the body gets expanded so that you can use custom #lang directives

See this thread for background

Slack channels can only have 100 pins. But we pin all problems in the #daily-programmer channel. @kevinkiklee has to manage these manually.

Create a bot that when it runs

1. Unpins the 100th pinned post in #daily-programmer (if there is one)
2. Adds a link to it along with its title (there's a standard format we use if you look at them) to some "Operation Code Daily Programmers" list somewhere online - may be a github pages repo, a wiki, or a web page

• Don't do that if this post is already linked
• We would want to do an initial scan through all posts in the channel and see if we can auto-detect them and put them up there.

As many daily programmers come from places like Hacker Rank and Leetcode, we don't want to post the problem itself outside of slack - that would violate copyright, just link to the post.