[E06] Not enough keys in the keymap for your configured layout (ZMK)

Sorry, another beginner question but further to #21 I now keep getting this error.
I have written my config a couple of ways, but to no avail.

I'm pretty baffled 😅 your config looks correct. Though it does contain 84 keys, but when I look at your keymap, I can only count 82 in the first keymap. I think 84 is correct though, as when I use your config with the Kinesis corp config, that works and does indeed contain 84 keys.
Could you maybe have dropped a key in your config somewhere? Is there some macro, or ZMK magic that fills in the missing keys?
I've pasted below what the plugin sees (and it looks correct to me, I can't see any obvious accidental joining of keys).
 I'll try and track down those missing 2 keys :D
Looks like plugin is correct and 'error between keyboard and chair` — what most of my 'issues' end up being ;)

Ended up discovering your review on YouTube when I was Googling for this keyboard layout 😅 great video! I didn't know it was the standard for the 360, I assumed ZMK was for more hardcore mech board users; knowing that people might be forced to use it has made me realise the error messages need to be a lot more helpful, as I can imagine a lot of non techies trying to just get their keyboard to work 🤔

Thanks for looking at this, adding the extra keys and all good now, thanks!


Label Styling issue

Hello!
I'm getting this rendering issue on your examples page and when I have the plugin installed locally, image below:

Any ideas on how to fix?
I'm using the angular-chart.js and bootstrap 3 as well, however I think this is a problem with Chart.js directly given its appearin on your home page too.

Can you please provide link to the examples page where you have this problem ?
The only place where I see donut chart is like this:

I think this was a Chrome on Windows issue. I recall a similar issue that turned out to be due to Chrome HW rendering. It has since been fixed, hence I am closing this issue.


[Jetbrains HTTP Client] Endpoints contain necessary headers as indicated in the definitions

For Api Keys and other similar header values, variable placeholders can be used.

Not all headers are supported at the moment, but accept and consumes are. The option to add custom headers is also there.
Let's see if we need more


400 Bad Request; You'll need to update Instagram to the latest version before you can use the app.

Bug Report
Form
Requirements

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version
[ ] I've debugged my code using the DEBUG variable.

Platform

[x] I'm using Node.js version v21.6.1
[ ] I'm using electron

Description
As of 1.3.2024, Instagram probably no longer accepts the version (and probably public key) constants found in this package, and requires an update to a ,,new version of App´´. It'd be good to update the values in that file. Or, how can one get the values from the App to put in the constants.ts file (best without manual reverse-engineering Java/Smali source) to manually fix that error in future?
Code
let unm = "MYUSERNAME";
let password = "MYPASSWORD1234."
ig.state.generateDevice(unm);
try{
    await ig.simulate.preLoginFlow();
}catch(e){
    console.error("WARNING: preLoginFlow thrown:", e);
}
console.log(`Logging in as ${unm}`);
this.user = await ig.account.login(unm, password); //Error goes from here

ig.simulate.postLoginFlow(); //No await is RIGHT HERE!!!

Error and Output

Executed from Node REPL

IgResponseError: POST /api/v1/accounts/login/ - 400 Bad Request; You'll need to update Instagram to the latest version before you can use the app.
    at Request.handleResponseError (/usr/lib/node_modules/instagram-private-api/dist/core/request.js:126:16)

Me too, I've been seeing the same error since March 2.

+1 on this

Same here

Could anyone check if it works now?

for now you can use this but make sure the filetype should be of .jpg
`
require("dotenv").config();
const express = require('express')
const app = express()
const port = process.env.PORT || 4000;
const fs = require('fs');
app.listen(port, () => {
console.log(Listening on port ${port})
})
const { IgApiClient } = require('instagram-private-api');
const { get } = require('request-promise');
const postToInsta = async () => {
const ig = new IgApiClient();
ig.state.generateDevice(process.env.IG_USERNAME);
await ig.account.login(process.env.IG_USERNAME, process.env.IG_PASSWORD);

const imageFilePath = '222.jpg';

try {
    const imageBuffer = fs.readFileSync(imageFilePath);

    const publish = await ig.publish.photo({
        file: imageBuffer,
        caption: 'RTTTT',
    });

    console.log(publish)

} catch (error) {
    console.error('Error reading the image file:', error);
}

}
postToInsta()`

Could anyone check if it works now?

I get this error when trying to publish anything (post/story):
C:\...\node_modules\instagram-private-api\dist\core\state.js:143
            throw new errors_1.IgCookieNotFoundError(key);
                  ^

IgCookieNotFoundError: Cookie "ds_user_id" not found

It's very funny... At localhost it works, but without session.
async #login(username, password, agent) {
    this.#client = new IgApiClient();
    this.#client.state.generateDevice(username);
    this.#client.request.defaults.agent = agent;

    // this.#client.request.end$.subscribe(async () => {
    //   const serialized = await this.#client.state.serialize();
    //   console.log("serialized");
    //   delete serialized.constants; // this deletes the version info, so you'll always use the version provided by the library
    //   this.#saveSession(serialized);
    // });

    // if (this.#existsSession()) {
    //   console.log("exists");
    //   const session = await this.#loadSession();
    //   if (session && Object.keys(session).length > 0) {
    //     console.log("deserialize");
    //     await this.#client.state.deserialize(session);
    //     return;
    //   }
    // }

    console.log("login");
    await this.#client.account.login(username, password);
  }

It's very funny... At localhost it works, but without session.
async #login(username, password, agent) {
    this.#client = new IgApiClient();
    this.#client.state.generateDevice(username);
    this.#client.request.defaults.agent = agent;

    // this.#client.request.end$.subscribe(async () => {
    //   const serialized = await this.#client.state.serialize();
    //   console.log("serialized");
    //   delete serialized.constants; // this deletes the version info, so you'll always use the version provided by the library
    //   this.#saveSession(serialized);
    // });

    // if (this.#existsSession()) {
    //   console.log("exists");
    //   const session = await this.#loadSession();
    //   if (session && Object.keys(session).length > 0) {
    //     console.log("deserialize");
    //     await this.#client.state.deserialize(session);
    //     return;
    //   }
    // }

    console.log("login");
    await this.#client.account.login(username, password);
  }

Works with the latest version 1.46.1!
Thanks @Nerixyz

Issue is fixed with 1.46.1. Thanks @Nerixyz


Parts of an image could end up being redacted.

Target components
log
What is wrong
If an html is being added (such as an image), some parts can end up being redacted (which may not be what's wanted).
System info
Any
Example script
No response

This is actually an important issue (that we should've tackled already).


add Maven credential metadata to the URLs it searches for POM files

Currently Dependabot uses any repository or pluginRepository URL it finds in the POM to search for parent POM files. However, there is no reason a child POM needs to have any repositories defined at all. It's fairly common for private/custom registries to only be defined in the parent which is published to the registry.
The reason why this works locally for Maven users is they often have a settings.xml which defines what registry to use, but that file isn't typically checked in to git.
Dependabot users commonly try to put the registry in dependabot.yml as a hint to where it can find the parent POM.
This PR takes that hint and puts Maven registries defined in dependabot.yml at the front of the list of registries to check.

This should fix https://github.com/dependabot/dependabot-core/issues/5523


Scratch Org Users in nonScratchOrgs result

Summary
Not sure if this is a regression or a change to the API, but force:org:list now returns users created in a scratch org in the nonScratchOrg section of the response. These users were previously in the scratchOrg response. This has caused some of my scratch org automation to fail.
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc
NOTE: If your issue is not reproducable by dreamhouse-lwc, i.e. requires specific metadata or files, we require a link to a simple Salesforce project repository with a script to setup a scratch org that reproduces your problem.

Create a scratch org: sfdx force:org:create -s -f config/project-scratch-def.json -a dreamhouse
Create a new user in the scratch org: sfdx force:user:create -a testuser<EMAIL_ADDRESS>permsets=DreamHouse
List all the orgs: sfdx force:org:list --json

Expected result
The "org" for testuser is displayed in the scratchOrgs response.
Actual result
The "org" for testuser is displayed in the nonScratchOrgs response.
Additional information
SFDX CLI Version: sfdx-cli/7.85.1-2fb9e41053 darwin-x64 node-v12.18.3
SFDX plugin Version: salesforcedx 50.16.1
OS and version: macOS 10.15

This is fixed in the new version of plugin-org (coming soon).  You can test it out right now to verify that it's fixed.
https://github.com/forcedotcom/cli/issues/835

Closing because the fix in plugin-org is shipped.


No notification sound on ios

No notification sound on ios.
we get notifications but not the sound.
core modules @ 2.2.0
ios runtime @ 2.2.0

Thanks for reminding me I did not implement it yet - you can now pass in sound: null for no sound, or leave it out for the default sound.

Tested on iOS simulator (tested for sound functionality on other apps first to ensure no issues with simulator sounds)
Steps:
tns platform remove ios
tns plugin remove nativescript-local-notifications
tns plugin add nativescript-local-notifications
tns platform add ios
tns prepare ios
tns run ios
Result:
No sound when local notification is received

will test  on device and report in a while


change 'current password' input fields to 'password'

it's odd to have any password field revealed by default

LGTM


[Master] Fix CCE for method access on union type

Purpose
Fixes #26726
Approach
Add switch case for Union type method access.
Samples
class EmployeeR {
    function func(int i) returns int => i;
}

class ManagerR {
    function func(int i) returns int => i+1;
}

class CompanyR {
    function func(int i) returns string => (i+2).toString();
}

public function main() {
    EmployeeR|ManagerR ob1 = new ManagerR();
    function (int i) returns int func1 = ob1.func;
}

public function main() {
    ManagerR ob2 = new EmployeeR();
    EmployeeR|ManagerR ob3 = ob2;
    function (int i) returns int func2 = ob3.func;
}

public function main() {
    CompanyR|ManagerR ob4 = new ManagerR();
    (function (int i) returns string)|function (int i) returns int func3 = ob4.func;
}

These test cases gave CCE. This PR will fix those.
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

I found another issue here
class ManagerR {
    function func(int i) returns int => i+1;
}

class CompanyR {
    function func(int i) returns string => (i+2).toString();
}

public function main() {
    ManagerR|CompanyR ob4 = new CompanyR();
    (function (int i) returns string)|function (int i) returns int func3 = ob4.func;
    function (int i) returns string func4 = <function (int i) returns string> func3;
}

This is not runtime error. But,
public function main() {
    CompanyR|ManagerR ob4 = new CompanyR();
    (function (int i) returns string)|function (int i) returns int func3 = ob4.func;
    function (int i) returns string func4 = <function (int i) returns string> func3;
}

if we swap the CompanyR|ManagerR ob4 = new CompanyR(); union type, then it gave me the
Error Output: error: {ballerina}TypeCastError {"message":"incompatible types: 'isolated function (int) returns (int)' cannot be cast to 'function (int) returns (string)'"}. I will fix and update the PR.

Holding this until this issue https://github.com/ballerina-platform/ballerina-spec/issues/1187 sorted

@MaryamZi @prakanth97 I think, we should disable allowing the call-expr on the union of function types, even with the union has the same shape.  This has multiple edge cases, so better to wait until the spec issue to support this in the compiler.

@MaryamZi @prakanth97 I think, we should disable allowing the call-expr on the union of function types, even with the union has the same shape. This has multiple edge cases, so better to wait until the spec issue to support this in the compiler.

This is already disallowed, right?
Related issue from some time ago - https://github.com/ballerina-platform/ballerina-lang/issues/19061.

@MaryamZi @prakanth97 I think, we should disable allowing the call-expr on the union of function types, even with the union has the same shape. This has multiple edge cases, so better to wait until the spec issue to support this in the compiler.

This is already disallowed, right?
Related issue from some time ago - #19061.

  ManagerR|CompanyR ob4 = new CompanyR();
  _ = ob4.func(1);

This is restricted already. But inorder to solve the current NPE issue. We should restrict ob4.func variable ref to the function and give error like undefined function 'func' in type '(ManagerR|CompanyR)'. WDYT @MaryamZi @hasithaa ?

@MaryamZi @prakanth97 I think, we should disable allowing the call-expr on the union of function types, even with the union has the same shape. This has multiple edge cases, so better to wait until the spec issue to support this in the compiler.

This is already disallowed, right?
Related issue from some time ago - #19061.

  ManagerR|CompanyR ob4 = new CompanyR();
  _ = ob4.func(1);

This is restricted already. But inorder to solve the current NPE issue. We should restrict ob4.func variable ref to the function and give error like undefined function 'func' in type '(ManagerR|CompanyR)'. WDYT @MaryamZi @hasithaa ?

What's the NPE issue? ob4.func should still work IMO. What shouldn't work is using that in a function/method call expression ob4.func().

@prakanth97 there are conflicts.

Updated e5a505e2926782fcca021f5ae7e8267763bf3aa1


Embedded schemas overwrite conflicting aliases

Closes https://github.com/elixir-ecto/ecto/issues/4124
Properly expands the nested embed module name so that it won't be overwritten by conflicting aliases.
I think we only need to care about expanding nested module aliases so I didn't consider the other cases from: https://github.com/elixir-lang/elixir/blob/50741091baa10170805730ed91943c481b7ab270/lib/elixir/lib/kernel.ex#L4971-L4993.
But this is not my strong suit so please correct me if I'm mistaken.

Nice start! I dropped some comments for additional cases to watch out for!


bump sqlite-jdbc to <IP_ADDRESS>

Fixes https://github.com/ngageoint/geopackage-java/issues/59

Thanks, I have it updated already here.  Was planning to release a new version next week for unrelated changes.


Feature/add websocket functionallity

Description
This pull request is a feature that allows the har-to-k6 converter to handle web-socket functionality. It uses the k6 library import ws from 'k6/ws'. These requests were formerly ignored in the original itteration of har-to-k6.
Type of change

This version handles the websocket send(...) messages and adds a setTimeout in place of sleep for websockets, this is because k6 websocket callbacks are not made to work with the sleep(...) function.
Websocket send messages are the only messages that are handled here
Once the file is converted, if you have specific timings or order that needs to be handled you must add that yourself.
This is very generic to support many different kinds of websocket testing

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hey @trinatafoya, thank you for your PR submission!
Unfortunately, I can not approve your PR, mainly due to the reason that we're currently overhauling k6 WebSockets APIs. You can find the new experimental module here: https://k6.io/docs/javascript-api/k6-experimental/websockets/.
As the name implies, the module is still experimental and is not fully implemented. Only when the k6 WS APIs become stable and land in k6 we'll be considering adding support to har-to-k6.


#Fix 29

what does this PR do ?
This PR restricts authenticated users from accessing signin and signup pages.
Fixes #29

Thanks a lot


Adding project support for linting

I noticed that the project has an eslint config but hasn't got the required devDependencies or an npm script for running the linter across all files from within the project itself.
Not sure if you want to add this in but I thought I'd set it up. All the correct dependencies have been added for airbnb and Babel. I've also added an npm script: npm run lint which will lint all files in ./client along with the Webpack config file.
Due to - I am assuming - the way Webpack resolves dependencies when bundling, there are a lot of 'import/no-unresolved' linting errors when this is run so it's probably worth disabling this rule?

Yes, that was my fault because I have a global eslint setup so I don't have to introduce it in every project. My bad for not including it here.
I'm ok with disablingimport/no-unresolved

Ah that's exactly what I assumed to be honest.
I've just added the following exclusions to the rules:
import/no-extraneous-dependencies: 0  import/no-unresolved: 0  import/extensions: 0  react/jsx-filename-extension: 0
That's reduced the number of errors by quite a lot. Got some left but it's not too bad and can work through them.

I'm ok with this for now. But we should come back to it to fine tune lint rules.
I'm counting on @elodszopos, he's known to be the lint/test junky

A big thank you, James

Superb! Yeah would be good to settle on a nicely tuned set of rules for the project. I'll look at fixing the linting errors we have currently.


[Bug] Color picker on Container widget blocks input for user

Description
Colour picker on container widget blocks input for user if user is trying to enter their own colour code.
Steps to reproduce the behaviour:

Drag and drop container widget on to canvas
Click on background colour input box to input you're own colour code - colour picker pops up and blocks input field

Important Details

Version: Cloud
OS: Win10
Browser: Chrome
Environment: Production

Closing this in favour of #4413


PWM board capacitors may be too small

When you move a lot of servos at the same time, there is a sudden demand for current on the 5V supply line.
The ideal solution is a capacitor located very close to the devices needing the current which stores charge and can make up any temporary shortages.
I ran across a "hooking it up" document for the PCA9685
https://learn.adafruit.com/16-channel-pwm-servo-driver/hooking-it-up
----------- which has this to say:
Adding a Capacitor to the thru-hole capacitor slot
We have a spot on the PCB for soldering in an electrolytic capacitor. Based on your usage, you may or may not need a capacitor. If you are driving a lot of servos from a power supply that dips a lot when the servos move, n * 100uF where n is the number of servos is a good place to start - eg 470uF or more for 5 servos. Since its so dependent on servo current draw, the torque on each motor, and what power supply, there is no "one magic capacitor value" we can suggest which is why we don't include a capacitor in the kit.
------------ end of quote
We have 9 servos on each PWM board, so the n * 100uF starting point would be 900uF. I'd be tempted to go a little higher, because we are definitely hitting the worst case of trying to drive all of the servos at the same time. The 470uF one that came on the board definitely seems to small, and this could account for several of the symptoms we've seen.
I have fresh 1000uF electrolytic caps that are the same diameter as the ones that come on the board, but 50% taller. I think I'll measure a couple of them, and swap in the ones with the highest capacitance.

changing capacitors to 1000uF has improved performance significantly. No twitch observed since this change, and all motors are responding consistently. Next step is to reduce the delays after each servo is moved in the SSD command, and see if it still works reliably, and if the cascading motion comes closer to simultaneous.

this is a confirmed performance improvement. closing issue


Fix autodiff of pad() of scalar inputs.

Fixes #10927

Here's a more compact repro:
from jax import jit
import jax.numpy as jnp
from functools import partial

@partial(jit, static_argnums=1)
def f(x, a):
  return x % a

f(jnp.complex64(1), 0.5)


svg's not loading

replace old .svg paths with the vite-svg-loader
(eg. pages/introduction.vue line 43)

You can assign it to me @roriwa


Fix workspace error when installing ckb-binary-patcher

error: current package believes it's in a workspace when it's not:
current:   /build/godwoken/gwos-evm/deps/ckb-binary-patcher/Cargo.toml
workspace: /build/godwoken/Cargo.toml

this may be fixable by adding `gwos-evm/deps/ckb-binary-patcher` to the `workspace.members` array of the manifest located at: /build/godwoken/Cargo.toml
Alternatively, to keep it out of the workspace, add the package to the `workspace.exclude` array, or add an empty `[workspace]` table to the package's manifest.
Makefile:86: recipe for target 'build/ckb-binary-patcher' failed
make[2]: *** [build/ckb-binary-patcher] Error 101
make[2]: Leaving directory '/build/godwoken/gwos-evm'
Makefile:64: recipe for target 'all-via-docker' failed
make[1]: *** [all-via-docker] Error 2
make[1]: Leaving directory '/build/godwoken/gwos-evm'
Makefile:30: recipe for target 'build-components' failed
make: *** [build-components] Error 2

No need. I added that patch repo in the Cargo.toml as excluded.
Maybe you need to rebase?

No need. I added that patch repo in the Cargo.toml as excluded.
Maybe you need to rebase?

Ah, I find it now.

But ckb-binary-patcher is not a dependency, so we just need to install it.
So this solution is more simple, right?
@magicalne
Also, please review the new commit: https://github.com/godwokenrises/godwoken/pull/877/commits/1b9ff27f16b8e04d22dd967bfa05f6ab2c6c996b

LGTM
So we can remove this line as well.

LGTM So we can remove this line as well.

done: https://github.com/godwokenrises/godwoken/pull/877/commits/a8156344d570d72725ee080f78d6420c2eb73d2f


Items options in cart

The items options stopped to be displayed in the cart.

https://github.com/vercel/commerce/pull/570

The MR has been merged


Audit & remove any assumptions that the frontend is JS only.

#11513 started to migrate our frontend to Typescript, but a lot of places in the codebase (and documentation) makes the assumption that it is Javascript only. For example in test-js-with-node#L119:
# Add ".js" to the end of all the file arguments, so index.js
# can actually verify if the file exists or not.
for index, arg in enumerate(options.args):
    if not arg.endswith('.js'):
        options.args[index] = arg + '.js'

@zulipbot claim

Cool, yeah, we should also look at our linter tooling.

@tommyip @skunkmb @priyank-p so for closing out this issue, we should:

Do a bit more thoughtful work on discussion of TypeScript in our docs.  E.g. we might want a top-level page in the "testing" section similar to the one we have on mypy, explaining that we're migrating, linking to the "cheat sheet", and providing some details on how our current partial integration works.  Let me know if you'd like me to help with drafting that -- I'm pretty fast at outlining documentation.  Potentially we should move this to a separate issue, since it's about documentation, not tooling.
Someone should carefully test that linter/etc. tooling actually works on the TS files, through manually breaking things, just because it's a lot more annoying to discover you weren't actually testing what you thought you were later.  Once we've had an additional audit on that work.

Regarding the linters, I believe TSLint currently doesn't actually do anything since we aren't giving it TS files to work with. See #11984.

I added a44de17f9b705d60fd406e2b38b09af6f844003e as a very much draft initial top-level doc on TypeScript and its migration.  I'd love contributions to extend it (filling in the TODO, etc.) and I think we can use the notes in the "migration strategy" section as a starting point for discussion.
I think we should make a list of all the types of code changes we have made in migrating dict.ts and divide them into three categories:

JavaScript style changes we should just bulk do now on the JS codebase and then change our linter rules.  E.g. return undefined; is something that could fit into this category if we wanted that styling (which I do think I prefer for a typed language).
Things we have to do as part of the atomic change that moves a file from JS to TS.
Style changes we can only make after we move a file to TypeScript, e.g. const/let.  Though actually, is TypeScript a superset of ES5?  I'm kinda wondering if we could move files without any code changes to ts in order to allow us to switch const/let and other ES6 things without adding types if we had the right linter exclude rules.  Just brainstorming a bit here.


Use schmitt trigger to detect the contat activation and deactivation in MANN

During our testing of MANNTrajectoryGenerator with @paolo-viceconte, we encountered an issue where unexpected contact was being generated. This was caused by the undesirable switch-bouncing effect triggered by MANN, which refers to the imperfect behavior of a switch leading to multiple transitions for a single input.

To address this issue, we decided to filter the contact using a Schmitt trigger, which is already available in blf 🎉 . However, we faced a challenge in utilizing the Schmitt trigger within MANNAutoregressive. Specifically, we needed to implement the ability to completely control the internal state of the Schmitt trigger, including all internal timers.
Furthermore, the switch off and on parameters of the Schmitt trigger were set to negative values (-0.01 and -0.01) since we consider the negative of the foot height. In our context, the output of the Schmitt trigger is considered active when there is a contact. Therefore, a value of -0.01 indicates that the contact is active if the distance between the foot and the ground is lower than 1cm.

Furthermore, the switch off and on parameters of the Schmitt trigger were set to negative values (-0.01 and -0.01) since we consider the negative of the foot height. In our context, the output of the Schmitt trigger is considered active when there is a contact. Therefore, a value of -0.01 indicates that the contact is active if the distance between the foot and the ground is lower than 1cm.

Just as an additional comment, this is an implementation-dependent choice. If the user can set this value, I would suggest forcing it somehow inside. I feel like it breaks the "principle of least astonishment" a little :thinking:

Furthermore, the switch off and on parameters of the Schmitt trigger were set to negative values (-0.01 and -0.01) since we consider the negative of the foot height. In our context, the output of the Schmitt trigger is considered active when there is a contact. Therefore, a value of -0.01 indicates that the contact is active if the distance between the foot and the ground is lower than 1cm.

Just as an additional comment, this is an implementation-dependent choice. If the user can set this value, I would suggest forcing the sign somehow inside. I feel like it breaks the "principle of least astonishment" a little thinking

I agree since it is counterintuitive I decided to ask the user to pass a positive number, since the foot height is always positive (at least in this scenario), and then convert it into negative to simplify the usage of the trigger inside the class

Hi @S-Dafarra, I modified what you suggested except for https://github.com/ami-iit/bipedal-locomotion-framework/pull/684#discussion_r1221037158. Let me know if you are fine with this


[flink] debug logging for state access

If found this (optional) logging essential to debug issues with state access. To enable it in embedded mode:
java -Dorg.slf4j.simpleLogger.defaultLogLevel=WARN -Dorg.slf4j.simpleLogger.log.org.apache.beam.runners.flink.translation.wrappers.streaming.ExecutableStageDoFnOperator=debug  -jar runners/flink/job-server/build/libs/beam-runners-flink_2.11-job-server-2.12.0-SNAPSHOT.jar </dev/null > jobserver.log 2>&1 &

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Run Python PreCommit

The problem I was debugging turned out to be a key encoding issue in the application. At the moment everything seems to work as expected. There does not seem to be any state caching on the SDK side yet, which should become noticeable at larger scale. We are using the stateful processing with very low throughput initially.

Run Python PreCommit

Run Python PreCommit


Promise type should separate failure and success types separately

Current type definition of Promise takes single polymorphic parameter R that seems to represent type of the value it will be successfully fulfilled with:
https://github.com/facebook/flow/blob/master/lib/core.js#L422
Unfortunately this mean error case is untyped:
https://github.com/facebook/flow/blob/master/lib/core.js#L423
Furthermore onFulfill handler can return rejected promise and there for make result of .then rejected promise.
I run into this issue with a code like:
class Future <error, value> {
  type: "Async";
  promise: () => Promise<value>;
  constructor(promise:() => Promise<value>) {
    super()
    this.type = "Async"
    this.promise = promise
  }
  await(resume:(task:Task<error, value>) => void):void {
    this
      .promise()
      .then(Task.succeed, fail)
      .then(Task.resume)
  }
}

Problem is I can no longer restrict errors that task can fail with. Which is why I'd like to propose altering a type definition for promises as follows:
// Bottomless type that can't be instantiated
type Never = Never

declare class Promise<R, X> {
    constructor(callback: (
      resolve: (result: R | Promise<R, X>) => void,
      reject:  (error: X) => void
    ) => mixed): void;

    then<U, Y>(
      onFulfill?: (value: R) => U | Promise<U, Y>,
      onReject?: (error: X) => U | Promise<U, Y>
    ): Promise<U, Y>;

    catch<U, Y>(
      onReject?: (error: X) => U | Promise<U, Y>
    ): Promise<U, Y>;

    static resolve<T>(object?: Promise<T> | T): Promise<T, Never>;
    static reject<Y>(error?: X): Promise<Never, Y>;
    static all<T, Y, Elem: Promise<T, Y> | T>(promises: Array<Elem>): Promise<Array<T>, Y>;
    static race<T, Y, Elem: Promise<T, Y> | T>(promises: Array<Elem>): Promise<T, Y>;

    // Non-standard APIs common in some libraries

    done(
      onFulfill?: (value: R) => mixed,
      onReject?: (error: X) => mixed
    ): void;

    static cast<T>(object?: T): Promise<T, Never>;
}

Closing this pending a proposal that addresses the concerns I outlined above.

I agree that this would be a great feature.  We've been longing to use a second type parameter in our promises.  It's clear, though, from Sam's examples, that flow would have to handle exceptions at the function level before tackling Promises (if that happens at all).
In your last Runtime error example, @samwgoldman, you say, " This behavior necessitates that the type parameter at least be bound by Error, which limits its utility."  Great observation, but I disagree that we've limited the utility.  Rather, I feel you've uncovered a bit of clumsiness with ES6 Promises that flow would have to deal with.
I'm wondering if perhaps flow could enforce that developers specify at least a union with Error, i.e. var p: Promise<*,number|Error> = ....  Does that make sense?  If so, that's not a bad compromise when developers want to transform rejection values.

@unscriptable Fair points, and thanks for the thoughtful discussion.
Say we could enforce that Error must be part of that type param. There's still an issue with explicit throw (non-Error type) from a function call inside the promise. For this we'd need call graph analysis to see if any of those calls might throw. Without that, implementing this soundly is intractable.

Just came here looking to see if there was a better story than in TypeScript https://github.com/Microsoft/TypeScript/issues/7588.

What if we allowed Promises to take optional second error type defaulting to any ? That would at least allow type refinements when .catch or .then is used.

Why was this closed?

Why was this closed?

@samwgoldman outlined in comment above that run-time exceptions could poison soundness. Like right now type guarantees by flow are sound in that even if you throw or run-time exceptions happens types will still match declarations. Unfortunately promises are different in a sense that exceptions will sneak back into run-time or in other words then handler could type check as expecting say type number but at runtime get Error instead (or whatever you happen to throw really).
I still think think it would still be improvement over what we have today, but I also understand provided counter arguments as that would alter overall soundness of flow.


Improving support for composed scheme

Describe the feature
Imporves support of composed scheme for openapi.
There was limitation in #825 for creating composed scheme of arrayed-elements.
#659 was not actually solved by #825, this PR adds support for responses with same status and group them to "oneOf" scheme.

Thanks @sealedtx ! Would you like this merged now, or can you wait and rebase it after the project is made a multi-module project?

Up to you, @tipsy. It would be nice to see these updates in the nearest releases. When multi-module is going to be ready?

When multi-module is going to be ready?

Next release is the plan!

I'll merge this now @sealedtx, I'll do the rebase on my own branch :)

This has been released as part of 3.7.0 now!
https://javalin.io/news/2020/01/01/javalin-3.7.0-released.html


Include vhost for RabbitMQ when retrieving queue info with useRegex

The vhost is included when you don't use useRegex: true. It makes
sense to have consistent behaviour between the two modes.
Fixes #2498

Provide a description of what has been changed
Checklist

[ ] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[ ] Tests have been added
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[ ] Changelog has been updated

Fixes #

@JorTurFer Any ideea why the test are failing now ? They passed yesterday and the only change I did was changelog

@JorTurFer Any ideea why the test are failing now ? They passed yesterday and the only change I did was changelog

Rerunning, it could be a transient error

I was not sure about the breaking change. I mean without vhost is the same but with vhost is not. I can move it to improvements, your call. We'll have a look at the tests next week

I was not sure about the breaking change. I mean without vhost is the same but with vhost is not.

That's why I said, if a user is already using rabbitmq with regex, vhost is not needed, so I'd assume that is not preset. In that case when vhost is not defined, there is not any breaking change.
any opinion about this @kedacore/keda-core-contributors ?

Is there a particular reason why is this marked as draft?

@zroubalik I guess we marked it as draft because we were not sure if the tests are correct and then we could not change the status.
This can be merged.

/run-e2e rabbitmq-queue*

/run-e2e rabbitmq-queue*

@Photonios any update on this please?

Sorry guys, we've been very busy and did not have time for this. I think some e2e tests need to be updated. We will try to have a look this week

Sorry guys, we've been very busy and did not have time for this. I think some e2e tests need to be updated. We will try to have a look this week

I'm not sure if the e2e test is wrong. I mean, the e2e test is testing regex without any vHost, so it should work in the same way even after your changes. Adding one  e2e test to check the regex with vHost sounds good, but the current e2e test is testing the other scenario and we should keep it (or do a breaking change, but I think we should avoid it).
I proposed a change on my review that could solve this problem, supporting both cases. WDYT?

After further investigations, I decided to rework the vhost computation part because the way it was computed in our previous commits completely removed the flow in which no vhost was provided (when the queue name regex was used). Indeed, this was the reason that led to the failing E2E test, but that was another problem that I tried to fix. The E2E test was created to test the case when a vhost and a queue name regex are provided, but the connection string omitted the vhost part, so the test was actually running on “All” vhosts, which led to the failure from our previous commits. I want to underline the fact that in my opinion, a new E2E test should be added, which will properly test the case with vhost = "" (which in fact is the equivalent for the "All" option in the RabbitMQ management console).
I spent some time in the RabbitMQ management console and I observed that if you're using any vhost (but the "All" option), the URL will contain the /<vhost> part, including the root vhost ('/'), which will lead the URL in the following format: /%2F. If the “All” option is selected, the URL does not contain the vhost at all, jumping directly to the query params.
In the end, I want to mention that I tried to setup the environment locally in order to run the E2E tests, but I think I failed since on my local machine all tests were passing, except for the scalers/rabbitmq-queue- trigger-auth.test.ts.

/run-e2e rabbitmq-queue*

/run-e2e rabbitmq*

/run-e2e rabbitmq* Update: You can check the progres here

This is broken after adding multi-arch build, I'll trigger it again when it's solved

/run-e2e rabbitmq*

hi @Photonios ,
Could you rebase main into your branch?

/run-e2e rabbitmq*

atlantis apply

LGTM. Only 2 nits:

Please add the issue instead of the PR to the changelog (we have changed that system some days ago 😄 )
Related with e2e test, Could you create the dummy queues in different vHost and push message to all of them? I mean, instead of adding dummy queues to the same vHost that you are using for scaling, in others. With this change you will test that regex only applies to your vHost

BTW. Thanks a ton for this contribution and for all the effort that you have done ❤ ❤ ❤ ❤

Sure, I pushed the changes.
We're glad we could fix this problem so we can both benefit from it. Will it be possible to have a bug-fix release containing this PR? We'll need it soon and doing a local build will require a lot of extra work.

/run-e2e rabbit*

We're glad we could fix this problem so we can both benefit from it. Will it be possible to have a bug-fix release containing this PR? We'll need it soon and doing a local build will require a lot of extra work.

Hey, unluckily that's not possible because in fact, this is not a bug-fix, it's a new feature. :(
I'd suggest to, after this PR is merged (and the image generated) pull it from KEDA's register, push it into one registry under your control and use that registry in your scenario till next version. With this approach, you will not need to build it from scratch by your self and you'll have a frozen version till next release in 2 months.
Other option could be use the image's sha instead of the tag for pulling always the same image but IDK if we could delete old images untagged sometime

We're glad we could fix this problem so we can both benefit from it. Will it be possible to have a bug-fix release containing this PR? We'll need it soon and doing a local build will require a lot of extra work.

Hey, unluckily that's not possible because in fact, this is not a bug-fix, it's a new feature. :(

Just to interject here, the RabbitMQ scaler has two relevant features:

Use regex in queueName parameter to select queue[s] instead of full name ([applying sum, max or avg] to compute the number of messages [across many queues]).
[Set the] Vhost to use for the connection.

[...] is text I added to clarify/frame the two features better for this discussion, the rest is quoted directly from the documentation.
The documentation does not say anywhere that these two features are incompatible.  As such, the fact that these two features are incompatible is a bug: either a documentation bug or an application bug, depending on how you choose to see it. Because of this, people will continue trying to use these two features together, perceiving the results as a bug until they search around enough to find this PR or the issue from which it stems.
The perception of a bug on the part of all users with this particular (not unusual or unexpected) use case would generally be a good argument for treating the feature-gap as a bug: either patching the documentation to highlight the incompatibility, or (as the application fix is already complete) patching the application between minor releases.

We're glad we could fix this problem so we can both benefit from it. Will it be possible to have a bug-fix release containing this PR? We'll need it soon and doing a local build will require a lot of extra work.

Hey, unluckily that's not possible because in fact, this is not a bug-fix, it's a new feature. :(

Just to interject here, the RabbitMQ scaler has two relevant features:

Use regex in queueName parameter to select queue[s] instead of full name ([applying sum, max or avg] to compute the number of messages [across many queues]).
[Set the] Vhost to use for the connection.

[...] is text I added to clarify/frame the two features better for this discussion, the rest is quoted directly from the documentation.
The documentation does not say anywhere that these two features are incompatible. As such, the fact that these two features are incompatible is a bug: either a documentation bug or an application bug, depending on how you choose to see it. Because of this, people will continue trying to use these two features together, perceiving the results as a bug until they search around enough to find this PR or the issue from which it stems.
The perception of a bug on the part of all users with this particular (not unusual or unexpected) use case would generally be a good argument for treating the feature-gap as a bug: either patching the documentation to highlight the incompatibility, or (as the application fix is already complete) patching the application between minor releases.

Okey,
Even do we treat this as a bug, we don't plan to do any urgent release with these changes, sorry.
KEDA's release plan is defined in governance repository
Do you have any other pov @kedacore/keda-maintainers ?

Okey, Even do we treat this as a bug, we don't plan to do any urgent release with these changes, sorry. KEDA's release plan is defined in governance repository Do you have any other pov @kedacore/keda-maintainers ?

Fair enough. I can't see a discussion of your policy on patch releases in the linked governance repo, but I can see your most recent patch release was a week or two after your latest minor version release.
That patch had a small number of small updates, such as a fix to an e2e test. The main fix seems to be to avoid sometimes-flaky behaviour when there are multiple triggers for a single scaled object.  I assume that that gives an idea of the impact threshold past which you will do a patch release.

just for clarifying, any extra release could be done if @kedacore/keda-maintainers agree with it. :smile:
v2.6.1 was released with the agreement of maintainers for solving a critical bug in the own core which affected whole the service after hard work before release v2.6.0 solving other bugs related with the cache in the core.
In this case, the potential impact of the error seems lower, so using the workaround for having this patch sounds reasonable. Using main tag (under your own risk) is other possibility for having this patch available since now


iOS crash：UIGraphicsBeginImageContext() failed to allocate CGBitampContext

this is crash log by firebase, how to fix it ?
Fatal Exception: NSInternalInconsistencyException
0  CoreFoundation                 0x83f20 __exceptionPreprocess
1  libobjc.A.dylib                0x16018 objc_exception_throw
2  Foundation                     0x6de9a4 -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:]
3  UIKitCore                      0xc2f40 _UIGraphicsBeginImageContextWithOptions
4  Clarity                        0x13610 (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
5  Clarity                        0xf454 (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
6  Clarity                        0xb44c (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
7  Clarity                        0xa3e4 (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
8  Foundation                     0xf43e4 _startElementNs
9  libxml2.2.dylib                0x2968 xmlParseStartTag2
10 libxml2.2.dylib                0x125ec xmlParseTryOrFinish
11 libxml2.2.dylib                0x11748 xmlParseChunk
12 Foundation                     0x123e7c -[NSXMLParser parseData:]
13 Foundation                     0x124008 -[NSXMLParser parseData:]
14 Foundation                     0x123bcc -[NSXMLParser parseFromStream]
15 Clarity                        0x12e34 (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
16 Clarity                        0x9b70 (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
17 Clarity                        0x91d0 (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
18 Clarity                        0xf651c (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
19 Clarity                        0x82700 (符號缺漏 UUID 1cfb1ff7928a33869f4e20db41a65760)
20 libdispatch.dylib              0x213c _dispatch_call_block_and_release
21 libdispatch.dylib              0x3dd4 _dispatch_client_callout
22 libdispatch.dylib              0xb400 _dispatch_lane_serial_drain
23 libdispatch.dylib              0xbf30 _dispatch_lane_invoke
24 libdispatch.dylib              0x16cb4 _dispatch_root_queue_drain_deferred_wlh
25 libdispatch.dylib              0x16528 _dispatch_workloop_worker_thread
26 libsystem_pthread.dylib        0x4934 _pthread_wqthread
27 libsystem_pthread.dylib        0x10cc start_wqthread

Thanks @GitHubYhb for reporting the issue. Could you please provide more details to help expedite our troubleshooting?
Describe the Bug
A clear and concise description of what the bug is.
Repro Steps
If applicable, steps to reproduce the behavior.
Screenshots
If applicable, add screenshots to help explain your problem.
Project Info
If this is an issue happening in a specific Clarity project,

Project ID

Platform/Framework Info

Device: [e.g. iPhone 13 Pro]
OS: [e.g. iOS 17.5]
Application Framework [e.g. ReactNative, Native UIKit-based or Native SwiftUI-based]
Clarity Version [e.g. 2.0.0]

Additional Context
Add any other context about the problem here. e.g. Nature of the issue (consistent or intermittent) or noticeable patterns

A fix should be released with our next version, so please stay tuned.

UIGraphicsBeginImageContext is deprecated at 17.0 or later, crash at iOS 17.0 or later, when size is zero.
UIKIT_EXTERN void     UIGraphicsBeginImageContext(CGSize size) API_DEPRECATED("Replace usage of UIGraphicsBeginImageContext with UIGraphicsImageRenderer.", ios(2.0, API_TO_BE_DEPRECATED), visionos(1.0, API_TO_BE_DEPRECATED));

Thanks @GitHubYhb for reporting the issue. Could you please provide more details to help expedite our troubleshooting?
Describe the Bug A clear and concise description of what the bug is.
Repro Steps If applicable, steps to reproduce the behavior.
Screenshots If applicable, add screenshots to help explain your problem.
Project Info If this is an issue happening in a specific Clarity project,

Project ID

Platform/Framework Info

Device: [e.g. iPhone 13 Pro]
OS: [e.g. iOS 17.5]
Application Framework [e.g. ReactNative, Native UIKit-based or Native SwiftUI-based]
Clarity Version [e.g. 2.0.0]

Additional Context Add any other context about the problem here. e.g. Nature of the issue (consistent or intermittent) or noticeable patterns

Bug
UIGraphicsBeginImageContext is deprecated at iOS 17.0 or later, crash when size is zero.
Project ID
nfxf04najx
Platform/Framework Info
OS: iOS 17 or later
Application Framework : Native
Clarity Version : cocoapods version is  Clarity (0.2.0)

The issue should be fixed if you upgrade to Clarity v2.1.0.


Set default value to NULL

Hi, @Oros42 Can you please merge my PR changes? because the default value in raw SQL shouldn't be there. Thanks!

Hello
I think we can comment the INSERT and not remove.
In this way, it can help developer to understand the content of imsi's table.
Can you make the change ?
Thank you

Hello I think we can comment the INSERT and not remove. In this way, it can help developer to understand the content of imsi's table. Can you make the change ? Thank you

@Oros42 done,


[Bug] The Troke drawing doesn't look good in the html canvas

I have an option for getStroke but the resulting stroke doesn't feel smooth.
const options = {
  size: 3,
  thinning: 0.2,
  smoothing: 1,
  streamline: 0.1,
  easing: (t) => t,
  start: {
    taper: 0,
    easing: (t) => t,
    cap: true,
  },
  end: {
    taper: 10,
    easing: (t) => t,
    cap: true,
  },
};

My canvas have
width={440} ; height={220}
Can you help me make it more beautiful?

Same issue in Svelte as well

try to use high DPI canvas
const width = 500;
const height = 500;
const scale = window.devicePixelRatio || 2;

<canvas width={width * scale} height={height * scale} style={{ width: width, height: height }}></canvas>


Service IP family must match public address family

Environmental Info:
K3s Version: v1.24.4+k3s1 (c3f830e9)
go version go1.18.1

Node(s) CPU architecture, OS, and Version:

aarch64 and amd64, all running Ubuntu 22.04.
Cluster Configuration:

1 server, 4 agents
Describe the bug:
Unable to set the default IP family to be IPv6.
Steps To Reproduce:

Installed K3s: Using k3s-ansible role.

Server systemd unit:
[Unit]
Description=Lightweight Kubernetes
Documentation=https://k3s.io
Wants=network-online.target
After=network-online.target

[Service]
Type=notify
ExecStartPre=-/sbin/modprobe br_netfilter
ExecStartPre=-/sbin/modprobe overlay
ExecStart=/usr/local/bin/k3s server --disable-kube-proxy --config /etc/rancher/k3s/config.yaml
KillMode=process
Delegate=yes
LimitNOFILE=1048576
LimitNPROC=infinity
LimitCORE=infinity
TasksMax=infinity
TimeoutStartSec=0
Restart=always
RestartSec=5s

[Install]
WantedBy=multi-user.target

Server config:
cluster-cidr: fddf:f7bc:9670::/48,<IP_ADDRESS>/16
disable:
- flannel
- traefik
- servicelb
- metrics-server
- local-storage
disable-cloud-controller: true
disable-network-policy: true
docker: false
etcd-expose-metrics: true
flannel-backend: none
kube-controller-manager-arg:
- 'bind-address=::'
kube-scheduler-arg:
- 'bind-address=::'
kubelet-arg:
- feature-gates=GracefulNodeShutdown=true
- feature-gates=MixedProtocolLBService=true
node-ip: 2001:67c:1104:e08d:e89b:6305:d07e:123e,<IP_ADDRESS>
service-cidr: 2001:67c:1104:fdb::/112,<IP_ADDRESS>/16
tls-san:
- <IP_ADDRESS>
- 2001:67c:1104:e08d:e89b:6305:d07e:123e
write-kubeconfig-mode: '644

Expected behavior:
It would not error out.

Actual behavior:
It errors out on server, with an error about IP family must match.

Additional context / logs:
Aug 31 00:20:48 k8s-master1 k3s[32999]: Error: error creating bootstrap controller: service IP family "2001:67c:1104:fdb::/112" must match public address family "<IP_ADDRESS>"
Aug 31 00:20:48 k8s-master1 k3s[32999]: time="2022-08-31T00:20:48+03:00" level=fatal msg="apiserver exited: error creating bootstrap controller: service IP family \"2001:67c:1104:fdb::/112\" must match public address family \"<IP_ADDRESS>\""

This appears to be an error somewhere in the core Kubernetes apiserver code. I suspect there's some additional argument that you'll need to pass to kube-apiserver to properly order the endpoint addresses to match the rest of the addresses you're using.

That's indeed a bug in upstream Kubernetes: https://github.com/kubernetes/kubernetes/issues/111671
Current workaround is to specify manually the advertise-address for apiserver to match.

Current issue is that the internal API k8s svc is not serving the certificate with the IP address of svc.
CoreDNS inside cluster:
WARNING] plugin/kubernetes: Kubernetes API connection failure: Get "https://[2001:67c:1104:fdb::1]:443/version": x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, 2001:67c:1104:e08d:e89b:6305:d07e:123e, ::1, not 2001:67c:1104:fdb::1

Thanks for bringing this issue up. I am closing this issue as it has been identified as being tracked upstream.


[Feature request] (match the game's) Field Of View

Just wanna say, thank you so much for sharing this tool. Improvement in VR presentation performance over Katanga is night and day (EDIT: at least with the default settings, cuz I learned it should be configured properly for a fair comparison), just wish it was merged with Katanga's features into HelixVision and other mirroring tools like VHT (whose dev sounds interested by the way).
Anyhow, I'm not a VR expert, but in my opinion, a screen in VR should take up as much of the player's FOV as the game's rendering FOV (or viceversa), so that surround sound/3D spatial audio is aligned with the visuals: sounds should be heard coming from the direction we see the object making the sound. This is the norm in spatial/ambisonics audio in 360 videos, but rarely an option with monitors because you'd need to be too close and stay within the sweetspot.
For example, if I'm using this tool right, to get a virtual screen that's 2m away (average HMD focal distance) to take up 60° of my horizontal FOV (2 x α, common game FOV), it should be 2.3094m (2 x 1.1547) wide, which would result in this launch command, which perhaps could be the default:
vr-screen-cap.exe --distance=2 --scale=2.3094

and would look like this:

Though on my Reverb G2, it takes up just enough space for me to see the entire frame at all times, but higher FOVs of modern games (90, 100, 103, etc) would probably take up the entire HFOV and then some.
This could be a simple way to make the FOVs match, but I think it would be better to specify distance + FOV and let VRScreenCap also apply the curvature needed for the screen to wrap around a section of the FOV sphere

or perhaps curve away from the viewer to compensate for barrel distortion? Again, I'm not an expert but I guess that also depends on the projection used by the engine.

Thanks for this - it is really helpful.


As Mary, I want to set up notifications for recalls I am interested in so that I receive automated updates without the need to come back to the site all the time

Interaction along the following lines:

Mary navigates to the recall site (URL?)
Mary enters key words for selected food e.g Lettuce, Ice Cream or ALL

This user story has an impediment from the business side. The API documentation for the food enforcement reports (https://open.fda.gov/food/enforcement/reference/) states: "This data should not be used as a method to collect data to issue alerts to the public, nor should it be used to track the lifecycle of a recall."
My interpretation is that the application should not allow subscription to alerts and therefore block this user need.
Alternatively a link to a site (need research) that allows subscriptions of that kind could be added.

Determined that API does not support this request.  Remove from backlog and close


feat: Set custom name to the app image

Checklist

[x] I didn't over-scope my PR
[x] My PR title matches the commit convention
[x] I did not include breaking changes
[ ] I included unit tests that cover my changes
[ ] I added/updated the documentation about my changes
[x] I made my own code-review before requesting one

Description of the changes
Add app image name customisation.
Add lenra.yml possibility to set the image name and tag in the dev config.
Set a default image name with the directory name and the tag with the git current branch: lenra/app/<current-dir>:<current-branch>

This was fixed in this PR: https://github.com/lenra-io/lenra_cli/pull/14/files#diff-2e9d962a08321605940b5a657135052fbcef87b5e360662bb527c96d9a615542L32


ValueError: unknown locale: UTF-8

Hi,
I just tried using your Jekyll plugin, but I get an error about unknown locale.
Traceback (most recent call last):
  File "/Users/hiphish/Developer/feeling-responsive/_plugins/jekyll-rst/rst2html.py", line 25, in <module>
    from transform import transform
  File "/Users/hiphish/Developer/feeling-responsive/_plugins/jekyll-rst/transform.py", line 2, in <module>
    from docutils.core import publish_parts
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/docutils/core.py", line 20, in <module>
    from docutils import frontend, io, utils, readers, writers
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/docutils/frontend.py", line 41, in <module>
    import docutils.utils
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/docutils/utils/__init__.py", line 20, in <module>
    import docutils.io
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/docutils/io.py", line 18, in <module>
    from docutils.utils.error_reporting import locale_encoding, ErrorString, ErrorOutput
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/docutils/utils/error_reporting.py", line 47, in <module>
    locale_encoding = locale.getlocale()[1] or locale.getdefaultlocale()[1]
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/locale.py", line 543, in getdefaultlocale
    return _parse_localename(localename)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/locale.py", line 475, in _parse_localename
    raise ValueError, 'unknown locale: %s' % localename
ValueError: unknown locale: UTF-8

I have docutils and Pygments installed via pip, otherwise the traceback would not have found them. If I remove the frontmatter from my reST file the error goes away, but it doesn't get compiled obviously. Do you have any idea what is going on?

This seems to be a general problem with Python on OS X. The solution is to run the following two lines first:
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8

I don't want to run them every time, so I put them in a file called ~/.bash_profile. Run source ~/.bash_profile to get the effect without logging out and back in.
The issue can be closed now, the plugin works.


Implement hidden field

Note: rebased on #161
Pre-Flight checklist

[x] Testing

[x] Code is tested
[x] Changes have been manually tested

What are the relevant tickets?
Fixes #163
What's this PR do?
Implements a hidden field
How should this be manually tested?
Run ./manage.py override_site_configs. Add a new piece of site metadata. In the network tab you should see a parameter hidden with the value hidden-value-here in the metadata dict.

@noisecapella looks like this PR also includes an implementation for https://github.com/mitodl/ocw-studio/issues/159?


Fix memory leaks when using Slack Image Picker Type

We have some memory leaks here
https://github.com/hoangtaiki/ChatViewController/issues/12#issuecomment-615480550
I removed request ph photo authorization when ChatViewController is initiated. It will only request when user clicks Image Gallery button

This PR will address issue #10 #12


build: bump packages to preview 6

:x: Build TheIdServer 1.0.2564 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/e1bae3400a by @)

:x: Build TheIdServer 6.3.1-user-ole1-0096 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/b6786bba0a by @)

:x: Build TheIdServer 6.3.1-user-ole1-0097 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/6f179762aa by @)

:x: Build TheIdServer 1.0.2567 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/63cd92c175 by @)

:x: Build TheIdServer 6.3.1-user-ole1-0099 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/d2a18d9ad9 by @)

:x: Build TheIdServer 6.3.1-user-ole1-0104 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/769ec4c931 by @)

:x: Build TheIdServer 6.4.0-user-ole1-0125 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/511ab0af9f by @)

:x: Build TheIdServer 6.4.0-user-ole.1+125.build.2598 failed (commit https://github.com/Aguafrommars/TheIdServer/commit/511ab0af9f by @)

:white_check_mark: Build TheIdServer 6.3.1-user-ole1-0126 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/8d8e5c6c34 by @)


chore: turn off failing synapse tests temporarily

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

/azp run

Codecov Report

Merging #1658 (2fa29f1) into master (76d7382) will decrease coverage by 5.37%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1658      +/-   ##
==========================================
- Coverage   82.06%   76.69%   -5.38%
==========================================
  Files         272      272
  Lines       14230    14230
  Branches      739      739
==========================================
- Hits        11678    10913     -765
- Misses       2552     3317     +765

Impacted Files
Coverage Δ

.../execution/streaming/continuous/HTTPSourceV2.scala
0.00% <0.00%> (-92.09%)
:arrow_down:

...che/spark/sql/execution/streaming/HTTPSource.scala
0.00% <0.00%> (-90.00%)
:arrow_down:

...ql/execution/streaming/continuous/HTTPSinkV2.scala
0.00% <0.00%> (-89.75%)
:arrow_down:

...ql/execution/streaming/DistributedHTTPSource.scala
0.00% <0.00%> (-78.34%)
:arrow_down:

...e/synapse/ml/cognitive/FormRecognizerSchemas.scala
7.69% <0.00%> (-76.93%)
:arrow_down:

...ure/synapse/ml/cognitive/FormOntologyLearner.scala
14.28% <0.00%> (-75.52%)
:arrow_down:

.../synapse/ml/cognitive/AnomalyDetectorSchemas.scala
33.33% <0.00%> (-66.67%)
:arrow_down:

...om/microsoft/azure/synapse/ml/io/IOImplicits.scala
10.16% <0.00%> (-61.02%)
:arrow_down:

...he/spark/sql/execution/streaming/ServingUDFs.scala
0.00% <0.00%> (-52.95%)
:arrow_down:

...ft/azure/synapse/ml/cognitive/TextTranslator.scala
33.33% <0.00%> (-52.06%)
:arrow_down:

... and 44 more

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

/azp run


Error in path to 'WEIGHTS_PATH' and 'CONFIG_PATH'

It's giving error like this : Vehicle-Counting-master/detectors/yolo/yolo_detector.py", line 20, in get_bounding_boxes
net = cv2.dnn.readNet(os.getenv('WEIGHTS_PATH'), os.getenv('CONFIG_PATH'))
cv2.error: OpenCV(4.1.0) /io/opencv/modules/dnn/src/dnn.cpp:3780: error: (-2:Unspecified error) Cannot determine an origin framework of files:  in function 'readNet'
Please help me to resolve this

Please refer to the Notes section of the README. You need to create an environment file for YOLO and specify the paths to a weights and config file.


Add a hook for scanning

I did not test this but the linter didn't complain and I don't see how this could not work

Would it be possible to rename the hook to something like ACF_PreBeginScanning?


Convert Starter Packs into Lists

Describe the Feature
A nice feature to have is a way to easily convert a starter pack into a list using a button like the "Follow All" on the top of the pack page (see image).
I think lots of people don't want to follow every account in a starter pack, and cherry picking accounts to follow or to manually add to a list is tedious.
In my case, I like to add accounts associated to a subject to a list and scan that list for a while and then decide to cherry pick some accounts that create interesting content.
Hope my 2 cents of an idea can make the starter pack feature even more functional.
Kudos!
Attachments

Describe Alternatives
No response
Additional Context
No response

an even better version than "convert to list" would be to have "add to list" option from a starter pack. this covers the "convert to list" use case, but also allows more flexibility in list management.

Honestly why are these two separate things in the first place? At the core they are identical - a collection of users. In the starter pack you can even look at the posts like a list.
Just make it so that you can either follow as a list, or follow all the accounts within.

Same concept, different wording, right? The final objective is to have the option to follow some/all users or add them easily to a new/existing list.

Yeah I guess what this implies is that a Starter Pack should be a List plus a list of Feeds, where a List is a set of Accounts. Then you could just have an option to take a Starter Pack's List, or create a Starter Pack from a List (with an empty set of Feeds)

I think that, if one takes the notion that users should be editing and
curating their own lists, then the semantics of "take a Starter
Pack's List" should be "add all the accounts in it to a list" rather than
"convert it to a user-list" (and similarly, when a user "takes" a list from
another user, they should have the ability to "add all accounts" to their
own list, rather than just duplicate the list).
On Mon, Nov 11, 2024 at 7:18 PM Joel Barciauskas @.***>
wrote:

Yeah I guess what this implies is that a Starter Pack should be a List
plus a list of Feeds, where a List is a set of Accounts. Then you could
just have an option to take a Starter Pack's List, or create a Starter Pack
from a List (with an empty set of Feeds)
—
Reply to this email directly, view it on GitHub
https://github.com/bluesky-social/social-app/issues/5970#issuecomment-2468674622,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADRLNAINQNYNQHWJPNV7MD2ADRHXAVCNFSM6AAAAABQXC2QXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGY3TINRSGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Starter Packs have both a group of Accounts and Feeds.

What’s the difference between a feed (within a starter pack) and a list? All I see is a list of recent posts by those users, which is exactly the same whether it’s a list or a feed in a starter pack.

is there a known way to turn a list into a starter pack?

is there a known way to turn a list into a starter pack?

https://nws-bot.us/bskyStarterPack.php

This is similar to #5940 but has had more discussion, so perhaps it should be merged in here.

@joaomendoncaa Great work on getting this going! Please take a look at #5932, I tried to think a lot about reusing existing UI concepts there.
I later added the part about doing the same for Lists, so that Lists can be combined... however, focusing on the just Starter Packs would be great at first!

An random user here with a use case. I find lots of interesting starter packs that I want to add to a pinned list on my home page. I have to subscribe to the accounts in the starter pack and then go to the list of people I am subscribed to and individually move them to the pinned list. I would like for example to have a pinned feed on my home page with lists of related scientists from different starter packs combined. In my case this is different starter packs of microbiologists from slightly different fields. I could do the same with a feed on Astronomy and astrophysics or Public health and infectious disease doctors.

Yes, your scenario would cover my case. I do take the point that others
have made that packaging an object as a "startup pack" and publishing it in
the way that is currently being used is also a useful tool. Thanks for your
response.
On Fri, 22 Nov 2024 at 10:26, João Mendonça @.***>
wrote:

An random user here with a use case. I find lots of interesting starter
packs that I want to add to a pinned list on my home page. I have to
subscribe to the accounts in the starter pack and then go to the list of
people I am subscribed to and individually move them to the pinned list. I
would like for example to have a pinned feed on my home page with lists of
related scientists from different starter packs combined. In my case this
is different starter packs of microbiologists from slightly different
fields. I could do the same with a feed on Astronomy and astrophysics or
Public health and infectious disease doctors.
If I understood your request correctly, the remaster of these features I
referred to here
https://github.com/bluesky-social/social-app/issues/5970#issuecomment-2481244721
makes this easily possible.
In this new design, starter packs would cease to exist, and people would
just make Lists of Accounts or Lists Feeds, and you'd be able to simply:

open a List of Accounts
add its members to another List of yours
pin that List to home

—
Reply to this email directly, view it on GitHub
https://github.com/bluesky-social/social-app/issues/5970#issuecomment-2493423466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BMKGWAKLL5AV4LXGBMT7H2T2B4BEBAVCNFSM6AAAAABQXC2QXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTGQZDGNBWGY
.
You are receiving this because you commented.Message ID:
@.***>

I was also missing this feature so I decided to make a small web tool for it until there is an official solution - pinkdawn.app.
Feel free to ping me on Bluesky @oloflovesai.bsky.social if you have any questions!

Tonight I discovered that @sbm12 has created a tool for doing this: https://github.com/sbm12/bsky-Pack2List

An random user here with a use case. I find lots of interesting starter packs that I want to add to a pinned list on my home page. I have to subscribe to the accounts in the starter pack and then go to the list of people I am subscribed to and individually move them to the pinned list. I would like for example to have a pinned feed on my home page with lists of related scientists from different starter packs combined. In my case this is different starter packs of microbiologists from slightly different fields. I could do the same with a feed on Astronomy and astrophysics or Public health and infectious disease doctors.

While I agree this would be useful as an internally developed resource I've got a tool that combines lists, so you can do it now while waiting for the core dev to make it available: https://nws-bot.us/bskyListCombiner.php. One of several bits on my collection of tools here: https://github.com/sbm12/bsky-Pack2List.

Hey all, I made a UserScript for TamperMonkey which can do this directly from the starter pack page.
https://github.com/user-attachments/assets/858fbd65-d3b1-4ed8-bfd3-2673070242e6

I used @b0o script successfully.  Good job boo. What's the difference between using TamperMonkey and the other various and sundry methods of interacting with bluesky?

I used @b0o script successfully. Good job boo. What's the difference between using TamperMonkey and the other various and sundry methods of interacting with bluesky?

Only lack of guardrails, essentially. Unlike OAuth or app passwords, TamperMonkey scripts and browser extensions can modify your access credentials. Browser extensions have some level of review (not much), while with TamperMonkey you really need to be sure you understand what it's doing and that it isn't able to run remote code in some manner.


fix(state): restart service when configuration has changed

PR progress checklist (to be filled in by reviewers)

[ ] Changes to documentation are appropriate (or tick if not required)
[ ] Changes to tests are appropriate (or tick if not required)
[ ] Reviews completed

What type of PR is this?

Primary type

[ ] [build]    Changes related to the build system
[ ] [chore]    Changes to the build process or auxiliary tools and libraries such as documentation generation
[ ] [ci]       Changes to the continuous integration configuration
[ ] [feat]     A new feature
[x] [fix]      A bug fix
[ ] [perf]     A code change that improves performance
[ ] [refactor] A code change that neither fixes a bug nor adds a feature
[ ] [revert]   A change used to revert a previous commit
[ ] [style]    Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)

Secondary type

[ ] [docs]     Documentation changes
[ ] [test]     Adding missing or correcting existing tests

Does this PR introduce a BREAKING CHANGE?

No.
Related issues and/or pull requests

Describe the changes you're proposing

Pillar / config required to test the proposed changes

Debug log showing how the proposed changes work

Documentation checklist

[ ] Updated the README (e.g. Available states).
[ ] Updated pillar.example.

Testing checklist

[ ] Included in Kitchen (i.e. under state_top).
[ ] Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
[ ] Updated the relevant test pillar.

Additional context

:tada: This PR is included in version 0.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

Thanks @n-rodriguez.  While this isn't mentioned there, it fits in with fixing https://tree.taiga.io/project/myii-saltstack-formulas/task/182.


Color inconsistency in debug view

Background color of the stack entries are in consistent, it has the same background color as Dracula theme.

Hi @gayanper, this is the same problem described in #67, please see my comment and the follow-up conversation that provides information about the problem and how to solve it on your side. As a theme author there is actually no way to fix this and it must be resolved within the JetBrains theme API itself.

Duplicate of #67


too many node disconnected message

when upgrade kafka-clients from 3.0.1  to  3.1.1, there are a lot of "Node 0 disconnected" message per day per listener(20-30k)
think it is introduced by
https://github.com/a0x8o/kafka/commit/cf22405663ec7854bde7eaa3f22b9818c276563f
questions:

is it normal with so many "Node X disconnected" message?
it mentioned a back-off configuration to reduce the message, how to implement it?

created at https://issues.apache.org/jira/browse/KAFKA-14080


Rename videoragqna to videoqna to align with other examples

Description
As per request from OPEA technical forum, rename videoragqna to videoqna to align with other examples
Issues
List the issue or RFC link this PR is working on. If there is no such link, please mark it as n/a.
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)
[x] Others (enhancement, documentation, validation, etc.)

Dependencies
N/A
Tests
test_reranks_videoqna.sh
test_service_orchestrator_with_videoqnagateway.py

@chensuyue For this CI error, I will request another PR in GenAIExamples to update this referred line, is that ok?

Per OPEA's request on technical forum, we need to rename the usecase to align with others. So I raised one PR in each repo. This one is dependency for https://github.com/opea-project/GenAIExamples/pull/798 @lvliang-intel @kevinintel @chensuyue  @XuhuiRen Please help to review and merge, thanks.
@ttrigui FYI


Implement Scrubbing

We would like to make it easy to scrub private information (e.g. PII/PHI):
python -m puterbot.scrub

Dear @abrichr,
I would like to work on implementing this issue. Just to confirm, my understanding is that we need to scrub private information from the input text such as:

Date of Births
Phone Numbers
Bank Card Numbers
Email Addresses

Please let me know if there are any additional requirements or specifications that I should consider while implementing the solution.

Excellent, thank you Krish! These are the top Google results for [pii python], this looks promising, please start here:
https://pypi.org/project/piicatcher/
https://pypi.org/project/pii-extract/
Here is a Phind.com search that may be insructive:
https://www.phind.com/search?q=how to implement a PII%2FPHI scrubber in python for text and images%3F we already have OCR available&c=&source=searchbox
Please provide a few options and tradeoffs for each.
💪 let's do this 💪

Phind.com recommends https://github.com/microsoft/presidio. After a glance it seems the top candidate (please let me know if you identify any other candidates worth comparing).
In your analysis please include a short description of the available APIs, e.g. function signatures, data sources/formats.
Thank you!!

Here's my analysis of the three options you've mentioned for implementing a PII/PHI scrubber in Python, along with their tradeoffs:
piicatcher:

piicatcher is a Python package for detecting personally identifiable information (PII) in text using regular expressions.
It currently supports the detection of email addresses, credit card numbers, US phone numbers, US Social Security numbers, and IP addresses.
The package is easy to install and use, and it provides a simple API for detecting PII in text.
Tradeoff: it only supports a limited number of PII types, and it relies solely on regular expressions for detection, which can result in false positives or missed detections.
Sample Usage API:
• Function Signature:
def catch(text: str, include_pattern_names: bool = False) -> List[str]:
• The function takes in a string of text as input and returns a list of PII entities detected in the text.

pii-extract:

pii-extract is a Python package for extracting PII from text using machine learning models.
It supports the extraction of various types of PII, including email addresses, phone numbers, credit card numbers, and dates of birth.
The package is easy to install and use, and it provides a simple API for extracting PII from text.
Tradeoff: it requires a training set of labeled data to build the machine learning models, and the quality of the extraction depends on the quality of the training data.
Sample Usage API:
• Function Signature:
def extract_entities(text: str) -> List[Dict[str, str]]:
• The function takes a string of text as input and returns a list of PII entities extracted from the text.
• The output is a list of dictionaries, where each dictionary represents a single PII entity and contains the following fields: entity_type, entity_value, start, and end.
• The entity_type field represents the type of PII entity detected (e.g., "EMAIL_ADDRESS", "PHONE_NUMBER", etc.), and the entity_value field represents the value of the entity detected.

Presidio:

Presidio is an open-source Python package for detecting and anonymizing PII in text and images using machine learning models.
It supports the detection and anonymization of various types of PII, including names, addresses, phone numbers, email addresses, credit card numbers, and social security numbers.
The package provides a comprehensive set of APIs for detecting and anonymizing PII, and it can be easily integrated into existing workflows.
Tradeoff: it requires a training set of labeled data to build the machine learning models, and the quality of the detection and anonymization depends on the quality of the training data.
Sample Usage APIs:
• analyze_text: a function that takes a string of text as input and returns a list of PII entities detected in the text. The function has the following signature:
def analyze_text(text: str, language: str = "en", score_threshold: float = 0.5) -> List[Entity]
• anonymize_text: a function that takes a string of text and a list of PII entities as input and returns the text with the PII entities anonymized. The function has the following signature:
def anonymize_text(text: str, entities: List[Entity], replacement_str: str = "<PII>") -> str
• analyze_image: a function that takes an image as input and returns a list of PII entities detected in the image. The function has the following signature:
def analyze_image(image: Union[bytes, str, IO]) -> List[Entity]
• anonymize_image: a function that takes an image and a list of PII entities as input and returns the image with the PII entities anonymized. The function has the following signature:
def anonymize_image(image: Union[bytes, str, IO], entities: List[Entity], replacement_color: Tuple[int, int, int] = (0, 0, 0)) -> bytes
• The Entity class represents a single PII entity and contains the following fields: entity_type, start, end, and score.
• The entity_type field represents the type of PII entity detected, and the start and end fields represent the start and end indices of the entity in the input text or image.
• The score field represents the confidence score of the detection.

Overall, I agree with your view point, that is, we should use "Presidio".
My Reasoning:

It provides a wide range of APIs for detecting and anonymizing PII/PHI in both text and images, and supports a variety of languages and entity types.

Presidio also offers advanced features such as custom entity recognition patterns, contextual analysis, and entity linking, which can help improve the accuracy and coverage of PII detection.

Please also consider where in the existing PuterBot code this should be implemented. Some options:

before recording
before visualizing
before modelling/replay
before sharing

Analysis:

before recording:
It would not benefit to Scrub before Recording, as we will have the ocr text generated only after the recording. Hence, we can rule out this option.

before visualizing:
In my opinion, we should Scrub the text before visualizing as it will help to visualize the data without exposing the sensitive information.

before modelling/replay:
In my opinion, we should Scrub the text before modeling/replay as it will help to model/replay the data without exposing the sensitive information.

before sharing:
In my opinion, implementing scrubbing before sharing is the most critical step for protecting privacy and ensuring compliance with data protection regulations.

BUT, scrubbing at multiple stage may be time consuming. I would recommend implementing scrubbing at the earliest possible stage where it can be effectively applied ONCE, and then it may be reused by any other stage/requirement.

I agree that we should scrub at the earliest possible stage. How about at the top of process_event?

I agree, we can provide with this idea. BUT,
We would need the text for scrubbing. Will it be something like,
text = event.text #Accessing the InputEvent's ._text attribute
scubbed_text = scrub(text)
Then, we need to set the new scrubbed text back to the event's _text attribute.
So, we need to add a new setter method in models.py under the InputEvent class.
Please correct me if my approach is incorrect.

Hi @KrishPatel13 , on further consideration, there are different types of scrubbing we need to implement depending on the event:

write_screeen_event should scrub image data
write_window_event should scrub text data from window titles and window state (work in progress, https://github.com/MLDSAI/puterbot/issues/75)
write_input_event is trickier because a single input event may not contain PII (e.g. the letter "b"), but a sequence of them will (e.g. the sequence "bob smith")

InputEvents are merged in get_consecutive_keyboard_events. This logic is nontrivial and currently incomplete, and may run several times before everything is merged.
The merging process is completed after the process  loop is completed in get_events. This is probably the better place to implement scrubbing of InputEvents.
Eventually we will want to save the processed events to new tables, which are ultimately what will be published (https://github.com/MLDSAI/puterbot/issues/46). This creation of new tables has not been implemented yet, and ideally should be implemented as part of this work, perhaps as a separate PR.

@abrichr
write_screeen_event should scrub image data
I am a bit unsure for the approach here. This is because, the given a binary string of png_data. If we want to scrub it,
We will need to decode using base64 and then scrub the text. Then again encoding to the png_data.
Please let me know if this approach is correct?

My Progress:
Before:

After:

@abrichr
Ready for Review! My PR


Setup Airbrake for your JavaScript application

Install Airbrake in 2 easy steps:
Step 1: Add the library
Include via CDN:
<script src="https://cdnjs.cloudflare.com/ajax/libs/airbrake-js/1.0.4/client.min.js"></script>

We also support installation via npm and Bower.
Step 2: Copy this config snippet to your app.js file
(You can find your project ID and API KEY with your project's settings):
var airbrake = new airbrakeJs.Client({
  projectId: <Your project ID>,
  projectKey: '<Your project API Key>'
});
airbrake.addFilter(function (notice) {
  notice.context.environment = 'production';
  return notice;
});

To test that Airbrake has been installed correctly in your JavaScript project, just open up the JavaScript console in your internet browser and paste in:
airbrake.notify('hey there!')

Visit official GitHub repo for more info on alternative configurations and advanced options.

Done in a3f3881b47ee9afa8e1b089033925aca0d750760


cmake: bluetooth: Don't #include gatt files from src files

Due to a bug in KBuild, bluetooth samples needed to #include the gatt
sources to re-use code between samples. This bug was not ported to
CMake so we can stop applying this workaround.
gatt source files are now directly added to the 'app' library instead
of having adapter source files in the app's src directory that
#include's the gatt files.
Signed-off-by: Sebastian Bøe<EMAIL_ADDRESS>

Codecov Report

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

@@           Coverage Diff           @@
##           master    #8362   +/-   ##
=======================================
  Coverage   64.53%   64.53%
=======================================
  Files         422      422
  Lines       40280    40280
  Branches     6799     6799
=======================================
  Hits        25993    25993
  Misses      11165    11165
  Partials     3122     3122

Continue to review full report at Codecov.

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


feedback after testing the testnet

no bugs
swaps,adding of liquidity,removing liquidity, staking lp, checking pools,
all the features presented in the testnets are perfect, didn't detect any bugs at all.
0xafcb1A9f66041D7ec5823D7746CD135b5E7F1F21

@lancecruxx Thank you for your testing and we hope to continue delivering high quality features and improvements!


Failure of select functions on large inputs.

I noticed an issue with GEQR and GESDD (specifically, AllVec and SomeVec options) failing when running on matrices of large sizes ( >=<PHONE_NUMBER> entries, double precision).
The failure error reported is "std::bad_array_new_length."
We are using Intel MKL 2023.02, running on Intel Xeon Gold 6248R, and have 1.5 TB RAM available for us.
The runs are performed in the context of RandLAPACK library, but I've isolated the calls to these particular routines in separate benchmarks, so there is no external interference that might be causing this failure.
I will report if I find out anything else.

2048000000 is getting close to the 2^31 =<PHONE_NUMBER> limit for 32-bit integers. What m, n are you using?
LAPACK++ takes 64-bit integers, but the underlying library may be taking 32-bit integers. How are you specifying the MKL library variant to link with at configure time? Did you set blas_int = int64?

2 048 000 000 is getting close to the 2^31 = 2 147 483 648 limit for 32-bit integers. What m, n are you using?
LAPACK++ takes 64-bit integers, but the underlying library may be taking 32-bit integers. How are you specifying the MKL library variant to link with at configure time? Did you set blas_int = int64?

I've encountered this issue when running GEQR with 1,000,000 rows and 2,048 columns; also, when running GESDD with 100,000 rows and 100,000 columns.
Prior to building the libraries, I specified MKL via:
export MAIN_MKL_LIBS="/nfs/home/mmelnic1/mkl/intel/oneapi/mkl/latest/lib/intel64"
export LD_LIBRARY_PATH="${MAIN_MKL_LIBS}:${LD_LIBRARY_PATH}"
export LIBRARY_PATH="${MAIN_MKL_LIBS}:${LIBRARY_PATH}"

I have not deliberately set blas_int = int64, will try this soon.
But if this was an issue, wouldn't other routines fail at the specified sizes?

If using modules (at least at ICL), module load intel-mkl should add everything to CPATH, LIBRARY_PATH, and LD_LIBRARY_PATH.
Otherwise, Intel provides a tool to setup the environment:
    /path/to/intel/compilers_and_libraries_2020.4.304/linux/bin/compilervars.sh intel64

which further invokes the mklvars.sh script.

Turns out that the issue was indeed in me not using -Dblas_int=int64 when configuring BLAS++ via CMake.
I have tested the aforementioned routines after setting up the libraries properly, all works well now.
We can close the issue.

Turns out that the issue was indeed in me not using -Dblas_int=int64 when configuring BLAS++ via CMake.
I have tested the aforementioned routines after setting up the libraries properly, all works well now.
We can close the issue.


Post request or get Request with huawei devices only Returned bad response statues code 500 always

Package
dio
Version
5.3.3
Operating-System
Android
Output of flutter doctor -v
[✓] Flutter (Channel stable, 3.13.8, on macOS 14.0 23A344 darwin-arm64, locale en-EG)
    • Flutter version 3.13.8 on channel stable at /Users/ahmedelnajar/development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (6 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/ahmedelnajar/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Users/ahmedelnajar/Applications/Android Studio Iguana 2023.2.1
      Nightly.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.8+0-17.0.8b1000.22-10799086)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (version unknown)
    • Android Studio at /Users/ahmedelnajar/Applications/Android Studio Iguana 2023.2.1 Nightly.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to determine Android Studio version.
    • Java version OpenJDK Runtime Environment (build 17.0.8+0-17.0.8b1000.22-10799086)

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 14.0 23A344 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 118.0.5993.96

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Dart Version
3.1.4
Steps to Reproduce
1- add request get or post
2- returned bad response statues code 500
3- with huawei devices only
Expected Result
when add post request  or get
good response statues code 200
and response data returend
with huawei devices only
Actual Result
when add post request or
returned bad response statues code 500
return missing parameter
with  huawei devices only
devices not supported google play but added in huawei store

Please provide a minimal reproducible example, or try with a minimal example on those Huawei devices.


Support aborting and rolling back incomplete upgrade

This adds limited support for aborting an ongoing upgrade and rolling back the
system.
For example:

System is on version v0
System has started rolling out v1, where some zones have completed upgrading
We discover that v1 is severely broken and we need to halt the upgrade, and
downgrade any infrastructure that has completed upgrading

Merge with internal PR.
@jonmv

Can you review this, @freva? I think Jon M. is OOO.


MM-T702 Edit to invalid URL

This PR validates that an error message appears when the user tries to edit a slash command's url and omits the protocol (https or https). This test:

creates a slash command with an http url
edits the url field and removes the 'http' transfer protocol
asserts a modal warning appears on clicking Update
asserts an error message appears after confirming the modal warning
adds an https protocol url and saves, removing warning
edits the url field and removes the 'https' transfer protocol
asserts a modal warning appears on clicking Update
asserts an error message appears after confirming the modal warning
adds an http protocol url and saves, removing warning

vercel
TM4J - could not find a test-case

Hello @MikeworX,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


Make error

gcc -Wall -Ofast  -c dekryptize.c -o dekryptize.o
dekryptize.c:8:20: fatal error: curses.h: No such file or directory
#include <curses.h>
^
compilation terminated.

Do you have the ncurses development headers installed?
sudo apt-get install libncurses5-dev
or
sudo yum install ncurses ncurses-devel

that fixed it...
Thank you


Support sovereign cloud deployment.

Problem:
Current version doesn't support sovereign cloud deployment only for Azure global.
Solution:
Add a command line parameter AzureName to specify which Azure cloud will be deployed to. Meanwhile, make TES service can be run at any Azure cloud which already deployed AKS feature.

I have submitted a PR for supporting sovereign cloud.

We created a PR to support sovereign cloud deployment.


Autocomplete for callout types

(Note: I also created this as a feature request for Obsidian itself, but I figured if it doesn't get added to the core, it could be a nice addition to this plugin: https://forum.obsidian.md/t/autocomplete-for-callout-types/39865)
Use case or problem
When using callouts it would be nice if the supported callout types were shown in an autocomplete dropdown list.
Proposed solution
As I start typing the callout syntax (eg. > [!) an autocomplete dropdown would show up, allowing me to select one of the supported callout types (note, abstract, etc)

This feature has already been implemented in Admonitions. Is it not working for you?
you do have to type 1 character after the !

The problem however is that you have to know one letter already, it cannot be used to show a list of all possible types. (The autocompletion only suggests types which include the letter you have typed.)

it cannot be used to show a list of all possible types

If it did, that would definitely be ideal.

@0xdevalias @Cito I just implemented this

@valentine195 Amazing, thanks! :)

@valentine195 Awesome, thank you! That was quick!

This feature has already been implemented in Admonitions. Is it not working for you?
you do have to type 1 character after the !

sorry for asking, can you specify plugin version where it was implemented?
seems that 9.3.3 doesn't have such feature


How to run tests without watch mod?

I have been added test as a precommit hook so I need to run tests without watch mod.

I fixed this by using CI=true npm test


fix li margin on cheerpj.com navbar

The WordPress theme on cheerpj.com adds a bottom margin to all li elements by default, which we don't want

Closing in favour of #105. Probably delete this branch


Rerender with new pins

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

This is likely the best solution here. I'll need to look into proper compiler version migrations.