programs.ssh configs are broken

I just tried to make a small change to my programs.ssh config and home-manager switch is throwing an error:
The option `programs.ssh.matchBlocks.myhost.data.hostname' defined in `/path/to/home.nix' does not exist.

I didn't see anything in the news items.  Any idea how to fix this?

This is related to 022228e0aa96d721bb9af20462c4b177e5dc4bb6 but I can't say what would cause the error you are seeing. I'm not able to reproduce it locally. Perhaps you could provide a bit more information?

Here is the ssh config section I'm using:
  programs.ssh = {
    enable = true;

    matchBlocks = {
      my-host = {
        hostname = "<IP_ADDRESS>";
        user = "root";
      };
    };
  };

And here's what I get when I try to switch to it:
$ home-manager -v switch
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
error: while evaluating the attribute 'activationPackage' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:52:3:
while evaluating 'showWarnings' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:16:18, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:37:12:
while evaluating 'foldr' at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/lists.nix:39:20, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:20:7:
while evaluating 'fold'' at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/lists.nix:42:15, called from /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/lists.nix:46:8:
while evaluating 'collectFailed' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:13:19, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:39:16:
while evaluating anonymous function at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:14:33, called from undefined position:
while evaluating the attribute 'assertion' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:427:9:
while evaluating 'any'' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:430:26, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:439:14:
while evaluating 'checkMatchBlock' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:438:31, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:430:63:
while evaluating anonymous function at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:438:43, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:438:38:
while evaluating 'checkLocal' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:436:26, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:438:47:
while evaluating 'any'' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:430:26, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:436:33:
while evaluating anonymous function at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:439:41, called from undefined position:
while evaluating the attribute 'data' at undefined position:
while evaluating anonymous function at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:75:45, called from undefined position:
while evaluating the attribute 'value' at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:338:9:
while evaluating the option `programs.ssh.matchBlocks.my-host.data':
while evaluating the attribute 'mergedValue' at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:370:5:
while evaluating anonymous function at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:370:32, called from /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:370:19:
while evaluating 'merge' at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/types.nix:368:22, called from /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:373:8:
while evaluating the attribute 'config' at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:87:25:
while evaluating 'yieldConfig' at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:74:29, called from /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:73:16:
while evaluating anonymous function at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:80:24, called from /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:80:11:
while evaluating anonymous function at /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:81:26, called from /nix/store/3mghl0pqxy21r0mslknklgywk1yhsach-nixpkgs-19.09pre173445.796a8764ab8/nixpkgs/lib/modules.nix:81:13:
The option `programs.ssh.matchBlocks.my-host.data.hostname' defined in `/path/to/home.nix' does not exist.

I'm running on macOS btw.

Ah, you are using Nixpkgs 19.09 but the master branch of Home Manager. If you use Nixpkgs 19.09 you need to use the release-19.09 branch of Home Manager.

I tried switching to 19.09 for everything but that doesn't seem to have worked.
$ nix-channel --list
darwin https://github.com/LnL7/nix-darwin/archive/master.tar.gz
home-manager https://github.com/rycee/home-manager/archive/release-19.09.tar.gz
nixpkgs https://nixos.org/channels/nixpkgs-19.09-darwin
$ home-manager -v switch
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
warning: Nix search path entry '/nix/var/nix/profiles/per-user/root/channels' does not exist, ignoring
error: while evaluating the attribute 'activationPackage' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:52:3:
while evaluating 'showWarnings' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:16:18, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:37:12:
while evaluating 'foldr' at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/lists.nix:52:20, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:20:7:
while evaluating 'fold'' at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/lists.nix:55:15, called from /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/lists.nix:59:8:
while evaluating 'collectFailed' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:13:19, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:39:16:
while evaluating anonymous function at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/default.nix:14:33, called from undefined position:
while evaluating the attribute 'assertion' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:427:9:
while evaluating 'any'' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:430:26, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:439:14:
while evaluating 'checkMatchBlock' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:438:31, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:430:63:
while evaluating anonymous function at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:438:43, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:438:38:
while evaluating 'checkLocal' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:436:26, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:438:47:
while evaluating 'any'' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:430:26, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:436:33:
while evaluating anonymous function at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:439:41, called from undefined position:
while evaluating the attribute 'data' at undefined position:
while evaluating anonymous function at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:75:45, called from undefined position:
while evaluating the attribute 'value' at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:336:9:
while evaluating the option `programs.ssh.matchBlocks.my-host.data':
while evaluating the attribute 'mergedValue' at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:368:5:
while evaluating anonymous function at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:368:32, called from /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:368:19:
while evaluating 'merge' at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/types.nix:368:22, called from /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:371:8:
while evaluating the attribute 'config' at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:87:25:
while evaluating 'yieldConfig' at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:74:29, called from /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:73:16:
while evaluating anonymous function at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:80:24, called from /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:80:11:
while evaluating anonymous function at /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:81:26, called from /nix/store/p76b0y3g5zn3sqhw9hhim997xby0zpmq-nixpkgs-19.09pre195073.f6c1d3b113c/nixpkgs/lib/modules.nix:81:13:
The option `programs.ssh.matchBlocks.my-host.data.hostname' defined in `/Users/doug/dotfiles-nix/home-manager/home.nix' does not exist.

Hmm, you still seem to be getting HM from the master branch:
while evaluating 'any'' at /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:430:26, called from /nix/store/pmsjm7jy5gbby1lq6f2mzd9ypydrfxb0-master.tar.gz/modules/programs/ssh.nix:436:33:

Do you have programs.home-manager.path set in your configuration?

Ahh yes.  It's in my home.nix.  I had looked for something about that in my darwin-configuration.nix.  Didn't think to look in home.nix.  So how do I undo this?  Commenting that out doesn't work because home-manager switch is the thing that's broken.  I tried running the install command nix-shell '<home-manager>' -A install but that didn't change the version I have installed either.

I'm getting the same thing. After commenting out my ssh block, I still get this:
error: value is a function while a set was expected, at /nix/store/p5qv2lr6w07xb7f80kg8czjp1v3yb199-home-manager-20.03/home-manager/modules/programs/emacs.nix:15:7

Downgrading to 19.09 and it's still broken:
error: value is a function while a set was expected, at /nix/store/ic5lasbvsv8v4igvf9rp3q5wvh1plj4a-home-manager-19.09/home-manager/modules/programs/emacs.nix:17:7

No idea what's wrong, and --show-trace doesn't give me a trace.

Commenting out my emacs configs finally got home-manager installed, at least my ~ is in a working state. Maybe some interface in the emacs options changed between 19.09 and 20.03?


Rule: SA1600

Rule summary

Key
Value

Title
SA1600ElementsMustBeDocumented

CheckId
SA1600

Category
Documentation Rules

Link
https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1600.md

What is the problem
This rule only seems relevant if you want to expose a documentation page / system generated by a tool.
But for readable code and no needs for code documentation, this rule provides no value but only noise.
If it was necessary for a project to have code documentation, it would be better to only enable it for the specific project need in the SRC/[project folder]/.editorconfig.
Suggestion
disable this rule in root .editorconfig with dotnet_diagnostic.SA1600.severity = none

https://github.com/atc-net/atc-coding-rules/blob/main/documentation/CodeAnalyzersRules/StyleCop/SA1600.md


Jidesha installing

I am hosting rocket.chat on my own server but not Jitsi, and rocket.chat is using Jitsi for the video chat.
So in my case, if I am using Jitsi's server for the video chat through rocket.chat, do i still need to install Jidesha in order for my users to use screen share ?  I do get the error message: failed to install desktop extension.
If so, is there a tutorial or instruction in terms of how to get Jidesha up running? there is nothing in Github.

https://github.com/jitsi/jidesha/tree/master/chrome


formatEther(x) != formatUnits(x,18)

In ethers.js formatEther(x) == formatUnits(x, 18), I noticed this is not the case with ethers.rs.  format_ether truncates the input number and returns U256, whileformat_units returns the input number in decimal representation as a string.
Is this intentional, or should it be like below?
pub fn format_ether<T: Into<ParseUnits>>(amount: T) -> Result<String, ConversionError> {
    format_units(amount, "ether")
}

+1
I can't work out how to print a decimal representation of ETH, like 0.1

I mean format_units(x, 18) works, but would expect it to be equivalent to format_ether(x)

Fixed with #2435
@halo3mic you can close the issue now.


[cppzmq] draft dependency update

cppzmq[draft] must need zeromq[draft] but it was not included.

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review".
That way, I can be aware that you've responded since you can't modify the tags.


operators hive-operator (1.2.3581-88b1c28)

Update Hive community operator channel(s) [['alpha']] to 1.2.3581-88b1c28
/hold

/hold cancel

/merge possible

/merge possible

/merge possible


Latest Linux ver gives startup error

Hello, everytime I try to start the program I get ./Oscilloscope: error while loading shared libraries: libGLEW.so.1.10: cannot open shared object file: No such file or directory. I've checked glew, I have 2.0.0-1

Are you a programmer? I think it would be possible the glut dependency entirely.


Support for block elements in headings

Obsidian itself also supports block elements in headings, like this:

Maybe this could be added here as well, for feature parity? :-)

It would be great to support that feature!
Thanks for the feedback.

After researching various options, it seems challenging to implement this feature due to the specifications of mdast and remark.
For example, consider the following markdown:
> [!note] title here
> body here

This is transformed into the following mdast, and this plugin generates the callout by manipulating this mdast.
{
  "type": "root",
  "children": [
    {
      "type": "blockquote",
      "children": [
        {
          "type": "paragraph",
          "children": [
            {
              "type": "text",
              "value": "[!note] # title here\nbody here",
              "position": {
                "start": {
                  "line": 1,
                  "column": 3,
                  "offset": 2
                },
                "end": {
                  "line": 2,
                  "column": 12,
                  "offset": 34
                }
              }
            }
          ],
          "position": {
            "start": {
              "line": 1,
              "column": 3,
              "offset": 2
            },
            "end": {
              "line": 2,
              "column": 12,
              "offset": 34
            }
          }
        }
      ],
      "position": {
        "start": {
          "line": 1,
          "column": 1,
          "offset": 0
        },
        "end": {
          "line": 2,
          "column": 12,
          "offset": 34
        }
      }
    }
  ],
  "position": {
    "start": {
      "line": 1,
      "column": 1,
      "offset": 0
    },
    "end": {
      "line": 2,
      "column": 12,
      "offset": 34
    }
  }
}

https://astexplorer.net/#/gist/10d8f7b32e0123fee005f49d8d75defa/6017a37f56a4098ff295b3c4730a217ef8132089
Notice that the title part of the callout exists as a paragraph in the mdast. According to the CommonMark specifications, only inline elements are allowed as children of a paragraph. Therefore, block elements cannot exist within a paragraph, making it impossible to use block elements as the title of a callout.
Furthermore, the heading included in the title part exists as text within the mdast. To recognize this as a heading element, the plugin would need to re-parse this string with remark, which is somewhat difficult to do accurately on the plugin side.
I am in favor of adding this feature, so if anyone is able to implement it, please feel free to mention me or send a PR.
Thank you for proposing this feature!


PyModbus based server

We already have a modbus server and want it to be sunspec compliant. I see that there are some device classes here that allows us to created devices by just giving their ids and that makes it so easy to implement these devices instead of specifying these registers manually.
The question is, how do I have these devices as server using PyModbus library. What would be good place to start writing a pymodbus plugin/transport layer so that we can use pysunspec and pymodbus to create sunspec compliant modbus servers.
Looking forward to answers.

Here is an example from pymodbus, where they are a sunspec client (rudimentary): https://pymodbus.readthedocs.io/en/stable/source/example/sunspec_client.html

Interesting: https://github.com/robogeek/pymodbus-sunspec


Item versions appear to be in progress even when they have been approved through workflow, preventing further versions being created.

Describe the bug
When a version has been created from an existing item and approved through workflow, the new item appears to be in progress, preventing further versions being created. DSpace 7.6 and DSpace 7.6.1
To Reproduce
Steps to reproduce the behavior:

Identify an item with no versions. The item should be in a collection with a defined workflow; an eperson or group should be specified in the Editor role.
Log in as an administrator and select the 'Create new version' button.
Click deposit.
Now switch to MyDSpace --> Workflow tasks. Claim the item and approve it.
In the new version of the item the 'Create new version' button will be greyed out with the message "A new version cannot be created because there is an inprogress submission in the version history".

Expected behavior
I should be able to create a further version of the item by selecting 'Create new version'. The 'Create new version' button should be black.
More
I was able to reproduce the behavior in the DSpace Demo site https://demo.dspace.org/items/b1e011de-f655-4c8b-ab1d-ed49c0889003
Sometimes refreshing the browser cache causes the new version button to appear black (as expected) briefly, before it changes back to grey. A new user logging in and accessing the item can sometimes cause the 'Create new version' button to appear in a black state.
We tested in Chrome, Firefox and Safari with no plugins or other extensions active.

Related work
Link to any related tickets or PRs here.

Thanks @peter975 for the report.  Pulling this over to the 7.6.x maintenance board in search of a volunteer to investigate what the problem may be.  Unclear to me if it'd be a backend or UI bug at this time, but definitely sounds like incorrect behavior.


[Fix #3947] Fix Rails/FilePath for dstr calling Rails.root without path

Any news on this? 😄

Waiting for more test cases. Otherwise I'll close this PR.

Guess I'll close this. @easybills-admin (or anyone else) feel free to pick it up.


JEI not respecting meta data for bark recipes

Adding custom bark recipes using blocks with different meta data works fine, however they don't show up properly in JEI.
Example script:
Bark.addRecipe("weedwood_bark_1", <thebetweenlands:log_weedwood:0>, <roots:bark_oak>);
Bark.addRecipe("weedwood_bark_2", <thebetweenlands:log_weedwood:12>, <roots:bark_oak>);

This should add versions of the weedwood logs (one that looks like a normal log, one that is covered in all bark).
However, JEI shows both recipes with meta 0 only:

Okay, I think I can safely say that this got fixed (although I forgot to mention this bug in my commit message):


Help with this error

Docker Toolbox install

When kitematic closed, machine stopped get this on restart also this error. Have recreated many times, any help would be appreciated.

Merging with #1029


Do I need to install putty to execute build.ps1?

The build.cake file asks for a putty sesion name. Why?
What happens if I put invalid data there?
BTW, I run the build script and it asks for my my password twice (one before deploying and another after it).
Thanks in advance :)

https://github.com/jeremylindsayni/RaspberryPi.Template/blob/master/RaspberryPiCore/coreiot/build.cake#L21
I am thinking that to develop on a Windows machine with this template, then deploy out to the raspberri pi, but I am just a beginner with this sort of thing.
Maybe the cake script could also be altered based on where the code is developed to eventually get deployed to the pi.
The script also asks for a pi IP address for the destination deploy machine.


Fix missing directory for manifests dump in integration test

Please provide a description of this PR:
This is a typo fix to ensure per cluster direcotories created before writing dump files.
Triggered when -istio.test.istio.dumpManifests flag is specified during the test. E.g.
2024-09-27T23:32:45.782114Z     info    tf      === BEGIN: Cleanup Istio [Suite=security] ===
2024-09-27T23:32:45.782489Z     error   tf      Unable to create directory for dumping cluster-0 install manifests: mkdir /tmp/security-e2dec165f98347419cbcd5/_suite_context/istio-deployment-3933594192/manifests: file exists
2024-09-27T23:32:45.782928Z     error   tf      Failed writing manifest 0/1 in cluster-0: open /tmp/security-e2dec165f98347419cbcd5/_suite_context/istio-deployment-3933594192/manifests/cluster-0/manifest-0.yaml: no such file or directory
2024-09-27T23:32:45.783061Z     error   tf      Failed writing manifest 1/1 in cluster-0: open /tmp/security-e2dec165f98347419cbcd5/_suite_context/istio-deployment-3933594192/manifests/cluster-0/manifest-1.yaml: no such file or directory
2024-09-27T23:32:45.783087Z     info    tf      clean up cluster cluster-0

@unicell: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
84e16664b6a55ddfc2e3604db9340dea9663e1c5
link
unknown
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest


[Feature] support image resizing on CfProperties

Is there an existing issue for this?

[x] I have searched the existing issues

Description
Here's how an image resizing request looks like in JS:
await fetch(url, {
    cf: {image: {width: w, height: h, quality: q, fit: 'scale-down'}},
  })

There are a few more of the within 'image' key. Here's the JS docs:
https://developers.cloudflare.com/workers//runtime-apis/request#requestinitcfproperties
and
https://developers.cloudflare.com/images/image-resizing/resize-with-workers
Adding support basically just means setting the according props on the JsValue in request_init.rs, right? And adding them in CfProperties.

I've started implementing this.

I've opened a draft PR! https://github.com/cloudflare/workers-rs/pull/233


Feature ImageData in SpeedyMediaSource

Continue from PR #56

Nice! We can just change files src/core/speedy-media-source.js and src/utils/types.js. Let's leave the other files, including the typescript definitions, for a different commit. We haven't changed the image sink yet.

In addition, in SpeedyMedia.type, let's handle the case in which the image source is an ImageData. Let's make it return the string 'data':
https://github.com/alemart/speedy-vision/blob/48934ac8317a5b7c3a665af00c69d22e626b888a/src/core/speedy-media.js#L113-L138

Hi @kalwalt,
Please sign your commits - see CONTRIBUTING.md.
I ask you to remove all files from this PR, except:

src/core/speedy-media-source.js
src/core/speedy-media.js
src/utils/types.js

Hi @kalwalt,
Please sign your commits - see CONTRIBUTING.md.
I ask you to remove all files from this PR, except:

src/core/speedy-media-source.js
src/core/speedy-media.js
src/utils/types.js

Maybe at this point it's better to recreate it. I'm using a GPG key to sign my commits but i will do as you mentioned in the contributing page. Sorry for this!

New updated PR #58

I think that it will be a better design to modify the existing image sink to introduce support for exporting an ImageData instead of creating a new node. I'll be doing that later.


[BUG] oiiotool with -i:ch flag crashes on multipart exr

Describe the bug
Using oiiotool to read an EXR with a <z_channel> while using the flag -i:ch=R,G,B,A results in a crash. If changing the flag to -i <file> --ch R,G,B,A, it does not crash. If the file does not have the <z_channel>, it does not crash.
The original EXR was created from a 3delight render, with an extra Image Layer (AOV) "Z (depth)".
The crash is happening with OIIO 2.3.10, 2.1.9, 2.4.0dev (from Arnold). The command silently fails (no crash) with OIIO from Arnold 2.2.1, 2.1.4dev. The command works as expected with OIIO from Arnold 2.1.0dev. All my tests were done on Windows10.
To Reproduce
Steps to reproduce the behavior:

Call oiiotool.exe -i:ch=R,G,B,A "in.exr" -o "out.exr"
Crash:

 1# OpenImageIO_v2_3::Sysutil::stacktrace in OpenImageIO_Util
 2# OpenImageIO_v2_3::Sysutil::stacktrace in OpenImageIO_Util
 3# seh_filter_exe in ucrtbase
 4# 0x00007FF66322FC4A in oiiotool
 5# _C_specific_handler in VCRUNTIME140
 6# _chkstk in ntdll
 7# RtlRaiseException in ntdll
 8# KiUserExceptionDispatcher in ntdll
 9# OpenImageIO_v2_3::ImageBuf::reset in OpenImageIO
10# OpenImageIO_v2_3::ImageBufAlgo::channels in OpenImageIO
11# 0x00007FF6631B4748 in oiiotool
12# 0x00007FF66320CCA7 in oiiotool
13# 0x00007FF6632032B9 in oiiotool
14# OpenImageIO_v2_3::ArgParse::parse_args in OpenImageIO_Util
15# OpenImageIO_v2_3::ArgParse::parse_args in OpenImageIO_Util
16# 0x00007FF6631FEF5D in oiiotool
17# 0x00007FF663216331 in oiiotool
18# 0x00007FF66322ADA0 in oiiotool
19# BaseThreadInitThunk in KERNEL32
20# RtlUserThreadStart in ntdll
 0# OpenImageIO_v2_3::Sysutil::hardware_concurrency in OpenImageIO_Util
 1# OpenImageIO_v2_3::Sysutil::stacktrace in OpenImageIO_Util
 2# OpenImageIO_v2_3::Sysutil::stacktrace in OpenImageIO_Util
 3# raise in ucrtbase
 4# OpenImageIO_v2_3::Sysutil::stacktrace in OpenImageIO_Util
 5# seh_filter_exe in ucrtbase
 6# 0x00007FF66322FC4A in oiiotool
 7# _C_specific_handler in VCRUNTIME140
 8# _chkstk in ntdll
 9# RtlRaiseException in ntdll
10# KiUserExceptionDispatcher in ntdll
11# OpenImageIO_v2_3::ImageBuf::reset in OpenImageIO
12# OpenImageIO_v2_3::ImageBufAlgo::channels in OpenImageIO
13# 0x00007FF6631B4748 in oiiotool
14# 0x00007FF66320CCA7 in oiiotool
15# 0x00007FF6632032B9 in oiiotool
16# OpenImageIO_v2_3::ArgParse::parse_args in OpenImageIO_Util
17# OpenImageIO_v2_3::ArgParse::parse_args in OpenImageIO_Util
18# 0x00007FF6631FEF5D in oiiotool
19# 0x00007FF663216331 in oiiotool
20# 0x00007FF66322ADA0 in oiiotool
21# BaseThreadInitThunk in KERNEL32
22# RtlUserThreadStart in ntdll

Expected behavior
A generated out.exr with RGBA layers only.
Evidence
Attached in.zip.
Platform information:

Input formats supported: bmp, cineon, dds, dpx, ffmpeg, fits, gif, hdr, iff, jpeg, null, openexr, png, pnm, psd, raw, rla, sgi, socket, softimage, targa, tiff, webp, zfile
Output formats supported: bmp, dpx, fits, gif, hdr, iff, jpeg, null, openexr, png, pnm, rla, sgi, socket, targa, term, tiff, webp, zfile
OpenColorIO 2.1.1, color config: built-in
Known color spaces: "linear", "default", "rgb", "RGB", "sRGB", "Rec709"
Filters available: box, triangle, gaussian, sharp-gaussian, catmull-rom, blackman-harris, sinc, lanczos3, radial-lanczos3, nuke-lanczos6, mitchell, bspline, disk, cubic, keys, simon, rifman
Dependent libraries: FFMpeg 4.4.1 (Lavf58.76.100), gif_lib 5.2.1, jpeg-turbo 2.1.3/jp62, null 1.0, OpenEXR 2.5.0, libpng 1.6.37, libraw 0.19.0-Beta1, LIBTIFF Version 4.3.0, Webp 1.2.2
OIIO 2.3.10 built for C++14/199711 sse2
Running on 8 cores 31.9GB sse2,sse3,ssse3,sse41,sse42,avx,avx2,fma,f16c,popcnt,rdrand
Windows 10 Pro 64

I can reproduce with this example, thanks. Looking into it, stay tuned...

Proposed fix in #3513
If you need a workaround, it should work to just use --ch separately from -i:
oiiotool in.exr --ch  R,G,B,A -o out.exr


Linq exception ("Sequence contains no matching element") when using locales sample from docs

When I add this to my bridge.json:
"locales": "en_GB"

The build fails with:
Bridge.targets(12,5): error : Error: Sequence contains no matching element    at System.Linq.Enumerable.First[TSource](IEnumerable`1 source, Func`2 predicate)
Bridge.targets(12,5): error :    at Bridge.Translator.Translator.ExtractCore(String outputPath, Boolean nodebug)
Bridge.targets(12,5): error :    at Bridge.Build.GenerateScript.Execute()

Changing it to en-GB fixes the issue but the docs have underscores in their examples. I presume this the docs are wrong though I think the compiler shouldn't crash with a vague error for bad config.

Hi DanTup! Somehow this changes were reverted in the Docs. In fact at a given time we had this mishap as underscore but it were fixed to hyphen. Don't really know the reason the underscore is back there but we'll fix this at once (again)!.. :)

Docs fixed, thank you!

Is there value in improving the error for when invalid cultures are added (if you haven't already)? I guessed what the issue was because I'd just added cultures, but if you grab a large project you're not familiar with, this error won't help identify what's wrong.


How to draw curve

how to draw curve as ground without svg?

Try using the chamfer feature. Alternatively, you can try using Bodies.fromVertices where you can pass any vertices you'd like.

thanks for your help!


[Spike] UI Plugin: Decide implementation for Clarity webcomponents/React

Considering UI tech stack for open source UI plugin React vs Angular:
Requires: Ability to use Clarity UI framework
Current React versions do not support web components (Clarity Core). Explore wrapping Clarity components for consumption in React.

Current React versions do not support web components (Clarity Core). Explore wrapping Clarity components for consumption in React.

Which React versions are being considered? For me, on 17.0.2, I was able to import a Clarity core web component into a React component. Haven't look too much into state/lifecycle, but I assume it will behave as a regular component.

Hi Garry, we would likely use the latest stable version of React which would be in v17 major. If we can confirm that component state works as it should (bindings and events like onchange), we may be good to go.


[App Config] Fix test failures

Fixting test failures: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1896914&view=results
These failures introduced in https://github.com/Azure/azure-sdk-for-net/pull/31588 PR.

I wonder why the CI pipeline didn't run this https://github.com/Azure/azure-sdk-for-net/pull/31588 PR?

I wonder why the CI pipeline didn't run this https://github.com/Azure/azure-sdk-for-net/pull/31588 PR?
CC: @weshaggard, @hallipr

API change check
API changes are not detected in this pull request.

Ahh I see...it did trigger the ci pipeline https://dev.azure.com/azure-sdk/public/_build/results?buildId=1893557&view=results for this PR but there was an issue in the ci.yaml that's why the tests cases didn't run for this PR.
The issue in ci.yaml is now fixed here https://github.com/Azure/azure-sdk-for-net/commit/2b44628fd882aeaf77f6c59705fcb2c0b84f925f and test cases are runing for this PR.

@ShivangiReja exactly.


Add theme groups for Dashboard

Add plugin file for dashboard.nvim
https://github.com/nvimdev/dashboard-nvim
Created new lua/cobalt2/plugins/dashboard.lua and entry in the init.lua.

@jmcollis, thanks for this.


Security updates: Simpleform does no longer works?

@jow- Maybe you can have a look. With the latest security updates in place I cannot use SimpleForm any longer, e.g. blacklist_tab.lua in adblock package:

Thanks!

This seems to be caused by some SimpleForm template markup issues. In my local test I see that the beginning of the form is rendered twice, like this:

<form method="post" name="cbi" action="/cgi-bin/luci/admin/services/adblock/advanced" enctype="multipart/form-data" onreset="return cbi_validate_reset(this)" onsubmit="return cbi_validate_form(this, 'Some fields are invalid, cannot save values!')">

		<input type="hidden" name="token" value="63c1ed2e026a54ffbaa2365498422146" />
		<input type="hidden" name="cbi.submit" value="1" />
		<input type="submit" value="Save" class="hidden" />

<form method="post" enctype="multipart/form-data" action="/cgi-bin/luci/admin/services/adblock/advanced">

		<input type="hidden" name="token" value="63c1ed2e026a54ffbaa2365498422146" />
		<input type="hidden" name="cbi.submit" value="1" />

This causes the token value to be sent twice, causing the verification to fail - will look into it asap.

I took the liberty to commit a fix for this directly. The redundant markup rendering was caused by instantiating the SimpleForm models through the cbi() and not the form() target.

I don't know whether it is the intended way to use it, but this is working:
_G.redirect = luci.dispatcher.build_url("...")


Missing using statement for annotation

Fixes #1297

@define-private-public Thanks for this. But please see PR #1422 - which already covers this (and several other places where this problem occurs).


fixes bug so that configmap volumemounts are merged in deployment

Issue Ref: [#1035]
Description:
Manually merge VolumeMounts in runtime container if defined in configmap.
Mergo doesn't add the VolumeMounts https://github.com/kubeless/kubeless/blob/master/pkg/utils/k8sutil.go#L376
possibly due to this error
cannot use deployment.Spec.Template.Spec.Containers[0].VolumeMounts (type []"k8s.io/api/core/v1".VolumeMount) as type "k8s.io/api/core/v1".VolumeMount in append

TODOs:

[x] Ready to review
[x] Automated Tests
[ ] Docs

The image built in the CI is kubeless/function-controller:build-170d445f-c8b3-48a2-a8ed-93bfe6e9cc39
https://circleci.com/gh/kubeless/kubeless/2693#artifacts/containers/0


atom-text-editor.Object.defineProperty.get is deprecated.

The contents of atom-text-editor elements are no longer encapsulated
within a shadow DOM boundary. Please, stop using shadowRoot and access
the editor contents directly instead.
atom-text-editor.Object.defineProperty.get (/Users/christinewhyte/Downloads/Atom.app/Contents/Resources/app.asar/src/text-editor-element.js:68:18)
MarkdownScrlSync.getVisTopHgtBot (/Users/christinewhyte/.atom/packages/markdown-scroll-sync/lib/utils.coffee:20:33)
MarkdownScrlSync.setMap (/Users/christinewhyte/.atom/packages/markdown-scroll-sync/lib/map.coffee:25:14)
MarkdownScrlSync.startTracking (/Users/christinewhyte/.atom/packages/markdown-scroll-sync/lib/main.coffee:75:12)
<unknown> (/Users/christinewhyte/.atom/packages/markdown-scroll-sync/lib/main.coffee:58:23)
Function.module.exports.Emitter.simpleDispatch (/Users/christinewhyte/Downloads/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)

Is there going to be a PR and fix the issue on this main repository?

@drorata see #65.

Does it mean it will be updated directly in Atom?

Any updates?

It's now March 4, and I'm still getting an alert for this on Atom's deprecation cop. Any new news?  (Atom 1.14.4 on Linux Mint 64-bit).

On Sat, Mar 4, 2017 at 11:06 AM, Michael Fierro<EMAIL_ADDRESS>wrote:

Any new news?

Unfortunately nothing is going to happen unless/until someone takes over
the project.  I don't have any time for atom for the foreseeable future.

I just submitted a pull request with the fix for this issue. If you can approve that request, that'll fix the issue. If you want, you can add me as an owner/approver for this project (biffster@gmail.com).

Thanks.  I'm glad you are willing to take over.

If you can approve that request, that'll fix the issue.

That isn't the hard part.  Prepping and releasing to npm is.  I don't even
have that dev env any more.
To transfer ownership you first need to delete any repos you have with the
same name.  Let me know when this is done.

Just a bump that this is still awaiting an incorporated release.

@biffster Sorry, Just a reminder that this commit needs to make it into a release to close the above error. That probably needs an owner.

Has this been done?  I too have been getting this popup it looks like @biffster was willing to take this over some time ago now.  Has that happened and how can one apply this fix?

I need to do what now?

I need to do what now?

I can give you ownership if you first make sure you have no repo with the same name.

Still no one take over it and push the update? I also can take over as well.

I also can take over as well.

That would be great.  The only thing you need to do is delete any repo with
the name markdown-scroll-sync.  Let me know when this is done and I'll
transfer the repo to you.  Then you can switch ownership of the package at
atom.io with the instructions here
http://flight-manual.atom.io/behind-atom/sections/maintaining-your-packages/#transferring-ownership
.

Confirmed.
I don't have a repo with the name markdown-scroll-sync currently.
Thanks @mark-hahn

I pulled the latest code of this package and run atom in dev mode locally. Seems markdown-scroll-sync still does not work. It shows the following warnings in the development console
Handling of 'mousewheel' input event was delayed for 2097 ms due to main thread being busy. Consider marking event handler as 'passive' to make the page more responive.
- worksapce-element.js:210
text-editor-component.coffee:1 Handling of 'mousewheel' input event was delayed for 2097 ms due to main thread being busy. Consider marking event handler as 'passive' to make the page more responive.
-text-editor-component.coffee:1

I am not familiar with the atom API currently,  need some time to investigate the issue and fix it.  It will be better if @mark-hahn or someone else can give me some hints about the issue and I can fix&publish a workable version quickly.
Thanks.

@vincentcn It works just fine for me with the changes made in e105bd099af89f1956b41712315d93235d0dcbaa. It would be great if you could publish a new release so we can use it.

@vincentcn any news?

Check out this it has pretty much everything you need for markdown: https://github.com/shd101wyy/markdown-preview-enhanced

Very nice, thk u


Mapping child null object as (empty) object on source

When mapping source parent object with a child object having a null reference to a destination object who's child object is set to a non null value, the result is a destination object who's child object properties are cleared. My assumption is the expected behavior should result in this destinations object child to be null as well. Attached a screen shot of result. As you can see personDTO.item is not set to null. Is expected behavior?
Using:

org.modelmapper
modelmapper
2.3.2

Same experience here with modelmapper 2.3.5.  The destination object gets all fields set to null.  It is apparently not calling a constructor, just nulling everything.  This results in an invalid object in some scenarios.  It would seem more appropriate to either call a noarg constructor to replace the destination object, or null the reference, but not simply null all the fields.  Is there a way to control this behavior, globally?

Same happened to me. I posted question to stackoverflow with an example.
I found out that same problem occurs when child property is of the same type and deepCopyEnabled is set to true.

when deepCopyEnabled  set false  ,the children has nonull value  ？


select tag doesnt work correctly when resizing

If you add a select tag with more than one option inside the resizable div and you select the second option (or make it selected by default), the first option gets selected while resizing and when you stop resizing the second option gets selected back again.

I'm guessing you're using the enableGhostResize input? It works by cloning the html element hence the behaviour you're seeing will be messing up angulars form controls. It works for a majority of use cases but in instances like this you'll need to not enable it and implement the ghost resizing logic yourself using the resizeStart / resizing and resizeEnd events.

Ah ok, I see. Thanks for the reply!


Ref 490, adding name_with_middle option

Adding option to return full name which contains "#{first_name} #{middle_name} #{last_name}".
Added tests for same.

:+1:

:+1:

@stympy Is there any issue with this change?

Thanks for the bump :)


Doesn't work in next.js project: Uncaught Error: Objects are not valid as a React child

I have the following setup:
// pages/system/queue/[[...slug]].tsx

import { QueueDashApp } from "@queuedash/ui";

function QueueDashPages() {
  return (
    <QueueDashApp
      apiUrl="/api/system/queue"
      basename="/system/queue"
    />
  );
};

export default QueueDashPages;

// pages/api/system/queue/[trpc].ts

import { Queue } from "bullmq";
import * as trpcNext from "@trpc/server/adapters/next";
import { appRouter } from "@queuedash/api";
import RedisService from "server/services/redis";

const connection = RedisService.createClient({
  maxRetriesPerRequest: null,
});

const queue = new Queue("main", {
  connection,
});

export default trpcNext.createNextApiHandler({
  router: appRouter,
  batching: {
    enabled: true,
  },
  createContext: () => ({
    queues: [
      {
        queue,
        displayName: "Main",
        type: "bullmq" as const,
      },
    ],
  }),
});

When I try to load the page it throws an error:
helpers.js:121 Uncaught Error: Objects are not valid as a React child (found: object with keys {$$typeof, type, key, ref, props}). If you meant to render a collection of children, use an array instead.

client.js:2 The above error occurred in the <US> component:
    at US (webpack-internal:///./node_modules/@queuedash/ui/dist/main.mjs:20598:13)
    at QueueDashPages
    at WithSuperJSON (webpack-internal:///./node_modules/babel-plugin-superjson-next/dist/tools.js:115:55)
...

Next.js: 13.5.6
Queuedash: 3.2.0

Try 3.3.0 and lmk 🤞


⚠ Heritage of Faith Christian Church - Gold Coast has degraded performance

In db90682, Heritage of Faith Christian Church - Gold Coast (https://heritageoffaith.com.au) experienced degraded performance:

HTTP code: 200
Response time: 7067 ms

Resolved: Heritage of Faith Christian Church - Gold Coast performance has improved in 48e4455.


Create User

Will require some integration with Auth0 as some information is stored in Auth0 and some is stored in UE database.
Ability for a user account to be able to be created in the system
Should also provide support to edit account

@tylerbhughes please add additional details if any

We will need to integrate with Auth0 and Gravatar. Auth0 will handle logins for us and will store the user's first name, last name, and e-mail for us. Auth0 will also give us what we call an Auth0 Id that we can use to associate users in our user table to the user in their system. Currently Auth0 also uses gravatar for their profile pictures so we either need to redirect someone to Gravatar when they want to update their profile pic or we need to integrate with Gravatar and let them upload the image through out API. I like the 2nd approach best but I'm not sure what functionality Gravatar gives to developers if any


release: bump version to 0.8.4

bump etcd operator version to 0.8.4

cc/ @hongchaodeng @hasbro17

LGTM

added most recent change into the changelog

LGTM


Use League Filesystem

I am playing with this idea for a while now. The main reason I didn't mention so far is that this package is a transition between a finder and a real filesystem package. I am not sure Flysystem completely fits into this-

Use it for what?
Flysystem is ok for target independent I/O, but I think you will loose a lot of functionality compared to the current package.

If you look at the File/Directory/Handler structure: they are 80-90% the
same. Using separate local adapters could solve the problem of areas. The
only thing we should rewrite a bit is the finder, which should call the
underlying filesystems has method.
I don't think any functionality would be lost, my only concern is that
things would definitely be more complex than now.
However if we make it a full integration, filesystem could be used for
remote file access as well. It could be useful for example when files from
upload should be saved to a cloud provider.

The thing I'm most worried about is the performance impact of all this abstraction, given the fact that the finder is used to load most of the framework related files. People that have file system abstraction as a functional requirement will use flysystem anyway.

Hm, that's a good point. I am going to do some benchmarks, but I'm afraid I
won't get positive results.
However Flysystem could still be integrated. IIRC most part of file
handling has not been completely migrated to v2 (reading, writting files,
etc). I don't think performance hit is as important as in case of the
finder.
I am not trying to push it, just an idea. The thing made me to open an
issue was the overlap between the mentioned components and the area problem.


WP Engine Auto Wordpress Updates failing

the bubsnext WP Engine install was pretty dated (wp 5.5 instead of 5.8) so I tried to update it from WP Engine dashboard. It fails pretty quickly after and emails this back to us:

The specific failed test consists of checking your environment(s) before and after the update to ensure we receive a 200 (OK) response, which usually confirms that no fatal errors have occurred.
As a result of the tests failing, we have reverted the following environment(s) to the previous version:

I then ran a backup of the install in WP Engine and proceeded to update the instance manually from the WP dashboard, where it succeeded immediately, with no errors on / or /graphql. I think we should resolve the WP engine auto updates for ease of site maintenance and to make sure we're not unintentionally blocking WP engine from applying security updates to sites.
I'm not sure which specific path WP Engine's updater verifies for the update test, but if it's /, maybe we could switch the redirect from being a HTTP status code to a html file with 200 response and meta redirect header - people aren't going to just  be stumbling upon the WP engine domain so this slower redirect doesn't seem to be a concern.

Good flag. Can you reach out to their support to see if there is a way around it? I'm hesitant not to 301 , I don't want google accidentally indexing anything.

I ended up chatting with somebody technical at WP Engine and they first told me that the check for a 200 response from / is how the auto updater determines whether to start the backup and whether to consider it a success (along with all the auto-rollback functionality).
Since the 301 redirect is important, I asked if we could attempt to send a 200 if a specific useragent is detected and they responded with this:

I do believe that this is how our platform handles the smoke test for the wordpress updates.```

I believe we can check for `WPEBot` useragent or `wpengine_no_cache` cookie before sending the 301 redirect to Vercel, and then return a 200, which would allow our headless sites to receive wordpress updates from WP Engine directly.

Given that we might even be missing on security updates without this, we should try to ensure this functionality works before our 1.0 release.

Great, I like that solve.


Integrate overlay with vaadin-date-picker

Closes #8

Reviewed 8 of 8 files at r1.
Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

bower.json, line 25 [r1] (raw file):
I think iron-icon and iron-icons are not (yet) used anywhere?

vaadin-date-picker-overlay.html, line 43 [r1] (raw file):
Add quotes around the bound value here.

vaadin-date-picker.html, line 21 [r1] (raw file):
The opened property is missing. Should it be removed from here?

vaadin-date-picker.html, line 22 [r1] (raw file):
The label property should also be declared in the properties object.

Comments from the review on Reviewable.io

Review status: 4 of 8 files reviewed at latest revision, 4 unresolved discussions.

bower.json, line 25 [r1] (raw file):
Done.

vaadin-date-picker-overlay.html, line 43 [r1] (raw file):
Done.

vaadin-date-picker.html, line 21 [r1] (raw file):
Done.

vaadin-date-picker.html, line 22 [r1] (raw file):
Done.

Comments from the review on Reviewable.io

 :beer:

Reviewed 4 of 4 files at r2.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

Comments from the review on Reviewable.io


k256 v0.13.3 causes an error on secp256k1_recover_pubkey_works test

After executing cargo update on packages/crypto to update k256 to v0.13.3, test secp256k1::tests::secp256k1_recover_pubkey_works fails with
---- secp256k1::tests::secp256k1_recover_pubkey_works stdout ----
thread 'secp256k1::tests::secp256k1_recover_pubkey_works' panicked at packages/crypto/src/secp256k1.rs:355:88:
called `Result::unwrap()` on an `Err` value: GenericErr { msg: "signature error", backtrace: <disabled> }

This error is not caused with k256 v0.13.1.

Thanks you. I can reproduce the issue with k256 v0.13.2 and v0.13.3. On it

Caused by this change: Reject signatures which aren't low-S normalized (https://github.com/RustCrypto/elliptic-curves/pull/914) (https://github.com/RustCrypto/elliptic-curves/blob/master/k256/CHANGELOG.md#0132-2023-11-15)

Thank you for the report. I think we can address this in two steps:

Pin version to 0.13.1
Figure out if the old behaviour can be restored by a different way of using k256. I asked here, let's see how straight forward that is.

I think https://github.com/CosmWasm/cosmwasm/pull/2000 (last commit) is a better fix since it avoids the pinning

Update: the fix is now in #2014. In #2000 we are back to adding only test vectors without touching the implementation.


Blogposts improvements

Fixes: #429

Navigation after the updates:

I run the Hugo server locally without before looking at this page.
I should say that I was totally blind and could't find the Weekly Updates at first sight. After I saw your image in the comments here I could finally find them.
If we want the Weekly Updates to be more visible maybe we should raise them one level? Otherwise if we want them not to make too much noise is fine like it is now.

Renamed Weekly Updates to Weekly Status and moved it to the top as agreed on arch. I am trying to look into RSS in hugo right now

RSS feed with hugo works out of the box: https://packit.dev/posts/index.xml . With the new structure, also https://packit.dev/posts/weekly/index.xml will work. I am merging this since it was approved and no significant changes were made by the last push (just things we agreed on at arch) :)


Selection > Add Next Occurrence goes backwards

Issue Type: Bug
In HTML mode while editing CSS rules in a

This does not reproduce for me. Can you try disabling all extensions? Or am I doing something differently?

It happened again since I posted this, but now I can't repro on any of my systems. Thanks for verifying. Closing.


[Roadmap][Move] Generics/Collections

The development of generic types in Move is tracked in https://github.com/libra/libra/issues/1000.
This issue tracks providing generic collections. For v1, we specifically need a generic Vector type. Other collection types may be considered in the future, but for now we are only committing to implement Vector.

Generic Vectors have been implemented now (https://github.com/libra/libra/pull/694). We have made some subsequent changes to add more APIs to the Vector type (e.g., https://github.com/libra/libra/pull/972, https://github.com/libra/libra/pull/1110, https://github.com/libra/libra/pull/1089, etc.). There may be some further polishing of the interface, but we can consider this complete now.


refactor(api,robot-server): remove redundant Pydantic model validation

Overview
Work-in-progress performance PR. Putting this up as a draft so we can all look at it and contribute.
This PR tackles two very easy, and fairly substantial, performance wins that come out of default behaviors of both Pydantic and FastAPI:

Pydantic validates all fields on model creation via the constructor
FastAPI runs validation on response bodies

A vast majority of the data we're working with does not require validation; it was either validated when it came in via an HTTP request or it's our own data, which we know is good thanks to static type checking and good test coverage. Thus, the validations that Pydantic and FastAPI are running are simply useless (and blocking!) work.
Changelog

Replace most BaseModel constructor usage with the .construct method, which skips validation
Tweak route specifications in /protocols and /runs to opt out of FastAPI outgoing response validation

Review requests

[ ] Is this faster?

According to some benchmarking that @SyntaxColoring has run, the answer should be "yes, noticeably"
Anecdotally, on my computer's dev server, I'm seeing a 30-45% decrease in response time for GET /protocols/:protocol_id for a simple protocol on this branch compared to edge

[ ] Are optional fields still being correctly omitted from responses

More specifically, we need to make sure this PR doesn't regress the work down in #8920

Risk assessment
A lot of this "don't run validations" can sound scary, but honestly, I think outbound data validation is bad all around for us, even setting aside the performance implications. If the outbound response data fails validation, the client gets a 500 instead of the response body, which (IMO) is a pretty ungraceful degradation of the server in the face of something unexpected.
So... low risk I think.

Results are promising from these very roughly measured benchmarking results:

edge
This PR

Time for analysis to complete in background after POST /protocols
~20 s
~23 s

GET /protocols  response time while analysis is pending (small response)
~0.1 s
~0.1 s

GET /protocols response time once analysis is complete (large response)
~6.6s
~1 s

Here's my benchmark protocol:
metadata = {
    "apiLevel": "2.11"
}

def run(protocol):
    tip_rack = protocol.load_labware("opentrons_96_tiprack_300ul", 1)
    pipette = protocol.load_instrument("p300_multi", "left")
    for i in range(1000):
        pipette.pick_up_tip(tip_rack.columns()[0][0])
        pipette.return_tip(tip_rack.columns()[0][0])


Agora - AGLogonScript Errors Prevent Environment Setup

Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?

https://azurearcjumpstart.io/azure_jumpstart_ag/contoso_supermarket/deployment/
Agora
Describe the issue or the bug

Because it's expensive to keep this environment online, I often use "azd up" and "azd down". The deployment finishes successfully but the AGLogonScript inside the VM errors out.
To Reproduce

Additional context

@bpersino please follow the Issue templates and provide more details!

@likamrat I have updated the issue using the provided template.

@bpersino  Thanks for submitting this issue. Can you try a new clean deployment and let us know if you face the same issue? We are working to add more optimizations to overcome the error you reported.

I did two new deployments today and they both were successful.  So, whatever changed fixed the problem.  Thank you.


Track behavior

For smoking, two options: in the chat or through the tracker

[ ] Ask technical team whether easier to track only through the tracker or in the chat.

For PA, only in the chat for PA other than steps/running

Bouke:

Wearables can track many different activities --> would be nice to track as many things as possible automatically
Button for cigarettes - we need to explain this to the user
Notificaties during tracking days to remind them

Question to Bouke:

[ ] What specific parameters for PA can we track? (relevant for research protocol)


Field Extra Parameters are wrong on some query

For some query like the RangeQuery or the TermQuery an extra parameter like _name (used for Named Queries) won't be at the top level.
Example:
$range = new RangeQuery('field', ['gt' => 0]);
$range->addParameter('_name', 'myname');
$range->toArray();
/*
Result:
[
    'range' => [
        'field' => [
            'gt' => 0,
            '_name' => 'myname'
        ]
    ]
]
Instead of expected:
[
    'range' => [
        'field' => [
            'gt' => 0
        ],
        '_name' => 'myname'
    ]
]
*/

This is due to the use of parameters as query parameters and not extra ones
https://github.com/ongr-io/ElasticsearchDSL/blob/197eeddacccf2195bd7a9e0572ef24bb50a700c8/src/Query/TermLevel/RangeQuery.php#L72
It's the same for TermQuery
https://github.com/ongr-io/ElasticsearchDSL/blob/197eeddacccf2195bd7a9e0572ef24bb50a700c8/src/Query/TermLevel/TermQuery.php#L70
I think here the processArray() should be called after...
This works with a Terms query:
$terms = new TermsQuery('field', ['values']);
$terms->addParameter('_name', 'myname');
$terms->toArray();
/*
Result:
[
    'terms' => [
        'field' => [
            'values'
        ]
        '_name' => 'myname'
    ]
]
*/

An excellent catch @homersimpsons. Will write a test for those cases and will double check if repositioning processArray() fix the issue.

@saimaz Thank you.
Moving the processArray() won't give the expected result, for example if one use 'boost' => 2.0 he expect it to be at the FieldLevel (i.e. 'field' => ['boost' => 2.0, ...]) so this processArray() should stay here...
I guess the best is to get 2 array of parameters:

FieldParameters: That will be used at FieldLevel, and remains in constructor
QueryParameters: That would be used at QueryLevel (and get accessed only via accessors ? or last param in constructor ?)

Then in the process of building the array this will be generated
[
    $this->field => $this->fieldParameters,
    ...$this->queryParameters // (via array_merge / processArray())
]

So the resulting Query would be
[
    $query->getType() => [
        'field' => [FieldParameters],
        ...QueryParameters
    ]
]


Properly enable TLS/SSL verification when tls_verify is true

Bug is: new versions of the http_check configuration file have tls_verify but not disable_ssl_validation.
Setting tls_verify to True is not enough to enforce SSL verification, it also requires to set up disable_ssl_validation even though this field is not documented and deprecated.
Simply removes the compatibility layer for the edge case where people explicitly configure tls_ca_certs but have disable_ssl_validation: True (default value) in the config.
In the very old implementation of the check, this led to disable ssl validation.
Pros:

Much easier than Idea 1 to support and maintain in the future.

Cons:

We break users relying on this edge case. IMO if someone sets the CA certificate, they should expect the check to validate the SSL certificate.

Note: The check now relies on certifi root ca certs instead of the embedded python one.

This broke the ability to disable verification. Setting tls_verify to false doesn't let you disable the validation


Add glassmorphism effects to FightResult and other suitable components

For now, focus on:

Trying to apply the glassmorphism effect with a background color that depends on the win status of the fight.

I've been experimenting for almost 2 hours different combinations of blur / background images, the two ideas I would highlight the most are:

Combination 1 using svgs from svggenerator:

Combination 2 using a minimalistic image:

One thing I discovered is that using background-attachment: fixed; in <body> breaks the glassmorphism effect, and the blur does not apply to the container


Please be kind and intimidate Google implementing all ideas below

Full feature Android for desktop is the future, and You should be part of it. Would love to get rid of proprietary RemoxOS/PhoenixOS on may main station for build from source Android x86.

What does that have to do with this project?

And there is android-x86 which uses this project

Closing, Taskbar has added a lot of new features in the 2½ years since this bug was opened that bring it more in parity with Remix OS and Phoenix OS.


Source entries for cshtml files in the pdb aren't fully qualified when razor is compiled into the assembly

For instance in the diagnostics package, it includes an ErrorPage.cshtml but without the full path. This will make it difficult to index sources on a source server or debug into source.
Notice ErrorPage.cshtml sitting there all by itself
> dbh C:\Users\rynowak\AppData\Local\Temp\szfjxbc5.k0o\lib\K10
\Microsoft.AspNet.Diagnostics.pdb src

C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\ErrorPageExtensions.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\WelcomePageExtensions.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\ErrorPageMiddleware.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\ErrorPageOptions.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\Resources.Designer.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\WelcomePageMiddleware.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\WelcomePageOptions.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\Views\BaseView.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\Views\DiagnosticsPage.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\Views\ErrorDetails.cs
ErrorPage.cshtml
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\Views\ErrorPage.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\Views\ErrorPageModel.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\Views\StackFrame.cs
C:\BuildAgent\work\7a0dd814ac68ad3d\src\Microsoft.AspNet.Diagnostics\Views\WelcomePage.cs
DiagnosticsPage.cshtml
WelcomePage.cshtml

Copied from aspnet/KRuntime#216

This doesn't look like it has to do with our code, diagnostics pre-generate the .cs files before compiling.
See: https://github.com/aspnet/Diagnostics/blob/dev/src/Microsoft.AspNet.Diagnostics/Views/ErrorPage.cs


Discussion: Disable JS build pipeline when preview is not required

Whilst QA'ing #16617, I noticed considerable lag whilst using the code editor. I believe this lag is introduced through the combination of the 750ms debounce and the attempt to transform the campers code on the fly.
Should we disable the build pipeline when the preview pane is not required?
@BerkeleyTrue
cc @freeCodeCamp/moderators

Yes, that should be a good idea, unless there is a requirement on the build to be used by tests. Right?

The build is also triggered when the Run Tests button is pressed, so that shouldn't be an issue

I am trying to learn about how FCC works so I am sorry if this makes no sense. And if it does not, please help educate me because I am looking to get more involved.
Would it be possible to put in a toggle of transforming the code on the fly or not, even if the preview pane is used? Then a button to build the preview if the toggle is off? That way if any users experience any lag when the preview pane is still used they can mitigate that.
Then in challenges that do not need the preview pane it would automatically be off and hidden?
Maybe that is way more complex then I am making it sound, but it sounds like you are talking about building the basic functionality of that anyways.
Again, please let me know if that makes no sense, thank you!

Hi @TJBarrettJR

I am trying to learn about how FCC works so I am sorry if this makes no sense. And if it does not, please help educate me because I am looking to get more involved.

That's awesome, and we would love to have you help us.

Would it be possible to put in a toggle of transforming the code on the fly or not, even if the preview pane is used? Then a button to build the preview if the toggle is off? That way if any users experience any lag when the preview pane is still used they can mitigate that.
Then in challenges that do not need the preview pane it would automatically be off and hidden?
Maybe that is way more complex then I am making it sound, but it sounds like you are talking about building the basic functionality of that anyways.

Yes, we are talking about having this, internally by default. That is without any user need to toggle the setting.
That said, I am think what you are interested in is with a way to disable the preview, for example until you have completed the code, and would like to see the preview with a button like "Display Preview"?
If yes, that's a different issue than this thread, and we welcome you to log a feature request on this tracker.
P.S: We hangout in Contributors Chat room, where we can answer all queries.
Happy contributing!


Overriding examples for action responses

We have some actions for which we'd like to override the example response. (In our particular situation, they are always on the :ok response, but in principle we could consider this as applying to other responses too.)
We don't want to use views to handle this because the examples we want to override are in nested media types, so we'd have to create views for all of the intermediate media types to achieve this. As all of the intermediate views would be identical to the defaults, this doesn't feel ideal. There are three high-level ideas I have for this, none of which seem especially stronger than the others:

Allow a totally custom override for the examples. I've hacked together a quick demo of this which you can see at smcgivern/praxis#1.
action :show do
  # ...
  example do |default_example|
    default_example[:name] = 'Override'
    default_example
  end
end

Let a response define several views to try, in order, falling back if a view is not available for a media type.
action :show do
  # Will try the :override view on each media type as it's rendered, and use :default otherwise.
  response :ok, V1::MediaTypes::Goodbye, views: [:override :default]
end

Make it possible to set a view as an alias of another view, so that identical views can have multiple names. (I don't want to provide an example for this, because I don't really like it.)

Closing very old issues


Invisible plot lines following OS and package updates

On a fresh install of Fedora 25 with all packages necessary to run dvmdostem, the model runs fine, but the calibration viewer only displays plot lines while the window is being resized. If the window is static, the plot lines disappear. In addition, when the suite is changed using the radio buttons, the following error occurs:
Parsing command line arguments...
Setting up logging...
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib64/python2.7/lib-tk/Tkinter.py", line 1537, in __call__
    return self.func(*args)
  File "/usr/lib64/python2.7/lib-tk/Tkinter.py", line 587, in callit
    func(*args)
  File "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_tkagg.py", line 147, in _on_timer
    TimerBase._on_timer(self)
  File "/usr/lib64/python2.7/site-packages/matplotlib/backend_bases.py", line 1305, in _on_timer
    ret = func(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 1049, in _step
    still_going = Animation._step(self, *args)
  File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 855, in _step
    self._draw_next_frame(framedata, self._blit)
  File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 875, in _draw_next_frame
    self._post_draw(framedata, blit)
  File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 898, in _post_draw
    self._blit_draw(self._drawn_artists, self._blit_cache)
  File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 913, in _blit_draw
    a.axes.draw_artist(a)
  File "/usr/lib64/python2.7/site-packages/matplotlib/axes/_base.py", line 2334, in draw_artist
    raise AttributeError(msg)
AttributeError: draw_artist can only be used after an initial draw which caches the render

Hmm, this seems like it might be an annoying and tricky issue to deal
with...
On Fri, Dec 2, 2016 at 5:57 PM, rarutter<EMAIL_ADDRESS>wrote:

On a fresh install of Fedora 25 with all packages necessary to run
dvmdostem, the model runs fine, but the calibration viewer only displays
plot lines while the window is being resized. If the window is static, the
plot lines disappear. In addition, when the suite is changed using the
radio buttons, the following error occurs:
Parsing command line arguments...
Setting up logging...
Exception in Tkinter callback
Traceback (most recent call last):
File "/usr/lib64/python2.7/lib-tk/Tkinter.py", line 1537, in call
return self.func(*args)
File "/usr/lib64/python2.7/lib-tk/Tkinter.py", line 587, in callit
func(*args)
File "/usr/lib64/python2.7/site-packages/matplotlib/backends/backend_tkagg.py", line 147, in _on_timer
TimerBase._on_timer(self)
File "/usr/lib64/python2.7/site-packages/matplotlib/backend_bases.py", line 1305, in _on_timer
ret = func(*args, **kwargs)
File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 1049, in _step
still_going = Animation._step(self, *args)
File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 855, in _step
self._draw_next_frame(framedata, self._blit)
File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 875, in _draw_next_frame
self._post_draw(framedata, blit)
File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 898, in _post_draw
self._blit_draw(self._drawn_artists, self._blit_cache)
File "/usr/lib64/python2.7/site-packages/matplotlib/animation.py", line 913, in _blit_draw
a.axes.draw_artist(a)
File "/usr/lib64/python2.7/site-packages/matplotlib/axes/_base.py", line 2334, in draw_artist
raise AttributeError(msg)
AttributeError: draw_artist can only be used after an initial draw which caches the render
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ua-snap/dvm-dos-tem/issues/250, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAzMT61hk0OFUQzkJyEthCNPJztT1RSVks5rENqkgaJpZM4LDLSe
.

Any more clues if you try --loglevel=debug?

Yeah, this is going to be interesting. I'm going to talk to Helene about remote access so I can keep messing with it (the laptop is in FAI).


Elements inside simplebar can't have height: 100%

Hi, currently it's not possible to set height: 100% on a element. It simply won't grow to the desired size.
If I compare it with a native-scroll-container its working though.
Here's a fiddle: http://jsfiddle.net/gvne6xk5/2/
The red container is the simplebar-scroll container and the blue one is the native-scroll container.
Notice the size difference of the h2 elements.

Thanks for your report.
I think you are right, there is no way of doing this in pure css. That seems like a limitation of how the plugin works. I don't see any solution to that in pure css :/
I will improve the caveats section with this.

That's very unfortunate...
I've tested other scrollbar plugins and the in the caveats section mentioned OverlayScrollbars plugin does support this behavior: http://jsfiddle.net/gvne6xk5/7/
Maybe you can ask the maintainer how he's doing it, because I think this is a quite important thing.

This is fixed in latest beta version.


[1.19.1] Game crashes after starting

https://gist.github.com/pewblaze/165d03e21cc4e940163555a85888170c
Hi, the game crashes after starting. I also tested it with a new install and this mods:

Duplicate of my issue #515, it happens because of the new chat and social interaction system, ban the features I mentioned and the mod will work.

Ah i see! Thank you!


Bump package to 5.0.1, bump ember-macro-helpers to 4.2.2

Version bump to include bug fix: https://github.com/kellyselden/ember-macro-helpers/pull/273
If cool with this (I was thinking it was a patch versus a minor, but not positive), would need a npm bump too.
Thanks for making the fix!

@kellyselden thanks that makes sense, fixed, lmk if anything else!

Perfect. Thanks!


[match] suppress null byte message

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
https://github.com/fastlane/fastlane/pull/20187/ introduced the ability to pass either a file path or the raw cert data to self.get_cert_info. It works by calling File.exist? which prints a harmless error message when a cert is passed in:
ERROR [2022-07-20 09:52:59.80]: get_cert_info: path name contains null byte

This PR suppresses the message and resolves #20489.
Description
Catches the error when it's raised and does nothing.
I tested the changes by running match and observed that the error message no longer prints.
Testing Steps
Run match; notice the error message is gone.

sorry about that! thanks for finding and fixing the issue 😅


Correction for raw affiliation INSERM, Univ Rennes, INRAE, Institut NUMECAN (Nutrition Metabolisms and Cancer) UMR_A 1341, UMR_S 1317, Rennes, France

Correction needed for raw affiliation INSERM, Univ Rennes, INRAE, Institut NUMECAN (Nutrition Metabolisms and Cancer) UMR_A 1341, UMR_S 1317, Rennes, France
raw_affiliation_name: INSERM, Univ Rennes, INRAE, Institut NUMECAN (Nutrition Metabolisms and Cancer) UMR_A 1341, UMR_S 1317, Rennes, France
new_rors: 003vg9w96;02vjkv261;015m7wh34;03zb6nw87
previous_rors: 003vg9w96;02vjkv261;015m7wh34
works_examples: W4386407414
contact: 3575cae28178a3039f91198f3f07c9f6:66a2367c526c31004fc535a915215259 @ univ-rennes.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Update usage of redirectTo to reflect gotrue-js usage

Fixes #29
I just saw your message, I already had this built up and testing it out, so you can feel free to use this!

The only slightly dodgy thing here is that when the URI comes back in from the redirect, the query string part is actually a query string-encoded fragment. This affects the HttpUtility.ParseQueryString(uri.Query) call in GetSessionFromUrl, since uri.Query is null.
I worked around this by adjusting my call to
            var uri = new Uri(Intent.Data.ToString().Replace("#", "?"));             client.GetSessionFromUrl(uri);
but that's probably not ideal.

Thanks for taking the time to open this, really nice to have your contribution!
I would rather use the built-in UriBuilder to handle adding the redirect_to into the query, so you'll see those changes there.
I also took your suggestion and adjusted the client.GetSessionFromUrl() (with a slight adjustment).
Will you check those changes and see if they work well for you?

Happy to help!
The updates look great, I prefer the UriBuilder as well. I loaded up the new version in my application and it works perfectly well

Awesome, I'll bundle a release and credit you in the CHANGELOG - let me know if you find anything else in the future!


questions about modules_to_save

First of all thank you for your work.
At the beginning, lora did not copy the weight of these trainable parameters when setting modules_to_save. However, after setting modules_to_save in the later update, a weight was copied for these trainable parameters, which led to the increase of VRAM and even OOM.  I would like to ask why this parameter is set and how to modify it so that this part of the weight can not be copied and can be trained normally. Looking forward to your reply, thank you! @pacman100

Requesting an answer.Thanks！

Hey, first of all, modules_to_save is not really specific to LoRA but a more general mechanism to allow certain modules to be trained independent of the adapter methods (so full fine-tuning).
If I understand your question correctly, you're asking why the ModulesToSaveWrapper, which is used when modules_to_save are set, creates a copy of the original parameters. The reason for that is that users may want to disable the adapter to get the original outputs from the base model, or they might want to unload the base model. To allow this functionality, we need to keep a copy of the original weights. This will, unfortunately, mean that a bit of extra memory is used.

Hey, first of all, is not really specific to LoRA but a more general mechanism to allow certain modules to be trained independent of the adapter methods (so full fine-tuning).modules_to_save
If I understand your question correctly, you're asking why the , which is used when are set, creates a copy of the original parameters. The reason for that is that users may want to disable the adapter to get the original outputs from the base model, or they might want to unload the base model. To allow this functionality, we need to keep a copy of the original weights. This will, unfortunately, mean that a bit of extra memory is used.ModulesToSaveWrapper``modules_to_save

Hello, i wander if i load the model like this

how can i merge the model, modules_to_save should be the weight like lora and added to the origin weight ,or modules_to_save should be the new weight replace the origin

@191220042 I don't quite understand your question. Could you maybe create a new issue and describe, ideally with some code, what you would like to achieve?

modules_to_save should be the weight like lora and added to the origin weight

This is not possible. With LoRA adapters, the multiplied LoRA weights can be added to the base weight, but with modules_to_save, the base weights need to be replaced completely.

@191220042 I don't quite understand your question. Could you maybe create a new issue and describe, ideally with some code, what you would like to achieve?

modules_to_save should be the weight like lora and added to the origin weight

This is not possible. With LoRA adapters, the multiplied LoRA weights can be added to the base weight, but with modules_to_save, the base weights need to be replaced completely.

thank you, You've answered my question，I added output_layer to the modules_to_save when I was fine-tuning ChatGPT with LoRa, but I found that it just copied the original parameters and opened the gradient without actually changing it

@191220042 I don't quite understand your question. Could you maybe create a new issue and describe, ideally with some code, what you would like to achieve?

modules_to_save should be the weight like lora and added to the origin weight

This is not possible. With LoRA adapters, the multiplied LoRA weights can be added to the base weight, but with modules_to_save, the base weights need to be replaced completely.

thank you, You've answered my question，I added output_layer to the modules_to_save when I was fine-tuning ChatGLM with LoRa, but I found that it just copied the original parameters and opened the gradient without actually changing it


Send error logs to Sentry

Part of #21. Based on #57.
I looked at the source for all calls to logger.(Err|Error|Panic|Fatal) and added an accompanying call to sentry.CaptureException. I also did some context plumbing to try tie as many Sentry events to the syncv3 requests that triggered them.
The diff is quite large. I am happy to split this up into smaller PRs if that would help.

I should also do an audit for panic() calls and stick in logging. Can make that a separate change though.


Not able to deploy clusters when external auth provider is enabled

Rancher Server Setup

Rancher version: 2.6-head commit id: 0ab00d
Installation option (Docker install/Helm Chart): helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1

Proxy/Cert Details: rancher generated

Information about the Cluster

Kubernetes version: 1.20.9
Cluster Type (Local/Downstream): Downstream - Windows custom RKE1, k3s Imported

Describe the bug
Not able to deploy clusters as a standard user when external auth provider is enabled
To Reproduce:

On 2.6-head, enable GH Auth or AD Auth
Deploy clusters using standard user token/as an admin
Windows custom RKE1 and Imported k3s clusters dont come up. Error seen - Error while applying agent YAML, it will be retried automatically: exit status 1, Error from server (InternalError): an error on the server ("unable to create impersonator account: error getting service account token: serviceaccounts \"cattle-impersonation-system/cattle-impersonation-u-kl3nli645y\" not found") has prevented the request from succeeding
Imported RKE2 works fine though

Note:
On 2.6.0-rc1 it works

On 2.6 - head commit id: 4b6af95d and on master-head commit id: 524aec1

On 2.6-head, enable AD Auth HA setup
Deploy clusters using standard user token/as an admin - RKE1 custom clusters
No issues seen, Clusters come up Active

On an upgrade from 2.5.9 to 2.6.0-rc2 , this issue is seen,

On 2.5.9 deploy a few downstream clusters
Upgrade rancher to 2.6.0-rc2
One of the downstream clusters (Custom RKE1 cluster) is stuck in Provisioning state with error Error while applying agent YAML, it will be retried automatically: exit status 1, Error from server (InternalError): an error on the server ("unable to create impersonator account: error getting service account token: serviceaccounts \"cattle-impersonation-system/cattle-impersonation-u-bdasg4j7sc\" not found") has prevented the request from succeeding

I was never able to reproduce this myself, but we've merged a change that will hopefully address the issue. If it doesn't, we also added trace logging so that if the problem is seen again, we can get more information about it.

On an upgrade from 2.5.9 to 2.6-head commit id: f811996

This issue was not seen, The setup was exactly as it was when the issue was originally seen
A cluster - with all v2 charts enabled. Custom cluster - 1 etc/control plane and 3 worker nodes
Will close this issue. Will reopen or log a new one if we see this again.


Define BlobMappingExtension interface for getting mapping Ambry blob Ids for external url paths

This pr defines a layer for getting mapping Ambry blob Ids for external url paths. This could be used for Ambry to serve external requests/urls directly with the help of library plugins implementing this interface.

Codecov Report

Merging #1850 (57fb5a0) into master (4480374) will decrease coverage by 58.76%.
The diff coverage is 0.00%.

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


Cannot install React RC with Material UI

Steps to reproduce
npm install @mui/material @emotion/react @emotion/styled
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^18.0.0 || ^19.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@mui/material
npm ERR!   @mui/material@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/user/.npm/_logs/2024-10-24T11_03_10_171Z-eresolve-report.txt
npm ERR!
  Output from `npx @mui/envinfo` goes here.

Search keywords: Nextjs
Search keywords:

@mj-manna Would you mind sharing a repro?

One issue is that the @mui/material-nextjs package requires Next.js 13 or 14 as a peer dependency, not 15:
https://github.com/mui/material-ui/blob/master/packages/mui-material-nextjs/package.json

I am fixing this.

This is fixed from our side but the error is still shown with Emotion because the current Next.js uses React release candidate version which is not working with Emotion's peerDependency `">=16.8.0"
Ref: https://github.com/npm/cli/issues/4958
The workaround is to run npm install --legacy-peer-deps

I am having issues updating @mui/material-nextjs only having updated to Next 15, not React 19 RC:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/next
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^14.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@mui/material-nextjs
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

I am having issues updating @mui/material-nextjs only having updated to Next 15, not React 19 RC:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/next
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ^14.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@mui/material-nextjs
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

@macedomauriz Hi, after 2 days I managed to fix it. Try to add this section to package.json and replace react version with yours
"overrides": {
  "react": "^19.0.0-rc-fb9a90fa48-20240614",
  "react-dom": "^19.0.0-rc-fb9a90fa48-20240614",
  "@emotion/react": {
    "react": "^19.0.0-rc-fb9a90fa48-20240614"
  },
  "@mui/material-nextjs": {
    "next": "^15.0.1"
  }
}

I've found that while you can install Material-UI on NextJS 15 (even without React 19) -- it just doesn't work, none of the hydration works, you get random client-side errors, and the theme palette mode won't go dark (?) Assume emotion incompatability.
Tried both NextJS 15 w/ React 18 and NextJS 16 w/ React 19.

I've found that while you can install Material-UI on NextJS 15 (even without React 19) -- it just doesn't work, none of the hydration works, you get random client-side errors, and the theme palette mode won't go dark (?) Assume emotion incompatability.
Tried both NextJS 15 w/ React 18 and NextJS 16 w/ React 19.

Please provide a repo that we can take a look at.

Please provide a repo that we can take a look at.

Sadly not possible. We dropped NextJS on all projects that we were allowed to. Remaining projects are private or under contract. However, my understanding is the process/result should be nearly identical for anyone else, even on a fresh project. After listing reproduction and trying again, I've found the issue is either React19 or TurboPack. If we reject both, the upgrade works.
I've attached following the steps (at least, what I can) for you to see. First I have the working NextJS14 / MaterialUI6 project below. For troubleshooting, we've done a fresh install, a fresh build, and triple-checked out dependency versions before beginning the upgrade.

Check our package versions before the upgrade
$ rm -rf node_modules/ && echo $? # 0 (Success)
$ yarn install   2>&1  && echo $? # 0 (Success)
$ yarn run build 2>&1  && echo $? # 0 (Success)

# Check our package versions pre-upgrade (known working state)
$ cat package.json | jq .dependencies | grep "@mui\|next\|emotion\|react"
  "@emotion/cache": "^11.13.1",
  "@emotion/react": "^11.13.3",
  "@emotion/server": "^11.11.0",
  "@emotion/styled": "^11.13.0",
  "@mui/icons-material": "^6.1.6",
  "@mui/material": "^6.1.6",
  "@mui/material-nextjs": "^6.1.6",
  "@mui/system": "^6.1.6",
  "@mui/x-charts": "^7.22.1",
  "next": "^14.2.16",
  "react": "^18.3.1",
  "react-dom": "^18.3.1",

$ cat package.json | jq .devDependencies | grep "react\|eslint"
  "@eslint/js": "^8.57.1",
  "@next/eslint-plugin-next": "^14.2.16",
  "@types/eslint__js": "^8.42.3",
  "@types/react": "^18.3.12",
  "@types/react-dom": "^18.3.1",
  "@typescript-eslint/eslint-plugin": "^8.12.2",
  "@typescript-eslint/parser": "^8.12.2",
  "eslint": "^8.57.1",
  "eslint-config-next": "^14.2.16",
  "eslint-plugin-import": "^2.31.0",
  "eslint-plugin-mui-path-imports": "^0.0.15",
  "eslint-plugin-react": "^7.37.2",
  "eslint-plugin-react-hooks": "^5.0.0",
  "typescript-eslint": "^8.12.2"

Setup a Fresh MaterialUI Project
First, setup a fresh MUI project:

Install NextJS 14 / MaterialUI 6 / Typescript / ESLint@8
Use the Pages Router
Follow the MaterialUI NextJS Integration Guide
Set your theme's colour mode to dark -- See it work

Upgrade the Project using the supplied commands

Use the codemod command to upgrade the project to Next15
Reject the React19 upgrade, opting to stay on React18
Allow the other codemods to run (except skip the app router one)

I've found 50% of the time these fail randomly (EPERM on file delete) if that happens, just do it again.

Site is now rendered white (and broken), with CSS and JS errors throughout.

The materialui-nextjs bridge only has Next14 imports, methinks blame that?

Alright, now it's time to attempt the upgrade...
First, we realize there are only instructions for App Router, so we follow those: https://nextjs.org/docs/app/building-your-application/upgrading/version-15
$ npx @next/codemod@canary upgrade latest
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

  Detected installed versions:
  - React: v18.3.1
  - Next.js: v14.2.16
√ Do you prefer to stay on React 18? ... yes
√ Enable Turbopack for next dev? ... no
? The following codemods are recommended for your upgrade. Select the ones to apply. »
Instructions:
    ↑/↓: Highlight option
    ←/→/[space]: Toggle selection
    a: Toggle all
    enter/return: Complete answer
( )   (v15.0.0-canary.179) app-dir-runtime-config-experimental-edge
(*)   (v15.0.0-canary.171) next-async-request-api
(*)   (v15.0.0-canary.153) next-request-geo-ip
Upgrading your project to Next.js 15.0.2..
➤ YN0000: · Yarn 4.5.1
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + @next/eslint-plugin-next@npm:15.0.2, eslint-config-next@npm:15.0.2, next@npm:15.0.2, and 12 more.
➤ YN0085: │ - @next/env@npm:14.2.16, @next/eslint-plugin-next@npm:14.2.16, @next/swc-darwin-arm64@npm:14.2.16, and 15 more.
➤ YN0000: └ Completed in 0s 564ms
➤ YN0000: ┌ Post-resolution validation
➤ YN0086: │ Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.
➤ YN0000: └ Completed
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 5 packages were added to the project (+ 290.97 MiB).
➤ YN0000: └ Completed in 3s 175ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 3s 410ms
➤ YN0000: · Done with warnings in 7s 210ms
WARNING: Git directory is not clean. Forcibly continuing.
Executing command: jscodeshift --no-babel --ignore-pattern=**/node_modules/** --ignore-pattern=**/.next/** --extensions=tsx,ts,jsx,js --transform<EMAIL_ADDRESS>S:\Projects\com.github\[redacted]
Processing 62 files...
Spawning 31 workers...
Sending 2 files to free worker...
[... last line repeated ...]
All done.
Results:
0 errors
62 unmodified
0 skipped
0 ok
Time elapsed: 0.871seconds
WARNING: Git directory is not clean. Forcibly continuing.
√ Is your app deployed to Vercel? (Required to apply the selected codemod) ... no
Skipping codemod "next-request-geo-ip" as your app is not deployed to Vercel.

✔ Codemods have been applied successfully.

Please review the local changes and read the Next.js 15 migration guide to complete the migration.
https://nextjs.org/docs/canary/app/building-your-application/upgrading/version-15

Then, verify the upgrade
Now we verify that the upgrade completed, by checking package versions and building.
$ yarn install   2>&1  && echo $? # 0 (Success)
$ yarn run build 2>&1  && echo $? # 0 (Success)

$ cat package.json | jq .dependencies | grep "@mui\|next\|emotion\|react"
  "@emotion/cache": "^11.13.1",
  "@emotion/react": "^11.13.3",
  "@emotion/server": "^11.11.0",
  "@emotion/styled": "^11.13.0",
  "@mui/icons-material": "^6.1.6",
  "@mui/material": "^6.1.6",
  "@mui/material-nextjs": "^6.1.6",
  "@mui/system": "^6.1.6",
  "@mui/x-charts": "^7.22.1",
  "next": "15.0.2",
  "react": "18.3.1",
  "react-dom": "18.3.1",

$ cat package.json | jq .devDependencies | grep "react\|eslint"
  "@eslint/js": "^8.57.1",
  "@next/eslint-plugin-next": "15.0.2",
  "@types/eslint__js": "^8.42.3",
  "@types/react": "18.3.12",
  "@types/react-dom": "18.3.1",
  "@typescript-eslint/eslint-plugin": "^8.12.2",
  "@typescript-eslint/parser": "^8.12.2",
  "eslint": "^8.57.1",
  "eslint-config-next": "15.0.2",
  "eslint-plugin-import": "^2.31.0",
  "eslint-plugin-mui-path-imports": "^0.0.15",
  "eslint-plugin-react": "^7.37.2",
  "eslint-plugin-react-hooks": "^5.0.0",
  "typescript-eslint": "^8.12.2"

Test the result worked
Alright, all good so far, now let's test that the site works:
$ yarn run dev
   ▲ Next.js 15.0.2
   - Local:        http://localhost:9250
   - Environments: .env

 ✓ Starting...
 ✓ Ready in 1513ms
 ○ Compiling / ...
 ✓ Compiled / in 3.2s (1221 modules)
 GET / 200 in 3632ms

Success.

how about npm?

Hey everyone!
For the issue described in this PR
The root cause is npm doesn't consider 19.0.0-rc.* to be a valid ^19.0.0 version. If you need React 19 before it becomes stable, you have the following options:

Run npm install with --force or --legacy-peer-deps flags. If React is the only dependency you're having issues with, then this is safe to do. That's why yarn and pnpm allow it.
Use yarn or pnpm instead of npm

This issue should stop happening once React 19 is stable.
I wouldn't consider this an issue on Material UI's side, and there are two possible workarounds, so I'm closing it.
For other issues with Next.js 15 and or React 19
Please open separate issues so we can track and properly address each one.


Fix copy'n'paste error in front_insert_iterator

https://github.com/tcbrindle/NanoRange/blob/275a8088ae5a7bb409a2ef9c60e9df5f3fae3c72/include/nanorange/iterator/front_insert_iterator.hpp#L33
This looks like a copy & paste error where back_insert_iterator.hpp was copied and push_back() was mistakenly changed to front_back instead of push_front like in line 27:
https://github.com/tcbrindle/NanoRange/blob/275a8088ae5a7bb409a2ef9c60e9df5f3fae3c72/include/nanorange/iterator/front_insert_iterator.hpp#L27
Disclaimer: I just started toying with NanoRange, so the code may be totally fine. In that case just close this issue, sorry. Also, I didn't find any tests for the insert iterators, so I couldn't add a test case.

That is definitely a copy-and-paste error, well spotted!

Fixed in #104