Lsp Finder throws error on open

Description

When opening the finder I get an error. The window contents are correctly highlighted, the previewer doesn't open and the selected highlight replaces my cursorline
Error executing vim.schedule lua callback: ...site/pack/packer/start/lspsaga.nvim/lua/lspsaga/libs.lua:46: Expected lua string

Expected Behavior

It should open as normal
Actual Behavior

Details

Reproduce

nvim -u test.vim the min config that only lspsaga
run finder mapping on a variable or function call in lua file

Environment
 saga.init_lsp_saga {
    debug = true,
    use_saga_diagnostic_sign = false,
    finder_action_keys = {
      open = "o",
      vsplit = "v",
      split = "s",
      quit = {"q", [[\<ESC>]]}
    }
  }

  map("n", "gh", [[<cmd>lua require'lspsaga.provider'.lsp_finder()<CR>]])

nvim --version output:

Error executing vim.schedule lua callback: ...site/pack/packer/start/lspsaga.nvim/lua/lspsaga/libs.lua:46: Expected lua string
NVIM v0.5.0-dev
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/neovim-tTsPN6/neovim-0.5.0+ubuntu2+git202102090237-38ea2ce34-d569569c9=. -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/build/neovim-tTsPN6/neovim-0.5.0+ubuntu2+git202102090237-38ea2ce34-d569569c9/build/config -I/build/neovim-tTsPN6/neovim-0.5.0+ubuntu2+git202102090237-38ea2ce34-d569569c9/src -I/build/neovim-tTsPN6/neovim-0.5.0+ubuntu2+git202102090237-38ea2ce34-d569569c9/.deps/usr/include -I/usr/include -I/build/neovim-tTsPN6/neovim-0.5.0+ubuntu2+git202102090237-38ea2ce34-d569569c9/build/src/nvim/auto -I/build/neovim-tTsPN6/neovim-0.5.0+ubuntu2+git202102090237-38ea2ce34-d569569c9/build/include
Compiled by buildd@lgw01-amd64-038

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Operating system: Ubuntu 20.10
lspsaga commit:

I've tried with debug = true but that doesn't print anything. This issue only started a few days ago when I think there was a change/refactor of the finder. Also should mention that I use sumneko_lua with efm so there are multiple lsps active in most of my buffers

@akinsho   quit = {"q", '<ESC>}  change like this

@glepnir unfortunately that didn't fix the issue. Do you need more info from me? are you able to see the same issue? for me it happens even if I use LspSaga finder etc. as if I map the lua function although that's to be expected probably

hmm quit = {'q','<ESC>'}  quit key like this

I tried just now removing the quit key as well as using it the way you show in the example above. To be clear the error isn't when I try to quit, the error is immediately I open a finder window it throws this error

the libs.lua :46 is create keymap of finder . so you got error because of your quit key.

Ok I tested removing that configuration completely and it works fine. I managed to work out what is wrong, if you specify finder_action_keys you have to specify the complete table and all it's keys. So I previously had that table but there didn't use to be a scroll_down and scroll_up key. Since I didn't specify them there seems to be no fallback so it was causing errors on open

OK i will enhance this .seems like should extend custom keymaps.

Now you do not need set all keymaps in finder .just set you need to change.

Thanks @glepnir that works now. Sorry to be burying you in issues 😅 , looking at your screenshot it seems you aren't seeing the finder window sizing and highlighting bugs. With the config above which I posted (or with 0 config) I'm seeing the highlighting doesn't reach the references section/ it seems to break as well.
Broken highlighting

Missing highlighting

I didn't post this earlier since I thought maybe you were already aware and working on it

why there has two definitions?

I don't really know there is only one function in that file, it's just what I get I tried it on another local function and I'm seeing two definitions as well 🤷🏿

I had fix height problem. but i test your config I don't have two definitions seems like you start two lua server?

@glepnir thanks for the quick height fix, I'm not sure how I could have 2 lsps running, looking at LspInfo I get

hmmm now still exist ? I can't reproduce it in my config.

I think maybe it might be the version of sumneko_lua I'll try and debug more soon and report back, I actually have two functions called map but one is local but that isn't the issue since when I check a bunch of different definitions (local) I get 0 definitions and then some references

ok if can reproduce with min config. post here I will test it.

@glepnir I've been testing with a minimal init.lua, with the latest version of sumneko_lua and I'm getting server returns wrong response, I think the newest server has some incompatible changes in neovim that might be causing this issue. I'll try downgrading later today to see if that helps
vim.cmd "packadd nvim-lspconfig"
vim.cmd "packadd lspsaga.nvim"

local lspconfig = require("lspconfig")

local sumneko_path = string.format("%s/lua-language-server", "<Path-to-install>")
local sumneko_binary = sumneko_path .. "/bin/Linux/lua-language-server"

lspconfig.sumneko_lua.setup {
  cmd = {sumneko_binary, "-E", sumneko_path .. "/main.lua"},
  settings = {
    Lua = {
      diagnostics = {globals = {"vim"}},
      completion = {keywordSnippet = "Both"},
      runtime = {
        version = "LuaJIT",
        path = vim.split(package.path, ";")
      },
      awakened = {cat = true},
      workspace = {
        maxPreload = 1000,
        preloadFileSize = 1000
      }
    }
  }
}

require("lspsaga").init_lsp_saga {
  use_saga_diagnostic_sign = false,
  finder_action_keys = {
    vsplit = "v",
    split = "s",
    quit = {"q", "<ESC>"}
  }
}

vim.api.nvim_set_keymap("n", "gh", [[<cmd>lua require'lspsaga.provider'.lsp_finder()<CR>]], {})

I test it with last commit neovim with this min config. works fine.
set rtp+=~/workstation/vim/lspsaga.nvim
set rtp+=~/.cache/vim/dein/repos/github.com/neovim/nvim-lspconfig

lua <<EOF

require('lspsaga').init_lsp_saga()

require('lspconfig').sumneko_lua.setup {
  cmd = {
    "/Users/bitcoder/workstation/lua-language-server/bin/macOS/lua-language-server",
    "-E",
    "/Users/bitcoder/workstation/lua-language-server/main.lua"
  };
  settings = {
    Lua = {
      diagnostics = {
        enable = true,
        globals = {"vim"}
      },
      runtime = {version = "LuaJIT"},
      workspace = {
        library = vim.list_extend({[vim.fn.expand("$VIMRUNTIME/lua")] = true},{}),
      },
    },
  }
}
EOF

https://user-images.githubusercontent.com/41671631/107373878-f5fca480-6b21-11eb-8624-3eae24ed2212.mov

@glepnir are you using the latest sumneko_lua language server version from today?

Ohh ..no  update now and test.

reproduce with latest ..

seems like something wrong in latest lua-language server. check the default handler of neovim
vim.lsp.buf.definition() got noting happened..

Ok in which case that doesn't have to do with this plugin then 👍🏿 , I did just try another lsp client just to check and using in a dart project I see.

Looking in the code in provider.lua it looks like opts.height expects some values and there is no fallback so opts.height can be nil and so tries to compare nil with max_height. The references and definitions look fine so think this isn't an lsp error

I also get it. but I am thinking about why get nil ..

fixed bug of nil value . but finder still not work in lua-language-server last commit

Damn the last commit of lua-language-server. it works slowly...

I think probably the change in lua-language-server is maybe incompatible with neovim somehow, I don't know much about the internals but seems the author is more focused on vscode so they might have broken in by mistake. Yeah also noticed it's really slow as well

yep. the author use vscode ..so I need rollback.


Improved Translation API via Hooks

We should investigate if we can improve our translations API using hooks.
Type of issue
Feature Request
Description
The current API for working with raw translated strings is a bit cumbersome, as it requires duplicating the translation keys, once in the withTranslations call, and once in the translate call. This is further described here: https://github.com/fusionjs/fusion-cli/pull/643
We should investigate various options of improving this API, potentially taking advantage of hooks.

A potential hook API could look something like this:
import {useTranslate} from 'fusion-plugin-i18n-react';

function Component() {
  const translate = useTranslate();
  const value = translate('some.key');
}


o-field problem with Vue 3 latest version

Overview of the problem
Oruga version: [0.5.3]
Vuejs version: [3.2.31]
OS/Browser: Windows 10/Firefox 97.0
Description
I've been experimenting with Vue 3 for the last week and today I faced the following problem when using 'o-field':
Uncaught (in promise) TypeError: this.$matchMediaRef is undefined
    created MatchMediaMixin-0c7dfcb9.mjs:32
    callWithErrorHandling runtime-core.esm-bundler.js:155
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:164
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:174
    callHook runtime-core.esm-bundler.js:2965
    applyOptions runtime-core.esm-bundler.js:2867
    finishComponentSetup runtime-core.esm-bundler.js:7170
    setupStatefulComponent runtime-core.esm-bundler.js:7082
    setupComponent runtime-core.esm-bundler.js:7012
    mountComponent runtime-core.esm-bundler.js:4922
    processComponent runtime-core.esm-bundler.js:4897
    patch runtime-core.esm-bundler.js:4489
    mountChildren runtime-core.esm-bundler.js:4685
    processFragment runtime-core.esm-bundler.js:4856
    patch runtime-core.esm-bundler.js:4482
    componentUpdateFn runtime-core.esm-bundler.js:5037
    run reactivity.esm-bundler.js:167
    setupRenderEffect runtime-core.esm-bundler.js:5156
    mountComponent runtime-core.esm-bundler.js:4939
    processComponent runtime-core.esm-bundler.js:4897
    patch runtime-core.esm-bundler.js:4489
    componentUpdateFn runtime-core.esm-bundler.js:5037
    run reactivity.esm-bundler.js:167
    setupRenderEffect runtime-core.esm-bundler.js:5156
    mountComponent runtime-core.esm-bundler.js:4939
    processComponent runtime-core.esm-bundler.js:4897
    patch runtime-core.esm-bundler.js:4489
    componentUpdateFn runtime-core.esm-bundler.js:5037
    run reactivity.esm-bundler.js:167
    setupRenderEffect runtime-core.esm-bundler.js:5156
    mountComponent runtime-core.esm-bundler.js:4939
    processComponent runtime-core.esm-bundler.js:4897
    patch runtime-core.esm-bundler.js:4489
    render2 runtime-core.esm-bundler.js:5641
    mount runtime-core.esm-bundler.js:3877
    mount runtime-dom.esm-bundler.js:1590
    setup app.js:14
    node_modules @inertiajs_inertia-vue3.js:9635
    promise callback*node_modules/ @inertiajs_inertia-vue3.js:9634
    <anonymous> app.js:6

Until today I did not had this issue.
The stack I'm using is:
Laravel 9 @ latest
InertiaJS  @ latest
Vite @ latest
Vue 3 @ latest
Tracking back the issue I managed to isolate the problem, which is a Vue 3 update.
The "good" version is 3.2.30 and the bad is 3.2.31
Steps to reproduce
Create a basic project with the latest versions of Laravel 9, InertiaJS, Vue3, Oruga and Vite
Expected behavior
No error
Actual behavior
Error

Thanks to investigate about Vue version, it's a good a workaround at the moment.

Hello, same problem for me on the dialog.open:
          const modal = this.$oruga.modal.open({
            parent: this,
            component: ModalForm,
            trapFocus: true,
          })

with ModalForm is the one of example.
Vue: 3.2.31
Oruga: 0.5.3
Vite; 2.8.3
TypeError: this.$matchMediaRef is undefined
    created MatchMediaMixin-0c7dfcb9.mjs:32
    callWithErrorHandling runtime-core.esm-bundler.js:155
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:164
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:174
    callHook runtime-core.esm-bundler.js:2965
    applyOptions runtime-core.esm-bundler.js:2867
    finishComponentSetup runtime-core.esm-bundler.js:7170
    setupStatefulComponent runtime-core.esm-bundler.js:7082
    setupComponent runtime-core.esm-bundler.js:7012
    mountComponent runtime-core.esm-bundler.js:4922
    processComponent runtime-core.esm-bundler.js:4897
    patch runtime-core.esm-bundler.js:4489
    render2 runtime-core.esm-bundler.js:5641
    render runtime-dom.esm-bundler.js:1564
    open modal.mjs:390
    createRoom RoomCreation.vue:103
    Async*_sfc_render/_cache[1]< RoomCreation.vue:133
    withModifiers runtime-dom.esm-bundler.js:1466
    callWithErrorHandling runtime-core.esm-bundler.js:155
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:164
    invoker runtime-dom.esm-bundler.js:366
    addEventListener runtime-dom.esm-bundler.js:316
    patchEvent runtime-dom.esm-bundler.js:334
    patchProp runtime-dom.esm-bundler.js:398
    mountElement runtime-core.esm-bundler.js:4603
    processElement runtime-core.esm-bundler.js:4566
    patch runtime-core.esm-bundler.js:4486
    mountChildren runtime-core.esm-bundler.js:4685
    mountElement runtime-core.esm-bundler.js:4594
    processElement runtime-core.esm-bundler.js:4566
    patch runtime-core.esm-bundler.js:4486
    componentUpdateFn runtime-core.esm-bundler.js:5037
    run reactivity.esm-bundler.js:167
    setupRenderEffect runtime-core.esm-bundler.js:5156
    mountComponent runtime-core.esm-bundler.js:4939
    processComponent runtime-core.esm-bundler.js:4897
    patch runtime-core.esm-bundler.js:4489
    componentUpdateFn runtime-core.esm-bundler.js:5037
    run reactivity.esm-bundler.js:167
    setupRenderEffect runtime-core.esm-bundler.js:5156
    mountComponent runtime-core.esm-bundler.js:4939
    processComponent runtime-core.esm-bundler.js:4897
    patch runtime-core.esm-bundler.js:4489
    mountChildren runtime-core.esm-bundler.js:4685
    mountElement runtime-core.esm-bundler.js:4594
    processElement runtime-core.esm-bundler.js:4566
    patch runtime-core.esm-bundler.js:4486
    componentUpdateFn runtime-core.esm-bundler.js:5037
    run reactivity.esm-bundler.js:167

Thanks for the quick fix @jtommy 👍🏻
Do you have a date for a new release shipping it?
(I tried downgrading vue to 3.2.30 but it was not ok).


[cinder-csi-plugin] Add test changes into zuul file

What this PR does / why we need it:
the changes in tests folder will not trigger CSI e2e and sanity check
update zuul file on this
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/lgtm

/approve


Document a breaking change that was raised in https://github.com/apache/beam/issues/25085

fixes: https://github.com/apache/beam/issues/25085

R: @RobMcKiernan


Kubernetes get-credentails fails if known_hosts is malformatted

Description
Not sure how/when my known_hosts file got messed up, but running az acs kubernetes get-credentials fails (I think paramiko tries to load the known_hosts file and throws an exception -
this could be caught and CLI could fail nicely):
Password for private key:
('[known_hosts_entry]', Error('Incorrect padding',))
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/azure/cli/main.py", line 36, in main
    cmd_result = APPLICATION.execute(args)
  File "/usr/local/lib/python2.7/site-packages/azure/cli/core/application.py", line 212, in execute
    result = expanded_arg.func(params)
  File "/usr/local/lib/python2.7/site-packages/azure/cli/core/commands/__init__.py", line 377, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/azure/cli/core/commands/__init__.py", line 626, in _execute_command
    reraise(*sys.exc_info())
  File "/usr/local/lib/python2.7/site-packages/azure/cli/core/commands/__init__.py", line 603, in _execute_command
    result = op(client, **kwargs) if client else op(**kwargs)
  File "/usr/local/lib/python2.7/site-packages/azure/cli/command_modules/acs/custom.py", line 814, in k8s_get_credentials
    _k8s_get_credentials_internal(name, acs_info, path, ssh_key_file)
  File "/usr/local/lib/python2.7/site-packages/azure/cli/command_modules/acs/custom.py", line 835, in _k8s_get_credentials_internal
    '.kube/config', path_candidate, key_filename=ssh_key_file)
  File "/usr/local/lib/python2.7/site-packages/azure/cli/command_modules/acs/acs_client.py", line 60, in secure_copy
    ssh.load_system_host_keys()
  File "/usr/local/lib/python2.7/site-packages/paramiko/client.py", line 102, in load_system_host_keys
    self._system_host_keys.load(filename)
  File "/usr/local/lib/python2.7/site-packages/paramiko/hostkeys.py", line 97, in load
    e = HostKeyEntry.from_line(line, lineno)
  File "/usr/local/lib/python2.7/site-packages/paramiko/hostkeys.py", line 366, in from_line
    raise InvalidHostKey(line, e)
InvalidHostKey: ('[ACTUAL_HOST_KEY]', Error('Incorrect padding',))

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: pip install azure-cli
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here: azure-cli (2.0.18)
OS Version: What OS and version are you using?
Answer here: MacOS 10.13
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: bash

the ask here is, how to get exceptions nicely.
@troydai, do we have any tactic in general in handling exception?

I think the fix here would be as simple just catching the specific exception e.g.:
...
except InvalidHostKey:
...

closing as az acs is deprecating


CodeQL

fix the CodeQL action
https://github.com/QuantityTypes/QuantityTypes/actions/workflows/codeql.yml

https://github.com/QuantityTypes/QuantityTypes/security/code-scanning


Compile error

Get a compile error when i try to compile today.. Not kept up to date as of late, so dont really know when this happened tho.
../src/d3d11/d3d11_options.cpp:5:21: error: ‘unordered_map’ in namespace ‘std’ does not name a template type
   const static std::unordered_map<std::string, D3D11OptionSet> g_d3d11AppOptions = {{
                     ^~~~~~~~~~~~~
../src/d3d11/d3d11_options.cpp: In function ‘dxvk::D3D11OptionSet dxvk::D3D11GetAppOptions(const string&)’:
../src/d3d11/d3d11_options.cpp:11:23: error: ‘g_d3d11AppOptions’ was not declared in this scope
     auto appOptions = g_d3d11AppOptions.find(AppName);
                       ^~~~~~~~~~~~~~~~~
[103/113] Compiling C++ object<EMAIL_ADDRESS>ninja: build stopped: subcommand failed.
[1/12] Compiling C++ object<EMAIL_ADDRESS>FAILED<EMAIL_ADDRESS>/usr/bin/x86_64-w64-mingw32-g++ -Og -gdwarf-2 -Isrc/d3d11/d3d11@sha -Isrc/d3d11 -I../src/d3d11 -I.././include -Isrc/dxvk -I../src/dxvk -Isrc/dxgi -I../src/dxgi -Isrc/dxbc -I../src/dxbc -fdiagnostics-color=always -pipe -Wall -Winvalid-pch -Wnon-virtual-dtor -std=c++1z -O3 -MMD -MQ<EMAIL_ADDRESS>-MF<EMAIL_ADDRESS>-o<EMAIL_ADDRESS>-c ../src/d3d11/d3d11_options.cpp
../src/d3d11/d3d11_options.cpp:5:21: error: ‘unordered_map’ in namespace ‘std’ does not name a template type
   const static std::unordered_map<std::string, D3D11OptionSet> g_d3d11AppOptions = {{
                     ^~~~~~~~~~~~~
../src/d3d11/d3d11_options.cpp: In function ‘dxvk::D3D11OptionSet dxvk::D3D11GetAppOptions(const string&)’:
../src/d3d11/d3d11_options.cpp:11:23: error: ‘g_d3d11AppOptions’ was not declared in this scope
     auto appOptions = g_d3d11AppOptions.find(AppName);
                       ^~~~~~~~~~~~~~~~~
^Cninja: build stopped: interrupted by user.

This is with 0900e1b5f905c68b49f676d7b3a3433b7bfd286a

I don't know why you need the include when I don't, but should be fixed now.


[Bug] Logout functionality not working

While choosing option 5 which is for Logging out the code is not logging out the user and instead displaying the same set of options which were asked to the logged user.
Steps to recreate the scenario:
Step 1: Fill the initial details and create the account.
Step 2: Press 5 on keyboard to Logout.
Step 3: Enter your email id and 4-digit pin.
Step 4: You will again see the Welcome Page.
Screenshot:

Can you assign me this issue?
I would like to work on this.

Yes sure

Can you assign me this issue? I would like to work on this.

Assigned

It is not a bug the problem is already solved.
After pressing 5 on keyboard, console clears and login screen comes up


Determine difficulty of each community

diameters will give the sizes of the communities
larger communities = harder levels
smaller communities = easier levels
I think to generate the random nodes and ensure many possibilities, we should query diameter/2 to get the "core" of each community


HOTFIX for spark3

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Kylin?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have create an issue on Kylin's jira, and have described the bug/feature there in detail
[ ] Commit messages in my PR start with the related jira ID, like "KYLIN-0000 Make Kylin project open-source"
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at user@kylin or dev@kylin by explaining why you chose the solution you did and what alternatives you considered, etc...

Codecov Report

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

@@           Coverage Diff           @@
##             main    #1717   +/-   ##
=======================================
  Coverage        ?   24.63%
  Complexity      ?     4451
=======================================
  Files           ?     1092
  Lines           ?    61884
  Branches        ?     8891
=======================================
  Hits            ?    15248
  Misses          ?    45031
  Partials        ?     1605

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 33c068f...80fdc84. Read the comment docs.


 It doesn't instantiate anything. It clones. Their documentation reflects that and I don't know why its called what it is. We can be better.
This is keeping me up at night.

With the new API/protocols/components, a clone function distinct from instantiate finally makes sense.


🐛 biome won't respect config when executed from a parent directory

Environment information
CLI:
  Version:                      1.9.2
  Color support:                true

Platform:
  CPU Architecture:             aarch64
  OS:                           macos

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "alacritty"
  JS_RUNTIME_VERSION:           unset
  JS_RUNTIME_NAME:              unset
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       unset

Workspace:
  Open Documents:               0

What happened?
create the following structure
project/sub/{biome.jsonc,my-file.js}
then from project run biome check sub
Expected result
In my view, it should respect that project/sub has a config and load it, instead of ignoring.
This is happens on a monorepo (without the extends usage) and commonly breaks formatting when running with pre-commit, which runs from the repository's root
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

This is a result of our lack of support for monorepos: https://github.com/biomejs/biome/issues/2228


Publish to npm

I dont see this package on npm. It seems like there already is a package.json. Would you be able to publish this to npm?

Thanks for pointing this out. I just published it on npm as bootstrap-arabic

Thanks so much!
On Fri, Feb 19, 2016, 4:35 PM zero<EMAIL_ADDRESS>wrote:

Thanks for pointing this out. I just published it on npm as
bootstrap-arabic
—
Reply to this email directly or view it on GitHub
https://github.com/zeroxme/bootstrap-3-arabic/issues/24#issuecomment-186238200
.


Validation errors found in deployment plans should identify which deployment plan the validation error is found in

Validation errors found in deployment plans should identify which deployment plan the validation error is found in. Many of our models contain numerous deployment plans, some of which are quite similar and use common assemblies. Finding which plan is the source of a validation error can be a very time consuming process. For instance, the following validation error messages do not specify which deployment plan is the source:
There were problems in executing the transformation: NLS missing message: GenerateAllDescriptors_FailureExecutingWorkflow in: com.zeligsoft.domain.ngc.ccm.descriptorgeneration.l10.Messagesworkflow/ngcgeneratorNoPostGeneration.mwe on platform:/resource/XYZ/ModelFiles/XYZ_Assemblies.emx. Connection between deployment parts testDriver_comp::idleGenerationClient and idleGenerator_comp_2::idleGenerationFacet on local interface requires collocation.

Analysis: The message being issued is part of the code generation templates. Apart from it providing too little information, CX provides a better validation framework than the one used here. The following fixes are proposed:

Include more information in the current message. In particular, add references to the deployment plan.
fix the "NLS missing message". While not critical to function, it is the manifestation of a typographical error
(more involved fix). Write a CX validation rule to detect the issue as part of the Validate action. This will have the side effect of highlighting the problematic elements in model tree, and displaying them in the Problems view. This is substantially better than the current behaviour, where the message is displayed in a pop-up dialog, and hidden away in the Eclipse error log.

Analysis: The message being issued is part of the code generation templates. Apart from it providing too little information, CX provides a better validation framework than the one used here. The following fixes are proposed:
* Include more information in the current message. In particular, add references to the deployment plan.

* fix the "NLS missing message". While not critical to function, it is the manifestation of a typographical error

* (more involved fix). Write a CX validation rule to detect the issue as part of the **Validate** action. This will have the side effect of highlighting the problematic elements in model tree, and displaying them in the Problems view. This is substantially better than the current behaviour, where the message is displayed in a pop-up dialog, and hidden away in the Eclipse error log.

SNA votes for the "more involved fix"

@elder4p - In regards to our phone discussion today, I believe this is the only additional GitHub issue (not counting https://github.com/ZeligsoftDev/CX4CBDDS/issues/23) that we'd like to have in the final CX 1.6.0.

Resolved via #19.

Just want to elevate Eric's comment above in case it was missed...

Re-opening Issue.

I attempted to test this fix on our end and I didn't notice a difference in behavior. I created a project, and deployment plan consisting of two components sharing a client, server (facet, receptacle) interface. Then, I placed them in different container processes and nodes in a deployment plan. Validate did not catch any issues, and generate descriptors still did (without telling me what deployment plan). The NLS bug seems to be fixed though.
However, this is not a big enough issue for us that we want to postpone the 1.6 release. We would like to move forward with the 1.6 release and address this in the next release

@j26151 We could not reproduce the issue after creating a model following your instructions. Please find the model we created as an attached file. The validation rule works fine for this model and if we disable the validation rule, xtend code generation creates an error message, as expected. Could you please modify the model and send us back the modified version which produces different results for the emf validation and xtend validation?
issue_08_reopened_working_example.zip

. Write a CX validation rule to detect the issue as part of the Validate action. This will have the side effect of highlighting the problematic elements in model tree, and displaying them in the Problems view.

The more involved fix above states that when validating your supplied model, validation should fail, and the offending deployment plan should be highlighted.  I do not see that happening with the 1.6 CX release and the model that you provided.
When generating descriptors, I see the background validation also succeed and the actual generation fails. (I do expect the generation to fail, although the validation should have failed before getting to that point.)

@j26151 : We think we have narrowed it down. The constraint fires in our development environments, but not when installed into RSA. We're trying to figure out why that is. No doubt something both trivial and esoteric.

@j26151 Apparently the problem was with the import of the ZML package in the DDS4CCM model.
We fixed the issue via #46 and created a draft milestone "CX4CBDDS 1.6.1 M1" from the "fix_zml_import_in_dds4ccm" branch. Please try the installers in the draft milestone and let us know if this solves the problem.

I have validated the bug. It looks like it all works now!.
Some additional comments about the RPMs. the 1.6.1 M1 tag produces a 1.6.0 rpm, where I would have expected a 1.6.1 rpm. Additionally, I have noticed that it is possible to install both ATCD and AXCIOMA cx rpms on a machine at the same time. Lastly, I think that it would be beneficial for the RPM to have a check in the %pre section to see if RSA is even installed yet, that way, if it isn't, you can exit the installation of the RPM without installing it and failing.

@j26151 : Sorry, the test build that was spun did not include version number updates for the plugins/features from the 1.6.0 release.  This will not affect your install experience. Each build includes the build date as part of the version number, so that a more recent build will always replace an older build, even it the version numbers don' t change.
We will need to discuss the timing of a 1.6.1 release. It will definitely contain this fix. We are also working on #45, which may be a candidate for inclusion, too.

Fixed by pull request #46.


Update Sketch Beta.app to latest version

After making all changes to the cask:

[X] brew cask audit --download {{cask_file}} is error-free.
[X] brew cask style --fix {{cask_file}} reports no offenses.
[X] The commit message includes the cask’s name and version.

Thank you for your PR! Closing in favour of https://github.com/caskroom/homebrew-versions/pull/4363


endpoints service_type element (k, v) should be required to avoid confusion/inconsistency with HashiCorp aws_vpc_endpoint default behavior

HashiCorp's "aws_vpc_endpoint" resource has a default "vpc_endpoint_type" of "Gateway". In the terraform-aws-modules/terraform-aws-vpc/vpc-endpoints submodule (in this repo), the default "service_type" seems to be "Interface" (I had to specify the "Gateway" service_type for my endpoints to avoid an empty list error coming from 'data "aws_vpc_endpoint_service"' (built out via for_each) in the submodule). You might want to require the service_type key for the endpoints so that others don't run into this issue (or is it too late now, as it would break existing Terraform code)? Thanks for your work.

We have chosen to default to Interface since the vast majority of service endpoints offered by AWS are only offered as interface endpoints - only S3 and DynamoDB are supported as gateway endpoints


Google Colab

How to easily install in google colab?

Hello @delta2golf!
You can roughly follow the steps in our tests CI workflow to have everything up and running (only the steps for Ubuntu) https://github.com/histolab/histolab/blob/master/.github/workflows/tests.yml#L73


Using pytest.ini in a location other than where the tests are created results in the tests not being executed

I am developing my custom test runner, and it functions correctly. However, I encounter an issue after installing pytest_robotframework where the tests do not run following the test collections. I suspect there might be a conflict between the pytest_robotframework plugin and my pytest.ini file.

this is my pytest.ini :
[pytest]
python_files = test_*.py *_test.py tca_*.py
python_classes = Test* tca_*

log_cli = True
log_cli_level = Debug
log_cli_format = [%(asctime)s.%(msecs)03d] [%(levelname)-3s] [%(name)s] %(message)s
log_cli_date_format = %Y-%m-%d %H:%M:%S

log_file_level = Debug
log_file_format = [%(asctime)s.%(msecs)03d] [%(levelname)-3s] [%(name)s] %(message)s
log_file_date_format = %Y-%m-%d %H:%M:%S

junit_family = xunit1
junit_duration_report = call

addopts = -p pytest_robotframework

Is there any recommendation?

will be fixed in the next version :)

@DetachHead Will version 2.5.2 support the fix? I've installed it, but the issue remains the same.

the fix worked for me and definitely in 2.5.2. could you please provide some more information about your setup:

what's the command you're using to run pytest?
where exactly is your pytest.ini file located in relation to your tests?

exit_code = pytest.main(args, plugins)
This is the pytest args :
['C:\new_xtr_ws\xtr\src\xtr\core\runner\pytest_plugins', 'C:\new_xtr_ws\demo-testing-projects\pytest_project\package1\test\test_tca1_1.py', 'C:\new_xtr_ws\demo-testing-projects\pytest_project\package1\test\test_tca1_2.py', '--junitxml=result\last_execution\Global\xtr-results.xml', '-p', 'no:cacheprovider', '-v', '-s', '--alluredir=result\last_execution\Global\allure-reports', '--timeout=300']
pytest.ini location : C:\new_xtr_ws\xtr\src\xtr\core\runner\pytest_plugins
tests path :
C:\new_xtr_ws\demo-testing-projects\pytest_project\package1\test\test_tca1_1.py
C:\new_xtr_ws\demo-testing-projects\pytest_project\package1\test\test_tca1_2.py

sorry but i still can't reproduce it. do you have any other plugins installed? could you maybe upload a git repo with a minimal reproduction of the issue?

Sorry, I don't have a git repository for my project.
Here are the plugins: allure-pytest-2.13.2, cov-3.0.0, pytest_robotframework-2.5.2, typeguard-4.1.5

And also, I defined a plugin with a pytest hook, but I tried running the project without my plugin, and I still have the same issue.

does it still happen if you disable all those plugins? does it work if you put the tests in the same location as your pytest.ini?

Disabling pytest_robotframework allows pytest to collect all items and execute them accordingly.
Disabling all other plugins except pytest-robotframework can lead to this error !

for pytest-robotframework
version 2.5.1 :
If the 'test' folder is placed in the same location as my pytest.ini file, pytest works perfectly. (However, I aim to define tests in a different location)

version 2.5.2 :
If placing the 'test' folder and pytest.ini in the same location still doesn't resolve the issue of tests not running.

version 3.0.0 :
If running my custom test runner is contributing to an exception in file xdist_utils under folder pytest_robotframework_internal
in this function is_xdist_master :

As a solution to address this exception :
def is_xdist_master(session: Session):     try :         return session.config.option.numprocesses is not None     except :         return  False
Even after resolving the exception, the issue with tests not running persists.

ok so i finally reproduced it. the problem is that you have both your tests and your pytest config file in a separate location to the working directory where pytest is being run. fixed in version 3.0.1


feat: Reward model

Description
https://github.com/camel-ai/camel/issues/889
Motivation and Context
https://github.com/camel-ai/camel/issues/889

[ ] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of example)

Implemented Tasks

[ ] Subtask 1
[ ] Subtask 2
[ ] Subtask 3

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[ ] I have read the CONTRIBUTION guide. (required)
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.

Thanks @Asher-hss , as mentioned in the issue, we also want to support  skywork (Seq. Classifier), could you also add this model?

Thanks wendong，I plan to update this model today.

The model is called [nemotron](https://build.nvidia.com/nvidia/nemotron-4-340b-instruct) not nemetrocan you fix that asap?

The model is called [nemotron](https://build.nvidia.com/nvidia/nemotron-4-340b-instruct) not nemetrocan you fix that asap?

I create a new pr to fix it now.


Grouping failures in testng-failed.xml for DataProvider with Factory

Look issue: https://github.com/cbeust/testng/issues/2521

Thanks for the fix! 👍


[modern-cpp-kafka] New port

[x] Changes comply with the maintainer guide
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is in the new port's versions file.
[x] Only one version is added to each modified port's versions file.

Close #32897

I don't think this really needs a CMake project. You can just add a config file directly to the port and install from the portfile.

I know. But I prefer provide a CMakeLists.

Usage passed on x64-osx with following demo code
set(CMAKE_CXX_STANDARD 17)

find_package(unofficial-modern-cpp-kafka CONFIG REQUIRED)
add_executable(test_kafka main.cpp)
target_link_libraries(test_kafka PRIVATE unofficial::modern-cpp-kafka::modern-cpp-kafka)

#include "kafka/AdminClient.h"
#include "kafka/Error.h"

int main() {
    kafka::Properties props;
    kafka::clients::admin::AdminClient client(props);
    return 0;
}

The usage test passed on x64-windows (header files found):
modern-cpp-kafka provides CMake targets:

    find_package(unofficial-modern-cpp-kafka CONFIG REQUIRED)
    target_link_libraries(main PRIVATE unofficial::modern-cpp-kafka::modern-cpp-kafka)


Download dependencies to a specific folder

Hi,
We are trying to download dependencies for my project, but we prefer to download to specific subfolder of our project folder, rather than the machine's .gradle folder.  Internet suggest writing a simple task to do the copying from the .gradle folder to any folder we desired.
We are wondering: Does the latest version of the gradle (v4.X.X) able to do this, with simple configuration, rather than having to write a task for such simple action?

I think you're referring to where the Gradle cache is located, which is where Gradle will download and cache files. This will always be located in the Gradle user home directory, which is configurable via the --gradle-user-home command line option.


Deployment via Docker & docker-compose

Setup a simple Dockerfile and docker-compose setup, to make it easy to deploy on the dataekspeditioner.dk website

We now have the website running on our webserver at https://market.dataekspeditioner.dk
Next steps:

[ ] ensure collectstatic and database migrations are executed automatically
[ ] make it easy run our tests
[ ] run tests automatically on Github Actions


Hint appearance vertical padding misnamed

There are two "Horizontal Padding (rem)" settings. The second acts as if it were "Vertical Padding (rem)"; it should probably be renamed.

*Saka Key 1.21.3 on Firefox 57.0a1 (2017-09-03) (64-bit)

Thanks for the notice!  This will be fixed in the next release.


fix(#4450 navbar): rotate 'Getting Started' arrow on click

Fixes #4450
Describe the changes you have made in this PR - UI Enhancement: Rotated the "Getting Started" arrow to improve the user experience.
Screenshots of the changes (If any) -
https://github.com/CircuitVerse/CircuitVerse/assets/93989204/f2064f93-c965-4ed3-8222-3a9cb35e2a12

@tachyons kindly check

Closing as there is active PR by the assigned contributor for the same issue.
From next time, try to get yourself assigned to a issue first.
Take a look at other issues.


Cleanup pre-release

Important fixes for PnP pre-release:

Mark pnp_protocol.* files as // DEPRECATED.  These are the helpers that we provided before the official API that came in #1891 was available.

While most vestigial samples we remove, it's possible customers are using these sample helpers in their product.  So we don't want to git delete in this case.
This also addresses @ahsonkhan feedback in this PR thread.

Samples had vestigial files and references to files paho_iot_hub_pnp_component_sample.c and paho_iot_hub_pnp_sample.c.  These were using the pnp_protocol.* stuff that was deprecated AND were replaced by paho_iot_pnp_component_sample.c and paho_iot_pnp_sample.c, respectively.

In this case the old samples (with "iot_hub_pnp*" and not the new "iot_pnp*") would be confusing to leave around.  They weren't being touch at all by any CMake rules, so just removing.

Have the provisioning sample send its maximum temperature always, not just when receiving something > default.  This is required to make the sample PnP Certified.

While presumably no one is shipping this sample much less certifying it!, we want to make it work out of the box with backend services in any event.

One question for @ahsonkhan / @RickWinter  - should I update the changelog.md in this checkin, or is that only something done as a later stage of release?  We have text from PM.


Creating or loading GPUParticles nodes crashes engine on macOS with Compatibility GLES3 renderer (Apple Silicon)

Godot version
4.0 beta 16
System information
macOS 13.1, GLES3, Apple M1 Pro GPU
Issue description
When creating a new GPUParticles2D or a GPUParticles3D node while having the editor set to the Compatibility (GLES3) renderer on a macOS device with an M1 architecture, it crashes reliably after a brief delay. This also happens when exporting the project and running it, as well as opening an existing project after switching from the Vulkan renderer to the GLES3 renderer. However, it only occurs when emitting is set to true, a non-emitting GPUParticles node does not cause a crash.
This only happens on macOS, it works just fine on Windows.
Steps to reproduce

Create a new project
Switch to Compatibility renderer
Create a new 2D or 3D scene
Create a new GPUParticles2D or GPUParticles3D node
The editor crashes, since the node is automatically created with emitting set to true

Alternatively:

Open provided minimal reproduction project
Change renderer to Compatibility and restart the editor

Minimal reproduction project
Minimal reproduction project (zip)

relevant traceback (copy-pasted from #77681 )
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.1.dev.custom_build (d9cf3695033a71902010239a27b7a264db7840cc)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] 1   libsystem_platform.dylib            0x00000001979daa24 _sigtramp + 56
[2] 2   libGLProgrammability.dylib          0x00000001fc63e27c glpLLVMCGSwitchStatement + 176
[3] 3   libGLProgrammability.dylib          0x00000001fc634ad8 glpLLVMCGNode + 588
[4] 4   libGLProgrammability.dylib          0x00000001fc63de60 glpLLVMCGBlock + 444
[5] 5   libGLProgrammability.dylib          0x00000001fc634aa8 glpLLVMCGNode + 540
[6] 6   libGLProgrammability.dylib          0x00000001fc63de60 glpLLVMCGBlock + 444
[7] 7   libGLProgrammability.dylib          0x00000001fc634aa8 glpLLVMCGNode + 540
[8] 8   libGLProgrammability.dylib          0x00000001fc650a9c glpLLVMCGIfStatementShortCircuit + 208
[9] 9   libGLProgrammability.dylib          0x00000001fc634ab8 glpLLVMCGNode + 556
[10] 10  libGLProgrammability.dylib          0x00000001fc63de60 glpLLVMCGBlock + 444
[11] 11  libGLProgrammability.dylib          0x00000001fc634aa8 glpLLVMCGNode + 540
[12] 12  libGLProgrammability.dylib          0x00000001fc63da68 glpLLVMCGFunctionDefinition + 2664
[13] 13  libGLProgrammability.dylib          0x00000001fc633744 glpLLVMCGTopLevel + 1480
[14] 14  libGLProgrammability.dylib          0x00000001fc65b20c glpLinkProgram + 10004
[15] 15  libGLProgrammability.dylib          0x00000001fc675140 ShLink + 208
[16] 16  GLEngine                            0x00000001fc829ac8 gleLinkProgram + 1228
[17] 17  GLEngine                            0x00000001fc797bcc glLinkProgramARB_Exec + 256
[18] ShaderGLES3::_compile_specialization(ShaderGLES3::Version::Specialization&, unsigned int, ShaderGLES3::Version*, unsigned long long) (in godot.macos.editor.dev.arm64) (shader_gles3.cpp:0)
[19] ShaderGLES3::_initialize_version(ShaderGLES3::Version*) (in godot.macos.editor.dev.arm64) (shader_gles3.cpp:678)
[20] ShaderGLES3::_version_bind_shader(RID, int, unsigned long long) (in godot.macos.editor.dev.arm64) (shader_gles3.h:204)
[21] ParticlesCopyShaderGLES3::version_bind_shader(RID, ParticlesCopyShaderGLES3::ShaderVariant, unsigned long long) (in godot.macos.editor.dev.arm64) (particles_copy.glsl.gen.h:29)
[22] GLES3::ParticlesStorage::_particles_update_instance_buffer(GLES3::ParticlesStorage::Particles*, Vector3 const&, Vector3 const&) (in godot.macos.editor.dev.arm64) (particles_storage.cpp:892)
[23] GLES3::ParticlesStorage::update_particles() (in godot.macos.editor.dev.arm64) (particles_storage.cpp:1102)
[24] RenderingServerDefault::_draw(bool, double) (in godot.macos.editor.dev.arm64) (rendering_server_default.cpp:87)
[25] RenderingServerDefault::draw(bool, double) (in godot.macos.editor.dev.arm64) (rendering_server_default.cpp:397)
[26] Main::iteration() (in godot.macos.editor.dev.arm64) (main.cpp:3405)
[27] OS_MacOS::run() (in godot.macos.editor.dev.arm64) (os_macos.mm:718)
[28] main (in godot.macos.editor.dev.arm64) (godot_main_macos.mm:77)
[29] 29  dyld                                0x0000000197653f28 start + 2236
-- END OF BACKTRACE --
================================================================

I suggest we use a similar workaround as proposed in https://github.com/godotengine/godot/issues/54052, where we convert GPUParticles nodes to CPUParticles at load-time on macOS. This will break many particle effects, but it's better than crashing the engine or not having any particles show up.

Still happening on 4.1.1 on MacOS Ventura 13.5.2 :(.

Still happening on 4.1.2. Is there no workaround we can utilize in the meantime without using a different machine?

It might be worth checking if ANGLE fixes this issue: https://github.com/godotengine/godot/pull/72831

Still happening on 4.1.3 on MacOS Sonoma 14.1. Crash immediately when adding or editing GPUParticles node.

It might be worth checking if ANGLE fixes this issue: #72831

For future reference, ANGLE does fix this issue but it's no longer the default in 4.2.1 following https://github.com/godotengine/godot/pull/85785.

It might be worth checking if ANGLE fixes this issue: #72831

For future reference, ANGLE does fix this issue but it's no longer the default in 4.2.1 following #85785. (It was the default in 4.2 only.)
You can opt into using ANGLE in the Project Settings (Rendering Driver.macos). This may impact performance negatively though.

I tried doing that but it still crashes the engine. (on 4.2.1_stable and 4.3_dev - master branch)

Adding a GPU particles node also crashes Godot 4.2.1-stable with Driver.macos set to "opengl3_angle" on macOS 14.2.1 (minor version increase from prev commenter).
https://gist.github.com/danneu/8cbe6c9f399f37dbbf4d5742e70cf0e5

Happens to us also on M1 2021 macOS 14.2.1. Is there any short-term resolution to unblock our team?
Thanks,
Jan

Is there any short-term resolution to unblock our team?

You can convert GPUParticles3D nodes to CPUParticles3D by selecting a GPUParticles3D node then using the GPUParticles3D menu at the top of the 3D editor viewport. This has some limitations though (no support for custom particle shaders, attractors, collision or turbulence).

Thanks for the suggestion.
Converting back to CPU is not really an option so I believe hiding is the only viable one.
The problem with hiding: It might work during game play but still poses a big issue during development in the editor. As soon as the particle scene is opened once in the editor it instantly crashes and there is no chance of even starting the project again on Mac. Any suggestion how we could handle this on the short-term until this bug is fixed?

Any suggestion how we could handle this on the short-term until this bug is fixed?

Without modifying the engine source code, the only way to avoid this is to add emitting = false below the particle node in the .tscn file. This can't be done if the scene is saved to a binary .scn file though.

Just an update on this issue. It's something that we are looking into, but it looks like there will be no easy solution.
GPUParticles work fine on intel macs. On Apple silicon macs, they cause this crash (likely because Apple silicon devices don't have OpenGL drivers, they instead of a layer that implements OpenGL over Metal and apparently that layer is missing support for transform feedback).
The typical solution would be to use ANGLE to translate OpenGL to Metal so we don't have to rely on Apple's broken automatic translation. Unfortunately, the ANGLE over Metal variant has significant performance problems and leaks memory rapidly making it unusable. The ANGLE over OpenGL variant works much better, but doesn't solve this crash.
Our best option is to workaround the performance issues and leaks. We already have identified a workaround for the leak, but it requires significant changes and we aren't sure why they are necessary (https://github.com/godotengine/godot-angle-static/pull/3). We need to investigate how to workaround the performance issues still.
Needless to say the Apple ecosystem is not friendly to devs who want to support multi-platform and/or older devices. :(

@clayjohn thanks for the information on this!
With Apple's apparent new interest in gaming, do you think it would be worth submitting feedback to Apple dev support or another contact method for the issues that are clearly caused by a poor Apple implementation?
2023 was the last year that Apple officially sold Intel based products and all future Apple systems will Apple Silicon. So I believe we can expect Apple Silicon and Metal to be the overwhelming majority of iOS and MacOS developer's rendering platform in the next 2-3 years.
I myself still have my old Intel MacBook Pro but I just switched to M3 Max. I can basically run Unreal Engine 5, Unity, and Godot with really good performance on M3 and I would greatly prefer the benefit of an all in one development platform vs needing to swap to my Intel Mac or RDP into my Windows machine when I'm not at my desk if I want to target web or compatibility for older hardware that requires the compatibility renderer.

With Apple's apparent new interest in gaming, do you think it would be worth submitting feedback to Apple dev support or another contact method for the issues that are clearly caused by a poor Apple implementation?

Unfortunately Apple has been quite clear that they have no intention of supporting OpenGL/WebGL.
Apple's interest in gaming only extends to gaming on devices that support Metal (and soon WebGPU for web gaming). The future for Apple devices appears like it is going to be Metal/WebGPU only.
Unfortunately, that means it is on us to find workarounds because we are the ones who care about supporting multi-platform and low-end devices.

Hi @Calinou, I ran into this issue when porting an Android app to iOS.  Which renderer do you recommend that I use for the iOS version of the app?  Forward+ or Mobile?

just stumbled upon this and it is fixed in 4.3.dev6

I wonder if this PR https://github.com/godotengine/godot/pull/88816 is responsible. It aimed at resolving a crash for super low end android devices. But seeing as this was an odd driver bug anyway, its possible that they shared a common root

I just confirmed. This bug is fixed in dev6/master. Reverting https://github.com/godotengine/godot/pull/88816 re-introduces the crash.
So I can happily report that this issue is fixed by https://github.com/godotengine/godot/pull/88816 :)

What you can do in the meantime is add a macos override to the Rendering Method project setting as follows, before adding any GPUParticles to the project:

After clicking Add, set the override's value to forward_plus or mobile. The project will look different than with the Compatibility rendering method (especially in 3D), but GPUParticles should work.
If you're importing an existing project that has GPUParticles in its main scene, edit project.godot with a text editor before opening the project in the editor to add the override by adding this at the bottom of the file:
[rendering]

renderer/rendering_method.macos="forward_plus"

If there's already a [rendering] section in project.godot, add renderer/rendering_method.macos="forward_plus" at the end of that section instead.

Thank you! this worked for me

For anyone new to Godot like myself: As of late July 2024 version 4.3 isn't quite released yet but you don't need to build from source. Official 4.3 release candidate builds can be found here: https://godotengine.org/download/preview/
4.3rc1 fixes the issue for me.


Accounts index not displaying all non-admin roles after updating orion to 1.3.0

After updating Orion 1.3.0, on the accounts index page, all the non-admin roles is not showing on he table, see image below:

Is this normal behaviour for version 1.3.0?

Same issue, there.

#257 fixes the issue.

Thanks @PEM--


git branch not updating when using Remote WSL

VSCode Version: <IP_ADDRESS>
OS Version: Version 20h2 (OS Built 19042.421)

Git branch does not change when browsing between different projects in the explorer when using the Remote WSL.
Steps to Reproduce:

open connection to with remote WSL. I am using ubuntu 20.04
Open folder/workspace containing mulitple git projects that reside inside of WSL folders. In my case I go via symlink that points to my windows directory   /home/arahman/work --> /mnt/c/Users/athiq/Woskapces/work
move between the projects, the branch in bottom left highlighted in blue does not change. only sticks to the first branch in the first folder browsed to
This problem does not occur when not using WSL

Does this issue occur when all extensions are disabled?: Yes, Kind of. I cannot disable the Remote WSL extension. All other extensions are disabled

You should use Remote WSL to edit files inside WSL. If you want to edit files on the Window side, please just use the regular VS Code.


Create new androapp  CustomListViewApp

Please describe about your Androapp

ListView App with OnClickListner
Java

Describe alternatives you've considered
No Alternates
Additional context
custom Listview with adapter and onclicklistner

@aadityamp01 please review the PR


[TACHYON-1132] Fix resolved path usage

Using getPath strips the scheme/authority which is required.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/6072/
Test PASSed.

LGTM

LGTM

A post-merge comment: there should be a test to cover this.


[WIP] Upgrade to ovirt-engine-nodejs-modules:2.1.0

Why?

adopt latest yarn 1.x
adopt nodejs 14 for running builds (faster and better memory management)

Note: Currently the build.repos has a temporary repo link to the jenkins ci build for the patch that bumps ovirt-engine-nodejs-modules to 2.1.0 (https://gerrit.ovirt.org/c/ovirt-engine-nodejs-modules/+/116116) so the new version can be tested before merging that patch.  This PR should not be merged until that patch is merged.

This PR is no longer necessary given changes in #1534.
(Patch 116116)[https://gerrit.ovirt.org/c/ovirt-engine-nodejs-modules/+/116116] has been merged and 2.1.1 is already available.
Note: To get nodejs v14 in stdci requires a change to the mock runner config files to enable the correct module version.  See https://gerrit.ovirt.org/c/jenkins/+/117671.


[P000591] Rep. Tom Price

Rep. Tom Price:
http://tomprice.house.gov
Likely contact form URL to start with:
http://tomprice.house.gov/contact-me

YAML file lost. I am working on it.


Support for multi-label classification and Kaggle integration

Support multilabel classification
Avoid having to specify the number of classes

Glean the number of classes from the metadata file (no need to
ask for user input)
Isolate augmentation code for inference
Display class names in the EDA notebook

Support inference

Let test images be loaded from a separate directory
called test_images

Also added SGD as an optimizer option

Support uploading code to Kaggle

Add a script for uploading code and models to a private
Kaggle dataset
Add a notebook that can be used for making submissions
on Kaggle

Miscellaneous

Document usage of the generated code
Correct a few linter errors
Change default hyperparameter values

Increase default epochs from 30 to 40
Decrease default batch size to 32
Slower rate of decay for learning rate
(larger gamma)

More options inside sweep.yaml
Use ruamel to read config.yaml files

some names in the dataset (files, columns) are now assumed to match with those in https://www.kaggle.com/c/plant-pathology-2021-fgvc8/data
the data in these buckets have been updated to match with the naming conventions in this code:

gs://luminide-example-darkmatter
gs://luminide-example-plant-pathology

the branch of this repo that is used in the production code (releases/2) now has the code from this PR (to make it easy to test)
also https://github.com/luminide/example-darkmatter now has code generated from this template (so that the tutorial in its current form is operational)

recommended way to test (on staging):

push the latest ide-server code to the staging server
create an empty project and then generate code from template
accept the default for all options other than "Kaggle". pick True for Kaggle.
follow the usage instructions in the generated README.md file

import data from gs://luminide-example-plant-pathology
run eda.ipynb
run a training session
tune using full sweep
upload to kaggle
submit entry on kaggle

possible issues:

ruamel package not installed on compute servers (pip install ruamel.yaml as a temporary solution)
https://github.com/luminide/ide-service/issues/589
https://github.com/luminide/ide-service/issues/590

TODO:

making this work with https://www.kaggle.com/c/plant-pathology-2021-fgvc8/data (very slow right now)
make a notebook for reporting the results instead of just leaving a png file behind
stretch goal - include class activation maps in the report

Data import was really fast (gs://luminide-example-plant-pathology). Maybe 30 sec or so.  Nice.
Modify and run eda.ipynb:

At first I thought it was a script I needed to run.  When I realized it was just a notebook, just clicking on it worked.
I chose "restart the kernel, then re-run the entire notebook".  Got this error:
ModuleNotFoundError: No module named 'util'
I installed ruamel.yaml but that didn't help (good news is that "manage packages" and "pip install" all worked correctly)
I didn't modify eda.ipynb.  Not sure how I was supposed to modify it.  Maybe that's the problem?

To train, use the Run Experiment menu.

Worked well.  Assumption is that the user will know to click on the "Start full training" button.

To monitor training progress, use the Experiment Visualization menu.

Worked well.

To tune the hyperparameters, edit sweep.yaml as desired and launch a sweep from the Run Experiment tab.

Worked well.  Assumption is that the user knows to click on the Sweep tab and click the "Start full sweep" button.
Sweep was interrupted, presumably by the spot instance getting preempted. Not an issue with the PR, but:

Error message "Compute detached" was displayed. Good.
Error message "Code directory empty" was displayed.  Seems like a bug.
No log files were saved to the Experiment Tracking output directory.   Also looks like a bug.

After an experiment is complete, use the file browser on the IDE interface to access the results on the IDE Server.

Looks good.  Verified the sweep results chart matched the TensorBoard output:

Use the Experiment Tracking menu to track experiments.

As mentioned, logs for full training looked good.  Logs for sweep were missing (due to spot instance getting preempted).

To use this repo for a Kaggle code competition, use kaggle.sh and kaggle.ipynb to upload and submit the code to Kaggle.

Failed with this message:
error: ~/.kaggle/kaggle.json not found on Compute Server
Run Experiment Process Errored

Looks like my Kaggle token was missing.  Kind of confusing because I think I didn't need it to download the dataset (got it from a Google bucket), so I hadn't already done that.  Maybe include this in the instructions somewhere.
Is there a typo in the kaggle.sh script?  Should the pathname be "~/.luminide/kaggle.json" instead of "~/.kaggle/kaggle.json"?  I see the token in that directory on the IDE server -- but it's still missing on the Compute server.

Looks like my Kaggle token was missing.

yes, that is a known issue - https://github.com/luminide/ide-service/issues/586

Using this repo with Luminide

Attach a Compute Server and download a dataset. An example dataset is available at gs://luminide-example-plant-pathology.

Good.  (Ran into some Compute Server, rsync, and GUI issues.  But pretty sure all are unrelated to this ticket.  Robert filed separate issues for them).

For exploratory analysis, run eda.ipynb.

Good.

To train, use the Run Experiment menu.

Good.

To monitor training progress, use the Experiment Visualization menu.

Good.

To tune the hyperparameters, edit sweep.yaml as desired and launch a sweep from the Run Experiment tab.

Good.

After an experiment is complete, use the file browser on the IDE interface to access the results on the IDE Server.

Good.

Use the Experiment Tracking menu to track experiments.

Good.

To use this repo for a Kaggle code competition:

Configure your Kaggle API token on the Import Data tab.

(skipped)

- Run [kaggle.sh](kaggle.sh) as a custom experiment to upload the code to Kaggle.

Good.

- To create a submission, copy [kaggle.ipynb](kaggle.ipynb) to a new Kaggle notebook and run it.

Worked correctly.  Only issue was that I had to iterate multiple times and fix the error each time.  Might be nicer to add a comment in the README and/or notebook so the user knows to do these things up front (or at least sees that they're required, so they're not surprised if/when they do get an error):

Run this on Kaggle after adding the notebook output of https://www.kaggle.com/luminide/wheels as Data
Your dataset at https://www.kaggle.com/<kaggle_username>/kagglecode should be added as Data
Add the competition dataset
Disconnect from the Internet
Enable the GPU

Once I did each of these, it looks like it worked.  (I submitted my results 13 minutes ago, and it's still running.  But looks good).

Submission succeeded.  0.62914 (private)  and 0.59948 (public) comes in around 450/626.

One confusing aspect is that the submission.csv file does contain a row with an empty label.  Not sure why, e.g. is it an error (even healthy leaves should be labeled "healthy"? is it hurting the submission score (seems likely)?  Might be worth investigating.
image,labels
85f8cb619c66b863.jpg,
ad8770db05586b59.jpg,complex frog_eye_leaf_spot
c7b03e718489f3ca.jpg,frog_eye_leaf_spot

In any case, looks like everything's working.  Nice.

merging... will take care of the issues raised in the next PR.


Implement std::error

To release ssi publicly, we should use thiserror to easily derive std::error::Error and make the API even more easy to use.
The main benefit of std::error::Error is the chain of errors, makes debugging easier.

this has been implemented


Add api to reject withdrawal request

This pr will be merged after merging #220 with changing param name.
(WithdrawRequestList -> WithdrawRequestMap)

Parameter name and type name was updated.

Thanks for the reviews!


[SPARK-49992][SQL] Default collation resolution for DDL and DML queries

What changes were proposed in this pull request?
This PR proposes not using session-level collation in DDL commands (create/alter view/table, add/replace columns).
Also, resolution of default collation should happen in the analyzer and not in the parser. However, due to how we are checking for default string type (using reference equals with StringType object) we cannot just replace this object with StringType("UTF8_BINARY") because they compare as equal so the tree node framework will just return the old plan. Because of this we have to perform this resolution twice, once by changing the StringType object into a TemporaryStringType and then back to StringType("UTF8_BINARY") which is not considered a default string type anymore.
Another thing is that the dependent rules ResolveInlineTables and CollationTypeCoercion are updated so that they don't execute if there are still unresolved string types in the plan.
Why are the changes needed?
The default collation for DDL commands should be tied to the object being created or altered (e.g., table, view, schema) rather than the session-level setting. Since object-level collations are not yet supported, we will assume the UTF8_BINARY collation by default for now.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Added new unit tests.
Was this patch authored or co-authored using generative AI tooling?
No.

The last commit changes code comment only, we don't need to test it again. I'm merging it to master, thanks!


AutoImplement delegate dependencies

If a type takes e.g. a Func<T> in it's constructor we should auto-implement that.
If it takes a Func<int, T> we should also auto-implement that provided int is used anywhere in the transient dependency chain for that type.

Completed in https://github.com/YairHalberstadt/stronginject/pull/27


How to build iml on centos6.5 ?

Description
(I am a beginner from china，so poor English， please)
I need to build iml on centos6.5, but I failed! so please help me how to build iml on centos6?
Below are two failed Build logs;

one is build iml-<IP_ADDRESS> on centos6.5, I think the iml-<IP_ADDRESS> source code missing some files,Maybe my false.

another is build iml-<IP_ADDRESS> on centos6.5

Build iml-<IP_ADDRESS> On Centos6
 [[ /usr/lib/python2.6/site-packages/chroma_agent/chroma_common/lib/evaluator.pyc == /etc/init/tty.conf ]]
+ echo '/usr/lib/python2.6/site-packages/chroma_agent/chroma_common/lib/evaluator.py[c,o]'
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id /root/iml/iml-2.3/chroma-agent/_topdir/BUILD/chroma-agent-<IP_ADDRESS>
find: `debug': No such file or directory
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-compress
+ /usr/lib/rpm/redhat/brp-strip-static-archive /usr/bin/strip
+ /usr/lib/rpm/redhat/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
+ /usr/lib/rpm/brp-python-bytecompile /usr/bin/python
Bytecompiling .py files below /root/iml/iml-2.3/chroma-agent/_topdir/BUILDROOT/chroma-agent-<IP_ADDRESS>-4240.x86_64/usr/lib/python2.6 using /usr/bin/python2.6
+ /usr/lib/rpm/redhat/brp-python-hardlink
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Processing files: chroma-agent-<IP_ADDRESS>-4240.noarch
Requires(interp): /bin/sh
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires(post): /bin/sh selinux-policy
Requires: /usr/bin/python python(abi) = 2.6
Processing files: chroma-agent-management-<IP_ADDRESS>-4240.noarch
Requires(interp): /bin/sh /bin/sh /bin/sh
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(VersionedDependencies) <= 3.0.3-1
Requires(post): /bin/sh
Requires(postun): /bin/sh
Requires: /bin/sh /usr/bin/python python(abi) = 2.6
Conflicts: sysklogd
Obsoletes: pacemaker-iml <= 1.1.7-6.wc2.el6 pacemaker-iml-cluster-libs <= 1.1.7-6.wc2.el6 pacemaker-iml-libs <= 1.1.7-6.wc2.el6 pacemaker-iml-cli <= 1.1.7-6.wc2.el6
Processing files: chroma-agent-devel-<IP_ADDRESS>-4240.noarch
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: python(abi) = 2.6
Checking for unpackaged file(s): /usr/lib/rpm/check-files /root/iml/iml-2.3/chroma-agent/_topdir/BUILDROOT/chroma-agent-<IP_ADDRESS>-4240.x86_64
Wrote: /root/iml/iml-2.3/chroma-agent/_topdir/RPMS/noarch/chroma-agent-<IP_ADDRESS>-4240.noarch.rpm
Wrote: /root/iml/iml-2.3/chroma-agent/_topdir/RPMS/noarch/chroma-agent-management-<IP_ADDRESS>-4240.noarch.rpm
Wrote: /root/iml/iml-2.3/chroma-agent/_topdir/RPMS/noarch/chroma-agent-devel-<IP_ADDRESS>-4240.noarch.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.cHTux6
+ umask 022
+ cd /root/iml/iml-2.3/chroma-agent/_topdir/BUILD
+ cd chroma-agent-<IP_ADDRESS>
+ rm -rf /root/iml/iml-2.3/chroma-agent/_topdir/BUILDROOT/chroma-agent-<IP_ADDRESS>-4240.x86_64
+ exit 0
mv _topdir/RPMS/noarch/chroma-agent-*.noarch.rpm dist/
rm -rf _topdir
make[1]: Leaving directory `/root/iml/iml-2.3/chroma-agent'
set -e; \
	if true; then \
		make -C chroma-manager all; \
		if [ all != download -a -d chroma-manager/dist/ ]; then \
			cp -a chroma-manager/dist/* dist/; \
		fi; \
	fi
+ sed -e 's/^v//' -e 's/RC[0-9]*//'
+ git describe --match 'v[0-9]*'
warning: tag 'v<IP_ADDRESS>RC4' is really 'v<IP_ADDRESS>' here
make[1]: Entering directory `/root/iml/iml-2.3/chroma-manager'
rm -rf  dist
mkdir dist
echo 'VERSION = "<IP_ADDRESS>"' > scm_version.py
echo 'PACKAGE_VERSION = "<IP_ADDRESS>"' >> scm_version.py
echo 'BUILD = "4240"' >> scm_version.py
echo 'IS_RELEASE = True' >> scm_version.py
Setting up ziplocker module for development...

cp:  can't state "../../../../chroma-externals/ziplocker/node_modules/" : No such file or directory
make[1]: *** [ziplocker/node_modules] Error 1
make[1]: Leaving directory `/root/iml/iml-2.3/chroma-manager'
make: *** [chroma-manager] Error 2

Build iml-<IP_ADDRESS> On Centos6
I have tried to build iml-<IP_ADDRESS> on centos6 ,but I failed!
this is the failed log. Maybe npm repository lost and missed some files.
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm info preinstall<EMAIL_ADDRESS>npm info trying registry request attempt 1 at 22:19:57
npm http GET https://registry.npmjs.org/iml/realtime/6.0.0
npm info trying registry request attempt 1 at 22:19:57
npm http GET https://registry.npmjs.org/iml/view-server/6.4.0
npm info trying registry request attempt 1 at 22:19:57
npm http GET https://registry.npmjs.org/iml/old-gui/2.1.2
npm info trying registry request attempt 1 at 22:19:57
npm http GET https://registry.npmjs.org/iml/socket-worker/3.2.0
npm http 404 https://registry.npmjs.org/iml/realtime/6.0.0
npm ERR! Error: No dist in undefined package
npm ERR!     at next (/usr/lib/node_modules/npm/lib/cache.js:746:26)
npm ERR!     at /usr/lib/node_modules/npm/lib/cache.js:739:5
npm ERR!     at saved (/usr/lib/node_modules/npm-registry-client/lib/get.js:148:7)
npm ERR!     at /usr/lib/node_modules/graceful-fs/polyfills.js:133:7
npm ERR!     at Object.oncomplete (fs.js:108:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>
npm ERR! System Linux 2.6.32-431.el6.x86_64
npm ERR! command "node" "/usr/bin/npm" "i" "-d"
npm ERR! cwd /root/iml/integrated-manager-for-lustre/chroma-manager/ui-modules
npm ERR! node -v v0.10.48
npm ERR! npm -v 1.3.6
npm http 404 https://registry.npmjs.org/iml/old-gui/2.1.2
npm http 404 https://registry.npmjs.org/iml/view-server/6.4.0
npm http 404 https://registry.npmjs.org/iml/socket-worker/3.2.0
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /root/iml/integrated-manager-for-lustre/chroma-manager/ui-modules/npm-debug.log
npm ERR! not ok code 0
make[1]: *** [ui-modules] Error 1
make[1]: Leaving directory `/root/iml/integrated-manager-for-lustre/chroma-manager'
make: *** [chroma-manager] Error 2

Hi @iskylite,
You should try to build latest IML 4.0.7 using CentOS 7.5.
Use these instructions to build:
yum install -y yum-plugin-copr make git epel-release python-setuptools rpm-build ed python-virtualenv systemd-devel graphviz-devel createrepo;

yum group install -y "Development Tools";

yum copr enable managerforlustre/manager-for-lustre -y;

yum copr enable ngompa/dnf-el7 -y;

yum install -y nodejs npm dnf 'dnf-command(repoquery)' ruby libpqxx-devel;

export distro=${distro:-el7}

cd integrated-manager-for-lustre/

scripts/jenkins_build

thx， @jgrund
Thanks for you help, but I need to build IML using CentOS6.5 or just have a iml-.tar.gz to be installed on CentOS6.5 . Because  the cluster that I have managed is running CentOS6.5 .
So , I need a tar ball having been built for CentOS 6.5 , the way to build IML using CentOS6.5 .
Please.

hi， @jgrund
I'm asking you to help me building IML using CentOS6.5. Or do you have a tar ball like iml-<IP_ADDRESS>.tar.gz to intsall iml software on CentOS6.5 , I need it ,please.

sorry, @johnsonw , I just get your reply.
I can't upgrade the operating system from 6.5 to 7.5? There are many software dependent operating systems OS 6.5. In fact, I don't need many new features. I just need the older IML software to monitor the lustre file system. So I need to build iml using CentOS6.5 , or do you have the older iml install package  for CentOS6.5.


BatchingRabbitTemplate Overwrites Custom Headers of Batched Messages

Description:
When sending multiple messages using the 'BatchingRabbitTemplate', each message has its own custom headers. However, the BatchingRabbitTemplate removes all custom headers from each message in the batch and instead applies the headers from the first message to all messages in the batch.
Steps to Reproduce:
Create multiple messages, each with distinct custom message headers.
Use BatchingRabbitTemplate to send these messages as a batch.
Observe the headers of each message in the batch.
Used following template:
@Bean
public BatchingRabbitTemplate batchingRabbitTemplate(ConnectionFactory connectionFactory) {
    BatchingStrategy strategy = new SimpleBatchingStrategy(20, 25_000, 10_000);
    ThreadPoolTaskScheduler scheduler = new ThreadPoolTaskScheduler();
    scheduler.setPoolSize(1);
    scheduler.initialize();
    BatchingRabbitTemplate template = new BatchingRabbitTemplate(strategy, scheduler);
    template.setConnectionFactory(connectionFactory);
    template.setMessageConverter(converter());
    return template;
}

Create Message with custom header and send (Example):
batchingRabbitTemplate.convertAndSend(exchange.getValue(), routingKey.getValue(), myObject, message -> {
    MessageProperties properties = message.getMessageProperties();
    properties.setPriority(priority);
    properties.setType("Sample-type");
    properties.setHeader("custom-header", "custom-value");
    return message;
});

Expected Behavior:
Each message should retain its original custom headers when sent in a batch.
Actual Behavior:
All messages in the batch receive the headers of the first message, losing their individual custom headers.
Environment:

Rabbit-amqp version: 3.0.13
Java Version: 17

Thank you very much!

See Javadocs:
/**
 * A simple batching strategy that supports only one exchange/routingKey; includes a batch
 * size, a batched message size limit and a timeout. The message properties from the first
 * message in the batch is used in the batch message. Each message is preceded by a 4 byte
 * length field.
 *
 * @author Gary Russell
 * @since 1.4.1
 *
 */
public class SimpleBatchingStrategy implements BatchingStrategy {

So, what you show is really expected.
Even if we do batching, still only a single AMQP message is emitted.
You might look into a custom BatchingStrategy which would batch those headers as well.

Hi @artembilan
Thank you for the clarification.


Switch over to windows-rs

Right now we're still reliant on the legacy winapi crate that's slowly being replaced with windows-rs, we'll need to do the same for our DirectX support.

We've already converted our public API to (by default) not expose any specific windows implementations and accept c_void pointers instead. Head-start made in the examples to show easy compatibility: https://github.com/Traverse-Research/gpu-allocator/pull/47 - and we can do the same on the internal side of things to have a cleaner, more convenient and safer API :)


附件设置，使用又拍云存储，提交时提示option key not exist错误。

Your current Sonic version
No response
Describe this feature
附件设置，使用又拍云存储，提交时提示option key not exist错误。
Additional information
No response

Close as duplicate of #226


wip: projects census

What type of PR is this?
/kind cleanup
/kind documentation
Any specific area of the project related to this PR?
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #44
Special notes for your reviewer:
Currently WIP.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This is great @leogr!

What about putting this in a special repository? (github.com/falcosecurity/falcosecurity)
So that you can see the index on the home of the falcosecurity Github profile.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, leogr, maxgio92
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr,maxgio92]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/hold cancel


pyarrow interoperability and integration testing

We're starting to get some bug reports in Apache Arrow from koalas users
https://issues.apache.org/jira/browse/ARROW-7986
A user commented

koalas in this case relies on pyarrow to convert the pyspark.ml.linalg-specific SparseVector, but arrow does not know what to do with it. The SparseVector comes from "libsvm" format. Here is an example using that format.

We've been working on providing tools to enable third party extensibility as well as informing the Arrow libraries how to handle serialization. There's probably some other things we can do to help in these scenarios (without taking on responsibility in Apache Arrow for handling every third party data structure out there)
Let us know how we can help with this so that we can coordinate and clarify any work needed on each side of the koalas / pyarrow divide
cc @jorisvandenbossche

Thanks for escalating the issue here!
It seems related to Spark UDT and Arrow.
Actually we can have a workaround to convert from/to pandas DataFrame/Series including Spark UDT objects, but I don't know how it works when manipulating pandas/Koalas.
If the user wants to use it in some function taking user functions, like apply, applymap, etc., Koalas doesn't support Spark UDTs since Koalas relies on PySpark's pandas UDFs which doesn't support Spark UDTs yet. (See e.g., SPARK-29952)
If you already have something to inform the Arrow libraries how to handle serialization of third party libraries, we can ask Spark community to support Spark UDT with it.

At the moment I don't think we have an API to provide for user-defined "unboxing" of array cell types into the corresponding Arrow storage, so we'd need to do a bit of thinking about what should happen. Here is a JIRA issue about the topic
https://issues.apache.org/jira/browse/ARROW-8004

Did https://github.com/databricks/koalas/pull/1324 fix the original reported issue from https://issues.apache.org/jira/browse/ARROW-7986 about converting the sparse vector to a koalas Series?

Yes, the issue https://issues.apache.org/jira/browse/ARROW-7986 can be closed. #1324 fixed the original issue.
However, we should note that this UDT support itself is supposed to be private at this moment, and Koalas does not currently support nested types.


Docs for publishing the operator in OperatorHub

Fixes #158
Proposed Changes

Docs for publishing the operator on OperatorHub

Release Note

blocked by https://github.com/knative/operator/pull/210, https://github.com/knative/operator/pull/200 and https://github.com/knative/operator/pull/201

cc @houshengbo
Do you want to try the 0.16 with the instructions?
Ticket: https://github.com/knative/operator/issues/212

@aliok Sure, 0.16.
Could you also update the instruction in this PR. I did not see you changed the instruction based on my question.

@houshengbo Sorry, I fixed it now.
Please have a look and let's get this merged

/lgtm


Add tests for base image volumes

And test_ha, test_engine_upgrade also needs update. We can give test_recurring_job a pass for now since the cronjob part shouldn't affect by the base image feature.


[GHSA-9324-jv53-9cc8] dio vulnerable to CRLF injection with HTTP method string

Updates

Affected products

Comments
Reference links:
CVE-2021-31402: This is the identifier of the vulnerability in the NVD database.
OSV - Open Source Vulnerabilities: Provides additional information about the vulnerability and the fix.
Issue #1752: Contains discussion and updates regarding the vulnerability and its fix in the project's GitHub repository.
Code commit:
Commit cfug/dio@927f79e: Describes the specific change made to fix the vulnerability and can be used as a reference for technical details.
Broader context:
You can search for other posts and discussions in the project's GitHub repository (such as Issue #1130) to get more context and information regarding the vulnerability and the fix.

Hi there @AlexV525! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

What is the point of changing the modified date? What data does the field rely on?

I executed the application on the Linux system and it worked without showing any error. The problem is that when installing the java project, I changed the version of the buckets, which led to a problem in the rest of the applications.

Not sure if the CVE has anything to do with your applications. It's a Dart dependency.

No, to fix the previous error, delete the cache file and restore the old version of the flutter


Ability to customise base HTML index.html

Is your feature request related to a problem? Please describe.
I want to use an HTML snippet at the top of each of the output pages. In my cases, it's just some ASCII art (not super important) but I could see people wanting to place more useful things there. Currently I cannot add that because iles hides the underlying HTML.
Describe the solution you'd like
Since iles abstracts the base HTML, I cannot do so. Would it be feasible to replace the base HTML with a custom one that uses a slot where iles can inject its output code?
Describe alternatives you've considered
I'm looking for ways to use Vue to inject some text into the HTML. But I might just abandon it and not add the snippet at all.

Hi Dhruv!
This is an enhancement that I've been wanting to add for a while now, as it would also make it easier to leverage any Vite plugins that rely on transformIndexHtml.
Regarding your use case, it's possible to inject anything you want using Vue but it will always be inside of the body.
If the ASCII is intended to be an HTML comment, you could use createCommentVNode from vue and render that in your layouts:
<script setup lang="ts">
import { createCommentVNode } from 'vue'
import asciiArtText from '~/ascii-art.txt?raw'

const AsciiArt = createCommentVNode(asciiArtText)
</script>

<template>
  <AsciiArt/>
</template>


[mgmt] edgezones with modular

https://github.com/Azure/sdk-release-request/issues/5072

/azp run prepare-pipelines

/azp run js - edgezones - mgmt - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-edgezones

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-edgezones

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-edgezones

/azp run js - edgezones - mgmt - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/arm-edgezones


serialization: add headers to config JSON example

This adds the schemaVersion, and mediaType headers to the serialization
config example.
Partially fixes #63
Signed-off-by: Sergiusz Urbaniak<EMAIL_ADDRESS>

I think we should add these fields eventually but requiring them intially will break compat with the configs that registries have today in Docker format. I am going to put it as post-v1.0.0.

or OPTIONAL? Question, if they're present, will docker just ignore them?
On Thu, May 5, 2016 at 9:48 AM, Brandon Philips<EMAIL_ADDRESS>wrote:

I think we should add these fields eventually but requiring them intially
will break compat with the configs that registries have today in Docker
format. I am going to put it as post-v1.0.0.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/opencontainers/image-spec/pull/64#issuecomment-217158775

@vbatts OPTIONAL is fine for pre-v1.0.0  if Docker will ignore the additional fields. My hunch would be yes because the JSON parsing in Go drops fields it doesn't know. But, maybe @stevvooe has a solid idea.

These fields really aren't necessary. We can add the mediatype, but the schemaVersion is mostly for backwards compatibility in the registry for manifests.
Adding these is just adopting cruft from other portions of the specification, so I am not sure this PR is necessary. Either way, they will be ignored.

Closing for now.


Add orc.b

Opcode: 0010011
Description:
Combines the bits within each byte using bitwise logical OR.
This sets the bits of each byte in the result rd to all zeros
if no bit within the respective byte of rs is set, or to all
ones if any bit within the respective byte of rs is set.
Operation:
let input = X(rs);
let output : xlenbits = 0;
foreach (i from 0 to (xlen - 8) by 8) {
output[(i + 7)..i] = if   input[(i + 7)..i] == 0
then 0b00000000
else 0b11111111;
}
X[rd] = output;
Disabled the gorci instruction because it is absent from the current
revision of the spec but is encoded the same way as orc.b.

Depends on https://github.com/MIPT-ILab/riscv-opcodes/pull/24


MM-19908 Add E2E for "Send Message" via profile popover

Summary
Add E2E for "Send Message" via profile popover
Ticket Link
Jira ticket: MM-19908

@saturninoabril this is not a must have, but wondering if it be ok to delete the new users after the tests? I think the data set that test-data generates fills out the the members quota per channel quite fast and thus sometimes fails the test creating a flaky-test situation.

This is awaiting for PR that fixes https://mattermost.atlassian.net/browse/MM-19996

Just for the sake of tracing the progress:
https://mattermost.atlassian.net/browse/MM-19996 and https://mattermost.atlassian.net/browse/MM-19982 are closed as duplicates and the ticket that's now awaiting fixes is https://mattermost.atlassian.net/browse/MM-17555.

Thanks @prapti!
@prapti @srkgupta Done update.  This should be ready for your reviews.

/update-branch

/update-branch


docs: update operators

Adds:

detectSQLi
detectXSS
pmFromDataset
ipMatchFromDataset
restpath
unconditionalMatch

We should probably generate the documentation as we do with directives.


addressable gem removed from dependencies

addressable gem looks like it hasn't been used for a long time.
In my project, this dependency is making it difficult to update.

Interesting, this was added in 134d0436, but I don't see any actual need for addressable. Thanks!


Configure the add-in for Vorlon.JS debugging point 3 not clear.

In 'Configure the add-in for Vorlon.JS debugging' point 3 I'm not sure what URL you refer to "https://localhost:1337/vorlon.js" or the URL I'm hosting my add-in on which during development would be "https://localhost:8080".

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: be179784-5839-3e8f-c131-1f4d89808b03
Version Independent ID: 69bca101-91a2-3a5e-5177-493723504354
Content: Debug Office Add-ins on iPad and Mac
Content Source: docs/testing/debug-office-add-ins-on-ipad-and-mac.md
Product: office 365
GitHub Login: @o365devx
Microsoft Alias: o365devx

Its the URL of the add-in. In your case, https://localhost:8080.


Members still have access when their status is UNPAID

Issue Summary
Members that paid previously and now are set to unpaid seems to get access to paid content.
Seems like @member.paid status is paid regardless if user is paid or unpaid same with {{content}} helper. Only works fine if user canceled subscription.
Technical details:

Ghost Version: 4.4
Node Version: 12
Browser/OS: All
Database: mysql

Hi @xoxoxo, apologies for the delay in response here.
This is expected, intentional behaviour. There are many use cases where accounts can be deliberately set to unpaid, where the expectation is that the member still has access.
The only status in which members do not have access is canceled.
However, this information was missing from our documentation, which has now been updated. See https://ghost.org/docs/themes/members/#the-member-object and https://ghost.org/docs/themes/members/#subscription-attributes.
Importantly:

@member.paid returns true for members with active subscriptions in states “active”, “trialing”, “unpaid” and “past_due”. To revoke access for members with failing payments, update your Stripe settings to automatically cancel subscriptions after all payment attempts have failed.


Informix SSL connection with JDBC fails

System information:

Operating system (distribution) and version: Windows 10 x64
DBeaver version: Version <IP_ADDRESS>101311042
Additional extensions: Informix DB

Connection specification:

Database name and version: Informix  Dynamic 12
Driver name: jdbc <IP_ADDRESS>
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
SSL Connection fails although I set SSLCONNECTION as true.
The same driver and exact same settings work with DbVisualizer v12.0.1.
Steps to reproduce, if exist:
N/A
Include any warning/errors/backtraces from the logs

com.informix.asf.IfxASFException: Attempt to connect to database server (my_db) failed.
Attempt to connect to database server (my_db) failed.
Attempt to connect to database server (my_db) failed.

Please tell, how (and where) do you set SSL connection in DBeaver?
Also logs can be helpful https://github.com/dbeaver/dbeaver/wiki/Log-files

Not allowed to add Driver properties. So I added a user property as the following:

I'm using Informix JDBC v4.10.10. I have no issue with other TCP informix connection. But SSL connection doesn't work. The error message in the log:
!ENTRY org.jkiss.dbeaver.model 4 0 2021-03-10 16:09:28.069
!MESSAGE
!SUBENTRY 1 org.jkiss.dbeaver.model 4 0 2021-03-10 16:09:28.069
!MESSAGE
!STACK 0
java.lang.NullPointerException
at com.informix.util.AdvancedProperties.getProperty(AdvancedProperties.java:94)
at com.informix.util.AdvancedUppercaseProperties.getProperty(AdvancedUppercaseProperties.java:52)
at com.informix.util.AdvancedProperties.asString(AdvancedProperties.java:89)
at com.informix.asf.Connection.openSocket(Connection.java:1561)
at com.informix.asf.Connection.connect(Connection.java:333)
at com.informix.asf.Connection.(Connection.java:327)
at com.informix.jdbc.IfxSqliConnect.(IfxSqliConnect.java:1257)
at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:169)
at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.lambda$0(JDBCDataSource.java:176)
at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.openConnection(JDBCDataSource.java:195)
at org.jkiss.dbeaver.ext.generic.model.GenericDataSource.openConnection(GenericDataSource.java:135)
at org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.connect(JDBCExecutionContext.java:101)
at org.jkiss.dbeaver.model.impl.jdbc.JDBCRemoteInstance.initializeMainContext(JDBCRemoteInstance.java:95)
at org.jkiss.dbeaver.model.impl.jdbc.JDBCRemoteInstance.(JDBCRemoteInstance.java:57)
at org.jkiss.dbeaver.model.impl.jdbc.JDBCDataSource.initializeRemoteInstance(JDBCDataSource.java:109)
at org.jkiss.dbeaver.ext.generic.model.GenericDataSource.(GenericDataSource.java:107)
at org.jkiss.dbeaver.ext.generic.model.meta.GenericMetaModel.createDataSourceImpl(GenericMetaModel.java:89)
at org.jkiss.dbeaver.ext.generic.GenericDataSourceProvider.openDataSource(GenericDataSourceProvider.java:106)
at org.jkiss.dbeaver.registry.DataSourceDescriptor.connect(DataSourceDescriptor.java:887)
at org.jkiss.dbeaver.runtime.jobs.ConnectJob.run(ConnectJob.java:70)
at org.jkiss.dbeaver.runtime.jobs.ConnectionTestJob.run(ConnectionTestJob.java:103)
at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:105)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

SSL for Informix is not supported by now.
Marked as feature request

Informix supports SSL, and work happily with Java (various applications) and Informix JDBC 4.10 and 4.50. If you are not using a CM group then the standard format connection string will work. If you are connecting to a group of CM you need to use the SQLH_TYPE syntax.
Where are these being set javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword?
Attempt to connect to database server is error 908  so you are not getting a connection, look in the informix logs and I suspect you will be seeing a 28014 error. The actual error string will point you in the right direction.

Could you please send how SSL configaration looks in another database client? It will help us to find the best way to implement the option.

From my test harness
System.setProperty("javax.net.ssl.trustStore", "someplace");
System.setProperty("javax.net.ssl.trustStorePassword", "somepassword");
/* Std SSL */
url[0] ="jdbc:informix-sqli://INFORMIXSERVER=db_ssl;DATABASE=db;USER=informix;PASSWORD=xxxx;SQLH_TYPE=FILE;SQLH_FILE=sqlhosts;SSLCONNECTION=true;";
/* SSL and CM */
url[1] ="jdbc:informix-sqli://INFORMIXSERVER=db_cm;database=db;user=informix;password=xxx;SQLH_TYPE=FILE;SQLH_FILE=sqlhosts;SSLCONNECTION=true;";
/* SSL and Group of CM*/
url[2] ="jdbc:informix-sqli://INFORMIXSERVER=g_db;database=db;user=informix;password=xxxx;SQLH_TYPE=FILE;SQLH_FILE=sqlhosts;SSLCONNECTION=true;";
/* STD java connection format will will work for all of above expect group of CM */
url[3] ="jdbc:informix-sqli://dbhost:9088/db:INFORMIXSERVER=db;user=informix;password=xxxx;";
url[4] ="jdbc:informix-sqli://dbhost:9089/db:INFORMIXSERVER=db_ssl;user=informix;password=xxxx;SSLCONNECTION=true;";
The only 'special' format that is needed is for a group of connection managers, that must use the SQLH_FILE approach.  Software such as Server Studio can request the cert from the database server, AFAIK they are java classes to enable that.  But my test harness expects the certs to already imported to the local keystore.

SSL connection works with the following walkaround:

Hello @wolverline
I do not have a test environment now to test, but, probably, you can put this setting in your URL pattern (and not in the Schema field):


Fix function name typo

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @jedi7,
Thank you for noticing this issue and entering a PR.
I will add it to review queue.

Merged in 475e3cc43e86b1752f4003491724c91f69d175c2
Thanks!