[#98] Move function promotion to streaming pipeline init

If the function is promoted too early (i.e. before the gRPC
incoming stream is wired), its streams will be initialized only
once and will not be reusable after the request-reply invocation
(a request-reply invocation = 1 START + 1 NEXT + complete signal).
The promotion is now moved inside the streaming pipeline init,
which occurs every time a new gRPC stream comes in.

You can validate this change with:
 $ cd /path/to/node/invoker && npm ci && npm test && npm pack
 $ cd /path/to/node/buildpack && point to local invoker + update SHA-1
 $ cd /path/to/builder && make build-dev
 $ cd /path/to/node/request-reply-function && pack build my/function --builder projectriff/builder --no-pull
 $ docker run -p 8080:8080 -e NODE_DEBUG='riff' my/function
 $ curl <IP_ADDRESS>:8080 -H 'Content-Type: application/json' -H 'Accept: application/json' -d 1
# run curl as many times (> 1) as you want

It seems odd to re-promote the function for every invocation, as the structure of the function won't have changed. But if this unblocks us, I'm 👍

I agree it seems counter-intuitive at first but I think it's the right choice, even long term.
The function input streams' lifecycles are bound to the gRPC readable stream's lifecycle.
In the case of a promoted request-reply function, its single output stream's lifecycle is the same as its single input stream's. Hence, all streams are bound to the gRPC readable stream in that case and must be closed upon gRPC readable stream completion.
It was a mistake to promote the function before the duplex stream is wired up as the function's streams cannot be reused across invocations (1 invocation = 1 gRPC duplex stream "instance").


Fix missing parts

-Add Win screen
-Save best times

Win screen done, but remember to fix the face (happy with glasses: when is pressed but not released and you release out of the button the face change to the default one)


Problems specifying extra args that have a space

I am running the ArtifactoryConan@1 Azure Task to create a Conan package, where I am supplying the following extra arguments:
-s MyPackage:compiler="Visual Studio"
However, the actual extra arguments being produced in the shell to run the Conan create command looks like:
-s "MyPackage:compiler=\"Visual" "Studio\""
The Conan create command then fails to execute because it believes I'm specifying the command incorrectly.  I believe I have tracked the problem to this extension where the extra arguments are being split by a space delimiter.  However, this won't work if one of the Conan arguments contains a space.  Is there any work around you could share with me?  Any and all help would be greatly appreciated!

What OS is your build agent running on - Windows, Unix, ?
Have you tried either of these:

-s MyPackage:compiler='Visual Studio'
-s "MyPackage:compiler=Visual Studio"

Hi
Problem still present on conan 1.59.0
Is there any way around it?


I can't see the : and . characters in the QtWeb web address (ReactOS)

Version: 037afdc3 (May 26, 2024 17:05)
Is there any way this could be fixed? Or is this qtweb's or reactos' fault?

Try enable FreeType in ReactOS settings (right click on Desktop -> Properties -> Appearance -> Effects -> Use the following method to smooth edges of screen fonts -> FreeType Antialiased)


drivechain_client: replace DataTable with SailTable, add header sorting

The tables have turned; we're now using SailTable everywhere in order to get a uniform look/feel. This change also adds sorting to all tables, hence refactoring simple DataTable/SailTable subtrees into their own widgets in order to control the sorting state.
This change introduces sorting functionality to SailTable very similar to the DataTable API.

vry nice. Two requests:

Could you make the whole header clickable when sorting, not just the text? See the video I'v attached (In the video i'm continuously clicking)
Is it possible to get an arrow indicating what direction it's sorted in? If it's hard, don't bother.

https://github.com/user-attachments/assets/c736ba8f-40e2-4e16-8046-52c7b0e570da

vry nice. Two requests:

Could you make the whole header clickable when sorting, not just the text? See the video I'v attached (In the video i'm continuously clicking)
Is it possible to get an arrow indicating what direction it's sorted in? If it's hard, don't bother.

Screen.Recording.2024-10-03.at.11.14.14.mov

Done! Also fixed up a bug where the selected index would remain the same after sorting while the selected row would be moved to a new index.


Require bootable disk for PXE and Template image sources

Pull Request Test Coverage Report for Build 301

4 of 6 (66.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 60.818%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Wizard/CreateVmWizard/StorageTab.js
4
6
66.67%

Totals

Change from base Build 235:
-0.004%

Covered Lines:
460

Relevant Lines:
692

💛  - Coveralls


add local/session storage helper

Moved from outwatch to here

Why does it need Scalajs-bundler?

Why does it need Scalajs-bundler?

Good question! I just needed it for installing jsdom. Otherwise window was undefined. Could we somehow just enable it test?

I added a new subproject just for the tests with jsdom.


Enable CONFIG_BTRFS_FS_REF_VERIFY for dashboard configs

Did you follow the procedure at https://github.com/google/syzkaller/blob/master/dashboard/config/linux/README.md ? I.e. edit the corresponding .yml file and then regenerate everything.


[nginx controller]Issue of high CPU cost of Nginx-ingress-controller

Hi,
Using the TOP to check the cpu and memory status of K8s cluster host, I found that the CPU cost of Nginx-ingress-controller is always very high. If I set the cpu limit to 2, then the CPU time would be almost 200%. If without cpu limit, the CPU time would be almost 400% in a 4-core VM. This controller is built by myself from master branch at September, 2016.
Is that normal?
Thanks
Liu Peng

@tjliupeng this is not normal. Please check if using the latest beta you see the same behavior.

I had the same issue few weeks ago, @aledbf could you explain how to provide more info when someone has the same issue?

@gianrubio this information can help:

indicate if the controller is running with limits and the values
enter in the pod using kubectl exec -it <pod ing> bash and execute top.
the logs shows reloads when the spike occur?

@aledbf , in my env, even when there is no high load request, the CPU usage is high. Does the controller provide any debug switch to enable the profiling?

@tjliupeng the controller exposes prometheus metrics in port 10254 and path /metrics. Also you can attach the go tool pprof in the same port and path /debug/pprof to check if the issue is in the go code.

@aledbf , that's cool. That I can use go-torch by Uber to generate the flame graph for performance analyzing.

@tjliupeng please reopen if you still have issues.


Release 1.0.0 beta.5

Current coverage is 100% (diff: 100%)

Merging #55 into master will not change coverage

@@           master   #55   diff @@
===================================
  Files          21    21
  Lines         475   475
  Methods        55    55
  Messages        0     0
  Branches       54    54
===================================
  Hits          475   475
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 8e9eb71...18ada3d


Remove scheduler plugin "buffer" resources

Problem description / Motivation
In order to prevent accidental overcommitting, on startup the scheduler plugin has a measure of "uncertainty" for each VM's usage that is resolved only when the autoscaler-agent makes a request to the scheduler plugin to inform it of its intentions.
This has two issues:

Forced to choose between "unavailable" and "inaccurate", we have chosen "unavailable". In practice this is much worse / higher risk than inaccuracies.
There's a short (~5s) period of unavailability immediately after startup. When we add replicas & leader election for the scheduler, this unavailability could be frequent enough to cause liveness issues for the scheduler (i.e. it may be unable to schedule for extended periods of time)

Feature idea(s) / DoD
Scheduler plugin scheduling uncertainty should not cause unavailability
Implementation ideas
Instead of keeping "buffer" resources, we should just entirely remove it, and be willing to make inaccurate scheduling decisions. Worst-case scenario is that we accidentally overcommit by a little bit — in practice, real resource usage in our clusters is much lower than reserved resources, so we have wiggle room.

It's an interesting idea... I think in theory we could do this, but in practice:

Delaying scheduling via the plugin is risky, because Pods may take a long time to be rescheduled if we fail them (and in general, we'd rather make sub-optimal scheduling decisions than completely block scheduling).
Delaying scheduling by waiting to return from plugin creation (like in #904) would not work, I think — IIRC the scheduler is only marked "ready" once everything's running, and the autoscaler-agents only communicate with it once it's "ready", so the plugin initialization would be waiting for requests that never come

That said, we could make modifications to the conditions for communicating, or the readiness checks, and maybe this would work

For this issue, I'm currently thinking the easiest way forward is to move the autoscaler-agent <-> scheduler plugin protocol into annotations on the VMs, which would:

Guarantee that all information is available just by reading the cluster state (so: no waiting for comms — basically, if we do it right, "buffer" would always be zero because everything is known)
Make replicas / leader election simple, because the autoscaler-agents wouldn't be communicating with any particular scheduler instance (see #841)

What do you think?

For this issue, I'm currently thinking the easiest way forward is to move the autoscaler-agent <-> scheduler plugin protocol into annotations on the VMs, which would:
1. Guarantee that all information is available just by reading the cluster state (so: no waiting for comms — basically, if we do it right, "buffer" would always be zero because everything is known)

2. Make replicas / leader election simple, because the autoscaler-agents wouldn't be communicating with any particular scheduler instance (see [Scheduler leader election #841](https://github.com/neondatabase/autoscaling/issues/841))

What do you think?

Sounds good!

RFC for the stuff above: https://www.notion.so/neondatabase/e9d3253836124f9f98e681f89c146a19


Collapse ApplicationDiscoverer and Connector.

What change does this introduce?
This PR collapses the Connector type into ApplicationDiscoverer, and removes ApplicationDiscoverer goroutine management code from the discoverer.
Why make this change?
Similarly to #14, this simplifies the implementation of the discoverer and gives more control for goroutine management to the observer.
With these changes in place the Connector really didn't do anything, so moving the dialing into the ApplicationDiscoverer allows dialing failures to be retried by the existing backoff strategy in the discoverer.
Is there anything you are unsure about?
No
What issues does this relate to?
None

Again, the diff view is probably less useful than just looking at the https://github.com/dogmatiq/discoverkit/blob/9733b7600172bda3b8fc6c94b11474fa2158303b/application.go file.

Again, the diff view is probably less useful than just looking at the https://github.com/dogmatiq/discoverkit/blob/9733b7600172bda3b8fc6c94b11474fa2158303b/application.go file.


Make the avatarURL optional in the AccountDropdown

#404

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Am I correctly passing the arugment?

I'm trying to run a migration where I change the table of the migrations like so node-pg-migrate -t test_table "up" but for some reason the default table is still used (INSERT INTO "public"."pgmigrations" (name, run_on) VALUES ('1632743234625_v1.0', NOW());).
Can it be because I'm using dotenv before or am I missing something really obvious?
Whole command
dotenv -e ./../../.env node-pg-migrate -t test_table up

hi @nealok! sorry for a late answer.
The command looks correct to me, and migrations table can't be specified via env variable.
Btw from the docs:

If a .env file exists, it will be loaded using dotenv (if installed) when running the node-pg-migrate binary. If the .env file is not on the same level where the command has been called, you can use the --envPath option to point to the location of your .env file.

Could you try to run it with --envPath or place the env file into the same place where you run the command?

The issue was passing the argument correctly, for anybody searching look below for a working solution.
dotenv -e ./../../.env node-pg-migrate -- -t db_migration (notice the double dash before the actual argument)


Interpolating modulate with int is not signalled in debug mode but fails in release mode

Godot version
3.4.4-stable
System information
Windows 10
Issue description
Interpolating the "modulate" property, which is a Color, with int values does not yield a warning or error, and does nothing in debug mode. In release mode, it renders the CanvasItem black.
Steps to reproduce
See project below
Minimal reproduction project
modulate_release.zip

It's exactly the same in 3.5rc6


[part 1/n] Introduce vtable-based dispatch

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup
/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-ebpf

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
This is the first in a series of PRs that aim to encapsulate all engine-specific behavior of libscap behind a series of vtables, instead of ifs and #ifdefs.
The motivation is:

to clean up the code and make it more maintainable
to enable alternative instrumentation engines

Special notes for your reviewer:
This PR (temporarily) makes things much uglier and is just the first one in a series. With this PR, the most important scap functions are routed through a vtable, if present. This PR creates separate implementations for the nodriver, source_plugin and udig engines. eBPF, kmod and savefile are still TODO, as are additional vtables, which are used mostly at initialization time.
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
4721e2ec69e53997d5657a135946bb0a7ece5b75
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

All in all, it looks quite good to me as an intermediate step!
I want to gather some more feedback by other maintainers before approving this, but IMO this is a +1 for me.

This is looking good!

This is a bigger discussion I suppose, do you want to see the end result (or at least some future steps) before merging part 1 or do you trust me that we won't end up in worse shape than we already are? ;)

I trust you :blue_heart:

This will make maintaining and extending libscap so much easier! 🚀

I believe this can go in as I find this to be a much better way of handling the system call providers we have. The only question I had was about the handle, but if you feel that doing it like proposed makes casting and type safety easier it's absolutely fine :)

Wow! This is huge! Thank you @gnosek for all this work, I can't wait to see it merged :heart_eyes: :rocket:

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

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
8c07f8dfe098cd24771671cce7b81c94d558abe6
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
8c07f8dfe098cd24771671cce7b81c94d558abe6
link
true
/test build-libs-minimal

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
8c07f8dfe098cd24771671cce7b81c94d558abe6
link
true
/test build-libs-minimal

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs-minimal
8c07f8dfe098cd24771671cce7b81c94d558abe6
link
true
/test build-libs-minimal

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

build-libs-bundled-deps
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

build-libs-bundled-deps
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-bundled-deps

build-libs-with-chisels
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-with-chisels

build-libs-minimal
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

/retest

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

Test name
Commit
Details
Required
Rerun command

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

build-libs-bundled-deps
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-bundled-deps

build-libs-with-chisels
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-with-chisels

build-libs-minimal
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-minimal

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

build-libs-bundled-deps
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-bundled-deps

build-libs-minimal
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-minimal

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

build-libs-with-chisels
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-with-chisels

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

build-libs-bundled-deps
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-bundled-deps

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

build-libs-with-chisels
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-with-chisels

build-libs-minimal
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

build-libs-with-chisels
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-with-chisels

build-libs-minimal
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-minimal

build-libs-bundled-deps
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-bundled-deps

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

build-libs-with-chisels
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-with-chisels

build-libs-minimal
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-minimal

build-libs-bundled-deps
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-bundled-deps

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

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

Test name
Commit
Details
Required
Rerun command

build-libs
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs

build-libs-with-chisels
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-with-chisels

build-libs-bundled-deps
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-bundled-deps

build-libs-arm
7e9dff7be33ae265acb9928e4228971d823f5c7e
link
true
/test build-libs-arm

build-libs-minimal
eb16ec7dfa91c30090a83ad2376399379767a8f8
link
true
/test build-libs-minimal

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

@Andreagit97 if you're okay with these changes, so am I :) This is just the first PR in a series so things like cleaning up scap-int.h can happen in a follow up PR.

Just noticed I need to make a few things static. Will update the PR

LGTM label has been added.  Git tree hash: 17cab41fb3ec7440e0e56b297aefd672d4396d54

New changes are detected. LGTM label has been removed.

LGTM label has been added.  Git tree hash: 9461a4085c4be567fa8ed1347505a8f4e38941f2

/retest

New changes are detected. LGTM label has been removed.

LGTM label has been added.  Git tree hash: f9d603cd78d90942d5d21de20b45e2e46db008eb

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/retest

/unhold

/test build-libs


fix: searchdialog - undefined scroll ref

PR Fixes:

Undefined scrollableContainerRef: The code previously referenced a variable named scrollableContainerRef for scrolling functionality, but it wasn't defined. I fixed that by defining it.

Resolves:  #351

Now website is working fine & error has gone

Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure you there is no similar/duplicate pull request regarding the same issue

Hello @CodeWhispererr , you can close this PR , as this issue has been resolved by harkirat

Done


[Snyk] Upgrade eslint from 8.49.0 to 8.50.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade eslint from 8.49.0 to 8.50.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released a month ago, on 2023-09-22.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Regular Expression Denial of Service (ReDoS) SNYK-JS-GETFUNCNAME-5923417
609/1000  Why? Proof of Concept exploit, Recently disclosed, CVSS 8.6
Proof of Concept

Information Exposure SNYK-JS-UNDICI-5962466
609/1000  Why? Proof of Concept exploit, Recently disclosed, CVSS 8.6
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: eslint

8.50.0 - 2023-09-22Features

27d5a9e feat: add suggestions to array-callback-return (#17590) (Tanuj Kanti)
f9082ff feat: flat-rule-tester make sure default config always matches (#17585) (fnx)
83914ad feat: Implement SourceCode#applyInlineConfig() (#17351) (Nicholas C. Zakas)
22a5582 feat: add rule no-object-constructor, deprecate no-new-object (#17576) (Francesco Trotta)
85a3d9e feat: allowVoid option in array-callback-return (#17564) (Tanuj Kanti)

Bug Fixes

cc4d26b fix: Ensure deprecated context.parserServices warns (#17593) (Nicholas C. Zakas)
1ea4cfb fix: Ensure all RuleTester tests all deprecated context methods (#17587) (Nicholas C. Zakas)
aa1b657 fix: wrong suggestion and message in no-misleading-character-class (#17571) (Yosuke Ota)

Documentation

1800537 docs: Fix and standardize JSX code examples (#17591) (Francesco Trotta)
48a44a7 docs: Add correct/incorrect tags to prefer-arrow-callback (#17589) (Francesco Trotta)
20893d4 docs: fix incorrect tag's place (#17575) (Tanuj Kanti)
bd7a71f docs: Update README (GitHub Actions Bot)

Chores

f8a8a2d chore: upgrade<EMAIL_ADDRESS>(#17599) (Milos Djermanovic)
38ada6d chore: package.json update for @ eslint/js release (ESLint Jenkins)

8.49.0 - 2023-09-08Features

da09f4e feat: Implement onUnreachableCodePathStart/End (#17511) (Nicholas C. Zakas)
32b2327 feat: Emit deprecation warnings in RuleTester (#17527) (Nicholas C. Zakas)
acb7df3 feat: add new enforce option to lines-between-class-members (#17462) (Nitin Kumar)

Documentation

ecfb54f docs: Update README (GitHub Actions Bot)
de86b3b docs: update no-promise-executor-return examples (#17529) (Nitin Kumar)
032c4b1 docs: add typescript template (#17500) (James)
cd7da5c docs: Update README (GitHub Actions Bot)

Chores

b7621c3 chore: remove browser test from npm test (#17550) (Milos Djermanovic)
cac45d0 chore: upgrade<EMAIL_ADDRESS>(#17549) (Milos Djermanovic)
cd39508 chore: package.json update for @ eslint/js release (ESLint Jenkins)
203a971 ci: bump actions/checkout from 3 to 4 (#17530) (dependabot[bot])
a40fa50 chore: use eslint-plugin-jsdoc's flat config (#17516) (Milos Djermanovic)
926a286 test: replace Karma with Webdriver.IO (#17126) (Christian Bromann)
f591d2c chore: Upgrade config-array (#17512) (Nicholas C. Zakas)

    from eslint GitHub release notes

Commit messages

Package name: eslint

299bfae 8.50.0
212687c Build: changelog update for 8.50.0
f8a8a2d chore: upgrade<EMAIL_ADDRESS>(#17599)
38ada6d chore: package.json update for @ eslint/js release
27d5a9e feat: add suggestions to array-callback-return (#17590)
f9082ff feat: flat-rule-tester make sure default config always matches (#17585)
83914ad feat: Implement SourceCode#applyInlineConfig() (#17351)
cc4d26b fix: Ensure deprecated context.parserServices warns (#17593)
1ea4cfb fix: Ensure all RuleTester tests all deprecated context methods (#17587)
1800537 docs: Fix and standardize JSX code examples (#17591)
22a5582 feat: add rule `no-object-constructor`, deprecate `no-new-object` (#17576)
48a44a7 docs: Add correct/incorrect tags to `prefer-arrow-callback` (#17589)
aa1b657 fix: wrong suggestion and message in `no-misleading-character-class` (#17571)
20893d4 docs: fix incorrect tag's place (#17575)
85a3d9e feat: allowVoid option in array-callback-return (#17564)
bd7a71f docs: Update README

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

fix on #148


Add method for testing pdf content

https://github.com/previousdeveloper/selenide/commit/2d2b9bfa88e3bd3e65aa08612e32884b8d4cf462

If Selenide provides support for testing PDF docs (using Apache PDFBox or anyother), it will be very helpful

@leslyarun I am in doubt if it should be a part of Selenide. Because it's not directly connected to WebDriver and browser automation. Probably it would be better to create a separate project like "github.com/codeborbe/pdf-asserts".
Can you specify, what exactly do you need to test in PDF?
As I see, you can only test that PDF contains required text. So, the API could look like this:
  File pdf = $("#cv").download();
  assertPdfContains(pdf, "John Belushi", "Birthday", "31.12.1956");

Is it what you want?

File pdf = $("#cv").download();
assertPdfContains(pdf, "John Belushi", "Birthday", "31.12.1956");
ya, this is what I want.
Ya, maybe we can have a separate project for PDF Automation.
Plus, If we are able to render the exact text (like, if there is a table in pdf, it should be rendered xactly in the same way), it would be great.
One more thing is, the text we are searching will be found if it is present in the entire PDF. I want to  search the text based on specific criteria.
(E.g.) If I want to search the word "hello" in a pdf, and if there are 10 instances where "hello" is displayed, then I don't want it to find the 1st instance and tell that the search term is found .
Instead I want to find the particular search term based on some criteria like - "hello" should be present in 3rd column of a table.

@leslyarun Ok, thank you for detailed explanation.
It's easy to assert text in the entire PDF file.
But I am not sure it's technically possible to make more specific texts like you have described. I am not sure if PDFBox or any other library allow it. I need to investigate it.
By the way, I found a similar library (quite old): http://jpdfunit.sourceforge.net/docs/GettingStarted.html

@leslyarun I created a first version of library PDFest (like "PDF Test"): https://github.com/codeborne/pdfest
Probably you can suggest better name? Name that would sound cool? Like "PDFUnit", "PDFee", "PDFium", "PDFilla", "PDFico", "VerifyPDF", "AssertPDF", "PDFool", "...

Wow that's great . Very fast @asolntsev.
What about PDFium or PDFide ???

PDFium is unfortunately already used. PDFium is a pdf rendering engine from Google.
And PDFide sounds like "pdf IDE" (the same problem is with Selenide too).
And I think that this name should be applicable for other formats too. Probably we will also create libraries for testing xls, epub, doc files. They could be named in the same manner.
Sent from my HTC
----- Reply message -----
From: "leslyarun"<EMAIL_ADDRESS>To: "codeborne/selenide"<EMAIL_ADDRESS>Cc: "Andrei Solntsev"<EMAIL_ADDRESS>Subject: [selenide] Add method for testing pdf content (#132)
Date: Thu, Jun 25, 2015 02:19
Wow that's great . Very fast @asolntsev.
What about PDFium or PDFide ???
—
Reply to this email directly or view it on GitHub.

We will be doing only PDF docs , or xls, epub also in this? @asolntsev

Only pdf. I would create separate project "xls-test" for testing excel files. Testing epub is technically possible, but I am not sure if anybody actually needs it.
Sent from my HTC
----- Reply message -----
From: "leslyarun"<EMAIL_ADDRESS>To: "codeborne/selenide"<EMAIL_ADDRESS>Cc: "Andrei Solntsev"<EMAIL_ADDRESS>Subject: [selenide] Add method for testing pdf content (#132)
Date: Fri, Jun 26, 2015 10:21
We will be doing only PDF docs , or xls, epub also in this? @asolntsev
—
Reply to this email directly or view it on GitHub.

@asolntsev
pdf-test is OK. Is it possible to integrate Apache Lucene in the project, so that we can search more efficiently???

@leslyarun what do you want to search during test run? Please describe the case.

I try to do it on my project. We have a lot of printing documents, which user is unable to see before they are printed. I found a way to print a single document on a virtual printer and then read it from the code

@asolntsev
The text we are searching will be found if it is present in the entire PDF. I want to search the text based on specific criteria.
(E.g.) If I want to search the word "hello" in a pdf, and if there are 10 instances where "hello" is displayed, then I don't want it to find the 1st instance and tell that the search term is found .
Instead I want to find the particular search term based on some criteria like - "hello" should be present in 3rd column of a table.
Also, assert will find all the words that starts with "hello" ?
Or will it only assert the exact text ?
(e.g. If there is a word "hellouis'', will it tell "hello" is present???)

@leslyarun How Apache Lucene would help us? As much as I understand, Apache Lucene can quickly search for a substring in huge texts. In most cases, PDFs that we test are not very big. It's typically some payment PDF form consisting of 1-2 pages.
The question actually is: is it techically possible to extract layout information from PDF. I don't know yet. I need to investigate it. At the moment pdf-test only allows you to assert that PDF contains some substring. In most cases it's good enough. We typivcally test that PDF contains correct amount, bill date and payer name.

I have to test 250 pages, so I thought , Lucene will help to search efficiently.
Also, assert will find all the words that starts with "hello" ?
Or will it only assert the exact text ?
(e.g. If there is a word "hellouis'', will it tell "hello" is present???)
Assert will find the 1st instance and tell that text is present ?

Yes, right now assertThat(pdf, containsText("hello")) finds any occurrence of "hello" in pdf, including "hellouius".
Sent from my HTC
----- Reply message -----
From: "leslyarun"<EMAIL_ADDRESS>To: "codeborne/selenide"<EMAIL_ADDRESS>Cc: "Andrei Solntsev"<EMAIL_ADDRESS>Subject: [selenide] Add method for testing pdf content (#132)
Date: Sun, Jun 28, 2015 09:44
I have to test 250 pages, so I thought , Lucene will help to search efficiently.
Also, assert will find all the words that starts with "hello" ?
Or will it only assert the exact text ?
(e.g. If there is a word "hellouis'', will it tell "hello" is present???)
Assert will find the 1st instance and tell that text is present ?
—
Reply to this email directly or view it on GitHub.

can u give me the maven code for pdf-test ? I need to experiment

Sure.
groupIe: com.codeborne
artifactId: pdf-test
version: 1.1
Actually you can find this info from mavens repo:
http://search.maven.org/#search|ga|1|Codeborne
Sent from my HTC
----- Reply message -----
From: "leslyarun"<EMAIL_ADDRESS>To: "codeborne/selenide"<EMAIL_ADDRESS>Cc: "Andrei Solntsev"<EMAIL_ADDRESS>Subject: [selenide] Add method for testing pdf content (#132)
Date: Sun, Jun 28, 2015 11:23
can u give me the maven code for pdf-test ? I need to experiment
—
Reply to this email directly or view it on GitHub.

@leslyarun
You said: "I have to test 250 pages, so I thought , Lucene will help to search efficiently."
Lucene will not make your tests faster. Typical usage of Lucene is as follows:

Index all large texts on startup (one time)   - it's long operation
Serve multiple search requests many times  - it's fast operation

In tests, you need to perform both 1. and 2. steps. You still need to waste time to Index your pdf during test run.

Fine.
Then we don't need lucene
Regards,
Lesly Arun Franco
On 29-Jun-2015 3:06 am, "Andrei Solntsev"<EMAIL_ADDRESS>wrote:

@leslyarun https://github.com/leslyarun
You said: "I have to test 250 pages, so I thought , Lucene will help to
search efficiently."
Lucene will not make your tests faster. Typical usage of Lucene is as
follows:

Index all large texts on startup (one time) - it's long operation
Serve multiple search requests many times - it's fast operation

In tests, you need to perform both 1. and 2. steps. You still need to
waste time to Index your pdf during test run.
—
Reply to this email directly or view it on GitHub
https://github.com/codeborne/selenide/issues/132#issuecomment-116344412.

@asolntsev
when will this become possible ???? :
File pdf = $("#cv").download();
assertPdfContains(pdf, "John Belushi", "Birthday", "31.12.1956");

@leslyarun It has been possible for a while.
Just add dependency pdf-test to your project:
  <dependency>
    <groupId>com.codeborne</groupId>
    <artifactId>pdf-test</artifactId>
    <version>1.2</version>
    <scope>test</scope>
  </dependency>

and use it:
PDF pdf = new PDF($("#cv").download());
assertThat(pdf, containsText("John Belushi"));
assertThat(pdf, containsText("Birthday"));
assertThat(pdf, containsText("31.12.1956"));

@asolntsev  Thanks a lot :)

@asolntsev  there is no assertThat method in testng.
I can only directly use this :
import static org.hamcrest.MatcherAssert.assertThat;
But if I use pdf-test and xls-test in the same class, then it will show error for the second asserthat of xls-test:
assertThat(pdf, containsText("checks"));```

```XLS spreadsheet = new XLS (getClass().getClassLoader().getResource("statement.xls"));
assertThat(spreadsheet, containsText("Statement"));```

any support for testng???

There is no special support needed for TestNG. Both pdf-test and xls-test can be used with TestNG, exactly as you described.
The problem is, that they cannot be used together. More exactly, they can be used in the same test, but you need to use full-qualified class name. Like this:
assertThat(pdf, com.codeborne.pdftest.PDFMatchers.containsText());
It's not nice. I will think how to solve this problem. But probably it's not a good idea to test both pdf and xls in the same test? They are different things.
Sent from my HTC
----- Reply message -----
From: "leslyarun"<EMAIL_ADDRESS>To: "codeborne/selenide"<EMAIL_ADDRESS>Cc: "Andrei Solntsev"<EMAIL_ADDRESS>Subject: [selenide] Add method for testing pdf content (#132)
Date: Sun, Jul 5, 2015 11:04
@asolntsev  there is no assertThat method in testng.
I can only directly use this :
import static org.hamcrest.MatcherAssert.assertThat;
But if I use pdf-test and xls-test in the same class, then it will show error for the second asserthat of xls-test:
PDF pdf =new PDF( $(By.cssSelector("#pers-new-left > div.grid_6.content > p:nth-child(16) > em > a:nth-child(1)")).download());
assertThat(pdf, containsText("checks"));
XLS spreadsheet = new XLS (getClass().getClassLoader().getResource("statement.xls"));
assertThat(spreadsheet, containsText("Statement"));
any support for testng???
—
Reply to this email directly or view it on GitHub.

@asolntsev  In my application, pdf file opens in a new window.
How can I test PDF in this scenario?
I don't want to manually download the PDF and test it using pdf-test.
download() works only in href.
Any Workarounds ?

You can catch the file using proxy server. It's quite easy. Just search how to use "mob browser proxy" with Selenium.
I will try to make it even simpler in future versions of Selenide.
Sent from my HTC
----- Reply message -----
From: "leslyarun"<EMAIL_ADDRESS>To: "codeborne/selenide"<EMAIL_ADDRESS>Cc: "Andrei Solntsev"<EMAIL_ADDRESS>Subject: [selenide] Add method for testing pdf content (#132)
Date: Tue, Jul 7, 2015 12:55
@asolntsev  In my application, pdf file opens in a new window.
How can I test PDF in this scenario?
I don't want to manually download the PDF and test it using pdf-test.
download() works only in href.
Any Workarounds ?
—
Reply to this email directly or view it on GitHub.


New version: GeoArrays v0.7.0

Registering package: GeoArrays
Repository: https://github.com/evetion/GeoArrays.jl
Created by: @evetion
Version: v0.7.0
Commit: 8cc15a75fb2ac1f9188a447ee46b4b3430bd54e7
Reviewed by: @evetion
Reference: https://github.com/evetion/GeoArrays.jl/commit/8cc15a75fb2ac1f9188a447ee46b4b3430bd54e7#commitcomment-63839472
Description: Simple geographical raster interaction built on top of ArchGDAL, GDAL and CoordinateTransformations

Maybe let's hold this breaking release to make sure https://github.com/evetion/GeoArrays.jl/issues/80 is fully addressed?

Hold this PR?

[noblock]
Ok, this can be merged now.


Add AioHttpIntegration and SqlalchemyIntegration to Sentry

Add AioHttpIntegration and SqlalchemyIntegration to Sentry

https://docs.sentry.io/platforms/python/sqlalchemy/
https://docs.sentry.io/platforms/python/aiohttp/

Do we need to add aiocontextvars to the requirements? The aiohttp integration docs mention it.

Ah nvm, looks like it's only 3.6 since we target 3.7 and above we should be good. Thanks!


Update wit.json : "i love you"

I want to create a new module called love.
The reason is that I sent a message to JARVIS that i love you, but I did not get the right answer.
The word i love you means to believe in the other person and at the same time is pleasant.
If you do not answer the most basic word i love you, JARVIS will be disappointed.
I wanted to make it even closer between users and JARVIS by adding new modules.
This will increase the credibility of the JARVIS messenger itself.

Thank you for taking the time to contribute! This is sincerely appreciated. 😇
(Powered by GitMate.io)


Department views show wrong parent

Looks like the department views have some small errors:
`views/user-management/department/edit.blade.php:50
this line: <option value="{{ $item->id }}" {{ ($item->id == $department->id) ? 'selected' : '' }}>{{ $item->title }}
should be: <option value="{{ $item->id }}" {{ ($item->id == $department->parent_id) ? 'selected' : '' }}>{{ $item->title }}
views/user-management/department/index.blade.php:62
this line: {{  $item->parent ? $item->parent->title : '----' }}
should be: {{  $item->parent_id ? $departments->find($item->parent_id)['title'] : '----' }}`

Hi @capsandiego
I apologize for the extremely delayed reply! Here, I have refactored the package and have big plans to add more functionality.
weprodev/larapanel-framework
Best,
Michael


Compare DevX between Aggregator and Stackup Bundler

Stackup bundler is an implementation of the 4337 equivalent of our aggregator:
https://github.com/stackup-wallet/stackup-bundler
Try this out and see what its dev experience is like compared to our aggregator.

@jzaki I'm a bit confused about whether you were more interested in the devX of running the aggregator/bundler or the devX of using an existing instance (ie, using the api).
For now I'm looking at a bit of both.

Not sure if they have more docs or not. Their link is currently broken: https://github.com/stackup-wallet/stackup-bundler/issues/91.

Getting up and running basically works as described.
You need to edit the .env file to set the URL of the node you're going to use (eg localhost:8545). This isn't documented.

As for the experience using the API, it's unclear right now.
It seems to be just-the-standard. They use json-rpc just like a node, and provide the eth_sendUserOperation method as described in the EIP.
It's hard to test because 4337 doesn't prescribe the wallet to use. Presumably stackup tests with their own smart contract wallets (seems to be their main thing), or some dev version of this.
I'm going to park this temporarily since I'm waiting for feedback both from @jzaki and from stackup (https://github.com/stackup-wallet/stackup-bundler/issues/91, https://github.com/stackup-wallet/stackup-bundler/issues/92).

Hi @voltrevo! I'm the author of stackup bundler and happy to answer some of your questions here. Alternatively, happy to also chat in our discord since we're generally more active there. Strange that the invite link didn't work for you, but you can try this one too.

Not sure if they have more docs or not.

We recently did an overhaul of our documentation and I must have missed updating this link. The updated bundler docs can be read here.

You need to edit the .env file to set the URL of the node you're going to use (eg localhost:8545). This isn't included in their readme steps.

Thanks for spotting this, I'll have to take a look into refreshing the readme soon. In the mean time we do document most of the config variables here. Although there are a couple new ones missing which I will also need to add. But you can also see config/values.go for the full list.

It's hard to test because 4337 doesn't prescribe the wallet to use. Presumably stackup tests with their own smart contract wallets (seems to be their main thing), or some dev version of this.

So there are primarily two ways we test our bundler.

Using our erc-4337-examples repo. This and our quickstart guide is generally what we share with other developers looking to jump in and test out an end to end UserOperation flow.
We also use the bundler-spec-tests as a more formal way of checking that the bundler is compliant with the EIP.

@jzaki I'm a bit confused about whether you were more interested in the devX of running the aggregator/bundler or the devX of using an existing instance (ie, using the api).

@voltrevo the general point is to ensure the BLS Wallet aggregator dev exp was at a point that you and the team are comfortable with. I gave Stackup as an example that was somewhat comparable, not pursuing 4337 bundling/use specifically.

Thanks @hazim-j 🙌.
@jzaki Gotcha. Shifting focus to improving docker support and possibly switching to sqlite.


"In main.cpp:fatal error: uWS/uWS.h: No such file or directory" while running make command!

I have cloned the uWebSockets repository into the PID controller folder but still the make command fails yet cmake compilation is successful. How can I figure this out?
THE WHOLE ERROR IS:
In main.cpp:fatal error: uWS/uWS.h: No such file or directory
compilation terminated.
CMakeFiles/pid.dir/build.make:86: recipe for target 'CMakeFiles/pid.dir/src/main.cpp.o' failed
make[2]: *** [CMakeFiles/pid.dir/src/main.cpp.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/pid.dir/all' failed
make[1]: *** [CMakeFiles/pid.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

https://github.com/udacity/CarND-Path-Planning-Project/issues/51


WebpackError: ReferenceError: window is not defined

I am having irritative behaviour with my gatsby build. I can successfully run the development build using npm start but when I use to run it in production mode using gatsby build I am getting below error
error Building static HTML failed for path "/application/"

See our docs page on debugging HTML builds for help https://gatsby.app/debug-html

  6097 |
  6098 | function getLocaleObject(localeName) {
> 6099 |   return window.__localeData__ ? window.__localeData__[localeName] : null;
       | ^
  6100 | }
  6101 |
  6102 | function getFormattedWeekdayInLocale(date, formatFunc, locale) {

  WebpackError: ReferenceError: window is not defined

  - index.js:6099 getLocaleObject
    [lib]/[react-datepicker]/es/index.js:6099:1

  - index.js:5973 formatDate
    [lib]/[react-datepicker]/es/index.js:5973:1

  - index.js:5990 safeDateFormat
    [lib]/[react-datepicker]/es/index.js:5990:1

  - index.js:8822 DatePicker._this.renderDateInput
    [lib]/[react-datepicker]/es/index.js:8822:1

  - index.js:8900 DatePicker.render
    [lib]/[react-datepicker]/es/index.js:8900:1

  - bootstrap:19 c
    lib/webpack/bootstrap:19:1

  - bootstrap:25 a.render
    lib/webpack/bootstrap:25:1

  - bootstrap:24 a.read
    lib/webpack/bootstrap:24:1

  - bootstrap:36 renderToString
    lib/webpack/bootstrap:36:1

  - static-entry.js:194 Module../.cache/static-entry.js.__webpack_exports__.defa    ult
    lib/.cache/static-entry.js:194:18

  - bootstrap:24 Promise
    lib/webpack/bootstrap:24:1

  - gatsby-browser-entry.js:2 Promise._resolveFromExecutor
    lib/.cache/gatsby-browser-entry.js:2:1

  - bootstrap:68 new Promise
    lib/webpack/bootstrap:68:1

Can someone please help why I am getting this error.
Thank you!!!

Have such error too.

I'm facing the same problem. In fact this library is not compatible with SSR (Server Side Rendering).
After a short investigation, the localization data are stored using window, which is not defined at compile-time in Gatsby. It's because this library share the locale you configure somewhere to the whole app.

@julien1619 @abobykin Could you find some work around?

@julien1619 Hi! As for me - don't know actually how it's all around Gatsby, have only React/Redux/Node.js in the stack I was starting working with couple of days ago. And I've made this thing working quite enough for my needs with a help of 'handleSelect' attribute. I've catched it in my React component function and then save it to the state object value which I bind to the other input below this input with datepicker which I've made transparent with CSS).

@julien1619 Please note that selected={this.state.date} was not working for me, right for the reason you described I suppose, I've just found this with debugger and remove this line at all from the the html component. It works only without this ) Hope it would be helpful for you!

@abobykin oh so you removed the selected option and get it worked! Great but I think this should be.fixed from the module itself. Why someone from the team is not replying

I've succeeded to make it work but the translations won't work in SSR.
To do it here is what I've done:
const isSSR = typeof window === 'undefined';
if (!isSSR) {
  registerLocale('fr', fr);
  setDefaultLocale('fr');
}

// In the render function
<DatePicker
  selected={filter.dateStart}
  onChange={this.handleDateStartChange}
  locale={isSSR ? 'en' : 'fr'}
/>

Well I have found a solution.
Go to node_modules/react-datepicker/es/index.js and define the window variable
var window = require('window')

@ashishlal91 Sounds cool! I'll try it soon) But of course this folder is rewritable. Let's give it a try and then maybe offer a fix to creators of this module.

@ashishlal91 not working!

There is a PR waiting to be merged that will fix this bug : #1634

@ron766  What's not working?

I forked #1634 (needed to build and push the built files) to test it on my Gatsby build and it works. For now I'm using "react-datepicker": "github:julien1619/react-datepicker#window-fix" in my package.json file until the fix is made available.

Something like this for Browserify and Webpack:
<Datepicker value={process.browser && date} />

For me in gatsby it's working something like that:
<DatePicker
        locale="en"
        selected={this.props.field.value}
        dateFormat="yyyy/MM/dd"
        withPortal
        onChange={this.handleChange}
      />

Simply adding locale="en" to my <DatePicker> elements solved it for me.

How about that:
import DatePicker from 'react-datepicker';
import node from 'detect-node';
{!node && <DatePicker />}

No I think it would be a dirty fix, the root cause should be fixed. I think the problem here, is that it's behaving in a different way than date-fns.
The date-fns library does not have any global configuration, it lets the user handle a configuration object. react-datepicker keeps a global configuration object whereas it should provide a similar way to configure it than date-fns. By doing it this way, it would remove the need for any global window usage.
Could there be a way to do it this way?

No I think it would be a dirty fix, the root cause should be fixed. I think the problem here, is that it's behaving in a different way than date-fns.
The date-fns library does not have any global configuration, it lets the user handle a configuration object. react-datepicker keeps a global configuration object whereas it should provide a similar way to configure it than date-fns. By doing it this way, it would remove the need for any global window usage.
Could there be a way to do it this way?

I agree - it is dirty, but I need solution today/now, and issue was created 7 Feb and is still not solved.
Beside, not rendering element on the server usually will not cause problems in crawling the page (hard to believe that value of input representing this component will be important). The only issue (side effect) is that it will cause inconsistency of prerendered html to browser side rendered html using React.hydrate()
To me solution proposed here link looks even worse.
.. with all respect :)

You're completely right ;) I wrongly thought you were proposing a definitive fix, sorry if I was a little bit agressive, it was not intended.


mip_opt_out is not supported as an option

What is the current behavior?

The Model Improvement Program documentation says that to opt out of the Model Improvement Program using the Deepgram Python SDK, you can add mip_opt_out: true to the PrerecordedOptions:
#  Install the SDK: pip install deepgram-sdk

import asyncio
import os
from dotenv import load_dotenv

from deepgram import DeepgramClient, PrerecordedOptions

load_dotenv()

API_KEY = os.getenv("DEEPGRAM_API_KEY")
AUDIO_URL = {
    "url": "https://static.deepgram.com/examples/Bueller-Life-moves-pretty-fast.wav"
}

options: PrerecordedOptions = PrerecordedOptions(
    model="nova-2",
    mip_opt_out: true
)

deepgram: DeepgramClient = DeepgramClient(API_KEY)

async def transcribe_url():
    url_response = await deepgram.listen.asyncprerecorded.v("1").transcribe_url(
        AUDIO_URL, options
    )
    return url_response

async def main():
    try:
        response = await transcribe_url()
        print(response.to_json(indent=4))
    except Exception as e:
        print(f"Exception: {e}")

if __name__ == "__main__":
    asyncio.run(main())

The sample appears to have a syntax error; it should read mip_opt_out=True. Perhaps copy and pasted from Javascript?
But even with that fixed, it fails with an error because mip_opt_out is not expected as a keyword argument.
Steps to reproduce

Attempt to run the above code sample. (The code sample also needs to be fixed to use proper Python syntax.)
Expected behavior

mip_opt_out is part of the Deepgram API and should be accepted by the Python SDK.
Please tell us about your environment

macOS Sequoia 15.0.1, Python 3.12.4
Other information

Please see pull request: https://github.com/deepgram/deepgram-python-sdk/pull/475

Documentation has been updated to use custom_options and addons, so closing this issue

Link for those that are interested:
https://developers.deepgram.com/docs/the-deepgram-model-improvement-partnership-program#want-to-opt-out


[terra-icon] Updated eIFU text to be Instructions for Use

Summary
Fixes #2759

@PaulSolDev will need update to requirements

Functional review complete. No issues identified.


HLK-SW16 Drops Connection

Home Assistant release with the issue:

0.100.2
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Integration:

https://www.home-assistant.io/integrations/hlk_sw16/
Description of problem:
I've noticed that the HLK-SW16 integration loses connection to the board every 15 seconds or so for a very brief moment. If I check the log I can see the following messages:
"HLK-SW16 relay1 disconnected
23:27 components/hlk_sw16/init.py (WARNING)"
and right after that comes
"HLK-SW16 relay1 connected
23:27 components/hlk_sw16/init.py (WARNING)"
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

sensor:
  - platform: command_line
    name: CPU Temp
    command: "cat /sys/class/thermal/thermal_zone0/temp"
    unit_of_measurement: "°C"
    value_template: '{{ value | multiply(0.001) | round(0) }}'

hlk_sw16:
  relay1:
    host: <IP_ADDRESS>
    switches:
      0:
        name: relay1-0
      1:
        name: relay1-1
      2:
        name: relay1-2
      3:
        name: relay1-3
      4:
        name: relay1-4
      5:
        name: relay1-5
      6:
        name: relay1-6
      7:
        name: relay1-7
      8:
        name: relay1-8
      9:
        name: relay1-9
      a:
        name: relay1-a
      b:
        name: relay1-b
      c:
        name: relay1-c
      d:
        name: relay1-d
      e:
        name: relay1-e
      f:
        name: relay1-f

Traceback (if applicable):

Additional information:
If this is a problem with the configuration of the board itself; I'm sorry that I posted here in that case but could you then also provide me with the solution?


Handling for the scenario where blastn -query returns no results

Hi there,
Yesterday I ran into a situation where prep_genome_lib/ctat-vif-lib-integration.py errored on line 79:
    df = pd.read_csv(blastn_outfile, sep="\t", header=None, usecols=[1,2,8,9]) when the previous blastn step outputs a file with no contents.
This checks for the number of lines in the blastn output file and bypasses the processing instead creating a dummy file just with column headers for use downstream.
I am a bit of a python novice so please let me know I've done something silly!

oh, interesting.  Thanks for pointing this out.  Leave the PR in, but I
might handle it differently when I put out a future release.
On Fri, Aug 19, 2022 at 9:57 AM Robert Allaway @.***>
wrote:

Hi there,
Yesterday I ran into a situation where
prep_genome_lib/ctat-vif-lib-integration.py errored on line 79:
df = pd.read_csv(blastn_outfile, sep="\t", header=None, usecols=[1,2,8,9])
when the previous blastn step outputs a file with no contents.
This checks for the number of lines in the blastn output file and bypasses
the processing instead creating a dummy file just with column headers for
use downstream.
I am a bit of a python novice so please let me know I've done something
silly!
You can view, comment on, or merge this pull request online at:
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45
Commit Summary

19b2734
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45/commits/19b2734a91a39a2733ae45f80200e3c1aa4e5357
Update ctat-vif-lib-integration.py

File Changes
(1 file
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45/files
)

M prep_genome_lib/ctat-vif-lib-integration.py
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45/files#diff-022fe316496fd04c2235f6074c3d786f20c15b39f6ff3cd8e331cf695a2f0c6d
(24)

Patch Links:

https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45.patch
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45.diff
—
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZRKX4A5UPKYTZEKYZZEKTVZ6HDRANCNFSM57A2VINQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Brian J. Haas
The Broad Institute
http://broadinstitute.org/~bhaas http://broad.mit.edu/~bhaas

Also, just in case, please be aware that we provide a virus database
collection to use with ctat-vif, but go ahead and use it on your own set
too if that's of interest.
On Fri, Aug 19, 2022 at 10:32 AM Brian Haas @.***>
wrote:

oh, interesting.  Thanks for pointing this out.  Leave the PR in, but I
might handle it differently when I put out a future release.
On Fri, Aug 19, 2022 at 9:57 AM Robert Allaway @.***>
wrote:

Hi there,
Yesterday I ran into a situation where
prep_genome_lib/ctat-vif-lib-integration.py errored on line 79:
df = pd.read_csv(blastn_outfile, sep="\t", header=None, usecols=[1,2,8,9])
when the previous blastn step outputs a file with no contents.
This checks for the number of lines in the blastn output file and
bypasses the processing instead creating a dummy file just with column
headers for use downstream.
I am a bit of a python novice so please let me know I've done something
silly!
You can view, comment on, or merge this pull request online at:
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45
Commit Summary

19b2734
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45/commits/19b2734a91a39a2733ae45f80200e3c1aa4e5357
Update ctat-vif-lib-integration.py

File Changes
(1 file
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45/files
)

M prep_genome_lib/ctat-vif-lib-integration.py
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45/files#diff-022fe316496fd04c2235f6074c3d786f20c15b39f6ff3cd8e331cf695a2f0c6d
(24)

Patch Links:

https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45.patch
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45.diff
—
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/CTAT-VirusIntegrationFinder/pull/45,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZRKX4A5UPKYTZEKYZZEKTVZ6HDRANCNFSM57A2VINQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Brian J. Haas
The Broad Institute
http://broadinstitute.org/~bhaas http://broad.mit.edu/~bhaas

--
Brian J. Haas
The Broad Institute
http://broadinstitute.org/~bhaas http://broad.mit.edu/~bhaas

oh, interesting.  Thanks for pointing this out.  Leave the PR in, but I
might handle it differently when I put out a future release.
Sounds good, I figure there is probably a better way to handle this. :)

Also, just in case, please be aware that we provide a virus database
collection to use with ctat-vif, but go ahead and use it on your own set
too if that's of interest.

Thanks! I did see that.
I am revisiting a 2021 summer intern's project- IIRC (and I certainly might be wrong about this) - the collection of viruses provided was only HPV at that time or maybe HPV plus some other viruses?
I believe she retrieved all of the available human viral sequences from NCBI and used that - so I am trying to use that for consistencies sake, but I'll check out the virus fasta you have provided as well.


“Downloading the first original photo or video” then stops

15macbookpro@15Macbookpro Pictures % icloudpd --directory /Volumes/Media/Pictures --username<EMAIL_ADDRESS>--password ******
2020-10-07 14:06:12 DEBUG    Authenticating...
2020-10-07 14:06:19 DEBUG    Looking up all photos and videos from album All Photos...
2020-10-07 14:06:20 INFO     Downloading the first original photo or video to /Volumes/Media/Pictures/ ...
100%|#################################################################################| 1/1 [00:00<00:00,  1.62it/s]
2020-10-07 14:06:21 INFO     All photos have been downloaded!

I have about 40,000 photos+videos since 2010 on my iCloud Photo Library. Not sure why its stopping after downloading one random picture from 2019. Probably a simple config I’m missing, but i can’t seem to figure it out.
I even tried telling it just download the most recent 40k pics
15macbookpro@15Macbookpro Pictures % icloudpd --directory /Volumes/Media/Pictures --username<EMAIL_ADDRESS>--password **** --set-exif-datetime --recent 40000
2020-10-07 13:57:41 DEBUG    Authenticating...
2020-10-07 13:57:46 DEBUG    Looking up all photos and videos from album All Photos...
2020-10-07 13:57:46 INFO     Downloading 40000 original photos and videos to /Volumes/Media/Pictures/ ...
  0%|                                                                           | 1/40000 [00:00<3:30:16,  3.17it/s]
2020-10-07 13:57:47 INFO     All photos have been downloaded!

And I got the same issue. Any help would be much appreciated it

@woopiepoopie what version of icloudpd are you using? icloudpd --version should give you the answer

@AndreyNikiforov , thank you for the response!
15macbookpro@15Macbookpro Pictures % icloudpd --version
icloudpd, version 1.6.1

Let me know if I can provide any other details

Update: Tried on my windows box as well (last one was macOS)
Got the following error:

2020-10-09 11:47:11 DEBUG    Authenticating...
Traceback (most recent call last):
  File "c:\users\pcserver\appdata\local\programs\python\python39\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "c:\users\pcserver\appdata\local\programs\python\python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\PCserver\AppData\Local\Programs\Python\Python39\Scripts\icloudpd.exe\__main__.py", line 7, in <module>
  File "c:\users\pcserver\appdata\local\programs\python\python39\lib\site-packages\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "c:\users\pcserver\appdata\local\programs\python\python39\lib\site-packages\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "c:\users\pcserver\appdata\local\programs\python\python39\lib\site-packages\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "c:\users\pcserver\appdata\local\programs\python\python39\lib\site-packages\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "c:\users\pcserver\appdata\local\programs\python\python39\lib\site-packages\icloudpd\base.py", line 292, in main
    directory = os.path.normpath(directory)
  File "c:\users\pcserver\appdata\local\programs\python\python39\lib\ntpath.py", line 452, in normpath
    path = os.fspath(path)
TypeError: expected str, bytes or os.PathLike object, not NoneType

That helps a lot! I was able to reproduce the problem on python 3.9, while 3.8 works fine. Also, with --no-progress-bar option icloudpd works in both python versions. I suggest using --no-progress-bar until the issues is debugged and fixed. Please report if suggested workaround worked for you.


suggest about rocketmq client

I read some sources of the rocketmq client . I find the client that contain some api which can use to modify broker config or get broker config . I think this is risk for the broker . I suggest separate the api about client and manage .

I think just separate the api of client and management can't solve the risk of broker thoroughly. Set ACL can help control the authority of modify broker config. I found the latest version RocketMQ is already support ACL.

I think separate the api of client ,simplify the api of client that business apply . The ACL should modify the files , not conveniently .

Hi @hwind001 ,RocketMQ 4.4.0 version has already supported the acl feature,You can try it in you developping enviroment.If you meet any problem in trying acl feature,you can find me to resolve it.Thank you!


Regression in parsing Duration flag

https://github.com/alecthomas/kingpin/pull/329 introduced a difference in parsing a DurationVar compared to the old version.
Unfortunately, this breaks the old behaviour when the duration was a negative value. The most common use case is probably to have a Default("-1s") to denote that the value isn't set at all. Similarly a --some-duration="" would previously fail but is now treated as 0s. Here are the differences that I can observe:
// parse negative duration
time.ParseDuration("-1s") => `-1s` // no error
str2duration.Str2Duration("-1s") => `(*errors.errorString)(0x140001c2b70)(invalid input duration string)`

// parse empty string
time.ParseDuration("") => `(*errors.errorString)(0x140001c2b80)(time: invalid duration "")`
str2duration.Str2Duration("") => 0s // no error

In practice this leads to the following (some-duration is a DurationVar).
// old version (v2.2.6)
$ go run main.go --some-duration="-1s"
... // runs fine

// new version (v2.3.1 (2e61e1e))
$ go run main.go --some-duration="-1s"
main: error: invalid input duration string, try --help
exit status 1

// old version (v2.2.6)
$ go run main.go --some-duration=""
main: error: time: invalid duration "", try --help
exit status 1

// new version (v2.3.1 (2e61e1e))
$ go run main.go --some-duration=""
... // runs fine

/cc @adowair

This also seems to be breaking our 32-bit testing. See: https://github.com/prometheus/node_exporter/pull/2622

It looks like the v2 of this library may fix the issues.
@alecthomas, can you cut a new tag with #336?

👍

Tagged 2.3.2

2.3.2 fixed it for me: https://github.com/linki/chaoskube/commit/c4b9b0d69175b4ecefd3921e5690406782ae09ca
Thank you @alecthomas and @SuperQ 🙏


Upgrade ant-design-vue to version 3.x

After upgrading to Vue3, have moved to ant-design-vue version 2.x. However it is now recommended to move to version 3.x:
https://www.antdv.com/docs/vue/migration-v3:
The 2.x version is a compatible version developed for compatibility with Vue 3. It does not bring many new features, and most of the API changes are only for better compatibility with Vue 3. The 3.x version has greatly improved performance, ease of use, and functions. After the 3.x version is stable, we will archive the 2.x version. It is recommended that you upgrade to the 3.x version as soon as possible. Although there are many changes, they are basically compatible. You can upgrade gradually according to the warnings given by the console.
ISSUE TYPE

Enhancement Request

COMPONENT NAME
UI

Hi @utchoang since you have done a great work on the Vue3 PR can you please check this one?

Is it possible to upgrade to from Vue 2 to Vue 3 while still using Antd 1.7.8?
Thanks!

@eliran-natan No, because Antd 1.7 only works with Vue 2. When I migrate from Vue 2 -> 3, I have to upgrade the Antd version from 1->2 (refer to https://github.com/apache/cloudstack/pull/5151)

Thank you! So this means that Antd version 2 would work with Vue2? (So we could do the upgrade step by step: first upgrade antd while still working with Vue2, and later on upgrade to Vue3).
Will it be the same for antd version 3? :)

@eliran-natan If you want to use Antd version 2, you must use Vue 3. You can refer to https://2x.antdv.com/docs/vue/migration-v2

@utchoang, so this means that there cannot be a step-by-step upgrade.
We have to move to Vue3 and to Antd2 on the same go...do you agree? :)

To update to Vue 3 I must have antd2
To update to antd2 I must have Vue3

We've already migrated to vue3, so it's about moving to andv2 now.


JPA guide has wrong artifactId for Helidon EclipseLink support

There is a reference to helidon-eclipselink-cdi which should be helidon-integrations-eclipselink-cdi.

Pilot error; closing


[Rümker] New admin member page

Related Task and Figma
The page was almost completely rewritten to accomodate the figma cleanly. The code is stable, there are tweaks cf pending issues below but it won't change much => I think it's ripe for review
You can test it on https://front-edge.dust.tt/w/0ec9852c2f/members
Did what I could to make it ~ok on mobile
Pending topics on product / design:

style of the hover, style of invitations modal:  @Duncid r?
modals: awful notification to user: window.alert on fail, reload on success

working on it, reloading is ~necessary but a nice notification after could be done => @Duncid would love your input here

revoked members and revoked invitations will not be shown in this first iteration

or I can quickly add a checkbox "Show revoked" below the search bar (but then actionable or not?)

Avatar image issue that i'm investigating

Looks great.
Only thing is that the modal has an animation problem for me. It comes from the right but over shoot to the left and wiggle back in place

Looks great.
Only thing is that the modal has an animation problem for me. It comes from the right but over shoot to the left and wiggle back in place

Addressed in sparkle, and bumped the sparkle version in front accordingly


Unwanted exception - SupabaseException: supabase_url is required

Describe the bug
I copied the 'Initializing' code snippet from Supabase Python docs.
Inserted my URL and API Key as requested.
But I'm still facing an exception.
When trying out snippets from the docs, we should not face any unwanted exceptions.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://supabase.com/docs/reference/python/initializing'
Click on 'copy' button in the code snippet and paste in your Python notebook
Fill in your URL and API Key in the snippet
See error

Expected behavior
No exceptions should appear when using code from the docs as it is. If any, then notes should be made in the docs itself.
Screenshots
Pasted above
Desktop (please complete the following information):
Colab notebook
pip install Supabase was run

Hi @adityaraute, you should create a project by going to https://supabase.com/ you will be redirected to a page where you will get project url and key of your project which you have to use in your code.
Alternatively if you have already created project you can go to settings of project and under API find both url and keys
FYR.

Hey @adityaraute,
Thanks for the query! As @devilsaint99 mentioned you'll need to copy over the appropriate  supabase  URL key from settings > API
I've also tested it locally and there should be no exceptions thrown on the latest version. Do let me know if this is not the case for you though.
Thanks devilsaint99 for jumping in. Appreciate your detailed response!
Thanks!


feat(multi_object_tracker): mot bicycle model revision

Description
Revise bicycle motion model.

Bicycle motion model and its Jacobian matrix *VehicleTracke::*VehicleTracker

(Current PR) Additionally considering centripetal acceleration

Rear and front wheel positions lf_, lr_

The wheel position lr is the distance from the center of the object.
(Previous) The initial configuration was 80% of its length, which is outside of the object. The wheel position was not updated when the object size is updated.
(Current PR)

The front wheel position is 30% of the object length, front from the center.
The rear wheel position is 25-30% of the object length (depends on object type), rear from the center.
The wheel positions will be updated when the object length is updated.

Prediction on large delta t *Tracker::predict(const rclcpp::Time & time)

The prediction is done by linearized motion estimation.
(Previous) While the time interval is too large, the linear assumption induces a large error.
(Current PR) If the time interval is large, repeat the Kalman update in divided time steps.

Process noise model Eigen::MatrixXd Q

(Previous) The process noise was a set of fixed values.
(Current PR) The process noise will consider current states and physical limitations.

In a high velocity, the object cannot have a high turn-rate, limited by latitudinal acceleration limit.
In a very slow velocity, the object cannot turn, limited by the bicycle motion model and its maximum steer angle (slip angle).
By modifying the process noise, the following improvements are expected.
Yaw stability on straight moving objects (lower Kalman gain)
Yaw trackability on turning objects (higher Kalman gain)

Tracked object output - twist covariance object.kinematics.twist_with_covariance

The tracked object interface has a velocity vector (vx and vy) while the tracker has velocity and slip angle. The covariance matrix is converted based on those relationships.

Refactoring: vx to vel (velocity in the tracking model is not a vector.)

This PR contains multiple changes since one of the changes can cause instability of tracking results. The multiple changes are incorporated for stability and trackability.
Related links
https://tier4.atlassian.net/browse/RT1-4914
Tests performed
Simulations of sensing and perception modules were performed under a tier4 deployment.
Blue objects: Detected objects
Red objects: Recorded predicted objects
Yellow objects: Predicted objects done by the revised tracker

Turning objects at a cross section

https://github.com/autowarefoundation/autoware.universe/assets/42434141/fa439733-e0e9-454b-a90b-119aef4c1f75
The revised tracker tracks yaw rate better than before. As result, the predicted objects follows turning objects well.
https://github.com/autowarefoundation/autoware.universe/assets/42434141/4df335cd-ddb9-4fc8-bb59-9fdc0d82d322
In tracking objects that turn and then move straight, the uncertainty of the yaw rate is set larger to avoid overestimating the turning.

Straight cruising object

https://github.com/autowarefoundation/autoware.universe/assets/42434141/8729181b-00a3-4732-94a9-a5def8e45c34
No performance degradation is observed in a tracking straight-moving object.
It can be seen that the revised tracker reduces position uncertainty (covariance matrix) by accumulating measurements.
Notes for reviewers
The Mahalanobis distances gate threshold is enlarged.
Interface changes
Not applicable.
Effects on system behavior
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

before

$$
\begin{aligned}
x_{k+1} & =x_{k}+v_{k} \cos \left(\psi_{k}+\beta_{k}\right) d t \
y_{k+1} & =y_{k}+v_{k} \sin \left(\psi_{k}+\beta_{k}\right) d t \
v_{k+1} & =v_{k} \
\psi_{k+1} & =\psi_{k}+\frac{v_{k}}{l_{r}} \sin \beta_{k} d t \
\beta_{k+1} & =\beta_{k}
\end{aligned}
$$

after

$$
\begin{aligned}
x_{k+1} & = x_{k} + v_{k} \cos \left( \psi_{k}+\beta_{k} \right) {d t}
-\frac{1}{2}  \left\lbrace w_k v_k \sin \left(\psi_{k}+\beta_{k} \right) \right\rbrace {d t}^2\
y_{k+1} & = y_{k} + v_{k} \sin \left( \psi_{k}+\beta_{k} \right) {d t}
+\frac{1}{2}  \left\lbrace w_k v_k \cos \left(\psi_{k}+\beta_{k} \right) \right\rbrace {d t}^2\
\psi_{k+1} & =\psi_{k} + w_k {d t} \
v_{k+1} & = v_{k} \
\beta_{k+1} & =\beta_{k}
\end{aligned}
$$

I updated this branch to import https://github.com/autowarefoundation/autoware.universe/pull/6278.
This will help you pass build-and-test-differential faster.


shoud channel pruning method fit for inception v1?

I want to prune inception v1 , can channel pruning fit for it ?

Yes.
Best,
Yihui He

From: lanka<EMAIL_ADDRESS>Sent: Thursday, October 26, 2017 9:45:04 AM
To: yihui-he/channel-pruning
Cc: Subscribed
Subject: [yihui-he/channel-pruning] shoud channel pruning method fit for inception v1? (#43)
I want to prune inception v1 , can channel pruning fit for it ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/yihui-he/channel-pruning/issues/43, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJkBS4EO6VQ609Vcl7lff2eN6vlUD8Inks5swDiAgaJpZM4QHIz1.


Hello from Preact 👋🏻

RMWC.
Hi! This message is a friendly 👋🏻 from Preact team.
I am not sure if you are aware but we maintained a similar wrapper over MDC-web for Preact alone.
With the increasing release speed of mdc-web's major version packages and more requirement of focus in some other areas we are looking to deprecate our fork in favor of anything that matches closely our efforts.
rmwc seems to be very close to what we want. I would personally like to offer help in form of maintenance help instead of a maintaining a whole repo on our own.
We are planning to make this the default for the material template of preact-cli and as a part of it would like to make contributions towards the gaps that we may find for preactX compatibility.
If this works then I would love to extend some help towards maintaining the overall project releases, bugs etc.
Thanks from Me and @developit. 👍

@prateekbh. Yes yes and yes. Ping me on discord or linkedin and maybe we could do a quick chat.

I am dumb and dont know how to discord! 🙈
My code is prateekbh#3043

@prateekbh just saw this, sent you a friend request on Discord

So, What went over the Discord. LoL

🙈 I was quite caught up, slowly coming back to my routine and stuff that got dropped

@prateekbh I was just thinking about reaching back out to you! Lets connectt.


Issues with download

Hi, I'm having issues downloading the software I've repeatedly tried to download and compress the files but to no avail. Am I doing something wrong?
Please help.

/


Enable georeferencer for database connectors

See #12566
This adds support for georeferencing geometry columns from external databases when using our import API.
It's specially interesting when connecting to other PostGIS instances, since now we are importing the geometry columns as a string column. We also need this for our new brand BigQuery connector and it's also useful for the rest of database connectors.
I've tested this locally by running several imports. Should I add proper unit tests? I've taken a look at the connector_runner.rb tests and it seems they just check that the init parameters are correct.
Adding @jgoizueta for CR
cc. @juanignaciosl

Regarding the tests, it'd be nice to add some proper unit tests, but that's not too easy/straightforward, I think the effort would be better employed in adding a connector integration test, checking connector imports, similar to this one for overviews: https://github.com/CartoDB/cartodb/blob/master/spec/connectors/importer_overviews_spec.rb
That would be a good place to check the effect of this PR.
We'd need some connector mockup though, to provides some fixture dataset. I'm not sure how easy that would be...  I leave it to your consideration, @alocar, if it's going to be time-consuming better open a separate ticket to add proper tests for connector imports.

Totally agree. Let me investigate a bit about how to properly test this and the amount of effort required.
Thanks!


Week from March 13-19 2016 is missing when displaying a calendar on Week Mode.

When in Week Mode, the days for March 13-19 week are missing! See screenshots below.

Tested on a Samsung Galaxy J1 (2016) on Android 5.1.1 (Lollipop)

Found these possibly related issues on CalendarView while investigating the root cause:

Android CalendarView Drops Weeks at Random

CalendarView Issues when Used Directly Outside of a DatePicker

I've narrowed the issue to the remove row calculation on CalendarPagerView.resetAndGetWorkingCalendar.
https://github.com/prolificinteractive/material-calendarview/commit/9edc9bf88c1150d3e57f96ee5b1e6b39b4d65134#diff-eb999a88de10aba2edab468c9e0c402bR74

I too had issues until I specified a minimumDate for the calendar, then the issue abstractly went away :+1:  whatever works I guess

Is it a coincidence that DST began for a number of countries on March 13?  Could a missing hour cause date arithmetic to be off?

I cannot recreate this issue. Can you confirm this is still a problem with version 1.2.1?

Yes, this is no longer happening on 1.2.1

FYI, it is March 16, 2018, and we are seeing this issue now on some devices. Using latest 1.4.3. Anything we can do without shipping a whole new app?

It happened to week March 14-20, 2021 too. Does this bug get fixed?


database: add client cert to tls config

I didn't want to have to update all of our services.  Instead, terraform will create the client cert/key and include it in the deployment as an environment variable

We could add it to the struct and let an env var override those values.

Codecov Report
Base: 78.00% // Head: 77.10% // Decreases project coverage by -0.89% :warning:

Coverage data is based on head (886622a) compared to base (0820b00).
Patch coverage: 39.13% of modified lines in pull request are covered.

:exclamation: Current head 886622a differs from pull request most recent head 07dd751. Consider uploading reports for the commit 07dd751 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #252      +/-   ##
==========================================
- Coverage   78.00%   77.10%   -0.90%
==========================================
  Files          29       30       +1
  Lines         973      996      +23
==========================================
+ Hits          759      768       +9
- Misses        166      179      +13
- Partials       48       49       +1

Impacted Files
Coverage Δ

database/mysql.go
31.91% <0.00%> (-1.42%)
:arrow_down:

database/tls.go
47.36% <47.36%> (ø)

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

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

@darwinz Feel free to merge this and update the changelog for a v0.35.0 release.


KYLIN-3586 Fix remaining boxing/unboxing problem

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@eb01b69). Click here to learn what that means.
The diff coverage is 14.28%.

@@            Coverage Diff            @@
##             master     #280   +/-   ##
=========================================
  Coverage          ?   21.28%
  Complexity        ?     4437
=========================================
  Files             ?     1087
  Lines             ?    69983
  Branches          ?    10126
=========================================
  Hits              ?    14896
  Misses            ?    53684
  Partials          ?     1403

Impacted Files
Coverage Δ
Complexity Δ

...in/java/org/apache/kylin/metadata/tuple/Tuple.java
0% <0%> (ø)
0 <0> (?)

...org/apache/kylin/common/debug/BackdoorToggles.java
0% <0%> (ø)
0 <0> (?)

...c/main/java/org/apache/kylin/jdbc/KylinClient.java
67.83% <20%> (ø)
33 <0> (?)

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 eb01b69...4bc2939. Read the comment docs.

Pull Request Test Coverage Report for Build 3734

1 of 7 (14.29%)  changed or added relevant lines in 3 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.01%) to 23.293%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-common/src/main/java/org/apache/kylin/common/debug/BackdoorToggles.java
0
1
0.0%

core-metadata/src/main/java/org/apache/kylin/metadata/tuple/Tuple.java
0
1
0.0%

jdbc/src/main/java/org/apache/kylin/jdbc/KylinClient.java
1
5
20.0%

Files with Coverage Reduction
New Missed Lines
%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
1
78.12%

core-cube/src/main/java/org/apache/kylin/cube/cuboid/TreeCuboidScheduler.java
2
68.46%

Totals

Change from base Build 3732:
0.01%

Covered Lines:
16301

Relevant Lines:
69983

💛  - Coveralls


Using UIImageColors in Swift Package Manager isn't working?

Hi guys: I've tried using this with Swift Package Manager, and it keeps failing. I haven't had any troubles adding any other packages (I use about 10 others). This is the message I see when it fails:
The package dependency graph can not be resolved; unable find any available tag for the following requirements:
https://github.com/jathu/UIImageColors — 2.1.0..<3.0.0
Thoughts?
Alan

I just released 2.2.0, can you try again? https://github.com/jathu/UIImageColors/releases/tag/2.2.0

Yep! That worked! Thanks.

Getting this error


Feature: Indexing fields by latitude/longitude rather than grid indices

A nice to have feature in Parcels would be the option to provide latitude and longitude indices, rather than the grid indices of the model.
For example, if I want to load a small region of a global ocean model in order to speed up the I/O of my simulation, I need to first identify the indices of the grid that line up with the latitude and longitude of said region (which can quite finicky to identify). I then pass these into my FieldSet.from_nemo() (or equivalent) function with the dictionary indices = {'lat' : range(1000,2000), 'lon' : range(400,800)}.
This becomes troublesome when using multiple fields using different grids, and so the grid indices will be different for different regions. It would be nice if I could instead pass a 'bounding box' or region in terms of latitude and longitude, rather than grid indices.
It would also be nice if this could deal with the periodic boundary, in the case where the region overlaps the periodic boundary of the model grid.

Yes, I agree this would be a nice feature. And don't forget to also add it to the documentation/tutorials (see #1511)


bugfix(#21315): Fix for #21315 to automatically set the SystemRoot environment

bugfix(#21315): Fix for #21315 to automatically set the SystemRoot environment
Signed-off-by: David Morris<EMAIL_ADDRESS>
Fixes #21315
Context

When writing unit tests which make use of the gradle runner on a Linux/MacOS it is very hard to know the impact they might have on a Windows user for not including the SystemRoot environment variable and the impact it has on them.  The cause of the error isn't obvious since there are no logs detailing what was missing.
I considered simply checking that the environment variable was there early on and failing with a clear log message, but that then forces every developer to put the same if Windows do X logic across multiple code bases.  This seemed the neater option, working similar to the effective arguments.
I'm unsure on how/where to write an automated test for this or if you even have a Windows based test rig to run them on.  I've manually tested it by building the branch on my Windows dual boot and using that as the gradle implementation with my reproducible example available at https://github.com/codefish1/gradle-windows-bug
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[x] Verify design and implementation
[ ] Verify test coverage and CI build status
[x] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

OK, I've already triggered a build for you.

@bot-gradle cancel

OK, I've already cancelled the pre-tested commit build.

@bot-gradle test and merge

OK, I've already triggered a build for you.

@codefish1 Thank you for the contribution!


juptyer notebook not working / too slow

Hi,
as i run a simple jupyter notebook, it takes a huge amount of time to excetuing or maybe it doesn't excute at all even only one cell. What could happen?
Thanks

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: enabled rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled

Load (avg)

Memory (System)
15.82GB (3.49GB free)

/extPython


test(rpc): parity tests for Filecoin.F3* RPC methods

Summary of changes

Changes introduced in this pull request:

parity tests for Filecoin.F3* RPC methods

| RPC Method                               | Forest | Lotus |
|------------------------------------------|--------|-------|
| Filecoin.F3GetCertificate (2)            | Valid  | Valid |
| Filecoin.F3GetECPowerTable (11)          | Valid  | Valid |
| Filecoin.F3GetF3PowerTable (10)          | Valid  | Valid |
| Filecoin.F3GetLatestCertificate          | Valid  | Valid |
| Filecoin.F3GetManifest                   | Valid  | Valid |
| Filecoin.F3GetOrRenewParticipationTicket | Valid  | Valid |
| Filecoin.F3GetProgress                   | Valid  | Valid |
| Filecoin.F3IsRunning                     | Valid  | Valid |
| Filecoin.F3ListParticipants              | Valid  | Valid |

Reference issue to close (if applicable)

Closes #4936
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Failed to bootstrap F3 in Lotus because of the late participation issue. Need to upgrade Lotus to a release in which InitialPowerTableCid is hard-coded for calibnet to unblock this PR

Unblocked

rock solid, as always!


Removed Environment Variables Command Line Argument Dependency.

Environment configuration dependency on command line argument removed from maestroconfig.

@JosephShobin Okay - after we discussed and looked at other options today, I guess that we can close this PR.
Whether we might want to force configuration in code with a trait for the interface to maestro seems like a separate question.  Since it would be a breaking change, we may revisit this at some point when we have other similar changes.