I can not reproduce enhanced audio for same noisy audio file. Question : sampler() ?

Hi,
Thank you for sharing your codes. I want to denoise a couple of audio files using sgmse-dereverberation model without any training involved. But when I checked generated tensors I realized that sgmse-dereverberation model produced different values for same audios each time because of sampler step. I'm curious about sampler().
Also the model is for 16 kHz sampling rate, right ?
Thanks.

Hi again,

I tried your suggestion (torch.manual_seed(0)) about 4 months ago and it worked but how about different pc's ?
How can I use DCUNet as the score model instead of NCSN++ for test model performance ? Is there any checkpoint for this purpose ?

Thank you !

torch.manual_seed(0) should also work if it runs on different computers.
We only offer checkpoints for SGMSE+ (NCSN++ backbone) and not for SGMSE (DCUNet backbone).


[Fix] Failing unit tests

5/7 tests are failing in scripts/jasmine/SpecRunner.html.
The app is working fine though. Those tests need to be updated.

After https://github.com/googleinterns/step230-2020/pull/72 the file is located in /test/webapp/script/IndexSpec.js


Time stretching causes source separation options to crash

"if you have time stretching turned on it will crash.  We're not using time-stretching so no big whup for us, but something you should check out for the general case"
Reported by John Hershey as a bug in #55.

@pseeth seems like something we must fix in the context of #55 ? Were you able to get a MWE to debug?

Hmm, I had look at the test case and I do test the code with time stretching and it passes...any chance I could get an MWE from @epicycles to test this?

@epicycles much has changed since this issue was reported (we're now on 1.6.2 !!).
Any chance you can test your code against this version and let us know if there are still issues?


Upgrade the distribution package version to 2.8.0-beta1 to eliminate the security alerts

What can we help you?

depend on #844

Closed by https://github.com/goharbor/harbor-operator/pull/895


Handle unknown block types more gracefully

At the moment the BlockSerializer throws an error for unknown block types. Could the renderer just render nothing, or an error string, and emit a warning instead of throwing an error?
We use different serializers (react + react-native) for the same content, and we have several custom blocks. This means that it is a real risks for the serializers to get out of sync with the block content, and the result would be an ugly crash of the application.
Another case: We render block content in a mobile app. Even if the serializers get updated properly, a lot of users will not update the app immediately. This means that all old versions of the app would crash once a new block element is used in content that is also loaded by old apps.

The configuration could offer to pass a errorSerializer. This would be a function that is called with an error object for all errors happening during serialization, and would be expected to return a renderable element.
We would also emit an error report to Sentry in case of an error, which could also be handled in the errorSerializer.

Hi, I just realised that #13 does exactly what we would need. Would it possible to merge the PR?

@barbogast it just got merged 🎉

@barbogast it just got merged 🎉

Should this issue be closed?

I guess so, yeah. Closing...


Not all files are installed

Hi team,
When installing nlmod using pip install, it seems that not all necessary files in the repository are being copied over. I noticed that the voleg and gleg files in the data/geotop directory are missing on my machine (only the csv files are there). Any clues?
Thanks!

You are right. Only csv-files were specified in the install-file (pyproject.toml). I will add a fix.

Thanks Ruben, I just tested this and it works


Update the installer script to run on a fresh install

This PR contains several adjustments I made to the script as I attempted to run it from a fresh FreeBSD install.

Run with /bin/sh and not /usr/local/bin/bash since it isn't installed yet
terminate the script if an error happens
use sudo to install the dependent packages
add icu as a dependency
add xorg as a dependency
adjust configure options to tools-make to make it properly point to libobjc
generate the CFLAGS and LDFLAGS with gnu step-config when building libs-corebase (it wasn't able to find the objc runtime headers)

Testing it now...


Verify transaction links from Console and Token Front End work successfully

Story
This story should already be true...
As a user
I can view the details of each of the transactions I make in console and token frontend by clicking on a 'view on explorer' link
So that I can check the details of my transaction (and share it with others if I wish)

[ ] Identify all the transaction types and places we link users to 'view on explorer' in console and token front end
[ ] Check and test links for all transaction types
[ ] Capture new tickets to fix any that aren't working

Console - Market Long&Short Orders Placed - Working fine - Example:
https://explorer.fairground.wtf/txs/0x0133CBC68041840D50145312AE1C81A731C2437591A1E8A5FE38C84B618BD177
Console - Limit Long Order Placed - - Working fine - Example:
https://explorer.fairground.wtf/txs/0x2DB40593712AA1D4025690A07C23355E3ACAAA9D48DFA5B78870FC259B019BD7


Feature antrea proxy ipset 2

Codecov Report

Merging #4 (daed89e) into main (66a9cf9) will decrease coverage by 10.12%.
The diff coverage is 49.21%.

@@             Coverage Diff             @@
##             main       #4       +/-   ##
===========================================
- Coverage   62.02%   51.89%   -10.13%
===========================================
  Files         281      284        +3
  Lines       21777    23484     +1707
===========================================
- Hits        13507    12187     -1320
- Misses       6859     9926     +3067
+ Partials     1411     1371       -40

Flag
Coverage Δ

kind-e2e-tests
31.65% <20.15%> (-20.76%)
:arrow_down:

unit-tests
40.65% <42.35%> (-0.99%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/agent/agent_linux.go
80.00% <0.00%> (-20.00%)
:arrow_down:

...g/agent/cniserver/interface_configuration_linux.go
16.15% <ø> (ø)

pkg/agent/cniserver/pod_configuration_linux.go
100.00% <ø> (ø)

pkg/agent/cniserver/sriov.go
0.00% <0.00%> (ø)

pkg/agent/config/traffic_encap_mode.go
100.00% <ø> (ø)

.../controller/egress/ipassigner/ip_assigner_linux.go
0.00% <0.00%> (ø)

pkg/agent/controller/networkpolicy/packetin.go
4.50% <0.00%> (-68.32%)
:arrow_down:

...agent/controller/traceflow/traceflow_controller.go
52.83% <0.00%> (-20.31%)
:arrow_down:

pkg/agent/flowexporter/connections/conntrack.go
76.19% <ø> (+2.27%)
:arrow_up:

.../agent/flowexporter/connections/conntrack_linux.go
59.78% <0.00%> (+0.64%)
:arrow_up:

... and 214 more


[WIP] Feat GUI add connection probability

Add connection probability to connection accordion boxes.

[] Add probability widgets to connection boxes
[] Test for connection box elements
[] Test for change in network construction

This PR is on hold. The problem is that if probability is changed, gid_pairs also needs to be recalculated. Work from this PR can be used once a means to update connection probabilities and associated parameters is implemented. This can either be on an API level, or changing the logic of the GUI to rebuild connections on Network init.
A patch fix to remove the GUI probability assignment logic was made in https://github.com/jonescompneurolab/hnn-core/pull/844.


Jupyter extension cause remote ssh disconnect at opening *.ipynb file

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Reproduce steps:

Connect to remote server via ssh (my local machine is mac, remote one is a linux server)
Install jupyter extension on remote machine
open a *.ipynb file
Then vscode will pop up with a window telling remote server disconnect.

Ablation:
after disabling jupyter extension, everything works fine.
VS Code Version
1.83.1 (Universal)
Jupyter Extension Version
v2023.9.1102792234
Jupyter logs
No response
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote

the same for me

Same problem here

@vincent0408 me the same, all in a sudden.

@vincent0408 @boli-bohan @maayan-myheritage @jupitersh
Sorry you are running into this issue.
Please could each of you share the following information:

Version of VS Code
Version of Jupyter extension
Local OS and version
Remote OS and version
Please verify you are using remote SSH
Please verify things work after disabling Jupyter extension

Things to try (please do try this and share the information):

If you have VS Code insiders installed,

Close all notebooks and python files,
Please intall the latest stable version of the Jupyter extension, versino 2023.9.**
Re-load VS Code
See how that goes

If the previous step doesn't fix it, please can you try to install the stable version of VS Code and giving that a go.

Finally, please can you  share the logs Extension Host and Remote SSH Logs

Version of VS Code: 1.83.1
Version of Jupyter extension: v2023.9.1102792234 (I tried 2 earlier versions, nothing helped)
Local OS and version: macOS Version 13.6 (22G120)
Remote OS and version: Ubuntu 20.04.5 LTS
Please verify you are using remote SSH: Yes
Please verify things work after disabling Jupyter extension: Yes, opening a notebook when the extension is disabled doesn't crush the remote session.
I also tried everything you suggested above, nothing helped.
I can confirm that other developers, using the same config don't have this problem.

Fresh (& latest) install of both remote ssh and jupyter
Experiencing same issue on vscode insiders
Version: 1.83.1
Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
Date: 2023-10-10T23:45:31.402Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.5.0-9-generic

One more thing: I noticed that this happens only with notebooks created today.
Running older notebooks works (even when edited as well).

Can someone please try installing VS Code 1.82 and see if that works.

Running older notebooks works (even when edited as well).

@maayan-myheritage
Ok, thats weird.
Sorry, but want to clarify

Opening old notebooks, no problem
Opening/creating new notebooks, causes vs code to crash
And disabling Jupyter extension fixes this

I can confirm that other developers that are using the same config don't have this problem.

Are they also using SSH/WSL?

Neither old nor new notebooks can be opened. The disconnect is some ~1-3 seconds after opening the notebook.

Local version: 1.83.1

Jupyter extension version: 2023.9.1102792234

Local OS: Windows 10 Pro 22H2 19045.3570

Remote: Red Hat 8.4.1-1

Using Remote - SSH extension

It does not disconnect if jupyter extension is disabled.

Already on stable jupyter

Already on stable vscode

 Extension Host
2023-10-19 16:27:35.101 [info] Extension host with pid 19616 started
2023-10-19 16:27:35.105 [info] [resolveAuthority(ssh-remote,1)][0ms] activating remote resolvers ssh-remote+softmatterlab01-p.gu.gu.se
2023-10-19 16:27:35.105 [info] [resolveAuthority(ssh-remote,1)][0ms] activating resolver for ssh-remote+softmatterlab01-p.gu.gu.se...
2023-10-19 16:27:35.111 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-ssh, startup: false, activationEvent: 'onResolveRemoteAuthority:ssh-remote'
2023-10-19 16:27:35.131 [info] [resolveAuthority(ssh-remote,1)][26ms] invoking final resolve()...
2023-10-19 16:27:36.139 [info] [resolveAuthority(ssh-remote,1)][1035ms] waiting...
2023-10-19 16:27:37.143 [info] [resolveAuthority(ssh-remote,1)][2039ms] waiting...
2023-10-19 16:27:38.147 [info] [resolveAuthority(ssh-remote,1)][3043ms] waiting...
2023-10-19 16:27:39.160 [info] [resolveAuthority(ssh-remote,1)][4055ms] waiting...
2023-10-19 16:27:39.399 [info] [resolveAuthority(ssh-remote,1)][4294ms] setting tunnel factory...
2023-10-19 16:27:39.399 [info] [resolveAuthority(ssh-remote,1)][4295ms] returned <IP_ADDRESS>:64446
2023-10-19 16:27:39.935 [info] Eager extensions activated
2023-10-19 16:27:40.039 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-containers, startup: false, activationEvent: 'onStartupFinished'
2023-10-19 16:27:40.088 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-wsl, startup: false, activationEvent: 'onStartupFinished'
2023-10-19 16:27:40.096 [info] ExtensionService#_doActivateExtension ms-vscode.remote-server, startup: false, activationEvent: 'onStartupFinished'
2023-10-19 16:27:41.585 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2023-10-19 16:32:28.514 [info] $getCanonicalURI invoked for authority (ssh-remote)
2023-10-19 16:32:32.620 [info] [resolveAuthority(ssh-remote,2)][0ms] activating remote resolvers ssh-remote+softmatterlab01-p.gu.gu.se
2023-10-19 16:32:32.621 [info] [resolveAuthority(ssh-remote,2)][0ms] activating resolver for ssh-remote+softmatterlab01-p.gu.gu.se...
2023-10-19 16:32:32.621 [info] [resolveAuthority(ssh-remote,2)][0ms] invoking final resolve()...
2023-10-19 16:32:33.621 [info] [resolveAuthority(ssh-remote,2)][1001ms] waiting...
2023-10-19 16:32:34.634 [info] [resolveAuthority(ssh-remote,2)][2014ms] waiting...
2023-10-19 16:32:35.641 [info] [resolveAuthority(ssh-remote,2)][3021ms] waiting...
2023-10-19 16:32:36.656 [info] [resolveAuthority(ssh-remote,2)][4036ms] waiting...
2023-10-19 16:32:37.671 [info] [resolveAuthority(ssh-remote,2)][5050ms] waiting...
2023-10-19 16:32:38.675 [info] [resolveAuthority(ssh-remote,2)][6055ms] waiting...
2023-10-19 16:32:39.679 [info] [resolveAuthority(ssh-remote,2)][7059ms] waiting...
2023-10-19 16:32:40.695 [info] [resolveAuthority(ssh-remote,2)][8074ms] waiting...
2023-10-19 16:32:41.695 [info] [resolveAuthority(ssh-remote,2)][9074ms] waiting...
2023-10-19 16:32:42.398 [info] [resolveAuthority(ssh-remote,2)][9778ms] setting tunnel factory...
2023-10-19 16:32:42.398 [info] [resolveAuthority(ssh-remote,2)][9778ms] returned <IP_ADDRESS>:64728

I can confirm that other developers that are using the same config don't have this problem.

Are they also using SSH/WSL?

yes, SSH

Running older notebooks works (even when edited as well).

@maayan-myheritage Ok, thats weird. Sorry, but want to clarify

Opening old notebooks, no problem
Opening/creating new notebooks, causes vs code to crash
And disabling Jupyter extension fixes this

yes, exactly

Jupyter extension does allow me to open notebooks without disconnect.

Are you disabling just the Jupyter extension, or Python extension as well.

Jupyter extension does allow me to open notebooks without disconnect.

Are you disabling just the Jupyter extension, or Python extension as well.

Great question. I was disabling both. Only disabling jupyter was apparently not enough to solve it

I didn't have to disable both, just the Jupyter extension

Is it possible this is a pylance issue? They released an update at about the same time these reports came rolling in, and it does get disabled with the python extension

Is it possible this is a pylance issue? They released an update at about the same time these reports came rolling in, and it does get disabled with the python extension

Disabling only pylance (in settings, language server None) also fixes the issue for me

I reverted to an older version pylance and it works again!

Is it possible this is a pylance issue? They released an update at about the same time these reports came rolling in, and it does get disabled with the python extension

Thinking the same, everything was fine before like 10 hours. During the the there was an update from pylance which asked for reloading the window, then the notebook crashed down.

@maxwellzh thats an excellent find, thank you very much
Temporary Solution,
Please disable Pylance for now

@vincent0408 @boli-bohan @maayan-myheritage @jupitersh
Please can you disable Pylance as a temporary solution.

@maxwellzh thats an excellent find, thank you very much
Temporary Solution,
Please disable Pylance for now

You can revert to the previous version, no need to disable

idk if anyone said this, but the same error happens on wsl


Sync Gateway doesn’t sync data from Server to my Android App

Hey Guys, I’m started to use Sync Gateway for my Android App, when I insert Data from Android to my Server everything works fine, but now I have the probleme that I can’t sync the Data from my Couchbase Server to the App.
There you can see my startSync method
public static final String SYNC_URL = "http://SERVER:4984/sync_gateway";
...
private void startSync() {
	URL syncUrl;
	try {
		syncUrl = new URL(SYNC_URL);
	} catch (MalformedURLException e) {
		throw new RuntimeException(e);
	}

	Replication pullReplication = database.createPullReplication(syncUrl);
	pullReplication.setContinuous(true);

	Replication pushReplication = database.createPushReplication(syncUrl);
	pushReplication.setContinuous(true);

	pullReplication.start();
	pushReplication.start();

	pullReplication.addChangeListener(this);
	pushReplication.addChangeListener(this);

}

and my config.json
{
"interface": ":4984",
"adminInterface": ":4985",
"log": ["CRUD", "CRUD+", "HTTP", "HTTP+", "Access", "Cache", "Shadow", "Shadow+", "Changes", "Changes+"],
"databases": {
"sync_gateway": {
"server": "http://SERVER:8091",
"bucket": "sync_gateway",
"sync": function(doc) {channel(doc.channels);},
"users": {
"GUEST": {
"disabled": false,
"admin_channels": ["*"]
}
}
}
}

}

Hi !
I had the same problem that @TheSlowlySnail : Data inserted on the bucket with a python script did not sync to my mobile App. After some googling I came here and learned about the  Bucket-Shadowing system.
I tryed to configure it and though I could still use the same bucket than the one used by my python script which is wrong : The app must use the shadow bucket.
Here is the first configuration I tried which did not work.
{
    "adminInterface": "<IP_ADDRESS>:4985",
    "interface": "<IP_ADDRESS>:4984",
    "log": ["CRUD+", "REST+", "Changes+", "Attach+","Shadow+"],
    "databases": {
            "grocery-sync": {
                    "server": "http://MYSERVER:8091",
                    "bucket":"grocery-sync",
                    "sync":`function(doc) { channel(doc.channels); }`,
                    "users": {
                            "GUEST": {"disabled": false, "admin_channels": ["*"]}
                    },
                    "shadow":{
                            "server": "http://MYSERVER:8091",
                            "bucket":"grocery-sync-shadow"
                    }
            }
    }
}

And here is the one that worked for me :
{
    "adminInterface": "<IP_ADDRESS>:4985",
    "interface": "<IP_ADDRESS>:4984",
    "log": ["CRUD+", "REST+", "Changes+", "Attach+","Shadow+"],
    "databases": {
            "grocery-sync": {
                    "server": "http://1MYSERVER:8091",
                    "bucket":"grocery-sync",
                    "sync":`function(doc) { channel(doc.channels); }`,
                    "users": {
                            "GUEST": {"disabled": false, "admin_channels": ["*"]}
                    }
            }
            "grocery-sync-app": {
                    "server": "http://1MYSERVER:8091",
                    "bucket":"grocery-sync-app",
                    "users": {
                            "GUEST": {"disabled": false, "admin_channels": ["*"]}
                    },
                    "shadow":{
                            "server": "http://MYSERVER:8091",
                            "bucket":"grocery-sync"
                    }
            }
    }
}

With this configuration, my python script can manipulate the "clean" grocery-sync bucket and my app can manipulate the "dirty" (sorry) grocery-sync-app bucket with lots of _sync stuff into each document.
I'm publishing this here so it can help others understand the shadow thing and maybe help improving the doc about it. Maybe adding a shadow example to configuration examples could be great too!
And finally I think the bucket shadowing should be mentioned somewhere in the documentation of couchbase mobile or couchbase sync because we discovered it quite late and it's quite a drawback :S
It works fine now on the grocery-sample, but we are not sure of how it will scale.

@ggendre I'd try to avoid bucket shadowing if at all possible, due to the complexity.  Any chance you can accomplish the same thing via a different route?  Eg, make sure all writes go through the sync gateway directly?

Hi @tleyden ,
I got an error as below when I start sync_gateway
C:\Program Files (x86)\Couchbase>sync_gateway "E:\Documents\My Project\mobile\Vegetable\sync-gateway-config.json"
2016-09-27T21:14:39.852+07:00 Enabling logging: [CRUD+ REST+ Changes+ Attach+]
2016-09-27T21:14:39.854+07:00 ==== Couchbase Sync Gateway/1.3.0(274;8c3ee28) ====
2016-09-27T21:14:39.855+07:00 Opening db /vegetable as bucket "vegetable", pool "default", server http://<IP_ADDRESS>:8091
2016-09-27T21:14:39.857+07:00 Opening Couchbase database vegetable on http://<IP_ADDRESS>:8091
_time=2016-09-27T21:14:39.936+07:00 _level=INFO _msg= Trying with selected node 0
_time=2016-09-27T21:14:39.938+07:00 _level=INFO _msg= Trying with http://<IP_ADDRESS>:8091/pools/default/bucketsStreaming/vegetable
_time=2016-09-27T21:14:39.965+07:00 _level=INFO _msg=Got new configuration for bucket vegetable
_time=2016-09-27T21:14:39.983+07:00 _level=INFO _msg= Trying with selected node 0
2016-09-27T21:14:40.047+07:00     Reset guest user to config
2016-09-27T21:14:40.048+07:00 Starting admin server on <IP_ADDRESS>:4985
2016-09-27T21:14:40.053+07:00 Starting server on :4984 ...
2016-09-27T21:14:40.054+07:00 FATAL: Failed to start HTTP server on <IP_ADDRESS>:4985: listen tcp <IP_ADDRESS>:4985: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. -- rest.(*ServerConfig).Serve() at config.go:628
Here is the my sync_gateway-config.json
{
"log":["CRUD+", "REST+", "Changes+", "Attach+"],
"databases": {
"vegetable": {
"server":"http://<IP_ADDRESS>:8091",
"bucket":"vegetable",
"sync":                function (doc) {                     channel (doc.channels);                 }            ,
"users": {
"GUEST": {
"disabled": false,
"admin_channels": ["*"]
}
}
}
}
}
Could you please help me !
Thanks

Hi @phamthai,
It seems sync_gateway question or issue.
If this is a question, please post https://forums.couchbase.com/c/mobile/sync-gateway
If this is a issue, please file the issue against sync_gateway repo? https://github.com/couchbase/sync_gateway/issues
Thanks!

@phamthai yes, please post to https://forums.couchbase.com/c/mobile/sync-gateway


Module build failed, ERROR: Cannot find module @babel/plugin-proposal-private-property-in-object

Describe the bug
(Write your answer here.)
Did you try recovering your dependencies?

(Write your answer here.)
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

(paste the output of the command here.)
Steps to reproduce

(Write your steps here:)

Expected behavior

(Write what you thought would happen.)
Actual behavior

(Write what happened. Please add screenshots!)
Reproducible demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

workaround here:
https://github.com/babel/babel/issues/15655

workaround here: babel/babel#15655

worked..thank you

Same

Same!!!


Segfault when calling nested parallel function with caching

Hi everyone,
I've run into a segfault when calling nested jit functions, specifically if the inner function has parallel=True, and the outer does not. The fault occurs only when caching is enabled for the outer function, and only when running from the cache (not on the first call).
Here is a minimal example which produces this behaviour (when calling outer_fn()):
import numpy as np
import numba

# @numba.njit('f4[:](i8)', parallel=True)  # with specified signature it works
@numba.njit(parallel=True)  # without specified signature it segfaults
def inner_fn(n):
    return np.zeros(n, dtype=np.float32)

@numba.njit(parallel=False, cache=True)
def outer_fn():
    inner_fn(10)

The fault occurs only if the inner function has some parallelizable functionality - e.g. the np.zeros(n) used in the example produces the fault, but np.empty(n) does not.
Could anyone shed any light on why this is occurring?
I'm using
numba==0.56.3
numpy==1.23.4
llvmlite==0.39.1

in a clean virtualenv on Python 3.9.15 with Ubuntu 22.10.
I've attached the output of "numba -s" for additional context.
The example script produces the same fault on Centos 7 with Python 3.9.7 (same package versions).
Any help much appreciated!
Ben
Edit: add the example in-line.
numba_diagnostic.txt
numba_segfault_minimal_example.py.txt

Thanks for the report, I can reproduce the issue by running:
import numpy as np
import numba

# @numba.njit('f4[:](i8)', parallel=True)  # with specified signature it works
@numba.njit(parallel=True)  # without specified signature it segfaults
def inner_fn(n):
    return np.zeros(n, dtype=np.float32)

@numba.njit(parallel=False, cache=True)
def outer_fn():
    inner_fn(10)

outer_fn()

twice.

Problem is caused by missing call to reload_init for the inner_fn.
The reload_init is responsible to setting up the threading backend.
https://github.com/numba/numba/blob/04d4af3ce9ae933cc1b9b8f861886e8794951969/numba/core/typed_passes.py#L274-L280
https://github.com/numba/numba/blob/04d4af3ce9ae933cc1b9b8f861886e8794951969/numba/core/typed_passes.py#L333
A workaround is to manually run _reload_parfor.

Possibly a dupe of https://github.com/numba/numba/issues/4807


yarn is required to install this library with npm

ReactUSWDS Version & USWDS Version:
1.17.0 , USWDS bundled with this
Describe the bug
We recently ran into an issue on a clean install using npm install - full log attached, and relevant excerpt below:
4038 verbose prepareGitDep @trussworks/react-uswds@github:nathillardusds/react-uswds#nathillardusds/ssr: installing devDeps and running prepare script.
4039 error prepareGitDep 1>
4039 error prepareGitDep ><EMAIL_ADDRESS>install /Users/nathillard/.npm/_cacache/tmp/git-clone-72e0de99/node_modules/watchpack-chokidar2/node_modules/fsevents
4039 error prepareGitDep > node install.js
4039 error prepareGitDep
4039 error prepareGitDep   SOLINK_MODULE(target) Release/.node
4039 error prepareGitDep   CXX(target) Release/obj.target/fse/fsevents.o
4039 error prepareGitDep   SOLINK_MODULE(target) Release/fse.node
4039 error prepareGitDep
4039 error prepareGitDep ><EMAIL_ADDRESS>install /Users/nathillard/.npm/_cacache/tmp/git-clone-72e0de99/node_modules/husky
4039 error prepareGitDep > node husky install
4039 error prepareGitDep
4039 error prepareGitDep husky > Setting up git hooks
4039 error prepareGitDep husky > Done
4039 error prepareGitDep
4039 error prepareGitDep ><EMAIL_ADDRESS>postinstall /Users/nathillard/.npm/_cacache/tmp/git-clone-72e0de99/node_modules/@babel/polyfill/node_modules/core-js
4039 error prepareGitDep > node -e "try{require('./postinstall')}catch(e){}"
4039 error prepareGitDep
4039 error prepareGitDep Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
4039 error prepareGitDep
4039 error prepareGitDep The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
4039 error prepareGitDep > https://opencollective.com/core-js
4039 error prepareGitDep > https://www.patreon.com/zloirock
4039 error prepareGitDep
4039 error prepareGitDep Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
4039 error prepareGitDep
4039 error prepareGitDep
4039 error prepareGitDep ><EMAIL_ADDRESS>postinstall /Users/nathillard/.npm/_cacache/tmp/git-clone-72e0de99/node_modules/core-js
4039 error prepareGitDep > node -e "try{require('./postinstall')}catch(e){}"
4039 error prepareGitDep
4039 error prepareGitDep
4039 error prepareGitDep ><EMAIL_ADDRESS>postinstall /Users/nathillard/.npm/_cacache/tmp/git-clone-72e0de99/node_modules/core-js-pure
4039 error prepareGitDep > node -e "try{require('./postinstall')}catch(e){}"
4039 error prepareGitDep
4039 error prepareGitDep
4039 error prepareGitDep ><EMAIL_ADDRESS>postinstall /Users/nathillard/.npm/_cacache/tmp/git-clone-72e0de99/node_modules/husky
4039 error prepareGitDep > opencollective-postinstall || exit 0
4039 error prepareGitDep
4039 error prepareGitDep Thank you for using husky!
4039 error prepareGitDep If you rely on this package, please consider supporting our open collective:
4039 error prepareGitDep > https://opencollective.com/husky/donate
4039 error prepareGitDep
4039 error prepareGitDep
4039 error prepareGitDep ><EMAIL_ADDRESS>prepare /Users/nathillard/.npm/_cacache/tmp/git-clone-72e0de99
4039 error prepareGitDep > yarn build
4040 error prepareGitDep 2> npm WARN install Usage of the `--dev` option is deprecated. Use `--also=dev` instead.
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>The gitlab package has found a new home in the @gitbeaker organization. For the latest gitlab node library, check out @gitbeaker/node. A full list of the features can be found here: https://github.com/jdalrymple/gitbeaker#readme
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>this library is no longer supported
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
4040 error prepareGitDep npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
4040 error prepareGitDep sh: yarn: command not found
4040 error prepareGitDep npm ERR! code ELIFECYCLE
4040 error prepareGitDep npm ERR! syscall spawn
4040 error prepareGitDep npm ERR! file sh
4040 error prepareGitDep npm ERR! errno ENOENT
4040 error prepareGitDep npm ERR<EMAIL_ADDRESS>prepare: `yarn build`
4040 error prepareGitDep npm ERR! spawn ENOENT
4040 error prepareGitDep npm ERR!
4040 error prepareGitDep npm ERR! Failed at the<EMAIL_ADDRESS>prepare script.

(this was on a fork of this repo pointed to by a github:-prefixed path, but it appears the issue exists in the main repo as well)
It appears the issue is in this line:
https://github.com/trussworks/react-uswds/blob/41a1cdc2e3fb96e7db2f7f4f05145798485ce7c6/package.json#L34
which assumes the use of yarn -- we are using npm for our project, and while its a reasonable assumption that folks would have installed yarn, this particular machine didn't have yarn installed and thus encountered this. If we do npm install -g yarn it goes away.
I believe the solution may be to use npm build in the prepare script  instead, but I'm not sure how this is typically handled, so there may be a better way ?
To Reproduce

On clean OS install
clone this project
run npm install with node v. 14.17.1 (installed via asdf but this shouldn't make a difference), and without yarn installed.
See error above

Expected behavior
Should be able to use the npm install toolchain without needing yarn installed
Screenshots
N/A
Additional context
Full install log:
uswds.log
Device and Browser Information (please complete the following information if describing a UI bug):
macOS Big Sur 11.4 (20F71) - M1 Apple Silicon - node v14.17.1 installed via  arch -x86_64 asdf install nodejs 14.17.1
(Updated to use template)

The https://github.com/trussworks/react-uswds/blob/main/docs/contributing.md specifies yarn, which seems fine for building or modifying the library itself. Yarn is pretty common on React projects since create-react-app uses it. I don't know of a lot of projects that can build with either, especially since the two use different lockfiles. Yarn issues a warning if it finds a package-lock.json file since it uses yarn.lock itself.
If react-uswds used as a dependency in a project you should be able to use either npm or yarn there.

(Hi Dave!) - Also though, and apologies for only just getting back to this, and for the initial lack of clarity. The issue is not that react-uswds uses yarn, but rather, we are seeing failures in our own project (henceforth "J40"), which has react-uswds as a dependency and which, itself, only uses npm, when we run an npm build. To your point, If react-uswds used as a dependency in a project you should be able to use either npm or yarn there: it should be possible to install this on a machine without yarn installed, this appears to be the bug.
To repro:

Clone our project, https://github.com/usds/justice40-tool/, on a fresh machine (henceforth J40). cd justice40-tool.
Run npm install. Note that J40 has react-uswds as a dependency
Encounter the above logs / the yarn: command not found error, which is a side effect of prepare cited above, because I don't have yarn installed globally
npm install -g yarn gets around this, but seems odd that I would have to install yarn just in order to install my dependency

Looking for precedent around this, I found this issue, though that being react-native it seems like a slightly different scenario.
There's also this which suggests using yarn-or-npm to work around this. This seems to have a fair number of users and seems to have been designed around this use case. There are also several projects using npm_execpath to test availability.
In any case, we have not seen this with other projects, even those like react itself which uses yarn (see [their https://github.com/facebook/react/blob/main/package.json ) , and there appears to be solutions like the above to this problem, so we thought to call it out. Overall minor, in that it is possible to install yarn on these machines, but seems there are ways around this that other projects have pursued

The most typical thing for libraries to do is to build and publish the artifacts on npm, for example in a dist directory (that is .gitignoreed), rather than having the consuming project do that.

This is our desired approach. From the original post:

(this was on a fork of this repo pointed to by a github:-prefixed path, but it appears the issue exists in the main repo as well)

Since the fork is not pointing to a published artifact, I imagine this is the source of the issue. We can look into supporting this case, but as of right now, the published artifacts should be used, otherwise yarn is required to build the project (directly or transitively, it seems).
@NatHillardUSDS Is the project fork under your control? If so, can you update the package.json in the fork to suit your needs as a workaround if the fork must be used?
Does the fork exist to cover some gap in functionality that this project is currently missing? Perhaps in that case the better long-term solution would be to close that gap and make sure a published npm artifact exists so that the github: url isn't needed.
Any more context around this case would be great to see what level we are able to support this, or what the best solution is 😄.

Hi Brandon -
Thank you for the response! This makes sense, and I had overlooked that this might be the reason why it was attempting to build.
As a bit more context, the fork was originally created to work around this issue - that said, we have since moved away from directly using FooterNav, and are now using the repo directly, rather than the fork.
After moving back to the standard repo / away from our fork, it now works again to run npm i without having yarn installed, and the reasoning you give for this makes sense. It should be OK to close this current issue given this explanation. Thanks again for taking the time to look into this!

I looked into this a few weeks ago but forgot to create a PR for it. I just made #1583 to document what I found. In general that PR can kinda-sorta make npm work for installs from a git commit, but there are some drawbacks that might argue against it. In any case feel free to close this issue and the PR if it seems better to leave things as-is.

@NatHillardUSDS thanks for that additional context! Some maintainers had a conversation about support for issues like https://github.com/trussworks/react-uswds/issues/1488, and it seems we're in agreement: we want to make sure this library is usable for server-side development, so we hope to resolve that issue directly, and come up with some safeguards for introducing code that leads to those types of bugs in the first place 😃
Thanks @dmethvin for making that PR! That's super helpful. We'll get some eyes on it and keep the conversation going!

Given the original question has been resolved and subsequent conversations have split to other issues linked above, I'm going to close this issue. If I missed something that is still unresolved unique to this thread, we can reopen, but I'd suggest opening a new, more specific issue for clarity.


fix(ui): adjust layout and font family of text inside avatar logos

Changelog
Update layout and text size inside the avatar logo for:

profile pages

Before
After

organization cards

Before
After

@vpchung I proposed an alternative solution in #1523 that limits the length of the initials.

Thanks, @tschaffter -- you brought up a good point during the standup that changing the avatar text size was just a bandage, not a solution.
I have since removed the text resizing, but would still like to merge this PR in, as it specifies to use the Lato font instead of Helvetica (consistent with our theme).

Looks good, thanks!


Remove full_document params on post_resource function

No POST APIs on Chino docs containts full_document as query params

This repository has been migrated to https://gitlab.com/chinoio-public/sdk-chino-ruby and will no longer be maintained on GitHub. Please reach out to<EMAIL_ADDRESS>for any question, or if you wish to contribute to the SDK development.


New Extension Suggestion!

Hello!!, I suggest extension idea!!!!
It will be best idea.
If u make for styling web ( css )
what about, you make html one!
it will be big!!!!!! thank you 😁👍🏻

thanks @varenzzzx - maybe i will think about adding support for custom javascript and html in the future. nothing on the horizon though :)


Workflow that runs dash-license tool

          That should be fine (doesn't hurt to double-check with the dash-license tool).

On a related note, I think the dash-license tool now has a maven plugin that we can add into our workflow so these things are automatically checked and reported. https://github.com/eclipse/dash-licenses
Originally posted by @abrokenjester in https://github.com/eclipse/rdf4j/pull/4437#discussion_r1114956175

After license questions in numerous PRs, I am taking a look at this. I think the maven-plugin is still quite "fresh", not even publish - but I think we can start and get the bugs and shortcomings fixed upstream.

I noticed that there is an experimental reusable workflow that the maintainers could consider in a follow-up PR.


Add binary maxpool 2D op

What do these changes do?
This adds the Binary Max Pool 2D op.
Issue #54 is relevant but lets close that once #364 is merged, after this one.
How Has This Been Tested?
Unittests have been added for float input, int8 input and bitpacked input, for many strides and filter sizes.

thanks @Tombana, have you done any benchmarking of this op?

what are the target devices for this op? how much speed up are you expecting compared to the float version?

what are the target devices for this op? how much speed up are you expecting compared to the float/int8 versions on each of these target devices?

Target device is Cortex-M, but the implementation is general.
The speedup we get is not due to this op, but due to the riptide style bconvs that we get from having this, which was already benchmarked, its about 10% or something.
This op itself will also be faster than an int8 maxpool, but I haven't benchmarked that yet, since they were only a small fraction of the total model time for most models that we are interested in. I'll post benchmarks later today.


Add host to devServer config

Just to show where it is so it's easier to change. (My dev env needs <IP_ADDRESS> / 8080 ).

Thank you!


Install script isn't using custom path's

You can customize Zinit paths as mentioned here. Except when you run the install script  the variable ZINIT_HOME is used instead of ZINIT[HOME_DIR].
Here's the culprit:
https://github.com/zdharma/zinit/blob/857d6fb6b46a4043f772315e8184c1b7e22c235e/doc/install.sh#L7-L10
I'm not sure if it's intentional but I expected to be used ZINIT[HOME_DIR] instead of ZINIT_HOME. If this is intentional how does one set a custom home dir for Zinit and plugins to install to?
Versions:

$ZSH_VERSION == 3.5
Operating system name and version (uname -a): Ubuntu 20.04

I'm pretty sure the install script is the only place where ZINIT_HOME is used. You can simply set ZINIT_HOME to the same value as ZINIT[HOME_DIR] before running the script and it should respect this value. As for why the install script uses a regular variable instead of the associative array used by Zinit elsewhere. The install script is written in (almost) POSIX sh which doesn't support associative arrays.

That makes sense I wasn't aware of POSIX sh's lack of support for associative arrays thanks, closing this.


nz-modal with nz-table using fixed columns, the fixed columns do not work

Reproduction link
https://stackblitz.com/edit/angular-grxzhn?file=src%2Fapp%2Fapp.component.ts
Steps to reproduce

click 'test' button
fixed columns in table are abnormal

What is expected?
should have two normal fixed columns
What is actually happening?
abnormal fixed columns

Environment
Info

ng-zorro-antd
18.0.0

Browser
edge 126.0.2592.68

Screenshot:

Hello @xuxzh,
The behavior you've observed with the fixed columns in your table is due to the way the left or right positions of each cell are determined by the widths of the cells that come before them. When your table is placed within a modal that uses an animation upon opening, it can cause the widths of the preceding cells to be calculated incorrectly.
To mitigate this issue promptly, you might want to consider the following solutions:

You could disable the animation of the modal, which may help in preventing the width miscalculation. This can be done by applying the [nzNoAnimation]="true" attribute to your nz-modal.
Another approach is to delay the loading of your modal's content. This can be implemented with the following code: @defer(on timer(240ms)) {}

These suggestions are intended as immediate remedies, and a more in-depth examination is recommended for a permanent resolution.

Thank you ! problem solved


[BUG] org.opensearch.indices.store.IndicesStoreIntegrationIT.testShardActiveElsewhereDoesNotDeleteAnother with remote store enabled is flaky

Describe the bug
org.opensearch.indices.store.IndicesStoreIntegrationIT.testShardActiveElsewhereDoesNotDeleteAnother
com.carrotsearch.randomizedtesting.UncaughtExceptionError: Captured an uncaught exception in thread: Thread[id=2648, name=opensearch[node_t1][remote_refresh_retry][T#1], state=RUNNABLE, group=TGRP-IndicesStoreIntegrationIT]
	at __randomizedtesting.SeedInfo.seed([D0CBB573CE1C86B1:636A211921CEDAC3]:0)
Caused by: org.opensearch.core.concurrency.OpenSearchRejectedExecutionException: rejected execution of java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@299ba45c[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@11232e88[Wrapped task = [threaded] org.opensearch.index.shard.ReleasableRetryableRefreshListener$$Lambda/0x00007f39bcba8f88@53ce2a03]] on org.opensearch.threadpool.Scheduler$SafeScheduledThreadPoolExecutor@641c0c3b[Shutting down, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 15]
	at __randomizedtesting.SeedInfo.seed([D0CBB573CE1C86B1]:0)
	at app//org.opensearch.common.util.concurrent.OpenSearchAbortPolicy.rejectedExecution(OpenSearchAbortPolicy.java:67)
	at java.base@21.0.2/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:841)
	at java.base@21.0.2/java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:340)
	at java.base@21.0.2/java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:562)
	at app//org.opensearch.threadpool.ThreadPool.schedule(ThreadPool.java:469)
	at app//org.opensearch.index.shard.ReleasableRetryableRefreshListener.scheduleRetry(ReleasableRetryableRefreshListener.java:125)
	at app//org.opensearch.index.shard.ReleasableRetryableRefreshListener.scheduleRetry(ReleasableRetryableRefreshListener.java:178)
	at app//org.opensearch.index.shard.ReleasableRetryableRefreshListener.runAfterRefreshWithPermit(ReleasableRetryableRefreshListener.java:167)
	at app//org.opensearch.index.shard.ReleasableRetryableRefreshListener.lambda$scheduleRetry$2(ReleasableRetryableRefreshListener.java:126)
	at app//org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:854)
	at java.base@21.0.2/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base@21.0.2/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base@21.0.2/java.lang.Thread.run(Thread.java:1583)

Related component
Storage:Durability
To Reproduce
See https://github.com/opensearch-project/OpenSearch/pull/12817
Expected behavior
Test always passes.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

[Triage - attendees 1 2 3 4 5 6 7]
@dblock Thanks for creating this issue.

This got fixed with https://github.com/opensearch-project/OpenSearch/pull/13301.
tests were run 9000+ times, and the issue did not reproduce.


A guide of PowerToys shortcuts

Description of the new feature / enhancement
The behaviour is exactly the same as the actual configuration of Windows shortcuts, but adding the PowerToys shortcuts.
Scenario when this would be used?
You don't remember how to enable (for example) FancyZones, so you activate this shortcut (you will have to remember it) and you can see which shortcut is for FancyZones.
Supporting information
No response

Duplicate of #15405

Thanks for your suggestion! This issue is a duplicate.
I'm linking this issue to #15405 to centralize the discussion thread, please go to that thread for discussion.
Thanks for your help to make PowerToys a better piece of software!


PS move and eye don't work after build

When i build the game on windows it doesn't work at all, showing the debug the error message
"failed to load library assets/plugins/x86_64/psmoveapi.dll" shows, i tried to build 32bit but the same error message shows even if i copied the dlls to the plugin folder in the build, i also tried to copy the dlls to a folder named "x86_64" it then crashes the whole build.
can you help me

I also have this problem. Could you help us?

So the version of psmoveapi I built is 64-bit (so that it will run in the editor. I can build a 32-bit version of the dll as well this weekend. Sorry I hadn't replied to this issue in a while (out of town on business).

This is also an issue for me. I'll be awaiting an update on this, thanks! :)

Ok. I believe I finally have this fixed with this check-in 18dd8e13bc6bcbeeca14eaa47b1c2c33e1015446:

I made a 32-bit build of my fork of psmoveapi and put the newly built dlls/utilities in assets/plugins/x86
Fixed some path issues in the dll loading code that was causing the manual dll loading to not work in standalone builds
Tested in editor (which is 64-bit on my machine) and with x86 and x86_64 standalone builds.

Sorry this took me so long to getting around to fixing. Please let me know if this fix works or not for you guys. If all looks good I'll close this issue.

Thanks for the commit. Unfortunately, it's not working for me. (Win10, Unity 5.3.41f)
When I run the built demo scene in this repository, it crashes. It still works running in editor mode. I'm going to email you my output_log files that the crash generated in case that helps you. Thanks man.

So after digging into that crash some more it appears that it's an issue deep inside libusb trying and failing to acquire the usb device (Specifically getting a failure code when calling WinUSB_Initialize on a device handle for the camera). I couldn't find any documentation online that would explain precisely what would lead to this failure (Error code 87). The two common causes I heard suggested where either the device thinking it was already open by another application or a bad driver associated with the usb device. You might try re-applying the libusb driver to the camera and see if that helps. In the mean time I checked in new 32 and 64 bit binaries (2196bd9482a9fc94ff4bbd35462c403cdce645b4) that handle the camera failure initialization case more gracefully. In your situation it'll still fail to acquire the camera, but at least you won't crash.

Alright thanks for digging man. Must be frustrating relying on such strange
dependencies. I'll just stick to the 64-bit build since that decided to
work for now.
By the way, any ideas of when that new revised package for psmove will be
coming out? I think I heard about that sometime...
On Sat, Apr 2, 2016 at 6:06 AM, Guido Sanchez<EMAIL_ADDRESS>wrote:

So after digging into that crash some more it appears that it's an issue
deep inside libusb trying and failing to acquire the usb device
(Specifically getting a failure code when calling WinUSB_Initialize on a
device handle for the camera). I couldn't find any documentation online
that would explain precisely what would lead to this failure (Error code
87). The two common causes I heard suggested where either the device
thinking it was already open by another application or a bad driver
associated with the usb device. You might try re-applying the libusb driver
to the camera and see if that helps. In the mean time I checked in new 32
and 64 bit binaries (2196bd9
https://github.com/HipsterSloth/psmove-unity5/commit/2196bd9482a9fc94ff4bbd35462c403cdce645b4)
that handle the camera failure initialization case more gracefully. In your
situation it'll still fail to acquire the camera, but at least you won't
crash.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/HipsterSloth/psmove-unity5/issues/19#issuecomment-204686226

@hazem17 I you get a chance would you mind syncing latest and seeing if either the 32 or 64 bit builds work for you.
@Ideae Yeah libusb can bit frustrating to work with sometimes, but it's the best option for cross platform usb support at the moment (that I know about anyway).
As for the revised package for psmoveapi (a.k.a. the PSMoveService), it's hard to say when it'll be done as myself and cboulay can only work on it our free time, which has been in fits and spurts lately. We currently have a service framework running that connects to psmove controllers, ps3eye cameras, and an HMD and then networks the data to either a C++ client dll plugin or to a config client that combines all of the calibration tools into one visual tool. That said there is still a fair bit of work remaining including: porting over the positional tracking (not doing anything with the video frames read from the PS3EYE at the moment), HMD/PS3EYE coregistration, and updating psmove-unity5 and psmove-ue4 to use the new client dll. Rather than re-write the Unity and UE4 plugins I'm thinking about making an OpenVR plugin instead, which I think would eliminate the need to a separate psmove plugin (since both Unity and Unreal have OpenVR tracked controller support). At minimum it's probably another month of work before we can have something publicly available. That's actually why I'm working on multi-cam positional tracking now in psmoveapi rather than the new service since people can try it out sooner.

An OpenVR plugin sounds great! I'm actually waiting to get my Vive right now. When that happens, I'll be moving over to OpenVR (SteamVR), so I can have both the Vive and DK2 work. When the Vive is available, obviously my application would use the Vive controllers, but if only the DK2 is available, it would be nice to have the PSMove controllers also work!

The 64 bit build works great, but the 32 bit still crashes, i used unity 5.3.1 64 bit to build the project.

@hazem17 Does the 32-bit version of ps3eye_sdl.exe crash for you as well in the assets/plugins/x86 folder? If so is there an error code in the output window it gives? I'm wondering if you get the same libusb error message Ideae was getting.

yes is crashes and gives me this error message: libusb: error [winusbx_claim_interface] could not access interface 0: [87] The parameter is incorrect.


谁可以看免费的资源你懂的参数问题

关于谁可以看免费的资源你懂的参数问题
>>>>>>点/此/进/入/最/新/观/看/入/口<<<<<<
网从高空砸下不偏不倚重重地砸在小伙伴阿新稚嫩的肩上父亲再也不让山娃上工地玩了有一天因为过于思念小伙伴山娃还偷心

你可以将谁可以看免费的资源你懂的参数问题	夏月鲜明，清辉下的沩江宁静诱人，煦风轻拂，除有游艇偶然划过，夜色宽厚，场合宁静。楼群、桥梁、人潮，绿树、亭台、楼阁，逐一被月色披上一层矇眬轻纱，本影成江水波粼闪耀。每到黄昏，沩江两岸的得意啊，老是如画如诗。

你能看到免费资源来理解问题的参数
"Of the ping's started said, gion bell, resort to Chen line imp.
The sankharas imp, and the method of a dream I, kung fu is might as well go back, returned to grandma means last night.
All diamond sutra: every phase, it is impossible that if in the phase of phase, namely, see such as come.
The old grandma to grandpa said, you lost a well caught a glimpse of the east gate, from Simon in the past?
, flood, earth woman corpse, grandpa at the moment I decided to determine in the phase of phase, caught a glimpse of the east gate of the Wells, from Simon in the past, my grandfather also caught a glimpse of the Buddha.

请参考下方链接：
https://github.com/dedesew/mzbeqda/issues/1
https://github.com/makedete/vtqpbbo/issues/1
https://github.com/tryuits/oif-xakru
https://github.com/tuderw/kxt-kxtge
https://github.com/tuderw/ooc-oocmq/issues/2
https://github.com/aoyouzg/cmfqgm/issues/4
https://github.com/chiquane/jobie/issues/3
https://github.com/goodiders/sexrk/blob/main/README.md
https://github.com/powercvt/rsq-rsqgb/blob/main/README.md
https://github.com/tooere/tncfm/issues/1
https://github.com/dedesew/xmsaai/issues/3
https://github.com/nyueed/pgyg/issues/1
https://github.com/tooere/tgdtewn/issues/6
https://github.com/dedesew/afnjcd/issues/5
https://github.com/aoyouzg/bgabe/issues/4
https://github.com/goodiders/jdqizaq/issues/2
https://github.com/tuderw/guxogk
https://github.com/goodiders/lnlxbim
https://github.com/nyueed/dtmcscl
https://github.com/dedesew/mzbeqda/blob/main/README.md


Telemetry improvement: Create telemetry item for completion of a resource name

In order to scope our problem to the most common resources #6249, it would be great to be able to track, what are the most common completions for "resource blah '_____'". This is the case where a user is trying to find the correct resource tag after they have named it.
Related to #6327
Partial Blocker for #6249

The name of this event will be vscode-bicep/snippet/resourcetype

Telemetry should include resource type as well as the version they select (if possible), islatest flag for if it is the lastest version available


fix: s/recieve/receive

Description

Closes https://github.com/ourzora/v3/issues/138
Motivation and Context

This updates the reciever var to its correct spelling.
How has this been tested?

yarn test

thanks!


[Request] possible options to add please

I had a few ideas for things that would make it even better. My number 1 would be to be able to push the enter key instead of having to use the mouse. The second one would be to be able to use custom llms like quivr or privategpt, things like that.

you can use cmd+enter to submit instead of using the mouse!

you can use cmd+enter to submit instead of using the mouse!

awesome, thanks for the tip.


Link to new BattleSnake game downloader CLI tool

Even though BattleSnake game downloader is lexicographically higher than cbinners/battlesnake-download-tool, I've placed it below because:

It makes sense to list browser extensions together.
Browser extensions are easier to use than a hardcore CLI tool and thus should be listed first.
battlesnake-download-tool is lexicographically higher if we ignore case and consider dashes equal to spaces :)

Thank you for the contribution!
Regarding the lexicographical ordering, I understand your point. I think I will edit this section to put the title of the tool before the contributor's name so that it is sorted by resource and name and not GitHub usernames.
I'll merge this soon. Thanks again!


Regenerate the self-signed SSL cert for tests.

It had expired in July 2017. Fixes #42.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #43   +/-   ##
=======================================
  Coverage   95.69%   95.69%
=======================================
  Files          29       29
  Lines        2971     2971
=======================================
  Hits         2843     2843
  Misses        128      128

Continue to review full report at Codecov.

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

If we're storing a self-signed cert, does the new one expire in longer than a year?

The new one lasts three years, at which point I hope we will have at least rewritten these tests. (The regeneration commands are listed in #42.)


Datetimes are now saved in UTC with the eastern timezone

Timezones were saved in UTC but being treated in code as eastern. Now, they are saved as UTC with their hour difference applied as is best practice. For example, before this change 4:00am was saved as 04:00:00 UTC and now 12:00am is saved as 08:00:00 UTC and Django will apply the eastern timezone when appropriate. See this for more details on the settings.
This also changes the block types that are used in EventPage AgendaItemBlock's and ItemIntroduction blocks. Before, they were unnecessarily using DateTimeBlock's and now they use their appropriate block types.
Additions

A new migration that changes the block types and migrates the datetimes on the pages to the appropriate values.

Changes

The timezone is now America/New_York and dates displayed in templates and input into forms will be treated as such.

Testing

Preferably start with a fresh database dump
Before pulling down
Go to the homepage and see dates in latest updates
Go to http://localhost:8000/about-us/events/archive-past-events/fall-community-bank-advisory-council-meeting-in-washington-dc/
see the start date and agenda times
After pulling down
run cfgov/manage.py migrate
Go to the homepage and see dates in latest updates unchanged
Go to http://localhost:8000/about-us/events/archive-past-events/fall-community-bank-advisory-council-meeting-in-washington-dc/
witness that they haven't been affected on the frontend
open a shell
run:

page = EventPage.objects.get(slug='fall-community-bank-advisory-council-meeting-in-washington-dc')
print page.start_dt

witness page.start_dt is saved as UTC with hour difference applied.
create a new EventPage with a future start time and agenda items with times
publish and see all the times are correct

Review

@kave
@richaagarwal
@rosskarchner

TODO

Later add the timezone selection for events and logic to handle different timezones

Checklist

[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the front end playbook
[x] Passes all existing automated tests
[x] New functions include new tests
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged
[x] Visually tested in supported browsers and devices
[x] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

This looks great. I'm going to test it locally.
It's worth noting (for anyone else that hasn't been following this closely) that this fixes some of the issues we were seeing before by getting rid of DateTimeBlock fields entirely. Just something to be aware of if we ever plan on reintroducing those.

Thanks for pointing that out!

Added a TODO

I can confirm the testing instructions work.

In order to get times to appear correctly on the leadership calendar (per #2198), I tweaked _convert_date  (in sheerlike/templates.py) to do timezone conversion. It seems like maybe it was always supposed to do that (why else would it take a timezone argument)?
def _convert_date(date, tz):
    if date and isinstance(date, basestring):
        date = parser.parse(date,
             default=datetime.datetime.today().replace(day=1))
             if isinstance(date, datetime.datetime) and tz:
                 this_tz = timezone(tz)
                 return date.astimezone(this_tz)
         return date

(the if isinstance block is what I added)
I think this PR is the place to make such a change

Thanks for the hard work on this @kurtw ! It looks like all the issues have been addressed, so 👍

Oh, and probably the CHANGELOG should be updated.

Haha I always do that last now since it ALWAYS gets updated. Updating then merging!!


Allow Multiple Package Protocol Buffer Generation

Scope of changes
Modifies how we do protocol buffer generation to allow the go-ensign package to correctly generate protocol buffers. This modification is super annoying but I've worked on this for almost 3 hours now and I think this is the best we can do.
Fixes SC-14968
Type of change

[ ] new feature
[ ] bug fix
[ ] documentation
[ ] testing
[x] technical debt
[ ] other (describe)

Acceptance criteria
Check to make sure this makes sense. Do we want a bash script like in the go-ensign repo?
NOTE: this PR blocks https://github.com/rotationalio/go-ensign/pull/5
Author checklist

[x] I have manually tested the change and/or added automation in the form of unit tests or integration tests
[ ]  I have updated the dependencies list
[x]  I have recompiled and included new protocol buffers to reflect changes I made
[ ]  I have added new test fixtures as needed to support added tests
[x]  Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
[x]  I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

[ ] Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.
[ ] Are there any TODOs in this PR that should be turned into stories?

I think this makes sense @bbengfort -- is the idea that we'll generate the protocol buffers here in ensign as well as in the SDK repos, and that in go-ensign we'll import the compiled pbs from go-ensign so we don't have a service definition conflict between the two versions of the compiled pbs?

Yes, we're trying to separate concerns so that ensign and go-ensign have independently generated protocol buffer code and that these scripts ensure they're kept up to date through the same generation process (trying to prevent recursive imports).


how can I create a connetion of pp2p which using c/c++ on windows?

[Enter feedback here]

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

ID: f2dbc342-5e8a-1686-cb4d-c41cce743011
Version Independent ID: 2ec5bb36-6bb8-96f8-a610-d0788b708667
Content: NDISWAN Overview - Windows drivers
Content Source: windows-driver-docs-pr/network/ndiswan-overview.md
Product: windows-hardware
Technology: network
GitHub Login: @aviviano
Microsoft Alias: amvivian

Thanks for reaching out to the Windows Driver Developer Documentation team.  You may have success posting your question in the following forums, where other driver developers and Microsoft engineers can be found. The community there is quite responsive.

windows-hardware-wdk
OSR's NTDEV forum


Admin UI client side field validation hook

For example, a Password field should validate the two password fields match, and if not, add an error to be displayed plus abort the creation.
Perhaps there's also a "warning" which aborts the creation on the first pass, but allows it to be ignored completely.
Perhaps we also implement all of the hooks client side:
  hooks: {
    resolveInput: async (...) => { ... },
    validateInput: async (...) => { ... },
    beforeChange: async (...) => { ... },
    afterChange: async (...) => { ... },
    beforeDelete: async (...) => { ... },
    validateDelete: async (...) => { ... },
    afterDelete: async (...) => { ... },
  },

Field's currently already have a serialise (which is essentially the resolveInput hook), and this issue is about the validateInput hook. Why not all the others?

🤔 What order should these hooks be executed in?
Looking at the Password field type, it has two inputs for a "confirm your password" style UI (inputPassword and inputConfirm):
https://github.com/keystonejs/keystone-5/blob/master/packages/fields/src/types/Password/views/Field.js#L41
Currently, there is no validation, so we want to use the validateInput() as suggested in this issue to check they're the same:
export default class PasswordController extends FieldController {
  validateInput = ({ resolvedData, addFieldValidationError }) => {
    if (!resolvedData[this.path].password !== resolvedData[this.path].confirm) {
      addFieldValidationError('Passwords do not match');
    }
  }
}

But, the field only accepts a single value (of type String) for its create mutation:

Which means we have a serialize step (roughly equivalent to the server-side resolveInput()):
export default class PasswordController extends FieldController {
  serialize = (data) => {
    // discard the "confirm" since we only need one version of the password
    return data[this.path].password;
  }

  validateInput = ({ resolvedData, addFieldValidationError }) => {
    if (!resolvedData[this.path].password !== resolvedData[this.path].confirm) {
      addFieldValidationError('Passwords do not match');
    }
  }
}

But the order of execution is:

serialize()
validateInput()

So our validateInput() cannot ever get access to the


Add numpy

Signed-off-by: junjiejiangjjj<EMAIL_ADDRESS>

Codecov Report

Merging #954 (f2f6d3e) into main (49c4a99) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #954      +/-   ##
==========================================
- Coverage   68.89%   68.84%   -0.06%
==========================================
  Files         206      206
  Lines        9112     9112
  Branches     1505     1505
==========================================
- Hits         6278     6273       -5
- Misses       2401     2406       +5
  Partials      433      433

Impacted Files
Coverage Δ

towhee/dataframe/dataframe.py
73.10% <0.00%> (-1.05%)
:arrow_down:

towhee/hub/repo_manager.py
80.18% <0.00%> (-0.91%)
:arrow_down:

Continue to review full report at Codecov.

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

@junjiejiangjjj the change in this pr has no effect.
update the change in Pypi website also


[SPARK-28468][INFRA][2.4] Upgrade pip to fix sphinx install error

What changes were proposed in this pull request?
Spark 2.4.x should be a LTS version and we should use the release script in branch-2.4 to avoid the previous mistakes. Currently, do-release-docker.sh fails at sphinx installation to Python 2.7 at branch-2.4 only. This PR aims to upgrade pip to handle this.
$ dev/create-release/do-release-docker.sh -d /tmp/spark-2.4.4 -n
...
= Building spark-rm image with tag latest...
Command: docker build -t spark-rm:latest --build-arg UID=501 /Users/dhyun/APACHE/spark-2.4/dev/create-release/spark-rm
Log file: docker-build.log
// Terminated.

$ tail /tmp/spark-2.4.4/docker-build.log
Collecting sphinx
  Downloading https://files.pythonhosted.org/packages/89/1e/64c77163706556b647f99d67b42fced9d39ae6b1b86673965a2cd28037b5/Sphinx-2.1.2.tar.gz (6.3MB)
    Complete output from command python setup.py egg_info:
    ERROR: Sphinx requires at least Python 3.5 to run.

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-2tylGA/sphinx/
You are using pip version 8.1.1, however version 19.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.

The following is the short reproducible step.
$ docker build -t spark-rm-test2 --build-arg UID=501 dev/create-release/spark-rm

How was this patch tested?
Manual.
$ docker build -t spark-rm-test2 --build-arg UID=501 dev/create-release/spark-rm

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/testing-k8s-prb-make-spark-distribution-unified/13100/
Test PASSed.

Test build #107991 has started for PR 25226 at commit e4ae98c.

cc @dbtsai , @srowen , @gatorsmile , @HyukjinKwon

BTW, @gatorsmile . Did you use branch-2.4 branch script or master branch script at 2.4.3 release? I'm wondering if this is a new situation after 2.4.3.

Test build #107991 has finished for PR 25226 at commit e4ae98c.

This patch fails due to an unknown error code, -9.
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/107991/
Test FAILed.

retest this please

Test build #107993 has started for PR 25226 at commit e4ae98c.

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/testing-k8s-prb-make-spark-distribution-unified/13103/
Test PASSed.

Thank you for retriggering, @HyukjinKwon .

Test build #107993 has finished for PR 25226 at commit e4ae98c.

This patch fails Spark unit tests.
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/107993/
Test FAILed.

retest this please

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/testing-k8s-prb-make-spark-distribution-unified/13120/
Test PASSed.

Test build #108010 has started for PR 25226 at commit e4ae98c.

Test build #108010 has finished for PR 25226 at commit e4ae98c.

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/108010/
Test PASSed.


Error occured while generating docs

Visual Studio code prints following message when I try to use the AI doc writer for any function:
Error occured while generating docs
Even for simple python functions like:
def test():     print("Hello World!")
System specs:
Windows 10 Enterprise Build 21H1
Visual Studio Code Version 1.63.2
AI Doc Writer v1.5.1 (Last updated on 24.1.2022, 22:45:04)

@tapsy0 we've been experiencing a delayed response from our supporting services. We're working around the clock to fix this as quickly as possible.
Thank you for your patience!

@tapsy0 we believe the issue has been resolved. Thank you for pining us the situation!


Chrome w/401 error, Authentication Required Popup

I implemented the code (attached below) to route restful calls to another server where they get processed.  It works terrific by the way, until the other server throws a 401 error.   Firefox correctly processes subsequent javascript, sees the 401 and brings the user back to our login page.  Chrome pops up an "Authentication Required" box asking for a UserName and password.  While the pop-up is there, the GET calls show as pending in the Chrome debugger and then finally show as 401 errors when I cancel the popup.
Do I need to do something special to pass 401 errors to Chrome and prevent this popup from happening?
app.use('/rest', function(req, res) {
  var request = require('request');
  var url = backendConfiguration.servicesBaseUrl + '/rest'+ req.url;
  var r = request(url);
  req.pipe(r).pipe(res);
});

var r = request(url, {auth: {user: 'username', pass: 'password'}});

Thanks @simov , but I am already passing Basic auth via the req.  In this case the other Server has rejected those credentials (because they are expired) and throws a 401 error.  I want to pass that 401 to some javascript which will take the user to another page (not show a popup to the user).  Again, this is fine with Firefox but not Chrome.

app.use('/rest', function(req, res) {
var r = request(url)
.on('response', function(response) { })
.on('error', function(response) {
console.log("crikey error!");
response.statusCode = 406;
})
.pipe(res);
});
Hi again.  So I have tried several different things and the above code seems to do exactly what I need, I can catch the error response and change the error code.  Unfortunately I lose all the benefits of the data in my original request.  The headers,  any form data, auth properties, etc.  With my original "req.pipe(r).pipe(res)" I didn't have to do anything at all.   I don't have to manually copy all of that out of the request I hope?  Perhaps I am missing something?

I went with the chained approach and copied all the stuff I needed from the original request (it took awhile to figure out what I needed).   Closing this issue and attaching the code I used in case it can be of use to anyone else.
app.use('/rest', function (req, res)
{
var url = backendConfiguration.servicesBaseUrl + '/rest' + req.url;
var options = {
url: url,
method: req.method,
json: true,
body: req.body,
headers: {
'Authorization' : req.headers.authorization,
'Accept': "application/json",
'Content-Type': "application/json"
}
};
var r = request(url, options)
.on('response', function (response)
{
if (response.statusCode === 200)
{
}
if (response.statusCode === 401)
{
console.log("401 error received");
res.statusCode = 470;
res.end(response.text);
}
})
.on('error', function (response)
{
console.log("error received: " +  response.text + " code: " + response.statusCode );
if (response.statusCode === 401)
{
res.statusCode = 470;
res.end(response.text);
}
})
.pipe(res);
});


Fix issues that throw exceptions

See https://github.com/AnalyticalGraphicsInc/gltf-vscode/issues/181

Thanks @bghgary!  I think the hack is fine for now.  Nothing in this VSCode extension should be attempting to write to Electron's localStorage ever.


feat(rollup): Allow Environment Variables to override config.json

Purpose or design rationale of this PR
The goal is to allow the rollup-relayer and gas oracle to be configured using environmental variables (in addition to the config.json file).
Here, variables are prefixed with SDKROLLUP_ which might not be a good design.
In the short term, this allows us to pass the config.json file as non-sensitive data, and use alternative ways of loading secrets into a running docker container. Specifically, we'll focus on private keys and database credentials.
I have not run this code in the Scroll SDK stack, and only a minimal test has been run to see if it works. This at least shows the string is being used as though it came from the JSON file.
❯ export SDKROLLUP_DB_CONFIG_DSN=postgres://postgres:azerty12345@postgresql-rollup:5432/scroll?sslmode=disable
❯ ./build/bin/gas_oracle --config ./conf/config.json
ERROR[08-20|13:44:18.305] gorm                                     err message="failed to initialize database, got error failed to connect to `host=postgresql-rollup user=postgres database=scroll`: hostname resolving error (lookup postgresql-rollup on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:54234-><IP_ADDRESS>:53: i/o timeout)"
CRIT [08-20|13:44:18.305] failed to init db connection             err="failed to connect to `host=postgresql-rollup user=postgres database=scroll`: hostname resolving error (lookup postgresql-rollup on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:54234-><IP_ADDRESS>:53: i/o timeout)"

Usage
// To override db_config.dsn:
// Set the environment variable SDKROLLUP_DB_CONFIG_DSN
// Example: export SDKROLLUP_DB_CONFIG_DSN="postgres://new-host/new-db?sslmode=disable"

// To override private keys:
// Set the environment variable SDKROLLUP_L1_CONFIG_RELAYER_CONFIG_GAS_ORACLE_SENDER_PRIVATE_KEY
// Example: export SDKROLLUP_L1_CONFIG_RELAYER_CONFIG_GAS_ORACLE_SENDER_PRIVATE_KEY="new_private_key_here"

// Set the environment variable SDKROLLUP_L2_CONFIG_RELAYER_CONFIG_GAS_ORACLE_SENDER_PRIVATE_KEY
// Example: export SDKROLLUP_L2_CONFIG_RELAYER_CONFIG_GAS_ORACLE_SENDER_PRIVATE_KEY="new_private_key_here"

// Set the environment variable SDKROLLUP_L2_CONFIG_RELAYER_CONFIG_COMMIT_SENDER_PRIVATE_KEY
// Example: export SDKROLLUP_L2_CONFIG_RELAYER_CONFIG_COMMIT_SENDER_PRIVATE_KEY="new_private_key_here"

// Set the environment variable SDKROLLUP_L2_CONFIG_RELAYER_CONFIG_FINALIZE_SENDER_PRIVATE_KEY
// Example: export SDKROLLUP_L2_CONFIG_RELAYER_CONFIG_FINALIZE_SENDER_PRIVATE_KEY="new_private_key_here"

PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[ ] build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
[ ] ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
[ ] docs: Documentation-only changes
[x] feat: A new feature
[ ] fix: A bug fix
[ ] perf: A code change that improves performance
[ ] refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
[ ] style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
[ ] test: Adding missing tests or correcting existing tests

Deployment tag versioning
Has tag in common/version.go been updated or have you added bump-version label to this PR?

[x] No, this PR doesn't involve a new deployment, git tag, docker image tag
[ ] Yes

Breaking change label
Does this PR have the breaking-change label?

[x] No, this PR is not a breaking change
[ ] Yes

BTW, what's the rationale of scroll-sdk needing ENV ? since there are some many options for rollup_realyer and gas_oracle

Adjusted prefix to SCROLL_ROLLUP to not be SDK specific.

Codecov Report
Attention: Patch coverage is 29.93197% with 103 lines in your changes missing coverage. Please review.

Project coverage is 52.26%. Comparing base (7c95208) to head (1032fcb).

Files
Patch %
Lines

coordinator/internal/config/config.go
25.67%
49 Missing and 6 partials :warning:

rollup/internal/config/config.go
34.24%
43 Missing and 5 partials :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1489      +/-   ##
===========================================
- Coverage    52.52%   52.26%   -0.27%
===========================================
  Files          156      156
  Lines        12528    12675     +147
===========================================
+ Hits          6580     6624      +44
- Misses        5382     5474      +92
- Partials       566      577      +11

Flag
Coverage Δ

bridge-history-api
71.16% <ø> (ø)

coordinator
17.77% <25.67%> (+0.38%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Feature Request - Windows Support

First-off, love this GitHub action! I've been using it to build for device and would like to use it for the Windows simulator.
I have a custom set up now that works using WinGet. Sharing learnings here in hopes that they can be adapted for this project!
#          ...
      build:
        runs-on: windows-latest
#          ...
      # https://github.com/microsoft/winget-cli/issues/1861
      # https://github.com/microsoft/winget-cli/issues/700
      - name: Install WinGet
        run: |
          Import-Module -Name Appx -UseWindowsPowerShell
          Invoke-WebRequest -Uri https://www.nuget.org/api/v2/package/Microsoft.UI.Xaml/2.7.3 -OutFile .\microsoft.ui.xaml.2.7.3.zip
          Expand-Archive .\microsoft.ui.xaml.2.7.3.zip
          Add-AppxPackage .\microsoft.ui.xaml.2.7.3\tools\AppX\x64\Release\Microsoft.UI.Xaml.2.7.appx
          $progressPreference = 'silentlyContinue'
          $latestWingetMsixBundleUri = $(Invoke-RestMethod https://api.github.com/repos/microsoft/winget-cli/releases/latest).assets.browser_download_url | Where-Object {$_.EndsWith(".msixbundle")}
          $latestWingetMsixBundle = $latestWingetMsixBundleUri.Split("/")[-1]
          Write-Information "Downloading winget to artifacts directory..."
          Invoke-WebRequest -Uri $latestWingetMsixBundleUri -OutFile "./$latestWingetMsixBundle"
          Invoke-WebRequest -Uri https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx -OutFile Microsoft.VCLibs.x64.14.00.Desktop.appx
          Add-AppxPackage Microsoft.VCLibs.x64.14.00.Desktop.appx
          Add-AppxPackage $latestWingetMsixBundle
          $latestWingetLicenseUri = $(Invoke-RestMethod https://api.github.com/repos/microsoft/winget-cli/releases/latest).assets.browser_download_url | Where-Object {$_.EndsWith("License1.xml")}
          $latestWingetLicenseBundle = $latestWingetLicenseUri.Split("/")[-1]
          Invoke-WebRequest -Uri $latestWingetLicenseUri -OutFile "./$latestWingetLicenseBundle"
          Add-AppxProvisionedPackage -Online -PackagePath .\$latestWingetMsixBundle -LicensePath .\$latestWingetLicenseBundle -Verbose

#          ...

      - name: Install PlaydateSDK
        run: winget install --version 1.13.7 Panic.PlaydateSDK --silent --accept-source-agreements

#          ... some other step PLAYDATE_SDK_PATH=C:\Users\runneradmin\Documents\PlaydateSDK

Some additional notes:

SDK installs to Documents by default, I didn't look into obtaining the path dynamically.
omitting --version to take the latest will bring down beta SDK v2
Path resolution for folders like ${{ runner.temp }} get messed up when using shell: bash in the windows runner.

Those are dependencies of WinGet specifically.
As for use case: For me it's developing games in C with build and test-validation with for both the simulator and device (underlying c calls do vary when cross-compiled for the device!).

Slightly off-topic: a couple of months ago, I was surprised that there's no action available on the GitHub Marketplace, which lets you install or use winget. Also, I find it surprising that the Windows Server version used in workflows doesn't come with winget installed, even though the retail version doesn't include it. Other platforms seem to use modified images, e.g. macOS comes with brew pre-installed. Do you happen to know more about this?

Looks like there's finally an action for installing Winget on the GitHub Marketplace
https://github.com/marketplace/actions/install-winget


Symbol override

Hello @kenmoore, nice plugin but not working when I create button symbol and try use plugin button resized but text not overridden. Fix please correct work with symbols and text override. Thank You!
Link to example - https://dl.dropboxusercontent.com/s/sev2wreax3ub3sp/2017-05-10 at 15.52.png

Hi @svitelskyi, I just updated the plugin to work with Sketch 44 (they made some data structure changes that broke the plugin).  Give it a try and let me know if you hit any snags.  Thanks.

Does this update to Sketch 44 break Sketch 43? I am having the same problem on v43. Works on folder but not on symbol.

@Tharon-C sorry, it's not a goal of mine to support prior releases -- it's tedious enough to support each new release as they deprecate APIs.

No worries, just making sure it's not me. Thank you for a super useful tool. Enough to get me to upgrade.


automation: report test coverage

Changes introduced with this PR
Run tests with coverage and upload the report as artifact.

By contributing to this repository, I agree to the contribution guidelines.
Signed-off-by: Sandro Bonazzola<EMAIL_ADDRESS>

Last execution results:
Coverage report: 82%
coverage.py v6.4.4, created at 2022-09-09 15:29 +0000

Module
statements
missing
excluded
coverage

example_plugin.py
30
1
0
97%

src/arcaflow_plugin_sdk/init.py
0
0
0
100%

src/arcaflow_plugin_sdk/_http.py
85
65
0
24%

src/arcaflow_plugin_sdk/jsonschema.py
17
0
0
100%

src/arcaflow_plugin_sdk/plugin.py
152
64
0
58%

src/arcaflow_plugin_sdk/schema.py
1731
338
0
80%

src/arcaflow_plugin_sdk/serialization.py
44
25
0
43%

src/arcaflow_plugin_sdk/test_jsonschema.py
29
2
0
93%

src/arcaflow_plugin_sdk/test_plugin.py
33
1
0
97%

src/arcaflow_plugin_sdk/test_schema.py
722
11
0
98%

test_example_plugin.py
16
0
0
100%

Total
2859
507
0
82%

No items found using the specified filter.
coverage.py v6.4.4, created at 2022-09-09 15:29 +0000

@sandrobonazzola can you possibly add this to display the code coverage? https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/

Thanks for sharing this article! Done.


just pretending to work

pretending to review and pretending to not like this, so pretending to close this, nice pretend work


Good Project But Not Working... ( it runs but it just suicide )

Ok, so for everyone that have the issue that bot is not moving or it just stop or it hide on invisible bush. Idk why this happening but the owner need to fix it.
I'll try to make a fix to this and try to contact the owner.

@wqq-z tu as réussi?


Remove duplicate url key in siteConfig

url was duplicated in siteConfig.js, both were the same value, so stripping one of them.

Good catch. Thanks!


[main-dl to main] clean column name on file reading and add more data

clean column name on file reading and add more data.
Rules:
Only allow

numberes
alphabets
underscores

Before

After

#31


SecurityMonkey doesn't provide detailed information

Please make sure that you have checked the boxes:

[x] Pease review the Troubleshooting doc for additional details regarding your issue.
[x] Review the Quickstart guide
[x] Search for both open and closed issues regarding the problem you are experiencing

Description of issue:
Hello,
I'm not sure which update broke it as it might have been either v1.0.0 -> v1.1.0 or v1.1.0 -> v1.1.3, but I don't have detailed information on issues anymore. I have also confirmed that I'm not the only one based on Gitter's messages. I'm going to reuse @ollytheninja 's screenshots from the Gitter (I hope you don't mind!).
Before:

After:

I can also confirm that everything was working correctly on v1.0.0. In my infrastructure, I'm using the Docker approach, so it's probably not the configuration issues.
Let me know if I can provide more details to help debug the issue.

I've checked the changes in related code and I believe this might be the reason: https://github.com/Netflix/security_monkey/commit/573f8f19ff0f14f9d37e2349aa0299b7112026e3#diff-8169662c9a73fa6bbdd63664d294fd1cR200 . However, my knowledge on SM's code is too small to be sure of that

Unfortunately, the new issue system is half-baked at the moment.
I don't have any cycles this quarter to work on this. Please feel free to debug and submit PRs to help fix.

Yeah, I'm having the same issue. If I want to know that issues are on a particular item, the best way is to use the Search page. The Notes column still display the issues.
But justifying any is not possible as you don't know which is which.

Same issue here

Is this fixed? Or does anyone know a safe commit to build off that doesn't have this issue?

From my investigation today, it appears there are two issues:

Notes aren't shown because the API returns a sub-item for every single issue
can be fixed by displaying any notes as well as a link to the sub-item
line 89 and 123 of dart/lib/component/itemdetails/intemdetails.html
The API appears to always return the item itself as the sub-item instead of the sub item
Haven't found the relevant code for that yet but going to test the fix for 1. now and open a PR if it does

How do I apply this patch?
I updated
/usr/local/src/security_monkey/static/packages/security_monkey/component/itemdetails/itemdetails.html
/usr/local/src/security_monkey/dart/lib/component/itemdetails/itemdetails.html

But my dashboard has not been updated with the changes

I am also facing the same issue. I see issues. But cant figure out the breach behind each

@jibsonline To be clear, these are not "breaches". These are potential issues that may or may not be a problematic configuration in your environment.

@mikegrima sorry about the terminology used.
How do I understand details of each issue mentioned so I can fix it?
The only link in each row above is "jibu.chacko" on click of which nothing happens

Issue #1094 still here ! got the same problem, i tried the commit of @ollytheninja and it doesn't work ! Insteade of the regular related note, i've got the name of the AWS account like @jibsonline.

Is there a timeline for this to be fixed, or a timeline for 2.0 to be released?
I've spent a decent amount of time getting this up and running, and I cant see the descriptions of the issues it highlights. I'd hate for it to have been a waste of time

I agree with @martwana. I'd hate for this implementation to have been a waste of time. Should we be rolling back to a previous version? I can't seem to get a solid understanding of the specific things security monkey is checking for, nor do the items being flagged have details. Is there a timeline for a fix?


[TASK] Add Typescript implementation of SemaphoreWhistleblowing

Overview
Task Checklist

[ ] Add Typescript implementation of SemaphoreWhistleblowing
[ ] Add relevant documentation and usage guides

Should add a typescript interface for the SemaphoreVoting contract located at contracts/extensions/SemaphoreWhistleblowing.sol


CNF-11274: support must-gather

/test all

/uncc @oourfali
/cc @rauhersu
/cc @browsell
/cc @jc-rh

/hold
adding support for recert-summary.yaml

/unhold
updated to include recert-summary.yaml and ostree status + slight optimization for faster collection

/hold
collecting SRIOV

/unhold
Updated to include

healthcheck func collects SriovNetworkNodeState
Tries to collect Sriov CRs such SriovNetworkNodePolicy
Collects output of lsblk to see partitioning

/hold
Addressing cr changes

/unhold

updated to collect everything under /etc and unbooted stateroot's /var/log
looking under all stateroots to collect  recert-summary

/lgtm

/lgtm

/approve

/cherrypick release-4.15


Generalise riboviz.test.regression.test_vignette

Generalise to take any configuration file, optionally run the workflow, then validate the actual outputs (as held in the directories specified within the configuration file) against a directory of expected outputs.
Will be of help in #32.

@FlicAnderson
riboviz.test.regression.test_vignette has been generalised and renamed to test_regression. It's in the generalise-regression-test-vignette-155 branch.
It now takes a --config-file parameter with a configuration file which is used to find the files to be validated (using dir_tmp and dir_out). The --expected parameter is still used to specify the regression test data location.
As an example of use, to validate output produced by a run with vignette/simdata_umi_config.yaml where output from a previous run is in $HOME/simdata-umi-data/ (which contains index, simdata_umi_tmp and simdata_umi_output subdirectories), run:
$ pytest -s riboviz/test/regression/test_regression.py --expected=$HOME/simdata-umi-data --config-file=vignette/simdata_umi_config.yaml --skip-workflow

To validate output produced by run using vignette/vignette-config.yaml, run:
$ pytest -s riboviz/test/regression/test_regression.py --expected=$HOME/vignette-20200304-2.0.beta --skip-workflow

docs/developer/testing.md has updated usage and documentation.
Please let me know how you get on and if there are any issues.

@FlicAnderson to test this.

See pull request #155.

I still need to test this, haven't yet.

Still haven't tested this yet, will do before end of week starting 01st June, as part of submitting new pull request for merging #32 regen-stats-32 code into develop.

Tested this, comparing 1 sample full-size data from G-Sc_2014 run in develop vs regen-stats-32.
Ran it between those file sets ("21 passed, 27 skipped in 71.65 seconds")
I then manually edited one of the numbers in read_counts.tsv in develop file bundle and re-ran again with the same command, getting "1 failed, 20 passed, 27 skipped in 69.44 seconds" and errors pointing to the read_counts.tsv file in develop bundle. Exactly what we expected.
VERY NICE!  This will make my life so much easier!
In summary, generalise-regression-test-vignette-155 branch:

runs vignette fine
regression tests pass, matching regression-test-data-20200221
merged latest develop into branch (commit 95178e2ef from 27th May), no conflicts.
pytest all-tests all pass: 166 in 187.42 seconds
coverage tests all passing, with 69% coverage
documentation good once I'd gotten my file bundle locations sorted out, but as I use it more often, I'll see if I can figure out any specific points I can improve or if I just had a slightly slower brain day today :)

Happy to close issue! (and subsequent pull request)


Fix equal constraint handling in matchTypes.

We had an inconsistency in the handling of ConstraintKind::Equal in that
we would take
  $T1 Equal $T2

where $T2 was previously bound to a type, and bind the RValue type of
$T2's type to $T1.  That does not allow for us to later attempt to bind
the LValue type of that type to $T1 (as might happen in simplifying an
OptionalObject constraint).
Instead, if $T1 can be bound to an LValue and $T2 is not an LValue,
we'll defer simplifying the Equal constraint until after $T1 is bound
through some other type variable binding or constraint simplification.
Fixes rdar://problem/31724272.

@swift-ci Please test

Closing this out for the moment to take a slightly different look at this on master.


Make CommandExecutor pluggable

Follow-up #1315 and make CommandExecutor pluggable using the same approach as #1325. Close #901
We're going to add the system property agent.command_executor.type, which allows that users can specify command executor type.
See also: #1315 (comment)

Thank you!


node tainter: fix test flakes

Fixes https://github.com/istio/istio/issues/50444

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

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
1b91521577210b12bf6e280e34078b11b6baa9f8
link
true
/test unit-tests

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

/retest
not related


remove keybase listener warning modal

This modal that says "Keybase listener is not listening, consider installing it first" can be removed. Some users will not install keybase and I don't think we should show this modal every time. I think a notification in wallet events is fine here.

Actually, I just realized it looks like this modal only appears once correct? If so I think it's fine to display once, just not after you have seen it the first time.

So, if that's correct and it's displayed once this issue can be closed.

Chris.  The modal dialog with message shown only when you manually try to start Keybase listener.
But also there is a message at notifications with critical level, that highlight the icon. That message will be every start.  I will change Level from critical to info. So it will not highlight the icon


make: fail migration targets with unhandled promise rejections

Closes #509

Closing in favour of https://github.com/getodk/central-backend/pull/548