Install on macOS fails

Using these install instructions and just accepting defaults:
-- The executable will be in '/Users/carlo.wahlstedt/bin'.
-- Downloading virtualenv package from https://pypi.python.org/packages/source/v/virtualenv/virtualenv-15.0.0.tar.gz.
-- Downloaded virtualenv package to /var/folders/zd/kbyf92z92517trsjwh5h3mg9xp9gss/T/tmpskokwh3b/virtualenv-15.0.0.tar.gz.
-- Checksum of /var/folders/zd/kbyf92z92517trsjwh5h3mg9xp9gss/T/tmpskokwh3b/virtualenv-15.0.0.tar.gz OK.
-- Extracting '/var/folders/zd/kbyf92z92517trsjwh5h3mg9xp9gss/T/tmpskokwh3b/virtualenv-15.0.0.tar.gz' to '/var/folders/zd/kbyf92z92517trsjwh5h3mg9xp9gss/T/tmpskokwh3b'.
-- Executing: ['/usr/local/opt/python3/bin/python3.6', 'virtualenv.py', '--python', '/usr/local/opt/python3/bin/python3.6', '/Users/carlo.wahlstedt/lib/vsts-cli']
Already using interpreter /usr/local/opt/python3/bin/python3.6
Using base prefix '/usr/local/Cellar/python3/3.6.3/Frameworks/Python.framework/Versions/3.6'
New python executable in /Users/carlo.wahlstedt/lib/vsts-cli/bin/python3.6
Also creating executable in /Users/carlo.wahlstedt/lib/vsts-cli/bin/python
Installing setuptools, pip, wheel...done.
-- Current executable /usr/local/opt/python3/bin/python3.6
-- Installed executable /Users/carlo.wahlstedt/lib/vsts-cli/bin/python
-- Is Python.framework
-- Installed Python executable exists
-- Created backup of installed Python executable
-- Replaced installed Python executable
-- Executing: ['/Users/carlo.wahlstedt/lib/vsts-cli/bin/pip', 'install', '--cache-dir', '/var/folders/zd/kbyf92z92517trsjwh5h3mg9xp9gss/T/tmpskokwh3b', '--pre', 'vsts-cli', '--upgrade', '--extra-index-url', 'https://vstscli.azurewebsites.net/']
Requirement already up-to-date: vsts-cli in /usr/local/lib/python3.6/site-packages
Requirement already up-to-date: knack in /usr/local/lib/python3.6/site-packages (from vsts-cli)
Requirement already up-to-date: vsts-cli-common==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli)
Requirement already up-to-date: vsts-cli-work==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli)
Requirement already up-to-date: vsts-cli-build==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli)
Requirement already up-to-date: vsts-cli-code==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli)
Requirement already up-to-date: vsts-cli-team==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli)
Requirement already up-to-date: jmespath in /usr/local/lib/python3.6/site-packages (from knack->vsts-cli)
Requirement already up-to-date: tabulate in /usr/local/lib/python3.6/site-packages (from knack->vsts-cli)
Requirement already up-to-date: pygments in /usr/local/lib/python3.6/site-packages (from knack->vsts-cli)
Requirement already up-to-date: pyyaml in /usr/local/lib/python3.6/site-packages (from knack->vsts-cli)
Requirement already up-to-date: argcomplete in /usr/local/lib/python3.6/site-packages (from knack->vsts-cli)
Requirement already up-to-date: colorama in /usr/local/lib/python3.6/site-packages (from knack->vsts-cli)
Requirement already up-to-date: six in /usr/local/lib/python3.6/site-packages (from knack->vsts-cli)
Requirement already up-to-date: vsts~=0.1.0b2.dev in /usr/local/lib/python3.6/site-packages (from vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: keyring in /usr/local/lib/python3.6/site-packages (from vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: python-dateutil in /usr/local/lib/python3.6/site-packages (from vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: vsts-cli-work-common==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli-work==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: vsts-cli-build-common==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli-build==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: vsts-cli-code-common==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli-code==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: vsts-cli-team-common==0.1.0b2.dev4422419 in /usr/local/lib/python3.6/site-packages (from vsts-cli-team==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: msrest>=0.4.5 in /usr/local/lib/python3.6/site-packages (from vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: requests-oauthlib>=0.5.0 in /usr/local/lib/python3.6/site-packages (from msrest>=0.4.5->vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: requests~=2.14 in /usr/local/lib/python3.6/site-packages (from msrest>=0.4.5->vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: certifi>=2017.4.17 in /usr/local/lib/python3.6/site-packages (from msrest>=0.4.5->vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: isodate>=0.5.4 in /usr/local/lib/python3.6/site-packages (from msrest>=0.4.5->vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: oauthlib>=0.6.2 in /usr/local/lib/python3.6/site-packages (from requests-oauthlib>=0.5.0->msrest>=0.4.5->vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.6/site-packages (from requests~=2.14->msrest>=0.4.5->vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: urllib3<1.23,>=1.21.1 in /usr/local/lib/python3.6/site-packages (from requests~=2.14->msrest>=0.4.5->vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Requirement already up-to-date: idna<2.7,>=2.5 in /usr/local/lib/python3.6/site-packages (from requests~=2.14->msrest>=0.4.5->vsts~=0.1.0b2.dev->vsts-cli-common==0.1.0b2.dev4422419->vsts-cli)
Traceback (most recent call last):
  File "/var/folders/zd/kbyf92z92517trsjwh5h3mg9xp9gss/T/vsts_cli_install_tmp_XXXX.uskjUUOL", line 444, in <module>
    main()
  File "/var/folders/zd/kbyf92z92517trsjwh5h3mg9xp9gss/T/vsts_cli_install_tmp_XXXX.uskjUUOL", line 426, in main
    exec_filepath = create_executable(exec_dir, install_dir)
  File "/var/folders/zd/kbyf92z92517trsjwh5h3mg9xp9gss/T/vsts_cli_install_tmp_XXXX.uskjUUOL", line 173, in create_executable
    cur_stat = os.stat(exec_filepath)
FileNotFoundError: [Errno 2] No such file or directory: '/Users/carlo.wahlstedt/bin/vsts'

macOS: 10.12.6

@carlowahlstedt - we identified the problem. It appears to be Python 3 specific. We patched the install script.
Try running the install again: curl -L https://aka.ms/install-vsts-cli | bash.
This will attempt to use Python 2 (if you have it installed). It should also not fail on the step it previously failed on.
Btw, even though the original install says it failed, you likely have a vsts script under /usr/local/bin (which should be in your $PATH) that you can run to launch the VSTS CLI.

Installation successful! Good work!
I didn't actually try the vsts command prior to doing the install. Jumped the gun and started the install again before reading the entire post, but it worked. So I think we're in good shape now.
Thanks!

@carlowahlstedt - thanks for verifying, and glad it's working for you.
I am going to keep this issue open since we still have a problem with Python3 on Mac. The updated install script favors Python2, which allowed the VSTS CLI to install successfully.

👍🏼
Let me know how/if I can assist.

I could not repro this issue now. Tried to run the install script with python 3.
Since the original issue was fixed and this was only to fix the script.
Marking it closed.


Error trying to use run picker

Editor/Client you used
Neovim
Installation and Dependences checklist

[X] xbase is installed and ~/.local/share/xbase has required binaries
[X] All listed editor/client dependences is installed

Description
When I try using the run picker, I get this error:

E5108: Error executing lua: .../pack/packer/start/xbase/lua/xbase/pickers/telescope.lua:47: attempt to concatenate field 'name' (a nil value)
stack traceback:
        .../pack/packer/start/xbase/lua/xbase/pickers/telescope.lua:47: in function 'find'
        .../pack/packer/start/xbase/lua/xbase/pickers/telescope.lua:70: in function <.../pack/packer/start/xbase/lua/xbase/pickers/telescope.lua:69>

### Expected behavior

_No response_

### Reproduce

```Markdown
My configuration:

require("xbase").setup({
	--- Log level. Set it to ERROR to ignore everything
	log_level = vim.log.levels.DEBUG,
	--- Options to be passed to lspconfig.nvim's sourcekit setup function.
	--- Usually empty map is sufficient, However, it is strongly recommended to use on_attach key to setup custom mapppings
	-- sourcekit = {}, --- Set it to nil to skip lspconfig's sourcekit setup
	sourcekit = {
		on_attach = require("mystuff.on_attach_conf"),
		capabilities = require("cmp_nvim_lsp").default_capabilities(),
	}, --- Set it to nil to skip lspconfig's sourcekit setup
	--- Statusline provider configurations
	--- Simulators to only include.
	--- run `xcrun simctl list` to get a full list of available simulator
	--- If the list is empty then all simulator available  will be included
	simctl = {
		iOS = {
			 "iPhone 14 Pro", --- only use this devices
		},
		watchOS = {}, -- all available devices
		tvOS = {}, -- all available devices
	},
	--- Log buffer configurations
	--- Mappings
	mappings = {
		--- Whether xbase mapping should be disabled.
		enable = true,
		--- Open build picker. showing targets and configuration.
		build_picker = "<leader>xb", --- set to 0 to disable
		--- Open run picker. showing targets, devices and configuration
		run_picker = "<leader>xr", --- set to 0 to disable
		--- Open watch picker. showing run or build, targets, devices and configuration
		watch_picker = "<leader>xs", --- set to 0 to disable
		--- A list of all the previous pickers
		all_picker = "<leader>xf", --- set to 0 to disable
		--- vertical toggle log buffer
		toggle_vsplit_log_buffer = "<leader>xl",
	},
}) -- see default configuration bellow

Actual behavior
Shows this error:

E5108: Error executing lua: .../pack/packer/start/xbase/lua/xbase/pickers/telescope.lua:47: attempt to concatenate field 'name' (a nil value)
stack traceback:
        .../pack/packer/start/xbase/lua/xbase/pickers/telescope.lua:47: in function 'find'
        .../pack/packer/start/xbase/lua/xbase/pickers/telescope.lua:70: in function <.../pack/packer/start/xbase/lua/xbase/pickers/telescope.lua:69>

### Operating system and version

macOS 13.3.1

### xbase version / branch / rev

8f85a17fc8b5f43d3ec9c172ed2b17efaa3c6583

### Neovim version

v0.9.0

### Vscode version (if the editor you used is vscode)

_No response_

### Installed XCode Developer Tools

```bash
Developer:

    Developer Tools:

      Version: 14.2 (14C18)
      Location: /Applications/Xcode.app
      Applications:
          Xcode: 14.2 (21534)
          Instruments: 14.1 (64556.12)
      SDKs:
          DriverKit:
              22.2:
          iOS:
              16.2: (20C52)
          iOS Simulator:
              16.2: (20C52)
          macOS:
              13.1: (22C55)
          tvOS:
              16.1: (20K67)
          tvOS Simulator:
              16.1: (20K67)
          watchOS:
              9.1: (20S71)
          watchOS Simulator:
              9.1: (20S71)

XBase Logs
INFO FSWatcher{name="dopestproductever"}: [Dropped]
 INFO Broadcaster{name="Dopestproductever"}: [Dropped]
 INFO Client{fd=13}: Connected
 INFO Runtime{name="Dopestproductever"}: [Initializing] ------------------------
 INFO Broadcaster{name="Dopestproductever"}: Created
 INFO Runtime{name="Dopestproductever"}: targets: {"dopestproducteverUITests": TargetInfo { platform: "iOS", configurations: ["Debug", "Release"] }, "dopestproducteverTests": TargetInfo { platform: "iOS", configurations: ["Debug", "Release"] }, "dopestproductever": TargetInfo { platform: "iOS", configurations: ["Debug", "Release"] }}
 INFO Broadcaster{name="Dopestproductever"}: Connected [37269]
 INFO Runtime{name="dopestproductever"}: Connected [37269]
 INFO Runtime{name="dopestproductever"}: [Initialized] -------------------------
 INFO FSWatcher{name="dopestproductever"}: Watching

XBase Build Server Logs
INFO Broadcaster{name="Dopestproductever"}: [Dropped]
 INFO FSWatcher{name="dopestproductever"}: [Dropped]
 INFO Client{fd=13}: Connected
 INFO Runtime{name="Dopestproductever"}: [Initializing] ------------------------
 INFO Broadcaster{name="Dopestproductever"}: Created
 INFO Runtime{name="Dopestproductever"}: targets: {"dopestproducteverTests": TargetInfo { platform: "iOS", configurations: ["Debug", "Release"] }, "dopestproducteverUITests": TargetInfo { platform: "iOS", configurations: ["Debug", "Release"] }, "dopestproductever": TargetInfo { platform: "iOS", configurations: ["Debug", "Release"] }}
 INFO Broadcaster{name="Dopestproductever"}: Connected [37813]
 INFO Runtime{name="dopestproductever"}: Connected [37813]
 INFO Runtime{name="dopestproductever"}: [Initialized] -------------------------
 INFO FSWatcher{name="dopestproductever"}: Watching

Thanks for reporting. It should be fixed now.


Interpreter path location is not correct for conda on windows

Virtual environments created with anaconda on windows have their python executable located in the root of the environment folder (conda v4.10.3), but implementation in pyo3-build-config assumes executable to reside in Scripts-subdirectory.
Relevant line of code:
https://github.com/PyO3/pyo3/blob/6e83516e9445a2aa0a3a1c3117a6a38300142d9b/pyo3-build-config/src/impl_.rs#L1112
I have not submitted a PR, as I do not know if virtualenv on windows uses Script or bin (i.e. if more branches in if-statement will be needed). A more robust approach might be to rely on the OS to resolve the python executable if a virtual environment is active?
This issue appears to be root cause of #1554.

Thanks, I've opened a PR to tweak the path as suggested, however I still encounter #1554 when testing anaconda locally with that fix...

PyO3 correctly interprets the information that Conda leaves out about a virtual environment via conda activate, which in turn generates and runs a (usually dynamically generated) shell script. The shell script itself can be seen (for Powershell) with conda shell.powershell activate <env_name>, and we can see it sets the CONDA_PREFIX env var which is used by PyO3. PyO3 uses this to emit a link signal to rustc, and the Python gets linked correctly. However, I don't think that's enough for it to also be initialized correctly by Py_InitializeEx. Instead, what might be required is respecifying the config via Py_InitializeFromConfig. I might be wrong, maybe it should work by default and something else is messing up how Py_InitializeEx works.

I agree with the thinking that Py_InitializeFromConfig is worth investiating. I haven't tried, though. I'd like to eventually, but other pieces keep claiming higher prioritisation.


fixed typo

Thanks for your reply.I cannot open the link of this form. Is there any other way to access this data set。Thank you very much！

I can open the link which redirects you to Google Form. Please make sure whether you can open Google Form or not.


Home/end support

Add support for using the home and end keys along with ctrl+b and ctrl+e to jump to start and end of line.

Sure, reasonable enough. I’ll see if I can implement it this weekend. Thanks for the suggestion!


Travamentos a partir de 10 páginas

o editor começa a travar apartir de 10 páginas, não sendo possível continuar.
observei que a renderização de páginas acontece a cada letra digitada.

Yes this is a known issue, as written in the readme. The algorithm for splitting the content in several pages runs every time you type a letter, and involves HTML DOM manipulation that is quite heavy as the number of pages grow.
So for now you can't use this library for big documents, the algorithm doesn't work well for big documents. Sorry


After updating obsidian version to 1.5.3, installing the sortable plug-in cannot sort the cssclass of cards.

Is the bug present when using the default Obsidian theme?
No
Is the bug present when snippets and plugins are disabled?
Yes
Minimal theme version
7.4.5
Describe the bug
After updating obsidian version to 1.5.3, installing the sortable plug-in cannot sort the cssclass of cards.

Debug info
After updating obsidian version to 1.5.3, installing the sortable plug-in cannot sort the cssclass of cards.

Experiencing the same issue. Sorting in cards view shows a blank menu, both with and without the sortable plugin.


IIS 8.5 error on load

After last round of upgrades to angular rc4 I get following error, when running your "APM - Final Updated" under IIS. Error is following:
System.import('app').catch(function(err){ console.error(err);  });

TypeError: Cannot read property 'NeverChecked' of undefined
	    at eval (node_modules/@angular/compiler/src/view_compiler/constants.js:48:112)
	    at Object.eval (node_modules/@angular/compiler/src/view_compiler/constants.js:52:2)
	    at eval (node_modules/@angular/compiler/src/view_compiler/constants.js:114:4)
	    at eval (node_modules/@angular/compiler/src/view_compiler/constants.js:115:3)

Running from "npm start" is working fine.

It appears Chrome cached old versions of the @angular files as everything is working fine in IE.
Apologies for the false alarm.


Occasional swiftc crash on Windows, "disposed a muxnote with an active thread"

Upon upgrading our Azure CI machines to use the new Azure Cobalt ARM64 processors, we started seeing frequent compiler crashes when building a large Swift project. After some investigation, the culprit appears to be a lifecycle violation in libdispatch in the Windows pipe handling code.
The crashing line: https://github.com/apple/swift-corelibs-libdispatch/blob/e85f6a0d5c9ea1f32f5013c3fa34e4fc146cd0eb/src/event/event_windows.c#L240
And the stack trace:
[Inline Frame] dispatch.dll!_dispatch_muxnote_dispose(dispatch_muxnote_s * dmn) Line 240s://github.com/apple/swift-corelibs-libdispatch/blob/e85f6a0d5c9ea1f32f5013c3fa34e4fc146cd0eb/src/event/event_windows.c#L240)	C
[Inline Frame] dispatch.dll!_dispatch_muxnote_release(dispatch_muxnote_s * dmn) Line 265	C
[Inline Frame] dispatch.dll!_dispatch_event_merge_pipe_handle_read(dispatch_muxnote_s * dmn, unsigned long dwBytesAvailable) Line 669	C
dispatch.dll!_dispatch_event_loop_drain(unsigned int flags) Line 915	C
dispatch.dll!_dispatch_mgr_invoke() Line 5419	C
dispatch.dll!_dispatch_mgr_thread(dispatch_lane_s * dq, dispatch_invoke_context_s * dic, <unnamed-tag> flags) Line 5447	C
[Inline Frame] dispatch.dll!_dispatch_continuation_pop_inline(dispatch_object_t dou, dispatch_invoke_context_s * dic, <unnamed-tag> flags, dispatch_queue_class_t dqu) Line 2496	C
dispatch.dll!_dispatch_root_queue_drain(dispatch_queue_global_s * dq, unsigned int pri, <unnamed-tag> flags) Line 6114	C
dispatch.dll!_dispatch_worker_thread(void * context) Line 6250	C
dispatch.dll!_dispatch_worker_thread_thunk(void * lpParameter) Line 6272	C
[External Code]

I suspect this is not an Cobalt/ARM64 specific issue, but is more likely a long-standing bug which has become common on this particular line of CPUs due to some scheduling or timing change.
The interesting section is here:
https://github.com/apple/swift-corelibs-libdispatch/blob/e85f6a0d5c9ea1f32f5013c3fa34e4fc146cd0eb/src/event/event_windows.c#L667-L669
The event set here is used to synchronize with the pipe monitoring thread, which itself calls _dispatch_muxnote_retain.Perhaps a change in timing affected the typical order of operations here, although I haven't been able to prove this yet.
I'm trying to reproduce the crash under LIBDISPATCH_LOG to get some more information.

I guess there is some flaw in muxnote management which makes whole URLSession a bit unstable on non-Darwin platforms (not only Windows). For sockets, it is possible to over-release a muxnote object under heavy usage, because register and unregister code is running on different threads. Perhaps this also affects pipes. Would be nice to investigate this further though.


Refactor Vacuum code to properly handle path url encoding

Which Delta project/connector is this regarding?

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

Description
This is intended to handle special characters in the table path. For context, DV team recently made a change to include special characters in all paths used by tests.
As of today, the paths we get from listing are not url encoded -- they get url-encoded later in the logic. However, paths contained in delta log files are already url encoded. To keep these two things compatible, this change makes the file names from listing to be url encoded and changes the later logic to not url encode again.
How was this patch tested?
Existing tests
Does this PR introduce any user-facing changes?
NO

jenkins merge

jenkins merge


Intersect rework

Intersect trait was removed and replaced with Continuous and Discrete traits according to #2.
For now they're implemented only for a few types.
Fixes #2

@kvark please merge it for now. It needs more work to be done, but I will do it in future PRs.

Hm, actually, I need to rebase it on current master.

Also, thanks @torkleyy for the review!


[IMPAC-622] threshold tooltip

@cesar-tonnoir here is the threshold tooltip rebased on top of v.1.6.1. I have applied your refactors as well.
I could not assign the switch like you wanted to in the kpi.svc:
host = switch.kpi.source
    ...

As one of the cases return $q.reject(err)

@cesar-tonnoir I have added commits to:

[ ] flag impac dependency in Changelog
[ ] clean up toastr error/success messages

Missing:

[ ] remove outline from kpi threshold buttons when loading


Hotwords not respected after PR #856

the test video is https://www.youtube.com/watch?v=Ybu6qTbEsew
if no hotwords
segments, info = model.transcribe(input_file, beam_size=5, language="en", vad_filter=False, vad_parameters = dict(min_silence_duration_ms=1000))

the result is:
“[261.76s -> 263.12s] The first thing you need to do is,
[263.12s -> 265.36s] of course, to copy the web address
[265.36s -> 266.12s] up here.
[266.12s -> 267.84s] Then you go into your Conf UI
[267.84s -> 270.04s] folder, again in the Conf UI
[270.04s -> 272.08s] folder, in there in the custom
[272.08s -> 274.08s] nodes folder and then up here
[274.08s -> 276.28s] in the address bar type CMD,
[276.28s -> 277.40s] hit enter.
[277.40s -> 279.40s] This opens up your command
[279.40s -> 281.24s] window. In here you type
[281.24s -> 283.36s] git clone and then
[283.36s -> 285.32s] put the web address and hit
[285.32s -> 287.36s] enter to clone the git
[287.36s -> 289.68s] project into your custom
[289.68s -> 290.56s] nodes folder.
[290.56s -> 291.60s] After you've done this, you're going
[291.60s -> 293.32s] to find in here the Conf UI”

if add hotwords
segments, info = model.transcribe(input_file, hotwords="the video is about comfyUI", beam_size=5, language="en", vad_filter=False, vad_parameters = dict(min_silence_duration_ms=1000))

the result is same:
"
“[261.76s -> 263.12s] The first thing you need to do is,
[263.12s -> 265.36s] of course, to copy the web address
[265.36s -> 266.12s] up here.
[266.12s -> 267.84s] Then you go into your Conf UI
[267.84s -> 270.04s] folder, again in the Conf UI
[270.04s -> 272.08s] folder, in there in the custom
[272.08s -> 274.08s] nodes folder and then up here
[274.08s -> 276.28s] in the address bar type CMD,
[276.28s -> 277.40s] hit enter.
[277.40s -> 279.40s] This opens up your command
[279.40s -> 281.24s] window. In here you type
[281.24s -> 283.36s] git clone and then
[283.36s -> 285.32s] put the web address and hit
[285.32s -> 287.36s] enter to clone the git
[287.36s -> 289.68s] project into your custom
[289.68s -> 290.56s] nodes folder.
[290.56s -> 291.60s] After you've done this, you're going
[291.60s -> 293.32s] to find in here the Conf UI”

@MahmoudAshraf97 will you find time to take a look? Thx.

I will, can you share the output before # 856?

segments, info = model.transcribe(input_file, hotwords="the video is about comfyUI", beam_size=5, language="en", vad_filter=False, vad_parameters = dict(min_silence_duration_ms=1000))
[261.76s -> 263.12s] The first thing you need to do is,
[263.12s -> 264.84s] of course, to copy the web
[264.84s -> 266.68s] address up here, then you go
[266.68s -> 268.48s] into your comfyUI folder,
[268.48s -> 270.80s] again in the comfyUI folder,
[270.80s -> 272.48s] in there in the custom nodes
[272.48s -> 274.28s] folder, and then up here in the
[274.28s -> 276.28s] address bar type cmd,
[276.28s -> 277.40s] hit enter.
[277.40s -> 279.40s] This opens up your command
[279.40s -> 281.20s] window. In here you type
[281.20s -> 283.08s] git clone and
[283.08s -> 285.00s] then put the web address and
[285.00s -> 286.92s] hit enter to clone
[286.92s -> 288.88s] the git project into
[288.88s -> 290.56s] your custom nodes folder.
[290.56s -> 291.48s] After you've done this, you're
[291.48s -> 293.32s] going to find in here the comfyUI

I tested on different materials. It seems like the hotwords option is not respected.

@MahmoudAshraf97 I forgot to add - the hotwords option is not respected in standard and batching interference.

I just tested the video you shared and hotwords worked as expected on several models, although smaller models were less affected, but still affected nonetheless. As for batched transcription, I'm working on adding hotwords support.


Sanitize dictionary inputs

It didn't work for me when my dictionary contained floats instead of strings:
values_dict = {'field': 7.2}
fillpdfs.write_fillable_pdf(input_filename, output_filename, values_dict)

But if I just wrap all dictionary values in a str() call then it works.

Had the same issue with the same solution - casting to string solves the problem nicely.

@stevobailey @patrick-osborne Thanks for the input, I added this to the code.


Validate Prometheus/Metrics in Operator

make sure that prometheus.enabled = true does what we need.

I think prometheusrule config is different in the armada helm charts -- see armada/deployment/armada/templates/prometheusrule.yaml.


ENH: Restructure custom ops

Starting from a discussion in our last monthly call... It makes the repository significantly easier to maintain if each contribution is binned into an API format. Some contributions are not derived from something as standardized as a Keras API though so we want a category where we could build more fluid guidelines. It also makes the directory structure more approachable from the root tensorflow_addons directory. That was a problem in the tf.contrib directory.
I would imagine this being the final directory layout for our first release. That's not to say we won't have more additions, but that these 4 directories will round out the APIs and we can start building more thorough docs for all of them

@av8ramit could you confirm that the python2 is failing because of CI debugging? It's passing for me locally and I know you're working with #48

The test error is indeed in the testing setup ( @av8ramit , for your reference: chmod: cannot access ‘/.../bazel_wrapper.py’: No such file or directory) -- I think it's safe to trust your local testing for now.


v0.7.3

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

not worth it... https://github.com/JuliaMath/openlibm/compare/v0.7.3...v0.7.4


Unable to support the Alamofire 5.0

pod 'Filestack' has dependency with Alamofire 4.x.x version. However, I have a Alamofire 5.0 which works fine for other pods (with dependency on alamofire). How to resolve this issue ?

@ashish7-iOS Thanks for reporting! As a matter of fact, we have just removed our dependency on AlamoFire on the latest release of Filestack (see 2.6.0.) so you should no longer have any issues using Filestack together with AlamoFire 5.x.

@ashish7-iOS Thanks for reporting! As a matter of fact, we have just removed our dependency on AlamoFire on the latest release of Filestack (see 2.6.0.) so you should no longer have any issues using Filestack together with AlamoFire 5.x.


PQ DAGs: Don't email on retry

It's noisy and it's dev.

FYI: @RobinL I've disable emails on retry for the PQ DAGs as it was annoying me and it's not very useful anyway. I'm just merging this.


Upgrade to Nikic parser 2

This package fixes the Nikic PHP parser dependency at 1.* which is ancient. Please upgrade!

Dependency has been updated and unit tests seem fine. Please point to master from now. A minor release will come soon if no problems arise.

Seems to be working fine.

Yes please release a 3.0.1, this is causing a version conflict with another package for me

Just released https://github.com/marcioAlmada/annotations/releases/tag/3.0.1
I apologize for the delay 😅


Complete rethink of the render lifecycle

At present, to change what's on-screen we need to re-render.  This is very expensive if there are complex animations on screen and causes total re-evaluation of the game state.
I was thinking we should probably instead define an entire animation during a render, and remove time-based mutation callbacks entirely.  This is a significant redesign.
I'd also like to add more scene graph and caching tech than we currently have.  This was originally going to do diffing, but I've found not bothering to be surprisingly effective.  If we're not bothering, a lot of the design decisions made before can be overruled.

Figuring out what to render (which could be multiple phases) on a state alone without mutating that state is actually rather fiddly.  I wonder if instead you should render a single phase at a time, also returning a mutation callback.  If there's a mutation callback, execute it and re-render.  Otherwise, loop the render.


An unhandled exception occurred while processing the request

InvalidOperationException: A view component named 'NToastNotify' could not be found. A view component must be a public non-abstract class, not contain any generic parameters, and either be decorated with 'ViewComponentAttribute' or have a class name ending with the 'ViewComponent' suffix. A view component must not be decorated with 'NonViewComponentAttribute'.
Microsoft.AspNetCore.Mvc.ViewComponents.DefaultViewComponentHelper.InvokeAsync(string name, object arguments)
New Text Document.txt
dotnetcore 3.1

closing due to inactivity


Fixing ingress version and adding new class parameter

Fixing ingress version depending on Kubernetes version
networking.k8s.io/v1beta1 is used from 1.14 to 1.18.
networking.k8s.io/v1 is used to 1.19+
reference: https://kubernetes.io/docs/reference/using-api/deprecation-guide/
Adding new parameter to inform ingress class
A new ingressClassName field has been added to the Ingress spec that is used to reference the IngressClass that should be used to implement this Ingress.
reference: https://kubernetes.io/blog/2020/04/02/improvements-to-the-ingress-api-in-kubernetes-1.18/#specifying-the-class-of-an-ingress

Awesome thanks @rafaelcam :+1: Thanks also for the references and explanations :bow:

@celanthe do you know why the CLAAssistant doesn't work here? Do I miss something?

@celanthe nevermind I have overseen the check


Session Expired Component Only in French

Issue and Steps to Reproduce
Once application has been successfully configured, when the session expires the component rendered is only in French. It would be great to be able to pass in a custom component for this - is there already a way?

Versions
3.1.7
Screenshots

Thanks so much @guillaume-chervet! Do you know how to simulate a "session lost" instance without having to wait for a session to actually expire? Also, are there props that get passed down to the sessionLostComponent parameter? Wondering if there is a refresh prop already available that's being passed in or if I have to explicitly call from the custom button...

It hard to simulate, it is easier with the comming v4 version => https://www.npmjs.com/package/@axa-fr/react-oidc-context
code here => https://github.com/AxaGuilDEv/react-oidc/pull/687


Support to write back exif data

so currently we are just reading it , i wonder can we make it write back like modify the data and write it back to file and trigger image download, it will be good privacy feature like if someone want to remove meta data from its images so that no one can track him.

Hello, thanks for reaching out. I have been considering and wanting do to something about this in some form (writing/modifying/replacing) but I unfortunately don't have that much time right now. Rewriting exifr to the form it is in now took me a whole last fall. And I can't dedicate this much time to writing-exif, because it would be a huge feat, even larger that adding support for new file formats.
But I'm not closing it because it's still on my mind.
related issues: #29 #32

Hi @MikeKovarik would it be easier to just remove the exif data?

Just adding support for this request. I have a need to randomize GPS location info in images at the client side, in the browser, before images get uploaded. I need to randomize the GPS location so it's somewhere within, say, 100 miles so the specific location of the image is not revealed. And I need to preserve other Exif tags as-is such as the camera make and model.


Fix copy buttons on the debug window

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
I fixed the issue, #3328. This problem occurred due to no textarea defined as red-ui-clipboard-hidden on the debug window. Therefore, I modified the code to add and remove the red-ui-clipboard-hidden on demand. (To solve this problem by another method, I thought that the navigator.clipboard.writeText(value) may be better than document.execCommand("copy") which is already deprecated.)
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 67.361% when pulling b00282590d728ad20c5a0fba1ff5fcf9abb9b038 on kazuhitoyokoi:master-fixcopybutton into aaa2b4c3db0f8bba9e2de909de8e1c97f15cdab4 on node-red:master.

Closing in favour of #3331


refactor: add more OS in 02_bug_report.yml

What is the purpose of this pull request?

[ ] New Icon
[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other: Refactor

Description

Add more OS in the ISSUE_TEMPLATE: This includes ChromeOS, iOS, and Android to ensure the report is concise as possible.
Before Submitting

[x] I've read the Contribution Guidelines.
[x] I've checked if there was an existing PR that solves the same issue.

This is supposed to be one PR with #2100, but I edit this on GitHub, not on VS Code. I have trouble installing pnpm because I wasn't the admin of my PC.

Thanks @chessurisme !

It is nice to work with Lucide, @ericfennis. You are very welcome.


REQUEST: Remove maintainer status at components-contrib for @artursouza

GitHub Username
@artursouza
Requirements

[X] I have reviewed the community membership guidelines (https://github.com/dapr/community/blob/master/community-membership.md)
[X] I have enabled 2FA on my GitHub account. See https://github.com/settings/security
[X] I have subscribed to the Dapr community Discord server
[X] I am contributing (any of the following apply: issues, discussions, PRs, reviews) to 1 or more Dapr repositories

List of contributions to the Dapr project
I would like to be removed from maintainer status at components-contrib repo. Please, do not add me as an approver, just remove from the maintainers' list at components-contrib. My goal is to dedicate my time to runtime and java-sdk repositories.

I think we should consider having an "emeritus" maintainer position (like http://technosophos.com/2018/01/11/introducing-helm-emeritus-core-maintainers.html). What do you think @artursouza?

I think it's a requirement for us to have emeritus status per CNCF guidelines.

LGTM. Let me create an issue for this and STC can vote.

I think we should remove all inactive approvers and maintainers after 6 months. And after 3 months we send a warning or something like that.
As for Emeritus maintainer - I commented on that issue - it's really just a shoutout to former maintainers in the respective repo's Readme. Nothing else, right?

it's really just a shoutout to former maintainers in the respective repo's Readme. Nothing else, right?

Correct

I think we should remove all inactive approvers and maintainers after 6 months. And after 3 months we send a warning or something like that.

Please, create a separate issue for that discussion. The scope of this issue is well defined.

Done. Removed myself.
It has been great helping with components-contrib in the past 4 years and proud to have helped onboard 2 more maintainers that have been doing an amazing job there. Thanks!


Onconflict leaks heap memory

It seems when a stigmergy message causes an onconflict to be called, memory is leaked from the system, which eventually can cause an out of memory error. The error is probably caused in the following lines. I tried to investigate what was leaking memory exactly, but I'm not familiar enough with the garbage collection of the vm yet.
Here is the C code to reproduce
#define FILE_TEST5 "resources/5_Onconflict.bbo"
TEST(vm_onconflict) {
    // Init VM
    vm = &vmObj;

    uint16_t robot = 0;
    bbzvm_construct(robot);
    bbzvm_set_error_receiver(&set_last_error);
    fbcode = fopen(FILE_TEST5, "rb");
    REQUIRE(fbcode != NULL);
    REQUIRE(fseek(fbcode, 0, SEEK_END) == 0);
    fsize = ftell(fbcode);
    REQUIRE(fsize > 0);
    REQUIRE(fseek(fbcode, 0, SEEK_SET) >= 0);

    bbzvm_set_bcode(&testBcode, fsize);

    REQUIRE(vm->state == BBZVM_STATE_READY);
    REQUIRE(bbzvm_register_functions() >= 0); // If this fails, it means that the heap doesn't have enough memory allocated to execute this test.

    // Stepping through script
    while (vm->state == BBZVM_STATE_READY) {
#ifdef DEBUG
        uint8_t instr = *vm->bcode_fetch_fun(vm->pc,1);
        if (instr > BBZVM_INSTR_CALLS) {
            printf("[%d: %s %d]\n", vm->pc, instr_desc[instr], *(int16_t*)vm->bcode_fetch_fun(vm->pc+1,2));
        }
        else {
            printf("[%d: %s]\n", vm->pc, instr_desc[instr]);
        }
#endif
        bbzvm_step();
        ASSERT(vm->state != BBZVM_STATE_ERROR);
    }
    ASSERT_EQUAL(vm->state, BBZVM_STATE_DONE);
    ASSERT_EQUAL(vm->error, BBZVM_ERROR_NONE);

    vm->state = BBZVM_STATE_READY;

    // Sending stigmergy message, will leak memory and eventually get an memory error
    uint8_t i = 0;
    while (1) {
        i++;
        bbzmsg_payload_t payload;
        uint8_t buff[] = {1, i, 0, __BBZSTRID_data, 0, 57, 2, 0, 1};
        bbzringbuf_construct(&payload, buff, 1, 16);
        payload.elsize = 1;
        payload.capacity = 10;
        payload.datastart = 0;
        payload.dataend = 9;

        bbzinmsg_queue_append(&payload);
        bbzvm_process_inmsgs();
        if(vm->error == BBZVM_ERROR_MEM){
            break;
        }

        bbzvm_gc();
    }

    // Runs out of memory
    ASSERT_EQUAL(vm->state, BBZVM_STATE_ERROR);
    ASSERT_EQUAL(vm->error, BBZVM_ERROR_MEM);

    bbzvm_destruct();
    fclose(fbcode);
}

Here is the buzz code from ressources/5_Onconflict.bzz
stig = stigmergy.create(0);
stig.onconflict(function(key, ld, rd) {
        return ld
})

Just to confirm, this issue is present only in BittyBuzz, not Buzz?

I did not test on Buzz, we only use BittyBuzz since we are on an embedded controller. It's been some time since I've checked this issues, I can try to reproduce it on Buzz


Disease code refactor (Part 1)

Refactored some of the code responsible for handling Actor's diseases.
For the most part, changes could be described as one of the following:

Styling improvements
Reducing code duplication (DRY)
Improving readability and adding JSDoc comments
Replacing .then() syntax with await syntax inside async function

But there are also several instances of actual changes and improvements, such as:

Adding await in places, where lack of it could lead to data loss and/or race conditions
Fixing actual errors.

I realize that most of these methods will need an additional pass when Disease are migrated (currently, I am unable to created new Items on this branch because of migration errors).
However, there are some lines that need an additional scrutiny:
### 1. Here, both "diseases" are not found in the compendiums, so lingeringDisease will always be null.
~~https://github.com/moo-man/WFRP4e-FoundryVTT/pull/1851/files#diff-c588f96685c7089ee5b43e41afbdb538af2993de610f58860343fe75a30cab2eR1414-R1418~~
Resolved in commits.
2. Here, the variable removeEffects was never defined (and if it were, it would already be an array, so the line itself is somewhat weird).
https://github.com/moo-man/WFRP4e-FoundryVTT/pull/1851/files#diff-c588f96685c7089ee5b43e41afbdb538af2993de610f58860343fe75a30cab2eR1426

New code will automatically set incubation.value to 0 in disease contracted from Lingering symptom.
I would suggest changing the Festering Wound (Compendium.wfrp4e-core.items.Item.kKccDTGzWzSXCBOb) incubation to 1d10 and days as unit. Currently unit is missing and incubation.value is not parseable.
I understand the need of clarification, but I think it should be moved to description.
Alternatively, we could modify the code to only try to parse stuff before a comma as roll formula.


how can i prevent the animation dom shake

<Motion style={{x: spring(isExpanded ? 30 : 0)}}>
  {({x}) =>
	<div style={{marginBottom: `${x}px`, marginTop: `${x}px` }}
	  className={classNames(style.loadableListItemContainer,
		isExpanded ?
		style.loadableListItemContainerExpand
		: style.loadableListItemContainerNormal
	  )}
	>
	  {this.renderHeader()}
	  { isExpanded &&  this.renderExpand() }
	</div>
  }
</Motion>

It is not clear what you mean by dom shaking. Code seems correct
Check your styles in css classes and any othe css you have applied to tge component
If you want to get more help, please create codepen/jsbin with your issue so we can reproduce it

I've solved this problem by reseting style value to 0.1
I think reseting x to zero create conflictions with some properties like margin and padding (happened to be padding with mine)
Try <Motion style={{x: spring(isExpanded ? 30 : 0.1 )}}>


Unable to use the Cntl + Shit + Up/down arrows to move lists in particular notes[BUG]

Describe the bug
I am unable to use the ctrl + shift + up/down arrow in certain notes to move lists up and down while it works fine in other notes.
To Reproduce
Steps to reproduce the behavior:

I create a new  note and create a list as shown in the screen recorder. Moving the list works fine.
When I try to do the same on my other document it doesn't work.
Yet when I copy that same data from the second note into the first note it does allow me to move the lists up and down

Expected behavior
I expect to be able to use the ctrl + shift + up/down arrow commands to move lists up and down.
Screenshots
https://drive.google.com/file/d/1ySQWhzP163R_6dRi_NeQW5N78jEPDINN/view
Desktop (please complete the following information):

OS: Windows
Obsidian Version: 1.0.3

Additional context

@sammychambers Thank you for your feedback.
The plugin is very strict about list line indents. If you have mixed up tabs/spaces or the wrong number of tabs/spaces, it will break the entire list.
Currently the plugin can't help identify the problem, but I have that idea in the plans.


Union.StrictOptional

🍩 Feature Request
Is your feature request related to a problem?
Yes. I am using Union.Strict to create a safe version of a table insert from a schema where an account must discriminate on a type literal. For example (not real), if the type column was user, it would allow the email column to be populated. If the type column was team, it would allow the memberCount column to be populated.
Uses Union.Strict gives the right answer:
type Schema =
  | { name: string, type: "user", email: string }
  | { name: string, type: "team", memberCount: number }
type InsertType =
  | { type: "user", email: string, memberCount?: undefined }
  | { type: "team", email?: undefined, memberCount: number }

There is no similar generic to handle an update. In this case, the update would require the discriminant to be provided in order to complete the discriminated field.
type Schema =
  | { name: string, type: "user", email: string }
  | { name: string, type: "team", memberCount: number }
type UpdateType =
  | { name?: string, type: "user", email?: string, memberCount?: undefined }
  | { name?: string, type: "team", email?: undefined, memberCount?: number }
  | { name?: string, type?: undefined, email?: undefined, memberCount?: undefined }

The discriminant can be determined by identifying the literals (which can conveniently be found in the newly added Any.Literal method!)
Describe the solution you'd like
Would be grateful for there to be a Union.PartialStrict method which did this magically.
Describe alternatives you've considered
I tried writing this but I'm getting stuck on some of the TypeScript around unions and updating each member of the union independently (they seem to merge so that I end up with type: "user" | "email" instead of keeping them separate). I don't have a solution yet.
Teachability, Documentation, Adoption, Migration Strategy
StrictPartial is like Strict but it allows partial completion while still allowing the discriminants to properly discriminate properties on the object. In order for this to work, to update any discriminated properties, the discriminant must be provided.

1: So if I understood well, you determine the fields to make undefined based on the schema that is be queried?
2: Why not remove the fields that are useless, is it to keep it generic (which is great)?
memberCount?: undefined is not needed if it's a type: "user"
3: In your second example, what is the meaning of, why have this?
{ name?: string, type?: undefined, email?: undefined, memberCount?: undefined }
instead of just:
  | { name?: string, type: "user", email?: string, memberCount?: undefined }
  | { name?: string, type: "team", email?: undefined, memberCount?: number }

4: If you ended up with type: "user" | "email" its probably because you forgot to distribute over the parent union:
type t0 = UpdateType extends unknown
		  ? // do your stuff here
		  : never

This will force a union to get distributed.

You are correct about 2! It's over-specified. The original reason was that it allowed the setting of null values in some place (i.e. it was something like email?: undefined | null) but as I was playing around with code, I removed the null for simplicity in thinking (fix a smaller problem first); however, I think it needs to be back in there with some more thinking or we can get inconsistent data.
For example, if we had a record:
const record = {name: "john", type: "user", email<EMAIL_ADDRESS>
// And we updated with

const update = {type: "team", memberCount: 10}

// We'd end up with

const updatedRecord = {name: "john", type: "team", email<EMAIL_ADDRESS>memberCount: 10}

I think I have to  spec this a little better...
With respect to 3, within the limits of the conversation without any null, it probably could be reduced to:
  | { name?: string, type: "user", email?: string }
  | { name?: string, type: "team", memberCount?: number }
  | { name?: string }

The third line was to allow name to be set without type since it's not being discriminated against.
But also, thank you so much for that tip about distributing over unions. There is so much undocumented (or poorly documented) stuff in TypeScript and precious few experts at it.

This is why you never explain things when you are tired. Let's retcon that last post.
The reason why I needed the undefined was because I was allowing extra arbitrary properties to pass through.
This...
type UpdateType =
  | { name?: string, type: "user", email?: string, memberCount?: undefined }
  | { name?: string, type: "team", email?: undefined, memberCount?: number }
  | { name?: string, type?: undefined, email?: undefined, memberCount?: undefined }

Would ultimately be joined with { [key:string]: any }
type UpdateType = (
  | { name?: string, type: "user", email?: string, memberCount?: undefined }
  | { name?: string, type: "team", email?: undefined, memberCount?: number }
  | { name?: string, type?: undefined, email?: undefined, memberCount?: undefined }
) & { [key:string]: any }

The ?: undefined were there so that the { [key:string]: any} wouldn't allow in a value for the discriminated properties. This is like Union.Strict which adds the undefined properties but this does the same thing for partials. The third row is to not allow entries into the discriminated properties when there is no discriminant present.

I built a version of the function as a reference. The idea of StrictPartial is generic but it is specific in that it handles discriminants in a specific way as to prevent bad states.
type Schema =
  | { type: "user"; user_id: number }
  | { type: "email"; email: string; auth_token: string }

// prettier-ignore
type Flatten<T> =
  T extends infer U ? { [K in keyof U]: U[K] } : never

type MapUndefinedToOptional<T extends object> = T extends unknown
  ? Object.Optional<T, Object.SelectKeys<T, undefined>>
  : never

// prettier-ignore
type MapNonLiteralToIncludeUndefined<T extends object> = {
  [K in keyof T]:
    Any.IsLiteral<T[K], string> extends 1
    ? T[K]
    : T[K] | undefined
}

// prettier-ignore
type StrictPartialFromStrict<ST extends object> =
  | MapUndefinedToOptional<MapNonLiteralToIncludeUndefined<ST>>
  | { [K in Union.Keys<ST>]?: undefined }

type StrictPartial<T extends object> = StrictPartialFromStrict<Union.Strict<T>>

type UpdateSchema = Flatten<StrictPartial<Schema> & { [key: string]: any }>

assertType.equal<
  UpdateSchema,
  | {
      [x: string]: any
      user_id?: number | undefined
      email?: undefined
      auth_token?: undefined
      type: "user"
    }
  | {
      [x: string]: any
      user_id?: undefined
      email?: string | undefined
      auth_token?: string | undefined
      type: "email"
    }
  | {
      [x: string]: any
      type?: undefined
      user_id?: undefined
      email?: undefined
      auth_token?: undefined
    }
>(true)

I don't think that well find a place for this in the standard library. There you go:
type Schema =
  | { name: string, type: 'user', email: string }
  | { name: string, type: 'team', memberCount: number }

type UpdateType =
  | { name?: string, type: 'user', email?: string, memberCount?: undefined }
  | { name?: string, type: 'team', email?: undefined, memberCount?: number }
  | { name?: string, type?: undefined, email?: undefined, memberCount?: undefined }

type Updater<Schema extends object> =
    // first we create a record that is a schema with all possible properties to which we add `{name?: string}`
    O.Record<U.Exclude<O.Keys<Schema>, 'name'>, never, ['?', 'W']> & {name?: string} extends infer CommonSchema
    ? (
      Schema extends unknown                                      // then we go over the union of Schema so that
      ? O.Required<O.Unionize<CommonSchema & {}, Schema>, 'type'> // each union member of Schema gets
      : never                                                     // gets unionized, fills the CommonSchema
      ) | A.Compute<CommonSchema> // finally we add the empty common schema for passing arbitrary properties
    : never

type t0 = Updater<Schema>                     // it works well
type t1 = O.Diff<Updater<Schema>, UpdateType> // spec compliant

We could write a generic version, but it would not work for your use-case. Still looking into it. Btw, you can use A.Compute instead of Flatten :)

@thesunny I found real generic solution. This is more elegant, since you can tell which types not to make Optional:
type Schema =
  | { name: string, type: 'user', email: string, nick: string}
  | { name: string, type: 'team', memberCount: number, nicks: string}

type UpdateType =
  | { name?: string, type: 'user', email?: string, memberCount?: undefined }
  | { name?: string, type: 'team', email?: undefined, memberCount?: number }
  | { name?: string, type?: undefined, email?: undefined, memberCount?: undefined }

type StrictOptional<O extends object, required extends A.Key = never> =
    U.Strict<O> extends infer OS
    ? OS extends unknown
      ? O.Optional<OS & {}, U.Exclude<O.Keys<OS & {}>, required>>
      : never
    : never

type t0 = StrictOptional<Schema | { name: string }, 'type'>
type t1 = O.Diff<StrictOptional<Schema>, UpdateType>

Notice that I had to add { name: string } after schema. And notice also that you can specify fields that must not be made optional.
I called it StrictOptional because I don't use the term Partial.

@thesunny do you want me to add it to the standard library?

Maybe this could fit into the Commiunity module.

Hi @pirix-gh, I will look at it today.
Thank you for your all your work on ts-toolbelt.

@pirix-gh after working with it, this feels complex:
type t0 = StrictOptional<Schema | { name: string }, "type">

We need to know that we have to | the { name: string} in order to not have it in the discriminated portion.
Repetitive as we already specified that name is a string { name: string }

If you felt inclined to pursue it, I wonder if this might provide a more intuitive UI.
type t0 = StrictOptional<Schema, "type", "email" | "memberCount">

We specify the Schema, the discriminant and then the discriminated properties. It's generic and intuitive. All the secondary arguments deal with the discriminant which will allow the secondary arguments to be optional. If they are omitted, we can return a type that does not discriminate any properties on the partial.
Feels like such a design would be a good candidate for inclusion.

I am not against the second version, but I see a limitation that I am not sure how to overcome cleanly: you see, Schema has 2 union members when the expected UpdateType has 3, this makes the distribution non-generic. Not 1-to-1.

This is why I added | { name: string }, so that we can map over 3 members.

I don't see any problem with discriminant and discriminated, we would just have to write a modified Strict version that can do that. Or maybe add this feature to Scrict too.

I may be misunderstanding the issue but can't we do something like:
type StrictOptional<T, Discriminant, Discriminated> =
  | OTHER_PROCESSING_HERE
  |
    Object.Optional<
      {
        [K in Union.Keys<T>]:
          K extends Discriminant ? undefined :
          K extends Discriminated ? undefined :
          T[K]
      },
      Discriminant | Discriminated,
      "flat"
    >

Well, that's partially what I did in https://github.com/pirix-gh/ts-toolbelt/issues/114#issuecomment-630760893
Otherwise it's completely OK that you have your own type for your own scenario, not everything has or can be generic. The most generic I can get is https://github.com/pirix-gh/ts-toolbelt/issues/114#issuecomment-630774344
And we could improve it with your suggestion type t0 = StrictOptional<Schema, "type", "email" | "memberCount">.
The thing is that you need to add | { name: string } to make your case generic, it's completely normal. To me this this simply means that you are going to allow something that does not have a type and other untracked properties.
Or maybe it's the fact of adding name by hand that disturbs you? Maybe you would like that to be generic for reasons that are not obvious to me. In this case, we can also do something.
Or, you could just create a type wrapper that hides this away, after all.

Thank you again for your work.
I think you've taken it farther than you needed to already and I think I'm convinced that it may not be generic enough for inclusion. If somebody else comes in asking for something similar or the same, it could be worth revisiting. :)

Great. As long as your problem got solved and that your software is correctly typed :) I would definitely take a look again if more people need it, and add it to the community.
Writing types is not easy, unfortunately, I have to keep the standard library case-agnostic while trying to satisfy most use-cases... Which leads people to compose their own case-specific types. And when none of this applies, I'm there to help :)
Thank you, you're welcome to ask more questions! Thanks for supporting the project.
Cheers


In API v2 GET /registrations/{id}/files/ - files relationship points to nodes directory

For example:
https://api.osf.io/v2/registrations/fjguy/files/
Shows the following value in relationships.files.links.related.href:
https://api.osf.io/v2/nodes/fjguy/files/osfstorage
which leads to a "Not Found" response.  Manually entering the following path displays the expected data:
https://api.osf.io/v2/registrations/fjguy/files/osfstorage

Well, that shouldn't happen. I've made an issue for it in Jira. We should get to it soon. Hopefully it should be an easy fix.


T: Theme and topic template - Modèle de thème et de sujet

Alpha prototypes are here:
https://tbs-proto1.openplus.ca/en/landing/working-for-government
https://tbs-proto1.openplus.ca/en/government/publicservice/pay.html

I thought we were getting rid of the doormat text (the blurb below the H1) in the new topic patterns?

@cfarquharson you're talking about the description right before the Most requested? We haven't started documenting the guidance on this (I'm hoping to start today), but I was thinking of making that text optional (the image as well would be optional). There may be situation where it's warranted to add that description, IMO - but there are situations where it would not be needed.

@quidampepin yeah, that's the text I'm talking about.  I'm OK if it's optional, I just don't want it required :)

@quidampepin
Also, can https://tbs-proto1.openplus.ca/en/landing/working-for-government double as a 'campaign' page?  I think the graphic space is inline with a campaign's desire for that extra-something-special, while freeing up the content area to be 'back-to-business'.

As as I'm concerned, the same type of design could be used in a campaign page, yes. Also, by allowing some graphic treatment on these pages, we're hoping that the temptation to use a campaign page would be reduced...

@quidampepin @cfarquharson IA considerations to this line of thinking? we have always wanted to keep campaigny stuff outside of the main theme & topic structure...

looping in @patlaj

@pcwsmith I'm not sure that the design impacts the IA of it, as it's just a visual treatment to the H1 container.   This design, stemming from the homepage of Canada.ca seems to be flexible enough to be repurposed beyond the homepage, as it's now the institutional profile, and the 'decorated' topic page.  I'm just suggesting that we firm it in as the design-of-choice for any page that needs that extra oomph.

@quidampepin Can you add in the sign-in/register button to the patterns too?  I believe you have them placed top-right in other patterns

@pcwsmith in my mind, this is a bit like the Spotlight pattern. It allows "some" visual treatment to satisfy the appetite for this - so campaign pages could be used only when there is a real campaign (so: some kind of promo, a temporary page for it, a call to action, etc.). Sometimes, the campaign page has been used just to circumvent the lack of visual treatment on topic pages, for example. This i what we want to avoid.
@cfarquharson you mean: add the sign-in button to the list of patterns to work on (not necessarily strictly on the theme/topic template, right?)

@quidampepin Yep, that's what I mean for the sign-in :)

Done!

Draft guidance: https://design.canada.ca/mandatory-templates/theme-topic-alpha.html
Very draft coded layout (missing some custom CSS): https://design.canada.ca/coded-layout/theme_topic_guidance.html

Latest prototypes:
THEME: https://tbs-proto1.openplus.ca/en/landing/working-for-government
TOPIC: https://tbs-proto1.openplus.ca/en/government/publicservice/pay.html

I get that this is supposed to be about the visual design, but why did you also change the content to remove military tasks from the Public service and military theme?
On the theme page, you removed

"military" from the title,
"Benefits and services for the military" from Services and Information, and
"Military Pay" from Most requested.

Despite them being some of the most clicked items on the page, and without consulting DND or the TBS theme leads (Véro). Why?

@ecoops: I agree that using this example may have been a bit clumsy. The point was really about the design, not the content. That specific page comes from an optimization project we did with the Public service pay information (where we experimented with using "Working for the government instead of "Public service and military", and it did work better for public servants...). Vero's team was indeed involved in the project. But we're not saying right now to change the name of the theme (because of course it would no longer work for military). In our current project, we're also testing some tasks with veterans. Maybe (and I really say MAYBE - it wouldn't happen without working with DND!) a new audience/theme called "Veterans and military" (and keeping "Working for the government" for public servants) would work better. But this wouldn't happen without testing, consulting, etc. Bottom line: we are NOT advising or requesting any change to these pages at the moment. It was just to show, in the open, the latest version of the prototype.

The template is now in Beta:

https://design.canada.ca/mandatory-templates/theme-topic.html
https://conception.canada.ca/modeles-obligatoire/theme-sujet.html


[CCXDEV-6254] Add smart proxy V2 rule content

Part of CCXDEV-6254. Needed to uncomment the tests at https://github.com/RedHatInsights/insights-results-smart-proxy/blob/master/content/content_test.go#L63.

ok

Could you please merge? I don't have write access. TY!

ok

@tisnik Could you please merge? I don't have write access. TY!

Yes sir!


Discoverability of YAML config files in the manager Activity log

API Services Portal Issue

User Story

As an API provider,
I want to reference Gateway configuration files in the API Services Portal
so that I know which files were applied to any given Gateway.
Test Case
ENV

[x] DEV
[ ] TEST
[x] PROD

TESTCASE

Navigate to the Activity log for a specific gateway https://api.gov.bc.ca/manager/activity
It's possible to reference the YAML file that was used for Gateway config by selecting the More details action on a " published gateway configuration" item:

A modal dialog will open upon interaction to show the contents of the config file:

EXPECTED

I'm concerned about the usability of the modal, specifically the call to action for the interaction (More details) and the modal title (Activity Details). I'm wondering if the modal component is used for any other purpose on the Activity page. If not, then we should consider renaming both items. It may also be helpful to include a modal description. I will also note that no reference is made in the DevHub documentation that the config file can be surfaced in this manner.
ACTUAL

As described above.
ERROR

Notes
This is an observation I made after discussion with a client in which we were trying to locate a Gateway configuration file and the Activity log was brought up as a possible source.

I have been thinking about this user story as well. One could approach this on an slightly more fundamental level which is to say there should be an API endpoint for retrieving gateway configuration (most recent, or potentially also historical). Then we could also integrate this function into the gwa-cli.
One unfortunate aspect of the current way gw config is provided from the /activity endpoint is that it is in Kong format, rather than the resource-based format we recommend and use in our tutorials (see docs for more on formats), regardless of the format the config was sent in. It isn't overly difficult for a user to do the conversion, but it would be nice to save them the effort.
So IMO, the acceptance criteria for work on providing access to current config would be to give an option to get gw config in Kong or resource-based format (if plan to continue supporting both).
We might also consider supporting the export of other resources (Products, Datasets, etc) in the Gateway, alongside the gw config.


[FancyZones] Remember Window's Original Position

Summary of the new feature/enhancement
Currently, if I put a window into a zone, then take it out of the zone, it retains the size of the zone. There should be an option for it to go back to it's original, or "pre-zoned" size.
Proposed technical implementation details (optional)
Essentially providing an option (and I think it should be an option, not a forced feature) that's similar to the way Windows' built-in window snapping works. By default on Windows 10, if you snap into the left or right, or in 1 of 4 grids, and then drag the window out of it, it'll return to it's pre-snap size. It will also help it feel like a more built-in feature.

Hi @iamkevinmccarthy
this feature request is tracked by https://github.com/microsoft/PowerToys/issues/166
Closing this as duplicate.
Thanks.


Error C1083 in only PIO project generated with the Code Generator // Problems to access 'pico/stdlib.h': No such file or directory

Hello,
Please, I am a new programmer under VS Code.
On a windows 10 computer (Spanish) I was able to compile manually all the examples but I tried the code generator with new projects under VSC (Windows 64) and I always got errors, when I compiled the first generated example code. The example code it is very usefully.
I always run the VSC from "Visual Studio Code for Pico" access. I tried the Raspberry Pi environment configuration from a PDF instructions file and it failure  in compile the example generated with Code Generator.
Now I selected the easiest example, with only PIO and debug with serial interface but I could not compile the generated code.
I received always error. The error is "C1083: Cannot open file include: 'pico / stdlib.h': No such file or directory".
The   hardware/divider.h library generated errors too.
Test: I added to CMakeList the stdlib but it did not solved the problem.
I added to CMakeList the hardware_divider and it clean the warning but I got other errors.
      # Add any user requested libraries
      target_link_libraries(cm04_rfi01
              pico_stdlib
              hardware_pio
              hardware_divider
              )

Please, I tried many options during days; I cannot confirm where the problem is.
Thanks
CMakeLists.txt
pico_PIO_With_Code_generator.zip

It looks like you were able to get the development tools installed and running with no issue, since you mention that you got the examples compiled.
Please post your issue in the Raspberry Pi Pico Forum, there is a good chance somebody will be able to help you over there.
Closing since this is not an issue with this project.

Hello,
Thanks for your suggestion.
I will uninstall all and I install again all the C compiler plus VSC.
Regards

I don't think reinstalling will help here. It seems your dev toolchain is fine to me. Please post the details of the issue on the forum like I suggested, and I'm sure you will get some helpful hints there.


Set v1.0.1

What does this PR do?

Sets the version to v1.0.1.

How should it be tested manually?
yarn test
# or
npm test

Pull Request Test Coverage Report for Build 11

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

Totals

Change from base Build 9:
0.0%

Covered Lines:
56

Relevant Lines:
56

💛  - Coveralls


jest 0.5.x: eval strict function and new expression

With vm.runInContext and jsdom 5.4.3, we started to get ReferenceError issues:
describe('strict eval', function() {
  it('eval', function() {
    var code = [
      'var _bar = 10;',
      'function foo() {',
      '  "use strict";', // because of this
      '  return _bar;',
      '}',
    ].join('\n');

    eval(code);

    new foo(); // Reference error: _bar is not defined
  });
});

Thus it relates only to "use strict" inside the function, without it, _bar is available in the new foo() call.
The vm.runInContext seems works fine in isolation in this case. Can be jsdom related?
CC @ide, @domenic

OK, it's nevertheless issue of vm.runInContext. If a code is wrapped into a function, then eval strict function inside that function, don't capture the bindings.
This works (file test.js):
var code = `
var foo = {m: 1};

function bar() {
  "use strict";
  return foo;
}
`;

eval(code);

bar();

Node session:
> vm.runInNewContext(fs.readFileSync('/Users/dmitrys/test.js', 'utf-8'))
{ m: 1 }
>

This doesn't:
function main() {

  var code = `
    var foo = {m: 1};

    function bar() {
      "use strict";
      return foo;
    }
  `;

  eval(code);

  bar(); // foo is not defined

}

main();

Node session:
> vm.runInNewContext(fs.readFileSync('/Users/dmitrys/test.js', 'utf-8'))
undefined:6
      return foo;
             ^
ReferenceError: foo is not defined
    at bar (eval at main (evalmachine.<anonymous>:13:8), <anonymous>:6:14)
    at main (evalmachine.<anonymous>:15:3)
    at evalmachine.<anonymous>:19:1
    at ContextifyScript.Script.runInNewContext (vm.js:18:15)
    at Object.exports.runInNewContext (vm.js:49:17)
    at repl:1:4
    at REPLServer.defaultEval (repl.js:154:27)
    at bound (domain.js:254:14)
    at REPLServer.runBound [as eval] (domain.js:267:12)
    at REPLServer.<anonymous> (repl.js:308:12)

Unless I'm missing something obvious from strict mode, it's probably a bug in vm module, and is not related to Jest or jsdom.

The exact same script source is passed to vm.runInContext and jsdom's evaluator: https://github.com/facebook/jest/blob/0.5.x/src/JSDomEnvironment.js#L110 and https://github.com/facebook/jest/blob/0.5.x/src/JSDomEnvironment.js#L132. And looking how jsdom evaluate scripts, it also uses vm.runInContext.
I repro'd your latest results where the same error occurs with both vm.runInContext and jsdom, even with plain function calls without new.
Another thing I noticed was that after the eval call, expect(_bar).toBe(10) throws an error since _bar is not defined. So either the eval is acting as some kind of indirect eval or it is using a different global scope.

Need to notice, this is test form io.js v2.3.1. With Node v.0.12 the vm.runInContext has even different behavior: the bar is not defined there.

OK, I filed this issue on io.js yet: https://github.com/nodejs/io.js/issues/2245, hope we'll get some clarifications. Though, it's currently a blocker for us at Facebook to switch to Jest 0.5 with io.js (CC @yungsters), and probably will be a blocker to merge 0.5 to master on August 1st as we planned.

This seems like it was fixed in node 4.


⚠ Bofrost.lu has degraded performance

In 91b1d82, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1221 ms

Resolved: Bofrost.lu performance has improved in f2ec788 after 17 minutes.


https got blocked cors

i was following this guide https://github.com/Rob--W/cors-anywhere/issues/371
but i have something problem https://stackoverflow.com/questions/69292208/certbot-is-working-on-nodejs-but-custom-port-not-work-properly-with-cors-anywher . i got blocked when using https.
my error :
Access to XMLHttpRequest at 'https://cors.xxxx.id/https://xx-xx.xxx.xx.zone/v2/payments' from origin 'https://xxx-xxx.xxxx.id'
has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-
Allow-Origin' header contains multiple values '*, *', but only one is allowed.

against, i tried click the url , its throw , Missing required request header. Must specify one of: origin,x-requested-with
[EDIT]
now i have trying to didnt make it redirect i follow some condition  so i would to fix my port can use https://cors.domain.id:3000 .
instead of manually create certbot i use
sudo certbot --nginx -d cors.domain.id -d cors.domain.id
then the file is generate on
lrwxrwxrwx  1 root root   42 Sep 23 06:46 cert.pem -> ../../archive/cors.domain.id/cert1.pem
lrwxrwxrwx  1 root root   43 Sep 23 06:46 chain.pem -> ../../archive/cors.domain.id/chain1.pem
lrwxrwxrwx  1 root root   47 Sep 23 06:46 fullchain.pem -> ../../archive/cors.domain.id/fullchain1.pem
lrwxrwxrwx  1 root root   45 Sep 23 06:46 privkey.pem -> ../../archive/cors.domain.id/privkey1.pem

server.js
const fs = require('fs');
// // SSL

// // Certificate - I copy the generate file into outside of project and change owner and permission to -R 777 just for testing
const privateKey = fs.readFileSync('./cert/privkey1.pem', 'utf-8').toString();
const certificate = fs.readFileSync('./cert/cert1.pem', 'utf-8').toString();
const ca = fs.readFileSync('./cert/fullchain1.pem', 'utf-8').toString();

// // Certificate - this not work, just throwing ENOENT
// const privateKey = fs.readFileSync('./etc/letsencrypt/live/cors.domain.id/privkey.pem', 'utf-8');
// const certificate = fs.readFileSync('./etc/letsencrypt/live/cors.domain.id/cert.pem', 'utf-8');
// const ca = fs.readFileSync('./etc/letsencrypt/live/cors.domain.id/fullchain.pem', 'utf-8');

my full server.js
const fs = require('fs');

const privateKey = fs.readFileSync('./cert/privkey1.pem', 'utf-8').toString();
const certificate = fs.readFileSync('./cert/cert1.pem', 'utf-8').toString();
const ca = fs.readFileSync('./cert/fullchain1.pem', 'utf-8').toString();

// Listen on a specific host via the HOST environment variable
var host = process.env.HOST || '<IP_ADDRESS>';
// Listen on a specific port via the PORT environment variable
var port = process.env.PORT || 8080;

var originBlacklist = parseEnvList(process.env.CORSANYWHERE_BLACKLIST);
var originWhitelist = parseEnvList(process.env.CORSANYWHERE_WHITELIST);
function parseEnvList(env) {
  if (!env) {
    return [];
  }
  return env.split(',');
}

var checkRateLimit = require('./lib/rate-limit')(process.env.CORSANYWHERE_RATELIMIT);

var cors_proxy = require('./lib/cors-anywhere');
cors_proxy.createServer( {
  originBlacklist: originBlacklist,
  originWhitelist: originWhitelist,
  requireHeader: ['origin', 'x-requested-with'],
  checkRateLimit: checkRateLimit,
  removeHeaders: [
    'cookie',
    'cookie2',
    'x-request-start',
    'x-request-id',
    'via',
    'connect-time',
    'total-route-time',
  ],
  redirectSameOrigin: true,
  httpProxyOptions: {
    xfwd: false,
  },
  key: privateKey,
	cert: certificate,
	ca: ca,
}).listen(port, host, function() {
  console.log('Running CORS Anywhere on ' + host + ':' + port);
});

if i make it redirect from https://cors.domain.id into http://cors.domain.id:3000 , error throw cors blocked.
start:1 Access to XMLHttpRequest at 'https://cors.domain.id/https://pxxxayments' from origin 'https://domain-domain.domain.id' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header contains multiple values '*, *', but only one is allowed.

Your server.js doesn't correctly configure https. For a correct example, see https://github.com/Rob--W/cors-anywhere/blob/02f0cbd9291eca55953406acc7f7f08c64d13454/test/test.js#L502-L505
The error message that you've pasted here cannot be generated by CORS Anywhere itself, you must have configuration issue elsewhere.
From the Stack Overflow post, it seems like you're trying to use nginx with a virtual directory. For an example of configuring nginx for use with CORS Anywhere, see https://github.com/Rob--W/cors-anywhere/issues/143#issuecomment-452468128


Make the projects inventory pipeline depends on folders.

Otherwise the scanner will complain if we only inventory org and projects.

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


deps: remove transformers

This is an upstream dependency

Codecov Report
Attention: Patch coverage is 52.00000% with 12 lines in your changes missing coverage. Please review.

Project coverage is 62.73%. Comparing base (0f7df61) to head (f64a5e9).
Report is 1 commits behind head on main.

Files
Patch %
Lines

src/vllm_tgis_adapter/__main__.py
42.85%
11 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #62      +/-   ##
==========================================
- Coverage   62.96%   62.73%   -0.24%
==========================================
  Files          18       18
  Lines        1288     1280       -8
  Branches      229      227       -2
==========================================
- Hits          811      803       -8
  Misses        399      399
  Partials       78       78

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

Done in https://github.com/opendatahub-io/vllm-tgis-adapter/pull/60


Have you tried to use DQN on the Carla environment?

I see you have DQN network on Chapter 6 and Carla environment on Chapter 8. Do you tried to train DQN on Carla env and how about the performance?

Yes. The DQN in chapter 6 ( which is actually a n-step double DQN) on an average required a minimum of 10M frames to converge to a good Q-function and therefore a reasonable driving policy.
You can set  "discrete_actions": True in the ENV_CONFIG and then use the DQN agent from Chapter 6 to train an agent in the CARLA environment.

Thank you for your reply. I made some changes on the code and I wonder how to choose the size of replay buffer based on Carla simluator environment.  I see that you choose 1e6, but this size is so large for the model to fill the pool.

@Derekabc: For deep RL and especially with DQN, the number of samples required to train a reasonably good policy in a complex environment like the driving environment, is large. A replay memory with a capacity of 1e6 for such an environment is reasonable if not a bare minimum.
Closing this item since there weren't any update. Feel free to re-open or create a new item if you need more info.


Random line break in middle of text inside  tags

Description
The results of beautification are not what I expect.
Expected Results
The beautified code should have looked like:

What it actually looks like:

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/anonymous/b381c33e49b46b32c1d8ac4ee2f0d568

Issue opened with JSBeautify

Closing this as a JS-Beautify bug.

Closing this as a JS-Beautify bug.

This was breaking tags for me as well with default settings.  Change your settings: Packages / Atom Beautify / Settings / HTML / Wrap line length to 0 to disable.


[Renderer] incorrect water culling under 3440x1440

Fixed in https://github.com/hzqst/MetaHookSv/releases/tag/v20241011a


[Feature] Order deps on resulting tables

First root deps (bold)
Then dev root deps (italic)
Then others (deps of deps, no highlight)

Closed in favor of #57


Bump iteratee and catbird versions

For Catbird 0.22 and iteratee 0.16.
Needed for Finch release: https://github.com/finagle/finch/pull/881

Thanks, @vkostyukov! Sorry for not getting to this yesterday, but will release shortly.


Added quirk for Schneider Wiser outlets

Based on the code supplied by krlssn in comment https://github.com/zigpy/zha-device-handlers/issues/1889#issuecomment-1337368444
I'm VERY new to the whole Python world so I feel totally lost when it comes to writing tests and honestly not capable of doing so currently. I'm currently trying to get a dev env setup with Python 3.12 but I get weird errors regarding building wheels and whatnot. I'll see if I can get that running...
Proposed change

Add quirks for Schneider Wiser outlets and how metering is calculated

Additional information

PR is based on the code attached to this comment: https://github.com/zigpy/zha-device-handlers/issues/1889#issuecomment-1337368444
I added the <SimpleDescriptor...> based on log information obtained via HA. I also attempted to verify other information by comparing to my 2-way Wiser outlet.
I have attached the info I got from HA so someone can look and confirm: Wiser-2way.json

Checklist

[ ] The changes are tested and work correctly
[ ] pre-commit checks pass / the code has been formatted using Black
[ ] Tests have been added to verify that the new code works

Also I would love some guidance on how I can test this on my HA Green that I'm running. Do I compile and upload as a custom component? I'd rather not screw it up since it works wonderfully at the moment, except for this little pesky thing with how numbers are reported :)

Also I would love some guidance on how I can test this on my HA Green that I'm running. Do I compile and upload as a custom component? I'd rather not screw it up since it works wonderfully at the moment, except for this little pesky thing with how numbers are reported :)

You can take a look at https://community.home-assistant.io/t/how-to-setup-local-zha-quirks/341226 on how to setup using a custom quirk.

Also I would love some guidance on how I can test this on my HA Green that I'm running.

You can take a look at https://community.home-assistant.io/t/how-to-setup-local-zha-quirks/341226 on how to setup using a custom quirk.

Also check out this PR with an end-user how-to guide for the readme -> https://github.com/zigpy/zha-device-handlers/pull/2419

@kosmiq Were you able to get this running and verify that it works for your plugs (by installing the file as a custom quirk)?

Pushed some small changes. This can be tested as a custom quirk using this: https://github.com/zigpy/zha-device-handlers/issues/1889#issuecomment-1901043565

@kosmiq Were you able to get this running and verify that it works for your plugs (by installing the file as a custom quirk)?

Hi! Not yet. It’s on my radar but life got in the way with Christmas and all. Still looking to find the time.

Tested here: https://github.com/zigpy/zha-device-handlers/issues/1889#issuecomment-1902459242
So, should be fine. Tests are also added.


Factory, privat constructor

I want to avoid other programmers to create new instances of my class by using the new word.
Therefore I create factory classes inside all of my entity classes and provide a private standard constructor private Entity(){} only to avoid instantiation via new but force them to use the factory instead.
public class Furniture {
    FurnitureView view;
    Player player;

   //enforces that nobody can create an instance via "new" from outside
   private Furniture() {}

    //Internal class, inherite from Factory<T,U> to enforce Create method to expect T,U parameters
    public class Factory : Factory<FurnitureView, Player, Furniture> {
    }
}

Now Zenject can't inject the view and player
My workaround is to just override create
public class Factory : Factory<FurnitureView, Player, Furniture> {
			public override Furniture Create(FurnitureView view, Player owner) {
				var res = base.Create(view, owner);
				res.View = view;
				res.Player = owner;
				return res;
			}
		}

But then Zenject will recognize the passed parameters as unnecessary
Error	1	ZenjectResolveException: Passed unnecessary parameters when injecting into type 'Furniture'.
So how can I solve this without creating a public constructor  public Furniture(FurnitureView view, Player owner){...} that serves for Zenject's constructor injection?

I just ran a quick test and Zenject appears to work fine with private constructors.
I think the reason it's complaining about unnecessary parameters is because the FurnitureView and Player methods are not marked with [Inject] and so Zenject doesn't know that it should inject into those.
What I would suggest is to add FurnitureView and Player parameters to your private constructor (this is even better than using [Inject] IMO)

Ah thanks.

What I would suggest is to add FurnitureView and Player parameters to your private constructor (this is even better than using [Inject] IMO)

This works fine.
closed


can add parquet output?

parquet is faster than csv more, and duckdb can read parquet so quickly.
I want use duckdb as plugin for postgre, need transfer data between each other.
if can read postgre by sql, then output parquet, it'll be so good!

Hi @wonb168 , connectorx currently focuses on in-memory destinations like dataframes. If understand your request correctly, you want to dump the result into parquet files. Can functions like to_parquet tackle your issue?


Question regarding HLS/HTTP

Hi, I have installed the pre-built version and want to enable HLS/HTTP. I am using the full.conf file but unable to get this work. Do i need to do a custom build, also you mention nginx, does this have to be installed separately? Basically I want all the features available in SRS. Thanks in advance.

Should never use full.conf, please follow the wiki step by step:

for HLS: https://github.com/simple-rtmp-server/srs/wiki/v1_EN_SampleHLS
for HTTP flv stream: https://github.com/simple-rtmp-server/srs/wiki/v2_EN_SampleHttpFlv


Add Twitter Bot logic

Changes add a script that executes a single tweet with the immediate Fixed APR reported.
Currently is using Testnet numbers. Sample Tweet below. The number for weth looks correct (I think) but the USDC number is quite obviously wrong. Not sure where that computation error is coming in. I also have several questions about how the addresses JSON file in the deployment repository is used and updated.
Mostly I am opening this draft pull request so that I can make sure this code is pushed somewhere remote in case my laptop dies suddenly.

Note: need to rebase to most recent main branch


undefined method `this_blogger?'

Sorry I'm a relative newbie to Rails. I read somewhere that setting "config.author_edits_only = true" with ensure only the author of a blog can change it. However when I set this I get
undefined method `this_blogger?'
I can see where it is using this_blogger in the code but i can't see where/how I'm supposed to set it?

Closed as no longer a part of blogit master


[BUG] Directors flagged as undefined variables

When linting my VCL with falco (via Terraform) I'm getting this error:
🔥 [ERROR] Undefined variable "alb_main"
in main.vcl at line 358, position 21
 358|  set req.backend = alb_main;

Relevant bits of VCL:
director alb_main random {
   .quorum = 10%;
   .retries = 5;
   {
    .backend = F_alb_main_0;
    .weight  = 100;
   }
}

In both my custom vcl_recv (and in the snippet Fastly auto-inserts, i should probably de-dupe them) I have:
set req.backend = alb_main;

Expected behavior
Fastly's Director documentation says:

Like backends, directors can be assigned to req.backend, and can also be used as a backend in other directors.

so I'd expect this to be ok.
Desktop
required

OS: MacOS 14.6.1
Shell zsh

🔥 [ERROR] Function "alb_main.backend" is not defined
in main.vcl at line 358, position 25
 358 |      set req.backend = alb_main.backend();
                             ^^^^^^^^^^^^^^^^

When I try to use the .backend() function, I'm getting this error.

I downloaded my actual VCL file from Fastly and ran the linting, and it didn't find these errors at all. I wonder if the way my backends are being generated from VCL don't include them, and they all get squashed together via Fastly's templating.

Hi @tibbon, thank you for reaching out to our project.
Just to confirm -  Is your director will be created via Terraform using this block?
Currently we're fetch Fastly resources only backend, dictionary, acls, snippets, and logging endpoints so director won't be fetched.

I downloaded my actual VCL file from Fastly and ran the linting, and it didn't find these errors at all. I wonder if the way my backends are being generated from VCL don't include them, and they all get squashed together via Fastly's templating.

On the actual generated VCL, Fastly will generate with registered directors so probably the linting will be fine.
If true for my confirmation, we will support director to solve it.


I created 2 virtualbox machines with vagrant.
1 manager with traefik & sonarqube
1 worker with sonarqube
When I tap "sonarqube.myapp" outside of the virtualbox I got a 404 error. But when I tap <IP_ADDRESS>:9000 I access to the home page of sonarqube.
What did you expect to see?
sonarqube home
What did you see instead?
404 error
Thanks for help.

Can you lease set the logs to debug for traefik using -l DEBUG , and give us a snippet of the logs?
I would like to see what the request it sees when it returns the 404.
Thanks!

I just reviewd this, and you have told traefik that your container listens on port 80, and then told docker to listen on port 9000:
 --label traefik.port=80 \
 --label traefik.frontend.rule=Host:sonarqube.myapp \
 --publish 9000:9000 \

@Chabane can we close this issue?

@ldez you can close it.
@dtomcej Thanks for your reply.


activate_aggressive setting is ignored (OSX/Homebrew/Fish)

Describe the bug
Even though activate_aggressive is set to true in the global config, the homebrew path is added in front of the mise paths:
mise settings

Key                  Value Source
activate_aggressive  true  ~/.config/mise/config.toml

echo $PATH

/opt/homebrew/bin /opt/homebrew/sbin /Users/bg/.local/share/mise/installs/ruby/3.1.4/bin /Users/bg/.local/share/mise/installs/node/16.20.2/bin /opt/homebrew/opt/mise/bin…

To Reproduce

install mise via homebrew on OSX (15.1.1)
Activate homebrew in config.fish: eval "$(/opt/homebrew/bin/brew shellenv)"
Open a new shell and check the $PATH variable

Expected behavior
Expeted behaviour is the mise paths being injected in first position of $PATH, which until recently worked fine.
mise doctor output
version: 2024.12.5 macos-arm64 (2024-12-10)
activated: yes
shims_on_path: no

build_info:
  Target: aarch64-apple-darwin
  Features: DEFAULT, NATIVE_TLS
  Built: Tue, 10 Dec 2024 18:39:48 +0000
  Rust Version: rustc 1.83.0 (90b35a623 2024-11-26) (Homebrew)
  Profile: release

shell:
  /opt/homebrew/bin/fish
  fish, version 3.7.1

dirs:
  cache: ~/Library/Caches/mise
  config: ~/.config/mise
  data: ~/.local/share/mise
  shims: ~/.local/share/mise/shims
  state: ~/.local/state/mise

config_files:
  ~/.config/mise/config.toml
  ~/Documents/git/bee/bee/.nvmrc
  ~/Documents/git/bee/bee/.ruby-version
  ~/Documents/git/bee/bee/Gemfile

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:

toolset:
<EMAIL_ADDRESS><EMAIL_ADDRESS>
env_vars:
  MISE_SHELL=fish

settings:
  activate_aggressive  true ~/.config/mise/config.toml

No problems found

I spent a couple hours on this but didn't really get anywhere. I attempted to reproduce by stepping through what mise does step-by-step:
mise activate --no-hook-env | source
mise hook-env | source
touch mise.toml
set -gx PATH /foo $PATH
mise hook-env | grep foo # noted that "/foo" was in the beginning, as expected
MISE_ACTIVATE_AGGRESSIVE=1 mise hook-env | grep foo # now "/foo" is behind mise tools, as expected

I also tried without that and much closer to your setup with ~/.config/mise/config.toml and not stepping through and also wasn't able to repro so idk at this point.

wait sorry, I think I just wasted my time, in your example the homebrew path should be after the mise tools. That's what aggressive does.

closing since this is behaving as expected, if you don't want that behavior then don't set aggressive

@jdx Thanks for looking into this! In my example agressive is set and still the brew paths come before the mise paths. I would expect it to be the other way around?
When I run mise activatein the shell one more time afterwards the order changes to the expected order.


Add documentation for testing a branch

What / why
Adding documentation for testing a branch of the gem.

was originally in dev docs, but multiple people expressed an inability to find it
removing from dev docs (originally at https://docs.publishing.service.gov.uk/manual/test-a-branch-of-the-components-gem.html)
adding it here to the gem will automatically include it in dev docs anyway
copied with no changes

Visual Changes
None.

Should we include the following on deploying to Integration? (I seem to remember I found this quite useful when testing with Whitehall)
In which case we would need to add information on updating Dockerfile to replace (or add) apt-get install -y build-essential nodejs with apt-get install -y build-essential nodejs git

I've not got experience of this - deploying to integration has always been just like deploying a regular branch, but presumably whitehall is a bit different? If you're able to write this section @jon-kirwan I'd be happy to include it.

Should we include the following on deploying to Integration? (I seem to remember I found this quite useful when testing with Whitehall)
In which case we would need to add information on updating Dockerfile to replace (or add) apt-get install -y build-essential nodejs with apt-get install -y build-essential nodejs git

I've not got experience of this - deploying to integration has always been just like deploying a regular branch, but presumably whitehall is a bit different? If you're able to write this section @jon-kirwan I'd be happy to include it.

Ah ok in which case if it's only for Whitehall maybe it's not necessary (since I think much of the Whitehall frontend has now been moved elsewhere to Collections or Government Frontend). Thanks, will re(approve)


[Refactor] Card

File Name
components/Cards/Card.tsx
Reason for Refactoring the Code

The prop type using an interface, to explicitly specify the expected props for the Card component.
declares descriptionRef as a reference to an HTML paragraph element, ensuring type safety and accurate type inference for the descriptionRef throughout the code
The null check before accessing scrollHeight and offsetHeight properties to avoid potential errors.

Checklist

[X] I have checked the existing issues.
[X] I have read the Contributing Guidelines.
[X] The changes don't break the code and don't introduce new functionality.
[X] I am willing to work on this issue (optional).
[X] I am a GSSoC23 contributor.

@Anmol-Baranwal sounds cool, you may start working on it :D


Update Ohai to 16.8.2 and pin chefstyle

This ohai should fix build failures and we don't need to pull chefstyle from git anymore since we only want the latest coming in on chef/chef master.
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

This looks to have fixed the failing TK tests, but some jobs still failed due to the docker rate limiting.

This looks to have fixed the failing TK tests, but some jobs still failed due to the docker rate limiting.


Update sql-vulnerability-assessment.md

Added PS cmdlets for Managed Instance as they were missing in the list. For consistency as this article covers both SQL DB and SQL MI, it is necessary to cover the instance level cmdlets as well.

@mokabiru : Thanks for your contribution! The author(s) have been notified to review your proposed change. @mibar

@barmichal - Could you review the proposed updates?
Also, when you can, would you change the metadata author value to your GitHub user name? PRMerger uses that value for notifications of PRs in the public repo (only ms.author should be your Microsoft alias). Thanks.

Hi @mokabiru - This pull request was opened in the public repository. Contributors who work in the Product Manager role should open pull requests in the private repository for advanced quality validations and staging. You also can sign off directly in the private repo, and some PRs qualify for auto-merge.
To edit an article in the private repo from within the documentation, after you select Edit on an article page,  add “-pr” to the repo name in the URL.
We’ll leave this PR for review in the public repo, but would you make future article updates in the private repo? Thanks!

Helpful links in the internal Microsoft Docs contributor guide:
Public vs. private repos | Move a commit to a different repo (public -> private) | GitHub for content reviews
Quick reference for contributing to the docs | Make changes to a Docs article | PR review quality criteria

Thanks for the update, Resent the PR in the Private Repo.


master to live

Docs Build status updates of commit 0c5e346:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Advertising/bingads-12/bulk-service/action-ad-extension.md
:white_check_mark:Succeeded

Advertising/bingads-13/bulk-service/action-ad-extension.md
:white_check_mark:Succeeded

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.


Vite dev server screen additional infos (mode, loaded env)

Description
As a developer using the dev server (vite) I'd like to see the mode passed with the --mode option, as well as the stack of .env var loaded.
Suggested solution
For mode, i guess directly here:
  VITE v5.4.11  ready in 171 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  Mode: development
  ➜  press h + enter to show help

For env, a new shortcut
  Shortcuts
  press e + enter to see the env files loaded
  press r + enter to restart the server
  press u + enter to show server url
  press o + enter to open in browser
  press c + enter to clear console
  press q + enter to quit

→
  Env files loaded:
  1. .env
  2. .env.local
  3. .env.development

Alternative
there's no real alternative, you can only console.log(import.meta.env) and compute the values mentally
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I think it makes sense to show the mode. But for the loaded env files, I guess you can know which file is loaded if you know which mode it's running in.