Cannot read properties of undefined (reading 'prototype')

Versions + Platform
"@sentry/electron": "^4.0.0",
"electron": "^17.0.0",
Windows
Description
Trying to setup the main process:
[Window Title]
Error
[Main Instruction]
A JavaScript error occurred in the main process
[Content]
Uncaught Exception:
TypeError: Cannot read properties of undefined (reading 'prototype')
    at eval (webpack:///./node_modules/core-js/modules/web.dom-exception.stack.js?:42:74)
    at Object../node_modules/core-js/modules/web.dom-exception.stack.js (C:\kiosk-prot\dist_electron\index.js:5801:1)
    at __webpack_require__ (C:\kiosk-prot\dist_electron\index.js:20:30)
    at eval (webpack:///./node_modules/@sentry/utils/esm/supports.js?:11:100)
    at<EMAIL_ADDRESS>(C:\kiosk-prot\dist_electron\index.js:1800:1)
    at __webpack_require__ (C:\kiosk-prot\dist_electron\index.js:20:30)
    at eval (webpack:///./node_modules/@sentry/utils/esm/instrument.js?:8:70)
    at<EMAIL_ADDRESS>(C:\kiosk-prot\dist_electron\index.js:1620:1)
    at __webpack_require__ (C:\kiosk-prot\dist_electron\index.js:20:30)
    at eval (webpack:///./node_modules/@sentry/utils/esm/index.js?:22:72)

[OK]

This is my background.js ( main proc) :
import * as Sentry from "@sentry/electron/main";

Sentry.init({ dsn<EMAIL_ADDRESS>});

That looks like an interesting stack trace and I'd like to get the bottom of what's happening but I'll need a way to reproduce it locally. Do you have a minimal reproduction for this including the webpack config?
The stack trace suggests that it's caused by a call to instrument and then supportsNativeFetch in @sentry/utils but it's not clear how or why this code is being run from the main process. The stack trace looks truncated.

Since I've not heard back I'll close this issue for now but please do re-open this if you have any more information to help me track it down.


arch/risc-v: Refine Toolchain.defs

Summary
Refine risc-v Toolchain.defs firstly, and it tested on qemu-rv32.
And then:

Apply new Toolchain.defs to all risc-v based chips
Merge the common src for rv32/rv64 (riscv_syscall.S/riscv_fpu.S etc, in rv32im and rv64gc)
Apply new common src to qemu-rv32 and qemu-rv64
Migrate all risc-v based chips to new implementation and remove old

Impact
Refactor only.
Testing
Tested on qemu-rv32

Look like we should finish this PR: https://github.com/apache/incubator-nuttx/pull/2822

Look like we should finish this PR: #2822

This PR will be finished in next phase, I will pick it later.

Waiting for #5082 , and this patch will be rebased on it.

@no1wudi there are some build error need to fix first.

@no1wudi there are some build error need to fix first.

Fixed

This is giving me:
$ make menuconfig
/home/normanr/src/nuttx/nuttx/tools/../Make.defs:23: /home/normanr/src/nuttx/nuttx/tools/../arch/risc-v/src/rv32im/Toolchain.defs: No such file or directory
make: *** No rule to make target '/home/normanr/src/nuttx/nuttx/tools/../arch/risc-v/src/rv32im/Toolchain.defs'.  Stop.
/home/normanr/src/nuttx/nuttx/Make.defs:23: /home/normanr/src/nuttx/nuttx/arch/risc-v/src/rv32im/Toolchain.defs: No such file or directory
make: *** No rule to make target '/home/normanr/src/nuttx/nuttx/arch/risc-v/src/rv32im/Toolchain.defs'.  Stop.

Is there anything special I need to do to clear out old state? I just tried make menuconfig and make.

This patch merge Toolchain.defs from rv32im/rv64gc to common, so you may need make distclean and reconfigure again.

I couldn't run make distclean because of the same reason, also deleting it broke things worse. I had to re-copy the Make.defs from the arch directory, and that fixed things.

Yes, copy Mak.defs can fix this problem too.


Can we have common response class for throwing APIResponse errors?

Can we have common response class for throwing APIResponse errors?

Not sure what you mean.


PUT/PATCH/POST/DELETE methods types are of return type object

They should either be void or have a model
AB#8680

this is actually not related to the operation type but to the response itself, we're not handling 204's for example, we're also not handling binary response types.


[Bug]: cheap-[module]-source-map not work with react compiler

System Info
System:
OS: macOS 14.5
CPU: (10) arm64 Apple M1 Pro
Memory: 323.69 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.18.1 - ~/.nvm/versions/node/v18.18.1/bin/node
npm: 9.8.1 - ~/.nvm/versions/node/v18.18.1/bin/npm
pnpm: 9.3.0 - ~/.nvm/versions/node/v18.18.1/bin/pnpm
bun: 1.0.14 - ~/.bun/bin/bun
Browsers:
Brave Browser: <IP_ADDRESS>
Chrome: 119.0.6045.105
Edge: 119.0.2151.97
Safari: 17.5
npmPackages:
@rspack/cli: 0.7.2 => 0.7.2
@rspack/core: 0.7.2 => 0.7.2
@rspack/plugin-react-refresh: 0.7.2 => 0.7.2
Details
Now we are using react-compiler for our dev branch code with version 0.6.5, the source map can be generated from react-compiler with devtool: 'cheap-module-source-map'
But it doesn't work with version 0.7. The generated source maps are not compiled by compiler and breakpoint won't work.
If I change the devtool to 'source-map', breakpoint would work, but the generated source map is not compiled by compiler.
Here is the part of rspack config:
  devtool: 'cheap-module-source-map',
  module: {
    parser: {
      //...
    },
    rules: [
      ...getModuleJSAndTSRules({ useReactRefresh }),
    ...,
   ],
...

and the method getModuleJSAndTSRules:
getModuleJSAndTSRules: ({ useReactRefresh }) => {
    if (typeof useReactRefresh !== 'boolean') {
      throw new Error('[getModuleJSAndTSRules] - Please provide valid parameters')
    }

    const swcLoaderConfig = {
      loader: 'builtin:swc-loader',
      /** @type {import('@rspack/core').SwcLoaderOptions} */
      options: {
        sourceMap: true,
        env: {
          targets: 'defaults and fully supports es6-module',
        },
        jsc: {
          parser: {
            syntax: 'typescript',
            tsx: true,
            dynamicImport: true,
          },
          transform: {
            react: {
              runtime: 'automatic',
              refresh: useReactRefresh,
              development: useReactRefresh,
            },
          },
        },
      },
    }

    return [
      {
        test: /\.(js|ts|jsx)$/,
        include: resolve(__dirname, 'src'),
        /** @type {import('@rspack/core').RuleSetUse} */
        use: [swcLoaderConfig],
      },
      {
        test: /\.tsx$/,
        include: resolve(__dirname, 'src'),
        /** @type {import('@rspack/core').RuleSetUse} */
        use: (info) => {
          // Configuration based on https://github.com/rspack-contrib/rspack-examples/tree/main/rspack/react-compiler-babel-ts

          // Do not run react compiler on these places since they tend to often violate the react rules at the moment and/or are deprecated.
          if (
            !info.realResource.includes('/modules/privacy') &&
            !info.realResource.includes('/modules/delivery') &&
            !info.realResource.includes('/modules/mifleet')
          ) {
            return [
              swcLoaderConfig,
              {
                loader: 'babel-loader',
                options: {
                  plugins: [
                    [
                      'babel-plugin-react-compiler',
                      {
                        runtimeModule: 'react-compiler-runtime',
                        // panicThreshold: 'critical_errors',
                        // environment: {
                        //   enableResetCacheOnSourceFileChanges: true,
                        // },
                      },
                    ], // must run first!
                    ['@babel/plugin-syntax-typescript', { isTSX: true }],
                  ],
                },
              },
            ]
          }

          return [swcLoaderConfig]
        },
      },
    ]
  }

Reproduce link
react compiler rspack ts example
Reproduce Steps

git clone this repo

open the file package.json and update the rspack libs' version to 0.6.5

run pnpm i and pnpm run dev

open the page localhost:8080 and the inspector source tab

in the source map file, the react codes are compiled by compiler and set the breakpoint to the setData("data") line. Every time we click on the click button, breakpoint would work

stop the terminal and open the package.json, revert the rspack libs' version back to 0.7.2

do the same thing, the source map files are not compiled and break point not work:

I reproduced this locally and it turned out the cheap source map is not correct on both v0.6.5 and the latest version. Thank you for the heads-up.

@h-a-n-a @xfsnowind
I am also observing the same issue with "cheap-module-source-map".
I also reported a different issue below with source-maps and rspack, hopefully with the local repro for this issue you can also repro  https://github.com/web-infra-dev/rspack/issues/6714
Basically for webpack we are able to successfully use "eval-cheap-module-source-map".  But with rspack, with this option the devTools in edge browser do not have the folder structure maintained and everything seems to load with giant relative paths. The bug has images . Eventually the devTool simply freezes and then crashes.

Ok, here's what I discovered locally. The problem is in the rspack_sources, which was leveraged in the rspack_plugin_devtool here:
https://github.com/web-infra-dev/rspack/blob/bcb70bebf7c11b778c50f29b1417fe42fcae05a1/crates/rspack_plugin_devtool/src/lib.rs#L231-L232
Here we mapped the sources into code and source maps. columns was determined upon the devtool you passed in.
It's false if it's a cheap source map. This is where everything goes wrong.
A simplified version to reproduce it locally:

Set devtool as cheap source map, it can be cheap-source-map for example
Create two files, one imports the other one
The final generated assets showed the source map is wrong

@h-a-n-a what happens if you add "eval" in your local simplified repro ? Are you able to repro https://github.com/web-infra-dev/rspack/issues/6714 ?


Include license information

Have the license stated as a separate file or somewhere else.

This was added in<PHONE_NUMBER>07d1540e5e1344165917fe96fef1ad


Can ember-a11y be leveraged?

https://github.com/nathanhammond/ember-a11y
http://www.nathanhammond.com/building-for-accessibility

Also https://github.com/edenspiekermann/a11y-toggle


Added new translatable:find rake task and pt_BR translations

For #1339

Created a new rake task called translatable:find

Scans all files in 'app/', 'lib/' (except 'node_modules/'), 'config/' for translatable text (meaning anything using the gettext markup: _('some text') or n_('item', 'items', variable). (This works with Ruby string interpolation)
Makes a backup of the POT/PO files (git ignores these backups)
Adds any new text (translatable text that does not exist in the current POT/PO file) with the gettext #, fuzzy notation
Marks any text that appears in the current PO/POT file but is no longer found in the translatable text list as obsolete using the gettext notation of commenting the lines out: #msgid "some text" and #msgstr "some text translated

Also added tasks to the translatable.rake file to assist with adding/removing new languages from the DB and to compare an app.po file to the app.pot
Made a few minor modifications to files to work with the translatable:find script
Ran rake translatable:find to update the app.pot and app.po files
Added in the Português (Brasil) translations
Cleaned up obsolete and fuzzy entries in pt_BR, en_US, en_GB and app.pot

Caveats with the translatable:find text (we can fix later if it becomes an issue:

If you use '+' as string concatenation you need to have a space between them and the gettext markup (e.g. "This is " + _('translatable') + "text" instead of "This is "+_('translatable')+"text"
Do not use Ruby line continuations, place your entire text on one line. If you use line continuations the results are unpredictable.

Example of PO/POT after running translatable:find ('fuzzy' denotes a new entry, '#msgid & #msgstr' denote an obsolete entry):
 ...

msgid "Change affiliation"
msgstr ""

#, fuzzy
msgid "Changing your organisation will result in the loss of your administrative privileges."
msgstr ""

msgid "DMP Templates"
msgstr ""

#msgid "DMPRoadmap ('the tool', 'the system') is a tool developed by the DCC and CDL as a shared resource for the research community. It is hosted at CDL by the University of California Curation Center."
#msgstr ""

...

Happy for this to be merged but i dont have time today to run pull it locally to resolve the conflicts

Fixed merge conflicts.


Delete at -2 vote doesn't work

The delete post at -2 votes feature seems to be broken, take a look:
https://www.reddit.com/r/ProgrammerHumor/comments/brpnwx/pretty_sure_those_are_node_modules/eofk07p?utm_source=share&utm_medium=web2x
Also might want to look at implementing something for more accurate detection

Fixed the -2 vote not working


Feature/vanity update util

cc @DragosIorgulescu
I've cleaned up this little utility and added it to a utils folder with its own gem, zerigodns_utils.  Any time we think of little commandline utils to help manage zerigodns, I think we should add an issue here, and then add them to that gem.
Needs tests of course ;), but any comments on the overall approach to this structure before I write them?

This looks good, my only comment is this one


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_13fec65d-a029-442c-b6b3-8cb696e47c25/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_13fec65d-a029-442c-b6b3-8cb696e47c25.git

Docs Build status updates of commit 7db0bf4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-ServiceAccountCannotAccessRepository] Your repository https://github.com/VSC-Service-Account/docs-archive-test-source has enabled Docs Build service account. It seems that at least one of the accounts, e2ebd4, does not have Read permission to the repo. Please ask your repo admin to grant correct permission to service accounts (refer to this document: https://review.docs.microsoft.com/en-us/engineering/projects/ops/engdocs/how-to-grant-service-account-permission-in-your-repository?branch=master#ops-e2e-ppe) and then retry the build. Don't know who to contact? Refer https://repos.opensource.microsoft.com/VSC-Service-Account/repos/docs-archive-test-source/permissions/ to get admin list of the repo if the repo is in one of the organizations Microsoft owns.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


deleting Lists from "Your lists" section.

I guess there should be a way to delete Lists which we add to this section, so that we could delete any List we dont want anymore from this section .

There is a (not very intuitive) way to do it by sliding across:

oh ok got it !!

I have opened a bug to improve onboarding:
https://github.com/openfoodfacts/openfoodfacts-androidapp/issues/2979
Ok to close this one ?

ya sure !!


linopy workshop

Awesome notebooks! Is there interest to convert the pyomo notebook to a linopy version?
Happy to work on this if you think it's useful

Could be nice! But probably running in "dual mode" for a while.
The argument for pyomo in the course is that it is currently much more widely used and may be more useful to students.

Cool! Happy to build a replica for Linopy so you can run it in dual mode
-- Linopy will be useful for the PyPSA crowd we like to train :)


Updated validations.py python script.

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Close: #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Implement IsSet and AllKeys

What does this PR do?
Implement IsSet and AllKeys.
IsSet implementation is different from viper. We check if the keys exists where viper checked if the key existed and was different from nil. This was a edge case force by viper's internal use of map[string]interface{}.
Possible Drawbacks / Trade-offs
Unit test were added. This code is not used anywhere for now. We're building a replacement for viper and will QA it entirely, outside of unit-tests, once it's ready.

/merge

/remove

/merge

/merge


got "access denied" when pick up authenticator v0.6.0

I got an access denied when picking up authenticator v0.6.0. and during debug, found it is caused by https://github.com/kubernetes-sigs/aws-iam-authenticator/pull/416. in this PR, it changed how authenticator look up the arn https://github.com/kubernetes-sigs/aws-iam-authenticator/pull/416/files#diff-4dfc68b8a5ed36d024d6f6626d8aa66132e3c5702e882182396fbbcb1299cf01L68.
before this PR, it used the value passed in as the key of map to look up the mapping. the value passed in is canonical arn, and the key is also canonical arn as well, so it worked.
But this PR changed to compare the value passed in with the value part of map. the value passed in is canonical arn, and the value of map does not guarantee canonical arn, so it failed.
Could you please take a look and also provide an integration test case for 416 to validate?
@logandavies181

Hi @nnmin-aws, it's been 6 months since I've looked at this code so you'll have bear with me.
I don't believe I changed any logic with regards to canonicalized ARNs being passed to the mapper. AFAIK, for the File and EKSConfigMap mappers, the user is implicitly required to declare the ARNs in their Canonicalized form and then the server canonicalizes the ARN from incoming requests before passing to the mappers:
https://github.com/kubernetes-sigs/aws-iam-authenticator/blob/master/pkg/server/server.go#L363
I'm not familiar with this new mapper or your scenario so I'm not sure how the ARNs have been written in the config or how they're parsed into RoleMappings.
Could you perhaps provide some more info on the new mapper and your scenario? How does your new mapper work; and what is the input you've given it (config and sts caller identity)?

Hi @logandavies181 thank you for the reply.
yes the server canonicalizes the ARN from sts response and passs it to the mappers.
The change is this function https://github.com/kubernetes-sigs/aws-iam-authenticator/pull/416/files#diff-4dfc68b8a5ed36d024d6f6626d8aa66132e3c5702e882182396fbbcb1299cf01L68.
it previously use m.lowercaseUserMap[canonicalARN]. the key of m.lowercaseUserMap is also canonical format. so it works.
But this PR changed it to use the value part of m.userMap (see below). and it doesn't ensure userMapping includes a canonical ARN. So if userMapping.Matches(canonicalARN) can fail and caused access denied.
for _, userMapping := range m.userMap {
if userMapping.Matches(canonicalARN) {
return &config.IdentityMapping{
IdentityARN: canonicalARN,
Username:    userMapping.Username,
Groups:      userMapping.Groups,
}, nil
}
}

@nnmin-aws the input is still canonicalized, I just changed when the lowercasing happens because it seemed tidier at the time - instead of relying on the various mappers to do the lowercasing as they saved the keys.
I'm wondering if you're trying to map a non-canonicalized ARN in your config. Could you please share the config you're using?
And also a brief description of the new feature for my benefit? Just so I can understand how it works without diving into the code. I've got a day job after all 😄

If I understand the issue correctly, the problem is that a possibly untested behavior that EKS uses is the ability to put a non-canonical ARN in a config source, and before the SSO change this worked, but after the SSO change this no longer worked because of a change in ARN used as a key to lookup mapping.  This is from my memory of a conversation we had a week or so ago, please correct me if I'm wrong @nnmin-aws.

So in order to unblock releasing new versions that are compatible with EKS, we are currently planning on reverting #416 from the release-0.6 branch and then we can consider next steps and make the fix in the master branch.

@nckturner are you sure that's the case? I just tested on my EKS cluster and my sts assumed-role creds did not map successfully.
I'm pretty sure only Canonicalized role ARNs in the EKS configmap work currently in EKS

I actually haven't tested in the EKS configmap, but EKS actually puts this in a static file (config of backend mode type MountedFile) and uses it for the "cluster creator" identity.

Hmm ok I tested and I concur the behaviour has changed for the MountedFile case. In the absence of docs specifying the behaviour, there's only examples of canonical ARNs so I'd possibly consider it a bug on EKS's side if it's relying on that behaviour 😉
Anyway, given how much pain went into getting that PR merged in the first place, and how I'm pretty sure it'd be easier and cleaner to fix forward - how about I submit a PR cementing and documenting the behaviour or allowing users to specify non-canonicalized ARNs in their mappings? I can probably get that in tonght UTC+13
Probably just canonicalize the ARNs as they get added to the map

Probably just canonicalize the ARNs as they get added to the map

Yeah this should work, but it still might be worth reverting from release-0.6 in the meantime while we work on the fix and tests, documentation for it.  We will need to decide in the next couple days, and we will take into consideration any fix you propose.  And to be clear this is just for the most recent release branch, I think we should only revert master if this results in more complexity than expected and the fix is more than a week or two out.

bug on EKS's side

Yes usage of undocumented behavior could be considered a bug, but given the practical implication of migrating I think I'd argue it makes sense to try to keep the existing behavior intact.


S05.html not found

The problem
https://design.perl6.org/S05.html  is returning not found. This is the link in serveral doc pages on explaining LTM.
Also, it would be nice in proto section in grammars to state whether the alternations are LTM or traditional, ie first matching. I had to test to figure this out.
best,
michael
Suggestions

That site is down, and it wasn't brought up. I'll see what we can do about
it.

In the meantime, you might want to use https://github.com/perl6/specs.

Depends on perl6/problem-solving#68. It's a work in progress.

This finally came back; I'm closing.


Add "connecting" status when wallet goes from offline to online.

Need to add the status "connecting" when the wallet goes from offline status to online.
Actual: no "connecting" status.
video_2019-10-23_14-02-12.zip

checked


add clarifications to the dockerless building installation instructions

@agniiyer let me know if the suggested changes makes the building process more clear :)

@agniiyer let me know if the suggested changes makes the building process more clear :)


feat!: implement all select types

This PR implements all available select types:

ui.StringSelect
ui.UserSelect
ui.RoleSelect
ui.ChannelSelect
ui.MentionableSelect

RichSelect was renamed to BaseSelect and is now the base class for every Rich<Type>Select class
TODO:

[x] add docstrings

I modified the title to reflect that this PR is breaking, as it removes components.RichSelect in favour of components.RichStringSelect. Alternatively, we could alias RichStringSelect to RichSelect in the same way disnake does, but iirc disnake's alias is only there for backward compatibility, so I'm fine with leaving it as-is, too.

Yup. Looking good now. I'll test this soon:tm: (probably tomorrow, maybe tonight), and merge when I'm sure everything works.
Thanks ^^


Ruby 2.6

Ruby has been updated to 2.6.3 in macOS Catalina so let's use it everywhere.
CC @sjackman that we'll need the ARM bottles; I don't have any way of building
them.
Migrated from https://github.com/Homebrew/brew/pull/6554 as I need to debug GitHub Actions CI issues.
Fixes https://github.com/Homebrew/brew/issues/6551

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

@sjackman that we'll need the ARM bottles; I don't have any way of building them.

Feel free to mere without the ARM bottles, and I'll take a shot at building them tonight.

@sjackman Check the CI, unfortunately even the x86_64 bottles from Docker aren't working on Linux.

/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems.rb:661: [BUG] Segmentation fault at 0x0000000000000018
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-linux]

-- Control frame information -----------------------------------------------
c:0012 p:0008 s:0056 e:000053 BLOCK  /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems.rb:661 [FINISH]
c:0011 p:---- s:0049 e:000048 IFUNC
c:0010 p:---- s:0046 e:000045 CFUNC  :each
c:0009 p:---- s:0043 e:000042 CFUNC  :each_with_index
c:0008 p:0006 s:0039 e:000038 METHOD /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems.rb:660
c:0007 p:0024 s:0034 e:000033 METHOD /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/specification.rb:1555
c:0006 p:0047 s:0028 e:000027 METHOD /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/specification.rb:1421
c:0005 p:0006 s:0023 e:000022 BLOCK  /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_gem.rb: [FINISH]
c:0004 p:---- s:0020 e:000019 CFUNC  :synchronize
c:0003 p:0223 s:0016 e:000015 METHOD /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_gem.rb:
c:0002 p:0027 s:0006 e:000005 TOP    <internal:gem_prelude>:4 [FINISH]
c:0001 p:0000 s:0003 E:001620 (none) [FINISH]

-- Ruby level backtrace information ----------------------------------------
<internal:gem_prelude>:4:in `<internal:gem_prelude>'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_gem.rb:67:in `synchronize'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_gem.rb:68:in `block in gem'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/specification.rb:1421:in `activate'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/specification.rb:1555:in `add_self_to_load_path'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems.rb:660:in `load_path_insert_index'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems.rb:660:in `each_with_index'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems.rb:660:in `each'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems.rb:661:in `block in load_path_insert_index'

-- Machine register context ------------------------------------------------
 RIP: 0x00000000006b2d0e RBP: 0x000000000000100f RSP: 0x00007ffe8826bcc0
 RAX: 0x0000000000000000 RBX: 0x0000000000000000 RCX: 0x000000000000004b
 RDX: 0x0000000002c6e428 RDI: 0x0000000000000000 RSI: 0x000000000000100f
  R8: 0x00007f5aa2f9c141  R9: 0x0000000002d33b70 R10: 0x00007f5aa309bde0
 R11: 0x0000000000000000 R12: 0x0000000000000000 R13: 0x000000000000000f
 R14: 0x00007ffe8826bd08 R15: 0x00007f5aa309bd70 EFL: 0x0000000000010246

-- C level backtrace information -------------------------------------------
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6d08b3) [0x6d08b3]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6d0abb) [0x6d0abb]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x58aef1) [0x58aef1]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6621ce) [0x6621ce]
/lib/x86_64-linux-gnu/libpthread.so.0(__restore_rt+0x0) [0x7f5aa3fc8390]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6b2d0e) [0x6b2d0e]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_callable_method_entry+0x12) [0x6b7312]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_vm_search_method_slowpath+0x1f) [0x6b734f]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6c39aa) [0x6c39aa]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_vm_exec+0x18a) [0x6bb95a]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_yield_values2+0x278) [0x6be828]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x5803b2) [0x5803b2]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6ba28b) [0x6ba28b]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6be1f3) [0x6be1f3]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_yield+0x30) [0x6c0690]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_ary_each+0x3d) [0x54190d]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_vm_call0+0x36e) [0x6c100e]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6b8222) [0x6b8222]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_block_call+0x29) [0x6b8469]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x57b092) [0x57b092]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6b5742) [0x6b5742]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6bf4d6) [0x6bf4d6]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6c05db) [0x6c05db]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6c5a35) [0x6c5a35]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_vm_exec+0x18a) [0x6bb95a]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_yield+0x258) [0x6c08b8]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_ensure+0xd2) [0x5914c2]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6b5742) [0x6b5742]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6bf4d6) [0x6bf4d6]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6c05db) [0x6c05db]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6c5a35) [0x6c5a35]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(rb_vm_exec+0x18a) [0x6bb95a]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x6d9483) [0x6d9483]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x661181) [0x661181]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(ruby_process_options+0x83) [0x661aa3]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(ruby_options+0xc3) [0x592703]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x478351) [0x478351]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f5aa30bd830]
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby(0x478389) [0x478389]

-- Other runtime information -----------------------------------------------

* Loaded script: /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/bin/ruby

* Loaded features:

    0 enumerator.so
    1 thread.rb
    2 rational.so
    3 complex.so
    4 encdb.so
    5 trans/transdb.so
    6 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/x86_64-linux/rbconfig.rb
    7 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/compatibility.rb
    8 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/defaults.rb
    9 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/deprecate.rb
   10 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/errors.rb
   11 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/version.rb
   12 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/requirement.rb
   13 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/platform.rb
   14 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/basic_specification.rb
   15 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/stub_specification.rb
   16 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/delegate.rb
   17 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/rfc2396_parser.rb
   18 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/rfc3986_parser.rb
   19 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/common.rb
   20 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/generic.rb
   21 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/file.rb
   22 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/ftp.rb
   23 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/http.rb
   24 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/https.rb
   25 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/ldap.rb
   26 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/ldaps.rb
   27 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri/mailto.rb
   28 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/uri.rb
   29 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/specification_policy.rb
   30 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/util/list.rb
   31 stringio.so
   32 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/specification.rb
   33 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/exceptions.rb
   34 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/util.rb
   35 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/bundler_version_finder.rb
   36 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/dependency.rb
   37 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_gem.rb
   38 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/monitor.rb
   39 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb
   40 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/core_ext/kernel_warn.rb
   41 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems.rb
   42 /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3/lib/ruby/2.6.0/rubygems/path_support.rb

* Process memory map:

00400000-00d58000 r-xp 00000000 08:01 3638817                            /
00f57000-00f7b000 rwxp 00957000 08:01 3638817                            /
00f7b000-00f97000 rwxp 00000000 00:00 0
02bf7000-03014000 rwxp 00000000 00:00 0                                  [heap]
7f5aa0145000-7f5aa030e000 r-xs 00000000 08:01 2863203                    /
7f5aa030e000-7f5aa0d7d000 r-xs 00000000 08:01 3638817                    /
7f5aa0d7d000-7f5aa0d93000 r-xp 00000000 08:01 2863224                    /
7f5aa0d93000-7f5aa0f92000 ---p 00016000 08:01 2863224                    /
7f5aa0f92000-7f5aa0f93000 rwxp 00015000 08:01 2863224                    /
7f5aa0f93000-7f5aa309d000 rwxp 00000000 00:00 0
7f5aa309d000-7f5aa325d000 r-xp 00000000 08:01 2863203                    /
7f5aa325d000-7f5aa345d000 ---p 001c0000 08:01 2863203                    /
7f5aa345d000-7f5aa3461000 r-xp 001c0000 08:01 2863203                    /
7f5aa3461000-7f5aa3463000 rwxp 001c4000 08:01 2863203                    /
7f5aa3463000-7f5aa3467000 rwxp 00000000 00:00 0
7f5aa3467000-7f5aa3469000 r-xp 00000000 08:01 2863297                    /
7f5aa3469000-7f5aa3668000 ---p 00002000 08:01 2863297                    /
7f5aa3668000-7f5aa3669000 r-xp 00001000 08:01 2863297                    /
7f5aa3669000-7f5aa366a000 rwxp 00002000 08:01 2863297                    /
7f5aa366a000-7f5aa3772000 r-xp 00000000 08:01 2863235                    /
7f5aa3772000-7f5aa3971000 ---p 00108000 08:01 2863235                    /
7f5aa3971000-7f5aa3972000 r-xp 00107000 08:01 2863235                    /
7f5aa3972000-7f5aa3973000 rwxp 00108000 08:01 2863235                    /
7f5aa3973000-7f5aa397c000 r-xp 00000000 08:01 2863211                    /
7f5aa397c000-7f5aa3b7b000 ---p 00009000 08:01 2863211                    /
7f5aa3b7b000-7f5aa3b7c000 r-xp 00008000 08:01 2863211                    /
7f5aa3b7c000-7f5aa3b7d000 rwxp 00009000 08:01 2863211                    /
7f5aa3b7d000-7f5aa3bab000 rwxp 00000000 00:00 0
7f5aa3bab000-7f5aa3bae000 r-xp 00000000 08:01 2863216                    /
7f5aa3bae000-7f5aa3dad000 ---p 00003000 08:01 2863216                    /
7f5aa3dad000-7f5aa3dae000 r-xp 00002000 08:01 2863216                    /
7f5aa3dae000-7f5aa3daf000 rwxp 00003000 08:01 2863216                    /
7f5aa3daf000-7f5aa3db6000 r-xp 00000000 08:01 2863277                    /
7f5aa3db6000-7f5aa3fb5000 ---p 00007000 08:01 2863277                    /
7f5aa3fb5000-7f5aa3fb6000 r-xp 00006000 08:01 2863277                    /
7f5aa3fb6000-7f5aa3fb7000 rwxp 00007000 08:01 2863277                    /
7f5aa3fb7000-7f5aa3fcf000 r-xp 00000000 08:01 2863271                    /
7f5aa3fcf000-7f5aa41ce000 ---p 00018000 08:01 2863271                    /
7f5aa41ce000-7f5aa41cf000 r-xp 00017000 08:01 2863271                    /
7f5aa41cf000-7f5aa41d0000 rwxp 00018000 08:01 2863271                    /
7f5aa41d0000-7f5aa41d4000 rwxp 00000000 00:00 0
7f5aa41d4000-7f5aa41fa000 r-xp 00000000 08:01 2863183                    /
7f5aa422e000-7f5aa4250000 r-xs 00000000 08:01 2863271                    /
7f5aa4250000-7f5aa4257000 r-xs 00000000 08:01 2864074                    /
7f5aa4257000-7f5aa43ef000 r-xp 00000000 08:01 3380710                    /
7f5aa43ef000-7f5aa43f4000 rwxp 00000000 00:00 0
7f5aa43f8000-7f5aa43f9000 rwxp 00000000 00:00 0
7f5aa43f9000-7f5aa43fa000 r-xp 00025000 08:01 2863183                    /
7f5aa43fa000-7f5aa43fb000 rwxp 00026000 08:01 2863183                    /
7f5aa43fb000-7f5aa43fc000 rwxp 00000000 00:00 0
7ffe87a77000-7ffe88276000 rwxp 00000000 00:00 0                          [stack]
7ffe883c3000-7ffe883c6000 r--p 00000000 00:00 0                          [vvar]
7ffe883c6000-7ffe883c7000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: https://www.ruby-lang.org/bugreport.html

Error: Forked child process failed: pid 19720 SIGABRT (signal 6) (core dumped)

https://github.com/Homebrew/brew/pull/6556/checks?check_run_id=252191345#step:5:438

How exciting. It's failing with a SIGABRT, which is usually intentional by the program itself calling abort(). The C level backtrace information doesn't appear complete though. I'll take a look into it tonight.

@sjackman Perfect, thanks. Given no-one is using these bottles yet I feel safe unpublishing/republishing them if necessary (if we need, as I suspect, homebrew-portable-ruby changes).

most files are not changed

There's no problem with that. What are you trying to say here?

Failed examples:

rspec ./test/cmd/reinstall_spec.rb:11 # brew reinstall reinstalls a Formula
rspec ./test/cmd/migrate_spec.rb:10 # brew migrate migrates a renamed Formula
rspec ./test/cmd/upgrade_spec.rb:10 # brew upgrade upgrades a Formula and cleans up old versions
rspec ./test/cmd/install_spec.rb:10 # brew install installs formulae
rspec ./test/cmd/install_spec.rb:19 # brew install can install keg-only Formulae
rspec ./test/cmd/install_spec.rb:32 # brew install can install HEAD Formulae
rspec ./test/dev-cmd/ruby_spec.rb:10 # brew ruby executes ruby code with Homebrew's libraries loaded

I can reproduce brew tests failing for these seven tests in Docker on my Macbook Pro.
brew install hello works as expected, as does brew install -s hello.
That's as far as I've gotten so far. I'm not yet sure why brew install is failing within brew tests.

I can reproduce brew tests failing for these seven tests in Docker on my Macbook Pro.
brew install hello works as expected, as does brew install -s hello.
That's as far as I've gotten so far. I'm not yet sure why brew install is failing within brew tests.

@sjackman I think we need to rebuild the bottle in a different configuration if it's failing on the C level like this at all. I'm also open to options for how best to handle this given it's currently blocking us matching the Ruby version on macOS which means different behaviour on different platforms (and brew tests failing there).

CC @mistydemeo for her wizardry and general smarts

I'm cautiously optimistic that PR https://github.com/Homebrew/brew/pull/6569 resolves the broken portable-ruby 2.6.3 bottle on Linux. The bottle will need to be rebuilt after merging that PR.

I'm cautiously optimistic that PR #6569 resolves the broken portable-ruby 2.6.3 bottle on Linux. The bottle will need to be rebuilt after merging that PR.

Unfortunately not. It's not a patchelf issue it seems.


[SPARK-22196][Core] Combine multiple input splits into a HadoopPartition

What changes were proposed in this pull request?
Spark native read path allows tuning the partition size based on spark.sql.files.maxPartitionBytes and spark.sql.files.openCostInBytes. It would be useful to add a similar functionality/behavior to HadoopRDD, i.e, pack multiple input splits into a single partition based on maxPartitionBytes and openCostInBytes. We have had several use-cases to merge small files by coalescing them by size to reduce the number of tasks launched.
How was this patch tested?
Added a unit test. It was also tested manually in a few production jobs.

Can one of the admins verify this patch?

@davies Can you please take a look?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

I'm closing PR because (a) it's been inactive for a couple of years and (b) the corresponding JIRA was bulk closed.


Cleanup

in progress...

Make sure the tests pass. It looks like you're not passing the waypoints correctly.

@adscib I took a look at the failed test. In the render_frame, it requires the number of waypoint sets should be the same as the number of cameras. I think this constraints is for the ego-centric birdview rendering during the training.
The code I added in this PR is to generate a global birdview containing the waypoints, so the number of camera is always one, while the number of waypoint sets depends on the agent num (2 in the test).
But currently, it's hard to distinguish the ego-centric view and global view inside the render_frame, could we add a bool parameter to indicate it directly? Or maybe you have some better ideas.

I think if you want to show waypoints for all agents to the same camera, you should concatenate waypoint sets across the agent dimension, meaning that all cameras would see all the waypoints as one set. This logically makes sense, since visually there is no indication which waypoint belongs to which agent, as far as I remember. Perhaps @lioutasb wants to weigh in on how this interface is intended to be used.


👌 IMPROVE: Resetting directive numbering between different directives

Having a separate enumerable node for each directive type, so that they have their separate numbering schemes.
NOTE: Numbering resets between directives but not between different pages.

Codecov Report

Merging #62 (97e6a1c) into master (60cd7f6) will increase coverage by 0.34%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #62      +/-   ##
==========================================
+ Coverage   96.46%   96.81%   +0.34%
==========================================
  Files           5        5
  Lines         283      314      +31
==========================================
+ Hits          273      304      +31
  Misses         10       10

Flag
Coverage Δ

pytests
96.81% <100.00%> (+0.34%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sphinx_proof/proof_type.py
100.00% <ø> (ø)

sphinx_proof/__init__.py
91.83% <100.00%> (+0.92%)
:arrow_up:

sphinx_proof/directive.py
100.00% <100.00%> (ø)

sphinx_proof/domain.py
100.00% <100.00%> (ø)

sphinx_proof/nodes.py
94.00% <100.00%> (+1.89%)
:arrow_up:

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 60cd7f6...97e6a1c. Read the comment docs.

@AakashGfude this is looking good.

[ ] You should remove _build folders and add it to the .gitignore

@AakashGfude this is looking good.

[ ]  You should remove _build folders and add it to the .gitignore

🤦🏻♂  Thanks @mmcky


Register HashQuark Validator

Network Choice
nemeton-1
Who are you?
HashQuark is a staking service provider under HashKey, whose parent company is Wanxiang Group, an early backer of Ethereum. We’ve been running over 50 nodes, such as Ethereum, Cosmos, EVMOS, Juno and Polkadot.


Do you want to copy existing state to the new backend?

Terragrunt wants to copy state to a new backend each run.
2018/07/02 16:57:54 [DEBUG] command: asking for input: "Do you want to copy existing state to the new backend?"
Do you want to copy existing state to the new backend?
  Pre-existing state was found while migrating the previous "s3" backend to the
  newly configured "local" backend. No existing state was found in the newly
  configured "local" backend. Do you want to copy this state to the new "local"
  backend? Enter "yes" to copy and "no" to start with an empty state.

No changes to the backend have been made.
Debug Output
Test Repo
Steps to reproduce:

Update backend bucket ./terraform/live/terraform.tfvars
Run terragrunt plan in ./terraform/live/dev/echo/

What version of Terragrunt? Could you paste the full log output?

@brikis98 the the log output is here Debug Output.
State is never pushed to S3 and S3 remains empty. This seems like a config issue on my end but 2 days of learning Terragrunt and I don't see where I've gone wrong.

terragrunt version v0.15.2
Terraform v0.11.7

During the init the backend is specified by the command-line flags:
[terragrunt] Running command: terraform init \
-backend-config=region=us-west-2 \
-backend-config=dynamodb_table=terraform-locks \
-backend-config=encrypt=false \
-backend-config=bucket=lz-terragrunt-terraform-state \
-backend-config=key=dev/vpc-eip/terraform.tfstate \
-from-module=file:///Users/davidneudorfer/dev/lrnz-ops/terraform/modules/aws/eip \
/Users/davidneudorfer/.terragrunt/229HQvoqVyk4F6er0XeSM8ci_wk/QG6HYkqiY7ug8JgGU0H6AdPSmRw

This is written to the state file but when plan runs Terragrunt doesn't fill in the backend details and Terraform is left thinking I am changing the backend.

@brikis98 I've gotten my env working and I'll post a follow up asap. It took reworking how I was dealing with modules but I'm glad I stuck with it. Hopefully my learnings can prevent others from going down a similar rabbit hole.

Did you have a backend "s3" { ... } block in your Terraform module?
Looking forward to hearing what you found!

@davidneudorfer I'm running in to a similar problem. Can you update us?

I have simular issue when changing Environment, eg:

I am working with prod env, here is all ok:

TF_VAR_env=prod terragrunt apply

I'm swithcing to another environment and receive the confirmation dialog:
TF_VAR_env=dev terragrunt apply

Do you want to overwrite the state in the new backend with the previous state?
Enter "yes" to copy and "no" to start with the existing state in the newly
configured "s3" backend.
Enter a value: no

The problem here is that a remote Bucket under the dev name will be written to the state prod. Then the code with dev variables will change the state of prod resources. This is very dangerous.
All environments exist and were created before.

@augustgerro This is not typical terragrunt usage, as the canonical usage is separating your environments into separate terragrunt.hcl files and folders (see our example in Keep your terraform code DRY).
What's happening here is the same thing that would happen if you modify the terraform remote state in the same terraform folder:

When you first run prod, terragrunt creates the source dir in .terragrunt-cache and calls terraform init. This sets up the state tracker in .terraform of the working dir. Then terragrunt proceeds to call terraform apply.
When you then switch to dev, terragrunt will reuse the source dir in the .terragrunt-cache and call terraform init again with the new setting. However, since the new remote state conflicts with the state that terraform expects, you get the warning. This happens because the old state is tracked in the same .terraform folder that is being used.

This is one of the reasons why we use different folders for each environment, as it creates completely different working directories per environment.
If you want to keep your current organization, the best way to handle this is to use the --terragrunt-source-update flag so that terragrunt will always wipe the working dir and start clean each time.

Closing as stale. If you are still running into this issue, please open a new issue, with an updated code sample that reproduces the issue. Thanks!


Crash preventation

Issue link: https://github.com/firebase/firebase-ios-sdk/issues/4659

@Guserx Thanks for the suggestions.
We'd appreciate if you'd send separate PRs for different pods. In this case, a separate PR for the Installations versus Crashylytics would help with the review process.
For the Installations change, please investigate the subsequent CI failure in https://travis-ci.org/firebase/firebase-ios-sdk/jobs/635952938
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/Messaging/Tests/FIRMessagingContextManagerServiceTest.m:85: error: -[FIRMessagingContextManagerServiceTest testMessageWithFutureStartTime] : ((self.scheduledLocalNotifications.count) equal to (1)) failed: ("0") is not equal to ("1")
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/Messaging/Tests/FIRMessagingContextManagerServiceTest.m:170: error: -[FIRMessagingContextManagerServiceTest testTimedNotificationsUserInfo] : ((self.scheduledLocalNotifications.count) equal to (1)) failed: ("0") is not equal to ("1")
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/Messaging/Tests/FIRMessagingContextManagerServiceTest.m:175: error: -[FIRMessagingContextManagerServiceTest testTimedNotificationsUserInfo] : ((notification.userInfo[messageIdentifierKey]) equal to (messageIdentifier)) failed: ("(null)") is not equal to ("fcm-cm-test1")
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/Messaging/Tests/FIRMessagingContextManagerServiceTest.m:176: error: -[FIRMessagingContextManagerServiceTest testTimedNotificationsUserInfo] : ((notification.userInfo[customDataKey]) equal to (customData)) failed: ("(null)") is not equal to ("world")

@GUserx Thanks for the suggestions.
We'd appreciate if you'd send separate PRs for different pods. In this case, a separate PR for the Installations versus Crashylytics would help with the review process.
For the Installations change, please investigate the subsequent CI failure in https://travis-ci.org/firebase/firebase-ios-sdk/jobs/635952938
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/Messaging/Tests/FIRMessagingContextManagerServiceTest.m:85: error: -[FIRMessagingContextManagerServiceTest testMessageWithFutureStartTime] : ((self.scheduledLocalNotifications.count) equal to (1)) failed: ("0") is not equal to ("1")
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/Messaging/Tests/FIRMessagingContextManagerServiceTest.m:170: error: -[FIRMessagingContextManagerServiceTest testTimedNotificationsUserInfo] : ((self.scheduledLocalNotifications.count) equal to (1)) failed: ("0") is not equal to ("1")
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/Messaging/Tests/FIRMessagingContextManagerServiceTest.m:175: error: -[FIRMessagingContextManagerServiceTest testTimedNotificationsUserInfo] : ((notification.userInfo[messageIdentifierKey]) equal to (messageIdentifier)) failed: ("(null)") is not equal to ("fcm-cm-test1")
- NOTE  | [iOS] xcodebuild:  /Users/travis/build/firebase/firebase-ios-sdk/Example/Messaging/Tests/FIRMessagingContextManagerServiceTest.m:176: error: -[FIRMessagingContextManagerServiceTest testTimedNotificationsUserInfo] : ((notification.userInfo[customDataKey]) equal to (customData)) failed: ("(null)") is not equal to ("world")

@paulb777 Thanks for your comment.
I did revert to previous version of this commit.

Thanks. Note that CI did run for Crashlytics because of the issue fixed by #4663

@GUserx thanks for the PR! We're going to run through some validation and review this PR later in the week after we've gone through with the first release

@GUserx thanks for the PR! We're going to run through some validation and review this PR later in the week after we've gone through with the first release

Got it. Thank you for info.


Don't use internal APIs for GPU memory allocation

Lux is currently using Realm::get_runtime() and Realm::RuntimeImpl::get_memory_impl from realm/runtime_impl.h, and Realm::Cuda::GPUFBMemory::alloc_bytes and Realm::Cuda::GPUFBMemory::get_direct_ptr from realm/cuda/cuda_module.h to allocate GPU memory that needs to persist past the lifetime of the allocating task (e.g. see https://github.com/LuxGraph/Lux/blob/master/pagerank/pagerank_gpu.cu#L269-L277). These are apparently Realm-internal interfaces, and instead the API in realm/instance.h, or possibly the new Legion variable-size allocation API should be preferred.

@manopapad Thanks for the suggestion! Are you referring to the create_instance calls in realm/instance.h? I didn't pay special attention to the new variable-size allocation calls in Legion. Do you have a pointer to related documents/discussions?

Are you referring to the create_instance calls in realm/instance.h?

That's the one. Based on the discussion at https://github.com/StanfordLegion/legion/issues/973, it sounds like that's the "officially supported" function for doing what you need. No idea how you're supposed to use it though :-)

I didn't pay special attention to the new variable-size allocation calls in Legion. Do you have a pointer to related documents/discussions?

I don't think there's much documentation available, but this test showcases the API. Unfortunately it looks like it's only available on the control_replication branch.

@jiazhihao can you confirm which Realm interface(s) you're using for this?  MemoryImpl::alloc_bytes has been gone for over a year now, and a change that should be merging into the master branch shortly moves Realm::Cuda::GPUFBMemory to a different header file, so if you are still directly using Realm for device memory allocation, it needs to be going through the public interface.

We use Realm::RegionInstance::create_instance for allocating GPU memory inside a task. Will that still work after the merge? The code snippet is as follows.
  Rect1 bounds(Point1(0), Point1(0));
  std::vector<size_t> field_sizes;
  field_sizes.push_back(model->config.simulator_work_space_size);
  Realm::RegionInstance::create_instance(simulatorInst,
      memory, bounds, field_sizes, 0, Realm::ProfilingRequestSet()).wait();
  base_ptr = (char*)simulatorInst.pointer_untyped(0, sizeof(char));
  capacity = model->config.simulator_work_space_size;

Yes, that should still work fine.  Thanks for checking.


Windows CI support: Add unit tests only to the PR gate - start with buildTools only.

Is your feature request related to a problem? Please describe.
coming from #1448  wherein goal is to add unit tests only to the PR gate,  start with buildTools only for Windows.

@mch2  do we need do any work for this issue?

I think we should close this issue.  Few if any these test suites are able to run on GH as a gate, and provide little value.  We should instead move the entire check on PR from Jenkins.


[Enhancement]: Hunt Your Card Game

Is your enhancement request related to a problem? Please describe.➕
Game enhancement

Images are not shown properly
Cards are not kept their right position and not aligned

https://github.com/kunjgit/GameZone/assets/114330097/4bceb2aa-3bb8-455a-a95a-f2a30c0df441
Describe the solution you'd like
Solution steps

Setting the links of the images.
Adding a good ui for the users.
Adding winning and losing sounds to make it more interactive.

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Avdhesh-Varshney !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @Avdhesh-Varshney ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


serial command 'serial()' TypeError

pyB12MPS v1.0.6
Firmware v1.5.3
mps.serial()

returns
TypeError: 'module' object is not callable

The function to query the serial number is "mps.serialNumber()". This is different from the serial command which is sent to the MPS ("serial").


Add missing ports to istio reseved ports list

What this PR does / why we need it:
istio documentation specify the list of ports istio is using - https://istio.io/latest/docs/ops/deployment/requirements/#ports-used-by-istio
kubevirt is using this list to avoid forwarding traffic to the vm on those ports in case of masquerade binding. And to avoid opening socket on those ports in case of passt.
Some ports were missing in the list kubevirt is using, this PR adding the missing ports.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/hold
Helping Tide.
The storage lane is currently broken. https://github.com/kubevirt/kubevirt/pull/9135 should fix this.
Feel free to remove the hold once this is merged.

/hold cancel


Some entries from awesome-chatgpt-prompts/main/prompts.csv don't show up in telescope.nvim for selection

Hello @jackMort . Hope you're doing well. Thank you for creating chatgpt.nvim.
Description
I realized that the following entries from prompts.csv are not displayed in telescope.nvim for selection:
UX/UI Developer
IT Architect
Developer Relations consultant
Doctor
AI Trying to Escape the Box
Buddha

Steps to reproduce

config:

{
  "jackMort/ChatGPT.nvim",
    event = "VeryLazy",
    config = function()
      require("chatgpt").setup()
    end,
    dependencies = {
      "MunifTanjim/nui.nvim",
      "nvim-lua/plenary.nvim",
      "nvim-telescope/telescope.nvim"
    }
}

:ChatGPTActAs

Please see the picture above

Isolated entries
I have then isolated the entries as below:
"act","prompt"
"UX/UI Developer","I want you to act as a UX/UI developer. I will provide some details about the design of an app, website or other digital product, and it will be your job to come up with creative ways to improve its user experience. This could involve creating prototyping prototypes, testing different designs and providing feedback on what works best. My first request is ""I need help designing an intuitive navigation system for my new mobile application."""
"IT Architect","I want you to act as an IT Architect. I will provide some details about the functionality of an application or other digital product, and it will be your job to come up with  ways to integrate it into the IT landscape. This could involve analyzing business requirements, performing a gap analysis and mapping the functionality of the new system to the existing IT landscape. Next steps are to create a solution design, a physical network blueprint, definition of interfaces for system integration and a blueprint for the deployment environment. My first request is ""I need help to integrate a CMS system."""
"Buddha","I want you to act as the Buddha (a.k.a. Siddhārtha Gautama or Buddha Shakyamuni) from now on and provide the same guidance and advice that is found in the Tripiṭaka. Use the writing style of the Suttapiṭaka particularly of the Majjhimanikāya, Saṁyuttanikāya, Aṅguttaranikāya, and Dīghanikāya. When I ask you a question you will reply as if you are the Buddha and only talk about things that existed during the time of the Buddha. I will pretend that I am a layperson with a lot to learn. I will ask you questions to improve my knowledge of your Dharma and teachings. Fully immerse yourself into the role of the Buddha. Keep up the act of being the Buddha as well as you can. Do not break character. Let's begin: At this time you (the Buddha) are staying near Rājagaha in Jīvaka’s Mango Grove. I came to you, and exchanged greetings with you. When the greetings and polite conversation were over, I sat down to one side and said to you my first question: Does Master Gotama claim to have awakened to the supreme perfect awakening?"

Add the following to config:

{
  "jackMort/ChatGPT.nvim",
    event = "VeryLazy",
    config = function()
      require("chatgpt").setup({
          predefined_chat_gpt_prompts = "https://gist.githubusercontent.com/kohane27/0758d6575aeec909227493224c80c75d/raw/b26952f3161729bd9923a37925199313ba6d1a24/prompt_v7.csv"
        })
    end,
    dependencies = {
      "MunifTanjim/nui.nvim",
      "nvim-lua/plenary.nvim",
      "nvim-telescope/telescope.nvim"
    }
}

reload nvim and :ChatGPTActAs and there is no entry in telescope.nvim for selection

What I have tried
I thought it's the length issue. But longer prompts like "Technology Transferer" show up without problem.
Any input is much appreciated. Thank you.

@jackMort
TL;DR: if the "prompt" contains the word digit or Aṅguttaranikāya or word stem sav (as in saving), the whole entry seems to be discarded. Very weird ikr. Please see below.
Description
If the "prompt" contains the word "digit" or word stem "sav" (as in saving) in the prompt, it won't work.
The reason why "UX/UI Developer" and "IT Architect" don't work is because they both contain the word "digit".
Doesn't work:
"act","prompt"
"UX/UI Developer","digit"

Work:
"act","prompt"
"UX/UI Developer","digi"

The reason why "Buddha" doesn't work is because it contains the word Aṅguttaranikāya.
Another example:
Doesn't work:
"act","prompt"
"Instructor","savi"

Work:
"act","prompt"
"Instructor","sav"

There doesn't seem to have any patterns to it.
How I debugged
If you're a user facing this issue, just take the prompt and test out sentence by sentence, until you narrow down to the buggy word.
To quickly debug, point predefined_chat_gpt_prompts to a local file so you don't need to fetch or update from some online csv or gist:
{
  "jackMort/ChatGPT.nvim",
    event = "VeryLazy",
    config = function()
      require("chatgpt").setup({
            predefined_chat_gpt_prompts = "file:///" .. vim.fn.expand("~") .. "/.config/nvim/gpt_prompt.csv",
        })
    end,
    dependencies = {
      "MunifTanjim/nui.nvim",
      "nvim-lua/plenary.nvim",
      "nvim-telescope/telescope.nvim"
    }
}

Thank you.

I did some more testing and have the following finding:
"act","prompt"
"test1","find docs"
"test2","virtual doctor"

These two "prompt" won't show up.
"test1" is taken from "Developer Relations consultant".
"test2" is taken from "Doctor".
Hopefully it helps.


[nova-compute / ovn-chassis] Upgrade 'ovn-chassis' from '22.03/stable' to '22.09/stable' cause RuntimeError

When COU refresh ovn-chassis from '22.03/stable' to '22.09/stable' during Jammy/Yoga -> Jammy/Zed upgrade, the ovn-chassis charm goes into error state with RuntimeError:
unit-ovn-chassis-0: 02:41:51 ERROR unit.ovn-chassis/0.juju-log nova-compute:43: Hook error:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms/reactive/__init__.py", line 74, in main
    bus.dispatch(restricted=restricted_mode)
  File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms/reactive/bus.py", line 390, in dispatch
    _invoke(other_handlers)
  File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms/reactive/bus.py", line 359, in _invoke
    handler.invoke()
  File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms/reactive/bus.py", line 181, in invoke
    self._action(*args)
  File "/var/lib/juju/agents/unit-ovn-chassis-0/charm/reactive/layer_openstack.py", line 134, in default_request_certificates
    with charm.provide_charm_instance() as instance:
  File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms_openstack/charm/core.py", line 99, in __enter__
    return BaseOpenStackCharm.singleton
  File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms_openstack/charm/core.py", line 352, in singleton
    _singleton = get_charm_instance(release=release,
  File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms_openstack/charm/core.py", line 165, in get_charm_instance
    return (_get_charm_instance_function or default_get_charm_instance)(
  File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms_openstack/charm/core.py", line 133, in default_get_charm_instance
    raise RuntimeError(
RuntimeError: Release zed is not a known OpenStack release?

unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed Traceback (most recent call last):
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/charm/hooks/nova-compute-relation-changed", line 22, in <module>
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     main()
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms/reactive/__init__.py", line 74, in main
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     bus.dispatch(restricted=restricted_mode)
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms/reactive/bus.py", line 390, in dispatch
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     _invoke(other_handlers)
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms/reactive/bus.py", line 359, in _invoke
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     handler.invoke()
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms/reactive/bus.py", line 181, in invoke
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     self._action(*args)
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/charm/reactive/layer_openstack.py", line 134, in default_request_certificates
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     with charm.provide_charm_instance() as instance:
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms_openstack/charm/core.py", line 99, in __enter__
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     return BaseOpenStackCharm.singleton
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms_openstack/charm/core.py", line 352, in singleton
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     _singleton = get_charm_instance(release=release,
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms_openstack/charm/core.py", line 165, in get_charm_instance
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     return (_get_charm_instance_function or default_get_charm_instance)(
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed   File "/var/lib/juju/agents/unit-ovn-chassis-0/.venv/lib/python3.10/site-packages/charms_openstack/charm/core.py", line 133, in default_get_charm_instance
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed     raise RuntimeError(
unit-ovn-chassis-0: 02:41:51 WARNING unit.ovn-chassis/0.nova-compute-relation-changed RuntimeError: Release zed is not a known OpenStack release?
unit-ovn-chassis-0: 02:41:51 ERROR juju.worker.uniter.operation hook "nova-compute-relation-changed" (via explicit, bespoke hook script) failed: exit status 1

Environment: deployed with stsstack-bundle using ./generate-bundle.sh --name cou -r yoga -s jammy --ceph --run
Note: ovn-chassis is a subordinate to nova-compute

This has the same cause as https://github.com/canonical/charmed-openstack-upgrader/issues/466#issuecomment-2205600149


Release is not gzipped

Describe the bug
Release is named .tar.gz but is actually a plain tar archive, not gzipped.
To Reproduce
Is the issue reproducible? Yes
Steps to reproduce the behavior:
A clear and concise description of the reproduce steps.
wget https://github.com/uber/cadence/releases/download/v0.18.0/docker.tar.gz
tar -xvzf docker.tar.gz

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now

tar -xvf docker.tar.gz
(succeeds)

Expected behavior
Release should unzip.

Thanks for catching this @jacobsevart
I just updated the 0.18.0 release so it's gzipped now. Please try again.

Thanks for catching this @jacobsevart
I just updated the 0.18.0 release so it's gzipped now. Please try again.

Thanks!

Thanks!


Backend Language 리서치

리소스

JAVA(JDK)

Spring Boot

Lombok

MapStruct

Spring Security

JWT

Sops

DB MySQL

OpenSearch(with dependency)

Loki

Redis / ElasticCache

Nginx

LogStash / Fluentbit

Doker

K8s

Grafana, Prometheus

k6

S3(with dependency)

Open AI / Ollama


Use a newer version of askalono so ISC is detected

It's been some time without a formal release of askalono. Latest is 0.3.0 (Sep 27, 2018), but some changes have been made to the master branch. In order to support ISC, we have to use a newer version which sadly is not available from crates.io.
In addition I've added some code to remove duplicates if multiple files refer to exactly the same license.
Fixes #123

BTW license cache had to be updated because the format has changed. In order to avoid having to maintain the branch dynamic-license-cache, I would suggest using askalono-cli to generate it when necessary.

Yes, it's indeed quite unfortunate they didn't release a new version for more than a year especially if they fixed bugs since then...
Thanks a lot for your fix @ebroto

Well, turns out I can't cargo publish with an un-released dependancy...

Damn, I was not aware of this limitation!
I've opened an issue in amzn/askalono#47 and it seems we will have a new version soon :tada:

Sorry for the huuuuge delta between releases -- 0.4.0 is up now, and I'm going to try to pay attention to making smaller, faster releases.
0.4.0 has some minor breaking changes that include dropping Results where unnecessary and removing a deprecated field. Shouldn't be anything difficult to update to, but I'm happy to help if you need it.


Unable to open save

Error
An exception was thrown (press Ctrl+C to copy):
System.NotImplementedException: don't know how to read stat type 49
at Gibbed.BorderlandsOz.FileFormats.PlayerStats.ReadData(Stream input, DataType type, Endian endian)
at Gibbed.BorderlandsOz.FileFormats.PlayerStats.Deserialize(Stream input, Endian endian)
at Gibbed.BorderlandsOz.FileFormats.PlayerStats.Deserialize(Byte[] data, Endian endian)
at Gibbed.BorderlandsOz.FileFormats.SaveFile.Deserialize(Stream input, Platform platform, DeserializeSettings settings)
at Gibbed.BorderlandsOz.SaveEdit.ShellViewModel.<>c__DisplayClass58_0.b__2()
at Caliburn.Micro.Contrib.Results.DelegateResult.Execute(ActionExecutionContext context)
OK
I am able to open other saves that are under level 30. The save that is giving me this error is at level cap.

Could you attach that save file to this issue?

My save was able to be loaded when trying today, not sure what happened, but here's the save.
http://www.mediafire.com/file/b7ryynynbzpdy2q/Save0001.sav


Error when opening a file in vi which contains the substring "vimrc" in its filename

When I open a file which has "vimrc" in its filename, in the Terminal (not in GUI mode), I get an error:
Here is the command using the file name "stringcontainingvimrcthrowsanerror":
$ mvim -v stringcontainingvimrcthrowsanerror

And the resulting output:
"stringcontainingvimrcthrowsanerror" [New File]
Error detected while processing /Users/maghga/.yadr/vim/bundle/vim-textobj-function/after/ftplugin/vim/textobj-functio
n.vim:
line   30:
E128: Function name must start with a capital or "s:": g:textobj_function_vim_select(object_type)
line   31:
E133: :return not inside a function
line   78:
E700: Unknown function: g:textobj_function_vim_select
Press ENTER or type command to continue

Maybe this is an error with vim or MacVim in general, but I'm not sure.

I've experimented a little more with this, and the issue is not limited to files with "vimrc" in their filename.  Maybe it's with the vim syntax detection.  I've created a vim script with the mkview command, and opening that file results in the same error.

Has anyone been able to reproduce this error?  Is it something specific to my environment?
I've found a similar issue when googling for the error message, but I can't quite tell if it's in the same exact plugin:
https://github.com/thinca/vim-textobj-function-javascript/issues/2

I started getting similar errors when updating YADR, and stumbled across the fix here:
https://github.com/VundleVim/Vundle.vim/issues/470
cd ~/.vim/bundles/vundle
git pull

I'm not sure how I got into a state where I had an older version of vundle, since I don't manipulate it outside of YADR.  From the lack of responses to this issue, I'm guessing it was some sort of oddball error specific to my environment.  Anyway, here is the fix, in case someone else finds it useful.


🔴 Ecosystem Project Idea: Public OP Mainnet Network Health Dashboard

What is an Ecosystem Project Idea?
An Ecosystem Project Idea is an idea for a project that someone could build within the Optimism ecosystem. As opposed to an Ecosystem Concept or an Ecosystem Idea, an Ecosystem Project is generally more fleshed out and corresponds to a relatively clear product to be built.

Summary
Users need clear, constant insight into the functional behavior of OP Mainnet. In order to provide insights and better understanding of the state and performance of the L2 network, the L2 Network Health Dashboard will offer a range of crucial statistics in a visual, easy-to-understand format. As an important part of the ecosystem, the ability to monitor the health and performance of the L2 network will allow developers, users, and operators to make informed decisions and adjustments.
Features

The dashboard should be built using Grafana for real-time monitoring and interaction.
The dashboard should be fully open source.
The dashboard should have instructions on how to populate the dashboard.
The dashboard should track transaction latency and offer insights into the average, peak, and minimum transaction times.
The dashboard should keep track of the costs associated with specific actions on the network.
The dashboard should track the speed of block production and highlight any significant deviations.
The dashboard should be able to track reorganizations on the network.
The dashboard should be able to track the time taken for a block to be produced and sent to L1.
The dashboard should track block finalization times.
Flexibility for adding additional metrics or data points as they become relevant or necessary.

Impact

The dashboard will provide critical insights into the performance of the L2 network, allowing for informed decision making.
The data collected and displayed could help identify any bottlenecks or areas of inefficiency on the network.
By making this information easily accessible, the dashboard could encourage the growth and development of the network by providing developers with the information they need to optimize their applications and services.
Having this kind of transparency could increase trust and confidence in the network. Users and developers alike will have a clearer understanding of how the network operates and performs under various conditions.

I'm tackling this one!

This is def something we need.

@smartcontracts If it's still open, I can look into this.

@nanobro Can you please share the demo link? Would love to take a look. Thanks!

Heyo!
@nanobro if you are still interest in working on this it is getting moved into a markdown file. You can make a PR to add yourself as a contributor!
This process should wrap up by the end of the week, so look out for instructions in the README then.
As always, stay optimistic!

@marianoclaveria @Nicca42 It's a shame to say this. But it's too complex for me, I failed. So sorry.


Jump to 0x0 when calling missing function (inscrutable error message)

Minimal reproduction project:
gist getter.zip
remember to install godot sandbox first.
Example of vmcall: sandbox.vmcall("on_ready", self)
Errors thrown:
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
OpenGL API 3.3.0 - Build <IP_ADDRESS>1 - Compatibility - Using Device: Intel - Intel(R) UHD Graphics 620

[] Exception when calling:
  (null) (0x0)
Backtrace:
->
->
-> [-] 0x0 + 0x0: (null)

Exception: Protection fault  (data: 0)
>>> [0x13EEC8] 00000073 SYS ECALL
>>> Machine registers:
[PC	13eec8] [RA	0013EE98] [SP	011FFCA0] [GP	00165DA0] [TP	00166C78]
[LR	00166B80] [TMP1	00000002] [TMP2	00000007] [SR0	011FFFE0] [SR1	011FFF90]
[A0	00000000] [A1	00000003] [A2	011FFCA8] [A3	00000000] [A4	00000008]
[A5	00100238] [A6	00166D00] [A7	00000049] [SR2	00166D00] [SR3	00000000]
[SR4	00000000] [SR5	00000000] [SR6	00000000] [SR7	00000000] [SR8	00000000]
[SR9	00000000] [SR10	00000000] [SR11	00000000] [TMP3	00000006] [TMP4	6474E551]
[TMP5	00000000] [TMP6	00800000]

[] Exception when calling:
  (null) (0x0)
Backtrace:
->
->
-> [-] 0x0 + 0x0: (null)

Exception: Execution space protection fault  (data: 0)
>>> [0x0]     0000 UNIMPLEMENTED: 2-byte 0 F0 (0)
>>> Machine registers:
[PC	0] [RA	01200000] [SP	011FFFD0] [GP	00165DA0] [TP	00166C78]
[LR	00166B80] [TMP1	00000002] [TMP2	00000007] [SR0	011FFFE0] [SR1	011FFF90]
[A0	011FFFD0] [A1	C0CB8410] [A2	011FFCA8] [A3	00000000] [A4	00000008]
[A5	00100238] [A6	00166D00] [A7	00000049] [SR2	00166D00] [SR3	00000000]
[SR4	00000000] [SR5	00000000] [SR6	00000000] [SR7	00000000] [SR8	00000000]
[SR9	00000000] [SR10	00000000] [SR11	00000000] [TMP3	00000006] [TMP4	6474E551]
[TMP5	00000000] [TMP6	00800000]

--- Debugging process stopped ---

This uses the Zig toolchain which strips executables by default. When programs are stripped we can't see any functions, so the program needs to register them by itself, through the puclic API.
You can disable stripping (a CMake option) or use the public API:
int main() {
    ADD_API_FUNCTION(on_ready, "void", "Node entity");
    ADD_API_FUNCTION(on_process, "void", "Node entity");
}

We can improve the error messaging here to say that the function doesn't exist, or it needs to be added to the public API.

It's also unclear you need to do this if you're copying from the demo:
https://github.com/libriscv/godot-sandbox-demo/tree/master/json_diff_sample/json_diff
is the cmake disable stripping buried somewhere in a subfolder, or is the demo outdated?

It's probably a bit of both: The demo uses an embedded RISC-V toolchain that @fire found in MSYS2 packages, while you are using the fairly new Zig toolchain, which isn't as well understood yet. The documentation probably needs to be updated so that code examples show the public API being used. And so on.

https://github.com/libriscv/godot-sandbox/commit/91d3c928e4ae4af49a19dd980ea016c5501847f3

So I changed main.cpp to this:
#include <api.hpp>

extern "C" void on_ready(Node entity){
}

extern "C" void on_process(Node entity){

}

int main() {
    ADD_API_FUNCTION(on_ready, "void", "Node entity");
    ADD_API_FUNCTION(on_process, "void", "Node entity");
}

And I get the same error:
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
OpenGL API 3.3.0 - Build <IP_ADDRESS>1 - Compatibility - Using Device: Intel - Intel(R) UHD Graphics 620

[] Exception when calling:
  (null) (0x0)
Backtrace:
->
->
-> [-] 0x0 + 0x0: (null)

Exception: Protection fault  (data: 0)
>>> [0x13EFA0] 00000073 SYS ECALL
>>> Machine registers:
[PC	13efa0] [RA	0013EF70] [SP	011FFCA0] [GP	00165E78] [TP	00166D78]
[LR	00166C80] [TMP1	00000002] [TMP2	00000007] [SR0	011FFFE0] [SR1	011FFF90]
[A0	00000000] [A1	00000003] [A2	011FFCA8] [A3	00000000] [A4	00000008]
[A5	00100238] [A6	00166E00] [A7	00000049] [SR2	00166E00] [SR3	00000000]
[SR4	00000000] [SR5	00000000] [SR6	00000000] [SR7	00000000] [SR8	00000000]
[SR9	00000000] [SR10	00000000] [SR11	00000000] [TMP3	00000006] [TMP4	6474E551]
[TMP5	00000000] [TMP6	00800000]

[] Exception when calling:
  (null) (0x0)
Backtrace:
->
->
-> [-] 0x0 + 0x0: (null)

Exception: Execution space protection fault  (data: 0)
>>> [0x0]     0000 UNIMPLEMENTED: 2-byte 0 F0 (0)
>>> Machine registers:
[PC	0] [RA	01200000] [SP	011FFFD0] [GP	00165E78] [TP	00166D78]
[LR	00166C80] [TMP1	00000002] [TMP2	00000007] [SR0	011FFFE0] [SR1	011FFF90]
[A0	011FFFD0] [A1	897C60C0] [A2	011FFCA8] [A3	00000000] [A4	00000008]
[A5	00100238] [A6	00166E00] [A7	00000049] [SR2	00166E00] [SR3	00000000]
[SR4	00000000] [SR5	00000000] [SR6	00000000] [SR7	00000000] [SR8	00000000]
[SR9	00000000] [SR10	00000000] [SR11	00000000] [TMP3	00000006] [TMP4	6474E551]
[TMP5	00000000] [TMP6	00800000]

--- Debugging process stopped ---

There is a new release out that prints and breaks when a function is not found. If that doesn't work then we need to investigate more, but from what I can see it just looks like a call to a function that doesn't exist, unfortunately.

For documentation, seems like the elf compiles correctly, since it loads fine on linux godot but not windows; the windows sandbox protection faults even if you run sandbox.has_function("on_ready"):
E 0:00:01:0946   vsk_entity.gd:10 @ _ready(): Sandbox exception: Protection fault
  <CPPScript Source>src\sandbox.cpp:522 @ load()
  <Stack Trace>  vsk_entity.gd:10 @ _ready()

Alright, I posted this issue: https://github.com/libriscv/godot-sandbox/issues/245
Thanks for trying things and posting the results. With all that we have identified the problem.


bugtool: improve lb dump support and add monitor helper for k8s tests

Fixes: #8081

This change is

test-me-please

test-me-please

Coverage decreased (-0.02%) to 41.893% when pulling fb923f89338fdb58bb58ab33fa1c7008b0b3b2b5 on pr/better-lb-bugtool-support into ec3910f1f33e866885a08aede919f270b2912975 on master.


Fix ChromaDB 0.5.X compatibility issues

throws exception when trying to delete unexisting collection

Reason: Exception type was changed in ChtomaDB


[components] zetacomponents.org

http://zetacomponents.org/

Happy to merge this when their website no longer references 2010 as the last status update.


Environments window is slow to open

UI freezes for a few seconds, it's longer if you don't already have Python packages already loaded. A bit longer still if conda support is enabled.
If it's the discovery that is slow, we should see if we can use a cached list, and/or make it load them incrementally.
First discovery is done on a worker thread, which shouldn't be blocking the UI. Not sure what's going on.

Most of the time is spent in InterpreterListToolWindow.List_ViewCreated, more specifically the loop that creates all the PipExtensionProvider instances.
To be continued...


Strategy for supporting AEM 6.2

With the upcoming release of AEM 6.2, the current version of ACS AEM Commons needs to be modified in some significant ways:

There needs to be a specific build compiled against the 6.2 UberJar due to a variety of major package version changes.
The com.day.cq.workflow.WorkflowSession interface has been changed in a non-backwards compatible way so the synthetic implementation must be changed to match.
The org.apache.sling.event.jobs.JobProcessor interface has been removed (was deprecated in 6.1).

Due to (1) and (2), we can no longer produce a cross-compatible version of ACS AEM Commons between 6.1 and 6.2 (let alone 6.0, 6.1, and 6.2).
Since I expect we will continue to have a significant number of users on 6.0 and 6.1, what I'm recommending is as follows:

We leave master as compatible with 6.0/6.1 and release using the current versions 2.x
We create a branch feature/6.2-compatibility and release a version against this branch with the version number 3.0.0.

At some point, based on feedback, we can switch this so that master is compatible with 6.2 and there's another branch for 6.0/6.1 compatibility.
Issues with this proposal:

GitHub only allows for a single milestone to be attached to each issue.
Since we need the unobfuscated UberJar, feature/6.2-compatibility cannot be built through TravisCI.

For 2, did the Granite workflow API change as well? I haven't looked but those two were identical. Could synthetic workflows extend/consume the other interface, thus reducing the work to bring it forward?
Single milestones can be fixed by having dup issues per release version. This will create overhead tasks, but we can also default to 3.0 release, and then determine if we want to add it back to 2.x.

@bstopp I'll have to defer to @davidjgonzalez on (2), but I think we need to use the CQ workflow API in order to support the workflow processes commonly used with synth workflows. worth doublechecking as maybe that would allow us to support 6.1 and 6.2 simultaneously

@bstopp We can't drop support of the CQ Workflow process API, else we'd wouldnt be able to use any CQ WorkflowProcesses in synth -- even dropping just the Synth impl of CQ WorkflowSession would have a trickle-down effect that would break CQ WorkflowProcess execution that may use it.
Def worth looking into the problem a bit more though.

Let's move forward with the plan as suggested. We can iterate in the future, but I'd like to get a 3.0.0 release out.

Hi Justin/David,
I am facing issue building my project jar in 6.2. And can see that while you also faced similar build error:
https://travis-ci.org/Adobe-Consulting-Services/acs-aem-commons/builds/133937577
Can you please let me know the fix for it:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project sandiskweb.core: Compilation failure
[ERROR] error: error reading M:\mvn-repo\com\adobe\aem\uber-jar\6.2.0\uber-jar-6.2.0-apis.jar; zip file is empty
Rohan

@rohanraj14 please do not use ACS AEM Commons github issues to ask questions which aren't related to ACS AEM Commons.
In our Travis builds, that error is because Travis does not have access to the unobfuscated UberJar. We try to mitigate that by using travis branch exclusions, but those don't work well with tags, so those errors are not particularly important for us.


Query: Refactor GroupBy aggregate to avoid dependency on Requires Materialization

@smitpatel is there a more general issue for "delayed requires materialization" that we talked about in planning or is this the one?

@divega - We don't have tracking issue for that separately. Could be part of #7520

@smitpatel ok, let's chat when we have a chance about how to best track it. If you add it to the list in #7520 that would be a good start.

@divega - #11215 I added note to that list.

Make sure to test case in #12089

Moved this into 2.2 since we believe it will help stabilize query. If, when working on it. it looks like it is going to have the opposite effect. then we should reconsider.

We do not have requires materialization visitor anymore. So this is no longer needed. We can do needful when we re-implement group by aggregate.

@smitpatel what does it exactly mean? Could you explain in simple terms?

In old pipeline, we had to determine in advance if we need to materialize entity or we can server eval. For GroupBy when you are applying aggregate, entity materialization is not required. But with mixed mode evaluation, it was not possible to determine in all cases, if we can translate to SQL group by since some client function or not mapped property can cause client eval. Hence we were having issues when advance determination was incorrect. This issue was tracking it. Now in new pipeline we don't do advance determination of materialization so this issue is no longer relevant.


Switch to josharian/native for native endian?

@hugelgupf, any chance this repo could switch to using https://pkg.go.dev/github.com/josharian/native
@josharian and I are trying to reduce the number of copies of this code in the Go ecosystem, per golang/go#57237
As of josharian/native#3 it has both a boolean const and a binary.ByteOrder var.
It also has a fallback to runtime-based detection if build tags get stale in the future.
If you're concerned about lacking control, I'm sure @josharian could grant you co-maintainership of the native repo.
Happy to send you a PR if you're cool with it. Or you can.

Oh, I guess we can't outright remove it, as it has a bunch of callers, like github.com/insomniacslk/dhcp/dhcpv4 etc.
But you could use the constant in a func init which should get compiled away to ~nothing.
And you could update the docs to point people at the native package?

I'm sure @josharian could grant you co-maintainership of the native repo

Indeed I could, just say the word.

No need for co-maintainership, I'm happy with this. Thanks!

If you go make a PR to update dhcp, I'll be happy to approve that as well.

If you go make a PR to update dhcp, I'll be happy to approve that as well.

Done: https://github.com/insomniacslk/dhcp/pull/484


The code of segmentation

Hi, do you have a plan to release the segmentation code? I reproduced the Mambaout-Tiny on ImageNet-1K, which achieves 82.6 top1 accuracy. I think the result is reasonable given the randomness and the different batch size (1024 rather than 4096). However, when I transfer the pre-trained model to semantic segmentation, it only achieves 46.1 mIoU on ade20k, much lower than the 47.4 reported in the paper. I use the Swin config based on MMsegmentation codebase. The droppath rate is 0.2 and no layer-wise decaying learning rate.

Hi @ydhongHIT , many thanks for your attention. Currently, I am busy and will arrange the segmentation code as soon as possible. MambaOut is also based on Swin config. Note to add LN for outputs of backbone at each stage. For all model sizes, the learning rate is 1e-4. The drop path is 0.3 for Tiny, 0.3 or 0.4 for Small and 0.6 for Base.

Thank you for the reply. I will train the model again according to your instructions. By the way, do you employ the layer-wise decaying learning rate like ConvNext?

Hi @yuweihao , Layer-wise decaying learning rate was not used for MambaOut.