Face Detection does not work if I move to different tab in the browser

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
No
OS Platform and Distribution
Mac OS
Mobile device if the issue happens on mobile device
No response
Browser and version if the issue happens on browser
Google Chrome Version 111.0.5563.146 (Official Build) (arm64)
Programming Language and version
Javascript (react.js)
MediaPipe version
"@mediapipe/camera_utils": "^0.3.1675466862",     "@mediapipe/drawing_utils": "^0.3.1675466124",     "@mediapipe/face_mesh": "^0.4.1633559619",
Bazel version
No response
Solution
FaceMesh
Android Studio, NDK, SDK versions (if issue is related to building in Android environment)
No response
Xcode & Tulsi version (if issue is related to building for iOS)
No response
Describe the actual behavior
The face mesh work fine if I am on the same tab where the facemesh logic is written, but if I move to the another tab, then I do not get the data from facemesh.

Describe the expected behaviour
It should work irrespective of which tab I am on.

Standalone code/steps you may have used to try to get what you need
const facemesh = new FaceMesh({ locateFile: (file) => `https://cdn.jsdelivr.net/npm/@mediapipe/face_mesh/${file}` });
facemesh.setOptions({
  maxNumFaces: 2,
  minDetectionConfidence: 0.5,
  minTrackingConfidence: 0.5,
  enableFaceGeometry: false
});
facemesh.onResults((result) => {
      console.log("########", new Date().toISOString());
    });
const camera = new Camera(videoElement, {
      facingMode: "user",
      onFrame: async () => {
        await facemesh.send({ image: videoElement });
      },
      width: 120,
      height: 90
    });
    camera.start();

Other info / Complete Logs
######## 2023-04-05T11:15:12.519Z
######## 2023-04-05T11:15:12.554Z
######## 2023-04-05T11:23:54.553Z
######## 2023-04-05T11:23:54.570Z
######## 2023-04-05T11:23:54.595Z
######## 2023-04-05T11:23:54.629Z
######## 2023-04-05T11:23:54.664Z

Hello @krisalay
This is not a bug. This works as per the standard Web APIs because it uses requestAnimationFrame() which is called frequently (60FPS) but it is paused if the tab is not in focus to save resources in the browsers. Please check the comment [here] (https://github.com/google/mediapipe/issues/3977#issuecomment-1377034643) where a user asked for a similar issue.

@ayushgdev If I want to not pause, then is there a way that it can be done?

I don't think so @krisalay . The main motivation for pausing the background activities is to restrict background usage of resources. So not even web workers are allowed to continue running.
In typical scenarios, like if you want to make HTTP calls continuously, developers use a trick. They push dummy notifications which can be listened to by a service worker in the browser and as soon as the notification arrives, they call HTTP APIs.
However, this trick cannot work in the case of webcam since for processing each frame, the call has to be made 60 times per second (or 30 atleast to get a 30FPS output), which is very fast compared to the push notifications the browser can receive.

@ayushgdev So you are saying that it can noway be done?

Yes @krisalay . The trick used is already shared. But it cannot be done in an ideal way.


Have a version for Firefox too

On the TODO list! :)

There we go! :) https://addons.mozilla.org/en-US/firefox/addon/ytcommentblock/
Just remember to change to "Always allow on YouTube.com", since the extension is loaded and runs while you browse.

Also, I'm not sure if YouTube is A/B testing, but they are experimenting with user handles for commenter names (instead of names). In some sense, it's both a good thing and a bad thing: Good because scammers usually advertise in their name (and it is a lot harder to do with ascii characters (vs. emojis, strange characters and so on), but also a bad thing since it makes detection a more difficult in some cases (since only the text can be used in the detection algorithms). Do you also see this change, or is it just me (because on Chrome, I see the names (not handles)?
Either way, the extension still works when blocking link spam and other things, for example:

Before:

After:

@xenova @erkinalp - Please close this issue!


Add ability to plot single node cycles

julia> g = SimpleDiGraph(4)
{4, 0} directed simple Int64 graph

julia> add_edge!(g, 1, 1)
true

julia> g
{4, 1} directed simple Int64 graph

julia> g
{4, 1} directed simple Int64 graph

julia> using GraphMakie

julia> using CairoMakie

julia> graphplot(g)
ERROR: MethodError: no method matching repeat(::Float64; inner=2)
Closest candidates are:
  repeat(::AbstractArray; inner, outer) at abstractarraymath.jl:260
  repeat(::AbstractArray, ::Any...) at abstractarraymath.jl:223 got unsupported keyword argument "inner"
  repeat(::Char, ::Integer) at strings/string.jl:334 got unsupported keyword argument "inner"

Thanks for the report i'll look into this. Unfortunately this won't be a quick fix. I need to add support for curvy lines to draw the self edge. This will allow a lot of nice features but will have implications for the placement of arroheads in DiGraphs and edge labels...

The move to bezier edges will likely take some more time. But the problem is partly solved in<EMAIL_ADDRESS>You won't see the self edges but at least it shouldn't error ^^


Querystring option

#172
Took a stab at adding support for passing in a querystring option parameter.
First contribution to the project and I am still pretty new to Node, so happy to talk over any problems in code.
It got a bit interesting with oAuth, the oAuth code supports pulling its parameters from the body or the querystring, with the querystring taking preference with a basic truthy test. This looked wrong to me, but the change I have made would cause a change in functionality in certain circumstances.
Also included is a js based test runner if you want to point the npm test script at it. Running windows here, so needed something platform agnostic.

the query option should be named qs to match the composable API.
also, it's unsafe to set properties on self.uri because the underlying url parsing library in core is subject to change. it would be better to simply re-compose the url string with the new querystring and reset self.uri to a new url.parse(newurl).
oAuth is dark voodoo that nobody really understands. it's unclear to me how signing should work if both the querystring and form body are present (which is a totally legal HTTP request). i would just leave oAuth alone and once someone is trying to use both querystring arguments and form bodies we can see how different servers react and tweak as necessary.

I'll need to have a think about the self.uri side of things. I want to support appending qs {} values to an existing querystring that was part of the uri.
I'll take a look later tonight after I have a think on it. Spotted a bug as well that I will fix for the next update.

Ok I went away and thought about it a bit. The change is now self contained and much cleaner while still passing all tests.
The only piece I am unhappy with is where it formats then parses the uri object. It feels like too much work for simply merging querystrings.
At this stage I do not see a good work around other than removing the dependency on self.uri as an actual uri object and instead making it our own structure that can be tweaked without the double processing.

the patch looks great now but i'm wondering what the run.js is?
we have a shell script that execs all the tests and can be executed using npm test.

The current script is a bash script. I'm on windows here and it doesn't run. I can drop it from the commit if you like, but thought it might be of interest.

good point.
i'll take it but please remove the bash script, change package.json to use this, and change it to running a static list of files because people tend to keep tests that aren't passing in that directory without checking them in.

Done.
Keep in mind this commit is now behind master a little and there are extra tests that will need to be added to static list in run.js.
Rebase etiquette is something I still am a little unsure of, I read conflicting things about whether I should rebase, merge or leave it to the project owner a this point.

if it merged cleanly i won't rebase, i'll just merge it now and then add the other tests in myself.


CVE 5.0 CVE Portal test login attempt results in 'csClient is undefined'

Attempting to log in with test credentials, fill out information on portal tab, click Login button, error dialog is 'csClient is undefined'. Tried with vulngram.github.io and local standalone server using 0.1.0 branch.
Attempting to record a demo for the November 2 CVE Services workshop.

Could be a caching problem on the browser. Does it happen in incognito mode?
The underlaying scripts were refactored. An old cached script or cookie could bring up error. Few others reported seeing errors, but refreshing/restarting the browser made the problem go away.

Sorry it's working now. I did test in icognito before filing the issue.

FWIW, macos, Firefox private window: can't log in, Chrome private window: can log in.

Firefox doesn't support spawning ServiceWorkers in Private mode https://bugzilla.mozilla.org/show_bug.cgi?id=1320796
Vulnogram uses them to emulate a session to CVE API connection and to share consistent state between browser tabs.
For now it just shows a warning message about browser not having the service workers feature. It needs a better fall-back mechanism.


Add user to group

Not sure if this is the best place to open this, but please could you add the user @tomvaughan77 to the bichard7-next-ui-admin-team in this repo. He has added his MoJ email address to his account.

Hi @bjpirt can you provide Tom's moj email address please and I will send out an invite to become a full org member, then I can add him to the team

Hi @NickWalt01, email is<EMAIL_ADDRESS>

Hi @tomvaughan77 thanks, have sent out an invite, the single sign on doesnt work with the justice email account, but you should still be able get access to GH and set up 2FA


Fix #11

Fix broken links in README.md

Hi! Thanks for PR.
Make sure you have checked points in PR Template correctly.

Can you share the PR template


style: line endings and new prettier rules

This PR adds some rules to .prettierrc and adds a .gitattributes file which hopefully tells Git not to convert line endings on Windows machines.
Also, I fixed some build issues which were introduced the last time around in #80.

Assuming the tests pass, lgtm. They aren't running automatically because you're on a fork instead of a branch in the repo

Assuming the tests pass, lgtm. They aren't running automatically because you're on a fork instead of a branch in the repo

that's annoying, is there any way we can run tests on pull requests before merging them?

Assuming the tests pass, lgtm. They aren't running automatically because you're on a fork instead of a branch in the repo

that's annoying, is there any way we can run tests on pull requests before merging them?

#83 is going to take a look at this, so this pr (#82) can be merged


Update to OAI 3.1 - Reference Object

When using the Reference Object, summary and description fields can now be overridden.

If I read the OAS 3.1.0 draft and its reference to JSON Schema correctly, the behaviour of $ref has changed in general. The old assertion  „Any members other than $ref in a JSON Reference object are ignored“ on references no longer holds true.
JSON Schema now allows overriding values of referenced objects in the referencing object (see <IP_ADDRESS>. Distinguishing Among Multiple Values). And by the compatibility claim, OpenAPI should support that as well now.
Does the current issue #143 cover this change? (Or did I miss something?)
At our company we highly appreciate this spec change and are looking forward to OpenAPI 3.1.0 getting operational, as we'd like to add application-specific metadata to fields.

Hi and welcome,
This is related to JSON Schema 2019-09 update #137 (which is described fuzzily for now).

Having it covered in the 3.1.0 update makes me happy :-).


Differential Privacy example via new Interactive API

It would be great to add Differential Privacy example to our existing tutorials, just to show exact place (ShardDescriptor class), where user need to put DP logic.

Closing this issue, as the Interactive API is being deprecated in favor of Workflow API. In parallel, we have started considering how DP could be more deeply integrated as a feature of OpenFL (rather than just example code).


Nested dialogs in dialog fragment bug?

Hello,
I have one question. I created multiple nested material-dialogs in dialog fragment, I run it and app crash with this error:
FATAL EXCEPTION: main .... Fragment XyzDialog not attached to Activity.
It happens only when embedding one dialog to another and calls getActivity() method. Sample code:
MaterialDialog testDialog;
testDialog = new MaterialDialog.Builder(getActivity()) // ON THIS LINE IT'S OK
				.title(R.string.title)
				.items(items)
				.itemsCallbackSingleChoice(-1, new MaterialDialog.ListCallback() {
					@Override
					public void onSelection(MaterialDialog dialog, View view, int which, CharSequence text) {

						if (a > b) {
							testDialog = new MaterialDialog.Builder(getActivity()) // CRASH ON THIS LINE!
									.title(R.string.title)
									.positiveText(R.string.Yes)
									.negativeText(R.string.No)
									.callback(new MaterialDialog.Callback() {
										@Override
										public void onPositive(MaterialDialog dialog) {
										}

										@Override
										public void onNegative(MaterialDialog dialog) {
										}
									})
									.show();
						} else if (a < b) {
							testDialog = new MaterialDialog.Builder(getActivity())
									.title(R.string.title)
									.positiveText(android.R.string.ok)
									.callback(new MaterialDialog.Callback() {
										@Override
										public void onPositive(MaterialDialog dialog) {

										}

										@Override
										public void onNegative(MaterialDialog materialDialog) {

										}
									})
									.show();
						}
					}
				})
				.positiveText(R.string.choose)
				.show();

Its bug or feature?

That isn't how dialog fragments are used. Look at Google's documentation, you don't manually show dialogs, you return build() in onCreateDialog().

There's also an example in the sample project.

https://github.com/afollestad/material-dialogs/issues/188#issuecomment-70121212

Ok, I will look at it. Thank you

Sorry Aidan,
but this is not the same, I wrote about nested dialogs. Removing show() and adding build() work only on main dialog, on nested dialogs is situation different, don't show. In your examples is only one main dialog situacion.


Check for non-cacheable entities on metadata level, not at runtime

This PR moves the check for non-cacheable entities from "runtime" to metadata definition.
If an entity has an association key as part of its PK, and this association key is not configured to be stored into SLC, an exception it thrown.
The previous approach was checking this constraint at "runtime" (right before saving the value), this PR moves this check at metadata level into (_validateAndCompleteAssociationMapping method).
testQueryNotCacheableAssociationException ther has been removed since this constraint is checked at metadata class loading time

Any news /feedback on this?

Besides minor CS fixes, looks good for me.
Thanks @goetas

done! thank you for reviewing my code

This is gonna be in 2.6.0, thanks! :-)


[DOCS] Add 8.15.0 release notes

Preview
https://elasticsearch-hadoop_2253.docs-preview.app.elstc.co/guide/en/elasticsearch/hadoop/master/eshadoop-8.15.0.html

💚 All backports created successfully

Status
Branch
Result

✅
8.15

Questions ?
Please refer to the Backport tool documentation


Correctly return control characters within query result strings

For example, if a string contains a newline (\n), it should not be returned as a literal backslash and a literal 'n'.

Thank you, I was too busy to fix the problem.


OSM API /map call: support Overpass JSON format

This pull request is about parsing performance, for context see https://github.com/openstreetmap/iD/issues/1727#issuecomment-26099201

The code in here adds parsing logic for an OSM/Overpass based JSON format, which I implemented as part of https://github.com/zerebubuth/openstreetmap-cgimap/pull/153.
As the deployment of the JSON format to production is currently delayed due to missing support on the Rails port, the code in here is "silent" and inactive. To enable the new JSON parser, a few more changes would be needed:

loadFromAPI:

call to return parseXML(payload, callback, options); needs to be replaced by  return parseJSON(payload, callback, options);
d3_xml(url, { signal: controller.signal }) needs to be replaced by d3_json(url, { signal: controller.signal })

loadTile

API endpoint expects ".json" suffix to trigger JSON output, hence var path = '/api/0.6/map?bbox='; needs to be replaced by var path = '/api/0.6/map.json?bbox=';

(replacing would depend on some flag to allow switching between XML and JSON formats)
JSON output can be tested on the dev instance master.apis.dev.openstreetmap.org. Halifax in Nova Scotia has plenty of test data.
Unit tests are currently missing. I’m not sure if we can simply copy the existing XML ones and have them parse json instead. Or maybe something else?

Upstream dependencies:

https://github.com/openstreetmap/openstreetmap-website/pull/2485 (for moving JSON support to production)

Nice!  It would be great to use this someday!

Unit tests are currently missing. I’m not sure if we can simply copy the existing XML ones and have them parse json instead. Or maybe something else?

Yes, I'd modify loadFromAPI somehow.. It currently just calls parseXML, but if it could inspect they payload, then you could test it against both XML and JSON payloads to make sure it works with both.
I'm just going to merge as-is, since it's dead code anyway..

In my loadFromAPI method, I'm deriving a use_json flag based on the path being passed on as paramter: var use_json = path.includes(".json");  and do all switching based on that flag. loadTile is the place to either go for a map?bbox or map.json?bbox URL.
I'm not quite sure what's next here, i.e. if we should add some optional URL parameter to enable/disable JSON (like we do say for backgrounds), or have some try/fallback mechanism.

Currently, I don't see the need to JSON enable any of the other endpoints. Let's focus on /map first. I'm not quite sure what's next here, i.e. if we should add some optional URL parameter to enable/disable JSON (like we do say for boundaries), or have some try/fallback mechanism.

Can we test this yet, maybe against dev server?

Yes, you can already test the cgimap version against https://master.apis.dev.openstreetmap.org

I've noticed @quincylvania changed some of the object lookups to also use json. Currently there's a hardcoded visible value in jsonparsers.{node,way,relation}:
visible: true,

Now looking at https://api.openstreetmap.org/api/0.6/node/3006673214/4.json, you'll notice that in case the object has been deleted, there will be an additional "visible" attribute.
My suggestion would be to use the obj.visible flag if is part of the API payload, otherwise assume "true" as default:
visible: obj.visible ?? true,

(or something similar accomplishing the same task)

I've noticed @quincylvania changed some of the object lookups to also use json

@mmd-osm Yep! I tried to use as many of the JSON endpoints as possible

My suggestion would be to use the obj.visible flag if is it part of the API payload, otherwise assume "true" as default

Sounds good, thanks for flagging this 👍


Proper way to set permission?

https://github.com/Xe/xn--ts9h/blob/8f1dda8e53a500ea1d2a31fbc3547c66d4f91d8e/Cargo.toml#L11
Seems setting permission to 6755 is a recommended way, I followed that direction:
$ sudo cp target/release/xn--ts9h /usr/bin/🥺
$ sudo chown root /usr/bin/🥺
$ sudo chmod 6755 /usr/bin/🥺
$ stat /usr/bin/🥺
  File: /usr/bin/🥺
  Size: 321840          Blocks: 632        IO Block: 4096   regular file
Device: 8,32    Inode: 183118      Links: 1
Access: (6755/-rwsr-sr-x)  Uid: (    0/    root)   Gid: (    0/    root)
...

$ 🥺 id
uid=0(root) gid=0(root) groups=0(root),998(wheel),1000(xnuk)

Which is nice, but this means any user in this computer can access to root:
$ sudo -u git 🥺 id
uid=0(root) gid=0(root) groups=0(root),975(git)

Setting chgrp wheel and chmod 6754 is probably what I wanted, but I still don't fully understand the 4-digit permission system:
$ sudo chgrp wheel /usr/bin/🥺
$ sudo chmod 6754 /usr/bin/🥺
$ stat /usr/bin/🥺
  File: /usr/bin/🥺
  Size: 321840          Blocks: 632        IO Block: 4096   regular file
Device: 8,32    Inode: 183118      Links: 1
Access: (6754/-rwsr-sr--)  Uid: (    0/    root)   Gid: (  998/   wheel)
...

$ 🥺 id
uid=0(root) gid=0(root) groups=0(root),998(wheel),1000(xnuk)
$ sudo -u git 🥺 id
sudo: unable to execute /usr/bin/🥺: Permission denied

So I want to ask:

am i doing right or could you write some guide for this
or is it intended that any user can access to root

It is intended that any user can access root with this tool. This is a satirical tool that is intended to make you rethink the concept of privilege escalation. Hint: it's almost always NOT the pattern you want.


chore(main): release 1.0.0

:robot: I have created a release beep boop
1.0.0 (2022-05-16)
Features

add code for rectangular assignment (8e65d4f)
add github workflows (904ac79)
rename the package, add README (74b92c2)

Bug Fixes

add again workflows (#4) (2f8d77d)
add check-types (#3) (6aacee5)
add package-lock (5df51e3)
add prettier write script (#2) (75d1992)
add test cases and split code (d53c4a0)
branch name (d353383)
gitHub workflows (#1) (02efeb0)
remove comments (40269cf)
remove support for node 14.x (#5) (a8d1ca0)
set bot_token (d20d982)
update workflows (#6) (8540439)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/jobo322/linearSumAssignment/releases/tag/v1.0.0 :sunflower:


generate samples for real estate offers

Using the [RDF Import Bot] (https://github.com/researchstudio-sat/won-rdfimport-bot), we can import TRIG files, each containing one need. For testing the RE case, we need to generate TriG files representing apartments and use the bot to import them.

i think before we tackle this, we should try and create the specific use cases with our usecase and detail definitions, in order to see if manually created posts have the necessary values. after this we can use the created post as a stub to automatically generate the real estate offers


AND-11 - Start sending interaction_id in Events launched from Interactio...

...ns. Update tests.

@pkamb I don't think it's necessary.  we'll have app.local as a prefix, and there's really no interaction in that context, so null serves the purpose just as well.


More ro ro translation updates

Could you please translate the sentences mentioned in this comment https://github.com/BustByte/coronastatus/pull/511#issue-396627593 for Romaina?


Hauling mechanoids should be able to do corpse-hauling

From Twilight on Steam:

@CaptainArbitrary - Noticed you had the opportunity to work on compatibility with Misc Robots. In testing and going through the patches it appears that the AIRobot_Hauler still lacks the ability to haul corpses.
As a test I tweaked the patch xml to give the them the MJobs_Undertaking worktype and this solved the problem. Just wondering if you would consider this as an official part of the patch. No obligation, its your mod and vision for it.

And from Bree on Steam:

I saw an earlier comment where you intentionally made it so the Lifters couldn't do the undertaker job. Is there a way you could add an option to turn it on? I'd like for my lifters to bury corpses.


why error when using pretrained model?

hi, I tried to train a 2-class model. i used your pretrained model .but   error likes this:
Check failed: from.shape() == to->shape() operands shape mismatchfrom.shape = (125,) to.shape=(30,)
my command is : python train.py --train-path /data/data/train.rec --val-path /data/data/val.rec --pretrained /data/model/yolo2_darknet19_416 --epoch 0
ps ,i have changed the class_num to 1.

Did you change num_class in the symbol file?


K8SPG-604 fix tests for k8s 1.31

CHANGE DESCRIPTION
Problem:
Short explanation of the problem.
Cause:
Short explanation of the root cause of the issue if applicable.
Solution:
Short explanation of the solution we are providing with this PR.
CHECKLIST
Jira

[ ] Is the Jira ticket created and referenced properly?
[ ] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[ ] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Is an E2E test/test case added for the new feature/change?
[ ] Are unit tests added where appropriate?

Config/Logging/Testability

[ ] Are all needed new/changed options added to default YAML files?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PG version?
[ ] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

custom-extensions
passed

custom-tls
passed

demand-backup
passed

finalizers
passed

init-deploy
passed

major-upgrade
passed

monitoring
passed

one-pod
passed

operator-self-healing
skipped

pitr
passed

scaling
passed

scheduled-backup
passed

self-healing
passed

start-from-backup
passed

tablespaces
passed

telemetry-transfer
passed

upgrade-consistency
passed

upgrade-minor
passed

users
passed

We run 18 out of 19

commit: https://github.com/percona/percona-postgresql-operator/pull/891/commits/3c3136f9146243a28a1f5cbb333a80179683e35e
image: perconalab/percona-postgresql-operator:PR-891-3c3136f91

Test name
Status

custom-extensions
passed

custom-tls
passed

demand-backup
passed

finalizers
passed

init-deploy
passed

major-upgrade
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

pitr
passed

scaling
passed

scheduled-backup
passed

self-healing
passed

start-from-backup
passed

tablespaces
passed

telemetry-transfer
passed

upgrade-consistency
passed

upgrade-minor
passed

users
passed

We run 19 out of 19

commit: https://github.com/percona/percona-postgresql-operator/pull/891/commits/3c3136f9146243a28a1f5cbb333a80179683e35e
image: perconalab/percona-postgresql-operator:PR-891-3c3136f91


drivers: uart: clarification of poll_out blocking duration

The API docs state that the uart_poll_out is a blocking call, but it does not specify how long a call to this function should block the calling thread. This is described in the UART driver documentation.
This patch clarifies the API docs and aligns it with the driver documentation.
ref https://github.com/zephyrproject-rtos/zephyr/blob/1a5ae376a3f93312fd85016464a8b6221c554c14/doc/hardware/peripherals/uart.rst?plain=1#L18-L20

What is the benefit of blocking in poll out until byte is sent?

I guess information for the API user when the byte is sent. I don't think there is any other function to poll for this information.

Maybe let me add a little context.
I can imagine an implementation of a device driver for an RS-485 bus driver. The device driver implementation requires sending a data frame on UART, waiting a defined time after the last character in the frame is sent, and switching GPIO (from TX to RX mode).
So the code would look like:
gpio_set_to_tx();
for (size_t i; i < sizeof(frame); i++) {
  uart_poll_out(&uart_dev, frame[i]);
}
// wait until the last character is transmitted
gpio_set_to_rx();
// start receiving a response

According to the text from uart.rst, no additional waiting after the loop is required, because uart_poll_out() blocks until the character is sent.
However, if uart_poll_out() didn't block until the character was sent, we would need another function like uart_flush() blocking until all queued characters were sent.

Maybe we are missing something like uart_poll_out_flush that would wait until byte is sent? Allowing poll_out to return without waiting for completion speeds up printf-like functions because next byte can be prepared while previous byte is being sent so UART bandwidth is better utilized.

@nordic-krch can you clarify if your comment calls for a request for change or if you want to +1 to move this forward? Thanks!


u64 bitwise rotate works incorrectly

Expected Behaviour
Bitwise rotating works correctly.
Example & Steps To Reproduce
I was porting SHA512 and this function worked differently on CPU and GPU:
fn big_sigma0(x: u64) -> u64 {
    x.rotate_right(28) ^ x.rotate_right(34) ^ x.rotate_right(39)
}

System Info

Rust: rustc 1.69.0-nightly (44cfafe2f 2023-03-03)
OS: NixOS Linux 5.15.110
GPU: AMD Radeon RX 6800 XT
GPU Driver: amdvlk
SPIR-V: v2023.2 unknown hash, 1980-01-01T00:00:00 (incorrect time because of NixOS)

Just FYI the same thing happens with u32.

I think @chrisliebaer just ran into the same issue, and AFAICT it's just this being flipped:
https://github.com/EmbarkStudios/rust-gpu/blob/e96418f9fa93c1e1a604d0d5f142496828cf7c22/crates/rustc_codegen_spirv/src/builder/mod.rs#L243-L247
(based on the name it should clearly be == not !=)


Slow down verification of AWS instance types due to rate limit

Signed-off-by: Sean Turner<EMAIL_ADDRESS>When you customise multiple instance types, tarmak fails due to trying to verify these types are available in your region faster than the AWS API will allow:
Slows down verification of AWS instance types so we don't hit the rate limit for these requests

/ok-to-test
/assign @alljames

Thanks @seanturner83 a solution to that merged via #626


Cast conversion request in the correct API group

What this PR does / why we need it:
Do internal version conversion in the conversion webhook
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
fixes https://kubernetes.slack.com/archives/C4NV3DWUC/p1599054237050400
Special notes for your reviewer:
This will patch the CI issue in #3241 also
Release note:

Fix conversion webhook when given v1beta1 requests

/kind bug

/cherrypick release-1.0

Is it possible to cover this code (and the similar mutate etc. methods I guess) with unit tests?

@james-w that is exactly what we are chatting about, will be a follow up PR will write an issue as this isn't a super easy one to cover correct


Modify, Detail, History Wizard of defect is not focused when open.

Test with HP ALI: <IP_ADDRESS>.4, IntelliJ IDEA 14.1.5

Hi,
Since the commit dialog (and consequently also the entity selector) is displayed in modal context, the non-modal history dialog cannot receive focus. I think that the solution is not to enable the context menu in the selector at all. Can you describe a real-world scenario where the context menu is meaningfully used from the selector/commit dialog?
Thanks.


SSL tracking is only available for pro+ accounts

Added callout explaining that only Pro accounts and higher may use SSL enabled click and open tracking

This is not true. SSL enabled click and open tracking is available on all accounts.


GitHub Action to send events to the map

What events, what map? 😕

good question, I think most events from GitHub could be interesting, for example:

issue new / comment / reaction
pr new / comment / approval
commit
reaction
discussion new / comment
...

Oh, okay.
I don't really understand the point of this repo, so I'll check that first.

No problem, this repo was a prototype I did quickly, but it needs to be started again.
The idea is when we are on a live stream to have this in the background behind me, and from Discord people can make themselves show on the map, but also they can appear on the side of the map with any GitHub activity

Oh okay. Well the 'About' section doesn't explain that well. maybe just put your comment in there.

Thank you 👍 . I have updated it with, hopefully that is more clear?

Map to show where viewers on the live stream are tuning in from. This will be trigged with a Discord bot command from viewers who wish to participate

Gorgeous.


Yammer as a "technology" category doesn't work, makes other Custom categories disappear if Yammer is made visible

Describe the bug
Yammer as a "technology" category doesn't work, makes other Custom categories disappear if Yammer is made visible
To Reproduce
If I would like to make the Yammer content visible and click the (eye)visibility icon, the content doesn't appear. Also if I create a custom category (Communities by Yammer as in our example) and assign the Yammer as the technology for the Custom playlists. It does not appear. I can ignore the problem by just not adding the Yammer as the technology there, so site is still usable. But just wandering is this a general error or something in our installation part that would perhaps require a new installation?
Expected behavior

A clear and concise description of what you expected to happen.

Screenshots
The Playlist and content is visible with these settings

But with this small change the content and playlist is not visible

Learning Pathways version number
version 4.1.3 (upgraded from version 3)
Additional context

If that's happening it would be because the Yammer technology was hidden, which then causes any content tagged with the Technology Yammer to be hidden and if a category has no visible playlists in it, it won't show up.  So, I would go check the Technologies view in the Admin page and make sure the Yammer Technology is not hidden.

Thanks @juliemturner I'll close this down, your suggestion was the answer. My mistake, thank you for the fast support. Now it's visible.


Feature request: np_episodes as new option to fit()

Hi,
I recently discovered keras-rl and noticed that it is possible to specify the number of steps for fitting, but not the number of episodes. I would find that a very useful feature and it only requires to change a few lines of code in core.py.
I did that in my installation, but it would be nice to have it in the official distribution. So this would be my feature request for the next release. I'm also happy to somehow provide my code changes if somebody tells me the best way to do this (I'm not so familiar with github).
Many thanks,
Axel

AxKo
I did that in my installation, ...

How you did it?

Make the following changes to your site-packages\rl\core.py file:
Around line 40:
def fit(self, env, nb_steps=0, nb_episodes=0, action_repetition=1, callbacks=None, verbose=1,
Around line 100:
params = {
'nb_steps': nb_steps,
'nb_episodes': nb_episodes,
}
And around line 115:
while self.step<nb_steps or episode<nb_episodes:
Now you can specify nb_steps OR nb_episodes in the call to fit()
Best regards,
Axel

Oh, and if this finds its way into a new release it would be helpful to make 'episode' an instance variable (self.episode) in core.py. That way also Policies can work on episodes instead of steps.
Thanx,
Axel

Thanks a lot.. it works but, need to change ...

Around line 40:
def fit(self, env, nb_steps=0, nb_episodes=0, action_repetition=1, callbacks=None, verbose=1,

to
def fit(self, env, nb_steps=1, nb_episodes=0, action_repetition=1, callbacks=None, verbose=1,
Very usefull! Thanx

I also add best reward...
1)

def fit(self, env, nb_steps=1, nb_episodes=0, br=0, action_repetition=1, callbacks=None, verbose=1,

2) before  if done: Around line 205:

if br != 0 and episode_reward >= br:
done = True
break

So, now it finish learning if it reach desired reward before it reach end of nb_episodes
500 for 'CartPole-v1', for example:

dqn.fit(env, nb_episodes=nb_Episodes, br=500, visualize=False, verbose=2)

Hi @Sat0ri , could you explain why someone would want to define a 'best maximum reward' in advance?

Hi @pollini , for example, train the net untill it reach best reward after save&test it.
This code:
dqn.fit(env, nb_episodes=nb_ep, visualize=False, verbose=2)
dqn.save_weights('Saved/weights.h5f', overwrite=True)
...sometimes when it training for n episodes it reach best reward early, but at the end of training the reward will be not the maximun, and it will save it anyway
this one:
dqn.fit(env, nb_episodes=nb_ep, **br=best_reward**, visualize=False, verbose=2) dqn.save_weights('Saved/weights.h5f', overwrite=True)
will save weights with best reward/results.

I agree with this proposal. Depending on the environment, and if episodes can be of arbitrary length, it's harder to compare the results of two models since one may have gone through many more episodes than the other if we use number of actions as the stopping criterion.

Thank you all, guys. I wish this feature too, it's very useful in some cases.

This would also be very useful for my use case.

I just tried to pass nb_episodes to .fit... but its not a kwarg, but is for .test.  Seemed like an obvious way to handle #123 .


dune-release publish distrib fails because of missing package delegate

Running dune-release publish distrib in the dune repo fails as follow:
$ dune-release publish distrib --verbose -n dune
dune-release: [INFO] dune-release 1.3.3 running
[-] Publishing distribution
dune-release: [INFO] Parsing opam file dune.opam
dune-release: [ERROR] readthedocs-dune-release-delegate: package delegate
                      cannot be found. Try `dune-release help delegate` for
                      more information.

Can I force dune-release to consider the project as a normal github project?

For others with this problem, this seems to work:

Do everything up to and including the  dune-release distrib step as usual.
Edit your main opam file to set homepage: "https://github.com/ORG/REPO" (but don't commit).
Run dune-release publish.
Undo the homepage change.
Copy _build/$main.url as _build/$other-pkg.url for each sub-package.
Run dune-release opam pkg.
Run dune-release opam submit.

FTR, that's what we have in the Makefile of dune:
opam-release:
	dune-release distrib --skip-build --skip-lint --skip-tests -n dune
	# See https://github.com/ocamllabs/dune-release/issues/206
	DUNE_RELEASE_DELEGATE=github-dune-release-delegate dune-release publish distrib --verbose -n dune
	dune-release opam pkg -n dune
	dune-release opam submit -n dune

I found a link to this issue in pp's release script. I was able to run it without the delegate env variable. Seeing as #188 is closed, shall we close this issue as well as resolved?
In this PR I am proposing to simplify pp's release script: https://github.com/ocaml-dune/pp/pull/22


remove legacy colorcodes

removed outdated color codes

Nice! I guess that is better than colours in logging.


File matching for the built-in coffee sourceTransformer is more strict

Closes #51

Thanks, merged as 43ccf01e5676b829aeaa6bfeed06e98d208b7bf6


fix speaker cards not showing && fix speaker and challenge card alignments

Might be better to remove text-center on challenge title. Such a small change so prob not worth creating a whole commit for it and just include it in another change? But just something to remove in the future

Might be better to remove text-center on challenge title. Such a small change so prob not worth creating a whole commit for it and just include it in another change? But just something to remove in the future

should be fixed now


Biome Categorys not working in 1.18.2

The Biome Categories don't work in the 1.18.2 version of this mod. Entities only spawn when you add minecraft: to the biomes in the config which makes the mod not compatible with biome mods.

Yup, this is an issue he said he wouldn't fix for 1.18.2 and it's only going to be fixed for 1.19+ IIRC
Yup: https://github.com/Slexom/earth2java/issues/62


Fix nilled PubKey curves causing nil pointer crash during signature verification

This PR fixes an issue where logging object containing pubkeys would alter those object by setting the Curve parameter to nil. This was done to avoid logs printing uninformative curve parameters, but had the side effect that the signature verification using the affected pubkeys would crash because of the now nil Curve.
We now loop over all the pubkey fields of the object to log, saving the Curve before nilling it, then properly restore it after logging.

Closing. Will instead set the curve before doing signature verification.


Investigate PyPy wheel upload issue from Travis-CI (OS X)

+cd python

++ls -A wheelhouse

+'[' -n keyvi-0.3.1-pp260-pypy_41-macosx_10_11_x86_64.whl ']'

+twine upload --config-file ../travis/pypirc -u [secure] -p [secure] wheelhouse/keyvi-0.3.1-pp260-pypy_41-macosx_10_11_x86_64.whl

dyld: lazy symbol binding failed: Symbol not found: _clock_gettime

  Referenced from: /Users/travis/.pyenv/versions/pypy2.7-6.0.0/bin//libpypy-c.dylib

  Expected in: flat namespace

dyld: Symbol not found: _clock_gettime

  Referenced from: /Users/travis/.pyenv/versions/pypy2.7-6.0.0/bin//libpypy-c.dylib

  Expected in: flat namespace

travis/upload_packages.sh: line 9: 16406 Trace/BPT trap: 5       twine upload --config-file ../travis/pypirc -u $PYPI_USERNAME -p $PYPI_PASSWORD wheelhouse/*

Script failed with status 133

full log: https://travis-ci.org/KeyviDev/keyvi/jobs/422959161

pypy upload worked in the last releases.


Restore selection correctly even when wrapping asymmetrically

Fixes: #31

Any chance that this can be included in a release soon? It'd save us from having to temporarily revert the upgrade from 3.2.0 in Zulip if we knew a release will be out in the next week or so.


Recognize most valid names

Covers most valid unicode names, disallows names starting with a number.
Aside, perhaps getting close to time to factor out some definitions (valid name, recursively defined valid type syntax, etc.)

 Thanks!
Feel free to open issues and explain possible refactoring ideas. We can then knock them out as we find the time.

Sounds good -- I probably won't dig much more for a couple days, but I'm giving atom a serious go, so I plan to be back soon.


Version 1.9

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.

@conda-forge-admin, please rerender

@erikmannerfelt I released version 1.9 on PyPI. Could you take a look at this? Did I miss anything?

Nevermind, the bot did exactly the same changes in #2. I will close this PR now.

Great, @AlexanderFabisch! Thanks for the update!

Note that 1.9 was broken (missing subpackages, https://github.com/rock-learning/pytransform3d/issues/145), 1.9.1 is the latest release: https://github.com/conda-forge/pytransform3d-feedstock/pull/3


Enable anti-aliasing?

This plugin produces nice results already, but maybe you could try enabling anti-aliasing: see: https://discourse.vtk.org/t/how-to-anti-alias-in-vtkrenderwindow/4556/11

@adam-urbanczyk I tried a quick test and it seems to work, but I'm wondering if it should be an option that you have to turn on. Also, should the user be able to vary the number of samples?


"rgb-color" dependency needed?

The "rbg-color" dependency is added but a file named "rgbcolor.js" is present in the project.
is it a deprecated dependency and can be excluded avoiding rgbcolor.js to be overwritten?
{
"name": "canvg",
"version": "1.0.0",
"main": "canvg.js",
"keywords": ["javascript", "client", "browser", "svg", "canvas"],
"ignore" : ["examples", "svgs"],
"dependencies": {
"rgb-color": "ariutta/rgb-color"
}
}

i only have rgbcolor.js in the repo for people that don't want to use bower. i guess it would make sense to rename it to rgb-color.js to match ariutta's repo, right?

we've updated build to be cleaner


Feature Request: autosave on throttled keyup

Like autosave function. When I entered some data, then Meteor saved it on timer.

Done in dev branch with PR #513

Done in AutoForm 5.0, now released.


test(example, windows): fix windows example white-on-white text

without this, on my machines at least (dark mode perhaps?) the example
did not show up any results - it was all blank
Related #532 /  #521
Test Plan
Tested on android, ios and windows

:tada: This PR is included in version 7.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Pytube (compatible to python 3)

Added compatibility to python 3 and fixed a bug

@KeluDiao Y U delete? I was going to merge once I had a chance to fix the failing tests.


Return a somewhat sane default value for L2 cache size if cpuid retur…

…ned something unexpected
Fixes #1610, the KVM hypervisor on Google Chromebooks returning zero for CPUID  0x80000006, causing DYNAMIC_ARCH builds of OpenBLAS to hang

I've confirmed that https://github.com/nelhage/openblas/tree/issue1610 resolves the issue on my chromebook, but that the patch on this PR so far is not enough. Thanks for the quick turnaround!


modernization of Galaxy101

Updated all to latest  interface features and updated tool versions

topics/introduction/images/open_wf_editor.png is not needed anymore?
It is needed
topics/introduction/images/history_options_menu.png --> why the black background?
To emphasize the edge of the window
the gif is great but somehow a bit blurry topics/introduction/images/drag_n_drop_dataset.gif
Let's keep it as is

@bgruening please feel free to make those comments directly on the relevant files in the future! :)


Host Files set to Root & Container Files set to 501:20

Hi,
So I tried to mount a local folder as a volume in my busybox.
docker run -it -v $(pwd)/test:/test busybox

Now I am in the busy box.
The first thing I see is, that the /test folder has the owner 501:20. Why is this so?
Now when I create a file inside the busybox, it gets the owner root, but on my host machine the file has also the owner root. But the owner should be my user. Otherwise I have to do everything as root?
#inside busybox
touch 123

Now when I create a file in my local test folder. In the busybox it has the owner 501:20.
Is there any workaround to map the files to the right user for both, on the host and in the container?
Best Regards,
Michael

Hello @smith64fx ,
I would have to know how you configured the NFS part on your box. Because if you do it with default configuration it should work.
See my tests step by step:

The 501:20 are the ids of your user and group on your host (mac os x):

toni at t-mac in ~/dev/projects/docker_test
$ echo $(id -u):$(id -g)
501:20

Result when I create a file on my host:

toni at t-mac in ~/dev/projects/docker_test
$ touch created_on_host

# ls result on my host
toni at t-mac in ~/dev/projects/docker_test
$ ls -las
total 0
0 drwxr-xr-x   3 toni  staff  102 Jan 12 09:32 .
0 drwxr-xr-x  15 toni  staff  510 Jan 12 09:28 ..
0 -rw-r--r--   1 toni  staff    0 Jan 12 09:32 created_on_host

# ls result on the virtual box (where you'll see the 501:20)
toni at t-mac in ~/dev/projects/docker_test
$ docker-machine ssh adlogix-dev ls -las /Users/toni/dev/projects/docker_test
total 8
     4 drwxr-xr-x    3 501      20             102 Jan 12 08:32 .
     4 drwxr-xr-x   15 501      20             510 Jan 12 08:28 ..
     0 -rw-r--r--    1 501      20               0 Jan 12 08:32 created_on_host

Let's create a file from inside the container

toni at t-mac in ~/dev/projects/docker_test
$ docker run -it -v $(pwd):/test busybox
/ # cd /test
/test # ls -las
total 8
     4 drwxr-xr-x    3 501      20             102 Jan 12 08:34 .
     4 drwxr-xr-x   20 root     root          4096 Jan 12 08:34 ..
     0 -rw-r--r--    1 501      20               0 Jan 12 08:32 created_on_host
/test # touch created_in_container
/test # ls -las
total 8
     4 drwxr-xr-x    4 501      20             136 Jan 12 08:34 .
     4 drwxr-xr-x   20 root     root          4096 Jan 12 08:34 ..
     0 -rw-r--r--    1 501      20               0 Jan 12 08:34 created_in_container
     0 -rw-r--r--    1 501      20               0 Jan 12 08:32 created_on_host

toni at t-mac in ~/dev/projects/docker_test
$ ls -las
total 0
0 drwxr-xr-x   4 toni  staff  136 Jan 12 09:34 .
0 drwxr-xr-x  15 toni  staff  510 Jan 12 09:28 ..
0 -rw-r--r--   1 toni  staff    0 Jan 12 09:34 created_in_container
0 -rw-r--r--   1 toni  staff    0 Jan 12 09:32 created_on_host

You can see that it keeps the same user:group.
Hope this helps.

Thank you @tonivdv
So how can I make it possible, that the user:group in the box, called 510:20 (the id from own Mac) is mapped to the user & group www:www inside my box?
Thank you!

@smith64fx how did you configure your box? By configuring it the default way? So by doing:
$ docker-machine --driver virtualbox test
$ docker-machine-nfs test

?

Hi @tonivdv
Yes, right, I created it this way.

That's odd it doesn't behave in the same way. Can you share the /etc/exports file.

/Users <IP_ADDRESS> -alldirs -maproot=0
The question is more, how can I map my 510:20 user to www:www inside the container?

@smith64fx I see the issue. Actually you did not run the docker-machine-nfs with default configuration because if you would have, the /etc/export file would have been:
/Users <IP_ADDRESS> -alldirs -mapall=501:20

ok but when I change it, the files inside the docker still have the user/group of 501:20.
But I want them to be www:www, and on my local mac smith:staff.
How to achieve this?
Best Regards & Thanks!
Michael

AFAIK this is not possible out of the box. You will have to create your own Dockerfile by creating that user etc. This is completely out of scope of this project :(

As this is not a bug related to this project I'm gonna close the issue.


Exception loading list index from file

Exception loading saved list index with version 0.4.6
Loads okay with 0.4.4
return cls.load_from_string(file_contents, **kwargs)
  File "/Users/***/chatbot/.venv/lib/python3.10/site-packages/gpt_index/indices/base.py", line 431, in load_from_string
    index_struct = docstore.get_document(index_struct_id)
  File "/Users/***/chatbot/.venv/lib/python3.10/site-packages/gpt_index/docstore.py", line 97, in get_document
    raise ValueError(f"doc_id {doc_id} not found.")
ValueError: doc_id 88151a8e-e3c5-41f2-bb14-f7f6cb9c4762 not found.

@itaim we refactored the docstore in 0.4.5, it's possible that introduced some breaking changes i wasn't aware of.
could you try regenerating the list index + saving + loading again to see if it's an issue? (the cost should be 0, list index doesn't make any LLM / embedding calls)

also i think i just figured out the issue, will create a patch fix (but also let me know if regenerating works)

It has ~30k documents so it would take a while to re-embed. I can try to load the json, parse and rebuild but if you already figured it out I'' wait for the fix 🙂

@itaim should be fixed with #485 , give it a shot

Works. thank you!


space-separated large numbers

Some large numbers have thousands separated with a space, so they get tokenized separately. Do we want to normalize them somewhere in reading projects or during pdf to txt conversion? Here's a screenshot from a pdf  with a couple of examples:

I think this would be hard to detect... What do you think @kwalcock ?

The pdf2txt converter already has this capability.  However, it is not turned on by default.  I don't remember exactly why, but perhaps it was thought that something could consider those spaces significant.  If you are working with the github project, you can change
case class Hyperparameters(joinWithSpaces: Boolean = false)

to use true.
The setting isn't available from the command line or a configuration file.  I'll at least add the latter for now.  The command line is already awfully crowded.

It probably won't stay this way forever, but temporarily one can make a configuration file like habitus.conf containing
Pdf2txt {
  numberParameters {
    joinWithSpaces = true
  }
}

and then call PdfToTextApp with -conf habitus.  Otherwise one can edit Pdf2txt.conf and change the value from false to true.

@kwalcock thank you!


Fix #152 header parse value fails

Any new Feature should handle all of below

http2har (export to all programming languages using httpsnippet or request sharing)
har2http (swagger3 import, swagger2 import, curl import)
postman2http (postman3 postman2 import)
http2postman (export http file to postman request collection)
http2curl (mirror, to check syntax or most scenarios)

are expected to work by default for any new feature. here is the checklist

[x] check request executed properly

[x] test case

[x] check har is generated properly and test case

[x] test case

[x] check postman collection export of that use is generated properly

[x] test case

[x] check with this new feature, postman import (few left out) can be bought back

[x] test case

[x] check curl is generated like expected

[x] test case

[x] check format is generated as expected

[x] test case

fixing this #152, causes other test case issues. closing


Cube._summary_coord_extra: efficiency and bugfix

🚀 Pull Request
Description
I started looking at this method with a view to fixing #3921, but once I looked couldn't ignore the fact that this method seemed a bit inefficient: we ultimately only want the elements of vary that exist as keys in coord's attributes dictionary, so I think we should only loop through those keys to begin with.
I've added one simple test for the #3921 case.  Note there is also one existing test for this method in the legacy tests.
I'd like to get this into Iris v3 if possible, as I believe lenient cube arithmetic will increase the prevalence of Frankencubes*.  So this method will get called more often.  And the change is only small :innocent:
Closes #3921.

*Frankencube noun: a cube with multiple coordinates that have the same name.  Coined at https://github.com/ESMValGroup/ESMValCore/issues/373

Added a further efficiency: we don't need to compare the given coordinate with itself.  Think I'm done now.

Thanks @rcomer , looks useful.
Aside : could we define a Frankencube as one that has DoppleGangCoords ?

Thanks @pp-mo
I see a whole new Glossary section of the docs coming on! :laughing:


[ENH] transform_column: transform multiple columns

@mdini if you'd like to take on this issue, please let us know here!

Hi @mdini Does this have a different functionality than transform_columns ?

@jk3587 Sorry i didn't see there is a function transform_columns. But why do we have transform_column then?  In my opinion transform_columns is enough and the user can call transform_columns with a list of one element.

But why do we have transform_column then?

@mdinin this was a design choice I made early on, which in retrospect may not have been the best. I had created the singular and plural versions of a function where relevant. Maybe it's better to only provide the plural version? @jk3587 what are your thoughts here?
I know that @zbarry and @szuckerman raised the same questions and didn't mind it at first, but looking at the API and how much it might grow, I think it's best to revisit this question once again.

In my opinion transform_columns is enough and the user can call transform_columns with a list of one element.

This is definitely a good API suggestion. I'm thinking that for transform_columns, a few example nice API might be as follows:
# transform only one column, while creating a new column name for it.
df.transform_columns(column_name=['col1'], function=np.abs, new_column_name=['col1_abs'])

# transform multiple columns by the same function, without creating a new column name.
df.transform_columns(column_name=['col1', 'col2'], function=np.abs)

# transform multiple columns by the same function, without creating a new column name.
df.transform_columns(column_name=['col1', 'col2'], function=np.abs, new_column_name=['col1_abs', 'col2_abs'])

# transform multiple columns, each with their own function, and new column names.
def negative(x):
    return -x

# note here that column_name is not provided, because it is present in the mapping.
df.transform_columns(
    mapping={
       # structure of dictionary:
       # <original column name>: (<function>, <new column name or None>)
        'col1': (np.abs, "col1_abs"),
        'col2': (negative, None),  # do not change this column name
)

This API should cover most of the use cases; in particular, use of the mapping kwarg is the most general, but the use of the other kwargs would make it easier to read for single- or few-column transformations. What do you all think?

But why do we have transform_column then?

@mdinin this was a design choice I made early on, which in retrospect may not have been the best. I had created the singular and plural versions of a function where relevant. Maybe it's better to only provide the plural version? @jk3587 what are your thoughts here?
I know that @zbarry and @szuckerman raised the same questions and didn't mind it at first, but looking at the API and how much it might grow, I think it's best to revisit this question once again.

In my opinion transform_columns is enough and the user can call transform_columns with a list of one element.

This is definitely a good API suggestion. I'm thinking that for transform_columns, a few example nice API might be as follows:
# transform only one column, while creating a new column name for it.
df.transform_columns(column_name=['col1'], function=np.abs, new_column_name=['col1_abs'])

# transform multiple columns by the same function, without creating a new column name.
df.transform_columns(column_name=['col1', 'col2'], function=np.abs)

# transform multiple columns by the same function, without creating a new column name.
df.transform_columns(column_name=['col1', 'col2'], function=np.abs, new_column_name=['col1_abs', 'col2_abs'])

# transform multiple columns, each with their own function, and new column names.
def negative(x):
    return -x

# note here that column_name is not provided, because it is present in the mapping.
df.transform_columns(
    mapping={
       # structure of dictionary:
       # <original column name>: (<function>, <new column name or None>)
        'col1': (np.abs, "col1_abs"),
        'col2': (negative, None),  # do not change this column name
)

This API should cover most of the use cases; in particular, use of the mapping kwarg is the most general, but the use of the other kwargs would make it easier to read for single- or few-column transformations. What do you all think?

While working on a TidyTuesday notebook example, I came across R's mutate function which seems to be essentially the transform_columns that is currently implemented but being allowed to transform multiple columns with different functions.
# Removes brackets from some columns
clean_df <- raw_df %>%
  # Removes brackets from a string columns 'producers' and 'genre'
  mutate(producers = str_remove(producers, "\\["),
         producers = str_remove(producers, "\\]"),
         genre = str_remove(genre, "\\["),
         genre = str_remove(genre, "\\]"))

The pandas documentation has a page comparing R vs pandas functions and it shows mutate is most similar to df.assign link.
Documentation for df.assign
Looking at the documentation for df.assign it seems that, for the most part, it does what transform_columns does. The part that I'm confused about is that the return value is a New DataFrame with the modified or new columns.
@ericmjl Does the current implementation of transform_column return a new DataFrame with the modified columns or does it return the original DataFrame with modified columns?
Lastly, for small datasets, a wrapper around df.assign with a col: df.str function mapping could help with #273. Here is a link of such implementation. Not sure how this would affect performance for larger DataFrames since it's returning a new DataFrame.

I like the idea of only having the plural version of the function. To still give it the same functionality of a "singular" function, there's a few options:

Allow column and columns arguments; column would take a string instead of a list and would work like transform_column.
Only allow a columns argument, but if a user inputs a string instead of a list you check it with something like the following:

if isinstance(columns, str):
    columns = [columns]

And thank you for the great sprint and this great package :-)

So, is it agreed then that there should only be the plural of each function?  Keen to get the final stance on this and see if I can take it on

@samukweku it's an important API decision. What's your thought?

I agree with the plural form of the functions. Less number of functions to keep track of, and the plural form still remains intuitive to the end user. Plural wins!

Sounds good. This is a breaking change for the API, btw, so be sure to follow "deprecation practices". If I remember correctly, @hectormz put in a decorator for deprecating stuff. You might want to see if (a) it can be reused, or (b) a similar thing can be built for this situation (i.e. "deprecation of singular"). I'll probably need a warning to remind myself for a few versions, as I've gotten used to typing df.transform_column("column_name", function_name, "new_column_name").

Bringing this up here as well. I think Pandas' transform function is sufficient and does pretty much all that transform column(s) does. I suggest we slate the function for deprecation - unless someone has some use cases that Pandas transform cannot pull off.

If I am reading the pandas docs correctly, I think transform only operates on the entire dataframe. Does it allow selective column transformations?

Yes, it does allow selective column transformations, although playing more with it, I see that you have to reassign the values to the dataframe :
df = pd.DataFrame(
[
    ["Juan", 0, 0, 400, 450, 500],
    ["Luis", 100, 100, 100, 100, 100],
    ["Maria", 0, 20, 50, 300, 500],
    ["Laura", 0, 0, 0, 100, 900],
    ["Lina", 0, 0, 0, 0, 10],
],
columns=["Name", "Date1", "Date2", "Date3", "Date4", "Date5"],
)

df

df.transform({'Date1':np.abs, 'Date3':lambda x: x+1, 'Date4' : np.sqrt})

    Date1 | Date3 | Date4
        0 | 401   | 21.213203
      100 | 101   | 10.000000
        0 | 51    | 17.320508
        0 | 1     | 10.000000
        0 | 1     | 0.000000

Cool stuff! Thanks @samukweku for figuring this out 😄 🎉!
With transform_column, looks like we're covering the case where we want to selectively transform a bunch of columns while retaining anything that isn't explicitly passed in. This is a value-add on top of what df.transform does. We are also able to transform the column into a new column this way too. The semantics of transform are such that the resulting dataframe columns are taken from the keys passed in, which I think might be a bit too restrictive for the broader use case that transform_columns solves.
I'd like to propose something along this lines then:

identity = lambda x: x

# Just a sketch, implementation needs to be fleshed out
def transform_columns(df, function_mapping: Dict, new_column_names: Dict):
    # First off, make a function mapping with "identity" as the default
    functions = {c: identity for c in df.columns}
    functions.update(function_mapping)

    # Next, transform the dataframe.
    new_df = df.transform(functions)

    # Next, rename the columns based on what's in new_column_names
    new_df = new_df.rename(new_column_names, axis="columns")

    # Finally, put back any columns from the original that are not intended to be overwritten.
    new_df = ... # something... mind is blank on this
    return new_df

This is kind of a nice programming puzzle to figure out, I think. It might also help eliminate future "semantics debt", where the semantics of a function get muddied over time. The implementation is also flat ("flat is better than nested"), delegates to pandas what ought to be delegated to pandas, and should be more maintainable in the long-run.
The only downside is that this is an API change, so I evolving the API would mean we should preserve the API now, add the new API as keyword arguments, add an API deprecation warning, mark the old chunk of code to be deprecated using comments, and only in the 1.x release deprecate the old code.
What do you all think?

@ericmjl do you mind sharing an example, so I can understand better your proposition? Confused about identity and the function mapping

Yep, definitely @samukweku!
I posted something here. Please let me know what you think of it!
cc: @sallyhong

Thanks for sharing the example! Helps a lot!
(Quick note: Cell6, the column rename didn't work. I think you have to put 'date4'--no caps)
Just wanted to confirm, for the second method style, how would you "transform" multiple columns when you want to rename some columns but not the other?  (That's the main reason I like the first method style.)
I also want think we should make sure that we preserve the column order of the original dataframe in the output. (Cell 8 output shows otherwise)

As a side note, what if we used a new name mutate/transmute (nothing original in those names), that way we avoid the single/plural verb names, while still using a synonym that captures what we mean?

Just wanted to confirm, for the second method style, how would you "transform" multiple columns when you want to rename some columns but not the other? (That's the main reason I like the first method style.)
I also want think we should make sure that we preserve the column order of the original dataframe in the output. (Cell 8 output shows otherwise)

@sallyhong I tried an alternative implementation, leveraging another function we have in the library. Check it out on this gist.

As a side note, what if we used a new name mutate/transmute (nothing original in those names), that way we avoid the single/plural verb names, while still using a synonym that captures what we mean?

@samukweku that's a cool idea. I think we might be hitting on the semantics of R's mutate.
What do both of you think about the 2nd implementation (transform_column_v3) in the gist? @sallyhong, would you like to give it a shot, sort of as a way of getting back into contributing? 😄

Hi, just assigned this to myself.
I'll take a shot at this, this weekend!
I want to study the R equivalent too to glean any other ideas.
Thanks!

Hi!
I attempted a v4.
Link to Gist
I put some scenarios at the bottom. Please take a look and I'd love to hear feedback from anyone (about anything!)
Thanks :)

@sallyhong I like the ideas. Just thinking about append_new argument; it makes the transform_columns function more like an 'assignfunction. My thought is thattransform` function should just transform(mutate) the columns, and not create new columns. Just my opinion, others might have a different opinion.

Very good point @samukweku . I was wrestling with this as R has two functions (mutate vs mutate_at) depending on whether or not you want to create a new column or overwrite the old column.
I decided that I didn't like the idea of changing a column contents without knowing that I did (e.g. providing a transform_dict with append_new=False, and wanted it as a default to clearly indicate which columns were changed.
Or maybe we can just raise a warning if a user changes a column without a name and suggest they use df.assign for those columns instead?  Not sure, but I'm not too attached to my code so I'm happy to change/update it :)

@sallyhong I like what you've done there! I am also wondering, what if the default suffix was not a fixed label, but instead the __name__ attribute of the function passed in? This would be magical :tada: for users. For functions that are anonymous (they don't have a __name__ attribute), such as lambdas, the _new can be the baseline default.

Thanks @ericmjl. I never knew of the __name__ attribute.  Let me do some research and learn about this!

@ericmjl , great idea! I tried it out with a test function too (named "add_two")
https://gist.github.com/sallyhong/627db0810ee917df0f978b8557245a61


[Storybook] RTL feature on the Toggle component is messed up

Detailed description
Steps:

Open the storybook
Click on Toggle component
Click on RTL sub-tab
Click on the RTL toggle - untoggled

Actual Result: Toggle label is hidden under the component
Expected Result: Toggle label must be visible
NOTE: all 3 types of toggle present problems

What browser are you working in?
Seen on Chrome, Safari, FF

What version of the Carbon Design System are you using?
Latest available at http://react.carbondesignsystem.com/

Hi 👋 thank you for reporting! You need to get RTL version of the CSS following the instruction at: https://github.com/carbon-design-system/carbon-components/blob/v10.2.0/docs/g11n.md - Once I did that I see the problem reported here doesn't happen.


fix: rules didn't match which start with undefine at-rules

@hzbhzb please fill the test specs and remove annotations


InvalidRegistrationDefinitionCreateRequest

I have followed the docs but I got below issues.
Scenario:  I have three subscriptions in my tenant, I have registered 2 subscriptions as a customer and left 1 subscription as a service provider but getting below error.
"error": {
"code": "InvalidRegistrationDefinitionCreateRequest",
"message": "The registration definition 'xxxxxxx' not allowed to use the 'xxxxxx' as ManagedByTenantId."
}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 85dc331a-0f34-f9a2-43d9-8ab7e0e635c6
Version Independent ID: 96c07c81-f84c-f47b-659c-b3d055aefb03
Content: Onboard a customer to Azure delegated resource management - Azure Lighthouse - Azure Lighthouse
Content Source: articles/lighthouse/how-to/onboard-customer.md
Service: lighthouse
GitHub Login: @JnHs
Microsoft Alias: jenhayes

Hi there -
This document describes how to onboard subscriptions from one tenant (i.e. a customer's tenant) so they can be managed by users in another tenant (i.e. a service provider's tenant). It sounds like you are working with three subscriptions in the same tenant, which is a different scenario where Azure delegated resource management would not be applicable. If I'm misunderstanding please let me know. #in-progress

@JnHs Thanks for the quick response
@sakaldeepyadav Please let us know if you have queries upon @JnHs's comment.

HI,
Yes, you are right, we need at least two tenants to test this. I have successfully completed this task using the doc with two tenants.
I recommend mentioning somewhere in the doc 'at least two tenants are required to complete this task one as an MSP and another as a customer'.
thanks
regards
sakaldeep

Great to hear you were able to make this work! We do mention that you need the tenant ID of two separate tenants, and that "the onboarding process requires actions to be taken from within both the service provider's tenant and from the customer's tenant." We'll continue to monitor this topic for additional feedback and clarify further as needed. I will close this now but please let us know if you have additional feedback. #please-close


RKE2 Provisioning: Cluster Options - Default Cluster Role for Project Members

Pick the default role for project members
apiVersion: provisioning.cattle.io/v1
kind: Cluster
metadata:
  name: #string
  annotations:
    {}
#    key: string
  labels:
    {}
#    key: string
  namespace: fleet-default
spec:
  cloudCredentialSecretName: do
  kubernetesVersion: v1.20.5+rke2r1
  rkeConfig:

#  defaultClusterRoleForProjectMembers: string

@deniseschannon , could you please clarify what defaultClusterRoleForProjectMembers should do? At this time it doesn't look like backend is using this field at all and there doesn't seem to be a field for this on the UI.

This field exists on appliedSpec on RKE1 clusters. Need to look into what functionality it delivers and have the equivalent available in RKE2 provisioning (if applicable). Moving back to triage in Team 2.

the field defaultClusterRoleForProjectMembers is already in the provisioning obj for RKE2 but is not used right now.
The fix will be taking use of this field for RKE2 provisioning.

In rancher:v2.6-head 0ad0def54,

if we set the value defaultClusterRoleForProjectMembers in the cluster.provisioning.cattle.io/v1 object, the value will be synced to the corresponding  cluster.management.cattle.io/v3 object, but not the other direction.
Although the value is set, it does not take any effect. There is no specific logic in the backend to use this value, even in the logic for v3 clusters.

Based on the above observation, first, I think we need to confirm the expected behavior for this value even though the field name is descriptive and self-explained. Then, once we better understand the usage case, we can determine how we want to implement it and which team to implement it: team2 or team1, or both.

@jiaqiluo isn't our goal here to just mimic the behavior of what RKE1 provisioned clusters do?
If that is the case, then I would expect that if a user sets the defaultClusterRoleForProjectMembers field on the v1 object, that gets trickled down to the v3 object, and subsequent project members on the cluster get the default cluster role.

@Oats87  Yep that is what we want to do. The problem is that Rancher and RKE1 do nothing when the field is set. The field is simply ignored, as far as I can tell.

I can confirm that this field is not used in either the backend or the frontend.

Closing it as "not needed" based on the comments above.


cargo: git_registry_url is not required field

Describe the bug
git_registry_url in the code is mentioned as Required: true , but the document says optional
I want to use http sparse index and not git_repository.
Artifactory version: 7.98.7
Terraform version : Terraform v1.9.0
terraform-provider-artifactory: v11.5.1
Requirements for and issue

[x] A description of the bug
[ ] A fully functioning terraform snippet that can be copy&pasted (no outside files or ENV vars unless that's part of the issue). If this is not supplied, this issue will likely be closed without any effort expended.
[x] Your version of artifactory (you can curl it at $host/artifactory/api/system/version
[x] Your version of terraform
[x] Your version of terraform provider

Expected behavior
git_registry_url should be optional
Additional context
Add any other context about the problem here.

@rayasm1 Thanks for the report! I've added this to our plan to update the code as well as documentation.


#ifdef usage to be changed to be #if defined()

Currently, any time we do conditional compilation, it is done using the #ifdef directive. To allow for compound conditionals such as A && !B, switch all usage of #ifdef to be #if defined() instead.

Task in progress by @danaack.

All #ifdef and #ifndef changes have been made. Changes are to be committed tomorrow.

Changes merged into development. Ref 11d9dda233


Release/1.5.x

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[ ] Did you read the contribution guide?
[ ] Did you update the docs? We use Numpy format for all the methods and classes.
[ ] Did you write any new necessary tests?
[ ] Did you update the CHANGELOG?

Type of Change

[ ] Examples / docs / tutorials / contributors update
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Improvement (non-breaking change which improves an existing feature)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes

Related Issue

Closing issues

Codecov Report

Merging #412 (eb849c0) into master (e4e4b31) will decrease coverage by 33.98%.
The diff coverage is 26.43%.

@@             Coverage Diff             @@
##           master     #412       +/-   ##
===========================================
- Coverage   87.47%   53.49%   -33.99%
===========================================
  Files          97       99        +2
  Lines        4736     5002      +266
===========================================
- Hits         4143     2676     -1467
- Misses        593     2326     +1733

Impacted Files
Coverage Δ

etna/clustering/distances/distance_matrix.py
32.83% <0.00%> (-60.61%)
:arrow_down:

etna/loggers/console_logger.py
51.72% <ø> (-37.94%)
:arrow_down:

etna/models/sarimax.py
43.33% <0.00%> (-52.62%)
:arrow_down:

etna/pipeline/autoregressive_pipeline.py
30.43% <0.00%> (-69.57%)
:arrow_down:

etna/transforms/datetime_flags.py
54.66% <ø> (-45.34%)
:arrow_down:

etna/transforms/filter.py
28.57% <0.00%> (-71.43%)
:arrow_down:

etna/transforms/gale_shapley.py
35.97% <0.00%> (-64.03%)
:arrow_down:

etna/transforms/holiday.py
40.00% <0.00%> (-60.00%)
:arrow_down:

etna/transforms/outliers.py
68.13% <0.00%> (-30.70%)
:arrow_down:

etna/transforms/power.py
86.66% <ø> (-6.20%)
:arrow_down:

... and 93 more

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 e4e4b31...eb849c0. Read the comment docs.


awk error during get_webrtc of ios

I've pulled down the build scripts from the master branch today (so that would be commit 7570628c93). I'm trying to build for iOS. Both get_webrtc and build_webrtc are generating the message below (illegal primary in regular expression). Hopefully it's not harmful.
.....
Get the current working directory so we can change directories back when done
If no directory where depot tools should be...
Change directory into the depot tools
Pull the depot tools down to the latest
Already up-to-date.
Go back to working directory
awk: illegal primary in regular expression ) |" at  |"
input record number 1, file
source line number 1
Using code signing identity
....

Seems like this is [a similar|the same] issue reported in #41?


reverse string using recursion

hey , they are not considering dsa,cp and algorithm repo
but you can contribute to this repo as a part of community :)
this will help many students to practice dsa

😭😭😭😭
Nuksaan to mera hua h na
9 contribution kr diye koi pull hi nhi ke rha koi excluded bta rha
On Sun, 3 Oct, 2021, 5:23 pm Avinash Singh, @.***>
wrote:

Merged #448 https://github.com/avinash201199/DSA-Questions/pull/448
into main.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/avinash201199/DSA-Questions/pull/448#event-5399648326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ3HXYYNT62W7JNTJYRCHR3UFA733ANCNFSM5FHKHQVA
.


Could not resolve _sentry-release-injection-stub

Hi, I'm using<EMAIL_ADDRESS>with @angular-builders/custom-esbuild@18 and the Angular build failed with this error:
✘ [ERROR] Could not resolve "/path/to/project/_sentry-release-injection-stub" [plugin angular-compiler]

I think it could be that the newer version of esbuild some how break this line: https://github.com/getsentry/sentry-javascript-bundler-plugins/blob/75a5d1debb8793a572ab495361b613138b452bb2/packages/esbuild-plugin/src/index.ts#L15
The only workaround that I could find is to set release.inject to false which would make the build succeed but then there's no debugID injected to the build output & so sentry-esbuild-plugin would just ignore and not upload any of our code artifacts.
[sentry-esbuild-plugin] Warning: Didn't find any matching sources for debug ID upload. Please check the `sourcemaps.assets` option.

Hi, would you mind providing a small repro example so we can take a closer look? Thanks!

Hi @lforst, I've created a test repo here:
https://github.com/ZeroX-DG/sentry-esbuild-demo
Although I don't have a test sentry org & auth token to replace to the config so I can't test if it's actually working.
You can fill in the sentry authentication key and run yarn build to see if the error actually occurs.

Thanks! We're a bit busy this week so I need to put this on the backlog. Feel free to investigate on your own in the meantime.

Following my investigation on #616 (thanks again for linking me to this issue), which is based on tsup (using esbuild under the hood), it seems that the onResolve and onLoad callbacks are only called for "internal" modules (i.e importing relative path).
I would believe that a fix could be to replace all occurrences of _sentry-release-injection-stub and _sentry-debug-id-ingestion-stub with ./_sentry-release-injection-stub and ./_sentry-debug-id-ingestion-stub, those would be considered local and correctly processed by esbuild.
My current workaround is to add this to my tsup.config.ts:
  noExternal: ["_sentry-debug-id-injection-stub"],

Which forces esbuild to consider the file as a local file. the generated file looks correct:
// _sentry-release-injection-stub
var _global = typeof window !== "undefined" ? window : typeof global !== "undefined" ? global : typeof self !== "undefined" ? self : {};
_global.SENTRY_RELEASE = { id: "012ec3c3a45c4f3d921e71aeb5a29abeeaab6b98" };

// sentry-debug-id-stub:_sentry-debug-id-injection-stub?sentry-module-id=996d7825-4b8c-4053-a10c-9e9232bbeefb
!function() {
  try {
    var e = "undefined" != typeof window ? window : "undefined" != typeof global ? global : "undefined" != typeof self ? self : {}, n = new e.Error().stack;
    n && (e._sentryDebugIds = e._sentryDebugIds || {}, e._sentryDebugIds[n] = "5ea6224e-be36-45c9-b0c7-ea8b9fb1af0f", e._sentryDebugIdIdentifier = "sentry-dbid-5ea6224e-be36-45c9-b0c7-ea8b9fb1af0f");
  } catch (e2) {
  }
}();

// src/instrument.ts

I don't know when this broke and if esbuild changed the way plugins are working but I would be glad to provide you more information if needed.

@ex0ns that is some nice investigation. Thanks! A bit of an annoying nuance that esbuild has.
Do you feel like contributing the change or should we take care of it? Maybe you're able to try it out for your setup and verify whether it works!

I will try to contribute and add a fix, but I can't promise anything yet.
After trying the above fix, the issue I'm now facing https://github.com/getsentry/sentry-javascript-bundler-plugins/issues/608 which I did not get any chance to investigate.

Re the first issue:

I would believe that a fix could be to replace all occurrences of _sentry-release-injection-stub and _sentry-debug-id-ingestion-stub with ./_sentry-release-injection-stub and ./_sentry-debug-id-ingestion-stub, those would be considered local and correctly processed by esbuild.

The unlucky thing is that it needs to be absolute for older eslint versions 🤔 Maybe we just drop support and release a major.


first commit - created notebook with stages

added first notebook

May our code bring joy to all who stumble upon it. Branch on ma boy.


[PT Run] Something went wrong - Destination array was not long enough exception

Microsoft PowerToys version
0.68.1
Installation method
Microsoft Store
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19045.0
IntPtr Length: 8
x64: True
Date: 08/03/2023 5:34:06 PM
Exception:
System.ArgumentException: Destination array was not long enough. Check the destination index, length, and the array's lower bounds. (Parameter 'destinationArray')
at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length, Boolean reliable)
at System.Array.Copy(Array sourceArray, Int32 sourceIndex, Array destinationArray, Int32 destinationIndex, Int32 length)
at System.Collections.Generic.List`1.System.Collections.ICollection.CopyTo(Array array, Int32 arrayIndex)
at System.Collections.ArrayList.InsertRange(Int32 index, ICollection c)
at System.Windows.Data.ListCollectionView.b__1_0()
at MS.Internal.Data.SynchronizationInfo.AccessCollection(IEnumerable collection, Action accessMethod, Boolean writeAccess)
at System.Windows.Data.BindingOperations.AccessCollection(IEnumerable collection, Action accessMethod, Boolean writeAccess)
at System.Windows.Data.ListCollectionView.RefreshOverride()
at System.Windows.Data.CollectionView.RefreshInternal()
at System.Windows.Data.CollectionView.PostChange(NotifyCollectionChangedEventArgs args)
at PowerLauncher.ViewModel.MainViewModel.<>c__DisplayClass127_0.b__0()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
✔ Expected Behavior
Was playing around how many search results to produce for powertoys run
❌ Actual Behavior
while testing the number of search outputs it crashed
Other Software
No response

Hi @ratulsarker
Do you have more information on your test?
I was able to test 5k+ search results with no crashes.
It would help if I can reproduce the crash to investigate it further.

/bugreport

this is #19707

/dup https://github.com/microsoft/PowerToys/issues/19707


fix: Fix event cron job in 60 seconds

Issue #205
Description of changes:

It should be 60 seconds not 1 second.
Add back lacked field to Cron expression.

@paultung Thank you for reporting this. This is the same as https://github.com/awslabs/aws-instance-scheduler/pull/201
We will address this in the next release

@paultung The cron expression has been updated in the source code.


Page reload changes location to server root

Hi, I like your approach and would like to use your alpinejs-router in a project. However I need a working router for a page in a sub directory of the servers root like /calculator/. When I load your example the first time the URL is
http://<IP_ADDRESS>:5500/examples/index.html, however all routes in the example transform the URL to http://<IP_ADDRESS>:5500/#/ instead of http://<IP_ADDRESS>:5500/examples/#/.
Is there any way I can configure the router to work in a sub directory of the servers root?
Thanks, Bernd

Have you tried configuring the base?

Thanks. I didn't see that.


Documentation should include how packages can authenticate against private registry

Currently, the kapp-controller packaging docs do not include recommended examples on how an InstalledPackage can reference a Package that requires authentication against a private registry.
As of now, it seems like for this to take place, a package author needs to configure the package with a secretRef for the image or imgpkg bundle. The user then must have this secret created in the namespace where an InstalledPackage is created so its underlying App can utilize the secret.
If the above workflow makes sense as we think more about authentication approaches, we should include this in the packaging API docs somewhere to help support users in need of this workflow.

Superseded by #244 to capture the new workflow


Reduce the back-n-forth between JNI and Java even more

Pass Strings as UTF-8 byte arrays between the Java code and the native library
to improve the performance.
Also remove the declaration of value_bytes(), because this function has never
been implemented in the native code.
See https://github.com/xerial/sqlite-jdbc/pull/162

@mkauf Thanks for the improvement. String.getBytes(UTF-8) has JVM specific optimization so it should be fast enough.

Thank you for merging!


Error copying data to system clipboard in docker container

Describe the bug
Can not copy data to clipboard in docker container.
To Reproduce

Dockerfile

FROM python:3.11

RUN pip install harlequin-mysql

Build docker image

docker build -t harlequin-mysql:latest -f ./Dockerfile .

Run docker container

docker run --rm -it \
harlequin-mysql:latest \
harlequin -a mysql -h localhost -p 3306 -U root --password example --database dev

# or

docker run --rm -it \
harlequin-mysql:latest \
sh -c "harlequin -a mysql -h localhost -p 3306 -U root --password example --database dev"

# or

docker run --rm -it \
harlequin-mysql:latest \
bash -c "harlequin -a mysql -h localhost -p 3306 -U root --password example --database dev"

Execute Ctrl + C

Expected behavior
Should be able to copy and paste column data.
Actual behavior
A clear and concise description of what happened; please include screenshots or animated gifs of Harlequin if possible.
Please refer To Reproduce section.
Additional context
What is the output of harlequin --version?
harlequin, version 1.13.0

Installed Adapters:
  - mysql, version 0.1.2
  - duckdb, version 1.13.0
  - sqlite, version 1.13.0

What database adapter are you using with Harlequin? (Default is DuckDB)
MySQL
Can you tell us more about your system?

Terminal: MobaXterm

For example, for my system, these are:

Bash

I think this is expected -- you'll need an x window manager in your container to use a clipboard. See https://harlequin.sh/docs/troubleshooting/copying-and-pasting

(The docs are a little out of date; copying from the results viewer or data catalog now works the same way as copying from the query editor)


add sincospi

Fixes https://github.com/EnzymeAD/Enzyme.jl/issues/735 requires https://github.com/EnzymeAD/Enzyme/pull/1114

Codecov Report
Patch coverage: 100.00% and project coverage change: -12.39 :warning:

Comparison is base (0c1b971) 77.12% compared to head (49708f2) 64.74%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #736       +/-   ##
===========================================
- Coverage   77.12%   64.74%   -12.39%
===========================================
  Files          18       18
  Lines        7205     6841      -364
===========================================
- Hits         5557     4429     -1128
- Misses       1648     2412      +764

Impacted Files
Coverage Δ

src/compiler/interpreter.jl
24.75% <ø> (-73.33%)
:arrow_down:

src/compiler.jl
65.10% <100.00%> (-12.66%)
:arrow_down:

... and 13 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Error when encrypting hotkey

Describe the bug
Following instructions here when trying to encrypt the hotkey I get the error:
Error: argument command: invalid choice: 'new_hotkey' (choose from 'subnets', 's', 'subnet', 'root', 'r', 'roots', 'wallet', 'w', 'wallets', 'stake', 'st', 'stakes', 'sudo', 'su', 'sudos', 'legacy', 'l', 'info', 'i')

To Reproduce

Create hotkey as per documentation
Run btcli new_hotkey --use_password

Expected behavior
Not to get error.
Screenshots
No response
Environment
MacOS 14.1, Bittensor 6.6.0
Additional context
No response

This is an error in documentation, nice catch! We will update this in the next release
here is the correct usage:
btcli wallet new_hotkey
Bittensor's btcli uses subcommands.


[Windows] "npm run dist" error on a clean install.

Prerequisites

[x] I have read the documentation;
[x] In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.

Description
On a clean install "npm run dist" is currently failing.
ERROR in ./utils.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./../node_modules/timers-browserify/main.js in D:\dev\temp\temp\react-jsonschema-form/src
 @ ./utils.js 1:0-54

This appears to be a dependency issue of some kind.  Replacing the entire node_modules directory with the node_modules directory from an earlier (and still working) version of react-jsonschema-form appears to work, so it's likely it will not be reproducible unless you start with a completely clean installation.  Running npm run dist on an installation a few weeks old will likely still work I think, you'll need to completely recreate your node_modules.
I've had a friend replicate it on his machine as well.
Steps to Reproduce
(on Windows ... not sure if replicable elsewhere on other OS's)
git clone https://github.com/mozilla-services/react-jsonschema-form.git
cd react-jsonschema-form
npm install
npm run dist

ERROR in ./utils.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./../node_modules/timers-browserify/main.js in D:\dev\temp\temp\react-jsonschema-form/src
 @ ./utils.js 1:0-54

Expected behavior
npm run dist should not error.
Actual behavior
ERROR in ./utils.js
Module not found: Error: Cannot resolve 'file' or 'directory' ./../node_modules/timers-browserify/main.js in D:\dev\temp\temp\react-jsonschema-form/src
 @ ./utils.js 1:0-54

Version
Current.

Damn, I don't have any Windows machine/vm at hand to investigate this. Would any Windows user be kind enough to work on fixing this?

So it doesn't seem many people are hit by this issue, not it seems many want to help investigating this. I'm gonna close the issue, though feel free to reopen if you're willing to help :)
Thanks for your understanding.

I solved this on Windows by adding the following to the webpack config:
resolve: {
  root: [
    path.join(__dirname, 'src'),
    path.join(__dirname, 'node_modules')
  ]
}

Unable to test on other platforms at this time.


Fix Nightly 30th Aug

[ ] Test FAILED gcp/test/test_users.py::test_users - AssertionError: Unexpected user account found in /etc/passwd: markus_guertler (fmi:<PHONE_NUMBER>6)
-> @mguertler to remove key from the google cloud project.

[ ] google.api_core.exceptions.ServiceUnavailable: 503 SERVICE UNAVAILABLE ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS: The zone 'projects//zones/' does not have enough resources available to fulfill the request.  '(resource type:compute)'. (fmi:<PHONE_NUMBER>8
-> @MrBatschner defines a zone that is less busy.

More permanent fix for first bullet point: PR #2310

Nightly completed successfully.

I see nightly is good. @MrBatschner , can we close this one?

Issue 1 (Markus' user) seems resolved, issue 2 (ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS) hit us in today's nightly again. @gehoern @MrBatschner

gcp platform tests currently run in europe-west4-c which seems out of resources on Google side. Need to change to a different zone by modifying the GCP_ZONE secrets at https://github.com/gardenlinux/gardenlinux/settings/secrets/actions to another zone (a, b) according to https://cloud.google.com/compute/docs/regions-zones. Note: we must not change the region to e.g. europe-west3 as this region does not offer ARM64 machine types.

Follow up: https://github.com/gardenlinux/gardenlinux/issues/2315

GCP_ZONE was set to europe-west4-a which seems to have solved the problem with ZONE_RESOURCE_POOL_EXHAUSTED_WITH_DETAILS. Follow-up #2315 should be done do make reconfiguration of such elements easier in the future (we should not have to guess the current value as we have to when using GitHub secrets for things like GCP_ZONE).

thank you @MrBatschner


Add "On Hold" (repeating) actions feature; Also with new TP Settings support.

Added support for "On Hold" type Touch Portal actions with a configurable repeat time.
All current actions which may make sense to repeat (such as for control surfaces or AP adjustments) should now be available in the "On Hold" TP button configuration page. The generated documentation now shows which actions can be held.

Note that "On Hold" actions do not trigger upon first button press, you need to  configure an "On Pressed" action as well, which is a bit more setup but is more flexible.
in case a single press should do some different action.

Added Action: Held Action Repeat Rate: Increment/Decrement 50ms or choose one of several presets. The last rate set this way is saved to persistent settings in TP.
Added State: Current Held Action Repeat Rate
Added support for Touch Portal plugin Settings (in the TP Settings -> Plug-ins -> MSFSTouchPortalPlugin page).
Added setting to control automatic connection to SimConnect upon TP (or plugin) startup. When disabled, connection must be made manually via the existing Connect action.

Changes are best reviewed by individual commit.
My main goal was to add repeating actions, so for example I can just hold down my Alt. Adjust bug button until I get to my value, instead of repeated presses. The first 3 commits do that, with a preset repeat delay rate (450ms).
But a set rate is limited (too fast for some things, too slow for others) so I decided to add a Setting for it that the user can control and would persist between runs.  Long story short, this is how the other 2 commits happened, adding overall support for TP Settings.  It's not ideal combining changes like this and I can certainly break things up more (I have everything on separate branches) but with all the other changes/PRs this is getting quickly confusing and interdependent.
On that note, this version is going to have 2 minor conflicts with one or two of the other pending PRs I submitted.  Once those are decided (merged or not), I can rebase this branch on top to ensure no conflicts.  It would be better to get those others out of the way before merging this one, hence I'm marking it as a Draft for now.  But I wanted to get the review/comments flowing.
Thanks!
-Max

I have consolidated and published all the changes so far (including my other PRs) on my fork's main branch: https://github.com/mpaperno/MSFSTouchPortalPlugin/tree/mp/main
This includes the updated DOCUMENTATION and CHANGELOG
I also have made a Release v0.5.4-mp of all the changes for others to test with: https://github.com/mpaperno/MSFSTouchPortalPlugin/releases

I'll submit PRs and request/wait for reviews before merging anything, unless you tell me otherwise  :)
Also, could you drop me a note at<EMAIL_ADDRESS>?  (You'd think GitHub collaborators would have some private way to contact each other, but noooo...)

There are some conflicts that need to be resolved.

There are?  GH says no conflicts...?  I haven't checked with actual git.

Weird, it shows for me:
This branch cannot be rebased due to conflicts

Something strange is going on... my git just hangs when trying to merge this branch into the current !release/1.0, and so does a rebase of this branch onto !release.  I'm tempted to push the GH Merge button just to see what happens...  :)


Testing pull request email notifications

Testing if emails are triggered to the dev mailing list when a pull request is opened

closing test pull request.