Options dialog not showing conf file

Installed bitcoin core on Windows 10. Changed the data directory to d:\bitcoin. Clicked Settings > Options > Open Configuration File. It opened a blank file for me and saved it in the data directory. I went back and updated the conf file with some defaults. And restarted bitcoin core. The debug log (attached), shows that it is reading my conf file. But when I open the GUI (screen shot attached), it shows the conf file as being "none".
Expected behavior
Expect that the conf file from which conf settings are being applied, should also be displayed in the GUI, so I have assurance that my settings have taken effect.
Actual behavior
It says "none" for my conf file.

To reproduce
I suppose it should be reproducible if somebody does the same steps on windows as described above.
System information
Bitcoin core version v0.21.1 downloaded from bitcoin.org
System: Dell Optiplex 3010 i5 Windows 10.
Debug log:
2021-07-28T17:43:21Z Bitcoin Core version v0.21.1 (release build)
2021-07-28T17:43:21Z Qt 5.9.8 (static), plugin=windows (static)
2021-07-28T17:43:21Z System: Windows 10 (10.0), x86_64-little_endian-llp64
2021-07-28T17:43:21Z Screen: \.\DISPLAY1 1440x900, pixel ratio=1.0
2021-07-28T17:43:21Z Assuming ancestors of block<PHONE_NUMBER>000000000b9d2ec5a352ecba0592946514a92f14319dc2b367fc72 have valid signatures.
2021-07-28T17:43:21Z Setting nMinimumChainWork=00000000000000000000000000000000000000001533efd8d716a517fe2c5008
2021-07-28T17:43:21Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2021-07-28T17:43:21Z Using RdRand as an additional entropy source
2021-07-28T17:43:21Z Default data directory C:\Users\asifs\AppData\Roaming\Bitcoin
2021-07-28T17:43:21Z Using data directory D:\bitcoin
2021-07-28T17:43:21Z Config file: D:\bitcoin\bitcoin.conf
2021-07-28T17:43:21Z Config file arg: rpcpassword=****
2021-07-28T17:43:21Z Config file arg: rpcuser=****
2021-07-28T17:43:21Z Config file arg: server="1"
2021-07-28T17:43:21Z Config file arg: txindex="1"
2021-07-28T17:43:21Z Config file arg: zmqpubrawblock="tcp://<IP_ADDRESS>:29000"
2021-07-28T17:43:21Z Config file arg: zmqpubrawtx="tcp://<IP_ADDRESS>:29000"
2021-07-28T17:43:21Z Using at most 125 automatic connections (2048 file descriptors available)
2021-07-28T17:43:21Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2021-07-28T17:43:21Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2021-07-28T17:43:21Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2021-07-28T17:43:21Z Script verification uses 3 additional threads
2021-07-28T17:43:21Z scheduler thread start
2021-07-28T17:43:21Z HTTP: creating work queue of depth 16
2021-07-28T17:43:21Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2021-07-28T17:43:21Z HTTP: starting 4 worker threads
2021-07-28T17:43:21Z Using wallet directory D:\bitcoin\wallets
2021-07-28T17:43:21Z init message: Verifying wallet(s)...
2021-07-28T17:43:21Z init message: Loading banlist...
2021-07-28T17:43:21Z SetNetworkActive: true
2021-07-28T17:43:21Z Using /16 prefix for IP bucketing
2021-07-28T17:43:21Z Cache configuration:
2021-07-28T17:43:21Z * Using 2.0 MiB for block index database
2021-07-28T17:43:21Z * Using 56.0 MiB for transaction index database
2021-07-28T17:43:21Z * Using 8.0 MiB for chain state database
2021-07-28T17:43:21Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2021-07-28T17:43:21Z init message: Loading block index...
2021-07-28T17:43:21Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2021-07-28T17:43:21Z Opening LevelDB in D:\bitcoin\blocks\index
2021-07-28T17:43:22Z Opened LevelDB successfully
2021-07-28T17:43:22Z Using obfuscation key for D:\bitcoin\blocks\index:<PHONE_NUMBER>000000
2021-07-28T17:43:23Z LoadBlockIndexDB: last block file = 0
2021-07-28T17:43:23Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2021-07-28T17:43:23Z Checking all blk files are present...
2021-07-28T17:43:23Z Opening LevelDB in D:\bitcoin\chainstate
2021-07-28T17:43:23Z Opened LevelDB successfully
2021-07-28T17:43:23Z Using obfuscation key for D:\bitcoin\chainstate: 28a99de8abe7eaf4
2021-07-28T17:43:23Z Loaded best chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progress=0.000000
2021-07-28T17:43:23Z init message: Rewinding blocks...
2021-07-28T17:43:23Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
2021-07-28T17:43:23Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
2021-07-28T17:43:23Z init message: Verifying blocks...
2021-07-28T17:43:23Z  block index            2094ms
2021-07-28T17:43:23Z Opening LevelDB in D:\bitcoin\indexes\txindex
2021-07-28T17:43:24Z Opened LevelDB successfully
2021-07-28T17:43:24Z Using obfuscation key for D:\bitcoin\indexes\txindex:<PHONE_NUMBER>000000
2021-07-28T17:43:24Z txindex thread start
2021-07-28T17:43:24Z block tree size = 255998
2021-07-28T17:43:24Z nBestHeight = 0
2021-07-28T17:43:24Z txindex is enabled at height 0
2021-07-28T17:43:24Z txindex thread exit
2021-07-28T17:43:24Z loadblk thread start
2021-07-28T17:43:24Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2021-07-28T17:43:24Z loadblk thread exit
2021-07-28T17:43:24Z torcontrol thread start
2021-07-28T17:43:24Z Bound to [::]:8333
2021-07-28T17:43:24Z Bound to <IP_ADDRESS>:8333
2021-07-28T17:43:24Z Bound to <IP_ADDRESS>:8334
2021-07-28T17:43:24Z init message: Loading P2P addresses...
2021-07-28T17:43:24Z Loaded 2545 addresses from peers.dat  16ms
2021-07-28T17:43:24Z Loaded 0 addresses from "anchors.dat"
2021-07-28T17:43:24Z 0 block-relay-only anchors will be tried for connections.
2021-07-28T17:43:24Z init message: Starting network threads...
2021-07-28T17:43:24Z net thread start
2021-07-28T17:43:24Z dnsseed thread start
2021-07-28T17:43:24Z addcon thread start
2021-07-28T17:43:24Z Waiting 300 seconds before querying DNS seeds.
2021-07-28T17:43:24Z opencon thread start
2021-07-28T17:43:24Z init message: Done loading
2021-07-28T17:43:24Z msghand thread start
2021-07-28T17:43:24Z GUI: Platform customization: "windows"
2021-07-28T17:43:30Z New outbound peer connected: version: 70016, blocks=693106, peer=0 (full-relay)
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 12
2021-07-28T17:43:31Z GUI:   OpenType support missing for "Arial", script 12
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS UI Gothic", script 12
2021-07-28T17:43:31Z GUI:   OpenType support missing for "SimSun", script 12
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 11
2021-07-28T17:43:31Z GUI:   OpenType support missing for "Arial", script 11
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS UI Gothic", script 11
2021-07-28T17:43:31Z GUI:   OpenType support missing for "SimSun", script 11
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 32
2021-07-28T17:43:31Z GUI:   OpenType support missing for "Arial", script 32
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS UI Gothic", script 32
2021-07-28T17:43:31Z GUI:   OpenType support missing for "SimSun", script 32
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 19
2021-07-28T17:43:31Z GUI:   OpenType support missing for "Arial", script 19
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS UI Gothic", script 19
2021-07-28T17:43:31Z GUI:   OpenType support missing for "SimSun", script 19
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 20
2021-07-28T17:43:31Z GUI:   OpenType support missing for "Arial", script 20
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS UI Gothic", script 20
2021-07-28T17:43:31Z GUI:   OpenType support missing for "SimSun", script 20
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 16
2021-07-28T17:43:31Z GUI:   OpenType support missing for "Arial", script 16
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS UI Gothic", script 16
2021-07-28T17:43:31Z GUI:   OpenType support missing for "SimSun", script 16
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 17
2021-07-28T17:43:31Z GUI:   OpenType support missing for "Arial", script 17
2021-07-28T17:43:31Z GUI:   OpenType support missing for "MS UI Gothic", script 17
2021-07-28T17:43:31Z GUI:   OpenType support missing for "SimSun", script 17
2021-07-28T17:43:31Z New outbound peer connected: version: 70016, blocks=693106, peer=1 (full-relay)
2021-07-28T17:43:31Z New outbound peer connected: version: 70015, blocks=693106, peer=2 (full-relay)
2021-07-28T17:43:32Z Synchronizing blockheaders, height: 257996 (~38.40%)
2021-07-28T17:43:33Z New outbound peer connected: version: 70016, blocks=693106, peer=3 (full-relay)
2021-07-28T17:43:33Z New outbound peer connected: version: 70015, blocks=693106, peer=4 (full-relay)
2021-07-28T17:43:33Z Synchronizing blockheaders, height: 259996 (~38.67%)
2021-07-28T17:43:34Z Synchronizing blockheaders, height: 261996 (~38.94%)
2021-07-28T17:43:35Z P2P peers available. Skipped DNS seeding.
2021-07-28T17:43:35Z dnsseed thread exit
2021-07-28T17:43:37Z Synchronizing blockheaders, height: 263996 (~39.21%)
2021-07-28T17:43:38Z Synchronizing blockheaders, height: 265996 (~39.47%)
2021-07-28T17:43:39Z Synchronizing blockheaders, height: 267996 (~39.73%)
2021-07-28T17:43:41Z Synchronizing blockheaders, height: 269996 (~40.01%)
2021-07-28T17:43:42Z Synchronizing blockheaders, height: 271996 (~40.29%)
2021-07-28T17:43:44Z Synchronizing blockheaders, height: 273996 (~40.56%)
2021-07-28T17:43:46Z Synchronizing blockheaders, height: 275996 (~40.83%)
2021-07-28T17:43:48Z Synchronizing blockheaders, height: 277996 (~41.11%)
2021-07-28T17:43:50Z Synchronizing blockheaders, height: 279996 (~41.38%)
2021-07-28T17:43:52Z Synchronizing blockheaders, height: 281996 (~41.65%)
2021-07-28T17:43:53Z Synchronizing blockheaders, height: 283996 (~41.92%)
2021-07-28T17:43:55Z Synchronizing blockheaders, height: 285996 (~42.20%)
2021-07-28T17:43:57Z Synchronizing blockheaders, height: 287996 (~42.47%)
2021-07-28T17:43:59Z Synchronizing blockheaders, height: 289996 (~42.75%)
2021-07-28T17:43:59Z New outbound peer connected: version: 70015, blocks=693106, peer=6 (full-relay)
2021-07-28T17:44:01Z Synchronizing blockheaders, height: 291996 (~43.03%)
2021-07-28T17:44:03Z Synchronizing blockheaders, height: 293996 (~43.30%)
2021-07-28T17:44:05Z Synchronizing blockheaders, height: 295996 (~43.58%)
2021-07-28T17:44:07Z Synchronizing blockheaders, height: 297996 (~43.86%)
2021-07-28T17:44:09Z Synchronizing blockheaders, height: 299996 (~44.14%)
2021-07-28T17:44:11Z Synchronizing blockheaders, height: 301996 (~44.41%)

Hi @asifshiraz!
I believe the issue raised by you is a design feature misinterpreted as a bug.
The Note mentioned above in the dialogue says:

The Options set in this dialogue are overridden by the command line or in the configuration file.

Focus on this
It does not say it reflects the name of the config file used for running the node. What it actually shows is a list of all the options relevant to that particular dialogue box and nothing else.
Coming back to the debug log attached by you. As it appears, the config file read by your node is bitcoin.conf (present at the data directory) and the options present in there are rpcpassword=****, rpcuser=****, server="1" and txindex="1", none of which are relevant to the options dialogue box. Also, no options were passed as command-line arguments.
If you had added any options (in config file or as command-line arguments) relevant to that dialogue box, they would have been listed instead of none.
I'll write an experiment that might clear the doubt further.

Add par=-1 to bitcoin.conf file (located at D:\bitcoin\bitcoin.conf)
run src/qt/bitcoin-qt -printtoconsole -par=1 -upnp -server=1 -rpcuser=x (Dont worry! All of these are safe options and wont affect any functioning)
Open the dialogue box : Settings > Options

You'll notice, although you added par=-1 in your config file, it shows -par=1 on the dialogue box. It is because the command-line argument overrides the option value added in the config file.
You will also notice there are only two options (-par=1 and -upnp) out of the four options you added as command-line arguments because only those two are relevant to that dialogue box.
I hope this clears out your doubt.  Attaching Screenshots for your reference.

No option in bitcoin.conf,  No Command-Line arg
-par=-1 option in bitcoin.conf, No Command-Line arg
par=-1 option in bitcoin.conf,-par=1 -upnp -server=1 -rpcuser=x as Command-Line args

Do let me know in case of any further query :)

@asifshiraz
Could this issue be closed?

Closing for now.

Hi
I am need to sate
On Wed, 11 Aug 2021 at 22:38, Hennadii Stepanov @.***>
wrote:

Closing for now.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bitcoin-core/gui/issues/388#issuecomment-897098752,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHV67JXLFO5DTFHZFU4ATILT4LGVHANCNFSM5BE3FXJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


Disable default python kernel

This disables the default python kernel in jupyter-lab, jupyter-notebook, and jupyter-nbclassic.

The MacOS tests are not passing, due to the tests of some component of Jupyter not working.

The setup upterm task has been running for 3 hours already.

The flake checks currently fail with
error: input 'jupyterWith/ihaskell/hls/pre-commit-hooks/flake-utils' follows a non-existent input 'hls/flake-utils'

According to this thread, it happens when one of the flake input uses the "follows" attribute. Among the chain of inputs, only ihaskell used to use this "follows" directive in its flake inputs, but this is now solved.
When running the flake checks locally, everything runs fine. I suspect cachix uses some cached version of jupyterWith, or iHaskell, that precedes the fix introduced in iHaskell that is linked above. I'm not familiar with cachix, so I'm not sure how to fix that at the moment.

Just run nix flake lock --update-input ihaskell  to fix the flake issue.

@GTrunSec, Thanks for the suggestion. I gave it a try but that still doesn't pass. Even without updating the lockfile, iHaskell is recent enough, and running nix flake lock --override-input jupyterWith ../.. locally works fine too.

How about cd example/flake then nix flake update? if it does not work again, I will add the follows for the ihaskell input.

That worked, thanks a lot @GTrunSec.
For some reason, the flake checks failed with nix 2.6, while they passed with nix 2.5. Updating the lockfile in example/flake made them pass with nix 2.6 as well.

That's great, thanks!


Strange time formatting

Any idea why khal displays times in my case like this:
10 =30-11 =30: Event Name

?

Can you post your khal.conf, please?

Closed…Pebcak-problem
I had to change my khal.conf and did it with a mass-replacement and with that ":" got changed to " =", thus the strange formatting. m)
Sorry for the inconvenience


Implement YAML serialization (#4)

I added an implementation of YAML serialization, wrote test cases and documentation. I used Jason's already implemented serializer as a basis, since YAML is very similar to it and is a more advanced format.
I suspect that not all cases were covered by tests, so I will add to the pull request as bugs are found and fixed.

Pull request checklist

[ ] Did you bump the project version?
Not yet
[x] Did you add a description to the Pull Request?
[x] Did you add new tests?
[x] Did you add reviewers?

Thank you for contributing your PR! However, during testing I discovered some problems.
Firstly, you use structures in your tests (Foo, Foo2 etc.) whose names coincide with the names of structures from tests for deserialization from deser.jl. This results in errors like this:
Got exception outside of a @test
  invalid redefinition of constant Main.Foo2
  Stacktrace:
    [1] macro expansion
      @ ~/.julia/dev/Serde/test/deser.jl:40 [inlined]
    [2] macro expansion
      @ ~/.julia/juliaup/julia-1.10.0+0.x64.linux.gnu/share/julia/stdlib/v1.10/Test/src/Test.jl:1577 [inlined]
    [3] macro expansion
      @ ~/.julia/dev/Serde/test/deser.jl:40 [inlined]
    [4] macro expansion
      @ ~/.julia/juliaup/julia-1.10.0+0.x64.linux.gnu/share/julia/stdlib/v1.10/Test/src/Test.jl:1577 [inlined]
    [5] top-level scope
      @ ~/.julia/dev/Serde/test/deser.jl:7
    [6] include(fname::String)
      @ Base.MainInclude ./client.jl:489
    [7] top-level scope
      @ ~/.julia/dev/Serde/test/runtests.jl:10
    [8] include(mod::Module, _path::String)
      @ Base ./Base.jl:495
    [9] exec_options(opts::Base.JLOptions)
      @ Base ./client.jl:318
   [10] _start()
      @ Base ./client.jl:552

This error is also reported by the linter (VSCode in my case).

The test does not create a new scope, you can test this using the following simple example.
using Test

@testset "test_foo1" begin
    struct Foo
        a::Int
    end
end

@testset "test_foo2" begin
    struct Foo
        b::Int
    end
end

x = Foo(1)

I will also give an example from your test:
struct Foo2
    bool::Bool
    number::Float64
    nan::Float64
    inf::Float64
    _missing::Missing
    _nothing::Nothing
end

foo = Foo2(true, 163.163, NaN, Inf, missing, nothing)
println(Serde.to_yaml(foo))

# OUTPUT
bool: true
number: 163.163
nan: null
inf: null
_missing: null
_nothing: null

However, according to the YAML specification, for NaN and Inf it is necessary to use .nan and .inf, and not null, i.e. the result should be as follows:
bool: true
number: 163.163
nan: .nan
inf: .inf
_missing: null
_nothing: null

It's also a problem that you don't put quotes around strings when serializing them. Consider the following example:
julia> foo = Dict("v" => "0x0123")
Dict{String, String} with 1 entry:
  "v" => "0x0123"

julia> Serde.to_yaml(foo) |> println
v: 0x0123

This result corresponds to an integer and is equivalent to the one below:
v: 291

At the same time the expected result:
v: "0x0123"

This problem also occurs when using special characters, as in the example below:
julia> foo = Dict("v" => "\"Hello\"\'")
Dict{String, String} with 1 entry:
  "v" => "\"Hello\"'"

julia> Serde.to_yaml(foo) |> println
v: \"Hello\"'

This result is not equivalent to the expected one:
v: "\"Hello\"'"

An equivalent result to the previous one can be obtained using YAML.jl:
julia> YAML.yaml(foo) |> println
: |-
  "Hello"'

@bountyHntr Thanks for the extensive feedback!
Let's go through the points:

The @testset does not create a new scope, you can test this using the following simple example.

I knew about this, but I completely forgot to run the entire test suite, my bad. Fixed.

for NaN and Inf it is necessary to use .nan and .inf

That's right, I added the missing conditions to the function for numbers.

In addition, when using types for which there are no corresponding ones from the YAML specification (for example, functions), you should just skip them or throw error

This problem covers the package as a whole, so far I have only added exception throwing for the "function" type, but this is clearly not the target solution. It might be worth discussing this in more detail and making it a new issue to develop a general solution.

It's also a problem that you don't put quotes around strings when serializing them

I'm used to constantly seeing lines in Yaml without quotes and it turned out badly for me. I returned it and everything is fine now.

name: "CI - Test Features"
on:
  push:
    branches:
      - main
  workflow_dispatch:

jobs:
  test:
    runs-on: ubuntu-latest
    continue-on-error: true
    strategy:
      matrix:
        features: [
            "anaconda",
            "aws-cli",
            "azure-cli",
            "common-utils",
            "conda",
            "desktop-lite",
            "docker-outside-of-docker",
            "docker-in-docker",
            "dotnet",
            "git",
            "git-lfs",
            "github-cli",
            "go",
            "hugo",
            "java",
            "kubectl-helm-minikube",
            "node",
            "nvidia-cuda",
            "oryx",
            "php",
            "powershell",
            "python",
            "ruby",
            "rust",
            "sshd",
            "terraform",
            "nix",
        ]
        baseImage:
          [
            "ubuntu:focal",
            "ubuntu:jammy",
            "debian:11",
            "debian:12",
            "mcr.microsoft.com/devcontainers/base:ubuntu",
            "mcr.microsoft.com/devcontainers/base:debian",
          ]
    steps:
      - uses: actions/checkout@v3

      - name: "Install latest devcontainer CLI"
        run: npm install -g @devcontainers/cli

      - name: "Generating tests for '${{ matrix.features }}' against '${{ matrix.baseImage }}'"
        run: devcontainer features test  --skip-scenarios -f ${{ matrix.features }} -i ${{ matrix.baseImage }} .

  test-scenarios:
    runs-on: ubuntu-latest
    continue-on-error: true
    strategy:
      matrix:
        features: [
            "anaconda",
            "aws-cli",
            "azure-cli",
            "common-utils",
            "conda",
            "desktop-lite",
            "docker-outside-of-docker",
            "docker-in-docker",
            "dotnet",
            "git",
            "git-lfs",
            "github-cli",
            "go",
            "hugo",
            "java",
            "kubectl-helm-minikube",
            "node",
            "nvidia-cuda",
            "oryx",
            "php",
            "powershell",
            "python",
            "ruby",
            "rust",
            "sshd",
            "terraform",
            "nix",
        ]
    steps:
      - uses: actions/checkout@v3

      - name: "Install latest devcontainer CLI"
        run: npm install -g @devcontainers/cli

      - name: "Testing '${{ matrix.features }}' scenarios"
        run: devcontainer features test -f ${{ matrix.features }} --skip-autogenerated  .

  test-global:
    runs-on: ubuntu-latest
    continue-on-error: true
    steps:
      - uses: actions/checkout@v3

      - name: "Install latest devcontainer CLI"
        run: npm install -g @devcontainers/cli

      - name: "Testing global scenarios"
        run: devcontainer features test --global-scenarios-only .

Can you try deserialising and then serialising the above example? It produces a valid yam but It seems that formatting is a bit off. Can you take a look into it?

Can you try deserialising and then serialising the above example? It produces a valid yam but It seems that formatting is a bit off. Can you take a look into it?

@dmitrii-doronin, I understand what you mean. I reconsidered the approach to handling newlines and applied it to the corresponding functions. now the document is serialized pretty :slightly_smiling_face:
I also added a test case for such cases, you can look it up.


external-usermanagement deployment example not working?

The keycloak example configuration doesn't work anymore and needs to be fixed.

I only ran the example for this PR https://github.com/owncloud/ocis-charts/pull/734, but it worked flawlessly for me in Minikube.
@d7oc What's the errors you get?

curl -k https://keycloak.kube.owncloud.test/
Internal Server Error

@d7oc Are all the pods up and running needed for Keycloak? Postgres operator, postgres pods, postgres pooler, ... ?

Yes everything is running:
> k -n keycloak get po
NAME                                 READY   STATUS      RESTARTS   AGE
keycloak-operator-84f7cd995c-xlb5s   1/1     Running     0          5m28s
ocis-keycloak-0                      1/1     Running     0          3m5s
ocis-keycloak-1                      1/1     Running     0          3m23s
ocis-keycloak-2                      1/1     Running     0          3m36s
ocis-realm-hkpmz                     0/1     Completed   0          4m2s
postgres-0                           1/1     Running     0          5m21s
postgres-1                           1/1     Running     0          5m15s
postgres-2                           1/1     Running     0          5m10s
postgres-pooler-54f5fcfd99-6kfml     1/1     Running     0          4m27s
postgres-pooler-54f5fcfd99-j4cf5     1/1     Running     0          4m27s
postgres-pooler-54f5fcfd99-pgppm     1/1     Running     0          4m27s

There is also no error logged when curl is triggered.
Only non-INFO in the log:
k -n keycloak logs -l app=keycloak | grep -v INFO
2024-09-18 09:46:05,696 WARN  [io.agroal.pool] (agroal-11) Datasource '<default>': FATAL: query_wait_timeout
2024-09-18 09:45:59,696 WARN  [io.agroal.pool] (agroal-11) Datasource '<default>': FATAL: query_wait_timeout

At least from the database I can also connect fine:
root@postgres-0:/home/postgres# psql -h postgres-pooler -U postgres
Password for user postgres:
psql (16.3 (Ubuntu 16.3-1.pgdg22.04+1), server 15.7 (Ubuntu 15.7-1.pgdg22.04+1))
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off)
Type "help" for help.

Also works with a debug container spawned inside the keycloak pod.

This is somehow related to the pooler:
/ # psql -h postgres -U keycloak
Password for user keycloak:
psql (16.3, server 15.7 (Ubuntu 15.7-1.pgdg22.04+1))
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off)
Type "help" for help.

keycloak=# \l
                                                       List of databases
   Name    |  Owner   | Encoding | Locale Provider |   Collate   |    Ctype    | ICU Locale | ICU Rules |   Access privileges
-----------+----------+----------+-----------------+-------------+-------------+------------+-----------+-----------------------
 keycloak  | keycloak | UTF8     | libc            | en_US.utf-8 | en_US.utf-8 |            |           |
 postgres  | postgres | UTF8     | libc            | en_US.utf-8 | en_US.utf-8 |            |           |
 template0 | postgres | UTF8     | libc            | en_US.utf-8 | en_US.utf-8 |            |           | =c/postgres          +
           |          |          |                 |             |             |            |           | postgres=CTc/postgres
 template1 | postgres | UTF8     | libc            | en_US.utf-8 | en_US.utf-8 |            |           | =c/postgres          +
           |          |          |                 |             |             |            |           | postgres=CTc/postgres
(4 rows)

keycloak=#
\q
/ # psql -h postgres-pooler -U keycloak
Password for user keycloak:
psql (16.3, server 15.7 (Ubuntu 15.7-1.pgdg22.04+1))
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off)
Type "help" for help.

keycloak=# \l
<hanging here>

The same works for both hosts if user postgres is used.


Intention and purpose

Might want to write some explanations in the README about what the intention and purpose of this repo is to attract more collaborators.
:+1:

for sure. we have no docs now, and won't make any public announcements until we do


changed path of gradle defined in chrcleci config to kts

Issue

close #666

Overview (Required)

FIxed .circleci/config.yml.  It changed build.gradle to build.gradle.kts.
I tested it with my circleci. It made the following settings APP_BUILD_TYPE=Debug

Links
-circleci build log
Screenshot
Nothing

Thanks!!

Yes, Finally I have solved the issue :) Thanks a lot!


Idea: use Swish instead of ELU?

GCAE uses the exponential linear unit ('ELU') as an activation function. In [1] it is claimed that 'the Swish activation function would be better in all cases [over ELU]'.
I am unsure if you think it would be worth to try out Swish? The improvements in accuracy as shown in [1] are only minor.

[1] Ramachandran, Prajit, Barret Zoph, and Quoc V. Le. "Searching for activation functions." arXiv preprint arXiv:1710.05941 (2017). https://arxiv.org/abs/1710.05941

Thanks for the suggestion!
The layers and their arguments (including activation function) are specified in the model definition file (e.g. models/M1.json).
Since Swish is implemented in tensorflow, it is easy to switch to this for any user who would be interested to try it out, by specifying it in the layer arguments instead of elu.
It's an interesting idea to try it out, we might experiment with it. But we will keep the example model in this respository the one that corresponds to the one in the paper, and leave it to users to try different models and training schemes.


Use proper color space when computing variations in Adaptive Tile Sampler

We're computing variations in linear RGB right now. Using sRGB would already be an improvement I think.

@dictoon  I would like to contribute to this. I am new to this repository as well as open source. It would be great if you could help me get started.

Hi @raviteja469, I'm curious if there's been any progress on this, otherwise I was considering getting started on it now, thanks!


added chroot connector

A new connector for chroot execution.
The code is very much based on the existing connectors namely local and docker.

Thank you for accepting it!


Помогите

Регистратор: homeassistant.util.loop
Источник: util/loop.py:84
Первое сообщение: 10:14:02 (672 сообщений)
Последнее сообщение: 10:14:46
Detected blocking call to open inside the event loop by custom integration 'tuya_local' at custom_components/tuya_local/helpers/device_config.py, line 101: self._config = load_yaml(filename) (offender: /usr/src/homeassistant/homeassistant/util/yaml/loader.py, line 226: with open(fname, encoding="utf-8") as conf_file:), please create a bug report at https://github.com/make-all/tuya-local/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle resp = await handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 83, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware response = await handler(request) File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle result = await handler(request, **request.match_info) File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin return await func(self, request, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 222, in post return await super().post(request, flow_id) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 70, in wrapper return await method(view, request, data, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 122, in post result = await self._flow_mgr.async_configure(flow_id, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 368, in async_configure result = await self._async_configure(flow_id, user_input) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 414, in _async_configure result = await self._async_handle_step( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 517, in _async_handle_step result: _FlowResultT = await getattr(flow, method)(user_input) File "/config/custom_components/tuya_local/config_flow.py", line 50, in async_step_user return await self.async_step_select_type() File "/config/custom_components/tuya_local/config_flow.py", line 88, in async_step_select_type async for type in self.device.async_possible_types(): File "/config/custom_components/tuya_local/device.py", line 355, in async_possible_types for match in possible_matches(cached_state): File "/config/custom_components/tuya_local/helpers/device_config.py", line 982, in possible_matches parsed = TuyaDeviceConfig(cfg) File "/config/custom_components/tuya_local/helpers/device_config.py", line 101, in init self._config = load_yaml(filename)


Fixup ASTER update geometries

Description
Real-world fixes from running the ASTER update geometries workflow. Note that we opened https://github.com/stac-utils/pystac/issues/960 and https://github.com/stac-utils/pystac/issues/958 based on this work.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Manual ingestion on 2023-01-23.
Checklist:

[x] I have performed a self-review
[ ] Changelog has been updated
[ ] Unit tests pass locally (./scripts/test)
[x] Code is linted and styled (./scripts/format)

Thanks for this and opening up those pystac issues.


Update README to include degit

Adds degit which is faster and easier than git clone.
https://github.com/Rich-Harris/degit

Hello @nainardev and thank you for your contribution! I will try this and do some research, will get back to you in a while! :)

@nainardev I moved the documentation for how to setup RMUIF to https://docs.rmuif.com where I included your change.


Fix Structure of the GameObjs

Move the render function into the Objects themselves and add some more functions and variables. It should be more Godot like

done


NJsonSchema will not load in Unity Game Engine

Probably not the highest priority, but figured I'd at least file this since I ran into it.
When trying to load a library that depends on NJsonSchema in Unity 2019.4.1, the following error is thrown:
Unloading broken assembly Assets/Packages/NJsonSchema.10.1.15/lib/net45/NJsonSchema.dll, this assembly can cause crashes in the runtime

Updating to current (10.1.21) does not fix this, and unfortunately Unity isn't super helpful on more detailed errors.
Not exactly sure what it is about NJsonSchema's DLL (using the nuget package) that causes this. May dig around myself and will update bug if I find anything.

Oops, nevermind. This seems to be just an issue with the NuGet package, and those in general don't play well with Unity. Packaging by hand into a new style Unity package (https://docs.unity3d.com/Manual/CustomPackages.html) works fine. Closing.


Fixing Portuguese error in README

CHANGELOG :memo:

Fixing a small error in the description of the "Database Relations" challenge.

Approved.
Thank you for your contribution, @gfgabrielfranca! 🚀


Fix indent in the SPDX identifier

Change tab indents to spaces in the SPDX identifier.
Resolves #1083
Signed-off-by: Juyeong Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #1137. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnstreamer.mooo.com/.

:octocat: cibot: @JuYeong0413, test/unittest/unittest_nntrainer_lazy_tensor.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @JuYeong0413, Applications/SimpleShot/test/simpleshot_utils_test.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @JuYeong0413, test/unittest/unittest_nntrainer_lazy_tensor.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @JuYeong0413, Applications/SimpleShot/test/simpleshot_utils_test.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @JuYeong0413, test/unittest/unittest_nntrainer_lazy_tensor.cpp does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @JuYeong0413, Applications/SimpleShot/test/simpleshot_utils_test.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.


installing sizeup and other apps that require accessibility access

Description of issue
[insert a detailed description of your issue here]
Output of `brew cask alfred or sizeup --verbose`
brew cask install alfred --verbose
==> Downloading https://cachefly.alfredapp.com/Alfred_3.1.1_737.zip
/usr/bin/curl --fail --remote-time --location --user-agent Homebrew/>1.0.0 (no git repository) (Macintosh; Intel macOS 10.12) curl/7.49.1 https://cachefly.alfredapp.com/Alfred_3.1.1_737.zip -C 0 -o /Users/lanopuljic/Library/Caches/Homebrew/Cask/alfred--3.1.1_737.zip.incomplete
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2894k  100 2894k    0     0  1577k      0  0:00:01  0:00:01 --:--:-- 1577k
==> Verifying checksum for Cask alfred
==> It seems there is already an App at '/Applications/Alfred 3.app'; not moving.
==> Enabling accessibility access
Password:
==> Error: attempt to write a readonly database
Error: Command failed to execute!

==> Failed command:
["/usr/bin/sudo", "-E", "--", "/usr/bin/sqlite3", "#<Pathname:/Library/Application Support/com.apple.TCC/TCC.db>", "INSERT OR REPLACE INTO access VALUES('kTCCServiceAccessibility','com.runningwithcrayons.Alfred-3',0,1,1,NULL,NULL);"]

==> Standard Output of failed command:

==> Standard Error of failed command:
Error: attempt to write a readonly database

==> Exit status of failed command:
#<Process::Status: pid 11756 exit 8>
Error: Kernel.exit

brew cask install sizeup --verbose
==> Downloading https://www.irradiatedsoftware.com/downloads/SizeUp_1.7.1.zip
/usr/bin/curl --fail --remote-time --location --user-agent Homebrew/>1.0.0 (no git repository) (Macintosh; Intel macOS 10.12) curl/7.49.1 https://www.irradiatedsoftware.com/downloads/SizeUp_1.7.1.zip -C 0 -o /Users/lanopuljic/Library/Caches/Homebrew/Cask/sizeup--1.7.1.zip.incomplete
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2949k  100 2949k    0     0   323k      0  0:00:09  0:00:09 --:--:--  539k
==> Verifying checksum for Cask sizeup
==> Moving App 'SizeUp.app' to '/Applications/SizeUp.app'
==> Enabling accessibility access
==> Error: attempt to write a readonly database
Error: Command failed to execute!

==> Failed command:
["/usr/bin/sudo", "-E", "--", "/usr/bin/sqlite3", "#<Pathname:/Library/Application Support/com.apple.TCC/TCC.db>", "INSERT OR REPLACE INTO access VALUES('kTCCServiceAccessibility','com.irradiatedsoftware.SizeUp',0,1,1,NULL,NULL);"]

==> Standard Output of failed command:

==> Standard Error of failed command:
Error: attempt to write a readonly database

==> Exit status of failed command:
#<Process::Status: pid 13447 exit 8>

Output of `brew doctor`
brew doctor
Your system is ready to brew.


[Refactoring] Disable availability checking to reduce errors

https://github.com/apple/swift/pull/38510 introduces a new error for concurrency not being available, so every async function will cause an error: concurrency is only available in macOS 12.0.0 or newer if on an older platform.
We don't care about availability in swift-refactor, so just disable it to reduce the error spam when a test fails.

@swift-ci please test


Use formatKeyName function instead of explicit replace methods

This partially resolves the sorting issue from yeatmanlab/AFQ-Browser PR 209 by using the afqb.global.formatKeyName function to standardize subjectID and other key names.

@richford Changes look good, merging now.


PPLRW ~1000 times faster on average maybe cause spinlock？

Hello opa334, the version 1.0.5 is very stable on my phone. After I compiled the latest develop branch (commit: https://github.com/opa334/Dopamine/commit/8b01e1e9584ebf92106d960d91caeca73c0bd6c9), the performance has improved significantly, but the stability has noticeably decreased, with problems related to spinlock. Is it possible that this problem is related to the code related to ppl or fork fix?

but i can confirm after 1.0.5, spinlock seems appear.

I've been spinlocking since alpha builds its not caused by 1.0.5 specifically but maybe it is. It seems to be random. I'm going on back to back 11 day runs. 11 is my current record

I used version 1.0.5 of uptime to record 8 days. However, since I switched to the alpha version after 1.0.5, I can only last up to 24 hours at most, and even the spinlock situation occurred within 2 hours. Currently, I am running the latest alpha version based on the current time, and it has been running for 22 hours.

I also had a random spin lock after updating the PPLRW version 1000 times faster. The previous version 1.0.5 with opa334 did not have this issue

I also had a random spin lock after updating the PPLRW version 1000 times faster. The previous version 1.0.5 with opa334 did not have this issue

I also had a random spin lock after updating the PPLRW version 1000 times faster. The previous version 1.0.5 with opa334 did not have this issue.

Had around 20 days of uptime on 1.0.5, restarted and updated this morning and have panicked 3 times so far today

Had around 20 days of uptime on 1.0.5, restarted and updated this morning and have panicked 3 times so far today

Yes, I have a few friends who are using the latest 1.1 version and have also experienced reboot issues within a few hours.

compiled https://github.com/opa334/Dopamine/commit/8b01e1e9584ebf92106d960d91caeca73c0bd6c9 without https://github.com/opa334/Dopamine/commit/067b873b2ff195f80b1ec07bb418a457927c2ee0 looks like very stable. so pplrw maybe is not the cause. uptime 8 hours now. 1.1 only uptime 2 hour for me and some of my friends. @opa334

I don't know if it's related but v1.1 is the first version that I face random reboots. This never happened for my device before 1.1.

I don't know if it's related but v1.1 is the first version that I face random reboots. This never happened for my device before 1.1.

could you help test the 1.0.5-pplrw version？

I don't know if it's related but v1.1 is the first version that I face random reboots. This never happened for my device before 1.1.

could you help test the 1.0.5-pplrw version？

Will do!

I don't know if it's related but v1.1 is the first version that I face random reboots. This never happened for my device before 1.1.

could you help test the 1.0.5-pplrw version？

Figured I would give this a try since I've had reboot issues (within the same day) since the first version. With version 1.1 I can get upwards of a day before a reboot (most of the time PSOD), and testing out the 1.0.5-pplrw, I only got around 8 hours of uptime.
My issue may be somewhat different as I've never had good uptime. Only one tweak installed Pods2Grant but has also been tested without any tweaks installed.

the pplrw solution in that commit is almost 1:1 identical to the one that's in 1.1, I only removed some parts of the code that would never be hit to begin with

the pplrw solution in that commit is almost 1:1 identical to the one that's in 1.1, I only removed some parts of the code that would never be hit to begin with

I can confirm at least for my device (iPhone XS Max, iOS 15.1.1) the pplrw makes no change to random reboots! v1.0 was zero reboots for me. Both 1.2 and 1.05 pplrw cause reboots

the pplrw solution in that commit is almost 1:1 identical to the one that's in 1.1, I only removed some parts of the code that would never be hit to begin with

I can confirm at least for my device (iPhone XS Max, iOS 15.1.1) the pplrw makes no change to random reboots! v1.0 was zero reboots for me. Both 1.1 and 1.05 pplrw cause reboots

There was no public 1.0 release?
Is there something else we can be doing to troubleshoot the reboots - Providing panic logs, etc?

the pplrw solution in that commit is almost 1:1 identical to the one that's in 1.1, I only removed some parts of the code that would never be hit to begin with

But 1.05-pplrw has been running for 3 days and 4 hours on my end (15.1, 13mini ), so this is very strange.
if it reboot, i'm going to use another version contain https://github.com/opa334/Dopamine/commit/067b873b2ff195f80b1ec07bb418a457927c2ee0

int kalloc(uint64_t *addr, uint64_t size)
{
uint64_t kalloc_data_external = bootInfo_getSlidUInt64(@"kalloc_data_external");
uint64_t allocation = kcall(kalloc_data_external, 2, (uint64_t[]){size, 1});
if (allocation != 0) {
if (addr) *addr = allocation;
return 0;
}
//  *addr = ? ;   If memory allocation fails, and the variable "addr" is not assigned any value. Will this have any impact here?
return 1;
}

the pplrw solution in that commit is almost 1:1 identical to the one that's in 1.1, I only removed some parts of the code that would never be hit to begin with

I can confirm at least for my device (iPhone XS Max, iOS 15.1.1) the pplrw makes no change to random reboots! v1.0 was zero reboots for me. Both 1.1 and 1.05 pplrw cause reboots

That's going to be coincedence because nothing that could have introduced these spinlock panics was added in 1.0 - 1.0.5 and also spinlock panics where happening for some people on private betas even.

the pplrw solution in that commit is almost 1:1 identical to the one that's in 1.1, I only removed some parts of the code that would never be hit to begin with

I can confirm at least for my device (iPhone XS Max, iOS 15.1.1) the pplrw makes no change to random reboots! v1.0 was zero reboots for me. Both 1.1 and 1.05 pplrw cause reboots

That's going to be coincedence because nothing that could have introduced these spinlock panics was added in 1.0 - 1.0.5 and also spinlock panics where happening for some people on private betas even.

in 1.1, If calling the kcall method returns equals to 0, then addr will not be assigned. Before refactoring the code, addr will be assigned to the 0  from kcall.

the pplrw solution in that commit is almost 1:1 identical to the one that's in 1.1, I only removed some parts of the code that would never be hit to begin with

I can confirm at least for my device (iPhone XS Max, iOS 15.1.1) the pplrw makes no change to random reboots! v1.0 was zero reboots for me. Both 1.1 and 1.05 pplrw cause reboots

That's going to be coincedence because nothing that could have introduced these spinlock panics was added in 1.0 - 1.0.5 and also spinlock panics where happening for some people on private betas even.

in 1.1, If calling the kcall method returns equals to 0, then addr will not be assigned. Before refactoring the code, addr will be assigned to the 0 from kcall.

what specifically are you refering to? please send me the line of code

https://github.com/opa334/Dopamine/blob/23ae3723f8c4812d05ac3ad83aa03db53e855359/BaseBin/libjailbreak/src/util.m#L60

https://github.com/opa334/Dopamine/blob/23ae3723f8c4812d05ac3ad83aa03db53e855359/BaseBin/libjailbreak/src/util.m#L60

Yeah but the return value takes care of that, you can't expect it to null out addr if it fails

kalloc

*addr = 0;  // add this line
return 1;
before return, i set the addr to 0, and 1.1 version works uptime 4.5 days. the origin 1.1 uptime is 3 hours.  if i meet reboot, i will install orig 1.1 to test if it was a accidental event.

While I don't think this should have any impact, I did some testing a while ago and did notice that kalloc sometimes returns 0 on random occasions so maybe it could be a good idea to protect against this

While I don't think this should have any impact, I did some testing a while ago and did notice that kalloc sometimes returns 0 on random occasions so maybe it could be a good idea to protect against this

Although we still don't know what triggers the spinlock, version 1.0.5 simply commits PPLRW, which noticeably increases the likelihood of a spinlock occurring on some devices（15.1，13mini）. Could we refactor PPLRW to maintain high performance while reverting to the stability of version 1.0.5? Or is there a correlation between the probability of a spinlock occurrence and the performance improvement of PPLRW?

13 Pro on 15.1.1 here - No difference
I don't see a correlation, but spinlock panics do not make any sense to begin with, only god knows what causes them.

This has been disproven, forkfix hooking every single process is what made spinlock panics worse.


lncli: incoming and outgoing peer alias in fwdinghistory

Change Description
Adds a peer alias to the ForwardingEvent which is returned by lncli fwdinghistory. Reference: https://github.com/lightningnetwork/lnd/issues/7000.
Steps to Test
Start up Polar and deploy a custom docker image pointing to the changes in this PR, then send a payment through a patched node.
The forwarding history of the patched node shows aliases of a forwarding event returned by lncli fwdinghistory. The lookup can be skipped if --skip_peer_alias_lookup is provided.

Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[ ] Tests covering the positive and negative (error paths) are included.
[ ] Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

[x] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[x] Commits follow the Ideal Git Commit Structure.
[ ] Any new logging statements use an appropriate subsystem and logging level.
[x]  There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our  Contribution Guidelines for further guidance.

@ellemouton @guggero addressed all the issues.

@guggero I added some peer alias checks in the payments test and moved the description of this change to the RPC section of the release notes.

@guggero I've addressed your nits.

This not being opt-in means that it will be slower for all existing callers, and if there is a bug associated with the lookup it will also break all callers who are not even using the data, these aspects argue for being opt-in rather than opt-out

This not being opt-in means that it will be slower for all existing callers, and if there is a bug associated with the lookup it will also break all callers who are not even using the data, these aspects argue for being opt-in rather than opt-out

Yes the performance concern was raised by @guggero before and opt-out was chosen to aid convenience for callers as I believe they are often interested in the peer aliases.
But your points are good - so if we believe that the performance for large event lists is too low and we want to be defensive about the implementation then I can make this feature opt-in.
Does anyone else have an opinion?

@ziggie1984 did you have any thoughts on this?

Adding to my previous response, if performance is not a concern but errors in the lookup are then we could hint the --skip-peer-alias-lookup flag in the error message for users to be aware that they can retry the call and skip this feature.

in that case you could have your cake and eat it too by defaulting to opting in on lncli but then on the API level have it default to off?

That sounds good to me. Will get a PR ready in some time.

That would be great, was having exactly this issue for external programs, which failed due to errors finding the alias and resulting in forking the external program to update the caller. So having it on lncli opt-out and on the api-level opt-in would be great :) thanks for looking into this


netutils/iperf: add more default device name

Summary
netutils/iperf: add more default device name
Impact
N/A
Testing
iperf test

Depends on https://github.com/apache/incubator-nuttx/pull/7626


[SPARK-45237][DOCS] Change the default value of spark.history.store.hybridStore.diskBackend in monitoring.md to ROCKSDB

What changes were proposed in this pull request?
This pr change the default value of spark.history.store.hybridStore.diskBackend in monitoring.md to ROCKSDB
Why are the changes needed?
SPARK-42277 change to use RocksDB for spark.history.store.hybridStore.diskBackend by default, but in monitoring.md, the default value is still set as LEVELDB.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No

cc @dongjoon-hyun FYI
I think this one need to backport to branch-3.4 and branch-3.5

Merged to master/3.5/3.4.


🌱  Added Repo Urls from GitHub marketplace

What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)

[x] PR title follows the guidelines defined in our pull request documentation

What is the current behavior?
What is the new behavior (if this is a feature change)?**

[x] Tests for the changes have been added (for bug fixes/features)

Which issue(s) this PR fixes

Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)

Thanks for the PR. Out of curiosity, are these all of the public GitHub actions? or how was this collected?
I'm going to wait until after the holidays on this. The weekly runs have been slow recently, and I don't want these extra repos to cause us not to finish our runs these next few holiday weeks.

Hey @spencerschrock,
Yes all of them are public repos, I have a script which pull the repo data from here and do some formatting and push it in my forked version and then I did the manual pull request.


File Comparison OS Shell Integration

I'd like to be able to select files from my OS's file manager for comparison, similar to BeyondCompare or other differs.
Selecting the first file, I'd have a right-click menu option "Select first file for comparison", selecting second file I'd have "Compare with the first file". That would open the VS Code's diff view with the two selected files side by side.

I know this can already be done from command line: https://github.com/Microsoft/vscode/issues/1768

My similar feature request was #15081
But it was closed.


ci: Add CI workflow for building fat container

This PR adds a new GitHub Actions workflow to do the client and server tests, and if they pass, then build the fat container image and push to DockerHub.
Test coverage results :test_tube:
:white_circle: Total coverage has not changed
No changes to code coverage between the base branch and the head branch

@mohanarpit, just pushed changes as discussed. There's quite a few insignificant whitespace changes, so you may want to ignore them in the Diff settings.


Add Missing Unlocks to Emagged Lathes and Move Recipes to Protolathe

About the PR

All the autolathe dynamic recipes were moved to the protolathe.
Emagged Protolathe gets

Truncheon
TelescopicShield
HoloprojectorSecurity
WeaponDisabler
WeaponDisablerSMG
PortableRecharger

Emagged Circuit Imprinter gets

ShuttleGunSvalinnMachineGunCircuitboard
ShuttleGunPerforatorCircuitboard
ShuttleGunFriendshipCircuitboard
ShuttleGunDusterCircuitboard

Why / Balance

These are all the security recipes that were missing from the emagged recipe lists. There doesn't seem to be any particular reason these recipes shouldn't be accessible via emagging when everything else is.
The original PR for ship guns gave the autolathe emag access to the power cages, but they forgot to add in a way to get emag access to the ship guns themselves so I moved it to the circuit imprinter.
I moved all the autolathe dynamic unlocks over to the protolathe since autolathes are meant for non-research crafting and the protolathe is meant for research gated crafting.
Technical details

yml stuff
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: The emagged protolathe can now print disablers, truncheons, and the new T3 portable recharger.
add: The emagged circuit printer can now print ship guns.
tweak: Autolathe emagged recipes that are research gated have been moved over to the protolathe.

I've never really interacted with protolathes before so I have no idea how "in flavor" it is to have the truncheon and telescopic shield in its recipe list.
If it can print laser guns, it might as well as be able to print disablers as well.

Even syndies can print disabler pistols now while sec still can't. 😭

Even syndies can print disabler pistols now while sec still can't. 😭

Sec can do it. I was the one to patch it in.

I have been informed on what the actual intended purpose of autolathes/protolathes are
namely that autolathes are for things that are unlocked immediately (no dynamic recipes) and the protolathe is for stuff that is unlocked through research (mainly dynamic recipes)
so I'll do a follow up PR moving all the autolathe dynamic emag recipes over to the protolathe

There doesn't seem to be any particular reason these recipes shouldn't be accessible

I have some pretty major balance concerns about giving syndicate members trivial methods of obtaining stun equipment. Truncheons, disablers, and disabler SMGs were formerly completely limited to sec. This made acquiring one require engaging with sec directly.
With these changes, emags become even more powerful as a way of obtaining stun equipment to use against sec and crew.

if i could give my 2 cents on this, while i do agree about disablers the truncheon in practice is mainly used to crit wounded suspects that have been harmed from bullets or lasers due to the high damage of each hit. I personally, have never stunned anyone with the truncheon because they have always gone crit before hand
What i suggest is that the disablers are removed but not the truncheons and we see if its broken and abused or if its actually ok.

think this is fine with no disablers


No obvious way to specify Fortran compiler

Currently we have to rely on a big pile of magic rather than simply specifying which one.

I'm working on this.


sACN and/or Art-Net Listener Client

What feature would you like to see added to TallyArbiter?
It would be nice to have a listener client that can turn on fixtures when a Device is in pvw or pgm. It would need to be configured similar to the relay and gpo clients.

May I suggest to use https://github.com/node-dmx/dmx-ts as the DMX library? It supports many different (even USB) interfaces.

Love this, it would allow us to have a singular client configurable for any type of dmx network.


Bug: hotplug block/net devices execeed pciBridgeMaxCapacity lack of rollback operations

Description of problem
Since const pciBridgeMaxCapacity = 30 which define the max pci slots can be used by pci deivces.
If we start 30 container in the same pod which will consume all the pci slots(every container's rootfs is a dm block device, it will consume 1 pci slot), then start 31th container in the pod, it will
fail becase no pci slot is available.
However if we stop the 30th container(it will release 1 pci slot), then start 31th container again, it still fail to start. Because kata-runtime don't rollback the inserted block device when 31th container first time start.
produce the problem
// start 30 containers in the same pod
....

// start 31the container get the error
docker run -itd --name=testContainer_31 --runtime kata-runtime ....
docker-origin: Error response from daemon: OCI runtime create failed: no more bridge slots available: unknown.

// stop 30th container
docker stop testContainer_30

// start testContainer_31 again
docker start testContainer_30
Error response from daemon: OCI runtime create failed: QMP command failed: Duplicate node name: unknown

Expected result
start 31th container successful at 2nd time.
Actual result
start 31th econtainer failed at 2nd time.

/cc @devimc

I will submit a PR to fix this problem later.


WIP: Custom scrollbar proto for dropdown

This PR adds Dropdown to the custom scrollbar prototypes.
TODO: border and shadow is not applied

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS

wrong approach and wrong merge. closing the PR as there is a replacement: https://github.com/microsoft/fluent-ui-react/pull/2092


dsCompositeIn: Handle L3 for new API dsCompositeInRegisterVideoModeUpdateCB

New API added in dsCompositeIn dsCompositeInRegisterVideoModeUpdateCB
Handle the L3 testcase for the same and also update the spec doc

merged to develop


Garbage Collector issue on Finalizers

Hi!
I am using CarouselViewControl with FFImageLoading.
Sometimes, when I scroll fast through the pages (there are also more than 1000 pages), the application deadlocks in GC.WaitForPendingFinalizers method called from inside FF library.
I use a Cancellation token to cancel the loading of the pages to make the app faster.
Any idea?

Could you test the newest prerelease? (<IP_ADDRESS>8)


Use attribute for region if not in ec2

Did you want to keep this separate from #115 or close that one in favor of this PR? Would love to see this get merged so I can unpin my much older cookbook. :+1:

This is a squashed version of #115.  I'll close it.

I, and others, would love to see this in milestone:2.7.2.

Thanks! I've tagged for the 2.8.0 release, which will include enhancements and features. 2.7.2 has been released already.
Side note: I think we definitely need to take a stab at adding spec testing to this cookbook, as this has lagged behind due to the remote API complexity, but the newer SDK has some nice stubbing/mocking abilities that should prove worthwhile.

I have a question on this...
If we are deploying instances say in us-west-1 but my s3 bucket is in us-west-2 will it screw up all of the outher uses of this cookbook by having this attribute set??? I would sure prefer just to have a variable that I set in the aws_s3_file LWRP for that particular file???
Or will this not be an issue??

@joshzitting Good point, that solution is being proposed in #149 so I am wondering if we need to merge these solutions together.
Have an attribute default that the LWRP defaults to, but allow for it to be changed with the LWRP defined resource. Otherwise I am in favor of merging #149 first then changing this solution to add that.

+1 @joshzitting  @martinisoft ... fits exactly the way I use this resource

do we know which version of the cookbook introduced this?  2.5.0 seems to be ok, 2.7.2 has this bug.

@rojomisin Version 2.6.0 is where they changed the gem which caused the break.

As a new user kicking the tires on this cookbook on a local vagrant instance before moving to AWS, hitting the dependency on the instance metadata under the 2.7.x branches is a rude bump. Would dearly love to see this merged and a release cut to supermarket. Thanks!

@tas50 I'm a :+1: on this.


building debian dockerfile has problems

Hello,
The key has expired in this line:
RUN apt-key adv --keyserver keys.gnupg.net --recv-keys 9E3E53F19C7DE460

https://github.com/aptly-dev/aptly/issues/717 has the new key:
RUN apt-key adv --keyserver keys.gnupg.net --recv-keys ED75B5A4483DA07C

Also the Aptly Bash completions fails.  I didn't bother debugging and just commented it out to continue.
converted 'https://github.com/smira/aptly/raw/master/bash_completion.d/aptly' (ANSI_X3.4-1968) -> 'https://github.com/smira/aptly/raw/master/bash_completion.d/aptly' (UTF-8)
--2020-07-18 02:52:16--  https://github.com/smira/aptly/raw/master/bash_completion.d/aptly
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/smira/aptly-fork/raw/master/bash_completion.d/aptly [following]
converted 'https://github.com/smira/aptly-fork/raw/master/bash_completion.d/aptly' (ANSI_X3.4-1968) -> 'https://github.com/smira/aptly-fork/raw/master/bash_completion.d/aptly' (UTF-8)
--2020-07-18 02:52:16--  https://github.com/smira/aptly-fork/raw/master/bash_completion.d/aptly
Reusing existing connection to github.com:443.
HTTP request sent, awaiting response... 404 Not Found
2020-07-18 02:52:16 ERROR 404: Not Found.

FYI, apparently a lot of the forked repos already have been fixing this and other issues.

Hi @m-fonseca, thanks for pointing out these issues. I just merged some changes to address these issues and hopefully this repo is still useful to those who find it: https://github.com/bryanhong/docker-aptly/pull/6


Feature/enable jdbc options

This fixes #76

@morazow : that was fast 👍 yeah I fixed the exception messages.
Thanks again sending the patch! We can release quick new version soon.
Best


Please consider to remove some print statements from the source code

Is your feature request related to a problem? Please describe.
When rendering the image at any time it prints "loaded image" into my terminal. If you could at least add a toggle to enable/disable such print statements within the widget with the default being no printing that would be awesome.
Additional context
Here is some code to reproduce the printing:
QrImageView(
  errorCorrectionLevel: 3,
  data: 'https://www.shuttleuteam.com',
  version: QrVersions.auto,
  size: MediaQuery.of(context).size.width * .8,
  embeddedImage: const AssetImage('assets/Images/marker.png'),
  foregroundColor: WidgetsBinding.instance.platformDispatcher.platformBrightness == Brightness.light ? Colors.black : Colors.white,
  backgroundColor: Theme.of(context).cardColor,
),

#157

Lol, this print still there after many versions published🤣


Channel Not working

Why is it that all channels display even when you specify just the one you need, Is it something that can be fixed? e.g I only want Card and Bank transfer but I still, see all the other ones.

This is an issue with Paystack and to result it you'll have to goto your dashboard to uncheck the changes you don't want.


Extra spaces after the opening dashes of the frontmatter trigger the TOC plugin to interpret them as h2

I initialize a bare project with lume init, then create this simple markdown file. Notice there is a space after the first 3 dashes:
---
key: value
---
Body text

The result:
<!DOCTYPE html>

key: value

Body text

If there isn't any space, then the result will be:
<!DOCTYPE html>

Body text

This bug is from Deno's std/front-matter package that returns the front matter as invalid due this space. I've created an issue: https://github.com/denoland/std/issues/5673

The bug has been fixed, I can close this.


modify the toString() method in the eventmesh-common component, make it more easy to read in human read type

modify the toString() method in the eventmesh-common component, make it more easy to read in human read type
HeartBeatInfo{serviceId=serviceIdinstanceId=110topicList=[topic1, topic2]}
to
HeartBeatInfo{serviceId='serviceId', instanceId='110', topicList=[topic1, topic2]}
modify some comment

good job


Crash when swiping left on the last screen

When the user is swiping left on the last screen, the method scrollViewDidScroll:  in PVOnboardView crashes when retrieving the nextPageView. you might have to swipe left on the last page until the last page is half across the screen.

@ecspress Thanks!


Documentation RegEx gets interrupted by the # character.

Markdown file:

Documentation viewer

The character should be escaped from the regular expression

it should indeed


Add a method to ServiceContext to delete APIToken objects

Needed for logout pages.

This should be done in a UserContext by the user itself.
with mydata.get_context(user=my_user) as c:
    api_token = c.api_tokens.retrieve(Token.token==token)[0]
    c.api_tokens.delete(api_token)


Optional parameters for distance rounding

The current implementation always rounds the distances to the nearest integer. It might be helpful for the non-integral instances to allow for different rounding functions.
Related issue: #7

I will not add support for this right now. This should be done by users themselves.


Make tests more descriptive

Blync Deploy!
The following files were not deployed

courses/ruby-primer/01-level-getting-started/03-method-arguments/spec.rb - courses/ruby-primer/01-level-getting-started/03-method-arguments/spec.rb file contains no meta data


Halo online black texture issue

Please describe your issue as accurately as possible.
If you use Windows, please check the following page: https://github.com/doitsujin/dxvk/wiki/Windows
Software information
Halo Online Ms23 (Using the Eldewrito Mods)
Everything is on High except for Shadow Quality (low) , and Motion blur is off
Some part of the game texture and weapon scope are black.
One of my friend play with dxvk and he has encountered these issue too hes using an Intel Arc GPU
System information

GPU: RX 570 4GB RED Dragon
Driver: Amernimezone custom driver 23.4.2 ( Issue also appear on AMD Official Driver )
Windows Version : W10 Pro 21H2
DXVK version: 2.2

Apitrace file(s)
Last Resort : https://drive.google.com/file/d/1GaTeAk2k_rhUsxC-ci6b4kAI2aKyP9gL/view?usp=share_link
Edge : https://drive.google.com/file/d/1yevOuJKd-mUyDoaqWw08x6HPOr1RNwRR/view?usp=share_link
Narrows : https://drive.google.com/file/d/14VxvO6iEu8S8t4FvNbhUobarNbycOYbl/view?usp=share_link
Last Resort Skyboxes water are black

Edge Grass are black

Narrows Floor are black

@Minelelol Hello and thank you for the issue. Can you verify that the issue goes away ingame when you make a file called dxvk.conf next to the exe (or where ever the logs appear) and insert d3d9.floatEmulation = Strict ?

Dang nice it did fixed the issue

thank you so much<3
is there a link that shows all of dxvk config commands that would be nice

yep, I guess there no reason to keep this issue open I assumed

The above PR will close it when merged. Might as well set the config for the exe internally in dxvk.


Asset Integrations: Update Wormhole asset pricing

What is the purpose of the change
Update Wormhole asset pricing; should use the larger spread pools over the lower spread pools

Brief Changelog
-Updates the pool id number for wormhole assets in price.ts
-Replaces the USDT image, since the main one was the wrong size:

Testing and Verifying
This change has been tested locally by rebuilding the website and verified content and links are expected

@JeremyParish69 is there an explicit reason it's a draft?

@JeremyParish69 is there an explicit reason it's a draft?

Yes, I always submit as a draft until I've been able to validate. In this particular case, it turns out I forgot to update the usdt image reference and discovered this bug upon validation:


[Balance suggestion] MM axes are too weak as weapons

When used for combat or butchering, the vanilla axes are pretty balanced (not counting enchantments), but the axes from mythic metals feel much weaker. For example, why should a steel axe only deal 7.5 attack damage when an iron axe deals 9 (assuming the same attack speed)?
Proposed solution: increase all axes' attack damage by 1.5

Hey, sorry for the long time without a response. You have not been ignored! Generally this question has brewed on my mind the last few weeks, and after consideration I do agree that the axes need some changes.
The reasoning behind the original axe damage values are because they are not strictly balanced around vanilla - They are only balanced around the high tier axes (diamond & netherite), since it is my belief that the other axes are NOT balanced. I mean come on, a Stone Axe gives you a +4 damage increase compared to a sword? Ridiculous.
Because of this the lower tier axes suffered, but as of 0.18.0 all axes will have the same treatment across the board (+2 damage over its sword). I believe this is the best approach as all the high-tier axes already have this treatment, and are more than sufficient weapons (for example adamantite, which is designed to be crafted into weapons).
Thank you for opening an issue regarding this. Hopefully you understand why I make the changes this way.


Used wrong flag './patcher.py -p' on a pool master....

Hi, So I accidentally used the wrong option './patcher.py -p' on one of our XenServer pool masters. The patches were applied so I reboot all the hosts in the pool and then realised that only the pool mater had been patched.
If I try to rerun the script on the pool master I get "No Patches Required. System is up to date."  and if I run it on one of the un-patched hosts in the pool the script just waits at "Internal Upload..."
I am manually patching the pool using XenCenter :( and should be finished by Christmas.
I guess this isn't realy a bug ? but for anyone in the situation in the future is there work around ? Can you force patches ?

It's an interesting point for sure. I think, given my lack of a xenserver environment for use/testing, and that we've not seen this issue before now, it's enough of an edge case to be ignored, for now at least. I do feel for you though! I guess the only side option is to break the pool to individual nodes, patch, and re-pool... But that's not necessarily a straightforward option in prod either!


Isolate Request Posting

Implementing the Isolate Request Posting prototype
UI
Home Page
On the home page, there is now a link, titled Submit a request, pointing to a page where an isolate can create a request to be sent to their volunteer.

Request Page
If this link is followed, the isolate is presented with the following page, where they can create tickets for each item/task they are requesting from their volunteer.

Creating Tickets
When the Create Ticket button is pressed, a ticket is created, and added to the request form.

If a ticket cannot be created, an alert is shown to the user:

Deleting Tickets
If the isolate would like to delete a ticket, they can simply click on the Delete Ticket button, and the ticket will be removed from the form.
Example
Before:

After:

If a ticket cannot be deleted, an alert is shown to the user:

Interesting approach. I think the ticket factory pattern might be a bit over-engineered for a prototype but could come in useful later on.

Yeah, the TicketFactory is an investment in the future. The tracking of tickets issued, caching of the template etc. aren't strictly necessary for a prototype.


Overwrite LinearAlgebra.mul!

I wish the behavior of * operation can change upon using this package. Otherwise, one needs to modify the program to let this package to speed up the code.
Example:
https://github.com/TensorBFS/TropicalGEMM.jl/blob/5ed2f0ae3e39e82f25ef75c44615a846ac8a5b8c/src/gemm.jl#L146

Resolved by #9


Remove version: Google.Chrome.Canary version 128.0.6612.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://dl.google.com/release2/chrome/c3xchuwut363fxvzhrryln2auu_128.0.6612.0/128.0.6612.0_chrome_installer.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 912)


Command pallet

Feature Description

Please take a moment to check that your feature hasn't already been suggested.

I looked through the open and closed issues and user the search term "pallet" and didn't find anything
Feature request
It would be nice if Gitea also implement a command pallet as it is a very efficient form of navigation and interacting with a software/website.
Rational

help users to be much more efficient in interacting with Gitea.
Perhaps it would also help with the server load as users don't load multiple pages to navigate but rather use the command pallet to jump to repos and issues with a very minimal Ajax requests to the server.

Use cases

jump between repos/organizations/issues/PRs
quick search in issues/PRs
copy close address of the current repo regardless of which subpage you are
quick commands for issues/PRs (including close, merge, lable, assign, ...)

Implementation examples

Softwares I know and worked with that has command pallet:

Rstudio (Ctrl+Shift+p)
VScode (Ctrl+Shift+p)
Inkscape (?)
Vivaldi (F2)

websites I know and worked with that has command pallet:

Github (Ctrl+k)

Screenshots
No response

FYI, the spelling is palette, but there's no results for that, either.
:+1:  for either a command palette, or slash commands (like in GitLab)

@lingo Thanks for pointing out my mistake. It is now corrected.

We should start small and gradually build it up, I would suggest starting with navigation like github's.
Pressing ctrl-k outside the Add a comment box will show the above screenshot, then backspace will let me navigate upwards


Update RPC docs to note Windows not supported

Description & motivation
I spent some time working to set up VSCode to support a remote compiler using RPC, before discovering that RPC support had been removed for Windows.

Thanks for opening this PR! One small comment, and then this LGTM


[CWS] do not re-query macro store when fetching macro fields

What does this PR do?
This PR makes sure that we don't query the macro store when fetching macro fields and event types. It's important since it allocates, but also because it's useless since the parent callers already call those functions on every macro in the store already.
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Bare bones identity gate

Not sure why coverage is failing.  Seems to be failing at typing_extensions

Coverage passing now.

Automerge cancelled: PR isn't classified as mergeable (I don't understand why).

Automerge cancelled: Spurious failure. Github API requires me to be an admin on the fork repository to merge master into the PR branch. Hit 'Update Branch' for me before trying again.

Automerge cancelled: Spurious failure. Github API requires me to be an admin on the fork repository to merge master into the PR branch. Hit 'Update Branch' for me before trying again.

Automerge cancelled: Merging is blocked (I don't understand why).


Extend /etc/nixos/configuration.nix rather than overwriting it entirely

Is there any reason you wouldn't just extend /etc/nixos/configuration.nix like this:
{
  outputs = { self, nixpkgs }: {
    # replace 'joes-desktop' with your hostname here.
    nixosConfigurations.joes-desktop = nixpkgs.lib.nixosSystem {
      system = "x86_64-linux";
      modules = [ /etc/nixos/configuration.nix ];
    };
  };
}

instead of creating a new configuration entirely?
My thinking is that you could just let the system take care of things like hardware-configuration.nix, and you only overwrite the things you need to which would make it more portable.
I'm just learning nix though and watched your YouTube videos, so I'm not sure if there is some reason not to do this.

You would lose one of the main advantages of nix if you did it that way which is reproducible builds. Your basically relying on there being some config on the machine already.
I would rather have a single repository that i can load onto a machine from install media and just redeploy my machine back to the way it was previously.
Also i think the flake I have setup is pretty portable as I just have to put the machine settings for each system I am managing this way in the flake instead.

Ok, thank you for the information.


Make more parts of the CLI crate public

Is your feature request related to a problem? Please describe.
I'm currently implementing a large system that relies on SQLx for database migrations and resets. It's using clap for the CLI, and I'm planning on merging some SQLx CLI functionality into my CLI.
Currently, the only struct that the CLI create exposes, is the Opt struct, which contains all available subcommands.
The problem I'm facing, is that I don't want to merge the parts of the CLI that are responsible for adding/managing migrations, so I only want to integrate a subset of the commands into my CLI.
I'd propose to make the other Opts, such as the DatabaseOpts and MigrateOpts public as well, so that one can import them into my CLI selectively.
In addition to that, the actual functions that are being called on the DB, when a CLI command is issued, such as the reset/create/setup functions (in the case of the general database operations) may also be made public, as these are very useful in cases such as mine, as one wouldn't have to reimplement their logic which may lead to diverging behavior down the road.
Describe the solution you'd like
Make the command structs, as well as the database operation functions public.
Describe alternatives you've considered
The only alternative i could find is embedding the whole root-level Opt struct into my CLI, but that contains migration management commands, that I don't really want/need in my CLI
I'd be happy to create a PR for that!

Sorry, sqlx-cli is not designed as a library crate. We don't want to have to worry about API stability.
You're free to copy it or take inspiration from it, but we're not interested in exposing its internals.
Database creation/deletion is handled by the MigrateDatabase trait which is implemented by Any: https://github.com/launchbadge/sqlx/blob/c597a225c577a4c50604fd264ab580e0588c0f11/sqlx-core/src/any/migrate.rs#L8


No pop up notifications on ubuntu 18.04

Hi all, I just installed yakyak as a snap on my ubuntu 18.04 system. I do get sound, but no pop-up notification for incoming messages, although activated under YakYak->Settings->View->Pop-Up Notification.

i had the same problem. Updating to v 1.51 fixed this..

I have Yak Yak 1.5.3, but i do not see any notification appearing... should it be visible?  I'm using ubuntu 18.04

I have Yak Yak 1.5.3, but i do not see any notification appearing too.

Same issue in Yak Yak 1.5.4 on Ubuntu 18.04.4


Routing broken in a couple of ways

Hello
I am finding the routing quite brtoken and despite spending several hours trying to fix it I can;t see what is wrong.
If the application is on the root directory the routes seem to end up like this when clicked on.
https://www.unikernel.guru/#!//ResetPassword
If the application is not running from the root directory the routes seem to end up like this when clicking on links:
https://www.example.com/htmlroot/temp/tcomb-spa-example/build/index.html#!/htmlroot/temp/tcomb-spa-example/build/index.html/ResetPassword
Any suggestions as to what is wrong and how I might fix it?
thanks

This seemed to fix it:
//page.start({hashbang: true});
page.base('/htmlroot/temp/tcomb-spa-example/build');


Fonts look super weird

Which operating system does the issue occur on?
Linux
If on linux, are you using X11 or Wayland?
Latest version of wayland, just installed alacritty version 0.2.8
I just updated, rebooted, and logged in. Now fonts in alacritty look like this...?

Let me know what other details you need

See https://github.com/jwilm/alacritty/issues/2102.
I'll try to release a new version asap as soon as sufficient testing is done to make sure no other regression has been introduced.
Sorry for the inconvenience.

Alright no worries :) Thanks for the quick reply!


Creating tests to the "cartolafc.Api.status" method

Coverage increased (+9.3%) to 42.439% when pulling 94ba64f3c190a84942a024123fde734cb001fb9e on dev into 3bb930bc36777880d113995d493bcd01d616b4a4 on master.


MC block references index in history

parent MC block references lookup should be optimized using an additional persistent storage in SC history having entries like this: mcblockId->scblockId

Done. ActiveChain class introduced to keep info about MC block reference data and header info with fast access to the data itself and containing SC block.


Bump required azdata engine version for schema compare

@Charles-Gagnon
@kisantia  pointed out that Schema Compare doesn't really need new ADS to operate, it only needs new ADS (new mssqltools) to show new bug fixes... it will work though without it also.... So leaving it up to you if you want to get this in or not...

Not sure I understand - is there functionality that was added in 1.10 that is required for the extension to operate (API changes and the like)?

There weren't any API changes. The extension just needs the new SqlToolsService changes to get a couple changes that were made in DacFx.

Alright, that still sounds like enough of a reason to bump the required version to ensure that the extension is using the correct version of the sqltoolsservice.


Fix build warnings in snippet gen code

Description:

There are warnings related to the EI build on snippet gen part
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Fixed in https://github.com/wso2/ballerina-integrator/pull/447


React 18 support

Hi, thanks for the great library.
the library only supports<EMAIL_ADDRESS>|| ^17.0.0"
pls also support 18
thanks.

Please make this work!!!

@justin-chu when I install this package it's not giving me the most up to date version of this repo with your react 18 commit.
can you update the npm package as well?

@tr1s Sorry, updated and published now


install via npm

Currently, angular-bootstrap is installable via bower and nuget. Would be great to register package in registry at https://npmjs.org/ to let it be installed via npm install angular-ui-bootstrap

+1
Two arguments:

Blocks usage in enterprise environments using npm integration with Nexus or Artifactory (neither supports Bower).
Many developers are already using npm for client-side package management, and the npm team has stated they'll be focusing efforts on this concern.

I submitted a PR, but it seems the issue is with how angular-ui publishing is handled. See my comments here: https://github.com/angular-ui/bootstrap/pull/3108
I'll file an issue in the publisher repo, and i (or someone else) can hopefully get that up and running asap.

For reference: https://github.com/angular-ui/angular-ui-publisher/issues/3

@ProLoser  I took control over angular-bootstrap on npm and added ProLoser and christopherthielen to the owners list, so now we can have the same name in bower as in npm.

Looks like angular-bootstrap on npm is 0.13.0-SNAPSHOT, even though the package.json lists the version as 0.12.0.

Note to self/maintainers refer to https://github.com/angular/angular.js/pull/10732

We definitely should look to try to tackle this sometime soon.

@wesleycho Added feature for 0.14?

We might want to think about doing this after 0.13.0 is out, and add support for CommonJS.

I agree with Wesley
On Mar 27, 2015 9:42 PM, "Wesley Cho"<EMAIL_ADDRESS>wrote:

We might want to think about doing this after 0.13.0 is out, and add
support for CommonJS.
--
Reply to this email directly or view it on GitHub
https://github.com/angular-ui/bootstrap/issues/1636#issuecomment-87159878
.

All, more than happy to help out tackling this problem if you need more hands.

This is now published to npm.

It's not clear which npm package to install.
angular-ui-bootstrap is out of date and has version 0.13.4
angular-bootstrap is even further behind 0.12.1
Has NPM support been stopped or am I installing the wrong package?

Okay, it's clear what to install now i've found https://github.com/angular-ui/bootstrap-bower
npm install angular-ui-bootstrap has installed the latest version after I deleted the other packages named above..
I, perhaps incorrectly, assumed that npm install angular-ui-bootstrap would update me to the latest version.

@B3nCr, I believe the instructions you are seeking are here.


Editor: Preload media REST API request

Feature Description
Similar to what was done in #2933, we can leverage the same _web_stories_envelope technique to markedly improve perceived performance when opening the editor by preloading requests to the Media REST API endpoint.
Alternatives Considered

Additional Context
Eventually this will be fixed in @wordpress/api-fetch so that we don't have to maintain this _web_stories_envelope logic ourselves anymore. See https://github.com/WordPress/gutenberg/pull/23807

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

When opening the editor, now extra HTTP request is made for the Media Library, as the request is preloaded upon page load.

Implementation Brief

Basically adapt #2933 for media requests.

Duplicate of #3197


fix: NullPointException when statistics query is null

When I used bigquery, I found a null pointer exception. I learned that the project uses JDK8, so I used Optional to rewrite this part of the code to avoid this exception.

Contributor License Agreement (CLA) signed.

Found the same issue in BQForwardOnlyResultSet and BQStatement, so I submitted a new commit

Merged in https://github.com/looker-open-source/bqjdbc/commit/f00d793ab2a344c430830deed85aede60cbf1993. Thank you!


[MATLAB] Bump libmexclass version to commit ca3cea6

Describe the enhancement requested
This is a follow up to #41370.
@sgilmore10 and I recently resolved multiple issues related to mathworks/libmexclass not supporting ARM-based macOS builds (i.e. builds on macos-14).:

https://github.com/mathworks/libmexclass/issues/76
https://github.com/mathworks/libmexclass/issues/77

We should bump the version of mathworks/libmexclass used by the MATLAB interface to the latest available commit (ca3cea6 as of now) in order to enable building the MATLAB interface to Arrow on macos-14 (which is ARM-based).
Component(s)
MATLAB

Issue resolved by pull request 41436
https://github.com/apache/arrow/pull/41436


Ensure to use HTTP 1.1 for presto-cli and presto-jdbc

Problem
We have found the waiting Http2Connection can block the program execution in presto-cli and presto-jdbc. It happens when HTTP 2 is used to communicate between the presto server and client. Although we still need a further investigation to support HTTP 2 by presto, ensuring HTTP 1.1 can be a good intermediate solution for the problem.
Overview

[x] : Ensure to use HTTP 1.1 by presto-cli
[x] : Ensure to use HTTP 1.1 by presto-jdbc

See also : https://github.com/prestosql/presto/issues/1169

@Lewuathe I'm going to close this based on the discussion in #1169 that SocketChannelSocketFactory is the root cause. Please ping me when the PR to disable that on JDK 11+ is ready.

Got it. Thanks!


NT jesus changes: players are jumping around when stop moving

on master (before localtime removal), your NT changes are causing jitter for the last move after stopping.
editor = host on the left.
build = client on the right.
notice how on the left, once it stops moving, it jumps back a little.
https://gyazo.com/19152c7b677b9c37fe086f54b94d8c6a

reverted on master for now

close?


Create sourcegraph.md

On February 22, 2023, Sourcegraph implemented a tax.
This is their email:
Hello,

The Sourcegraph free tier will be changing on February 22, 2023 with the release of Sourcegraph 4.5. Details and an FAQ on the change [can be found here](https://docs.sourcegraph.com/admin/free-tier). Instances upgrading to Sourcegraph 4.5+ will automatically be moved to this new free tier, and instances that stay on version 4.4 or older will not be impacted.

We’ll be making the following changes:

* The maximum number of private repositories synced to each instance will be reduced from unlimited to 1.
* The free tier will no longer support SSO/SAML.

We apologize for any disruption this may cause. If you’re interested in upgrading to a paid version of Sourcegraph, you can [schedule a time with our team here](https://sourcegraph.chilipiper.com/book/me/casi-neff?type=free-tier-upgrade) and we’ll be happy to work with you on a plan that works for you. No action is required on your part if you’d like to stay on the new free tier.

Best,

The Sourcegraph Team

While it sucks that they yanked the feature from the free tier, I don't think it's eligible for sso.tax – SAML is included in their cheapest paid tier, and sso.tax excludes free tiers.
Happy to be corrected if I'm missing something.