ng build --prod

ng build runs fine, but with --prod the following error occur
ERROR in ./src/$$_gendir/app/app.component.ngfactory.ts
Module not found: Error: Can't resolve 'ng4-loading-spinner/ng4LoadingSpinner.component' in '<PROJECT_PATH>/src/$$_gendir/app'
resolve 'ng4-loading-spinner/ng4LoadingSpinner.component' in '<PROJECT_PATH>/src/$$_gendir/app'
Parsed request is a module
using description file: <PROJECT_PATH>/package.json (relative path: ./src/$$_gendir/app)
Field 'browser' doesn't contain a valid alias configuration
after using description file: <PROJECT_PATH>/package.json (relative path: ./src/$$_gendir/app)
resolve as module
<PROJECT_PATH>/src/$$_gendir/app/node_modules doesn't exist or is not a directory
<PROJECT_PATH>/src/node_modules doesn't exist or is not a directory
/opt/node_apps/node_modules doesn't exist or is not a directory
/opt/node_modules doesn't exist or is not a directory
/node_modules doesn't exist or is not a directory
looking for modules in <PROJECT_PATH>/node_modules
using description file: <PROJECT_PATH>/package.json (relative path: ./node_modules)
Field 'browser' doesn't contain a valid alias configuration
after using description file: <PROJECT_PATH>/package.json (relative path: ./node_modules)
using description file: <PROJECT_PATH>/node_modules/ng4-loading-spinner/package.json (relative path: ./ng4LoadingSpinner.component)
no extension
Field 'browser' doesn't contain a valid alias configuration
<PROJECT_PATH>/node_modules/ng4-loading-spinner/ng4LoadingSpinner.component doesn't exist
.ts
Field 'browser' doesn't contain a valid alias configuration
<PROJECT_PATH>/node_modules/ng4-loading-spinner/ng4LoadingSpinner.component.ts doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
<PROJECT_PATH>/node_modules/ng4-loading-spinner/ng4LoadingSpinner.component.js doesn't exist
as directory
<PROJECT_PATH>/node_modules/ng4-loading-spinner/ng4LoadingSpinner.component doesn't exist

I am also getting the same issue, building with angular/cli --aot=true
(relative path: ./src/ng4-loading-spinner/ng4LoadingSpinner.service)
no extension
Field 'browser' doesn't contain a valid alias configuration
***\src\ng4-loading-spinner\ng4LoadingSpinner.service doesn't exist
.ts
Field 'browser' doesn't contain a valid alias configuration
***\src\ng4-loading-spinner\ng4LoadingSpinner.service.ts doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
***\src\ng4-loading-spinner\ng4LoadingSpinner.service.js doesn't exist
as directory
***\src\ng4-loading-spinner\ng4LoadingSpinner.service doesn't exist
looking for modules in ***\src
using description file: ***\package.json (relative path: ./src)
Field 'browser' doesn't contain a valid alias configuration
after using description file: ***\package.json (relative path: ./src)
using description file: ***\package.json (relative path: ./src/ng4-loading-spinner/ng4LoadingSpinner.service)
no extension
Field 'browser' doesn't contain a valid alias configuration
***\src\ng4-loading-spinner\ng4LoadingSpinner.service doesn't exist
.ts
Field 'browser' doesn't contain a valid alias configuration

Ya.. i believe that this issue is direct related whit aot... the flag --prod of ng build includes --aot during the build process... if i execute the build process "ng build --env=prod --output-hash none"  (ignoring --aot) every thing goes fine...

Hello @justogaiht  and @justogaiht ,
This is now fixed in the latest version 1.1.1.
Please reopen the issue if you still face the same. :+1:
Thank you.


fix: App crashes on restart in android

Fix: When we navigate back and exit from the application and then trying to restore it - application crashes.

test branch_sdk#master


v1.80.2 breaks ability to install .vscode-server into running pod

Type: Bug
When attaching VSCode to a k8s pod, the installation of the code server fails from v1.80.2 onwards. I tried investigating to see what could be causing this issue, but in the diff between tags I haven't been able to find much info.
This is the full log of the attempted installation:
[73 ms] Dev Containers 0.304.0 in VS Code 1.80.2 (2ccd690cbff1569e4a83d7c43d45101f817401dc).
[72 ms] Start: Resolving Remote
[89 ms] Start: Run: wsl -l -v
[265 ms] Could not connect to WSL.
[266 ms] Command failed: wsl -l -v
[267 ms]
Copyright (c) Microsoft Corporation. All rights reserved.

Usage: wsl.exe [Argument]

Arguments:

    --install <Options>
        Install Windows Subsystem for Linux features. If no options are specified,
        the recommended features will be installed along with the default distribution.

        To view the default distribution as well as a list of other valid distributions,
        use 'wsl --list --online'.

        Options:
            --distribution, -d [Argument]
                Specifies the distribution to be downloaded and installed by name.

                Arguments:
                    A valid distribution name (not case sensitive).

                Examples:
                    wsl --install -d Ubuntu
                    wsl --install --distribution Debian

            --inbox
                Install the optional Windows feature instead of the version available via the Microsoft Store.

            --no-distribution
                Do not install a distribution (cannot be used with --distribution).

            --no-launch, -n
                Do not launch the distribution after install.

            --web-download
                Download the most recent version of WSL from the internet instead of the Microsoft Store.

    --list, -l [Options]
        Lists distributions.

        Options:
            --online, -o
                Displays a list of available distributions for install with 'wsl --install'.

    --status
        Show the status of Windows Subsystem for Linux.

    --help
        Display usage information.

[267 ms]
[271 ms] Start: Run: kubectl exec -it [redacted cluster and pod names] -- /bin/sh -c VSCODE_REMOTE_CONTAINERS_SESSION='3fd25137-d8ba-46d2-ac2e-c8043cbe0dcb1691507695095' /bin/sh
[340 ms] Start: Run in container: echo $PATH
[2094 ms] /opt/conda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
[2095 ms] Unable to use a TTY - input is not a terminal or the right kind of file
[2096 ms] Start: Run in container: id -un
[2159 ms] jovyan
[2160 ms]
[2162 ms] Start: Run in container: uname -m
[2230 ms] x86_64
[2230 ms]
[2231 ms] Start: Run in container: (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
[2287 ms] NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
[2288 ms]
[2289 ms] Start: Run in container: getent passwd jovyan
[2342 ms] Start: Run in container: test -d /home/jovyan/.vscode-server
[2402 ms]
[2403 ms]
[2405 ms] Start: Run in container: test ! -f '/home/jovyan/.vscode-server/data/Machine/.writeMachineSettingsMarker' && set -o noclobber && mkdir -p '/home/jovyan/.vscode-server/data/Machine' && { > '/home/jovyan/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
[2456 ms]
[2456 ms]
[2456 ms] Exit code 1
[2457 ms] Start: Run in container: cat /home/jovyan/.vscode-server/data/Machine/settings.json
[2529 ms]
[2529 ms] cat: /home/jovyan/.vscode-server/data/Machine/settings.json: No such file or directory
[2529 ms] Exit code 1
[2531 ms] Start: Run in container: test -d /home/jovyan/.vscode-server/bin/2ccd690cbff1569e4a83d7c43d45101f817401dc
[2593 ms]
[2594 ms]
[2594 ms] Exit code 1
[2595 ms] Installing VS Code Server for commit 2ccd690cbff1569e4a83d7c43d45101f817401dc
[2597 ms] Start: Downloading VS Code Server
[2597 ms] 2ccd690cbff1569e4a83d7c43d45101f817401dc linux-x64 stable
[3091 ms] read ECONNRESET
[3092 ms] Retrying to download VS Code Server.
[3486 ms] Start: Installing VS Code Server
[3487 ms] Start: Run in container: mkdir -p /home/jovyan/.vscode-server/bin/2ccd690cbff1569e4a83d7c43d45101f817401dc_1691507701803
[3542 ms]
[3542 ms]
[3544 ms] Start: Run in container: (dd iflag=fullblock bs=8192 count=0 2>/dev/null; dd iflag=fullblock bs=0 count=1 2>/dev/null) | tar --no-same-owner -xz -C /home/jovyan/.vscode-server/bin/2ccd690cbff1569e4a83d7c43d45101f817401dc_1691507701803
[3603 ms]
[3604 ms]
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
[3604 ms] Exit code 2
[3604 ms] Start: Run in container: rm -rf /home/jovyan/.vscode-server/bin/2ccd690cbff1569e4a83d7c43d45101f817401dc_1691507701803
[3664 ms]
[3665 ms]
[3667 ms] Start: Downloading VS Code Server
[3667 ms] 2ccd690cbff1569e4a83d7c43d45101f817401dc linux-x64 stable
[4018 ms] read ECONNRESET
[4019 ms] Retrying to download VS Code Server.
[4137 ms] Start: Installing VS Code Server
[4137 ms] Start: Run in container: mkdir -p /home/jovyan/.vscode-server/bin/2ccd690cbff1569e4a83d7c43d45101f817401dc_1691507702453
[4191 ms]
[4191 ms]
[4194 ms] Start: Run in container: (dd iflag=fullblock bs=8192 count=0 2>/dev/null; dd iflag=fullblock bs=0 count=1 2>/dev/null) | tar --no-same-owner -xz -C /home/jovyan/.vscode-server/bin/2ccd690cbff1569e4a83d7c43d45101f817401dc_1691507702453
[4248 ms]
[4249 ms]
gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
[4249 ms] Exit code 2
[4250 ms] Start: Run in container: rm -rf /home/jovyan/.vscode-server/bin/2ccd690cbff1569e4a83d7c43d45101f817401dc_1691507702453
[4312 ms]
[4313 ms]
[4319 ms] Command in container failed: (dd iflag=fullblock bs=8192 count=0 2>/dev/null; dd iflag=fullblock bs=0 count=1 2>/dev/null) | tar --no-same-owner -xz -C /home/jovyan/.vscode-server/bin/2ccd690cbff1569e4a83d7c43d45101f817401dc_1691507702453
[4320 ms] gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
[4320 ms] Exit code 2

VS Code version: Code 1.80.2 (2ccd690cbff1569e4a83d7c43d45101f817401dc, 2023-07-27T20:40:28.909Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Connection to 'notebook in jupyter-hidalgo-20rey-20inigo-20tea-2da (axso4prod4aa4core4acr.azurecr.io/dslab-jupyter-final:2-0-2)' could not be established

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.76GB (14.03GB free)

Process Argv
--crash-reporter-id 0e6f97b0-e405-4b57-bcb9-afa6854f08b0

Screen Reader
no

VM
0%

Connection to 'notebook in jupyter-hidalgo-20rey-20inigo-20tea-2da (axso4prod4aa4core4acr.azurecr.io/dslab-jupyter-final:2-0-2)' could not be established
Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
282f8724:30602487
f6dab269:30613381
vscrpc:30673769
showlangstatbar:30737416
vsctsb:30748421
03d35959:30757346
24365598:30736109
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofb:30804716
pythonnosmt12:30797651
pythonidxptcf:30805731
pythonnoceb:30805159
e537b577:30795824
dsvsc013:30795093
dsvsc014:30804076

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.81.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

The issue remains in the latest version. It first appeared in v1.81.0 and I traced backwards to my previous installation which did work, v1.80.1

Any update?

There seems to be an issue when downloading the server, are you behind a network proxy?
Could you enable trace logging in the user settings, retry and share the log from that?


Fix CarbonPlan hub health check failures

After deploying #1642, I ran into the same error message I reported in #1611. Since both the CarbonPlan and Openscapes hubs allow choosing of environment images for each machine profile, I figured it was the same bug and applied the fix from #1639 to the CarbonPlan hubs. However, the health check is still failing when I run it locally 🤔

Which logs need to be inspected? I had k logs -c hub hub-xxxx --follow running while I ran the test, but it wasn't very informative, just showed the startup time increasing

I've figured out the issue. We have this schema [...].value.slug: value. It wasn't working because I had something like: [...].python_trace.slug: python when it should have been: [...].python.slug: python. I can see the deployment-service-check pod pending now. I'll push a new commit.

Wooo, passing locally now!


Fix camel case  - 1979

[Auto generated]
Number: [#1979]

openshift-python-wrapper[pull_request][4e63-11ef-89d2-709198e2adec][PR 1979]: Closing issue for PR: Fix camel case .
PR was closed.


Set the Font Family of an Element passes with incorrect code

A camper pointed out that this challenge can be passed with the following code:
var code = "formatted";

CatPhotoApp

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

Purr jump eat the grass rip the couch scratched sunbathe, shed everywhere rip the couch sleep in the sink fluffy fur catnip scratched.

This does not meet the objectives of the lesson (make all of your p elements use the Monospace font), but both Takumar and I were able to recreate the issue.
Suggested solution: adjusting the test
"tests": [
        "assert($(\"p\").css(\"font-family\").match(/monospace/i), 'Your p elements should use the font Monospace.')"
      ]

When discussing with Takumar, he found that the next challenge, "Import a Google Font", has a similar test and could also be adjusted. (I did not verify his finding, as i don't know how to check the tests, but trust his assessment :) )

I agree, this needs to be fixed.  @rphares - this is your chance!  You can fix this and file a PR!  It'll be epic!

I would like to work on this issue if possible.

Go for it @JayaDarby!  I was just giving @rphares a hard time.  :wink:

Ok I will fix this today.

I have a fix I think, but can't test yet cause I have to head to work and couldn't get mongo installed in time.
https://github.com/robjloranger/FreeCodeCamp/tree/fix/%236286_font-family


how can I get the userID from direct message

I try to solve it but failture so how can I get the userID from direct message

Please use #matrix-bot-sdk:t2bot.io for support


GEOMESA-3326 Ingest from stdin even if an SFT and converter are not specified

Cache any bytes that the schema inference functions read from the stdin input stream - preventing those functions from consuming those bytes and leaving behind nothing for the actual ingest to read

Implement this logic by creating a new wrapper class for StdInHandle

Flip the lat/lon columns - this fixes a bug where a SimpleFeature wasn't getting ingested due to a latitude < -90
Add a comment about an unused parameter

looks like there are some build errors that need fixing:

/home/runner/work/geomesa/geomesa/geomesa-accumulo/geomesa-accumulo-tools/src/test/scala/org/locationtech/geomesa/accumulo/tools/ingest/IngestCommandTest.scala:120: value readNBytes is not a member of java.io.InputStream
Error:        stream.readNBytes(3)

@adeet1 have you tested this through the CLI tools themselves (vs in a unit test)? if not, could you try that out? using redis might be an easy way, as you can run a redis instance just with docker run --rm -p 6379:6379 redis:latest

also, looks like some conflicts from main have crept in... could you merge in main and fix the conflicts? thanks!

@elahrvivaz I've pushed some commits that should now make the CLI tools do the schema inference and run the ingest successfully.
However, the "cache bytes when reading from stdin" unit test is passing, with and without these fixes. I think the next step will be to change the unit test such that it fails without the fixes.


Can we have a shortcut for the substitute-over-range that makes it apply over the whole file?

Currently it would be something like gg<leader>s<motion1>G or if you had a textobject for 'whole file' it would be <leader>s<motion1>ie. which isn't too bad but could be better.
Perhaps, for maximum flexibility add a configuration option that would allow to specify <motion2> (the range over which to substitute) from the call in the keymapping. Then we could put ie, ip, or whatever else might be most common for our workflow.

Btw, thanks for the plugin, I had a very adhoc janky version of the functionality that I wrote myself that I have just replaced with yours because it seems more polished.

Nice idea, I will try to do something soon.

I've tried something here, can you try this ?

With a quick test it works great, thanks.
The only thing is that because vim doesn't have a 'whole file' textobject the user would have to define that themselves, I don't know if you might want to provide an example of that or provide a separate option for whole file (which could literally just not specify the range in the :s/// command)
map("o", "ie", "<cmd>normal! mzggVG<cr>`z", {noremap=true,silent=true})

I don't think that it's the scope of this plugin to provide motions. For my part, I use https://github.com/kana/vim-textobj-entire to do this and I prefer let users map their own motions.
Maybe it could be an option, I will think about it.
For the moment, I think I will just merge this PR and improve this later.
Thanks for this suggestion (and for the support ;) )


Option to disable Copilot for certain directories / files whose path matches certain patterns

Motivation
I want to disable Copilot for my university assignments to avoid the risk of cheating. So I want to disable Copilot for all files in a particular directory.
Feature Request
Add an option to disable Copilot for certain directories or files whose path matches certain patterns.
Or provide example config scripts if this can be done by the user without modifying the plugin. I tried running setup conditionally and using autocmd but with no luck.

I'll think about making this an official feature, but in the meantime, this code works perfectly for me:
local disable_dir = vim.fn.expand('$HOME/.config/nvim_configs') .. '/*'

vim.api.nvim_create_autocmd({"LspAttach"}, {
  pattern = disable_dir,
  callback = function (lsp_args)
    if lsp_args['data'] and lsp_args.data['client_id'] then
      local client = vim.lsp.get_client_by_id(lsp_args.data.client_id)

      if client.name == 'copilot' then
        vim.lsp.stop_client(client.id, true)
      end

    end
  end
})

Obviously you will need to change the disable_dir path to be wherever it is you do your work as well as run the above before copilot is launched

Might be worth adding:

:Copilot disable to stop the client
:Copilot enable to start the client (only if copilot.setup() was already called, otherwise it won't know the config)

As there's no documentation for #127, I'm wondering how it resolves this issue.

Or you can use the 'exrc' option from latest neovim.
And for your specific repo, create a file called .nvim.lua and do:
vim.cmd("Copilot disable")

A working solution is already provided in @zbirenbaum's comment, and this issue is supposed to be tracking a built-in solution. I'm fine if the built-in solution is not implemented right now, but I don't think this issue should be closed as a result of Copilot disable.
BTW, the LspAttach and lsp.stop_client based solution seems better to me. It directly hooks the LSP event instead of relying on the somehow indirect DirChanged event, and different buffers can have different LSPs attached.

That comment is quite old and not really what you want. Even if you do lsp.stop_client, when you open another file it'll start the server again. Copilot will be attached to the new buffer, LspAttach will be triggered again, you'll do lsp.stop_client again... and it'll go on for each new file you open. So the plugin is not completely disabled/stopped.
On the other hand :Copilot disable completely disables the plugin. It does lsp.stop_client under the hood along with other stuffs (e.g. cleaning up autocmds created by copilot).
But you don't specifically need to use DirChanged, you can do the same thing with LspAttach autocmd. It'll run when copilot is initially attached on a buffer, and immediately disable it.
I don't want to add some super specific config option for disabling copilot for certain directories/files patterns. The :Copilot disable solution is flexible enough to satisfy any use-cases. I hope that makes sense.
@zbirenbaum what do you think?

That comment is quite old and not really what you want. Even if you do lsp.stop_client, when you open another file it'll start the server again. Copilot will be attached to the new buffer, LspAttach will be triggered again, you'll do lsp.stop_client again... and it'll go on for each new file you open. So the plugin is not completely disabled/stopped.

I don't want to completely disable it. I just want it to be disabled when the file is in some directory. If I open a file in another directory, Copilot should be working there.

I don't want to completely disable it. I just want it to be disabled when the file is in some directory. If I open a file in another directory, Copilot should be working there.

Not sure about the use-case. Can you explain a bit about how you're using neovim?
- dir-a
  - dir-x
    - file-x-1
    - file-x-2
  - dir-y
    - file-y-1
    - file-y-2
- dir-b
  - file-b-1
  - file-b-2

Open Neovim in dir-a, then you want copilot to be disabled for files inside dir-a/dir-x but enabled for files inside dir-a/dir-y?
Open Neovim in dir-a, you want copilot to be disabled for all files inside it. Open another Neovim in dir-b, you want copilot to be enabled for all files inside it?
Open Neovim in dir-a/dir-x, you want copilot to be disabled. Then change the directory using :cd ../dir-y command to dir-a/dir-y and want copilot to be enabled?

Or something else?

Ideally, whether Copilot is working or not should depend only on the path of the file being edited (whether the path matches a pattern), not where I initially opened neovim, not which files I opened before, and not where the PWD is.
I don't understand your example, because you didn't specify which directory is the directory where I want to disable Copilot.

I'm commenting here because the "closed this as completed in #127" made me think a built-in solution was added in #127 and I missed it. I'm happy with the lsp.stop_client based solution, so it's OK for me to close this as a no-fix, but not as implemented.

Hmm... I think I misunderstood your problem. Now I understand exactly what you want.
I'd suggest to modify the solution from https://github.com/zbirenbaum/copilot.lua/issues/74#issuecomment-1301498938 to this:
  local augroup = vim.api.nvim_create_augroup("copilot-disable-patterns", { clear = true })
  for _, pattern in ipairs({ "/dir-a/dir-x/*", "/dir-b/*" }) do
    vim.api.nvim_create_autocmd("LspAttach", {
      group = augroup,
      pattern = pattern,
      callback = function(args)
        vim.api.nvim_buf_call(args.buf, function()
          vim.cmd("Copilot detach")
        end)
      end,
    })
  end

vim.lsp.stop_client kills the whole server. So all the files copilot is currently attached will get detached, not just the specific file from your pattern. :Copilot detach will only affect the current buffer.
Whether this will be included in the plugin's config is up to @zbirenbaum .
The downside of adding it to plugin's config is that the patterns will need to be hardcoded in config. And directory structure is different for different machines (i.e. config won't be portable between machines).
Keeping it outside plugin's config let's you use it from .nvim.lua file (i.e. with 'exrc' option). So you can add these autocommand only for a specific repo.
I'm keeping the issue open for zbirenbaum's decision.

vim.lsp.stop_client kills the whole server. So all the files copilot is currently attached will get detached, not just the specific file from your pattern. :Copilot detach will only affect the current buffer.

I realized this but I thought it was not a big problem in my workflow, and I didn't notice the new :Copilot detach. Thanks for the new config as it does look much better.

I changed the callback to this:
    callback = function(args)
      local client = vim.lsp.get_client_by_id(args.data.client_id)
      if client.name == 'copilot' then
        vim.defer_fn(function()
          vim.cmd("silent Copilot detach")
        end, 0)
      end
    end,

Without vim.defer_fn it shows "not attached", and the command output is noisy so silent.

Based on the functions suggested by @MunifTanjim, @ouuan  and @zbirenbaum I wrote this one to exclude a number of directories and empty buffers with cwd matching any of the disable_dirs:
local augroup = vim.api.nvim_create_augroup("copilot-disable-patterns", { clear = true })
local disable_dirs = {
    vim.fn.expand "$HOME/Documents" .. "/*",
}
for _, pattern in ipairs(disable_dirs) do
    vim.api.nvim_create_autocmd("LspAttach", {
        group = augroup,
        pattern = "*", -- This pattern will match all files, including new buffers
        callback = function(args)
            -- Check if the buffer has a name (file associated) or if CWD starts with /home/user/Documents
            local bufname = vim.api.nvim_buf_get_name(0)
            local cwd = vim.fn.getcwd()

            if bufname == "" and cwd:match("^" .. pattern) or bufname:match(pattern) then
                local client = vim.lsp.get_client_by_id(args.data.client_id)
                if client.name == "copilot" then
                    vim.defer_fn(function()
                        vim.cmd "silent Copilot detach"
                    end, 0)
                end
            end
        end,
    })
end

But the "silent" part seems not to work - I get 202 "Detached buffer(id:1) from client (id:1)" messages.
Apart from the noise - why does the plugin/copilot tries repeatedly to attach again to the buffer after being detached?

Many of the recent approaches react to the LspAttach event. This means the LSP client was started and attached already.
I am asking myself: Does this already provide information to the LSP we would rather not reveal?
Also not knowing the overall architecture the vim.defer_fn look suspicious. Why is this needed? Is there a short time where data might reach the LSP?
If the goal is to prevent data be handled by copilot, I think we should cut it of as soon as possible. Scanning through the code the plugin, I see https://github.com/zbirenbaum/copilot.lua/blob/b03617a6dc4bc88b65ab5deac1631da9a9c2dcaf/lua/copilot/util.lua#L99C12-L99C25 which can prevent the LSP client from actually being attached. I personally would rather like to see a feature hooking in there. That would give me a way better feeling that the exclusion actually works as intended.
Do you think it would be possible to provide a customizable API, something which allows configurations like this?
require("copilot").setup({
    -- ... other options ...
    should_attach = function()
       -- Custom conditions come here.
       return true
   end
})

It would be very handy to have access to the current buffers filename and the cwd. To enable filtering based on paths.


M3-4345 [CMR] NodeBalancer Landing Table

Description
This adds CMR styles for NB Landing table. This one wasn't using the EntityTable pattern so to keep the conditional consistent I added that pattern here.
I didn't include responsive styles in this PR.
Type of Change

Non breaking change ('update', 'change')

Note to Reviewers
The usual: please check all table functions both with CMR and without.

Actually @Jskobos I went ahead and added the header to this PR, if you could take a look again: https://github.com/linode/manager/pull/6665/commits/cf58b9227bc30e16a20f673b2fc9f25f97a84128


Add relocated snakeyaml to shaded Jar

Signed-off-by: Ahmed Hussein (amahussein<EMAIL_ADDRESS>Fixes #152

Change core/pom.xml to relocate the or.yaml.* package and include it in the jar

I tested the Jar by running the wrapper on both dataproc2.1 and dataproc2.0 and it does not fail.


Porting the benchmarks proofs to the haskell backend

List of the proofs to be ported:

[x] tests/specs/benchmarks/address00-spec.k: https://github.com/kframework/evm-semantics/pull/839
[ ] tests/specs/benchmarks/bytes00-spec.k
[ ] tests/specs/benchmarks/ecrecover00-siginvalid-spec.k
[ ] tests/specs/benchmarks/ecrecover00-sigvalid-spec.k
[ ] tests/specs/benchmarks/ecrecoverloop00-sig0-invalid-spec.k
[ ] tests/specs/benchmarks/ecrecoverloop00-sig1-invalid-spec.k
[ ] tests/specs/benchmarks/ecrecoverloop00-sigs-valid-spec.k
[ ] tests/specs/benchmarks/ecrecoverloop02-sig0-invalid-spec.k
[ ] tests/specs/benchmarks/ecrecoverloop02-sig1-invalid-spec.k
[ ] tests/specs/benchmarks/ecrecoverloop02-sigs-valid-spec.k
[ ] tests/specs/benchmarks/encode_keccak00-spec.k
[ ] tests/specs/benchmarks/encodepacked_keccak01-spec.k
[ ] tests/specs/benchmarks/keccak00-spec.k
[x] tests/specs/benchmarks/overflow00-nooverflow-spec.k: https://github.com/kframework/evm-semantics/pull/851
[x] tests/specs/benchmarks/overflow00-overflow-spec.k: https://github.com/kframework/evm-semantics/pull/851
[ ] tests/specs/benchmarks/requires01-a0gt0-spec.k
[ ] tests/specs/benchmarks/requires01-a0le0-spec.k
[ ] tests/specs/benchmarks/staticarray00-spec.k
[ ] tests/specs/benchmarks/staticloop00-a0lt10-spec.k
[x] tests/specs/benchmarks/storagevar00-spec.k: https://github.com/kframework/evm-semantics/pull/857
[ ] tests/specs/benchmarks/storagevar01-spec.k
[ ] tests/specs/benchmarks/storagevar02-nooverflow-spec.k
[ ] tests/specs/benchmarks/storagevar02-overflow-spec.k
[ ] tests/specs/benchmarks/storagevar03-spec.k

Haskell backend issues:
Completeness:

https://github.com/kframework/kore/issues/1945

Usability of kore-repl:

Major:

https://github.com/kframework/kore/issues/1955
https://github.com/kframework/kore/issues/1960

Minor:

https://github.com/kframework/kore/issues/1946
https://github.com/kframework/kore/issues/1957


cannot launch docusaurus docs

cannot run existing docs. Crashes with exception
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
at new NodeError (node:internal/errors:387:5)
at validateString (node:internal/validators:162:11)
at Object.join (node:path:429:7)
at Object.module.exports [as plugin] (D:\pct4\pct-docs\pct4-docs\node_modules@lunaticmuch\docusaurus-terminology\src\index.js:27:27)
at initializePlugin (D:\pct4\pct-docs\pct4-docs\node_modules@docusaurus\core\lib\server\plugins\init.js:83:61)
at async Promise.all (index 6)
at async initPlugins (D:\pct4\pct-docs\pct4-docs\node_modules@docusaurus\core\lib\server\plugins\init.js:91:21)
at async externalCommand (D:\pct4\pct-docs\pct4-docs\node_modules@docusaurus\core\lib\commands\external.js:17:21)
at async file:///D:/pct4/pct-docs/pct4-docs/node_modules/@docusaurus/core/bin/docusaurus.mjs:231:3 {
code: 'ERR_INVALID_ARG_TYPE'
termsURL is undefined here, dunno why because in default options it is given but it's not relative.
I've managed to override those with a tuple config ['@lunaticmuch/docusaurus-terminology', { termsUrl: './docs/terminology', termsDir: './docs/terminology'}] but now it says that

despite pointing to real folder with .md files in it.

gr8 job from Pytak. It works now but there's another issue. URL which is generated for replaced item points into wrong place, e.g. http://localhost:3000/docs/developer-guides//docs/terminology/applicationTemplate

Oh I missed this. Is it still current?

This is now being fixed in version 2 out later today


Hide namespace cli commands that are no longer relevant

Motivation
Explain here the context, and why you're making that change.
What is the problem you're trying to solve.
Modifications
Describe the modifications you've done.
Result
After your change, what will change.

@merlimat

what is the reason for hiding this command?

In 2.0 the concept of cluster in a topic name goes away. Plus I believe we(and the rest of the industry) have standardized on the keyword topic. The hiding is to make sure that legacy users still have access to the old way.

what is the reason for hiding this command?

pulsar-admin namespaces destinations $MY_NAMESPACE
was converted into pulsar-admin namespaces topics $MY_NAMESPACE.
Initially, I used an alias in JCommander, but that doesn't really work (and also leaves topics(destinations) in the help text which is confusing.
Documentation will refer only to the preferred way, but old command will still work.


pi-hole and 1300+ "Number of non-domains on this list:"

hi, i use pi-hole and it says about 1300 of the domains out of 3500 or so on the list cannot be imported.
i still see ads but i will try to restart the spotify app on ios as i didnt do that
ill report back but comments are welcome

ah i just had to copy and past the list into the field of pi-hole for domains and click the button add to blacklist then all 3700+ are added? before i added the txt to addlist and nothing was added.
looking forward to see how this works.
also i will not add whitelist for now and will see if the blacklist just works first


Merge from upstream

Update code for actix-4.
TODO: Need to fix CI.

Replace with https://github.com/fluidex/paperclip/pull/6 by rebasing to save upstream histories.


Warning in console

Hi, I installed your plugin but this Warnig comes out on the console, what is it? what problems are there?
thank you

[Multiverse-Core] "Multiverse-Core v4.0.0-b766" has registered a listener for org.bukkit.event.entity.EntityCreatePortalEvent on method "public void com.onarandombox.MultiverseCore.listeners.MVPortalListener.entityPortalCreate(org.bukkit.event.entity.EntityCreatePortalEvent)", but the event is Deprecated. "Server performance will be affected"; please notify the authors [Rigby, fernferret, lithium3141, main--, dumptruckman].

I'm getting different weird WARNS, not sure if related to multiverse tho
https://pastebin.com/FDQn8e00

Hmm removing chanks.dat in server/world/data folder seems to have removed my warns

can confirm, getting the same warning on a different pre-release version of MV

The file is not present CHANKS.DAT in server/world/data folde
Il
11.08.2019 03:46 Shano_dekono ha scritto:

Hmm removing chanks.dat in
server/world/data folder seems to have removed my warns
--
You
are receiving this because you authored the thread.
Reply to this
email directly, view it on GitHub [1], or mute the thread [2].

Con OpenStar hai Giga, SMS e i minuti che vuoi da 4,99€ al mese, per sempre. Cambi gratis quando e come vuoi e in più hai 6 mesi di INFINTY! http://tisca.li/myopen

Where do I find the pre-release version ??
Il 11.08.2019 07:06
Daniel Jarski ha scritto:

[1]
can confirm, getting the same
warning on a different pre-release version of MV
--
You are
receiving this because you authored the thread.
Reply to this email
directly, view it on GitHub [2], or mute the thread [3].

Con OpenStar hai Giga, SMS e i minuti che vuoi da 4,99€ al mese, per sempre. Cambi gratis quando e come vuoi e in più hai 6 mesi di INFINTY! http://tisca.li/myopen

I don't understand what he wants to tell me with his answer !!!!!
Il
11.08.2019 03:34 Shano_dekono ha scritto:

I'm getting different
weird WARNS, not sure if related to multiverse tho

https://pastebin.com/FDQn8e00 [1]

--
You are receiving this
because you authored the thread.
Reply to this email directly, view it
on GitHub [2], or mute the thread [3].

Con OpenStar hai Giga, SMS e i minuti che vuoi da 4,99€ al mese, per sempre. Cambi gratis quando e come vuoi e in più hai 6 mesi di INFINTY! http://tisca.li/myopen

Duplicate of #2000. At least that issue number is easy to remember...

@Peppe-73 disregard my previous comments it turned out to be lightcleaner (another plugin) hence why I deleted my posts

?????
then ??? solutions to my problem ???

No sorry I'm not a dev/author and I haven't come across this issue

Try going to the page Ebon referenced you to

[Multiverse-Core] "Multiverse-Core v4.0.0-b766" has registered a listener for org.bukkit.event.entity.EntityCreatePortalEvent on method "public void com.onarandombox.MultiverseCore.listeners.MVPortalListener.entityPortalCreate(org.bukkit.event.entity.EntityCreatePortalEvent)", but the event is Deprecated. "Server performance will be affected"; please notify the authors [Rigby, fernferret, lithium3141, main--, dumptruckman].

???

Duplicate of #2000. (You can read more about this "issue" there.


TypeError: Argument 1 of mozRTCPeerConnection.getStats does not implement interface MediaStreamTrack.

Need to investigate why that happens on Firefox 40.0.3 (have not checked other versions).

FF42 - the same error

Still seeing the error in FF43

I believe we call on getStats in an incompatible way on Firefox (adapter.js shim does not shim this correctly).

OK, we should fix that shim then. I believe @alvestrand is working on fixing getStats, but it won't be until Q2.

I just tested this and I think this was fixed in adapter.js. I merged a new adapter version in #259.

I'm seeing this error in Firefox 45.0.1.

Same here - happening again. :-(

+1

Sorry about this, will fix.

It's more about test.webrtc.org which has stopped working completely on Firefox

Fix is in for review, just waiting for a reviewer to get it done.
adapter.js (the shim we use) has changed the way it handles getStats hence apps needs to be updated.

test.webrtc.org has now been updated and should work fine on Firefox now. Will take a look at apprtc now.

It's broken again on Firefox 57.

I've been seeing this as well, FF57

Still an issue in FF58

Can any one suggest me how resolve this issue..

This is happening when visiting microsoft teams, and cause video streams to not work.


.travis.yml setup

It would be nice if you also provide  .travis.yml for Travis CI.
In the script, it should test out a few commands with setup.py such as
python setup.py install, etc.

I'm not sure if we want to give a suggestion about which Ci system to use.
If there is a particular good reason why Travis Ci is preferred, that's fine, but if not - I wouldn't do that.
Maybe we can suggest it in the README thoughh?

There are a lot of cookiecutter templates, which provide different setup of Python project, including config, CI, testing, et.
And let this project for setup.py only.


dockerComposeTest doesn't pick up test resources

I have a play application and resources in the test/resources folder which is the default test-resources folder for a play application. If I run a test which accesses test resources from dockerComposeTest the test resources are not on the classpath although they are if I run the same test witch test.

Hi @dpfeiffer, the class path for test dependencies is defined in the plugin as an overridable taskKey named testDependenciesClasspath.
testDependenciesClasspath =: // The path to all managed and unmanaged Test and Compile dependencies. This path needs to include the ScalaTest Jar for the tests to execute. This defaults to all managedClasspath and unmanagedClasspath in the Test and fullClasspath in the Compile Scope.
Here is the default implementation:
testDependenciesClasspath := {
  val fullClasspathCompile = (fullClasspath in Compile).value
  val classpathTestManaged = (managedClasspath in Test).value
  val classpathTestUnmanaged = (unmanagedClasspath in Test).value
  (fullClasspathCompile.files ++ classpathTestManaged.files ++   classpathTestUnmanaged.files).map(_.getAbsoluteFile).mkString(":")
}

Is there an additional sbt setting/path that you can append to the default list allow your test resources to be located from your Play application tests? Depending on what the solution is it's possible that the default set of paths I'm building needs to be updated to account for your scenario.

@dpfeiffer Maybe something like the following:
    testDependenciesClasspath := {
      val fullClasspathCompile = (fullClasspath in Compile).value
      val classpathTestManaged = (managedClasspath in Test).value
      val classpathTestUnmanaged = (unmanagedClasspath in Test).value
      val testResources = (resources in Test).value
      (fullClasspathCompile.files ++ classpathTestManaged.files ++ classpathTestUnmanaged.files ++ testResources).map(_.getAbsoluteFile).mkString(":")
    }

@kurtkopchik Thank you for your fast reply, it works as expected when I set the testDependenciesClasspath manually (like you suggested). I should have read the docs more carefully. I think that adding the testResources as a default would suite most scenarios as I assume it's a default behaviour (having access to test resources) for running test.

Thanks @dpfeiffer! I'm glad that worked for you.
I've published a release that now includes the test resources in the classpath by default when executing dockerComposeTest.
addSbtPlugin("com.tapad" % "sbt-docker-compose" % "1.0.16")


[WIP][Proof-of-Concept] Test upgrade with retry

Why is this PR needed?
Does it fix an issue? addresses a business case?
add a description and link to the issue if one exists.
Fixes #
Reminder: Add the "fixes bsc#XXXX" to the title of the commit so that it will
appear in the changelog.
What does this PR do?
please include a brief "management" technical overview (details are in the code)
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:

link to other PRs that should be merged together
link to packages that should be released together
upstream issues

Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

No longer needed.


Bail when override toolchain is not installed

This PR is in relation to #652
When overriding toolchains, there are 2 places to be concerned with when a toolchain is missing:

When fuelup is the command run
When a proxy command is run

For 2, we are already covering this scenario by installing missing components and plugins on first run.
As for 1, this PR will now bail!() unless the command is to install, uninstall, or create a new toolkit.
...
No tests yet because I want to get feedback to see if I'm on the right track.

LCOV of commit 69176e8 during CI #2038
Summary coverage rate:
  lines......: 82.3% (2364 of 2873 lines)
  functions..: 44.6% (367 of 823 functions)
  branches...: 59.6% (272 of 456 branches)

Files changed coverage rate: n/a

Once I found that toolchain installations were not failing because of code, everything started falling into place...
I've left the dialoguer comment in fmt.rs so that you can all see how that library is not able to be tested without a real tty (which is a shame given it works really nicely). So as is, we are still currently prompting the user via the original hand-rolled stdin nibbler.
We should now be a bit more robust with this PR when parsing <channel>-<date>-<target>, however I have left out most of the split on "-" code which I believe is/was causing most of the problems when specifying channel/toolchains, because it may be breaking behaviour which I'll avoid for now.
But for something to keep in mind, in the future we're probably better off converting split on "-" to regexes.

I forgot to mention, with the toolchain spec here:
/// Parses a distributable toolchain description from a string.
///
/// The supported formats are:
///     <channel>
///     <channel>-<target>
///     <channel>-<YYYY-MM-DD>
///     <channel>-<YYYY-MM-DD>-<target>
///     <channel>-<target>-<YYYY-MM-DD>
/// The parsing begins from the end of the string, so the target is the last part of the string,
/// then the date and finally the name
impl FromStr for DistToolchainDescription {

I think <channel>-<target>-<YYYY-MM-DD> should be removed since it doesn't follow the channel format of <channel>[-<date>].
--
Other quick change to the PR could be to move the URL concats into a separate function like fn github_releases_download_url(), but figured it was easy enough to leave it as is. Happy to change it if someone thinks it's better to go that way.

Keeping this PR in DRAFT but backgrounding for now...
Most of these changes have moved to other PRs and have been merged, but there's a few change and comments remaining that I want to pull into future changes.


Make basic-javascript.json file COM1000 compliant

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

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

Checklist:

[x] Tested changes locally.

Description

This makes it easy for editing and fixing bugs without showing unnecessary diffs.

Simply opened the file using COM1000 and saved it.

Thanks @abhisekp, but COM needs to fit FCC not the other way around.


Makefile doesn't build hello_world binary

When I run
make -f tensorflow/lite/micro/tools/make/Makefile hello_world_bin
I get:
No rule to make target 'tensorflow/lite/micro/tools/make/gen/osx_x86_64_default/obj/core/tensorflow/lite/micro/examples/hello_world/main.o', needed by 'tensorflow/lite/micro/tools/make/gen/osx_x86_64_default/bin/hello_world'
The error is the same when replacing hello_world_bin with hello_world. hello_world_test works as expected. The other examples magic_wand and person_detection work as expected. I'm on a Mac (OSX 10.15.7).

have u tried with bazel?


refactor: change Hello message from broadcasting to direct messaging

Description
I have updated the Hello message from broadcasting to direct messaging. This change will reduce network usage and improve efficiency.

I did not work on this pull request and noticed that there are several conflicts. Therefore, I am attempting to open a new pull request.

new PR : #665


a

this is the best PR i've ever seen. :ship:
oh, also reminder that this is a public project :)

sorry @igor47, I was trying to figure out since which commit travis began to fail the tests...
Let me revise the PR name and description.


install Zulip on a website?

Hello,
I'm wondering if I can embed a Zulip frame in a website and have visitors participating (through the website) to the chat...?
If yes, where can I find the corresponding setup and embedding instructions?
Thanks and regards,
Roger

Any idea on how to proceed?Roger Elkaim
-------- Original message --------From: Seth Addo @.> Date: 6/27/22  10:58  (GMT+01:00) To: zulip/zulip @.> Cc: relkaim @.>, Author @.> Subject: Re: [zulip/zulip] install Zulip on a website? (Issue #22281)
I think so
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Fixes for iOS

I want to make a couple of comments along with this:

This is incredible work.  I set out this morning to write the exact same thing in Golang with dynamo and AWS lambda + serverless framework.  Found out you had already done the work for me.
These are the fixes needed to make the library work for iOS.  It looks like Bitwarden would benefit heavily from some documentation, and needs to clean up the protocol so hacks like this aren't necessary.

Changes:

Allows cipher key Uris to be uppercase OR lowercase.
On iOS, if you don't specify a URI, you get null in the body which needs to be handled.
On iOS, the header is lower-case device-type.  This is spooky because I looked through bitwarden/mobile and the header is uppercase, so whatever source code is on the app store doesn't quite match up.  It's possible there's a bug with whatever HTTP library bitwarden/mobile uses, but this should be investigated.
On iOS the device type is the string "1" so we need to try and parse it.
Update README to note that iOS has been tested and is working.

Great work - I look forward to contributing more in the future!

Looks like that Travis failure isn't my fault - Encrypted environment variables have been removed for security reasons.

@subdavis yeah, I can run the test suite from my side to verify, it's at least in the source repo so I can see master is stable. You can run the test suite from your machine in case you provide AWS credentials  via env vars or the config file. I though about running something like a simulated environment, but running against AWS will always be the better integration test.
HTTP headers are generally case-insensitive, but it's implementation dependent unfortunately sometimes. I normalize bodies to lowercase in a bunch of places, but I don't touch the headers, also the AWS lambda handler signature seems to keep the sent case, so it should already happen coming from the iOS app as far as I can se.
thanks for contributing!


Set privileges even if no users currently have them. (Issue #6351)

Type of Change

[X] Bug fix (non-breaking change, fixes #6351 )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Fix bug that claimed user already had a privilege when nobody had that privilege
Approach
When the privilege is missing from the file, it adds the entire privilege instead of just adding the user to an existing list of users.
Commands to test
Set-DbaPrivilege -Type LPIM

yes, please! im running out of servers to try it on 😅

(it worked, i was just surprised there was not output so I'm creating some output)

Here's my powershell session...

awesome! works for me, thanks so much 🥳🥳🎉🎈 thank you for the contribution, merging and publishing now


Question: Open html page after execution

Hi,
One of my scripts goes and gets information from a Linux box and displays the output in an html file.
Is there a way to launch this file from WebCommander when the script has completed? Or, just embed the html into the results?
Thanks!

First of all, you must output the URL to the html in your PS1 script. So the user could open the page with it.
If you want the redirect to happen automatically, you need to add codes as below in webcmd.php
header("Location: url_to_the_html");
die();


Multilanguage, unicode and many pages

Added multilanguage, unicode and many pages to installer template
Added unicode
Use NSIS 3.0 for build (for unicode support)

Will check it next week. :) Feel free to ping after a while... :bowtie:
My open source sunday time is over for today. ;)

Hmm... as this is not available with brew yet - I think unfortunately I have to pass on this. :(
Or do you have any suggestions how to get it on mac. :)
This is what I get here:
> makensis --version                                                                      [20:46:16]
MakeNSIS v04-Oct-2015.cvs - Copyright 1995-2009 Contributors
See the file COPYING for license details.
Credits can be found in the Users Manual.

Usage:
  makensis [option | script.nsi | - [...]]
   options are:
    -CMDHELP item prints out help for 'item', or lists all commands
    -HDRINFO prints information about what options makensis was compiled with
    -LICENSE prints the makensis software license
    -VERSION prints the makensis version and exits
    -Px sets the compiler process priority, where x is 5=realtime,4=high,
        3=above normal,2=normal,1=below normal,0=idle
    -Vx verbosity where x is 4=all,3=no script,2=no info,1=no warnings,0=none
    -Ofile specifies a text file to log compiler output (default is stdout)
    -PAUSE pauses after execution
    -NOCONFIG disables inclusion of <path to makensis.exe>/nsisconf.nsh
    -NOCD disabled the current directory change to that of the .nsi file
    -Ddefine[=value] defines the symbol "define" for the script [to value]
    -Xscriptcmd executes scriptcmd in script (i.e. "-XOutFile poop.exe")
   parameters are processed by order (-Ddef ins.nsi != ins.nsi -Ddef)
   for script file name, you can use - to read from the standard input
   you can use a double-dash to end options processing: makensis -- -ins.nsi
FAIL: 1

And I think I'm up to date.
stefan @ stefan-mac: ~/Sites/blocky master (╯°□°)╯
> brew upgrade makensis                                                                   [20:47:29]
Error: makensis 2.46 already installed

I dont use mac. But NSIS 3.0 is beta. "brew" keep beta version?

Ja - I'd wait with this one then until NSIS 3.0 is out of beta as it should make it easy to create installers and for mac users as this currently is not the case. :(

"brew" keep beta version?

I don't understand.

Closing until NSIS 3.0 is out...
-> we plan to move to Squirrel anyways soon'ish.


Add sideEffects field to applicationinsights-shims package.json

To make this package optimizeable via webpack tree shaking, please add a correct sideEffects field to the package.json file for this lib.
thanks to @johncrim for pointing this out as part of an issue raised in https://github.com/microsoft/DynamicProto-JS/issues/22

Closing as 2.5.9 is now completely deployed to NPM and all CDN ednpoints


[10.x] Implement feature to resolve route from path

Based on #47800, this PR solves #47795.
This PR adds a new method to the Illuminate\Routing\RouteCollection that allows you to resolve a (unknown) URI / URL path to a Illuminate\Routing\Route object if it exists in your routes. In comparison to the given suggestion (described in the mentioned issue), it will not affect the current request.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

@taylorotwell I understand that you can't just merge any  PR. In itself it of course isn't a direct bugfix, however the current way of doing this is either by a manual implementation of the \Illuminate\Routing\RouteCollection::matchAgainstRoutes method (since it's protected and thus not accessible) or by using the suggestion that was given over 6 years ago of which there still isn't a valid alternative.
@driesvints mentioned he understood the use case, after I explained it in detail within the mentioned issue. When I personally encountered this issue it took me a frustratingly long time to debug since in itself it's not clear it is directly related to the match method (since it resolves to the current route and automatically binds that route with a new request underwater).
Since the top searches for "Laravel resolve route name by url" still returns both the mentioned Laracast answer as well as this SO answer, the chances other developers who are looking for this functionality will encounter this bug somewhere in their development cycle is not unthinkable.
Since it's a small addition within a core class, I do not think a package will be able to provide the desired syntax, nor do I think it will reach its intended audience.
I'll be happy to make changes to make it fit within the Laravel Framework.


Handle null value for causedBy

This is useful when you have conditional statements for the value.
For example:
->causedBy(Auth::check() ? Auth::user() : null)

I fixed the error from continuous-integration/styleci/pr — Issues have been identified with 1 file but seems like it's not re-scanning.

Travis error seems to be related to some other parts of the codebase.

Could you add a test that provided that causedBy now works when passing null?

@EmilMoe your change isn't precise enough - it accepts everything that's converted to false. Primary the 0 could lead to problems if I use custom IDs for my Model.
http://sandbox.onlinephpfunctions.com/code/54f28c289472fd661af7d39dc68e457d140c5b91
A more precise solution would be:
if (is_null($modelOrId)) {
  return;
}

And it work's but isn't nice - the test would be better in the same PR (here) and not another one. But this is just beauty.^^

@Gummibeer how about $modelOrId === null. That should work too afaik?

Thanks @Gummibeer I have modified my PR

Thanks!


Unused InsertResult does not generate a compiler warning.

I've found code that wrongly assumes that after an insert has been called for an Entity that calling storage.get(entity).unwrap() is not going to panic.  This may panic because the Entity could have been dead for the insert.  Is it possible for us to generate a compiler warning for unused InsertResult similar to how rustc generates a compiler warning for unused Result?

Yep, with #[must_use].


Ctrl+Alt+cursor-up/down  jagged vertical line is

Issue Type: Bug
Visual Studio Code Insiders 1.68 on Windows 11:
---------------------=====
Ctrl+Alt+cursor-up/down  jagged vertical line instead of straight vertical line
all of a sudden (after update ?).
Used to work a day ago or so on same data file.
Visual Studo Code:
Works, fine.
VS Code version: Code - Insiders 1.68.0-insider (15253f1528573fc8f84e956b21af4bad57f38c07, 2022-06-02T05:16:07.238Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.67GB (22.69GB free)

Process Argv
--crash-reporter-id 2d852f38-512e-4f58-8415-8900749cecdf

Screen Reader
no

VM
0%

Extensions (26)

Extension
Author (truncated)
Version

project-manager
ale
12.6.0

gitignore
cod
0.7.0

doxdocgen
csc
1.4.0

githistory
don
0.6.19

gitlens
eam
12.0.7

unicode-math-vscode
Gui
0.3.4

reg
ion
1.1.0

plantuml
jeb
2.17.2

better-cpp-syntax
jef
1.15.14

svg
joc
1.4.18

git-tree-compare
let
1.14.0

git-graph
mhu
1.30.0

remote-containers
ms-
0.237.0

remote-ssh
ms-
0.80.0

remote-ssh-edit
ms-
0.80.0

remote-wsl
ms-
0.66.3

cmake-tools
ms-
1.10.5

cpptools
ms-
1.10.3

cpptools-extension-pack
ms-
1.2.0

hexeditor
ms-
1.9.6

makefile-tools
ms-
0.5.0

r
REd
2.5.0

markdown-preview-enhanced
shd
0.6.3

cmake
twx
0.0.17

markdown-pdf
yza
1.4.4

vscode-open-in-github
ziy
1.3.6

(1 theme extensions excluded)

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256197
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vsdfh931cf:30280410
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30404738
wslgetstarted:30449409
vscscmwlcmt:30465136
cppdebug:30492333
pylanb8912:30496796
vsclangdf:30492506

/gifPlease
Do you use custom fonts (especially if not monospeced)? Maybe fonts with ligatures?

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette).
Happy coding!

2022.06.03: Editor offered update.
Update applied.
Update resolved issue.
Normal cursor operation restored.
Thank you.


Master fails to start on latest raspbian.

After installing '2016-05-10-raspbian-jessie' on 5 rpi-2s, running rpi-update, and installing 'v0.7.0/kube-systemd.deb', and running 'kube-config enable-master', only 1 container starts up:
pi@splinter:~ $ sudo docker ps
CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS              PORTS               NAMES
848ff163c378        kubernetesonarm/hyperkube   "/hyperkube kubelet -"   8 seconds ago       Up 7 seconds                            k8s-master

As a result, the setup of the workers fail. Is this a known issue, if not, where should I start debugging?

Duplicate of #96


add inquiry information to the account page

as a developer, I need to add and populate an inquiry tab for all user account pages so that users can view the progress of their inquiries without contacting MARE

Tasks

[ ] create an inquiry tab for all users in their account page
[ ] populate the tab with their inquiries, as well as information they should be seeing [Lisa, I need more input here], and the status
[ ] [Lisa, it's possible to note additional information we need, and allow them to enter it directly from their account page, would this be valuable functionality?]
[ ] create an inquiry details modal that shows detailed information of their progress and submitted information

Definition of Done

[ ] each user type has an inquiry tab on their account page
[ ] users can see all their inquiries as well as basic details in the initial list view
[ ] users can click into each inquiry to bring up detailed information about progress and the information they entered
[ ] [possible, but need Lisa's feedback first] users can update or add new information to an inquiry

@autoboxer Also on this issue too, I think you mean another Lisa. :)

Ignoring most of what is written above, when family is logged in, under My Information, need sub tab entitled Inquiries with a question mark icon.  Once selected, should reveal list of all inquiries associated with the family record, showing the following fields: Date Taken On (but titled Date Submitted), Inquiry Type, Children, and Inquiry Method.  Should order with most recent first, and does not need to be sortable.
Q: Is it possible for name under Children to link to their web profile?

Additional note: confirming current functionality is such that if you try to access child profile that you don't the permissions for, it just defaults to general child profile page.

reference #706 for convo on SW inquiries.

@bchiaruttini other than active, which child statuses should still display a link to allow the user's to view their profile in the gallery?

@n-devr
1.) active is only child status that should display a link
2.) no other fields necessary, although I believe "on behalf of" is answerable by two distinct fields...the text box manual entry or the registered family name

Couple more questions @bchiaruttini :

Do we want to show inquiries that were submitted on behalf of families?  E.g. Social Worker X submits an inquiry on behalf of Family Y. Family Y logs in to their account, should they see that Inquiry in the list?

If so, should we include a line with the SW who submitted the inquiry for them?

Do we want to indicate whether or not the inquiry has been accepted?

Easy answers - no to both.  thanks.


doc(gwk): upload visualization doc

Overall, I can clearly understand how to use the visualization methods provided by Fling through the README documentation. However, there are some details that could be improved and some aspects that are confusing:

For Activation Maximization:

In addition to citing the basic principles, there should also be references to the sources of method implementations, such as those in the overview: The concrete implementation is based on: https://github.com/Nguyen-Hoa/Activation-Maximization..
Additionally, the dimensions of the generated images should be included as a parameter in am_demo. This would facilitate personalized adaptation for networks trained with different image sizes.

For Hessian Dominant Eigenvalue Method:

I am unclear why an additional training model step (Step 3) is required here. My understanding is that the Hessian dominant eigenvalue should be computed with just one model, one dataset, and one iteration count. This seems to differ from the earlier methods, where the emphasis was not on the training process. Or is it suggesting applying the Hessian method during the training process?
Also, the note in Step 4 appears to be incorrect; it is written as "loss landscape."

For Loss Landscape Method:

Some details could be included to remind users: only linear layers and convolutional layers can be referenced…

For the demos provided for these three methods, it would be more convenient for users if there were simple explanations of the example images. From a user's perspective, it would be helpful to see the potential outcomes of the visualization methods before choosing, as images or data are just results.

Overall, I can clearly understand how to use the visualization methods provided by Fling through the README documentation. However, there are some details that could be improved and some aspects that are confusing:

For Activation Maximization:

In addition to citing the basic principles, there should also be references to the sources of method implementations, such as those in the overview: The concrete implementation is based on: https://github.com/Nguyen-Hoa/Activation-Maximization..
Additionally, the dimensions of the generated images should be included as a parameter in am_demo. This would facilitate personalized adaptation for networks trained with different image sizes.

For Hessian Dominant Eigenvalue Method:

I am unclear why an additional training model step (Step 3) is required here. My understanding is that the Hessian dominant eigenvalue should be computed with just one model, one dataset, and one iteration count. This seems to differ from the earlier methods, where the emphasis was not on the training process. Or is it suggesting applying the Hessian method during the training process?
Also, the note in Step 4 appears to be incorrect; it is written as "loss landscape."

For Loss Landscape Method:

Some details could be included to remind users: only linear layers and convolutional layers can be referenced…

For the demos provided for these three methods, it would be more convenient for users if there were simple explanations of the example images. From a user's perspective, it would be helpful to see the potential outcomes of the visualization methods before choosing, as images or data are just results.

In fact, here you can choose to train the model (step 3) or load a trained model. The description of the hessian eigenvalue visualization is "It can reflect to some extent the intensity of the upcoming change in the parameter gradient". It can be used to observe the state of the model at a certain point in time, so the user is actually free to choose when to observe the model. It is possible to visualize a trained model or to visualize a model during the training process.


Feat: use AWS's EKS Security Groups for pods

:question: What
Add a new template for rendering a SecurityGroupPolicy manifest with a configured AWS Security Group list.
:speech_balloon: Why
Not long ago AWS released a new feature for EKS allowing to attach an existing Security Group to pods. Such feature allows for a better security making possible to allow access in resources outside the cluster not to the full cluster subnets but to selected Security Groups (attached to pods).
This is the case scenario for the company I work for. We run metabase in one of our clusters and we're about to close our RDS's DBs to only some Security Groups, forbidding all remaining pods in the cluster subnets to access the DB (layer 3). We cannot do this until we enable our metabase deployment to access such DBs by attaching the metabase pods it's exclusive Security Group.
This PR adds such functionality.
:spiral_notepad: Notes
$ helm lint
==> Linting .

1 chart(s) linted, 0 chart(s) failed

helm template .
all current resources rendered without the new SecurityGroupPolicy manifest.
helm template --release-name metabase --set sgp.enabled=true --set sgp.sgIds[0]=sg-foo --set sgp.sgIds[1]=sg-bar .
...
---
# Source: metabase/templates/securitygrouppolicy.yaml
apiVersion: vpcresources.k8s.aws/v1beta1
kind: SecurityGroupPolicy
metadata:
  name: metabase
  namespace: sandbox
  labels:
    app: metabase
    chart: metabase-1.1.0
    release: metabase
    heritage: Helm
spec:
  podSelector:
    matchLabels:
      app: metabase
      release: metabase
  securityGroups:
    groupIds:
      - "sg-foo"
      - "sg-bar"
...

Hi, thanks for your contribution !
This feature is specific to AWS EKS, it would be much clear if you let sgp option come into a section called awsEKS or something to make a room for future features related to EKS.

Hi, thanks for your contribution !
This feature is specific to AWS EKS, it would be much clear if you let sgp option come into a section called awsEKS or something to make a room for future features related to EKS.

Changes up to date with your comments, would you like some other modification?

Nice ! LGTM


Multisig. No deposit and fee validation on Confirm

Description
account with amount not available for deposit and fee
Steps to Reproduce

Create multisig -> follow the whole flow -> create ms

Actual Behavior
allows signing, fails with unavailable fee error
Expected
https://www.figma.com/design/HgFuj8QZd0xqEbkG10DIfs/Flexible-multisig-|-Milestone-4?node-id=1108-55991&t=0VoLOig1LjxypsJw-1

The validation error should be shown on the confirmation screen.

depends on:
https://github.com/novasamatech/nova-spektr/issues/2615

Status verification: ✅


⚠ Bofrost.at has degraded performance

In 13f9922, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1050 ms

Resolved: Bofrost.at performance has improved in b1164ff.


[WFLY-15023] Move WildFly Preview to a native jakarta.* namespace variant of JBoss Metadata artifacts that use EE APIs

https://issues.redhat.com/browse/WFLY-15023
Also cleans up some unnecessary module.xml dependencies that imply EE APIs were used when they are not
Builds upon #14507

WildFly Preview tests:
https://ci.wildfly.org/viewLog.html?buildId=267345&tab=buildResultsDiv&buildTypeId=WF_WildFlyPreviewLinuxJdk11
https://ci.wildfly.org/viewLog.html?buildId=267343&tab=buildResultsDiv&buildTypeId=WF_Ee9BootableJarLinuxJdk8

@ehsavoie re this and https://github.com/jboss/metadata/compare/14.0.0.Beta1...14.0.0.Beta2
Alternative to JBMETA-422 is just to leave javax behind beginning with JBM 14. That's a valid option if all we expect in a javax-based JBM is bug fixing. I went for source transformation though because I didn't want to bet on that yet.


[CT-2114] In-repo documentation (readmes): architecture/sequence diagram of core execution flow

I'm envisioning a diagram that includes:

breakdown of major steps in core execution flow
inputs & outputs of each step

Is this a "flow diagram" or a "sequence diagram"? I didn't even realize that these are different things, but plenty of people have thought about this in more depth than I have.
I don't think we should aim to auto-generate this. It should be one level higher than specific methods / codepaths. Rather, this should instruct & inform on the patterns we're seeking to actualize in our execution APIs.
Potential inspiration (internal Notion docs / diagrams from 2021!):

What does dbt Core do?
dbt Parsing
The post-it note exercise from November :)

Out of scope for this: flow/sequence diagram that breaks down parsing. This is also important, but for the sake of core's execution flow, parsing can be understood as a single step with clear inputs & outputs.

@jtcohen6 As part of backlog grooming, we aren't going to point this issue as there is no acceptance criteria and are not sure what the work to be done is.
Outstanding questions

who will this diagram be for (particularly helpful to understand the necessary complexity of the diagram)
where should this live
who should own this
how will this be maintained over time

@stu-k Good questions, thanks for asking them!

who will this diagram be for (particularly helpful to understand the necessary complexity of the diagram)

This is not intended for the average end user of dbt. The target audience is:

Maintainers of dbt-core (us & future team members)
Our engineering colleagues at dbt Labs, who want to develop a mental model of dbt-core's execution flow
Community contributors to dbt-core (more technical than the average end user of dbt)

where should this live

A README in this repository

who should own this

@dbt-labs/core-execution !

how will this be maintained over time

I'd leave that for the Core-Execution team to determine. It might inform implementation decisions about which tool to use, and how to keep it up-to-date. As I said in the issue description, I don't think this is something we should be auto-generating from code; we could look to define it using code that lives in this repo, but I'd also be happy with a Lucid diagram.

To make the point more strongly — IMO these are medium/high-priority exit criteria for Phase 2 of API-ification:

Our team is capable of making a high-level diagram of the dbt-core task/command execution flow. Any member of the Core-Execution team can contribute to it and reason about it.
This diagram exists for public reference. Improvements to our actual codepaths & abstractions are essential, but if we don't do a good job of documenting them, I don't believe we'll have accomplished our goal as maintainers of an application (erstwhile "tool" and future "library") that lots of people want/need to comprehend and contribute to.

We're going to call this a spike with the assumption that the output is some sort of diagram that depicts the dbt-core task/command execution flow. Timebox at 2 days.


Question: Extension method that returns Expression<Func<T, bool>> ?

I have some queries that I would like to use this library with, but I would like to just have the library return back an Expression<Func<T, bool>> so I can just call it from within my same code, with minimal changes.  Is that something that I can already do?

That would be like:
var expression = DynamicExpressionParser.ParseLambda<T, bool>(config, true, "expression");

See also https://github.com/StefH/System.Linq.Dynamic.Core/blob/2d7b8ee16cc76ec780fb2891b2a8dd495358aee4/test/System.Linq.Dynamic.Core.Tests/DynamicExpressionParserTests.cs#L801

Or you can just use ParseLambda and cast the result.


Error: connect ECONNREFUSED <IP_ADDRESS>:443

I used the scrape-it module before and it didn't give me any errors.
I thought that it was in my repo the error, but I got it downloading this repo.
I npm install the dependencies and I tried to run the example index.js with node index.js
The error is the next
Gabriel at iMac-de-Gabriel in ~/scrape-it/example on master*
$ node index
{ Error: connect ECONNREFUSED <IP_ADDRESS>:443
    at Object.exports._errnoException (util.js:1026:11)
    at exports._exceptionWithHostPort (util.js:1049:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)
  code: 'ECONNREFUSED',
  errno: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 443 }

I have node 6.5.0 and npm 3.10.3

I have the exact same problem. node v6.6.0 and npm 3.10.3

Sorry guys. It happened due to a mistake in the previous version of ul (the tests were not covering that use-case also).
Fixed in the latest patch release of ul. npm update should be enough to fix the things. :rocket:


Install fails on ClusterRoleBinding

On OKD 4.11 I installed the hive operator from OperatorHub -- tried both the alpha channel and the mce-2.0 channel. Once installed, I created a base HiveConfig;
apiVersion: hive.openshift.io/v1
kind: HiveConfig
metadata:
  name: hive
spec:
  logLevel: debug
  targetNamespace: hive

This fails, and pods in my hive namespace are never created. The status on HiveConfig throws this error;
    message: |-
      unable to apply asset: config/controllers/hive_controllers_role_binding.yaml: error when applying patch:
      {"metadata":{"$setElementOrder/ownerReferences":[{"uid":"fd49def4-3900-41e6-9a6a-4305e4c2cb5b"}],"annotations":{"kubectl.kubernetes.io/last-applied-configuration":"{\"apiVersion\":\"rbac.authorization.k8s.io/v1\",\"kind\":\"ClusterRoleBinding\",\"metadata\":{\"annotations\":{},\"name\":\"hive-controllers\",\"ownerReferences\":[{\"apiVersion\":\"hive.openshift.io/v1\",\"blockOwnerDeletion\":true,\"kind\":\"HiveConfig\",\"name\":\"hive\",\"uid\":\"fd49def4-3900-41e6-9a6a-4305e4c2cb5b\"}]},\"roleRef\":{\"apiGroup\":\"rbac.authorization.k8s.io\",\"kind\":\"ClusterRole\",\"name\":\"hive-controllers\"},\"subjects\":[{\"kind\":\"ServiceAccount\",\"name\":\"hive-controllers\",\"namespace\":\"hive\"}]}\n"},"ownerReferences":[{"apiVersion":"hive.openshift.io/v1","blockOwnerDeletion":true,"kind":"HiveConfig","name":"hive","uid":"fd49def4-3900-41e6-9a6a-4305e4c2cb5b"},{"$patch":"delete","uid":"8bb8e669-5c32-42db-9569-6ad0ff5a3b95"}]}}
      to:
      Resource: "rbac.authorization.k8s.io/v1, Resource=clusterrolebindings", GroupVersionKind: "rbac.authorization.k8s.io/v1, Kind=ClusterRoleBinding"
      Name: "hive-controllers", Namespace: ""
      for: "object": error when patching "object": ClusterRoleBinding.rbac.authorization.k8s.io "hive-controllers" is invalid: [metadata.ownerReferences.apiVersion: Invalid value: "": version must not be empty, metadata.ownerReferences.kind: Invalid value: "": kind must not be empty, metadata.ownerReferences.name: Invalid value: "": name must not be empty]

Hi @japhar81. We don't work with OKD much (um, ever), but I'll go off and try to create an environment where I can reproduce this. Stay tuned!

Update: I was able to deploy manually on OKD; so this is going to be something to do with the OLM packaging.

Installed from alpha (currently quay.io/openshift-hive/hive:v1.2.3996-500a742) via OperatorHub and created the HiveConfig with contents as in your OP. Everything worked smoothly. I'm on OKD 4.11.0-0.okd-2023-01-14-152430.
Based on the error message, it looks like our apply function is only setting the uid of the owner. Here is the code that sets up that OwnerReference. As you can see, we set up all the fields that the error message is complaining about before we send the object off to be applied. The apply code creates the object if it does not exist. If it does exist, we create a patch to apply the changes.
In this case, based on the fact that the CRB has a last-applied-configuration, it appears as though that CRB existed previously -- probably from a previous iteration of the hive-operator's reconcile loop. I'm not sure why it's trying to $setElementOrder. Can you please dump me the full manifest of that CRB, as well as the hiveconfig in its current state?
oc get clusterrolebinding hive-controllers -o yaml
oc get hiveconfig hive -o yaml


Offer a view mechanism

We should support a view system directly in PDI instead of re-implementing it in each and every plugin:
The syntax could be something like:
data:
  gtemp: #< virtual global 3D array (t, x, y)
    type: array
    subtype: double
    size: [ inf, '$global_size[0]', '$global_size[1]' ]
  temp:
    type: array_view
    view_of: gtemp
    buffer_size: [ '$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]' ]
    buffer_selection_start: [ '$ghosts[0]', '$ghosts[1]' ]
    size: [ 1, '$local_size[0]', '$local_size[1]' ]
    start: [ $timestep, '$global_pos[0]', '$global_pos[1]' ]

In GitLab by @ksiero on Aug 5, 2021, 10:36
Maybe this is more clear?
data:
  gtemp:
    type: array
    subtype: double
    size: [ inf, '$global_size[0]', '$global_size[1]' ]
    selection:
      temp:
        size: [1, '$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
        start: [$timestep, '$global_pos[0]', '$global_pos[1]']
  temp:
    type: array
    subtype: double
    size: ['$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]']
    selection:
      gtemp:
        size: ['$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
        start: ['$ghosts[0]', '$ghosts[1]']

unassigned @ksiero

In GitLab by @agueroud on Aug 5, 2021, 19:05
For me the first one seems much more interesting:
having a map_in this way : give us the possibility to define multiple map_ins for the same data, this way i can use different map_ins for different plugins, or even in the same plugin (this is not possible when doing the map_in in the data subtree itself, unless you redefine the data every time you need another map_in :thinking_face: that's an interesting point in my opinion

In GitLab by @ksiero on Sep 9, 2021, 15:23
Last(?) iteration idea:
data:
  local_p: # data
    type: array
    subtype: double
    size: ['$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]']

views:
  global_r: # aka dataset
    type: array_view
    subtype: double
    size: [*, '$global_size[0]', '$global_size[1]' ]
    mappings:
      - data:
          name: $local_p
          size: ['$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
          start: ['$ghosts[0]', '$ghosts[1]']
        dims_order: [, 0, 1]
        start: [$timestep, '($local_size_with_ghosts[0] - 2) * $rank_pos[0]', '($local_size_with_ghosts[0] - 2) * $rank_pos[1]'] #before changing dims order

plugins:
  decl_hdf5:
    file: data.h5
    on_event: event
    write: global_r # the name of the data that describes the dataset

In GitLab by @ksiero on Aug 6, 2021, 13:46
Here is next iteration of the ideas:
data:
  global_r: # aka dataset
    type: struct
    members:
      position_member: &paricle_data
        type: array
        subtype: double
        size: [ inf, '$global_size[0]', '$global_size[1]' ]
      velocity_member: *paricle_data
      size: int
  local_p: # data
    type: array
    subtype: double
    size: ['$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]']
  local_v: # data
    type: array
    subtype: double
    size: ['$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]']
  data_size: int

map_in:
  - global_r.position_member:
      size: [1, '$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
      start: [$timestep, '($local_size_with_ghosts[0] - 2) * $rank_pos[0]', '($local_size_with_ghosts[0] - 2) * $rank_pos[1]']
    local_p:
      size: ['$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
      start: ['$ghosts[0]', '$ghosts[1]']
  - global_r.velocity_member:
      size: [1, '$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
      start: [$timestep, '($local_size_with_ghosts[0] - 2) * $rank_pos[0]', '($local_size_with_ghosts[0] - 2) * $rank_pos[1]']
    local_v:
      size: ['$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
      start: ['$ghosts[0]', '$ghosts[1]']
  - global_r.size: $size

plugins:
  decl_hdf5:
    file: data.h5
    write:
      local_v: # the name of the data to write
        dataset: global_r # the name of the data that describes the dataset
      local_p: # the name of the data to write
        dataset: global_r # the name of the data that describes the dataset

and:
data:
  global_r: # aka dataset
    type: struct
    members:
      position_member: &paricle_data
        type: array
        subtype: double
        size: [ inf, '$global_size[0]', '$global_size[1]' ]
      velocity_member: *paricle_data
      size: int
    +selection_for:
      local_p:
        position_member: &position_member_selection_for
          size: [1, '$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
          start: [$timestep, '($local_size_with_ghosts[0] - 2) * $rank_pos[0]', '($local_size_with_ghosts[0] - 2) * $rank_pos[1]']
      local_v:
        velocity_member: *position_member_selection_for
      data_size: $size
  local_p: # data
    type: pointer
    subtype:
      type: array
      subtype: double
      size: ['$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]']
      +selection_for:
        global_r.position_member: &local_p_global_p_selection_for
          size: ['$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
          start: ['$ghosts[0]', '$ghosts[1]']
  local_v: # data
    type: array
    subtype: double
    size: ['$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]']
    +selection_for:
      global_r.velocity_member: *local_p_global_p_selection_for
  data_size: int
plugins:
  decl_hdf5:
    file: data.h5
    write:
      local_v: # the name of the data to write
        dataset: global_r # the name of the data that describes the dataset
      local_p: # the name of the data to write
        dataset: global_r # the name of the data that describes the dataset

In GitLab by @ksiero on Aug 5, 2021, 14:18
After discussion with Amal we are divided by two ideas:
map_in mapping in the root, with named selections:
data:
  global: # aka dataset
    type: array
    subtype: double
    size: [ inf, '$global_size[0]', '$global_size[1]' ]
  local: # data
    type: array
    subtype: double
    size: ['$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]']
map_in:
  map_1:
    local:
      size: ['$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
      start: ['$ghosts[0]', '$ghosts[1]']
    global:
      size: [1, '$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
      start: [$timestep, '($local_size_with_ghosts[0] - 2) * $rank_pos[0]', '($local_size_with_ghosts[0] - 2) * $rank_pos[1]']
plugins:
  decl_hdf5:
    file: data.h5
    write:
      local: # the name of the data to write
        dataset: global # the name of the data that describes the dataset
        selection: map_1

And selection_for as a type subtree, which works more like casting operator:
data:
  global: # aka dataset
    type: array
    subtype: double
    size: [ inf, '$global_size[0]', '$global_size[1]' ]
    selection_for:
      local:
        size: [1, '$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
        start: [$timestep, '($local_size_with_ghosts[0] - 2) * $rank_pos[0]', '($local_size_with_ghosts[0] - 2) * $rank_pos[1]']
  local: # data
    type: array
    subtype: double
    size: ['$local_size_with_ghosts[0]', '$local_size_with_ghosts[1]']
    selection_for:
      global:
        size: ['$local_size_with_ghosts[0] - 2', '$local_size_with_ghosts[1] - 2']
        start: ['$ghosts[0]', '$ghosts[1]']
plugins:
  decl_hdf5:
    file: data.h5
    write:
      local: # the name of the data to write
        dataset: global # the name of the data that describes the dataset

In GitLab by @ksiero on Aug 6, 2021, 09:05
Is it possible use-case, that the local data can have different map_ins into the global data (where both remain the same types)?

I like the map_in option too as it seems more flexible for use-cases we don't think of yet.
For the multiple map_in. One may think of a single buffer used for two different mappings depending on the time step... Not really a good idea, but possible


Improve ClientRequestSizeMetrics test

The test was only checking that the metrics where updated but was not
testing if the updates were correct.
This patch also fix the ClearableHistogram.clear method (through an ugly
hack) that was not clearing the histogram count.

+1


Feature request: .env file parsing

Hello, i would like to propose a feature, that generates secrets.yaml, based on current environment (with prefix filter, i.e. "HELM_ENV_") or .env file.
Currently i'm using "workaround" - dumping needed env vars with "printenv > .env" then using following function in template:
https://github.com/ReDev1L/helm-env-file-parsing
Function does following:
KEY_ENV1=VAL_ENV1           KEY_ENV1: base64(VAL_ENV1)
KEY_ENV2=VAL_ENV2       =>  KEY_ENV2: base64(VAL_ENV2)
KEY_ENV3="${VAL_ENV3}"      KEY_ENV3: base64("${VAL_ENV3}")

Environment secret yaml template:
apiVersion: v1
kind: Secret
metadata:
  name: php-fpm-{{ .Values.environment }}-env
  labels:
    environment: {{ .Values.environment }}
type: Opaque
data:
{{ tuple . "configs/backend/php-fpm/.env" | include "env.parseFile" | indent 2}}

This would be awesome. Having separate types of configuration files for environment variables just for kubernetes is really broken. I don't think k8s team will support this anytime soon but it can be done much more appropriately with helm without many big changes to the k8s core.

I thought about introducing a new flag similar to the --set-file like --set-dot-env-file string       set values from respective .env file specified via the command line.
key=value
other_key=value

@bacongobbler would you be open for a PR like this?

I'm not sure what would be the difference between --values and this new --set-dot-env-file flag, other than the file format (YAML vs an undocumented key/value format).

An alternative is to use plain ol' bash.
><> echo --set $(echo $(cat .env) | tr ' ' ',')
--set foo=bar,car=star

Hope this helps.

Sorry, missed your comments. I was thinking of a native .env integration as the format is commonly used in the web community. But like the bash approach. Thanks

I’m closing this as something we’re not interested in supporting an alternative parser. I’ve demonstrated a few ways to work around this or use existing practices to achieve the same effect. Thanks.

I think this is really great feature.
@bacongobbler
Can I add this feature by PR?
There is already a feature "fromYaml" in helm. So I would like to add a feature like below.
{{- $env := ($.Files.Get (print ($.Values.envFile)) | fromEnv ) }}

No

i understood it. sorry about rough proposal

.env files are like standard for many frameworks. just check the popularity of https://www.npmjs.com/package/dotenv and it's daily downloads. it is used by default for many popular products - Strapi, Laravel, many kinds of React-based bundles and so on. and it is really painful to define for example in the CI variables the same configset twice in different formats. but... forget it :)

I don't understand the resistance against this, it would be a great benefit to use the existing Dotenv standard from many frameworks natively rather than trying to parse manually.

Not sure what's the problem with fromEnv similarly to fromYaml. I'd be happy to get rid of pre-processing (currently done with gomplate as it supports env and vault datasources) and render whole chart in one step. (if fromVault is also added :) )


Avoid needless verbosity for broken texture error messages

Pushed additional changes:

New IC/TS attribute: "max_errors_per_file" puts a limit on how many
error messages will be printed for each file. More than the first few
almost certainly will not provide any useful additional information,
but will clutter your logs and harm performance.
Suppress printing of empty error messages.
In testtex, make sure error printouts lock against each other to keep
from making unintelligible console output when many errors are issued
simultaneously from different threads.

Even though the person who inspired this has not replied with test results, nobody else has objected so I'm going to merge it.


Fix wrong steps in Working with the CHIP Tool page

This PR fixes #23546 wrong steps in Working with the CHIP Tool page:
Step 5: Determine Matter device's discriminator and setup PIN code
Step 4: Determine network pairing credentials

@lboue please apply restyle fixes

andy31415: What should be done exactly?

What should be done exactly regarding restyle fixes?

@lboue run scripts/helpers/restyle-diff.sh (see the file for documentation as needed) and then include the resulting changes in your PR?