Add caching to mongodb connector

Description
Currently, we will reestablish connections to the MongoDB via pymongo every time we try to fetch any data. We should introduce some caching to improve performance and reduce resource costs. We can take inspiration from the enterprise version
MongoDB connector function is in src/taipy/core/common/_mongo_connector.py under the name _connect_mongodb()

This ticket has already been fixed

This ticket has already been fixed


Plugin cannot detect STM32CubeIDE

Type: Bug Report
Describe the bug

OS and Version: Mac os 12.5.1
VS Code Version: 1.71
Embedded Tools Extension Version: 0.3.220903001
Target embedded device:
RTOS version:
Other extensions you installed (and if the issue persists after disabling them):
A clear and concise description of what the bug is.

Plugin does not detect STM32CubeIDE but ide was installed. Additionally I cannot select .cproject file - possibility for selecting this file is disabled.

@Michal123456747 this issue should now be fixed in the pre-release version of Embedded Tools. Click "Switch to Pre-Release Version" and ensure you have version v0.3.220909001 or later installed. Note that code must exist on the PATH environment variable for conversion to be successful. If it's not already, follow these steps to add it.

Now plugin works correctly. Really thank you for help. Unfortunately I get error, when I'm starting debugging. I will open new issue.


[Spike: 6hr] Erik to draft a vision on good community citizen work

Goal
To formulate a vision in text, conveying how team members could invest time and coordinate around contributing to various open source ecosystems and individual projects under the "good community citizen" time allocation.
Qualities of the text:

Includes concrete and easily adoptable practices
Includes motivation of choices compared to alternatives

Clarifies alignment with 2i2c mission and values

Definition of done

[ ] Erik spends up to 6 hours focused towards the goal

No time was allocated


Also check for errors in x86_64-xlate.pl.

In https://github.com/openssl/openssl/pull/10883, I'd meant to exclude
the perlasm drivers since they aren't opening pipes and do not
particularly need it, but I only noticed x86_64-xlate.pl, so
arm-xlate.pl and ppc-xlate.pl got the change.
That seems to have been fine, so be consistent and also apply the change
to x86_64-xlate.pl. Checking for errors is generally a good idea.

Merged to master.  Thanks.


Refactor email-client and email-server to mail

@Pharb: This is just for the refactoring, actual functinality additions are for later.

LGMT


Handle composer versions without composer/semver enabled

Fixes #8.
On some composer versions, semver package is not available.
In this case, use the old comparator and version constraint.
I added a special case on Travis for this: https://travis-ci.org/Soullivaneuh/composer-versions-check/jobs/83852780
Thanks @OskarStark for issue reporting. :+1:

:+1:

New patch version incoming.

Tagged: https://github.com/Soullivaneuh/composer-versions-check/releases/tag/v1.0.1


Vulnerabilty with ejs which is dependant on @angular-eslint/builder

Command
new
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Create new Angular v16 project.
Run npm audit in the project folder
The devDependencies
@angular-eslint/builder": 16.2.0
Minimal Reproduction
Create new Angular v16 project.

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1602.5 (cli-only)
@angular-devkit/core         16.2.5 (cli-only)
@angular-devkit/schematics   16.2.5 (cli-only)
@schematics/angular          16.2.5 (cli-only)

Anything else relevant?
No response

Hi, @angular-eslint is not maintained by the Angular team. Please refer to @angular-eslinthttps://github.com/angular-eslint/angular-eslint


setup React

"This pull request adds a basic React frontend "Hello World" feature that is nested within an existing Rails app backend. The front end is built using React and is connected to the backend using an API.
The feature can be accessed by navigating to the '/Greeting' route in the Rails app.
This feature serves as a starting point for future development of the application's front end.
Please review and test thoroughly before merging."

Hi @andym80,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that did not meet the minimum requirements. Here are the reasons;

[ ] Linters not set up for our frontend project
[ ] README file is not descriptive and missing the main headers as we have in our backend

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Open Order Time Not Set

Expected Behavior
When LEAN fetches an open order, we get the time is was recorded by IB.
Actual Behavior
The order timestamp is DateTime.MinValue.
Potential Solution

Reproducing the Problem
Open Limit Order for MES, for example.
Deploy algorithm to IB.

2024-06-24T22:10:23.8663356Z TRACE:: InteractiveBrokersBrokerage.HandleOpenOrder(): OrderId: -2, Contract: FUT MES USD CME, OrderStatus: Submitted
2024-06-24T22:10:23.8762989Z ERROR:: InteractiveBrokersBrokerage.HandleOpenOrder(): Unable to locate order with BrokerageID -2
2024-06-24T22:10:23.9069760Z TRACE:: InteractiveBrokersBrokerage.HandleOrderStatusUpdates(): OrderId: -2, Status: Submitted, Filled: 0, Remaining: 1, AverageFillPrice: 0, PermId:<PHONE_NUMBER>, ParentId: 0, LastFillPrice: 0, ClientId: 0, WhyHeld: ,MktCapPrice: 0
2024-06-24T22:10:23.9070630Z ERROR:: InteractiveBrokersBrokerage.HandleOrderStatusUpdates(): Unable to locate order with BrokerageID -2

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

This is a limitation of the IB API, this information is currently not available

Could you be more specific regarding the limitation? If I query endpoint /iserver/account/orders, it provides lastExecutionTime, which is much better than 0000-12-31 19:36:45.
Reference: https://www.interactivebrokers.eu/campus/ibkr-api-page/webapi-doc/#monitoring-live-orders-33


gui-wm/river: Fix wlroots dependency.

River 0.2.6 will not build against wlroots 0.17.
Found this issue with the ebuild I submitted Yesterday. When building against wlroots 0.17, I would get an error message like this:
Build Summary: 29/32 steps succeeded; 1 failed (disable with --summary none)
install transitive failure
└─ install river transitive failure
   └─ zig build-exe river ReleaseSafe native 3 errors
deps/zig-wlroots/src/wlroots.zig:190:9: error: zig-wlroots requires wlroots version 0.16
        @compileError("zig-wlroots requires wlroots version 0.16");
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
deps/zig-wlroots/src/render/drm_format_set.zig:2:11: error: C import failed
const c = @cImport(@cInclude("wlr/render/drm_format_set.h"));
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/wlr/render/drm_format_set.h:6:2: error: "Add -DWLR_USE_UNSTABLE to enable unstable wlroots features"
#error "Add -DWLR_USE_UNSTABLE to enable unstable wlroots features"

Going back to wlroots 0.16 resolved the issue.

I'll also try to sneak by the ARM64 support in the ebuild. I use river on my daily driver arm laptop where it works just fine...

I'll also try to sneak by the ARM64 support in the ebuild. I use river on my daily driver arm laptop where it works just fine...

haha, well given that you're the one maintaining this, sounds good with me!
Thanks!


chore(deps): update node.js to v14.21.3

This PR contains the following updates:

Package
Type
Update
Change

node

minor
14.17.4 -> 14.21.3

node
engines
minor
14.17.4 -> 14.21.3

Release Notes

nodejs/node (node)
v14.21.3: 2023-02-16, Version 14.21.3 'Fermium' (LTS), @richardlau
Compare Source
This is a security release.
Notable Changes
The following CVEs are fixed in this release:

CVE-2023-23918: Node.js Permissions policies can be bypassed via process.mainModule (High)
CVE-2023-23920: Node.js insecure loading of ICU data through ICU_DATA environment variable (Low)

More detailed information on each of the vulnerabilities can be found in February 2023 Security Releases blog post.
This security release includes OpenSSL security updates as outlined in the recent
OpenSSL security advisory.
This security release also includes an npm update for Node.js 14 to address a number
of CVEs which either do not affect Node.js or are low severity in the context of Node.js. You
can get more details for the individual CVEs in
nodejs-dependency-vuln-assessments.
Commits

[97a0443f13] - build: build ICU with ICU_NO_USER_DATA_OVERRIDE (RafaelGSS) nodejs-private/node-private#374
[9e6221529b] - deps: cherry-pick Windows ARM64 fix for openssl (Richard Lau) #4https://github.com/nodejs/node/pull/46566/46566)
[0d5f86451d] - deps: update archs files for OpenSSL-1.1.1t (RafaelGSS) #4https://github.com/nodejs/node/pull/46566/46566)
[8c11d17b40] - deps: upgrade openssl sources to 1.1.1t (RafaelGSS) #4https://github.com/nodejs/node/pull/46566/46566)
[224e93c9ef] - deps: upgrade npm to 6.14.18 (Ruy Adorno) #4https://github.com/nodejs/node/pull/45936/45936)
[d73ea4de13] - doc: clarify release notes for Node.js 14.21.2 (Richard Lau) #4https://github.com/nodejs/node/pull/45846/45846)
[f7892c16be] - lib: makeRequireFunction patch when experimental policy (RafaelGSS) nodejs-private/node-private#358
[fa115ee8ac] - module: protect against prototype mutation (Antoine du Hamel) #4https://github.com/nodejs/node/pull/44007/44007)
[83975b7fb4] - policy: makeRequireFunction on mainModule.require (RafaelGSS) nodejs-private/node-private#358
[a5f8798d7a] - test: avoid left behind child processes (Richard Lau) #4https://github.com/nodejs/node/pull/46276/46276)

v14.21.2: 2022-12-13, Version 14.21.2 'Fermium' (LTS), @richardlau
Compare Source
Notable Changes
OpenSSL 1.1.1s
This update is a bugfix release and does not address any security
vulnerabilities.
Root certificates updated to NSS 3.85
Certificates added:

Autoridad de Certificacion Firmaprofesional CIF A626340
Certainly Root E1
Certainly Root R1
D-TRUST BR Root CA 1 2020
D-TRUST EV Root CA 1 2020
DigiCert TLS ECC P384 Root G5
DigiCert TLS RSA4096 Root G5
E-Tugra Global Root CA ECC v3
E-Tugra Global Root CA RSA v3
HiPKI Root CA - G1
ISRG Root X2
Security Communication ECC RootCA1
Security Communication RootCA3
Telia Root CA v2
vTrus ECC Root CA
vTrus Root CA

Certificates removed:

Cybertrust Global Root
DST Root CA X3
GlobalSign Root CA - R2
Hellenic Academic and Research Institutions RootCA 2011

Time zone update to 2022f
Time zone data has been updated to 2022f. This includes changes to Daylight
Savings Time (DST) for Fiji and Mexico. For more information, see
https://mm.icann.org/pipermail/tz-announce/2022-October/000075.html.
Commits

[436a596e99] - crypto: update root certificates (Luigi Pinca) #4https://github.com/nodejs/node/pull/45490/45490)
[4b422d34af] - deps: V8: cherry-pick d2db7fa (Richard Lau) #4https://github.com/nodejs/node/pull/45785/45785)
[625f4bf3a9] - deps: update corepack to 0.15.1 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/45331/45331)
[48a9810de8] - deps: update corepack to 0.15.0 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/45235/45235)
[9f4e64b603] - deps: update timezone to 2022f (Richard Lau) #4https://github.com/nodejs/node/pull/45521/45521)
[f297b6bd21] - deps: update archs files for OpenSSL-1.1.1s (RafaelGSS) #4https://github.com/nodejs/node/pull/45272/45272)
[11629fef15] - deps: upgrade openssl sources to 1.1.1s (RafaelGSS) #4https://github.com/nodejs/node/pull/45272/45272)
[c3a90c4b44] - http2: fix memory leak when nghttp2 hd threshold is reached (rogertyang) #4https://github.com/nodejs/node/pull/41502/41502)
[785dc3efee] - module: cjs-module-lexer WebAssembly fallback (Guy Bedford) #4https://github.com/nodejs/node/pull/43612/43612)
[2dbeb889f6] - node-api: handle no support for external buffers (Michael Dawson) #4https://github.com/nodejs/node/pull/45181/45181)
[5b2ea124f3] - test: add test to validate changelogs for releases (Richard Lau) #4https://github.com/nodejs/node/pull/45325/45325)
[f13f889956] - test: add a test to ensure the correctness of timezone upgrades (Darshan Sen) #4https://github.com/nodejs/node/pull/45299/45299)
[5608e6fa72] - tools: update certdata.txt (Luigi Pinca) #4https://github.com/nodejs/node/pull/45490/45490)
[d6f1d7107b] - tools: have test-asan use ubuntu-20.04 (Filip Skokan) #4https://github.com/nodejs/node/pull/45581/45581)
[370a00f737] - tools: make license-builder.sh comply with shellcheck 0.8.0 (Rich Trott) #4https://github.com/nodejs/node/pull/41258/41258)

v14.21.1: 2022-11-04, Version 14.21.1 'Fermium' (LTS), @BethGriggs
Compare Source
This is a security release.
Notable changes
The following CVEs are fixed in this release:

CVE-2022-43548: DNS rebinding in --inspect via invalid octal IP address (Medium)

More detailed information on each of the vulnerabilities can be found in November 2022 Security Releases blog post.
Commits

[2b433af094] - inspector: harden IP address validation again (Tobias Nießen) nodejs-private/node-private#354

v14.21.0: 2022-11-01, Version 14.21.0 'Fermium' (LTS), @danielleadams
Compare Source
Notable changes

deps:

update corepack to 0.14.2 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/44775/44775)

src:

add --openssl-shared-config option (Daniel Bevenius) #4https://github.com/nodejs/node/pull/43124/43124)

Commits

[773f587912] - deps: cherry-pick libuv/libuv@3a7b955 (Ben Noordhuis) #4https://github.com/nodejs/node/pull/43950/43950)
[a1dea66956] - deps: cherry-pick libuv/libuv@abb109f (Ben Noordhuis) #4https://github.com/nodejs/node/pull/43950/43950)
[98c49d81f5] - deps: update corepack to 0.14.2 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/44775/44775)
[18c43c8518] - deps: update timezone to tz2022e (Richard Lau) #4https://github.com/nodejs/node/pull/45094/45094)
[a1f8e4db48] - deps: update corepack to 0.14.1 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/44704/44704)
[e55389ca86] - deps: update corepack to 0.14.0 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/44509/44509)
[0227462418] - deps: update corepack to 0.13.0 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/44318/44318)
[ee24c320ea] - deps: update corepack to 0.12.3 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/44229/44229)
[28e9891449] - deps: update corepack to 0.12.2 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/44159/44159)
[b6972c9df2] - deps: update corepack to 0.12.1 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/43965/43965)
[9d6cb3b5f1] - deps: update corepack to 0.12.0 (Node.js GitHub Bot) #4https://github.com/nodejs/node/pull/43748/43748)
[fa6c276b4f] - deps: update Corepack to 0.11.2 (Maël Nison) #4https://github.com/nodejs/node/pull/43402/43402)
[4f83d75626] - (SEMVER-MAJOR) src,doc,test: add --openssl-shared-config option (Daniel Bevenius) #4https://github.com/nodejs/node/pull/43124/43124)
[9487028043] - test: fix intl tests on small-icu builds (Antoine du Hamel) #4https://github.com/nodejs/node/pull/41939/41939)
[a1d52097f8] - tools: add more options to track flaky tests (Antoine du Hamel) #4https://github.com/nodejs/node/pull/43954/43954)

v14.20.1: 2022-09-23, Version 14.20.1 'Fermium' (LTS), @bengl
Compare Source
This is a security release.
Notable changes
The following CVEs are fixed in this release:

CVE-2022-32212: DNS rebinding in --inspect on macOS (High)
CVE-2022-32213: bypass via obs-fold mechanic (Medium)
CVE-2022-35256: HTTP Request Smuggling Due to Incorrect Parsing of Header Fields (Medium)

More detailed information on each of the vulnerabilities can be found in September 22nd 2022 Security Releases blog post.
Commits

[a9f1146b88] - http: disable chunked encoding when OBS fold is used (Paolo Insogna) nodejs-private/node-private#341
[a1121b456c] - src: fix IPv4 non routable validation (RafaelGSS) nodejs-private/node-private#337
[de80707870] - src: fix IS_LTS and IS_RELEASE flags (Richard Lau) #4https://github.com/nodejs/node/pull/43761/43761)

v14.20.0: 2022-07-07, Version 14.20.0 'Fermium' (LTS), @danielleadams prepared by @juanarbol
Compare Source
This is a security release.
Notable Changes

[8e8aef836c] - (SEMVER-MAJOR) src,deps,build,test: add OpenSSL config appname (Daniel Bevenius) #4https://github.com/nodejs/node/pull/43124/43124)
[98965b137d] - deps: upgrade openssl sources to 1.1.1q (RafaelGSS) #4https://github.com/nodejs/node/pull/43686/43686)

Commits

[b93e048bf6] - deps: update archs files for OpenSSL-1.1.1q (RafaelGSS) #4https://github.com/nodejs/node/pull/43686/43686)
[98965b137d] - deps: upgrade openssl sources to 1.1.1q (RafaelGSS) #4https://github.com/nodejs/node/pull/43686/43686)
[837a1d803e] - deps: update archs files for OpenSSL-1.1.1p (RafaelGSS) #4https://github.com/nodejs/node/pull/43527/43527)
[c5d9c9a49e] - deps: upgrade openssl sources to 1.1.1p (RafaelGSS) #4https://github.com/nodejs/node/pull/43527/43527)
[da0fda0fe8] - http: stricter Transfer-Encoding and header separator parsing (Paolo Insogna) #&#8203https://github.com/nodejs/node/pull/315ll/315)
[48c5aa5cab] - src: fix IPv4 validation in inspector_socket (Tobias Nießen) nodejs-private/node-private#320
[8e8aef836c] - (SEMVER-MAJOR) src,deps,build,test: add OpenSSL config appname (Daniel Bevenius) #4https://github.com/nodejs/node/pull/43124/43124)

v14.19.3: 2022-05-17, Version 14.19.3 'Fermium' (LTS), @richardlau
Compare Source
Notable Changes

This release updates OpenSSL to 1.1.1o. This update is not being treated as a security release as the issues addressed in OpenSSL 1.1.1o were assessed to not affect Node.js 14. See https://nodejs.org/en/blog/vulnerability/openssl-fixes-in-regular-releases-may2022/ for more information on how the May 2022 OpenSSL releases affects other Node.js release lines.
The list of GPG keys used to sign releases has been synchronized with the main branch.

Commits

[68397e49d9] - deps: update archs files for OpenSSL-1.1.1o (RafaelGSS) #4https://github.com/nodejs/node/pull/42956/42956)
[7f9a5ed4a8] - deps: upgrade openssl sources to 1.1.1o (RafaelGSS) #4https://github.com/nodejs/node/pull/42956/42956)
[61eba58cb6] - doc: add release key for Juan Arboleda (Juan José) #4https://github.com/nodejs/node/pull/42961/42961)

v14.19.2: 2022-05-04, Version 14.19.2 'Fermium' (LTS), @BethGriggs prepared by @juanarbol
Compare Source
Notable Changes
doc:

New release key for Bryan English

Learn more at: #4https://github.com/nodejs/node/pull/42102/42102)
Contributed by Bryan English (@bengl)
npm:

Upgrade npm to v6.14.17.

Learn more at: #4https://github.com/nodejs/node/pull/42900/42900)
Contributed by Ruy Adorno (@ruyadorno)
V8:

V8 had a stack overflow issue affecting the vm module, cherry-picking cc9a8a37445e
from V8 solves this issue.

Learn more at: #4https://github.com/nodejs/node/pull/41826/41826)
Contributed by Gus Caplan (@devsnek)

Using getHeapSnapshot() was causing a Node.js crash due a V8 issue, this is fixed by backporting 367b0c1e7a32
from V8.

Learn more at: #4https://github.com/nodejs/node/pull/42637/42637)
Contributed by Chengzhong Wu (@legendecas)
Commits

[c73ac527d6] - build: set DESTCPU correctly for 'make binary' on Apple Silicon (Chris Heisterkamp) #4https://github.com/nodejs/node/pull/40147/40147)
[dcaed6db24] - build: use ccache in make-v8.sh on ppc64le and s390x (Richard Lau) #4https://github.com/nodejs/node/pull/42204/42204)
[4203d132b1] - child_process: queue pending messages (Erick Wendel) #4https://github.com/nodejs/node/pull/41221/41221)
[a3ebdbfe8f] - deps: upgrade npm to 6.14.17 (Ruy Adorno) #4https://github.com/nodejs/node/pull/42900/42900)
[39e44f8382] - deps: V8: cherry-pick cc9a8a3 (Gus Caplan) #4https://github.com/nodejs/node/pull/41826/41826)
[b52a268b6f] - deps: V8: cherry-pick 367b0c1 (legendecas) #4https://github.com/nodejs/node/pull/42637/42637)
[77ba012065] - doc: fix documentation of FileHandle.prototype.appendFile (Antoine du Hamel) #4https://github.com/nodejs/node/pull/42588/42588)
[3d3d7ed1b7] - doc: specify flag needed for JSON and Wasm modules (Rich Trott) #4https://github.com/nodejs/node/pull/42736/42736)
[542d812c93] - doc: use openpgp.org for keyserver examples (Nick Schonning) #3https://github.com/nodejs/node/pull/39227/39227)
[7f2825b1a9] - doc: add release key for Bryan English (Bryan English) #4https://github.com/nodejs/node/pull/42102/42102)
[75302d3dce] - fs: fix write methods param validation and docs (Livia Medeiros) #4https://github.com/nodejs/node/pull/41677/41677)
[d4171e0eac] - stream: resume stream on drain (Robert Nagy) #4https://github.com/nodejs/node/pull/41848/41848)
[de474c8b6f] - worker: do not send message if port is closing (Rich Trott) #4https://github.com/nodejs/node/pull/42357/42357)

v14.19.1: 2022-03-17, Version 14.19.1 'Fermium' (LTS), @richardlau
Compare Source
This is a security release.
Notable Changes
Update to OpenSSL 1.1.1n, which addresses the following vulnerability:

Infinite loop in BN_mod_sqrt() reachable when parsing certificates (High)(CVE-2022-0778)
More details are available at https://www.openssl.org/news/secadv/20220315.txt

Commits

[b5c52e337e] - build: pin Windows GitHub runner to windows-2019 (Richard Lau) #4https://github.com/nodejs/node/pull/42350/42350)
[3b1a0b24f0] - deps: update archs files for OpenSSL-1.1.1n (Richard Lau) #4https://github.com/nodejs/node/pull/42347/42347)
[c83dd99e0b] - deps: upgrade openssl sources to 1.1.1n (Richard Lau) #4https://github.com/nodejs/node/pull/42347/42347)

v14.19.0: 2022-02-01, Version 14.19.0 'Fermium' (LTS), @richardlau
Compare Source
Notable Changes
Corepack
Node.js now includes Corepack, a script that acts as a bridge between Node.js projects and the package managers they are intended to be used with during development.
In practical terms, Corepack will let you use Yarn and pnpm without having to install them - just like what currently happens with npm, which is shipped in Node.js by default.
Please head over to the Corepack documentation page for more information on how to use it.
Contributed by Maël Nison - #3https://github.com/nodejs/node/pull/39608/39608)
ICU updated
ICU has been updated to 70.1. This updates timezone database to 2021a3, including bringing forward the start for DST for Jordan from March to February.
Contributed by Michaël Zasso - #4https://github.com/nodejs/node/pull/40658/40658)
New option to disable loading of native addons
A new command line option --no-addons has been added to disallow loading of native addons.
Contributed by Dominic Elm - #3https://github.com/nodejs/node/pull/39977/39977)
Updated Root Certificates
Root certificates have been updated to those from Mozilla's Network Security Services 3.71.
Contributed by Richard Lau - #4https://github.com/nodejs/node/pull/40280/40280)
Other Notable Changes

[0d448eaab5] - (SEMVER-MINOR) crypto: make FIPS related options always available (Vít Ondruch) #3https://github.com/nodejs/node/pull/36341/36341)
[004eafbebf] - (SEMVER-MINOR) lib: add unsubscribe method to non-active DC channels (simon-id) #4https://github.com/nodejs/node/pull/40433/40433)
[625be7585d] - (SEMVER-MINOR) lib: add return value for DC channel.unsubscribe (simon-id) #4https://github.com/nodejs/node/pull/40433/40433)
[607bc74eae] - (SEMVER-MINOR) module: support pattern trailers (Guy Bedford) #3https://github.com/nodejs/node/pull/39635/39635)
[f74fe2a59c] - (SEMVER-MINOR) src: make napi_create_reference accept symbol (JckXia) #3https://github.com/nodejs/node/pull/39926/39926)

Commits

[0231ffa501] - build: add --without-corepack (Jonah Snider) #4https://github.com/nodejs/node/pull/41060/41060)
[5389b8ab05] - crypto: update root certificates (Richard Lau) #4https://github.com/nodejs/node/pull/40280/40280)
[0d448eaab5] - (SEMVER-MINOR) crypto: make FIPS related options always available (Vít Ondruch) #3https://github.com/nodejs/node/pull/36341/36341)
[cd20ecc7cb] - deps: upgrade Corepack to 0.10 (Maël Nison) #4https://github.com/nodejs/node/pull/40374/40374)
[737df75e17] - (SEMVER-MINOR) deps: add corepack (Maël Nison) #3https://github.com/nodejs/node/pull/39608/39608)
[b85aa5a143] - deps: upgrade npm to 6.14.16 (Ruy Adorno) #4https://github.com/nodejs/node/pull/41603/41603)
[2755d391a5] - deps: update ICU to 70.1 (Michaël Zasso) #4https://github.com/nodejs/node/pull/40658/40658)
[3089326d89] - deps: update archs files for OpenSSL-1.1.1m (Richard Lau) #4https://github.com/nodejs/node/pull/41173/41173)
[59da7c12aa] - deps: upgrade openssl sources to 1.1.1m (Richard Lau) #4https://github.com/nodejs/node/pull/41173/41173)
[cede1f26f6] - deps: add -fno-strict-aliasing flag to libuv (Daniel Bevenius) #4https://github.com/nodejs/node/pull/40631/40631)
[4477da858f] - doc: fix corepack grammar for --force flag (Steven) #4https://github.com/nodejs/node/pull/40762/40762)
[5971d58600] - doc: add missing YAML tag in esm.md (Antoine du Hamel) #4https://github.com/nodejs/node/pull/41516/41516)
[e903798ae1] - doc: add note regarding unfinished TLA (Antoine du Hamel) #4https://github.com/nodejs/node/pull/41434/41434)
[a90defebcf] - esm: make process.exit() default to exit code 0 (Gang Chen) #4https://github.com/nodejs/node/pull/41388/41388)
[fc328f1ab0] - fs: nullish coalescing to respect zero positional reads (Omar El-Mihilmy) #4https://github.com/nodejs/node/pull/40716/40716)
[004eafbebf] - (SEMVER-MINOR) lib: add unsubscribe method to non-active DC channels (simon-id) #4https://github.com/nodejs/node/pull/40433/40433)
[625be7585d] - (SEMVER-MINOR) lib: add return value for DC channel.unsubscribe (simon-id) #4https://github.com/nodejs/node/pull/40433/40433)
[2c365961d0] - module: support pattern trailers for imports field (Guy Bedford) #4https://github.com/nodejs/node/pull/40041/40041)
[607bc74eae] - (SEMVER-MINOR) module: support pattern trailers (Guy Bedford) #3https://github.com/nodejs/node/pull/39635/39635)
[f74fe2a59c] - (SEMVER-MINOR) src: make napi_create_reference accept symbol (JckXia) #3https://github.com/nodejs/node/pull/39926/39926)
[b050c65885] - src: add option to disable loading native addons (Dominic Elm) #3https://github.com/nodejs/node/pull/39977/39977)
[c1695ac68a] - tools: update certdata.txt (Richard Lau) #4https://github.com/nodejs/node/pull/40280/40280)

v14.18.3: 2022-01-10, Version 14.18.3 'Fermium' (LTS), @richardlau
Compare Source
This is a security release.
Notable changes
Improper handling of URI Subject Alternative Names (Medium)(CVE-2021-44531)
Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.
Versions of Node.js with the fix for this disable the URI SAN type when checking a certificate against a hostname. This behavior can be reverted through the --security-revert command-line option.
More details will be available at CVE-2021-44531 after publication.
Certificate Verification Bypass via String Injection (Medium)(CVE-2021-44532)
Node.js converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.
Versions of Node.js with the fix for this escape SANs containing the problematic characters in order to prevent the injection. This behavior can be reverted through the --security-revert command-line option.
More details will be available at CVE-2021-44532 after publication.
Incorrect handling of certificate subject and issuer fields (Medium)(CVE-2021-44533)
Node.js did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.
Affected versions of Node.js do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.
More details will be available at CVE-2021-44533 after publication.
Prototype pollution via console.table properties (Low)(CVE-2022-21824)
Due to the formatting logic of the console.table() function it was not safe to allow user controlled input to be passed to the properties parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be __proto__. The prototype pollution has very limited control, in that it only allows an empty string to be assigned numerical keys of the object prototype.
Versions of Node.js with the fix for this use a null protoype for the object these properties are being assigned to.
More details will be available at CVE-2022-21824 after publication.
Thanks to Patrik Oldsberg (rugvip) for reporting this vulnerability.
Commits

[e2a74f3c99] - console: fix prototype pollution via console.table (Tobias Nießen) nodejs-private/node-private#307
[df1b2c33f6] - crypto,tls: implement safe x509 GeneralName format (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#300
[9f2c52617f] - src: add cve reverts and associated tests (Michael Dawson and Akshay Kumar) nodejs-private/node-private#300
[b14be42518] - src: remove unused x509 functions (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#300
[83d8f880bb] - tls: fix handling of x509 subject and issuer (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#300
[461a0c674b] - tls: drop support for URI alternative names (Tobias Nießen and Akshay Kumar) nodejs-private/node-private#300

v14.18.2: 2021-11-30, Version 14.18.2 'Fermium' (LTS), @richardlau
Compare Source
Notable changes
This release contains a c-ares update to fix a regression introduced in
Node.js 14.17.5 resolving CNAME records containing underscores
#3https://github.com/nodejs/node/issues/39780/39780).
Also included are commits to allow Node.js 14 to continue to build and
pass tests on our Jenkins CI, including adding Python 3.10 to the list
of allowable Python versions for building.
Commits

[7923c61a62] - build: pin build-docs workflow to Node.js 14 (Richard Lau) #4https://github.com/nodejs/node/pull/40939/40939)
[da356128fb] - build: support Python 3.10.0 (FrankQiu) #4https://github.com/nodejs/node/pull/40296/40296)
[9c3a85d279] - deps: update c-ares to 1.18.1 (Richard Lau) #4https://github.com/nodejs/node/pull/40660/40660)
[cd7c340545] - deps: V8: patch jinja2 for Python 3.10 compat (Michaël Zasso) #4https://github.com/nodejs/node/pull/40296/40296)
[6330d435f5] - doc: mark Node.js 10 as End-of-Life (Richard Lau) #3https://github.com/nodejs/node/pull/38482/38482)
[8ca082ec71] - doc: fix CJS-ESM selector in Safari (Bradley Farias) #4https://github.com/nodejs/node/pull/40135/40135)
[92490d1c89] - doc: add macOS arm64 experimental status (Michael Rienstra) #4https://github.com/nodejs/node/pull/40127/40127)
[8894bdd4d8] - lib: fix regular expression to detect `/` and `\` (Francesco Trotta) #&#8https://github.com/nodejs/node/pull/40325/pull/40325)
[704989b698] - test: deflake child-process-pipe-dataflow (Luigi Pinca) #4https://github.com/nodejs/node/pull/40838/40838)
[df401cd346] - test: update upload.zip to be uncorrupted (Greg Ziskind) #3https://github.com/nodejs/node/pull/37294/37294)
[aa947f7dbf] - tools: add script to update c-ares (Richard Lau) #4https://github.com/nodejs/node/pull/40660/40660)
[6b7b2bba41] - tools: patch jinja2 for Python 3.10 compat (Michaël Zasso) #4https://github.com/nodejs/node/pull/40296/40296)
[39583f77d8] - worker: avoid potential deadlock on NearHeapLimit (Santiago Gimeno) #3https://github.com/nodejs/node/pull/38403/38403)

v14.18.1: 2021-10-12, Version 14.18.1 'Fermium' (LTS), @danielleadams
Compare Source
This is a security release.
Notable changes

CVE-2021-22959: HTTP Request Smuggling due to spaced in headers (Medium)

The http parser accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS). More details will be available at CVE-2021-22959 after publication.

CVE-2021-22960: HTTP Request Smuggling when parsing the body (Medium)

The parse ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions. More details will be available at CVE-2021-22960 after publication.

Commits

[8c254ca7e4] - deps: update llhttp to 2.1.4 (Fedor Indutny) nodejs-private/node-private#285
[9b92ae2499] - http: add regression test for smuggling content length (Matteo Collina) nodejs-private/node-private#285
[f467539719] - http: add regression test for chunked smuggling (Matteo Collina) nodejs-private/node-private#285

v14.18.0: 2021-09-28, Version 14.18.0 'Fermium' (LTS), @targos
Compare Source
Notable Changes

[3a60de0135] - assert: change status of legacy asserts (James M Snell) #3https://github.com/nodejs/node/pull/38113/38113)
[df37c106a7] - (SEMVER-MINOR) buffer: introduce Blob (James M Snell) #3https://github.com/nodejs/node/pull/36811/36811)
[223494c548] - (SEMVER-MINOR) buffer: add base64url encoding option (Filip Skokan) #3https://github.com/nodejs/node/pull/36952/36952)
[14fc4ddabc] - (SEMVER-MINOR) child_process: allow options.cwd receive a URL (Khaidi Chu) #3https://github.com/nodejs/node/pull/38862/38862)
[b68b13acb3] - (SEMVER-MINOR) child_process: add timeout to spawn and fork (Nitzan Uziely) #3https://github.com/nodejs/node/pull/37256/37256)
[da98c9f99b] - (SEMVER-MINOR) child_process: allow promisified exec to be cancel (Carlos Fuentes) #3https://github.com/nodejs/node/pull/34249/34249)
[779310ac87] - (SEMVER-MINOR) child_process: add 'overlapped' stdio flag (Thiago Padilha) #2https://github.com/nodejs/node/pull/29412/29412)
[40eb3b79f1] - (SEMVER-MINOR) cli: add -C alias for --conditions flag (Guy Bedford) #3https://github.com/nodejs/node/pull/38755/38755)
[39eba0a2e1] - (SEMVER-MINOR) cli: add --node-memory-debug option (Anna Henningsen) #3https://github.com/nodejs/node/pull/35537/35537)
[d8d9a9628a] - (SEMVER-MINOR) dns: add "tries" option to Resolve options (Luan Devecchi) #3https://github.com/nodejs/node/pull/39610/39610)
[15ba19b020] - (SEMVER-MINOR) dns: allow --dns-result-order to change default dns verbatim (Ouyang Yadong) #3https://github.com/nodejs/node/pull/38099/38099)
[307c1d817f] - doc: refactor fs docs structure (James M Snell) #3https://github.com/nodejs/node/pull/37170/37170)
[9ee3f77e32] - (SEMVER-MINOR) errors: remove experimental from --enable-source-maps (Benjamin Coe) #3https://github.com/nodejs/node/pull/37362/37362)
[e73bfed2f4] - esm: deprecate legacy main lookup for modules (Guy Bedford) #3https://github.com/nodejs/node/pull/36918/36918)
[989c204a58] - (SEMVER-MINOR) fs: allow empty string for temp directory prefix (Voltrex) #3https://github.com/nodejs/node/pull/39028/39028)
[ef72490cde] - (SEMVER-MINOR) fs: allow no-params fsPromises fileHandle read (Nitzan Uziely) #3https://github.com/nodejs/node/pull/38287/38287)
[cad9d20f64] - (SEMVER-MINOR) fs: add support for async iterators to fsPromises.writeFile (HiroyukiYagihashi) #3https://github.com/nodejs/node/pull/37490/37490)
[2b0e2706c0] - fs: improve fsPromises readFile performance (Nitzan Uziely) #3https://github.com/nodejs/node/pull/37608/37608)
[fe12cc07b3] - (SEMVER-MINOR) fs: add fsPromises.watch() (James M Snell) #3https://github.com/nodejs/node/pull/37179/37179)
[2459c115a8] - (SEMVER-MINOR) fs: allow position parameter to be a BigInt in read and readSync (Darshan Sen) #3https://github.com/nodejs/node/pull/36190/36190)
[6544cfb4b9] - (SEMVER-MINOR) http2: add support for sensitive headers (Anna Henningsen) #3https://github.com/nodejs/node/pull/34145/34145)
[a6c6cbb4e6] - (SEMVER-MINOR) http2: allow setting the local window size of a session (Yongsheng Zhang) #3https://github.com/nodejs/node/pull/35978/35978)
[1e5aca550c] - inspector: mark as stable (Gireesh Punathil) #3https://github.com/nodejs/node/pull/37748/37748)
[93af04afbb] - (SEMVER-MINOR) module: add support for URL to import.meta.resolve (Antoine du Hamel) #3https://github.com/nodejs/node/pull/38587/38587)
[f9f9389d83] - (SEMVER-MINOR) module: add support for node:‑prefixed require(…) calls (ExE Boss) #3https://github.com/nodejs/node/pull/37246/37246)
[87c71065eb] - (SEMVER-MINOR) net: introduce net.BlockList (James M Snell) #3https://github.com/nodejs/node/pull/34625/34625)
[b421d99a48] - (SEMVER-MINOR) node-api: allow retrieval of add-on file name (Gabriel Schulhof) #3https://github.com/nodejs/node/pull/37195/37195)
[6a4811df8a] - (SEMVER-MINOR) os: add os.devNull (Luigi Pinca) #3https://github.com/nodejs/node/pull/38569/38569)
[4a88ddeeca] - (SEMVER-MINOR) perf_hooks: introduce createHistogram (James M Snell) #3https://github.com/nodejs/node/pull/37155/37155)
[1a6bf1c4a3] - (SEMVER-MINOR) process: add api to enable source-maps programmatically (legendecas) #3https://github.com/nodejs/node/pull/39085/39085)
[99735a6fe8] - (SEMVER-MINOR) process: add 'worker' event (James M Snell) #3https://github.com/nodejs/node/pull/38659/38659)
[3982919317] - (SEMVER-MINOR) process: add direct access to rss without iterating pages (Adrien Maret) #3https://github.com/nodejs/node/pull/34291/34291)
[526e6c7bde] - (SEMVER-MINOR) readline: add AbortSignal support to interface (Nitzan Uziely) #3https://github.com/nodejs/node/pull/37932/37932)
[e6eee08692] - (SEMVER-MINOR) readline: add support for the AbortController to the question method (Mattias Runge-Broberg) #3https://github.com/nodejs/node/pull/33676/33676)
[32de361d70] - (SEMVER-MINOR) readline: add history event and option to set initial history (Mattias Runge-Broberg) #3https://github.com/nodejs/node/pull/33662/33662)
[797f7f8a38] - (SEMVER-MINOR) repl: add auto‑completion for node:‑prefixed require(…) calls (ExE Boss) #3https://github.com/nodejs/node/pull/37246/37246)
[abfd71b64c] - (SEMVER-MINOR) src: call overload ctor from the original ctor (Darshan Sen) #3https://github.com/nodejs/node/pull/39768/39768)
[1efae01b18] - (SEMVER-MINOR) src: add a constructor overload for CallbackScope (Darshan Sen) #3https://github.com/nodejs/node/pull/39768/39768)
[f7933804ba] - (SEMVER-MINOR) src: allow to negate boolean CLI flags (Michaël Zasso) #3https://github.com/nodejs/node/pull/39023/39023)
[6d06ac2202] - (SEMVER-MINOR) src: add --heapsnapshot-near-heap-limit option (Joyee Cheung) #3https://github.com/nodejs/node/pull/33010/33010)
[577d228ca0] - (SEMVER-MINOR) src: add way to get IsolateData and allocator from Environment (Anna Henningsen) #3https://github.com/nodejs/node/pull/36441/36441)
[658a266cd4] - (SEMVER-MINOR) src: allow preventing SetPrepareStackTraceCallback (Shelley Vohr) #3https://github.com/nodejs/node/pull/36447/36447)
[f421422ea4] - (SEMVER-MINOR) src: add maybe versions of EmitExit and EmitBeforeExit (Anna Henningsen) #3https://github.com/nodejs/node/pull/35486/35486)
[a62d4d60f4] - (SEMVER-MINOR) stream: add readableDidRead if has been read from (Robert Nagy) #3https://github.com/nodejs/node/pull/39589/39589)
[63502131a3] - (SEMVER-MINOR) stream: pipeline accept Buffer as a valid first argument (Nitzan Uziely) #3https://github.com/nodejs/node/pull/37739/37739)
[68bbebd42c] - (SEMVER-MINOR) tls: allow reading data into a static buffer (Andrey Pechkurov) #3https://github.com/nodejs/node/pull/35753/35753)
[1cbb74d63d] - (SEMVER-MINOR) url: expose urlToHttpOptions utility (Yongsheng Zhang) #3https://github.com/nodejs/node/pull/35960/35960)
[8eb11356dd] - (SEMVER-MINOR) util: expose toUSVString (Robert Nagy) #3https://github.com/nodejs/node/pull/39814/39814)
[84fcdc3074] - (SEMVER-MINOR) v8: implement v8.stopCoverage() (Joyee Cheung) #3https://github.com/nodejs/node/pull/33807/33807)
[b238b6bf17] - (SEMVER-MINOR) v8: implement v8.takeCoverage() (Joyee Cheung) #3https://github.com/nodejs/node/pull/33807/33807)
[9f6bc58da8] - (SEMVER-MINOR) worker: add setEnvironmentData/getEnvironmentData (James M Snell) #3https://github.com/nodejs/node/pull/37486/37486)

Commits
Semver-minor commits

[f3563d3197] - (SEMVER-MINOR) async_hooks: use new v8::Context PromiseHook API (Stephen Belanger) #3[https://github.com/nodejs/node/pull

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Superseded by https://github.com/apollographql/apollo-ios-dev/pull/151.


Second milestone for Portfolio mobile project

This is my "Portfolio: setup a mobile project" from week # 1 at Microverse Program. I chose template number one from Figma site.
In this project you will find:

A portfolio setup mobile project.
The index.html and styles.css files are based on the Figma Microverse Template number 1.
Use of flexbox and grid tools.
Styling the project according to the project requirements.
Building the header, navbar, headline and hamburger menu.

I appreciate your kind review in order to make the corrections as soon as possible.
Thanks in advance.

Changes were made according to your suggestions, thank you @Owusu-Desmond !!!

Hi @Shedrack-Sunday, thanks for the inputs. I take note and applied the requested changes.!!

Great @oovillagran. Be fast so you get reviewed before the deadline

Hi @oovillagran ,
Congratulations! 🎉 Your project is complete and ready to be merged! 🚀

Highlights

Very Nice UI ✔
Linters green ✔
Descriptive PR ✔

Optional Suggestions 💡

While these comments with the [OPTIONAL] prefix won't prevent the approval of this pull request, I strongly recommend taking them into account as they can improve your code. Some of them were missed by the previous reviewer and addressing them will really enhance your application.

Cheers and Happy coding!👏👏👏
If you have any questions or need clarification on anything, feel free to leave a comment in the pull request thread and don't forget to tag me so I'll receive the notification.
As per the Code reviews limits policy, you have a limited number of reviews per project. If you feel that the code review was unfair, you can request a second opinion using this form.
Once again, congratulations on completing this project! 🎉

Thank you!!!


[BLOCKED] Set content type via serializer

This PR is based off #175, so it shouldn't be merged until that one is.
This leverages the new "pass the entire response to the serializer" to change the out-of-the-box serializers to set an appropriate Content-Type header on the response.

Note: this would supercede #158


IBM Z DFLTCC: Buffer deflate() input data

Hi,
I'd like to gather some opinions on how to proceed with this.
I tried to initiate a discussion on the zlib mailing list, but it never got past the moderator, so only people on Cc: received my message:
Hello zlib developers,

I've been investigating a problem in the QEMU test suite on IBM Z [1]
[2] in connection with the IBM Z compression accelerator patch [3].

The problem is that a QEMU thread compresses data that is being
modified by another QEMU thread. zlib manual [4] does not state that
this is safe, however, the current stable zlib in fact tolerates it.

The accelerator, however, does not: not only what it compresses ends up
being unpredictable - QEMU actually resolves this just fine -
but the accelerator's internal state also ends up being corrupted.

I have a design question in connection to this: does zlib guarantee
that modifying deflate() input concurrently with deflate() is safe?
Or does it reserve the right to change this in the future versions?

Cc:ing zlib-ng folks for their opinion as well.

[1] https://lists.gnu.org/archive/html/qemu-devel/2022-03/msg06841.html
[2] https://lists.gnu.org/archive/html/qemu-devel/2022-04/msg00329.html
[3] https://github.com/madler/zlib/pull/410
[4] https://zlib.net/manual.html

Best regards,
Ilya

So far I got only the following responses from Dr. David Alan Gilbert:
Specifically what qemu does is :

    a) write block of RAM
    b) <notices block changed)
    c) write block of RAM again

we don't care whether (a)'s data is coherent on the destination
since we know we're going to keep rewriting it (c) until it stabilises.
So we accept undefined decoding of (a) under the assumption that the
stream will still be a valid stream and that a change in one instance
won't affect a future encoding to be invalid.  Is that assumption
correct?

and from @mtl1979:
Then the only issue is that the internal state used by hardware deflate
acceleration gets out of sync when the data is changed and compression is
restarted from known "good" position... As I said, in that case, the internal
state used by the accelerator needs to be either reset or resynced with the
state structure. As the code flow is unique to this specific "accelerator", it
is responsibility of the accelerator to detect it, not generic compression
code (in either zlib or zlib-ng).

I put some more details regarding the fix into the commit message: https://github.com/zlib-ng/zlib-ng/commit/28429507d69a5138a2f83ff3dba38e34cb56480e
Best regards,
Ilya

There was some talk outside the mailing list, but no word from Mark Adler what is his "official" opinion about if zlib should tolerate it or not.

I can not speak for what zlib intends to support or not, in our compat-mode we attempt to be as compatible with zlib as we can, so this would depend on the zlib implementation (I realize this might be something madler would have to make a new policy about, and that he might in fact not clarify this).
But I think we could discuss whether zlib-ng in native-mode should clarify whether we want to restrict such usage.
My personal opinion is that while zlib-ng has the pointer to the data and is executing on it, nobody else should be touching that data and that it is the responsibility of the application to make sure that is the case.
On a related note; A pro if we were to always copy input to an internal buffer would be that we can be certain of alignment and extra trailing buffer space (in relation to vector operations).
The big con is that copying to a buffer is always slower than zero-copy, and zero-copy is IMO a very good thing to strive towards. Also buffers occupy more ram and could push other things out of cache.

I can not speak for what zlib intends to support or not, in our compat-mode we attempt to be as compatible with zlib as we can, so this would depend on the zlib implementation (I realize this might be something madler would have to make a new policy about, and that he might in fact not clarify this).
But I think we could discuss whether zlib-ng in native-mode should clarify whether we want to restrict such usage. My personal opinion is that while zlib-ng has the pointer to the data and is executing on it, nobody else should be touching that data and that it is the responsibility of the application to make sure that is the case.
On a related note; A pro if we were to always copy input to an internal buffer would be that we can be certain of alignment and extra trailing buffer space (in relation to vector operations). The big con is that copying to a buffer is always slower than zero-copy, and zero-copy is IMO a very good thing to strive towards. Also buffers occupy more ram and could push other things out of cache.

Yep, our migration code has the same challenge of course; if we know zlib is defined to need the copy then that's fine and we can do it, but otherwise as you say it eats ram and cpu.  The code was originally written around just a write()/sendmsg and has had the compression layer inserted into it;  the 'write' case is fine with the data changing underneath us because of the structure of what's written (anything that changes always sets a flag to say we need to rewrite again later); so we're OK with undefined ness and don't care about the data that ends up in the block when received, but we don't expect the undefinedness to spil over into future blocks.

Use PREFIX() for some of the Z_INTERNAL symbols should be its own PR imo. It's been mentioned in issue #1279 also.

I need to rebase this, this part has already been committed as https://github.com/zlib-ng/zlib-ng/commit/9be98893aaf69892811d617122e28ea2dd8e17ba (apparently more is needed to solve the problem in a generic way, I was just concerned with the s390 part here).
Regarding this issue: I'm currently looking into using the inline history mode instead of the circular buffer history. This may reduce the overall amount of copying and somewhat reduce the 25% overhead.

This PR is not necessary: concurrent modification of deflate() buffer is not allowed: https://lists.gnu.org/archive/html/qemu-devel/2022-07/msg00889.html


Viewing TCmalloc memory allocations

Related to Chromium's TCmalloc, but maybe somebody here can help.
Modified Chromium TTMalloc allocator to expose pagemap_ like below:
third_party/tcmalloc/chromium/src/page_heap.h

class PERFTOOLS_DLL_DECL PageHeap {
 public:
  PageHeap();
  typedef MapSelector<kAddressBits>::Type PageMap;
  PageMap pagemap_;

third_party/tcmalloc/chromium/src/static_vars.cc

PageHeap Static::pageheap2_;

third_party/tcmalloc/chromium/src/static_vars.h

static PageHeap pageheap2_;

Exposed PageHeap via pageheap2_, but somehow 3 radix tree does not contain data/pointers? Only "0"
My script (https://github.com/marcinguy/tcmalloc-inspector) shows the same:
USED:
BLOCK SUMMARY
0 blocks, 0 total size
size frequencies:
FREE:
BLOCK SUMMARY
0 blocks, 0 total size
size frequencies:
LOST:
BLOCK SUMMARY
0 blocks, 0 total size
size frequencies:

More GDB output here: https://github.com/marcinguy/tcmalloc-chromium
Any idea why?
Did I modify the TCMalloc wrongly?
With Google's Tcmalloc in another sample program ia works correctly.
https://github.com/marcinguy/tcmalloc-inspector
Thanks,

As of writing this comment, Chromium uses a variant of https://github.com/gperftools/gperftools.  It has a number of local patches to it which modify internal data structures.  This might be interfering with your script.


Embedding ractive code in html pages

Hi, am wondering if it's possible to embed Ractive code inside an html template.
e.g:

   {{#items}}

{{ name }}

   {{/items}}

ie: the ractive code is embedded in an html page, which contains the template, so that all of the code can be in one place?

Hi @Rich-Harris I've been playing with Vue.js recently, seem really similar to this idea we bounced around in 2014.
In fact one of the examples above looks just like a .vue file !
Seems to work pretty nicely.
Dave Moshal

Yep! A lot of Vue's ideas are heavily influenced by Ractive, including this one – we've been using single-file components since long before .vue files existed. We just never did a good job of advertising it 😁

We should have!
Vue.js is the second most starred front-end framework on Github (after AngularJS).
Dave


Fix doc gen in the build

Purpose
$subject
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #21998 into stage will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            stage   #21998   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

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 0cc2647...cec97b6. Read the comment docs.


Can default values be specified in some shorter way?

In #[derivative(Default(value="123"))] boilerplate is ten times bigger than the value itself.
Maybe it can just be sometihng like #[default("123")]? This way it's only five times bigger.
The short form may be opt-out with cargo features to provide a way of dealing with conflicts with other derives.

All attributes must be on the form #[derivative(…)]

There is no requirement from #[proc_macro_derive] that attributes must be of one form with a specific keyword related to the #[derive]. The question is whether those attributes might conflict with other attributes from other derives.

In smart-default it's just #[default].

I don't want just #[default("123")] because that might conflict with other stuffs. Eg. even serde uses #[serde(default = "foo")].

What if, similar to use foo as bar, you write this?
#[derive(Derivative)]
#[derivative(Default as bar)]
pub struct Foo {
	#[bar("123")]
	a: u32,
}

This way it's up to the user to avoid name conflicts and in the same way name conflicts are avoided in other contexts.


Fix vector tile map crashes on login/logout

Overview
Fix a bug whereby the vector tile map would crash on logging in or
logging out caused by a missing check to ensure that the map object
existed before calling getZoom. Adjust it to use the stored zoom state
instead.
Connects #822
Notes
Fixing this uncovered another quirk whereby we are clearing the existing facilities data on logout, along with the filter settings. This is how the existing map setup also works, so I did not try to address it here and will make another card for fixing it.
Testing Instructions

get this branch then sign in and turn on the vector tile map
try to re-create the bug described in #822 and verify that it has been fixed

Checklist

[ ] fixup! commits have been squashed
[ ] CI passes after rebase
[ ] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

Looking at this now.


Feed data and pagination from backend api

Thank you for the amazing and elegant work!
My use case, involves having a headless CMS that provides api to access, paginate, filter and sort the data. The number of data rows is in the millions and hence can not be pre-fetched.
I was wondering if it is easy to connect datatables with arbitrary backend api (so the data is not all readily available) where we can retrieve the data for each page and apply any necessary filtration / sorting. All done for a backend api.
Should I, with my case above, implement/extend DataHander class?

+1 i need to load lot of data and it would be nice to see an example of server side pagination

Currently this lib can't help at all in the case where the data processing logic applies on the server side (searching, filtering, paging, sorting...)
I'm working on it.
In any case, if you are looking for something operational right away, there are surely more advanced tools than this one

Currently we need an handler that can trigger requests to fetch the data once table state changes.
The major concern will be to provide something fairly universal because there are a lot of different API designs.
Maybe by using a derived store to get the table state:
const params = handler.getState()
// params:
{
    search: 'john',
    page: { number: 2, offest: 40, limit: 20 },
    rowsPerPage: 20,
    sort: [ { key: 'first_name', direction: 'asc' }, {key: 'last_name', direction: 'asc'} ]
}

// users?per_page=20&offset=40&search=john

const response = await fetch(`/users?per_page=${params.rowsPerPage}&offset={params.page.offset}&search=${params.search}`)

+1, this feature would be much appreciated. Will be working with millions of table entries, so front-end pagination and operations really isn't an option

Made a draft implementation with some examples using public APIs.
http://localhost:5173/datatables/remote/examples
We must define an api-specific reload() function which is triggered at each change of state.
handler.onChange( (state) => reload(state) )

The reload function is triggered using the following method:
handler.invalidate()

More details here:
https://vincjo.fr/datatables/remote/basic-usage


Fix some IE11 ua string cases

Coverage increased (+0.02%) to 80.764% when pulling ed82008a5a2987b8769ee88ecbd351a0ee190387 on scottmo/fixUADetectorIE11 into d59df2da95ca1eed158d2d6713597170ac68d83a on master.


Combine IDP and regular login?

I'm trying to configure Authentik so that people can use their exiting IDP session on it to access copyparty directly.
My problem is that as soon as I declare (as documented here)
[global]
  ...
  idp-h-usr: x-idp-user
  idp-h-grp: x-idp-group

I lose the ability to use the regular login method with a cookie.
When I enter my password, I get the "hi {user}" page, but then I m' redirected to the default page again, and in the header I can see I'm not logged in.
Is it expected? Is there a way to combine both methods? (as a fallback, or if a user is only defined in copyparty for example)
Thanks again for your software, it kicks ass ^^
EDIT: After reading the source code I've tried adding bauth-last to the configuration but no luck :(

hey! and thanks :grin:
until now, the IdP auth would entirely disable the regular login stuff, since that's what the other IdP usecases appeared to expect.
but now that you ask, I agree it would be cool to be able to mix the two -- so now it does this:

first, check if there's a password or login-session which matches any of the users defined in the copyparty config / commandline args
then, it checks if there's an IdP username header, and if that header has a value, and if that header is trusted (from a legit reverseproxy) -- if all of those is true, then the IdP username wins

here's a beta -- copyparty-sfx.py.zip -- would it better with a docker image instead? In that case, which image flavor and archtecture are you running on?

Hey thanks a lot!
Yes I'm using the Docker image, the ac variant on amd64.

Alright -- you should get the beta if you switch to the beta tag, so  copyparty/ac:beta :+1:
just please make sure to switch back to copyparty/ac:latest when the next version is released, since the beta tag doesn't get regular updates!
let me know if you hit any issues :>

I can confirm that the regular login now still works when enabling IDP support! \o/
I still have to figure out the proper way to trigger the IDP-based auth using a special URL, but that's a problem on my side. I'll post the configuration for Apache using mod_auth_openidc if I find one that's working.
Thanks, again :+1:

It finally works the way I wanted. I'll try to sum up the necessary configurations on copyparty and Apache's sides.
In copyparty (using the current beta, but soon the next stable I'm sure):
[global]
  name: copyparty.example.org
  # OpenID/Authentik
  idp-h-usr: x-Authentik-User
  idp-h-key: X-Authentik-SOMESECRET
  bauth-last

Now in Apache, assuming that

your Authentik is running on authentik.example.org
your copyparty's public address is copyparty.example.org
your copyparty is reachable at copyparty:3923 from Apache
you've created an OAuth2/OIDC application and provider on Authentik with the slug copyparty
you've set the Launch URL for copyparty in Authentik to https://copyparty.example.org/oauth/authorize (this is perfectly arbitrary, see the <Location> section below)
the client ID is YOURCLIENTID
the client secret is YOURCLIENTSECRET
the secret passphrase is YOURSECUREPASSPHRASE
the secret header for securing the OIDC headers is X-Authentik-SOMESECRET
you want Authentik's nickname field to be used as the username in copyparty

Only important directives are present here, you might need to add additional SSL/TLS options to handle HTTPS properly.

<VirtualHost *:443>
ServerName copyparty.example.org
DocumentRoot /var/www

# Authentik OpenID Configuration
OIDCProviderMetadataURL https://authentik.example.org/application/o/copyparty/.well-known/openid-configuration
OIDCClientID YOURCLIENTID
OIDCClientSecret YOURCLIENTSECRET
OIDCCryptoPassphrase YOURSECUREPASSPHRASE

OIDCProviderIssuer https://authentik.example.org/application/o/copyparty/
OIDCProviderAuthorizationEndpoint https://authentik.example.org/application/o/authorize/
OIDCProviderTokenEndpoint https://authentik.example.org/application/o/token/
OIDCRedirectURI https://copyparty.example.org/redirect_uri
OIDCScope "openid email profile"

<Location "/oauth/authorize">
  AuthType openid-connect
  Require valid-user

  RewriteEngine On
  RewriteRule .* / [R=301,L]
</Location>

<Proxy *>
  Deny from all

  AuthType openid-connect
  Require valid-user
  OIDCUnAuthAction pass

  RequestHeader set X-Authentik-User "%{OIDC_CLAIM_nickname}e" env=OIDC_CLAIM_sub
  RequestHeader set X-Authentik-SOMESECRET OK env=OIDC_CLAIM_sub

  Satisfy any
</Proxy>

ProxyPass        /oauth/authorize !

ProxyPass        /                http://copyparty:3923/ nocanon
ProxyPassReverse /                http://copyparty:3923/

ProxyPreserveHost On
AllowEncodedSlashes On
</VirtualHost>

Now you can access your copyparty and log in using the regular credentials as usual, assuming you have local accounts on it, but you can also trigger the OIDC login process by hitting the https://copyparty.example.org/oauth/authorize which will redirect you to the Authentik login page (or, if you're already logged in, to your copyparty's home page with a valid session).
Enjoy!


Sending the SPA-response html to Rendertron instead of URL of page

Sending the SPA-response html to Rendertron instead of URL of page
I would like to send the response from our Single Page Application forwarded to the rendertron (not the url) to be prerendered and then send that prerendered html back.
This way, I am saving on a couple of hops which adds significant delays on our end to get a response from rendertron.
So can we have something like:
www.rendertronIPaddress/RenderThisHTML/string=".... ..."
Thanks a lot.

Unless that has all assets inlined (CSS, JS, images), it would still need to make a network request to whatever serves the SPA. I'm not sure the potential gain would justify the additional complexity of such feature. That being said, you can of course explore that option by modifying Rendertron yourself.


running assembleDebug crashes on linux

🐛 Bug Report

When run flutter run in the assembleDebug on linux get an error
here after the log:
flutter run
Using hardware rendering with device Android SDK built for x86. If you get graphics artifacts, consider
enabling software rendering with "--enable-software-rendering".
Launching lib/main.dart on Android SDK built for x86 in debug mode...
Initializing gradle...                                              2,8s
Resolving dependencies...                                           7,0s
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugResources'.

Android resource linking failed
Output:  /home/../build/app/intermediates/incremental/mergeDebugResources/merged.dir/values/values.xml:86: error: resource android:attr/fontVariationSettings not found.
/home/../build/app/intermediates/incremental/mergeDebugResources/merged.dir/values/values.xml:87: error: resource android:attr/ttcIndex not found.
error: failed linking references.

Command: /home/michele/.gradle/caches/transforms-1/files-1.1/aapt2-3.2.1-4818971-linux.jar/2da2d4ba53882e9ff3c9aa62fbcfd11d/aapt2-3.2.1-4818971-linux/aapt2 link -I
/home/michele/Android/Sdk/platforms/android-27/android.jar\
--manifest\
/home/..../build/app/intermediates/merged_manifests/debug/processDebugManifest/merged/AndroidManifest.xml
-o\
/home/.../build/app/intermediates/processed_res/debug/processDebugResources/out/resources-debug.ap_
-R\
@/home/.../build/app/intermediates/incremental/processDebugResources/resources-list-for-resources-debug.ap_.txt
--auto-add-overlay\
--java\
/home/.../build/app/generated/not_namespaced_r_class_sources/debug/processDebugResources/r
--custom-package\
com.example.balanceapp\
-0\
apk\
--output-text-symbols\
/home/.../build/app/intermediates/symbols/debug/R.txt
--no-version-vectors
Daemon:  AAPT2 aapt2-3.2.1-4818971-linux Daemon #0
Output:  /home/michele/.gradle/caches/transforms-1/files-1.1/core-1.0.1.aar/de5189c4d2c58338c0f057db7575797e/res/values/values.xml:89:5-125:25: AAPT: error: resource android:attr/fontVariationSettings not found.
/home/michele/.gradle/caches/transforms-1/files-1.1/core-1.0.1.aar/de5189c4d2c58338c0f057db7575797e/res/values/values.xml:89:5-125:25: AAPT: error: resource android:attr/ttcIndex not found.
error: failed linking references.
Command: /home/michele/.gradle/caches/transforms-1/files-1.1/aapt2-3.2.1-4818971-linux.jar/2da2d4ba53882e9ff3c9aa62fbcfd11d/aapt2-3.2.1-4818971-linux/aapt2 link -I
/home/michele/Android/Sdk/platforms/android-27/android.jar\
--manifest\
/home/.../build/app/intermediates/merged_manifests/debug/processDebugManifest/merged/AndroidManifest.xml
-o\
/home/.../build/app/intermediates/processed_res/debug/processDebugResources/out/resources-debug.ap_
-R\
@/home/.../build/app/intermediates/incremental/processDebugResources/resources-list-for-resources-debug.ap_.txt
--auto-add-overlay\
--java\
/home/.../build/app/generated/not_namespaced_r_class_sources/debug/processDebugResources/r
--custom-package\
com.example.balanceapp\
-0\
apk\
--output-text-symbols\
/home/.../build/app/intermediates/symbols/debug/R.txt
--no-version-vectors
Daemon:  AAPT2 aapt2-3.2.1-4818971-linux Daemon #0

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 14s
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                        15,3s

The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

Gradle task assembleDebug failed with exit code 1
Expected behavior
The app is not deployed on target environment
Reproduction steps
make: flutter clean / flutter run
Configuration
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v1.5.4-hotfix.2, on Linux, locale it_IT.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Android Studio (version 3.1)
[✓] IntelliJ IDEA Community Edition (version 2018.2)
[✓] VS Code (version 1.33.1)
[✓] Connected device (1 available)
• No issues found!
Platform:

[x] : linux android emulator
[ ] :iphone: iOS
[ ] :robot: Android

@michelemazzei did you update your App to support AndroidX? The compile error actually mentions the following:

The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

More information can also be found here: https://github.com/BaseflowIT/flutter-permission-handler/issues/98#issuecomment-484775141


Fix crashing issue #13

This shouldn't be necessary. ModifierId already extends from ResourceLocation (see the TConstruct source code).


fix: telemetry logger middleware

Description

Remove UseTelemetryLoggerMiddleware section in appsettings.json, use telemetry section to control
Add feature section to compose default settings page.

Task Item
fixes #2789

Screenshots

@luhan2017 Hi Lu, could you please review this pr about the settings part? Do we need to keep the UseTelemetryLoggerSettings or just use the 'telemetry' section to maintain.

I think we need to move all those settings to the bot\settings\appsettings.json page, and so that user can edit it in composer, otherwise user can't see this. in appsettings.json, we can only keep bot and root to specify the bot location.

yes actually I add a default settings in Composer to include the runtime settings, I'm not sure, is this config section reasonable?
protected createDefaultSettings = (): any => {
    return {
      feature: {
        UseTranscriptLoggerMiddleware: false,
        UseShowTypingMiddleware: false,
        UseInspectionMiddleware: false,
        UseCosmosDb: false,
      },
      MicrosoftAppPassword: '',
      MicrosoftAppId: '',
      luis: {


Please, enable the libvmaf_cuda

Please, enable the libvmaf_cuda.
When I try to run
ffmpeg -hide_banner -nostdin -f lavfi -i color=c=black:s=320x240:d=1 -lavfi [0:v][0:v]libvmaf_cuda=eof_action=endall:n_threads=15:model=version=vmaf_v0.6.1 -f null -
I get
[AVFilterGraph @ 0000025fbd5c5700] No such filter: 'libvmaf_cuda'
Failed to set value '[0:v][0:v]libvmaf_cuda=eof_action=endall:n_threads=15:model=version=vmaf_v0.6.1' for option 'lavfi': Filter not found
Error parsing global options: Filter not found

As explained before(https://github.com/BtbN/FFmpeg-Builds/issues/328), libvmaf_cuda cannot be statically linked, and is also not compatible with the GPL.
So no, that won't happen unfortunately.


Debugging

Not exactly sure why but org.slf4j.Logger#debug(String) doesn't work, but org.slf4j.Logger#error(String) does work.

pretty sure this is just due to paper's log4j config...


How can I set my own cookie after authentication?

Hello, how can i add my own cookie after a successful authentication? I want to add a cookie that is randomly generated and all it. mycookie.
Thanks!

Hi, sorry for the delay in responding. Were you able to fix the problem? I'll be adding this feature in a future release, but for now, this should be a good place to start
http://php.net/manual/en/function.setcookie.php
http://www.w3schools.com/php/func_http_setcookie.asp

Thanks Brad. Yes, I did end up fixing it.

If you fixed it, maybe you could do a pull request...


Call to invalidadParametesError on get-city-hotels.php

Fixs issue  #3 Change error responses for City Hotels API

@prabhakar267 please review this.

@Mangu93 closing this PR due to lack of communication
Feel free to open this again if you would like to work on it :+1:


Experimental API Gateway operations fail with 400 on fresh install

Environment details:

Native Ubuntu (Ubuntu 14.04.2 LTS)
Ephemeral CouchDB container
Docker version 1.12.0, build 8eab29e

{
  "openwhisk": "hello",
  "version": "v1",
  "build": "2017-02-16T18:13:03Z",
  "buildno": "latest"
}

Steps to reproduce the issue:

Setup according to https://github.com/openwhisk/openwhisk/blob/master/tools/ubuntu-setup/README.md
Run $ wsk api-experimental create /hello /echo get /whisk.system/utils/echo -v or request https://{apihost}/api/v1/experimental/routemgmt (with appropriate credentials).

Expected results and outputs:
Expected creation to succeed. (Have not had it work, so can only say I expect it to not fail.)
Actual results and outputs:
error: Unable to create API: Response is not valid 'application/json'.

or
{
  "error": "Response is not valid 'application/json'.",
  "code": 1657
}

Additional information:
Verbose output of create command:
$ ./bin/wsk api-experimental create /hello /echo get /whisk.system/utils/echo -v -i
REQUEST:
[POST]	https://{apihost}/api/v1/experimental/routemgmt
Req Headers
{
  "Authorization": [
    "Basic {creds}"
  ],
  "Content-Type": [
    "application/json"
  ]
}
Req Body
{
  {
    "apidoc": {
      "namespace":"_",
      "gatewayBasePath":"/hello",
      "gatewayPath":"/echo",
      "gatewayMethod":"GET",
      "id":"API:_:/hello",
      "action":{
        "name":"utils/echo",
        "namespace":"whisk.system",
        "backendMethod":"POST",
        "backendUrl":"https://{apihost}/api/v1/namespaces/whisk.system/actions/utils/echo",
        "authkey":"{authkey}"
      }
    }
  }
}
RESPONSE:Got response with code 400
Resp Headers
{
  "Access-Control-Allow-Headers": [
    "Authorization, Content-Type"
  ],
  "Access-Control-Allow-Origin": [
    "*"
  ],
  "Connection": [
    "keep-alive"
  ],
  "Content-Length": [
    "74"
  ],
  "Content-Type": [
    "application/json; charset=UTF-8"
  ],
  "Date": [
    "Fri, 17 Feb 2017 15:40:35 GMT"
  ],
  "Server": [
    "nginx/1.11.10"
  ]
}
Response body size is 74 bytes
Response body received:
{
  "error": "Response is not valid 'application/json'.",
  "code": 5313
}

I also noticed that the documentation references a Go CLI, but my fresh install built the standard wsk executable in the /bin directory, so I'm wondering if it's a CLI version mismatch resulting in a malformed/bad request for the build of OpenWhisk I'm running.
I've also tried it with other Actions and credentials with the same result.

This was my fault. Did not run the apigateway.yml ansible playbook. Had assumed was part of the openwhisk.yml playbook. If I get a chance will submit a PR to update docs to clarify.


Multi diff editor: no corresponding TabInput class in API

For tab group being multi-diff editor, property Tab.input is undefined (while it properly points to TabInputText or TabInputTextDiff for text/diff editors).

cc @hediet

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

/duplicate #206411


Install guide small mistake? --save-dev => --save

I think ng2-facebook-sdk package should be located in dependencies (not in devDependencies).
If so, please update the document.

You're right. dependencies makes more sense.


Create Form UI for Creating Post for Donating Blood

The feature request is same as #30 . But , this form will be for the person who wants to volunteer for the blood donation. Fields that should be included are Person's Name, Phone Number, Blood Group, Location. If you have any other idea regarding feel free to mention.

Hi
i would like to work on this issue please assign it to me


Converting to an object in mongoose

The mongoose adapter uses toObject  while the authentication-local uses toJSON,  why not keep it consistent since both functions do the same thing. I am only saying this cause I have modified my schemes toObject like so
if (!userSchema.options.toObject) userSchema.options.toObject = {};
        userSchema.options.toObject.transform = function (doc, ret) {
            ret.id = ret._id;
            delete ret._id;
            delete ret.__v;
            return ret;
        };
}

and its calling the toJson, Am still learning Feathers is changing the _id a bad idea.
Nice framework by the way,  best one yet

toJSON is a standard used by JSON.stringify so it is probably the one that should be used.


lzfse_decode can't distinguish between decompression error and insufficient space

It would be nice if, when lzfse_decode fails, it would be possible to distinguish between the decoder running out of space in the output buffer (in which case retrying with a larger buffer may fix the issue) and more serious errors such as corrupt data.
In order to get around this limitation in Squash, I'm using the internal API.
My suggestion would be to change the function to something like
int lzfse_decode_buffer(uint8_t *__restrict dst_buffer,
                           size_t* dst_size,
                           const uint8_t *__restrict src_buffer,
                           size_t src_size,
                           void *__restrict scratch_buffer) LZFSE_LIB_API;

dst_size becomes an in/out variable, and the return value can be used to indicate a failure.  See https://quixdb.github.io/squash/api/c/group__SquashCodec.html#gada8fa80a9fe604d8b2bb48f84e3914d1 for an example.

The contract of the decode function is to fill the DST buffer and return DST_SIZE in case the actual decoded size is >= DST_SIZE.  This is not an error.
What we can do is add a function returning the decoded size of a valid encoded buffer, without decoding anything (i.e. fast).


Sri Hari: Batch-3/Neetcode-150: Added Golang, Kotlin

@neetcode-gh

Took 5 hours for this work.
Please review it.

In the commit with LC: 215, Leetcode has added a new test case and your video solution(quick select) is getting TLE, so I added a new approach for it.

Thanks @Srihari2222


HIghlight escaped character in string literal

And highlight meta string in regexp literal is also useful.
But we may need regexp parser if do this in strict.

Definitely. But I guess highlighting for regexp is more difficult than String's one.
I think regular expression is enough to highlight escaped characters in String, but probably we need a parser (maybe Onigumo) for special character in regexp as you said.
So I'll implement this feature for String firstly, then I'll investigate Onigumo.


Improve code coverage

Pull Request Test Coverage Report for Build 241

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.8%) to 90.005%

Totals

Change from base Build 240:
0.8%

Covered Lines:
1891

Relevant Lines:
2101

💛  - Coveralls

Previously passing tests are failing from time to time on Appveyor, this is a known issue with the CI. All tests have passed consistently locally and on Travis.


Prevent compilation of imported files

When a template is extracted into a separate file that gets imported into the main document, the extension will compile an empty PDF when the template file is edited.
This is probably also undesirable for any partial file that gets imported in another document, even if it contains content.
An idea would be to parse files in the workspace to check if they have an #import statement, and to avoid generating PDF files for those files that are imported at some point.
Additionally, the extension could trigger a recompile of the main file when an imported file gets modified.
Practically, keeping a map of files that are arguments of an import statement for the workspace would allow both of the above. The map keys would be the imported files and their values would be a set of files where the import statement resides.

Would it also be possible to replicate typst --watch bleh.typ's behavior in that the file is recompiled when an imported file is changed?

Huge plus 1 on this. The extension is great, but this would be a huge benefit. Perhaps some people would want to compile document sections separately, so this should be togglable.

Regarding compiling a partial, there is a command to manually compile the active file.


Add constant folding for lq.quantize and lq.dequantize

What do these changes do?
This PR adds constant folders for lq.quantize and lq.dequantize ops.
This PR also includes a few minor changes from our internal fork to bring them inline with each other.
How Has This Been Tested?
Added MLIR Filecheck
Co-Authored-By: Tom Bannink<EMAIL_ADDRESS>

The name of the PR was a bit confusing to me though, I was going through the code to look for the place where you added a folder or moved something from one folder to another, but then it turns out it was about folding instead of folders (as in paths)

Good point, changed the title.


Jitsi crashing in windows traced back to run.c

The Jitsi nightly builds work fine so those builds must be done differently.  I have read of others having the same problem as I am trying to get compiled windows installer running.
My development environment is Windows 10 64bit, Eclipse Mars 64bit, JDK v1.7.79 64bit, Ant v1.9.6, TDM32 GCC 5.1.0.  I have tried different versions of all of these things including Mingw32 gcc to verify it's not the compiler.  I am trying to compile Jitsi as a 32bit app.  Yes I am using jre 32bit as my included runtime.
I have narrowed it down to run.c when it tries to do the JNI call.  The following commit seems to be partially responsible.  It was apparently added to prevent a similar crash condition. When I remove it I can get Jitsi to run.  Splash screen doesn't work though so something is still a little off.
I have also verfied all my paths and dependencies in my development environment.  It all seems to point back to run.c
http://code.metager.de/source/diff/jitsi/src/native/windows/run/run.c?r1=/jitsi/src/native/windows/run/run.c@f7361e133800b3b3c0de5c22e9d2e494194e84c3&r2=/jitsi/src/native/windows/run/run.c@dc1c301d2d23a469da8f0cde5bcdf5183232b3a9&format=s&full=0

Applies Ingo Bauersachs' fix for a crash related to an invalid calling convention upon trying to call JNI_CreateJavaVM.

Fixes a failure to load the JRE runtime library because of unreachable dependencies which are actually available in the bin directory.

There's nothing special in there. Have you verified that the runtimeLib and javaHome arguments in Run_runJavaFromRuntimeLib are what they should be? I'm suspecting that these point to a 64bit JRE.

Thank you for the response.  Based on your advice I tried creating a 64bit installer which worked perfectly.  Using the same setup I tried creating a 32bit installer making sure to change my paths to all 32 development software including JDK and embedded JRE.  It still won't work and I cannot find any 64bit paths or software anywhere other than my OS.
I went so far as to uninstall all 64bit development software including JDK ,JRE and Eclipse and TDM64 GCC.  Even with all 32bit develpment sofware I cannot get it to work.  My next step would be to try set this all up on a 32bit Windows OS which I don't have.  I guess I will have to keep looking for the root cause on 64bit OS.

I removed the -O2 compiler flag and now I see it is getting as far as loading Java bundles.  The splash screen freezes on "NimbuzzAvatars".  So it is running SIPCommunicator.java and getting as far as org.apache.felix.main.Java.
The only thing I find related to that error is this.  I confirmed my load order is 13 as per that fix.
https://github.com/jitsi/jitsi/commit/f5dc6edede237288d6b09dddcabd1ed47f55c8c2

Try removing your sip-communicator.bin folder that is in your home folder
and try starting again.
On Mon, Feb 29, 2016 at 10:32 PM, powerpbx<EMAIL_ADDRESS>wrote:

I removed the -O2 compiler flag and now I see it is getting as far as
loading Java bundles. The splash screen freezes on "NimbuzzAvatars". So it
is running SIPCommunicator.java and getting as far as
org.apache.felix.main.Java.
The only thing I find related to that error is this. I confirmed my load
order is 13 as per that fix.
f5dc6ed
https://github.com/jitsi/jitsi/commit/f5dc6edede237288d6b09dddcabd1ed47f55c8c2
—
Reply to this email directly or view it on GitHub
https://github.com/jitsi/jitsi/issues/229#issuecomment-190537435.

dev mailing list
<EMAIL_ADDRESS>Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

I had looked for that but there is no folder or file with that name or any similar name.  I also did a drive and registry search.

You'll need to get access to what Java is printing to STDOUT. You can e.g. change SIPCommunicator.java (near the end of the main(...) method) to print this into a file.

If I run jitsi.exe that was compiled without the -O2 flag it installs and runs on Windows 7 32bit.  If I compile with the -O2 flag it crashes the same as it does on Windows 10 64bit.
I found this line in SIPCommunicator.java
System.setOut(new ScStdOut(System.out));
and had a look at ScStdOut.java and read all the comments in the file but it's not clear to me what I should do here to print out STDOUT.
This still looks like it could be a JNI issue to me because if I remove that code as explained in my first post it will work.

I managed to get my 32bit compiled version running on Win10 64bit.  It requires a combination of using a slightly older embedded JRE (JRE8u40) in combination with removing the -O2  CPPFLAG from ./src/native/windows/run/Makefile.

I thought I had everything working.  I have 32bit app working on windows 7 32bit and Windows 10 32bit.  I have 64bit app working on Windows 10 64bit.
However, I cannot get the exact same 32 or 64bit apps working on Windows 7 64bit.  Freezes at splash screen.

I have it working on Win 7 64 now.  When my development environment is Win 7 64bit it works.  When my development environment is Win 10 it doesn't seem to be portable to Win 7 64bit.

The Jitsi releases are built on Windows 7 64bit, using cygwin.
32bit compiler: gcc version 4.5.2 (tdm-1)
64bit compiler: gcc version 4.5.2 (tdm64-1)
Embedded JRE: <IP_ADDRESS>
I don't know what else could be the problem, so I'm closing this issue.


Collect MEMO form

BLOCKED: by #2

with email
with connected wallet
with address
validation for address & email

Are we implementing collect with e-mail? @vikiival

Are we implementing collect with e-mail? @vikiival

Yes :)


Refactor logs

There were a few things I found confusing looking at this project for my other PR, so I thought I'd suggest some very minor refactors. I kept it separate so you can just ignore this one if you like!

If the artifact doesn't exist at all, the server still logs out "not found locally, downloading it" which sounded (to me) like it definitely does exist remotely. I slightly reworded it to make it clear that we're only looking for it remotely.
I removed the log line about it being successfully downloaded because it looks like that may trigger in certain situations even if the process has failed. I looked at putting it in downloadArtifact() or artifactApi.ts but it seems like Axios will error if it fails, and there is already error logging if the compression fails, so it seemed both misleading and unnecessary.
Made the default port a const as that (or a config file) is where I'd expect to find it.
Type hinting for downloadArtifact() that I added when putting the above logline in there before I decided against it. Left it in just for helpfulness.

Looks like a great PR :]
Thank you for submitting it 👍🏽
can you rebase the master so I will be able to merge it?

Done! I remembered to run build as well. Just have a quick glance yourself to make sure I rebased properly :)

Thank you for this PR 🙏🏼


New package: Smallstep.step-ca version 0.23.1

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run

/azp run

In a VM, this installs normally, but presents an error when launched:

error opening C:\Users\user.step\config\ca.json: open C:\Users\user.step\config\ca.json: The system cannot find the path specified.

Hi @stephengillie, this is the expected output when the server is started with no configuration file, however I can understand why it's confusing. I've opened https://github.com/smallstep/certificates/issues/1248 to make the output more helpful.
We cannot ship a default configuration file with the package, because it contains unique private keys, etc.
However, even once we have that, the command is designed to return an error status code when run by itself and when there is no configuration file.
Is there a way to mark this package as OK, under the circumstances?
Alternatively, we may be able to write a setup script that generates a default server configuration when the package is installed. Would that work?

We have added a much more helpful message to the output, to cover this use case.
It will be in our next release.
I will close this now and open a new PR for that release soon.
I've also added Smallstep.step as a dependency to this project, so that folks can get set up immediately by running step ca init.


feat(receiver/mysql): add metrics based on table_lock_waits_summary_by_table table

Description:
Add metrics based on table_lock_waits_summary_by_table table
mysql docs
This is going to add equivalents of the following telegraf metrics:
mysql_perf_schema_read
mysql_perf_schema_read_high_priority
mysql_perf_schema_read_no_insert
mysql_perf_schema_read_normal
mysql_perf_schema_read_with_shared_locks
mysql_perf_schema_write
mysql_perf_schema_write_allow_write
mysql_perf_schema_write_concurrent_insert
mysql_perf_schema_write_low_priority
mysql_perf_schema_write_normal

Link to tracking Issue: #14138
Testing: Units
Documentation: auto-generated

This is PR which should be issued against upstream when https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/ will be resolved


Fix non-visible motion vector text in shader prepass example

Objective
In the shader prepass example, changing to the motion vector output hides the text, because both it and the background are rendererd black.
Seems to have been caused by this commit? https://github.com/bevyengine/bevy/commit/71cf35ce426bf3ab448c9d1e6ff0c22fc5a10336
Solution
Make the text white on all outputs.

I'm guessing it was because motion vectors used to use a yellow background, instead of white.


Small extensions for a 3Bot instance waits for payment forever.

Description
The setup is as follows: I deploy a new 3Bot instance. This instance expires at 9:30 PM today. The chatflow creates a new pool with a suitable amount of cus and sus to keep the instance alive until that time. Since the workload is actives, the pool cloud units (cus and sus) decrease at a fixed rate. If I extend the instance to expire at 9:31 PM, the increase in cloud units is very small and before reaching the "waiting for payment" step, the cloud units drops back to a value less than they were before extension. This prevents the chatflow from seeing that the pool was extended.
Steps to reproduce

Make a 3Bot instance that expires at 9:30 PM.
Extend it to expire at 9:31 PM.

Requires min value for datetime to be at least 1 day or validation against the payment itself on stellar

Shouldn't be an issue anymore because we don't check on trigger cus/sus but on payment info that got recently exposed #2151

Shouldn't be an issue anymore because we don't check on trigger cus/sus but on payment info that got recently exposed #2151


feat(post): add alquimodelia post

@JotaFan if you have some time, how about completing this post? 😺 I took the freedom to add you as an author to motivate you further to write this post 🧙🏽♂

Can we merge this?

We need to work more on the text. Its not yet clear enough


Updated files to account for name changes in bigplanet.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (1cd8cd4) 0.00% compared to head (6943a5c) 0.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main     #17   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          4       4
  Lines        242     242
=====================================
  Misses       242     242

Files
Coverage Δ

multiplanet/multiplanet.py
0.00% <0.00%> (ø)

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


oui docs - headers page changes

Signed-off-by: Kroosh Crusius<EMAIL_ADDRESS>Description
Edits to the Header documentation within OUI. These changes include removing references to products no longer relevant to the OpenSearch project.
Issues Resolved
#110
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] All tests pass

[ ] yarn lint
[ ] yarn test-unit

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

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@BSFishy my mistake - somehow only committed one file instead of all of them. This has now been updated and is now available for your review


Explore gluestack-ui renderer

https://ui.gluestack.io/
This may be what we need for Expo/React-native support

Closing this as we have some interesting preliminary results.
Will open new issues to follow-up.


Add decode_compressed support

This fix tries to address the issue raised in #14887 to add decode_compressed support.
The API will take a string Tensor (compressed with either ZLIB or GZIP) and output a string Tensor of the same shape with content uncompressed.
This fix fixes #14887.
Signed-off-by: Yong Tang<EMAIL_ADDRESS>

(from API review: This is good to go.)

Jenkins, test this please.

@martinwicke Thanks for the help. It seems python 3 build still has failures (python 2 is OK). Let me take a look and update the PR.

@martinwicke The Python 3 build failure has been fixed and the PR has been updated and pushed. Please take a look.

Argh sorry -- I edited the docstring to make it more explicit, could you regenerate the APIDefs?

Thanks @martinwicke. The PR has been updated with tensorflow/core/api_def/update_api_def.sh rerun.
All tests passed except Ubuntu Sanity, which I think might be unrelated as I also see several other PRs (like #15491 and #15461) having the same issue.
Please take a look.

@martinwicke All tests passed now but cla/google is stuck. Not sure how to trigger to pass the test. Is there a way to manually get around it?

Yes, that's because I added a commit. I'll merge over it.

Thanks all for the help  👍 🎉 🌈


[coc.nvim] No typos exists

I used a line from the readme, and it's saying no typos exist:
They are povied.

vim:
 NORMAL  /tmp/a[+]                                                                                utf-8[unix]  100% ㏑:1/1☰℅:16
[coc.nvim] No typos exists

Versions:
$ typos --version
typos-cli 1.11.1

$ vim --version | head -n 2
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jul 12 2022 21:26:30)
Included patches: 1-5172

vim:
: CocList typos
[coc.nvim] Task error: spawn typos ENOENT

Troubleshooting
Use command :CocCommand workspace.showOutput typos to open output channel.

  1 [Info - 14:43:37.923] 0 typos found for file:///tmp/a.                                                         |  1 They are povied.
  2 [Info - 14:43:38.723] 0 typos found for file:///tmp/a.                                                         |~
  3 [Info - 14:43:38.950] 0 typos found for file:///tmp/a.                                                         |~
  4 [Info - 14:43:39.936] 0 typos found for file:///tmp/a.                                                         |~
  5 [Info - 14:43:45.193] 0 typos found for file:///tmp/a.                                                         |~
  6                                                                                |~
~

Oh it does work now I guess, not sure why my test file didn't pick up the spelling error...?
typos --diff <FILE>

--- lib/testing/hydra-testing.ts        original
+++ lib/testing/hydra-testing.ts        fixed
@@ -66 +66 @@
-        this.grantAsumeCellRolePermission();
+        this.grantAssumeCellRolePermission();
@@ -122 +122 @@
-        new ssm.StringParameter(this, "RoleForTestingSingleEnvPermisisonsSSMParameter", {
+        new ssm.StringParameter(this, "RoleForTestingSingleEnvPermissionsSSMParameter", {
@@ -358 +358 @@
-    grantAsumeCellRolePermission(): void {
+    grantAssumeCellRolePermission(): void {


[Bug] cannot set the similarity percentages to descendants.

Current Behavior
When i try to change the percentage, it always changes to a full number. But i need to change it to eg. 99,5% and not 99%
Expected Behavior
Set the percentage to a more accurate number
Steps To Reproduce
go to settings --> misc --> try to set percentage to eg. 99.5%
Environment
Synology DS920+ with latest FW.
Container creation
Installed via Portainer with following compose file:
version: "3"
services:
  video-duplicate-finder:
    container_name: video-duplicate-finder
    image: jlesage/video-duplicate-finder
    environment:
      USER_ID: MyUID
      GROUP_ID: MyGID
      TZ: Europe/Vienna
      DARK_MODE: 1
      WEB_AUTHENTICATION_USERNAME: MyUsername
      WEB_AUTHENTICATION_PASSWORD: MyUserpass
    ports:
      - 5800:5800
    volumes:
      - /volume2/docker/video-duplicate-finder:/config:rw
      - /volume2/docker/video-duplicate-finder/TRASH:/trash:rw
      - /volume1/photo:/photo:rw

Container log
no log after try to change the percentage. it just automatically switched to a full number.
When i put 99.5 ans push ENTER, it writes 99

Container inspect
No response
Anything else?
No response

Since this is not an issue with the container itself, can you report this to the upstream project : https://github.com/0x90d/videoduplicatefinder/issues


Waypoints dont move when global frame is selected

When the global frame box is selected the waypoints should shift along with MAP data and axes.

corrected in pull request #113


Merge prTesting_201902140903 branch to master branch

OPS Build status updates of commit 97268d0:
:clock10: Preparing: average preparing time is 44 sec(s)

OPS Build status updates of commit 97268d0:
:clock10: Incremental building: average incremental building time is 14 sec(s)

OPS Build status updates of commit 97268d0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix: selector errors in the scraper

Thanks, but I am sure there is more to fix, at least this page, which has the complete solution and therefore requires the same changes:
https://crawlee.dev/docs/introduction/refactoring
Also this .ActorStoreItem selector you had to change is used in many other examples in the docs, including other parts of the introduction guide.

Sure! I'll look into this as well.

Closing in favor of https://github.com/apify/crawlee/pull/1915