[llama] llama 3 70B hangs after multiple batches of full context decode generation

Describe the bug
Consistent hang running llama3 70B demo after several batches of 32x prompts are completed, i.e. 2048 tokens decoded for 32x users multiple times. The hang sometimes occurs on the 2nd batch of 32 prompts, sometimes after 10 or more. The model forward call hangs and does not terminate.
To Reproduce
Steps to reproduce the behavior:
1 build tt-metal on commit f0534b4 (https://github.com/tenstorrent/tt-metal/tree/f0534b4467eb7ae994dfa8dbecbbabb2f6893806)
2. run llama 3 demo with looping (attached patch file: llama3_70b_demo_looping.patch
)
Expected behavior
The demo should complete all loops of decode token generation.
logs
pytest -svv models/demos/t3000/llama3_70b/demo/demo.py::test_LlamaModel_demo[wormhole_b0-True-short_context-check_disabled-sampling-tt-70b-T3000-80L-decode_only-text_completion-llama3]
...
2024-07-26 09:28:10.337 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 2045
2024-07-26 09:28:10.451 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 2046
2024-07-26 09:28:10.564 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 2047
2024-07-26 09:28:10.566 | INFO     | models.demos.t3000.llama2_70b.demo.demo:latency_printout:303 - Overall throughput: 3.4 ms @ 292.8 tokens/s
2024-07-26 09:28:10.566 | INFO     | models.demos.t3000.llama2_70b.demo.demo:latency_printout:304 - Tokens per second per user: 9.2 tokens/s/u
2024-07-26 09:28:10.566 | INFO     | models.demos.t3000.llama2_70b.demo.demo:latency_printout:305 - User latency: 109.3 ms @ 9.2 tokens/s
2024-07-26 09:28:10.574 | INFO     | models.demos.t3000.llama2_70b.demo.demo:main:108 - batch_idx: 1
2024-07-26 09:28:10.574 | WARNING  | models.demos.t3000.llama2_70b.demo.demo:run_decode:237 - Requested more output tokens than allowed by model. Truncating to 2000 output tokens.
2024-07-26 09:28:10.674 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 1
2024-07-26 09:28:10.773 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 2
2024-07-26 09:28:10.872 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 3
...
2024-07-26 09:29:05.200 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 523
2024-07-26 09:29:05.309 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 524
2024-07-26 09:29:05.417 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 525
2024-07-26 09:29:05.526 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 526
2024-07-26 09:29:05.634 | INFO     | models.demos.t3000.llama2_70b.demo.demo:run_decode:261 - Loop 527
-> hung for over 10 minutes before I killed process

Please complete the following environment information:

OS: Ubuntu 20.04
Version of software: f0534b4467eb7ae994dfa8dbecbbabb2f6893806
firmware bundle: <IP_ADDRESS>
tt-kmd: 1.28

Additional context
Possible issues with Ethernet on latest firmware.

@pavlejosipovic could this be a di/dt issue? If so, anything you can recommend?

@tstescoTT I just ran my demo with your patch and was able to run it for the complete 2048 loops. Commenting here for visibility. Lets sync on what might be different.

Thanks for posting @ksriv001, any info helps. I'm testing on https://github.com/tenstorrent/tt-metal/commit/1b62f170c35e29a66c37c1a824e7b7682779b81f now. Was this just main at the time you pulled or was there a reason for using this specific commit SHA?

@tstescoTT Sure, no problem! Yes it was just the main when I pulled this morning.

I am very happy to report that after rebuilding on https://github.com/tenstorrent/tt-metal/commit/1b62f170c35e29a66c37c1a824e7b7682779b81f I no longer get the hang after running 10x batches and counting.
2024-08-08 19:41:32.178 | INFO     | __main__:run_decode:248 - Loop 2045
2024-08-08 19:41:32.287 | INFO     | __main__:run_decode:248 - Loop 2046
2024-08-08 19:41:32.397 | INFO     | __main__:run_decode:248 - Loop 2047
2024-08-08 19:41:32.508 | INFO     | __main__:latency_printout:306 - Overall throughput: 3.4 ms @ 298.2 tokens/s
2024-08-08 19:41:32.509 | INFO     | __main__:latency_printout:307 - Tokens per second per user: 9.3 tokens/s/u
2024-08-08 19:41:32.509 | INFO     | __main__:latency_printout:308 - User latency: 107.3 ms @ 9.3 tokens/s
2024-08-08 19:41:32.516 | INFO     | __main__:main:125 - finished batch: 10.
2024-08-08 19:41:32.516 | INFO     | __main__:main:115 - starting batch: 11, n_users:= 32
2024-08-08 19:41:32.516 | WARNING  | __main__:run_decode:235 - Requested more output tokens than allowed by model. Truncating to 1938 output tokens.
2024-08-08 19:41:32.517 | INFO     | __main__:run_decode:248 - Loop 1
2024-08-08 19:41:32.618 | INFO     | __main__:run_decode:248 - Loop 2
2024-08-08 19:41:32.718 | INFO     | __main__:run_decode:248 - Loop 3
2024-08-08 19:41:32.818 | INFO     | __main__:run_decode:248 - Loop 4
2024-08-08 19:41:32.919 | INFO     | __main__:run_decode:248 - Loop 5
2024-08-08 19:41:33.020 | INFO     | __main__:run_decode:248 - Loop 6
2024-08-08 19:41:33.119 | INFO     | __main__:run_decode:248 - Loop 7
2024-08-08 19:41:33.218 | INFO     | __main__:run_decode:248 - Loop 8

@tstescoTT do you know what is the machine that you've run it on when reporting the issue, and what is the machine that you've run it to verify that it doesn't exist on main? Also, @ksriv001 what is the machine that used as well?
di/dt seems to be machine(chip)-specific, so it's quite possible that things work on one machine, and not on antother one

It's the same machine that had the hang previously f10cs02, same firmware and tt-kmd also.

BTW, I tested last on v0.51.0-rc19 before https://github.com/tenstorrent/tt-metal/commit/1b62f170c35e29a66c37c1a824e7b7682779b81f.

That's great :) Thanks

running llama 3.1 70B I just hit:
2024-08-09 08:29:52.710 | INFO     | __main__:run_decode:248 - Loop 2044
2024-08-09 08:29:52.819 | INFO     | __main__:run_decode:248 - Loop 2045
2024-08-09 08:29:52.928 | INFO     | __main__:run_decode:248 - Loop 2046
2024-08-09 08:29:53.037 | INFO     | __main__:run_decode:248 - Loop 2047
2024-08-09 08:29:53.146 | INFO     | __main__:latency_printout:302 - Overall throughput: 3.3 ms @ 305.9 tokens/s
2024-08-09 08:29:53.146 | INFO     | __main__:latency_printout:303 - Tokens per second per user: 9.6 tokens/s/u
2024-08-09 08:29:53.146 | INFO     | __main__:latency_printout:304 - User latency: 104.6 ms @ 9.6 tokens/s
2024-08-09 08:29:53.152 | INFO     | __main__:main:125 - finished batch: 9.
2024-08-09 08:29:53.153 | INFO     | __main__:main:115 - starting batch: 10, n_users:= 32
2024-08-09 08:29:53.153 | WARNING  | __main__:run_decode:235 - Requested more output tokens than allowed by model. Truncating to 1564 output tokens.
2024-08-09 08:29:53.154 | INFO     | __main__:run_decode:248 - Loop 1
2024-08-09 08:29:53.257 | INFO     | __main__:run_decode:248 - Loop 2
2024-08-09 08:29:53.357 | INFO     | __main__:run_decode:248 - Loop 3
2024-08-09 08:29:53.459 | INFO     | __main__:run_decode:248 - Loop 4
2024-08-09 08:29:53.561 | INFO     | __main__:run_decode:248 - Loop 5
2024-08-09 08:29:53.662 | INFO     | __main__:run_decode:248 - Loop 6
...
2024-08-09 08:30:08.430 | INFO     | __main__:run_decode:248 - Loop 155
2024-08-09 08:30:08.530 | INFO     | __main__:run_decode:248 - Loop 156
2024-08-09 08:30:08.630 | INFO     | __main__:run_decode:248 - Loop 157
2024-08-09 08:30:08.729 | INFO     | __main__:run_decode:248 - Loop 158
2024-08-09 08:30:08.829 | INFO     | __main__:run_decode:248 - Loop 159
2024-08-09 08:30:08.928 | INFO     | __main__:run_decode:248 - Loop 160
2024-08-09 08:30:09.028 | INFO     | __main__:run_decode:248 - Loop 161
2024-08-09 08:30:09.128 | INFO     | __main__:run_decode:248 - Loop 162
2024-08-09 08:30:09.229 | INFO     | __main__:run_decode:248 - Loop 163
2024-08-09 08:30:09.330 | INFO     | __main__:run_decode:248 - Loop 164
2024-08-09 08:30:09.430 | INFO     | __main__:run_decode:248 - Loop 165
2024-08-09 08:30:09.531 | INFO     | __main__:run_decode:248 - Loop 166
2024-08-09 08:30:09.634 | INFO     | __main__:run_decode:248 - Loop 167
2024-08-09 08:30:09.734 | INFO     | __main__:run_decode:248 - Loop 168
2024-08-09 08:30:09.834 | INFO     | __main__:run_decode:248 - Loop 169
2024-08-09 08:30:09.934 | INFO     | __main__:run_decode:248 - Loop 170
2024-08-09 08:30:10.034 | INFO     | __main__:run_decode:248 - Loop 171
libc++abi: terminating due to uncaught exception of type std::runtime_error: Read 0xffffffff from PCIE: you should reset the board.
Aborted (core dumped)

and when attempting reset:
(.venv) :~/tt-smi$ tt-smi -r 0,1,2,3
 Starting pci link reset on WH devices at pci indices: 0, 1, 2, 3
 Failed to recover WH chip, please reboot the system to reset the chip. Exiting...
(.venv) :~/tt-smi$ ll /dev/tenstorrent/
total 0
drwxr-xr-x  2 root root    120 Aug  6 20:25 ./
drwxr-xr-x 21 root root   4180 Aug  6 20:25 ../
crw-rw-rw-  1 root root 236, 0 Aug  6 20:25 0
crw-rw-rw-  1 root root 236, 1 Aug  6 20:25 1
crw-rw-rw-  1 root root 236, 2 Aug  6 20:25 2
crw-rw-rw-  1 root root 236, 3 Aug  6 20:25 3

Ok this defintely smells like di/dt. @davorchap @ttmtrajkovic

after rebooting the host I'm only seeing 3 of the 4 n300s come back up
$ ll /dev/tenstorrent/
total 0
drwxr-xr-x  2 root root    100 Aug  9 16:53 ./
drwxr-xr-x 21 root root   4180 Aug  9 16:53 ../
crw-rw-rw-  1 root root 236, 0 Aug  9 16:53 0
crw-rw-rw-  1 root root 236, 1 Aug  9 16:53 1
crw-rw-rw-  1 root root 236, 2 Aug  9 16:53 2

If you haven't, you may need a cold boot to bring all 4 devices back

Cold boot brought back the 4th card.
I reproduced the same issue on v0.51.0-rc26:
2024-08-09 12:53:19.112 | INFO     | __main__:run_decode:248 - Loop 2044
2024-08-09 12:53:19.222 | INFO     | __main__:run_decode:248 - Loop 2045
2024-08-09 12:53:19.332 | INFO     | __main__:run_decode:248 - Loop 2046
2024-08-09 12:53:19.441 | INFO     | __main__:run_decode:248 - Loop 2047
2024-08-09 12:53:19.551 | INFO     | __main__:latency_printout:302 - Overall throughput: 3.3 ms @ 303.7 tokens/s
2024-08-09 12:53:19.552 | INFO     | __main__:latency_printout:303 - Tokens per second per user: 9.5 tokens/s/u
2024-08-09 12:53:19.552 | INFO     | __main__:latency_printout:304 - User latency: 105.4 ms @ 9.5 tokens/s
2024-08-09 12:53:19.559 | INFO     | __main__:main:125 - finished batch: 5.
2024-08-09 12:53:19.560 | INFO     | __main__:main:115 - starting batch: 6, n_users:= 32
2024-08-09 12:53:19.560 | WARNING  | __main__:run_decode:235 - Requested more output tokens than allowed by model. Truncating to 1929 output tokens.
2024-08-09 12:53:19.561 | INFO     | __main__:run_decode:248 - Loop 1
2024-08-09 12:53:19.679 | INFO     | __main__:run_decode:248 - Loop 2
2024-08-09 12:53:19.779 | INFO     | __main__:run_decode:248 - Loop 3
2024-08-09 12:53:19.879 | INFO     | __main__:run_decode:248 - Loop 4
2024-08-09 12:53:19.979 | INFO     | __main__:run_decode:248 - Loop 5
2024-08-09 12:53:20.079 | INFO     | __main__:run_decode:248 - Loop 6
2024-08-09 12:53:20.180 | INFO     | __main__:run_decode:248 - Loop 7
2024-08-09 12:53:20.279 | INFO     | __main__:run_decode:248 - Loop 8
2024-08-09 12:54:16.215 | INFO     | __main__:run_decode:248 - Loop 562
2024-08-09 12:54:16.321 | INFO     | __main__:run_decode:248 - Loop 563
libc++abi: terminating due to uncaught exception of type std::runtime_error: Read 0xffffffff from PCIE: you should reset the board.
Aborted (core dumped)

This time, tt-smi -r 01,2,3 worked:
(.venv) ~/tt-smi$ tt-smi -r 0,1,2,3
 Starting pci link reset on WH devices at pci indices: 0, 1, 2, 3
 Finishing pci link reset on WH devices at pci indices: 0, 1, 2, 3
 Re-initializing boards after reset....
 Detected Chips: 8

Hit the same crash after 29 batches of 32x prompts this time on Llama 3 70B. Cold boot required to bring all 4 cards up again.

Testing using the experimental firmware bundle <IP_ADDRESS> (https://github.com/tenstorrent/tt-firmware/blob/6154c3f999b22072d6f6ac193559e73f1e490116/experiments/fw_pack-<IP_ADDRESS>.fwbundle) with decrease max AICLK to 900MHz appears to resolve the issue.
I tested running 15x25 + 23 = 398 batches (12,736 sample prompt completions, ~26M decode loops):
2024-08-15 10:40:11.483 | INFO     | __main__:run_decode:248 - Loop 2045
2024-08-15 10:40:11.597 | INFO     | __main__:run_decode:248 - Loop 2046
2024-08-15 10:40:11.711 | INFO     | __main__:run_decode:248 - Loop 2047
2024-08-15 10:40:11.825 | INFO     | __main__:latency_printout:302 - Overall throughput: 3.5 ms @ 287.7 tokens/s
2024-08-15 10:40:11.825 | INFO     | __main__:latency_printout:303 - Tokens per second per user: 9.0 tokens/s/u
2024-08-15 10:40:11.825 | INFO     | __main__:latency_printout:304 - User latency: 111.2 ms @ 9.0 tokens/s
2024-08-15 10:40:11.831 | INFO     | __main__:main:125 - finished batch: 22.
2024-08-15 10:40:11.832 | INFO     | __main__:main:115 - starting loop: 15, batch: 23, n_users:= 32
2024-08-15 10:40:11.832 | WARNING  | __main__:run_decode:235 - Requested more output tokens than allowed by model. Truncating to 2014 output tokens.
2024-08-15 10:40:11.833 | INFO     | __main__:run_decode:248 - Loop 1
2024-08-15 10:40:11.936 | INFO     | __main__:run_decode:248 - Loop 2
2024-08-15 10:40:12.039 | INFO     | __main__:run_decode:248 - Loop 3
2024-08-15 10:40:12.142 | INFO     | __main__:run_decode:248 - Loop 4
2024-08-15 10:40:12.245 | INFO     | __main__:run_decode:248 - Loop 5
2024-08-15 10:40:12.348 | INFO     | __main__:run_decode:248 - Loop 6

An apparent performance degration of ~5% is observed (9.5 t/s/u to 9.0 t/s/u). This is anticipated given the reduced frequency.


PI-1236 Fix install issue for new users

We removed config.js from the plugin.  cloudflare_update.sh checks for config.js in order to update. In this PR it we check composer.json instead.

I've re-run CI.

Going to merge!


New theme: Materialize-BP hugo theme

Theme submission
Link to my theme repository: https://github.com/spech66/materialize-bp-hugo-theme
I made sure that...

[x] the repository contains a good README.md describing my theme
[x] an open source license has been added to LICENSE.md
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

N.B. By submitting a theme to the Hugo Themes Showcase you understand that you need to maintain your theme. You will need to keep an eye on whether your theme's demo generates on the Hugo website, whenever there is a new release. We are a very small team and we just cannot keep up opening issues in the various theme repositories to notify authors. Whenever a theme demo breaks and remains broken then at some point it will be removed from the list without prior warning. If you no longer wish to maintain a theme please let us know.
--

Theme is based on my other themes. e.g. bootstrap-bp-hugo-theme.
Submission is already including changes from https://github.com/gohugoio/hugoThemes/issues/682
The latest example page uses baseURL = "https://gohugo.io/" but submission guidelines requires example.org. What is the correct url?
Submission would like to have LICENSE file as md file but GitHub requires the non md version for displaying the License short information. Currently all themes of mine include both versions. Are there plans to combine this?

PS: Thank you for maintaining all this :-)

@spech66
Thank you for the theme submission. Your theme looks fine!
I have only noticed the following minor issue:

In line 11 of theme.toml please change the min_version attribute to 0.57.0 (Hugo now uses semver versioning and its format is required.

Once you do this please let me know so that I can add your theme to the showcase.

@onedrawingperday thank you for the reply I changed the version number on all of my themes including this one.

@spech66 I have added your theme to the repo.
Next, @digitalcraftsman will promote your theme on Twitter, through Hugo's official account in the coming days.

Thank you! @onedrawingperday

@spech66 your theme has now been promoted on Hugo's official Twitter account.


⚠ Bofrost.be has degraded performance

In 4ec494b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1484 ms

Resolved: Bofrost.be performance has improved in 59ea182.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.11 to before v5.13.4",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a28b2bfc099c6b9caa6ef697660408e076a32019",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e1b2b2b61d30d7ce057ec17237c217d152ed97f2"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "a28b2bfc099c6b9caa6ef697660408e076a32019",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "e1b2b2b61d30d7ce057ec17237c217d152ed97f2",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "cpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.13.4 by commit e1b2b2b61d30d7ce057ec17237c217d152ed97f2, it was introduced in version v5.11 by commit a28b2bfc099c6b9caa6ef697660408e076a32019. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001181


Search in caskroom/fonts doesn't work properly

~ brew tap
homebrew/dupes
homebrew/versions
phinze/cask
~ brew tap caskroom/fonts
Cloning into '/usr/local/Library/Taps/caskroom-fonts'...
remote: Reusing existing pack: 3277, done.
remote: Counting objects: 145, done.
remote: Compressing objects: 100% (145/145), done.
remote: Total 3422 (delta 92), reused 0 (delta 0)
Receiving objects: 100% (3422/3422), 508.39 KiB | 285.00 KiB/s, done.
Resolving deltas: 100% (1930/1930), done.
Checking connectivity... done.
Tapped 0 formula
~ brew cask search font
==> Partial matches
dfontsplitter	    fontexplorer-x-pro	fontprep	    monotype-skyfonts

The last command should have given me all the fonts, no?
Either the manual isn't clear, or I'm doing something wrong.
Here's my cask's doctor:
~ brew cask doctor
==> OS X Version:
10.9.2
==> Hardware Architecture:
intel-64
==> Ruby Version:
1.8.7-p358
==> Ruby Path:
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
==> Homebrew Version:
0.9.5
==> Homebrew Executable Path:
/usr/local/bin/brew
==> Homebrew Cellar Path:
/usr/local/Cellar
==> Homebrew-cask Version:
0.31.0
==> Contents of $LOAD_PATH:
/usr/local/Cellar/brew-cask/0.31.0/rubylib
/usr/local/Library/Homebrew
/usr/local/Library/Homebrew/vendor
/Library/Ruby/Site/1.8
/Library/Ruby/Site/1.8/powerpc-darwin13.0
/Library/Ruby/Site/1.8/universal-darwin13.0
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/vendor_ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/vendor_ruby/1.8/universal-darwin13.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/powerpc-darwin13.0
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin13.0
.
==> Contents of $RUBYLIB Environment Variable:
nil
==> Contents of $RUBYOPT Environment Variable:
nil
==> Contents of $RUBYPATH Environment Variable:
nil
==> Contents of $RBENV_VERSION Environment Variable:
nil
==> Contents of $GEM_HOME Environment Variable:
nil
==> Contents of $GEM_PATH Environment Variable:
nil
==> Contents of $BUNDLE_PATH Environment Variable:
nil
==> Running As Privileged User:
No

This is no longer the case.

i don't even have a mac anymore XD


shell: adc: adc shell for testing adcs

The adc shell makes it possible to configure ADC_0 and ADC_1 for testing
purposes. It includes helpful printouts if the number of arguments is
wrong.
Signed-off-by: Nicolai Glud<EMAIL_ADDRESS>

Codecov Report

Merging #12100 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #12100   +/-   ##
=======================================
  Coverage   48.07%   48.07%
=======================================
  Files         284      284
  Lines       43328    43328
  Branches    10389    10389
=======================================
  Hits        20828    20828
  Misses      18363    18363
  Partials     4137     4137

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bd34448...b60ff21. Read the comment docs.

+1 for this addition. Currently, we do not have any samples for easy testing of ADC functionality.

Changes since last push: I have made the changes requested and made reference and gain tab completion.

@Kludentwo If you can address the issues of missing calls to shell_error() when a shell command encounters an error, I think this is good to go in.

Lists are now const. I have tried resolving the comments for changes that have been made.

I have submitted a PR for adding a sample for showcasing and compile testing of the ADC shell functionality in #17165.


How can I use HttpClientImageDownloader?

I want to change HttpURLConnection to HttpClient to achieve connection keep-alive.
I known that I can use HttpClientImageDownloader, but I don't known how to use.
Are there some sample code for using HttpClientImageDownloader?
Thank you.

Sorry, it is easy to use by HttpClientImageDownloader.
I modify createImageDownloader method in DefaultConfigurationFactory.java as follows,
/** Creates default implementation of {@link ImageDownloader} - {@link BaseImageDownloader} */
public static ImageDownloader createImageDownloader(Context context) {
	SchemeRegistry schemeRegistry = new SchemeRegistry();
	schemeRegistry.register(new Scheme("http", PlainSocketFactory.getSocketFactory(), 80));
	schemeRegistry.register(new Scheme("https", new EasySSLSocketFactory(), 443));

	HttpParams params = new BasicHttpParams();
	params.setParameter(ConnManagerPNames.MAX_TOTAL_CONNECTIONS, 30);
	params.setParameter(ConnManagerPNames.MAX_CONNECTIONS_PER_ROUTE, new ConnPerRouteBean(30));
	params.setParameter(ConnManagerPNames.TIMEOUT, 10000);
	params.setParameter(HttpProtocolParams.USE_EXPECT_CONTINUE, false);
	HttpProtocolParams.setVersion(params, HttpVersion.HTTP_1_1);

	ClientConnectionManager cm = new ThreadSafeClientConnManager(params, schemeRegistry);
	HttpClient client = new DefaultHttpClient(cm, params);

	return new HttpClientImageDownloader(context, client);
}


[Enhancement]: Ollama module

Problem
Its not having an Ollama module.
I realize that my POC here needs to have a discussion of design and features, but its a fun litte thing
Solution
Make a module, here's a prototype of Ollama working with Testcontainers in LinqPad 8:
Deps the nugets Testcontainers and OllamaSharp

var container = new ContainerBuilder()
	.WithName("ollama-container")
	.WithImage("ollama/ollama")
	.WithPortBinding(11434, 11434)
	.WithVolumeMount("ollama", "/root/.ollama")
	.WithExposedPort(11434)
	.Build();

var keepAlive = true;

container.Started += async (sender, args) =>
{
	Console.WriteLine("Container started");
	try
	{
		Console.WriteLine("Start ollama service");
		await container.ExecAsync(new List<string>() {
			"ollama run llama2"
		});
		var result = await RunAsync();
		result.Dump();
	}
	catch (Exception ex)
	{
		Console.WriteLine(ex);
	}

	keepAlive = false;
};

await container.StartAsync();

while (!QueryCancelToken.IsCancellationRequested && keepAlive)
{
	await Task.Delay(1000);
}

var logs = await container.GetLogsAsync();

await container.StopAsync();
await container.DisposeAsync();

async Task<string> RunAsync()
{
	try
	{
		var client = new OllamaApiClient("http://localhost:11434/api/generate", "llama2");
		ChatRequest request = new ChatRequest();
		request.Messages ??= new List<Message>();
		request.Messages.Add(new Message(ChatRole.User, "Write me a dad-joke about cats please?", Enumerable.Empty<string>().ToArray()));
		request.Model = "llama2";
		request.Stream = false;
		var messages = new List<ChatResponseStream>();
		var responses = await client.SendChat(request, x => messages.Add(x));
		return string.Join("\n\n", responses.Select(r => r.Content));
	}
	catch (Exception ex)
	{
		return ex.ToString();
	}
}

Benefit
Its really cool
Alternatives
To be less cool
Would you like to help contributing this enhancement?
Yes

The output from a non-initial run:

[testcontainers.org 00:00:00.07] Connected to Docker:
Host: npipe://./pipe/docker_engine
Server Version: 24.0.7
Kernel Version: <IP_ADDRESS>-microsoft-standard-WSL2
API Version: 1.43
Operating System: Docker Desktop
Total Memory: 62.39 GB
[testcontainers.org 00:00:00.30] Docker container 042f3c377795 created
[testcontainers.org 00:00:00.35] Start Docker container 042f3c377795
[testcontainers.org 00:00:01.67] Wait for Docker container 042f3c377795 to complete readiness checks
[testcontainers.org 00:00:01.69] Docker container 042f3c377795 ready
[testcontainers.org 00:00:01.73] Docker container a9d04460af00 created
[testcontainers.org 00:00:01.76] Start Docker container a9d04460af00
[testcontainers.org 00:00:02.01] Wait for Docker container a9d04460af00 to complete readiness checks
[testcontainers.org 00:00:02.02] Docker container a9d04460af00 ready
Container started
Start ollama service
[testcontainers.org 00:00:02.03] Execute "ollama run llama2" at Docker container a9d04460af00
Write me a dad-joke about cats please?
Why did the cat join a band? Because he wanted to be the purr-cussionist! 😹
[testcontainers.org 00:00:08.85] Stop Docker container a9d04460af00
[testcontainers.org 00:00:09.24] Delete Docker container a9d04460af00

Hi 👋, thanks for creating the request.
Total Memory: 62.39 GB

This sounds like you are running a pretty nice machine 😄.
Since you are interested in contributing the Ollama module, which is great, I would like to share some additional information. You will find a basic guide about implementing a module here. All of our existing modules can be used as a blueprint too. All of them follow our best practices, which are necessary for a smoothly working module across various systems, etc.
If you have any further questions, do not hesitate to reach out to me or the other developers in our Testcontainers community on Slack.

If you have any further questions, do not hesitate to reach out to me or the other developers in our Testcontainers community on Slack.

So i spent the day, (in the few moments between my dayjob's demands for attention), got it pretty nice, then when I was going to go through the best practices, and there's a stumbling block for. I might not need Volume to be statically named, but a default and configurable one would save on time as the there are resources downloaded.
From the best practices:

Avoid assigning static names to Docker resources such as containers, networks, and volumes. Static names may clash with existing resources, causing tests to fail. Instead, use random assigned names. By default, Docker assigns random names.

I will make the PR, and link this issue and we can discuss when actually looking at the

Is there any update on this?

We had some technical limitations adding more modules to the repository. We have partially addressed this issue (https://github.com/testcontainers/testcontainers-dotnet/issues/1136). Right now, I have a couple of days off, so I might find some time to do reviews, but I am not prioritizing it and plan to spend the time with family. Module PRs are not critical in my opinion; developers can always fall back to the generic container builder and use the configurations from Init() (in the PR). I am aware that there are a couple of modules waiting for review, and I will try to address them after my time off. I try to address urgent bugs or blockers as soon as possible.


git is not recognized error

I keep getting the following issue when I try to clone the repository
git clone https://github.com/SevaSk/ecoute
the following error occurs
it : The term 'git' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1

git clone https://github.com/SevaSk/ecoute

  + CategoryInfo          : ObjectNotFound: (git:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

Hey! you seem new but you need to install git to download a GitHub projects. There are many tutorial online. Good luck!

Hey SevaSk/ecoute,
Yeah I got into it not too long ago and I apologize if I have caused you
any inconvenience,
I ran into one more issue while trying to run "python main.py"
PS C:\Windows\system32\ecoute> python main.py
C:\Users\onlya\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\whisper\timing.py:57:
NumbaDeprecationWarning: The 'nopython' keyword argument was not supplied
to the 'numba.jit' decorator. The implicit default value for this argument
is currently False, but it will be changed to True in Numba 0.59.0. See
https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-object-mode-fall-back-behaviour-when-using-jit
for details.
@numba.jit
Traceback (most recent call last):
File "C:\Windows\system32\ecoute\main.py", line 3, in
from GPTResponder import GPTResponder
File "C:\Windows\system32\ecoute\GPTResponder.py", line 2, in
from keys import OPENAI_API_KEY
File "C:\Windows\system32\ecoute\keys.py", line 1
OPENAI_API_KEY=" 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
^
SyntaxError: unterminated string literal (detected at line 1)
PS C:\Windows\system32\ecoute>
I hope I wont take any more of your time,
Thanks man and I really appreciate the work you have done!
-Ash
On Tue, Jun 6, 2023 at 8:21 PM Seva @.***> wrote:

Closed #75 https://github.com/SevaSk/ecoute/issues/75 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/SevaSk/ecoute/issues/75#event-9452062854, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BALF3LWV4YAYNXBZRCFCFZ3XJ7CRTANCNFSM6AAAAAAY3ZN2RQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey SevaSk/ecoute,
Yeah I got into it not too long ago and I apologize if I have caused you
any inconvenience,
I ran into one more issue while trying to run "python main.py"
I hope I wont take any more of your time,
Thanks man and I really appreciate the work you have done!
-Ash
PS C:\Windows\system32\ecoute> python main.py
C:\Users\onlya\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\whisper\timing.py:57: NumbaDeprecationWarning: The 'nopython' keyword argument was not supplied to the 'numba.jit' decorator. The implicit default value for this argument is currently False, but it will be changed to True in Numba 0.59.0. See https://numba.readthedocs.io/en/stable/reference/deprecation.html#deprecation-of-object-mode-fall-back-behaviour-when-using-jit for details.
@numba.jit
Traceback (most recent call last):
File "C:\Windows\system32\ecoute\main.py", line 3, in
from GPTResponder import GPTResponder
File "C:\Windows\system32\ecoute\GPTResponder.py", line 2, in
from keys import OPENAI_API_KEY
File "C:\Windows\system32\ecoute\keys.py", line 1
OPENAI_API_KEY=" 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
^
SyntaxError: unterminated string literal (detected at line 1)


Team Meetings

Core Team Meetings
Every other Tuesday at 10:30AM PST
All meetings will start with a progress updates from the team members, with a focus on the assignees for in-progress milestone tasks.
3-26-24

[x] Update Meeting Topics document with Rhonda's progress [This subtask is now a default]
[x] Create meeting agenda
[x] Attach agenda to Google Calendar event
[x] Compile meeting notes
[x] Assign action items as tasks

All action items assigned.


npm audit gives malware warning?

When installing @piwikpro/ngx-piwik-pro, npm audit throws a critical warning.
(i needed to install it with --force, because of issue #9: angular 14/15 support)
piwik-pro-angular-tracking  *
Severity: critical
Malware in piwik-pro-angular-tracking - https://github.com/advisories/GHSA-93jq-pwrf-g6h6
No fix available
node_modules/piwik-pro-angular-tracking

The report is for all versions, not just the latest, or a specific fork
(Apologies to @andrii-lundiak, because i first thought the problem was in his PR #11, but it appears to be in all versions)
I looked through the code, and havent found anything suspicious myself, but this is very worrying

No worries @koesper I got ur first comment right. Anyhow thank you for ANY feedback here, coz I believe it will increase a chance to get attention to the problem - on any levels this package has.

@andrii-lundiak I noticed that, and had the same result on my fork, where i basically copied the changes in your pullrequest.
I'm running the LTS versions:
npm --version
9.5.0
node --version
v18.14.2

And btw @koesper if you DIRECTLy install piwik-pro-angular-tracking then yesy it's kinda suspisios component:
its readme:
# Security holding package

This package contained malicious code and was removed from the registry by the npm security team. A placeholder was published to ensure users are not affected in the future.

Please refer to www.npmjs.com/advisories?search=piwik-pro-angular-tracking for more information.

its package.json:
{
  "name": "piwik-pro-angular-tracking",
  "version": "0.0.1-security",
  "description": "security holding package",
  "repository": "npm/security-holder"
}

Yes, @piwikpro/ngx-piwik-pro is NOT the sameas.
but YES @piwikpro/ngx-piwik-pro package.json DOES HAVE wrong name:

I noticed the naming discrepancy too, but wasn't sure if that was the problem.
But it does explain that i cant actually find the malicious code, since that only exists in the deleted piwik-pro-angular-tracking package.
I'm also looking into the source of each of the npm published versions, in everyone the name in the package.json is correct: "name": "@piwikpro/ngx-piwik-pro",.
Only the first version v0.0.9, i havent been able to check, since NPM is still building the file list https://www.npmjs.com/package/@piwikpro/ngx-piwik-pro/v/0.0.9?activeTab=explore

@koesper FYI :)
https://github.com/PiwikPRO/ngx-piwik-pro/pull/13

I'm trying to reproduce the steps, gimme a minute

I also executed npm ci and no audit warnings:

@koesper Also try to:
npm i git@github.com:andrii-lundiak/ngx-piwik-pro.git#4ee9734b44ab3ee751593f595198796fc17aa389

meaning that you will get package AFTER my change in scope of this PR. U know.
But that branch is based on master and on NodeJS v10 API, so you Node v18 will BREAK lock file. You have to have OLD nodejs to be on the same conditions as package itself.
As you see I do have OK again:

I think i'm going crazy, i've been able to reproduce this from scratch multiple times, but now my audit is not giving errors anymore..
what i did was:
npx @angular/cli@13 new myProject
cd myProject
npm i @piwikpro/ngx-piwik-pro
vi package.json #to check if it was actually installed
npm audit

and then i got that error.
i forced angular-cli to use a old version, to get around the versioning problem, but i've also done it with 'regular' v15, or with an ancient v9.
sometimes i needed to use --force or --legacy-peer-deps, to force it to install.
perhaps cleaning my npm cache triggered it to reload the audit data? i'm very confused, because now i cant reproduce it anymore.
But i do feel that your pullrequests should solve the problems!
#11 to fix the versioning
#13 to get rid of all references to the package-name-squatting malware
Thanks for going on this adventure with me @andrii-lundiak ! I've learned a lot today about NPM security

First of all --force is a sign that Angular packages DO MISMATCH OR some packages DO have legacy dependencies. It's not ur problem for sure :) As soon as u have to use --force AFTER installing PIWIK package, that is PIWIK's issue for 100%. Calm down :)

@koesper  Second of all, if you use npx for basic setup, I am not sure what version npx u have locally and what version of npm npx would pick up. I personally AVOID using npx. And clean Node / npm versions for Angular v13 Project setup should be at least 100% same as for PIWIK package. To be clean.

@koesper And 3) sire, if u did npm cache clean --force than you may have got rid of cached version of SOME package, not necessary of POWIK or ng-xyz... Just some... Then npm audit may regenerate new result.


run_rolling in damask should be just run

cf. title

Hi @samwaseda , is it possible to rewrite or and new function in the subclass.run() call. The reason to use run_rolling instead of job.run() itself is that, we want to have some specific function in run_rolling().

Yes, we have to define run_static, but I guess I can take over the task.


Update azure-gaming-samples.md

Spelling mistake fixed

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sandbox/gamedev/azure-gaming-samples.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thanks for the fix!


Formatted with prettier

Codecov Report

Merging #3 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master     #3   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           5      5
  Lines          13     13
=====================================
  Hits           13     13

Impacted Files
Coverage Δ

src/colorMethods.js
100% <ø> (ø)
:arrow_up:

src/index.js
100% <ø> (ø)
:arrow_up:

src/addModifier.js
100% <100%> (ø)
:arrow_up:

src/decorateSelector.js
100% <100%> (ø)
:arrow_up:

src/makeThemeColor.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f92f932...c39390c. Read the comment docs.

Released as v1.0.3.


create group fix

seed data for groupsite using group slugs to get dynamic group id

Remove secrets from appsettings please


Automated cherry pick of #3690: remove useless aws instance type config

Cherry pick of #3690 on release/2.13.
#3690: remove useless aws instance type config

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.13@2247b71). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.13   #3692   +/-   ##
==============================================
  Coverage                ?   6.95%
==============================================
  Files                   ?     499
  Lines                   ?   83896
  Branches                ?       0
==============================================
  Hits                    ?    5835
  Misses                  ?   77564
  Partials                ?     497

Flag
Coverage Δ

#aFlag
6.95% <0%> (?)

Impacted Files
Coverage Δ

pkg/multicloud/aws/region.go
0% <ø> (ø)

pkg/compute/models/skus.go
1.29% <0%> (ø)

pkg/multicloud/aws/host.go
0% <0%> (ø)

pkg/compute/guestdrivers/managedvirtual.go
0% <0%> (ø)

pkg/multicloud/aws/instance.go
0% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2247b71...665f526. Read the comment docs.

/approve
/lgtm


Accuracy problem

I am very happy to see such an excellent work. I am very interested in your article.
But I use your code, without any changes, the running results always change, and it is difficult to have an accuracy of 65.4%, why is this?
Thank you very much

Sorry for the late reply. This variability is mainly due to random initialization of the network parameter, a well-known "problem" of these neural methods.


[v4] Link's rerendering on naviagte

Based on output from why did you update, it would seems all Link's are rerendered on nagivate. If their active state didn't change, might this be avoidable?

Dupe of #3985, and there is a PR open for it: #3986

Thanks. The PR addresses links that are active agnostic. What about those that aren't - is there anything to prevent them from rerendering when their active state doesn't update?


Add statistics

Add statistics

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.66%. Comparing base (620a77e) to head (f0cdd87).
Report is 11 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #199      +/-   ##
==========================================
+ Coverage   99.65%   99.66%   +0.01%
==========================================
  Files           4        4
  Lines         286      296      +10
  Branches       30       31       +1
==========================================
+ Hits          285      295      +10
  Misses          1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Turn on greenkeeper

This is one for @dlmanning to do

Most of the time enabling a repository is straight forward – just execute greenkeeper enable. In some cases, especially when there are private repositories or permissions involved, it can fail. Fear not. This guide will walk you through all the required steps.
If you can’t get your repository enabled after these steps please contact us. greenkeeper support

If you want to enable a private repository for the first time make sure to grant Greenkeeper the necessary rights by running greenkeeper login --force --private.
With GitHub’s new permission model you need to grant Greenkeeper access per organization. You can do this with greenkeeper access.
Keep in mind that you need admin access to a repository to enable it. If you don’t have access please ask someone on your team for help.

✅


No simple solution for secure content when dropwizard is deployed behind a reverse proxy

When a dropwizard application is deployed behind a reverse proxy that also offloads TLS, the http connector is perfectly capable of handling the x-forwarded headers set by the reverse proxy server.
So the connector will properly set the javax.servlet.ServletRequest isSecure flag to true when the request was issued using https.
However there does not appear to be a simple way to make a resource "confidential" in dropwizard.
Now you have to write a servlet filter to redirect request to the secure endpoint yourself which is quite annoying, while adding a simple annotation to your resource could handle this for you regardless whether you are using a reverse proxy setup or handle TLS directly in dropwizard.
Related issue: https://stackoverflow.com/questions/27467365/openshift-diy-dropwizard-with-https

What do you mean by "confidential"?  Do any of the new authorization-related changes in Dropwizard 0.9.x solve your issue?

A servlet engine typically defines a secure endpoint and a non secure endpoint. If you look at tomcat for example it has a non secure port, by default on port 8080, and a secure port, by default on port 8443, defined in it's configuration for this.
You can mark a servlet as "confidential". This means that if you want to access that particular servlet you'll need to access it using the secure endpoint. The port using TLS.
If you access the servlet marked "confidential" using the non secure port, the servlet engine will redirect you to the secure endpoint.
When using a reverse proxy server, you'll need to tell the servlet container whether the connection being used is secure, and if there is secure and non secure content, how to redirect to the proper endpont.
I don't know what you've fixed inn the latest version of Dropwizard, but I will try to take a look.


write-podejsonresponse

Describe the Bug
There is an abnormality in powershell 5.1 in how the convertto-json function works depending on if the item was sent via the pipeline or not
Steps To Reproduce
powershell 5.1 handles these two items differently
ConvertTo-Json @('chapterresponse') -compress
@('chapterresponse') |ConvertTo-Json -compress
Result:
["chapterresponse"]
"chapterresponse"
so if I have an object I created
$newObj=[pscustomobject]@{
name=$name
id=$id
array=@($items)
}
If that array has only one item, the json result will be a text string for that array field instead of being an array.
Expected Behavior
When an array is passed to write-podejsonresponse it returns an array always regardless of the number of items it contains
Platform

OS: [Windows]
Browser: chrome
Versions:

Pode: [e.g. Pode v2.4.2]
PowerShell: [e.g. PS5.1]

Good spot, @robertfshort!
It seems PowerShell 7 also suffers from the same issue as well, so we'll have to change it from piping to being properly passed in as a parameter.


Issue with RN 0.44.2

I'm unable to update react-native-svg to the latest react native 0.44.2. See the following error:
Unable to resolve module `AccessibilityInfo` from `PATH/node_modules/react-native/Libraries/react-native/react-native-implementation.js`: Module does not exist in the module map or in the directories:
PATH/node_modules/react-native/node_modules,
PATH/node_modules

No longer an issue with 0.44.3

0.45.1 fixes this as well. react-native-git-upgrade did the trick for me.

Apparently it's not fixed. I get this error everytime:
ld: library not found for -lRNSVG-tvOS
clang: error: linker command failed with exit code 1 (use -v to see invocation)
mateioprea$ react-native --version
react-native-cli: 2.0.1
react-native: 0.45.1
If I unlink the library everything seems fine.


Option "do not scrape duplicates"

Often, when scraping several similar queries (or one query in nearby locations), duplicates may appear in search results, resulting in duplicate entries in the output file and requiring additional time to complete the task. Is it possible to implement a parameter that prevents scraping information about an organization if it has already been scraped earlier?

hi @maksbdev ,
this sounds like a good idea.
I will try to include in the next release.
thanks for your feedback

i have made one script in py to do this


[TF 2.0 API Docs] tf.io.decode_base64

Existing Url with the issue:
https://www.tensorflow.org/versions/r2.0/api_docs/python/tf/io/decode_base64
Description of issue (what needs changing):
Clear description
For example, why should someone use this method? How is it useful?
Correct links
The link to the python script where the function is define is inactive
Wrong: python/ops/gen_string_ops.py
Correct (The file is not mentioned in the repo)
Parameters defined
Are all parameters defined and formatted correctly?
Returns defined
Are return values defined?
Raises listed and defined
Are the errors defined? For example,
https://www.tensorflow.org/versions/r2.0/api_docs/python/tf/feature_column/categorical_columErrors are not defined
Usage example
No usage example provided
Use case: (The documentation does not define how to use, when to use the symbol)

@Emanuz We are checking to see if you still need help on this issue. Could you please have a look on the link1 , link2 and let us know if it helps? Thanks


Remove scrolling iteration from versioning

@AAAlinaaa I think this needs to be ported to 9.x. Please confirm?


config generation with --outDir that doesn't exist fails

running npx amplify generate config --outDir something where "something" does not exist fails. Instead it should create the directory and write config to that location

https://github.com/aws-amplify/amplify-backend/pull/1117 addresses this


Bump mirror node image to 0.75.0-SNAPSHOT

Signed-off-by: Ivo Yankov<EMAIL_ADDRESS>Description:

Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
Base: 74.16% // Head: 74.16% // No change to project coverage :thumbsup:

Coverage data is based on head (c7d3f49) compared to base (1f9b860).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #891   +/-   ##
=======================================
  Coverage   74.16%   74.16%
=======================================
  Files          29       29
  Lines        1827     1827
  Branches      339      339
=======================================
  Hits         1355     1355
  Misses        374      374
  Partials       98       98

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

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


Azure: Update examples and README files containing Wordpress examples

Update cluster/examples and docs/ with portable Wordpress on Azure.
Part of #617
Depends on #572, #647, #648, #649
What seems to be the problem?
Examples and documentation do not exist for deploying the portable Wordpress application stack [#572] on Azure.
What could Crossplane do to help?
Examples and documentation should be updated to contain necessary YAML files and directions for deploying the portable Wordpress application stack on Azure.
What does it look like when we're done?
A user can:

Find all resource classes, network resources, and defaulting policies needed to allow the portable Wordpress stack to be provisioned on Azure.
Find documentation with instructions on how to setup Azure and install the Wordpress app stack.

Todo

[ ] Azure portable Wordpress examples created.
[ ] Azure portable Wordpress docs created.

I had problems with my Azure account and left this PR behind.  It may be a starting point for this work.
https://github.com/crossplaneio/crossplane/pull/574

Awesome, thanks @displague!

The issue would be a parent to https://github.com/crossplaneio/crossplane/issues/538 and would close https://github.com/crossplaneio/crossplane/issues/519 (so long as the GCP and AWS examples and docs haven't drifted away).

There may be some work in #574 that we could reuse for the Azure docs update, but potentially not if our docs overhaul for v0.3 is fairly drastic.

We have documentation for installing Wordpress in Azure via the services guide and the stacks guide:

https://crossplane.io/docs/v0.3/services/azure-services-guide.html
https://crossplane.io/docs/v0.3/stacks-guide-azure.html

Users should be able to copy and paste from those guides to end up with WordPress running in Azure.
So I think what's still missing from this issue is the cluster/examples yaml files, which we have for GCP and AWS, but not for Azure:
https://github.com/crossplaneio/crossplane/tree/master/cluster/examples/workloads/kubernetes/wordpress

@jbw976 I should be able to get this done and close out the issue today!


Optimize setting the data gpio bits

This change significantly cuts down on the number of accesses to the GPIO control registers. Testing shows around 800% (8x) speed improvement with this change.
Note that this does not completely resolve #1019. It simply makes it better.
Max read speed is now 166KB/sec

@akuker @nucleogenic I am missing the SonarCloud analysis for this PR. @nucleogenic Can it be that it got lost with one of your recent workflow changes?

It looks like SonarCould ran for this. I can see the results as well: https://sonarcloud.io/summary/new_code?id=akuker_PISCSI&branch=akuker_fix_1019


Update to Release 3.5 standard (pre GA)

Still in preview - breaking changes are not considered applicable.

Changes:

Inclusion of status code (due to sync).
Inclusion of account and volume property (AD and export policy)
Inclusion of missing capacityPool patch properties
ServiceLevel name change
Changed resourceGroup to resourceGroupName (correct naming for CLI features)
(internal ticket NFSAAS-1875)

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby
Nothing to generate for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js
A PR has been created for you:
https://github.com/Azure/azure-sdk-for-js/pull/1541

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5431
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5431/commits/526dc91584db52d084f0489b461dbdadd8a76f11

@kpajdzik would you take this one? thanks!

@veronicagg I will :)

If you haven't taken a look at our new onboarding experience at OpenAPIHub, it's a convenient way to create your PR when you're copying from an existing API version or when you're editing your existing specs. If you have any feedback or questions, feel free to use the feedback button on top of the site for help. Thanks!

Automation for azure-sdk-for-java
Nothing to generate for azure-sdk-for-java

@anuchandy Could you please take a look?

Automation for azure-sdk-for-java
Nothing to generate for azure-sdk-for-java

@anuchandy Could you please take a look?

Just a clarification - is Java SDK something that Microsoft will auto generate? Is it one of those handled from within the Devx OpenAPI hub for instance?

Automation for azure-sdk-for-java
Nothing to generate for azure-sdk-for-java

@anuchandy Could you please take a look?

Just a clarification - is Java SDK something that Microsoft will auto generate? Is it one of those handled from within the Devx OpenAPI hub for instance?

Yes, it is the one handled by OpenAPI portal. It included Java, Node.js (soon deprecated so no new SDKs), TypeScript, Ruby and Python.

I've provided answers for the comments but this PR is still open. Can someone either respond if there are further issues or merge please.
Thanks.

Since this is approved, is there any chance it could be merged? Thanks.


Add support for styles labels set in block.json

Feature Request

[x] Yes, I reviewed the contribution guidelines.

Describe your use case and the problem you are facing
When you set some block styles in block.json and use the wp i18n make-pot command, the generated .pot file doesn't contains the label strings.
Example:
"styles": [
	{
		"name": "default",
		"label": "Default",
		"isDefault": true
	},
	{
		"name": "subscription",
		"label": "Subscription"
	}
],

Default and Subscription are missing from the .pot file.
Describe the solution you'd like
These strings should be part of the .pot file.

Hey @benoitchantre 👋
That sounds strange. What version of wp i18n are you using? You can check using wp cli info and wp package list.
This field has long been translatable (for over 4 years) and according to this passing test the string extraction should actually be working.
Do you perhaps have some code, e.g. a GitHub Gist or repository, where this can be reproduced?

Hi @swissspidy,
My bad, there was a mistake on my side: I had an inconsistent textdomain set in block.json.
After having fixed that value, I now the the expected .pot file


[Bug]  pake fail

Search before asking

[X] 我在 issues 列表中搜索，没有找到类似的内容。
I searched in the issues and found nothing similar.

Pake version
2.1.2
Downloaded windows v0.39.0 (registry rsproxy)
Compiling proc-macro2 v1.0.60
Compiling unicode-ident v1.0.9
Compiling quote v1.0.28
Compiling autocfg v1.1.0
Compiling serde v1.0.164
Compiling cfg-if v1.0.0
Compiling syn v1.0.109
Compiling memchr v2.5.0
Compiling windows_x86_64_msvc v0.48.0
Compiling ppv-lite86 v0.2.17
Compiling siphasher v0.3.10
Compiling winapi v0.3.9
Compiling getrandom v0.1.16
Compiling log v0.4.19
Compiling proc-macro-hack v0.5.20+deprecated
Compiling getrandom v0.2.10
Compiling parking_lot_core v0.9.8
Compiling fnv v1.0.7
error: linker link.exe not found
|
= note: program not found
note: the msvc targets depend on the msvc linker but link.exe was not found
note: please ensure that Visual Studio 2017 or later, or Build Tools for Visual Studio were installed with the Visual C++ option.
note: VS Code is a different product, and is not sufficient.
error: could not compile windows_x86_64_msvc due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile quote due to previous error
error: could not compile getrandom due to previous error
error: could not compile proc-macro-hack due to previous error
error: could not compile memchr due to previous error
error: could not compile serde due to previous error
error: could not compile proc-macro2 due to previous error
error: could not compile syn due to previous error
error: could not compile parking_lot_core due to previous error
error: could not compile winapi due to previous error
Error failed to build app: failed to build app
file:///D:/dev/nvm/v16.19.1/node_modules/pake-cli/dist/cli.js:369
reject(new Error(${code}));
^
Error: 1
at file:///D:/dev/nvm/v16.19.1/node_modules/pake-cli/dist/cli.js:369:24
at D:\dev\nvm\v16.19.1\node_modules\pake-cli\node_modules\shelljs\src\exec.js:145:9
at ChildProcess.exithandler (node:child_process:410:5)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
System version
win11
Node.js version
v16.19.1
Minimal reproduce step
pake https://weekly.tw93.fun --name Weekly --transparent
What did you expect to see?
1
What did you see instead?
1
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

有按照这个配置吗？https://github.com/tw93/Pake/blob/master/bin/README_CN.md#windowslinux-注意事项

一周没有回复，先关闭，假如问题还没有解决，辛苦直接打开这个issue就好


string parse bugfix

String parsing error that wasn't showing up before.

Out of curiosity, why didn't this show up previously?  (LGTM)

Ah that's a question that I don't know how to answer. I was just as surprised, because we went through that path in the code many many times in all clusters..


Switch to parsec

parsec comes builtin with ghc, so switching with it will reduce the list of dependencies

done in #64, no more megaparsec, hurray, this reduces by 30s the build time of the dependencies.


PacketFilter API refactor

Split up configuration table to contain rules key plus keys for global options (state_track, state_check). In my opinion this makes the API more straightforward to use.

if we have no rules ({}) then it seems all packets should be dropped?

Right, a no-rules filter would drop everything.
Currently, the behaviour of a global state_check is to check before any rule, and if it finds a match, the packet is passed.  Therefore, a filter with only a global state_check and no rules means "pass only known connections", which I think is a pretty common case.


feat: Autoscaling mechanism for regions without ECS task autoscaling

Description
In some AWS regions, ECS service autoscaling is not supported.
As a result, ECS cluster deployments have a fixed number of tasks requiring manual updating
Use Case
As an ECS service gets increased utilization and hits resource limits such as CPU and memory, additional tasks can't be automatically started to handle the load without manual intervention.
Conversely, as utilization decreases and fewer ECS tasks are needed to handle the workload, tasks aren't removed from the ECS service, resulting in over provisioning of resources and added costs.
Proposed Solution
A construct to track Cloudwatch Metrics for an ECS service, and set the desired task count for the service based on those metrics.
Other information
No response
Acknowledge

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

Feel free to assign me.


Cannot build when LuaJIT 2.1.0-beta is installed but LuaJIT 2.0 does not.

It seems that Ubuntu 18.04 ships with LuaJIT 2.1.0-beta3 instead of LuaJIT 2.0.x, and the FindLuaJIT.cmake script doesn't look for include/luajit-2.1 and include/luajit2.1, thus the configure script fails.
I have to modify FindLuaJIT.cmake to search also in include/luajit-2.1 and include/luajit2.1 to fix this problem.

Can confirm on Debian 9 / testing.  Same issue.
line 7 set(LUAJIT_SEARCH_PATHS
line 8  ++  /usr/include/luajit-2.1


[Bug]: Eufy 3 (S330) Cameras Showing as not compatible devices

What happened?
11/14/2022, 2:48:04 PM] [EufySecurity-2.2.0-beta.7] WARN: This accessory is not compatible with HomeBridge Eufy Security plugin: Front Door Type: 19
Eufy cam S330 show as not compatible
Device Type
Indoor Camera (Supported)
Plugin Version
beta (Best Effort)
HomeBridge Version
v1.4.x (Supported)
NodeJS Version
v16 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
11/14/2022, 2:48:04 PM] [EufySecurity-2.2.0-beta.7] WARN: This accessory is not compatible with HomeBridge Eufy Security plugin: Front Door Type: 19

17/11/2022, 16:53:58] Homebridge v1.5.1 (HAP v0.10.4) (Homebridge D4FB) is running on port 51004.
[11/17/2022, 4:54:00 PM] [EufySecurity-2.1.3] DEBUG: EufyClient connected true
[11/17/2022, 4:54:00 PM] [EufySecurity-2.1.3] DEBUG: CameraMaxLivestreamDuration: 30
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] DEBUG: Found Station T8010P1321232B6D Hooter Home Base STATION <IP_ADDRESS>
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] INFO: You're using guest admin account with this plugin! This is recommanded way!
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] DEBUG: Device ignored
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] DEBUG: Found Station T8030P13223211E1 HomeBase 3 HB3 <IP_ADDRESS>
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] INFO: You're using guest admin account with this plugin! This is recommanded way!
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] DEBUG: This device is not a station. Generating a new UUID to avoid any duplicate issue
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] DEBUG: HomeBase 3 UUID: 7e8d9739-23f2-4302-b69a-9b756b02cc25
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] DEBUG: HomeBase 3 Constructed Station
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] DEBUG: HomeBase 3 manual alarm will be triggered only in these hk modes:
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] DEBUG: HomeBase 3 Mapping for station modes: [{"hk":0,"eufy":1},{"hk":1,"eufy":0},{"hk":2,"eufy":3},{"hk":3,"eufy":63}]
[11/17/2022, 4:54:01 PM] [EufySecurity-2.1.3] INFO: Updating accessory: HomeBase 3
[17/11/2022, 16:54:01] [Abode Locks] Restoring existing accessory from cache: Back Door Lock
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] DEBUG: Found device T8140P612121334F Backyard Patio CAMERA2_PRO
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] DEBUG: Device ignored
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] DEBUG: Found device T8140P8121355629 Front Yard Right CAMERA2_PRO
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] DEBUG: Device ignored
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] DEBUG: Found device T8140P8122044807 Front Yard Left Camera CAMERA2_PRO
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] DEBUG: Device ignored
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] DEBUG: Found device T8160P1122310F35 Front Door CAMERA3
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] DEBUG: Front Door UUID: 51bc0018-83d1-450d-a2e1-e17239fade76
[11/17/2022, 4:54:02 PM] [EufySecurity-2.1.3] WARN: This accessory is not compatible with HomeBridge Eufy Security plugin: Front Door Type: 19
[11/17/2022, 4:54:14 PM] [EufySecurity-2.1.3] DEBUG: Push Connected!
[11/17/2022, 4:54:45 PM] [EufySecurity-2.1.3] INFO: Looking for old cached accessories that seem to be outdated...
[11/17/2022, 4:54:45 PM] [EufySecurity-2.1.3] INFO: No outdated cached accessories found.
Basically same debug log when on 2.2.0 beta as well
[17/11/2022, 16:58:23] Homebridge v1.5.1 (HAP v0.10.4) (Homebridge D4FB) is running on port 51004.
[11/17/2022, 4:58:24 PM] [EufySecurity-2.2.0-beta.7] DEBUG: EufyClient connected true
[11/17/2022, 4:58:24 PM] [EufySecurity-2.2.0-beta.7] DEBUG: CameraMaxLivestreamDuration: 30
[11/17/2022, 4:58:24 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Plugin-Config interaction server was started on port: 11260
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Found Station T8010P1321232B6D Hooter Home Base STATION <IP_ADDRESS>
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] INFO: You're using guest admin account with this plugin! This is recommanded way!
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Device ignored
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Found Station T8030P13223211E1 HomeBase 3 HB3 <IP_ADDRESS>
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] INFO: You're using guest admin account with this plugin! This is recommanded way!
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] DEBUG: This device is not a station. Generating a new UUID to avoid any duplicate issue
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] DEBUG: HomeBase 3 UUID: 7e8d9739-23f2-4302-b69a-9b756b02cc25
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] DEBUG: HomeBase 3 Constructed Station
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] DEBUG: HomeBase 3 manual alarm will be triggered only in these hk modes:
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] DEBUG: HomeBase 3 Mapping for station modes: [{"hk":0,"eufy":1},{"hk":1,"eufy":0},{"hk":2,"eufy":3},{"hk":3,"eufy":63}]
[11/17/2022, 4:58:26 PM] [EufySecurity-2.2.0-beta.7] INFO: Updating accessory: HomeBase 3
[17/11/2022, 16:58:26] [Abode Locks] Restoring existing accessory from cache: Back Door Lock
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Found device T8140P612121334F Backyard Patio CAMERA2_PRO
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Device ignored
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Found device T8140P8121355629 Front Yard Right CAMERA2_PRO
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Device ignored
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Found device T8140P8122044807 Front Yard Left Camera CAMERA2_PRO
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Device ignored
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Found device T8160P1122310F35 Front Door CAMERA3
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Front Door UUID: 51bc0018-83d1-450d-a2e1-e17239fade76
[11/17/2022, 4:58:27 PM] [EufySecurity-2.2.0-beta.7] WARN: This accessory is not compatible with HomeBridge Eufy Security plugin: Front Door Type: 19
[11/17/2022, 4:58:28 PM] [EufySecurity-2.2.0-beta.7] WARN: Push Closed!
[11/17/2022, 4:58:34 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Push Connected!
[11/17/2022, 4:58:34 PM] [EufySecurity-2.2.0-beta.7] DEBUG: Push Connected!
config

{
  "accessories" : [

  ],
  "bridge" : {
    "advertiser" : "avahi",
    "name" : "Homebridge D4FB",
    "pin" : "",
    "port" : 51004,
    "username" : ""
  },
  "platforms" : [
    {
      "name" : "Config",
      "platform" : "config",
      "port" : 8581
    },
    {
      "cameras" : [
        {
          "hsv" : false,
          "rtsp" : false,
          "serialNumber" : "T8140P612121334F",
          "snapshotHandlingMethod" : 3
        },
        {
          "hsv" : false,
          "rtsp" : false,
          "serialNumber" : "T8140P8121355629",
          "snapshotHandlingMethod" : 3
        },
        {
          "hsv" : false,
          "rtsp" : false,
          "serialNumber" : "T8140P8122044807",
          "snapshotHandlingMethod" : 3
        }
      ],
      "cleanCache" : true,
      "country" : "US",
      "deviceName" : "",
      "ignoreDevices" : [
        "T8140P612121334F",
        "T8140P8121355629",
        "T8140P8122044807"
      ],
      "ignoreStations" : [
        "T8010P1321232B6D"
      ],
      "password" : "",
      "platform" : "EufySecurity",
      "username" : ""
    }

Could you share some more debug logs?

Sharing debug with beta and current releases above. Let me know if you need any more info....

Most recent beta change now has camera showing up as motion sensor and showing correct pictures in settings for the camera and new homebase. "Front Door" below is new S330 camera on Homebase 3. Homekit now sees the camera as a motion sensor. Still does not appear to be fully accept as a camera in settings. Progress definitely happening! Here is new debug logs:
[19/11/2022, 07:47:35] Homebridge v1.5.1 (HAP v0.10.4) (Homebridge D4FB) is running on port 51004.
[11/19/2022, 7:47:36 AM] [EufySecurity-2.2.0-beta.8] DEBUG: EufyClient connected true
[11/19/2022, 7:47:36 AM] [EufySecurity-2.2.0-beta.8] DEBUG: CameraMaxLivestreamDuration: 30
[11/19/2022, 7:47:36 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Plugin-Config interaction server was started on port: 17272
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Found Station T8010P1321232B6D Hooter Home Base STATION <IP_ADDRESS>
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] INFO:  You're using guest admin account with this plugin! This is recommanded way!
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Device ignored
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Found Station T8030P13223211E1 HomeBase 3 HB3 <IP_ADDRESS>
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] INFO:  You're using guest admin account with this plugin! This is recommanded way!
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] DEBUG: This device is not a station. Generating a new UUID to avoid any duplicate issue
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] DEBUG: HomeBase 3 UUID: 7e8d9739-23f2-4302-b69a-9b756b02cc25
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] DEBUG: HomeBase 3 Constructed Station
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] DEBUG: HomeBase 3 manual alarm will be triggered only in these hk modes:
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] DEBUG: HomeBase 3 Mapping for station modes: [{"hk":0,"eufy":1},{"hk":1,"eufy":0},{"hk":2,"eufy":3},{"hk":3,"eufy":63}]
[11/19/2022, 7:47:37 AM] [EufySecurity-2.2.0-beta.8] INFO:  Updating accessory: HomeBase 3
[19/11/2022, 07:47:37] [Abode Locks] Restoring existing accessory from cache: Back Door Lock
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Found device T8140P612121334F Backyard Patio CAMERA2_PRO
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Device ignored
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Found device T8140P8121355629 Front Yard Right CAMERA2_PRO
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Device ignored
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Found device T8140P8122044807 Front Yard Left Camera CAMERA2_PRO
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Device ignored
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Found device T8160P1122310F35 Front Door CAMERA3
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door UUID: 51bc0018-83d1-450d-a2e1-e17239fade76
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door has a battery, so append Battery characteristic to him.
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Constructed Camera
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door config is: {
serialNumber: 'T8160P1122310F35',
rtsp: false,
talkback: false,
name: 'Front Door',
enableButton: true,
motionButton: true,
forcerefreshsnap: false,
videoConfig: {},
immediateRingNotificationWithoutSnapshot: false,
delayCameraSnapshot: false,
hsv: false,
experimentalRTSP: false,
snapshotHandlingMethod: 3
}
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door has a motion sensor.
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door enableButton config: true
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door has a isEnabled, so append switchEnabledService characteristic to him.
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door motionButton config: true
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door has a isMotionDetectionEnabled, so append switchMotionService characteristic to him.
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Looks like not compatible with DeviceLight
[11/19/2022, 7:47:38 AM] [EufySecurity-2.2.0-beta.8] INFO:  Updating accessory: Front Door
[11/19/2022, 7:47:46 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Push Connected!
[11/19/2022, 7:47:52 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceMotionDetected: false
[11/19/2022, 7:47:52 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceEnabled: true
[11/19/2022, 7:47:52 AM] [EufySecurity-2.2.0-beta.8] DEBUG: HomeBase 3 GET StationCurrentMode: 1
[11/19/2022, 7:47:52 AM] [EufySecurity-2.2.0-beta.8] DEBUG: HomeBase 3 GET StationCurrentMode: 1
[11/19/2022, 7:47:52 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceMotionDetection: true
[11/19/2022, 7:48:19 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceMotionDetected: false
[11/19/2022, 7:48:19 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceEnabled: true
[11/19/2022, 7:48:19 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceMotionDetection: true
[11/19/2022, 7:49:07 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceMotionDetected: false
[11/19/2022, 7:49:07 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceEnabled: true
[11/19/2022, 7:49:07 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door GET DeviceMotionDetection: true
[11/19/2022, 7:49:36 AM] [EufySecurity-2.2.0-beta.8] INFO:  Looking for old cached accessories that seem to be outdated...
[11/19/2022, 7:49:36 AM] [EufySecurity-2.2.0-beta.8] INFO:  No outdated cached accessories found.
[19/11/2022, 07:49:47] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /storedAccessories
[19/11/2022, 07:49:47] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /storedAccessories
[19/11/2022, 07:49:57] [Homebridge UI] [homebridge-eufy-security] Terminating child process...
[19/11/2022, 07:49:57] [Homebridge UI] [homebridge-eufy-security] Child process ended
[11/19/2022, 7:54:59 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: personName Unknown
[11/19/2022, 7:54:59 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: personDetected true
[11/19/2022, 7:54:59 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door ON DeviceMotionDetected: true
[11/19/2022, 7:55:09 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: personName
[11/19/2022, 7:55:09 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: personDetected false
[11/19/2022, 7:55:09 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door ON DeviceMotionDetected: false
[11/19/2022, 7:55:44 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: personName Unknown
[11/19/2022, 7:55:44 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: personDetected true
[11/19/2022, 7:55:44 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door ON DeviceMotionDetected: true
[11/19/2022, 7:55:54 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: personName
[11/19/2022, 7:55:54 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: personDetected false
[11/19/2022, 7:55:54 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door ON DeviceMotionDetected: false
[11/19/2022, 7:57:39 AM] [EufySecurity-2.2.0-beta.8] DEBUG: Front Door Property Changes: pictureUrl https://cdn-us.eufylife.com/thumb/2022/11/19/station/T8030P13223211E1/0NO0rzEpLuRYdVag./snapshort.jpg?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJYLV2KOLW6PU4FSA%2F20221119%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20221119T125739Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=bcbad69dc7f5f3315aae1627e0d1c1c436863962d3cd002b34219f21ddd691df
[19/11/2022, 07:59:16] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /storedAccessories
[19/11/2022, 07:59:16] [Homebridge UI] [homebridge-eufy-security] Incoming Request: /storedAccessories
[19/11/2022, 07:59:22] [Homebridge UI] [homebridge-eufy-security] Terminating child process...
[19/11/2022, 07:59:22] [Homebridge UI] [homebridge-eufy-security] Child process ended

You'll have to enable the camera manually through the configuration ui. See here
I think that should do the trick.

Doesn’t give you the option thus my comment after the update that it still doesn’t appear to be handling it fully as an acceptable camera.

Ah. Now I see... give me a bit. Will add a fix...

You’re awesome. Ty! Let me know and I’ll try

It's currently publishing. Should be up in 5-10 minutes.

Ty. I assume just update beta release?

Yep. Should now be visible as beta.9 (Maybe npm needs some time to update).

Working! Nice.  Running in unbridge mode


search server list

Issue Type: Feature Request
I have lots of server connections saved in the servers list. It would be great to either be able to search the list, or if the list had focus and I start typing the server name have the focus shift to the correct server as I type - similar to how the object pane in SSMS works.
Azure Data Studio version: azuredatastudio 1.12.2 (c9bef82ace6c67190d0e83820011a2bbd1f793c1, 2019-10-11T04:56:40.634Z)
OS version: Windows_NT x64 10.0.17134

@sivey42 We have a command called Search: Servers in the command palette (Ctrl/Cmd + Shift + P)


Attempt to download Linux kernel fails: does not support range request

$ pget -p 6  https://git.kernel.org/torvalds/t/linux-6.5-rc2.tar.gz
[WARNING] Using a large number of connections to 1 URL can lead to DOS attacks.
In most cases, `4` or less is enough. In addition, the case is increasing that if you use multiple connections to 1 URL does not increase the download speed with the spread of CDNs.
See: https://github.com/Code-Hex/pget#disclaimer

Would you execute knowing these?
 (y/n) [n]: y
Error:
  https://git.kernel.org/torvalds/t/linux-6.5-rc2.tar.gz: does not support range request

go120-1.20.3
FreeBSD 13.2

Same happens for the "benchmark" in the README

I am also running into issues where range requests are not supported by servers and I was anticipating using pget. I think this isn't really fixable by pget, at least insofar as I don't think it can -resume- these downloads, but perhaps a flag could be added that says "if range request not available, overwrite if exists"?


PVS editing

I'd like to edit the PVS of VISleafs. The use case is to make a particular VIS leaf visible to all other leafs, the way info_overview_point with reverse flag in zhlt does.

@mfaizsyahmi In my fork I added 'VIS Debugger' feature. It mark all faces, blue is visibled, red if not visibled. Start leaf is camera position. (Debug Widget>TEST VIS DATA button)


Make things work on Linux and OS X

There's a few places where we need to triage over the platform. Only Windows has been implemented so far.

Since we already have crossplatform CI, it should be easy to achieve this with some decent tests.
We can enable screen sessions / configure screen resolution on CI if needed too.

Spinning up an Ubuntu VM and my old macbook should do the trick at first. But yeah, we need more tests too :)

I'm working on Ubuntu at the office and Windows at home, so I should be able to pitch in some Ubuntu support as well.

We need the binaries (e.g. from https://github.com/gfx-rs/wgpu/pull/416) anyway :)  (or setup a rust build environment).

Did a little bit of the work for this in #24 ; we can start testing on all platforms now

Most of the implementation is done in #27, tracking further in #28 and #29


Add JarInfer models for Android 11 (SDK 30)

This is a new NullAway artifact to serve as platform models
for the android.jar classes for SDK level 30 / Android 11,
providing nullability information for Android platform classes
as determined by the JarInfer tool.
The binary model jarinfer.astubx produced from AOSP tag
android-11.0.0_r34 by running JarInfer on it as
described in RELEASING.md.

Pull Request Test Coverage Report for Build #494

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 89.166%

Totals

Change from base Build #493:
0.0%

Covered Lines:
3465

Relevant Lines:
3886

💛  - Coveralls


Our dns server list has reported to many errors. I can't continue.

some dns servers have request limits.
One time you have been blacklisted the dns server will stop responding.
that why dmut delete that server from his list and try to use another one.
the best solution here is to use a much bigger dns list or try using a much smaller alteration list.


Can heavy Git history be cleaned out?

As mentioned in #6, the Git repository takes some time to clone due to the fact that the Git history contains old binaries for macOS and Windows (which have been removed from the code base in the meantime).
Investigation required
Is there a way to "compact" the repository, to avoid having to download a huge, unnecessary history? e.g.

Maintenance and Data Recovery - Git Internals (official Git documentation)
How to Shrink a Git Repository (Steve Lorek)
Compact Git repository with history depth (StackOverflow)
Compact repo by removing old commits (StackOverflow)
Reduce git repository size (StackOverflow)

That's a good idea. I have no objection to that and I'm okay with moving my local branch to a new, rewritten history. If you'd like to tackle that, feel free.


[$500] IOU - The red dot displays on add attendee page when making a split bill

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Precondition:

Log in with the same account in the main testing device and a secondary device
Disable the internet connection in the main testing device
On the secondary device, split a bill with two users with whom you don't have existing conversations
In the main testing device (should be offline) create the SAME split bill with the 2 users
Enable the internet connection in the main testing device
Tap/click the X in the error message
Steps:
Tap on FAB
Select Request Money
Select Manual tab
Write any amount and tap on Next button

Expected Result:
The attendee listing page should be properly displayed
Actual Result:
The red dot displays on add attendee page
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/d7074f97-3faa-4eb1-b34f-bcd5d6bd9ea3
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0101f5b6d9ca416f4a
Upwork Job ID:<PHONE_NUMBER>431738880
Last Price Increase: 2023-12-28

Currently new to it , can anyone guide how can i contribute anything , i am ready to learn new things even if required.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01307592ed793cc494

I'm also not sure that there's a clear expected behaviour here that is different to what we're seeing.
I'm also struggling to imagine this flow (multiple devices in varying on/offline states trying to create the same split) actually occurring at all in regular use, feels like an extreme edge case. Going to close this one out.


swift-im: init at 4.0.2

Motivation for this change
The software is actually called Swift; I am following the example of AUR by using the attribute swift-im to disambiguate with other Swifts.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-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)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libnatpmp, swift-im
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: libnatpmp, swift-im
Partial log (click to expand)
shrinking /nix/store/2l409qlmimmwjsvz1dbn3rny5sic0dma-swift-im-4.0.2/bin/swift-im
shrinking /nix/store/2l409qlmimmwjsvz1dbn3rny5sic0dma-swift-im-4.0.2/bin/swift-open-uri
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/2l409qlmimmwjsvz1dbn3rny5sic0dma-swift-im-4.0.2/bin
patching script interpreter paths in /nix/store/2l409qlmimmwjsvz1dbn3rny5sic0dma-swift-im-4.0.2
checking for references to /build in /nix/store/2l409qlmimmwjsvz1dbn3rny5sic0dma-swift-im-4.0.2...
postPatchMkspecs
postPatchMkspecs
/nix/store/4j7n8j54hpb0b5paj262yssdpvi7av3x-libnatpmp-20150609
/nix/store/2l409qlmimmwjsvz1dbn3rny5sic0dma-swift-im-4.0.2

Success on aarch64-linux (full log)
Attempted: libnatpmp, swift-im
Partial log (click to expand)
shrinking /nix/store/9yh9dgmlji5sav6ck3cqv8fl8sslfzwl-swift-im-4.0.2/bin/swift-open-uri
shrinking /nix/store/9yh9dgmlji5sav6ck3cqv8fl8sslfzwl-swift-im-4.0.2/bin/swift-im
strip is /nix/store/jk6j4lh9v5mvjdbdc35sj0zffhhf6s56-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/9yh9dgmlji5sav6ck3cqv8fl8sslfzwl-swift-im-4.0.2/bin
patching script interpreter paths in /nix/store/9yh9dgmlji5sav6ck3cqv8fl8sslfzwl-swift-im-4.0.2
checking for references to /build in /nix/store/9yh9dgmlji5sav6ck3cqv8fl8sslfzwl-swift-im-4.0.2...
postPatchMkspecs
postPatchMkspecs
/nix/store/fd0q1ddj3p1x8bi2fc6rg6lp1a5g556g-libnatpmp-20150609
/nix/store/9yh9dgmlji5sav6ck3cqv8fl8sslfzwl-swift-im-4.0.2


Rename middleware test file name to follow convention

Renamed appendAction.js to appendAction.spec.js.

Coverage remained the same at 96.382% when pulling fc6bd058a404e68d83760c101b3e887a27032e88 on tests-convention into 256495ef4877a6185567805df4ad787796c70202 on master.

Coverage remained the same at 96.474% when pulling 2d0d04c38d8307a8e591eee3af41fcfa0c89f291 on tests-convention into da182dc3b23fd1d102869a47232157ad2f05edba on master.


Fixes the cleanupUser cloud function.

Fixes the cleanupUser cloud function as mentioned in #126.
The error thrown in cloud function logs is as follows:

Thanks @NoahWilcox !


[Task]: Move filtering of js object actions to DB

SubTasks
One optimisation that can be done after observing the new relic metrics pushed in this PR, is that the part where we filter out JS object actions can be done on the DB layer itself. This task is to make this improvement and observe the metrics locally for heavy application.

Spans before moving filtering to DB

Spans after moving filtering to DB


State is being shared across instances

Describe the bug
Since version 2.11.1, state seems to be shared between instances.
To Reproduce

Install fakeredis==2.11.1
Run the following snippet

from fakeredis import FakeRedis

fake_redis_1 = FakeRedis()
fake_redis_2 = FakeRedis()

fake_redis_1.set("foo", "bar")

assert fake_redis_2.get("foo") is None

Expected behavior
State should not be shared across instances unless the same FakeServer is being used.
Desktop (please complete the following information):

OS: Debian 11
python version: 3.11.2
redis-py version: 2.11.1

The behaviour I am experiencing is new in 2.11.1 though. The documentation also says that state is not shared by default and it's the other way around from what you suggested; You need to explicitly pass the same FakeServer instance to share state.

The state is stored in an instance of FakeServer. If one is not provided at construction, a new instance is automatically created for you, but you can explicitly create one to share state

I'm fine if this is intentional, but then the docs should probably be changed and a note added somewhere about this breaking change.

True, I missed updating the documentation.
Could you create a PR to update the documentation for it?

I added in 2.11.0 the awareness of connection parameters.
So if you create multiple clients with the same connection parameters, it will use the same FakeServer.
As a result of this, when you don't supply any connection parameters => I chose to use a "shared" FakeServer (see here) - I think it makes more sense, but I agree it is a breaking change and I guess should be reverted for the case no connection-parameters are provided.

Like you said, there are arguments for both cases.
I can share that tests in rq using FakeRedis are failing because, internally, a new connection is created, so sharing a state is needed. Also, in redis.Redis connection parameters are required.
I need to think about it more. But regardless, it is a breaking change, and if introduced, should be in v3.


vpp: init at 24.06

Description of changes
VPP is a high-performance userland network stack for routing/switching on general purpose computers.
Supersedes #290529 & #256601, module & tests will be added later in a separate PR (#347797). Basic multithread routing functionality w/ DPDK was tested on an Intel X520-DA2 NIC.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4668

@markuskowa Thanks, could you also add the tag for backporting to 24.05? Would be much easier than creating the PR manually.

Nevermind, just realized I can do it myself. Apologies for the ping.


Unable to open progression gui in enchanting table

Whatever i try to do i am unable to use an enchanting table to open the gui, it just does what a wand would normally do when right-clicking.
Everything worked fine until i disabled the engineering example. suddenly the wands went to beginner and wont open in an enchanting table anymore.
So basically what i want is to use the wand on an enchanting table to open the progression gui.

That sounds like you also accidentally removed survival as well. What does mexample list say?

It says
Examples:
  - spawnmobs
  - survival

Try using mexample set survival spawnmobs
this will put survival back as the main example and hopefully fix your problems.

I tried it but nothing changed.

I figured out the wands didn't work because when i disabled the engineer example the classes of people stayed unchanged so it wasn't recognized. though i still do not know how to fix it.

Ah, I see- that's unfortunate, sorry. I hadn't really thought about that... I also can't think of a good solution. Try this, maybe:
/meditor path engineer, and then put in the editor just this:
engineer:
  inherit: master

Then do the same for architect, that may fix it? I'll try and come up with a better solution.


Firestore BaseClientInitializer?

I am aware of how to initialize using the environment variable. However, If I want to initialize in the code, could I do it with the baseclient?
                var test2 = new BaseClientService.Initializer
                {
                    ApplicationName = "Test",
                    ApiKey = "[YOUR_API_KEY_HERE]",
                };

How would I specify the credentials in Firestoredb object? I am assuming its somewhere in the client I just dont know where.

No, BaseClientService.Initializer is how you initialize our REST-based clients. Google.Cloud.Firestore is a gRPC-based library. You'd need to create the FirestoreClient from a Channel with suitable authentication (not an API key) and then pass that FirestoreClient into the FirestoreDb.Create method.
See this FAQ entry for creating the FirestoreClient. We want to make all of this easier, but that should help for now.

(Please let me know if you need more help than that; otherwise I'll close this issue after a while.)

@jskeet Thanks for the quick response. I have the necessary config for the javascript api I am just trying to convert that for use with the C# api.
const config = {
  apiKey: "",
  authDomain: "",
  databaseURL: "",
  projectId: "",
  storageBucket: "",
  messagingSenderId: ""
};

Is there a way for me to use these to authenticate?

No, you can't use an API key to authenticate using Google.Cloud.Firestore.

Sorry I guess that was redundant. But thanks for the quick response haha!

Does anyone have a code-sample or an answer on how to go about Authenticating coming from a validated User Credential (as in the initial Question) to connect it to Firestore ??
I would prefer not having to use the Service Account, and just use the End Users credentials to access the Firestore.
Is this possible or am I dreaming ?

Well, so far "Google.Apis.Firestore.V1" does work on the same principles, hence then BaseClientInitializer..
Alass the documentation is quite lacking to get things rolling, and almost everything online refers to the gRPC-based "Google.Cloud.Firestore" ...

You can use FirestoreDbBuilder (in the latest beta) as an easy way of specifying credentials. For example:
ITokenAccess credential = ...; // Populate your UserCredential any way you want
var db = new FirestoreDbBuilder
{
    ProjectId = "myprojectid",
    TokenAccessMethod = credential.GetAccessTokenForRequestAsync
}.Build();

However, this isn't the intended use for the API - it's intended to be used with service accounts, and I don't know whether it will work at all with a user credential. (The user credential would need to be associated with a GCP project which has Firestore enabled, I believe.)
If this isn't sufficient help, please file a new issue with more details - but I really would strongly recommend using service accounts, or default compute credentials if running on GCP.


timeouts

Socks should expose a way to configure the SO_RCVTIMEO and SO_SNDTIMEO.
This will allow us to conform to the C7 spec:
public func send(_ data: Data, timingOut deadline: Double) throws

And it will help frameworks using Socks to avoid memory leaks from dead connections that never close.

Related to #30.
Agreed, I'll investigate and report back.


Fix error for missing path parameter in artifact file delete

Signed-off-by: Lukas Balzer<EMAIL_ADDRESS>Removed error when trying to delete a file from the files tab in an artifact template

[x] Ensure that the commit message is a good commit message
[ ] Change in CHANGELOG.md described
[ ] Tests created for changes
[ ] Screenshots added (for UI changes)

Can one of the admins verify this patch?