deepin.dde-control-center: init at 4.10.11

Motivation for this change
Get #59023 going for 19.09 :fireworks:
I've left the redshift functionality unpatched because it looked too impure for NixOS.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

It seems that deepin-sync-daemon is a private package that allows to synchronize configuration files to cloud networks. It exists in deepin linux, but not on arch linux.


reformat datetime on x axis with different charts

Could you please help me review it. Just reformat the datetime on chart. thanks!

ignore this branch as i make some mistake during the git push. please delete this branch and review the new_ml branch instead. thanks!


Invalid arithmetic operator

I'm getting this issue when I build and run. Build was success.

==============================================================================
conform: require("conform.health").check()

conform.nvim report ~
- Log file: /Users/2312949/.local/state/nvim/conform.log
- OK stylua ready (lua)

==============================================================================
kickstart: require("kickstart.health").check()

kickstart.nvim ~
- NOTE: Not every warning is a 'must-fix' in `:checkhealth`

    Fix only warnings for plugins and languages you intend to use.
      Mason will give warnings for languages that are not installed.
      You do not need to install, unless you want to use those languages!
- System Information: {
    machine = "arm64",
    release = "23.4.0",
    sysname = "Darwin",
    version = "Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:08 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8122"
  }
- OK Neovim version is: '0.10.0'
- OK Found executable: 'git'
- OK Found executable: 'make'
- OK Found executable: 'unzip'
- OK Found executable: 'rg'

==============================================================================
lazy: require("lazy.health").check()

lazy.nvim ~
- OK 'git' installed
- OK 'luarocks' installed
- OK no existing packages found by other package managers
- OK packer_compiled.lua not found

==============================================================================
luasnip: require("luasnip.health").check()

luasnip ~
- OK jsregexp is installed

==============================================================================
mason: require("mason.health").check()

mason.nvim ~
- OK mason.nvim version v1.10.0
- OK PATH: prepend
- OK Providers:
    mason.providers.registry-api
    mason.providers.client
- OK neovim version >= 0.7.0

mason.nvim [Registries] ~
- OK Registry `github.com/mason-org/mason-registry version: 2024-06-25-golden-hog` is installed.

mason.nvim [Core utils] ~
- OK unzip: `UnZip 6.00 of 20 April 2009, by Info-ZIP.  Maintained by C. Spieler.  Send`
- WARNING wget: not available
  - ADVICE:
    - spawn: wget failed with exit code - and signal -. wget is not executable
- OK curl: `curl 8.4.0 (x86_64-apple-darwin23.0) libcurl/8.4.0 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.58.0`
- OK gzip: `Apple gzip 430.100.5`
- OK tar: `bsdtar 3.5.3 - libarchive 3.5.3 zlib/1.2.12 liblzma/5.4.3 bz2lib/1.0.8 `
- OK bash: `GNU bash, version 3.2.57(1)-release (arm64-apple-darwin23)`
- OK sh: `Ok`

mason.nvim [Languages] ~
- WARNING Go: not available
  - ADVICE:
    - spawn: go failed with exit code - and signal -. go is not executable
- WARNING cargo: not available
  - ADVICE:
    - spawn: cargo failed with exit code - and signal -. cargo is not executable
- WARNING luarocks: not available
  - ADVICE:
    - spawn: luarocks failed with exit code - and signal -. luarocks is not executable
- WARNING Composer: not available
  - ADVICE:
    - spawn: composer failed with exit code - and signal -. composer is not executable
- WARNING PHP: not available
  - ADVICE:
    - spawn: php failed with exit code - and signal -. php is not executable
- WARNING javac: not available
  - ADVICE:
    - spawn: javac failed with exit code 1 and signal 0. The operation couldn’t be completed. Unable to locate a Java Runtime.
      Please visit http://www.java.com for information on installing Java.

- OK node: `v21.7.3`
- WARNING julia: not available
  - ADVICE:
    - spawn: julia failed with exit code - and signal -. julia is not executable
- WARNING java: not available
  - ADVICE:
    - spawn: java failed with exit code 1 and signal 0. The operation couldn’t be completed. Unable to locate a Java Runtime.
      Please visit http://www.java.com for information on installing Java.

- OK python: `Python 3.9.6`
- OK npm: `10.5.0`
- OK pip: `pip 24.1 from /Users/2312949/Library/Python/3.9/lib/python/site-packages/pip (python 3.9)`
- OK Ruby: `ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [arm64-darwin23]`
- OK python venv: `Ok`
- OK RubyGem: `3.5.3`

mason.nvim [GitHub] ~
- OK GitHub API rate limit. Used: 3. Remaining: 57. Limit: 60. Reset: Tue Jun 25 19:33:46 2024.
  Install and authenticate via gh-cli to increase rate limit.

==============================================================================
nvim: require("nvim.health").check()

Configuration ~
- OK no issues found

Runtime ~
- OK $VIMRUNTIME: /opt/homebrew/Cellar/neovim/0.10.0/share/nvim/runtime

Performance ~
- OK Build type: Release

Remote Plugins ~
- OK Up to date

terminal ~
- key_backspace (kbs) terminfo entry: `key_backspace=^H`
- key_dc (kdch1) terminfo entry: `key_dc=\E[3~`
- $TERM_PROGRAM="tmux"
- $COLORTERM="truecolor"

tmux ~
- OK escape-time: 10
- OK focus-events: on
- $TERM: screen-256color

External Tools ~
- OK ripgrep 14.1.0 (/opt/homebrew/bin/rg)

==============================================================================
nvim-treesitter: require("nvim-treesitter.health").check()

Installation ~
- OK `tree-sitter` found 0.22.6 (parser generator, only needed for :TSInstallFromGrammar)
- OK `node` found v21.7.3 (only needed for :TSInstallFromGrammar)
- OK `git` executable found.
- OK `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
  Version: Apple clang version 15.0.0 (clang-15<IP_ADDRESS>)
- OK Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

OS Info:
{
  machine = "arm64",
  release = "23.4.0",
  sysname = "Darwin",
  version = "Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:08 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8122"
} ~

Parser/Features         H L F I J
  - bash                ✓ ✓ ✓ . ✓
  - c                   ✓ ✓ ✓ ✓ ✓
  - diff                ✓ . . . .
  - git_config          ✓ . ✓ . ✓
  - html                ✓ ✓ ✓ ✓ ✓
  - json                ✓ ✓ ✓ ✓ .
  - lua                 ✓ ✓ ✓ ✓ ✓
  - luadoc              ✓ . . . .
  - markdown            ✓ . ✓ ✓ ✓
  - markdown_inline     ✓ . . . ✓
  - objc                ✓ ✓ ✓ ✓ ✓
  - python              ✓ ✓ ✓ ✓ ✓
  - query               ✓ ✓ ✓ ✓ ✓
  - swift               ✓ ✓ . ✓ ✓
  - vim                 ✓ ✓ ✓ . ✓
  - vimdoc              ✓ . . . ✓

  Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
         +) multiple parsers found, only one will be used
         x) errors found in the query, try to run :TSUpdate {lang} ~

==============================================================================
provider.clipboard: require("provider.clipboard.health").check()

Clipboard (optional) ~
- OK Clipboard tool found: pbcopy

==============================================================================
provider.node: require("provider.node.health").check()

Node.js provider (optional) ~
- Node.js: v21.7.3

- WARNING Missing "neovim" npm (or yarn, pnpm) package.
  - ADVICE:
    - Run in shell: npm install -g neovim
    - Run in shell (if you use yarn): yarn global add neovim
    - Run in shell (if you use pnpm): pnpm install -g neovim
    - You may disable this provider (and warning) by adding `let g:loaded_node_provider = 0` to your init.vim

==============================================================================
provider.perl: require("provider.perl.health").check()

Perl provider (optional) ~
- WARNING "Neovim::Ext" cpan module is not installed
  - ADVICE:
    - See :help |provider-perl| for more information.
    - You may disable this provider (and warning) by adding `let g:loaded_perl_provider = 0` to your init.vim
- WARNING No usable perl executable found

==============================================================================
provider.python: require("provider.python.health").check()

Python 3 provider (optional) ~
- WARNING No Python executable found that can `import neovim`. Using the first available executable for diagnostics.
- WARNING Could not load Python :
  /usr/bin/python3 does not have the "neovim" module.
  /opt/homebrew/bin/python3.12 does not have the "neovim" module.
  python3.11 not found in search path or not executable.
  python3.10 not found in search path or not executable.
  python3.9 not found in search path or not executable.
  python3.8 not found in search path or not executable.
  python3.7 not found in search path or not executable.
  python not found in search path or not executable.
  - ADVICE:
    - See :help |provider-python| for more information.
    - You may disable this provider (and warning) by adding `let g:loaded_python3_provider = 0` to your init.vim
- Executable: Not found

Python virtualenv ~
- OK no $VIRTUAL_ENV

==============================================================================
provider.ruby: require("provider.ruby.health").check()

Ruby provider (optional) ~
- Ruby: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [arm64-darwin23]
- WARNING `neovim-ruby-host` not found.
  - ADVICE:
    - Run `gem install neovim` to ensure the neovim RubyGem is installed.
    - Run `gem environment` to ensure the gem bin directory is in $PATH.
    - If you are using rvm/rbenv/chruby, try "rehashing".
    - See :help |g:ruby_host_prog| for non-standard gem installations.
    - You may disable this provider (and warning) by adding `let g:loaded_ruby_provider = 0` to your init.vim

==============================================================================
telescope: require("telescope.health").check()

Checking for required plugins ~
- OK plenary installed.
- OK nvim-treesitter installed.

Checking external dependencies ~
- OK rg: found ripgrep 14.1.0
- WARNING fd: not found. Install [sharkdp/fd](https://github.com/sharkdp/fd) for extended capabilities

===== Installed extensions ===== ~

Telescope Extension: `fzf` ~
- OK lib working as expected
- OK file_sorter correctly configured
- OK generic_sorter correctly configured

Telescope Extension: `ui-select` ~
- No healthcheck provided

==============================================================================
vim.lsp: require("vim.lsp.health").check()

- LSP log level : WARN
- Log path: /Users/2312949/.local/state/nvim/lsp.log
- Log size: 5 KB

vim.lsp: Active Clients ~
- sourcekit (id=1, root_dir=~/Documents/iOS, attached_to=[1])

vim.lsp: File watcher ~
- File watch backend: libuv-watch

==============================================================================
vim.treesitter: require("vim.treesitter.health").check()

- Nvim runtime ABI version: 14
- OK Parser: bash                 ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/bash.so
- OK Parser: c                    ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/c.so
- OK Parser: diff                 ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/diff.so
- OK Parser: git_config           ABI: 13, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/git_config.so
- OK Parser: html                 ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/html.so
- OK Parser: json                 ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/json.so
- OK Parser: lua                  ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/lua.so
- OK Parser: luadoc               ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/luadoc.so
- OK Parser: markdown             ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/markdown.so
- OK Parser: objc                 ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/objc.so
- OK Parser: swift                ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/swift.so
- OK Parser: vim                  ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/vim.so
- OK Parser: vimdoc               ABI: 14, path: /Users/2312949/.local/share/nvim/lazy/nvim-treesitter/parser/vimdoc.so
- OK Parser: bash                 ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/bash.so
- OK Parser: c                    ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/c.so
- OK Parser: lua                  ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/lua.so
- OK Parser: markdown             ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/markdown.so
- OK Parser: markdown_inline      ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/markdown_inline.so
- OK Parser: python               ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/python.so
- OK Parser: query                ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/query.so
- OK Parser: vim                  ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/vim.so
- OK Parser: vimdoc               ABI: 14, path: /opt/homebrew/Cellar/neovim/0.10.0/lib/nvim/parser/vimdoc.so

==============================================================================
which-key: require("which-key.health").check()

WhichKey: checking conflicting keymaps ~
- WARNING conflicting keymap exists for mode **"n"**, lhs: **" d"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"o"**, lhs: **"a"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"o"**, lhs: **"i"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"gc"**
- rhs: `<Plug>(comment_toggle_linewise)`
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"gb"**
- rhs: `<Plug>(comment_toggle_blockwise)`
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sh"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sr"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sF"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sd"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"sf"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"v"**, lhs: **"a"**
- rhs: ` `
- WARNING conflicting keymap exists for mode **"v"**, lhs: **"i"**
- rhs: ` `

==============================================================================
xcodebuild: require("xcodebuild.health").check()

Checking xcodebuild.nvim ~
- OK xcodebuild.nvim: commit #2c11361

Checking OS ~
- OK macOS 14+: release 23.4.0

Checking plugins ~
- OK telescope.nvim installed.
- OK nui.nvim installed.
- OK nvim-tree installed.
- WARNING neo-tree not installed. (Optional to visually manage project files)
- OK oil.nvim installed.
- WARNING nvim-dap not installed. (Optional to debug applications)
- WARNING nvim-dap-ui not installed. (Optional to present debugger UI)
- OK nvim-treesitter installed.
- OK nvim-treesitter: Swift parser installed.

Checking required dependencies ~
- OK xcodebuild: version 15.3
- OK xcodebuild: installed
- OK xcrun: installed
- OK xcode-build-server: installed

Checking optional dependencies ~
- WARNING pymobiledevice3: not installed. Required for debugging on physical devices and/or running apps on devices below iOS 17. (https://github.com/doronz88/pymobiledevice3)
- OK xcodeproj: installed
- OK xcbeautify: installed
- OK ruby: version 3.3.0

Checking debugger ~
- ERROR codelldb: cannot be checked because dap is not installed.

Checking buildServer.json ~
- OK buildServer.json: found

Checking .nvim/xcodebuild/settings.json ~
- OK .nvim/xcodebuild: found
- OK .nvim/xcodebuild/settings.json: found

This is build logs window, it looks like error in your code :)

Can you see in your logs what's the full error line. You can open .nvim/xcodebuild/original_logs.log and search for invalid arithmetic operator

Can you see in your logs what's the full error line. You can open .nvim/xcodebuild/original_logs.log and search for invalid arithmetic operator

It only shows build succeeded as the last log. But in report.log it shows
{"testsCount": 0, "failedTestsCount": 0, "tests": [], "buildWarnings": [], "buildErrors": [{"source": "/Users/2312949/Library/Developer/Xcode/DerivedData/Project-eudrdyzgxvdztubwyrhmnzdskwmr/Build/Intermediates.noindex/Project.build/Debug-iphonesimulator/Project.build/Script-6CF80361214057EC00523BE5.sh: line 8: [[: Debug}", "message": ["invalid arithmetic operator (error token is \"}\")"]}], "testErrors": []}

Can you see in your logs what's the full error line. You can open .nvim/xcodebuild/original_logs.log and search for invalid arithmetic operator

Found it sorry
Running upload-symbols in Build Phase mode
Validating build environment for Crashlytics...
Validation succeeded. Symbol uploading will proceed in the background.
/Users/2312949/Library/Developer/Xcode/DerivedData/Project-eudrdyzgxvdztubwyrhmnzdskwmr/Build/Intermediates.noindex/Project.build/Debug-iphonesimulator/Project.build/Script-6CF80361214057EC00523BE5.sh: line 8: [[: Debug}: syntax error: invalid arithmetic operator (error token is "}")

It looks like you've got some bug in your Build Phases script

Yeah, rewrote eh. So sorry and thank you!


Added Another example with react

Added Another example with react

@royderks Please review it !!

@royderks Please Review my PR.


factor: query Prometheus more frequently to update metrics timely

What problem does this PR solve?

Issue Number: close #562
Problem Summary:
The refresh interval of Prometheus is 15s and the interval for TiProxy reading Prometheus is 15s. Thus, the metric delay is at most 30s.
If TiProxy reads Prometheus every 5s, the max delay is 20s.
What is changed and how it works:

Update the reading metrics interval to 5s
Do not update the backend snapshot if the metric of this backend is not updated, even if the whole query result is updated.

Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Notable changes

[ ] Has configuration change
[ ] Has HTTP API interfaces change
[ ] Has tiproxyctl change
[ ] Other user behavior changes

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

/retest


Abort on Mac OS X 11.4 Big Sur

When parsing https://github.com/sifive/freedom-e-sdk/blob/origin/dev/zongl/unmatched/bsp/sifive-hifive-unmatched/design.svd (attached) with [svd2rust](https://crates.io/crates/svd2rust), on OS X 11.4 (Big Sur) I get the following (note the abort/lack of backtrace):
sergibli@HephaestusMobi:~/Development/svd2rust
▶ RUST_BACKTRACE=1 svd2rust --target riscv -i ../bg/ada/sifive_hifive_unmatched_hal/sifive_hifive_unmatched.svd -o ../bg/ada/sifive_hifive_unmatched_hal/output/
fatal runtime error: failed to initiate panic, error 5
Abort trap: 6
sergibli@HephaestusMobi:~/Development/svd2rust
▶ svd2rust --version
svd2rust 0.19.0 ( )
sergibli@HephaestusMobi:~/Development/svd2rust
▶ rustc --version
rustc 1.53.0 (53cb7b09b 2021-06-17)
Tried single-stepping in the debugger; crash appears to be in proc-macro-2-1.0.27::detection::initialize(), but the debugger was also acting flaky at this point.
▶ cargo tree -i proc-macro2
proc-macro2 v1.0.27
...
├── svd2rust v0.19.0 (/Users/brad/Development/svd2rust)
...

Switching to a Linux VM, using the same file and toolchain version, everything worked fine.
[form](https://crates.io/crates/form) also aborted on OS X in the same way while parsing a lib.rs file.  form also has a dependency on proc-macro2 (v0.4).
Can anyone confirm? Any insights as to what the issue might be?

I was curious why I wasn't seeing this reported by other Mac users as well.  I spent some time to set up another Mac environment and the abort did not replicate.  Closing this issue, as it appears to be something in my own dev environment.


Posting to LinkedIn company pages

It is unclear if this feature supports posting to LinkedIn company pages. LinkedIn does not have dedicated user accounts for their company administration and when you use a personal LinkedIn account (designated as a company admin), the posts always end up on their personal activity feed.
Would be great to clarify this in the article by either stating that you can only post to your personal LinkedIn or provide instructions how to do it for LinkedIn Companies. Similar to what you have there for Facebook.
Thanks!
Tomas

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

ID: 4f9cad1e-9d1d-0332-4b09-ed26354dd0c0
Version Independent ID: 2cbb9e75-d6f9-f0c9-cbb2-84b749adf44e
Content: Configure and authenticate social media accounts  (Dynamics 365 Marketing)
Content Source: ce/marketing/mkt-settings-social-media.md
Service: dynamics-365-marketing
GitHub Login: @alfergus
Microsoft Alias: alfergus

Hi Tomas. The new early access version of the social media post designer allows you to post to a LinkedIn company page. To do this, select LinkedIn as the social channel and Company from the Post as dropdown.

You will, of course, need to ensure that the LinkedIn account you're using is authorized to post on behalf of the company page.

@alfergus Alex, I really appreciate you finding time to respond to me. This addresses my question. Thank you! Tomas


Decompress public key for stark

Hi there,
Following from issue, how can I use starknet to "decompress" the public key as Jonathan suggested?
Thanks

starknet-crypto does contain the logic of decompressing public keys as it needs to do that for verifying signatures. See this line.
However as of today, this functionality is an implementation detail and not exposed as part of the public API. If you need to use it, the best way to do that today would be to fork this repository and expose the function yourself.

Optimistically closing this. Feel free to re-open if you have further questions on the topic.

Hi @rhobro I noticed you just forked our library, and just want to remind you that we just discovered a critical bug which causes the decimal representation of FieldElement to be incorrect. This bug is currently tracked as https://github.com/xJonathanLEI/starknet-rs/issues/74.
So if you print out the coordinates you get, you'll be getting incorrect numbers. You might want to incorporate the fix once it's implemented (very soon).

Sure thing :)

The commit fixing the issue is on master now @rhobro

That was rapid. Thanks man.

I forked it and exposed just the logic to get the y coordinate which I found in EcPoint::from_x. It is amazing that it was the same logic I found on the starkware website.
Out of interest @xJonathanLEI, would it be possible to be able to do arithmetic with references to FieldElements rather than having to clone them to pass into a function?

Yeah I'd expect the same logic to be used everywhere. I guess that means we have a correct implementation :)
As for using references for arithmetic, yes we will be implementing ops that take references alongside the existing ones. However, I'd say you shouldn't worry about this for performance reasons (I'm presuming you're trying to do it for performance reasons; please ignore me if that's not the case :)), as this will be taken care of by the Rust optimizer.

I was trying to do it for performance reasons 😳. How can the rust optimiser solve it?

Obviously you'd need to benchmark for your case yourself, but generally speaking, if ownership is taken without being used, the compiler might turn it into a reference instead, depending on a lot of factors including the size of the struct in question.

Ok. Thanks for the info.


Unclear on parallel execution

Hi,
Thanks for the hard work on this, it shows a lot of promise.
I'm trying to set up a distributed workflow which emulates gnu parallel. In order to do this, I'd like to have a single command trigger processes on multiple nodes, each routing their results back to a single node.
Right now there seems to be no way to describe a single node as being executable by a set of devices simultaneously. Instead, I need to enumerate each device using a new node annotated with the deviceID as a constraint. I was under the impression that you could exclude the deviceID and it would send a message to all devices, but the message (say, a timestamp) doesn't arrive at every other node in spite of either 1N or NN link between them. I suspect this is because I am thinking in parallel and not as a matter of 1 message to 1 node, and that there is some intermediate node I should be using.
To reproduce, take three node-red instances, NR1, NR2 and NR3. Create a single timestamp node, an exec node (with ls as the command, excluding payload), and a debug node. Assign the timestamp node to NR1 (via node requirements) and set the exec node to a 1 1 requirement for mem/cores. Then set the debug node to N1.
Am I misunderstanding how to set up parallel flows?

Hi there,
Thanks for your interest. Your observation is right. It is an interesting and known limitation on the constraint definition where you cannot have a excluding constraint. I suppose adding something like "run this node on device other than X" will be something in my todo list.
The main reason behind this is when a node doesn't have a constraint, it will be deployed and available on every participating NR instances. Consequently, when the inject node realizes that there is an exec node (it's peer) that can run in the same device as its own, it won't send a message out to other devices.
At the current situation, there is a hack to make this happen I guess. This is by using the location requirement, essentially we want all the nodes to have a constraint. So you pretending to have 3 NR instances in 3 different locations, let say the inject node is constrained to run in Vancouver, the exec to run in Seattle and the debug to run in SanFran (could be the same as Vancouver). You can do this with location-based node requirement.
Then you configure your NR instances so that one located in Vancouver, the ones that needs to run the exec node to be located in Seattle, and the one who run the debug node to be in SanFran. You can do this by configuring the Dnr Daemon node and checking the Location Fixed checkbox.
You could try this and let me know.


Add event rule pattern detail and control finding generator variable

what
Add two variables for better customization of the module.
why
cloudwatch_event_rule_pattern_detail - allow a more specific detail pattern in order to filter events sent through the SNS topic.  Currently using to only match events which have failed and are 'HIGH' and 'CRITICAL'.
control_finding_generator - optionality that exists on aws_securityhub_account. Ensures that users of this module don't sacrifice functionality.

Any chance we can get this prioritized / merged?


RYA-110 - Add Uninstall command to Rya Console.

hey fix the merge conflict and i will merge.

This PR is now also clean

@isper3at I just noticed your list at RYA-208.  I'll comment on that ticket as I merge them.  Thanks again.

Awesome, thanks!


Unable to set static proxy in WSL2

Environment
Windows build number: Microsoft Windows [Version 10.0.20185.1000]
Your Distribution version: Ubuntu 20.04.1 LTS
Whether the issue is on WSL 2 and/or WSL 1: WSL

Steps to reproduce

Try to connect the windows system with any network. In which internet is served throught static proxy.
Then try to set a static proxy by

https://github.com/microsoft/WSL/issues/1570#issuecomment-271531911
https://askubuntu.com/questions/1121521/how-to-configure-http-proxy-with-authentication-on-ubuntu-wsl-on-windows-10
Acquire::http::Proxy "http://proxy.foo.com:8080"; in /etc/apt/apt.conf Website
Some other method like placing a function in .bashrc

WSL logs: Do you want log.
Expected behavior
Proxy should work fine in WSL2 as in Windows.

Actual behavior

Proxy doesn't work.
Err:1 http://security.ubuntu.com/ubuntu focal-security InRelease
  Could not connect to <IP_ADDRESS>:2980 (<IP_ADDRESS>). - connect (111: Connection refused)
Err:2 http://archive.ubuntu.com/ubuntu focal InRelease
  Could not connect to <IP_ADDRESS>:2980 (<IP_ADDRESS>). - connect (111: Connection refused)
Err:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease
  Unable to connect to <IP_ADDRESS>:2980:
Err:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease
  Unable to connect to <IP_ADDRESS>:2980:
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal/InRelease  Could not connect to <IP_ADDRESS>:2980 (<IP_ADDRESS>). - connect (111: Connection refused)
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-updates/InRelease  Unable to connect to <IP_ADDRESS>:2980:
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/focal-backports/InRelease  Unable to connect to <IP_ADDRESS>:2980:
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/focal-security/InRelease  Could not connect to <IP_ADDRESS>:2980 (<IP_ADDRESS>). - connect (111: Connection refused)
W: Some index files failed to download. They have been ignored, or old ones used instead.

Pingging a DNS should work!
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
11 packets transmitted, 0 received, 100% packet loss, time 10396ms

Ping and an http proxy are not the same. If you can't ping <IP_ADDRESS>, that is unrelated to the "steps to reproduce" cited.
What does nslookup proxy.foo.com return. If it doesn't resolve, then you can't do Acquire::http::Proxy "http://proxy.foo.com:8080", because it won't be able to get the IP of your http proxy server.

i just used a valid static proxy. which i tested in different device and the proxy was working.

Ping and an http proxy are not the same. If you can't ping <IP_ADDRESS>, that is unrelated to the "steps to reproduce" cited.
What does nslookup proxy.foo.com return. If it doesn't resolve, then you can't do Acquire::http::Proxy "http://proxy.foo.com:8080", because it won't be able to get the IP of your http proxy server.

This is one of the approach. i tried to solve this error an every time i tried ping and got the same result.

An every time i tried ping and got the same result.

An http proxy will not get you ping (a ICMP request is not a HTTP request). Moving to discussion.


AJAX extra params

Changed a few lines to support sending extra params to the service

Will take a look, thanks!

Already merged this functionality from another pull request. Thanks though!


C sshnpd binary (from c0.1.8 release) won't run on Ubuntu 20.04 due to missing glibc dependency

Describe the bug
Running ./sshnpd returns:
./sshnpd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./sshnpd)
./sshnpd: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./sshnpd)

Steps to reproduce

First I downloaded the sshnp-linux-x64.tgz tarball from the c0.1.8 release
Then I extracted the binary: tar -xvf sshnp-linux-x64.tgz sshnpd
And then I run the binary ./sshnpd

Expected behavior
Daemon shows help
Additional context
uname -a
Linux DB4 <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.6 LTS
Release:        20.04
Codename:       focal

ldd --version
ldd (Ubuntu GLIBC 2.31-0ubuntu9.16) 2.31
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

@cpswan This should hopefully solve this problem:
https://github.com/atsign-foundation/noports/pull/1221
If not, then I will investigate further.

@XavierChanth I've tried the binaries for your manual test build and the c0.1.9-rc1 release and they both still fail to run for the same reason as before

This may deserve its own ticket, but I just had a go at building locally, and that's failing:
[ 50%] Linking C executable sshnpd
/usr/bin/ld: CMakeFiles/sshnpd.dir/src/main.c.o: in function `main':
main.c:(.text+0x8f2): undefined reference to `pthread_create'
/usr/bin/ld: main.c:(.text+0xcf2): undefined reference to `pthread_join'
/usr/bin/ld: _deps/srv-lib-build/libsrv-lib.a(srv.c.o): in function `run_srv_daemon_side_multi':
srv.c:(.text+0x8ee): undefined reference to `pthread_create'
/usr/bin/ld: srv.c:(.text+0x960): undefined reference to `pthread_detach'
/usr/bin/ld: _deps/srv-lib-build/libsrv-lib.a(srv.c.o): in function `socket_to_socket':
srv.c:(.text+0xdf9): undefined reference to `pthread_create'
/usr/bin/ld: srv.c:(.text+0xe63): undefined reference to `pthread_create'
/usr/bin/ld: srv.c:(.text+0xf3b): undefined reference to `pthread_join'
/usr/bin/ld: srv.c:(.text+0xfb1): undefined reference to `pthread_cancel'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/sshnpd.dir/build.make:113: sshnpd] Error 1
make[1]: *** [CMakeFiles/Makefile2:751: CMakeFiles/sshnpd.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

My CMake line was:
cmake -B build -S . -DBUILD_SHARED_LIBS=off -DCMAKE_C_COMPILER=gcc -DCMAKE_C_FLAGS="-Wno-calloc-transposed-args -Wno-error -pthread -lrt"

https://github.com/wheybags/glibc_version_header may help here
https://stackoverflow.com/a/76085075 also suggests using the zig compiler, which would tie into #1208

With Zig ruled out as an approach I'll take a look at the glibc_version_header way of dealing with things.

Alpine Linux: Effortless static linking and portable applications for C/C++ provides a good overview of the issue we're facing with glibc.
I've already spent some time getting a linux-x64/arm64 build working inside of Debian 10 (glibc 2.28.0) in Docker. Unfortunately doing the same for armv7 is challenging as both CMake and Clang aren't available.
Will also take a look at what we can do with musl (building inside Alpine).


[WIP] EVP: Enforce that EVP_PKEY_set_alias_type() only works with legacy keys

This also deprecates the function, as it is not necessary any more,
and should fall out of use.

This is the opposite of #12675

The Travis issue will go away as soon as #12536 is merged

Assuming this should have the "approval: done" label, so adding it now.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

This pull request is ready to merge

I needed to make a small change in test/evp_extra_test.c.  Do note that we already test EVP_PKEY_set_alias_type() quite thoroughly in test/ecdsatest.c.

Travis failure is just a timeout..

This pull request is ready to merge

Merged
14711fffbf2726f94d6a05d8f9cbae7fe7a4bc09 EVP: Enforce that EVP_PKEY_set_alias_type() only works with legacy keys
8a288609b12488b5e2dbca28ea54c3dd2c0de15b TEST: Remove use of EVP_PKEY_set_alias_type() in test/evp_extra_test.c


Cannot do "case"

With this sample file
module AtomTst where

open import Data.Product

f : {A B : Set} → (A × B) → A
f x =  ?

when the cursor is in the hole and when I type ctrl-c ctrl-c, I got this error message:
when checking that the expression ? has type .A```

In some other cases I got error message about co-pattern splitting. It seems that Agda thought I issued a different command.

That's because Agda has no idea which pattern variables to case, and you'll have to provide one by putting it in the hole.
But I've never done any co-pattern splitting before, maybe that's another issue, could you provide a sample file about this?

I see. I've always entered the variable to case after Ctrl-c-c, hence the confusion. Casing works if I specify the variable first.
Thanks! I think we can consider this issue closed.

In Emacs, if the hole is left empty when casing, agda-mode would pop a input box and ask you to fill it.
I'll close this issue after adding it to Atom.

v0.3.2


Trouble compiling examples

I am having trouble compiling the examples, I get an error from the TinyXMLADMData.h file. (This is after I have make installed, when I am making the examples).
/tmp/ccip6zmd.o: In function bbcat::TinyXMLADMData::__Creator(void*)': /usr/local/include/bbcat-audioobjects-0.1/bbcat-audioobjects/TinyXMLADMData.h:63: undefined reference to bbcat::TinyXMLADMData::TinyXMLADMData()'
Apparently the TinyXMLADMData::__Creator function cannot see its own constructor? I do not know enough c++ but am attempting to diagnose or workaround this. I can see the class + constructor in the library file with nm.

ebenn@ebenn-mac$ nm /usr/local/lib/libbbcat-audioobjects-0.1.so -C | grep "bbcat::TinyXMLADMData::TinyXMLADMData"
000000000003be50 T bbcat::TinyXMLADMData::TinyXMLADMData()
000000000003be50 T bbcat::TinyXMLADMData::TinyXMLADMData()

Here is the examples make output:
make
g++ pkg-config --cflags bbcat-base-0.1 pkg-config --cflags bbcat-dsp-0.1 pkg-config --cflags bbcat-control-0.1 pkg-config --cflags bbcat-audioobjects-0.1 -Wall -Werror -Wextra -msse2 -O2 -g pkg-config --libs bbcat-base-0.1 pkg-config --libs bbcat-dsp-0.1 pkg-config --libs bbcat-control-0.1 pkg-config --libs bbcat-audioobjects-0.1  read-adm-bwf.cpp -o read-adm-bwf
/tmp/ccaKzq3s.o: In function bbcat::TinyXMLADMData::__Creator(void*)': /usr/local/include/bbcat-audioobjects-0.1/bbcat-audioobjects/TinyXMLADMData.h:63: undefined reference to bbcat::TinyXMLADMData::TinyXMLADMData()'
/tmp/ccaKzq3s.o: In function bbcat::TinyXMLADMData::Register()': /usr/local/include/bbcat-audioobjects-0.1/bbcat-audioobjects/TinyXMLADMData.h:24: undefined reference to bbcat::ADMData::RegisterProvider(bbcat::ADMData* ()(void), void*)'
/tmp/ccaKzq3s.o: In function main': /home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:23: undefined reference to bbcat::ADMRIFFFile::ADMRIFFFile()'
/home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:25: undefined reference to bbcat::ADMRIFFFile::Open(char const*)' /home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:50: undefined reference to bbcat::ADMData::GetObjects(std::string const&, std::vector<bbcat::ADMObject const*, std::allocator<bbcat::ADMObject const*> >&) const'
/tmp/ccaKzq3s.o: In function bbcat::ADMObject::ToString() const': /usr/local/include/bbcat-audioobjects-0.1/bbcat-audioobjects/ADMObjects.h:209: undefined reference to bbcat::Printf(std::string&, char const*, ...)'
/tmp/ccaKzq3s.o: In function main': /home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:74: undefined reference to bbcat::ADMData::GetObjects(std::string const&, std::vector<bbcat::ADMObject const*, std::allocator<bbcat::ADMObject const*> >&) const'
/home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:81: undefined reference to typeinfo for bbcat::ADMAudioObject' /home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:81: undefined reference to typeinfo for bbcat::ADMObject'
/home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:84: undefined reference to bbcat::ADMAudioFileSamples::ADMAudioFileSamples(bbcat::SoundFileSamples const*, bbcat::ADMAudioObject const*)' /tmp/ccaKzq3s.o: In function bbcat::ADMObject::ToString() const':
/usr/local/include/bbcat-audioobjects-0.1/bbcat-audioobjects/ADMObjects.h:209: undefined reference to bbcat::Printf(std::string&, char const*, ...)' /tmp/ccaKzq3s.o: In function main':
/home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:97: undefined reference to bbcat::ADMAudioFileSamples::~ADMAudioFileSamples()' /home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:118: undefined reference to bbcat::ADMRIFFFile::~ADMRIFFFile()'
/home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:118: undefined reference to bbcat::ADMRIFFFile::~ADMRIFFFile()' /home/ebenn/bbcat/bbcat-audioobjects/examples/read-adm-bwf.cpp:97: undefined reference to bbcat::ADMAudioFileSamples::~ADMAudioFileSamples()'
collect2: error: ld returned 1 exit status
make: *** [read-adm-bwf] Error 1

I was able to resolve this partially by manually separating the compile and link steps;
g++ -D_FILE_OFFSET_BITS=64 -D__LINUX__ -DENABLE_GPL=1 -I/usr/local/include/bbcat-base-0.1 -I/usr/local/include/bbcat-dsp-0.1 -I/usr/local/include/bbcat-control-0.1 -I/usr/local/include/bbcat-audioobjects-0.1 -Wall -Werror -Wextra -msse2 -O2 -g -o read-adm-bwf.o -c read-adm-bwf.cpp
g++  -o read-adm-bwf read-adm-bwf.o -L/usr/local/lib -lbbcat-base-0.1 -L/usr/local/lib -lbbcat-dsp-0.1 -L/usr/local/lib -lbbcat-control-0.1 -L/usr/local/lib -lbbcat-audioobjects-0.1
And then manually pointing the binary to the libraries:
env LD_LIBRARY_PATH=/usr/local/lib ./read-adm-bwf

Running an extra
sudo ldconfig
After the library make install has resolved the final problem.

Hi Evan,
Thanks for persevering with the issue, did you try running ldconfig after the library install and then running the original examples makefile?  I'm just wondering whether the ldconfig is a complete cure for the problem and the splitting of the makefile into two stages is not necessary?
I haven't experienced this build issue at all whilst using the libraries so would you mind describing your system, please? I am guessing it is a Mac but what version OS and Xcode?  Or are you using non-LLVM gcc?
Nonetheless, I'll have a look at your pull request.
Thanks,
Richard.


Add some sacred icon's for Headlong.

Make it a bit less ambiguous in regards to install order.
http://puu.sh/p9LMG/a4a657263d.png

Added :) http://i.imgur.com/RsFxjGV.png


3592: remove phase banner and add feedback link

The phase banner needs to be removed for go-live, but we want to keep the feedback link. This PR removes the banner and adds in a GOV.UK-style link at the bottom of the content. Rather than pop open a short form in the GOV.UK style this just links through to the existing feedback form on old frontend.

Looks good to me 👍


Actually point to the correct type declarations

This reverts the change I made here (https://github.com/wlamason/opendota.js/pull/20) and remedies the issue I was originally trying to resolve. I apologize for the mixup, and understand if you just want to revert and move on with your life!
Thanks!!

@kroy No worries at all! I just merged and published 2.0.4, which should contain these changes. Cheers! 🥂
NPM:
https://www.npmjs.com/package/opendota.js
Github release:
https://github.com/wlamason/opendota.js/releases/tag/v2.0.4

2nd time's the charm! Thanks for understanding and responding so quickly @wlamason . Cheers!


Make ECMAScript2015 the default in Scala.js 1.x

There are real advantages to using ECMAScript 2015 now:

Throwables, by virtue of properly extending JavaScript's Error, have an [[ErrorData]] internal slot, and therefore receive proper debugging info in JS engines, allowing better display of stack traces and error messages in interactive debuggers.
Static fields and methods in JS classes are properly inherited. See https://github.com/scala-js/scala-js/issues/2771.
Overall, Scala.js is specified in terms of ES2015. The ES 5.1 output that we emit is already, conceptually, a desugaring of the ES2015 meaning of Scala.js programs.

For those reasons, I think we should make it the default in Scala.js 1.x.
Any objection?

Will this work in my browser? :P

Probably, unless you're using something very old: https://caniuse.com/#feat=es6 :P

Good. Then I'm happy :P


Typescript Types

Hello!
Im currently evaluating hyper-express vs nanoexpress.  Nanoexpress has some typescript type issues (its written in javascript and provides a d.ts with a bunch of errors).  With HyperExpress I cant seem to import any types.  For example, trying to write a middleware:
const middleware = (req: ?, res: ?, next: ?) => {
   return next()
}

Are these types exported anywhere?
Thank you

HyperExpress is also written in Javascript and implements its types through the d.ts files contained in /types folder.
I would assume you should be able to import types just like you would import components in TypeScript/Module system of Node.
For the specific use case above, you should look at
https://github.com/kartikk221/hyper-express/blob/master/types/components/router/Router.d.ts
to find any specific exported types you may need for your purpose.

Thanks for the reply @kartikk221!
I think the problem is that Request, Response etc is not exported in the types.  Seems like only Server and Router are exported.
I think adding changing index.d.ts to:
export * as compressors from 'uWebSockets.js';
export Server from './components/Server';
export Router from './components/router/Router';
export Request from './components/http/Request';
export Response from './components/http/Response';

would be a good start.
Also, if you can export these two types https://github.com/kartikk221/hyper-express/blob/master/types/components/router/Router.d.ts#L7-L8 I should be able to import them.
Would you like a pull request?

Oh I see, yeah go ahead and make a pull request and I'll merge it.
Currently working on the 6.0.0 update which would include API improvements, type improvements and support for Node 18 / uWebsockets.js 20.8.0, so will get this published right along with that.

Sounds good!  I will do that now.  Any idea when 6.0.0 is going to be released?  Anything I can do to help?

It's almost done, just writing/updating tests, types and docs for the few changes that have been made.
Should be released later today hence the timing will line up to have your pull request included.
My only request would be to export essentially any and all types you think may be useful/referenced by users but I think the Server, Router, Request and Response exports you have above are already good ones to start with.

Can do!

#65 opened.

Hows the release looking, think its going to get published tonight or should I just link my fork for now?

Hey, I'm essentially done with the update and just need to do a quick skim tomorrow morning before I publish the update. 6.0.0 will 100% be released tomorrow, so If your current use case is more tim sensitive, feel free to fork/link your current modifications.

Will do, I will probably have a few more pushes to my PR as I run through and test it all out.  Will talk tomorrow!

Do you mind if I add a setter for req.body?  I need to write my own body parser middleware.  Or would you prefer to expose req._body in the typedefs?

Do a setter for Request.body which writes the value to the underlying _body property.

Will do.

Let me know when this gets published.  So far so good on my side.

Let me know when this gets published. So far so good on my side.

6.0.0 should be published. Let me know If you find any problems with documentation or types. I had to modify the JSDoc types a little bit to make the intellisense work properly for Non-Typescript projects.

Awesome.  Installing now and will let you know if I run into anything.


[Request] Automatic category by player race

I'd like to have a category that automatically applies to everyone of a certain player race.

+1


Adding command initial

    if (args.length < 1) {

Why not use args.length === 0?

Looks good to me


Evaluate the Program Training determination

Both the checkmarks on the profile page and on the Event View tab. There should not be duplicate items, and fulfillment by attendance should work correctly.

 Evaluate the Program Training determination


Tool can break the Trigger with one animation.

I have original avatar package and tested it works good.
The avatar uses Boolean paramater for Trigger (in the menu)
The Animator looks [ IDLE ] <- -> [ ANIMATION STATE]. It uses only 1 animation, and the animation has 2 frames for 0 and 1, so it toggle to 1 and when toggle is reset, animation is also reset and goes to 0. Each frame has own settings for avatar.
The tool changed the FX in the way it can break this type of animation, because there is no more "reset" send to animation. That means the animation will never go back to Frame 0 and stays always in Frame 1.
I have another avatar with FX, using 2 animations for ON and OFF. So in the animator there are 2 states. This toggle structure is different from one-animation / state setup. Your tool has no problems with two On/Off animation method. It works without much problems.
But, Haï, i wasted hours to figure out why my toggles cannot reset the animation position and when i slowly build up, i discovered your tool changed the FX and broke the reset part. Why can your tool break some animator parts? This is not supposed to break something.
Now i know your tool can break the one animation/state trigger config, i am forced to use two animations/stats ON/OFF trigger config. But i am not happy here. Can you explain me what happened in the animator? What might break the animator parts?
I delete all generated FX setups made by your tool, and then all triggers worked normal. You did something here that cause broken FX for avatar toggle with one-animation/state method, like in picture below. No reset send here even trigger is back to False.

Hello,
First of all I need to ask, is your animator compliant with VRChat Documentation, notably the "Write Defaults of States" section?
See https://docs.vrchat.com/docs/avatars-30#write-defaults-on-states

Write Defaults is an option available on states in Animators in Unity. [...] Write Defaults will write the initial state of all animation properties at run-time. This can cause some very strange interactions if you don't plan for it.
[...]
We recommend keeping Write Defaults off and explicitly animating any parameter that needs to be set by the animation. Note that this may require adding "reset" animations or adding properties to the animation to "initialize" transforms in a specific orientation.

By default, CGE requires that your avatar animator to be compliant with VRChat Documentation. If it is not compliant, CGE can break things because it was designed to work with compliant avatars.
If your avatar is NOT compliant with VRChat Documentation, you need to change this setting to tell CGE that it needs to be built with a compatibility mode:


[WIP] RPC import multi

cc @promag

Beside my comments, there are a lot of inconsistencies in the code regarding {}, spaces and maybe indentation. Also, follow the argument naming convention whenever possible.
Please rebase with bitcoin master.

@promag Please review

If rescan is true and one timestamp is not provided then the rescan should begin at genesis.

Fixed.

Change commit message.

 Like in other calls (importpubkey, importprivkey, importaddress):

No, it shouldn't be a problem if there is chain data since the timestamp is provided. Otherwise a warning may be added to the return object saying that there is a chance some transactions are missing.

Deprecated by PR in upstream bitcoin. PR number 7551.


关于这个项目什么时候更新呢

hi，您好，想了解下，这个项目预计什么时候回公开呢

I'm interested too!

Thank @qqpann and @turbo0212 for your interest! Sorry for the delay because I spent a lot of time cleaning the code. Most of the code are now ready and I plan to release the code before the next week.

Code is realsed. If you have any problem using it, please don't hesitate to contact me.  @turbo0212 @qqpann


Mesh Skinning. Attempt #3

Objective
Load skeletal weights and indices from GLTF files. Animate meshes.
Solution

Load skeletal weights and indices from GLTF files.
Added SkinnedMesh component and  SkinnedMeshInverseBindPose asset
Added extract_skinned_meshes to extract joint matrices.
Added queue phase systems for enqueuing the buffer writes.

Some notes:

This ports part of # #2359 to the current main.
This generates new BufferVecs and bind groups every frame. The expectation here is that the number of Query::get calls during extract is probably going to be the stronger bottleneck, with up to 256 calls per skinned mesh. Until that is optimized, caching buffers and bind groups is probably a non-concern.
Unfortunately, due to the uniform size requirements, this means a 16KB buffer is allocated for every skinned mesh every frame. There's probably a few ways to get around this, but most of them require either compute shaders or storage buffers, which are both incompatible with WebGL2.

@Looooong Why extract the SkinnedMeshInverseBindposes into an Asset? Handling them would be much easier if the individual matrices were stored as component of the joint entities. Is there any benefit to it I'm not seeing?

I consolidated the joint binding into the Mesh bind group, which I think is the right path forward, given how limited bind group slots are in practice (4 is what we can rely on).
I think this is good to go. I'll wait for feedback on the merged bind group from at least one other person involved in this before merging though.

How does WGSL/wgpu handle bindings that go unused? I was originally under the impression that the two had to be 1:1 Any skinned mesh on screen would add an extra binding to all drawn meshes.

How does WGSL/wgpu handle bindings that go unused? I was originally under the impression that the two had to be 1:1 Any skinned mesh on screen would add an extra binding to all drawn meshes.

Bindings must be used / bound. Note that in my change there are two "flavors" of the bind group: one with skinning and one without. The proper bind group is selected based on whether or not skinning is enabled. It is always a "perfect fit".

While I think this will work for this particular case, I'm not sure how well this will go when we need expanded support (i.e. morph targets), as we'd have combinatorially many bind groups. I guess we'll cross that bridge when we get there.

bors r+

there is some Z-fighting in 'custom_skinned_mesh' example, not like a major issue but it's better not to see things like that)


New ent schema will not migrate database gracefully.

Describe the bug
Upgrading to latest ent schemas will trigger the following error on postgres if it's using a older database.
2021-11-30 13:57:10.201 AEST [864] ERROR:  column "created_at" contains null values
2021-11-30 13:57:10.201 AEST [864] STATEMENT:  ALTER TABLE "refs" ADD COLUMN "created_at" timestamp with time zone NOT NULL

We need to investigate if its possible to adjust the migration process of ent to accommodate for this new column. Or if there is something we can change in the schema.

Maybe we should have an init container which checks the database schema version and the updates the steps between the actual version and the one needed by flow/funtions etc. For now on main we can just run the init container to update from 0.5.x to 0.6.0.

I have created a WIP PR for this. An init-container which can update the database manually if required.

I've had a look at the pr and it fixes the original problem created by the created_at. From what I understand we need to somehow know both the current version of the database tables and the current flow version. The current flow version is easy enough as it's something that exists in the helm values. But a record of the current database version is not stored anywhere (at least to my knowledge), and would probably need to be stored in the database itself.
What I'm thinking:

Add a table to our database that keeps a record of current and previous versions of the database. [To clarify, by version I mean something like v.0.6.0]
On init container compare current helm version tag with current version from the database. If database version is older than the current helm, then execute all manual migration upgrades from db version to latest/current helm version. Finally, update db table and set current database version to current helm version.
Limitation: This can only upgrade forward. You will not be able to downgrade gracefully (Technically we could also handle this, but I don't think it's worth the effort of inversing the upgrade steps.)

I agree. I left that open for you and Alan to assess and implement. At the moment it can only do forward as you said but I think that is the only way we need. I think we store the generation in the database and on startup we compare it with the generation in flow. That is how it is implemented, assuming we get the difference of generations on startup.


ciao-storage: correct args for CreateBlockDevice

imageFeatures was appended as an argument when creating block
devices, however, it was incorrectly done as a single string
rather than an array so it caused failures when executing.
Signed-off-by: Kristen Carlson Accardi<EMAIL_ADDRESS>

Coverage increased (+0.006%) to 66.781% when pulling ce43abd0c7328a4ab0b34a1b77490a34133bb68e on kaccardi:topic/fix-image-layering-param into 37625c2d772254a8e2e3ecf2be0c6e63642820e2 on 01org:master.


minor performance tweak

Codecov Report
Base: 88.95% // Head: 87.13% // Decreases project coverage by -1.81% :warning:

Coverage data is based on head (1b061bd) compared to base (de96b4e).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #401      +/-   ##
==========================================
- Coverage   88.95%   87.13%   -1.82%
==========================================
  Files          11       11
  Lines        2688     2682       -6
==========================================
- Hits         2391     2337      -54
- Misses        297      345      +48

Impacted Files
Coverage Δ

src/abstractinterpret/typeinfer.jl
89.09% <100.00%> (-5.22%)
:arrow_down:

src/analyzers/jetanalyzer.jl
90.81% <0.00%> (-3.84%)
:arrow_down:

src/ui/print.jl
91.33% <0.00%> (-0.67%)
:arrow_down:

src/JET.jl
71.36% <0.00%> (-0.60%)
:arrow_down:

src/abstractinterpret/inferenceerrorreport.jl
91.42% <0.00%> (-0.39%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


add container registry to e2e

Changes

Fixes https://github.com/shipwright-io/cli/issues/43
Submitter Checklist

[ ] Includes tests if functionality changed/was added
[ ] Includes docs if changes are user-facing
[ ] Set a kind label on this PR
[ ] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
NONE

/kind dependency-chage

/kind cleanup

the unit test failure was another timing window in the log follow test I recently added ... will open separate issue

/approve
/lgtm

I'll work on https://github.com/shipwright-io/cli/issues/48 in a few as this PR is getting unlucky with it

hopefully https://github.com/shipwright-io/cli/pull/49 unblocks the unrelated unit test hiccup seen here


ERROR: Failed to handle asynchronous tasks as synchronous, tasks result is undefined

Policy Package Import failed to a Domain in R80.10 MDS - following is the error (in italics)  happens after importing access-sections -
`
_Imported 80 out of 114 access-sections (70%)
Imported 100 out of 114 access-sections (87%)
Traceback (most recent call last):
File "import_export_package.py", line 61, in
import_package(client, args)
File "/Users/manub/Desktop/cpmigration/ExportImportPolicyPackage-master/importing/import_package.py", line 52, in import_package
layers_to_attach = import_objects(args.file, client, {})
File "/Users/manub/Desktop/cpmigration/ExportImportPolicyPackage-master/importing/import_objects.py", line 103, in import_objects
import_objects(rulebase_object_file.name, client, changed_layer_names, layer_name)
File "/Users/manub/Desktop/cpmigration/ExportImportPolicyPackage-master/importing/import_objects.py", line 94, in import_objects
changed_layer_names, api_call, num_objects, client)
File "/Users/manub/Desktop/cpmigration/ExportImportPolicyPackage-master/importing/import_objects.py", line 335, in add_object
publish_reply = client.api_call("publish", wait_for_task=True)
File "/Users/manub/Library/Python/2.7/lib/python/site-packages/cpapi/mgmt_api.py", line 352, in api_call
res = self.__wait_for_task(res.data["task-id"])
File "/Users/manub/Library/Python/2.7/lib/python/site-packages/cpapi/mgmt_api.py", line 510, in _wait_for_task
task_result)
cpapi.api_exceptions.APIException: ERROR: Failed to handle asynchronous tasks as synchronous, tasks result is undefined
`

Hi @manuadoor,
It seems to be related to our Python SDK and not the tool itself.
In order to investigate this issue, please send the exported file (tar.gz) you try import + tool logs + specify from which version you did export to<EMAIL_ADDRESS>Thanks,
Roy

Hello @chkp-royl  Thanks for responding. This issue was further isolated due to compute resources, allocating more resources solved this....
Thanks....


OSS-Fuzz doesn't work with bzlmod

Expected Behavior
After migrating to bzlmod, OSS-Fuzz continues to work for my project.
Actual Behavior
I get the following error, full log:
no such package '@@[unknown repo 'rules_fuzzing_oss_fuzz' requested from @@]//': The repository '@@[unknown repo 'rules_fuzzing_oss_fuzz' requested from @@]' could not be resolved: No repository visible as '@rules_fuzzing_oss_fuzz' from main repository

This arises because bazel_build_fuzz_tests in OSSFuzz checks out my project, and then attempts to build it with bazel flags like,
--@rules_fuzzing//fuzzing:cc_engine=@rules_fuzzing_oss_fuzz//:oss_fuzz_engine

However, the name @rules_fuzzing_oss_fuzz is not exposed by my repository: this is a transitive non-module-dependency of rules_fuzzing.
In general, it seems like users of rules_fuzzing need to be able to refer to these "non-module dependencies" (to set flags like --@rules_fuzzing//fuzzing:cc_engine), so they should be exposed.
Workaround
Indeed, we can get OSSFuzz to work again by adding to our MODULE.bazel,
non_module_dependencies = use_extension("@rules_fuzzing//fuzzing/private:extensions.bzl", "non_module_dependencies")
use_repo(
    non_module_dependencies,
    "rules_fuzzing_oss_fuzz",
)

But this can't be the intended interface (since the module extension is private). Should it be public instead? Or are we holding it wrong and we should expose this name in some other manner?
cc @fmeum (who added bzlmod support in https://github.com/bazel-contrib/rules_fuzzing/pull/242) @nopsledder (who reported this issue internally)
Specifications

Version: 0.5.2
Platform: Linux

The workaround is not very satisfactory because it requires us to add direct deps on Abseil and fuzztest (http://pwrev.dev/238471) even though these are in fact transitive deps required by rules_fuzzing_oss_fuzz.

I sent https://github.com/bazel-contrib/rules_fuzzing/pull/258 to give Bzlmod users a way to reference this engine without reaching into internal extensions.
We would need to update the OSS-Fuzz build scripts in lockstep or perform some kind of feature detection - not sure what's the best way to do this. As a workaround, you should be able to specify the new targets via extra build flags.


docs: fix article "remove-network" to guide the user to click resource name, update title and etc

Description of changes

[ ]

GitHub issues resolved by this PR

[ ] This PR resolves #864

Quality Assurance

Once the changes in this PR are merged and deployed, success criteria is: Update the article https://www.devopness.com/docs/linked-resources/add-linked-resource/

More info

@dudunog is this PR title compatible with the changed files in this PR? 🤔
Also, could you please add a short Description of changes for more context?

@jfoliveira Fixed the PR title and the description of changes.


<EMAIL_ADDRESS>hash check failed

Prerequisites

[X] I have used the predefined issue title. (e.g. "xxx@xxx: hash check failed")
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name and Version
<EMAIL_ADDRESS>

ERROR Hash check failed!
App:         extras/wechat
URL:         https://dldir1v6.qq.com/weixin/Windows/WeChatSetup.exe#/dl.7z
First bytes: 4D 5A 90 00 03 00 00 00
Expected:    04a668ea0d36cd8963acc2b9c0f0aff0c0a7c73f46127863ea1f90e942664171
Actual:      76b4d0f4dc28a679bea09b2471444956e43680982b31eec9584e9ccf695046d9

Fixed by #14022.


Move fixed-point datatypes to their own package.

This adds a little more friction in order to encourage the use of type
class constraints rather than hard-coding a particular type.

Current coverage is 78.10% (diff: 33.33%)

Merging #33 into master will not change coverage

@@             master        #33   diff @@
==========================================
  Files            27         28     +1
  Lines           507        507
  Methods         504        503     -1
  Messages          0          0
  Branches          2          3     +1
==========================================
  Hits            396        396
  Misses          111        111
  Partials          0          0

Powered by Codecov. Last update 2aa57dc...6154083

Seems harmless enough. My only question would be about the package name. You already have matryoshka.instances, which would seem to be intended to contain things like this, but there's nothing in it at the moment except the sub-package fixpoint, which I guess is more like demos and not really meant to be used in anger, although the name doesn't really convey that. I don't see a clear distinction between data and instances. Why not just put the concrete types in instances?

So, instances may not be a great name, but I think it does need to be distinct from data.
data is something you’ll hopefully use sparingly, perhaps just in main, when you decide exactly what representation you want when applying all the generic algebras and folds.
instances.fixedpoint is more an alternative to (parts of) Cats or Scalaz. It’s an application of recursion schemes that could potentially be a separate library. IIRC, the intervening instances name was intended for when #21 was sorted out, and there would be instances.std as well as instances.scalaz and instances.cats in appropriate subprojects.

OK, well I don't think either name is great, but names are hard for this stuff, so as long as you've thought it through I'm willing to defer to you and I don't have any other concerns.

Well, the data name comes from Cats (with, I think, the same intent) – the type classes are in cats, and the data types are in cats.data. So, I was just trying to maintain the pattern there. In general, I’ve been taking organizational cues from there instead of Scalaz, even though we still only support Scalaz.


Improve article 2206.14176

Exact location of issue
https://ar5iv.labs.arxiv.org/html/2206.14176
Problem details
Conversion to HTML had a Fatal error and exited abruptly. This document may be truncated or damaged.
Desktop (please complete the following information)

OS: Windows
Browser chrome, firefox

Thanks again! Keep the issues coming 👍🏻
Missing packages here: cuted.sty, eqparbox.sty, xstring.sty, tocbasic.sty, datetime2.sty, stackengine.sty, xpatch.sty
Combined with a raw interpretation of tabularray.sty (in a LaTeX 3 context), an infinite loop lead to 100 errors, terminating conversion.

The article now produces some HTML, but a long way remains to fully supported:

Conversion complete: 14 warnings; 13 errors; 6 undefined macros[\NewColumnType, \BODY, \xapptocmd, {mytabular}, \NewEnviron, \DeclareTOCStyleEntry]; 7 missing files[xstring.sty, eqparbox.sty, datetime2.sty, stackengine.sty, xpatch.sty, cuted.sty, tocbasic.sty]


fix [amodownloads] service test

https://app.circleci.com/pipelines/github/badges/daily-tests/493/workflows/6325b24b-9bb1-48a3-bc70-258f8bd9ee87/jobs/1391

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 1c4bfad9fc2fe2861fb4bcec1adec99ca721e3e1


[docs] Update README.md

fix a spelling error

Which Delta project/connector is this regarding?

[ ] Spark
[ ] Standalone
[x] Flink
[ ] Kernel
[ ] Other (fill in here)

Description

How was this patch tested?

Does this PR introduce any user-facing changes?

Thank you for catching it!


PHP 8.1 and CLI

progress bar is not compatible with php 8.1 yet.
https://github.com/thephpleague/climate/issues/189

php8.4 released recently. closing this old issue


Enable monitoring of multiple Stream keys

Currently we only support monitoring single Streams. Would be great to have a single instance of the app monitor multiple streams concurrently in the same database.

First of all, thanks for create this project. I started to use it and now I have to create one exporter per stream. Monitor multiple streams would be awesome. Thanks.

@danielrosa-zh multi-stream support has been added in v0.6 👍

For what it's worth, https://github.com/oliver006/redis_exporter now has streams support (plus groups). To be perfectly honest I'd recommend using that over this project since it's more actively maintained.

@chrnola , great!
good to know that this from oliver support stream. Thanks a lot!


Add support for unix:// transport

This change adds support for unix domain socket transport for using unix:// for connections.

While this may look good functionally, it unfortunately lacks documentation and tests. I've prepared a very much similar PR, do you feel like updating or should I file mine? :+1:

I added some test, but hhvm fails. I will try to fix it tomorrow.

Ok, i made ugly hack for hhvm because there is a bug in hhvm (see https://github.com/facebook/hhvm/issues/7733).
Tomorrow I will add some info in readme about the unix sockets.


Add support for intel_backlight on FreeBSD

Test if intel_backlight binary is present, and if so use it.
Note: this works for now but it might be a good idea to make sure ~/.lumina/.currentxbrightnessalways matches intel_backlight output, and also this just changes things for lumina-open, not sure about the system dashboard slider.

Changing the setting in this function will change all Lumina support for screen brightness (all utilities/sliders use the same backend functions). I will adjust the change a little bit to ensure the setting gets saved for later in just a moment for you... :-)
Thanks for working on that!

Ok, I just finished cleaning up the change a bit[1].
Note how I check for success of intel_backlight: I looked up the utility sources and discovered that it does not report success/failure of the operation, so I had to set it up to re-run the tool and compare the current setting against the value we just tried to set. I also changed prioritization for the tools, since the PC-BSD tool is for any type of hardware (all ACPI/sysctl's) I gave that higher priority in the detection routine than intel_backlight (intel_backlight is only for Intel motherboards/GPUs?). It should properly "fall through" until it finds a working implementation now though (with software brightness setting as the last resort).
Thanks!
[1] https://github.com/pcbsd/lumina/commit/82b49f3eb8667290b4c5ed6d3b9036fbe96a4de2

Nice works on the success check.
I gave Intel_backlight "priority" on purpose.... because I have pcbsd-utils installed on freebsd (to use pcdm for example and other tools) but the pc-sysconfig utility won't do much for me and with this way it would still run it and then run xbrightness skipping intel_backlight... but that was with my poor if else cycle which was not bad consider this was probably my first c++/qt patch to anything xD
But now it looks much better and will work for all cases, awesome xD


"treat all warnings as errors" cmake rule, macro for disabling 3rdparty includes' warnings

"treat all warnings as error" cmake rule, macro for disabling 3rdparty includes warnings
Description
Useful tools for dealing with warnings have been added
Testing
It wasn't really tested at all
TODO list:

Fix warnings with these tools

[CI]: Can one of the admins verify this patch?

[CI]: Can one of the admins verify this patch?

As far as I can tell, AnastaZIuk will verify it, but I'm not sure yet

we will test it with CI once you wrap all our 3rdparty includes present in Nabla sources with those macros

okay I need to think about it if std includes generate warnings we actually could silent them too

okay I need to think about it if std includes generate warnings we actually could silent them too

silent all 3rdparty which are included into Nabla first, if there are errors from directly std after you do it we may silent the headers they come from too

okay I need to think about it if std includes generate warnings we actually could silent them too

they never should

as you are on it you could turn all of our 3rdparty include directives you are wrapping with the macro which use <> into ""


Add a way to configure cert loading from the storage

This is a proposal PR to address https://github.com/caddyserver/certmagic/issues/76
Note: I don't fully understand the assumption made in CertMagic so this might be incorrect/problematic in some places. I also didn't fully test it. This PR is to show what changes I suggest.
In term of DX, changes are as follow:

the OnDemand concept is restricted to generating certs from the CA instead of this + loading from storage
an extra configuration struct is added to control how storage certs are loaded
exact match certificates are still loaded as previously
loading multi-level wildcard certificates is gated by an extra config flag to avoid the performance penalty, even if you want to load wildcard certificates

@mholt Is that something you would consider?

I'll take a look at it as soon as I get a chance, thanks!

No pressure :)

I forget when exactly it happened, but loading wildcards from storage is already implemented. Closing this.


Port the firmware to the new Migen and MiSoC versions

We are currently using the legacy branch of Migen and MiSoC. This means that we aren't getting the new features or fixes that are being developed. We should move to the new version as soon as we are able.
Before the conversion can be done, the dependencies need to be converted too. We currently depend on;

[x] liteeth - https://github.com/enjoy-digital/liteeth
[x] litescope - https://github.com/enjoy-digital/litescope
[x] litex - https://github.com/enjoy-digital/litex (LiteEth and LiteScope depend on LiteX)

We should also consider the state of the following lite modules but they are not blocking;

[x] litejpeg - https://github.com/enjoy-digital/litejpeg
[x] [low] litedram - https://github.com/enjoy-digital/litedram
[x] [low] litepcie - https://github.com/enjoy-digital/litepcie
[x] [very low] liteusb - https://github.com/enjoy-digital/liteusb

Once they have been confirmed as done, we then need to convert our code. According to @enjoy-digital most of the work will be around the DMA.
One of the biggest change in migen was the way simulations are done. However, we don't have many simulations in our current system? Most of the tests seem to be in the csc module (see https://github.com/timvideos/HDMI2USB-misoc-firmware/tree/master/gateware/csc/test).

This has been done! Yay \o/


Document SSH requirements

Fixes #460
docs about ssh

/override pull-kubeone-e2e-aws-upgrade-1.14-1.15
/override pull-kubeone-e2e-aws-upgrade-1.13-1.14

/override pull-kubeone-e2e-aws-upgrade-1.14-1.15
/override pull-kubeone-e2e-aws-upgrade-1.13-1.14


[loadgenerator] Bump deps and update container base image

Changes
For some unknown reason the loadgenerator container image had a size of 1.02GB.
When updating the Dockerfile, I've also updated the dependencies and tidied up a bit the locustfile.py.
Now the image has a size of 135MB.
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[x] CHANGELOG.md updated to document new feature additions
[ ] Appropriate documentation updates in the docs folder

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

I think changelog is needed.

@mviitane would you be able to try it again?

@mviitane would you be able to try it again?

I now get further, but it still fails:
#0 27.56 Building wheels for collected packages: flask-basicauth, gevent, grpcio, markupsafe, msgpack, psutil, roundrobin, wrapt, zope-interface
#0 27.56   Building wheel for flask-basicauth (setup.py): started
#0 27.73   Building wheel for flask-basicauth (setup.py): finished with status 'done'
#0 27.73   Created wheel for flask-basicauth: filename=Flask_BasicAuth-0.2.0-py3-none-any.whl size=4241 sha256=1ac0f649a72d37c37be9509708d3c5562a5e3af06b0e4e0e1aa47e8169c25f08
#0 27.73   Stored in directory: /root/.cache/pip/wheels/b7/ac/af/20577bcc2e68ce45b0b40376df225e259ee98867c4afd79c1d
#0 27.73   Building wheel for gevent (pyproject.toml): started
#0 31.13   Building wheel for gevent (pyproject.toml): finished with status 'error'
#0 31.14   error: subprocess-exited-with-error

@mviitane how about now?

Thank you very much @mviitane, that was an interesting one.
Lets wait for some others to take a look, and if we get this merged I'll follow the same approach with the recommendationservice that has also a big image size.

Let's discuss this on Monday! That image size reduction is huge


Question. Why is z.custom not required by default

Following schema definition
const dataSourceSchema = registry.register(
    "DataSource",
    z
      .object({
        urn: z.custom<string>().openapi({
          description: "A unique URN for this datasource.",
        }),
        uri: z.string().openapi({
          description: "A URI where this data originated from.",
        }),
        date: z.string().openapi({
          description: "A point in time when this datasource was processed.",
        }),
      })
      .openapi({
        description: "wsdsdsdsd",
      })
  );

will produce following yaml

  DataSource:
    type: object
    properties:
      urn:
        nullable: true
        description: A unique URN for this datasource.
      uri:
        type: string
        description: A URI where this data originated from.
      date:
        type: string
        description: A point in time when this datasource was processed.
    required:
      - uri
      - date
    description: wsdsdsdsd

Why is it that

nullable:true
not required?

I have tried to work around with
const dataSourceSchema = registry.register(
    "DataSource",
    z
      .object({
        urn: z.custom<string>().openapi({
          description: "A unique URN for this datasource.",
        }),
        uri: z.string().openapi({
          description: "A URI where this data originated from.",
        }),
        date: z.string().openapi({
          description: "A point in time when this datasource was processed.",
        }),
      })
      .openapi({
        description: "wsdsdsdsd",
        required : ["urn", "uri", "date"]
      })
  );

But when referencing this schema from another schema like this
  const otherSchema = zodOpenApiController.getRegistry().register(
    "OtherSchema",
    z.object({
      datasource: dataSourceSchema,
    })
  );

the yaml seems not correct to me
    DataSource:
      type: object
      properties:
        urn:
          nullable: true
          description: A unique URN for this datasource.
        uri:
          type: string
          description: A URI where this data originated from.
        date:
          type: string
          description: A point in time when this datasource was processed.
      required:
        - urn
        - uri
        - date
      description: wsdsdsdsd
    OtherSchema:
      type: object
      properties:
        datasource:
          allOf:
            - $ref: "#/components/schemas/DataSource"
            - required:
                - uri
                - date

What am i doing wrong? Why is it generating this strange allOff
Thx. for help!

@brupxxxlgroup as for your initial question - well because this is the way zod works when it parses data. Using your example the following:
  dataSourceSchema.safeParse({
    uri: 'some uri',
    date: 'some date',
  })
``
would result in `{ success: true, data: { uri: 'some uri', date: 'some date' } }`

and so would passing `urn: null`. So it should be nullable.

As for your other question. This is an interesting one. We should look into it, however I do not know when we would be able to present a fix.

@brupxxxlgroup when I tested this today I do not see an issue with the result from this script:

extendZodWithOpenApi(z);

const registry = new OpenAPIRegistry();

const dataSourceSchema = registry.register(
  'DataSource',
  z
    .object({
      urn: z.custom<string>().openapi({
        description: 'A unique URN for this datasource.',
      }),
      uri: z.string().openapi({
        description: 'A URI where this data originated from.',
      }),
      date: z.string().openapi({
        description: 'A point in time when this datasource was processed.',
      }),
    })
    .openapi({
      description: 'wsdsdsdsd',
    })
);

const otherSchema = registry.register(
  'OtherSchema',
  z.object({
    datasource: dataSourceSchema,
  })
);

const generator = new OpenApiGeneratorV3(registry.definitions);

const docs = generator.generateDocument({
  openapi: '3.0.0',
  info: {
    version: '1.0.0',
    title: 'My API',
    description: 'This is the API',
  },
  servers: [{ url: 'v1' }],
});

console.log(JSON.stringify(docs, null, 4));

being:
{
    "openapi": "3.0.0",
    "info": {
        "version": "1.0.0",
        "title": "My API",
        "description": "This is the API"
    },
    "servers": [
        {
            "url": "v1"
        }
    ],
    "components": {
        "schemas": {
            "DataSource": {
                "type": "object",
                "properties": {
                    "urn": {
                        "nullable": true,
                        "description": "A unique URN for this datasource."
                    },
                    "uri": {
                        "type": "string",
                        "description": "A URI where this data originated from."
                    },
                    "date": {
                        "type": "string",
                        "description": "A point in time when this datasource was processed."
                    }
                },
                "required": [
                    "uri",
                    "date"
                ],
                "description": "wsdsdsdsd"
            },
            "OtherSchema": {
                "type": "object",
                "properties": {
                    "datasource": {
                        "$ref": "#/components/schemas/DataSource"
                    }
                },
                "required": [
                    "datasource"
                ]
            }
        },
        "parameters": {}
    },
    "paths": {}
}

This is correct so apparently we've fixed that with some other issue. Closing this issue


Specify config file location via environment

I'm using cargo in an autoconf-managed build system. I want to auto-generate a part of the .cargo/config file, because Cargo doesn't seem to expose env variables for the vendored sources config options, but where the vendored sources live should be overwritable by the user during ./configure. It seems cargo really wants to be run inside the source tree, but config.status places the generated .cargo/config into the build dir. Copying the entire rust tree of the project from the source dir into the build dir could be a workaround, but instead it'd be neat if cargo allowed to just specify a different location for its config file.

Note that it's a bug in Cargo if Cargo doesn't read .cargo/config values from the environment, so I think that may be the best fix here?

Perhaps I misunderstand, but what would the env variables even be for something like [source.vendored-sourced] where the vendored-sources seems to be a user-defined string?

Oh in general we just have a standard mechanism for defining config values as environment variables

that doesn't explain at all how to set that. It says: "For each configuration key above of the form foo.bar the environment variable CARGO_FOO_BAR can also be used to define the value. For example the build.jobs key can also be defined by CARGO_BUILD_JOBS."
This doesn't explain how to put this:
[source.vendored-sources]
directory = "foo"
into env variables. Also, how can I unset something via env variable that's given in a configuration file? Happy to improve the documentation once I understand that :)

Oh that would in theory be CARGO_SOURCE_VENDORED_SOURCES_DIRECTORY=foo. Unfortunately there's no way to unset what's in a config file, although I believe the environment takes precedence.
PRs are of course always welcome to improve the docs!

@alexcrichton It doesn't look like setting environment variables to set source properties like that is supported, and the relevant source code is just looking up "sources" from a hash map, without checking the environment variables. I'll raise a bug for this.

There is now a lot more information about setting environment variables via #7650.  The [source] table not supporting env vars is tracked via #5416.


[Feature] Redesign of customer cards v2

Se agregó el rediseño en CustomerCardActivity.

[ ] Coverage > 90%
[x] Android Lint check
[x] Code Style checked

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@e431dc4). Click here to learn what that means.
The diff coverage is 18.8%.

@@            Coverage Diff            @@
##             develop    #538   +/-   ##
=========================================
  Coverage           ?   3.94%
=========================================
  Files              ?     180
  Lines              ?   12208
  Branches           ?    1076
=========================================
  Hits               ?     481
  Misses             ?   11656
  Partials           ?      71

Impacted Files
Coverage Δ

...c/main/java/com/mercadopago/DiscountsActivity.java
0% <ø> (ø)

...ain/java/com/mercadopago/PaymentVaultActivity.java
0% <ø> (ø)

.../src/main/java/com/mercadopago/model/Campaign.java
3.4% <0%> (ø)

.../mercadopago/adapters/CustomerCardItemAdapter.java
0% <0%> (ø)

...in/java/com/mercadopago/CustomerCardsActivity.java
0% <0%> (ø)

.../main/java/com/mercadopago/core/MercadoPagoUI.java
0% <0%> (ø)

...rcadopago/providers/CustomerCardsProviderImpl.java
0% <0%> (ø)

...paymentmethodsearch/PaymentMethodSearchOption.java
0% <0%> (ø)

.../mercadopago/presenters/PaymentVaultPresenter.java
52.5% <25%> (ø)

.../main/java/com/mercadopago/util/ResourcesUtil.java
50% <50%> (ø)

... and 1 more

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 e431dc4...1ceb88f. Read the comment docs.


nuxt 3 project fails building

building a nuxt 3 project via dream2nix does not work due to the way nuxi handles project roots.
relevant log:
> 37-ocean-breeze@ build /nix/store/dlyxmpnjga0wa0n3bh4c862j7vaxrga4-37-ocean-breeze-unknown/lib/node_modules/37-ocean-breeze
> nuxt build

Nuxi 3.0.0-rc.11
Nuxt 3.0.0-rc.11 with Nitro 0.5.4

 ERROR  Cannot detect workspace root from /nix/store/dlyxmpnjga0wa0n3bh4c862j7vaxrga4-37-ocean-breeze-unknown/lib/node_modules/37-ocean-breeze

  at findWorkspaceDir (node_modules/pkg-types/dist/index.mjs:117:9)
  at async loadOptions (node_modules/nitropack/dist/shared/nitro.9c828268.mjs:2271:26)
  at async createNitro (node_modules/nitropack/dist/shared/nitro.9c828268.mjs:2347:19)
  at async initNitro (node_modules/nuxt/dist/index.mjs:1402:17)
  at async initNuxt (node_modules/nuxt/dist/index.mjs:1612:3)
  at async loadNuxt (node_modules/nuxt/dist/index.mjs:1635:5)
  at async loadNuxt (node_modules/@nuxt/kit/dist/index.mjs:732:19)
  at async Object.invoke (node_modules/nuxi/dist/chunks/build.mjs:34:18)
  at async _main (node_modules/nuxi/dist/cli.mjs:50:20)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! 37-ocean-breeze@ build: `nuxt build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the 37-ocean-breeze@ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /build/.npm/_logs/2022-09-29T11_24_55_449Z-debug.log

relevant part as screenshot

hmm, after some testing, it seems to be only happening when using direnv, running nix develop works fine

in my case, update npm fixed it
npm install -g npm@latest
it seems to be an issue with the npm version.
I didn't have this issue when using pnpm.

I was not able to reproduce this issue on a freshly initialized nuxt3 project. Could you provide a flake that reproduces the issue?


Error:Unexpected error in EventBusAnnotationProcessor: java.lang.EnumConstantNotPresentException: org.greenrobot.eventbus.ThreadMode.MAIN_ORDERED

ThreadMode.MAIN_ORDERED is not getting recognized by the EventBusAnnotationProcessor.
Please check the configurations as below.
build.gradle
android {
    compileSdkVersion 25
    defaultConfig {
        applicationId "com.sumitanantwar.eventbus_poc"
        minSdkVersion 15
        targetSdkVersion 25
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
        javaCompileOptions {
            annotationProcessorOptions {
                arguments = [ eventBusIndex : 'com.sumitanantwar.eventbus_poc.MyEventBusIndex' ]
            }
        }
    }
    ...
}

dependencies {
    .......
    // Eventbus
    implementation 'org.greenrobot:eventbus:3.1.1'
    annotationProcessor 'org.greenrobot:eventbus-annotation-processor:3.1.0'
    .......
}

Activity.java
public class MainActivity extends AppCompatActivity
{
    @Subscribe(threadMode = ThreadMode.MAIN_ORDERED)
    public void onEvent(TestEvent event)
    {
        // Do some stuff
    }

    @Override
    protected void onCreate(Bundle savedInstanceState)
    {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

        EventBus.getDefault().register(this);
    }

    public static class TestEvent
    {
        String data;
    }
}

ERROR
Error:Unexpected error in EventBusAnnotationProcessor: java.lang.EnumConstantNotPresentException: org.greenrobot.eventbus.ThreadMode.MAIN_ORDERED
Error:Execution failed for task ':app:compileDebugJavaWithJavac'. > Compilation failed; see the compiler error output for details.

Stack Trace
java.lang.EnumConstantNotPresentException: org.greenrobot.eventbus.ThreadMode.MAIN_ORDERED
        at sun.reflect.annotation.EnumConstantNotPresentExceptionProxy.generateException(EnumConstantNotPresentExceptionProxy.java:46)
        at sun.reflect.annotation.AnnotationInvocationHandler.invoke(AnnotationInvocationHandler.java:84)
        at com.sun.proxy.$Proxy130.threadMode(Unknown Source)
        at org.greenrobot.eventbus.annotationprocessor.EventBusAnnotationProcessor.writeCreateSubscriberMethods(EventBusAnnotationProcessor.java:287)
        at org.greenrobot.eventbus.annotationprocessor.EventBusAnnotationProcessor.writeIndexLines(EventBusAnnotationProcessor.java:373)
        at org.greenrobot.eventbus.annotationprocessor.EventBusAnnotationProcessor.createInfoIndexFile(EventBusAnnotationProcessor.java:333)
        at org.greenrobot.eventbus.annotationprocessor.EventBusAnnotationProcessor.process(EventBusAnnotationProcessor.java:106)
        at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)
        .......
error: Unexpected error in EventBusAnnotationProcessor: java.lang.EnumConstantNotPresentException: org.greenrobot.eventbus.ThreadMode.MAIN_ORDERED
1 error

I can compile for targetSdkVersion 25 but not for 26 or 27

The issue occurs when updating the Android Gradle Plugin to 3.0.0. It appears to be caused by the annotation processor artifact depending on EventBus 3.1.0 instead of 3.1.1.
Will likely fix by releasing an updated annotation processor artifact. -ut

Dear @greenrobot-team, how would I have gone about debugging this and offering a fix?
I've not done anything with annotation processing except for poking around with this and thinking about some ideas I might want to implement. But being (more) helpful in situations like this seems like a good start.

@BrendonW I would try to reproduce the issue with a simple test project to narrow down where it breaks.
In this case there isn't a fix you can suggest, there is apparently an issue with the version of the EventBus artifact the processor depends on. As the new Android Gradle plugin seems to handle dependencies for annotation processors differently this blew up.
-ut

Checked just now, the build was successful, and the index was also successfully generated.
Thanks a lot!

It's working for me too.
THANKS.