Convert pixel width to mm

I want to convert the width of an object in the image from pixels to cm: depends on this link  I need to calculate this equation:
object_image_size = (real_object_size * lens_focal_length)/object distance
From your website, the cameras have sensor 1/3" which is 4.8X3.6MM, but you show the focal length in pixels is that mean for HD720 the focal length is (700*0.004 ) = 2.8 MM. is that right?

I'm joining the question. It is also important for me. Or do you recommed to convert depth to PCL and then check the object dimensions?

Please, can we get an answer to this question?

I may not have understood the question but since the depth information is available, and you have 2 "bounds" pixel. You can get the 3D points coordinates for each and compute the euclidian distance. That will give you the object size in metrics from 2 pixels.
Here is a snippet of what I mean :
import pyzed.sl as sl
import math
import numpy as np

def main():
    zed = sl.Camera()

    init_params = sl.InitParameters()
    init_params.coordinate_units = sl.UNIT.UNIT_METER

    err = zed.open(init_params)
    if err != sl.ERROR_CODE.SUCCESS:
        exit(1)

    runtime_parameters = sl.RuntimeParameters()
    point_cloud = sl.Mat()

    zed.grab(runtime_parameters)
    zed.retrieve_measure(point_cloud, sl.MEASURE.MEASURE_XYZRGBA)

    # Object 2D bounds
    b1_u = 110
    b1_v = 200

    b2_u = 150
    b2_v = 200

    # Get the 3D coordinates for these positions
    err, b1_3d_value = point_cloud.get_value(b1_u, b1_v)
    err, b2_3d_value = point_cloud.get_value(b2_u, b2_v)

    # Euclidian Distance between the two 3D points
    dist = math.sqrt((b1_3d_value[0] - b2_3d_value[0]) * (b1_3d_value[0] - b2_3d_value[0]) +
                            (b1_3d_value[1] - b2_3d_value[1]) * (b1_3d_value[1] - b2_3d_value[1]) +
                            (b1_3d_value[2] - b2_3d_value[2]) * (b1_3d_value[2] - b2_3d_value[2]))

    print("Object size ", dist)
    zed.close()

if __name__ == "__main__":
    main()

Would that work for your application?

Thanks, @adujardin for the reply. But I am working on estimating the depth using deep learning model and I am using the Zed camera depth view as the ground truth. So, I need to know the focal length in mm to calculate the depth from the output of the model. I hope, I clarify why I need the length in mm.

The focal in mm can be found by using this formula :
f_mm = (fx+fy) / 2 * pixel_size_mm

If you know exactly the size of the object and you are able to detect it, then you could have an estimation of the distance using the method described at the link.
However, if the deep learning estimation algorithm output the disparity then you can compute the 3D coordinates. The "metric" part is provided by the distance between the 2 camera sensors, also known as the baseline, not the focal.
You can't compute absolute distances with only 1 camera (and no other knowledge), even with calibrations.
The depth is computed from the calibrated focal in pixel, the disparity between the left and right image and the transformation matrix between the 2 sensors.
depth = focal_x * baseline / disparity
x = ( (u - principal_point_x) * depth) / focal_x
y = ( (v - principal_point_y) * depth) / focal_y

If the algorithm outputs a pseudo depth, for instance using only the left image, then you can't get metrics values without estimating first the absolute scale (similar to the monocular odometry problem).

Thank you @adujardin, for explaining.


Solr CrossDC Consumer Helm chart.

Simple Helm chart with a deployment descriptor, and a Jib-based image build.
I added a wrapper to make it easier to pass configuration properties through environment. We could also roll this into the base Consumer class.

So I'm not against this having a docker image, but when we merge this cross dc stuff into the Solr repository, it will likely not have its own docker image (much like the prometheus exporter). So I'm not sure its worth merging this in the meantime.
Also the helm chart is very lightweight and could really be replaced by a kubectl run <name> --image=solr/solr-crossdc-consumer:latest --env="VARIABLE=value", so I'm not sure it's really bringing much to the table. Might be a useful thing to add to the Solr Operator at some point though.

@HoustonPutman thanks, this makes sense - closing.


BENCH-1769: Install latest version of R in dataproc startup script

Adds an initialization action to install the latest version of R on all dataproc cluster nodes. See https://verily.atlassian.net/browse/BENCH-1769 for more details.
For the short term, we need to put this script in our public gcs bucket as initialization scripts only supports public gcs files, so we can't use a github file url.
Followup work: Modify WSM to pass this script as an initialization action on cluster creation.

@mbookman @yuhuyoyo
The R kernel wasn't working right after installing a new version of R. Added changes to:

Install R jupyterlab kernel
Allow stdout, stderr to stil output so that users can also debug issues via the initialization actions output files
Make sure the output file is successfully created in worker nodes too.


(GH-1901) Change 'master' references to 'main'

This updates documentation, scripts and github workflows to point to the
'main' branch instead of 'master'.

CLA signed by all contributors.


REQ/REP hangs when sending messages larger than 1MB

The Req socket hangs when I try to send a message larger than 1MB.  I have the same problem with both IPC and TCP.   Example:
extern crate scaproust;

use scaproust::*;

fn recv() {
    loop {
        let mut session = SessionBuilder::new().with("ipc", Ipc).build().unwrap();
        let mut socket = session.create_socket::<Rep>().unwrap();
        socket.bind("ipc:///tmp/s").unwrap();

        println!("Received message of length: {}", socket.recv().unwrap().len());
        socket.send(vec![0]).unwrap();
    }
}

fn send() {
    for n in [1e3,1e4,1e5,0.9e6,1e6,1.1e6].iter() {
        let msg = vec![0;*n as usize];

        let mut session = SessionBuilder::new().with("ipc", Ipc).build().unwrap();
        let mut socket = session.create_socket::<Req>().unwrap();
        socket.connect("ipc:///tmp/s").unwrap();
        socket.send(msg).unwrap();
        socket.recv().unwrap();

        std::thread::sleep(std::time::Duration::from_millis(100));
    }
}

fn main() {
    send();
}

Hi,
Each socket has an option to limit the size of incoming messages. The default value for this option is 1 MB. You can change this value using the RecvMaxSize variant.
socket.set_option(ConfigOption::RecvMaxSize(64 * 1024));

Regards,
Benoît

Ah.. I didn't even think to look for an option like that.  Thanks, that fixes it.
Is it not possible/desirable for the sending socket to return an error when the receiving socket's limit is exceeded rather than hang?

Looks like I spoke too soon without actually testing it..
It looks like RecvMaxSize isn't marked as a generic socket option, so it just returns an error when trying to set.  This fixes it:
diff --git a/src/core/config.rs b/src/core/config.rs
index 3bf7806..c4feefc 100644
--- a/src/core/config.rs
+++ b/src/core/config.rs
@@ -118,6 +118,7 @@ impl ConfigOption {
             ConfigOption::Linger(_)       |
             ConfigOption::SendTimeout(_)  |
             ConfigOption::SendPriority(_) |
+            ConfigOption::RecvMaxSize(_)  |
             ConfigOption::RecvTimeout(_)  |
             ConfigOption::RecvPriority(_) |
             ConfigOption::RetryIvl(_)     |

The documentation is also incorrect.  Setting the max size to 0 doesn't remove the limit.

Yep, just ran into the same problem(I had tried the option from the docs before seeing the message and coudln't figure out why it was considered invalid). Error message:
Custom { kind: InvalidInput, error: StringError("option not supported") }',

Regarding the sending socket behavior in the case the receiving socket chooses to discard the message, the correct behavior would be to have the receiver not only drop the message but also close the connection. This should prevent the sender from hanging. I will investigate this later on.

The problem with REQ/REP is that REQ will retry to send periodically, and as soon as the automatic reconnection occurs.


Use full file paths within DOI archives

Currently the ihm_dataset_other fields "doi" and "content_filename" are used to refer to a DOI of a zip archive and a file within that archive.  In our nup84, mediator and exosome example data the currently supplied content_filename is not actually the full path within the zip archive -- it excludes the top level directory listed in the archive.  In the nup84 example data the "content_filename" is given, for example, as "data/ScNup84_7-488_506-726_new.pdb", but the actual path in the archive is "integrativemodeling-nup84-a69f895/data/ScNup84_7-488_506-726_new.pdb".  Currently the top level directory is not being included because it is technically difficult to determine in an automated fashion according to Ben Webb.  That top level directory name includes the GitHub repository version string and is automatically included in an upload to Zenodo.  These details are specific to current Sali lab practices and should not alter the fact that "content_filename" should always be a full path to a file in the referenced archive.

The nup84, mediator, and exosome example IHM files should be changed to list the full paths within the archives.

Should be resolved by 47bb7b7b.


wtf is this for?

hey novalty
stumbled upon this repo whilst shilling asdf on reddit, and I'm curious why dasel would need an asdf plugin? just curious bro

any tool can have an ASDF plugin. It's a good way to put tools and their versions as dependencies in a repo, and install them easily with asdf install.


DOC: Remove the "Basic functions" section from the SciPy tutorial.

Reference issue
To fix #12413
What does this implement/fix?
Removed the "Basic functions" section from the SciPy tutorial.
The "Basic Functions" section of the SciPy tutorial is actually a small NumPy tutorial. NumPy has great documentation, including tutorials, so I think we can simply remove this entire section.

Perhaps instead of completely removing this section, it should be demoted to a short paragraph in the introduction stating a basic understanding of NumPy is required and links to their tutorials?

Perhaps instead of completely removing this section, it should be demoted to a short paragraph in the introduction stating a > basic understanding of NumPy is required and links to their tutorials?
I think that is good idea.
What do you think? @WarrenWeckesser

I updated code using @peterbell10 's idea.

I'd say that linking to NumPy and how to find docs is already covered in the Introduction section: http://scipy.github.io/devdocs/tutorial/general.html. I don't quite see why we would want to keep a Basic functions section in the top-level overview of tutorials for a redundant couple of lines? Removing this entry would be good:

Thank you for reviewing. I didn't know there is a doc link in the introduction. I agree. I deleted it again. PTAL.

I think removing these files and tweaking doc/source/tutorial/general.rst was what @peterbell10 meant. That file could use a more extensive makeover, so let's not block merging this PR on it.
In it goes, thanks @AtsushiSakai.


[FEA] [follow-up] Parse just time to timestamp

Is your feature request related to a problem? Please describe.
This is from: https://github.com/NVIDIA/spark-rapids-jni/pull/1539#issuecomment-1894854381
Implements just time format:
// has no yyyy-MM-dd parts:

[h]h:[m]m:[s]s.[ms][ms][ms][us][us][us][zone_id]

T[h]h:[m]m:[s]s.[ms][ms][ms][us][us][us][zone_id]
Spark link:
val localDate = if (justTime) {
LocalDate.now(zoneId)
}

Not planing work on this for release 24.04, unassign it from me.


Fix a bug for onecycle scheduler usage in Pytorch Lightening Version

I've observed a performance degradation when employing the onecycle scheduler, which appears to diverge from the results presented in your report. Upon investigation, I identified the source of the issue to be the lr_scheduler_step function defined within openstl/methods/base_method.py. The current implementation is as follows:
def lr_scheduler_step(self, scheduler, *args, **kwargs):
        scheduler.step(epoch=self.current_epoch)

However, the onecycle scheduler operates on a per-iteration basis rather than per-epoch. Therefore, I suggest modifying the function to simply invoke scheduler.step() without passing the epoch, as shown below:
def lr_scheduler_step(self, scheduler, *args, **kwargs):
       scheduler.step()

This adjustment should align the scheduler's step function with the expected behavior for onecycle scheduler, potentially resolving the observed performance degradation.

Thank you a lot for your valuable suggestion! There is a conflict between lr_scheduler_step and configure_optimizers. I think removing the lr_scheduler_step will help.

I have fixed this bug in the commit a6e0dd3.


limit RBAC hwameistor-role permissions

What this PR does / why we need it:
fix #1460,#1457
Special notes for your reviewer:
Does this PR introduce a user-facing change?

cc @FloatXD @peng9808


Do we have a list of version.sub options somewhere?

Is there a list of the available string-replacement options that can be used in the url stanza for version, like #{version.before_comma},#{version.dots_to_commas} etc, somewhere in the docs?

https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/stanzas/version.md is all we have I think.


[PE-D][Tester E] Filter command behaviour for sequence of keyword and command is not aligned with UG.

In the UG, it states that the sequence of the command and keywords doesn't matter, which is not shown when i try Google/c.

Labels: severity.High type.FunctionalityBug
original: nubnubyas/ped#6

The UG was vague, now has been fixed to show the exact format.

Order refers to the keywords, not the order of text. UG updated, but marked as invalid.


mailto: must be in the list of protocols

This is the another attempt to fix the issue https://github.com/orbikm/mkdocs-ezlinks-plugin/issues/48 "()[mailto:*] must be treated as a protocol to avoid link conversion"
The fix allows<EMAIL_ADDRESS>to be treated as one of the protocols and not apply the conversion to this link type.
PS This is the copy of PR https://github.com/orbikm/mkdocs-ezlinks-plugin/pull/50

Any ETA of a review/release of this PR?


fix: update nguniversal/express-engine token path

update @nguniversal/express-engine to the latest version
update breaking changes in express-engine for the REQUEST token path
rollup barked at me to use a different configuration syntax, so i updated that too.

Hey @brendanairvuz, you have closed this PR. Are you planning on submitting another PR which fixes the issue?

Yes. I ran into issues with the tests failing because the demo downloads
the published ngx-device-detector from npm. Do you have any suggestion for
ways around this?
On Sat, Mar 3, 2018 at 8:45 AM, Ahsan Ayaz<EMAIL_ADDRESS>wrote:

Hey @brendanairvuz https://github.com/brendanairvuz, you have closed
this PR. Are you planning on submitting another PR which fixes the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KoderLabs/ngx-device-detector/pull/28#issuecomment-370152511,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfWfiYWScR5cVeaZXjoo8AM99FjVYrrNks5taqxygaJpZM4SaiMn
.

@brendanairvuz I merged it and released the newer version. However, the tests still fail for some reason. And I'm unable to get the AOT build compiled as well.


Replaced 'Message was Sent' with guild rank tag in the Discord embed

A lot of people wanted a way to see guild ranks in the Discord message so here it is 🤷
Personally I think this looks much nicer than using colours for each rank :)

I've changed it so if there is no guild tag on a user it will default to Member, hopefully this fixes it!


Send to Interactive is not available

Hello,
After a fresh installation of VS2019 community edition preview, the command “Send to Interactive” is not available. I have tried switching environments, installing new ones, repairing installation, uninstalling and reinstalling, etc. Ctrl + Enter does not work either and the command does not appear in the contextual menu.
With VS2017 community edition, it works right in the same machine, not configuration needed, just Alt + I.
Thanks.
David

So sorry about that. It's broken in 16.0 Preview 2. We've fixed it for the upcoming Preview 3.
https://github.com/Microsoft/PTVS/issues/4954

Ok, thanks,


Add a new minSelectValues prop to RangeDatePicker

Closes #2467
Description
Add a new minSelectValues prop to RangeDatePicker.

@Shunii85 @108yen
Hi, have you finished revising your review?If so, please submit the review again.

@Shunii85
Hi, conflicts appear to be occurring. Please fix.


Responsive design is not working

I followed the ratio on the phone so it was not very responsive, but thank a lot you for reviewing ^.^!!!

Hmm probably because of your browser

try resizing horizontally 😅


[e2e]: nodejs tag main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.303
Run: https://github.com/slsa-framework/example-package/actions/runs/8843819660
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.303
Date: Fri Apr 26 06:05:36 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.304
Run: https://github.com/slsa-framework/example-package/actions/runs/8857792893
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.304
Date: Sat Apr 27 06:09:11 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.305
Run: https://github.com/slsa-framework/example-package/actions/runs/8865508333
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.305
Date: Sun Apr 28 06:07:49 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.307
Run: https://github.com/slsa-framework/example-package/actions/runs/8890035008
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.307
Date: Tue Apr 30 06:07:03 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.308
Run: https://github.com/slsa-framework/example-package/actions/runs/8906040825
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.308
Date: Wed May  1 06:08:12 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.309
Run: https://github.com/slsa-framework/example-package/actions/runs/8919335139
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.309
Date: Thu May  2 06:05:57 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.310
Run: https://github.com/slsa-framework/example-package/actions/runs/8934776354
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.310
Date: Fri May  3 06:06:04 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.311
Run: https://github.com/slsa-framework/example-package/actions/runs/8948475773
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.311
Date: Sat May  4 06:08:37 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.312
Run: https://github.com/slsa-framework/example-package/actions/runs/8956150483
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.312
Date: Sun May  5 06:07:44 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.313
Run: https://github.com/slsa-framework/example-package/actions/runs/8964705285
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.313
Date: Mon May  6 06:06:22 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.314
Run: https://github.com/slsa-framework/example-package/actions/runs/8980431853
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.314
Date: Tue May  7 06:06:49 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.315
Run: https://github.com/slsa-framework/example-package/actions/runs/8997038838
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.315
Date: Wed May  8 06:06:56 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.316
Run: https://github.com/slsa-framework/example-package/actions/runs/9013107602
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.316
Date: Thu May  9 06:07:00 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.317
Run: https://github.com/slsa-framework/example-package/actions/runs/9027998626
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.317
Date: Fri May 10 06:08:07 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.318
Run: https://github.com/slsa-framework/example-package/actions/runs/9041592901
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.318
Date: Sat May 11 06:05:40 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.319
Run: https://github.com/slsa-framework/example-package/actions/runs/9049283076
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.319
Date: Sun May 12 06:05:44 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.320
Run: https://github.com/slsa-framework/example-package/actions/runs/9057986363
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.320
Date: Mon May 13 06:08:28 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.321
Run: https://github.com/slsa-framework/example-package/actions/runs/9074518440
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.321
Date: Tue May 14 06:08:03 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/v36.0.322
Run: https://github.com/slsa-framework/example-package/actions/runs/9090761460
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.tag.main.default.slsa3.yml
Trigger: push
Branch: v36.0.322
Date: Wed May 15 06:08:52 UTC 2024
Tests are passing now. Closing this issue.


[Issue 5215,4601,5215][pulsar-io] Add jdbc sinks: postgres, mariadb, clickhouse

Fixes #5215  #4601 #5215
Motivation
Right now, the number of supported JDBC connectors is rather limited. There are a couple of open issues related to the missing connectors.
Modifications
As a base for this pull request, I took the changes from @huangdx0726 Unfortunately,  I was not able to reach him to merge my changes to his branch, so I created a new one.
The main modification is a split of one JDBC module into a bunch of them. One module serves as a core and provides the main logic of the connector. Other modules are real connectors and add only an appropriate JDBC driver.
Verifying this change
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes)
The default values of configurations: (yes)
Anything that affects deployment: (yes / don't know)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (docs / JavaDocs)

I would like to confirm that this is the right way and after that, I can change existing documentation for the MySQL and SQLite connectors, and add docs for the newly added connectors.
One more question is related to the MySQL connector and the #6656 Does it mean that we need to remove the MySQL connector?

@sijie could you please comment on this pull request? Do you think that it is a right approach? Shall I continue working on it and change/add docs? Did I miss something?

@vzhikserg I like the approach. This works out very well.
Just one minor comment - I don't think we can bundle MySQL in the release anymore because of the license issue. It might be worth removing that one from this pull request.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@sijie the pull request is ready for the final review.
The MySQL connector was removed from the distribution. Documentation on how to use the MySQL connector was substituted with the Postgres connector. The integration tests were also updated to use Postgres.


Question about no_weight_decay in the code of ViT

Hi @hila-chefer, I have a question about the no_weight_decay function below:
https://github.com/hila-chefer/Transformer-Explainability/blob/23cac8e66c846454d59af4b1caac241626897077/baselines/ViT/ViT_new.py#L189-L191
I think it make sense to perform no_weight_decay for the parameters of embeddings, but I didn't find the reference of this function in your repo. Will you explain it for me?
Thanks :)

Hi @yztongzhan, thanks for your question 👍
For ViT implementation, I'm using this repo:
https://github.com/rwightman/pytorch-image-models
(which is a great source in general in my opinion).
no_weight_decay is not in use because I don't actually train the model (i.e., I don't initialize any optimizer), I used the pretrained weights.
I hope this answers your question, I'll update the code soon with a cleanup and remove all unused code to eliminate confusions.

Thanks for your reply! ☺


Documentation on SPOD Macros

http://old.haxe.org/manual/spod

I don't plan to cover this in the manual.


Fix toc

Titles and numbers overlap when the number is too large. In this PDF, the result of tests/test-big-toc.tex without the fix.

Thanks :)


Shovel URI examples are incorrect

Describe the bug
One of the example URI formats in the shovel-management plugin are wrong and wont work on 3.13.
The https://www.rabbitmq.com/docs/uri-query-parameters page is also wrong in it's example
Reproduction steps
The last example on the shovel management plugin URI example page is amqps://server-name?cacertfile=/path/to/cacert.pem&certfile=/path/to/cert.pem&keyfile=/path/to/key.pem&verify=verify_peer&fail_if_no_peer_cert=true&auth_mechanism=external
The uri query parameters documentation page is also wrong with the example for advanced.config
{amqp_client, [
{ssl_options, [
{cacertfile, "path-to-ca-certificate"},
{certfile, "path-to-certificate"},
{keyfile, "path-to-keyfile"},
{verify, verify_peer},
{fail_if_no_peer_cert, true}
]}
]}
fail_if_no_peer_cert is not accepted anymore with Erlang 26 and will fail with a not obvious error (for non erlang users like myself)
Expected behavior
Examples should work :-)
Additional context
No response

Anyone can open a PR for the documentation, you don't even need to file an issue first. Here is the relevant page:
https://github.com/rabbitmq/rabbitmq-website/blob/main/docs/uri-query-parameters.md

@lukebakken no problem I can do that one.
I have no idea how to start with the shovel-management plugin

PR #1933 added

Fixed by #1933

@lukebakken I have also put a PR in rabbitmq-server for the shovel-management PR #11318


fix for #23

The problem is that the < relation for intervals doesn't give a complete order, so cannot be used for sort.

Codecov Report

Merging #24 (4c75308) into main (8bd6eb6) will increase coverage by 3.55%.
The diff coverage is 73.33%.

@@            Coverage Diff             @@
##             main      #24      +/-   ##
==========================================
+ Coverage   50.93%   54.48%   +3.55%
==========================================
  Files           4        4
  Lines         161      156       -5
==========================================
+ Hits           82       85       +3
+ Misses         79       71       -8

Impacted Files
Coverage Δ

src/utilities.jl
12.50% <0.00%> (ø)

src/interval_unions.jl
53.44% <50.00%> (ø)

src/set_operations.jl
65.67% <100.00%> (+8.72%)
:arrow_up:

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 8bd6eb6...4c75308. Read the comment docs.

Fixes issue #23 (don't know why GH didn't add the reference)

Well spotted!


Arrow 8359

Hello @xhochy! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file dev/tasks/crossbow.py:

Line 694:80: E501 line too long (81 > 79 characters)

@github-actions crossbow submit conda-linux-gcc-py36-aarch64


Coerce isn't the right term

Very minor nitpick, but coerce means forcing something to happen, or to change. Does runtime's coerce method do anything apart from checking that an object is already conforming to the type?
(Otherwise, very interesting library!)

Fair enough, any suggestions? validate is probably the most correct term, but I already have that method as one that doesn't throw but returns a Result indicating success or failure. validateOrThrow? Kind of a mouthful.

assertType
checkType
assert
check
requireType
cast

I like check, short and sweet.


add fix command for eslint

What kind of change does this PR introduce?
Add's a new npm script: npm run fix to autofix eslint issues
Summary

https://twitter.com/samccone/status/895074832013864962

Thanks


Need to login after every question

Hi!
After every question I need to redo the login process due to 429 error - when starting chrome it doesn't open up my default login so I need to redo my whole google login process again.
Is there any way to fix this? I've tried to remove all users from chrome in order to make my gmail account default but it still just opens up as a new login

Hi there! Yes, this is a known issue and it's a side effect of the recent OpenAI throttling measures. Since we depend on 'unofficial APIs', I don't have a proper solution to this yet :(

Yes thanks for the explanation but what I'm after is that when vscode opens chrome it does with a blank setup - if it's possible to make it open the default profile or even a pre-selected one then wouldn't we automatically login to the last chatGpt login?

@o92design please update your extension. With v2.0 you will no longer need to login everytime after a question. Just make sure to keep the browser open, it'll be minimized automatically after successful login.

Yes - it works good now 👍


Fix gemspec dependencies test-kitchen logic

Description
This commit fixes gemspec version dependencies for test-kitchen.
Issues Resolved
kitchen-vro stopped working with latest chef-workstation package, because kitchen-vro had wrong dependency versions.
Error without fix:
E, [2024-02-05T15:29:55.975080 #4110] ERROR -- Kitchen: Message: Unable to activate kitchen-vro-1.0.0, because test-kitchen-3.3.1 conflicts with test-kitchen (~> 1.4, >= 1.4.1)

@damacus could you please take a look, i believe this fixes the incorrect version constraint introduced via https://github.com/test-kitchen/kitchen-vro/pull/10


Node properties window does not update to show newly imported volumes

Newly imported tiff files do not show up in an open Nodes Properties window. When the window is closed and opened again, the volume shows up.

Fixed in #186.


Fix file reads in the prefetched data

Summary
There is an error when reading bytes from log segment file to a ByteBuf in prefetched data. This PR fixes that error.
Test
Unit test

Codecov Report
Attention: Patch coverage is 0% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 18.22%. Comparing base (c56a1fd) to head (9d7bba7).

Files
Patch %
Lines

...ls/src/main/java/com/github/ambry/utils/Utils.java
0.00%
12 Missing :warning:

...va/com/github/ambry/store/StoreMessageReadSet.java
0.00%
5 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             master    #2734       +/-   ##
=============================================
- Coverage     70.66%   18.22%   -52.45%
+ Complexity    11565     2816     -8749
=============================================
  Files           833      833
  Lines         70912    70925       +13
  Branches       8527     8529        +2
=============================================
- Hits          50111    12925    -37186
- Misses        18178    56802    +38624
+ Partials       2623     1198     -1425

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Lgtm! Just a q.. what is the bug with current code?

In some partition, reading a whole blob out would fail because file channel won't return all the required bytes at one read. And if we fail three times, this would mistakenly mark this partition unavailable.


[$500]  Mentioning an email with double @ sign results in an invalid email mention

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open any chat
Type @ and select any email from suggestions
Move the cursor to the beginning
Add another @ sign
Hit the send button
Click on the mentioned email

Expected Result:
The valid email is mentioned
Actual Result:
Invalid email is mentioned
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.78-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/38435837/30ac83c8-54d6-4e7f-b85c-29c51703de6e
https://github.com/Expensify/App/assets/38435837/1a130972-b500-4fc1-96a7-dda7e465456c
https://github.com/Expensify/App/assets/38435837/6d52ffa5-8319-4dfc-8305-fabec4fed58d
https://github.com/Expensify/App/assets/38435837/8bdc424f-e2c4-4a13-b74f-372a7020ed7c
https://github.com/Expensify/App/assets/38435837/55a89672-3161-4291-93c3-c3675d3b7f76
https://github.com/Expensify/App/assets/38435837/d5cdfb6f-1ff6-460f-b607-3990adf6fb3f
https://github.com/Expensify/App/assets/38435837/4739b083-9660-4771-a34d-783e9d56e592
Expensify/Expensify Issue URL:
Issue reported by: @adeel0202
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1696445508377469
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~016783de9809fcb5bd
Upwork Job ID:<PHONE_NUMBER>857413120
Last Price Increase: 2023-12-07

Proposal
Please re-state the problem that we are trying to solve in this issue.
Mentions with Double leading @ redirect to the wrong route
What is the root cause of that problem?
To correctly calculate the display name or the login of the mentioned user, we only remove the leading @
using
displayNameOrLogin = props.tnode.data.replace(CONST.UNICODE.LTR, '').slice(1);

Which causes the navigation link to contain the extra @
What changes do you think we should make in order to solve the problem?
We can use the following regex to remove all the leading @ and correctly calculate the navigation link
 displayNameOrLogin = props.tnode.data.replace(/^((CONST\.UNICODE\.LTR)*@)*/, '')

What alternative solutions did you explore? (Optional)
N/A

Proposal
Please re-state the problem that we are trying to solve in this issue.
Mentioning an email with double @ sign results in an invalid email mention.
What is the root cause of that problem?
The root cause is replace regex of userMentions in ExpensiMark class of expensify-common repo.
https://github.com/Expensify/expensify-common/blob/bc275547d5e0e36cfd25169bdb6eb0ae3f505bf2/lib/ExpensiMark.js#L111-L120
Currently, it inputs the whole string inside <mention-user> tag if the string is matched with regex.
So if the string contains multiple @ characters at the first, <mention-user> tag will include multiple @ characters too.
<EMAIL_ADDRESS>=> <mention-user><EMAIL_ADDRESS>
That's why the app shows invalid email with @ characters at first, on the mentioned email.
What changes do you think we should make in order to solve the problem?
We need to update replace regex of userMentions to input only one @ character inside <mention-user> tag.
Rest of @ characters should stay outside <mention-user> tag.
name: 'userMentions',
regex: new RegExp(`[a-zA-Z0-9.!$%&+/=?^\`{|}-]?(@*?)(@${CONST.REG_EXP.EMAIL_PART})(?!((?:(?!<a).)+)?<\\/a>|[^<]*(<\\/pre>|<\\/code>))`, 'gm'),
replacement: (match, g1, g2) => {
    if (!Str.isValidMention(match)) {
        return match;
    }
    return `${g1}<mention-user>${g2}</mention-user>`;
},

As a result, the app will show valid email although the user inputs multiple @ characters at first.
<EMAIL_ADDRESS>=> @<mention-user><EMAIL_ADDRESS>
What alternative solutions did you explore? (Optional)
N/A

Proposal
Please re-state the problem that we are trying to solve in this issue.
Mentioning an email with double @ sign results in an invalid email mention
What is the root cause of that problem?
We're matching multiple @ signs in the regex of user mentions rule in ExpensiMark i.e. the @+ in the @+${CONST.REG_EXP.EMAIL_PART} section matches one or more @ symbols.
regex: new RegExp(`[a-zA-Z0-9.!$%&+/=?^\`{|}-]?@+${CONST.REG_EXP.EMAIL_PART}(?!((?:(?!<a).)+)?<\\/a>|[^<]*(<\\/pre>|<\\/code>))`, 'gm'),

What changes do you think we should make in order to solve the problem?

I propose removing the + after the @ symbol so only one @ is matched.
regex: new RegExp(`[a-zA-Z0-9.!$%&+/=?^\`{|}-]?@${CONST.REG_EXP.EMAIL_PART}(?!((?:(?!<a).)+)?<\\/a>|[^<]*(<\\/pre>|<\\/code>))`, 'gm'),

This is what the regex will capture whenever there are multiple leading @ symbols after this change.
<EMAIL_ADDRESS>This behavior is also consistent with what we currently have when there are multiple leading @ symbols for @here mentions.

Demo after changes
https://github.com/Expensify/App/assets/79470910/16a2b217-d4ca-4a10-b258-43be95077d48

What alternative solutions did you explore? (Optional)
None as of yet.

Thanks, @akamefi202 @Victor-Nyagudi Both of your proposals work.
I like your @Victor-Nyagudi as its cleaner and does the job. Wondering why + was added in the first place, are we missing something?

I'm not sure either, @Santhosh-Sellavel.
I looked through the merged PRs, and I didn't find any that added the +. It's possible it may have always been there from the beginning.

@Santhosh-Sellavel do you have any further input for the proposals that were provided?

Asked here for clarifications regarding this proposal.

@getusha can you respond to @Santhosh-Sellavel question

Asked here for clarifications regarding this https://github.com/Expensify/App/issues/28946#issuecomment-1750185844.

@Santhosh-Sellavel are we good to keep moving with that PR?

@Santhosh-Sellavel is there an acceptable proposal here? Otherwise I can pull someone in to get a fix moving for this one

I guess we are good here as we have proposals already. I'll let post my comments soon.

@abekkala please add hold for the same, thanks!

updated to HOLD

@Santhosh-Sellavel Can you confirm we're still on HOLD for this one?

still on hold

still on hold

On hold

Still on hold

@Santhosh-Sellavel The PR of the issue we're holding for has been merged, and the version of Expensify-Common has been bumped to the latest version which includes the changes.
However, I can still reproduce the issue on latest main even after the PR was deployed to staging.

Video of bug still reproducible after PR merge
https://github.com/Expensify/App/assets/79470910/b7c42a03-f685-42c6-8bd9-1da2e523b53a

My solution still holds even after the PR merge, and all tests are still passing.

My changes after the PR merge
https://github.com/Expensify/App/assets/79470910/8797e5ac-46c9-46ac-82cf-77421a9813e1

Should we wait until the regression testing period is over to proceed?
Please Note:
The fix from the merged PR wasn't showing in DEV, so I had to change the commit hash to the one belonging to the PR in package.json in order to see the changes.
- "expensify-common"<EMAIL_ADDRESS>+ "expensify-common"<EMAIL_ADDRESS>
Everything works fine in staging.
For reference, you could try pasting the following in the composer to see if it's highlighted correctly.
@test.example+2@gmail.com@here
@here<EMAIL_ADDRESS>@test.example+2@gmail.com<EMAIL_ADDRESS>@here<EMAIL_ADDRESS>@here@gmail.com@here
@here<EMAIL_ADDRESS>@here+1@gmail.com@here

I'm heading out for the Thanksgiving holiday and will be back bright and early Monday morning.
If something pops up that needs urgent attention please reapply label or ask in slack.

@Santhosh-Sellavel can you address the comment above by @Victor-Nyagudi

@Santhosh-Sellavel friendly bump here

@abekkala Sorry Hold label confuses. Can you take this off hold, please?
@Victor-Nyagudi Can you submit a formal proposal again, after the latest changes?

@Santhosh-Sellavel I'll check on this tomorrow morning.
If my proposal ends up being the same as the current one, can I just use that instead, leave a comment linking to my proposal titled "Updated", or just make a new identical one?

Testing my solution.

@Santhosh-Sellavel Tests well so far.
I'm going to stick with my original proposal.

not overdue - @Santhosh-Sellavel can you review the proposal by Victor?

@Victor-Nyagudi proposal looks good to me!

@Victor-Nyagudi proposal looks good to me!
C+ Reviewed
🎀 👀 🎀

@Victor-Nyagudi do you have a timeframe for the PR?

Proposal looks good 👍

Thank you for the offer.
I'll get to work on the PR.
ETA the next 24-48 hours

@Santhosh-Sellavel The PR is ready for review.

We have the expensify-common PR merged, can we expect the App PR shortly @Victor-Nyagudi?

Oh, sorry about that, @amyevans . I didn't know I should make an Expensify/App PR.
Is it the one changing the expensify-common commit hash in Expensify/App to the latest commit in my PR?

Exactly! 😄

The docs put that under "Expensify only", so I thought only internal engineers should update expensify-common.
Nevertheless, it's late for me, so I'll make a PR first thing in the morning.

@amyevans The PR is ready for review.
Commit hash in package.json has been updated.
license/snyk tests are currently failing, but according to this comment in a recently merged PR, it is a known issue that is currently being worked on.
The PR was merged with those tests failing.
cc: @Santhosh-Sellavel

Friendly bump, @Santhosh-Sellavel, for a PR review.
I just changed the commit hash, so no deep analysis of code required.

@kadiealexander
STATUS
I'm ooo through Jan 03
This is at the finish line and last thing should be issuing payment once the regression period passes after PR is deployed to prod.

@adeel0202 [$50] Issue Reporter
@Victor-Nyagudi [$500 - if no regressions] Fix Offer link
@Santhosh-Sellavel [$500 - if no regressions] PR Review - in NEWDOT, not Upwork

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@Santhosh-Sellavel] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/expensify-common/pull/524
[x]  [@Santhosh-Sellavel] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/expensify-common/pull/524/files#r1357339778
[x]  [@Santhosh-Sellavel] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x]  [@Santhosh-Sellavel] Determine if we should create a regression test for this bug.  Yes
[ ]  [@Santhosh-Sellavel] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ]  [@abekkala / @kadiealexander] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Bug:  Mentioning an email with double @ sign results in an invalid email mention
Steps:

Log into an account and open a report
Type '@' in the composer followed by the valid email of someone you've chatted with before. You can also optionally select one from the mentions' suggestions list.
Place the cursor at the beginning of the composer, type another '@' sign, and then send the message.
Verify that only the first '@' sign before the email and the email is highlighted e.g<EMAIL_ADDRESS>Repeat step 2 and then send the message.
Verify that a regular mention with one '@' sign works as usual.

I'm back from ooo, unassigning @kadiealexander and creating regression test GH and payment today

@Victor-Nyagudi  payment sent and contract ended - thank you! 🎉

@adeel0202 payment offer sent in Upwork - once accepted, I can process payment

@Santhosh-Sellavel  - [$500] to be made via New Dot

@adeel0202 payment sent and contract ended - thank you! 🎉

@Santhosh-Sellavel have you requested/received your payment in NewDot?

Requested on ND

PAYMENTS:
Muhammad Adeel Nawaz paid ✅
Victor-Nyagudi paid ✅
Santosh - requested payment [$500] in ND

$500 payment approved for @Santhosh-Sellavel based on this comment.


Add support for array.resize

Closes #8015
I have added initial support array.resize for numpy arrays in Numba. I have taken inspiration from reshape implementation. I have considered 3 cases,

New size of array is less than or equal to the original size of array - Then there is no need to allocation extra amount of data. Just fill the shape and strides (according to order of the input array).
New size of arrays is greater than the size of the original size of array - Here, other than filling the shape and strides according to the new shape, we have to allocate new block of memory and then fill the extra values with zero.

I have currently implemented and tested the first case. Will update the PR for the second case as well.
Please let me know if you have any other approach in mind. Will be happy to implement that as well. Thanks.

I feel that you are right. So that means we don't need to add resolve_resize function to numba/core/typing/arraydecl.py file I think? Plus does that also mean that we need to make changes to reshape's implementation as well? Please let me know, I can do that in a separate PR. Thanks.

I feel that you are right. So that means we don't need to add resolve_resize function to numba/core/typing/arraydecl.py file I think?

I think that's the case. The typing part of the @overload* functions can do any type checking or analysis needed.
The idea behind using the extension APIs internally is to make it so that Numba's implementation of functionality is itself written using it's own APIs, it means there's less to maintain and ensures that the APIs are appropriate for real world use! Perhaps take a look at the guide to using @overload if you are not familiar with it: https://numba.readthedocs.io/en/stable/extending/overloading-guide.html

Plus does that also mean that we need to make changes to reshape's implementation as well?

I'd try and restrict the scope of the PR to the minimum. What's the issue you've run into with reshape or is it just that it uses the old-style APIs?
Thanks for your help.

Perhaps take a look at the guide to using @overload if you are not familiar with it: https://numba.readthedocs.io/en/stable/extending/overloading-guide.html

Thanks for sharing. I read this and its a wonderful documentation. Reinforces my learnings from previous PRs here.

What's the issue you've run into with reshape or is it just that it uses the old-style APIs?

No conceptual issues as such. Just that it helps in maintaining consistency across the code base. No worries though if we don't want to make changes to reshape, its already working so we can leave as it is.

Well while try to use overload_method in resize, we can't do it. The reason is we need lower level access to shape and strides so that we can just update these two things when new size is less than or equal to the original size. overload_method will not allow something like, a.shape = new_shape. So may be that's why we need lower_builtin to update the arrays directly, the way reshape does.

@czgdp1807 Thanks for looking at this some more. Some observations:

np.ndarray.resize (the method on the NumPy array object) updates the array in-place and returns None. It also has a default of checking CPython's reference counter (kwarg refcheck=True). This is problematic on numerous fronts:

Numba's type inference system cannot handle in-place type changes, e.g.x = np.ones((3, 4, 5)) # types.Array(float64, 3d, 'C')
x.resize((2,)) # types.Array(float64, 1d, 'C') but there's no assignment!

Numba has no access to or knowledge of CPython's reference counter, it has its own reference counting system.
The array type is represented as a LLVM SSA value of type struct, so the parts that need mutating (e.g. shape) cannot be mutated.

Due to the above, it's unfortunately not possible to implement this functionality in Numba.

np.resize (the NumPy module API function) returns a new array with the given shape. This should be possible to implement in Numba.

2. np.resize (the NumPy module API function) returns a new array with the given shape. This should be possible to implement in Numba.

Yeah. It would be not that difficult I think to do. I can do this in a separate PR.
Thanks for explaining @intrinsic in https://github.com/numba/numba/pull/8020#issuecomment-1118791450.
I will close this PR then and will make a new one for np.resize.


NASM assembly build requires Windows API RtlVirtualUnwind

I am enabling assembly builds for the UEFI environment, where the prescribed assembler is NASM. Within the pre-OS environment, there are no Windows APIs available, but it appears that perlasm_scheme=>"nasm" forces the inclusion of __imp_RtlVirtualUnwind. Access to Windows APIs shouldn't be required to use NASM.
Additionally, and maybe this needs to be a feature request, but it would be helpful to have a build flag to avoid AVX instructions, as currently it only checks against the nasm executable version, and the UEFI environment isn't built to support AVX.
Attached config dump:
config.log

Marking as inactive, to be closed at the end of 3.4 dev barring further input

I have checked with some EDK2 folks and it sounds like they're happy living with the existing workaround, which is to build against a stub function for __imp_RtlVirtualUnwind.


How to save time to compare between model_results in dictionary?

In comparing part of three models in 03. Pytorch Computer Vision,
How to show in table about time difference of model_1_results, model_2_results and model_3_results for CPU or GPU?

Hey @JasOlean,
You could add a column for "device" in the DataFrame detailing which device the model was trained on.
For example:
# Add training device to results comparison
compare_results["device"] = [...,
                                                   ...,
                                                   ...]

Closing this due to inactivity, let me know if you have any other questions.


Cannot download linked imgur albums

Hello.
Im really sorry for asking, but i cannot download imgur albums from new posts (2018) on NSFW artworks. "Download imgur" option is enabled.

Expected result: downloaded a picture from tumblr post + downloaded a larger copy from imgur
Actual result: downloaded a picture from tumblr post, but not from imgur

Am I doing something wrong or it is not possible?

Looks like they are linked differently again in that blog. It's probably just a line of code (adjusting the regular expression in the Imgur parser), but for sure it could be the case that for that blog, you'll not be able to download the linked images.
If there would be one single way to do something, things would be too easy, really, ..

Well, I've actually looked into this, and couldn't get it easily working, .. then I tested the urls in the blog, and they are all dead as well. For example:
https://imgur.com/4B2BSpz
https://imgur.com/T2FpMRQ
I'm not even sure if those have a valid format.

No, I believe you. I had similar experience when I was implementing the tumblr _raw photo detection. The current Imgur RegEx for album detection would also not detect those links above as they are in the form
https://imgur.com/4B2BSpz
https://imgur.com/T2FpMRQ
instead of
https://imgur.com/a/4B2BSpz
https://imgur.com/A/T2FpMRQ
without the a or A after the host.


PSI and JIR high level functions will fail first time they're called with a "try-error", but work subsequently

I've seen PSI and JIR fail, the first time they run and then work subsequent times on the same input SQB objects.  Maybe this is some initialization issue since it only appears to happen the first time the jir/psi function is called?
Error:
Error in as.data.frame.default(x) :
  cannot coerce class ‘"try-error"’ to a data.frame
Calls: junction_inclusion_ratio ... merge.default -> merge -> as.data.frame -> as.data.frame.default

sb1 <- SnaptronQueryBuilder$new()
sb1<-sb1$from_url("http://snaptron.cs.jhu.edu/srav2/snaptron?regions=chr2:29446395-30142858&contains=1&rfilter=strand:-")
sb2 <- SnaptronQueryBuilder$new()
sb2<-sb2$from_url("http://snaptron.cs.jhu.edu/srav2/snaptron?regions=chr2:29416789-29446394&contains=1&rfilter=strand:-")
jir<-junction_inclusion_ratio(list(sb1),list(sb2))

PSI:
inclusion_group1 <- SnaptronQueryBuilder$new()
inclusion_group1 <- inclusion_group1$from_url("http://snaptron.cs.jhu.edu/srav2/snaptron?regions=chr1:94468008-94472172&exact=1&rfilter=strand:+")
inclusion_group2 <- SnaptronQueryBuilder$new()
inclusion_group2 <- inclusion_group2$from_url("http://snaptron.cs.jhu.edu/srav2/snaptron?regions=chr1:94472243-94475142&exact=1&rfilter=strand:+")
exclusion_group <- SnaptronQueryBuilder$new()
exclusion_group <- exclusion_group$from_url("http://snaptron.cs.jhu.edu/srav2/snaptron?regions=chr1:94468008-94475142&exact=1&rfilter=strand:+")

psi<-percent_spliced_in(list(inclusion_group1), list(inclusion_group2), list(exclusion_group), min_count=1)

This could also be tied to running the queries in parallel. I have gotten of the code that does so.

I agree, looks like they're both working now the first time, thanks!


add generate questions to stackoverflow

We should start adding simple generate questions to stackoverflow that we can answer, to provide users with a way to find searchable help and feedback.
SO actively encourages simple, high quality code questions like this. It would be great if someone could just start asking basic questions for @doowb and I to answer.  feel free to link them here if anyone wants to do this

Wow I can't believe I missed this comment! I'm so sorry, we'd love to have you join the org!

I wish I had seen this comment earlier, I hope you didn't feel discouraged that we didn't answer. I have been travelling, and @doowb is doing some moving/package/storage stuff right now.

Hi @jonschlinkert, don't worry about that, I'm patient enough and motivated to wait your answers.
I'm more than ever motivated to join your orgs (the more I use the toolkit — and I do!
—, the more I love it!), and I'm really pleased to know that it will be done!
Waiting for the next step!

great! I'm starting to add you now, I'm really glad you like using the tools and are getting value out of them. We have lots of room for improvement!


link coursera specialization

Updated index.Rmd to

link to the Coursera Specialization
comment out the leanpub link

This time the render preview failed because of the github thing..... So I may need to merge the OTTR sync PR first


ADD troubleshooting to readme

Awesome job @sofroniewn!
aside from the serialport trouble, I had to upload the firmata standard firmware to my arduino to make it work.  I had some goofy custom code on there before.  It might be worth mentioning that in the readme.
This is from the johnny-five docs:
If the above didn't work as expected, make sure that StandardFirmata is installed on the board:
Download Arduino IDE
Plug in your Arduino or Arduino compatible microcontroller via USB
Open the Arduino IDE, select: File > Examples > Firmata > StandardFirmata
Click the "Upload" button.
If the upload was successful, the board is now prepared and you can close the Arduino IDE.

@andyh616 Yes - great suggestion, I've updated the docs, thanks!


gtk 3 wxGTX 3.1 programs POEdit and Kicad fail assertion '(withWebKit -> (stdenv).isDarwin)'

Describe the bug
The pull request #163335 introduced a regression where certain wxGTK 3.1 applications fail the assertion '(withWebKit -> (stdenv).isDarwin)'. In particular the following packages seem to be affected:

poedit
kicad, kicad-small, kicad-unstable, kicad-unstable-small

Steps To Reproduce
Steps to reproduce the behavior:

in a nix repl, :lf github:NixOS/nixpkgs/55b85b13561945f6c8fcb84995b0f76762cf3362
try to evaluate the expression outputs.legacyPackages.x86_64-linux.poedit

Expected behavior
Something similar to
«derivation /nix/store/152ybxsvldg9fpfbfik65j7l2vb6n4mv-poedit-3.0.1.drv»

Actual behavior
nix-repl> outputs.legacyPackages.x86_64-linux.poedit
error: assertion '(withWebKit -> (stdenv).isDarwin)' failed

       at /nix/store/z19plswfzbjzmv2pdh2bvp69rgq5h23m-source/pkgs/development/libraries/wxwidgets/wxGTK31.nix:35:1:

           34|
           35| assert withWebKit -> stdenv.isDarwin;
             | ^
           36|
[27.8 MiB DL]«derivation

Notify maintainers
@AndersonTorres @tfmoraes @knl
Metadata

system: "x86_64-linux"
host os: Linux 5.15.29, NixOS, 22.05 (Quokka)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.7.0
channels(root): "nixos"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

This is also affecting qgis on linux:
$ nix-build $NIXPKGS -A qgis
error: assertion '(withWebKit -> (stdenv).isDarwin)' failed

       at /home/wcohen/programming/nix/nixpkgs/pkgs/development/libraries/wxwidgets/wxGTK31.nix:35:1:

           34|
           35| assert withWebKit -> stdenv.isDarwin;
             | ^
           36|
(use '--show-trace' to show detailed location information)

I'm looking into this, will try to find some time tonight. Probably the safest thing is to remove this assertion, as it's wrong (or reverse it).


Bug in thin_observations

There is a bug in thin_observations and specifically the bias method if no observation is located above the percentile of the bias layer. In this case, the vector for sub-setting the data.frame is empty.

Should be fixed. I added a check and message in L1452


main has been removed but is needed for IE 11

main {
    display: block;
}

is needed for IE 11 to render the element properly. Probably also for IE 10.

This rules was removed for a mistake. figure, figcaption and few another tags really added in IE9, but main still display:inline.
Here is screen from IE11:

The request merge is needed

Sent from my BlackBerry 10 smartphone.
From: Gosha Egorian
Sent: Wednesday, March 14, 2018 10:23 AM
To: necolas/normalize.css
Reply To: necolas/normalize.css
Cc: Subscribed
Subject: Re: [necolas/normalize.css] main has been removed but is needed for IE 11 (#727)
The request merge is needed
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/necolas/normalize.css/issues/727#issuecomment-372939898, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVnnMnBeFSprYQ6QUvZ2hAbNGE8udBHBks5teNN-gaJpZM4SCF6_.

As I thought upgrade to normalize.css 8.0.0 won't break anything as out project points to user with ie >= 10, but actually this main element issue came to me. Wonder when it'll be patched🙄

Please do it !

Not sure about IE10, but IE11 needs it.

IE 10 needs it too.

This can be closed now since #51 has been merged.

@fritx missing a publish to NPM though

@oles yeah, I have mentioned that here: https://github.com/necolas/normalize.css/pull/730#issuecomment-436934588

Forgot to publish. Should be up now. Thanks

Awesome! Thank you, @necolas!


For only Jupyter extension it does NOT fill in all data automatically when submitting a bug

I have the latest version of VS code for now.
When I submit a bug using this form

I will be redirected to this useless web page:

so that after clicking on "get started" no information will be filled in automatically.
But for other extensions (python, pylance, ...  whatever else)   I will get redirected to this page:

For those who just don't believe:  https://www.youtube.com/watch?v=2BKCZS1zqSc  - this is how it behaves.  Sorry for my mood on the video: I am really annoyed with this behavior, but this lasts for too long time.  It is really time to fix.


use channel for event errors

This adds a channel for the event stream to pass errors.

@ehazlett can you also update README.md
There is an example at the end.

@vieux done!  thx!

LGTM, thanks!


Added window.queueMicrotask() to externs

The declaration for window.queueMicrotask() is missing in the externs declarations.

@googlebot I signed it!


no 'comment' documentation exists in the developer doc!

[x] Updated to the latest version
[x] Read the README and docs
[x] Searched the bugtracker for similar issues including closed ones

Purpose of your issue?

[ ] Bug report (encountered problems/errors)
[ ] Feature request (request for a new functionality)
[ ] Question
[x] Other

Describe your issue
I noticed the developer documentation of instabot is incomplete. In the table of contents, a whole section on comment exists but none can be found in the actual documentation page - the link is dead/no text exists.

I don't think commeting works at all. When I use comment by hastag, enter a wierd hashtag only used by a photo of me - instabot says it commeting on like 7 medias but I dont see a comment under my photo

Instructions for use
https://instagrambot.github.io/docs/en/How_to_use.html
Documentation for Developers
https://instagrambot.github.io/docs/en/For_developers.html

Search for previously asked questions

Instructions for use
https://instagrambot.github.io/docs/en/
Documentation for Developers
https://instagrambot.github.io/docs/en/For_developers.html

Search for questions that were previously asked

Comments in the script files themselves

If you don’t follow the link to the desired document. Copy it and paste it into the browser manually.

Hello @disayner ,
This is not what u mean. I know how to use instabot but the effects of some example scripts are not so clear to me. An overview with a better explanation would be helpfull.
Sadly the documentation page does not explain this. (also, I fount it to be incomplete)

@MrMdR suggest the improve....

@MrMdR Now I understand. Yes, unfortunately there is no complete documentation. But there are basic documents, having studied which you can solve many issues.


deprecate quick replies in favor of using custom

Description of Problem:
We currently support quick_replies in the domain file, though they are only supported on the facebook channel. This leads to a lot of extra code for something that is a pretty specific use case. I thought about this after reconsidering adding them to the SDK, where the support for them never made it in.
Overview of the Solution:
Now that the same functionality can be accomplished via the custom domain key, we can handle facebook quick replies the way that any other channel-specific UI elements are handled.

@tmbo what are your thoughts on this?

Thinking we should do this for elements as well. We can provide examples of how to use channel-specific features in the channel's documentation if we want -- similar to https://github.com/RasaHQ/rasa/pull/5693 but showing how to implement that stuff in custom

Current facebook quick reply format:
utter_something:
  - text: "hi!"
    quick_replies:
    - title: "button 1"
      payload: "/payload1"
    - title: "button 2
      payload: "/payload2"

with custom:
utter_something:
  - custom:
      text: "hi!"
      quick_replies:
        - content_type: "text"
          title: "button 1"
          payload: "/payload1"
        - content_type: "text"
          title: "button 2
          payload: "/payload2"

It's a little more work, but you can also add images to your buttons, as well of tons of other quick reply content types like location, emails, and phone numbers. I expect some people are already using custom to achieve this functionality.

Key 'quick_replies' was not defined
when i try to do
`utter_something:

text: "hi!"
quick_replies:

title: "button 1"
payload: "/payload1"
title: "button 2
payload: `"/payload2"``


Update SAR check for SA Token

We're looking to stop using the mig serviceAccount which is over privileged. This isn't a definitive check of every permission required, but should be a good start to determining if a SA is properly privileged to be used for a migCluster. We may have to / want to find a sane way to check for everything down the road, although if I'm following how this is done it would be a huge number of checks .

Looks like the Linux failure is happening on other commits and not specific to my PR? Any insight?

@Danil-Grigorev I'm testing that right now, I'd like to get this one merged asap if it looks good to controller folks. I will report back with my testing.

@eriknelson not sure why you're having trouble:
I added some logging:
  log.Info("i##########################################################")
  log.Info(fmt.Sprintf("migrationSar: %t", migrationSar.Status.Allowed))
  log.Info(fmt.Sprintf("veleroSar: %t", veleroSar.Status.Allowed))
  log.Info("i##########################################################")
  if !migrationSar.Status.Allowed || !veleroSar.Status.Allowed {
    cluster.Status.SetCondition(migapi.Condition{
      Type:     SaTokenNotPrivileged,
      Status:   True,
      Reason:   Unauthorized,
      Category: Critical,
      Message:  SaTokenNotPrivilegedMessage,
    })
  }

# oc get po migration-controller-5668cf7dc9-kstlz -o yaml| grep image:
    image: quay.io/jmontleon/mig-controller:gvr
    image: quay.io/jmontleon/mig-controller:gvr
    image: quay.io/jmontleon/mig-controller:gvr
    image: quay.io/jmontleon/mig-controller:gvr

{"level":"info","ts":1584657657.4911134,"logger":"cluster|54dlt","msg":"i##########################################################"}
{"level":"info","ts":1584657657.4912024,"logger":"cluster|54dlt","msg":"migrationSar: true"}
{"level":"info","ts":1584657657.491217,"logger":"cluster|54dlt","msg":"veleroSar: true"}
{"level":"info","ts":1584657657.4912236,"logger":"cluster|54dlt","msg":"i##########################################################"}

$ oc sa get-token migration-controller
eyJhbGciOiJS....CcMFTwccHEt61SPlu8Ag

oc get secret -o yaml ocp4
apiVersion: v1
data:
saToken: ZXlK...OEFn
kind: Secret
metadata:
creationTimestamp: "2020-03-18T21:32:17Z"
name: ocp4
namespace: openshift-migration
resourceVersion: "14260358"
selfLink: /api/v1/namespaces/openshift-migration/secrets/ocp4
uid: f0f47f11-695f-11ea-9965-5254009f7cb2
type: Opaque
[root@192 ~]# echo ZXlK...OEFn | base64 -d
eyJhbGciOiJS...CcMFTwccHEt61SPlu8Ag

Could be my old clusters. I'll retry and update.
Get BlueMail for Android
On Mar 19, 2020, 6:51 PM, at 6:51 PM, Jason Montleon<EMAIL_ADDRESS>wrote:

@eriknelson not sure why you're having trouble:
I added some logging:
log.Info("i##########################################################")
log.Info(fmt.Sprintf("migrationSar: %t", migrationSar.Status.Allowed))
 log.Info(fmt.Sprintf("veleroSar: %t", veleroSar.Status.Allowed))
log.Info("i##########################################################")
 if !migrationSar.Status.Allowed || !veleroSar.Status.Allowed {
   cluster.Status.SetCondition(migapi.Condition{
     Type:     SaTokenNotPrivileged,
     Status:   True,
     Reason:   Unauthorized,
     Category: Critical,
     Message:  SaTokenNotPrivilegedMessage,
   })
 }

# oc get po migration-controller-5668cf7dc9-kstlz -o yaml| grep image:
   image: quay.io/jmontleon/mig-controller:gvr
   image: quay.io/jmontleon/mig-controller:gvr
   image: quay.io/jmontleon/mig-controller:gvr
   image: quay.io/jmontleon/mig-controller:gvr

{"level":"info","ts":1584657657.4911134,"logger":"cluster|54dlt","msg":"i##########################################################"}
{"level":"info","ts":1584657657.4912024,"logger":"cluster|54dlt","msg":"migrationSar:
true"}
{"level":"info","ts":1584657657.491217,"logger":"cluster|54dlt","msg":"veleroSar:
true"}
{"level":"info","ts":1584657657.4912236,"logger":"cluster|54dlt","msg":"i##########################################################"}

$ oc sa get-token migration-controller
eyJhbGciOiJS....CcMFTwccHEt61SPlu8Ag

oc get secret -o yaml ocp4
apiVersion: v1
data:
saToken: ZXlK...OEFn
kind: Secret
metadata:
creationTimestamp: "2020-03-18T21:32:17Z"
name: ocp4
namespace: openshift-migration
resourceVersion: "14260358"
selfLink: /api/v1/namespaces/openshift-migration/secrets/ocp4
uid: f0f47f11-695f-11ea-9965-5254009f7cb2
type: Opaque
[root@192 ~]# echo ZXlK...OEFn | base64 -d
eyJhbGciOiJS...CcMFTwccHEt61SPlu8Ag

--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/konveyor/mig-controller/pull/457#issuecomment-601452735

This needs to be merged simultaneously with https://github.com/konveyor/mig-operator/pull/259


Implement %TypedArray%.from

Implement the TypedArray.from routine
add a helper function: ecma_get_object_builtin_id
fix issue #1670 : the return value of builtin object's routine can not be empty, and I use undefined instead.

JerryScript-DCO-1.0-Signed-off-by: Zidong Jiang<EMAIL_ADDRESS>

updated according to @zherczeg 's comments. And I added another test case for exceptions during from routine


add support for PJAXResponseMixin to support sub-classes defining get_pjax_template_name as an alternate to defining pjax_template_name

Allows a callable to be defined on PJAXResponseMixin subclasses for instances where the pjax template name must be defined dynamically, such as in instances where it is based on the request.

Could you add an example to readme file?

Hi @ryanisnan Thanks for you contribution. However I don't think it would be necessary to have another method involved. For this very specific scenario you could simply override the method get_template_names to return the template name based on whatever rules you'd need. It would even be difficult to explain in the README how to use the class-based view flavour with these two ways of defining pjax_template_name.
And wouldn't be so bad to do something like the following:
class CallablePJAXTemplateView(djpjax.PJAXResponseMixin, View):
    template_name = 'template.html'

    def get_template_names(self):
        if self.request.META.get('HTTP_X_PJAX', False):
            if '1' in self.request.path:
                return ['template-1-pjax.html']
            elif '2' in self.request.path:
                return ['template-2-pjax.html']

        return super(CallablePJAXTemplateView, self).get_template_names()

Let me know if you disagree with something, alright?


QuickCheck bounds are out-of-date

The latest hackage version of QuickCheck is 2.15 but the .cabal file here restricts the version to <2.15.

to <2.15.0
  build-depends:
    , QuickCheck  >=2.14.2   && <2.15.0

2.15 < 2.15.0.

My bad... My god PVP is stupid...

It's not PVP fault. PVP actually says

A package version number SHOULD have the form A.B.C, and MAY optionally have any number of additional components, for example <IP_ADDRESS> ...

That's nitpicking, but as far as PVP semantics are considered, they always assume there is some C, there is no case for absent one. So there are no semantics specified for the allowed changes between X.Y and X.Y.0(.W). I have to assume the worst.
It could mention that if C is absent, for the purpose of C+1 cases, it should be assumed to be zero. (So 2.15 -> 2.15.0 cannot add anything, i.e. can only be mere patch release, like <IP_ADDRESS> -> <IP_ADDRESS>); you may suggest that at https://github.com/haskell/pvp/issues

Of course, and cabal just does lex ordering... Technically speaking both lex and "assume 0" ordering make sense, but my intuition was definitely assume 0 (to the point where I didn't check and assumed a missing =).


Missing Number= with gnomad.v3.1.2.echtvar.v2.zip

Hi,
Thanks for providing gnomad.v3.1.2.echtvar.v2.zip. However, I'm having trouble with some downstream tools that complain about the INFO line of the annotated VCF, where there's no number in the INFO lines.
Command run:
echtvar anno -e gnomad.v3.1.2.echtvar.v2.zip -e CoLoRSdb.GRCh38.v1.0.0.deepvariant.glnexus.zip 7.bed.bcf 7.bed_echtvar_anno.bcf.gz

Missing Number=number
##INFO=<ID=gnomad_ac,Number=,Type=Integer,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_an,Number=,Type=Integer,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_nhomalt,Number=,Type=Integer,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_af,Number=,Type=Float,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_popmax_ac,Number=,Type=Integer,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_popmax_an,Number=,Type=Integer,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_popmax_nhomalt,Number=,Type=Integer,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_popmax_af,Number=,Type=Float,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_controls_and_biobanks_af,Number=,Type=Float,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_controls_and_biobanks_nhomalt,Number=,Type=Integer,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">
##INFO=<ID=gnomad_filter,Number=,Type=String,Description="added by echtvar from gnomad.v3.1.2.echtvar.v2.zip">

This is not the case for a database I have encoded myself:
##INFO=<ID=colorsdb_af,Number=1,Type=Float,Description="added by echtvar Allele Frequency estimate for each alternate allele">
##INFO=<ID=colorsdb_ac,Number=1,Type=Integer,Description="added by echtvar Allele count in genotypes">

Any idea what is up with gnomad.v3.1.2.echtvar.v2.zip?
PS, Seems to have sneaked in a None here as well:
##echtvar_annoCommand=anno -i None 20.bed.bcf 20.bed_echtvar_anno.bcf.gz -e "gnomad.v3.1.2.echtvar.v2.zip -e CoLoRSdb.GRCh38.v1.0.0.deepvariant.glnexus.zip"

hi, sorry for the delay, can you show the json file that you used to create the problematic zip file?

Hi, no worries. The problematic zip file seems to be the pre-made file for hg38 provided with the releases.
I could remake the file using your json (https://github.com/brentp/echtvar/blob/main/examples/gnomad.v3.1.2.json) and use the resulting file without problems. Is the file provided under releases perhaps using an older version of echtvar?

hi, my reply seems to have been lost...
so you're saying it works if you remake with a recent version of echtvar?
If so, I'll see if I can get a new version of the zips uploaded somewhere.

hi, my reply seems to have been lost... so you're saying it works if you remake with a recent version of echtvar? If so, I'll see if I can get a new version of the zips uploaded somewhere.

Yes! It seems like the later version of echtvar produces a valid VCF. Would be great!

Thanks! 🙌


Could not find a JavaScript runtime

On Manjaro Linux I tried to install and run middleman. Got the following errors when running init:

cannot load such file -- coffee_script
Could not find a JavaScript runtime.

What am I missing?

Detailed command line log
19:30:54 mcn@x270 ~ gem install middleman
Successfully installed middleman-4.3.6
1 gem installed
19:31:02 mcn@x270 ~ middleman init middleman_test
Traceback (most recent call last):
    16: from /home/mcn/.local/share/gem/bin/middleman:23:in `<main>'
    15: from /home/mcn/.local/share/gem/bin/middleman:23:in `load'
    14: from /home/mcn/.local/share/gem/gems/middleman-cli-4.3.6/bin/middleman:49:in `<top (required)>'
    13: from /home/mcn/.local/share/gem/gems/middleman-cli-4.3.6/bin/middleman:49:in `new'
    12: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/application.rb:263:in `initialize'
    11: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/application.rb:263:in `new'
    10: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extension_manager.rb:12:in `initialize'
    9: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extensions.rb:125:in `load_settings'
    8: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extensions.rb:125:in `each'
    7: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extensions.rb:127:in `block in load_settings'
    6: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extensions.rb:91:in `load'
    5: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/core_extensions/rendering.rb:11:in `block in <top (required)>'
    4: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
    3: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
    2: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/renderers/coffee_script.rb:2:in `<top (required)>'
    1: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
/usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': cannot load such file -- coffee_script (LoadError)
    23: from /home/mcn/.local/share/gem/bin/middleman:23:in `<main>'
    22: from /home/mcn/.local/share/gem/bin/middleman:23:in `load'
    21: from /home/mcn/.local/share/gem/gems/middleman-cli-4.3.6/bin/middleman:49:in `<top (required)>'
    20: from /home/mcn/.local/share/gem/gems/middleman-cli-4.3.6/bin/middleman:49:in `new'
    19: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/application.rb:263:in `initialize'
    18: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/application.rb:263:in `new'
    17: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extension_manager.rb:12:in `initialize'
    16: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extensions.rb:125:in `load_settings'
    15: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extensions.rb:125:in `each'
    14: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extensions.rb:127:in `block in load_settings'
    13: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/extensions.rb:91:in `load'
    12: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/core_extensions/rendering.rb:11:in `block in <top (required)>'
    11: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
    10: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
    9: from /home/mcn/.local/share/gem/gems/middleman-core-4.3.6/lib/middleman-core/renderers/coffee_script.rb:2:in `<top (required)>'
    8: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:156:in `require'
    7: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:168:in `rescue in require'
    6: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:168:in `require'
    5: from /home/mcn/.local/share/gem/gems/coffee-script-2.4.1/lib/coffee_script.rb:1:in `<top (required)>'
    4: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
    3: from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
    2: from /home/mcn/.local/share/gem/gems/execjs-2.7.0/lib/execjs.rb:4:in `<top (required)>'
    1: from /home/mcn/.local/share/gem/gems/execjs-2.7.0/lib/execjs.rb:5:in `<module:ExecJS>'
/home/mcn/.local/share/gem/gems/execjs-2.7.0/lib/execjs/runtimes.rb:58:in `autodetect': Could not find a JavaScript runtime. See https://github.com/rails/execjs for a list of available runtimes.  Most OSes ship with one, but I guess manjaro doesn't
You'll want to add therubyracer to your Gemfile, which is a copy of the Google V8 engine that we can use to interact with javascript. Its a beefy library and may require you to add additional packages to your own to compile and link it.

More info: https://github.com/rubyjs/therubyracer

middleman 4.3.8, I got same errors when middleman init

No, this is good. This actually looks like a bug. It seems the CLI is trying to see if we're in a existing project, which because we're calling 'init', we definitely aren't. Let me take a look.

I'm getting the same thing on macOS Catalina. Tried to install therubyracer as well but it either failed or didn't fix the issue.
/usr/local/lib/ruby/gems/2.7.0/gems/execjs-2.7.0/lib/execjs/runtimes.rb:58:in autodetect': Could not find a JavaScript runtime. See https://github.com/rails/execjs for a list of available runtimes. (ExecJS::RuntimeUnavailable)`

I got this error on a new install of Big Sur. It cleared up for me when I installed node with homebrew.

Here another +1. OS X, Big Sur, same problems

Here another +1. OS X, Big Sur, same problems

Should be the same solution. Install node via homebrew or nvm.

Should be the same solution. Install node via homebrew or nvm.

Nope, doesn't solve :(

Nope, doesn't solve :(

@ciscodesign not sure if you've already solved this, but just in case — I ran into an issue with JS runtimes when I upgraded to Big Sur and here's how I fixed it, if that's somehow helpful? Then again, I just now removed sq_mini_racer (which I'd needed to get Middleman working again) after having installed Node with n a couple weeks ago and everything still seems to be working fine, so I'm not sure if this would help. Either way... good luck!

also faced this on macOS Monterey, solved by adding Node's binaries to PATH:
export PATH="$(brew --prefix node@16)/bin:$PATH"


Choose language

Hi,
I would like to be able to specify the output language
req = sdmx.Request()
response = req.get(url=URL)
df = sdmx.to_pandas(response)

in the sdmx to pandas step (or elsewhere).
Is this what you mean to implement in the documentation in your
Todo:
Support selection of language for conversion of InternationalString. ?
From what I see, it would need to add the possibility to set locale to something else than DEFAULT_LOCALE in sdmx.to_pandas().
Would you be able to estimate when this will be done ?
It would be very helpful to me. Thank you very much,
Pauline ML

Solved in #224. Request class has now a property default_locale. It is used by writers to extract str values. It is set to 'en' by default as before. Now you can easily change it from public API.
This should be relased in a week or so.


Component that changes a sub-property of its own state object by async method re-renders the whole component in an infinite loop

This one is quite confusing. I'm not sure if I'm doing something wrong or if it's a bug in ArrowJS.
This is as simple as I can make it while still replicating the behaviour:
https://jsfiddle.net/9d51qhe2

If you run the fiddle, you'll see it continually prints zz0mkno. It's re-rendering the entire getLoginComponent component every time in an infinite loop.
Here's a fiddle that demonstrates more closely what I was doing when I came across this bug (including a network request instead of a timeout). Basically I was loading some user data on the login page to allow it to do client-side validation before making a server request to log in.

I've run into the same issue just now. Did you ever found a solution/workaround @Clonkex ?

@Aidenir Unfortunately my "solution" was to switch to Preact + HTM (which is relatively easy to achieve even with an existing ArrowJS codebase because the ArrowJS and HTM syntax is similar - it's also still fully clientside, no build step necessary). It's not quite as elegant as ArrowJS in some ways (in particular, it took me a while to get my head around state handling - having to set an entirely new copy of the object when anything changes feels jank, but also potentially simpler and more reliable) but in other ways it's simpler and has the significant benefit of being battle-tested. If you make the same switch, just know that when you're trying to understand some Preact feature, search for React first because Preact is basically just a reimplementation of React.
So yeah, I was unable to work around this problem and it was enough to make me suffer the pain of learning Preact instead.

Alright, thanks for the reply @Clonkex  :) . I did find a super janky workaround I think, where I changed the type of the value I keep in the reactive state to a string instead of an array: https://jsfiddle.net/09Lwopqy/
    function getLoginComponent() {
        const state = reactive({
            pageDatas: "[]",
        });
        setTimeout(async () => {
        		state.pageDatas = JSON.stringify(JSON.parse(state.pageDatas).push(Date.now()))
        }, 500);

        return html`<div>bob</div>`;
    }

From limited testing this at least solved my issue for now, and while it's definitely not a good solution, it let me keep working on the other problems in my app until hopefully a better solution comes along :P

Alright, thanks for the reply @Clonkex :) . I did find a super janky workaround I think, where I changed the type of the value I keep in the reactive state to a string instead of an array: https://jsfiddle.net/09Lwopqy/
    function getLoginComponent() {
        const state = reactive({
            pageDatas: "[]",
        });
        setTimeout(async () => {
        		state.pageDatas = JSON.stringify(JSON.parse(state.pageDatas).push(Date.now()))
        }, 500);

        return html`<div>bob</div>`;
    }

From limited testing this at least solved my issue for now, and while it's definitely not a good solution, it let me keep working on the other problems in my app until hopefully a better solution comes along :P

There are things wrong with this code and the code above it:

setTimeout doesn't take awaitable functions, remove the async in front of the lambda
You shouldn't set your reactive variable to an object that has one property pageDatas, just use the array directly and it should work fine

Try this: const pageTimestamp = reactive([])
Also, the naming of the variable to state doesn't describe what you are using it for and pageDatas is also poorly named as it looks to be timestamps. If you need to keep state then you would need to spread the array, as only the object changes are being tracked, so changing the child array directly will never trigger the change event.
Here is how keeping the object would work: state.pageTimestamps = [...state.pageTimestamps, Date.now()]

But your problem of circular loop can be fixed by splitting your state, anything that is for the component directly should be separate from the state for the children. Having it as 1 shared state can cause any changes to rerender both components.


Slow mouse or keyboard input with +gfx during YouTube playback

I found that when the option +gfx is on.
Mouse and keyboard input getting slow during YouTube playback.
But there's no error show on console
Version is 1.2.4.dev

@gareks per default FreeRDP handles input and gfx in one thread which might have the effect that input processing is "slower".  Can you try if the options  +async-input +async-update (maybe also +async-channels and +async-channels) improve that problem?

@bmiklautz I work with @gareks . I have tried +async parameters but it doesn't help. Any other suggestions? The command we use is xfreerdp -sec-nla /cert-ignore /u: /f /drive:*,hotplug /network:modem /rfx /gfx +gfx-h264 +gfx-thin-client -offscreen-cache +fonts /v:<IP_ADDRESS>. Please advise. Thanks.

#3364 addresses input starvation.


add GEP-1323: Response Header Filter

Signed-off-by: Sanskar Jaiswal<EMAIL_ADDRESS>
What type of PR is this?
/kind gep

What this PR does / why we need it:
Adds a GEP proposing a way of modifying response headers via a new field responseHeaderModifier.
Which issue(s) this PR fixes:

Fixes #1323
Does this PR introduce a user-facing change?:

NONE

Thanks for all the work on this @aryan9600! We talked about this at today's community meeting. I left some follow up comments above, but I think the major themes are:

This GEP feels very close to ready to merge.
When it comes to variables in header names, we should mention that some underlying implementations like Envoy support interpolating variables into header values, but that is unlikely to be portable across implementations.
When it comes to policy attachment, we should mention it as a possible future extension point, but we don't need to cover it in detail in this GEP.

/ok-to-test

Thanks @aryan9600! This LGTM but will defer to someone else for the final approval.
/approve

Yup, I think this is good to go.
/lgtm