[Feature Request]: Adding Flask Tutorial under Docs.

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Flask is a lightweight WSGI web application framework written in Python. It is widely used for building web applications and APIs due to its simplicity and flexibility. I propose adding a comprehensive Flask tutorial under the Docs section. This tutorial will cover the following topics to help users get started and effectively use Flask:
1.Introduction to Flask
2.Installing Flask
3.Setting up a new Flask project
4.Flask routing and request handling
5.Using templates with Jinja2
6.Handling forms and user input
7.Working with databases (SQLAlchemy)
8.Flask blueprints and application structure
9.Error handling and debugging
10.Deployment options and best practices
Use Case
This feature would enhance the project by providing a structured guide for using Flask, which is essential for building web applications and APIs. For example, new users unfamiliar with Flask will benefit from step-by-step instructions, enabling them to quickly develop and deploy their applications.
Benefits
Adding a Flask tutorial under Docs will simplify the learning process for new users by providing a clear and detailed guide on building web applications with Flask. This will enhance the project's documentation, making it a valuable resource for both beginners and experienced developers.
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Ajay-Dhangar sir, kindly assign me this issue under GSSOC'24.


POC: Template Operator - Use Kubebuilder Declarative Pattern to improve the Manifest Library for easy Reconciliation

Research into kubebuilder declarative approach to hide reconciliation complexity from a template-operator user.
With this declarative approach ideally, the reconciliation complexity and status (or state) handling should happen implicitly as part of the offered framework. For installation of target resources it could use manifest library as an option.
https://github.com/kubernetes-sigs/kubebuilder-declarative-pattern

@adityabhatia please submit a draft PR in case you are working on this. I would suggest we even consider submitting an alpha plugin into the addons in https://github.com/kubernetes-sigs/kubebuilder-declarative-pattern/tree/master/pkg/patterns/addon, or as an alternative as alpha plugin in https://github.com/kubernetes-sigs/kubebuilder/tree/master/pkg/plugins

@adityabhatia please submit a draft PR in case you are working on this. I would suggest we even consider submitting an alpha plugin into the addons in https://github.com/kubernetes-sigs/kubebuilder-declarative-pattern/tree/master/pkg/patterns/addon, or as an alternative as alpha plugin in https://github.com/kubernetes-sigs/kubebuilder/tree/master/pkg/plugins

Early PRs for declarative pattern implementations:
https://github.com/kyma-project/manifest-operator/pull/67
https://github.com/kyma-project/kyma-operator/pull/123

We should consider also the support for Kustomize as first teams are asking for it.


DPDK rte_mempool_free doesn't work

Or we use it in wrong way.
mbuf unexpectedly change their contents or even mempool return mbufs which are not from it. It leads to segmentation falls in multiple unexpected places due to packet internal fields corruption
Previous issue for this: https://github.com/intel-go/nff-go/issues/285

rte_mempool_free has three functions, two of them are confusing:

rte_mempool_free_memchunks has comment /* Free memory chunks used by a mempool. Objects must be in pool */. It is unclear what does it mean. We tried to return mbufs to mempool - error remains.
rte_memzone_free can return an error. However rte_mempool_free doesn't. SO this error will be dropped.

Cannot reproduce with new DPDK https://github.com/intel-go/nff-go/pull/572


Failing finding debugbar.js

App spins up fine (fixes for #7, et al) but when I render the page, I get this:
10:40:42 web       | Started GET "/_debugbar/assets/script" for ::1 at 2024-02-20 10:40:42 -0500
10:40:42 web       | [Wafris] Redis connection error: File /Users/jathayde/.rbenv/versions/3.3.0/lib/ruby/gems/3.3.0/bundler/gems/debugbar-6e1cb95cb4e1/public/debugbar.js does not exist. Request passed without rules check.
10:40:42 web       |
10:40:42 web       | ActionController::RoutingError (No route matches [GET] "/assets/script"):

Looking in the gem folder, public is empty.

Are you using the gem from git or from Rubygem? How did you add it to your project?
If it's from git, indeed the final client is not committed, it's only added when the .gem file is built. You should be able to build it like this:
cd client
rm -rf dist
npm install
npm run build
cp dist/assets/debugbar-*.js ../public/debugbar.js

I recommend using the latest published version from rubygems.org tho. I'll be publishing many new versions as bug report come in.


Remove duplicate rows（now = timezone.now # L18，L21 & -L27）

try:
    from django.utils import timezone
    now = timezone.now # L18
except ImportError:
    from datetime import datetime
    now = datetime.now # L21

and  now = timezone.now # L27 should be removed

Coverage decreased (-0.005%) to 94.232% when pulling decaabd21859ebe0962b0d6ee3b31369efa9b4ad on missuor:patch-1 into 89bfa0ed6eeefabbad811e7df79d85b03d55f79b on justquick:master.

Coverage decreased (-0.005%) to 94.232% when pulling decaabd21859ebe0962b0d6ee3b31369efa9b4ad on missuor:patch-1 into 89bfa0ed6eeefabbad811e7df79d85b03d55f79b on justquick:master.

Coverage decreased (-0.005%) to 94.232% when pulling decaabd21859ebe0962b0d6ee3b31369efa9b4ad on missuor:patch-1 into 89bfa0ed6eeefabbad811e7df79d85b03d55f79b on justquick:master.


Vouching is delayed. Profiles are not updating.

Describe the Bug
I have vouched 3 hours ago but it isn't impact on my profile. On the telegram group there is a bunch of users reporting the same behaviour. Some of them are waiting from a day ago.
Is it normal? Could be an issue related to the new way of free gas vouching?
To Reproduce

Click on vouch on a profile.
Accept the signature.
Submit vouch.

No impact on the profile.
Expected Behavior
Impact on the vouched profile in a couple of hours.

Can you please check that this is still reproducible? The vouch should be detected immediately now.

@mtsalenc working for me, closing the issue
thanks!


ARROW-15898: [CI] Clean old conda nightlies more thoroughly

The "osx-arm64" architecture was not handled
Some old builds were left behind if the corresponding configuration (e.g. Python 3.6) was obsolete

@github-actions crossbow submit conda-clean

Is there a way to test this short of pushing to master? @kou

Example failed build that tried deleting: https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=21187&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181

Update run (again, no token so no actual delete):
https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=21189&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181

@github-actions crossbow submit conda-clean

I can't confirm that all items in detected item list are valid but it seems that more files than VERSIONS_TO_KEEP = 5 are deleted:
e.g.: linux-64/arrow-cpp...py38_cpu...
https://dev.azure.com/ursacomputing/crossbow/_build/results?buildId=21190&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=d9b15392-e4ce-5e4c-0c8c-b69645229181&l=755
- arrow-nightlies/arrow-cpp/8.0.0.dev194/linux-64/arrow-cpp-8.0.0.dev194-py38h61d1e9c_0_cpu.tar.bz2

https://anaconda.org/arrow-nightlies/arrow-cpp/files

arrow-cpp-8.0.0.dev201-py38h61d1e9c_0_cpu.tar.bz2
arrow-cpp-8.0.0.dev197-py38h61d1e9c_0_cpu.tar.bz2
arrow-cpp-8.0.0.dev194-py38h61d1e9c_0_cpu.tar.bz2
arrow-cpp-8.0.0.dev186-py38h2d0d860_0_cuda.tar.bz2

It seems that dev201, dev197, dev194, dev186 and dev185 are the latest 5 versions:

@kou You're right, I was missing the "features" information (CPU / Cuda). Can you take a look again?

These files are several months old, so yes.


Query string removed from notification URL

Describe the bug
I have a notification URL such as this:
forms://api.my-server.com/changedetection/update?token=123

When a notification is triggered, it seems the token is removed from the URL.
This appears in the debug log:
DEBUG - Loaded JSON URL: jsons://api.my-server.com/changedetection/update?method=POST&format=text&overflow=upstream&rto=4.0&cto=4.0&verify=yes

I need the token to authenticate with my server. Or is there another way I should be doing that?
Version
Exact version in the top right area: 0.45.5
Expected behavior
Should merge query strings instead of removing any

please read https://github.com/caronc/apprise/wiki/Notify_Custom_Form#get-parameter-manipulation
thanks :)

Also worth updating your version, there was some updates to the apprise library included

Thanks!


Route map view controller no longer shows the user's location

This screen should show a blue dot indicating the user's current location.

Also, change the icon that launches this to be the words "Show Map"


Feature/update docker build

Description
Currently the docker build for our circulation manager backend needs some updates. Right now it builds pulling in the code from git within the docker build, it should instead be using the locally available files.
Motivation and Context

To avoid cloding duplicate codebase in every jobs

How Has This Been Tested?

Checklist

[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.

One more comment here, can you update the README file, since we no longer need the repo and version arguments.

I will do once tested.

@aseefahmed I pushed a commit here to not copy everything into the ls_build folder. If you can fix those other issues, then I will test again. I think this is close to ready to merge.


STG 93 changelogs

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Storage.Blobs


IRC setting Pop-up won't disappear, Some buttons overlap others

When trying to access regional controls, the IRC setting pop-up appears right over some of the information that I want to see. Also, some of the "buttons" are in illogical places, or overlap other buttons.

Should be fixed.


Request to release evaluation function

Thanks for your excellent job. I would like to request an evaluation code to measure the performance on different datasets.
Your contribution is greatly appreciated.

Thanks for the interest. The evaluation codes on KITTI360 is released, along with the trainin codes.


Tokio 0.2 support

Tokio is probably close to releasing its version 0.2 and this crate should be ready for it. Maybe it is even possible to do it in a way that one feature turns on support for tokio 0.1, while another support for tokio 0.2.
The implementation needs to be against the alpha releases for now, so it probably should stay in a branch for now, to try it out, but this can be ready for just setting the right dependency and releasing.
Note that supporting async-std is currently impossible, as there's no way to plug arbitrary file descriptors into it right now.

I am currently trying to do this and it compiles but my tests fail with
called Result::unwrap() on an Err value: Custom { kind: Other, error: "no current reactor" }
for
let mut runtime = Runtime::new().unwrap();
...
runtime.block_on(...)

and  'default Tokio reactor already set for execution context
for
let reactor = tokio_net::driver::Reactor::new().unwrap();
let handle = reactor.handle();
let _guard = tokio_net::driver::set_default(&handle);
let mut runtime = Runtime::new().unwrap();

Any idea why this is happening?

I think the first should work, if you're using runtime from the same version as the network primitives (AFAIK currently tokio doesn't yet have a migration path ready, so spawning 0.2 TcpStream or anything else onto tokio 0.1 reactor doesn't work).
The second one can't work, because Runtime also sets a reactor and these two fight each other.
Anyway, it's hard to tell from this little snippet. If you could maybe share the whole code you have, I might be able to help more.

This is my branch, the tests that fail are tokio::repeated and tokio::delayed, and the relevant Tokio stuff is here.
rg tokio Cargo.lock shows that there is only tokio 0.2-alpha.6 (and tokio-timer 0.3.0-alpha.6) in the dependency tree, so AFAICT there shouldn't be any conflicts.

I've discovered the problem. The into_async is the one that fails. The Registration (as is part of Async) could be called from outside the context of the reactor in previous versions of tokio. This is no longer the case ‒ I'm not sure if this is on purpose or by accident. Anyway, the registration.register_with can be moved into the poll_next, just before poll_read_ready (it's fine it'll be called repeatedly).
It seems there are some other problems, but they are not tokio related I'd say.

should the handle be stored inside the Async?
The problem is that into_async_with_handle then would have to take the handle by value, or should it be
pub fn into_async_with_handle(self, handle: &Handle) -> Result<Async, Error> {
    Async::new(self, handle.clone())
}

anyway, those are the errors now:
---- tests::repeated stdout ----
thread 'tests::repeated' panicked at 'assertion failed: `(left == right)`
  left: `29`,
 right: `30`', tests/tokio.rs:37:17

---- tests::delayed stdout ----
thread 'tests::delayed' panicked at 'index out of bounds: the len is 128 but the index is 128', /rustc/c27f7568bc74c418996892028a629eed5a7f5f00/src/libcore/slice/mod.rs:2716:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

I don't think I know enough about Tokio and signal-hook to debug them myself.

Handle can probably be taken by value. It's cheap to clone on the caller side and it's not expected one would create thousands of signal-listening streams.
As for the off-by-one numbers, I suspect it has to do with your change of order of the lines inside poll_next ‒ originally, it first took the signal reference, then incremented the position, now it happens in the other order.

I see there was a progress made after last message here in tokio-0.2 branch.
How far is it though?
I've just decided to use signals.into_async().unwrap().into_future() and found that it is incompatible with Tokio 0.2 apparently.

I'm thinking about actually not finishing/experimenting more with that. Tokio contains its own suppot https://docs.rs/tokio/0.2.13/tokio/signal/unix/fn.signal.html, it is built on top of signal-hook-registry. So there's not much motivation.
Do you have any use case not covered by that?

Didn't try it before, but it probably does. I'm not doing anything fancy.

I think this will eventually get outdated by #39.

I think we can close this one with the merge of #51.

Technically, we got version 0.3 there 😇. But yes, you're right. I'll keep it open just until I do the promised release.

OK, it's been released a minute ago :-). Thanks to everyone involved.


i have a question

严重性	代码	说明	项目	文件	行	禁止显示状态
错误	KRB1001	Package references have not been pinned. Run './build.cmd /t:Pin'.
Also, you can run './build.cmd /t:Restore' which will pin and restore packages. 'build.cmd' can be found in 'D:\Research\DependencyInjection'.	DI.Abstractions	D:\Research\DependencyInjection\Directory.Build.targets	12
when i'm going to build solution,this mistake is coming?How can i resolve it?

Run build.cmd first

when i run build.cmd, it doesn't work.
Then i run build.sh through gitbash in my PC, it seems to be a success,but a waring is coming.
https://github.com/lukangkang/surpass/blob/master/jietu.png
Then i tried to follow the cue and add the path to my system PATH,but it's still useless.

What happens when you run build.cmd

The window flashed past.
When I run as an administrator, the result is the same
@ECHO OFF PowerShell -NoProfile -NoLogo -ExecutionPolicy unrestricted -Command "[System.Threading.Thread]::CurrentThread.CurrentCulture = ''; [System.Threading.Thread]::CurrentThread.CurrentUICulture = '';& '%~dp0build.ps1' %*; exit $LASTEXITCODE"
this is the code in build.cmd,do I need to change anything?

Run it from the command line...

Open a command prompt window
Navigate to the path where you cloned the GitHub repository
Run "build"

If you get errors, please cop & paste the exact messages you get

Hi, I have the similar problem to build any of .net core projects (DI, Configuration, Hosting etc).
The suggest commands build.cmd /t:Pin, build.cmd /t:Restore and build.cmd all not work, same error like below.
PS C:\Codes\Configuration> .\build.cmd
Downloading KoreBuild 2.1.0-preview1-15493
Using KoreBuild 2.1.0-preview1-15493
WARNING: dotnet found on the system PATH is 'C:\Program Files\dotnet\dotnet.exe' but KoreBuild will use
'C:\Users\heku\.dotnet\x64\dotnet.exe'.
WARNING: Adding 'C:\Users\heku\.dotnet\x64' to system PATH permanently may be required for applications like Visual
Studio or VS Code to work correctly.
Adding C:\Users\heku\.dotnet\x64 to PATH
.NET Core runtime 2.0.0 is already installed. Skipping installation.
dotnet-install: Downloading link: https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.0-preview1-007042/dotnet-sdk-2.1.0-preview1-007042-win-x64.zip
dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/2.1.0-preview1-007042/dotnet-sdk-2.1.0-preview1-007042-win-x64.zip
dotnet-install: Adding to current process PATH: "C:\Users\heku\.dotnet\x64\". Note: This change will not be visible if PowerShell was run as a child process.
dotnet-install: Installation finished
>>> dotnet.exe msbuild @C:\Codes\Configuration\artifacts\msbuild\msbuild.rsp
Invoke-RepositoryBuild : Program 'dotnet.exe' failed to run: The specified executable is not a valid application for th
is OS platform.At C:\Users\heku\.dotnet\buildtools\korebuild\2.1.0-preview1-15493\scripts\common.psm1:7 char:5
+     & $cmd @args
+     ~~~~~~~~~~~~.
At C:\Codes\Configuration\build.ps1:173 char:5
+     Invoke-RepositoryBuild $Path @MSBuildArgs
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [Invoke-RepositoryBuild], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed,Invoke-RepositoryBuild

It seems it downloads a x64 version dotnet CLI to my x86 OS, is this a bug? Any suggestion?
Here is my environment info.
C:\Users\heku>dotnet --info
.NET Command Line Tools (2.0.0)

Product Information:
 Version:            2.0.0
 Commit SHA-1 hash:  cdcd1928c9

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.15063
 OS Platform: Windows
 RID:         win10-x86
 Base Path:   C:\Program Files\dotnet\sdk\2.0.0\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

@heku use a 64 bit OS if you want to build ASP.NET Core repositories.

@davidfowl Thank you, may I know if this is by design?

Everyone that builds these repositories use a 64bit OS, that includes us an most of the OSS contributors. We wouldn't optimize for both unless there was a large number of people on 32 bit OSes trying to build these repos (and there isn't).

@davidfowl Got it, thank you for help.

@heku try setting the KOREBUILD_DOTNET_ARCH environment variable to x86 before running build.cmd.
If you're using Command Prompt
set KOREBUILD_DOTNET_ARCH=x86

If you're using PowerShell
$env:KOREBUILD_DOTNET_ARCH='x86'

cref https://github.com/aspnet/BuildTools/blob/08465c77b2a0a265163bafa4013434dd998e0e1e/files/KoreBuild/scripts/KoreBuild.psm1#L465-L470

@heku I stand corrected.

@davidfowl Never mind, I always appreciate your help.
@natemcmaster Awesome! Let me have a try.

Closing because this appears to be resolved.

@natemcmaster Would it be possible to expose a 32-bit version of build.cmd on all repos? Though it may hit only a small number of people, we should make it as easy as possible to have anyone contribute.

IMO it would be better to just detect when a machine is 32-bit only. I think this can be determined from env variables like PROCESSOR_ARCHITECTURE and PROCESSOR_ARCHITEW6432


Abort request

Hello. I tried call pjax from backbone as         $.pjax({url: '/search?' ,container: '#content', timeout: 600000}), ajax request was cancelled, error in jquery on the line:
f.send(a.hasContent && a.data || null)
Please help.

if set parameter async: false the problem disappears.
but I think it is not the best solution

You're right, you shouldn't use asnyc: false. But I don't know where your problem might lie. It's something else in the application that's canceling the request. Without any extra info or steps to reproduce, I'm afraid I can't help you.

Sorry, there is not enough information given here for us to be able to provide any advice. It sounds like this might be a problem with usage of this project, and not a bug in our code. If you do think this is a bug, please reopen this and provide more information, such as steps to reproduce. Thank you!


"Duration" filter on channel pages is grayed out, if the content type filter is something else than "Any".

"Duration" filter on channel page is grayed out, if the content type filter is something else than "Any".
Seems to only happen in Odysee.com?
Locally it works like expected. (Can set duration limit for "Any", "Audio" and "Video", and it's grayed out for others)

--close--
e014fe0b


Provide a pkg-config file or similar to help with static linking

It seems that - depending on compiler and platform - several additional linker flags have to be passed when linking libxsmm statically, see for example:

https://github.com/spack/spack/pull/9308/commits/5b0042050a5bed02643361c1ae27708b69b0d01d
https://github.com/spack/spack/pull/9308#issuecomment-430815341

Other projects provide either a .pc pkg-config (preferred) or libtool .la files to help with that but I guess any other method where we could easily retrieve the required flags would help.

Nice, thank you very much! Do you have a rough ETA for v1.10?

Nice, thank you very much! Do you have a rough ETA for v1.10?

This week at best and by end of this month in any case.

@hfp awesome, thanks!

the current 2fb520d295f2cab5646f69f0e90e477037b71a12 .pc-generation seems to have a problem:
Name: libxsmm
Description: Matrix operations and deep learning primitives
URL: https://github.com/hfp/libxsmm
Version: 1.9.0

prefix=/scratch/tiziano/work/libxsmm
includedir=${prefix}/include
libdir=${prefix}/lib

Cflags: -I${includedir}
Libs: -L${libdir} -lxsmm
Libs.private: -lpthread -lrt
 -ldl -lm -lc

... there's a newline before the -ldl ..., making pkg-config ignore those libraries:
$ PKG_CONFIG_PATH="$PWD/lib" pkg-config --libs --static libxsmm
-L/scratch/tiziano/work/libxsmm/lib -lxsmm -lpthread -lrt

The ETA is by the end of this week at best and by the end of this month in any case.
From: Tiziano Müller<EMAIL_ADDRESS>Sent: Monday, October 22, 2018 10:14 AM
To: hfp/libxsmm<EMAIL_ADDRESS>Cc: Pabst, Hans<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [hfp/libxsmm] Provide a pkg-config file or similar to help with static linking (#269)
Nice, thank you very much! Do you have a rough ETA for v1.10?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/hfp/libxsmm/issues/269#issuecomment-431764983, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGb3tQLh_MDRxLS3t6IbWlURCyYREOCPks5unX5DgaJpZM4XrWqN.
Intel Semiconductor AG
Registered No. 020.30.913.786-7
Registered Office: Badenerstrasse 549, 8048 Zurich, Switzerland

Thanks for testing the pc-file(s). The issue is now fixed.


Package maintenance

Landed in https://github.com/tshemsedinov/wasm-import/commit/a51381d6e24638e16d83683c2390166ad8333d8a, https://github.com/tshemsedinov/wasm-import/commit/a0eb8cbbcfb9eec24e878a0991a581851e6f4cb8, and https://github.com/tshemsedinov/wasm-import/commit/bfa21f07265655c14e6a3679e0399c53dbc8b9fb


Match Dependency Versions

Summary
Slim the wepback entry point size by matching the peer dependency verisons. What is happening is hoist will attempt to flatten node_modules to the root level but isn't clever enough to flatten dependencies with mismatching minimum versions. This bloated the console output on install and caused our webpack entry point size to be ~6.81MiBs. Once these matched, the entry point size was ~3.07MiB.
Terminal Output

lerna bootstrap --hoist
><EMAIL_ADDRESS>bootstrap:hoist /Users/er047227/terra-framework
> lerna bootstrap --hoist

lerna info version 2.11.0
lerna info versioning independent
lerna info Bootstrapping 26 packages
lerna info lifecycle preinstall
lerna WARN EHOIST_ROOT_VERSION The repository root depends on<EMAIL_ADDRESS>which differs from the more common<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-embedded-content-consumer" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-dialog-modal" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-modal-manager" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-navigation-side-menu" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-slide-panel-manager" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-aggregator" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-utility" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-layout" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-utility" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-collapsible-menu-view" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-dialog-modal" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-form-validation" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-hookshot" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-popup" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-modal-manager" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-notification-dialog" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-slide-panel-manager" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-aggregator" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-layout" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-popup" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-utility" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-modal-manager" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-slide-panel-manager" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-collapsible-menu-view" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-embedded-content-consumer" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-slide-group" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-time-input" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-dialog-modal" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-notification-dialog" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-form-validation" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-time-input" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-aggregator" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-collapsible-menu-view" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-infinite-list" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-popup" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-layout" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-utility" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-infinite-list" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-collapsible-menu-view" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-notification-dialog" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-layout" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-application-name" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-collapsible-menu-view" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-collapsible-menu-view" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-theme-provider" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-dialog-modal" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-modal-manager" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna WARN EHOIST_PKG_VERSION "terra-infinite-list" package depends on<EMAIL_ADDRESS>which differs from the hoisted<EMAIL_ADDRESS>lerna info Installing external dependencies
lerna info hoist Installing hoisted dependencies into root
lerna info hoist Pruning hoisted dependencies
lerna info hoist Finished pruning hoisted dependencies
lerna info hoist Finished installing in root
lerna info Symlinking packages and binaries
lerna info lifecycle postinstall
lerna info lifecycle prepublish
lerna info lifecycle prepare
lerna success Bootstrapped 26 packages
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

added 2507 packages in 418.889s

@bjankord Agreed, this will be impossible to maintain otherwise

@bjankord @tbiethman  I think this makes sense. I've made the changes to simplify the version.


Advance locations gem to 0.4.0.

After this is merged Orangelight's base URL for stackmap routing needs to be pointed at /locations/map. Also need to point the main catalog at this new base URL. This allows us to kill the old shim that has a dependency on Primo's API.

@tampakis - can you take care of this later today?


文字识别问题反馈

Microsoft PowerToys version
0.74.1
Installation method
Microsoft Store
Running as admin
None
Area(s) with issue?
TextExtractor
Steps to reproduce
文字识别效果不够准确。括号“（）”一直被识别为“0”。望优化，ᠪᠠᠨᡳᡥᠠ（巴尼哈/谢谢）
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

This issue is with the underlying OCR Engine and fixing it is beyond the scope of this project.

此問題與底層 OCR 引擎有關，修復此問題超出了本項目的範圍。

在我的使用體驗中，主要問題是文字識別的準確率。這樣的問題，該如何反饋呢？

[translated] In my experience, the main problem is the accuracy of text recognition. How to respond to such a problem?

There are a few things you can do to make the text recognition better:

make sure you are using the OCR language to match the text language
light background with dark text
make the text or image with text larger

Supporting other OCR engines (like tesseract) is not currently supported but might get added in the future.


Kill off advanced search

This is only used by whitehall.  whitehall#5122 switches to the normal
search endpoint, so advanced search can be removed.
Before this commit is merged, the endpoint should be removed from
gds-api-adapters.

Trello card

The /search/advanced finder is unrelated to the advanced search endpoint - we just have a lot of things called "advanced search" 😢

Oh god. Confusing!!!


Option to Limit Minimum Brightness on Slider to 1%

Is your feature request related to a problem? Please describe.
I have a lot of situations where I want to turn the light on at or down to the lowest brightness. This is very difficult to achieve on any device without turning the light off since the slider goes to 0%.
Describe the solution you'd like
Create an option to limit the minimum brightness for the slider to 1%. Since I already have the option to make taping the card to toggle the light ON/OFF, I don't see the need to turn off the light with the slider.
Describe alternatives you've considered
I haven't seen this issue discussed anywhere and I'm not comfortable editing the code myself. I could maybe use Trigger IDs to turn the light back on to 1% when it was turned off by the Mushroom card and make tapping the card call a service to toggle it via an automation. But, I'm not sure this would work very well, it would cause the light to flicker off then on, and is overall very inelegant.
Double tapping the card to set the brightness to 1% was also something I briefly thought about, but requiring additional know-how to use lights often doesn't pass the wife approval test and may result in unwanted behavior if not done correctly/quickly enough.
Additional context
This is already how the entity pop-up in HA behaves. The slider only changes the brightness and you have to click the ON/OFF button to change its state. If there is a limitation to why this can't be replicated with Mushroom cards or would be too difficult/time consuming then I understand, but this is the final piece that is keeping me from fully implementing Mushroom as my go-to for light dashboards. FWIW, the Slider Button Card is also missing this functionality.

It would be awesome if this could be implemented. Especially during night and feeding little kids when you want to turn stuff on only to 1% fast.
Thanks.


Strange borrow checker error

This code produces such error:
error[E0382]: use of moved value: `*self`
   --> src/stream.rs:331:26
    |
326 |     #[no_panic]
    |     ----------- value moved here
...
331 |                     vec![self.curr_byte_unchecked(), c],
    |                          ^^^^ value used here after move
    |
    = note: move occurs because `self` has type `&mut stream::Stream<'a>`, which does not implement the `Copy` trait

You can test it in this branch.
Probably the same issue as in the https://github.com/dtolnay/no-panic/issues/1

Thanks! I released no-panic 0.1.8 with a fix. This was a bug related to self being used inside of a macro invocation like vec!.


(3.0.80) after closing the error dialg, login button goes inactive

I would expect less-than-desirable behavior from Jadeite after an unexpected error. The solution in this case is to close the login window and reopen Jadeite.
If that is not acceptable, I can wrap the login code in an error handler which fixes the conditions so the button will re-enable before showing the error dialog. However, that isn't a very good solution either.
Reassigning to @dalehenrich for comment and removing November 19 label.

I think that the code should always work correctly even in the presence of errors .... agree that it is not a high priority ... but for completeness this should be fixed ...

I've reset the session on login errors in 3.0.82. Manual testing shows that the login button re-enables after an error.

It sometimes take a couple of seconds to reenable, but it seems pretty reliable that it eventually does.


[Simple-FFT] Add new port

closes #11928

License added, thanks to the author of the library

/azp run

LGTM now. Thanks for this PR @Pospelove

/azp run


Synchronization of audio and video dimensions before calculating the contrastive loss

Hi,
Could you please clarify how synchronization happens in terms of dimensionality between the video and audio representations? Specifically, I’m curious about how this works during training with the contrastive loss and during zero-shot evaluation.
From what I observed, the feature extractors output dimensions of (1,14,8,768) and (1,14,6,768), and the projection layer seems to operate on the 768-dimension, not the time dimension. I couldn’t fully understand how this is handled in the code.
Thank you!

Hi,
During contrastive pre-training (stage I), the time dimension is avg pooled (similar for audio): https://github.com/v-iashin/Synchformer/blob/814f3ff46d6cf504d09544feeeab990b0c50aaa3/configs/segment_avclip.yaml#L40
So you end up with features (1, 14, 768) for audio and RGB.
At this stage, the input clips are in-sync and you could take a window of consecutive features, e.g. 8, and compute dot product between all windows of 8 in another modality. This is shown on the gifs in README.
If the highest dot product response of two windows starts at the same time stamp, the prediction is correct (in zero-shot setting). Notice, that the granularity is 1 feature = segment size = 0.64 seconds.

During stage II, we remove the agg_time_module to keep the time dimensions (8 for rgb and 6 for audio). Then we could flatten the segment dimension to features with finer time granularity: 1, 14*8, 768 and 1, 14*6, 768. These will be used to train the synchronization module as a classified onto (21, for 0.2s-grid as in paper, or more classes if you wish higher sync precision).

If I understand correctly, in the example.py file, the classification model is used, so it flattens the segment dimension instead of averaging over time, right?

yes, the model is defined in the cfg.model in the config of the experiment that you are providing. see the agg_time_module in cfg-24-01-04T16-39-21.yaml.

are the weights used to generate features at the end of the first training phase kept constant during the second phase of training?

yes, see
https://github.com/v-iashin/Synchformer/blob/814f3ff46d6cf504d09544feeeab990b0c50aaa3/configs/sync.yaml#L7
and
https://github.com/v-iashin/Synchformer/blob/814f3ff46d6cf504d09544feeeab990b0c50aaa3/configs/sync.yaml#L19

Thank you!


Invalid SSRC

rtsp-server very usefull but i've got a problem with a rtsp server ( IbaRtsp) the session ID after the setup got a lazy syntax :
SETUP rtsp://<IP_ADDRESS>:554/cam2/live RTSP/1.0
CSeq: 3
Transport: RTP/AVP;unicast;client_port=10100-10101;mode=play
User-Agent: gortsplib

RTSP/1.0 200 OK
CSeq: 3
Server: ibaRTSPServer/5.1.4
Session: <IP_ADDRESS>+7789+937239728
Transport: RTP/AVP/UDP;unicast;client_port=10100-10101;server_port=50024-50025;ssrc=937239728

thank for your incredible job..

Hello, the SSRC is 4 bytes long - that server you posted sent a SSRC that is 5 bytes long, therefore it can't be decoded, even if i wanted to. Please contact the authors of that RTSP server and tell them to fix the issue.

Maybe they encoded the SSRC as a decimal int; it must be encoded as a hex-encoded byte array.

yes i see this yesterday they send SSRC in dec..


Counting files as folders leads to misleading search description if only an empty folder is read.

Images to demonstrate listdupes.py interpreting folder as file.
Originally posted by @geblerj in https://github.com/Chris-Dobbins/listdupes/issues/21#issuecomment-1225091347

I've been letting some parts of the app consider folders as files because it's accurate enough in one sense, but this particular example gives the user a really misleading impression. I'm gonna fix this issue and depending on what the fix is like I might need to take look at the whole issue of counting folders as files.


Update the NIST ELR mappings to use the correct spec for the *_ELR types

User Story
As a sender of NIST ELR HL7 messages, I would like the ELR specific datatypes to get translated
Description/Use Case
Currently, when we read message into the NIST ELR Java class, the mappings do not work as they need to reference the *_ELR types
Risks/Impacts/Considerations
Dev Notes
In XPN_ELR/HumanName, the mapping is currently
family:
  type: STRING
  valueOf: XPN.1.1
  expressionType: HL7Spec

when it needs to be
family:
  type: STRING
  valueOf: XPN_ELR.1.1
  expressionType: HL7Spec

Acceptance Criteria

[ ] All of the ELR datatypes are updated to reference the correct spec
[ ] HL7Reader.kt updated (see comment referencing ticket)

Hey team! Please add your planning poker estimate with Zenhub @adegolier @arnejduranovic @brick-green @jack-h-wang @jalbinson @JFisk42 @mkalish @thetaurean

Please add your planning poker estimate with Zenhub @david-navapbc

As part of this work we should probably update the Java class to split CWE_ELR_OBX5 from CWE_ELR so the mappings will match the documentation

NIST ELR mappings are no longer needed and shall be merged into the "Catchall" mappings


ARGOS and GlyGen DB Updates: Details Page/Card specific view updates

[ ] On the Dataset Detail page, there should be an option to show the full description about the dataset and not just the first sentence (full usability domain)

I am displaying all lines now (making this optional can be done in the future).

complete


SPARK-5888. [MLLIB]. Add OneHotEncoder as a Transformer

This patch adds a one hot encoder for categorical features.  Planning to add documentation and another test after getting feedback on the approach.
A couple choices made here:

There's an includeFirst option which, if false, creates numCategories - 1 columns and, if true, creates numCategories columns.  The default is true, which is the behavior in scikit-learn.
The user is expected to pass a Seq of category names when instantiating a OneHotEncoder.  These can be easily gotten from a StringIndexer.  The names are used for the output column names, which take the form colName_categoryName.

Test build #30206 has started for   PR 5500 at commit 04590bc.

Test build #30206 has finished for   PR 5500 at commit 04590bc.

This patch passes all tests.

This patch merges cleanly.

This patch adds the following public classes (experimental):

class OneHotEncoder(labelNames: Seq[String], includeFirst: Boolean = true) extends Transformer

This patch does not change any dependencies.

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

@sryza Thanks for adding OneHotEncoder to spark.ml. One thing I want to discuss is the expected input of OneHotEncoder. There are two use cases:

input a string column and output a vector column with binary values
input a column with category indices and output a vector column with binary values

The input to 2) would be the output from StringIndexer we recently merged. I would call 1) OneHotEncoder, which is a UnaryTransformer, and 2) StringVectorizer, which is a combination of StringIndexer and OneHotEncoder. If both of us agree on the semantics, we can implement 1) as OneHotEncoder in this PR and add StringVectorizer in another PR. Does it sound good to you?

@mengxr that makes sense to me, but did you mean to switch 1 and 2?  I.e. in this PR we should implement OneHotEncoder, which takes an input column with category indices and outputs a vector column, and in a later PR we can implement StringVectorizer which chains StringIndexer with OneHotEncoder.

Updated the patch conform to the approach described above.

Test build #30436 has started for   PR 5500 at commit 64da101.

Test build #30436 has finished for   PR 5500 at commit 64da101.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

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

Test build #30725 has started for   PR 5500 at commit 7e53579.

Test build #30725 has finished for   PR 5500 at commit 7e53579.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

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

Test build #31010 has started for   PR 5500 at commit 7e53579.

Hey @mengxr this should be ready for review again.

@sryza I think we can add label names later. For this PR, if the input column carries a nominal attribute with values, we can use it for names. Otherwise, we put no names in the output column.

@sryza Could you address the comments? If you are busy, I can send you an update.

Merged build triggered.

Merged build started.

Test build #31803 has started for   PR 5500 at commit f383250.

Test build #31803 timed out     for PR 5500 at commit f383250     after a configured wait of 150m.

Merged build finished. Test FAILed.

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

test this please

Merged build triggered.

Merged build started.

Test build #31826 has started for   PR 5500 at commit f383250.

Test build #31826 has finished for   PR 5500 at commit f383250.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

test this please

Merged build triggered.

Merged build started.

Test build #31889 has started for   PR 5500 at commit f383250.

Test build #31889 has finished for   PR 5500 at commit f383250.

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

Merged build finished. Test PASSed.

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

LGTM. Merged into master and branch-1.4. Thanks!


storyshots bug in react with typescript

Issue details
When running storyshots with jest I get this error:
> jest

 FAIL  src/__tests__/storyshots.test.tsx
  ● Test suite failed to run

    Invariant Violation: Target container is not a DOM element.

      at invariant (node_modules/fbjs/lib/invariant.js:42:15)
      at renderSubtreeIntoContainer (node_modules/react-dom/cjs/react-dom.development.js:15180:34)
      at Object.render (node_modules/react-dom/cjs/react-dom.development.js:15290:12)
      at renderException (node_modules/@storybook/react/dist/client/preview/render.js:66:22)
      at renderPreview (node_modules/@storybook/react/dist/client/preview/render.js:140:12)
      at renderUI (node_modules/@storybook/react/dist/client/preview/index.js:89:26)
      at Object.dispatch (node_modules/redux/lib/createStore.js:186:7)
      at ConfigApi._renderError (node_modules/@storybook/react/dist/client/preview/config_api.js:57:24)
      at render (node_modules/@storybook/react/dist/client/preview/config_api.js:76:19)
      at ConfigApi.configure (node_modules/@storybook/react/dist/client/preview/config_api.js:91:9)
      at evalmachine.<anonymous>:5:22
      at runWithRequireContext (node_modules/@storybook/addon-storyshots/dist/require_context.js:102:3)
      at Object.testStorySnapshots [as default] (node_modules/@storybook/addon-storyshots/dist/index.js:105:35)
      at Object.<anonymous> (src/__tests__/storyshots.test.tsx:4:27)

I've been able to replicate it in the following repo:
https://bitbucket.org/diegolacarta/storyshots-bug/src
After a bit of debugging I saw the error happens here:
<EMAIL_ADDRESS>    _reactDom2.default.unmountComponentAtNode(rootEl);

Any ideas?
Thanks

I'm having the same issue. It looks like its related to the preview functionality for story panels. Is that new? I couldn't find documentation of it.
Since I was already mocking out react-dom for other reasons, I was able to fix the tests by using:
jest.mock("react-dom", () => {
    return {
        render: () => null,
        unmountComponentAtNode: () => null,
        findDOMNode: () => null,
    };
});

Thanx for this, I was getting the same thing :)

thanks for the workaround.
To clarify, this only works if i put it before the initStoryshots(), but breaks all my other normal jest tests if i put it in setupTests.ts.
I guess we need to make sure the snapshot tests don't rely on react-dom for now. How would we go about fixing this for real so we don't need a workaround?

stil a problem

Please reopen this issue, it's still showing up.  The workaround ahead works, but it should not be necessary.

I agree. Plus until its fixed in the core, addons or future updates might cause changes that break the work-around.
I wish I had some insight into what's going on with the preview/main stuff, but I haven't seen documentation for that (from a dev perspective) or anything about the channels module that all addons seem to use. Is this all private core functionality, that none of us should worry about?


Clean up squbs builds

Reduce memory of squbs builds
Reduce time of squbs builds
Reduce excess logging so the logs will fit into 10,000 lines provided by the build console.

Both PR and master builds are now stable.


Documentation of MAPF algorithms used here

Feature request
I would like to read more documentation about MAPF algorithms implemented/WIP/to-be-implemented in the Open-RMF.
Description
At the moment I could not find any documentation besides the code in this repository. Will these be Rust-only implementations, or will it be possible to implement algorithms in C/C++/Python, for example?

Hi @mxgrey,
Can you please provide flow diagram/architecture of this algorithm for understanding its core. It would be better if you can provide reference of related research paper.

Hi guys, I believe the implementation in this codebase is referenced from: https://arxiv.org/abs/1901.05506

A few points of clarification:

This is a planning framework rather than an implementation of a single algorithm.
There are several single-robot planning algorithms that are being provided, including A*, Dijkstra (forward and backward), and SIPP (Safe Interval Path Planning).
The only multi-agent planning algorithm we have right now is Continuous-time Conflict Based Search, but we will add more over time.
It is possible to write custom algorithms or custom domains downstream (in your own projects/libraries) and use them with this framework, exactly the same as any algorithms that we provide out of the box from this repo.

Will these be Rust-only implementations

I will be implementing all the algorithms in this repo using Rust. Since downstream projects can also implement algorithms for this framework, those projects are welcome to incorporate other languages into their algorithms using bindings if it suits them.
It's likely that I will create downstream packages to provide language bindings so that out-of-the-box planners that we implement with this library can be used in other languages, like C++ and Python.

@mxgrey Thank you for the clarification and your answers. I don't know Rust (yet?), but the C++/Python bindings will be helpful for sure in the future.


[GLUTEN-6887][VL] Daily Update Velox Version (2024_09_23)

Upstream Velox's New Commits:
4e45bc51f by Pedro Eugenio Rocha Pedreira, Fix date_diff() bug across time zone boundaries (#11053)
00e65bc63 by Ge Gao, Change unicode escaping in JSON (#10887)
1e736ba89 by yingsu00, Fix fmt V11 build errors (#10904)
c61a3532d by Marcus D. Hanwell, CMake: Only set the variable if it has not been defined (#11040)
6d1fbf057 by Christian Zentgraf, Upgrade FBOS dependencies to 2<IP_ADDRESS> (#11018)
8cd2d1ae6 by Daniel Hunte, Ongoing clean up of DateTimeStampFunctionsTest.cpp (#11050)
919106c0e by Daniel Hunte, Ongoing clean up of DateTimeStampFunctionsTest.cpp (#11047)
746370614 by xiaodou, Allow pushdown of dynamic filters through HashAggregation (#10988)
023be97ce by NEUpanning, Refactor TimestampConversion to return velox::Expected (#10997)
8c2fa20b0 by Wei He, Fix internal build of velox_expression_fuzzer_test (#11044)
9851a4e26 by Xiaoxuan Meng, Avoid the deadlock when failed to create root memory pool (#11042)
19d184e6d by Zac Wen, Extend filesystem APIs (#10504)
ba772c9f0 by Chengcheng Jin, Fix AggregateSpillBenchmarkBase not set HashBitRange (#11037)
15b88d43b by Jialiang Tan, Remove transfer capacity logic in MockSharedArbitratorTest (#11045)
ad745b0f4 by Kevin Wilfong, Allow Custom Types to provide custom implementations of compare and hash functions. (#11021)
7adc39ce8 by zhli1142015, Fix channel not found in scan spec when the row_index column exists (#10854)
d6cde1386 by David Tolnay, More semicolon enforcement on velox macros calls (#11041)
f9d2ba49d by Kevin Wilfong, Clean up some dead code from ExtremeValueFunctionTimestampWithTimezone (#11020)
48c662813 by Deepak Majeti, Fix CI adapters test (#11038)
243f9e5f2 by yingsu00, Refactor Driver::runInternal (#10906)
5127cfe14 by Heidi Han, Cast timestamp to json (#11013)
fad77502a by Jimmy Lu, Expose ArrayVectorBase::hasOverlappingRanges as static method to be used in different vector implementation (
#11031)

@GlutenPerfBot benchmark


[nrf fromtree] Hci iso data packets fragmentation fix

PR contains four commits:
1st commit fixes Zephyr LL controller to pass bsim tests after the following changes in Host
2nd commit fixes calculations of HCI ISO Data packet length
3rd commit fixes timestamp value for SDUs fragmented to several HCI ISO Data packets
4th commit fixes KConfig descriptions of BT_ISO_TX_MTU and BT_ISO_RX_MTU

change the order of commits, controller commit before host commits

thank you, I fixed the order of commits. Now the 1st commit in the PR fixes LL Controller


Signature Does not Validate as a Signature in other Open PGP products

I'm creating a signature of data as follows, based on the examples given:
/**
 * signData - Generates a GPG signature for a given Uint8Array
 * @param data - A String or Uint8Array to be signed
 * @param privkey - An armored version of the privateKey
 * @param passphrase - The passphrase to acccess the privateKey
 * @returns Promise - Resolve - The signature
 *                    Reject - An error object with the reason for the failure.
 */
module.exports.signData = function(data, privKey, passphrase){
    "use strict";
    var deferred = q.defer();

    getKey(privKey, passphrase).then(function(key){
        var params = {
            msg:        data,
            sign_with:  key
        };

        kbpgp.box (params, function(err, result_string, result_buffer) {
            if(err)
                deferred.reject(err);
            else
                deferred.resolve(result_string);
        });
    }, function(error){
        deferred.reject(error);
    });

    return deferred.promise;
}

function getKey(privKey, passphrase){
    "use strict";
    var deferred = q.defer();
    kbpgp.KeyManager.import_from_armored_pgp({
        armored: privKey
    }, function(error, key) {
        if(error)
            deferred.reject(error);
        else {
            if (key.is_pgp_locked()) {
                key.unlock_pgp({
                    passphrase: passphrase
                }, function(err) {
                    if(err)
                        deferred.reject(err)
                    else
                        deferred.resolve(key);
                });
            } else
                deferred.resolve(key);
        }
    });
    return deferred.promise;
}

This generates a signature like the following:
-----BEGIN PGP MESSAGE-----
Version: Keybase OpenPGP v2.0.72
Comment: https://keybase.io/crypto

yMUAAnicjVUJbJRFGF2Oov5FWkANoMiPglLBMvfRaBTKJRQUJS0omM5ZF+wW/t2G
I4jGcJUCWkQ8YjBRvKrVRGMkqUYhKoYqYAUvQAipEgUTFYJiEZxiNJFEafJn/2R3
581733tv5v2Lu6WiLin2ysoV+1OVXVo+aKlNzSjfMGyMy5okPTeXrsmUxKULtUvi
KenMbJWNc4lKZ9KZqjhxc2uy6VxNsrA4KlPa3fvvP0a3Jumq9Dmro3KXZM9iwmIY
jVE5VxKPS9IjYgziibWZGAHIYyhKoAxPPBwAEI1KzD3pnDO52sRlS2JVbRmJszW1
iXFRaU313JqMy+TCD6Ymk0vSOpo8ht5RW10SxRhDQRTTygCAmESMCga5ct5byZCW
sQDi71UjdTqjkoXXn0UfeZsyc1SVyxbrRSiKPVVEI2cNh8pKEeAM1xxaYTF3XpqY
g39g/uJ1DgAADCGLiHHOYkCAAQJToq30SFnCQAwZFuQ8VKoWRTHxgT8KGMIqaKxB
HjvCtHBUKc+NOgfoXDJnIbDHiECgFZSeCQocJIIZ46k1GoWBQAjx/1OJ4g4VzhuM
OOOKaq8UC5iIUosJ0lrESP4XieiOCaNgMIcAjSgDylEmAWaAUAAwQNIpLaT1infI
5Ex31iRsAiHPRZgIZUpRZLRFhlniILLQoeCWhEH7ec3CgGnsbNAVJsO8R8gbAgk3
Wobl2nsvlQxOdto0iML2UCiqJJFYIMMJoRwwSZxUmkJgsOQM+06YR4VE0mgAjRKB
B6OWe8E8EDJ8eg8N80YALDtlIvMOakqlM5AbrqB1BIiOYEnolVU6vLC2QJ3HzOBi
sJNJxomzJAQ7mOgV1oFbR+qJc0RzokjoHA8sQ2U6SoQNJCDUyVrMGFakszY7Fbhp
ZhWVHAAPEKAsDIBKFZgiT6UHWhgcOh7iHXYJ+gDHGkKvQ8qkP6/9RiETaDnitQpV
DzniVCvmBDfGQs6CHMqhB6F8HEBMKeJCQRfUQ0KIpp2OhaAe2aBDaWIAEZooSLxC
LmBJyaAjkIUSCC2VU2FvBFDoqhfaOQk056QTcQEyOGyBt6HyIToO2uCOBUZhGb4E
HnrGSHALhBFaL7Hy2EsHBECIOsR5p2IUjkCnMIfAQssRQ1yz0BIjtAkVDMeKCGee
AQxiwbkGwocT02obREDvBYH/G6+tW2Z2T3WJUj3yunbcSanoosK/b6r2kwWnZZI/
qblu+icPTlkc5Z/YemZ4bSGfNO/Ko5t2Vpe3RBuHtg9vi3579qfTyy4dV3/Xtovy
Z/ce/Pj8tz9rGXd1nyG9pr/b/YmrfqnvtWXtBSuPzRtdftMNm0rumvjtdraq28H0
52tf4LsqWvddlr1k47LTy3e+1L5g+Ye+8PDTk3qUrj5ed1WfX6sb78+rXDRk4Lr9
DWcO3rBi8eYrDz+QF0+bdfvS+r6FeG7r7se/a9097d6+xTsOz8B7it4YP7HftQ8v
GDTzyZ3bX2tb8+OGJWNv/qHh0Q+KTp6eZ267sN+Mx5Z8dV/T2jlVQ9/Yd6D/rKnp
Lmeq+h5oGAkvb2x48dmBz+wvU2Xzft8Uzz70UbTh4usXNxXenlczf/DSg/1f3z9n
w5OjBsSDW4tTa45Nu65b1+ENm3fd3PtU3ampBflFwyZ0X7BryOodP7ZeOiW/Yv6Y
T+97dNDeJfrNlvqCbwY+v2X8A/BCXvdH4zrY47qN31R8e0vz5IdW2+yW9W2z/eib
DjUMqjzaOvnV79/f/sjTz/VctvyL7n23rt/ds7698sE7i7q++uWepOmp1+7e3tx7
+suvjL2/21v35CoermjuvWw0bLt6xXe9MkdSe0oXl/788eHGqZW2onjTkbK1K7ou
3/ZEc7Lg9YNTy3N7h/Ua2LNg6Nd7qlTy3oS2a+5Wt6w/cWzpFWPTN36WOvl2XlPj
Q3PgiJ5HmlZVZYue3/HOvjq8+fiS/gPa+5SVH33qTyzI/rc=
=QZw0
-----END PGP MESSAGE-----

I'm then trying to validate that signature given the file and the above message. OpenPGP and Kleapatra do not recognize the above block as a valid signature block.
Since technically signature blocks should be -----START PGP SIGNATURE-----, I tried swapping this out to see if it made a difference and it does not.
I'm using this code to sign the Release file of an Debian apt repository. Debian also rejects this signature and states that its not valid. As a result it does not appear to be isolated to a particular place/way of validating the signature.
Am I creating a signature properly? If so, there appears to be a bug here.
If not, can you please help clarify?
In case its needed, this is what was signed:
Description: Cyber Ninjas training repository.
Label: Cyber Ninjas
Origin: Cyber Ninjas
Version: 1.1
Date: Fri, 30 Jun 2017 18:19:19 +000
Architectures: amd64 source
Components: contrib
MD5Sum:
 33184a6bac002692658617aeffd962b9 808 contrib/binary-amd64/Packages.bz2
 f5a4b2edc71ad98ac0c7b71d8d37ef9c 70 contrib/source/Packages.bz2
 00622d24ceed3040c08354bd9f2ad460 16384 contrib/binary-amd64/Packages.gz
 4f17a2d308da1cdc2f3e46b8e5aaf7ca 16384 contrib/source/Packages.gz
 43f32410ba19f6850e1486ccf5dcb208 1113 contrib/binary-amd64/Packages
 d304efc32767a5bfaa6241255d342bb8 29 contrib/source/Packages
SHA1:
 40b2560ae569036045003029eab89dfa72d3076b 808 contrib/binary-amd64/Packages.bz2
 3cefcf78f3e56aa52cbd2c6d4e12d1e2d8d913f3 70 contrib/source/Packages.bz2
 306b3ed7a5e146ff22fc4147cb93f3bfff9a9cee 16384 contrib/binary-amd64/Packages.gz
 121e218a5a949382c744570694e9ab510c39763f 16384 contrib/source/Packages.gz
 58929cb01ca8ff965d7f86f08986fff1c6fc8039 1113 contrib/binary-amd64/Packages
 6fe1b559ec17c7a1de4088da191fadab91f3bd0a 29 contrib/source/Packages
SHA256:
 69674ed4835029fa3b5d7622d4ee4b74a4d96786f37ead983c1401addd3663a4 808 contrib/binary-amd64/Packages.bz2
 eafadb6da59700f020566f059ad0a2f59f0b8c3eff19f83c559073b11fb0369f 70 contrib/source/Packages.bz2
 ca2cadde4fba8ac52c75ba6e87ccd176ee4571f0dc2701355278a1e6741444b5 16384 contrib/binary-amd64/Packages.gz
 85f2dda5ab4c048b4a14fa2e1e69961e416a728b9aea7cc20250ef8bee90b774 16384 contrib/source/Packages.gz
 09e1bd0fdf32589e1d350d0ca390fd0f1f66429f066fdf93af3f9e080225e277 1113 contrib/binary-amd64/Packages
 7efea3710d1d72627b63bfc8bc2cbcf58ed3c0613877b08fef9dbde901ff841a 29 contrib/source/Packages

Works for me. You have to use decryption and not verification because.... uh ..reasons.
Anyways, pipe that to gpg --decrypt and it should work

@maxtaco I'm not sure exactly what you're saying. Are you basically stating that if I run it through the tools in a different way it will validate? That doesn't really do me much good. apt-get is going to consume this information, I can't tell it to run it a different way. I need to have the signature in the format defined by the specs for a PGP Signature block so that any client can validate it.
I'm not both the person signing and validating, in which case I could really do whatever I wanted.
Are you saying that kbgpg does not support signature blocks, according to the GPG standard, or are you saying I need to generate the signature differently with my code?

I am pretty sure we do support detached signatures. I will have to look
it up when I get back to a machine.
On Fri, Jun 30, 2017 at 3:16 PM Doug Logan<EMAIL_ADDRESS>wrote:

@maxtaco https://github.com/maxtaco I'm not sure exactly what you're
saying. Are you basically stating that if I run it through the tools in a
different way it will validate? That doesn't really do me much good.
apt-get is going to consume this information, I can't tell it to run it a
different way. I need to have the signature in the format defined by the
specs for a PGP Signature block so that any client can validate it.
I'm not both the person signing and validating, in which case I could
really do whatever I wanted.
Are you saying that kbgpg does not support signature blocks, according to
the GPG standard, or are you saying I need to generate the signature
differently with my code?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/kbpgp/issues/155#issuecomment-312351637, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA05_y-ZH92h8BnO-OS1Ad_l0gYIj5kGks5sJUmCgaJpZM4OK5yU
.

@maxtaco That would be absolutely awesome. From a quick grep of the source code it certainly looks like a lot of signature stuff is buried in there, I just haven't yet figured out the right way to call it.
As noted, the example giving for signing doesn't appear to create the "normal" output.

@maxtaco This is likely my error. What I'm testing and validating apparently is more than just "signing" its clearsigning. I found #109, and I'm trying to digest that into my code, but I'm really not understanding where F.key_flags is coming from.

I'm going to close this. This is probably best answered under #109 .


Add zlib 1.2.11 as separate Sample Scan

We currently have zlib as part of a composite Sample scan file.  This task is to add a separate scan for teh complete zlib 1.2.11 package from http://zlib.net/zlib-1.2.11.tar.gz.  zlib is one of the most popular open source packages with a few license exceptions - notably the GPL-licensed ADA code.

Update with new version with Root.

Closing Issues #35-#38 -- addressed by Issue #46 and Pull Request #51.


Fix ProxyDrawables not respecting whether the originals would be drawn

Fixes #1283, fixes ppy/osu#1591.
Alternative to #1505.
Proxying the draw nodes seems to cover every case I can think of without requiring any parent traversal. Drawbacks to this:

Requires passing a frame counter down through GenerateDrawNodeSubtree/addFromComposite to determine if the drawnode was generated in the frame from the original drawable.
Adds around 24 bytes to ProxyDrawable.

So the way this all works now is ProxyDrawable now generates and adds a DrawNode to the subtree, but the only purpose of this specialised DrawNode is to proxy the DrawNode.Draw() call to the real DrawNode as generated by the original Drawable.
From:

To:

I've now made ProxyDrawable a private class nested (in a partial class) in Drawable. It's exposed as a Drawable to consumers of CreateProxy now, with the now public members IsProxy/HasProxy if they need to specifically check for if it's  aproxy

I personally don't mind large files (your IDE should help deal with them easily) and thus would rather be in favor of not partialing Drawable at all. Alternatively, if it were to be partiald, then a lot more than just ProxyDrawable should be in a partial class.

This particular case is where the partial part is only used to store a tightly coupled nested class. We do the same in osu! (BeatmapManager -> BeatmaapManagerWorkingBeatmap).
I'm fine with this usage of partial, but strongly against the same class being split across files. Hopefully @Tom94 can agree to this.

I'm fine with that reasoning as long as we're consistent. How about the nested HandleInputCache?

We generally only do it for larger classes, but even HandleInputCache is probably large enough to be moved out IMO. At the moment it's awkwardly wedged in the middle.

+1 to moving HandleInputCache to a partial class too

I am really uncomfortable with adding the complexity of the frame counter and validation along with DrawNode cross-references. I wonder if a nicer solution exists, because I'd like to keep the code Update/Draw pipeline as lean as possible.
On second thought I am also starting to doubt whether it makes sense to hide the Proxy when the parent is hidden, but not when it is masked away in the first place. That decision seems inconsistent. Since we also argued that partial masking would be impossible, I'd actually start leaning towards the old behaviour of not tying the Proxy to its Parent's state in general.
Lastly, we should also not ignore the possibility that ProxyDrawable may not be the optimal mechanism for the thing we're trying to achieve on the osu! side. Are there any alternatives? IIRC we didn't think very long and hard when we decided to add ProxyDrawable as a simple way to make approach circles work. If ProxyDrawable starts to get used in more complex ways and requires additional overhead we should re-evaluate if it's truly worth it.

Re: Counter. I don't think the counter is too offensive, but we may be able to remove that in-exchange for a flag that gets set + reset on validation + on draw respectively. I'll experiment with this if you'd like.
Re complexity. I can't think of any other way to do this other than doing DrawNode cross references/validation, since you can't know whether the original Drawable would have been drawn until post-DrawNode-generation. Would be open to suggestion, however I've thought about this for many days and have attempted many things.

Re: Masked away. What do you mean by "not when it is masked away"? If the proxied drawable is outside of the proxy's parents' (which is masking) masking area, the proxied drawable will be "masked away" without IsMaskedAway being set to true.
E.g. with the following code:
new Container
{
    Children = new Drawable[]
    {
        box,
        new Container { Masking = true, Child = box.CreateProxy() }
    }
}

The following is possible (yellow is the masking container, red is box's proxy with the original box's position/size, white is the drawn part):

Obviously you can imagine that as the box is moved more outside the container, less and less of it will be drawn, until a point where it is completely masked away. This stays true to the definition of IsMaskedAway which states "but it may be false, even if the Drawable was masked away" (i.e. in the above scenario, IsMaskedAway will be false).

You're free to suggest an alternative for osu!, however this doesn't exclude the fact that ProxyDrawables are inherently broken in their current state.

I don't have a better idea in mind; just wanted to make sure the design decision was thought about long and hard.

I think you misunderstand. I'm talking about the case where the original is masked away by the original parent. I think it is inconsistent to keep drawing the proxy in this case, but to not keep drawing the proxy when the original parent hides the original in some other way than masking (e.g. by !IsPresent or !IsAlive). Either all of these cases should hide the proxy or none of them, and I favour "none", because "all" would require some sensible form of masking by the original, which we cannot do.

I am not fully familiar with the context in which proxies are used within lazer and frankly I do not have the time to follow both lazer and framework development in detail. This makes it hard for me to come up with any specific ideas, so I leave the final decisions to you. Just giving my 2 cents on what I think may be the best course of action in case there is another way. IIRC for approach circles proxies were only used to customise draw order without throwing hitobject grouping under the bus; nothing else.

When it is fully masked away by its parent, it's not going to be drawn by the proxy, since the original won't generate draw nodes. This is consistent with !IsPresent / !IsAlive.
When it is partially masked away by its parent (or even not masked away at all), the original would be drawn, so will be drawn by the proxy. The only difference is that the proxy is the one that has the final say as to how things appear on screen as it does the final drawnode masking.

Your "none" proposal is infeasible and potentially dangerous, as that means you can remove a drawable from the hierarchy and still have it drawn by the proxy, meanwhile it's not getting any updates and may potentially even have no parent.

Still sounds strange to me. If full masking by the original parent has any effect, why wouldn't partial masking do so, too?
Also, I find it to be a weird notion, that moving the original around without affecting how the proxy is ultimately drawn can result in the proxy suddenly becoming invisible. Seems like annoying mental overhead that is required when using proxies. As far as I can tell, as it stands now, proxied drawables are simply the originals inserted at other arbitrary positions within the scene graph without any strings attached. This sounds like the most straightforward model to me.
Could you refresh my mind on what the use case of the new behaviour would be within lazer?

Re "none" proposal being dangerous: Should be trivial to throw an exception in such a case.

We can change the original to never have its IsMaskedAway never updated, I wouldn't mind that on a first thought.
There are two immediate use cases for this in lazer:

Approach Circles (as previously discussed), where you should be able to fastforward in the editor at any time and cause the original to become !IsAlive, and have it not be drawn.
Swells (taiko), where they're proxied into an upper layer so they don't underlap the black underlay for the drum on the left. Upon fastforwarding in something like the editor, again, the hitobject will be in an !IsAlive state and should be hidden.

So your exception would be essentially "if the original is not drawn, throw an exception"? No way, that will cause so many issues and make limit ProxyDrawable to being used in completely static contexts.


Notebooks - Intellisense not helpful if using . to select pandas df column

If i use the . to select a column in a pandas dataframe and then use . again to apply some function to it, the intellisense pop up is not helpful as it does not show the function in full

Compared to using the [ ] to select a column

This is the label from Jupyter being super long. Going to change this anyway to not be so long. That change will fix this bug.

Repro steps:

Clone https://github.com/claudiaregio/data-science.git
Create conda environment using the 'golden_scenario_env.yml'
Open in VS code
Open titanic.ipynb
Switch to the golden_scenario kernel
Run the first two cells
Create a new cell
type in titanic_df. and wait a bit (jupyter provides column names so might have to wait a bit)
if you get Embarked in the autocomplete, hit tab and then . again
verify the auto complete is only the next word, and doesn't have titanic.Embarked. embedded in it.

Should look something like so:

Looks good.


Issue loading Hildebrand using Boot?

Hello,
Caveat: I suspect that this is probably an issue with how I'm loading things, and not with hildebrand itself, but any advice here would be appreciated.
I'm trying to use hildebrand on a toy project to create an AWS Lambda Function using CLJS. I'm using boot as my build tool, instead of leiningen.
When I run my lambda function,  aws-sam-local (functions.js is the compiled file), I get:
module initialization error: TypeError
    at Object.<anonymous> (/var/task/functions.js:3251:21)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/var/task/tournaments.js:2:9)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)

This is happening even with this minimal file:
(ns functions.core
  (:require [cljs-lambda.macros :Refer-macros [defgateway]]
                 [promesa.core :as p]
                 [hildebrand.channeled :refer [query!]]))

However, given I can require other libraries without issue, I think there must be something at least related to Hildebrand here.
I'm compiling using the google closure compiler with simple optimizations.
Any advice? Thank you!

The R in refer-macros looks capitalised, which'd be a problem.


repeat action?

is there a way to dispatch an action that already happened? to repeat that action, basically?

@pvinis There isn't a resend action button, but you can use the "Dispatcher" (located middle'ish on bottom button row) to send a new action and copy-pasting the previous action payload.

yea I saw that, but if the action was holding much payload, a repeat button is useful. maybe I can try to make a PR that adds the button on mouseover.


function definition

will you give some explanations on the functions to help us understanding the code?  such as ?<, ?<=,=,> ,>=, ~=,intension and singleton.

Hi @tangyaohua ,
We didn't release the full descriptions of the functions due legal implications.
The singleton returns the singleton element of list or returns an error if there are more than one elements in the list.
Functions starting with ? return a constraint.
?<=(reference: Any): Any
construct the constraint "less than or equal to reference"

?<>(reference: Any): Any
construct the constraint "not equal to reference"

?=(reference: Any): Any
construct the constraint "exactly equal to reference"

?>(reference: Any): Any
construct the constraint "greater than reference"

?>=(reference: Any): Any
construct the constraint "greater than or equal to reference"

?~=(reference: Any): Any
construct the constraint "approximately equal to reference"

Best,
Hao

thanks for your reply, another question about functions is what's the difference between revise, UpdatePreflightEventWrapper and NewClobber.  Looks like they are all used to update some values.

Hi @tangyaohua,
Thanks for your questions. You've prompted us to start writing up a README with some general explanations of library functions, especially for these less intuitive ones.
In the meantime, here's my attempt to explain these specific functions:
NewClobber makes a nondestructive copy on the dataflow graph of the node matching its :intension argument, with the node matching its :slotConstraint replaced by the node matching its :value argument.
ReviseConstraint has an interface just like NewClobber's, except instead of fully replacing the old node (:slotConstraint) with a new node (:value), it revises an old Constraint (:oldLocation) with a new Constraint (:new). We have custom (currently private) revision logic that attempts to match the pragmatics of what we actually want when we ask for updated constraints in language. Sometimes it's replacing one field in the constraint, sometimes it's relaxing or removing a field, etc. In very simple cases it looks like dict.update in Python, and in fact that is the revision logic we use in our MultiWOZ experiments.
UpdatePreflightEventWrapper is our representation of a request that will eventually get sent to an external event updating API. It's "Update" because it will eventually change an event that already exists on your calendar. And it's "Preflight" because we're not sending the request over the wire just yet; we're still in requirements gathering mode.
Cheers,
-Sam

Thanks very much. It would be a great help if you could release more information, expecially on Constraint and data labelling guideline.
Best,
Yaohua

will you give some explanations on functions like ActionIntensionConstraint,extensionConstraint, UpdateEventIntensionConstraint, alwaysTrueConstraintConstraint and nested Constraint[Constraint[Time]].  UpdateEventIntensionConstraint and Constraint[Constraint[Event]] both could be used as the oldLocation field of ReviseConstraint.
Can I take Constraint as a search function?

Hi @tangyaohua, we have now provided a README for the semantics here. Hope this can answer some of your questions.

thanks~~

same questions about Constraint[Constraint[Event]], AlwaysFalseConstraint, AlwaysTrueConstraint?

Hi, same problem here. It seems the README does not give any explanation regarding constraints (Constraint[Constraint[Event]], AlwaysFalseConstraint, AlwaysTrueConstraint, ActionIntensionConstraint, extensionConstraint, UpdateEventIntensionConstraint) and I cannot figure out what these are. Could you give some explanation or update the readme? Thanks!

It would be a lot of work to fully document everything. It might be worth asking why you want to know? Forgive the oversimplified analogy, but you don't expect machine translation datasets to come with a complete reference description of the languages involved, nor do researchers typically need to be able to read the inputs and outputs. Of course it can be helpful, but as I said it would be a little onerous. If you give an example of why you are asking, perhaps we can provide some limited documentation that will answer that question and all questions like it?

This analogy is kind of missing the point, as this "language" is only "spoken" by Semantic Machines...
Why should anyone bother translating natural language utterances into a semantic representation they don't understand...?


[Bug] Docs are inconsistent with respect to install

[x] I didn't find a similar issue already open. (I did but doesn't seem like anything has been addressed on the situation)
[x] I read the documentation (README AND Wiki)
[x] I have installed FFMpeg
[x] My problem is related to Spleeter only, not a derivative product (such as Webapplication, or GUI provided by others)

Description
The documentation gives conflicting messages about whether or not to use Conda for dependency install. If Conda is "not recommended" as the docs now indicate the steps for alternative install should be laid out (ie; instructions to install dependencies with pip, whatever). pip install spleeter is not sufficient.
Step to reproduce

Visit the README or the install document with no prior context and notice how Conda is not recommended and conda commands are still present in the document.

@mattpetters the documentation doesn't say not to use conda it says not to install spleeter using conda.
"Note that we no longer recommend using conda for installing spleeter."
while the conda command is used to install ffmpeg & libsndfile. ffmpeg & libsndfile are completely different packages and are used by Spleeter but are not a part of the spleeter project.
"conda install -c conda-forge ffmpeg libsndfile"

Oh, that clears it up. I think my reading of it was that conda shouldn't be used period. Thanks for this.

Not a problem... I can see how you'd make that mistake..


Added CodeCov yml file for settings

Added CodeCov yaml file setting ignore settings for the project

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 79.84%. Comparing base (e2d4362) to head (4090107).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   88.99%   79.84%   -9.15%
==========================================
  Files          12        8       -4
  Lines         318      129     -189
==========================================
- Hits          283      103     -180
+ Misses         35       26       -9

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


White bubble when overing icon on map

Hi,
The preview note when overing the icon is fine, but the white bubble that appears also when overing seems like unnecessary if preview appears. Would it be possible to add an option to choose also if we want the white buble to show up or not?
Tx

I can easily make it optional, the problem is that I was unable to find a way to show the note name in the preview (which Obsidian completely manages by itself), so without that extra bubble you'd get a completely anonymous file preview. That's the reason for the annoying duplicity.
Is it useful to enable turning it off?

I understand.
As far as I know, the white bubble only shows name of note and below, the place, if the location is defined inline. Then I may suggest:
-Would it be possible to make the bubble to have the same width than the note preview window? If so, then could it be possible to place it exactly (touching) above the preview window? I am trying to suggest a way to fake it, i.e. to put the bubble just as a piece glued above the preview window, so to give the impression it is a single entity...
If too complicated, or not possible then, at least, I would suggest:

to remove the .md extension from the name
format it a bit better: put the name in a larger font, and maybe followed by the location in the same line in a smaller size and between parenthesis or brackets, just to make the bubble a single line, so the bubble is perceived as just for that, to show the name. Alternatively, if it is preferred to keep them in two lines (name and location), then in addition to adjust the font sizes, styles (whatever) to horizontal center both, name and location, and to reduce the interline space and margins).
Make it change color with Obsidian (Dark, Light modes)
Make the corners of the bubble more like the theme, if possible.

Not sure about to add an option to turn it off. I have a title/name in the first line in some of my notes (so I can ID them in preview), but not in all of them. I am not sure.

I correct my last line, it might be useful to add an option to disable it, for people using plugins like "Hover Editor" or similar that replaces/improves the core plugin "Page Preview", and which shows nicely the name of the note at the top of the preview window. So, if possible I would add the option to turn it off too.

Added in the just-released 2.0.0 version.


Try to improve Rust performance for Lesson 203

I've tried to improve the performance of Rust code for lesson 203. Ideally, I'd use axum (for http server) and metrics-exporter-prometheus for metrics but I haven't changed that as this comparison is between actix-web and Go framework.

Thanks for the PR @devashishdxt , i'd like to keep original code as is just for the future references, would you mind to create something like rust-app-v2 or improved folder in this 203 lesson and I'll merge and test the code?

Thanks for the PR @devashishdxt , i'd like to keep original code as is just for the future references, would you mind to create something like rust-app-v2 or improved folder in this 203 lesson and I'll merge and test the code?

Ok. Will create another PR.


PyPI v0.2 and Github tag v0.2 don't match

I'm going to roll a v0.3 release once I can verify that the tests do indeed pass, but want to bring it up that the tag was made in January by the package on PyPI was created last November.

Not sure if this is actually worth fixing, but was curious what happened (or if anyone knows).

Closing issues -- v0.3.0 tag and release on PyPI match, so this is only an issue for previous installations.


Dispatching customized events

Making possible dispatch events during the "smart banner" life cycle

Hi Kudago,
I am Carlos Gusmão, software engineer from Globo.com(http://globo.com).
Two months ago I opened a pull request to make possible dispatch custom events during smart banner life cycle.
Could you take a look in my pull request, please? I am waiting that to finish my smart app banner.
Tks and best regards,
Carlos Gusmão

Hi @caeugusmao!
I could not find a use-case for that and how is it better than just running code after creating a banner.

Hi @dfcreative!
We need to know when the banner was loaded and how the banner is created asynchronously I believe that custom events are the best form to solve this kind of problem . The event enables I know if banner is already loaded and trigger another functions that depend the smart banner loaded.
Another form to solve this problem is trigger a callback after banner is loaded, but I prefer events.
Do you know another way to my use-case?
Thanks for listening!
Carlos Gusmão

There is no much of async to introduce events pattern.
If you are afraid to run code before banner is ready, you can force your code be invoked inside of DOMContentLoaded event.
Otherwise I would recomment just include smartbanner at the end of the document - that way you can safely run your code after banner in sync way.
As for async patterns there are events core module, promises and node-style callbacks, the last is preferrable in such simple cases.


simple_form issue

rails 3.2.22
simple form 2.1.3
<%= f.input :file, as: :attachment %>

undefined method `merge_wrapper_options' for #<SimpleForm::Inputs::AttachmentInput:0x007fc2b0e542a8>

refile (0.6.2) lib/refile/simple_form.rb:8:in `input'
simple_form (2.1.3) lib/simple_form/components/label_input.rb:11:in `label_input'
simple_form (2.1.3) lib/simple_form/wrappers/many.rb:29:in `block in render'
simple_form (2.1.3) lib/simple_form/wrappers/many.rb:27:in `each'
simple_form (2.1.3) lib/simple_form/wrappers/many.rb:27:in `render'
simple_form (2.1.3) lib/simple_form/wrappers/root.rb:15:in `render'
simple_form (2.1.3) lib/simple_form/form_builder.rb:117:in `input'
app/views/imports/_form.html.erb:14:in `block (2 levels) in _app_views_imports__form_html_erb__1822506517190200501_70237088127880'

http://stackoverflow.com/questions/26303091/undefined-method-merge-wrapper-options
Fixed by creating a custom input implementing the merge_wrapper_options:
class AttachmentInput < SimpleForm::Inputs::AttachmentInput
  def merge_wrapper_options(options, wrapper_options)
    if wrapper_options
      options.merge(wrapper_options) do |_, oldval, newval|
        if Array === oldval
          oldval + Array(newval)
        end
      end
    else
      options
    end
  end
end

Makes sense to add support to latest compatible simple form with rails 3.2?


Graphic Path type  inconsistencies.

There 3 path types : Rhumb (constant bearing), great circle (geodesic or shortest distance), and linear.
Cesium and WorldWind are defaulting path type to great circle. The SEC renderer is using rhumb.  I checked and the EMP core geo libraries used for calculations  are using great circle.  So the only component using rhumb is the SEC renderer.  There must be an option in the core and API to set the path type for all engines. What path types should be the default?

After further discussion and investigation the default path type should be rhumb for all engines. If rhumb is the path type of choice then there is no need to expose a property for path type in the EMP API.
Cesium will add an option for selecting rhumb type : https://github.com/AnalyticalGraphicsInc/cesium/issues/4000.

-WW Android is fine handling rhumb

Need to set  rhumb paths in Leaflet and webWorldwWnd. I don't know is the engine's sdk support the use of rhumb.
-issue Blocked until Cesium add support for rhumb path.

WSEC complaint that Android map calculations for graphics is incorrect because they are expecting geodesic and the map is rendering rhumb. The same issue happens also in emp3-web because it is using the same geo libraries Android map uses.  The solution is to replace to  library that supports geodesic like in the following link:
https://geographiclib.sourceforge.io/scripts/geod-calc.html
Cesium by default does support geodesic.
WW web ?
Leaflet ?
The Javascript renderer only supports rhumb. I need to talk to @michael-spinelli  about the level of effort required to upgrade the renderer to use geodesic.


go.mod: github.com/containerd/zfs v0.0.0-20210322090317-0e92c2247fb7 (for snapshot usage)

Contains "Implements zfs usage by returning the USED field from the zfs snapshot"
(https://github.com/containerd/zfs/pull/38)

Question from a total newbie on containerd's release process: I suppose this fix can't / won't be backported to the 1.4 branch?
I'm asking because this fix would be more than welcome in MicroK8s, which will use containerd 1.4.x for the next MicroK8s 1.21 release.

@dalbani zfs is supported in 1.4 so this would be a backport-able change. I believe that would require backporting in the zfs repo as well to exclude non-backported changes when vendoring into the 1.4 branch.

@dmcgowan
Shall I then open a feature request regarding my wish to have this function backported to 1.4?

I believe that would require backporting in the zfs repo as well to exclude non-backported changes when vendoring into the 1.4 branch.

Diff between version used in 1.4 and this version; https://github.com/containerd/zfs/compare/9abf673ca6ff9ab8d9bd776a4ceff8f6dc699c3d...0e92c2247fb7. At a glance, most changes look "ok" (so probably wouldn't require containerd/zfs to branch for 1.4); only change that requires local changes (afaics) is this commit: https://github.com/containerd/zfs/commit/804f3e066141aeb70ade73631fcb8bc913d60e81 (https://github.com/containerd/zfs/pull/31) (would depend on cherry-picking https://github.com/containerd/containerd/commit/96f4ce4a5c24745efc9596975b885be30101a5f4 https://github.com/containerd/containerd/pull/4534)

Thanks @thaJeztah for this detailed report! Let me know if I can help.


[FLINK-28857][docs] Add Document for DataStream Cache API

What is the purpose of the change
Add Document for DataStream Cache API.
Brief change log

Add Document for DataStream Cache API

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@gaoyunhaii Thanks for your comment! The PR has been updated accordingly. Could you please take another look?


Add DNS query logging to FAST net stages

Fixes #2020

Reopening this as I'm getting this error applying the changes in my existing net stage


Update most date functions to be explicit of a date or character var is necessary

We can either update the programming strategy requiring a conversion before date functions are used, be explicit in the documentation or update date functions for consistency

Did the tester mention for which functions the information is missing? I checked some and did not find any where it was not stated if a date, datetime, or character variable is expected.

Example i found: see https://pharmaverse.github.io/admiral/reference/derive_vars_dtm.html min_dates and max_dates arguments. DTM can be used here as well as DT but its not clear from the documentation

as a good example here i like https://pharmaverse.github.io/admiral/reference/derive_vars_duration.html which says for start_date / end_date: "A date or date-time object is expected.". We could just copy this over to any doc pages that doesn't have it clearly shown for date arguments.

@rossfarrugia - I am new to this, I will take a look at the derive_vars_dtm for updating the documentation. I'll take a look at other functions that may have this issue and update the documentation.

thanks @VD766 - much appreciate your contribution!
also if you get chance can you update the below on github to help us keep track of all our contributors:


Ability to auto screenshot?

Have you tried or thought about this being able to send screenshots automatically to the hook? Essentially the same as the original screenshot plug with pets, deaths, kills?

Sorry for the late reply. I'm not sure what you're asking, You mean randomly screenshotting and sending it to the webhook?

No worries.
Not randomly no. You know how the official screenshot plugin saves to the directory on deaths, pets, kills, levels etc? Essentially wondering if it would be possible to have those screenshots send without having to click the button

Ah, I could implement that, however there are multiple plugins available that already do exactly that.


KAFKA-6789: Handle COORDINATOR_LOAD_IN_PROGRESS, COORDINATOR_NOT_AVAILABLE retriable errors in AdminClient API

Handle COORDINATOR_LOAD_IN_PROGRESS, COORDINATOR_NOT_AVAILABLE retriable errors in
AdminClient describe groups, delete Groups, list Offsets API

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@hachikuji  Please take a look when you get a chance.

retest this please

Hi @omkreddy , if you don't mind, I've reviewed it too and left a few comments.

@hachikuji Pls take a look.

@hachikuji pinging for review.

@hachikuji  pinging for review

@cmccabe can you please review this?

AdminClient already has retry logic for consumer group requests.
However, there are a few cases that we don't handle.  One is where the leader has moved between the call to findCoordinator and our attempt to describe the group that the coordinator owns.  This patch doesn't fix that case either, though.
This patch replaces a lot of checks for specific errors with checks to see if something inherits from RetriableException.  As I've commented before on other JIRAs, I don't think this is a good idea for AdminClient.  Specific exceptions have to be handled in a specific way based on what they indicate.  For example, if there is a load in progess, maybe we need to back off for a little bit until it completes.  If the coordinator has moved, we should try to send to the new coordinator.  Just checking for what inherits from what tends to lead to the wrong behavior because people don't think about what each specific error case means and how it should be handled.
Also, what is the rationale for renaming COORDINATOR_LOADING_IN_PROGRESS to COORDINATOR_LOAD_IN_PROGRESS?
I can see that the patch adds retry logic to deleteConsumer groups.  However, I don't understand why we would want to do this.  It seems like all the errors for deleting groups are not retryable and related to things like authorization, etc.
In general I think we should probably drop this PR and rethink the approach.  It would be particularly useful to know what specific errors people want to handle that aren't handled now.

@cmccabe  This PR implementation is consistent with existing code (listConsumerGroups), where we try for COORDINATOR_LOAD_IN_PROGRESS, COORDINATOR_NOT_AVAILABLE errors.
Yes, this PR does not solve NOT_COORDINATOR errors (where leader moved).
This is an attempt to maintain consistent behaviour across all methods calls.
There is no rename of COORDINATOR_LOAD_IN_PROGRESS, I just updated the comment with correct enum name.
In  deleteConsumer groups also, We are only retrying retriable exceptions, not all exceptions.
This PR implementation approach is same as https://github.com/apache/kafka/pull/5595 PR.

This PR implementation is consistent with existing code (listConsumerGroups), where we try for COORDINATOR_LOAD_IN_PROGRESS, COORDINATOR_NOT_AVAILABLE errors.

I agree that we should make listGroups and describeGroups consistent.  What I disagree with is that I don't think we should be checking whether something is a RetriableException.  We should list what to do with each particular exception type.

Yes, this PR does not solve NOT_COORDINATOR errors (where leader moved). This is an attempt to maintain consistent behaviour across all methods calls.

Understood.  We certainly don't have to solve every problem in this PR.  However, I think that the current name of the PR, "Add retry logic to AdminClient consumer group requests" is misleading, since it implies that there is no existing retry logic.

There is no rename of COORDINATOR_LOAD_IN_PROGRESS, I just updated the comment with correct enum name.

That's true -- my mistake.  Your change just fixes a comment.

This PR implementation approach is same as #5595 PR.

The approach in #5595 is to enumerate specific errors and handle them as needed.  That's different than handling all subclasses of RetriableException the same way.

ok..I tried to extract duplicate code to a common method. this me made to handle all RetriableExceptions in same way.  I will try to revert some of the changes and will try to handle specific errors .

@cmccabe @hachikuji  Updated the PR to handle COORDINATOR_LOAD_IN_PROGRESS, COORDINATOR_NOT_AVAILABLE retriable errors in consumer group API.

@hachikuji Thanks for the review. Updated the PR, Please take a look.