bug: lag while typing %s command in cmdline

Did you check docs and existing issues?

[X] I have read all the noice.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of noice.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.0
Operating system/version
MacOS 14.5
Describe the bug
Getting lags while typing %s/some_text/{from_there}
Steps To Reproduce

With noice cmdline

https://github.com/user-attachments/assets/ad593533-16c2-4490-a057-37747dda7ff1

Without it

https://github.com/user-attachments/assets/c4208907-8dfe-478f-8fdb-03242860a654
Expected Behavior
typing without lags
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
"folke/noice.nvim",
  event = "VeryLazy",
  dependencies = { "MunifTanjim/nui.nvim" },
  config = function()
    require("noice").setup({
      lsp = {
        override = {
          ["vim.lsp.util.convert_input_to_markdown_lines"] = true,
          ["vim.lsp.util.stylize_markdown"] = true,
          ["cmp.entry.get_documentation"] = true,
        },
      },
      presets = { command_palette = true, lsp_doc_border = true },
    })
  end,
},
    -- add any other plugins here
  },
})

First of all your videos look pretty much identical to me, so this is already a very minor thing.
Noice needs to do redraws to ensure the cmdline gets rendered. Otherwise you wouldn't see what you're typing.

so it can't be fixed or I do something wrong?
I tried changing the throttle setting and it flashes much less frequently, but I don't think it's solution

All you can try i making sure you're using an up to date nightly.
Nothing much I can do about this. So can't fix,


Finalizers are not retried after exception

Describe the bug
An uncaught exception in a finalizer terminates the operator.
To Reproduce
Implement an operator that registers a finalizer. Throw an exception in the method FinalizeAsync of the corresponding IResourceFinalizer.
Expected behavior
If an event handler in the controller throws an exception, the event is retried a number of times instead of terminating the operator. I would have expected the same for finalizers.
In general, it is advised to implement the cleanup logic in finalizers to be idempotent, to support retries (see here). I.e., the cleanup logic is called again (with some back-off time) until it completes and the finalizer can be removed.

Got this reproduced on the template. All that was necessary, as described, was simply adding a throw new Exception(); in the FinalizeAsync method.
https://github.com/buehler/dotnet-operator-sdk/blob/727a73321afdb3bd2ddb1653da157e58e863ff57/src/KubeOps.Templates/Templates/Operator.CSharp/Finalizer/DemoFinalizer.cs#L18-L23
And I do agree that this is an issue; resource controllers re-queue four times upon exception, and finalizers should behave the same.

There is also no requeueing in the HandleResourceFinalization of ManagedResourceController. Would it be fine to just add a similar block as in https://github.com/buehler/dotnet-operator-sdk/blob/master/src/KubeOps/Operator/Controller/ManagedResourceController{TEntity}.cs#L248 ?

By the way: why is it exactly for retries?

There is also no requeueing in the HandleResourceFinalization of ManagedResourceController. Would it be fine to just add a similar block as in https://github.com/buehler/dotnet-operator-sdk/blob/master/src/KubeOps/Operator/Controller/ManagedResourceController{TEntity}.cs#L248 ?

That's what I'm working on, though it's giving me a bit of grief with propagating exceptions back up the stack to be properly handled.

By the way: why is it exactly four retries?

I know it's a finite number because you don't want to just continually hammer the API server if something's broken. 4 retries means 5 attempts over a span of ~30 seconds depending on how long it takes to fail, and that would usually be enough time for a lot of transient errors to resolve themselves. That was around well before me though, so a better answer may come from Christoph

Bah, all my troubles were because Rider wasn't rebuilding my KubeOps copy that I was changing... that should solve it.
info: KubeOps.Operator.Finalizer.FinalizerManager[0]
      Execute finalizer "demo.kubeops.dev/demofinalizerfinalizer" on entity "DemoEntity/test".
info: TestOperator.Finalizer.DemoFinalizer[0]
      entity test called FinalizeAsync.
fail: KubeOps.Operator.Controller.ManagedResourceController[0]
      Finalize resource "DemoEntity/test" threw an error. Retry attempt 3.
      System.Exception: Blow up the finalizer
         at TestOperator.Finalizer.DemoFinalizer.FinalizeAsync(V1DemoEntity entity) in .../TestOperator/Finalizer/DemoFinalizer.cs:line 23
         at KubeOps.Operator.Finalizer.FinalizerManager`1.<>c__DisplayClass6_1.<<KubeOps-Operator-Finalizer-IFinalizerManager<TEntity>-FinalizeAsync>b__2>d.MoveNext() in .../dotnet-operator-sdk/src/KubeOps/Operator/Finalizer/FinalizerManager{TEntity}.cs:line 82
      --- End of stack trace from previous location ---
         at KubeOps.Operator.Finalizer.FinalizerManager`1.KubeOps.Operator.Finalizer.IFinalizerManager<TEntity>.FinalizeAsync(TEntity entity) in .../dotnet-operator-sdk/src/KubeOps/Operator/Finalizer/FinalizerManager{TEntity}.cs:line 73
         at KubeOps.Operator.Controller.ManagedResourceController`1.HandleResourceFinalization(QueuedEvent data) in .../dotnet-operator-sdk/src/KubeOps/Operator/Controller/ManagedResourceController{TEntity}.cs:line 299
dbug: KubeOps.Operator.Controller.ManagedResourceController[0]
      Retry attempt 3 for event "Finalizing" on resource "DemoEntity/test" with exponential backoff "00:00:08.4030000".

Maybe it be a good idea to make the number of attempts configurable - but that's not urgent and just an idea.

If that would be useful to you, I'd recommend opening up an issue for it. I personally wouldn't use it, so I'm not just going to do the work out of nowhere.
That being said, it doesn't appear that a huge change would be necessary. It should be (more or less) as simple as moving MaxRetries onto the OperatorSettings class and making it not a constant.
https://github.com/buehler/dotnet-operator-sdk/blob/02bb7ecd4309cd26ec4b3cdd60b40584fd633b94/src/KubeOps/Operator/Controller/ManagedResourceController{TEntity}.cs#L20-L23

I have to admit that currently I also don't see an immediate need for it. Sometimes a well-chosen constant is better than a configuration. If it turns out to be useful, I will make an according pull request. Thank you for pointing me to the right place!

That is funny, I thought I do retry finalizer as well... (～￣▽￣)～


[bug] Building release Appimage leads to broken external binary in the package

Describe the bug
When building the app for release with an external binary (this binary was built using pkg) this causes the binary to break only for AppImage works fine it's a deb on macOS & windows.
Reproduction

Download the linux binary from here
Clone this repo: https://github.com/fayeed/test-tauri
Copy that to src-tauri/bins
Run yarn tauri build
The Binary that's copied in src-tauri/target/release/bundle/appimage/test-tauri.AppDir/usr/bin/ad4m when run using ./ad4m serve will throw this error message

pkg/prelude/bootstrap.js:1

���
   �/�$����_��&�"�-���
                      �/�(������[��*�b

SyntaxError: Invalid or unexpected token
    at new Script (node:vm:101:7)
    at readPrelude (node:internal/bootstrap/pkg:29:13)
    at node:internal/bootstrap/pkg:36:18
    at node:internal/bootstrap/pkg:43:4
    at node:internal/bootstrap/pkg:44:2

Expected behavior
Expect the release AppImage binary to work.
Platform and versions
Environment
› OS: Ubuntu 22.04 X64
› Node.js: 16.13.2
› npm: 8.1.2
› pnpm: Not installed!
› yarn: 1.22.15
› rustup: 1.24.3
› rustc: 1.60.0
› cargo: 1.60.0
› Rust toolchain: stable-x86_64-unknown-linux-gnu
Packages
› @tauri-apps/cli [NPM]: 1.0.5
› @tauri-apps/api [NPM]: Not installed!
› tauri [RUST]: 1.0.5,
› tauri-build [RUST]: 1.0.4,
› tao [RUST]: 0.12.2,
› wry [RUST]: 0.19.0,
App
› build-type: bundle
› CSP: unset
› distDir: ../src
› devPath: ../src
App directory structure
├─ node_modules
├─ src
├─ .git
├─ src-tauri
└─ .vscode
Stack trace
No response
Additional context
No response

Running the md5sum command on sidecar.AppDir/usr/bin/app (from the example/sidecar example) shows that the external binary is modified by linuxdeploy AppImage. Even just running the linuxdeploy command without the plugins will result in a broken external binary.
[I] dlangevi@hunger ~/c/t/e/s/s/t/r/b/appimage (dev)> cp ../appimage_deb/data/usr/bin/app sidecar.AppDir/usr/bin/app
[I] dlangevi@hunger ~/c/t/e/s/s/t/r/b/appimage (dev)> md5sum sidecar.AppDir/usr/bin/app
094934b97979cb74257495b39d10c9c7  sidecar.AppDir/usr/bin/app
[I] dlangevi@hunger ~/c/t/e/s/s/t/r/b/appimage (dev)> sidecar.AppDir/usr/bin/app
[2:29:19 PM] new message
[2:29:20 PM] new message
[2:29:20 PM] new message
^C
[I] dlangevi@hunger ~/c/t/e/s/s/t/r/b/appimage (dev)> /home/dlangevi/.cache/tauri/linuxdeploy-x86_64.AppImage --appdir sidecar.AppDir/ > stdout.txt
linuxdeploy version 1-alpha (git commit ID 287c436), GitHub actions build 110 built on 2022-08-17 20:56:20 UTC
[I] dlangevi@hunger ~/c/t/e/s/s/t/r/b/appimage (dev)> md5sum sidecar.AppDir/usr/bin/app
84c73f2b334f8a9ce305e4f4993bc241  sidecar.AppDir/usr/bin/app
[I] dlangevi@hunger ~/c/t/e/s/s/t/r/b/appimage (dev)> sidecar.AppDir/usr/bin/app
pkg/prelude/bootstrap.js:1

SyntaxError: Invalid or unexpected token
    at new Script (vm.js:102:7)
    at readPrelude (internal/bootstrap/pkg.js:29:13)
    at internal/bootstrap/pkg.js:36:18
    at internal/bootstrap/pkg.js:43:4
    at internal/bootstrap/pkg.js:44:2

Any new updates about this bug? it still happens (ffmpeg and ffprobe binaries in my case)


Easy to use fake inmemory for testing

If you're talking about something similar to RavenDB's famous embedded DB, unfortunately that's probably going to have to wait- more info here: https://www.youtube.com/watch?v=2pl_44IREng#t=19m50s

This was originally just to have a pre-built stub for our IDocumentSession. Honestly, after thinking about this, I'm shutting it down as "will not fix." The things that are easy to stub/mock in Marten are easily done w/ any mocking tool and the things that aren't really appropriate to mock have to be integration tests anyway.

Time to re-open? https://www.nuget.org/packages/PostgreSql.Binaries.Lite/
Marten.Embedded for the win!

@jeffdoolittle I've been mulling this one over all weekend. I'm thinking that we go for it.

I think this would be a huge win for the growing Marten community.

I'm opening a new issue for the "embedded option"


phototourism data not optional?

I downloaded the required GL3D part of the training set and ran the training for the first time to generate the matches.
The dataset preparation fails when trying to access the tourism_0001 folder, which is not part of the core training set:
2020-07-02 11:22:54.930044: W Prepare match sets upon request.
 37% (401 of 1073) |#######              | Elapsed Time: 5:26:00 ETA:  11:46:47 50% (542 of 1073) |##########          | Elapsed Time: 6:58:28 ETA:   0:49:24Traceback (most recent call last):
  File "train.py", line 141, in <module>
    tf.compat.v1.app.run()
  File "[...]/tensorflow_core/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "[...]/absl/app.py", line 299, in run
    _run_main(main, args)
  File "[...]/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "train.py", line 132, in main
    regenerate=FLAGS.regenerate, is_training=FLAGS.is_training, data_split=FLAGS.data_split)
  File "[...]/tfmatch/preprocess.py", line 101, in prepare_match_sets
    visualize=False, global_img_list=global_img_list)
  File "[...]/tfmatch/tools/io.py", line 142, in parse_corr_to_match_set
    matches = read_corr(input_corr)
  File "[...]/tfmatch/tools/io.py", line 118, in read_corr
    with open(file_path, 'rb') as fin:
FileNotFoundError: [Errno 2] No such file or directory: '[...]/GL3D/data/tourism_0001/geolabel/corr.bin'
100% (1073 of 1073) |###################| Elapsed Time: 6:58:29 Time:  6:58:29

Is the phototourism data required for training?

I downloaded the required GL3D part of the training set and ran the training for the first time to generate the matches.
The dataset preparation fails when trying to access the tourism_0001 folder, which is not part of the core training set:
2020-07-02 11:22:54.930044: W Prepare match sets upon request.
 37% (401 of 1073) |#######              | Elapsed Time: 5:26:00 ETA:  11:46:47 50% (542 of 1073) |##########          | Elapsed Time: 6:58:28 ETA:   0:49:24Traceback (most recent call last):
  File "train.py", line 141, in <module>
    tf.compat.v1.app.run()
  File "[...]/tensorflow_core/python/platform/app.py", line 40, in run
    _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
  File "[...]/absl/app.py", line 299, in run
    _run_main(main, args)
  File "[...]/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "train.py", line 132, in main
    regenerate=FLAGS.regenerate, is_training=FLAGS.is_training, data_split=FLAGS.data_split)
  File "[...]/tfmatch/preprocess.py", line 101, in prepare_match_sets
    visualize=False, global_img_list=global_img_list)
  File "[...]/tfmatch/tools/io.py", line 142, in parse_corr_to_match_set
    matches = read_corr(input_corr)
  File "[...]/tfmatch/tools/io.py", line 118, in read_corr
    with open(file_path, 'rb') as fin:
FileNotFoundError: [Errno 2] No such file or directory: '[...]/GL3D/data/tourism_0001/geolabel/corr.bin'
100% (1073 of 1073) |###################| Elapsed Time: 6:58:29 Time:  6:58:29

Is the phototourism data required for training?

Hi, I met the same problem, did you solved it?


feat: Add Nuxt Module

Context
Create a nuxt module so we can easily use it with our Nuxt 3 projects. It will make it easier to setup since Nuxt makes it super powerful to auto import and compassables with @nuxt/kit.
Examples
https://github.com/unocss/unocss/tree/main/packages/nuxt
Thanks 💚

Closed via #81
This will be available in the next release.


Fixed breadcrumbs

It would be nice if the breadcrumbs was fixed and did not scroll with the contents, especially if the mouse or touchscreen is used for navigation.

sort of duplicate of https://github.com/bpatrik/pigallery2/issues/27

lets continue there. closing this.


Do something about NA values in Series.value_counts and describe on object arrays

@takluyver, fixed in the above commit-- I think excluding NAs is the right behavior. i amended after I pushed...hopefully the git gods will forgive me

Yes, I think so. I wonder if .describe() should return a len field as well, so you can see at a glance how many NaNs there were.

I'm fairly indifferent about that-- if you think it would be useful it certainly does no harm


SQL ORDER, what am I doing wrong?

Hi, I want to ORDER in alphabetically but none of the codes that I tried work, where and how do I have to put the ORDER to make this thing work?
$data = $database->select("tipos", [
        'id',
        'main_name',
        'slug'
    ], function ($tipos) {
        echo $tipos["nombre"]."<br>\n";
    }
);

The result are id ordered by default instead of the main_name column

Nevermind 😅, it was just add the ["ORDER" => "main_name"] before the function


ghq: Migrate to buildGoModule, ensure go 1.13 compatibility

Motivation for this change
Preparation for #68135 (Go 1.13 compatiblity)
Refs https://github.com/NixOS/nixpkgs/pull/68135#issuecomment-528489365
Things done

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

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

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

Notify maintainers
cc @sigma

@GrahamcOfBorg build ghq

Blocks #68135

@Mic92 - addressed your comment from https://github.com/NixOS/nixpkgs/pull/68135#pullrequestreview-285198103
can you merge this?


Update to later versions of Rust?

For info, this project was completed with a brew-installed rust v1.12.0 on macOS (probably Sierra 10.12.x).
For example, v1.23.0 is out with lots of awesome new stuff 😄
https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1230-2018-01-04

Closing due to inactivity.


Update for Laravel 4.2 -- SoftDeletingTrait

Just a small update for Laravel 4.2, not sure if a separate branch is required or maybe add a config option to select between 4.1-4.2 so different models could be grabbed?
I'll try fiddling with a config option and see where it lands

If you are still interested in a fix for Laravel 4.2 let me know. We just release a version for Laravel 5 with new features.


If a column is created dynamically there is no tooltip

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

If I create the columns dynamically via addColumn there is no any tooltype appearing if I hover the mouse over the cell, except above the first (frozen) column which is a string (the other columns are rendered as 'int'.)
W2ui 1.5

Can you please provide a Fiddle/Bin/Pen to demonstrate the issue?

Grid cells of the added column have a tooltip, just like the other ones: http://jsfiddle.net/m19wuhfL/
Closing issue: cannot reproduce; no response


tests/tools/test_ruff_works.py fails as ruff  was deprecated in ruff 0.3.0

ruff 0.3.0 deprecated ruff <path> in favor of ruff check <path>. See this PR for more info. Because tests/tools/test_ruff_works.py uses ruff <path> the test now fails. The test should be updated to use ruff check <path>.

thanks - want to make a pr?

Found the time to look into it and created a PR.


No cron emails from gantry-cache

This means we don't get alerts about disk failures:
/etc/cron.hourly/drivemonitor: line 13: mail: command not found

@dlebauer Closeable?

Needs to be moved to the other organization at least.


6 high vulnerabilities after install - how I fixed it

I am fresh to npm and node.js which I installed using brew one day ago. I installed it just for pageres but I kept seeing an issue over and over that I could not resolve until I used the --global flag.
Versions
Mac OS High Sierra 10.13.6
npm --version 7.5.0
node --version v15.8.0
npm install --global pageres-cli followed by npm audit fix
The global install fixes my issue in that I can use pageres but why is the package 326MB in size? Is this avoidable somehow. I have a feeling that this question is not for the pageres developers but any guidance would be much obliged. I am reading the npm docs for now but node is new to me. I installed it only for pageres.
➜  npm npm install --global pageres-cli

added 259 packages, and audited 260 packages in 52s

33 packages are looking for funding
  run `npm fund` for details

6 high severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
➜  npm npm audit fix

up to date, audited 1 package in 298ms

found 0 vulnerabilities

This is what kept happening when I did not install globally ( npm install pageres )
➜  npm npm install pageres
((                       )) reify:date-fns: timing reifyNode:node_modules/puppeteer Completed in 1242ms

added 174 packages, and audited 176 packages in 55s

22 packages are looking for funding
  run `npm fund` for details

5 high severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
➜  npm
➜  npm
➜  npm npm audit
# npm audit report

lodash  <=4.17.18
Severity: high
Prototype Pollution - https://npmjs.com/advisories/1065
Prototype Pollution - https://npmjs.com/advisories/1523
Prototype Pollution - https://npmjs.com/advisories/577
Prototype Pollution - https://npmjs.com/advisories/782
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/cheerio/node_modules/lodash
  cheerio  0.14.0 - 0.19.0
  Depends on vulnerable versions of lodash
  node_modules/cheerio
    w3counter  1.0.0 || >=1.2.0
    Depends on vulnerable versions of cheerio
    node_modules/w3counter
      get-res  >=2.0.0
      Depends on vulnerable versions of w3counter
      node_modules/get-res
        pageres  >=4.0.0
        Depends on vulnerable versions of get-res
        node_modules/pageres

5 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force
➜  npm npm audit fix --force
npm WARN using --force Recommended protections disabled.
npm WARN audit Updating pageres to 3.0.2,which is a SemVer major change.
npm WARN deprecated<EMAIL_ADDRESS>Development of this module has been stopped.
npm WARN deprecated<EMAIL_ADDRESS>Please update to ini >=1.3.6 to avoid a prototype pollution issue
npm WARN deprecated<EMAIL_ADDRESS>Please use the native JSON object instead of JSON 3
npm WARN deprecated<EMAIL_ADDRESS>this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>the module is now available as 'css-what'
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>the module is now available as 'css-select'
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! code 1
npm ERR! path /Users/admin/node_modules/phantomjs
npm ERR! command failed
npm ERR! command sh -c node install.js
npm ERR! Downloading http://phantomjs.googlecode.com/files/phantomjs-1.9.2-macosx.zip
npm ERR! Saving to /var/folders/mt/dbxxpsbx661ctykd_48t9w6m0000gn/T/phantomjs/phantomjs-1.9.2-macosx.zip
npm ERR! Receiving...
npm ERR! Error requesting archive
npm ERR! Phantom installation failed Error: Error with http request: {
npm ERR!   'content-type': 'text/html; charset=UTF-8',
npm ERR!   'referrer-policy': 'no-referrer',
npm ERR!   'content-length': '1593',
npm ERR!   date: 'Tue, 16 Feb 2021 23:18:53 GMT',
npm ERR!   connection: 'close'
npm ERR! }
npm ERR!     at ClientRequest.<anonymous> (/Users/admin/node_modules/phantomjs/install.js:227:23)
npm ERR!     at Object.onceWrapper (node:events:485:26)
npm ERR!     at ClientRequest.emit (node:events:378:20)
npm ERR!     at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:636:27)
npm ERR!     at HTTPParser.parserOnHeadersComplete (node:_http_common:129:17)
npm ERR!     at Socket.socketOnData (node:_http_client:502:22)
npm ERR!     at Socket.emit (node:events:378:20)
npm ERR!     at addChunk (node:internal/streams/readable:313:12)
npm ERR!     at readableAddChunk (node:internal/streams/readable:288:9)
npm ERR!     at Socket.Readable.push (node:internal/streams/readable:227:10) Error: Error with http request: {
npm ERR!   'content-type': 'text/html; charset=UTF-8',
npm ERR!   'referrer-policy': 'no-referrer',
npm ERR!   'content-length': '1593',
npm ERR!   date: 'Tue, 16 Feb 2021 23:18:53 GMT',
npm ERR!   connection: 'close'
npm ERR! }
npm ERR!     at ClientRequest.<anonymous> (/Users/admin/node_modules/phantomjs/install.js:227:23)
npm ERR!     at Object.onceWrapper (node:events:485:26)
npm ERR!     at ClientRequest.emit (node:events:378:20)
npm ERR!     at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:636:27)
npm ERR!     at HTTPParser.parserOnHeadersComplete (node:_http_common:129:17)
npm ERR!     at Socket.socketOnData (node:_http_client:502:22)
npm ERR!     at Socket.emit (node:events:378:20)
npm ERR!     at addChunk (node:internal/streams/readable:313:12)
npm ERR!     at readableAddChunk (node:internal/streams/readable:288:9)
npm ERR!     at Socket.Readable.push (node:internal/streams/readable:227:10)

npm ERR!      /Users/admin/.npm/_logs/2021-02-16T23_18_53_716Z-debug.log
➜  npm npm list
admin@ /Users/admin
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
➜  npm npm uninstall pageres

removed 174 packages, and audited 2 packages in 2s

found 0 vulnerabilities

Issue resolved

Fixed in https://github.com/sindresorhus/pageres/releases/tag/v7.0.0


prevent duplicate aliases (settings banch)

Description of the PR
Added a check to the autoAliases method to prevent aliases from being added if it is already present in the aliases array. Possibly added by the user manually or if you have aliases like this-is-an-example, this-isan-example, thisisan-example which would normally end up changing them all to thisisanexample and adding them to the aliases array.
Changes Proposed in this Pull Request (List new items in CHANGELOG.MD)

Semver Classification

[ ] This PR only includes documentation or non-code changes.
[x] This PR fixes a bug and does not change the (intended) framework interface.
[ ] This PR adds methods or properties to the framework interface.
[ ] This PR removes or renames methods or properties in the framework interface.

this isn't necessary, as the end result is still a collection mapping aliases to commands, which you can't have duplicate keys.

I know the aliases only have 1 alias mapped to a command, but it affects if you have a help embed for a command that lists all the command's aliases. Like this

This happened because autoAliases automatically added the aliases while I also had the aliases already defined in the alias array for that command.

If you don't like that behavior, then don't do it. There is no need to patch for that behavior directly in klasa.


(SERVER-64) Store full file path in LOADED_FEATURES in autoloader

The implementations of require in JRuby and MRI don't check the same
paths in $LOADED_FEATURES. Both check a version of the relative path, but
MRI checks with the file extension and JRuby checks without. Both check the
absolute path, so if we save that instead we should get consistent behavior
across platforms.

CLA signed by all contributors.

I forked this from master this week, the branch is still only 4 commits behind.

The yum failure is bizarre... The test is should not be using agent, which was added in a5d1913bf6250dc8649d1198603412eb7c8a00e8. I think beaker has some logic to select the first host with the agent role, but idk... maybe the test ran with an older version of beaker... We should update the test to use the plural agents instead.

jenkins please test this

Using the custom function in the description of https://tickets.puppetlabs.com/browse/PUP-8733, and I pointed the puppet submodule in puppetserver to your PR, but I'm still seeing the file type being redefined. It looks like the file parameter passed to mark_loadedis sometimes a relative path, and that ends up getting cached the first time. Note I applied the following diff to print when we updated theLOADED_FEATURES` hash:
diff --git a/lib/puppet/util/autoload.rb b/lib/puppet/util/autoload.rb
index fb8fdee43c..26f67ca250 100644
--- a/lib/puppet/util/autoload.rb
+++ b/lib/puppet/util/autoload.rb
@@ -37,7 +37,10 @@ class Puppet::Util::Autoload
     # into memory.
     def mark_loaded(name, file)
       name = cleanpath(name).chomp('.rb')
-      $LOADED_FEATURES << file unless $LOADED_FEATURES.include?(file)
+      unless $LOADED_FEATURES.include?(file)
+        Puppet.notice("LOADED FEATURE #{file}")
+        $LOADED_FEATURES << file
+      end
       loaded[name] = [file, File.mtime(file)]
     end

2018-05-23 15:39:52,340 INFO  [clojure-agent-send-pool-0] [puppetserver] Puppet LOADED FEATURE ./ruby/puppet/lib/puppet/type/file.rb
...
2018-05-23 15:40:21,540 INFO  [qtp977866504-36] [puppetserver] Puppet LOADED FEATURE /Users/josh/.puppetlabs/etc/code/environments/production/modules/foo/lib/puppet/parser/functions/owner_defed_after_require.rb
LOADING puppet/type/file.rb
2018-05-23 15:40:21,554 INFO  [qtp977866504-36] [puppetserver] Puppet Redefining file in Puppet::Type
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/type/file.rb:363: warning: already initialized constant CREATORS
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/type/file.rb:364: warning: already initialized constant SOURCE_ONLY_CHECKSUMS
2018-05-23 15:40:21,709 INFO  [qtp977866504-36] [puppetserver] Puppet owner_defed_after_require: enter
2018-05-23 15:40:21,709 INFO  [qtp977866504-36] [puppetserver] Puppet owner_defed_after_require: exit (false)
2018-05-23 15:40:21,900 INFO  [qtp977866504-36] [puppetserver] Puppet LOADED FEATURE ./ruby/puppet/lib/puppet/type/notify.rb
2018-05-23 15:40:22,013 INFO  [qtp977866504-36] [puppetserver] Puppet Compiled catalog for localhost in environment production in 0.78 seconds
2018-05-23 15:40:22,017 DEBUG [qtp977866504-36] [puppetserver] Puppet Puppet::Network::Format[msgpack]: feature msgpack is missing
2018-05-23 15:40:22,019 DEBUG [qtp977866504-36] [puppetserver] Puppet catalog supports formats: json pson yaml dot
2018-05-23 15:40:22,111 DEBUG [qtp977866504-35] [p.r.core] Processing :put /puppet/v3/report/localhost
2018-05-23 15:40:22,115 DEBUG [qtp977866504-35] [puppetserver] Puppet Evaluating match for Route /^\/puppet\//
2018-05-23 15:40:22,116 DEBUG [qtp977866504-35] [puppetserver] Puppet Evaluating match for Route /v3/
2018-05-23 15:40:22,117 DEBUG [qtp977866504-35] [puppetserver] Puppet Evaluating match for Route /^\/environments$/
2018-05-23 15:40:22,117 DEBUG [qtp977866504-35] [puppetserver] Puppet Did not match path ("/report/localhost")
2018-05-23 15:40:22,118 DEBUG [qtp977866504-35] [puppetserver] Puppet Evaluating match for Route /^\/environment\/[^\/]+$/
2018-05-23 15:40:22,119 DEBUG [qtp977866504-35] [puppetserver] Puppet Did not match path ("/report/localhost")
2018-05-23 15:40:22,120 DEBUG [qtp977866504-35] [puppetserver] Puppet Evaluating match for Route /.*/
2018-05-23 15:40:22,121 DEBUG [qtp977866504-35] [puppetserver] Puppet Evicting cache entry for environment 'production'
2018-05-23 15:40:22,121 DEBUG [qtp977866504-35] [p.s.j.puppet-environments] Removing environment 'production' from registry
2018-05-23 15:40:22,126 DEBUG [qtp977866504-35] [p.s.j.puppet-environments] Registering environment 'production'
2018-05-23 15:40:22,126 DEBUG [qtp977866504-35] [puppetserver] Puppet Caching environment 'production' (ttl = 0 sec)
2018-05-23 15:40:22,127 DEBUG [qtp977866504-35] [puppetserver] Puppet Applying settings catalog for sections reporting
2018-05-23 15:40:22,152 ERROR [qtp977866504-35] [puppetserver] Puppet Could not create resources for managing Puppet's files and directories in sections [:reporting]: no parameter named 'ensure'
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/util/errors.rb:157:in `fail'
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/type.rb:662:in `[]='
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/type.rb:2495:in `block in set_parameters'
org/jruby/RubyArray.java:1735:in `each'
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/type.rb:2489:in `set_parameters'
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/type.rb:2396:in `initialize'
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/type/file.rb:493:in `initialize'
/Users/josh/work/puppet-server/ruby/puppet/lib/puppet/resource.rb:461:in `to_ral'

I assume this is because my dev/puppetserver.conf contains relative paths:
    ruby-load-path: [./ruby/puppet/lib, ./ruby/facter/lib, ./ruby/hiera/lib]

whereas an install from a package contains:
    ruby-load-path: [
        "/opt/puppetlabs/puppet/lib/ruby/vendor_ruby",
        "/opt/puppetlabs/puppet/cache/lib"
    ]

Can we expand the ruby-load-path settings when puppetserver starts so that we don't have to "expand" the path in the autoloader unnecessarily?
If I change ruby-load-path to use absolute paths, then it works ok:
2018-05-23 15:54:26,887 INFO  [qtp1008064330-35] [puppetserver] Puppet owner_defed_after_require: exit (true)

Ok trying with expanded in autoloader

jenkins please test this on redhat7-64,windows2012r2-64

The yum failure is due to a bad test introduced in a5d1913bf6250dc8649d1198603412eb7c8a00e8. It's calling agent outside of an hosts/agents loop. I think it fails on windows, because the test confines itself to a subset of linux and beaker creates methods based on roles. Presumably it doesn't meta-program an agent method if none are suitable.

jenkins please test this on redhat7-64a,windows2012r2-64a

The issue is that you have to append a for hosts to have the agent role. If no hosts have the role, then beaker never defines the method on the TestCase.
@McdonaldSeanp @branan could we update the PR testing logic to always include the agent role?


Fixed #35945 -- Added async interface to Paginator

Trac ticket number
ticket-35945
Branch description
Added AsyncPaginator and AsycPage.
I initially intended to add only asynchronous methods to the existing Paginator class.
However, since the cached_property and property decorators do not support asynchronous methods, I had no choice but to create separate AsyncPaginator and AsyncPage classes.
If there’s a better approach, I’m open to revising this.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[x] I have added or updated relevant docs, including release notes if applicable.
[ ] I have attached screenshots in both light and dark modes for any UI changes.

@sarahboyce
I have refactored code based on your feedback and prepared docs and release notes.
Please review them. 😀


fails at NERSC with new CFG_PATH

pippin.sh LSST_starterKit.yml &
[1] 57463
[kessler@cori08 pippin]$ ERROR:root:Unable to find relative path inputs when searching through the data directories: ['/global/cfs/cdirs/desc-sn/pippin']
ERROR:root:Data dir inputs cannot be resolved!
Traceback (most recent call last):
File "/global/cfs/cdirs/lsst/groups/SN/pippin/run.py", line 135, in
run(args)
File "/global/cfs/cdirs/lsst/groups/SN/pippin/run.py", line 87, in run
global_config = get_config(initial_path=cfg, overwrites=overwrites)
File "/global/cfs/cdirs/desc-sn/pippin/pippin/config.py", line 22, in get
instance = fn(*args, **kwargs)
File "/global/cfs/cdirs/desc-sn/pippin/pippin/config.py", line 59, in get_config
assert updated is not None
AssertionError

Can you put the yml file in here as well for me, along with the cfg.yml, and Ill have a look first thing in the morning


[Web App] Web app and plan different rgs

Description

This PR adds the possibility of creating a web app in a resource group that is different from the plan you are trying to create
Testing Guide

In order to test this PR, you should follow the instructions on this issue that explain how to reproduce it. You should run:
$APP_SERVICE_PLAN_NAME = "appserviceplan"
$PLAN_RESOURCE_GROUP_NAME = "appservice-plan-group"
$APP_RESOURCE_GROUP_NAME = "webapp-group"

az group create --name $PLAN_RESOURCE_GROUP_NAME --location australiaeast --subscription $SUBSCRIPTION_ID

az group create --name $APP_RESOURCE_GROUP_NAME --location australiaeast --subscription $SUBSCRIPTION_ID

az appservice plan create --name $APP_SERVICE_PLAN_NAME --resource-group $PLAN_RESOURCE_GROUP_NAME --sku B1 --is-linux

$WEBAPP_NAME = [System.Guid]::NewGuid().ToString()

az webapp create --name $WEBAPP_NAME --resource-group $APP_RESOURCE_GROUP_NAME --plan $APP_SERVICE_PLAN_NAME --runtime """python|3.6""" --query id

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

Fixes #12090

add to S169

@Kotasudhakarreddy can you PR this change please?


Spread-out data points lead to error in mbtiles reader

Hi all,
While trying to convert a rather sparse .mbtiles file, I ran into the following error.
Invalid column type Null at index: 0, name: MIN(tile_row)
I traced this error back to /versatiles_container/src/container/mbtiles/reader.rs, where it goes through the zoom levels and finds the middle column and calculates the minimum and maximum tile_row value. However - this middle column is not guaranteed to have data associated with it. Case in point, in my dataset at zoom level 3 I have data in column 2 and 4, so the calculated middle column value is 3, which has no data, so the min(tile_row) is NULL.
I guess there should be some check in place here if there actually is data for this middle column value, and if not take the closest value that exists. (Edit: alternatively, of course, you could just take one of the columns that you already know have data in them, that might be faster, since we don't know how the data is distributed anyway. I just tested this locally, seems to work fine.)

Good point!
Finding the middle column was a hack to speed up the SQL queries ... but yes, this hack doesn't seem to be a good solution, because there might not be a "middle column". :(
What do you think about using the minimum column: be80b611cd4a2056ef4fb82ebbc6cf345b041fc1 ?

Yeah, that was the way I tested it locally as well. Works fine for me!
(The exact effect it has on the speed is probably dependent on the distribution of the data, and for most distributions the center is probably a good place to look - so one could try that and fall back to the first column only if it doesn't work, but I'm not sure it makes that much of a difference speedwise)

I assume that in most cases the tiles are arranged in a rectangle. In these cases, it doesn't matter which column is selected.
In all other cases, the query may take a second, but I think that's tolerable.
I'll trigger a new release.


Split kfctl_go_test.py into separate python functions for building and deploying kubeflow

Right now we have a single python file
https://github.com/kubeflow/kubeflow/blob/master/testing/kfctl/kfctl_go_test.py
That does two things

Builds kfctl
Deploys kfctl

We will probably want to split those into two separate python functions to make it more composable.
One use case for composability is to create an E2E test for upgradability (#35). In that E2E test we will want to build kfctl once but invoke kfctl twice; once to deploy and once to do the upgrade.
Another use case is to create E2E tests for other platforms configurations. For example we want an E2E test for installing Kubeflow on an existing cluster (kubeflow/kubeflow#3496).
In that case we need to provision a Kubernetes cluster before deploying Kubeflow; e.g. using kops.
Related to: #35 E2E test for kfctl upgrade
/cc @yanniszark @Jeffwan

@jlewi I can take a shot at this. I need to spend some time to understand the flow before attempting changes. If its not urgent, I can try to submit a PR.
My current understanding is as below:

Create kfctl_go_build_test.py and kfctl_go_deploy_test.py.

Move the build and deploy code to the appropriate files from

https://github.com/kubeflow/kubeflow/blob/2f15d8dbe85f0081652c1e5363f6a8c547a3e5fc/testing/kfctl/kfctl_go_test.py#L53

Modify

https://github.com/kubeflow/kubeflow/blob/2f15d8dbe85f0081652c1e5363f6a8c547a3e5fc/testing/workflows/components/kfctl_go_test.jsonnet#L219

to include separate steps for build and deploy.
In #35, there is mention about "minimal py_func". Does this mean that create two py_funcs one for build and another for deploy in kfctl_go_test.py and change the kfctl_go_test.jsonnet to only invoke specific py_func in the workflow.
I see that each step calls only one test and not individual py_func from test files.

@jlewi
Should I start a PR in the kfctl repo or in the kubeflow repo. I understand that currently there is duplication in these repos. Based on your advice, I will start.

@nrchakradhar I'll need this next week so if you could take a stab at this that would be great.

Create kfctl_go_build_test.py and kfctl_go_deploy_test.py

Yes. Although it may be easier to fork kfctl_go_build_test.py into a new script kfctl_build_test.py this way we can check in those files without having to update the E2E test.
Updating the E2E test to use the new scripts is blocked on kubeflow/kubeflow#4148 which replaces kfctl_go_test.jsonnet with a python function that builds the Argo workflow.
So we'll want to get that PR merged first and then modify the resulting python code to use the new scripts.

@jlewi I started with the first refactor with PR#4170.
PTAL
If this is fine, I will take up further modifications after merging this. Does that sound reasonable?

@nrchakradhar sounds great. I LGTM'd your first PR this morning.

@nrchakradhar How's it going splitting up kfctl_go_test.py into two separate steps?
We can split the code into two separate function/modules now. But lets wait until after kubeflow/kubeflow#4148 is merged before updating the workflow to run two steps instead of 1.

@jlewi I am https://github.com/kubeflow/kubeflow/pull/4148 following your PR, I will start today with changes and try to submit a PR.

@jlewi I just created a PR https://github.com/kubeflow/kubeflow/pull/4187 to separate build and deploy. PTAL.


Test case for #16

Relates to #16
Looks like a combination of config options are conflicting?
Not sure why it triggers on CLI but not in IDE for me, but the run_spec is able to reproduce it in this repo.

@fbartho I've invited you as a collaborator, so you can make branches without a fork, to make it easier to collaborate.  I'm taking a look into this now.  I updated my project at work to the latest version, and running prettier in the cli does not throw any errors, so at least it doesn't seem like something that broke in the latest release.

This appears to be related to importOrderBuiltinModulesToTop.  Setting that to false makes this test case pass.

constants is one of the builtin node modules.  The regex needs to be more explicit.  I should be able to crank out a fix, thanks for pointing this out!

How about changing this to

^(${builtinModules.join("|")}|${builtinModules.map(module => 'node:'+module).join("|")})$

That resolves to

^(_http_agent|_http_client|_http_common|_http_incoming|_http_outgoing|_http_server|_stream_duplex|_stream_passthrough|_stream_readable|_stream_transform|_stream_wrap|_stream_writable|_tls_common|_tls_wrap|assert|assert/strict|async_hooks|buffer|child_process|cluster|console|constants|crypto|dgram|diagnostics_channel|dns|dns/promises|domain|events|fs|fs/promises|http|http2|https|inspector|module|net|os|path|path/posix|path/win32|perf_hooks|process|punycode|querystring|readline|repl|stream|stream/consumers|stream/promises|stream/web|string_decoder|sys|timers|timers/promises|tls|trace_events|tty|url|util|util/types|v8|vm|wasi|worker_threads|zlib|node:_http_agent|node:_http_client|node:_http_common|node:_http_incoming|node:_http_outgoing|node:_http_server|node:_stream_duplex|node:_stream_passthrough|node:_stream_readable|node:_stream_transform|node:_stream_wrap|node:_stream_writable|node:_tls_common|node:_tls_wrap|node:assert|node:assert/strict|node:async_hooks|node:buffer|node:child_process|node:cluster|node:console|node:constants|node:crypto|node:dgram|node:diagnostics_channel|node:dns|node:dns/promises|node:domain|node:events|node:fs|node:fs/promises|node:http|node:http2|node:https|node:inspector|node:module|node:net|node:os|node:path|node:path/posix|node:path/win32|node:perf_hooks|node:process|node:punycode|node:querystring|node:readline|node:repl|node:stream|node:stream/consumers|node:stream/promises|node:stream/web|node:string_decoder|node:sys|node:timers|node:timers/promises|node:tls|node:trace_events|node:tty|node:url|node:util|node:util/types|node:v8|node:vm|node:wasi|node:worker_threads|node:zlib)$

Yep, exactly.  Although I used a non-capturing group.  I also simplified down the test case a bit.

Oh this is interesting.  I guess that node:fs/promises wasn't valid in node 12.  I'll adjust the tests a bit.

I guess the other option is to stop supporting node 12.  It's EOL, after all.  I propose that we remove it from our tests, at least.  What do you think, @blutorange, @fbartho?

I'm certainly supportive of only explicitly supporting N-1 on stable node release lines. -- Like maybe it works on node-12, but we shouldn't try to maintain support for it!

The PR is green! Please let me know if you want me to strip out the test case, or move it somewhere, or if this PR is ready to go!

Released in https://github.com/IanVS/prettier-plugin-sort-imports/releases/tag/v3.4.2.


NIP-09: Event Deletion

https://github.com/nostr-protocol/nips/blob/master/09.md

Completed in 1e419720729d41c14bbe7efe0b853d750192c23c.


1.19.3

Conflicts have been fixed, works with @ZakShearman's metadata fixes

@iam4722202468 I don't understand wdym by "fix" so i just marked it as resolved

Thanks for your help, i will try to fix the tests soon


Fix warnings with new GCCs and glibcs

This fixes warnings when building with recent glibc versions.
Part of coreos/coreos-overlay#2886

It looks as though gtest provides pkg-config files now?

If it does, Gentoo's latest version doesn't install them.


Resolve several nits in the Terminal AI code

Summary of the Pull Request

[x] Remove the ESC handler that clears the query message
[ ] Streamline error handling code
[x] Fix this and & in several lambdas
[ ] Fix getting the active commandline properly
[x] Use fwlinks
[ ] Use XAML color ramp resource names instead of hardcoded colors

PR Checklist

[ ] Closes #xxx
[ ] Tests added/passed
[ ] Documentation updated

If checked, please file a pull request on our docs repo and link it here: #xxx

[ ] Schema updated (if necessary)

Would this be the right place to switch all of the hardcoded colors to use the standard XAML color ramp resource names? That would let us support light mode...

Would this be the right place to switch all of the hardcoded colors to use the standard XAML color ramp resource names? That would let us support light mode...

Yep! Added to the todo list

Dark mode:

Light mode:

High contrast (Desert):

High contrast (Night sky):


Update to Nodejs v20

Problem description
Nodejs v20 is released and holds promise to be somewhat more performant (possibly resolving #4903)
Solution description
Update to v20, resolving any build issues that arise.

[x] blst https://github.com/ChainSafe/lodestar/pull/5612
[x] cpu_features https://github.com/ChainSafe/lodestar/pull/5674
[x] snappy https://github.com/ChainSafe/lodestar/pull/5617
[x] gc-stats https://github.com/ChainSafe/lodestar/pull/5677 https://github.com/ChainSafe/lodestar/pull/5683 https://github.com/ChainSafe/lodestar/pull/5686 https://github.com/ChainSafe/lodestar/pull/5690

Additional context
No response

Would also do a quick scan of the documentation to ensure anywhere we state node requirements to use node 20.

unstable branch with Node 20 has been deployed to our feat1 group for several days

Closed with 1.10.0


Green check mark vs computer icon.

Hello, I am trying to decipher the difference between the green check mark and the computer icon in the electrum GUI when using EPS.
I am using Windows, Bitcoin Core 018.0, EPS 0.17, Electrum 3.3.6. I have set up the software per the tutorial https://github.com/DriftwoodPalace/guides/blob/master/hodl-guide/hodl-guide_63_eps-win.md and have electrum only connecting to one node, "localhost".
I have successfully verified incoming and outgoing UTXOs on several wallets and have not figured out why sometimes a green checkmark is present and why sometimes a computer icon is present. When the computer icon is present the "date" field filled with "Local" instead of a date.
At some point in the past the circle at the bottom was blue as well and all icons were computers instead of green  check marks. However, now most wallets have all green check marks and only a few have computer icons. The circle is green in all wallets.
The behavior seemed to change as I was troubleshooting and rescaning and probably connected a few times to non localhost servers over electrum because of accidentally not using the shortcut that forces "--oneserver --server localhost:50002:s"
I wish I could be more specific with respect to reproducing a computer icon or blue circle in contrast to green checkmark and green circle but I was doing multiple things before I realized the change in Electrum behavior.
Any insight is appreciated. Thank you.

Thanks for the issue. This happened to me once but I wasn't able to reproduce the issue. I'd say try setting up EPS again from the start with a new Core wallet.dat file, then import all addresses again and rescan. Also restore your Electrum wallet again from seed. (Remember you can export and import labels so you don't lose them)
Blue circle in the bottom-right means Electrum was connecting to the server(s) over Tor.

Creating a new Core wallet.dat, importing and rescanning /w EPS again  worked. All dots are green. Thank you.


eBPF uninstall fails after spinxsk watchdog failure

We're seeing several runs where the spinxsk watchdog fires, which generates a live dump, and then the eBPF uninstall watchdog fires, which triggers a bugcheck. Those bugchecks are not ending up in AzWatson after several repros, which means we have no visibility into the root cause.
Revert the bugcheck change on the eBPF uninstall path and verify the live dump(s) will be uploaded as artifacts. Capture a process dump of any relevant services, including ebpfsvc.
### Tasks

Live kernel dumps are now being uploaded. Next: collect the process dumps for spinxsk.exe, ebpfsvc, and msiexec.exe.

I haven't seen this for a while. Diagnostics were added to debug next time we get a repro.


Fix overflow at nodeStatusList API

https://github.com/aicers/review-web/issues/37 와 관련하여 NodeStatus 쪽 부분에 한정하여 개선을 하고자 합니다. To fix it, GraphQL API should return these fields as wrapped as StringNumber.
total_memory
used_memory
total_disk_space
used_disk_space
ping

https://github.com/aicers/review-web/blob/d808245a7c03e4bbba2b6c065965ad1e780b4189/src/graphql/node.rs#L405-L428

Regarding precision loss, would not returning String avoid it?
What exactly "overflow" means?

I think our APIs should keep the attributes of the values as much as possible. Returning String should be a last resort.

Good, what do you think about StringNumber instead?
https://docs.rs/async-graphql/latest/async_graphql/types/struct.StringNumber.html#

As we discussed offline, the type we are concerned with is only u64, which GraphQL's standard types cannot represent.

Agreed, and not a big deal, just a quick comment, that there is i64 as well, which will be handled as StringNumber, just like u64.


I am interested in using your game on my website. Could you add a license file like the MIT one in this pull request so I know how you want your software used?

This is a great idea, thanks for bringing my attention to this! Is this website live yet?

Not yet. I'll send a link when it is. Thanks!
On Fri, Feb 17, 2017 at 3:40 AM, ssjoleary<EMAIL_ADDRESS>wrote:

This is a great idea, thanks for bringing my attention to this! Is this
website live yet?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ssjoleary/Android--Math-Game/pull/1#issuecomment-280628163,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGrFLzxDqUn37C5P5kBPacGPqm7Lm6rks5rdYcfgaJpZM4L3dBy
.


Iconize does not translate strings when a file is started by Obsidian (like with Homepage Plugin)

Describe the bug
It seems when I try to use icons from the Iconize plugin that they are not active when Homepage opens its marked Note at startup. Only by closing the note and reopening it (whether automatically or manually) will the icons be seen.
I believe this has to do with the ordering of the startup of the plugins. I do not know how to fix this from an Obsidian side (have asked in the Discord), but thought I would also like to make this apparent to you in case you can do some magic to reload after all plugins have been loaded.
Steps to reproduce

Install Homepage and Iconize plugins
Create a Note and mark it as the "Homepage"
In this note use a few Icons

Examples

:FasChartColumn:
:FasBrain:
:FasMemory:
:FasVideo:
:FasRecycle:

Reload Obsidian to see that these icons are still text strings and not replaced by Iconize.

Expected behavior
When Homepage opens its file, I expect that Iconize will refresh the icons used without requiring my to manually interject.
Additional context
According to novov  (author of Homepage), this seems to be an error with Iconize. "From my testing, Iconize fails to insert icons with files loaded on startup, even without Homepage. When I disable Homepage, open a file with icons, close Obsidian, and then reopen Obsidian, the icons are not successfully rendered on startup. Only when I open the file again or open another file are the icons rendered."

Facing the same issue. I believe that this is not related to other plugins, and #368 is related. Also, this bug doesn't seem to affect the lucide icon pack.


improved character case handling in firebird

Can you elaborate abit on what was changed and why ?

sure:

FBOptions.PackKeyNames has been extended to allow the configuration of the FirebirdTruncator. Due to firebird allowing only a specific length in names. This one scrambles the name really weird. I wanted to configure to disable that (so instead getting an exception on execution instead of silently creating a weired name)

the lower(*) stuff is to allow checking for names/constraints in the database, without knowing the correct case.

The GenerateSetNull has a bug (sets the opposite value), this one fixes that (see http://www.firebirdfaq.org/faq103/)

commit retain does really weired stuff on firebird. So it's better to use real transaction commiting.

it should only store undoexpression history if undo enabled (leads to NPE otherwise)

the SequenceExists crashes with an ArgumentException if the table does not exist, instead it should say no

I totally understand what you mean. Of course you can reason about possibly. I think that this a little bit more practical. Especially this is the similar behavior to what the sqlserver one returns.
And I think if you really have this special scenario you always can use the raw sql stuff instead which would make this even more explicit

@woehrl01 Thanks

@tommarien, @woehrl01
sorry to comment on an -meanwhile- "old" topic and an already closed PR.
I have some concerns regarding this PR. First of all I don't understand why some tests are passing on the build server when they should actually fail!

FirebirdProcessorTests
For example the test CanCreateAndDropSequenceWithExistCheck should fail on line 146 since this PR handles everything case insensitive.
Indeed the test fails on my machine.

Antother question related to the change in CommitRetaining:
Ponder for example one test in FirebirdIndexTests. It uses the class FirebirdTestTable which is storing a reference to the Transaction object of the processor.
Now each time CommitRetaining is called it generates a new Transaction object which makes the referenced Transaction in FirebirdTestTable no longer valid and all tests should ultimatly fail!
How come they don't on the build server? They do fail on my machine.

Beside the above mentioned pure technical issues I don't see strong semantic reasons for both changes regarding case insesitivity and commit retaining.

Case insensitivity:
The Public API already allowed work in a case insensitive manner.
For example it was already possible to do Create.Table("table1") which correctly stored "TABLE1" in Firebird.
Now if some one wishes to store table1 say as "TaBLe1" (using the quotes) this PR will prevent that without an obvious reason!

Commit retaining:
Although it is absolutly true that the commit retaining option in Firebird is not recommended, the Transaction object on the Processor (which the change in CommitRetaining is modifying) is publically accessible!
This lastly means that anything holding a reference to that transaction object (whether it makes sense or not) will be broken after an automatic transaction commit (using CommitRetain() in this PR).
Yes, commit retaining is not recommended in Fb but it worked in the context of FluentMigrator like it should.

Hi @amroel
you are absolutely correct that these test should have failed. I don't know why, but both of them (sadly) do work on my machine.
Regarding your semantic concerns:
I know that everyone has a different usecase so my points are regarding to my daily work and I'll explain why I did these changes.
Foreword: We use Fluent.Migrator to run our migrations for Firebird, Sql Server and Sqlite. That is the reason I want them to behave equally.

Case insensitivity:
It's true that the public API should work in a case insensitive manner. But it doesn't do it e.g. for Schema.XYZ.Exists() checks. Sqlite and Sql Server check those case insensitiv, Firebird not. We would need to know the case sensitivity only for firebird. True this is not a big problems, but still a possibility to fail. Case sensitivity is semantically correct, but in my opinion: SQL is case insensitiv, why the hell should tablenames be?
Another thing is regarding the column names. The altering of nullable only works on Firebird if you know the exact name and provide it like that. It wouldn't even fail with an exception! Good luck debugging this mess.
Regarding creating of those tables, I don't see any change which should prevent this. (And why do you even want this kind of names? )

Commit retaining:
You are totally correct, but commit retaining is not behaving like it should. I had a lot of troubles with this one, because of the totally weird behaviour of transactions within firebird. (Visibility of newly created tables, columns, type changes, creating indizies on newly created columns etc.). And the only working thing is commiting and reopening.

I personally just want to have these things work the same across those vendors. I know that there are a lot of compromisses to make. I only know that these changes are working amazingly well since about 2 years in production now, with currently more than 300 migrations across all those vendors. (that's the reason why I even made the PR)

Hi @woehrl01
what I'm realy worried about are those tests that should fail!
We should come after the reason. It's making me very nervous :)
You're right regarding the table names. I simply missed that it's still possible using quotes.
Regarding Commit retaining:
where exactly did you have problems in the context of FluentMigrator?
I didn't come against any issues while I was (and I'm still) working with FluentMigrator targeting Firebird!
Are you eventually using the FirebirdProcessor directly in your projects?
In General you can't treat different db engines equally. That's precisley the reason why FluentMigrator has all those different "Processors" implementing a common interface.
I would do the same if I had to.

@amroel
Regarding those test, I think that has something to do with the .NET Library. There was a hugh difference between the "old" .NET 3.5 and the newer 4.0 Library. There were a lot of memory/connection leaks in the 3.5 one (and I think this is the one this project uses).
Regarding commit retaining:
I'm not sure what is was (its over a year now) but as I remember correctly, it had something to do with altering a table in the same migration as you insert data into it. (i know you shouldn't do that either, but there were cases I had to).
Regarding treating equally:
I'm totally aware that I can't treat them equally. But with fluent.migrator I'm near, to write a single fluent statement for most of the simple cases (alter/create/drop of indicies/tables/column). Stored Procedures/Triggers etc. are of course totally different cases.
That was a huge productivity improvement for us, compared to our old pure sql scripts and with less bugs. (If anyone has created a TIMESTAMP in Firebird and mistakenly uses TIMESTAMP in Sql Server for the same column, know what struggle this can make :) )

@woehrl01
I'm actually having a hard time trying to get those tests passing at all! Not even once.
It can't be just the .net library (if it is the cause at all).
They just do what they should, namley fail. Always.
Here is an example (fails because of the change to CommitRetaining):
<test-case name="FluentMigrator.Tests.Integration.Processors.Firebird.FirebirdIndexTests.CallingIndexExistsCanAcceptIndexNameWithSingleQuote" executed="True" success="False" time="0.069" asserts="0">
	<failure>
		<message><![CDATA[System.InvalidOperationException : Execute requires the Command object to have a Transaction object when the Connection object assigned to the command is in a pending local transaction. The Transaction property of the Command has not been initialized.]]></message>
		<...>
    </failure>
</test-case>

I'm astonished that they do pass on your side and on the build server. I simply don't get it.
@tommarien any Ideas?

@tommarien
Is this what currently drives the build on travis?
If yes then it means the tests I'm refering to do not run at all! Right?
Is it the same for team city?

Yes that should be the same in teamcity except the notworkingonmono part
I'll try to verify asap
Verstuurd vanaf mijn iPhone

Op 23-sep.-2015 om 17:08 heeft amroel<EMAIL_ADDRESS>het volgende geschreven:
@tommarien
Is this what currently drives the build on travis?
If yes then it means the tests I'm refering to do not run at all! Right?
Is it the same for team city?
—
Reply to this email directly or view it on GitHub.

Just verified indeed teamcity is excluding IntegrationTests Only, not NotWorkingOnMono ;)


Updated org in Settings document

Related Issue
Please reference the issue that this pull request addresses. This can be a new issue or an existing one.
Proposed Changes
Please describe the changes proposed in this pull request. This could include bug fixes, feature enhancements, code refactoring, documentation updates, or any other modifications to the codebase.
Reviewers
Please tag the person or team responsible for reviewing this pull request, using the @ symbol followed by their username.

/do-doc-build


Add test for docker image

For https://github.com/giantswarm/giantswarm/issues/2831
WIP

Closing. It occurred to me that this cannot easily be tested.


Add NotFound to help situation when need to raise for non-strict routes

Failed tests here: https://github.com/sanic-org/sanic/pull/2100/checks?check_run_id=2274096036
The reason was that #21 removed the cascading. There actually was a need for that in some circumstances. Mainly when there is a match on a route that otherwise is being evaluated with == and it was passed with /. Strict slashes is a bear for support and complexity.
def find_route(path, router, basket, extra):
    parts = tuple(path[1:].split(router.delimiter))
    num = len(parts)
    if num > 0:
        if parts[0] == "test":
            if num > 1:
                if parts[1] == "other" and num == 2:
                    if extra == {'host': 'sub1.example.com'}:
                        basket['__handler_idx__'] = 0
                    elif extra == {'host': 'sub2.example.com'}:
                        basket['__handler_idx__'] = 1
                    else:
                        raise NotFound
                    basket['__raw_path__'] = 'test/other'
                    return router.dynamic_routes[('test', 'other')], basket
                raise NotFound    # <<< WAS MISSING
            if extra == {'host': 'example.com'}:
                basket['__handler_idx__'] = 0
            elif extra == {'host': 'sub.example.com'}:
                basket['__handler_idx__'] = 1
            elif extra == {'host': 'sub1.example.com'}:
                basket['__handler_idx__'] = 2
            elif extra == {'host': 'sub2.example.com'}:
                basket['__handler_idx__'] = 3
            else:
                raise NotFound
            basket['__raw_path__'] = 'test'
            return router.dynamic_routes[('test',)], basket
    raise NotFound

Can we add a test for this in sanic-routing?

Can we add a test for this in sanic-routing?

Yup. Working on it.

For reference, here are the results of tests on sanic using this branch. This is probably something that we should automate so that we do not need to remember to make sure to do this all the time (which I forgot for 0.5.1), at least until we merge this back into the main repo.
Results (67.72s):
     872 passed


GetDeepSearchResults returns 410 error code

Zillow may be killing this api to the public, 410 gone error code now

Looks like Zillow shut down their API:
https://twitter.com/zillow/status/1365418247949058048

was able to get a workaround / build my own tool using endpoints https://www.zillow.com/cma-tool/get-zpid and https://www.zillow.com/graphql/

was able to get a workaround / build my own tool using endpoints https://www.zillow.com/cma-tool/get-zpid and https://www.zillow.com/graphql/

How did you find the qraphql schema? Looks like introspection is turned off.


QMainWindow.showMaximized does not work

When calling showMaximized in QMainWindow nothing happens.
Nor does calling setWindowState(Qt.WindowMaximized).
Calling from the central widget does nothing.
However, when calling showMaximized on the modern-wrapper it works.
class MainWindow(QMainWindow):
    def __init__(self):
        super().__init__(flags=Qt.Window)

        central_widget = Master(self)
        self.setCentralWidget(central_widget)

        self.showMaximized()  # <- This does not work
        self.setWindowState(Qt.WindowMaximized)  # <- This does not work

class Master(QWidget):
    def __init__(self, *args, **kwargs):
        super().__init__(*args, **kwargs)

       self.parent().showMaximized()  # <- This does not work

def main():
    app = QApplication(sys.argv)

    main_window = MainWindow()
    main_window.showMaximized()  # <- This does not work
    qtmodern.styles.dark(app)
    modern_window = qtmodern.windows.ModernWindow(main_window)
    modern_window.show()
    modern_window.showMaximized()  # <- This DOES work!
    sys.exit(app.exec_())

if __name__ == '__main__':
    main()

I have found, that showFullScreen() also does not work


Support webdriver-manager 3.8.6 auto detection

According to https://github.com/SergeyPirogov/webdriver_manager/releases/tag/v3.8.6 webdriver-manager supports an auto-detection mode if no version is specified:
if version is None - tries to determine installed browser version, and if fail - downloads like "latest" - LATEST_RELEASE.
But it seems that pylenium doesn't support setting no version and seems to pass "latest" if no version is specified.

Thanks for calling this out! I'm labeling this as a bug since our implementation of driver version works for some and not for others. I'll update this so we take full advantage of how webdriver_manager does things.
I haven't switched to Selenium's "Selenium Manager" yet because it still has a lot of issues, but I'm assuming that will be the solution we move to eventually.

https://github.com/ElSnoMan/pyleniumio/releases/tag/v1.18.0


Ruby group capstone: set up your Kanban board

Capstone Ruby project: https://github.com/anthonymr/catalog-of-my-things/projects/1
Project members: 3
Member distribution:

Member 1: @anthonymr
Member 2: @RaphDasilva
Member 3: We split those issues between @anthonymr and @RaphDasilva until @AbdimulhinYussuf3675 shows up.

Hi Team,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights

good job dividing the work between the team members.

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


[Bug]  Installation of backpack/generators with backpack/crud:"4.2.*" fails on new laravel project.

Bug report
What I did
Created fresh laravel project.
Executed
composer require backpack/crud:"4.2.*"
composer require --dev backpack/generators

What I expected to happen
Package being installed succesfully.
What happened
Your requirements could not be resolved to an installable set of packages.
  Problem 1
    - backpack/base[dev-master, 1.1.9, ..., 1.1.13] require laravel/framework 5.8.*|^6.0 -> found laravel/framework[v5.8.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev] but it conflicts with your root composer.json require (^8.65).
    - backpack/base[0.9.0, ..., 0.9.7] require laravel/framework 5.5.*|5.6.* -> found laravel/framework[v5.5.0, ..., 5.6.x-dev] but it conflicts with your root composer.json require (^8.65).
    - backpack/base[0.9.8, ..., 0.9.12] require laravel/framework 5.5.*|5.6.*|5.7.* -> found laravel/framework[v5.5.0, ..., 5.7.x-dev] but it conflicts with your root composer.json require (^8.65).
    - backpack/base[1.0.0, ..., 1.0.4] require laravel/framework 5.6.*|5.7.* -> found laravel/framework[v5.6.0, ..., 5.7.x-dev] but it conflicts with your root composer.json require (^8.65).
    - backpack/base[1.1.1, ..., 1.1.8] require laravel/framework 5.8.* -> found laravel/framework[v5.8.0, ..., 5.8.x-dev] but it conflicts with your root composer.json require (^8.65).
    - backpack/generators[v3.1.0, ..., v3.1.11] require backpack/crud 4.1.* -> found backpack/crud[4.1.0, ..., 4.1.x-dev] but it conflicts with your root composer.json require (4.2.*).
    - backpack/generators v3.x-dev requires backpack/base 0.9.*|1.0.*|1.1.* -> satisfiable by backpack/base[0.9.0, ..., 0.9.12, 1.0.0, ..., 1.1.13].
    - backpack/base 1.0.x-dev is an alias of backpack/base dev-master and thus requires it to be installed too.
    - Root composer.json requires backpack/generators ^3.1 -> satisfiable by backpack/generators[v3.1.0, ..., v3.x-dev].

Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP 8.0.13 (cli) (built: Nov 22 2021 09:50:43) ( NTS )
Copyright (c) The PHP Group
Zend Engine v4.0.13, Copyright (c) Zend Technologies
    with Zend OPcache v8.0.13, Copyright (c), by Zend Technologies

### LARAVEL VERSION:
v8.76.2@c67acfdc968f487b6235435080eef62a7e2ed055

### BACKPACK VERSION:
4.2.x-dev@7c34334db53c2ddd03f958369b7294615345b562

@PitchRE , heads-up: I'm pretty sure none of the Backpack addons will get 4.2 support until we actually launch 4.2. Until then, if you want to use 4.2-dev, it's recommended you do composer require backpack/crud:"4.2.x-dev as 4.1.99
That should make all of them install just fine, as if you were running 4.1.x

@tabacitu Thank you. I am now able to play with it.
I just got confused by the docs and expected it to work.
@pxpm
https://github.com/Laravel-Backpack/CRUD/pull/4002
Thank you for this PR. Its amazing, I was waiting for it!

Yeah, sorry didn't come to mind installing dev-branch as 4.1.
It's a fast moving branch, so make sure you pull the updates regularly.
There are some known issues I am gathering here: https://github.com/Laravel-Backpack/CRUD/issues/4012
Let me know if you spot something else that I missed.
Thanks,
Pedro

My bad - the docs did not mention this. I've just updated the 4.2 docs to instruct people to use 4.2.x-dev as 4.1.99 for now.


gtranslator: init at 3.32.0

Tool for translating Gettext files: https://gitlab.gnome.org/GNOME/gtranslator
Things done

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

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

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

Has libglade in it's Requries https://gitlab.gnome.org/GNOME/gtranslator/blob/3.32.0/data/gtranslator.pc.in#L8 ?

And now CI does not like harfbuzz:
fixed-output derivation produced path '/nix/store/w3n916nvkx6zrqjmgy0mr6frm45sxsms-harfbuzz-2.4.0.tar.bz2' with sha256 hash '0vrkvdlmihdg62a4c6h5kx27khc33xmb95l50zgnwnavvpwyyw5l' instead of the expected hash '11a3kq3m6mgyjymgrmacr3h562qmmy2f6rc6wcj21mwv31j0avrk'


Using  within  results in error thrown at runtime

Version
6.0.0-alpha.1
Test Case
https://codesandbox.io/s/react-router-38xq6
Steps to reproduce
Attempt to use a <Link /> inside of a <StaticRouter />.
Expected Behavior
The link is rendered as an <a>.
Actual Behavior
A runtime error with the following text is thrown:
TypeError: b.createHref is not a function

      at Object.useHref (packages/react-router/modules/index.js:363:10)
      at packages/react-router-dom/modules/index.js:137:14
      at renderWithHooks (node_modules/react-dom/cjs/react-dom.development.js:15108:18)
      at updateForwardRef (node_modules/react-dom/cjs/react-dom.development.js:16746:20)
      at beginWork$1 (node_modules/react-dom/cjs/react-dom.development.js:18522:16)
      at HTMLUnknownElement.callCallback (node_modules/react-dom/cjs/react-dom.development.js:347:14)
      at invokeEventListeners (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:193:27)
      at HTMLUnknownElementImpl._dispatch (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:119:9)
      at HTMLUnknownElementImpl.dispatchEvent (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:82:17)
      at HTMLUnknownElementImpl.dispatchEvent (node_modules/jsdom/lib/jsdom/living/nodes/HTMLElement-impl.js:30:27)
      at HTMLUnknownElement.dispatchEvent (node_modules/jsdom/lib/jsdom/living/generated/EventTarget.js:157:21)
      at Object.invokeGuardedCallbackDev (node_modules/react-dom/cjs/react-dom.development.js:397:16)
      at invokeGuardedCallback (node_modules/react-dom/cjs/react-dom.development.js:454:31)
      at beginWork$$1 (node_modules/react-dom/cjs/react-dom.development.js:23217:7)
      at performUnitOfWork (node_modules/react-dom/cjs/react-dom.development.js:22211:12)
      at workLoopSync (node_modules/react-dom/cjs/react-dom.development.js:22185:22)
      at renderRoot (node_modules/react-dom/cjs/react-dom.development.js:21878:11)
      at scheduleUpdateOnFiber (node_modules/react-dom/cjs/react-dom.development.js:21419:22)
      at scheduleRootUpdate (node_modules/react-dom/cjs/react-dom.development.js:24319:3)
      at updateContainerAtExpirationTime (node_modules/react-dom/cjs/react-dom.development.js:24347:10)
      at updateContainer (node_modules/react-dom/cjs/react-dom.development.js:24436:10)
      at node_modules/react-dom/cjs/react-dom.development.js:24963:7
      at unbatchedUpdates (node_modules/react-dom/cjs/react-dom.development.js:21687:12)
      at legacyRenderSubtreeIntoContainer (node_modules/react-dom/cjs/react-dom.development.js:24962:5)
      at Object.render (node_modules/react-dom/cjs/react-dom.development.js:25042:12)
      at node_modules/@testing-library/react/dist/index.js:86:25
      at batchedUpdates$1 (node_modules/react-dom/cjs/react-dom.development.js:21643:12)
      at act (node_modules/react-dom/cjs/react-dom-test-utils.development.js:1002:14)
      at act (node_modules/react-dom/cjs/react-dom-test-utils.development.js:1418:12)
      at render (node_modules/@testing-library/react/dist/index.js:82:26)

I use <StaticRouter /> in tests. I can use <MemoryRouter /> in tests (which does resolve this issue), but this potentially bricks server side rendering.

Currently I have no time for a PR, but if you @danpantry would like to do it, it should only be something like this:
createHref(location) {
  return createPath(location);
}

Can do


Class with Generics declare in function`s parameter,and renturn unknown

TypeScript Version:  3.5.2

**Search Terms:T extends Generics  property type is unknown
Code
export class Config<T> {
    constructor(
        public classType?: Type<T>
    ) {
    }
}
export class SubClass {
    test: string = 'print out'
}
export class SubConfig extends Config<SubClass>{
    classType = SubClass
}
interface Type<T> {
    new(...args: any[]): T;
}
function f1<D, T extends Config<D>>(val: T) {
    return val
}
function f2<D, T extends Config<D>>(val: T) {
    return val.classType
}
/**
 * when `f1` return val,and classType=>SubClass
 * but `f2` return  val.config.classType and classType=>unknown
 * I want to use `f2` and also return `SubClass`
 * How to Change Code?
 * Or like a bug?
 */
let a = f1(new SubConfig())
let classA = new a.classType()
/**ok */
console.log(classA.test)
let b = f2(new SubConfig())
let classB = new b()
/**error */
// console.log(classB.test)

Expected behavior:
f2 return type is SubClass
Actual behavior:
f2 return type is unknown
Playground Link:
Related Issues:

Better to try stackoverflow first, unless you think there is a bug here.
function f2<T>(val: Config<T>) {
    return val.classType
}

let b = f2(new SubConfig())
let classB = new b!()

This is the intended behavior; see above comment for solution

Better to try stackoverflow first, unless you think there is a bug here.
function f2<T>(val: Config<T>) {
    return val.classType
}

let b = f2(new SubConfig())
let classB = new b!()

thanks!
Although  I don`t known declare more detail but get unknown,reverse,without extends and have return a right type.


Don't create zero amount change ouputs

Closes #1319
When creating lightning offers, we request zero change, which adds a zero amount output.

Any idea why CI isn't passing? I get same thing locally ...

There's a test that relies on an empty thing your now ignoring as a new epoch trigger to make progress @justinmoon

I can't tell you the why, @jkitman might have an idea, but it seems processing the offer takes one less epoch, so you have to reduce the 2 to a 1 here:
https://github.com/fedimint/fedimint/blob/13e9b2a3b2fe5f616fa43b573d0dab90f89ac33b/integrationtests/tests/tests.rs#L442

There's a test that relies on an empty thing your now ignoring as a new epoch trigger to make progress @justinmoon

I think that was actually more accidental. I get it now. Even an empty e-cash output would run one more consensus round (to exchange an empty signature share struct) before there was nothing left to do anymore. We don't need that extra epoch imo (at least in the case of lightning_gateway_pays_internal_invoice which I was just debugging).

Waiting one less epoch fixed it. Thanks guys!


this.raw is broken after update to 4.x?

↓↓↓ See update & the fix on the bottom ↓↓↓
Before migration to adonis/lucid 4.x I had a few raw migrations like:
const Schema = use('Schema')

class WhateverMigration extends Schema {

  up() {
    this.raw("WHATEVER COMMAND")
  }

  down() {
    // My down code
  }

}

module.exports = WhateverMigration

These raw migrations worked just fine with Adonis/Lucid 3.x, however, these do not pass with adonis 4.x and give following trace:
   at WhateverMigration.raw (/path_to_project/node_modules/@adonisjs/lucid/src/Schema/index.js:238:17)
   at WhateverMigration.raw (/path_to_project/node_modules/@adonisjs/lucid/src/Schema/index.js:238:17)
   at WhateverMigration.raw (/path_to_project/node_modules/@adonisjs/lucid/src/Schema/index.js:238:17)
   at WhateverMigration.raw (/path_to_project/node_modules/@adonisjs/lucid/src/Schema/index.js:238:17)
   at WhateverMigration.raw (/path_to_project/node_modules/@adonisjs/lucid/src/Schema/index.js:238:17)
   at WhateverMigration.raw (/path_to_project/node_modules/@adonisjs/lucid/src/Schema/index.js:238:17)
   at WhateverMigration.raw (/path_to_project/node_modules/@adonisjs/lucid/src/Schema/index.js:238:17)
   at WhateverMigration.up (/path_to_project/database/migrations/1493454741900_add-superadmin-users.js:8:10)
   at Migration._executeSchema (/path_to_project/node_modules/@adonisjs/lucid/src/Migration/index.js:250:36)
   at Migration._execute (/path_to_project/node_modules/@adonisjs/lucid/src/Migration/index.js:270:18)
   at Migration.up (/path_to_project/node_modules/@adonisjs/lucid/src/Migration/index.js:362:18)
   at <anonymous>

I have to admit that line
   at WhateverMigration.raw (/path_to_project/node_modules/@adonisjs/lucid/src/Schema/index.js:238:17)

Is repeated around 10000+ times like it goes to some kind of infinite loop.
The code in raw statement does not matter, I tried to put even very simple things — they all fail. I have a few dozen migration files so I'm quite sure that only raw is failing, all the other commands like table.create work fine.
Update
Changing this.raw("WHATEVER COMMAND") to this.schema.raw("WHATEVER COMMAND") seems to fix the issue. No, apparently, in this case the code is simply not run

So I thought that changing this.raw("WHATEVER COMMAND") to this.schema.raw("WHATEVER COMMAND" fixes the issue. But apparently, it does not run the code in this case. So the issue is still open for me…

I'm believe I'm having the same issue. Looking at the code should this be using the _deferredActions array?
raw (statement) {
  this.deferredActions.push({ name: 'raw', args: [statement] })
  return this
}

Have you have tried
  async up () {
    await this.schema.raw("")
  }

Also fixed this.raw. Following should work fine
  async up () {
    await this.raw("")
  }


fix: onboarding config and readme updates for web-app

Summary:
When setting up the mobility-feed-api using the readme, I ran into an issue running the command docker-compose --env-file ./config/.env.local  up -d --force-recreate where the error was that it couldn't find the changelog.xml. With the help of @davidgamez it was discovered that the file structure changed in liquibase 4.27 and that the solution was to include 'changelog' into the search-path. It was tested on David's machine that this addition did not break the existing functionality
For the addition in the web-app if you build the package with npm install it will return an error as react-scripts seems to not be compatible with the latest typescript (https://github.com/facebook/create-react-app/issues/13080). Installing with yarn seems to use smart alternatives to this mismatch
Expected behavior:
Be able to run docker-compose --env-file ./config/.env.local  up -d --force-recreate without error when setting up the project as per the readme
Testing tips:
Go through the readme and assure that nothing is broken
Please make sure these boxes are checked before submitting your pull request - thanks!

[X] Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
[X] Add or update any needed documentation to the repo
[X] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[X] Linked all relevant issues
[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

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


Power Platform hub documentation linked files appear to be incomplete

In the Download the Assets section of "Create an internal Microsoft Power Platform hub", https://aka.ms/pphub-download points to PowerPlatformHub.zip within the PowerPlatform Hub subfolder of the coe-starter-kit repository.
We were running into issues with the Deploy-PowerPlatformHub.ps1 script from PowerPlatformHub.zip in our tenant (specifically, Invoke-PnPSiteTemplate fails every run), and as we were debugging we noticed a few things:

The Source folder which contains images used by the template exists in the GitHub repo, but not PowerPlatformHub.zip. This leads to errors when Invoke-PnPSiteTemplate attempts to apply these images via the template. It is not clear in the documentation that one should download this Source folder from the GitHub repo in addition to PowerPlatformHub.zip.
Deploy-PowerPlatformHub.ps1 in the GitHub repo is a very different script from Deploy-PowerPlatformHub.ps1 in PowerPlatformHub.zip. We noticed that there are 2 Invoke-PnPSiteTemplate calls in the PowerPlatformHub.zip version and one in 1 call in the GitHub version.

I am working with our tenant admin to try the most recent GitHub repo version of the script, but we've still been running into errors (I'll open a separate issue for these if we don't solve them).
Anyway, I'm just a little confused about the PowerPlatformHub.zip being misaligned with the GitHub version. I would understand if they were just different versions based on new updates, but the PowerPlatformHub.zip doesn't seem to work at all.

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

ID: 9ff93b5f-b80f-45e4-7d90-9d22f5c56089
Version Independent ID: 58c095c5-1963-bd82-cbca-a57ff90c91e0
Content: Create an internal Microsoft Power Platform hub - Power Platform
Content Source: power-platform/guidance/adoption/wiki-community.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Hi @lrwarren94 -
Thanks for opening the issue.
I compared both files just now - and they are both the same files. Both the zip file and the powershell file have been updated last October 17th.
The image errors are a bit misleading - because the template engine checks first if the image already exists and when there's an error (that's what you'll see when you roll out this template for the first time), it will upload the image as a new file. That's why there's that many errors. In a future update we might add a toggle to show/hide the debugging output so that it's not worrying for people who deploy the template.
Did the site get deleted at the end of running the script? Or could you see the site after running the script and seeing the errors?
Kind regards,
Daniel

Thanks @Laskewitz, looks like you're right about the files being the same. When we initially encountered errors with the original script, we modified it to add traceroutes and see what was going wrong. We must have accidentally modified or copy/pasted some of the original code in the process. Apologies for the confusion.
When we were running the original script, the site would be created, but the template would fail to apply. It would look like a normal community site with none of the custom content from the Power Platform Hub template. After the script failed, the site was not deleted--it remained and had to be manually deleted and cleared by our SharePoint admin. We repeated this while adding different traceroutes until we discovered errors like "The object id "site:812c10c9-b0ac-43d2-905c-569a1d39ed8f:web:4d2701dc-687c-4bd0-a349-a49a7cb58344" is invalid". We looked into the Source folder on the GitHub and noticed those GUIDs matched the image file names. Here are the traceroute logs (some information redacted):

2022-12-14.txt
20221214_1250.txt
20221214_1302.txt

I will go ahead and close this, though, because we eventually got the site to deploy correctly. What we had to do was revert to the original script file and run it after extracting both the contents of the template.pnp and the contents of the Source folder on GitHub to the root folder where Deploy-PowerPlatformHub.ps1 was. That gave us a clean run. After that, it had been deployed almost entirely correctly: the top bar menu navigation was missing, but we fixed that by digging through and finding a SharePoint setting that needed to be enabled. It all looks great now.
Thanks for putting this out there for the community,
Lindsey


Add WASM support

Add supporting for WASM and flutter 3.22

Thanks a lot for the contribution! I have to double-check some of the code but so far looks good. Will merge, tweak it a little bit, and deploy in the next release


STL-1669 Send tax declaration for 2021

Short Description

With this PR onwards, we send the tax declaration for the year 2021, no longer for 2020.
We also searched the whole code for occurrences of "2020". Everything that is still left, we deemed unnecessary to change as it wasn't referring to the Veranlagungsjahr, but just representing other/random dates.

Changes

Add constants for the VERANLAGUNGSJAHR
Searched for all occurrences of "2020" and replaced them by one constant
Adapt Eric namespace (the RBM namespace stays the same)
Change place in XML for the Kontoinhaber
Remove is_digitally_signed from erica + webapp
Update tax_offices list with updated tax offices returned by new Eric Version
Adapt samples
Delete unused samples in the webapp

What we didn't do

Adapt the namespace + samples + interfaces of the beleg (id) requests

Feedback

Do you think placing the constants in the utils makes sense?
Any, really

How to review this Pull Request
Link to Confluence (internal)

I just noticed that we should also adapt the server_responses in erica_app/tests/elster_client/json_respones/sample_response

Yes they're not adapted, but as far as I've seen, they also didn't change. The one occurence of "2020" is in an insufficient_privilege response which could really include any year that you didn't have the privilege to get the data from.


Release storage SDKs

The Storage Data plane SDKs have been regenerated using autorest.typescript - v4.2.3 with changes published in this PR. This PR is created to fix this issue and this issue.
The following SDKs have been regenerated and versions have been updated.

No
SDK Name
Existing Version
New Version

1
@azure/storage-blob
10.5.0
11.0.0

2
@azure/storage-file
10.3.0
10.3.1

3
@azure/storage-queue
10.3.0
10.3.1

4
@azure/storage-datalake
0.2.0
0.3.0

Commands Used
@azure/storage-blob
autorest --typescript --license-header=MICROSOFT_MIT_NO_VERSION --typescript-sdks-folder=/Users/saranganrajamanickam/Projects/azure-sdk-for-js --use=<EMAIL_ADDRESS>--package-version=11.0.0 /Users/saranganrajamanickam/Projects/Storage-XStore/src/XFE/OpenApi/Microsoft.BlobStorage/stable/2019-02-02/readme.md --output-folder=/Users/saranganrajamanickam/Projects/azure-sdk-for-js/sdk/storage/storage-blob/src/generated/

@azure/storage-file
autorest --typescript --license-header=MICROSOFT_MIT_NO_VERSION --typescript-sdks-folder=/Users/saranganrajamanickam/Projects/azure-sdk-for-js --use=<EMAIL_ADDRESS>--package-version=10.3.1 /Users/saranganrajamanickam/Projects/Storage-XStore/src/XFE/OpenApi/Microsoft.FileStorage/preview/2019-02-02/readme.md --output-folder=/Users/saranganrajamanickam/Projects/azure-sdk-for-js/sdk/storage/storage-file/src/generated/

@azure/storage-queue
autorest --typescript --license-header=MICROSOFT_MIT_NO_VERSION --typescript-sdks-folder=/Users/saranganrajamanickam/Projects/azure-sdk-for-js --use=<EMAIL_ADDRESS>--package-version=10.3.1 /Users/saranganrajamanickam/Projects/Storage-XStore/src/XFE/OpenApi/Microsoft.QueueStorage/preview/2019-02-02/README.md --output-folder=/Users/saranganrajamanickam/Projects/azure-sdk-for-js/sdk/storage/storage-queue/src/generated/

@azure/storage-datalake
autorest --typescript --license-header=MICROSOFT_MIT_NO_VERSION --typescript-sdks-folder=/Users/saranganrajamanickam/Projects/azure-sdk-for-js --use=<EMAIL_ADDRESS>--package-version=0.3.0 https://raw.githubusercontent.com/Azure/azure-rest-api-specs/6d4e0d294d568a37b1f3421b789290934517d115/specification/storage/data-plane/readme.md

We probably want to make this change in the feature/storage branch. /cc @XiaoningLiu

Storage uses swagger\README.md to specify autorest options. Could you please update that file?

We probably want to make this change in the feature/storage branch.

We should do in both master and feature/storage branches, right?

We should do in both master and feature/storage branches, right?

Yes for master if on breaking change; otherwise I am not sure whether we want a major version bump now.

there's also a npm script build:autorest in package.json that runs autorest. Need to update the version of the autorest typescript there too.

there's also a npm script build:autorest in package.json that runs autorest. Need to update the version of the autorest typescript there too.

Done. FYI.. That script will not work anyway since the readme is pointing to a non existing input file

Done. FYI.. That script will not work anyway since the readme is pointing to a non existing input file

Yes I believe it's a manual process to copy file then generate.

Yes I believe it's a manual process to copy file then generate.

I believe we'll have something like this?
https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/storage/azure-storage-blob/swagger/README.md
(With a public input-file)

We probably want to make this change in the feature/storage branch. /cc @XiaoningLiu

Storage uses swagger\README.md to specify autorest options. Could you please update that file?

feature/storage is more sutiable, master branch is in stable and breaking change is not planned before.

@sarangan12 based on the discussion we need to target feature/storage branch. We will need to use v5 of the autorest typescript extension.  Also the swagger files in the future should be from https://github.com/Azure/azure-rest-api-specs/tree/storage-dataplane-preview/specification/storage/data-plane/Microsoft.BlobStorage/preview/2019-02-02.
@XiaoningLiu & @jiacfan: any modification/we need to do on top of the swagger files from the above link?  I know we need to apply a workaround for isXML: false after the codegen.

@jiacfan Any specific swagger change needed?

Am closing this PR as we will not be regenerating the storage on the master branch.
Instead, we will focus on the v12 version which is in the feature/storage branch.


Fix empty import.

Fix for https://github.com/Azure/azure-rest-api-specs/pull/6662 to avoid generate invalid package import declaration.
@anuchandy , @jianghaolu  could you help me review this PR? Thanks.

🤖 AutoRest automatic publish job 🤖
success (version: 2.1.91)


Add SSH PATH to environment variables

It would be better to add ssh.exe and ssh-keygen.exe to environment variables in Windows instead of specifying the location of ssh in settings of tray.

Fixed.


Dockerhub account?

As far as I know this is a truly FOSS project. It would be nice to have an official dockerhub image that people can trust/use versus having to build it themselves. Do you already have an account like this: https://www.docker.com/community/open-source/application/ ?

Yeah that's a great point. Thanks for raising this up.
We have an account for onetimesecret on dockerhub but haven't been using it obviously. I'm updating the docker (and docker compose) configs concurrent with the Ruby 3 work. I haven't looked into building and pushing images via Github Actions but I imagine that's a thing. Would you be interested to help with that?

Absolutely! Can you let me know when your most recent commits have been pushed up?

Since the dockerhub image is tagged linux/arm64 it doesn't work on linux/amd64. Is that easy to change or work around? Thanks!

It probably just needs to be built for cross-platform upon publishing to dockerhub.

@venkatamutyala Exactly yeah. The latest code ready to build is v0.13.0-RC3 btw.  I pushed an arm64 image for that tagged release.
Did you want to give it a go with the github action for building these? Otherwise I'll have a look probably this weekend.

@danselmi-intecrowd The amd64 image is available now as well. Thanks for the heads up.
For anyone's interest, I followed the process documented in this very relevant docker blog post.
  # Create a new builder instance
  $ docker buildx create --use

  # Re-build the image using `buildx`
  $ docker buildx build --platform=linux/amd64,linux/arm64 . -t onetimesecret/onetimesecret -t onetimesecret/onetimesecret:next -t onetimesecret/onetimesecret:latest -t onetimesecret/onetimesecret:v0.13.0-RC3 --push


Fixes ask function, was not displaying question

Dear @m038,
Please create branch bugfix/fix-ask-function and features/adds-run-as-user-functionality before create pull request.
https://github.com/deployphp/deployer#contributing

#244 uses the proper branch structure.


chore(package): update local-repository-provider to version 1.2.31

Coverage remained the same at 81.739% when pulling c20d2692aee0ce058fbe51f71a173fc42ea5a567 on greenkeeper/local-repository-provider-1.2.31 into 45a90120654edf6d3395a1b9d3478825e0745101 on master.

:tada: This PR is included in version 7.7.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Inline Render blocking scripts

How to get time taken by the inline render blocking scripts time.
I wrote tiny inline scripts in my HTML file. I want to know the scripting time and the scripts block the parsing of the html? I am trying to know the scripting time of the inline script. But I cant the chrome dev tool takes inline scripting as parsing.

This should be asked/filed over on the main lighthouse project: https://github.com/GoogleChrome/lighthouse