Native Gems from darwin do not work

Checklist

[ ] Upgrade Jets: Are you using the latest version of Jets? This allows Jets to fix issues fast. There's a jets upgrade command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/
[x] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on https://community.rubyonjets.com
[ ] Code sample: Have you put together a code sample to reproduce the issue and make it available?  Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.

My Environment

Software
Version

Operating System
OS X 11.0.1

Jets
2.3.17

Ruby
2.5.8

I deploy directly from my machine
Expected Behaviour
Lambda functions do not crash at startup
Current Behavior
All lambda functions crash at startup
Step-by-step reproduction instructions

Include nokogiri in your Gemfile
bundle update nokogiri
jets deploy from os x
jets call any function

{
  "errorMessage": "Could not find nokogiri-1.11.0 in any of the sources",
  "errorType": "Init<Bundler::GemNotFound>",
  "stackTrace": [
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `map!'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in `specs_for'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in `requested_specs'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in `block in definition_method'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in `setup'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler.rb:149:in `setup'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in `block in <top (required)>'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in `with_level'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in `silence'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in `<top (required)>'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:92:in `require'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:92:in `require'",
    "/var/task/handlers/controllers/kyc_controller.rb:1:in `<top (required)>'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:72:in `require'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:72:in `require'"
  ]
}

Solution Suggestion
Looking at the gem layer, two things stood out to me: the gem directory name included darwin and there was no nokogiri in the extensions directory.
$ find prod-api-services-gems-4798ad2d-0411-4225-b627-95b881850be0 -type directory -name '*nokogiri*'
prod-api-services-gems-4798ad2d-0411-4225-b627-95b881850be0/ruby/gems/2.5.0/gems/nokogiri-1.11.0-x86_64-darwin
prod-api-services-gems-4798ad2d-0411-4225-b627-95b881850be0/ruby/gems/2.5.0/gems/nokogiri-1.11.0-x86_64-darwin/ext/nokogiri
prod-api-services-gems-4798ad2d-0411-4225-b627-95b881850be0/ruby/gems/2.5.0/gems/nokogiri-1.11.0-x86_64-darwin/lib/nokogiri

I tried to force the use of compiled gems (via bundle config set force_ruby_platform true).  This fixed the gem directory but added the wrong platform for the extensions:
$ find prod-api-services-gems-81a44894-60e9-455d-9863-b123823bce84 -type directory -name '*nokogiri*'
prod-api-services-gems-81a44894-60e9-455d-9863-b123823bce84/ruby/gems/2.5.0/extensions/x86_64-darwin-19/2.5.0/nokogiri-1.11.1
prod-api-services-gems-81a44894-60e9-455d-9863-b123823bce84/ruby/gems/2.5.0/extensions/x86_64-darwin-19/2.5.0/nokogiri-1.11.1/nokogiri
prod-api-services-gems-81a44894-60e9-455d-9863-b123823bce84/ruby/gems/2.5.0/gems/nokogiri-1.11.1
prod-api-services-gems-81a44894-60e9-455d-9863-b123823bce84/ruby/gems/2.5.0/gems/nokogiri-1.11.1/ext/nokogiri
prod-api-services-gems-81a44894-60e9-455d-9863-b123823bce84/ruby/gems/2.5.0/gems/nokogiri-1.11.1/lib/nokogiri

I had to downgrade nokogiri to 1.10.x

I see that 3.0.0 just dropped.  I can try upgrading.

I see that 3.0.0 just dropped.  I can try upgrading.

Same problem occurred to me with Jets 3.0.0.
I have fixed it adding version lock for nokogiri.
# Gemfile
gem 'nokogiri', '~> 1.10.0'

Same problem occurred to me with Jets 3.0.0.
I have fixed it adding version lock for nokogiri.
# Gemfile
gem 'nokogiri', '~> 1.10.0'

@ryz310 Unsure what's going on there 🧐 Just tested it and was able to use the latest version of nokogiri.
Here's a simple test controller:
require 'open-uri'

class NokogiriController < ApplicationController
  def index
    # Fetch and parse HTML document
    doc = Nokogiri::HTML(URI.open('https://nokogiri.org/tutorials/installing_nokogiri.html'))

    # Search for nodes by css
    content = nil
    doc.css('nav ul.menu li a', 'article h2').each do |link|
      content = link.content
    end

    render json: {
      content: content,
      nokogiri_version: Nokogiri::VERSION,
      jets_version: Jets::VERSION,
      ruby_version: RUBY_VERSION,
    }
  end
end

Here's the debugging output from the Jets app on AWS Lambda.
$ curl https://ykmipzptqc.execute-api.us-west-2.amazonaws.com/dev/ ; echo
{"content":"Appendix A: The Compiler Toolchain¶","nokogiri_version":"1.11.1","jets_version":"3.0.0","ruby_version":"2.7.2"}
$ curl -s https://ykmipzptqc.execute-api.us-west-2.amazonaws.com/dev/ | jq
{
  "content": "Appendix A: The Compiler Toolchain¶",
  "nokogiri_version": "1.11.1",
  "jets_version": "3.0.0",
  "ruby_version": "2.7.2"
}
$

Code is also here: https://github.com/tongueroo/jets-nokogiri-demo

@ryz310 Unsure what's going on there 🧐 Just tested it and was able to use the latest version of nokogiri.
Here's a simple test controller:
require 'open-uri'

class NokogiriController < ApplicationController
  def index
    # Fetch and parse HTML document
    doc = Nokogiri::HTML(URI.open('https://nokogiri.org/tutorials/installing_nokogiri.html'))

    # Search for nodes by css
    content = nil
    doc.css('nav ul.menu li a', 'article h2').each do |link|
      content = link.content
    end

    render json: {
      content: content,
      nokogiri_version: Nokogiri::VERSION,
      jets_version: Jets::VERSION,
      ruby_version: RUBY_VERSION,
    }
  end
end

Here's the debugging output from the Jets app on AWS Lambda.
$ curl https://ykmipzptqc.execute-api.us-west-2.amazonaws.com/dev/ ; echo
{"content":"Appendix A: The Compiler Toolchain¶","nokogiri_version":"1.11.1","jets_version":"3.0.0","ruby_version":"2.7.2"}
$ curl -s https://ykmipzptqc.execute-api.us-west-2.amazonaws.com/dev/ | jq
{
  "content": "Appendix A: The Compiler Toolchain¶",
  "nokogiri_version": "1.11.1",
  "jets_version": "3.0.0",
  "ruby_version": "2.7.2"
}
$

Code is also here: https://github.com/tongueroo/jets-nokogiri-demo

Ah, thanks for the reply.  I'll try it out.  I was able to repro with just running the quick start (minus db code)

Ah, thanks for the reply.  I'll try it out.  I was able to repro with just running the quick start (minus db code)

Your project gave me the same error:
$ curl https://szg6nfeohb.execute-api.us-east-1.amazonaws.com/dev/ ; echo
{"message": "Internal server error"}
$ jets call nokogiri-controller-index '{"test":1}'|jq
Calling lambda function nokogiri-dev-nokogiri_controller-index on AWS
Function name: nokogiri-dev-nokogiri_controller-index
Pro tip: The Lambda Console Link to the nokogiri-dev-nokogiri_controller-index function has been added to your clipboard.
{
  "errorMessage": "Could not find nokogiri-1.11.1 in any of the sources",
  "errorType": "Init<Bundler::GemNotFound>",
  "stackTrace": [
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `map!'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in `specs_for'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in `requested_specs'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in `block in definition_method'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in `setup'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler.rb:149:in `setup'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in `block in <top (required)>'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in `with_level'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in `silence'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in `<top (required)>'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:92:in `require'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:92:in `require'",
    "/var/task/handlers/controllers/nokogiri_controller.rb:1:in `<top (required)>'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:72:in `require'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:72:in `require'"
  ]
}

Full deploy logs:
$ jets deploy
Deploying to Lambda nokogiri-dev environment...
Building CloudFormation templates.
Generated CloudFormation templates at /tmp/jets/nokogiri/templates
Deploying CloudFormation stack with jets app!
Waiting for stack to complete
11:12:16AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack nokogiri-dev User Initiated
11:12:20AM CREATE_IN_PROGRESS AWS::S3::Bucket S3Bucket
11:12:21AM CREATE_IN_PROGRESS AWS::S3::Bucket S3Bucket Resource creation Initiated
11:12:42AM CREATE_COMPLETE AWS::S3::Bucket S3Bucket
11:12:43AM CREATE_COMPLETE AWS::CloudFormation::Stack nokogiri-dev
Stack success status: CREATE_COMPLETE
Time took for stack deployment: 31s.
The jets version has changed enough since the last build to merit refreshing the build cache.
Current jets version: 3.0.0 Last built jets version: unknown
Removing /tmp/jets/nokogiri to start fresh.
=> Compling assets in current project directory
=> yarn install
yarn install v1.22.4
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "webpack-dev-server ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[4/4] 🔨  Building fresh packages...
✨  Done in 9.27s.
=> JETS_ENV=development bin/webpack
Hash: bf8104733f8829203ac7
Version: webpack 4.46.0
Time: 3073ms
Built at: 01/11/2021 11:13:03 AM
                                   Asset       Size       Chunks                         Chunk Names
                  css/theme-091f1fb2.css  252 bytes        theme  [emitted] [immutable]  theme
              css/theme-091f1fb2.css.map  564 bytes        theme  [emitted] [dev]        theme
  js/application-e1f775d69c4918a86720.js    318 KiB  application  [emitted] [immutable]  application
js/application-e1f775d69c4918a86720.js.map    375 KiB  application  [emitted] [dev]        application
        js/theme-8d93dc0cc7011472ae21.js   3.93 KiB        theme  [emitted] [immutable]  theme
    js/theme-8d93dc0cc7011472ae21.js.map   3.61 KiB        theme  [emitted] [dev]        theme
                           manifest.json  901 bytes               [emitted]
Entrypoint application = js/application-e1f775d69c4918a86720.js js/application-e1f775d69c4918a86720.js.map
Entrypoint theme = css/theme-091f1fb2.css js/theme-8d93dc0cc7011472ae21.js css/theme-091f1fb2.css.map js/theme-8d93dc0cc7011472ae21.js.map
[./app/javascript/packs/application.js] 872 bytes {application} [built]
[./app/javascript/packs/theme.scss] 39 bytes {theme} [built]
[./app/javascript/src/jets/crud.js] 2.24 KiB {application} [built]
[./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 552 bytes {application} [built]
  + 2 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js??ref--6-1!node_modules/postcss-loader/src/index.js??ref--6-2!node_modules/sass-loader/dist/cjs.js??ref--6-3!app/javascript/packs/theme.scss:
  Entrypoint mini-css-extract-plugin = *
  [./node_modules/css-loader/dist/cjs.js?!./node_modules/postcss-loader/src/index.js?!./node_modules/sass-loader/dist/cjs.js?!./app/javascript/packs/theme.scss] ./node_modules/css-loader/dist/cjs.js??ref--6-1!./node_modules/postcss-loader/src??ref--6-2!./node_modules/sass-loader/dist/cjs.js??ref--6-3!./app/javascript/packs/theme.scss 1.06 KiB {mini-css-extract-plugin} [built]
      + 1 hidden module
=> Copying current project directory to temporary build area: /tmp/jets/nokogiri/stage/code
=> Reconfiguring webpacker development settings for AWS Lambda.
=> Bundling: running bundle install in cache area: /tmp/jets/nokogiri/cache.
=> cd /tmp/jets/nokogiri/cache && env bundle install
Fetching gem metadata from https://rubygems.org/......

Gems in the groups development and test were not installed.
Bundled gems are installed into `./vendor/gems`
Post-install message from i18n:

HEADS UP! i18n 1.1 changed fallbacks to exclude default locale.
But that may break your application.

If you are upgrading your Rails application from an older version of Rails:

Please check your Rails app for 'config.i18n.fallbacks = true'.
If you're using I18n (>= 1.1.0) and Rails (< 5.2.2), this should be
'config.i18n.fallbacks = [I18n.default_locale]'.
If not, fallbacks will be broken in your app by I18n 1.1.x.

If you are starting a NEW Rails application, you can ignore this notice.

For more info see:
https://github.com/svenfuchs/i18n/releases/tag/v1.1.0

Bundle install success.
Tidying project: removing ignored files to reduce package size.
=> rsync -a --links /tmp/jets/nokogiri/stage/code/vendor/gems/ruby/2.5.0/ /tmp/jets/nokogiri/stage/opt/ruby/gems/2.5.0/
=> Replacing compiled gems with AWS Lambda Linux compiled versions: /tmp/jets/nokogiri/stage/opt
Checking projects gems for binary Lambda gems...
ERROR: Limit Reached
You have reached your daily anonymous download limit.
You can increase the limit by registering:

  https://www.serverlessgems.com/rate-limits

Registering increases your rate limit.
Once you get a token, you can configure your machine with:

  jets configure TOKEN

Note: Replace TOKEN with your actual token.

$ # I added a token

$ jets deploy
Deploying to Lambda nokogiri-dev environment...
The /tmp/jets/nokogiri/cache folder exists. Incrementally re-building the jets using the cache.  To clear the cache: rm -rf /tmp/jets/nokogiri/cache
=> Compling assets in current project directory
=> yarn install
yarn install v1.22.4
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.58s.
=> JETS_ENV=development bin/webpack
Hash: bf8104733f8829203ac7
Version: webpack 4.46.0
Time: 1397ms
Built at: 01/11/2021 11:20:44 AM
                                   Asset       Size       Chunks                         Chunk Names
                  css/theme-091f1fb2.css  252 bytes        theme  [emitted] [immutable]  theme
              css/theme-091f1fb2.css.map  564 bytes        theme  [emitted] [dev]        theme
  js/application-e1f775d69c4918a86720.js    318 KiB  application  [emitted] [immutable]  application
js/application-e1f775d69c4918a86720.js.map    375 KiB  application  [emitted] [dev]        application
        js/theme-8d93dc0cc7011472ae21.js   3.93 KiB        theme  [emitted] [immutable]  theme
    js/theme-8d93dc0cc7011472ae21.js.map   3.61 KiB        theme  [emitted] [dev]        theme
                           manifest.json  901 bytes               [emitted]
Entrypoint application = js/application-e1f775d69c4918a86720.js js/application-e1f775d69c4918a86720.js.map
Entrypoint theme = css/theme-091f1fb2.css js/theme-8d93dc0cc7011472ae21.js css/theme-091f1fb2.css.map js/theme-8d93dc0cc7011472ae21.js.map
[./app/javascript/packs/application.js] 872 bytes {application} [built]
[./app/javascript/packs/theme.scss] 39 bytes {theme} [built]
[./app/javascript/src/jets/crud.js] 2.24 KiB {application} [built]
[./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 552 bytes {application} [built]
  + 2 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js??ref--6-1!node_modules/postcss-loader/src/index.js??ref--6-2!node_modules/sass-loader/dist/cjs.js??ref--6-3!app/javascript/packs/theme.scss:
  Entrypoint mini-css-extract-plugin = *
  [./node_modules/css-loader/dist/cjs.js?!./node_modules/postcss-loader/src/index.js?!./node_modules/sass-loader/dist/cjs.js?!./app/javascript/packs/theme.scss] ./node_modules/css-loader/dist/cjs.js??ref--6-1!./node_modules/postcss-loader/src??ref--6-2!./node_modules/sass-loader/dist/cjs.js??ref--6-3!./app/javascript/packs/theme.scss 1.06 KiB {mini-css-extract-plugin} [built]
      + 1 hidden module
=> Copying current project directory to temporary build area: /tmp/jets/nokogiri/stage/code
=> Reconfiguring webpacker development settings for AWS Lambda.
=> Bundling: running bundle install in cache area: /tmp/jets/nokogiri/cache.
=> cd /tmp/jets/nokogiri/cache && env bundle install
Using rake 13.0.3
Using concurrent-ruby 1.1.7
Using i18n 1.8.7
Using minitest 5.14.3
Using tzinfo 2.0.4
Using zeitwerk 2.4.2
Using activesupport 6.1.1
Using builder 3.2.4
Using erubi 1.10.0
Using mini_portile2 2.5.0
Using racc 1.5.2
Using nokogiri 1.11.1 (x86_64-darwin)
Using rails-dom-testing 2.0.3
Using crass 1.0.6
Using loofah 2.8.0
Using rails-html-sanitizer 1.3.0
Using actionview 6.1.1
Using rack 2.2.3
Using rack-test 1.1.0
Using actionpack 6.1.1
Using globalid 0.4.2
Using activejob 6.1.1
Using mini_mime 1.0.2
Using mail 2.7.1
Using actionmailer 6.1.1
Using activemodel 6.1.1
Using activerecord 6.1.1
Using aws-eventstream 1.1.0
Using aws-partitions 1.415.0
Using aws-sigv4 1.2.2
Using jmespath 1.4.0
Using aws-sdk-core 3.110.0
Using aws_config 0.1.0
Using memoist 0.16.2
Using rainbow 3.0.0
Using thor 1.0.1
Using aws-mfa-secure 0.4.3
Using aws-sdk-apigateway 1.58.0
Using aws-sdk-cloudformation 1.46.0
Using aws-sdk-cloudwatchlogs 1.38.0
Using aws-sdk-dynamodb 1.58.0
Using aws-sdk-kinesis 1.30.0
Using aws-sdk-kms 1.40.0
Using aws-sdk-lambda 1.57.0
Using aws-sdk-s3 1.87.0
Using aws-sdk-sns 1.36.0
Using aws-sdk-sqs 1.35.0
Using aws-sdk-ssm 1.101.0
Using bundler 2.1.4
Using cfn-status 0.4.2
Using cfn_camelizer 0.4.9
Using cfn_response 0.2.0
Using dotenv 2.7.6
Using dynomite 1.2.6
Using gems 1.2.0
Using hashie 4.1.0
Using rack-proxy 0.6.5
Using method_source 1.0.0
Using railties 6.1.1
Using semantic_range 2.3.1
Using jetpacker 0.5.0
Using jets-html-sanitizer 1.0.4
Using rexml 3.2.4
Using kramdown 2.3.0
Using mimemagic 0.3.5
Using recursive-open-struct 1.1.3
Using serverlessgems 0.1.0
Using shotgun 0.9.2
Using text-table 1.2.4
Using jets 3.0.0
Using mysql2 0.5.3
Bundle complete! 11 Gemfile dependencies, 71 gems now installed.
Gems in the groups development and test were not installed.
Bundled gems are installed into `./vendor/gems`
Bundle install success.
Tidying project: removing ignored files to reduce package size.
=> rsync -a --links /tmp/jets/nokogiri/stage/code/vendor/gems/ruby/2.5.0/ /tmp/jets/nokogiri/stage/opt/ruby/gems/2.5.0/
=> Replacing compiled gems with AWS Lambda Linux compiled versions: /tmp/jets/nokogiri/stage/opt
Checking projects gems for binary Lambda gems...
=> Generating shims in the handlers folder.
=> Creating zip file for /tmp/jets/nokogiri/stage/opt
=> cd /tmp/jets/nokogiri/stage/opt && zip --symlinks -rq opt.zip .
Zip file created at: /tmp/jets/nokogiri/stage/zips/opt-01dc7260.zip (22.2 MB)
=> Creating zip file for /tmp/jets/nokogiri/stage/code
=> cd /tmp/jets/nokogiri/stage/code && zip --symlinks -rq code.zip .
Zip file created at: /tmp/jets/nokogiri/stage/zips/code-891ded52.zip (157 KB)
Building CloudFormation templates.
Generated CloudFormation templates at /tmp/jets/nokogiri/templates
Uploading CloudFormation templates to S3.
Uploading code zip files to S3.
Uploading /tmp/jets/nokogiri/stage/zips/opt-01dc7260.zip (22.2 MB) to S3
Uploaded to s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/code/opt-01dc7260.zip
Time to upload code to s3: 4s
Uploading /tmp/jets/nokogiri/stage/zips/code-891ded52.zip (157 KB) to S3
Uploaded to s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/code/code-891ded52.zip
Time to upload code to s3: 0s
Checking for modified public assets and uploading to S3.
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/404.html
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/index.html
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/500.html
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/favicon.ico
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/422.html
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/css/theme-091f1fb2.css.map
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/css/theme-091f1fb2.css
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/js/theme-8d93dc0cc7011472ae21.js.map
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/js/theme-8d93dc0cc7011472ae21.js
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/js/application-e1f775d69c4918a86720.js
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/manifest.json
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/js/application-e1f775d69c4918a86720.js.map
Time for public assets to s3: 1s
Deploying CloudFormation stack with jets app!
Waiting for stack to complete
11:21:30AM UPDATE_IN_PROGRESS AWS::CloudFormation::Stack nokogiri-dev User Initiated
11:21:35AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiGateway
11:21:35AM CREATE_IN_PROGRESS AWS::IAM::Role IamRole
11:21:35AM CREATE_IN_PROGRESS AWS::Lambda::LayerVersion GemLayer
11:21:36AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiGateway Resource creation Initiated
11:21:36AM CREATE_IN_PROGRESS AWS::IAM::Role IamRole Resource creation Initiated
11:21:44AM CREATE_IN_PROGRESS AWS::Lambda::LayerVersion GemLayer Resource creation Initiated
11:21:45AM CREATE_COMPLETE AWS::Lambda::LayerVersion GemLayer
11:21:46AM CREATE_COMPLETE AWS::CloudFormation::Stack ApiGateway
11:21:49AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiResources1
11:21:49AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiResources1 Resource creation Initiated
11:21:56AM CREATE_COMPLETE AWS::IAM::Role IamRole
11:21:58AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack JetsPreheatJob
11:21:58AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack NokogiriController
11:21:59AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack JetsPreheatJob Resource creation Initiated
11:21:59AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack NokogiriController Resource creation Initiated
11:22:00AM CREATE_COMPLETE AWS::CloudFormation::Stack ApiResources1
11:22:02AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack JetsPublicController
11:22:04AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack JetsPublicController Resource creation Initiated
11:22:33AM CREATE_COMPLETE AWS::CloudFormation::Stack NokogiriController
11:22:38AM CREATE_COMPLETE AWS::CloudFormation::Stack JetsPublicController
11:22:40AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiDeployment20210111112122
11:22:41AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiDeployment20210111112122 Resource creation Initiated
11:22:52AM CREATE_COMPLETE AWS::CloudFormation::Stack ApiDeployment20210111112122
11:23:54AM CREATE_COMPLETE AWS::CloudFormation::Stack JetsPreheatJob
11:23:56AM UPDATE_COMPLETE_CLEANUP_IN_PROGRESS AWS::CloudFormation::Stack nokogiri-dev
11:23:56AM UPDATE_COMPLETE AWS::CloudFormation::Stack nokogiri-dev
Stack success status: UPDATE_COMPLETE
Time took for stack deployment: 2m 31s.
Prewarming application.
API Gateway Endpoint: https://szg6nfeohb.execute-api.us-east-1.amazonaws.com/dev/
[jhottenstein@hottenmac jets-nokogiri-demo (master)]$ curl https://szg6nfeohb.execute-api.us-east-1.amazonaws.com/dev/ ; echo
{"message": "Internal server error"}
[jhottenstein@hottenmac jets-nokogiri-demo (master)]$ curl https://ykmipzptqc.execute-api.us-west-2.amazonaws.com/dev/ ; echo
{"content":"Appendix A: The Compiler Toolchain¶","nokogiri_version":"1.11.1","jets_version":"3.0.0","ruby_version":"2.5.8"}
[jhottenstein@hottenmac jets-nokogiri-demo (master)]$

Your project gave me the same error:
$ curl https://szg6nfeohb.execute-api.us-east-1.amazonaws.com/dev/ ; echo
{"message": "Internal server error"}
$ jets call nokogiri-controller-index '{"test":1}'|jq
Calling lambda function nokogiri-dev-nokogiri_controller-index on AWS
Function name: nokogiri-dev-nokogiri_controller-index
Pro tip: The Lambda Console Link to the nokogiri-dev-nokogiri_controller-index function has been added to your clipboard.
{
  "errorMessage": "Could not find nokogiri-1.11.1 in any of the sources",
  "errorType": "Init<Bundler::GemNotFound>",
  "stackTrace": [
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `map!'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in `specs_for'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in `requested_specs'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in `block in definition_method'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in `setup'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler.rb:149:in `setup'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in `block in <top (required)>'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in `with_level'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in `silence'",
    "/var/runtime/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in `<top (required)>'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:92:in `require'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:92:in `require'",
    "/var/task/handlers/controllers/nokogiri_controller.rb:1:in `<top (required)>'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:72:in `require'",
    "/var/lang/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:72:in `require'"
  ]
}

Full deploy logs:
$ jets deploy
Deploying to Lambda nokogiri-dev environment...
Building CloudFormation templates.
Generated CloudFormation templates at /tmp/jets/nokogiri/templates
Deploying CloudFormation stack with jets app!
Waiting for stack to complete
11:12:16AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack nokogiri-dev User Initiated
11:12:20AM CREATE_IN_PROGRESS AWS::S3::Bucket S3Bucket
11:12:21AM CREATE_IN_PROGRESS AWS::S3::Bucket S3Bucket Resource creation Initiated
11:12:42AM CREATE_COMPLETE AWS::S3::Bucket S3Bucket
11:12:43AM CREATE_COMPLETE AWS::CloudFormation::Stack nokogiri-dev
Stack success status: CREATE_COMPLETE
Time took for stack deployment: 31s.
The jets version has changed enough since the last build to merit refreshing the build cache.
Current jets version: 3.0.0 Last built jets version: unknown
Removing /tmp/jets/nokogiri to start fresh.
=> Compling assets in current project directory
=> yarn install
yarn install v1.22.4
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "webpack-dev-server ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[4/4] 🔨  Building fresh packages...
✨  Done in 9.27s.
=> JETS_ENV=development bin/webpack
Hash: bf8104733f8829203ac7
Version: webpack 4.46.0
Time: 3073ms
Built at: 01/11/2021 11:13:03 AM
                                   Asset       Size       Chunks                         Chunk Names
                  css/theme-091f1fb2.css  252 bytes        theme  [emitted] [immutable]  theme
              css/theme-091f1fb2.css.map  564 bytes        theme  [emitted] [dev]        theme
  js/application-e1f775d69c4918a86720.js    318 KiB  application  [emitted] [immutable]  application
js/application-e1f775d69c4918a86720.js.map    375 KiB  application  [emitted] [dev]        application
        js/theme-8d93dc0cc7011472ae21.js   3.93 KiB        theme  [emitted] [immutable]  theme
    js/theme-8d93dc0cc7011472ae21.js.map   3.61 KiB        theme  [emitted] [dev]        theme
                           manifest.json  901 bytes               [emitted]
Entrypoint application = js/application-e1f775d69c4918a86720.js js/application-e1f775d69c4918a86720.js.map
Entrypoint theme = css/theme-091f1fb2.css js/theme-8d93dc0cc7011472ae21.js css/theme-091f1fb2.css.map js/theme-8d93dc0cc7011472ae21.js.map
[./app/javascript/packs/application.js] 872 bytes {application} [built]
[./app/javascript/packs/theme.scss] 39 bytes {theme} [built]
[./app/javascript/src/jets/crud.js] 2.24 KiB {application} [built]
[./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 552 bytes {application} [built]
  + 2 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js??ref--6-1!node_modules/postcss-loader/src/index.js??ref--6-2!node_modules/sass-loader/dist/cjs.js??ref--6-3!app/javascript/packs/theme.scss:
  Entrypoint mini-css-extract-plugin = *
  [./node_modules/css-loader/dist/cjs.js?!./node_modules/postcss-loader/src/index.js?!./node_modules/sass-loader/dist/cjs.js?!./app/javascript/packs/theme.scss] ./node_modules/css-loader/dist/cjs.js??ref--6-1!./node_modules/postcss-loader/src??ref--6-2!./node_modules/sass-loader/dist/cjs.js??ref--6-3!./app/javascript/packs/theme.scss 1.06 KiB {mini-css-extract-plugin} [built]
      + 1 hidden module
=> Copying current project directory to temporary build area: /tmp/jets/nokogiri/stage/code
=> Reconfiguring webpacker development settings for AWS Lambda.
=> Bundling: running bundle install in cache area: /tmp/jets/nokogiri/cache.
=> cd /tmp/jets/nokogiri/cache && env bundle install
Fetching gem metadata from https://rubygems.org/......

Gems in the groups development and test were not installed.
Bundled gems are installed into `./vendor/gems`
Post-install message from i18n:

HEADS UP! i18n 1.1 changed fallbacks to exclude default locale.
But that may break your application.

If you are upgrading your Rails application from an older version of Rails:

Please check your Rails app for 'config.i18n.fallbacks = true'.
If you're using I18n (>= 1.1.0) and Rails (< 5.2.2), this should be
'config.i18n.fallbacks = [I18n.default_locale]'.
If not, fallbacks will be broken in your app by I18n 1.1.x.

If you are starting a NEW Rails application, you can ignore this notice.

For more info see:
https://github.com/svenfuchs/i18n/releases/tag/v1.1.0

Bundle install success.
Tidying project: removing ignored files to reduce package size.
=> rsync -a --links /tmp/jets/nokogiri/stage/code/vendor/gems/ruby/2.5.0/ /tmp/jets/nokogiri/stage/opt/ruby/gems/2.5.0/
=> Replacing compiled gems with AWS Lambda Linux compiled versions: /tmp/jets/nokogiri/stage/opt
Checking projects gems for binary Lambda gems...
ERROR: Limit Reached
You have reached your daily anonymous download limit.
You can increase the limit by registering:

  https://www.serverlessgems.com/rate-limits

Registering increases your rate limit.
Once you get a token, you can configure your machine with:

  jets configure TOKEN

Note: Replace TOKEN with your actual token.

$ # I added a token

$ jets deploy
Deploying to Lambda nokogiri-dev environment...
The /tmp/jets/nokogiri/cache folder exists. Incrementally re-building the jets using the cache.  To clear the cache: rm -rf /tmp/jets/nokogiri/cache
=> Compling assets in current project directory
=> yarn install
yarn install v1.22.4
[1/4] 🔍  Resolving packages...
success Already up-to-date.
✨  Done in 0.58s.
=> JETS_ENV=development bin/webpack
Hash: bf8104733f8829203ac7
Version: webpack 4.46.0
Time: 1397ms
Built at: 01/11/2021 11:20:44 AM
                                   Asset       Size       Chunks                         Chunk Names
                  css/theme-091f1fb2.css  252 bytes        theme  [emitted] [immutable]  theme
              css/theme-091f1fb2.css.map  564 bytes        theme  [emitted] [dev]        theme
  js/application-e1f775d69c4918a86720.js    318 KiB  application  [emitted] [immutable]  application
js/application-e1f775d69c4918a86720.js.map    375 KiB  application  [emitted] [dev]        application
        js/theme-8d93dc0cc7011472ae21.js   3.93 KiB        theme  [emitted] [immutable]  theme
    js/theme-8d93dc0cc7011472ae21.js.map   3.61 KiB        theme  [emitted] [dev]        theme
                           manifest.json  901 bytes               [emitted]
Entrypoint application = js/application-e1f775d69c4918a86720.js js/application-e1f775d69c4918a86720.js.map
Entrypoint theme = css/theme-091f1fb2.css js/theme-8d93dc0cc7011472ae21.js css/theme-091f1fb2.css.map js/theme-8d93dc0cc7011472ae21.js.map
[./app/javascript/packs/application.js] 872 bytes {application} [built]
[./app/javascript/packs/theme.scss] 39 bytes {theme} [built]
[./app/javascript/src/jets/crud.js] 2.24 KiB {application} [built]
[./node_modules/webpack/buildin/module.js] (webpack)/buildin/module.js 552 bytes {application} [built]
  + 2 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js??ref--6-1!node_modules/postcss-loader/src/index.js??ref--6-2!node_modules/sass-loader/dist/cjs.js??ref--6-3!app/javascript/packs/theme.scss:
  Entrypoint mini-css-extract-plugin = *
  [./node_modules/css-loader/dist/cjs.js?!./node_modules/postcss-loader/src/index.js?!./node_modules/sass-loader/dist/cjs.js?!./app/javascript/packs/theme.scss] ./node_modules/css-loader/dist/cjs.js??ref--6-1!./node_modules/postcss-loader/src??ref--6-2!./node_modules/sass-loader/dist/cjs.js??ref--6-3!./app/javascript/packs/theme.scss 1.06 KiB {mini-css-extract-plugin} [built]
      + 1 hidden module
=> Copying current project directory to temporary build area: /tmp/jets/nokogiri/stage/code
=> Reconfiguring webpacker development settings for AWS Lambda.
=> Bundling: running bundle install in cache area: /tmp/jets/nokogiri/cache.
=> cd /tmp/jets/nokogiri/cache && env bundle install
Using rake 13.0.3
Using concurrent-ruby 1.1.7
Using i18n 1.8.7
Using minitest 5.14.3
Using tzinfo 2.0.4
Using zeitwerk 2.4.2
Using activesupport 6.1.1
Using builder 3.2.4
Using erubi 1.10.0
Using mini_portile2 2.5.0
Using racc 1.5.2
Using nokogiri 1.11.1 (x86_64-darwin)
Using rails-dom-testing 2.0.3
Using crass 1.0.6
Using loofah 2.8.0
Using rails-html-sanitizer 1.3.0
Using actionview 6.1.1
Using rack 2.2.3
Using rack-test 1.1.0
Using actionpack 6.1.1
Using globalid 0.4.2
Using activejob 6.1.1
Using mini_mime 1.0.2
Using mail 2.7.1
Using actionmailer 6.1.1
Using activemodel 6.1.1
Using activerecord 6.1.1
Using aws-eventstream 1.1.0
Using aws-partitions 1.415.0
Using aws-sigv4 1.2.2
Using jmespath 1.4.0
Using aws-sdk-core 3.110.0
Using aws_config 0.1.0
Using memoist 0.16.2
Using rainbow 3.0.0
Using thor 1.0.1
Using aws-mfa-secure 0.4.3
Using aws-sdk-apigateway 1.58.0
Using aws-sdk-cloudformation 1.46.0
Using aws-sdk-cloudwatchlogs 1.38.0
Using aws-sdk-dynamodb 1.58.0
Using aws-sdk-kinesis 1.30.0
Using aws-sdk-kms 1.40.0
Using aws-sdk-lambda 1.57.0
Using aws-sdk-s3 1.87.0
Using aws-sdk-sns 1.36.0
Using aws-sdk-sqs 1.35.0
Using aws-sdk-ssm 1.101.0
Using bundler 2.1.4
Using cfn-status 0.4.2
Using cfn_camelizer 0.4.9
Using cfn_response 0.2.0
Using dotenv 2.7.6
Using dynomite 1.2.6
Using gems 1.2.0
Using hashie 4.1.0
Using rack-proxy 0.6.5
Using method_source 1.0.0
Using railties 6.1.1
Using semantic_range 2.3.1
Using jetpacker 0.5.0
Using jets-html-sanitizer 1.0.4
Using rexml 3.2.4
Using kramdown 2.3.0
Using mimemagic 0.3.5
Using recursive-open-struct 1.1.3
Using serverlessgems 0.1.0
Using shotgun 0.9.2
Using text-table 1.2.4
Using jets 3.0.0
Using mysql2 0.5.3
Bundle complete! 11 Gemfile dependencies, 71 gems now installed.
Gems in the groups development and test were not installed.
Bundled gems are installed into `./vendor/gems`
Bundle install success.
Tidying project: removing ignored files to reduce package size.
=> rsync -a --links /tmp/jets/nokogiri/stage/code/vendor/gems/ruby/2.5.0/ /tmp/jets/nokogiri/stage/opt/ruby/gems/2.5.0/
=> Replacing compiled gems with AWS Lambda Linux compiled versions: /tmp/jets/nokogiri/stage/opt
Checking projects gems for binary Lambda gems...
=> Generating shims in the handlers folder.
=> Creating zip file for /tmp/jets/nokogiri/stage/opt
=> cd /tmp/jets/nokogiri/stage/opt && zip --symlinks -rq opt.zip .
Zip file created at: /tmp/jets/nokogiri/stage/zips/opt-01dc7260.zip (22.2 MB)
=> Creating zip file for /tmp/jets/nokogiri/stage/code
=> cd /tmp/jets/nokogiri/stage/code && zip --symlinks -rq code.zip .
Zip file created at: /tmp/jets/nokogiri/stage/zips/code-891ded52.zip (157 KB)
Building CloudFormation templates.
Generated CloudFormation templates at /tmp/jets/nokogiri/templates
Uploading CloudFormation templates to S3.
Uploading code zip files to S3.
Uploading /tmp/jets/nokogiri/stage/zips/opt-01dc7260.zip (22.2 MB) to S3
Uploaded to s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/code/opt-01dc7260.zip
Time to upload code to s3: 4s
Uploading /tmp/jets/nokogiri/stage/zips/code-891ded52.zip (157 KB) to S3
Uploaded to s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/code/code-891ded52.zip
Time to upload code to s3: 0s
Checking for modified public assets and uploading to S3.
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/404.html
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/index.html
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/500.html
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/favicon.ico
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/422.html
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/css/theme-091f1fb2.css.map
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/css/theme-091f1fb2.css
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/js/theme-8d93dc0cc7011472ae21.js.map
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/js/theme-8d93dc0cc7011472ae21.js
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/js/application-e1f775d69c4918a86720.js
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/manifest.json
Uploading and setting content type for s3://nokogiri-dev-s3bucket-16100aiab26dj/jets/public/packs/js/application-e1f775d69c4918a86720.js.map
Time for public assets to s3: 1s
Deploying CloudFormation stack with jets app!
Waiting for stack to complete
11:21:30AM UPDATE_IN_PROGRESS AWS::CloudFormation::Stack nokogiri-dev User Initiated
11:21:35AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiGateway
11:21:35AM CREATE_IN_PROGRESS AWS::IAM::Role IamRole
11:21:35AM CREATE_IN_PROGRESS AWS::Lambda::LayerVersion GemLayer
11:21:36AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiGateway Resource creation Initiated
11:21:36AM CREATE_IN_PROGRESS AWS::IAM::Role IamRole Resource creation Initiated
11:21:44AM CREATE_IN_PROGRESS AWS::Lambda::LayerVersion GemLayer Resource creation Initiated
11:21:45AM CREATE_COMPLETE AWS::Lambda::LayerVersion GemLayer
11:21:46AM CREATE_COMPLETE AWS::CloudFormation::Stack ApiGateway
11:21:49AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiResources1
11:21:49AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiResources1 Resource creation Initiated
11:21:56AM CREATE_COMPLETE AWS::IAM::Role IamRole
11:21:58AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack JetsPreheatJob
11:21:58AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack NokogiriController
11:21:59AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack JetsPreheatJob Resource creation Initiated
11:21:59AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack NokogiriController Resource creation Initiated
11:22:00AM CREATE_COMPLETE AWS::CloudFormation::Stack ApiResources1
11:22:02AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack JetsPublicController
11:22:04AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack JetsPublicController Resource creation Initiated
11:22:33AM CREATE_COMPLETE AWS::CloudFormation::Stack NokogiriController
11:22:38AM CREATE_COMPLETE AWS::CloudFormation::Stack JetsPublicController
11:22:40AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiDeployment20210111112122
11:22:41AM CREATE_IN_PROGRESS AWS::CloudFormation::Stack ApiDeployment20210111112122 Resource creation Initiated
11:22:52AM CREATE_COMPLETE AWS::CloudFormation::Stack ApiDeployment20210111112122
11:23:54AM CREATE_COMPLETE AWS::CloudFormation::Stack JetsPreheatJob
11:23:56AM UPDATE_COMPLETE_CLEANUP_IN_PROGRESS AWS::CloudFormation::Stack nokogiri-dev
11:23:56AM UPDATE_COMPLETE AWS::CloudFormation::Stack nokogiri-dev
Stack success status: UPDATE_COMPLETE
Time took for stack deployment: 2m 31s.
Prewarming application.
API Gateway Endpoint: https://szg6nfeohb.execute-api.us-east-1.amazonaws.com/dev/
[jhottenstein@hottenmac jets-nokogiri-demo (master)]$ curl https://szg6nfeohb.execute-api.us-east-1.amazonaws.com/dev/ ; echo
{"message": "Internal server error"}
[jhottenstein@hottenmac jets-nokogiri-demo (master)]$ curl https://ykmipzptqc.execute-api.us-west-2.amazonaws.com/dev/ ; echo
{"content":"Appendix A: The Compiler Toolchain¶","nokogiri_version":"1.11.1","jets_version":"3.0.0","ruby_version":"2.5.8"}
[jhottenstein@hottenmac jets-nokogiri-demo (master)]$

That was a tough one. Seems like ruby and/or bundler changed the way gems can be installed, which changes the way native gem detection works. Fixed. Try upgrading to jets v3.0.1 and then:
rm -rf /tmp/jets
jets deploy

That was a tough one. Seems like ruby and/or bundler changed the way gems can be installed, which changes the way native gem detection works. Fixed. Try upgrading to jets v3.0.1 and then:
rm -rf /tmp/jets
jets deploy

In my case, when I fixed the version to 1.9.1 to avoid using nokogiri's 1.11, I got an error related to liblzma, so I fixed it to 1.10 and that solved the problem.If you're having same trouble, please refer to the following.
liblzma.so.5: cannot open shared object file: No such file or directory - /opt/ruby/gems/2.7.0/gems/nokogiri-1.9.1/lib/nokogiri/nokogiri.so

- gem 'nokogiri', '1.9.1'

+ gem 'nokogiri', '~> 1.10.0'

In my case, when I fixed the version to 1.9.1 to avoid using nokogiri's 1.11, I got an error related to liblzma, so I fixed it to 1.10 and that solved the problem.If you're having same trouble, please refer to the following.
liblzma.so.5: cannot open shared object file: No such file or directory - /opt/ruby/gems/2.7.0/gems/nokogiri-1.9.1/lib/nokogiri/nokogiri.so

- gem 'nokogiri', '1.9.1'

+ gem 'nokogiri', '~> 1.10.0'

Had to do with gem detection and specific versions of nokogiri gem. Fixed in #529 It was already fixed in Jets v3. Also, released in jets v2.3.19.

Had to do with gem detection and specific versions of nokogiri gem. Fixed in #529 It was already fixed in Jets v3. Also, released in jets v2.3.19.


[FIX] the hostname of enpoint parser should parse dash symbol.

Summary by CodeRabbit

新特性

更新了主机名解析的正则表达式，允许更多字符出现在主机名末尾。
增加了一个新的测试方法，以验证包含破折号的主机的连接字符串解析。

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 13.24%. Comparing base (f1b83af) to head (7ac01d9).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
+ Coverage   13.20%   13.24%   +0.04%
==========================================
  Files         110      110
  Lines       19050    19059       +9
==========================================
+ Hits         2516     2525       +9
  Misses      16534    16534

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Where is generate?

https://github.com/VolkovLabs/volkovlabs-abc-datasource/generate missing.

@vova-malenky Are you logged in to GitHub? You can't generate if you are not logged in.
Let me know.

I hope it worked for you. Let me know if not.

Got it, thanks.


some issue about result

Hi
I trained 3400 images ( 1700 cover,1700 stego )
but I got same loss value for wow 0.3 and wow 1.0 ( LOSS = 0.6125 )
In predict phase I always get AUC = 0.5
There must be something wrong :(
PS:

Since ImageDataGenerator doesn't support pgm format ( dataset boss_base ) I changed pgm to png. does it make sense ?
I use google colab
Thank you

你现在解决了吗，不需要更改图像格式


Support to run coverage

Codecov Report

:exclamation: No coverage uploaded for pull request base (ros_vendoring@10c9078). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             ros_vendoring       #1   +/-   ##
================================================
  Coverage                 ?   34.57%
================================================
  Files                    ?        4
  Lines                    ?      937
  Branches                 ?        0
================================================
  Hits                     ?      324
  Misses                   ?      613
  Partials                 ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 10c9078...72e151c. Read the comment docs.


Alternative routes with CH are very slow for the foot profile

According to the measurement I introduced recently the queries take around 1.8s on average in Germany. Before #2491 I even measured something like 2.8s. For comparison, the same measurement yields something like 20ms (like 100x faster) when using the car profile. Not sure if this is real or it might depend on our way to measure this as well. Probably for the foot profile we get a bigger overlap between the forward and backward search trees as the graph is more dense?! Also not sure if we can do much about it, because for alternative routes the quality of the routes is more important, and this is not so easy to quantify. Also we can expect most foot routes to be rather short compared to car routes and shorter routes are faster to calculate anyway.

I see this also on GH maps. It works for shorter routes (say within Berlin), but longer routes (like 600km) are either very slow (>10s) or even time out: https://graphhopper.com/maps2/?point=48.297578%2C9.420381&point=52.746103%2C13.524756&profile=foot&layer=MapTiler. Similar routes for car take <0.5s


Feature request - add env var to enable extensions by default

By example, when need enable by default the uuid extension need execute additional scripts in startup:
CREATE EXTENSION IF NOT EXISTS "uuid-ossp";

But, is a great idea send the extensions by arguments, by example:
$ sudo docker run postgres -e "EXTENSION=uuid-ossp" -e "EXTENSION=other-extension" ...

Basically the same response as, https://github.com/docker-library/mongo/issues/460#issuecomment-797795751; tldr: "We are always very hesitant to add new environment variables."
And I'll add, especially for something that amounts to a two line dockerfile (or an extra line in a docker-compose.yml file to mount an initdb.d directory):
FROM postgres:13
RUN echo 'CREATE EXTENSION IF NOT EXISTS "uuid-ossp";' > /docker-entrypoint-initdb.d/uuid-ossp.sql

But can not use docker compose, why not use enviroment variable for easy enabling extension?, is same question: why pass the password on enviroment variable and not in docker compose using RUN and create user statement?, in a productive enviroment need enable very specific extensions and dynamics passwords.


【Offline installation】Failed to pull image "percona@sha256:713c1817615b333b17d....."

[Offline installation]
During offline installation, there is no way to download such an offline mirror. How to replace the mirror with a version number for installation.

Hi @lefeiwang,
You can at any time specifying the MySQL server image by settings image field on the MysqlCluster resource. See this example:
apiVersion: mysql.presslabs.org/v1alpha1
kind: MysqlCluster
metadata:
  name: my-cluster
spec:
  replicas: 2
  secretName: my-secret
  image: your-mirror-percona:5.7

Please let me know if this helps!

Thank you for your reply, the problem has been solved.


Theme responsiveness is broken in all themes

It can be fixed partially by updating the metadata to Bootstrap 5 format:
on line 22 of file src/View/Metadata.php replace
$this->meta[] = ['viewport' => 'width=device-width, initial-scale=1'];
with
$this->meta[] = ['name' => 'viewport', 'content' => 'width=device-width, initial-scale=1'];
it is enough to fix the Auth theme, but the Admin theme needs some restructuring for narrow screens: it opens with expanded menu, the elements do not fit at the top and the sandwich button is misplaced. The left menu maybe is not the best idea for phone screens.

I may offer a PR for fixing the metadata, but that should perhaps be done together with redoing the UI, which I am not particularly good at.

PR #389 re-enabled mobile view, fixed the most glaring of the display issues.

PR #389 re-enabled mobile view, fixed the most glaring of the display issues.


Add ServerName to TLS config.

This is a follow-up to https://github.com/uber/cadence/pull/2769
I didn't test that earlier PR with host verification enabled. Now when I deploy the 0.11.0 release with host verification enabled, it fails with:
Incompatible cassandra versions: unable to create CQL Client: gocql: unable to create session: control: unable to connect to initial hosts: x509: cannot validate certificate for <ip address> because it doesn't contain any IP SANs

This PR adds a server name setting, which is passed into tls.Config.ServerName to bypass the error. I have verified this connects successfully with both enableHostVerification: true and serverName:  set.

Coverage increased (+0.5%) to 67.797% when pulling 3d843891b737e548e225e3becaa8abe622f6b744 on aoby:tls-add-server-name into c09186f4c8583d3084315b9fe8a493c2b080d1f6 on uber:master.

Thx for the review @meiliang86. Can we get this merged soon? Do I need anything else?

@aoby Sorry for the delay. I just merged the pull request.


[Bug]: Page URL not retained after reverting changes in Page URLs in Git-connected apps

Is there an existing issue for this?

[X] I have searched the existing issues

Description
In Git-connected apps, if we change a page URL and then revert it to its original state, the URL is not retained.
Steps To Reproduce

Go to a Git connected app.
Change the name of a page e.g. Page1 -> Page1Test.
Now change the page URL and save it.
Now remove the changes made to the Page URL.

Expected: The page URL should now get reverted to its original state.
Public Sample App
No response
Environment
Production
Severity
Medium (Frustrating UX)
Issue video log
https://jam.dev/c/175f58de-2026-49da-955d-5e4410b9c096
Version
Cloud

This mostly happens for home pages in any branch: https://jam.dev/c/cf3e1098-ba4f-41b5-a361-951d2a4a8cd1


Duplicates + Other Data Questions

Hello! Thanks for publishing this dataset!
Are there meant to be duplicates in the raw review data? I seem to be noticing some duplicates when loading the Grocery_and_Gourmet_Food data, although it is possible I am making a mistake here
It also seems like there is 1 review in Grocery_and_Gourmet_Food with a rating of 0.0, but this doesn't seem possible on Amazon. Do you happen to know what happened here?
Thanks so much again for your help!

Hi, thank you for bringing these issues to our attention! I have a few follow-up questions:
Q1: Should the duplicates be exact copies, including all metadata (like ASIN, parent ASIN, etc.)? Or should only the text (titles, descriptions) be duplicated for different ASINs?
Q2: Yes, I was able to reproduce the results. I also discovered that there is only one review in the Grocery_and_Gourmet_Food category with a rating of 0.0. I attempted to locate the corresponding review on the Amazon website but was unable to find it. It’s possible that the review was deleted or removed due to a website update. Currently, we do not know what could potentially result in a rating of 0.0. We will provide an update in this thread if we manage to identify the cause.

Thanks for responding to my question!
Q1: I have attached the data that I found to be duplicates - it seems that these are exact copies, but perhaps I made a mistake somewhere when loading the data: (sorry, it won't let me upload a file this large in github, so this is a box link) https://ucdavis.box.com/s/obit55zbyhqmw9vfao4w9ubli7vrxjwt
Some examples include:

rating
title
text
images
asin
parent_asin
user_id
timestamp
helpful_vote
verified_purchase

4
Rugelach, in my experience, are always rolled
Nancysl, I have made many rugelach in my life and eaten many times more,   made by my Jewish, Yiddish-speaking grandma. They are definitely rolled, with   the filling in a layer on top of the dough. No rugelach I have ever seen or   made was hollow with filling inside it. These look very good - my grandmother   did not use cream cheese in the dough. Hers were closer to 17th century than   today's...although I do prefer the dough made with cream cheese.
[]
B08CBV7L2S
B08CBV7L2S
AG3MU6VSQIOTVJWV7OZKBII3OMOQ
1.6715E+12
0
FALSE

2
Not worth the calories
Too soft for my liking and very little flavor.
[]
B079TRNVHX
B079TRNVHX
AG3MU6VSQIOTVJWV7OZKBII3OMOQ
1.6229E+12
0
TRUE

4
Large, sturdy husks for tamales
Good quality and large size, mostly. Some husks were excessively dirty at   the ends and worse, several had holes in them, all the way through, making   them unusable.
[]
B08LR23QK8
B08LR23QK8
AG3MU6VSQIOTVJWV7OZKBII3OMOQ
1.6193E+12
0
TRUE

5
Love this yeast!
I baked my regular recipe for French bread with this yeast and it was   amazingly good! My husband says it's the best bread I've made. Dough rose   faster and higher and was so easy to use, no proofing required, just add to   flour and go! I've used Red Star and Fleischmann's and this one is FAR   superior.
[]
B00GWSK7MA
B00GWSK7MA
AG3MU6VSQIOTVJWV7OZKBII3OMOQ
1.5885E+12
1
TRUE

5
No refrigeration is so convenient, yummy too!
This is delicious, so easy because needs no refrigeration and tastes   great. Since it needs no refrigeration, it doesn't cool down your coffee.   Great invention!
[]
B000YUOY30
B0BL9KF4SK
AG3MU6VSQIOTVJWV7OZKBII3OMOQ
1.5056E+12
0
TRUE

5
I love this tea.
Really good taste.
[]
B00G4A6B4Y
B0B1WGVVKN
AE5UW4XLVL5AXSJP24MTH4LKK4DA
1.6106E+12
0
TRUE

Q2: Thanks so much for looking into this for me! I appreciate it!


Flashlight Problem

Sometimes, when i press flash on button, flashligh is not opened. And also it is same vice versa. Why flashlight does not work properly? How can i overcome this problem?

Please provide more details:

Platform / version
Error log / stack trace / minimal code example to reproduce.


STOR_VHDX: Add two cases about copy 5G files( copy locally/wget/nfs) …

…to SCSI/IDE disk

Hi Jing Li,
Thank you for the new additions!
We would like to take these scenarios, but have a few recommendations first:

since the initial commit some other changes seems to have occurred, and we cannot merge it in the current state.
can the test be modified to handle selective tests - for eg run only wget?
there should be no effect in testing both IDE and SCSI for these scenarios, so my recommendation is to focus only on SCSI, so one test case.

Hi Chris,
Thank you so much for your review, will update new patch based on your recommendation.

Close this PR, will request a new one


Socket: fix memory leak

Also need memory deallocation before return (if error) in _can_read and _can_write.

+1 and merged. Thanks.
I have added another commit fixing same memory leak on errors.


Add new job roles to listing journey

⚠ Draft PR from David's branch
Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-2871

Closed in favour of consolidated #3886.


add: Keptn CLI auto completion docs

Fixes #729

Preview:

@christian-kreuzberger-dtx I have made the necessary changes. Regarding the auto-generated files, I would really like to open up an issue regarding the same and work on it!

Closing this in favor of https://github.com/keptn/keptn.github.io/pull/760


Vehicle physics is broken with current Godot.

Operating system or device:
Linux, but seems unrelated
Issue description (what happened, and what was expected):
Setup a car using the same parameters as in truck town demo.
Don't add collision shape. Use y-offset of 0 for the wheels from body, and setup
every wheel parameter to the same configuration as in demo.
Don't add collision shape yet, test your car - it should be stable on flat ground,
no jumping, just stationary.
Steps to reproduce:
Add collision shape (I used Box). The expected outcome is nothing changed in car behavior.
Actually, car starts to vibrate at high pitch rate.  The only way out is delete scene and start anew.
Not adding collision shape avoids this bug, but everything passes through your car then.
Link to minimal example project (optional but very welcome):
Will add if nobody can reproduce this.
It seems that other tweaking of parameters lead tho this problem, but it is quite random and unrelated,
as returning to known set won't fix it and problem still persists.
Video, demonstrating this bug: https://youtu.be/IzwvcN0Jbo0

Another workaround is replace the VehicleBody node with Spatial using UI button,
then run scene once, then replace it back with VehicleBody.

well, it seems you have to delete CollisionShape then use above workaround to get rid of vibration and jumpiness.

Single huge CollisionShape fixes this problem, it seems that stability depends on CollisionShape size,
which is really really weird.

it seems that everything depends on CollisionShape size, looks like the bigger the collision shape,
the more stable we are. Wiat it is used for? Momentum? At leas this should be configurable,
as adding one smaller CollisionShape  makes car go haywire.

At least some multiplier should exist to control this behavior...

Trying to setup vehicle Godot crashes without any errors specified. Console output:
CLOSING CONNECTION
TextureButton: 16,-4
Label: 108,63
HBoxContainer: 112,27
SAVING: res://vehicles/new_scene.scn
SAVING: res://vehicles/new_scene.scn
running: /home/slapin/godot/bin/godot.x11.opt.tools.64 -path /home/slapin/school-rage/main -rdebug localhost:6007 -p 0x0 res://vehicles/new_scene.scn
********* listening on port 6007
OK! 15
has connection!
has connection!
shit?: Connection reset by peer
ERROR: read: Server disconnected!
At: drivers/unix/stream_peer_tcp_posix.cpp:276.
CLOSING CONNECTION

Well, I will stop digging on this, hope somebody will fix this can of worms.

Center of mass is a too critical setting.
If the center of the body shape is approximately the same of the body origin  the vehicle is stable.
But it must be desirable to set the center of mass as real cars.

The thing which troubles me most is car stability depending on collision shapes.
Also random problems requiring swapping VehicleBody to Spatial and back.

Is this still an issue?

Dunno, not used Godot for a long time now, and will not be able to for several months.
If anybody cares, please re-test. If not, feel free to close.

I'm seeing the vibrations on my project exported to 3.0 (strangely, no vibrations in 2.0).
This is in the same test project as #8651

#12521

Closing as superseded by #12521.


Feature request: add tags to bam rather than writing 3 separate files

Hi,
Thanks for longshot, it's a great tool. I like the option to write out 3 bam files for the haplotype-separated reads, but have a related feature request.
Do you think it would be possible to write out only a single bam file, but adding tags to each read to specify both the haplotype and the phase block identifier?
Thanks,
Wouter

Thanks for the feedback. We are in the process of adding this feature. The branch 'singlebam' has code to output a single bam with the haplotype (HP) tag. The phase block identifier is not output currently but should be added soon.

Thank you!

The updated code that outputs the HP and PS tags is now on conda and master branch.

Thanks!


error using of attribute animated inside ion-search (use ionic-angular 3.1.0). If use 3.0.0 - app correct working

Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
If use attribute animated inside ion-searchbar return this error (show example to plnkr). Example is work, but if use angular core v 3.1.0 - this example showing this error:
Runtime Error ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'true'. Current value: 'false'. Stack Error: ExpressionChangedAfterItHasBeenCheckedError: Expression has changed after it was checked. Previous value: 'true'. Current value: 'false'.     at d (http://localhost:8100/build/polyfills.js:3:3991)     at viewDebugError (http://localhost:8100/build/main.js:8889:32)     at expressionChangedAfterItHasBeenCheckedError (http://localhost:8100/build/main.js:8867:12)     at checkBindingNoChanges (http://localhost:8100/build/main.js:9031:15)     at checkNoChangesNodeInline (http://localhost:8100/build/main.js:12467:9)     at checkNoChangesNode (http://localhost:8100/build/main.js:12433:9)     at debugCheckNoChangesNode (http://localhost:8100/build/main.js:13007:28)     at debugCheckRenderNodeFn (http://localhost:8100/build/main.js:12947:13)     at Object.eval [as updateRenderer] (ng:///AppModule/HomePage.ngfactory.js:107:5)     at Object.debugUpdateRenderer [as updateRenderer] (http://localhost:8100/build/main.js:12929:21)     at checkNoChangesView (http://localhost:8100/build/main.js:12293:14)     at callViewAction (http://localhost:8100/build/main.js:12612:17)     at execEmbeddedViewsAction (http://localhost:8100/build/main.js:12590:17)     at checkNoChangesView (http://localhost:8100/build/main.js:12292:5)     at callViewAction (http://localhost:8100/build/main.js:12612:17)
Expected behavior:
example show/hide search bar in ion-header.
Steps to reproduce:
http://plnkr.co/edit/fsutc5CVoSK2Cqh8ZBkx?p=preview
Related code:
insert any relevant code here

Other information:
I think, error including in  "ionic-angular": "^3.1.0". If delete attribute animated - app working correct!
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.5.0
Ionic Framework Version: 3.1.0
Ionic CLI Version: 2.2.3
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.6
ios-deploy version: Not installed
ios-sim version: Not installed
OS: macOS Sierra
Node Version: v6.10.2
Xcode version: Xcode 8.3.1 Build version 8E1000a

Angular lib 4.0.2

Known issue. Please use nightly for now - 3.1.0-201704272149, or revert to 3.0.2 to keep using it.


man command doesnt work

Hi, great work.
Installed V15.0.19 in wsl2 with
wsl.exe --import WSlackware c:\WSlackware .\install.tar.gz
running man commands gives error:
man: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory
solved with
slackpkg install libseccomp
Gianluca

@gcecchi Thank you for using WSLackware. We'll add this package to the next release.
Reza


Choose display field when using dropdown

When creating a dropdown with fields populated from a table it displays the ID instead of the name field.
I created 3 tables, then I created 1 table with dropdowns to the 3 other tables. Just 1 dropdown shows the id instead of the name field.
How can I choose which field to display?

Same question here
I want to display column title instead of id

Same here

Same #192  ??

@cerelli  Not the same, here we want to change the default column that specified on the package for values "name" to other field we choose


Parcelport plugins

The main addition of this PR is the ability to have parcelport plugins (both statically compiled into the main HPX library and dynamically loadable). This addresses #1201 and #680. In addition, the MPI parcelport has been rewritten in such a way that it reaches an acceptable performance (#1275). The IPC and ibverbs parcelports are temporarly disabled since they are non functional and need to be fixed. The changeset also includes various other code improvements.

This looks reasonably good. We should merge it to have regular testing.

The unit tests look pretty fine now. Please verify the latest changes once more.


Migration should notify of skipped resources

What problem are you facing?
When creating a migration on a local filesystem if a file contains unknown Kinds, the migrator will not process the file without emitting any warnings or errors.
For example, if a manifest contains a Secret which does not have a registered converter, outputs are never generated.
---
apiVersion: v1
kind: Secret
metadata:
  name: demo-foo-mq-rabbitmq-creds
  namespace: example
  annotations:
    argocd.argoproj.io/sync-wave: "-2"
type: Opaque
immutable: true
data:
  password: "cGFzc3dvcmQK"
---
apiVersion: mq.aws.crossplane.io/v1alpha1
kind: Broker
metadata:
  labels:
    crossplane.io/provider-version: v0.26.1
  name: demo-foo-mq-rabbitmq
  namespace: example
  annotations:
    argocd.argoproj.io/sync-wave: "1"
spec:
  forProvider:
    region: us-east-1
    engineType: RabbitMQ
    publiclyAccessible: false
    autoMinorVersionUpgrade: false
    engineVersion: 3.8.11
    hostInstanceType: mq.t3.micro
    deploymentMode: SINGLE_INSTANCE
    subnetIDs:
      - subnet-2cc5ce61
    securityGroupIdRefs:
      - name: demo-foo-mq-rabbitmq-security-group
    users:
      - username: rabbitmq-admin
        consoleAccess: true
        passwordSecretRef:
          key: password
          name: demo-foo-mq-rabbitmq-creds
          namespace: example
    tags:
      App: crossplane
      Environment: qa
      Name: crossplane-mq
      Product: crossplane
      Squad: sandbox
      Tier: backend
      VS: sandbox
      cluster: mq-cluster
  writeConnectionSecretToRef:
    name: demo-foo-mq-creds
    namespace: example
  providerConfigRef:
    name: awsconfig

The generated migration plan is mostly empty and none of the other directories are crated.
spec: {}
version: 0.1.0

How could Upjet help solve your problem?
The user should be informed of any local filesystem resources that have been skipped during processing.

I think this issue is also related with https://github.com/upbound/upjet/issues/233


Update homu

This change is

@bors-servo r+

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

:pushpin: Commit 9d95184 has been approved by metajack

:hourglass: Testing commit 9d95184 with merge e1b0a0b...

:sunny: Test successful - travis


Allow Vite to serve from pages other than index.html

Clear and concise description of the problem
As a developer using Vite I want to be able to serve from different HTML pages so that I may more closely replicate my production environment.
I have an application that once built produces two different index.html pages for two different brands, for example index-a.html and index-b.html.
The production web server then chooses which of these html files to serve in SPA mode based on the domain that the request is coming from, so www.example.com goes to index-a.html and www.test.com goes to index-b.html
I'm trying to replicate this with the vite dev server, but I can't because the served page is hard-coded as index.html which you can see in the spaFallback middleware.
I've attempted to override this using a plugin and middleware, but I either get into an infinite redirection loop, or the server never serves the request.
This is not the same as multi-page apps as the target here is SPAs and even with a multi-page app you still need an index.html file in the root of the project. It is also not the same as being able to change the directory that the page is served from - the issue is being able to serve from a file other than index.html.
Suggested solution
Add a configuration property: server.indexFile with a default of index.html that is then used by the vite:spa-fallback module to retrieve the right index file. This should also be able to be set from the command line in the vite serve and vite preview commands.
This should not interfere with the multi-page app setup
Alternative
I've attempted to do this with a plugin, but I don't believe that I can effectively override the vite:spa-fallback middleware.
Additional context
Previously asked in the Discussions area with no positive response.
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

As another reason why this would be useful, I think it would resolve an issue in mocha-vite-puppeteer: https://github.com/larsthorup/mocha-vite-puppeteer/issues/28#issuecomment-962603743

Similar issue encountered, I'm working with multi-page apps and I suppose that vite could provide any option to disable the spa-fallback middleware to work with other express middlewares like serve-index

I've attempted to do this with a plugin, but I don't believe that I can effectively override the vite:spa-fallback middleware.

You can do so using the configureServer hook. See https://github.com/vitejs/vite/issues/5720 and SvelteKit's implementation. The linked issue could be a way to solve this too, as I think there would always be many points of configuration to get to the desired fallback behaviour.

I think using configureServer is the right choice here instead of another config option. Vite 3 introduced a new appType config which you can set to mpa so that it disables the spa fallback. You can then inject a custom spa fallback middleware with a Vite plugin via configureServer.
Something like (untested):
import history from 'connect-history-api-fallback'

export function speciallSpaFallback() {
  return {
    name: 'special-spa-fallback',
    config() {
      return {
        appType: 'mpa'
      }
    },
    configureServer(server) {
      return () => {
         server.middlewares.use(history(/* custom config */))
      }
    }
  }
}

Let me know if this works for you

Hey @steveworkman, did you get this working by any chance? Im looking for what i think is the exact same thing.
I have a plugin that takes the index.html and build out multiple different html files ( in my case different language files like en.html, fr.html etc ).
Looking to be able to access localhost:3000/en.html and so on

Closing due to lack of response


Please add ability view tabs-panel on no javascript

Please add this to scss
html.no-js{
    .tabs-panel{
        display: block;
    }
}

to display .tabs-panel when javascript not supporting by device

Relatedly, I don't think there's anything in the docs that recommends using <html class="no-js">. Should be added to the JavaScript page?

@soulcreate seems reasonable, would you like to submit a PR for this?
@andycochran yes, probably should.  @rafibomb can you take a look?

Bump.
This + accordion probably and also for the print mode might make sense.

@ncoden @kball what can we do to bring this issue forward?

For now there is no "no javascript" mode for Foundation. I could make sense to add it but it should be consistent across components.

Definitely. So it would be some sort of new feature for all components (no-js mode / styles).

We will revisit this for 7 then as this will be a new feature.


issue 1

I click on something in it and it does nothing

kjyoly

;,ll; @chrispecoraro

Nothing to preview @donovanjedj.com

@chrispecoraro


OpenTnsNamesFile cannot be used due to TnsNamesFileInfo constructor being internal.

If I want to pass in existing tnsnames.ora file and not use ResolveRootTnsNamesFiles() method to get TnsNames, then it is impossible as I cannot create parameter of type TnsNamesFileInfo.
Either empty public constructor should exist or existing should be made public.
Thank You!

Hi, I will look into this. I have a new upcoming version where source code for the ANTLR runtime is embedded, so no dll dependency on ANTLR.


[AutoPR iothub/resource-manager] [Hub Generated] Review request for Microsoft.Devices to add version preview/2019-03-22-preview

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6337

(message created by the CI based on PR content)


Feature/picker

🤔 这个 PR 的性质是？

[ ] 日常 bug 修复
[x] 新特性提交
[ ] 文档改进
[ ] 演示代码改进
[ ] 组件样式/交互改进
[ ] CI/CD 改进
[ ] 重构
[ ] 代码风格优化
[ ] 测试用例
[ ] 分支合并
[ ] 其他

🔗 相关 Issue

💡 需求背景和解决方案

📝 更新日志

fix(picker): 新增picker组件

[ ] 本条 PR 不需要纳入 Changelog

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[x] 文档已补充或无须补充
[x] 代码演示已提供或无须提供
[x] TypeScript 定义已补充或无须补充
[x] Changelog 已提供或无须提供

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@fe1166a). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             main    #143   +/-   ##
======================================
  Coverage        ?   6.85%
======================================
  Files           ?     303
  Lines           ?    3399
  Branches        ?     863
======================================
  Hits            ?     233
  Misses          ?    3166
  Partials        ?       0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fe1166a...318d972. Read the comment docs.


About auto_connect

Hi!
After the changes related to issues #47 and #87 I understand that auto connect should be issued (if required) as no longer it is turned on by default.
May it be pertinent to include it on the Basic commands of the documentation to be aware of that?
Also this setting could be a candidate to be included in the Basic Web Interface so it is not required to enter the console when performing a basic setup.
Thank you!

auto_connect is off (auto_connect 0) after first flashing or after "reset factory". As soon as you enter an SSID (on the CLI or the web interface) it will be automatically set on (auto_connect 1). As you usually typically set the SSID as first interaction, changing the auto_connect mode manually isn't really required.
There is no good reason, why you shouldn't want it to be on during operation, besides it's failure messages spam the serial console during first config. It doesn't harm anything on the web interface.
If you really want it to be off, you have to use the CLI. I think, that is okay, isn't it?

My confusion then may be related to a different cause during the provisioning of a device when its clients reported a drop on the connection that wasn't being recovered even after repeated restarts. Issuing the auto_connect resolved it, but I can't tell whether I have changed it or not as I did a lot of changes on the whole system during the setup.
I'll keep it in mind. However may you consider to include this explanation you just provided me about the auto_connect behaviour on the documentation? I think it's the only parameter missing there.
Thank you! The quality of your software is amazing.

Thank you - added that to the docu in Readme.md.


Delete button is always gone in repeating groups when hideTable is enabled

Description
The delete button is by default visible in repeating groups, but even with the property deleteButton set to True, it will not be visible if the mode is set to hideTable.
This means that if a user adds another entry to the list by mistake, they will not be able to get out of it unless they fill out the whole group in such a way that validation on save works, or they refresh the page.
Neither of these are good solutions, and a lot of users would simply be stuck - at a loss for what to do.
Additional Information
Example case where delete button is missing:

When using mode: "showAll" it looks like this:

Could it be done the same way for hideTable?


cp: only allow directory for -t

Add a validator to the --target-directory option that only allows directories as the argument value.
Closes #2986

Thank you! I'm a little bit hesitant about the use of clap validators. In any code that does not need to be compatible with other code I would encourage using them, but in this project we try to match GNU coreutils as closely as possible. With this solution, both the error message and the exit code are in compatible (it's 1 in GNU and 2 here). Could you maybe defer this check to after the argument parsing and return a custom error?

Thank you! I'm a little bit hesitant about the use of clap validators. In any code that does not need to be compatible with other code I would encourage using them, but in this project we try to match GNU coreutils as closely as possible. With this solution, both the error message and the exit code are in compatible (it's 1 in GNU and 2 here). Could you maybe defer this check to after the argument parsing and return a custom error that matches GNU?

I totally understand. I will make the change.

@tertsdiepraam I had a couple of thoughts as I went back to make your suggested changes.
For exit codes, you're going to encounter this issue with any sort of clap argument rules. We just went through this in #3012. In that case, I used try_get_matches_to with map_err to force an exit code of 1 since all clap parsing errors return 2:
    let matches = uu_app()
        .override_usage(&usage[..])
        .after_help(&long_usage[..])
        .get_matches_from(args);
        .try_get_matches_from(args)
        .map_err(|e| {
            e.print().expect("Error writing clap::Error");
            match e.kind {
                clap::ErrorKind::DisplayHelp | clap::ErrorKind::DisplayVersion => 0,
                _ => 1,
            }
        })?;

Instead of using the closure, we could add a common named function and use that with all clap argument parsing. This would allow using convenient clap argument rules and GNU compliant exit codes.
That said, we would not get GNU identical error messages. Is that a hard design requirement of the project?

Interesting idea! I would also like to see some more flexibility of clap on this, but this sounds like a good workaround. Another option is to implement From<ClapError> for UResultand fine it exit code 1.
Regarding the messages, we're not super strict about them if they are due to invalid arguments. Because that's usually not behaviour that people rely on and claps messages are now informative than GNU usually.

I added a UError impl for clap::Error. If uu_app().try_get_matches_from(args)? results in an error, the exit code will be 1 instead of 2.
Doing it this way disables the colorized output from clap. I'm sure there is some simple thing that I am missing to make this work. I just haven't figured it out yet.

@tertsdiepraam is that ok with you?


How to configure go2rtc as a ONVIF server?

Hi all,
Using go2rtc 1.8.5 as port 1984 on a docker instance running on a Raspberry Pi 3.  go2rtc works great with RTSP and HTTP streaming to tablets and to Home Assistant clients on my LAN (single subnet).
I’m now trying to get the Roku IP Camera Viewer Basic version to display a camera feed on my TV.  As it requires a MJPEG-encoded feed, I configured the settings in the Roku camera app as:
IP: <IP of Raspberry Pi>
Port: 1984
URL: /stream.html?src=my_camera_instance&mode=mjpeg

Doesn’t work.
I also tried just:
IP: <IP of Raspberry Pi>
Port: 1984
URL: /stream.html?src=my_camera_instance

Again, nada nada.
That’s when I learned about ONVIF.  If I’m RTFM’ing correctly, if the go2rtc server instance advertised as a ONVIF server (or at least had the right port open), the camera feeds on my go2rtc would be discoverable by the Roku camera app.
Right now, however, when I tell the Roku camera app to scan my network for ONVIF instances, it doesn’t detect anything.
Help?

Your URL doesn't have stream name in src param. So them doesn't work.
go2rtc doesn't provide ONVIF auto-discovery feature. ONVIF server runs at same port as Web API.

Your URL doesn't have stream name in src param. So them doesn't work. go2rtc doesn't provide ONVIF auto-discovery feature. ONVIF server runs at same port as Web API.

Hi @AlexxIT -- apologies, because I didn't wrap the IP / Port / URL entries inside a code-block, the stuff I angle-bracketed didn't display.
Please re-review what I have above?

MJPEG will work for you only if source camera support it. Or if you setup transcoding via ffmpeg.
If your app support only MJPEG stream - html link won't work. It's only for browser

It's sad to find lots of onvif camera viewers like scrypted or synology surveillance, I cannot provide the camera's name in the onvif address

The ability to configure go2rtc for adoption in unifi protect's recently added onvif support would effectively open that platform.

Should manual adoption be possible already? Using /onvif/{stream} throws an error
Is the onvif server considered an output module? It is not documented like the others.
I am under the impression that there is a general expectation for onvif servers that "1 IP == 1 Camera"

Creating the interfaces for other IPs is probably a bit much, but assuming they exist on the host: would adding the ability to configure additional instances of the existing onvif server to listen on a specific interface be reasonable?
Initial suggestion for configuration options to start a discussion:
onvif:
- listen: <IP_ADDRESS>:8000
  advertise: true
  name: Channel 5
  model: go2rtc
  highStream: channel5
  lowStream: channel5lq
- listen: <IP_ADDRESS>:8000
  advertise: false
  name: Channel 6
  model: go2rtc
  highStream: channel6
  lowStream: channel6lq

There is a mostly working reference implementation here: https://github.com/p10tyr/rtsp-to-onvif/
Advertising go2rtc's rtsp's streams with both high and low quality works great but snapshots are currently glitchy (ECONNRESET for frame.jpeg, intermittent for frame.mp4, unclear to me it's the tcp-proxy that project is using or some other interaction or just a bug on unifi's side).
Thanks!

Usually ONVIF expected only host and port, not URL
Multiple ONVIF severs in plans. It's a big task
The ONVIF implementation in go2rtc was tested with HA. I don't have any other software to test with
You can now run multiple instances of go2rtc. And get multiple ONVIF servers in this way

    Usually ONVIF expected only host and port, not URL

Right, I think this issue is about the potential need for additional config/doc around how go2rtc implements the existing onvif server.

Is there any chance to get this working? My Dahua NVR also doesn't accept anything but host and port and I want to record from non-Dahua MPJEG camera with the help of transcoding.

I don't know what you mean by "working". ONVIF server inside go2rtc is working.
ONVIF protocol has no settings other than host/port/username/password.
It does not assume the selection of a single camera. Within it, all streams are transmitted simultaneously.

In my case the RTSP address is the following rtsp://<IP_ADDRESS>:8554/intercom_h264. If ONVIF is on the same port how can I reference an intercom_h264 there if I cannot provide a name (path from url)?

This is ONVIF software problem

Most likely because it shows Failed to parse the domain error if I input <IP_ADDRESS>/intercom_h264 in the domain field. Is there any way of exposing the stream under different port instead of path in the url?

You can run separate go2rtc app and setup only one stream there.
Running multiple ONVIF servers in one go2rtc - only in plans.

setup only one stream there

That made me confused because intercom_h264  is the only stream I have defined in go2rtc config and without stream name I get an error.

Then why do you keep entering something other than the domain in the domain field?

If ONVIF is on the same port

go2rtc ONVIF server is not on the RTSP port.
go2rtc ONVIF server is on the API port.
go2rtc ONVIF server only implements the small subset of the full ONVIF spec required for basic ONVIF clients.
go2rtc ONVIF server works with basic ONVIF clients that only require the implemented subset of the ONVIF spec.
If your ONVIF client isn't happy with the existing implementation using ":" you have the option to contribute additional implementation.
See #1520 for an example of what that can look like.
Here is an example config that works for me, in my ONVIF client I entered <go2rtc IP>:9984
streams:
  channel2:
    - 'rtsp://admin:1234@<IP_ADDRESS>/cam/realmonitor?channel=2&subtype=0&unicast=true'

rtsp:
  listen: ":9554"

api:
  listen: ":9984"
  origin: "*"

log:
  api: trace
  onvif: trace

Did anyone manage to get ONVIF working with ONVIF Device Manager?

ONVIF Device Manager is not supported at this time. I'll test the PR from @acortelyou. And I will add support for this software as needed. I only tested compatibility with Home Assistant.


POS-Simplified-Signed-Properties-Hashing-Error

Hi there,
I've tested the B2B with its credit/debit notes and it is working as expected, regarding the simplified invoice and simplified credit/debit invoices I'm getting Invalid signed properties hashing, SignedProperties with id='xadesSignedProperties' when calling compliance/invoices.
Any help is really appreciated.

you face problem while submitting invoice, or at compliance test ??

Compliance test.
Request Object:
request.json

@fkalpana
I did send an email 3 days ago, but I didn't get a response.


Startup issue with 1.2.3

I am having an issue on startup with the latest version (1.2.3).  This issue doesn't happen for me on 1.2.2.  Here are the logs:
2019-01-27T00:51:55.556899266Z Start OpenLDAP...
2019-01-27T00:51:55.610210985Z Waiting for OpenLDAP to start...
2019-01-27T00:51:55.614614565Z Add TLS config...
2019-01-27T00:51:55.702928252Z Disable replication config...
2019-01-27T00:51:55.849956679Z *** /container/run/startup/slapd failed with status 34
2019-01-27T00:51:55.850142842Z
2019-01-27T00:51:55.850192678Z *** Killing all processes...
2019-01-27T00:52:48.921313505Z *** CONTAINER_LOG_LEVEL = 3 (info)
2019-01-27T00:52:48.922151599Z *** Search service in CONTAINER_SERVICE_DIR = /container/service :
2019-01-27T00:52:48.922271110Z *** link /container/service/:ssl-tools/startup.sh to /container/run/startup/:ssl-tools
2019-01-27T00:52:48.922338966Z *** failed to link /container/service/:ssl-tools/startup.sh to /container/run/startup/:ssl-tools: [Errno 17] File exists
2019-01-27T00:52:48.922410621Z *** link /container/service/slapd/startup.sh to /container/run/startup/slapd
2019-01-27T00:52:48.922474593Z *** failed to link /container/service/slapd/startup.sh to /container/run/startup/slapd: [Errno 17] File exists
2019-01-27T00:52:48.922534176Z *** link /container/service/slapd/process.sh to /container/run/process/slapd/run
2019-01-27T00:52:48.922591009Z *** directory /container/run/process/slapd already exists
2019-01-27T00:52:48.922645501Z *** failed to link /container/service/slapd/process.sh to /container/run/process/slapd/run : [Errno 17] File exists
2019-01-27T00:52:48.922704333Z *** Set environment for startup files
2019-01-27T00:52:48.926415503Z *** Environment files will be proccessed in this order :
2019-01-27T00:52:48.926543956Z Caution: previously defined variables will not be overriden.
2019-01-27T00:52:48.926616165Z /container/environment/99-default/default.startup.yaml
2019-01-27T00:52:48.926685192Z /container/environment/99-default/default.yaml
2019-01-27T00:52:48.926754169Z
2019-01-27T00:52:48.926813217Z To see how this files are processed and environment variables values,
2019-01-27T00:52:48.927014308Z run this container with '--loglevel debug'
2019-01-27T00:52:48.949824664Z *** Running /container/run/startup/:ssl-tools...
2019-01-27T00:52:48.963657410Z *** Running /container/run/startup/slapd...

I am running Docker on a Synology NAS.  The docker --version command outputs the following:
Docker version 17.05.0-ce, build 9f07f0e-synology
I use openldap with docker compose.  My config is configured like this (variables are in a .env file, but should't really matter):
openldap:
    image: osixia/openldap:latest
    networks:
      - backend
    volumes:
      - "${OPENLDAP_CONFIG}/db:/var/lib/ldap"
      - "${OPENLDAP_CONFIG}/slapd.d:/etc/ldap/slapd.d"
    restart: always
    environment:
      LDAP_ORGANISATION: ${SERVER_NAME}
      LDAP_DOMAIN: ${SERVER_NAME}
      LDAP_ADMIN_PASSWORD: secret

log-level doesn't appear to be supported with my version of docker-compose:
sh-4.3# docker-compose --log-level DEBUG start openldap
Define and run multi-container applications with Docker.

Usage:
  docker-compose [-f <arg>...] [options] [COMMAND] [ARGS...]
  docker-compose -h|--help

Options:
  -f, --file FILE             Specify an alternate compose file (default: docker-compose.yml)
  -p, --project-name NAME     Specify an alternate project name (default: directory name)
  --verbose                   Show more output
  -v, --version               Print version and exit
  -H, --host HOST             Daemon socket to connect to

  --tls                       Use TLS; implied by --tlsverify
  --tlscacert CA_PATH         Trust certs signed only by this CA
  --tlscert CLIENT_CERT_PATH  Path to TLS certificate file
  --tlskey TLS_KEY_PATH       Path to TLS key file
  --tlsverify                 Use TLS and verify the remote
  --skip-hostname-check       Don't check the daemon's hostname against the name specified
                              in the client certificate (for example if your docker host
                              is an IP address)
  --project-directory PATH    Specify an alternate working directory
                              (default: the path of the Compose file)

Commands:
  build              Build or rebuild services
  bundle             Generate a Docker bundle from the Compose file
  config             Validate and view the Compose file
  create             Create services
  down               Stop and remove containers, networks, images, and volumes
  events             Receive real time events from containers
  exec               Execute a command in a running container
  help               Get help on a command
  images             List images
  kill               Kill containers
  logs               View output from containers
  pause              Pause services
  port               Print the public port for a port binding
  ps                 List containers
  pull               Pull service images
  push               Push service images
  restart            Restart services
  rm                 Remove stopped containers
  run                Run a one-off command
  scale              Set number of containers for a service
  start              Start services
  stop               Stop services
  top                Display the running processes
  unpause            Unpause services
  up                 Create and start containers
  version            Show the Docker-Compose version information

log-level doesn't appear to be supported with my version of docker-compose:

This is actually a command for the image/container, not for Docker itself. Besides it's loglevel (without the hyphen). So you should use it like so:
openldap:
    image: osixia/openldap:latest
    [...]
    command: --loglevel debug

Or when running directly:
docker run [...] osixia/openldap:latest --loglevel debug

I have faced this issue too, here is debug log
https://gist.github.com/avoidik/f02869c61fd072856e372a8b5d6fb6ff

@avoidik to you have the issue with 1.2.4-dev image tag ?

on a :latest docker image

AFAICS the problematic part is here
Processing file /container/service/slapd/assets/config/admin-pw/ldif/07-admin-pw-change.ldif
5c6c094e conn=1002 fd=12 ACCEPT from PATH=/var/run/slapd/ldapi (PATH=/var/run/slapd/ldapi)
5c6c094e conn=1002 op=0 BIND dn="" method=163
5c6c094e conn=1002 op=0 BIND authcid="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth" authzid="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth"
5c6c094e conn=1002 op=0 BIND dn="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth" mech=EXTERNAL sasl_ssf=0 ssf=71
5c6c094e conn=1002 op=0 RESULT tag=97 err=0 text=
5c6c094e conn=1002 op=1 do_modify: invalid dn (cn=admin,)
5c6c094e conn=1002 op=1 RESULT tag=103 err=34 text=invalid DN
5c6c094e conn=1002 op=2 UNBIND
5c6c094e conn=1002 fd=12 closed
ldap_modify: Invalid DN syntax (34)
	additional info: invalid DN
modifying entry "cn=admin,"
*** /container/run/startup/slapd failed with status 34

*** Run commands before finish...
*** Killing all processes...
5c6c094e conn=1003 fd=12 ACCEPT from IP=<IP_ADDRESS>:58186 (IP=<IP_ADDRESS>:389)
5c6c094e conn=1003 op=0 do_bind: invalid dn (cn=admin,)
5c6c094e conn=1003 op=0 RESULT tag=97 err=34 text=invalid DN
5c6c094e conn=1003 op=1 UNBIND
5c6c094e conn=1003 fd=12 closed
ldap_bind: Invalid DN syntax (34)
	additional info: invalid DN
5c6c094e daemon: shutdown requested and initiated.
5c6c094e slapd shutdown: waiting for 0 operations/tasks to finish
5c6c094e slapd stopped.

Folks, again, please make sure you include all necessary information so that others do not waste time trying to figure out how to reproduce your issues. The problem here is linked to the fact that you use existing database and potentially configuration files.
I managed to reproduce it using the following scenario:
rm -rf TEST && mkdir -p TEST/config TEST/database
# 1st time used to create database and config
docker run --volume $PWD/TEST/database:/var/lib/ldap --volume $PWD/TEST/config:/etc/ldap/slapd.d --env LDAP_TLS=false --detach osixia/openldap:1.2.3
# IMPORTANT the following only works if osixia/openldap is the only running container
docker kill $(docker ps -q)
# This second run will fail
docker run --volume $PWD/TEST/database:/var/lib/ldap --volume $PWD/TEST/config:/etc/ldap/slapd.d --env LDAP_TLS=false --detach osixia/openldap:1.2.3 --loglevel debug

Forgot to mention that using 1.2.2 previous scenario works perfectly well

Yes, right. I have
    volumes:
      - ${VOLUMES_ROOT}/ldap-data:/var/lib/ldap
      - ${VOLUMES_ROOT}/ldap-config:/etc/ldap/slapd.d
      - ${COMPOSE_ROOT}/ldif:/container/service/slapd/assets/config/bootstrap/ldif/custom

I think I have identified the commit which introduce this issue: [
https://github.com/osixia/docker-openldap/commit/7e4eaa8370fb04a1ce4a1a6d1132a0f7f9bd8aef](url
https://github.com/osixia/docker-openldap/commit/7e4eaa8370fb04a1ce4a1a6d1132a0f7f9bd8aef)
@alexandrst88 @BertrandGouny

Please note that I have written a test for this issue:
https://github.com/obourdon/osixia-docker-openldap/commit/e41b2bc991375380b7456ff011a0287db8040fcf

Fix available https://github.com/osixia/docker-openldap/pull/294

thanks to @obourdon
Fix have been merged in 1.2.4 branch, and can be tested with image tag 1.2.4-dev
waiting your feedback to release 1.2.4 :)

@BertrandGouny thanks to you for the merges. Tested the 1.2.4-dev hot fix branch and seem working like a charm for me.
BTW I sometimes have test failures running on MacOSX (never got any on Linux) due to the fact that wait_process slapd is successful but then the call to ldapsearch does not succeed as the server is not fully launched yet (longer startup I guess) but this does not happen on a regular basis

@danwelcome may be this issue can now be closed ?

I pulled the 1.2.4-dev image and all seems good.  Thanks for resolving!

Thanks for fixing this works for my  (Y)

got same error with 1.2.4-dev image, so frustrating that the same yaml file was working before on 1.2.1 but not working now , neither on 1.2.4-dev. What are the reasons ?
i have prune system , volume , containers, images but still getiing same error.

@adarshaJha please note that 1.2.4-dev is now quite old
1.3.0 is the latest official version but you can also use 1.2.5 or 1.2.4
Debug logs and yams file would also be great for helping you.

@obourdon hi，obourdon. I get the same issue with version 1.3.0.  From above, you have committed the change in 1.2.4-dev and merged.  Why is it reproduced in version 1.3.0?  @BertrandGouny Didn't you merge obourdon's previous submission in version 1.3.0