Japanese string is corrupted.

Describe the bug
If avatar name includes Japanese character, the report of /avatar/config string is wrong
To Reproduce
Change to an avatar with Japanese in the name.
Expected behavior
Expect the string will not be corrupted.
Unicode
日 --- U+65e5
本 --- U+672c
語 --- U+8a9e
UTF-8
日 --- E6 97 A5
本 --- E6 9C AC
語 --- E8 AA 9E
Expected
"日本語" -> E6 97 A5 E6 9C AC E8 AA 9E
Actual
"日本語" -> E5 2C 9E
Screenshots

I'll note that according to the OSC specs, the string datatype is specifically an ASCII string. As such, paths will probably need to be passed as a blob type.

I'll note that according to the OSC specs, the string datatype is specifically an ASCII string. As such, paths will probably need to be passed as a blob type.

Based on this commit, the /avatar/config endpoint is being removed and instead they'll just be using the avatar ID.
This works around this specific issue, and will just have to be a design consideration going forward.

Currently planning to remove the /avatar/config output while we work through the issues with this approach. An alternative would be to output the path relative to the PersistentData directory, which should only be ASCII characters. So VRChat would send the string OSC\usr_xxxxxxxx-xxxx\Avatars\avtr_xxx_xxxxx_xxxxx.json to the address /avatar/configPath, and an external tool could combine that with the root of the user's VRChat persistent data directory. This way, paths with possible non-ASCII characters are avoided, and if the path to config data changes in the future, this endpoint will still report correctly.
However - this does not properly send config information for Build & Test avatars (whose configs are not written to disk).

Currently planning to remove the /avatar/config output while we work through the issues with this approach. An alternative would be to output the path relative to the PersistentData directory, which should only be ASCII characters. So VRChat would send the string OSC\usr_xxxxxxxx-xxxx\Avatars\avtr_xxx_xxxxx_xxxxx.json to the address /avatar/configPath, and an external tool could combine that with the root of the user's VRChat persistent data directory. This way, paths with possible non-ASCII characters are avoided, and if the path to config data changes in the future, this endpoint will still report correctly.
However - this does not properly send config information for Build & Test avatars (whose configs are not written to disk).

While this solves this specific issue, this doesn't resolve that you cannot send messages to an avatar parameter containing UTF-16.

Currently planning to remove the /avatar/config output while we work through the issues with this approach. An alternative would be to output the path relative to the PersistentData directory, which should only be ASCII characters. So VRChat would send the string OSC\usr_xxxxxxxx-xxxx\Avatars\avtr_xxx_xxxxx_xxxxx.json to the address /avatar/configPath, and an external tool could combine that with the root of the user's VRChat persistent data directory. This way, paths with possible non-ASCII characters are avoided, and if the path to config data changes in the future, this endpoint will still report correctly.
However - this does not properly send config information for Build & Test avatars (whose configs are not written to disk).

Ah, that certainly makes more sense if you're planning on replacing /avatar/config with one that can be controlled to not include unicode. Note of course that the avatar name needs to be either removed from the config path or sanitized in this case.


[1.19.2 Bug]: Two types of fluid even though you can only get one

Bug Description
There's a bucket of Raw Experience (and fluid for it), but the obelisk cannot accept it nor can it be extracted.
How to Reproduce?

Open minecraft
Filter JEI to the mod and check for the Raw Experience

Expected Behavior
Only having Cognitium
Version
1.4.8
Mod Loader Version
43.3.2
Mod Loader
Forge
Logs or additional context
N/A - but it would be nice if you linked this issue tracker on the mod's page.
Code of Conduct

[X] I have searched the issue tracker and confirmed that the issue has not been reported
[X] I have checked the FAQ (if one is present) and my issue is not listed
[X] I have verified that I am using the latest version of the mod
[X] I have verified that I have installed all the required dependencies for the mod
[X] I have verified that I do not have Optifine installed. We will close issues if we detect Optifine is in your pack. We cannot fix Optifine issues. Please do not report issues with Optifine present.

I also noticed that you can't pump fluids into the Obelisk (at least with Create's pump). It'd be nice if we could do that.

Raw experience is a legacy fluid that was used in earlier versions of the mod; it's still around for backwards compatibility. It'll be removed when the content expansion releases!


tracy: 0.10 -> 0.11.1 + other changes

Description of changes
https://github.com/wolfpld/tracy/releases/tag/v0.11.0
https://github.com/wolfpld/tracy/releases/tag/v0.11.1
Supersedes https://github.com/NixOS/nixpkgs/pull/320273. A follow up to https://github.com/NixOS/nixpkgs/pull/315205.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

There's some conflicts blocking a merge, I assume. Would be nice to have this in!

Thanks for working on this @paveloom
I've checked your changes, the conflicts are due to the stdenv.isXXX -> stdenv.hostPlatform.isXXX treewide rename. Just changing those will fix it. Tested it and it works fine. Could you rebase, please?

LGTM and works nicely on Wayland (Plasma).
In case this is useful: To test I've rebased your changes and resolved conflicts. (Looks like packages were formatted tree-wide recently)
Feel free to use/take these rebased commits :slightly_smiling_face:  https://github.com/NixOS/nixpkgs/compare/master...Mrmaxmeier:nixpkgs:tracy-wayland-0.11.1

Thanks. This also fixes the build with the current boost version.


Normalization Conventions and Condon-Shortley Sign Conventions

Regarding the normalization conventions, there are three main types (see solid_harmonics2/docs/src/SH.md for more details).

Orthonormalized
Schmidt semi-normalized (Racah's normalization): In this normalization, Y_0^0 is equal to 1.
4π-normalized

Polynomials4ML utilizes orthonormalized complex and real spherical harmonics, orthonormalized complex solid harmonics and Schmidt semi-normalized real solid harmonics.
As for Condon-Shortley sign convention, there are two sign conventions for associated Legendre polynomials.

Include the Condon-Shortley phase factor (-1)^m
Exclude the Condon-Shortley phase factor  (-1)^m

Based on my understanding, Polynomials4ML includes Condon-Shortley phase factor for complex spherical harmonics, complex and real solid harmonics, but not for the real spherical harmonics.

Thank you for doing that research!!
I see - so this is why you added the (-1) factors for the real solid harmonics. So what is your proposal - should we also include the (-1) factors in the real spherical harmonics? or remove it from the real solid harmonics? I don't have too strong a view either way. What would the consequences of either decision be?

I think the inclusion or exclusion of the Condon-Shortley phase factor is relatively unimportant. We only need to check and be aware of the sign convention used in the sources we are using, and correctly account for any differences there.

In that case would you be happy to remove it from the real solid harmonics? It will save us a few lines of code and possibly even a bit of performance?

Maybe we can keep it as it is for now and decide later whether any changes are necessary when we encounter related issues?

Okay, I'll remove it

thank you - most importantly it is then consistent with the spherical harmonics.
everything ready to wrap up your PR? Then we can start focusing on the actual wave function...

I'm almost finished with the unit tests and documentation, except for resolving the issue with the Laplacian ForwardDiff test. And I still need to remove the Condon-Shortley phase factor from the real solid harmonics as we discussed above. Earlier today, I merged version 0.1.0-dev into the solid harmonics 2 branch, but it looks like you made another modification after that.

closing this - but we should review and polish the documentation for all our basis sets over the next few months...


switch statement breaks string comparison

I hope I'm not going nuts, this really seems "off the wall" - what am I missing?
I have code in a node which works 100% as expected but if I include a switch statement above it, it produces bizarre results.
What are the steps to reproduce?
let repo='/home/pi/H4firmware'
let hardcoded='/home/pi/H4firmware/H4.ino.d1_mini.bin'
let bin1
let bin2
let type='WEMOS_D1MINI'
bin1='d1_mini'
switch(type){
    case 'WEMOS_D1MINI':
        bin2='di_mini';
        break;
}
//bin2='d1_mini' // comment out this line and msg is '...nuts'
let f1=`${repo}/H4.ino.${bin1}.bin`
let f2=`${repo}/H4.ino.${bin2}.bin`
if(f1!==f2) node.warn('completeley nuts')
else node.warn('perfectly normal')
node.warn('f1='+f1+' '+typeof f1+' L='+f1.length)
node.warn('f2='+f2+' '+typeof f2+' L='+f2.length)
node.warn(f1===hardcoded) // true OF COURSE!
node.warn(f2===hardcoded) // false ???

return msg;

What do you expect to happen?
I expect f1===f2=== hardcoded
and that the msg"completely normal" should appear
Result with bin2 assignment commented out
4/3/2020, 11:43:06 PMnode: Works OK
function : (warn)
"completeley nuts"
4/3/2020, 11:43:06 PMnode: Works OK
function : (warn)
"f1=/home/pi/H4firmware/H4.ino.d1_mini.bin string L=38"
4/3/2020, 11:43:06 PMnode: Works OK
function : (warn)
"f2=/home/pi/H4firmware/H4.ino.di_mini.bin string L=38"
4/3/2020, 11:43:06 PMnode: Works OK
function : (warn)
true
4/3/2020, 11:43:06 PMnode: Works OK
function : (warn)
false

Result with bin2 assignment overriding value set inside switch

4/3/2020, 11:49:06 PMnode: Works OK
function : (warn)
"perfectly normal"
4/3/2020, 11:49:06 PMnode: Works OK
function : (warn)
"f1=/home/pi/H4firmware/H4.ino.d1_mini.bin string L=38"
4/3/2020, 11:49:06 PMnode: Works OK
function : (warn)
"f2=/home/pi/H4firmware/H4.ino.d1_mini.bin string L=38"
4/3/2020, 11:49:06 PMnode: Works OK
function : (warn)
true
4/3/2020, 11:49:06 PMnode: Works OK
function : (warn)
true

Please tell us about your environment:

[v1.0.0 ] Node-RED version:
[ ] Node.js version:
[ ] npm version:
[ ] Platform/OS:
[ ] Browser: Google Chrome Version 80.0.3987.149 (Official Build) (64-bit) on Windows7

Try this one:
let repo='/home/pi/H4firmware'
let hardcoded='/home/pi/H4firmware/H4.ino.d1_mini.bin'
let bin1
let bin2
let typee='WEMOS_D1MINI'
bin1='d1_mini'
switch(typee){
    case 'WEMOS_D1MINI':
        bin2='d1_mini';
        break;
}
//bin2='d1_mini' // comment out this line and msg is '...nuts'
let f1=`${repo}/H4.ino.${bin1}.bin`
let f2=`${repo}/H4.ino.${bin2}.bin`
if(f1!==f2) node.warn('completeley nuts')
else node.warn('perfectly normal')
node.warn('f1='+f1+' '+typeof f1+' L='+f1.length)
node.warn('f2='+f2+' '+typeof f2+' L='+f2.length)
node.warn(f1===hardcoded) // true OF COURSE!
node.warn(f2===hardcoded) // false ???

return msg;

@tmdoit  can you say what is different about the code you have posted - save us having to do a line by line diff to see what you've changed.

I fear this i me going blind....and being stupid...

OMG. So embarassed. Sorry to waste your time people. My terrible eyesight.

And thanks @tmdoit  for his better eyes! :(

@knolleary typo inside switch statement: bin2='di_mini'; > bin2='d1_mini';


Update LFE Examples

Lots has changed in LFE since some (many? all?) of the examples were added; I'd like to do a round of clean-up, update the syntax, docstrings, etc.
Tasks:

[x] Update (: m f a) usage to (m:f a)
[x] Apply formatting consistently
[x] Examine usage instructions and check that they still work
[x] Add usage instructions for any that don't currently work

Okay, tasks are done, PR is submitted, and this is ready for review!


Add support for CANable USB to CAN interface

I thought this would be a good place to post an an official 'TODO' for adding support for a USB to CAN adapter, such as the CANable Pro, which can be purchased online (Aliexpress) for 10 USD or so. This is the only thing keeping me (and likely many others) from using this wonderful piece of software.

This task currently in progress 👍

will something like this also be supported?
https://www.inno-maker.com/product/usb-can/

Hi @andrey-pr ,
I have bought a CAnable usb.
I see you have already created the branch canable, are there any things to keep in mind. Or can this branch be tested? (I have a Bafang m200).

Sorry, development of canable driver is paused. Branch "canable" is currently absolutely unusable

Thanks for the reply.
I received my CANable-usb today, so I was keen to setting it up before seeing your comment.
I have merged the master branch into the canable branch and did a ton of tinkering with the canable class.
I have finally managed to receive can data and make it show-up in the UI.
Tomorrow I will look into sending data onto the can-bus. I hope this fixes a lot of fields being empty in the UI.
(As you can see some of the fields are still empty: https://imgur.com/a/LcdiD5D )

Hi @andrey-pr ,
I could use your help a little bit since I think you have already looked at this problem.
I'm having trouble collecting the serial-numbers & hw / software version.
I do receive some data on the can bus when said data is requested, but looking at the length of the data, it seems I am still missing some data?
(it is not even close to the demo data)
I do think it has something to do with the MULTIFRAME_START = 0x04 of the CanOperationCode
Do I need to ACK the data or something?
I hope you can help me.
This is the received data:
Hardware version (3):
{canCommandCode: 96, canCommandSubCode: 0, canOperationCode: 4, sourceDeviceCode: 4, targetDeviceCode: 5, data: [3]}
Firmware version (4):
{canCommandCode: 96, canCommandSubCode: 1, canOperationCode: 4, sourceDeviceCode: 4, targetDeviceCode: 5, data: [4]}
model(32):
{canCommandCode: 96, canCommandSubCode: 2, canOperationCode: 4, sourceDeviceCode: 4, targetDeviceCode: 5, data: [32]}

Hi @andrey-pr ,
I could use your help a little bit since I think you have already looked at this problem. I'm having trouble collecting the serial-numbers & hw / software version.
I do receive some data on the can bus when said data is requested, but looking at the length of the data, it seems I am still missing some data? (it is not even close to the demo data)
I do think it has something to do with the MULTIFRAME_START = 0x04 of the CanOperationCode Do I need to ACK the data or something? I hope you can help me.
This is the received data: Hardware version (3): {canCommandCode: 96, canCommandSubCode: 0, canOperationCode: 4, sourceDeviceCode: 4, targetDeviceCode: 5, data: [3]}  Firmware version (4): {canCommandCode: 96, canCommandSubCode: 1, canOperationCode: 4, sourceDeviceCode: 4, targetDeviceCode: 5, data: [4]}  model(32): {canCommandCode: 96, canCommandSubCode: 2, canOperationCode: 4, sourceDeviceCode: 4, targetDeviceCode: 5, data: [32]}

This kind of parameters (version names, etc) transported several frames per parameter. One frame have limited length and this parameters are longer, so the first frame will be returned as MULTIFRAME_START, then several with MULTIFRAME, then MULTIFRAME_END and after each one you need to answer with NORMAL_ACK. Code that processes this frames is located in   device/besst/besst.ts file, but its not stable enough

Thanks for explaining the process.
I have created a generic can frame handler class, but those multiframes are all-over the place. (some targets need an ACK before sending the middle/end frame. And some targets will just send you all the multi-frames.)
I also had an issue where receiving different subcommands from the same target would just send the reply of 3 data points in a single sequence, so this required me to add a check if the message is complete at every received multiframe command.
The first mutliframe message contains the bytes' length of the incoming message. I have used this as much as possible to try and repair the received frames. When an ending frame is received, the buffer is always cleared. Broken frames are discarded, but it seems to be pretty stable now.
What seems to make the multiframes wayyy more reliable is adding a timeout between sending multiframe requests. (I have added 200ms * (SubCode % 5) for all requests to Code 60)
I do still seem to be missing some data, but maybe that is my Bafang M200 (Veloretti) not having those data points.
Do you have Canable device and time to test if it is the code or my engine that is causing the data to be unavailable?
Eg. when clicked the refresh button on the engine page I see 2 parameters(conParams_1 & conParams_2) not loaded:
https://imgur.com/a/bcTcryd


Feature request to find untagged files

Just like it finds unliked files, It would be great for this plugin to find untagged files, where every file without even one tag is listed. This will be helpful to tag files later.

Available in new release.


Cannot find module '../build/Release/sharp-{platformAndArch}.node on typescript project

Possible install-time or require-time problem

[x] I have read the documentation relating to installation.
[ ] I have ensured that the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime.

Are you using the latest version of sharp?

[x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest, please open an issue against that package instead.
Is this a problem with filesystem permissions? NO
If you are using npm v6 or earlier and installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?
If you are using npm v7 or later, does the user running npm install own the directory it is run in?
If you are using the ignore-scripts feature of npm, have you tried with the npm install --ignore-scripts=false flag?
What is the complete output of running npm install --verbose sharp?

Too Long, but no visible error during this step.

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
System:
OS: macOS 12.2
CPU: (8) x64 Apple M1
Memory: 35.98 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.19.0 - ~/.nvm/versions/node/v14.19.0/bin/node
Yarn: 1.22.17 - ~/.nvm/versions/node/v14.19.0/bin/yarn
npm: 6.14.16 - ~/.nvm/versions/node/v14.19.0/bin/npm
npmPackages:
sharp: ^0.30.2 => 0.30.2
Suspicions and additional context
I do understand the platform and arch are different but sharp is clever enough to detect the platform and install the appropriate pre-built binaries. In addition, the installation process is restarted on the lambda.
Lastly, this error is only occuring at runtime. Project is setup to use typescript. I have tried using different kinds of imports like require('sharp'), import {sharp} from 'sharp', import * as sharp from 'sharp' and import sharp from 'sharp' as in other issues but with no luck.
Error on lambda function

@lovell does this library currently support typescript? I dove deep into the documentation but could not find how to use it with typescript. This image shows the error I was encountering both on my local on Mac and on AWS lambda. Please assist.
Error on M1 showing the file actually exists

Hi, did you see https://sharp.pixelplumbing.com/install#aws-lambda ?

Hello, yes I checked it out. However I am not deploying with a zip file with node_modules. It is being deployed via a code pipeline. I think if I am able to solve for my local dev, it should be able to solve for the lambda.

Are you populating node_modules using Code Pipeline? If so, what is the output of npm install sharp --verbose when run on Code Pipeline?

Yes, all that is taken care of when the serverless lambdas are deployed. Looking more critically at the problem at my local with fewer variables, I think its relates to typescript and esbuild that is bundling the project files. I saw some mention of externals in other related issues but this is now beyond my understanding, but I suspect the challenge lies around there.

I've just added a section to the docs (not published yet) about use with esbuild - see https://github.com/lovell/sharp/blob/main/docs/install.md#esbuild

Thank you, this pins down the challenge I was having. Thank you for your amazing library!

I hope this information helped. Please feel free to re-open with more details if further assistance is required.

For AWS lambda deployment with Sharp module, the following worked for me when using serverless, esbuild and serverless-esbuild. Changed the serverless.yml file with the below configuration. It is basically telling esbuild to download sharp again with the following --arch=x64 --platform=linux considering your lambda uses x64 arch. Check serverless-esbuild packager and packagerOptions options for more understanding.
esbuild:
    # keep existing configurations
    external:
      - sharp
    packagerOptions:
      scripts:
        - npm install --arch=x64 --platform=linux sharp

@SayefReyadh thank you very much this makes sense. Thank you for the added explanation of what is going on. Out of interest, how did you get to that solution?

@chris-kck similar implementations were done for serverless-webpack and discussed in #2230

I am having issues making sharp work on aws lambda (with cdk) and esbuild. I am creating one .js file via esbuild and then deploy my lambda function via cdk with that one .js file (instead of using a zip folder).
When I run my lambda function I get this error:
{
    "errorType": "Error",
    "errorMessage": "\nSomething went wrong installing the \"sharp\" module\n\nCannot find module '../build/Release/sharp-linux-x64.node'\nRequire stack:\n- /var/task/processMarketingFile.js\n- /var/runtime/UserFunction.js\n- /var/runtime/Runtime.js\n- /var/runtime/index.js\n\nPossible solutions:\n- Install with verbose logging and look for errors: \"npm install --ignore-scripts=false --foreground-scripts --verbose sharp\"\n- Install for the current linux-x64 runtime: \"npm install --platform=linux --arch=x64 sharp\"\n- Consult the installation documentation: https://sharp.pixelplumbing.com/install",
    "stack": [
        "Error: ",
        "Something went wrong installing the \"sharp\" module",
        "",
        "Cannot find module '../build/Release/sharp-linux-x64.node'",
        "Require stack:",
        "- /var/task/processMarketingFile.js",
        "- /var/runtime/UserFunction.js",
        "- /var/runtime/Runtime.js",
        "- /var/runtime/index.js",
        "",
        "Possible solutions:",
        "- Install with verbose logging and look for errors: \"npm install --ignore-scripts=false --foreground-scripts --verbose sharp\"",
        "- Install for the current linux-x64 runtime: \"npm install --platform=linux --arch=x64 sharp\"",
        "- Consult the installation documentation: https://sharp.pixelplumbing.com/install",
        "    at /var/task/processMarketingFile.js:82:67968",
        "    at /var/task/processMarketingFile.js:1:222",
        "    at /var/task/processMarketingFile.js:83:121",
        "    at /var/task/processMarketingFile.js:1:222",
        "    at /var/task/processMarketingFile.js:83:63844",
        "    at /var/task/processMarketingFile.js:1:222",
        "    at Object.<anonymous> (/var/task/processMarketingFile.js:90:16737)",
        "    at Module._compile (internal/modules/cjs/loader.js:1085:14)",
        "    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)",
        "    at Module.load (internal/modules/cjs/loader.js:950:32)"
    ]
}

I have read the installation guidelines on lambda and esbuild but I don't think that makes sense here. I need to have the sharp package present in the lambda context if I should exclude it in esbuild (which I am doing with the aws-sdk package). But how do I then get it to be present in my lambda?
If I follow the lambda instructions on the other hand it also doesn't work and I get the above error.
Any hints for me on this one?

@flosky I have faced similar issues while deploying with esbuild and serverless framework, I am not sure if aws cdk supports YAML, do consider trying having a look at our existing discussion in this PR #3235

@SayefReyadh Thanks for the hint. As far as I can see the mentioned PR is not relevant here. The cdk setup with esbuild seems to be different from serverless.
I managed to get it to work which also made me realized what is missing. Since we have to mark sharp as external dependency with esbuild, we have to make sure the lib the present in the lambda function. For this I had to change the Lambda setup in cdk from using a single js file (which was the whole point for using esbuild) to create an S3 asset with all the files (including the node_modules).
In the end I did a hybrid version. I created the single js file bundle with esbuild but excluded sharp and then added another package.json that only has sharp as dependency to create a node_modules only with sharp and its dependencies (I then also had to run the code that installs sharp for the right target architecture) and upload all of that to S3 as my Lambda code.
Not a great solution, I think. Ideally I would like to just use esbuild without marking sharp as external but I guess that is not possible due to the compiled source files. Another option would be to offer a lambda layer with sharp and all it's dependencies installed. I saw that people created this but it wasn't very well maintained. Would be better to offer this from the main maintainer.

@SayefReyadh I found a good solution that should be added to the sharp docs, I think.
You can set this up quite easily by using the NodejsFunction from aws-cdk-lib/aws-lambda-nodejs. It has esbuild as bundler built in and allows for some useful bundling configurations, which help in this case:

You can tell the bundler to keep certain packages in their node_modules file and not bundle them into the final .js file
You can force the bundler to always run inside a docker container which aligns with the target architecture. So no need to additionally call SHARP_IGNORE_GLOBAL_LIBVIPS=1 npm install --arch= arm64 --platform=linux --libc=glibc sharp. I tested it with setting the Lambda architecture to Architecture.ARM_64 and it worked

Just as a reminder, this is for cdk Lambda projects using sharp

NodejsFunction

Thanks, appreciated the update.


add $HOME/.ssh/config to support other ports and account on other systems

add $HOME/.ssh/config
#
Host example.com
    Port 1234
Host server1
    HostName server1.cyberciti.biz
    User nixcraft
    Port 4242
    IdentityFile /nfs/shared/users/nixcraft/keys/server1/id_rsa
Host nas01
    HostName <IP_ADDRESS>
    User root
    IdentityFile ~/.ssh/nas01.key

examples:
https://www.cyberciti.biz/faq/create-ssh-config-file-on-linux-unix/
https://dev.to/hoelzro/ssh-shortcuts-13l9

vi $HOME/.ssh/config
#       ~/.ssh/config
###
Host one
   HostName one-rpi3b.cptx86.com
   User uadmin
   Port 22

commands
ssh-copy-id one
ssh one

scp example:that-important-file.txt .
sftp example
rsync -ar example:my-project/ .
git remote add example ssh://example/~/my-project
vim scp://example/that-important-file.txt

try this
Host *.yourdomain.com
User joe


⚠ Bofrost.at has degraded performance

In 993ed45, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1654 ms

Resolved: Bofrost.at performance has improved in 0514309 after 6 minutes.


[CI/Build] Move test_utils.py to tests/utils.py

Since #4335 was merged, I've noticed that the definition of ServerRunner in the tests is the same as in the test for OpenAI API. I have moved the class to the test utilities to avoid code duplication. (Although it only has been repeated twice so far, I will add another similar test suite in #4200 which would duplicate the code a third time)
Also, I have moved the test utilities file (test_utils.py) to under the test directory (tests/utils.py), since none of its code is actually used in the main package. Note that I have added __init__.py to each test subpackage and updated the ray.init() call in the test utilities file in order to relative import tests/utils.py.

I'm not that familiar with how the nccl library is handled in vLLM. How would using relative imports cause the library to not be loaded?

I think it should be OK now.

@rkooo567 did you forget to merge this?

oops. sorry .can you resolve the merge conflict?

oops. sorry .can you resolve the merge conflict?

See if this passes

Apart from the AMD tests failing due to out of storage space and kernels-test-3 being canceled, the tests have passed.

amd failure seems unrelated. cc @simon-mo I am merging this

It's a little bit late but I find pytorch also has some testing code in the main library https://github.com/pytorch/pytorch/tree/main/torch/testing . Maybe we need to discuss it. Relative import used in this PR is quite fragile .

Hmm is there a way to just exclude it in actual wheel?

Hmm is there a way to just exclude it in actual wheel?

Not sure. But why do we care about this anyway? It's just a single python file with dozens of lines.

Relative import used in this PR is quite fragile.

By this, do you mean that it breaks calling pytest from inner directories? I think this is not necessarily tied to the location of utils. The reason why I moved it to tests directory is to avoid accidentally making test-only dependencies required for the user.
If we want to reinstate this functionality while keeping utilities in the tests directory, we can import the utilities by import tests.utils rather than the original import vllm.testing_utils. Prior to this PR, some test code already referred to the root conftest in a similar manner (import tests.conftest).


gerrit: no syntax highlighting of go files

I cannot select "Go" as language in the diff preferences hence there is no syntax highlighting of Go files on https://go-review.googlesource.com/

I think you need to file an issue at https://code.google.com/p/gerrit/ instead.

When I open the create issue mask there i get the following notice:
***** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!!
*****                                                       *****
*****   THOSE ISSUES BELONG IN DIFFERENT ISSUE TRACKERS     *****

Who is the master Go's gerrit instance?

You should still file the bug report with gerrit, as they have intentionally
disabled Go syntax highlighting in 3 months agao:
https://gerrit-review.googlesource.com/#/c/60690/

I filled an issue here https://code.google.com/p/gerrit/issues/detail?id=3106 and keep you up to date with this issue.


Fix NL right-outer join error handling

It got stuck when the right upstream called fail.
testRightJoinRightUpstreamFails triggered the bug. The other two test
cases are just for the sake of completness.

@seut please review

Current coverage is 81.39% (diff: 100%)

Merging #4461 into 0.57 will increase coverage by 0.07%

@@               0.57      #4461   diff @@
==========================================
  Files          1311       1311
  Lines         44714      44714
  Methods           0          0
  Messages          0          0
  Branches       7126       7126
==========================================
+ Hits          36364      36397    +33
+ Misses         5659       5635    -24
+ Partials       2691       2682     -9

Powered by Codecov. Last update ffabd1d...4606505


Changing 'guys' to 'people'

Tiny doc change here!
Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Folks at Ubuntu aren't all male so calling them 'guys' is a little odd. This updates the README to change the word 'guys' to 'people'.

Isn't guys gender neutral?

Isn't guys gender neutral?

It sometimes is, which means it can be tricky. Most of the time it won't cause a problem but sometimes a woman will read it and feel left out. Avoiding using it when it's not necessary is a great way to prevent that moment of a woman thinking "Oh, I guess this isn't a place for me. I'll go somewhere else."  It's a little thing but I figure if it's easy to fix, maybe it's worth it?

Isn't guys gender neutral?

Yes, it is..
Exception: people desperately looking to be offended.

Exception: people desperately looking to be offended.

@Hrxn I'm sure you're a good person and you don't mean to be rude or hurtful. If you'd like to talk about this in person I'd be happy to do a Google Hangout and we can discuss it. I'd love to hear your perspective.

This is a joke, right?

@Hrxn Absolutely not. I think using gender-inclusive language is a real issue and you think it's not. We could respectfully talk it through like two humans who work in the same industry and will likely run into each other from time to time in the software community. That's a more mature response than just yelling insults at each other, yeah?


TypeScript 2.5 "unused type parameter" breaks existing code

TypeScript Version:  2.5.2
Code
type Foo<s> = object;

This worked fine in TypeScript 2.4, but causes the following error in 2.5.2:
error TS6133: 's' is declared but never used.

This change in TypeScript is breaking massive amounts of code that use phantom type parameters. And there doesn't seem to be any workaround.

You can turn off no unused variables, or name them with a leading underscore (Foo<_s> will not cause an error).

I tried adding a leading underscore:
type Foo<_s> = object;

Still causes the same error ('s' is declared but never used.)
Switching off noUnusedLocals does work, but at the great expense of loosing that feature

I'm interested in what you use phantom type parameters for, as they are not enforced by the compiler. If a type parameter is not referenced in the type's body, it's not considered during checking.

I'm interested in what you use phantom type parameters for, as they are not enforced by the compiler. If a type parameter is not referenced in the type's body, it's not considered during checking.

You are right, it turns out that the code in the style above was actually from some older experiments with phantom types, that we don't actually use.
The way we actually use phantom types with correct type checking is by adding a dummy field:
export class Q<s> {
    protected dummy: [Q<s>, s];
}

Logged  #18420


Update 'puppetlabs/stdlib' to 4.5.0

The latest version of Puppet's standard library is 4.5.0. The changelog can be
seen at https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/CHANGELOG.md

@rjw1 @samjsharpe @dcarley 4.2ified.


fix(autocomplete): Fix unused defaultValue prop

The defaultValue prop was not being used, which resulted in it not
working.
Closes #244
PR Checklist
This PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] A changelog entry has been added to CHANGELOG.md if necessary

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] react application / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?
defaultValue prop on the Autocomplete component does nothing.
Issue Number: #244
What is the new behavior?
defaultValue prop on the Autocomplete component iis taken into account.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
Resolved issues
Fixes: #244

This isn't the right way to fix the underlying problem. See the discussion on #244. Closing this PR.


How to rewrite labels

Hi,
I want to change some labels and the name of metrics. I followed the VictoriaDB guide and setup a relabel config. Now I'm struggling with where to place the relabel config.
Does this work at all, when using the influx integration?
For completeness, I want to apply following config:

source_labels: [name]
regex: 'sensor..plant_sensor(.)_value'
replacement: '$1'
target_label: plant_id
source_labels: [name]
regex: 'sensor.(.)plant_sensor._value'
replacement: '$1'
target_label: sensor_type
source_labels: [name]
regex: 'sensor..plant_sensor._value'
replacement: sensor.plant_sensor
target_label: name

It took me a while to figure out it need to add it to the scrape configuration in prometheus.tpl. (Never used victoriadb/prometheus before)
Is there a recommended way to replace the configuration?
As far as I can see, this might be related to Map the Home Assistant config directory to the add-on container, although I don't care about the location of the configuration file, as long as I can change it ;)

It took me a while to figure out it need to add it to the scrape configuration in prometheus.tpl. (Never used victoriadb/prometheus before)
Is there a recommended way to replace the configuration? As far as I can see, this might be related to Map the Home Assistant config directory to the add-on container, although I don't care about the location of the configuration file, as long as I can change it ;)

Hey @andyfr,
we have a great coockbook about relabeling. You can do some opactice at

@denisgolius Thanx for your help!


[MINOR][DOC] spark.executor.memoryOverhead is not cluster-mode only

What changes were proposed in this pull request?

Remove "in cluster mode" from the description of spark.executor.memoryOverhead
Why are the changes needed?

fix correctness issue in documentaion
Does this PR introduce any user-facing change?

yes, users may not get confused about the description spark.executor.memoryOverhead
How was this patch tested?

pass GA doc generation

Test build #130847 has started for PR 30311 at commit 3aa18e8.

Test build #130847 has finished for PR 30311 at commit 3aa18e8.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130847/
Test FAILed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35455/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35455/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35455/
Test PASSed.

retest this please

Test build #130872 has started for PR 30311 at commit 3aa18e8.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35479/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35479/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35479/
Test PASSed.

Test build #130872 has finished for PR 30311 at commit 3aa18e8.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130872/
Test FAILed.

retest this please

Test build #130899 has started for PR 30311 at commit 3aa18e8.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35505/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/35505/

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/35505/
Test PASSed.

Test build #130899 has finished for PR 30311 at commit 3aa18e8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/130899/
Test PASSed.

cc @cloud-fan @maropu too~

Thanks! Merged to master/branch-3.0. Could you open a PR to backport this into branch-2.4?

yea, thanks for merging

@maropu the description for spark.executor.memoryOverhead is fine in http://spark.apache.org/docs/2.4.7/configuration.html. Then it is not that necessary to backport this although it's wrong in the code.


Craft 4? Or is this plugin dead?

Haven't seen a release since late 2019, so I'm wondering if this plugin is still in active development? If so, will there be a Craft 4 compatible version?

Hey @angieherrera, mind sharing your thoughts on this discussion, please? Thank you!


Add StaggeredGridView Widget

Proposal
Expose "natively" the flutter_staggered_grid_view package.
Reason
Unfortunately this package seems to not be maintained anymore according to the numerous issues inside without feedback from the owner, despite the 1K+ rating...
The library simply does not support lazy loading and it is leading to out of memory errors and crashes.
I am refering to this issue
So it would be awesome to have a StaggeredGridView widget that has no performances issues, that means being usable.
Thanks !

@Tom3652
There's a similar open issue describing your case, https://github.com/flutter/flutter/issues/40856
Please follow-up there for updates.
Closing this as duplicate.
Also, notifying @letsar on this issue related to the plugin performance.


Connecting to containers outside my network

I'm currently using this docker to connect a few other containers to the internet through my VPN using network-container=pia.. one of which happens to be linuxserver/rutorrent. In my rutorrent container i get an error that a port is closed.  I've forwarded the port correctly within my pia container, and i've even forwarded traffic on my router to my servers local ip. am i missing something?

You will need to portforward it on the PIA side, you don't need to do anything on your router. The forwarded port is random and will be displayed in the logs, provided you set PORT_FORWARDING=true. The IP address will be the one you have on the PIA server side.
I personally do not need port forwarding for any of my apps so I can't speak of experience however.

hey @qdm12 - thanks for the reply.. and sorry for not responding since but i've been out of town. i currently have PORT_FORWARDING=true set, but i don't see any information about the ports in my startup log


use reduce to allow select operators to take muti args

For 6 of the operators (+ - / * & |) it makes sense to use reduce to allow for greater than 2 args.
The need comes from rio calc usage; instead of requiring deeply-nested expressions for e.g. reading four rasters and taking their sum
rio calc "(+ (+ (+ (read 1) (read 2)) (read 3)) (read 4))"

We can express it as
rio calc "(+ (read 1) (read 2) (read 3) (read 4))

Coverage decreased (-0.9%) to 99.074% when pulling d91d4eb177a8510ab689463812c1b9afe8a1106b on multi-args into da0c30de9f64801eaeec96f0cbfd57ae35522bab on master.

@sgillies What do you think about the idea and implementation here?

Coverage remained the same at 99.074% when pulling 2ced778be6ab6c539c3b47d8e0db65b382e150ec on multi-args into 81bb721e14f9319bb6d3ffd192cb8a0871bdb312 on master.

@perrygeo this is great. 👍  👍


Perf issue with c-ares DNS resolver

Hi 👋
Title: Perf issue with c-ares DNS resolver
Description:
The c-ares DNS resolver calls getifaddrs syscall. getifaddrs can be slow or CPU intensive (example https://github.com/envoyproxy/envoy/issues/19717). If Envoy has many DNS clusters, the performance hit can be considerable.
Repro steps:
This issue happened for us with the following scenario:

A server runs latest Envoy version
The server has 700+ network namespaces
XDS server tries to push between 500 and 2k DNS clusters onto Envoy

As a result, after connecting to the XDS server, the main thread is saturated initializing c-ares DNS resolvers. For us, it causes high CPU usage and disconnection-reconnection loops to the XDS server, probably because the main thread is busy listing interfaces instead of responding to keep-alives.
Root cause:
Because there are many network namespaces on our server, getifaddrs is CPU intensive.

It seems that c-ares DNS resolver lists the network interfaces of the machine to satisfy filter_unroutable_families https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/network/dns_resolver/cares/v3/cares_dns_resolver.proto#extensions-network-dns-resolver-cares-v3-caresdnsresolverconfig:

(bool) The resolver will query available network interfaces and determine if there are no available interfaces for a given IP family. It will then filter these addresses from the results it presents. e.g., if there are no available IPv4 network interfaces, the resolver will not provide IPv4 addresses.

Suggestion:
No matter the value of filter_unroutable_families, interfaces are listed anyway. I would suggest to:

Either only list interfaces whenever filter_unroutable_families is true (early return here https://github.com/envoyproxy/envoy/blob/main/source/extensions/network/dns_resolver/cares/dns_impl.cc#L508)
Or only list interfaces once and re-use the result across different DNS resolvers

Other ideas welcome. I'm happy to provide a PR too

cced @yanavlasov and @mattklein123  based on  cares CODEOWNER
Also cced @yanjunxiang-google worked on this area in the past

@nicoche Can these options you mentioned relieve the issue?

@yanjunxiang-google I think so.
We built Envoy with a patch that returns {true, true} line 508. It runs since a few days in production and fixed our issue. It would be similar to making sure that getifaddrs is ran only when filter_unroutable_families=true.
I don't know about the other suggestion, but pretty sure it would work too.
If you want to reproduce the issue, I was able to do so locally:

Setup:

1000 net namespaces and a veth plugged on each one => running getifaddrs takes about 100ms, which is similar to what we witnessed
2000 envoy DNS clusters

I can share the scripts to setup that, if you want.
When I use the latest dev image, it takes about 50 seconds to initialize DNS clusters. One of the CPU of the machine is at 100% when I check htop:
$ sudo docker run --network=host -v $(pwd)/envoy.yaml:/envoy.yaml --rm envoyproxy/envoy:dev -c /envoy.yaml
(...)
[2024-06-23 23:32:49.603][1][info][admin] [source/server/admin/admin.cc:65] admin address: <IP_ADDRESS>:9901
[2024-06-23 23:32:49.603][1][info][config] [source/server/configuration_impl.cc:168] loading tracing configuration
[2024-06-23 23:32:49.603][1][info][config] [source/server/configuration_impl.cc:124] loading 0 static secret(s)
[2024-06-23 23:32:49.603][1][info][config] [source/server/configuration_impl.cc:130] loading 2000 cluster(s)
[2024-06-23 23:33:36.851][1][info][config] [source/server/configuration_impl.cc:138] loading 1 listener(s)
[2024-06-23 23:33:36.854][1][info][config] [source/server/configuration_impl.cc:154] loading stats configuration
[2024-06-23 23:33:36.854][1][info][runtime] [source/common/runtime/runtime_impl.cc:625] RTDS has finished initialization
[2024-06-23 23:33:36.854][1][info][upstream] [source/common/upstream/cluster_manager_impl.cc:240] cm init: all clusters initialized

When I use the our patch, it loads in 2 seconds:
$ sudo docker run --network=host -v $(pwd)/envoy.yaml:/envoy.yaml --rm xxx/envoy_patched:v1 -c /envoy.yaml
[2024-06-23 23:43:37.880][1][info][admin] [source/server/admin/admin.cc:65] admin address: <IP_ADDRESS>:9901
[2024-06-23 23:43:37.881][1][info][config] [source/server/configuration_impl.cc:168] loading tracing configuration
[2024-06-23 23:43:37.881][1][info][config] [source/server/configuration_impl.cc:124] loading 0 static secret(s)
[2024-06-23 23:43:37.881][1][info][config] [source/server/configuration_impl.cc:130] loading 2000 cluster(s)
[2024-06-23 23:43:39.253][1][info][config] [source/server/configuration_impl.cc:138] loading 1 listener(s)
[2024-06-23 23:43:39.255][1][info][config] [source/server/configuration_impl.cc:154] loading stats configuration
[2024-06-23 23:43:39.256][1][info][runtime] [source/common/runtime/runtime_impl.cc:625] RTDS has finished initialization
[2024-06-23 23:43:39.256][1][info][upstream] [source/common/upstream/cluster_manager_impl.cc:240] cm init: all clusters initialized

Setting filter_unroutable_families to true or false does not change anything.

Hey 👋
Is there anything I can do to help move this forward? I would really love to see a fix in the next release. Once again, given a direction, I'm happy to provide a PR. I think that

Only list interfaces whenever filter_unroutable_families is true (early return here https://github.com/envoyproxy/envoy/blob/main/source/extensions/network/dns_resolver/cares/dns_impl.cc#L508)

is the simplest fix.

Hey,
I'm commenting to prevent this issue from going stale. Is there anything else I can do to help?

HI, @nicoche
Could you please send out a PR for your solution on this?
Thanks for contributing!

Sure thing, I'll push something soon 🙂

not stale, I still want to push that change
It's a one line change, but it breaks some tests and I struggle with the toolchain, so it's a longer task than I thought 😢. I haven't dedicated the time to that yet, sorry!


Incorrect handling of ObjectId fields with lua scripts

Environment

VerneMQ Version: 1.11.0
OS: Debian 10 (buster)
Erlang/OTP version (if building from source): 22
VerneMQ configuration (vernemq.conf) or the changes from the default
Cluster size/standalone: any

Expected behaviour
Calling mongodb.find_one returns document with ObjectId fields. At example userId: ObjectId('5ec51288ace1c90a347fb4a4')
Actual behaviour
2020-11-25 12:26:17.572 [error] <0.455.0>@vmq_diversity_script_state:handle_info:177 can't call function auth_on_register with args [{addr,<<"<IP_ADDRESS>">>},{port,47156},{mountpoint,<<>>},{client_id,<<"service5d0f1c5a">>},{username,<<"service:100">>},{password,<<>>},{clean_session,true}] in "/etc/vernemq/scripts/auth_tp.lua" due to {error,badarg}
In source vmq_diversity/src/vmq_diversity_mongo.erl  I found processing of document _id field by function check_ids. But it not processes other ObjectId fields!
Field mapping and unmapping done by vmq_diversity_utils:map and vmq_diversity_utils:unmap. Why ObjectId fields not processed in this functions?
Also need function to create value with ObjectId type from string in lua script.

@mtaobiz thanks, I'm not sure what you are looking to achieve or how I can help. You might want to check the format of auth_on_register arguments in your script.

script is simple:
function auth_on_register(reg)
log.debug("auth wp1")

local svc = mongodb.find_one(pool, "svcs", {
    id = 136
})

log.debug("auth wp2")

return true

end
and error is:
2020-11-25 15:23:06.361 [debug] <0.483.0>@vmq_diversity_lager:debug:41 auth wp1
2020-11-25 15:23:06.362 [error] <0.483.0>@vmq_diversity_script_state:handle_info:177 can't call function auth_on_register with args [{addr,<<"<IP_ADDRESS>
">>},{port,49322},{mountpoint,<<>>},{client_id,<<"servicee1cf29b5">>},{username,<<"service:9">>},{password,<<>>},{clean_session,true}] in "/etc/verne
mq/scripts/auth_tp.lua" due to {error,badarg}
svcs contains this doc:
{
"_id" : ObjectId("5f6b45ed5362be63fa8ed962"),
"id" : 136,
"type" : "account",
"userId" : ObjectId("5f6b45ed5362be63fa8ed960"),
"access" : "userservice",
"server" : "sandbox",
"active" : true,
"created" : ISODate("2020-09-23T15:56:13.477+03:00")
}
without userId all works fine

@mtaobiz have you been able to find out more here? maybe related to https://github.com/vernemq/vernemq/issues/1678 also?

No its not about this issue. Im already done patch to use ObjectId field needed for my project. But Im badly know Erland and can`t make universal solution.
Please check my lua-script with document from comment above.


Failed to parse JSON: expected value at line 1 column 1

Whenever I attempt to start the game by using aki.start_game(), I receive the following error message: Failed to parse JSON: expected value at line 1 column 1. This issue also persists when running the tests provided in this repository.
The complete error message is as follows:
Exception has occurred: ValueError
Failed to parse JSON: expected value at line 1 column 1
  File "H:\Sayoka\extensions\tmp.py", line 17, in test
    first_question = aki.start_game()
                     ^^^^^^^^^^^^^^^^
  File "H:\Sayoka\extensions\tmp.py", line 53, in <module>
    test()
ValueError: Failed to parse JSON: expected value at line 1 column 1

(This error occurs when running the test_sync.py file available in the akinator.py repository.)

@kollhdxdlp and also @Jonak-Adipta-Kalita, fixed that issue, it was a regex problem, it worked before I do not know why it stopped working now, but it should work now.
Update to newest version on PYPI (v0.2.2) and try again, thanks!

@kollhdxdlp and also @Jonak-Adipta-Kalita, fixed that issue, it was a regex problem, it worked before I do not know why it stopped working now, but it should work now.
Update to newest version on PYPI (v0.2.2) and try again, thanks!

Alright 👍


dragon antag refactor

About the PR
made dragon use antag refactor stuff and remove all mention of GenericAntag
depends on #28216
Why / Balance
copypasta bad
Technical details

added AntagRandomSpawn for rules to create antag spawners at random tiles on a station
added AntagSpawner for rules to shrimply spawn a mob for the spawned entity
dont know if this is already possible somehow but whatever

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes
MobDragon isnt in the spawn menu anymore because it wouldnt have the role or objectives. just addgamerule DragonSpawn instead
Changelog
no cl no fun

Consider that admins might want to spawn a dragon specifically for being a dragon, without the game rules.
Like a John Nanotrasen visit to the station or something

Consider that admins might want to spawn a dragon specifically for being a dragon, without the game rules. Like a John Nanotrasen visit to the station or something

For the second purpose a custom prototype is uploaded anyways, but being able to just spawn a mob dragon anywhere would be appreciated in some cases

does this fix dragon devour bug

no see dead dragon rework pr


Determine Tech Stacks

User Story: As a Developer, I would like to determine which tech stacks to use so that I can start building my application.
Acceptance Criteria:

Tech Stacks should be for Front-End and Back-End
Tech Stacks should be based off of need for client and current career interests

Front-End:

React.Js
Next.Js
Jest

Back-End:

Spring
Java
Mongo/Mongoose


Where did you find the .h5 weights file?

Is the .h5 weights file downloaded from somewhere else? Or did you train your weights?
For example in model.py
weights_path = os.path.expanduser(os.path.join('~', '.keras/models/fcn_vgg16_weights_tf_dim_ordering_tf_kernels.h5'))
model.load_weights(weights_path, by_name=True)
return model

Based on the file path .keras/, it looks like a weights file come from Keras. But I am not aware of that keras provides fcn weights.

you can review the utils/get_weights_path.py  and utils/transfer_FCN.py

If I understand it correctly,
TF_WEIGHTS_PATH = 'https://github.com/fchollet/deep-learning-models/releases/download/v0.1/vgg16_weights_tf_dim_ordering_tf_kernels.h5'

This is only the normal vgg16 weights on ImageNet?
Therefore, there is no transpose convolution layer's weights?

I guess you should read the codes first. The model used Linear Upsample instead of the Deconvolution.

@CreatCodeBuild the new README.md explains what to do
@aurora95 you can close this issue (or maybe consider adding me as a collaborator so I can close it?)

https://github.com/aurora95/Keras-FCN/blob/d923eff053785e919d1099e04a27588e8127b4f6/utils/transfer_FCN.py#L77
Changed this line to if layer.name in index:

@mrgloom can you make a pull request with that?


MPIRun will cause the program to crash

Expected Behavior
That the program continues to execute
Actual Behavior
Program troughs seg fault.
Steps to Reproduce the Behavior
Run the 'run.bash' file with the mpirun line uncommented and the regular './ExoSAI' line commented out.

Problem isn't with the mpi run its with the rand_connection logic. It needs to be revisited.

This has been fixed already.


Please support --recode-video ts or --recode-video mpegts

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.08.18. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.08.18

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Description of your issue, suggested solution and other information
When downloading a video I often need to convert it to a .ts (transport stream) file, which requires an additional step, typically running something like
ffmpeg "original_file.mp4" -c copy "new_file.ts"
Since ffmpeg supports .ts files, it would be handy if the --recode-video option also allowed specifying ts or mpegts as an option.  At present if you try to specify either --recode-video ts or --recode-video mpegts you get "youtube-dl: error: invalid video recode format specified".
What I am requesting may or may not be similar to issue #11498, I didn't fully understand that issue but what I am asking for is a way to re-encode ANY video downloaded from ANY supported site as a .ts file, without having to do an additional separate run of ffmpeg.  Most supported sites don't offer a .ts file natively, so I think the only way to do this would be to recode the file.  You already support recoding to several other formats, so why not .ts?

There is one other thing I have discovered.  When you get the video from some sites it is already in .ts format but sometimes in small chunks that would just need to be combined.  In such cases the .ts file(s) often contain embedded ATSC closed captions that can be displayed with no problem by a standard ATSC television.  However when the .ts files are converted to some other format, the closed captions are either lost, garbled, or converted to a non-embedded format in a separate file (if that option is used), all of which are useless to ATSC television sets.  So having the ability to save files that originate in .ts format as .ts files would be a big help for the hearing-impaired.

So having the ability to save files that originate in .ts format as .ts files would be a big help for the hearing-impaired.

you can use:
--hls-use-mpegts                 Use the mpegts container for HLS videos,
                                 allowing to play the video while
                                 downloading (some players may not be able


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?
Bicep
Module Classification?
Resource Module
Module Name
avm/res/network/front-door-web-application-firewall-policy
Module Details
Front Door WAF Policy, migration from CARML
Do you want to be the owner of this module?
No
Module Owner's GitHub Username (handle)
No response
(Optional) Secondary Module Owner's GitHub Username (handle)
No response

Thank you @krbar! Feel free to get started! ;)

[x] PR merged; Module published. PR: https://github.com/Azure/bicep-registry-modules/pull/772
[x] GitHub teams are available and assigned to their parents.
[x] CODEOWNERS file updated.

Thank you for your work @krbar! I'm closing this issue now.
Since this module was migrated from CARML without an owner, an orphaned module request was also created: https://github.com/Azure/Azure-Verified-Modules/issues/502


Tests require missing images

Several tests (for example, the one in test_estimate_alpha.py) fail because a required image is missing:
FAILED tests/test_estimate_alpha.py::test_alpha - FileNotFoundError: [Errno 2] No such file or directory: 'data/input_training_lowres/GT01.png'
FAILED tests/test_laplacians.py::test_laplacians - FileNotFoundError: [Errno 2] No such file or directory: 'data/input_training_lowres/GT01.png'
FAILED tests/test_lkm.py::test_lkm - FileNotFoundError: [Errno 2] No such file or directory: 'data/input_training_lowres/GT01.png'
FAILED tests/test_preconditioners.py::test_preconditioners - FileNotFoundError: [Errno 2] No such file or directory: 'data/input_training_lowres/GT01.png'

Could/should GT01.png be included?

The images are not included directly for licensing reasons. They can be downloaded by running python3 tests/download_images.py.
See https://github.com/pymatting/pymatting#testing

Oh. Thanks.
Would it be okay to have them downloaded automatically?

For legal reasons it is probably better to not download things unless the user wanted to do so. But I am not a lawyer and law is different all over the world, so who knows.

Yes...
Maybe I'll have pytest issue a warning for people such as myself who miss that line in the readme.

Closed by https://github.com/pymatting/pymatting/pull/89


Simplify camera transformations with the new Frame3d-Feature from RoSys

Since the next RoSys release will fix https://github.com/zauberzeug/rosys/discussions/130, this PR utilizes the new Frame3d to get rid of hacks throughout the codebase. While at it, I fixed some typing issues, made some cleanups and extracted/renamed variables to improve readability and consistency.
NOTE: this branch does only work with the RoSys main line at the moment and should only be merged after RoSys 0.14.0 has been released.
ToDos

[x] fix tests
[ ] test camera card's tool augmentation and relevant weeds augmentation on real robot
[ ] test plant locator is proper functioning on real robot
[ ] review code
[x] wait for RoSys 0.14.0 and update requirements.txt
[ ] Check for old calibration

I fixed the test_follow_crops_outlier test by increasing the error margin from 1° to 2°. The introduction of the Frame3d seems to skew the orientation a bit different than before. To verify that 2° of error is still ok, I added multiple outliers to the follow crops simulation which looks quite good to me.

@pascalzauberzeug or @angelom93: you can review and test the code already (with rosys main branch). That way we could merge as soon as the 0.14.0 version of RoSys get's released.

@rodja I already checked the code, but don't have time to test it on a robot until tuesday
@angelom93 you can test it if you find the time, otherwise I will do it on tuesday

Iiiiiiiioioiioooooooooooooooooooooooooooooooooo iooooooooooooooooooo wir oooooooooooooooooooooooooo wir ooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooo die oooooooooooooooooooooooooo  ooooooooooooooooooooooooooooooooo ooooooooiooooooooooooooooo oooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooo   ich ii   und ooooooooooooooooooooooooooooooooo  ooooooooiooooooooooooooooo die 🎲 Iooooooooöooioo die 🎲 🎲 III oooioooooooooooooooooooooooooooooo oooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooo oooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooo oooooooooooooooooooooooooo ooo ooooo wir oooooooooo o9iioooiiíoIooooooooöooioo ii o o öiioö mi ok KK ku you oiuilöo

I have updated rosys to v0.14.0 and merged main into this branch.
We have to push this forward tomorrow, because https://github.com/zauberzeug/field_friend/pull/149 depends on v0.14.0 and needs this PR for it to work

@rodja @pascalzauberzeug I tried to get this PR working on a real robot. After fixing some issues with the calibration dialog and camera card, I encountered a bigger problem. In line 210 of camera_card.py, we try to get the image position of the world coordinates, including the odometer position of the robot:
        tool_3d = self.odometer.prediction.point_3d() + \             rosys.geometry.Point3d(x=self.field_friend.WORK_X, y=self.field_friend.y_axis.position, z=0)         tool_2d = self.camera.calibration.project_to_image(tool_3d) / self.shrink_factor
I think we need to pass the robot’s pose as frame parameter. As the calibration itself doesn´t know the current frame of the camera. The same issue occurs in the plant_locator in the other direction.
            image_point = rosys.geometry.Point(x=d.cx, y=d.cy)             world_point_3d = camera.calibration.project_from_image(image_point)
Additionally, there was a problem with the old calibration on the robot, as it seems to be incompatible with the new code. Upgrading would require us to either recalibrate all robots or create a calibration import method.

@angelom93 Wow. Thanks for uncovering these issues. Let's dive in:

I think we need to pass the robot’s pose as frame parameter. As the calibration itself doesn´t know the current frame of the camera.

The camera pose should have already a associated frame which automatically should be used when doing the projection. At least that was true when testing in simulation. Maybe the frame is not set correctly on a real robot?
With your changes in ca81e46795f55 the tool display in the camera does not work anymore in the simulation.

Additionally, there was a problem with the old calibration on the robot, as it seems to be incompatible with the new code. Upgrading would require us to either recalibrate all robots or create a calibration import method.

That is problematic. How much effort would it be to write such a calibration import step? Maybe that is better than recalibrating every robot?

@rodja I don't have a new calibration file on hand, but I think it shouldn't be too hard to write a converter. When looking at calibration in 0.14.0, extrinsics is a Pose3D and before it was it's own class.
I think this should be the main difference

Here is an example of a broken calibration from F13/RB36
cat field_friend.vision.calibratable_usb_camera_provider.json
{
    "cameras": {
        "32e4-9230-platform-3610000.xhci-usb-0:2.4:1.0": {
            "id": "32e4-9230-platform-3610000.xhci-usb-0:2.4:1.0",
            "name": "32e4-9230-platform-3610000.xhci-usb-0:2.4:1.0",
            "connect_after_init": true,
            "streaming": false,
            "focal_length": 1830,
            "calibration": {
                "intrinsics": {
                    "model": "pinhole",
                    "matrix": [
                        [
<PHONE_NUMBER>299275,
                            0.0,
<PHONE_NUMBER>719205
                        ],
                        [
                            0.0,
<PHONE_NUMBER>575603,
<PHONE_NUMBER>150279
                        ],
                        [
                            0.0,
                            0.0,
                            1.0
                        ]
                    ],
                    "distortion": [
                        -0.42323083237038744,
                        0.24994860543758948,
                        -0.0016619969416450243,
                        -7.288107826439712e-05,
                        -0.07725206082664601
                    ],
                    "xi": 0.0,
                    "rotation": {
                        "R": [
                            [
                                1,
                                0,
                                0
                            ],
                            [
                                0,
                                1,
                                0
                            ],
                            [
                                0,
                                0,
                                1
                            ]
                        ]
                    },
                    "size": {
                        "width": 1020,
                        "height": 700
                    }
                },
                "extrinsics": {
                    "rotation": {
                        "R": [
                            [
                                0.0012156952531017229,
                                0.8037678718850602,
                                -0.5949417872451164
                            ],
                            [
                                0.9999974845579332,
                                -0.0020985613297158645,
                                -0.0007917816314380813
                            ],
                            [
                                -0.001884930465043511,
                                -0.5949393281383465,
                                -0.8037684012645899
                            ]
                        ]
                    },
                    "translation": [
                        0.0,
                        0.0,
                        1.0
                    ]
                }
            },
            "auto_exposure": true,
            "exposure": false,
            "width": 1280,
            "height": 720,
            "fps": 9
        },
        "32e4-9230-platform-3610000.xhci-usb-0:2.3:1.0": {
            "id": "32e4-9230-platform-3610000.xhci-usb-0:2.3:1.0",
            "name": "32e4-9230-platform-3610000.xhci-usb-0:2.3:1.0",
            "connect_after_init": true,
            "streaming": true,
            "focal_length": 1830,
            "calibration": {
                "intrinsics": {
                    "model": "pinhole",
                    "matrix": [
                        [
<PHONE_NUMBER>299275,
                            0.0,
<PHONE_NUMBER>719205
                        ],
                        [
                            0.0,
<PHONE_NUMBER>575603,
<PHONE_NUMBER>150279
                        ],
                        [
                            0.0,
                            0.0,
                            1.0
                        ]
                    ],
                    "distortion": [
                        -0.42323083237038744,
                        0.24994860543758948,
                        -0.0016619969416450243,
                        -7.288107826439712e-05,
                        -0.07725206082664601
                    ],
                    "xi": 0.0,
                    "rotation": {
                        "R": [
                            [
                                1,
                                0,
                                0
                            ],
                            [
                                0,
                                1,
                                0
                            ],
                            [
                                0,
                                0,
                                1
                            ]
                        ]
                    },
                    "size": {
                        "width": 1020,
                        "height": 700
                    }
                },
                "extrinsics": {
                    "rotation": {
                        "R": [
                            [
                                0.0012156952531017229,
                                0.8037678718850602,
                                -0.5949417872451164
                            ],
                            [
                                0.9999974845579332,
                                -0.0020985613297158645,
                                -0.0007917816314380813
                            ],
                            [
                                -0.001884930465043511,
                                -0.5949393281383465,
                                -0.8037684012645899
                            ]
                        ]
                    },
                    "translation": [
                        0.0,
                        0.0,
                        1.0
                    ]
                }
            },
            "auto_exposure": true,
            "exposure": false,
            "width": 1280,
            "height": 720,
            "fps": 9
        }
    }
}

@rodja The camera and projection movement are now fixed for the 3dScene with  https://github.com/zauberzeug/rosys/pull/183.
It still needs to be tested on a real robot and the implement projection of the camera card is still broken, but @angelom93 and I think that the camera card should be adressed in another PR to get this one merged

Sounds good to me!


drivers: clock_control: Move stm32f1 series to Cube LL API

stm32f1 series migrated to Cube LL API.
This completes migration of stm32 clock control drivers to unique API and hence simplify generic
driver implementation in calls to clock control driver.
Former driver code cleaned up.

About GPIO:
It is needed to get gpio_stm32.h modif available when activating CONFIG_CLOCK_CONTROL_STM32_CUBE in in boards defconfig.
The gpio_stm32.c could be moved in clean up, but I decided to group .h and .c gpio stuff

For the gpio stuff, I just meant move the commit earlier in the series of commits before the board changes to enable the CUBE clock support


Allow to create custom controls

Closing as stale. Re-open and resolve conflicts if decide to work on this PR further.


Errors when attempting to run

First off, thank you very much for the work here, this is something that YNAB needs to implement themselves, and appreciate someone stepping in and making an effort here!
I was able to clone from GitHub, and run the ynam --quickstart , and set up my account. it looks like its authorized into my YNAB account as it appropriately grabbed the budget and account names, but I didn't know how to verify if it was connecting with Mint.
When attempting to run ynam I get these errors
ynam Traceback (most recent call last): File "/usr/local/bin/ynam", line 8, in <module>     sys.exit(main())   File "/usr/local/lib/python3.10/site-packages/ynam/main.py", line 20, in main     mapi = MintAPI()   File "/usr/local/lib/python3.10/site-packages/ynam/mint_api.py", line 10, in __init__     self.restClient = mintapi.RESTClient AttributeError: module 'mintapi' has no attribute 'RESTClient'
I attempted to install mintapi itself to see if that would update the failed attribute, but no change in error.

It looks like you're using the mintapi/mintapi repo. ynam is using a newer version that isn't yet out on mintapi/mintapi:main, so for now install it from snowskeleton/mintapi. That should fix your issue.

Appreciate the quick reply. I've cloned ynam and mintapi from your repos and installed them from there.

after doing so when running I get the following errors

do you have chromium installed?

per the mintapi readme, chromium-browser and chromium-chromedriver both need to be installed. they're available from apt-get and other package managers. The error you're getting is one usually associated with not having chromium installed and/or not having it on your PATH

good catch. I am NOT a chrome user, so had no version of chromium installed. I hadn't dove into the mintapi repo to see that req. I just installed chrome, re-ran and it popped open the browser and let me log in. it still seems to be getting stuck on that line 41 of mint_api.py and never pulls the transitions

I moved the cookies and api_key to the home directory rather than worry about potentially non-existent sub-directories.
give this a try and see if it works?

that resolved it. was able to use ynam --graphics to get past the first login, and then after that used ynam --days 20 --graphics and it sent over the last 20 days of transactions to my test budget that I had set up. It DIDN'T actually launch the graphical version on the second command but completed the task.
good fix! thanks for the quick work

Also, I'm the rare case of not having any version of chromium installed, but maybe worth dropping a note in the readme for this repo that calls out the need for anyone in the future who is in the same boat!

I'm glad it worked!
Some background on the --graphics flag. It's only relevant if you haven't run ynam recently. Those cookies and api_key you were having trouble writing can be used to complete most functions through the REST API. That's why the browser didn't come up the second time. ynam will always try the REST call first, and only if that fails will it login with the browser to update the cookies and key. And then it'll retry the REST call. All that to say, the behavior you're seeing is expected.

Also, I'm the rare case of not having any version of chromium installed, but maybe worth dropping a note in the readme for this repo that calls out the need for anyone in the future who is in the same boat!

Good idea! It would probably be even better to have ynam check if it's installed, and prompt you to install it if missing.


[Bug]: jacoco-maven-plugin report EOFException in Flink Module CI

What happened?
When running CI Test program, the Flink module encounters EOFException which is reported by jacoco-maven-plugin.

Affects Versions
master
What engines are you seeing the problem on?
Flink
How to reproduce
No response
Relevant log output
No response
Anything else
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

duplicate with #1364


Local file support for buttons, images, menus

This allows users to use file:// prefix on what used to be all remote files for images within the Jasonette framework so that images files don’t have to be downloaded in cases where it’s static content for the mobile app.

Let me know if you think there are more tweaks to this to be made @gliechtenstein or if this is a viable mod to the platform.

@hoffmabc This looks great! i've been meaning to take care of this but never had time to, thanks for taking care of this!
I see you extracted out the - (void)setTabImage:(UIImage*)image withTab:(NSDictionary*)tab andItem:(UITabBarItem*)item to avoid duplicate code. Could you do the same for the rest (menu, button, etc.)? Would appreciate it!
I think we should be good to go once we take care of that.

Sure, @gliechtenstein I'll clean it up.

ok @gliechtenstein i refactored it.

Thanks @hoffmabc ! Just merged it in 🥇

For completeness' sake, added local image support for body.style.background and image type layers https://github.com/Jasonette/JASONETTE-iOS/commit/f1e69d0d17b3a1a19967131e6bd7a70d48f7a314

Almost forgot, also support footer.input.left https://github.com/Jasonette/JASONETTE-iOS/commit/1ff83c05f856e0d625b02a9ef2c8c61a207e893d


Minor consistency update correction for WW-5029 fix to the 2.5.x branch

Minor consistency update correction for WW-5029 fix to the 2.5.x branch:

Correct missing verification in buildAllowedMethods()/loadGlobalAllowedMethods() that the nodes are of type Node.TEXT_NODE (as buildResults() does).
Made two class fields final, as suggested by IDE.

Hello @lukaszlenart and @yasserzamani .
Apologies, but I missed a node type check in #347 that should have been performed for safety/consistency of the processing (make sure the node is a text node).  When reviewing the code again the oversight was noticed.  This small PR corrects that oversight.  :blush:

Hello Apache Struts Team.
The JDK 8 build run "succeeded but failed" yet again (3rd time in recent memory).
The Travis CI log shows the initial build succeeded (no failures) but the "2nd build" for JDK8 that was launched failed with: "The job exceeded the maximum log length, and has been terminated.".
So it seems the PR is OK, but the CI job still has intermittent issues with JDK8 builds (none of the others seem to fail).

LGTM 👍


Orders with multiple random qualities

Previously, a merchant ordered a specific amount of a random product with a random quality. With this PR, merchants order a specific amount and get items of one random product type but of different qualities. The qualities are chosen uniformly randomly from the available qualities.
Unit price, fixed order costs and product stock is now unique for each product type. Previously these attributes were unique for each product type and quality combination. This change has the advantage, that merchants can calculate how much an order will cost them.
The producer API changed. E.g. an order contains a list of products instead of one product. Existing merchants won't work with these changes. I'll create a pull request with updated example merchants. There will also be a change in the analytics repository.
Currently it's not possible to inspect or change the producer configuration in the management UI. I'll need to change the management UI as well to work with the new product information format.
If a merchant orders a product, he will receive an order with the following attributes:

product id
product name
billing amount
fixed cost
unit price
stock
left in stock
list of products

And products in that order have the following attributes:

uid
product id
name
quality
amount
time to life
start of lifetime
signature

This pull request is work in progress. Please do not merge yet

I updated the communication between producer and management UI and removed some API routes that are not used. For now, I done with this pull request.


[LM-12531] Create Post Media Handling

Description
Features
Bugs
What kind of change does this PR introduce? (check at least one)

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Hotfix (fix for breaking changes)
[ ] New Feature (non-breaking change which adds functionality)
[ ] Other, please describe:

Author Checklist

[ ] Assignee added
[ ] Reviewer added
[ ] Description added
[ ] Unit test cases added

Reviewer Checklist

[ ] PR title starts with Jira ticket number prefix
[ ] If hotfix, Add Hotfix as prefix in PR title
[ ] Label added
[ ] Commit messages follows standard format (added, changed, removed, code commented and chore)
[ ] Description about the Feature/ Bugs added

LGTM!


rpc error code = 2 desc = shim error context deadline exceeded

Is this a bug or a feature request?
What did you expect?
sending data from the gateway to the server
What happened?
I got that error
What version are your using?
How can your issue be reproduced?
Could you share your log output?

I'm closing this issue as no details are provided how this can be reproduced.


Ignore unrecognized tag warnings in schema tests in this repo

This PR fixes the default resolver override in conftest.py that was broken by changes to resolver code in asdf.  It also disables warnings on unrecognized objects when deserializing schema examples in tests.
These changes will allow the tests to function when new schemas are added to this repo.

Doing another rush merge here, but I'll follow up on any comments with an additional PR.


Add wpa_cli, wpa_supplicant, scan for hidden networks, parse negative noise

This is a big PR, because during my development, I merged in @carlos-alarcon 's PR https://github.com/bakerface/wireless-tools/pull/5 into my dev branch. Quoting from his PR:

I added some new 'fatures':
iwlist:
scan:
Will be able to show hidden networks.
Will be able to run in 'active' mode to look for an specific hidden SSID
wpa_supplicant:
disable can kill any wpasupplicant for a specific interface
manual: launch wpasupplicat (unconfigured) so it can receive commands from wpa_cli (to be setup)
wpa_cli: Connect to wpasupplicant and set/update configuration

The feature that I added is:
iwlist: parse negative noise

This seems super useful, I was about to start implementing wpa_cli myself until I saw this. Why hasn't this been merged?

Sorry, this fell off my radar. I will revisit it today and tomorrow.

Sorry, this fell off my radar. I will revisit it today and tomorrow.

Thanks for the fast reply, I appreciate the effort.

I just pushed a new release 0.16.0 with these changes.


Removal of & operator? [discussion]

A few days ago when I installed the software the operator & was describe as a way to receive inputs from Midi Controller. This has disappear now. May I ask why it was removed?

I've made a big change on how midi works in orca, I temporarily disabled it today while I repaired it.
Give me a couple of hours and it will be back, as it was before.

Ok, nothing urgent. ;)
Take the time that is needed, I'll wait.

It's back :)