Add fuzzer with OSS-fuzz build script

This PR adds a fuzzer implemented with the go-fuzz fuzzing engine. Furthermore a build script is added to set up continuous fuzzing by way of OSS-fuzz.
Fuzzing is a way of testing programs wherby pseudo-random data is passed to a target application with the goal of finding bugs and vulnerabilities. In this fuzzer, the entrypoint to Cilium is the UnmarshalJSON implementatin in the labels package.
Integrating Cilium into OSS-fuzz allows Google to run all fuzzers in the Cilium project continuously free of charge. If bugs are found, maintainers get notified with detailed bug reports that include stack trace and reproducible test case. The service is offered free of charge to open source project with an implied expectation that bugs are fixed, and it has contributed to finding vulnerabilities in major open source projects like Kubernetes.
If there is interest in integrating Cilium, I will be happy to complete the integration on the OSS-fuzz side. For this at least one maintainer email address is needed.
Signed-off-by: AdamKorcz<EMAIL_ADDRESS>

Thanks for this @AdamKorcz :)
Yes, it would be great to get Cilium fuzzed regularly by OSS-Fuzz. Looking at OSS-Fuzz's guidelines for new projects it looks like Cilium is well qualified.
I've opened https://github.com/google/oss-fuzz/pull/4784 to get Cilium added to OSS-Fuzz as having a PR from a Cilium maintainer skips a manual email verification step.
There are obviously several entry points for fuzzing and Cilium and this is great start, thank you. Let's wait to see if Cilium gets accepted and then merge this and add more.

@AdamKorcz note that for this PR to be merged, all commits will need the Signed-off-by line as described in the contributing guide. You'll need to squash your commits.

@twpayne Thanks for the heads up!

@twpayne Let me know if anything else is missing from my side.

@AdamKorcz can this script be moved out of the tests directory? Currently tests holds our older bash based test scripts and I think it would be better to put any new features in either test dir, or a completely new one.

@nebril that is not an issue. The build file has hereby been moved.

@aanm Oh sorry about that. Both files have now been moved to /test/fuzzing

test-me-please

test-me-please

Let me know if there is anything missing from my side.

Let me know if there is anything missing from my side.

retest-runtime

retest-runtime


Vulnerability in react-scripts > @svgr/webpack > @svgr/plugin-svgo > svgo > css-select > nth-check & css-what

Describe the bug
Upgrade react-scripts to have the<EMAIL_ADDRESS>as the dependency. As the current<EMAIL_ADDRESS>has following vulnerable versions as dependency.
nth-check - https://security.snyk.io/vuln/SNYK-JS-NTHCHECK-1586032
css-what - https://security.snyk.io/vuln/SNYK-JS-CSSWHAT-1298035
Below is the dependency tree:
+--<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS><EMAIL_ADDRESS>Environment
Environment Info:
current version of create-react-app: 5.0.0
System:
OS: Windows 7 6.1.7601
CPU: (8) x64 Intel(R) Xeon(R) CPU E3-1585L v5 @ 3.00GHz
Binaries:
Node: 14.17.6 - ...\tools\nodejs14-win7\latest\node.EXE
Yarn: Not Found
npm: 8.2.0 - ...\data\npm14\npm.CMD
Browsers:
Chrome: 97.0.4692.71
Internet Explorer: 11.0.9600.20139
Steps to reproduce
npx create-react-app
Expected behavior
The react-scripts should not be having any dependency on vulnerable components.
Actual behavior
The dependent package @svgr/webpack 5.5.0 refers to vulnerable components, as per the author the v6 has the fix for the same.

Hi, any updates on when the package will be updated?
Thank you.

Hi, I am also facing the same issue. When I upgrading react-scripts to 5.0.0 version. While npm audit I am getting the same  Vulnerability Error.
Error:
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/svgo/node_modules/nth-check
css-select  <=3.1.0
Depends on vulnerable versions of nth-check
node_modules/svgo/node_modules/css-select
svgo  1.0.0 - 1.3.2
Depends on vulnerable versions of css-select
node_modules/svgo
@svgr/plugin-svgo  <=5.5.0
Depends on vulnerable versions of svgo
node_modules/@svgr/plugin-svgo
@svgr/webpack  4.0.0 - 5.5.0
Depends on vulnerable versions of @svgr/plugin-svgo
node_modules/@svgr/webpack
react-scripts  >=2.1.4
Depends on vulnerable versions of @svgr/webpack
node_modules/react-scripts
FYI, Upgrade react-scripts to have the @@svgr/webpack@6. as the dependency. As the current<EMAIL_ADDRESS>has following vulnerable versions as dependency.
Thanks & Regards,
Praveen Kumar D.

same here...
'''
npm audit report
nth-check  <2.0.1
Severity: moderate
Inefficient Regular Expression Complexity in nth-check - https://github.com/advisories/GHSA-rp65-9cf3-cjxr
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/svgo/node_modules/nth-check
css-select  <=3.1.0
Depends on vulnerable versions of nth-check
node_modules/svgo/node_modules/css-select
svgo  1.0.0 - 1.3.2
Depends on vulnerable versions of css-select
node_modules/svgo
@svgr/plugin-svgo  <=5.5.0
Depends on vulnerable versions of svgo
node_modules/@svgr/plugin-svgo
@svgr/webpack  4.0.0 - 5.5.0
Depends on vulnerable versions of @svgr/plugin-svgo
node_modules/@svgr/webpack
react-scripts  >=2.1.4
Depends on vulnerable versions of @svgr/webpack
node_modules/react-scripts
6 moderate severity vulnerabilities
'''

the vulnerable dependency is dependent of<EMAIL_ADDRESS>% npm list nth-check
create-react-app@ /Users/palmito/Development/create-react-app
├─┬ cra-docs@ -> ./docusaurus/website
│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       └─┬<EMAIL_ADDRESS>│         └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>-> ./packages/react-scripts
│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       └─┬<EMAIL_ADDRESS>│         └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>

The vulnerable dependency is caused by svg-term-cli
project seems to be abandoned for a couple of years (a lot of dependabot pull-requests getting rotten...)

@marionebl any feedback on svg-term-cli ?

Have you guys read this stickied issue?
https://github.com/facebook/create-react-app/issues/11174

Hi, any updates on when the package will be updated?
Thanks & Regards,
Praveen Kumar D.

Read this: #11174 ...then wait, there are more important things than fixing false positives. It will be fixed at the next scheduled update or when a critical bug appears.

Read this: #11174 ...then wait, there are more important things than fixing false positives. It will be fixed at the next scheduled update or when a critical bug appears.

Fair enough

same issue.
npm run build, failed to compile.
npm audit fix, got this:
nth-check  <2.0.1
Severity: moderate
Inefficient Regular Expression Complexity in nth-check - https://github.com/advisories/GHSA-rp65-9cf3-cjxr
fix available via npm audit fix --force
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/@svgr/plugin-svgo/node_modules/nth-check
css-select  <=3.1.0
Depends on vulnerable versions of nth-check
node_modules/@svgr/plugin-svgo/node_modules/css-select
svgo  1.0.0 - 1.3.2
Depends on vulnerable versions of css-select
node_modules/@svgr/plugin-svgo/node_modules/svgo
@svgr/plugin-svgo  <=5.5.0
Depends on vulnerable versions of svgo
node_modules/@svgr/plugin-svgo
@svgr/webpack  4.0.0 - 5.5.0
Depends on vulnerable versions of @svgr/plugin-svgo
node_modules/@svgr/webpack
react-scripts  >=2.1.4
Depends on vulnerable versions of @svgr/webpack
node_modules/react-scripts

Is there any ETA for nth-check & css-what ?

While this issue is not fixed, I did a workaround to solve it.
The problem seems to be in the  @svgr/webpack 4.0.0 - 5.0.0.

If you are using node >= 16, you can install @svgr/webpack by yourself, in my case I installed the version:  "^6.2.1" as devDependency.
After that, you should create a overrides (or resolutions if you are using yarn) section in your package.json and include the the line: @svgr/webpack": "$@svgr/webpack. (in my case, I already had the react and react-dom).

And last, you must remove your node_modules folder and your package-lock.json, and execute npm install.
This worked for me :)

And last, you must remove your node_modules folder and your package-lock.json, and execute npm install.

thanks, bro

While this issue is not fixed, I did a workaround to solve it.
The problem seems to be in the @svgr/webpack 4.0.0 - 5.0.0.

If you are using node >= 16, you can install @svgr/webpack by yourself, in my case I installed the version: "^6.2.1" as devDependency.

After that, you should create a overrides (or resolutions if you are using yarn) section in your package.json and include the the line: @svgr/webpack": "$@svgr/webpack. (in my case, I already had the react and react-dom).

And last, you must remove your node_modules folder and your package-lock.json, and execute npm install.
This worked for me :)

i was getting mad, thanks bro! it worked perfect.
if there's a newbie like me there, you can install the dependency with this line:
npm install @svgr/webpack --save-dev

While this issue is not fixed, I did a workaround to solve it.
The problem seems to be starting with the lib @svgr/webpack 4.0.0 - 5.0.0.

If you are using node >= 16, you can install @svgr/webpack by yourself, in my case I installed the version: "^6.2.1" as devDependency.

After that, you should create a overrides (or resolutions if you are using yarn) section in your package.json and include the line: @svgr/webpack": "$@svgr/webpack. (in my case, I already had the react and react-dom).

And last, you must remove your node_modules folder and your package-lock.json, and execute npm install.
This worked for me :)

In my case,
my overrides in package.json should be
"overrides": {
"@svgr/webpack": "^6.2.1"
},

In my case, my overrides in package.json should be
"overrides": { "@svgr/webpack": "^6.2.1" },

"To make this limitation easier to deal with, overrides may also be defined as a reference to a spec for a direct dependency by prefixing the name of the package you wish the version to match with a $"
https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides

Best solution:
"overrides": {
    "nth-check": "2.0.1"
},

Is there any ETA for this?

Any update?

guys?

Any update?

If you move react-scripts in "devDependencies", npm audit --production do not display any vulnerabilities.
The best explanation of why everything is in "dependencies" is here.
https://stackoverflow.com/questions/44868453/create-react-app-install-devdepencies-in-dependencies-section/44872787#44872787
But in fact, it matters when running npm audit --production because devDependencies are ignored.

https://github.com/facebook/create-react-app/issues/11647#issuecomment-1243863292


feat: show documentation text when mouse is over component

Feature to show documentation comments:
model User {
  id Int @id @default(autoincrement())
  /// user email needs to be unique
  email String @unique
  name String

  @@map("users")
}

Thanks for this. Forgot triple slash comments got persisted in the AST, this would've been a great idea to have before.


Add concurrency to tag Lookup

This was to address performance issues when deleting images in repos with a large number of tagstore
https://github.com/distribution/distribution/issues/3525
Signed-off-by: jack-baines<EMAIL_ADDRESS>

Codecov Report

Merging #3589 (76c29bf) into main (b609265) will increase coverage by 0.22%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3589      +/-   ##
==========================================
+ Coverage   56.33%   56.56%   +0.22%
==========================================
  Files         101      101
  Lines        7313     7354      +41
==========================================
+ Hits         4120     4160      +40
- Misses       2536     2537       +1
  Partials      657      657

Impacted Files
Coverage Δ

...ribution/distribution/registry/storage/tagstore.go
81.63% <0.00%> (+6.16%)
:arrow_up:

Continue to review full report at Codecov.

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

This PR fixes 1 of the 2 things described in the issue which is that we have to look up every tag in the repo to detect whether it matches the digest being deleted and needs to be untagged and previously this was done one tag at a time.
The 2nd bit has much lower impact from manual testing and is that once we have identified which tags match the digest we untag them sequentially.

Final thing to point out is that I have hardcoded the concurrency limit to 10 obviously may be some advantages to that being configurable but wasn't entirely sure on how that could be achieved, so if that is deemed required would appreciate a pointer of a similar code that gets config into something like the tag store.

Just wondering since we are addressing these slow deletes...this code in S3 delete driver could use a bit of TLC, too. If the repo contains a lot of data, we end up growing s3Objects slice into huge size; the actual deletes are batched, though that is of little help since we must first go through all contents of the repo.

LGTM...
800TB files in ceph ,its' hard to delete.
patch  it by this pr
delete file with 3TB / min

Is there any news on this?

Ping @bainsy88

Friendly ping @bainsy88

There is also https://github.com/distribution/distribution/pull/3890 which is more comprehensive.
We need to decide which one to keep focussing on.

If https://github.com/distribution/distribution/pull/3890 is more comprehensive and more (recently) active then I’d say it’s safe to close this PR (also given that the author hasn’t responded to the reviews).


rust:slim is not stretch

Steps to reproduce
Update rust:slim, build a new docker container.
Expected  behavior
App runs
Actual behavior
App will immediately fail due to wrong glibc version.
https://github.com/peterhuene/azure-functions-rs/blob/master/docker/build-image/Dockerfile#L1 should target rust:1.39-stretch until mcr.microsoft.com/dotnet/core/runtime-deps:2.2 is built against buster.

Thanks for reporting this!
I'll get this fixed and push up a new build image soon.

@dbcfd Thanks again for reporting this.  I've pushed a new peterhuene/azure-functions-rs-build:0.11.0 image with the change to Stretch.  I'll close this issue when #468 is merged that fixes the Dockerfile.

Please let me know if this didn't resolve your issue.  Thanks!

So ran into one issue with the new image
The method driver /usr/lib/apt/methods/https could not be found.
Removing /etc/apt/sources.list.d/microsoft-prod.list allowed me to build as normal, and the new image worked correctly.

Hi @dbcfd. Do you have repro steps I could follow to reproduce the error?
I had no problems with the image when I tested it before pushing it up, so I'd like to figure out why it didn't work for you.


calaos_installer: fix darwin install

Motivation for this change
On darwin this builds an application instead of a binary.
/cc ZHF #45961
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

Success on x86_64-darwin (full log)
Attempted: calaos_installer
Partial log (click to expand)
/nix/store/y40adf87sg46pqlh182yp0lr8wikrb73-calaos_installer-3.1

Success on x86_64-linux (full log)
Attempted: calaos_installer
Partial log (click to expand)
these paths will be fetched (1.62 MiB download, 3.71 MiB unpacked):
  /nix/store/3cy852q4b2b8r76b71j7l9vizc1id4xy-calaos_installer-3.1
copying path '/nix/store/3cy852q4b2b8r76b71j7l9vizc1id4xy-calaos_installer-3.1' from 'https://cache.nixos.org'...
/nix/store/3cy852q4b2b8r76b71j7l9vizc1id4xy-calaos_installer-3.1

Success on aarch64-linux (full log)
Attempted: calaos_installer
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/2kwvk4pilm6pv1mmsg62drhg3insvfc6-calaos_installer-3.1
shrinking /nix/store/2kwvk4pilm6pv1mmsg62drhg3insvfc6-calaos_installer-3.1/bin/calaos_installer
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/2kwvk4pilm6pv1mmsg62drhg3insvfc6-calaos_installer-3.1/bin
patching script interpreter paths in /nix/store/2kwvk4pilm6pv1mmsg62drhg3insvfc6-calaos_installer-3.1
checking for references to /build in /nix/store/2kwvk4pilm6pv1mmsg62drhg3insvfc6-calaos_installer-3.1...
postPatchMkspecs
postPatchMkspecs
/nix/store/2kwvk4pilm6pv1mmsg62drhg3insvfc6-calaos_installer-3.1

backported: 4199eb48faa


Retry failed connections

Carrying on discussion from https://github.com/kamailio/kamailio/issues/2820
Unfortunately my rust is non existent so i don't think i will be able to help much other than discuss ideas...
A retry mechanism would be really handy in case of transient network and server issues.
I have modified the ruxc module to have a basic retry mechanism as follows:
	ruxc_http_post(&v_http_request, &v_http_response);

	//Retry logic
	//If attempts < configured retries and return code is < 0 but > -20 [libruxc null url return code] or has a response code between 500-699
	int attempt;
	attempt = 0;
	while(attempt < _ruxc_http_retry &&
	  ((v_http_response.retcode < 0 && v_http_response.retcode > -20) ||
	  (v_http_response.rescode > 499 && v_http_response.rescode < 699)){
		attempt++;
		LM_DBG("Retrying Request Attempt: %d - Response Code: %d - Return Code: %d - URI: %s\n",
		  attempt, v_http_response.retcode, v_http_response.rescode, v_http_request.url);
		ruxc_http_post(&v_http_request, &v_http_response);
	}

Which seems to work nicely and protects against the issues openssl seems to be having on ubuntu 18.04
In order to make this logic as unopinionated as possible there should be an optout mechanism so you could specify that a request shouldnt retry if retries are enabled.  I would propose that the least intrusive way of doing this would be to use a "X-" http header to control participation.  The header name could be a configurable value with a sensible default of X-RUXC-NORETRY, the presence of the configured header name in a request would disable the retry logic, the value would be irrelevant.
There is also no reason why the configured retry attempts couldnt also be overriden with a http header included in the request.
i.e. if 3 retries are configured globally, then for a given unreliable destination you could override the number of attempts by including an X-RUXC-RETRYATTEMPTS in the specific request.
This would allow simple setting of defaults through mod params if using kamailio, and per request overrides if you add the headers in kamailio config, or any other client to libruxc

I would rather add a new field in the request structure, rather that relying on headers, because then we have to specify which ones should be propagated to http message or skipped. The structure is used per function call, so should be easy to do requests with or without retry.
See the structure in the c header file:

https://github.com/miconda/ruxc/blob/main/include/ruxc.h

The library is at its very beginning, so adding new fields is ok (or use the exiting  by-now-unused flags field), kamailio module is also not released.

I would only view headers as a secondary control mechanism, just to be able to override values at runtime when used with kamailio, i.e. have a pv set the retry attempts, but thats really a module feature not a library feature.
Ive been meaning to have a look at rust for a while now, so this has given me all the excuse i need to spend the afternoon having a learn

I made a first attempt of retrying the http request by reusing the http agent. You can try with latest dev version of libruxc and set the retry field in the C code:

https://github.com/miconda/ruxc/blob/main/include/ruxc.h#L21

If works as expected, then a modparam can be added to kamailio module to set it as a global option, also look for a way to control it per https request done in kamailio.cfg routing blocks.

Initial testing if going well, no connection failures logged in a timespan that would usually log one.
Where is the best place to discuss module functionality here or on the kamailio repo?
For enabling config block/per request control i guess it depends on how you see ruxc developing, would the plan be to add more rust exports apart from HTTP based functionality?
As mentioned for HTTP use i have a preference for HTTP headers (or a control string) used as an adhoc control mechanism as my dev team are used to providing various control headers to some api's we use and keeps things pretty extensible, i.e. if basic auth is added to the lib, then it wouldn't be hard to add to add per request credentials using headers, similarly if download handling was added then an output path could be supplied by header.
My hesitancy in adding arguments to the basic ruxv_http_get() signature is that it could descend into the positional hell that is asterisk dialplan apps and functions, while ruxc_http_get(uri, headers, pv) is concise it could grow to ruxc_http_get(url, headers, pv, username, password, retry, debug, outputPath,....), i guess a control argument could be provided and is handled similarly to attributes in dispatcher (; separated list of keywords and values) which would work as well, either way some string parsing would be required.
Which then loops the discussion back around to use headers for control or an attribute string, and as attribute strings are already widely used by dispatcher that would be a more consistent approach, that another ad hoc control mechanism.
so having talked my self around i would propose this:
ruxc_http_get(url, headers, pv, requestOptions)
ruxc_http_post(url, body, headers, pv, requestOptions)
with requestOptions looking like this:
debug={>=1,yes,true};retries={0-10};reuseConnection={0,1,2},tlsAccept={0,1},timeout={0-10000}
Another thing that occurs to me is should the lib have configurable max values which cant be overriden by requestOptions?, as it is a blocking process and if someone sets a 60000ms timeout for example that would almost certainly break a call attempt that invoked it.  Or should user protection live higher up in the module, as the short timeout requirement (we have a 100ms max response time for any service which can block on dialog progress) for example is peculiar to VoIP user experience and not general purpose GETting and POSTing....

Using headers is suitable for passing info between applications, being done via the protocol, but for controlling a lib I consider that it has to be done via parameters/structure fields.
In this case, mixing headers that should be set to HTTP request with headers that should be used only to control libruxc behaviour makes it confusing. Then it has to be defined a way to specify what headers are for control and should not be passed further to http layer, bringing more complexity. I started from the beginning with two structures, one for defining the http request and the other one for http response, so the functions prototypes stay the same, but new options can be passed by adding fields to structures.
For the kamailio module, the idea was to have something close to a drop-in replacement for http_client module. It has the option to defines connection attributes via modparam or in a configuration file:

https://www.kamailio.org/docs/modules/stable/modules/http_client.html#http_client.p.httpcon

The idea to provide the options via a new parameter for kamailio functions seems a good alternative as well.


Click detected

Hello,
I was a long time subliminal user, It is a great tool. i just use it in some bash script to get subtitle, and copy the episode to the right dir somewhere on another hdd. Today I cloned the current version, but it seems a little buggy.
root /media/500gb/Downloads/ # subliminal download -l en *

/usr/local/lib/python2.7/dist-packages/subliminal-1.0.1-py2.7.egg/subliminal/cli.py:115: Warning: Click detected the use of the unicode_literals __future__ import.  This is heavily discouraged because it can introduce subtle bugs in your code.  You should instead use explicit u"" literals for your unicode strings.  For more information see http://click.pocoo.org/python3/
  @click.pass_context
/usr/local/lib/python2.7/dist-packages/subliminal-1.0.1-py2.7.egg/subliminal/cli.py:145: Warning: Click detected the use of the unicode_literals __future__ import.  This is heavily discouraged because it can introduce subtle bugs in your code.  You should instead use explicit u"" literals for your unicode strings.  For more information see http://click.pocoo.org/python3/
  @click.pass_context
/usr/local/lib/python2.7/dist-packages/subliminal-1.0.1-py2.7.egg/subliminal/cli.py:172: Warning: Click detected the use of the unicode_literals __future__ import.  This is heavily discouraged because it can introduce subtle bugs in your code.  You should instead use explicit u"" literals for your unicode strings.  For more information see http://click.pocoo.org/python3/
  @click.pass_obj
Collecting videos  [####################################]  100%
0 video collected / 6 videos ignored / 12 errors

you can disable the warning by adding:
import click
click.disable_unicode_literals_warning = True

but this doesnt resolve this at fundum

Please search issues before posting. #495


Use relative url mapping so reverse proxies supported

Shipyard redirects to root urls, making reverse-proxying trickier.  e.g.
    location /shipyard/ {
       proxy_set_header X-Real-IP  $remote_addr;
       proxy_set_header X-Forwarded-For $remote_addr;
       proxy_set_header Host $host;
       proxy_pass http://shipyard_hosts/;
       }

Won't work as it forwards to /auth, /images, /containers, etc.  This requires a second reverse proxy on the shipyard host to get around.  Would be better if relative URLs were used so that this wasn't necesary, as in Kibana for instance.

Closing as duplicate to #587


Return the original libpostal components in the response

based on this discussion: https://github.com/gosom/address-parser-go-rest/issues/1
looks like it's a good idea to return the original libpostal components in the response.
In particular:
in file addressparser/addressparser.go in the Address struct add an attributed:
Components []AddressComponent `json:"libpostal_components"`
```

AddressComponent should be a struct having 2 attributes (Label, Value) both strings.

Components should contain the libpostal raw result .

Implement in v1.0.2 (https://github.com/gosom/address-parser-go-rest/releases/tag/v1.0.2)


Add check hook for pgstat_end_function_usage in fmgr

Description
In babelfish there could be cases where a procedure rollbacks/deletes it self during execution.
For example
BEGIN TRAN
CREATE PROCEDURE p AS ROLLBACK;
EXEC p;

Procedure 'p' does not exists after its execution since the transaction where it was created was rolled back.
Now while executing rollback inside such procedures, the pg_stat entry for this proc is also deleted.
When we return to fmgr to end the proc invocation, we will overwrite on this freed block of memory.
To avoid this, we add an additional check before writing on the pg_stat entry post invocation.
Check involves simply looking for a local cache pg_stat entry for given key.
Note* PG does not need this check since such a case is not possible there.
Issues Resolved
[BABEL-4740]
Sign Off
Signed-off-by: Tanzeel Khan<EMAIL_ADDRESS>Test Scenarios Covered

Enable track_function GUC for github actions otherwise execution does not even enter the pg_stat related code.
Different permutation and variation of example in description.
older test cases like TestTransactionSupportForProcedure & TestSimpleErrorsWithImplicitTran crashes without this fix when track function GUC is enabled.
Todo: Check how much the check hook deteriorates the performance.

Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

-1 of 7 (85.71%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 72.291%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tsql/src/hooks.c
6
7
85.71%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
40754

Relevant Lines:
56375

💛  - Coveralls


fix tispark query err: for PushDownFilter, conditions and executor_id should both be empty or neither should be empty

What problem does this PR solve?
Issue Number: close #4865
Problem Summary:
What is changed and how it works?
fix bug from https://github.com/pingcap/tiflash/pull/4783/files#diff-82a0d2f1d3a9216cb12886709ed704a96b435b2a86e24878d097b5738e4de872R63
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/merge


Build dbtool in CI/nix

I just noticed I forgot to add a flake.nix entry in #1321.

Probably put into a fedimintd container as well (it already contains fedimint-cli)

This should be fixed as of this PR https://github.com/fedimint/fedimint/pull/1523/files#diff-206b9ce276ab5971a2489d75eb1b12999d4bf3843b7988cbe8d687cfde61dea0


When data rows are deleted and pagination resets to the last page due to page index out of bounds (with table prop, autoResetPageIndex = false), data is not shown in certain cases.

material-react-table version
v1.14.0
react & react-dom versions
v18.2.0
Describe the bug and the steps to reproduce it
Here is a code sandbox demonstrating the bug.  Code sandbox bug demo
Bug description is also in the sandbox.
Fix for bug is given below.
Description
When using autoResetPageIndex=false and data passed to the updates, page index can get out of bounds (i.e. There are no longer enough data rows for the current page index).
Use the provided code sandbox to see this behavior, click Get 3 pages of data then go the 3rd page (showing rows 21-30 of 30). Then click Get 2 pages of data. Notice table footer now shows 11-20 of 20, but no data is displayed. Then if you click go to previous page, you can see data on the first page. And if you click go to next page, data in 2nd page is shown correctly
In this case, the table tries to reset the page index so that the second page is shown. However there is a bug in the useEffect that attempts to reset the index. Description and fix for bug are in the discord thread.
Cause
There are two issues with this if statement in MRT_TableRoot component.
(packages\material-react-table\src\table\MRT_TableRoot.tsx : line 394)
if (firstVisibleRowIndex > totalRowCount) {
table.setPageIndex(Math.floor(totalRowCount / pageSize));
}

Comparison in if statement should be updated.
The comparison should be firstVisibleRowIndex >= totalRowCount  instead of '>'
(-1 discrepancy between index and count. )

Math to calculate new index is wrong when totalRowCount is a multiple of pageSize.
Example.  totalRowCount of 10 and pageSize of 5 gives new index of  2 (3rd page) but index should be 1 (2nd page)

Fix
Either of fixes work. Page index will be updated and table rows will be populated with data.
Option 1
Page index calculation uses table.getPageCount().
    if (firstVisibleRowIndex >= totalRowCount) {
      const lastPageIndex = Math.max(0, table.getPageCount() - 1)
      table.setPageIndex(lastPageIndex);
    }

Option 2
Or we can just compare the pageCount with pageIndex instead of having to calculate firstVisibleRowIndex as in option 1.
   const pageCount = table.getPageCount()
   if (pageIndex >=  pageCount) {
      const lastPageIndex = Math.max(0, pageCount  - 1)
      table.setPageIndex(lastPageIndex);
    }

Pull Request
I'd be happy to submit a pull request, but I am not sure what testing standards this project has. I didn't see tests in the repo, so not sure if unit tests are required for this fix?
Minimal, Reproducible Example - (Optional, but Recommended)
Code sandbox example included in description section above.
Screenshots or Videos (Optional)
No response
Do you intend to try to help solve this bug with your own PR?
Yes, I am also opening a PR that solves the problem along side this issue
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Did you find any solution by any chance? @kenny-lu-hl

Did you find any solution by any chance? @kenny-lu-hl

The fix is included in the original post.

This should be fixed in v2.7.0


[DO NOT MERGE] Add a jenkins job to dump routes and content every day

The routes dump artefact will be used in a separate job which checks for consistency between the content store and the router-api.

This will be done in a better way.


BUG: Breaking when pressing A multiple times on calculator

I got this from clicking into the address finder box, then pressing cmd a and control a repeatedly

what does cmd-a and control-a mean on your OS and browser? Is it "select all" ?

Fixed


Initiating an http call through the service name in the gateway's fliter fails.

When I initiate an http call through the service name in the fliter of the gateway, it fails. There is no problem with the 2.x version, and there is a problem with the 3.0.x version.

If you'd like us to spend some time investigating, please take the time to provide a complete, minimal, verifiable sample (something that we can unzip attached to this issue or git clone, build, and deploy) that reproduces the problem. Then we will reopen


[STG93] Adding Rename Support to List Ranges API

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

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

Looks like there was an issue with recording the new test.

Looks like there was an issue with recording the new test.

yea i ran live earlier, should be all fixed now :)


made travis build smarter

Coverage decreased (-1.05%) to 41.531% when pulling 4ba23da91074bd0cfe9382c50b18d29e27aa0084 on Tr0nYx:master into b7e1029a6c304c8f04d8639cd43b083ab028b9b3 on Alpha-Trader:master.


{AKS} Skip deprecated test case test_aks_browse_legacy

Description

Skip deprecated test case test_aks_browse_legacy, since we cannot create a cluster with version lower than 1.19.0 which meets the test requirements anymore.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

AKS


Candy Crush

Project title

Candy Crush
Project Description

Candy Crush is a popular mobile puzzle game that challenges players to match colorful candies in various combinations to progress through hundreds of levels.
Web stack

HTML , CSS AND JAVASCRIPT
Screenshot(mandatory)

Additional Context(mandatory)
Are you contributing under any open-source program ?
I am working under codepeak'23.

@Mayank77maruti Please don't make any PR until & unless you get assigned . Now you can submit your PR.

@apu52 , so sorry for doing so , it would not be repeated.


Update README.md, added ChakraProvider

For the Chakra UI section, I thought it was missing the ChakraProvider component

Thanks! But I added it

https://github.com/Jonghakseo/chrome-extension-boilerplate-react-vite/pull/423


Warning: calls to std::mem::drop with a reference encountered while following instructions in instruction.md.

my environment

macos
asdf
rust 1.74.1
llvm@16 installed via brew

I Encountered warning while following instructiosn in install.md.
Executing the command cd lib/skc_rustlib; cargo build; cd ../../ resulted in a warning message related to calls to std::mem::drop with a reference.
kyama@Nyanko-Book-Pro shiika % cd lib/skc_rustlib; cargo build; cd ../../
  Downloaded unicode-segmentation v1.10.1
  Downloaded cmake v0.1.50
  Downloaded rand_chacha v0.3.1
  Downloaded uncased v0.9.9
  Downloaded ppv-lite86 v0.2.17
  Downloaded getrandom v0.2.10
  Downloaded plain v0.2.3
  Downloaded chrono-tz-build v0.0.3
  Downloaded chrono-tz v0.6.3
  Downloaded bdwgc-alloc v0.6.6
  Downloaded 10 crates (1.8 MB) in 1.61s
   Compiling libc v0.2.147
   Compiling regex-syntax v0.7.4
   Compiling uncased v0.9.9
   Compiling ppv-lite86 v0.2.17
   Compiling shiika_ffi v0.1.0 (/Users/kyama/Projects/shiika/lib/shiika_ffi)
   Compiling plain v0.2.3
   Compiling unicode-segmentation v1.10.1
   Compiling shiika_ffi_macro v0.1.0 (/Users/kyama/Projects/shiika/lib/shiika_ffi_macro)
   Compiling cc v1.0.82
   Compiling getrandom v0.2.10
   Compiling time v0.1.45
   Compiling phf_shared v0.11.2
   Compiling rand_core v0.6.4
   Compiling phf v0.11.2
   Compiling phf_generator v0.11.2
   Compiling chrono v0.4.26
   Compiling phf_codegen v0.11.2
   Compiling rand_chacha v0.3.1
   Compiling rand v0.8.5
   Compiling cmake v0.1.50
   Compiling regex-automata v0.3.6
   Compiling bdwgc-alloc v0.6.6
   Compiling regex v1.9.3
   Compiling parse-zoneinfo v0.3.0
   Compiling chrono-tz-build v0.0.3
   Compiling chrono-tz v0.6.3
   Compiling skc_rustlib v0.1.0 (/Users/kyama/Projects/shiika/lib/skc_rustlib)
warning: calls to `std::mem::drop` with a reference instead of an owned value does nothing
  --> lib/skc_rustlib/src/builtin/file.rs:65:5
   |
65 |     std::mem::drop(SkFile(shiika_file).file_mut());
   |     ^^^^^^^^^^^^^^^------------------------------^
   |                    |
   |                    argument has type `&mut File`
   |
   = note: use `let _ = ...` to ignore the expression or result
   = note: `#[warn(dropping_references)]` on by default

warning: `skc_rustlib` (lib) generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 8.00s

Thank you for reporting! It seems that I was using older rustc. After upgrading to 1.74.1, I got the same warning.

Should we specify the rust version in the install.md?
What rust version are you currently using?

Fine, but how about just write "latest stable"? (because if you write "1.74.1" there then you need to update it everytime new rust is released)

Nice. Check this.
https://github.com/shiika-lang/shiika/pull/528

Installed 1.74.1 last night, so I'll keep using it.

OK thx. I'll also keep using 1.74.1.

Oh we should fix the warning.


Updating Copyright to 2015 and composer.phar

@Lansoweb can you avoid upgrading composer.phar? That is really something only the CR team should do (due to security issues)

@Ocramius  Sure! Will revert it. Sorry :-)

@Ocramius Reverted.

@Lansoweb thanks!


check for pxDuplicateNetworkBufferWithDescriptor returning NULL

Check for pxDuplicateNetworkBufferWithDescriptor returning NULL
Description
pxDuplicateNetworkBufferWithDescriptor in FreeRTOS_IP.c might return a NULL pointer => we need to check for this case and avoid dereferencing a NULL pointer.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks a lot, @RolinBert !
I think that your diagnosis is correct, and also the remedy. I recommend merging this tiny PR.
Hein

Thank you @RolinBert for spotting this issue and creating a PR to fix it!
We shall get this PR merged quickly.
P.S. I had to push a couple of commits to rebase your PR and uncrustify the sources.


FIO V1 History: Duplicate trnsfiopubky transactions

Multiple transfer fio pub key transactions are showing up in the Explorer. For example see:
https://explorer.fioprotocol.io/account/o3vozszmxmto

From @lukestokes

Raw data doesn't show up: https://explorer.fioprotocol.io/transaction/28cf9d4afa8272decc4197bdec4408ac81c73cf619caeed694a97a331911f190

Transactions seem to be accounted for in the latest history plugin fix. Should be making it into the next release.
For trnsfiopbkey, the following history insertions take place:
action trace inserted by account receiver - entry for the contract account
action trace inserted by actor - filtered and inserted if the param exists, action trace is inserted for the actor account
action trace inserted by hashed down fio pub key - in this case, the receiver may not exist yet as it was just created before the transfer occurred, additional insertion was created using an account that was derived from the payee public key
The caching of the three separate entries of the same action allows transaction to be searchable by sender, receiver or payee account. So, what we get is all 3 of those action traces when looking up by account.
There is a unique action_digest that we will attempt to leverage to filter out the duplicate results. Discussing the next steps with the team...

Adam A - Dapix, [01.05.20 12:35]
Hey @any_x . Seeing some duplication for a some transactions, specifically trnsfiopbky. This is the current modified history plugin. Trying to rule out the plugin itself, could the the explorer..
https://github.com/fioprotocol/fio/blob/feature/MAS-1563_temp/plugins/history_plugin/history_plugin.cpp#L188-L264

Aaron Cox (jesta) — Greymass, [01.05.20 13:01]
I believe that's the default behavior, it's returning all traces involving the account being queried. Sadly it doesn't also filter the traces to the account being notified.
Aaron Cox (jesta) — Greymass, [01.05.20 13:03]
It can be filtered at the explorer level by receiver though I believe. Those 3 traces being returned have unique receiver fields of:

fio.token (the contract)
gjkdwmtx2tse (the originating account)
l35p5swqgvoo (the destination account)

Adam A - Dapix, [01.05.20 13:12]
Makes sense. Filtering out duplicate transactions for the receiver at the explorer should be easy... thanks
Aaron Cox (jesta) — Greymass, [01.05.20 13:15]
No problem!
Aaron Cox (jesta) — Greymass, [01.05.20 13:16]
Our history viewer in the wallet also suffered from those duplicates, though we never fixed it. I don't remember if there was some reason we didn't do it though, this was a long time ago we looked into it.
Aaron Cox (jesta) — Greymass, [01.05.20 13:17]
It's possible that the receiver was incorrect on some of the transactions we acutally wanted to displayed.
Aaron Cox (jesta) — Greymass, [01.05.20 13:17]
Just saying all this so you're aware and can make sure going this route doesn't eliminate some sort of data you actually want 😉
Adam A - Dapix, [01.05.20 13:47]
Already had a situation where we were storing incorrect account names for address and domain registration actions that weren’t supplied with an owner fio public key.  Oops.
That’s been cleaned up. 1 duplicate makes sense when you account for both sender and receiver, but 2 duplicates, that’s a little confusing
Adam A - Dapix, [05.05.20 10:36]
Hypothetical question related to the latest changes of the history plugin, just throwing it out here.
We introduced duplicate results by account_name when doing additional insertions of action traces (which are working great)... if get_actions endpoint were modified to filter out results with identical action digests, what would this harm ?
Adam A - Dapix, [05.05.20 10:43]
The actions are exactly the same. If we leave out the extra ones from the result, I only see positives at this point so correct me if wrong.
Adam A - Dapix, [05.05.20 10:47]
We could very easily do the filtering on the block explorer or any FR, but dapix product team has concluded I should pursue a clean and compatible solution at the api since we are seeing some noticeable differences in how some of the wallets handle action history.
Adam A - Dapix, [05.05.20 10:48]
@jestagram
Aaron Cox (jesta) — Greymass, [05.05.20 12:52]
I personally don't know of any issues it'd cause, so long as some transactions don't go missing.
Are we talking about filtering at the API call level or in the actual index/storage level?
@any_x might have a better idea than I do if this would cause any headaches.
Luke Stokes, [05.05.20 13:41]
We talked a little yesterday and today about this and I'm wondering if it makes sense to have a call with yourselves, Igor (for Hyperion), what's his name from Amseterdam and his history solution, etc... make sure we are all on the same page as to what should go into the block_log and how that should be indexed for a history solution and how those things should be filtered when showing explorer history.
Luke Stokes, [05.05.20 13:42]
the Bloks guys are going to start to working on an integration. We currently have different wallet experiences, from what I hear, regarding edge and trust. I think Edge uses Hyperion, but I'm not sure.
Luke Stokes, [05.05.20 13:42]
Should we start this conversation in the EOS Mainnet channel or start a new one?
Aaron Cox (jesta) — Greymass, [05.05.20 13:54]
The block_log is independent of this conversation, there's no derived state within it. All transactions will always be in the block_log, the various solutions just have different methods of extracting and generating the derived state from it.
From my point of view there's no much value at the moment getting those parties together. V1 history (native) is different than V2 (Hyperion) in far too many ways and will never be identical, and Chronicles from Amsterdam isn't even an API just a tool to help build datasets for APIs. Each wallet and app independently is going to choose which route they go based on their needs.
I'm willing to engage on the topic, but I don't see what we'd aim to accomplish.

We decided that we would look into creating a new get action call for integrators that will filter out duplicate trnsfiopubky calls.

Eric Butz, [06.05.20 11:38]
@any_x, thanks for the info on this. Very helpful. There is still some concern that we have a history node that will return duplicate transactions for our wallet and exchange partners. So we somehow have to tell them how to manually filter FIO transfer transactions. @pawmmm suggested we create a modified get actions call that automatically does the filtering. Any thoughts on that approach?
anyx — TeamGreymass, [13.05.20 15:06]
[In reply to Eric Butz]
I still highly recommend against it. The format of the contract and its token action structure is identical to all EOSIO chains, so if they see this issue for FIO they are going to see it for EOS Mainnet and everything else. If its a multi-chain wallet (which most are), it seems to me that it is better to identify this commonality and solve it wallet-side. Helping the wallet understand this (as it relates to all EOSIO chains) would be nice of course.
We could likely identify an API-side improvement, but I would argue this is something that should be considered for a V2 spec history. V1 spec history is very blunt and returns a lot of not-so-useful data, it's not great. So, personally, I would suggest not departing further from EOSIO here and having wallets implement different strategies per-eosio chain, and instead help us with V2 spec. ;)

anyx — TeamGreymass, [13.05.20 15:06]
[In reply to Eric Butz]
I still highly recommend against it. The format of the contract and its token action structure is identical to all EOSIO chains, so if they see this issue for FIO they are going to see it for EOS Mainnet and everything else. If its a multi-chain wallet (which most are), it seems to me that it is better to identify this commonality and solve it wallet-side. Helping the wallet understand this (as it relates to all EOSIO chains) would be nice of course.
We could likely identify an API-side improvement, but I would argue this is something that should be considered for a V2 spec history. V1 spec history is very blunt and returns a lot of not-so-useful data, it's not great. So, personally, I would suggest not departing further from EOSIO here and having wallets implement different strategies per-eosio chain, and instead help us with V2 spec. ;)

Duplicate transaction issue was fixed with https://github.com/fioprotocol/fio/releases/tag/v2.0.0
Closing.


[AP-007] Fix Dryrun Evidence Printing

Summary
fixed evidence printing in dryrun mode
Tables now print with proper column spacing
Test Plan
run gitlab with dryrun

Task
[AP-007]

@check-spelling-bot apply changes


Change "Gitdub" to "Github"

I would imagine "Github" is what is meant in these sections instead of "Gitdub", maybe I'm missing out on a new and exciting service.

thanks for doing this!


gb should support tranisitively building standard library packages

Related to #31
gb currently ignores any package it thinks is part of the standard library; it just assumes they are up to date.
This may not be correct in a cross compilation world, where package resolution and isStale calculation could reach all the way back to runtime
Can will need to be taken that package resolution always goes, $GOROOT, $PROJECT/src, $PROJECT/vendor/src-- it should never be possible for$PROJECT/src/errorsfor example, to override$GOROOT/src/errors`.
However, when it comes to package compilation time, we want to cache the results of compiling source from $GOROOT/src in $PROJECT/pkg and this will be tricky.

Just ran into this with the innocuous cmd name in https://github.com/tianon/go-tags.
go build happily spits out a binary, but gb build returns the wonderfully cryptic FATAL command "build" failed: failed to resolve import path "cmd": no buildable Go source files in /usr/lib/go/src/cmd (because cmd exists in GOROOT, so it must be GOROOT/src/cmd I want to compile, right?  except there are no .go files there so it errors out instead :smile:).

@tianon kicking this to a new issue.

:heart:!


Way to cancel file upload?

Problem/Feature Request Summary
I'm wondering if there is a way to cancel an upload. For example if the file type isn't expected or the file upload name isn't what was expected. I know onFileBegin can be used to modify the upload, but how can it be stopped?

Hello, you can get the path of the file after uploading, and then check if the file meets the specifications you ordered, if not, you can delete it with the fs module

I think this idea is useful.(Even we can delete it with the fs nodule)


Linkify geo: and xmpp: URIs automatically

It'd be helpful if Flexmark rendered geo: and xmpp: URIs as links automatically, i.e. without requiring the link syntax. Would it be possible to add this?

@contrapunctus-1, auto links extension uses org.nibor.autolink for finding links in text.
If there is an option to enable geo: and xmpp: URI recognition then it would be a matter of adding an option to have them automatically recognized. Otherwise, either a customized version of org.nibor.autolink or if possible an extension added to it.
I have not looked into org.nibor.autolink to see if extending it is possible but suspect that it is not only possible but probably easy.
If you are so motivated you can take a look at the AutolinkNodePostProcessor.java which handles auto links and if org.nibor.autolink can be configured to recognize other resources then it would only require modifying the link extractor instance used by the node post processor to implement the functionality you want.
If you do find a solution and would like to see it as part of the library then please either PR a fix or post your changes here and I will incorporate it into the extension.


There is only one  .NET 6 runtime stack in the list when creating a  .NET 6 Function App

OS: Win10
Build Version: 20211103.2
.NET 6 Version: 6.0
Function Core Tools: v4
Repro Steps:

F1 -> Azure Functions: Create New Project... -> Select a folder -> Select C# language -> There are two .NET 6 runtimes in the list.

F1 -> Azure Functions: Create Function App in Azure... -> Enter a name.
Check Whether there are two .NET runtimes stack in the list.

Expect:
There are two .NET runtimes stack in the list.
Actual:
There is one  .NET runtime stack in the list.

More Info:
Fail to deploy the .NET 6 isolated project to .NET 6 function app.

This should not be the case anymore.  Could you test this off of the release or off main?

Verified this issue on the latest build 20211111.1, it doesn't reproduce. So I close it.


Add support for allow_nil/allow_blank

I was looking to replace validates_url_format_of with this library in rubygems.org but I need the ability to say:
validates_formatting_of :website, :using => :url, :allow_nil => true, :allow_blank => true

Would you be willing to add these options?

Absolutely. I don't know how soon I will be able to release this feature, but I would love to add it. Thanks for the suggestion!

The code in the branch works for me. I hope it gets merged into master and pushed soon. :)
I just opened another feature request: #2.

Thanks for the quick push. I just updated rubygems/rubygems.org@06c8978f75f694bcce10e017b99f9d937f575800 to use validates_formatting_of instead of validates_url_format_of. :)

No problem! Glad to be of help.


Rebuild assets and return back styles

Fix #980
Looks like assets were not rebuilt/committed on a PR that was merged to master that's why we lost all styles after installing Demo from scratch following the README
I just rebuilt the assets and committed changes here.

I don't understand this PR:

If I try to merge it, the tool we use says: "Unable to merge branch pull/982. Resolve the conflict by hand and start the command again" But there's no conflict.
If I try to recreate this PR myself, I can't. I rebuild assets ... but end with the same result as in the existing master branch of the repo.

So, I can't merge this ... and I can't reproduce this 🤔  Could you please double check what's going on here? Thanks.

Ah, you were faster than me :)
P.S. Not sure what was the problem though, glad you were able to merge it this way


Pass image as byte array not as file path

Hi,
Have you consider adding to your library possibility to pass image not as file path but using byte array? I am asking because I think that could speed up processing time in combination with own camera implementation.
Regards,
Daniel

Hi @LosDanieloss,
unfortunately not. My library is based on the OpenALPR and they only expose methods to pass the path of the image (https://github.com/SandroMachado/openalpr-android/blob/master/app/src/main/java/org/openalpr/AlprJNIWrapper.java).
Regards,
Sandro Machado


add support for posting GitHub commits

To use this, add a WebHook to your GitHub repository:
• Payload URL will be e.g. http://your.machine:9990/gibot/github
• Content Type can be application/json or application/x-www-form-urlencoded
• Secret: generate a strong password and set it as “GithubSecret” in JSON config
fixes #11

Yeah, I had it working before sending the PR of course :). I’ll deploy it onto one of my Raspberry Pis first, will share the config afterwards.


Gradle sync failed: Could not find com.afollestad:material-dialogs:<IP_ADDRESS>.

MaterialDialogs repository changed? I tried adding new repo in buildsystem/dependency.gradle, didn't work. How can i sync materialDialog?

Ok. Compiled.
In Buildsystem/Dependencies.gradle
add repository
maven { url "https://jitpack.io" }
and in ext
materialDialogsVersion = '<IP_ADDRESS>@aar'

presentationDependencies
materialDialogs:        "com.github.afollestad.material-dialogs:core:<IP_ADDRESS>@aar",


Reconsider usage of accessor properties

Is your feature request related to a problem?
Recent API refactoring replaced accessor properties and plain properties with methods. This will inadvertently increase the maintenance burden for maintainers of react-posprocessing if left as-is.
Describe the solution you'd like
Reconsider using a hybrid approach of methods and accessors properties if applicable.
Additional context
https://github.com/vanruesc/postprocessing/issues/279#issuecomment-1048704511

I'll copy the middle in here for reference:

we won't be able to set and, more importantly, spread props over passes, we'll have to know all props beforehand and translate them to functions. functions cannot be expressed declaratively, they are not serializable either.

good examples could be threejs, or the dom, they strike a good balance between atomics and more complex functions that will either carry out calculations or set multiple props at once. the upside for atomics is that they can easily by driven by state models and spread over the surface.
another upside is maintenance for abstractions of pp. if pp updates and introduces a new atomic, say foo, the userland solution or library using it just needs to npm update and foo will work without having to adjust the abstraction.
we are also publishing types for raw postprocessing, https://github.com/pmndrs/react-postprocessing/blob/master/types/postprocessing.d.ts that would be another "abstraction" that's currently quite simple to adjust. we were thinking about adding it to microsofts @types/postprocessing

good examples could be threejs, or the dom, they strike a sensible balance between atomics and more complex functions that will either carry out calculations or set multiple props at once.

That sounds reasonable. One motivation behind the move towards methods was that a lot of settings on effects need to trigger shader recompilations to take effect. Using method calls makes it clear that changes will be expensive as opposed to just changing the value of a seemingly harmless property.

Getter and setter methods have been converted into accessor properties in<EMAIL_ADDRESS>I had my concerns regarding accessors, but it's ultimately ease-of-use and consistency that matters.


Basic auth fixed

Issue: When using AlwaysMitm ext/auth/basic.go would attempt to authenticate requests twice resulting in the 407 unauthorized message.
This fixes two outstanding issues with the basic auth behavior of this library.

BasicConnect handler was preventing other handlers from running (AlwaysMitm)
Basic was trying to authenticate connection that was already authenticated by BasicConnect

Resolves: https://github.com/elazarl/goproxy/issues/309, https://github.com/elazarl/goproxy/issues/416
Below is a simple test case to validate the behavior before/after the patch:
package main

import (
	"flag"
	"log"
	"net"
	"net/http"
	"regexp"

	"github.com/elazarl/goproxy"
	"github.com/elazarl/goproxy/ext/auth"
)

func handleRequest(req *http.Request, ctx *goproxy.ProxyCtx) (*http.Request, *http.Response) {
	ip, _, err := net.SplitHostPort(req.RemoteAddr)
	if err != nil {
		log.Print(err)
	}

	log.Printf("[%d] %s --> %s %s", ctx.Session, ip, req.Method, req.URL)

	return req, nil
}

func main() {
	verbose := flag.Bool("v", false, "should every proxy request be logged to stdout")
	addr := flag.String("addr", ":8080", "proxy listen address")
	flag.Parse()
	username, password := "foo", "bar"
	hostmatch := "google.com|neverssl.com|apache.org"
	proxy := goproxy.NewProxyHttpServer()
	auth.ProxyBasic(proxy, "Auth", func(user, passwd string) bool {
		return user == username && password == passwd
	})
	proxy.OnRequest(goproxy.ReqHostMatches(regexp.MustCompile(hostmatch))).
		HandleConnect(goproxy.AlwaysMitm)
	proxy.OnRequest().DoFunc(handleRequest)
	proxy.Verbose = *verbose
	log.Fatal(http.ListenAndServe(*addr, proxy))
}

@elazarl Could you merge this PR?

I'm very careful about adding yet another field to the context. Can we do it in some other way?

Actually I did't think another way :) But this PR working correctly for me.

Sorry, I had a problem after i implemented it.
'ctx.Authenticated' not returns 'true' for http connect methods.
I am getting 407 (proxy auth required) for this code. Is there something I did wrong?
`addr := flag.String("addr", ":8080", "proxy listen address")
hostmatch := flag.String("hostmatch", "^.*$", "hosts to trace (regexp pattern)")
verbose := flag.Bool("v", true, "verbose output")
flag.Parse()
log.SetFlags(log.Lmicroseconds)

proxy := goproxy.NewProxyHttpServer()

auth.ProxyBasic(proxy, "Auth", func(user, passwd string) bool {
	return true
})

proxy.OnRequest(goproxy.ReqHostMatches(regexp.MustCompile(*hostmatch))).
	HandleConnect(goproxy.AlwaysMitm)

proxy.OnRequest().DoFunc(handleRequest)

proxy.Verbose = *verbose
log.Fatal(http.ListenAndServe(*addr, proxy))`

@elazarl Given the importance of the MR, could you do the change you are suggesting? Best regards!

这个啥时候能修复呢

@guanyufen123 just fork and merge the change. This is what happens when the community needs and demand things but authors are reluctant to listen.

@thalesfsp can you please explain me again, why using the User pointer is not a good solution in this case?
I'm very open to listen, but was not able to spurr discussion.


More flexible options around customBoard namespace selection

Related to https://kyverno.github.io/policy-reporter-docs/policy-reporter-ui/custom-boards.html#namespace-selector
Currently I get the following response from the UI when no namespaces are specified

No configured namespaces are found

    customBoards:
        [
          {
            name: 'My Custom Board',
            clusterScope: { enabled: false },
            sources: {
              list: ['Trivy Vulnerability'],
            },
            namespaces: {}
          },
        ],

I'm not sure selectors at the moment are powerful enough since I don't think they let me select multiple values with the same key. In our case we don't have a single label selector that is applied to all namespaces (seems overkill to add it just for this purpose).
Something like https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#set-based-requirement would be ideal here I think...
Failing that, shouldn't the default show all namespaces rather than the "No configured namespaces are found" response?

Sorry for the late response.
So I recently added support for more "operations":
https://github.com/kyverno/policy-reporter/blob/main/charts/policy-reporter/values.yaml#L932
So you can check if an label exists - independent of the value. You can check for a list of values or if a label does not exist. Does this help with your issue?


Equity Datasets Gaps

In advance of the next article for APA we need to add a few resources:

[ ] https://onemap.cdc.gov/portal/apps/sites/#/eji-explorer

Hi David,
Here are a few resources i'm aware of/found:

USDOT Equitable Transportation Community (ETC) Explorer - [https://experience.arcgis.com/experience/0920984aa80a4362b8778d779b090723/page/ETC-Explorer---Homepage/]
Description: The U.S. DOT Equitable Transportation Community (ETC) Explorer is an interactive web application that uses 2020 Census Tracts and data, to explore the cumulative burden communities experience, as a result of underinvestment in transportation, in the following five components: Transportation Insecurity, Climate and Disaster Risk Burden, Environmental Burden, Health Vulnerability, and Social Vulnerability.
LEHD (if not already included should probably be included in the article- [https://lehd.ces.census.gov/]
**EPA Smart Location Database: **

Link 1: [https://www.epa.gov/smartgrowth/smart-location-mapping#SLD]
Link 2: [https://www.epa.gov/smartgrowth/smart-location-mapping]
**Description: **The Smart Location Database is a nationwide geographic data resource for measuring location efficiency. It includes more than 90 attributes summarizing characteristics such as housing density, diversity of land use, neighborhood design, destination accessibility, transit service, employment, and demographics. Most attributes are available for every census block group in the United States.

EPA EJ Screen Tool -  [https://www.epa.gov/ejscreen]
Description: _n order to better meet the Agency’s responsibilities related to the protection of public health and the environment, EPA has developed a new environmental justice (EJ) mapping and screening tool called EJScreen. It is based on nationally consistent data and an approach that combines environmental and demographic indicators in maps and reports. _
Open Trip Planner - [https://www.opentripplanner.org/]
GTFS - [https://gtfs.org/]

I think we need to add the USDOT too, but we cover LEHD elsewhere, but it is also an equity dataset in theory.
I think we have EJ Screen. We have SLD under built environment.
There are few datasets that frustratingly defy classification in one.

Recent commit addresses this.


0.6.0

upstream: https://github.com/FEniCS/ffcx/compare/v0.5.0...v0.6.0
needs https://github.com/conda-forge/fenics-basix-feedstock/pull/9

@conda-forge-admin please rerender


Greatly improve Try/Finally handing, particularly initialization checks.

This pulls in the changes of Checker Framework PR 1826, and makes a few
fixes of our own in how we handle try{...}finally{...} statements
without catch blocks.

This fixes #101 too right?

It should :) . Let me post a comment and they can check, since that doesn't have a full repro case.


luaformatter: fix x86_64 darwin

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 345839

x86_64-linux

:white_check_mark: 1 package built:

luaformatter

aarch64-linux

:white_check_mark: 1 package built:

luaformatter

x86_64-darwin

:white_check_mark: 1 package built:

luaformatter

aarch64-darwin

:white_check_mark: 1 package built:

luaformatter


refactor: type override instead of generic for locale type

Related to #7, WIP

Closing since we favored #10


Show derived speedtest data on the Explorer

Based on the data received from MOBILE PoC Oracle, show

Passed | Failed | No Data | Not Enough Data Speed Test Status
"Upload Speed" | "Download Speed" | "Latency" values that were used for determining Passed/Failed status or last measured in case of Not Enough Data
Informational copy.

Screens

Thanks,
This will be a very helpful new metric on explorer.
I do have a question about the test's. I have a ticket in with FF about not finding any speed test results in my magma logs. I think someone else in discord had this issue too, but did not see if it was resolved. Did see an attempt in the FF logs, but apparently that had an expired license?
I really want to make sure all is in order for the next stage of genesis, so any guidance would be appreciated.
Also, any time-line on when this will go live?
Thanks again
Jim

Duplicate of https://github.com/helium/explorer/issues/1063


How to implement actuator's action 'change' boundary?

Hi,
I'm a student  and I'm trying to use MuJoCo for robot control.
I'm looking for some help with action 'change' boundary ( not action boundary itself)
Here is a model which explains my question:
<actuator>
    <position class="hexy" name="FR1" joint="FR1" ctrlrange="-0.6 0.6"/>
    <position class="shin" name="FR2" joint="FR2" ctrlrange="-1.2 -0.2"/>
    <position class="foot" name="FR3" joint="FR3" ctrlrange="-0.2 0.6"/>
    <position class="hexy" name="MR1" joint="MR1" ctrlrange="-0.6 0.6"/>
    <position class="shin" name="MR2" joint="MR2" ctrlrange="-1.2 -0.2"/>
    <position class="foot" name="MR3" joint="MR3" ctrlrange="-0.2 0.6"/>
</actuator>

From above code, there is 6 actuators. and I set the boundary like ' ctrlrange="-0.6 0.6" ' for six actuators.
But, considering real robot deployment , there is also action change limit due to overloading of motors.
for example, 'FR1" motor's action(position) should satisfy this equation :
|| Action_fr1_{t+1}    -    Action_fr1_{ t }  ||   < 0 .1
How can I implement this equation on mujoco settings?
Thank you for reading my question!  : )

Have you tried using velocity control instead and limiting the range of each joint?
For example, <joint name="FR1" type="??" axis="?? ?? ??" limited="true" range"-0.6 0.6"/>


Unable to use site URL to connect to Craft nitro

Description
I cannot seem to use the SITE URL that I selected during the craft set up to access the craft website.
OR (maybe the issue is) - Nitro has not configured the host files to recognize the IP address of the site as the SITE URL
TLDR:
Q) is there a way to find out what IP address the nitro site is running on - like nitro open <sitename> ?
After posting the question I managed to find the answer to the Site IP address question:
By running: nitro bridge it will output the the IP address of the websites running on your machine
From docs: https://craftcms.com/docs/nitro/2.x/local-sharing.html
Q) is there a location to find out the sites details - or any errors to be addressed in its setup?
Q) can you download an earlier version of craft, or does the version of craft downloaded by Nitro match the version of PHP you set the project up with - so if you decide to run php 7.2 - Nitro downloads the version of Craft suited for PHP 7.2?
Steps to reproduce

Run nitro create <sitename>
Input required details - and have conformation of successful install
run nitro craft setup & complete
Try to acsess the site address: https://tutorial.nitro/ or http://tutorial.nitro/
presented with  This site can’t be reached

--
Any debugging steps would be really helpful (im very keen to use Nitro for local dev, but the set up has been bumpy) - thanks

I have the same issue on Mac. Just installed Nitro (running on alternative port 8080 for http).
I can connect to the database, all containers are running but I cannot get to the site.
I have Valet installed too, maybe that has something to do with it?

@TomDeSmet -
I found (from my above)
By running: nitro bridge it will output the the IP address of the websites running on your machine
From docs: https://craftcms.com/docs/nitro/2.x/local-sharing.html
If you see your craft website here and IP address - then you can use the IP address instead of the site name to access it.

I already tried that but it doesn't work for me because I get the following error when trying to go to the IP url.
I obscured some data here of course.
connecting to the-craft.nitro
Bridge server listening on http://XXX.XXX.X.XXX:8000
2022/02/08 17:55:42  /
2022/02/08 17:55:42 http: proxy error: dial tcp: lookup my-website.nitro on [2a02:1800:100::42:1]:53: no such host

@TomDeSmet This is kinda out of my depth - it has not been a easy set up on my end (using windows)....
But, check everything is running as required I guess??
Is the DB running? Check Docker

Command: nitro ls will list out the status as well:

If they have stopped you can start the process by using nitro start

Everything’s running fine. Not getting any errors of any meaning in the containers. I already stopped valet and restarted all containers. Nothing…

@TomDeSmet what output do you get when you run the command craft bridge?
Should be:

What error do you get once you try and go to that IP address that is listed - if it is listed?

@wallythewebdev as stated in a previous post above:
connecting to mywebsite.nitro
Bridge server listening on http://XXX.XXX.X.XXX:8000
2022/02/08 17:55:42  /
2022/02/08 17:55:42 http: proxy error: dial tcp <IP_ADDRESS>:80: connect: connection refused

@TomDeSmet

I have Valet installed too, maybe that has something to do with it?

Valet and Nitro will conflict, if you try mysite.nitro:8080 it should resolve?
@wallythewebdev

By running: nitro bridge it will output the the IP address of the websites running on your machine
From docs: https://craftcms.com/docs/nitro/2.x/local-sharing.html

The bridge command looks at your local machine IP (your laptop) and allows you to share a site on the network with another device (e.g. iPad or iPhone). Nitro runs everything in localhost/<IP_ADDRESS> so its not public to people on your network without the bridge command.

Hi @jasonmccallister - Thanks for the reply.
Thanks for mentioning the localhost/<IP_ADDRESS> address - however this does not connect to the site.
Also, the IP address nitro bridge provides is now showing an error:
connecting to tutorial.nitro
Bridge server listening on http://XXXXXXXX:8000
2022/02/08 19:03:47  /
2022/02/08 19:03:47 http: proxy error: dial tcp: lookup tutorial.nitro on XXXXXXXXXX: no such host

So you have any suggestions for how to debug the above (it worked yesterday after a fresh install).
Thanks

I already tried that and strange enough, now it works with the added port.
Is there a way to split valet and nitro or should I uninstall valet?

@wallythewebdev Check your host file, it should contain:
#<nitro>
<IP_ADDRESS> tutorial.nitro
#</nitro>

@TomDeSmet
Host file does not contain that: I manually added it and can access it from http://tutorial.nitro/ (which is great so thanks).
But this does make me wonder @jasonmccallister @TomDeSmet - is there a command missing to allow Nitro to update the host files & does this mean that Nitro needs to edit host files when it is started nitro start - Which if it is, is fine, I just need to make sure that it can if that is the case.
any suggestions?

My host file was edited when I added my project. So it's definitely possible. It prompts for your password when adding/creating a site to modify your host file.
And there's also the nitro hosts command.

#@wallythewebdev There is a technical limitation on Windows that does not allow us to edit the hosts file. This page has more details on how to use Nitro with Windows https://craftcms.com/docs/nitro/2.x/windows.html
Glad you got it sorted!

@TomDeSmet - Thanks for the suggestion - running nitro apply got it working by printing out the required host file path that needed to be added:

@jasonmccallister Ah that all makes way more sense now - thanks for the advice and pointing to the Docs.
Can I make a small UI suggestion for windows users regarding the docs, I know writing docs is not an easy task, and there is allot of information packed into them, but given the slightly different install process for windows and caveats (regarding limitations) - it might be best to separate out the docs into separate pages for Windows and Mac/Linux installs of Nitro.
One of the issues I came across was trying to piece together info from different doc pages instead of it being in one controlled flow of information that follows the install process.
Just some UX feedback, not a criticism, and I'm really grateful for the help you've given here.

Thank you and that is probably a good suggestion @wallythewebdev, I'm going to ping @mattstein and see if this is something he wants to add/improve on the documentation.
If we have this working, I think we are ok to close this issue out?

@jasonmccallister Yeah great and thanks for your help and @TomDeSmet as well -
if you want input on writing the docs - happy to help :)

Thanks @wallythewebdev!
If I’m understanding right, you’re saying it’d be easier to navigate Nitro + Windows docs if they were visually separated by that OS. I get that—there were enough Windows caveats that we separated out the install instructions by OS, and added that Development with Nitro and WSL2 page so we could (hopefully) call those things out clearly.
The ultimate goal, and the reason I’m hesitant to segregate the docs by OS, is to rejoin the docs flow for daily usage that shouldn’t vary significantly from one OS to another.
If there are more nuanced issues you had finding bits of information that were there I’d like to understand and address them, but I’m not sure about splitting the docs out by operating system. Let me know if I’m missing your point or if the unified-docs goal seems out of touch with reality! :)


LSTM is extremely slow ( 2 hours )

Hi. I'm trianing an LSTM network that takes 2 hours to train 1000 training data with only 2000 iterations. Why is it so very slow?
// learns if string is like a date

// get training data
const trainingData = [
    {"input":"33 minutes ago","output":"yes"},
    {"input":"20 hours ago","output":"yes"},
    {"input":"May 7 at 13:42 AM","output":"yes"},
    {"input":"Feb 21 at 8:43 AM","output":"yes"},
    {"input":"Jul 22, 2012 ","output":"yes"},
    {"input":"Apr 14, 2018 ","output":"yes"}
    // 1000 total...
]

const network = new brain.recurrent.LSTM();

// create configuration for training
const config = {
    iterations: 2000,
    log: true,
    logPeriod: 200,
    layers: [10],
    log(detail) {
        console.log(detail);
    }
};

network.train(trainingData, config);

const output = network.run('Apr 6, 2014');

console.log(`Is like a date: ${(output == 'yes') ? 'YES' : 'NO' }`);

Try to replace your outputs with 0 or 1 instead of 'no' / 'yes' since you only have two type of outputs
Maybe it will speed up the process a little

I didn't pay more attention to your trainingSet in my previous answer, but I see that you are trying to train your network with dates in the form of strings.
I suggest you to take a different approach by normalizing your data:
Maybe try to see what the similarities are in your data and use them in your trainingSet as inputs instead of a literal string
Example: hasSpaces, hasNumber, hasStrings, hasCommas, hasYear, ...
(I suggest you add more of those)
Make a short script before, reviewing all your data by checking if it meets the above criteria.
(e.g. if hasSpaces, then your first input value should be 1, and so on)
Then fill your trainingSet like that:
{
   input: [1, 0, 1, 1, 0], output: [0],
   input: [1, 1, 1, 1, 1], output: [1]
}

And when you want to use run, go through to same process

@tymmesyde That makes sense now. Thanks

@tymmesyde thank you so much

The training takes too long i.e. somewhere around 14 hours or even more..
My data set is having different output for different input strings..
Is there a way i can reduce my training time? Although i am storing the trained results in JSON and using that while retrieving the output..
Using Node with brain.js version 2.0.0-alpha.11
const trainingData = [
{"input":"How are you","output":"very well"},
{"input":"How have you been","output":"very well"},
{"input":"welcome to new york","output":"thanks"},
{"input":"welcome to our city","output":"thanks"},
{"input":"welcome to usa","output":"thanks"},
{"input":"Lets catchup today","output":"ofcourse"},
{"input":"Lets meet today","output":"ofcourse"}
...... many more....
//large data set with different responses for different scenarios..
]
const network = new brain.recurrent.LSTM();
// create configuration for training
const config = {
iterations: 10000,
log: true,
};
network.train(trainingData, config);

I am having the exact same problem as above.  Can someone please help me?

@ninjaferrari90 @Paulsy10 , this is not a bot, this is a neural net, a component to build your bot.
Read my answer above, you cannot feed plain text data to the neural net, you need to normalize your dataset first.

I  am still a bit confused on what you mean by "normalizing"... Do you mean to use numbers instead of strings?

I am still a bit confused on what you mean by "normalizing"... Do you mean to use numbers instead of strings?

Read the issue and my comment in response to this issue, this is explained in details.

I am still a bit confused on what you mean by "normalizing"... Do you mean to use numbers instead of strings?

Read the issue and my comment in response to this issue, this is explained in details.
I have a different situation where I am not using dates and just training it to chat. I don't see any similiarties with my text.

This is the same issue, you need to normalize your dataset.
It isn't meant to be fed with text data. However you can give it numeric values, ranging from 0 to 1.
You need to find a way to translate those text values into readable ones for the net.
In your case if you just want to make a simple answers bot, you only need to create a dictionary of strings like so:
Questions:
How are you = 0
How have you been = 1
...

Answers:
very well = 0
thanks = 1
...

Then normalize your data by using your dictionary to translate these values to a [0,1] range.
{
    input: [0], // How are you
    output: [0] // very well
},
{
    input: [1], // How have you been
    output: [0] // very well
}
...

More on the matter here:
https://github.com/cazala/synaptic/wiki/Normalization-101
https://github.com/adadgio/neural-data-normalizer
Hope it helps.


make organizer script more readable

Update the offset image and make organizer script more readable.
Really willing to see this repo be updated furthermore.

@scturtle
Removing hashlib infavor of sha256sum is not acceptable, as that would break support for windows platform.
I've altered this in the merge.
The general idea should be to have as much within py ecosystem as possible. I would have ditched hactool as example, if it were possible to extract exefs partitions and ncas without it. (see atmosphere_loader_patcher.py for example for non-hactool decompression and extraction of loader.kip)


swinUNETR not working due to out-of-memory error on Google Colab

I am trying to use swinUNETR with the tutorial on swin_unetr_btcv_segmentation_3d.ipynb.
However, I am facing an out-of-memory error on Google Colaboratory's free GPU, and the notebook is not running.
The error occurs at the following lines :
max_iterations = 5
eval_num = 5
post_label = AsDiscrete(to_onehot=14)
post_pred = AsDiscrete(argmax=True, to_onehot=14)
dice_metric = DiceMetric(include_background=True, reduction="mean", get_not_nans=False)
global_step = 0
dice_val_best = 0.0
global_step_best = 0
epoch_loss_values = []
metric_values = []
while global_step < max_iterations:
    global_step, dice_val_best, global_step_best = train(global_step, train_loader, dice_val_best, global_step_best)
model.load_state_dict(torch.load(os.path.join(root_dir, "best_metric_model.pth")))

Training (5 / 5 Steps) (loss=2.98188):  21%|██        | 5/24 [00:04<00:14,  1.30it/s]
Validate (X / X Steps) (dice=X.X):   0%|          | 0/6 [00:00<?, ?it/s]
Training (5 / 5 Steps) (loss=2.98188):  21%|██        | 5/24 [00:04<00:18,  1.04it/s]
---------------------------------------------------------------------------
OutOfMemoryError                          Traceback (most recent call last)
[<ipython-input-16-9717af412448>](https://localhost:8080/#) in <module>
     10 metric_values = []
     11 while global_step < max_iterations:
---> 12     global_step, dice_val_best, global_step_best = train(global_step, train_loader, dice_val_best, global_step_best)
     13 model.load_state_dict(torch.load(os.path.join(root_dir, "best_metric_model.pth")))

15 frames
[/usr/local/lib/python3.9/dist-packages/monai/networks/nets/swin_unetr.py](https://localhost:8080/#) in forward(self, x, mask)
    496         ].reshape(n, n, -1)
    497         relative_position_bias = relative_position_bias.permute(2, 0, 1).contiguous()
--> 498         attn = attn + relative_position_bias.unsqueeze(0)
    499         if mask is not None:
    500             nw = mask.shape[0]

OutOfMemoryError: CUDA out of memory. Tried to allocate 1.80 GiB (GPU 0; 14.75 GiB total capacity; 11.31 GiB already allocated; 638.81 MiB free; 13.02 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

I have tried adjusting PYTORCH_CUDA_ALLOC_CONF by setting it to max_split_size_mb:128, but I still face the same error.
To try and resolve this, I have reduced max_iterations and eval_num to 5. Additionally, I have reduced the num_workers for CacheDataset to 1 and the num_samples in the "Setup transforms for training and validation" part to 1.
I would appreciate any suggestions or solutions to resolve this issue. Thank you.

You could try this to reduce memory usage if the machine resources are limited:
Reduce the number of samples:
num_samples = 4
in
        RandCropByPosNegLabeld(
            keys=["image", "label"],
            label_key="label",
            spatial_size=(96, 96, 96),
            pos=1,
            neg=1,
            num_samples=num_samples,
            image_key="image",
            image_threshold=0,
        ),

This will decrease the actual batch size during training:

Thank you for your response and suggestion.
However, we have already reduced  num_samples to 1 in the code as follows.
num_samples = 1
os.environ["CUDA_DEVICE_ORDER"] = "PCI_BUS_ID"
device = torch.device("cuda" if torch.cuda.is_available() else "cpu")
train_transforms = Compose(
[
LoadImaged(keys=["image", "label"], ensure_channel_first=True),
ScaleIntensityRanged(
keys=["image"],
a_min=-175,
a_max=250,
b_min=0.0,
b_max=1.0,
clip=True,
),
CropForegroundd(keys=["image", "label"], source_key="image"),
Orientationd(keys=["image", "label"], axcodes="RAS"),
Spacingd(
keys=["image", "label"],
pixdim=(1.5, 1.5, 2.0),
mode=("bilinear", "nearest"),
),
Do you have any other suggestions or recommendations that we could try to further reduce memory usage or address this issue?
Thank you for your help.

what's the GPU memory on your side, SwinUNETR is a relative larger model, it probably needs at least 16G for a smooth train/validation/test, but it also depends on the data dimensions.

Thank you for your response and for letting us know about the memory requirements of SwinUNETR.
Our GPU memory is on Tesla T4（16GB）from Google Colaboratory(free).
However, I am following the tutorial on Google Colab, which is supposed to provide free GPU resources.
Therefore, I find it frustrating that the tutorial is not working as expected on a platform that is advertised to support this type of workload.
Even if the BTCV dataset is quite large, I can't get the tutorial does not work on free Google Colab.

No worries, thanks again on trying the SwinUNETR model and the tutorial.
Can you have a final try of these:

Double check whether the batch size = 1 and the number_smaple = 1.
Double check if the Out-of-memory (OOM) issue occurs at validation, if OOM in validation, you could set the slidingWindowInferce's sw_device to CPU following the MONAI doc API.
If above steps are still not working, you could do this:

Try run the tutorial and retrain SwinUNETR in a smaller patch size, such as 64x64x64 instread of 96x96x96, this will sacrifice a little of performance, but I feel it will work close to 96.
By doing this, you need to change according patch size in transforms and the SwinUNETR network definition, change all 96 to 64.

Hope these helps.

I changed 96x96x96 to 64x64x64, and it worked.
Thank you so much for your kind support.


Updated ASP.NET TypeScript skeleton

This fixes #325 by adding a Gulp task to handle running the jspm install command.
I also went ahead and added typings/main to the exclusion list for tsconfig.json. If this needs to be removed I'll be happy to update my PR. However, removing this does reintroduce #325 by adding 800+ errors in Visual Studio all having the error Duplicate identifier.

@RandomlyKnighted So removing typings/main causes the errors to go away. Are there any negative side-effects?

Correct, removing typings/main caused Visual Studio to compile with 0 errors. I have yet to find any side effects. I went through and tested the whole skeleton application. While doing that I had the JavaScript console window open and I never once received an error.

Wooah....line endings or something...looks like you changed everything. Can you try to fix it up so it only has the actual change?

Sure. Just give me a few minutes and I'll see what I can do.

@EisenbergEffect Sorry about that, I've disabled that feature in Visual Studio so it shouldn't happen again. Anyways, the line endings should be fixed now.

The typings change is documented(here)[https://github.com/typings/typings/blob/master/docs/faq.md#maindts-and-browserdts] and should be applied to all typescript skeletons.

@Gheoan Are you saying that the typings/main needs to be excluded from all of our TS skeletons? Or that we need to make some other change?

Yes, typings/main needs to be excluded from all ts skeletons.

@RandomlyKnighted I'm unfortunately going to have to ask you to rebase on master. There are conflicts due to changes that have been made in the skeletons. Can you do that for us please?

@EisenbergEffect Done

I still get merge conflicts for some reason. Let me try one more thing.


[SECURITY] Fix Temporary File Information Disclosure Vulnerability

Security Vulnerability Fix
This pull request fixes a Temporary File Information Disclosure Vulnerability, which existed in this project.
Preamble
The system temporary directory is shared between all users on most unix-like systems (not MacOS, or Windows). Thus, code interacting with the system temporary directory must be careful about file interactions in this directory, and must ensure that the correct file posix permissions are set.
This PR was generated because a call to File.createTempFile(..) was detected in this repository in a way that makes this project vulnerable to local information disclosure.
With the default uname configuration, File.createTempFile(..) creates a file with the permissions -rw-r--r--. This means that any other user on the system can read the contents of this file.
Impact
Information in this file is visible to other local users, allowing a malicious actor co-resident on the same machine to view potentially sensitive files.
Other Examples

CVE-2020-15250 - junit-team/junit
CVE-2021-21364 - swagger-api/swagger-codegen
CVE-2022-24823 - netty/netty
CVE-2022-24823 - netty/netty

The Fix
The fix has been to convert the logic above to use the following API that was introduced in Java 1.7.
File tmpDir = Files.createTempFile("temp dir").toFile();

The API both creates the file securely, ie. with a random, non-conflicting name, with file permissions that only allow the currently executing user to read or write the contents of this file.
By default, Files.createTempFile("temp dir") will create a file with the permissions -rw-------, which only allows the user that created the file to view/write the file contents.
:arrow_right: Vulnerability Disclosure :arrow_left:
:wave: Vulnerability disclosure is a super important part of the vulnerability handling process and should not be skipped! This may be completely new to you, and that's okay, I'm here to assist!
First question, do we need to perform vulnerability disclosure? It depends!

Is the vulnerable code only in tests or example code? No disclosure required!
Is the vulnerable code in code shipped to your end users? Vulnerability disclosure is probably required!

Vulnerability Disclosure How-To
You have a few options options to perform vulnerability disclosure. However, I'd like to suggest the following 2 options:

Request a CVE number from GitHub by creating a repository-level GitHub Security Advisory. This has the advantage that, if you provide sufficient information, GitHub will automatically generate Dependabot alerts for your downstream consumers, resolving this vulnerability more quickly.
Reach out to the team at Snyk to assist with CVE issuance. They can be reached at the Snyk's Disclosure Email.

Detecting this and Future Vulnerabilities
This vulnerability was automatically detected by GitHub's CodeQL using this CodeQL Query.
You can automatically detect future vulnerabilities like this by enabling the free (for open-source) GitHub Action.
I'm not an employee of GitHub, I'm simply an open-source security researcher.
Source
This contribution was automatically generated with an OpenRewrite refactoring recipe, which was lovingly hand crafted to bring this security fix to your repository.
The source code that generated this PR can be found here:
SecureTempFileCreation
Opting-Out
If you'd like to opt-out of future automated security vulnerability fixes like this, please consider adding a file called
.github/GH-ROBOTS.txt to your repository with the line:
User-agent: JLLeitschuh/security-research
Disallow: *

This bot will respect the ROBOTS.txt format for future contributions.
Alternatively, if this project is no longer actively maintained, consider archiving the repository.
CLA Requirements
This section is only relevant if your project requires contributors to sign a Contributor License Agreement (CLA) for external contributions.
It is unlikely that I'll be able to directly sign CLAs. However, all contributed commits are already automatically signed-off.

The meaning of a signoff depends on the project, but it typically certifies that committer has the rights to submit this work under the same license and agrees to a Developer Certificate of Origin
(see https://developercertificate.org/ for more information).
- Git Commit Signoff documentation

If signing your organization's CLA is a strict-requirement for merging this contribution, please feel free to close this PR.
Sponsorship & Support
This contribution is sponsored by HUMAN Security Inc. and the new Dan Kaminsky Fellowship, a fellowship created to celebrate Dan's memory and legacy by funding open-source work that makes the world a better (and more secure) place.
This PR was generated by Moderne, a free-for-open source SaaS offering that uses format-preserving AST transformations to fix bugs, standardize code style, apply best practices, migrate library versions, and fix common security vulnerabilities at scale.
Tracking
All PR's generated as part of this fix are tracked here: https://github.com/JLLeitschuh/security-research/issues/18

Please STOP attempting to create FUD with "Security" PRs in test code.

I'm going to attempt to rewrite the recipe a bit so that it only creates a PR if it fixes a problem both in non-test code. When production code is fixed, test code will also be addressed.
IE.

Vulnerability in non-test -> PR non-test code
Vulnerability in test -> no PR
Vulnerability in non-test & test -> PR non-test and test code

Thoughts?

It would be irrelevant since you are unwilling to follow our disclosure process described at https://commons.apache.org/security.html


[buildfix] delete alink_sample project for GD32F4xx

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Cheng-SG:x: AlenXiaoYou have signed the CLA already but the status is still pending? Let us recheck it.


Resolve the #280 issue

Improved the UI of footer section of the Iskcon event page and home page. And I have already tested

Pls attach the screenshot of your changes here @harshita-india

https://github.com/akshitagupta15june/Moksh/assets/69025470/dc1633c5-adf4-43c7-a2fc-4960425e6361

Pls attach the screenshot of your changes here @harshita-india

Added please check

updated footer

please follow same colour scheme also add same footer as index.html

should i make same footer for all pages. I think i will look nice if all pages would have same footer and also user friendly

I think adding navigation links in the footer seems a little redundant because we have an open navbar on all pages.
We are planning to add social media links and GitHub stats and for that we will be utilising footer section.
@akshitagupta15june Feedback ?

Ok , I should change the iscon event footer and remove quick links from it and make it same as home page footer

removed the quick links page from the iscon and home page

Reference

should i commit it??

update your code also please keep the current index.html as it is the colours should be same


Plaiceholder v3

📝 Changed routes:

/about

(view full size)

Commit 8b840eecc9522832cd935864daa1be50ccd83eb5 (https://tadashi0713dev-iz5pn1i7c-tadashi0713.vercel.app).