bypass ambassador LICENSES.md

Similarly to telepresence, edge-stack contains a LICENSES.md file with other projects licenses in it. This PR contains code to ignore it.
Signed-off-by: Aidan Hahn<EMAIL_ADDRESS>

We have decided to rename the file instead.


Global not being export

Global.js
{
_: require('@sailshq/lodash'),
HttpStatus: require('http-status-codes'),
}
in my controller:   sails.log(HttpStatus.BAD_REQUEST);
error:  ReferenceError: HttpStatus is not defined

Hi @Gheshwin,
I hope you were able to find your way through this issue.
Just wanted to let you know we are consolidating all open Sails issues into one repo.
~Cheers!

@Gheshwin I tried this out myself and got the same result, but then I took another look at the Concepts > Globals docs, and I didn't see anything in there about adding custom globals. You can definitely disable globals, but I don't think you can add new ones in that file.
Hope this helps!

Just confirmed with @mikermcneil that adding custom globals to globals.js isn't supported, so going to go ahead and close this one. (Won't lock it or anything, so feel free to continue the conversation if anything else comes up!)


testgetboolfromserviceannotation [Cloud Provider Openstack]

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/ok-to-test

/approve
Looks good, let's see if tests pass.

The code seems to still be formatted incorrectly. You should be able to check that before submitting running make check from the repo.

/retest

/retest
Error's unrelated.

/retest

/retest

/assign

/lgtm
...but you'll have to rebase to enable merging.

Your test looks good. Thanks!
If you have a bit more time, have another look at the production code. Do you see something strange? In particular: do you think logging could be improved?

The production code currently do not log errors when an invalid annotation is encountered in the annotation. We could add error logging when the annotation is neither true or false to improve robustness. This would also help in debugging issues where annotation value is unexpected.
Is this what you see strange in the production code? or there's something else @pierreprinetti

/lgtm

/lgtm ...but you'll have to rebase to enable merging.

Just fixed that. Thanks

Your test looks good. Thanks!
If you have a bit more time, have another look at the production code. Do you see something strange? In particular: do you think logging could be improved?

The production code currently do not log errors when an invalid annotation is encountered in the annotation. We could add error logging when the annotation is neither true or false to improve robustness. This would also help in debugging issues where annotation value is unexpected.
Is this what you see strange in the production code? or there's something else @pierreprinetti

This is precisely what I saw. If a non-boolean annotation is found, we log "Found a service annotation:" and then the default setting, which is not what happened. Do you want to fix that?

Sure, would fix that right away. Thanks


[C++] CI failures on Windows & Substrait (appears to be abseil linking issues)

Describe the bug, including details regarding any error messages, version, and platform.
I've seen this CI failure pop up recently on two unrelated PRs.
Example:
https://github.com/apache/arrow/actions/runs/5509303570/jobs/10041817398?pr=35440
 FAILED: release/libarrow_substrait.dll release/libarrow_substrait.dll.a
cmd.exe /C "cd . && D:\a\_temp\msys64\mingw32\bin\c++.exe -Wno-noexcept-type -Wno-self-move  -fdiagnostics-color=always  -Wa,-mbig-obj -Wall -Wno-conversion -Wno-sign-conversion -Wunused-result -Wdate-time -fno-semantic-interposition -mxsave -msse4.2  -O3 -DNDEBUG -O2 -ftree-vectorize  -Wl,--version-script=D:/a/arrow/arrow/cpp/src/arrow/symbols.map -shared -o release\libarrow_substrait.dll -Wl,--out-implib,release\libarrow_substrait.dll.a -Wl,--major-image-version,1300,--minor-image-version,0 @CMakeFiles\arrow_substrait_shared.rsp  && cd ."
D:/a/_temp/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/13.1.0/../../../../i686-w64-mingw32/bin/ld.exe: src/arrow/engine/CMakeFiles/arrow_substrait_shared.dir/substrait/serde.cc.obj:serde.cc:(.text+0xf30): undefined reference to `absl::lts_20230125::operator<<(std::ostream&, absl::lts_20230125::Status const&)'
D:/a/_temp/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/13.1.0/../../../../i686-w64-mingw32/bin/ld.exe: src/arrow/engine/CMakeFiles/arrow_substrait_shared.dir/substrait/serde.cc.obj:serde.cc:(.text+0x101c): undefined reference to `absl::lts_20230125::Status::UnrefNonInlined(unsigned int)'
D:/a/_temp/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/13.1.0/../../../../i686-w64-mingw32/bin/ld.exe: src/arrow/engine/CMakeFiles/arrow_substrait_shared.dir/substrait/serde.cc.obj:serde.cc:(.text+0x141d): undefined reference to `absl::lts_20230125::operator<<(std::ostream&, absl::lts_20230125::Status const&)'
D:/a/_temp/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/13.1.0/../../../../i686-w64-mingw32/bin/ld.exe: src/arrow/engine/CMakeFiles/arrow_substrait_shared.dir/substrait/serde.cc.obj:serde.cc:(.text+0x14f1): undefined reference to `absl::lts_20230125::Status::UnrefNonInlined(unsigned int)'
D:/a/_temp/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/13.1.0/../../../../i686-w64-mingw32/bin/ld.exe: src/arrow/engine/CMakeFiles/arrow_substrait_shared.dir/substrait/serde.cc.obj:serde.cc:(.text$_ZN4absl12lts_202301256StatusD1Ev[__ZN4absl12lts_202301256StatusD1Ev]+0x17): undefined reference to `absl::lts_20230125::Status::UnrefNonInlined(unsigned int)'
D:/a/_temp/msys64/mingw32/bin/../lib/gcc/i686-w64-mingw32/13.1.0/../../../../i686-w64-mingw32/bin/ld.exe: release/libsubstrait.a(algebra.pb.cc.obj):algebra.pb.cc:(.text$_ZN6google8protobuf13RepeatedFieldIiE14GrowNoAnnotateEii[__ZN6google8protobuf13RepeatedFieldIiE14GrowNoAnnotateEii]+0x8d): undefined reference to `__emutls_v._ZN6google8protobuf8internal15ThreadSafeArena13thread_cache_E'

It's very consistent.  I am going to start investigating but wanted to create an issue in case someone was already looking into it.
Component(s)
C++

From what I can tell so far is that the mingw builds are installing a system-wide grpc, protobuf, and abseil.  So, IIUC, those should all be compatible and nothing should be getting bundled?

Ok.  I have confirmed locally that I get these exact errors when I try the versions of protobuf and abseil that pacman is installing:
libprotobuf               4.23.1               hd1fb520_0    conda-forge
libabseil                 20230125.3      cxx17_h59595ed_0    conda-forge

...which is unfortunate.  Investigating further.

https://github.com/apache/arrow/issues/35987 is probably related.  It seems we want a newer version of protobuf.

@kou there is no protobuf 4.23.3 in mingw yet.  Should we create an issue/PR at https://github.com/msys2/MINGW-packages ?  I don't work with mingw much so I don't know the best approach.

Thanks for investing this!
I'll open a pull request to fix this.

@pitrou @kou should this be added to 13.0.0, I would think so.

I've decided to add it.


Issue with 8.4.0 due to PR #5954

Check that this is really a bug

[X] I confirm

Reproduction link
Will create a repro if needed.
Bug description
The code in https://github.com/nolimits4web/swiper/pull/5954/files#diff-88a223b4c7649642379e3d1da5338dc2432bbe32b5787cfcda0b484fce3e3786 is causing me issues because there is a circumstance where displayName is null, and since there is no check for && child.type.displayName in the if statement, I'm getting a Cannot read property 'includes' of undefined when that situation is encountered.
Expected Behavior
Check succeeds without error.
Actual Behavior
TypeError: Cannot read property 'includes' of undefined
Swiper version
8.4.0
Platform/Target and Browser Versions
React
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[X] I'm willing to open a PR

I can confirm the issue is valid, as quick workaround we had to use swiper 8.3.2 version.

Same problem here...
TypeError: e.type.displayName is undefined

Thanks for the quick response!


Defining computed: { pgConfig () {} } Causes Unnecessary GET request for entire table

In my app, I have a page where a user can create a new record, which is backed by the records table.
RecordNew.vue
import { pg } from 'vue-postgrest';

export default {
  mixins: [pg],
  data() {
    record: {}
  },
  computed: {
    pgConfig () {
      return {
        route: 'records'
      }
    }
  },
  mounted() {
    this.record = this.pg.$new(createBlankRecord());
  },
  methods: {
    async createNewRecord(value) {
      await this.record.$post({ return 'minimal' });
    }
  }
}

Whenever I navigate to this page (/records/new), the code instantly fires a GET request to the postgrest API for all of the records table. I am only trying to connect it so that I can perform the POST when createNewRecord is called. If I don't have the computer->pgConfig block, the $post( call fails with an error.
How can I prevent this unnecessary GET request on page load?

The mixin is used in cases where you want to show a list of things and add to that list at the same time. That's why it works with this.pg as a GenericCollection. And that includes GET requests to fill the collection in the first place.
For your use-case, you don't seem to need the mixin. I suggest you just use plugin:
export default {
  data() {
    record: createBlankRecord();
  },
  methods: {
    async createNewRecord(value) {
      await this.$postgrest.ready
      await this.$postgrest.records.post({}, { return 'minimal' }, this.record);
    }
  }
}

Great, this worked! Thanks, I didn't realize that was the primary purpose of the mixin.


⚠ Cioos National CKAN has degraded performance

In 7661c6e, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 12228 ms

Resolved: Cioos National CKAN performance has improved in 43c9507 after 38 minutes.


Websocket are sent only in when the connection is closed

I have the following code:
\Ratchet\Client\connect('ws://localhost:8090')->then(function($conn) {

		$conn->on('close', function($code = null, $reason = null) {
            echo "Connection closed ({$code} - {$reason})\n";
        });

		$conn->send('Connected to WS');

		$ssh = new \phpseclib\Net\SSH2($deviceIP);
		$ssh->setTimeout(5);

		$result = $ssh->login('lab', 'lab');
		$conn->send('Logging in to device...');
		 $ssh->read();

		if (!$result) {
			exit('Login failed');
		}

		$ssh->write("en\n");
		$conn->send('Enabling device...');
		 $ssh->read();
		$ssh->write("pass\n");
		$ssh->setTimeout(5);
		echo $ssh->read();
		$conn->close();

});

The problem is that all the websockets are sent in the same time.

Why it happens? Is there any solution for this?

I am not familiar with phpseclib, but it appears that it is a synchronous library or at least is not running with the react loop.


Copy edit "Flutter for iOS"

Not yet published, but once it is, please do a copyediting pass.

Hey Shams -- just want to confirm -- is this the page that needs a copy edit:  Preparing an iOS App for Release

Is this still to do?


add context information to numeric conversions

This feels like a good point to stop and figure out how to do some tests on Anyhow errors or wire up a custom error with slightly more data than a &str. Time for thiserror?


Mini-whatis docs - treat differently from resource

When you access a what is doc on the site, it takes you to a min-whatis page that is a text version of a whatis that also has a listing of whatis/howto docs.
I have a question with a few contingencies.
First, let's remember that at some point ALL whatis docs will link to PDFs, these mini-whatis docs will go away and the link will simply go to a PDF in the browser. So let's not go big-budget with a complicated solution.
I'd like to have the mini-whatis docs NOT include the what is/howto docs of their topic. This will mean they are different from resources. Is that complicated?
Is there an easy way to go about this.
I'm including Lois to monitor responses and chip in advice.

Can you give examples of the two kinds of pages ("whatis" and "miniwhatis")? Are these pages named diffrerently, or do they have different metadata?

Hi Clara —
The mini-WhatIs docs are brief versions of WhatIs docs.  They follow the same naming convention (WhatIsXXX, WhatAreXXX) and use the same metadata (all are Level 0 files).  The only difference is that the mini-WhatIs docs are much shorter than the 2-page WhatIs docs.  Over time, we might transition some of the mini-WhatIs docs to full WhatIs docs, depending on priorities for site content.
The plan is for each topic on the site (as shown in the Style Guide) to have at a mini-WhatIs or WhatIs doc to define terminology and scope on the site, and to be used in the forthcoming resource map.   We still have a few more topics to go.
The mini-WhatIs docs are here (*.md files):
https://github.com/betterscientificsoftware/betterscientificsoftware.github.io/tree/master/Site/Categories/Topics
For example:
https://github.com/betterscientificsoftware/betterscientificsoftware.github.io/blob/master/Site/Categories/Topics/WhatAreDisussionForumsAndQASitesForBetterScientificSw.md
https://github.com/betterscientificsoftware/betterscientificsoftware.github.io/blob/master/Site/Categories/Topics/WhatIsIssueTracking.md
The various WhatIs docs currently are available as curated content on the site, pointing to external *.pdf files:
https://github.com/betterscientificsoftware/betterscientificsoftware.github.io/blob/master/CuratedContent/WhatIsGoodDocumentation.md
https://github.com/betterscientificsoftware/betterscientificsoftware.github.io/blob/master/CuratedContent/WhatIsVersionControl.md
From: Clara Raubertas <notifications<EMAIL_ADDRESS>Reply-To: "betterscientificsoftware/betterscientificsoftware.github.io" <reply<EMAIL_ADDRESS>Date: Sunday, May 21, 2017 at 4:58 PM
To: "betterscientificsoftware/betterscientificsoftware.github.io" <betterscientificsoftware.github.io<EMAIL_ADDRESS>Cc: Lois Curfman McInnes <curfman<EMAIL_ADDRESS>Assign <assign<EMAIL_ADDRESS>Subject: Re: [betterscientificsoftware/betterscientificsoftware.github.io] Mini-whatis docs - treat differently from resource (#140)
Can you give examples of the two kinds of pages ("whatis" and "miniwhatis")? Are these pages named diffrerently, or do they have different metadata?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://github.com/betterscientificsoftware/betterscientificsoftware.github.io/issues/140#issuecomment-302962780, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAv_lXeCCw11lhk6BLRydv_xckveLNsEks5r8KVfgaJpZM4NhGNz.

OK -- if I understand correctly, the request is to not have "whatis" links show up on documents that are themselves a whatis, and it sounds like there's no important distinction on my end between whatis and miniwhatis.
I've made the change so that these links don't show up on those pages. Let me know if this solves this or if there are more concerns!

What we need for this: add some examples of WhatIs that are links to PDFs.

Here are 2 examples:
The various WhatIs docs currently are available as curated content on the site, pointing to external *.pdf files:
https://github.com/betterscientificsoftware/betterscientificsoftware.github.io/blob/master/CuratedContent/WhatIsGoodDocumentation.md
https://github.com/betterscientificsoftware/betterscientificsoftware.github.io/blob/master/CuratedContent/WhatIsVersionControl.md

OK, I believe we are all good with handling the different WhatIs docs in the same manner. Please confirm!

This is  not needed now. Can be closed.


Add support for feign's QueryMap annotation for Object mapping

The @QueryMap annotation in OpenFeign allows support for Map-to-query and Object-to-query encoding. In the current state, there's an inconsistency between OpenFeign and spring-cloud-openfeign:

In OpenFeign, you can mark an Object parameter with @QueryMap to use it as query parameters instead of a body.
In Spring, having an Object parameter in a GET mapping will map it to query automatically. Therefore, there is no equivalent annotation for @QueryMap.

Since SpringMvcContract overrides the Feign BaseContract, which handles the QueryMap annotation, having an Object parameter would pass it as a body instead of query parameters.
Another solution to this inconsistency would be to modify the RequestParamParameterProcessor to allow for Object parameters for QueryMap if the method  in question is a GET. Let me know if you'd rather have such a solution instead.

Codecov Report

Merging #79 into master will decrease coverage by 0.29%.
The diff coverage is 40%.

@@             Coverage Diff             @@
##             master      #79     +/-   ##
===========================================
- Coverage     76.64%   76.35%   -0.3%
- Complexity      298      301      +3
===========================================
  Files            37       38      +1
  Lines          1246     1256     +10
  Branches        185      186      +1
===========================================
+ Hits            955      959      +4
- Misses          213      219      +6
  Partials         78       78

Impacted Files
Coverage Δ
Complexity Δ

...ork/cloud/openfeign/support/SpringMvcContract.java
83.13% <100%> (+0.1%)
44 <0> (ø)
:arrow_down:

...enfeign/annotation/QueryMapParameterProcessor.java
33.33% <33.33%> (ø)
3 <3> (?)

How about a test?

Can you add some documentation as well?


Add plugin @resoc/eleventy-plugin-social-image

A plugin to support automated social images with 11ty and Netlify on-demand builders.
NpmJs/doc: https://www.npmjs.com/package/@resoc/eleventy-plugin-social-image
CSS-Tricks tutorial: https://css-tricks.com/create-your-own-automated-social-images-with-resoc/

I committed another change in the same branch, thus polluting this PR. Please, forget it. I'm going to create another, clean one.

The fixed one is https://github.com/11ty/11ty-website/pull/1218


[stable/postgresql] Update to the recommended pvc patterns.

This is a split-off of PR #408 to just contain the chart postgresql.
If there's any commonality in changes nessary between this PR and the others that are being submitted at once, please mention them in #408.
Some things to note:

This initial PR will not be updating the Chart.yaml's version string, as I feel it should be done manually per-pr once each chart's otherwise acceptable.
An automated script created the splits and the PRs, on a per-folder basis under stable, after copying the relevent files from a backup of my local copy of #408

Added note about fallback in README, and bumped the chart version.
LGTM


Recent --strictNullChecks issue w/ && || type result check

About 1 weak ago, this sample below would transpile flawlessly under --strictNullChecks:
let sinOrCos = Math.random() < .5;

let choice = sinOrCos && Math.sin || Math.cos;
//let choice = sinOrCos? Math.sin : Math.cos;

alert(choice(Math.PI));

But to my surprise today, under<EMAIL_ADDRESS>only the statement using the ternary conditional operator works now!
Somehow TS thinks that choice could be boolean as well when using && + || expression.  =(
Is that intentional from now on? I miss when it was smarter just 1 week ago.  :-(
tsc --pretty --newLine LF --removeComments --experimentalDecorators --strictNullChecks -d -t ES6 sinCos

1 more example:
function sq(n?: number): number {
	const r = n !== undefined && n*n || 0;
	return r;
}

alert(sq(3));

sq.ts(3,9): error TS2322: Type 'number | boolean' is not assignable to type 'number'.
Type 'boolean' is not assignable to type 'number'.

Like due to changes in #8949 which resolved #8892.

I see what's going on here. The issue is that we give the sub-expression sinOrCos && Math.sin the type ((x: number) => number) | boolean. Since the result could be the boolean value false, this is technically not wrong. But it is a little bit too permissive. The type really should be ((x: number) => number) | false, meaning that the only the boolean value false is possible. We should likewise return T | 0 and T | "" for && operations where the first operand is of type number or string respectively.
Then we should furthermore say that in an x || y operation, we remove the definitely-falsy types (undefined, null, void, false, 0, and "") from the type of x in the resulting union type.
Now, the only problem with this solution is that we don't (yet) support boolean literal types or numeric literal types. This means we need to do one of the following:

Add support for boolean and numeric literal types now.
Back out #8949 and add support for boolean and numeric literal types later.

Adding @mhegazy and @RyanCavanaugh.

Add support for boolean and numeric literal types now.

:+1:

and numeric ranges:
type Positive = number > 0;

Numeric ranges? Are those even possible? That'd be über cool though.
I always wanted to use boolean literals for overloaded functions just like strings do.
I wonder whether those proposed numeric literals would include enums as well?
But of course the most important thing now is to have the && + || archaic idiom back!  :P


Error attempting a cast send transaction: (code: -32602, message: Invalid block range, data: None)

Describe the bug
When attempting to use cast send to transfer eth from one account to another on a testnet, the call fails with an error about an improper type.
Expected Output
Successful transfer of value from one account to another.
Actual Output
The cast responds with
(code: -32602, message: Invalid block range, data: None)

while the reth node, with the debug statements turned on, prints
2023-03-24T23:03:52.014116Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body completed
2023-03-24T23:03:52.014129Z ERROR connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: [next_inner] Deserialization to "ethereum_types::uint::U64" failed. Error: Error("invalid type: integer `10`, expected a (both 0x-prefixed or not) hex string or byte array containing between (0; 8] bytes", line: 1, column: 2), input JSON: "10,\"latest\",[5.0]]"
2023-03-24T23:03:52.014137Z ERROR connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: Error parsing "block_count" as "U64": InvalidParams(invalid type: integer `10`, expected a (both 0x-prefixed or not) hex string or byte array containing between (0; 8] bytes at line 1 column 2)

Steps to reproduce

Use the genesis file mentioned in this gist to generate a database called node1.

Call the reth with the following node subcommand (note that the secret-key and jwtsecret can be removed)

 RUST_LOG=info,sync::stages=trace,downloaders=trace,debug reth node --chain genesis.json --db node1 -vvvvv -d --http.addr <IP_ADDRESS> --ws.addr <IP_ADDRESS> --authrpc.addr <IP_ADDRESS> --discovery.port 30303 --port 30303 --http --debug.tip dc58c6e5c98d17d5a7b4add2990fe802fc6c8ced3c70a9a2e6cf5a5adef111b7 --secret-key secret1 --authrpc.jwtsecret jwt1.hex

Attempt the following cast:

cast send --value 1ether --from 0xde156C5bBB3EcdA5DFd12de7E34e4A08AB8e9e2B -i --json --rpc-url http://<IP_ADDRESS>:8545 0xc6Ba77E8c77e0762A323A8c5c36213062373136C

Node logs
2023-03-24T23:03:52.013221Z  INFO connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: Accepting new connection 1/100
2023-03-24T23:03:52.013371Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: parsed 4 headers
2023-03-24T23:03:52.013380Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body is content-length (47 bytes)
2023-03-24T23:03:52.013391Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body completed
2023-03-24T23:03:52.013434Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: flushed 166 bytes
2023-03-24T23:03:52.013676Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: parsed 4 headers
2023-03-24T23:03:52.013686Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body is content-length (82 bytes)
2023-03-24T23:03:52.013692Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body completed
2023-03-24T23:03:52.013752Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: flushed 1662 bytes
2023-03-24T23:03:52.013945Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: parsed 4 headers
2023-03-24T23:03:52.013949Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body is content-length (82 bytes)
2023-03-24T23:03:52.013953Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body completed
2023-03-24T23:03:52.013985Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: flushed 203 bytes
2023-03-24T23:03:52.014108Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: parsed 4 headers
2023-03-24T23:03:52.014112Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body is content-length (79 bytes)
2023-03-24T23:03:52.014116Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: incoming body completed
2023-03-24T23:03:52.014129Z ERROR connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: [next_inner] Deserialization to "ethereum_types::uint::U64" failed. Error: Error("invalid type: integer `10`, expected a (both 0x-prefixed or not) hex string or byte array containing between (0; 8] bytes", line: 1, column: 2), input JSON: "10,\"latest\",[5.0]]"
2023-03-24T23:03:52.014137Z ERROR connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: Error parsing "block_count" as "U64": InvalidParams(invalid type: integer `10`, expected a (both 0x-prefixed or not) hex string or byte array containing between (0; 8] bytes at line 1 column 2)
2023-03-24T23:03:52.014150Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: flushed 325 bytes
2023-03-24T23:03:52.014262Z DEBUG connection{remote_addr=<IP_ADDRESS>:56284 conn_id=27}: read eof
2023-03-24T23:03:53.650042Z DEBUG connection{remote_addr=<IP_ADDRESS>:53386 conn_id=0}: parsed 5 headers
2023-03-24T23:03:53.650099Z DEBUG connection{remote_addr=<IP_ADDRESS>:53386 conn_id=0}: incoming body is content-length (63 bytes)
2023-03-24T23:03:53.650220Z DEBUG connection{remote_addr=<IP_ADDRESS>:53386 conn_id=0}: incoming body completed
2023-03-24T23:03:53.650446Z DEBUG connection{remote_addr=<IP_ADDRESS>:53386 conn_id=0}: flushed 162 bytes
2023-03-24T23:04:00.653571Z DEBUG connection{remote_addr=<IP_ADDRESS>:53386 conn_id=0}: parsed 5 headers
2023-03-24T23:04:00.653622Z DEBUG connection{remote_addr=<IP_ADDRESS>:53386 conn_id=0}: incoming body is content-length (63 bytes)
2023-03-24T23:04:00.653739Z DEBUG connection{remote_addr=<IP_ADDRESS>:53386 conn_id=0}: incoming body completed
2023-03-24T23:04:00.654000Z DEBUG connection{remote_addr=<IP_ADDRESS>:53386 conn_id=0}: flushed 162 bytes

Platform(s)
Mac (Apple Silicon)
What version/commit are you on?
b913b6e from PR #1946
Code of Conduct

[X] I agree to follow the Code of Conduct

thanks for this,
currently in process of ironing out all RPC bugs.
on #1880 we also have mining support for testing purposes

I believe this is an issue with eth_feeHistory

Seems to be! This could be because there is no prior block.
 Error: Error("invalid type: integer `10`, expected a (both 0x-prefixed or not) hex string or byte array containing between (0; 8] bytes", line: 1, column: 2), input JSON: "10,\"latest\",[5.0]]"
2023-03-31T21:58:40.035801Z ERROR connection{remote_addr=<IP_ADDRESS>:65424 conn_id=0}:method_call{method="eth_feeHistory"}: Error parsing "block_count" as "U64": InvalidParams(invalid type: integer `10`, expected a (both 0x-prefixed or not) hex string or byte array containing between (0; 8] bytes at line 1 column 2)
2023-03-31T21:58:40.035807Z TRACE connection{remote_addr=<IP_ADDRESS>:65424 conn_id=0}:method_call{method="eth_feeHistory"}: send="{\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32602,\"message\":\"invalid type: integer `10`, expected a (both 0x-prefixed or not) hex string or byte array containing between (0; 8] bytes at line 1 column 2\"},\"id\":4}"
2023-03-31T21:58:40.035814Z TRACE connection{remote_addr=<IP_ADDRESS>:65424 conn_id=0}:encode_headers: Server::encode status=200, body=Some(Known(201)), req_method=Some(POST)
2023-03-31T21:58:40.035817Z TRACE connection{remote_addr=<IP_ADDRESS>:65424 conn_id=0}: buffer.queue self.len=124 buf.len=201
2023-03-31T21:58:40.035826Z DEBUG connection{remote_addr=<IP_ADDRESS>:65424 conn_id=0}: flushed 325 bytes

With #1880 and using --auto-mine, the cast returns a different error
cast send --value 1ether --from 0xf39Fd6e51aad88F6F4ce6aB8827279cff
Fb92266 --json --rpc-url http://<IP_ADDRESS>:8545 0xc6Ba77E8c77e0762A323A8
c5c36213062373136C --interactive

Error:
custom error: EIP-1559 not activated

and prints out a whole bunch of the following:
2023-03-31T22:18:40.449438Z  WARN execute{stage=Headers}: Stage reached maximum block, skipping. stage=Headers
2023-03-31T22:18:40.449470Z  WARN execute{stage=TotalDifficulty}: Stage reached maximum block, skipping. stage=TotalDifficulty
2023-03-31T22:18:40.449495Z  WARN execute{stage=Bodies}: Stage reached maximum block, skipping. stage=Bodies
2023-03-31T22:18:40.449530Z  WARN execute{stage=SenderRecovery}: Stage reached maximum block, skipping. stage=SenderRecovery
2023-03-31T22:18:40.449556Z  WARN execute{stage=Execution}: Stage reached maximum block, skipping. stage=Execution
2023-03-31T22:18:40.449584Z  WARN execute{stage=AccountHashing}: Stage reached maximum block, skipping. stage=AccountHashing
2023-03-31T22:18:40.449616Z  WARN execute{stage=StorageHashing}: Stage reached maximum block, skipping. stage=StorageHashing
2023-03-31T22:18:40.449651Z  WARN execute{stage=TransactionLookup}: Stage reached maximum block, skipping. stage=TransactionLookup
2023-03-31T22:18:40.449679Z  WARN execute{stage=IndexStorageHistory}: Stage reached maximum block, skipping. stage=IndexStorageHistory
2023-03-31T22:18:40.449705Z  WARN execute{stage=IndexAccountHistory}: Stage reached maximum block, skipping. stage=IndexAccountHistory
2023-03-31T22:18:40.449731Z  WARN execute{stage=Finish}: Stage reached maximum block, skipping. stage=Finish

I think this is fixed by #3288 (or at least I cannot reproduce this error anymore).

Thanks for the ping on this, will close this issue, but let us know if it is still persistent for you on the latest alpha @ryanorendorff 🙇🏻


创建项目显示的时区不一致

1.1.1 harbor 版本，
harbor 的容器里面时区已经修改，数据库的时区也修改了，但是创建项目依然不是东八区的时间，.

Did you try to query the data via DB and what is the timestamp?
Could you verify your browser's setting?

There will be another one opened by community user based on my communication.
Closing this one.


tests/ci: fix sonarqube analysis for main branch

Only use the branch options if it's actually running in a branch and
analyse main without them, sonarqube otherwise doesn't recognize the
main branch.

I found out that the scan results for main branch were actually not updated and were instead treated as pullrequests. This should fix it.


Use $.Array Instead of List for S.pipe and S.meld

As discussed in #148 .

:deciduous_tree: Thanks!


It extends Container, not ParticleContainer

Performance fix possible by implementing ParticleContainer ?
More info here: https://pixijs.download/dev/docs/PIXI.ParticleContainer.html

It depends on your use case, but in general the constant adding/removing children that this library does isn't what ParticleContainer (or normal Container) really likes - see https://pixijs.io/particle-emitter/examples/particleContainerPerformance.html


Storybook

React version (e.g., 16.8.5) 16.8.6
Concurrent mode no
Describe the bug
Example storybook doesn't work as intended.
I get this error:

Add a  component higher in the tree to provide a loading indicator or placeholder to display.
in ArticleList (at articlelist.stories.js:11)
in MockProvider (at articlelist.stories.js:9)

If I add a suspense component then it get stuck at loading
<MockProvider results={options.loading}>
    <Suspense fallback={"loading"}>
        <ArticleList maxResults={10} />
    </Suspense>
</MockProvider>`

To Reproduce
Steps to reproduce the behavior:
Small repo displaying the error:
https://transfernow.net/231vh0a9o5d1
Expected behavior
Working test :)

Found the problem. When you import 'rest-hooks/test' it imports the commonjs version (because it's expected to be able to run in node). However, in storybook it uses the normal module'd version that is built by webpack. This means the react context that is used in mockprovider is different from the one consuming in usecache(). So it's not passing the state because they are different contexts.
Really I should just make it a separate package...but I'll see if I can come up with an easier solution for now.

Workaround:
Import from rest-hooks/lib/test
import { MockProvider } from 'rest-hooks/lib/test';

Also - another bug is one of the mock test functions needs redux. So
yarn add redux
This will work until I figure out a real fix.

Released https://github.com/coinbase/rest-hooks/releases/tag/1.6.7


Add helper note to address frequent user question

Added a highlighted note under "Log in to Kibana" to better callout and clarify one of the more common support questions regarding additional users

Thanks, @AmberAlston !


copy-webpack-plugin error when update to 6.02 version

The error occurs after updating the plugin from version 5.1.1 to the latest version 6.0.2:

It looks like this code:
   new CopyWebpackPlugin([       { from:${PATHS.src}/${PATHS.assets}img, to: ${PATHS.assets}img},       { from:${PATHS.src}/${PATHS.assets}fonts, to: ${PATHS.assets}fonts},       { from:${PATHS.src}/static, to: '' },     ]),
needs to be replaced with the following:
   new CopyWebpackPlugin({       patterns: [         { from:${PATHS.src}/${PATHS.assets}img, to: ${PATHS.assets}img},         { from:${PATHS.src}/${PATHS.assets}fonts, to: ${PATHS.assets}fonts},         { from:${PATHS.src}/static, to: '' },       ],     }),
It worked for me, but you check.

Fixed commit
Stable version: 2.0.0


Expose yaml parser from QDup

To allow for extension of Parser with custom commands.
Following discussion on https://github.com/Hyperfoil/qDup/pull/172, this PR does not create a Parser static

This is an example of how I am using it: https://github.com/johnaohara/poc-automated-regression-bisect/blob/rebase-qDup/src/main/java/io/hyperfoil/tools/PerfAutoBisect.java#L113


Add yveCRV (Backscratcher) and yvstETH (Lido Staked Ether Vault) to Vaults UI

Is your feature request related to a problem? Please describe.
Yearn has two great products that are not featured in v2: our Backscratcher and our Lido staked ether vault.
Describe the solution you'd like
Implement the yveCRV Backscratcher and the yvstETH Vault at the top of the Vaults page to bring them more attention.
Describe alternatives you've considered
While the original plan is to put these on their own separate page, that will lead to these products being hidden and forgotten about. They should be at the very front of a user's attention, especially since the more CRV Yearn holds, the better our yields will be.
Additional context
yveCRV contract: 0x7CE6fDBCc4C22385D1BE50898f00fc8D0500A807
yvstETH contract: 0x15a2B3CfaFd696e1C783FE99eed168b78a3A371e
We would also want to include yield (growth) for both of these. For yveCRV it would be the 3Crv returns, for yvstETH it would be the staking returns.

Backscratcher is added at the moment, looking forward to Lido.

 Add yvstETH to Vaults UI

Out of scope for v2, yvstETH can be included in v3 Labs page potentially


Add bazel module for Universal_Robots_Client_Library version 1.4.0

Adds BUILD targets for

filegroup for rtde recipes
The ur_client_library
example binary full_driver
tests that don't depend on a simulator or real robot. (they however share ports)

I could unfortunately not find a stable release url. @bazel-io skip_check unstable_url

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (universal-robots-client-library) have been updated in this PR. Please review the changes.

Nit: Title is bazel, not blaze

@bazel-io skip_check unstable_url because I can unfortunately not find a stable release url.

@bazel-io skip_check unstable_url because I can unfortunately not find a stable release url.

The recommendation by https://buildkite.com/bazel/bcr-presubmit/builds/8927#01934a88-286b-4685-bb75-41df0c95a7e1 was to add that comment.
The release page (https://github.com/UniversalRobots/Universal_Robots_Client_Library/releases/tag/1.4.0) only lists the link I used in this request.


feat: add hdf5 support

This PR adds hdf5 frame/table readers and an example for Table Setup from Dishwasher.

NOTE: Unfortunately, polars doesn't natively support hdf5 (https://github.com/pola-rs/polars/issues/3520), and pandas/vaex didn't work either for the example dataset -- hence the raw iteration.

LGTM. As we are now upto 4 dataset formats. Shall we add some supporting docs f.e HOWTO.md

Shall we add some supporting docs f.e HOWTO.md

lets tee it up for the next release


Allow multivalued query parameters

This fix allows to apply several filters to a single column.
Currently every new filter overrides the previous one (e.g. builder.gte('x', 10).lte('x', 20) produces x=lte.20), this is due to how httpx.QueryParams.__set__ works.

Thank you for your contribution! I'm merging this now.


Support for multiple batterys

some devices have more than one battery, eg. some lenovo devices.
so it would be pretty cool to have support for displaying more than one battery.

would be cool to have an option for this, yes.

I'm implemented this feature. I will create a pull request as soon as I have cleaned up the code.

@vidister Do you need help before you can make a PR ?

Done in 7f1f217d84ae7f3b020ce28cd920f15722e15f52


Update createMethods.ts wrong function call

There is a typo in the call of the function for username field
faker.internet.username() => faker.internet.userName()

nice catch!

released in 0.11.1


Function / Alias Namespaces should allow noun prefixes

PowerShell considers Get to be the default verb.
So, resolving the command "foo" will resolve to Get-Foo.
When creating custom commands, we will often want there to be a command to get all of that type.

Closing as a red herring.
The transpilation works in this circumstance, but the eponymous function is still called, so it cannot be created interactively.
Luckily, this could be encompassed into noun support (#517)


[BACKEND] Fix ProgramPoint passing in AxisInfoAnalysis

Fixes #5122.
The ProgramPoint here is created on the stack. Then its address is passed to the MLIR SparseAnalysis code, where it is added as a dependency and later dereferenced. By the time the ProramPoint is dereferenced in the AbstractSparseForwardDataFlowAnalysis::visit, the AxisInfoAnalysis::visitForOpInductionVar will have finished and the ProgramPoint stack variable destroyed. This leads to a segfault (which can be reproed on the base rev with the lit test added in this PR).
The code modified in this PR was originally added in #4927, in conjunction with updating the llvm-project hash to b5cc222d7429. However, as noted in https://github.com/llvm/llvm-project/pull/110344 (the llvm-project PR that has made the refactoring prompting the AxisInfo.cpp change in #4927):

For dense forward data-flow analysis and other analysis (except dense backward data-flow analysis), the program point corresponding to the original operation can be obtained by getProgramPointAfter(op)

As the AxisInfoAnalysis (in Triton) inherits from SparseForwardDataFlowAnalysis (in MLIR), in this PR we follow the above which resolves the segfault issue (as the ProgramPoint is now stored in the instance-level state of the pass).
P.S. The lit test added in this PR is not exactly minimal. However, I did my best to minimize it starting from the 400-line repro TTGIR in #5122. Further minimization does not seem to expose the segfault.

@ThomasRaoux

should it be:
getLatticeElementFor(op, op.getLowerBound())->getValue();

IIUC, getLatticeElementFor here takes ProgramPoint* as the first argument (used to be ProgramPoint before https://github.com/llvm/llvm-project/pull/110344) which is not directly initializable from scf::ForOp. There is also getLatticeElement here which just takes a Value and returns the same thing as getLatticeElementFor. Do you mean we can use getLatticeElement here instead of getLatticeElementFor as in the original code (my impression was that adding a dependency is intended)?

@ThomasRaoux

should it be:
getLatticeElementFor(op, op.getLowerBound())->getValue();

IIUC, getLatticeElementFor here takes ProgramPoint* as the first argument (used to be ProgramPoint before llvm/llvm-project#110344) which is not directly initializable from scf::ForOp. There is also getLatticeElement here which just takes a Value and returns the same thing as getLatticeElementFor. Do you mean we can use getLatticeElement here instead of getLatticeElementFor as in the original code (my impression was that adding a dependency is intended)?

You're right, looks like I was looking at some old MLIR version where there was implicit casting from Operation to ProgramPoint. The code looks right

Cherry-picked to rc/3.2.x, thanks for the fix @aakhundov


My GatsbyJS website fails to build

My GatsbyJS website builds perfectly on Azure Pipelines, GitHub Actions, Netlify, and yet it fails to build as an Azure Static Web App.
After creating the website, I can see that the first run failed as I had a requirement for yarn ">=1.22" in the engines node inside the package.json file: https://github.com/PedroLamas/pedrolamas.com/actions/runs/111930224
I've now lowered that to 1.17, yet it still fails to build, this time due to some error while processing the images: https://github.com/PedroLamas/pedrolamas.com/actions/runs/111933866
The branch in use is here: https://github.com/PedroLamas/pedrolamas.com/tree/azure-test

Thanks.
adding @miwebst

This morning someone also ran into this exact issue and the fix was to update the gatsby config
https://github.com/micahgodbolt/micahgodbolt.com/commit/f516323e59f68922cc5958f24f22d118ad59bf8d
Error https://github.com/micahgodbolt/micahgodbolt.com/runs/696944712?check_suite_focus=true

Yes this is because our version of Oryx is missing this package:  libGL.so.1
@johnpapa , @craigshoemaker we should update our Gatsby doc to do the build before our Github Action. Otherwise we will keep seeing people hit this.

Hi @anganti, thank you for your suggestion but I wouldn't call disabling the automatic conversion of images files to webp format a "fix", as that is basically cutting down the functionality provided by GatsbyJS!

@miwebst thank you for your comments, but wouldn't it be easier to just add the missing package to "permanently" fix the problem?
Also, my first failure was due to my own specification that this site required yarn 1.22 or above, I know I can bundle yarn in the repo, but is there a way I can force the build process to download and use the correct version of yarn?

@PedroLamas agree, a more better word would have been mitigate. And the other option would be as @miwebst suggested to skip the build as together via StaticWebApps GitHub action and purely use it for deployment.

Yes Pedro you have a good point, we could add the missing package. The challenge here is that the more packages that we add to our base image, the larger it becomes, and the longer it takes for your action to start.
We are still investigating options for making this faster and have the libraries that apps need. If you have feedback on that, please let us know!

@anganti thanks for your help, seems that adding the build steps to the azure-static-web-apps-jolly-ground-016a8c003.yml file did the trick! https://github.com/PedroLamas/pedrolamas.com/commit/b82fcbcef206da534f6e661521d2f91b452f24e2
I still need to properly test this, but I can already see the site live at https://jolly-ground-016a8c003.azurestaticapps.net/

Ok, got it all working in the end, with images and custom domain!
https://azure-test.pedrolamas.com
I've ran some quick benchmarks on it:

https://www.pedrolamas.com - perf 96/100 (built and hosted on Netlify, served by Cloudflare CDN) https://www.fastorslow.com/app/profile/f2f146f8-11f5-5526-b14b-eca2d8e9b4ec
https://azure-test.pedrolamas.com - perf 98/100 (built by GitHub Actions, hosted and served by Azure Static Web Apps) https://www.fastorslow.com/app/profile/ca6be8e7-1db8-5e42-b92c-cdb5eff79857

Some initials quirks to deploy, but very impressive results in the end!! 😊
I;m closing this ticket as this is a fully valid workaround for the problem, but I would recommend either changing the instructions or making some changes on the way Gatsby websites (and possibly others) are built!

@anganti, @PedroLamas - so does the doc need to have both the changes for disabling wbp and updating the uses section?

My take is not to disable webp or anything else (it should just work as it is and not require specific changes for Azure Static Web Apps to be happy with)
Instead, just do a normal build before invoking the Azure/static-web-apps-deploy action so that all it needs to do is copy and publish the static files (so will skip the need to build on this step as it did on the previous one)

@softchris - do you have this in your learn module?

Before we update the docs, lets finish our exploration into the larger image that should solve this problem. @PedroLamas do you mind if I fork your repo for testing?

@miwebst please go ahead! 😁

@softchris - do you have this in your learn module?

I don't have an instruction where I tell them to build the Gatsby project prior no. I'll wait for @miwebst before doing any update as he wanted to explore a solution involving the image

Hey @PedroLamas, I've updated our image to use the larger version of Oryx that contains the necessary dependencies for webp.
You will still need to downgrade your version of yarn. (@kichalla as a side ask, is there anything we can do to avoid this issue in the future- maybe download latest yarn on the fly?)
Aside from that everything should just work! Do you mind giving it a try?

@miwebst it works!!
I've just done my changes to use the default building mechanism and now it is working fine!
On the plus side, I was surprised to see that the environment variables my build needs are being correctly passed so everything works fine!


How to use this project? What are parameters of train ?

There is no training with CNOS. We use pre-trained models provided DINOv2 and SAM).
README.md provides all the instructions to use this project.

what is the "src"? How to use it?


Cosmos DB discussion:PartitionKey

It's not a bug, but I'd like to trigger a discussion around the setup of the PartitionKey in the CosmosDB provider.
Initially, in 2.2 preview 2, there was no support for partitionkeys. CosmosDB didn't really enforce the use of it either, unless you went for shared throughput on database level.
Because we have a database per microservice, and a collection per tenant, we did not want to pay 20€/month/collection, and thus went for the shared throughput approach.
To be able to do this we had to do some plumbing ourselves:

we had to get the CosmosDB provider working (missing headers)
we had to implement basic support for partitionkeys
we had to support dynamically setting the container

Up until now this works pretty smooth, until yesterday I was digging around in the stored procedures section of Cosmos, and understood that a SP runs within a PartitionKey. And that's really sh*tty, as we've used the Id field (generated guid by EF) to set as the PK, hardcoded in the provider.
This doesn't allow us to do bulk deletes/updates though...
As the architecture of our platform was getting shaped, our revised plan was to start using Discriminator as the PartitionKey for most of the cases. This would at least allow us to do bulky things within the same entity type.
However, I was digging in the latest codebase for 3.0 preview 3(?) And saw that PartitionKey is set to 0. I didn't quite understand that, and would like to discuss if we cannot set this up using fluent api? On entity level isn't fit for all purposes as many entity types can be stored in one collection, but you can only have one PartitionKey.
What's your thoughts on this?

Triage: @AndriySvyryd to look for dupe.

Duplicate of https://github.com/aspnet/EntityFrameworkCore/issues/12086
Partition key configuration is not implemented yet


Some operators e.g. rxjs/operator/multicast pulls in code for all operators now

It looks like now that the older operator files import the lettable operators, they (unintentionally?) import all operators.
https://github.com/ReactiveX/rxjs/blob/de9f2c8543381ae5f2fa31eb2c9968329ef4fbe0/src/operator/multicast.ts#L4
https://github.com/ReactiveX/rxjs/blob/de9f2c8543381ae5f2fa31eb2c9968329ef4fbe0/src/operator/buffer.ts#L3
https://github.com/ReactiveX/rxjs/blob/de9f2c8543381ae5f2fa31eb2c9968329ef4fbe0/src/operators/index.ts#L1-L59

I also see this pattern is used in some pending PRs too
I've been out of the loop, so it's entirely possible I'm confused or there is some magic that prevents it from being a problem--without requiring people use treeshaking. Or maybe that's the plan?

Using this harness with a non-tree-shaking, CommonJS bundler:
const Observable = require("rxjs/Observable");
require("rxjs/add/operator/map");

When bundling<EMAIL_ADDRESS>the resultant bundle size is 39,151 bytes.
When bundling<EMAIL_ADDRESS>the resultant bundle size is 550,768 bytes.
If, in operator/map.ts, this were to be used instead:
import { map as higherOrder } from '../operators/map';

The resultant bundle size would be 42,638 bytes.

@cartant good catch. I was wrong: it's not the lettable operators which pull in the others, it's the older operator files that do that now, as they defer their implementation to the lettable forms.


Update dependencies

Update OkHTTP to version matching internal recommendation
Update SpringFox from 2.x to 3.x
Move Swagger/SpringFox into its own module that can be ignored or taken as needed

Coverage decreased (-0.002%) to 93.912% when pulling 94e2c3ab873964ece27a7db14e25d3a6eacf3c1a on tgianos:updateOkHttp3 into f6273cc8a372fd0e419e7782cba64bf44dec5d41 on Netflix:master.


404 not found using npx ts-remove-unused

Not sure what I'm doing wrong here?
> npx ts-remove-unused --check
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/ts-remove-unused - Not found
npm ERR! 404
npm ERR! 404  'ts-remove-unused@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npx @line/ts-remove-unused

My expectations was that people would npm i before npx ing but I've learnt that's not always the case... I've changed the  example code snippets in README to npx @line/ts-remove-unused and I will work on the screenshot as well!
I've also published https://www.npmjs.com/package/ts-remove-unused to avoid risks.


Run Minecraft as correct user

A recent change to the Minecraft server container now runs Minecraft
as user/group 1000 instead of root. When the persistent volume (/data)
is mounted, it's not readable by this user unless we specify an
appropriate securityContext, which will ensure that the persistent
volume is mounted with the appropriate uid/gid.
@gtaylor

I ran into the same issue, and @AlainRoy's changes fixed the issue for me.
Can we re-open this, or can I open a new PR?


Cannot install "stuntrally" because of hash mismatch in dependency.

Trace:
[...]
output path ‘/nix/store/28z2f8xzy2i7f4cy842lr34d1m5xiaml-tracks’ should have r:sha256 hash ‘1j237dbhd1ik5mj8whbvlff5da9vzzgiskcj5nzfpw1vb1jpdjvd’, instead has ‘1614j6q1d2f69l58kkqndndvf6svcghhw8pzc2s1plf6k87h67mg’
cannot build derivation ‘/nix/store/icsqv1hyn47annjprkzqz8hbk1vgdwjp-stunt-rally-2.5.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/icsqv1hyn47annjprkzqz8hbk1vgdwjp-stunt-rally-2.5.drv’ failed

This should be fixed now. It seems I forgot to commit the new hashes when updating back then.


Study with Photometric Interpretation YBR_FULL_422 are "green"

Hello to everyone,
when I try to visualize a study with Photometric Interpretation YBR_FULL_422 the images are "green". Seems like there is trouble with the color channels.

If I open the same study with another viewer (weasis or osirix) the images are correctly shown.
I have this problem with OHIF Viewer v2 and v3-stable.

Can you help me?

I'm investigating this early next week.

is this still happening in the latest master branch?

Hi @sedghi I will check next week.
Did you fix it?

We had couple of fixes, so please try

same issue v3.8.0beta-27

Could you kindly provide the data if it has been anonymized and you can confirm that there is no patient health information present in any of the headers or embedded within the pixel data?

Check out the latest master branch, it is most likely fixed

I'm running 3.8.0-beta.54 and still seeing the same issue here. Do you still need some test data ? I might be able to provide some if it's still needed.

It's not just about the data, but also about what servers do (arbitrarily). It would make sense to send both the data and server information.

@BITC01
Hey, the issue has already fixed
@sedghi helped me a lot solving it
Cloning the latest version should solve the problem.

You don't need this even anymore, it is default

but try

@BITC01 Hey, the issue has already fixed @sedghi helped me a lot solving it
Cloning the latest version should solve the problem.
Adding this :
dataSources: [ { ... acceptHeader: [ 'multipart/related; type=application/octet-stream; transfer-syntax=*'] }, }], to your configuration file (under dataSources) will also solve the issue

I tried that but it didn't work unfortunately, We are not using OrthanC as our server so it's something else.
A little more information before I go through the process of uploading. I have tried the same with Uncompressed studies and it works fine(ie; xfersyntax=1.2.840.10<IP_ADDRESS>.50= Jpeg Process 1) . Its just UltraSound studies that have been compressed jpeg lossless (We are encoding as Process 14 =xfersyntax= 1.2.840.10<IP_ADDRESS>.57).
Our reply sends the following header in response to the ..frames/1 call to wadors.
Content-Type: "image/jpeg"; transfer-syntax=1.2.840.10<IP_ADDRESS>.57
and we also send back the raw pixel data from the dicom file without conversion as far as I can tell.
Thanks for looking into this.

As i said it is about servers, they sometimes tell (in metadata) that it is YBR_FULL but in reality it is something else. So it is a bug in your server, we are trying to catch those anomalies here, maybe stay tuned and that will fix it, but in reality it is the server issue https://github.com/cornerstonejs/cornerstone3D/pull/829

As i said it is about servers, they sometimes tell (in metadata) that it is YBR_FULL but in reality it is something else. So it is a bug in your server, we are trying to catch those anomalies here, maybe stay tuned and that will fix it, but in reality it is the server issue cornerstonejs/cornerstone3D#829

I have written a bit of code to replace the metadata with whatever it "should" be. Can you tell me how I can figure out what it should be. I've replaced the metadata with "RGB" , "YBR_FULL_422" and neither of those values make a difference. If I can see it in the BINARY data somewhere maybe that would lead me to the right place ?

The server should respond with whatever the client is asking, if it is asking for * it should return as it is, and if it converts the color spaces the metadata should be in sync
you can read more here https://discourse.orthanc-server.org/t/orthanc-convert-ybr-to-rgb-but-does-not-change-metadata/3533?u=alireza

I read that thread before posting here. It is what lead me to believe that the issue is the colorspace. However unlike in orthanc , our server simply sends back the pixeldata AS IS. The server does not decompress it , thus  the Metadata PHOTOMETRIC value and the actual colorspace for the pixel data should be in sync naturally. However I'm still seeing the green overlay.
Is there a test I can perform on the binary pixeldata we're returning to make sure it's colorspace matches what is in the metadata.
I do have access to the server code and I'm attempting to find this bug, if it is indeed in the server I'd like to squash it.
btw Thanks for your assistance and attention to this.

just a small added bit of info JIC it makes a difference . We are using Dgate for the dicom compression.

YBR and RGB can't be easily distinguished by the pixel data. I've shared a link to a PR in Cornerstone3D. Once it's merged, it might solve your problem. In the meantime, you can try checking out that branch and locally linking it to OHIF for testing purposes.
https://docs.ohif.org/development/link/

@sedghi
I'll link it in and see if it makes a difference. Thanks again for you assistance.

@sedghi
I hope it's ok to ask this here. I can make this request elsewhere if there's a more appropriate location .
I had some time today to try and link in the PR you were discussing. But first I followed your tutorial on linking in cornerstone3d tools into ohifviewer. before I did the yarn link @cornerstonejs/tools I was able to successfully run yarn dev and yarn run build. Once I linked it in i am now getting an error whenever I try to yarn run build or even yarn dev. I get the following error output from yarn

using description file<EMAIL_ADDRESS>(relative path: ./Filters/General/ContourLoopExtraction)
@ohif/app:               no extension
@ohif/app:                 Field 'browser' doesn't contain a valid alias configuration
@ohif/app<EMAIL_ADDRESS>doesn't exist
@ohif/app:               .js

I'm not a big react person so I'm at a bit of a loss as to where to go from here. If you might have a pointer in the correct direction that would be great.

You need to upgrade vtk.js on OHIF, we have PRs soon, but since you are linking you should add that

@sedghi
As requested in the office hours last week I have found a study that exhibits the behavior outlined in this thread. I have verified this by using https://viewer-dev.ohif.org/localbasic . I have attached the zipped study to this post.
As a reminder to the discussion in office hours I was able to generate an OHIF viewer with the Cornerstone3d PR #829  and have verified that PR does not fix this issue.
I also need to correct a statement I made above. We are not compressed as transfer-syntax= 1.2.840.10<IP_ADDRESS>.57 , We ARE compressed as transfer-syntax= 1.2.840.10<IP_ADDRESS>.70.
Please let me know if I can provide any more information or study data.
BrokenUS.zip

closing in favor of https://github.com/OHIF/Viewers/issues/4082


Problem 3D2DtexteScreen

Now since 3day i dont see my textscren permanent "im superadmin". and the players cant ues this item ... :/ help pls and thank for reply to steam workshop
[3D2D Textscreens] lua/weapons/gmod_tool/stools/textscreen.lua:56: attempt to call method 'SetLine' (a nil value)

LeftClick - lua/weapons/gmod_tool/stools/textscreen.lua:56
unknown - gamemodes/sandbox/entities/weapons/gmod_tool/shared.lua:254

Please disable all other addons and report if this issue still occurs. I don't see how this could happen (and am unable to reproduce), without another addon removing the entity as soon as it's being created.

I found thank you for the tip :)
this was in conflict addons
http://steamcommunity.com/sharedfiles/filedetails/?id=239222059

Thanks for the update! Glad you figured it out!


Fixed ERROR in Error during template compile of 'AppModule' Bug

Problem was there was logic in the ModuleWithProvider and i also clean up how to set the default to Bootstrap 4.

Looks like I'm still getting the error even with these changes.


add support for multiple versions

What changes were proposed in this pull request?

extend MAX_VERSIONS flag usage (it was used to set how many versions was fetched only)
give the ability to create table which holds more than one version
give the ability to fetch more than one (latest) view of the same entity
you can set number of versions to fetch

How was this patch tested?
It contains own suite with few integration tests.

Thanks for this PR. I'll review this soon.

Retriggered travis CI build.

@btomala The PR is useful. Some minor comments.

I updated the code comments a little bit.

Thanks, @btomala . Merged to branch-1.6.


added cpc pay page

/staging

After discussion with @rarcif , we will merge into gitbook branch instead


[CLEANUP]: Move image upload context to contexts folder

Description of what needs to be cleaned up
The image upload context file was added to the upload folder in the images component. To be consistent we should move it to the contexts folder.

done in PR #117


Implement instruction handler

Issue description
The govern layer must receive a queue of instructions and discern which task is going to handle every message. To do so, it has to assign that message to the appropiate task
Additional info
Refer to the issue #3 for further details

Blocked by #3


Add event hooks to nuxt-loading component

Is your feature request related to a problem? Please describe.
I have some async data being loaded in fetch. I want to scroll on the page after all content is loaded. The easiest way seemed to be something like this.$loading.$once('finished').
Describe the solution you'd like
I'd like some events added to the nuxt-loading component so people can use it as the source of truth if stuff is still being loaded. The only one I am concerned about is finished, but I could see some others added as well.
Describe alternatives you've considered
Not using the component as the single source of truth. This can be more accurate, but also takes more work. Using the nuxt-loading component is fast, has good support with things like axios already, and is pretty simple to use.

Let's track progress via https://github.com/nuxt/nuxt/issues/14221.


Publish Concise as a npm module

Would be nice if we could install Concise with npm.

Done! npm install concise.css


Avoid conflicts with possible Object.prototype accessors

Coming from PR #1 this is the spec compliant version of the method.
In case there is some obtrusive polyfill (Symbol) or framework around (Polymer WeakMap sham) that uses accessors on the Object.prototype the current version would possibly suffer conflicts when such property, or symbol, would be assigned to the accumulator object.
The current check avoids, only when necessary in order to preserve performance,  every possible conflict with these cases.

I also don't know what's wrong with your Travis CI node 4.2 but I'm sure you understood what is the problem and how this should be fixed.
A simplified version of your code has been updated in the poly shown in the spec page.

node 4.2 is the only one that runs the linter - the output on https://travis-ci.org/ljharb/object.getownpropertydescriptors/jobs/106689619 shows the linting error.

Found a delightful bug in Object.getOwnPropertyNames in node 0.6-0.12: https://gist.github.com/ljharb/8956b254bd8b7d3f4c07
This makes testing for this case difficult, since the implementation uses getOwnPropertyNames internally, and I don't see any way to avoid it.

Fix released as v2.0.2

nice bug. I don't see it as a problem because even MIPS platform has at least node 0.10 available and since 3+ years ago. I would stop testing and discouraging the usage of node 0.6 regardless this specific bug. just my 2 cents

Found a delightful bug in Object.getOwnPropertyNames in node 0.6-0.12

The bug in object literal, not in Object.getOwnPropertyNames:
Object.defineProperty(Object.prototype, 'a', { set: function (v) { throw new Error(v); } });;
({a: 42}); // error

@zloirock oh dear gosh that's even worst ... !

whoa, nuts! @zloirock so if i create {a: 42} in two steps it won't trigger it?

I guess the following will work
Object.defineProperty(Object.prototype, 'a', { set: function (v) { throw new Error(v); } });
var o = Object.defineProperty({}, 'a', {configurable: true, enumerable: true, writable: true, value: 42});

if it doesn't , that would explain the weirdo bug in older Android where you have to delete (where possible) inherited accessors before being able to overwrite them.
Funny bugs are funny, thankfully node .6 is the equivalent of IE5

I'm not sure that will work - https://github.com/ljharb/object.getownpropertydescriptors/blob/master/test/tests.js#L35-L42 is where the bug happens in the test, with an object that was created before the Object.prototype setter was created.


Constraint DSL: Generate

Provide a constraint that can generate a customized primitive for a given list of instances.
These instances should be excluded from subcircuit identification.
Parameters should be passed to the generating class.
class Generate():
    instances: List[str]
    name: str
    interleave: Optional[Literal["common_centroid", "interdigitated"]] = "common_centroid"
    parameters: Optional[Dict[str, Union[str,int]]

Example:
{
  "constraint": "generate",
  "instances": ["mn1", "mn2"],
  "name": "diffpair",
  "parameters": {
    "n_rows": 4,
    "add_guardring": true
  }
}

@kkunal1408 , could you please review this enhancement? This is to customize transistor, passive, unknown device primitives.

Can we discuss this during today meeting?

From other discussion:
templates.sp: * @: Generator(name="mos", params=[])
const.json:   * @: Generator(instances=["mn0"], params=[insert_dummy, share_diff])
const.json:   * @: Generator(instances=["mn1", "mn2"], params=[nrow, id, sparse])
combine template and const where const has precedence
What happens with a generator constraint?
	Generator(instances=["mn1", "mn2"], params=[nrow, id, sparse])
		create a virtual subcircuit guid_x for mn1 and mn2
		make sure mn1 and mn2 to matches to a template in templates.sp
		.subcircuit guid_x:
			const: generator(name="mos", params=[nrow, id, sparse])

@kkunal1408 , is there a question?

No, I copy-pasted the future work which we identified from #964 . I think both have some relation. We can brainstorm both together.

This issue indirectly addressed in recent PR's


Remove logging from azblob reader

also move accountName into options parameter
re: AB#9491

LGTM. Thankyou very much for sorting out the mess I left there!

np :) no mess left!


Not compatible with recent kit versions

The add-on has not been compatible with the last few kit releases.

New release for UMAExtension, But it's required CORE version 1.62.

New release for UMAExtension, But it's required CORE version 1.62.

Looks like it's mostly working, but character deserialization is broken. Need to add namespace MultiplayerARPG to PlayerCharacterDataExtension_UMA.

Looks like it's mostly working, but character deserialization is broken. Need to add namespace MultiplayerARPG to PlayerCharacterDataExtension_UMA.

Oh, thank you, I've fixed it.

Oh, thank you, I've fixed it.


Unit tests failures

@karrtikr

ts-node tests should not run windows registry tests on linux

These tests used to work and were platform independant.
I didn't realize the reason they were failing is because they are no longer platform independant. If that's the case, then we might want to run unit tests on a Windows box as well in the PR pipeline.

@DonJayamanne I didn't realize these were supposed to be platform independent. Something is likely broken. We will need to investigate.

I'm fixing this in PR #12236.


Funimation extractor not working correctly

Checklist

[X] I'm reporting a broken site
[X] I've verified that I'm running yt-dlp version 2021.10.22. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've read the guidelines for opening an issue
[x] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
Australia
Description
I am trying to download Demon Slayer: Mugen Train (LINK) from Funimation, but when trying to download the JSON data, it errors.
Verbose log
[debug] Command-line config: ['--netrc', 'https://www.funimation.com/v/demon-slayer-kimetsu-no-yaiba/demon-slayer-kimetsu-no-yaiba-the-movie-mugen-train', '-F', '-Uv']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, err utf-8, pref UTF-8[debug] yt-dlp version 2021.10.22
[debug] Python version 3.10.0 (CPython 64bit) - macOS-12.1-x86_64-i386-64bit
[debug] exe versions: avconv present, avprobe present, ffmpeg N-104454-gd92fdc7144, ffprobe N-104454-gd92fdc7144, rtmpdump 2.4
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
yt-dlp is up to date (2021.10.22)
[funimation:page] Checking geo-location
[funimation:page] Logging in
[debug] [funimation:page] Extracting URL: https://www.funimation.com/v/demon-slayer-kimetsu-no-yaiba/demon-slayer-kimetsu-no-yaiba-the-movie-mugen-train
[funimation:page] demon-slayer-kimetsu-no-yaiba_demon-slayer-kimetsu-no-yaiba-the-movie-mugen-train: Downloading JSON metadata
[debug] [Funimation] Extracting URL: https://www.funimation.com/player/1621628
[Funimation] 1621628: Downloading player webpage for 1621628
[Funimation] demon-slayer-kimetsu-no-yaiba-the-movie-mugen-train: Downloading Uncut japanese (1751780) JSON
WARNING: [Funimation] Funimation said: Error 4 - No valid Free Avails for this experience
[Funimation] demon-slayer-kimetsu-no-yaiba-the-movie-mugen-train: Downloading Uncut english (1621628) JSON
WARNING: [Funimation] Funimation said: Error 4 - No valid Free Avails for this experience
ERROR: [Funimation] 1621627: No video formats found!; please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/Cellar/yt-dlp/2021.10.22/libexec/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 1280, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/Cellar/yt-dlp/2021.10.22/libexec/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 1318, in __extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/usr/local/Cellar/yt-dlp/2021.10.22/libexec/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 1368, in process_ie_result
    ie_result = self.process_video_result(ie_result, download=download)
  File "/usr/local/Cellar/yt-dlp/2021.10.22/libexec/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 2237, in process_video_result
    self.raise_no_formats(info_dict)
  File "/usr/local/Cellar/yt-dlp/2021.10.22/libexec/lib/python3.10/site-packages/yt_dlp/YoutubeDL.py", line 882, in raise_no_formats
    raise ExtractorError(msg, video_id=info['id'], ie=info['extractor'],
yt_dlp.utils.ExtractorError: [Funimation] 1621627: No video formats found!; please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.

Funimation requires cookies to extract properly from my experience, it's been like that as long as I can remember though.

so netrc doesn't work yet?

nope, downloaing cookies and using them doesn't work

so netrc doesn't work yet?
netrc is working and it does log in, the problem I think is Funimation considering ytdlp as another device if cookies aren't supplied and free accounts are limited to just 1 device so if your web session is still active you won't be able to download anything without cookies. I think the base sub is limited to 2 devices so it can still happen sometimes.
nope, downloaing cookies and using them doesn't work
Works for me, I'm using manually extracted cookies rather than the cookies from browser option though.

netrc is working and it does log in

oh, I thought login had broken. Hence why this is being kept open
@Jules-A can u try to download the same video as OP and confirm whether you can reproduce the issue

Do you have a Funimation sub?
AnimeLab account, which is equivalent to Premium Plus Yearly

btw i downloaded the video specified using the raw m3u8 stream with cookies supplied, if that's any help

@Jules-A can u try to download the same video as OP and confirm whether you can reproduce the issue

I already said that it was working for me and I can not reproduce, well with cookies supplied that is. If I don't supply cookies then I get the same error as OP.

AnimeLab account, which is equivalent to Premium Plus Yearly

Hmm same here.

Can confirm the issue exists. Unless cookies are used, incapsula silently voids the login causing the "No free experience" error


Use the new iOS 15 Wallet

In iOS 15 we got a new wallet module for vaccine certificates.
You could actually replace your old one with this:
https://www.computerbild.de/artikel/cb-News-App-Check-iOS-15.1-Impfnachweis-wandert-in-die-Wallet-30805397.html

https://developer.apple.com/news/?id=7h3vwlh5

Please see https://github.com/covidpass-org/covidpass/issues/75#issuecomment-924334367 & https://github.com/corona-warn-app/cwa-app-ios/issues/2965#issuecomment-925176909.
This doesn't help here.

@Ein-Tim thanks

@Ein-Tim thanks


How can I add Textbox

Hi Author,
I want to add a text box because iText is not wrapping.
[new fabric.Textbox]
please advise.
Thank you

@prabhathebeyonds
In the image-editor, text object is made up of i-text, so it is impossible.


just: 0.9.5 -> 0.9.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/casey/just/releases.
meta.description for just is: "A handy way to save and run project-specific commands"
meta.homepage for just is: "https://github.com/casey/just"
meta.changelog for just is: "https://github.com/casey/just/blob/v0.9.6/CHANGELOG.md"
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/qx5qbdscckjw3fvx38rd3iiszmbxh6rz-just-0.9.6/bin/just passed the binary check.

1 of 1 passed binary check by having a zero exit code.

1 of 1 passed binary check by having the new version present in output.

found 0.9.6 with grep in /nix/store/qx5qbdscckjw3fvx38rd3iiszmbxh6rz-just-0.9.6

found 0.9.6 in filename of file in /nix/store/qx5qbdscckjw3fvx38rd3iiszmbxh6rz-just-0.9.6

directory tree listing: https://gist.github.com/0d6a545daed5f2c2627892d92d7ec666

du listing: https://gist.github.com/3c3487207d267e01f862aac9bba8cc09

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
just

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qx5qbdscckjw3fvx38rd3iiszmbxh6rz-just-0.9.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A just https://github.com/r-ryantm/nixpkgs/archive/0830a2c41dbc2679465f180c375e04e1f3a593d3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qx5qbdscckjw3fvx38rd3iiszmbxh6rz-just-0.9.6
ls -la /nix/store/qx5qbdscckjw3fvx38rd3iiszmbxh6rz-just-0.9.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

just

Maintainer pings
cc @xrelkd @06kellyjac for testing.

I'm going to make a PR because I forgot to remove the v prefix from the changelog for the last release

Result of nixpkgs-review pr 128102 at 0830a2c4 run on aarch64-linux 1

1 package failed to build:

just

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Closing in favor of #128248


Feature Request: Can you add one time password generation TOTP and HOTP

Great tool.
Any chance you could add event and time based one time password generation

Here is an example of implementation in javascript of TOTP as defined in RFC6238 and used in Google Authenticator-like applications.
HOTP is the same except the step is defined by a counter maintained by both token and server rather than time.
TOTP_demo.zip


Cannot do a POST request with an empty body.

This works: pushReq.end("--request body (ignore this value)--")
But this doesn’t: pushReq.end() or pushReq.end("")

Oddly enough, when I create an isolated test case this error does not happen.  However, when I have a nested request, it does seem to happen.  Here is the OpenWhisk action where I am seeing this behavior:
https://github.com/IBM-Swift/BluePic/blob/develop/BluePic-OpenWhisk/actions/KituraCallback.swift#L88
If I remove the string value being passed into pushReq.end() then the request just seems to hang - this happens with both the empty string and nil value.

@rolivieri  and @triceam  I don't know if I fixed this issue or not. I improved things some what, but to be honest I wasn't seeing the problem before the fix.
Can you either verify that this fix actually helps or provide a standalone test case that shows the problem?

@shmuelk I defer to @triceam. Andy ran into this issue while developing the OpenWhisk code for BluePic.


fast-dds-gen-3.3.0 with idl-parser 3.0.0 : idl parse error observed when idl contains a struct which references an array typedef

The below mentioned idl file parsing fails with below mentioned error (idl-parser 3.0.0 is used alongwith fast-dds-gen 3.3.0) :
IDL file:

module module1
{
enum mod1_enum_val
{
value1, //1
value2 //2
}; //mod1_enum_val
}; //module1
const module1::mod1_enum_val enum1 = module1::mod1_enum_val::value1;
typedef string StringU;
typedef int32 IntArray[23];
struct SampleStruct
{
StringU stringU;
IntArray ArrayInt32;
}; //SampleStruct

Error:

Processing the file /tmp/IdlParseError.idl...
/tmp/IdlParseError.idl:11:26: error: Error evaluating array dimension: ;enum1=module1::mod1_enum_val::value1;enum1=module1::mod1_enum_val::value1;(23) | 0
/tmp/IdlParseError.idl:15:3: error: 'IntArray' was not defined previously

In the above idl file, there is a struct which tries to declare an int array as typedef. One observation is that when the enum declaration (const module1::mod1_enum_val enum1 = module1::mod1_enum_val::value1;) is removed/commented, the parsing works fine.
Below command is used :

<Path to java11 exe> -jar <path to fastddsgen.jar> -replace -ppDisable -d <path to folder where files should be generated> <path to IdlParseError.idl file>

For example:

"/home/user/java11/jre/bin/java" -jar "/home/user/fastddsgen.jar" -replace -ppDisable -d "/home/user/SampleFolder" "/home/user/IdlParseError.idl"

Additionally, please check the below IDL file as well:

module Top
{
const uint32 MAXLEN = 64;
const uint32 SeqLenAssumingThisModule = MAXLEN;
const uint32 SeqLen = Top::MAXLEN;
}; //Top
struct Sub
{
int32 userID;
double f64Data;
uint8 vChar;
}; //Sub
typedef Sub SubSequence[Top::SeqLen];
struct AllSubs
{
SubSequence Subs;
}; //AllSubs

Similar error is encountered:

Processing the file /tmp/IdlParseError_2.idl...
/tmp/IdlParseError_2.idl:13:36: error: Error evaluating array dimension: ;Top_MAXLEN=64;Top_SeqLenAssumingThisModule=MAXLEN;Top_SeqLen=Top::MAXLEN;(Top_SeqLen) | 0
/tmp/IdlParseError_2.idl:16:3: error: 'SubSequence' was not defined previously

Thanks for the report. We will take it into a look.

Hi @richiware ,
I have tried the fix and the previously mentioned IDL files are processing successfully.
Given below is another IDL file for which the processing fails with this fix as well:

module module1
{
enum mod1_enum_val
{
value1,
value2
}; //mod1_enum_val
}; //module1
const int32 myValUsingFullPathAsInt32 = module1::mod1_enum_val::value1;
const module1::mod1_enum_val myValUsingFullPath = module1::mod1_enum_val::value1;
const module1::mod1_enum_val myVal = module1::mod1_enum_val::value2;
module Top
{
const uint32 MAXLEN = 64;
const uint32 SeqLenAssumingThisModule = MAXLEN;
const uint32 SeqLen = Top::MAXLEN;
}; //Top
struct Sub
{
int32 userID;
double f64Data;
uint8 vChar;
}; //Sub
enum Modes
{
MODE1, //11
MODE2, //20
MODE3 //200
}; //Modes
const int32 myDefaultModeAsInt32 = Modes::MODE3;
const Modes myDefaultMode = Modes::MODE3;
const Modes myDefaultMode1 = Modes::MODE2;
typedef Sub SubSequence[Top::SeqLen];
struct AllSubs
{
SubSequence Subs;
}; //AllSubs

Error

Processing the file /tmp/IdlError3.idl...
/tmp/IdlError3.idl:9:70: error: Error evaluating expression: ;(module1_mod1_enum_val_value1) | 0
/tmp/IdlError3.idl:30:47: error: Error evaluating expression: ;Top_MAXLEN=64;Top_SeqLenAssumingThisModule=64;Top_SeqLen=64;(Modes_MODE3) | 0

Requesting you to take a look at this as well.

Hi @richiware ,
Can you please take a look at the above IDL file as well.

I was testing your last IDL file. The failure is caused by the integer constant that is set with a enumeration value. This corner case will be more difficult to be supported and right now I don't have that time.
I propose you to open a new issue for this new case and we will fix it when we have time and this issue could be closed automatically when the related PR are merged.

Hi @richiware ,
As requested in earlier comments, raised issue 385 for IDL parse error when integer constant is set with enum value.
Thanking you,
S.Ravi.Chaitanya


Compiling for Windows fails (mingw-w64-gcc)

Godot version:
master (https://github.com/godotengine/godot/commit/886afa9b7692bc263cf96c03882760521b74b942)
deleted godot folder and cloned again
OS/device including version:
Antergos (Arch Linux)
Issue description:
Output:

[Initial build] Linking Program        ==> bin/godot.windows.opt.tools.64.exe
[Initial build] /usr/lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld: platform/windows/os_windows.windows.opt.tools.64.o:os_windows.cpp:(.rdata$.refptr.FOLDERID_Music[.refptr.FOLDERID_Music]+0x0): undefined reference to `FOLDERID_Music'
/usr/lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld: platform/windows/os_windows.windows.opt.tools.64.o:os_windows.cpp:(.rdata$.refptr.FOLDERID_Videos[.refptr.FOLDERID_Videos]+0x0): undefined reference to `FOLDERID_Videos'
/usr/lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld: platform/windows/os_windows.windows.opt.tools.64.o:os_windows.cpp:(.rdata$.refptr.FOLDERID_Downloads[.refptr.FOLDERID_Downloads]+0x0): undefined reference to `FOLDERID_Downloads'
/usr/lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld: platform/windows/os_windows.windows.opt.tools.64.o:os_windows.cpp:(.rdata$.refptr.FOLDERID_Documents[.refptr.FOLDERID_Documents]+0x0): undefined reference to `FOLDERID_Documents'
/usr/lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld: platform/windows/os_windows.windows.opt.tools.64.o:os_windows.cpp:(.rdata$.refptr.FOLDERID_Pictures[.refptr.FOLDERID_Pictures]+0x0): undefined reference to `FOLDERID_Pictures'
/usr/lib/gcc/x86_64-w64-mingw32/8.3.0/../../../../x86_64-w64-mingw32/bin/ld: platform/windows/os_windows.windows.opt.tools.64.o:os_windows.cpp:(.rdata$.refptr.FOLDERID_Desktop[.refptr.FOLDERID_Desktop]+0x0): undefined reference to `FOLDERID_Desktop'
collect2: error: ld returned 1 exit status
scons: *** [bin/godot.windows.opt.tools.64.exe] Error 1
scons: building terminated because of errors.

Steps to reproduce:
git clone https://github.com/godotengine/godot.git
scons p=windows bits=64 target=release_debug tools=yes -j 8

Regression from #28166, CC @KLee1248.

Sorry for breaking this. I'm working on writing a pull request to fix this.
The issue is that for cross-compilation we just need to at the uuid library. I was able to get this to work locally (using Ubuntu), but just need to test and double-check before I submit it.
I'll also test this change against a clean Windows environment to make sure that everything still works as expected there.


module.openshift.aws_iam_instance_profile.openshift-instance-profile: "roles": [DEPRECATED] Use role instead. Only a single role can be passed to an IAM Instance Profile

Hi Dave,
Can you please check the below error.
Error : Error applying plan:
1 error(s) occurred:

module.openshift.aws_iam_instance_profile.openshift-instance-profile: 1 error(s) occurred:

aws_iam_instance_profile.openshift-instance-profile: Error creating IAM instance profile openshift-instance-profile: EntityAlreadyExists: Instance Profile openshift-instance-profile already exists.
status code: 409, request id: 36715f10-5cf2-11e7-b146-e900a1ed359e

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Changed few lines in 03-roles.tf
`resource "aws_iam_policy_attachment" "openshift-attachment-forward-logs" {
name       = "openshift-attachment-forward-logs"

roles      = ["${aws_iam_role.openshift-instance-role.name}"]

role      = "${aws_iam_role.openshift-instance-role.name}"
policy_arn = "${aws_iam_policy.openshift-policy-forward-logs.arn}"
}

//  Create a instance profile for the role.
resource "aws_iam_instance_profile" "openshift-instance-profile" {
name  = "openshift-instance-profile"

roles = ["${aws_iam_role.openshift-instance-role.name}"]

role = "${aws_iam_role.openshift-instance-role.name}"`

but got error on openshift-attachment-forward-logs removed it then was able to get openshift running. But this is just a workaround that  I tried.
please try fixing these issues, as this repo is pretty much helpful for anyone who is trying to play with openshift.

Hi @jagannathsarma I'll look into this this week.
One quick question - it looks like the setup failed because the role already existed. Have you tried removing all resources created by terraform and recreating?

@dwmkerr yes Dave I tried it then it worked with above mentioned edits, but cloud trail is giving issues so to make this setup work I have disabled cloud trail in my setup. and Even tried enabled hawkular-metrics from the link that you provided in docs, unfortunately that did not work.

Hmm definitely something weird going on. I've had trouble with roles before, I might be wrong but from memory there are some thing terraform cannot easily do with roles because it can be difficult to tell when they are fully created. I'll take a look

This issue has been solved, but for anyone who sees something similar, make sure to update your terraform client since these changes went in!


Dialog buttons no longer have foreground/background color tokens

In insiders.vscode.dev the dialog buttons are inheriting the colors of monaco-dialog-box:

I see this in a lot of places, and it looks to be caused by https://github.com/microsoft/vscode/commit/e5bf5a7939d586e33d5ae822891040dfa906aeb5#diff-66a07df088d0eb0a5f86befb962cf52e893a8cc3ae2fc716968effb45c485185


What's left for nodejs backend support?

Hey Jason!
I remember we briefly talked about the nodejs backend for UFront, and you said it's partially implemented. I'm wondering what's exactly left to implement / what are the main challenges there? Maybe we could break them down into specific issues to tackle here? I'd love to help.
Cheers.

Hi Marcelo, sorry for the late reply!
The latest ufront-mvc release filled in many of the missing pieces for NodeJS support, including:

Using the official Haxe Foundation NodeJS externs: https://github.com/HaxeFoundation/hxnodejs/
Using Franco's Express externs: https://github.com/abedev/hxexpress
Providing a FileSession implementation (that's all async friendly)
Providing a FileViewEngine implementation (also async friendly)
The HelloWorld example has been updated to work with NodeJS.

In terms of what is left:

There are some holes in the NodeJS HttpRequest object, see documentation on: http://api.ufront.net/nodejs/ufront/web/context/HttpRequest.html

Fixing the remaining inconsistencies with request parameters etc.
Get parseMultipartUpload / postString working.

Testing!

Try getting the Hello World example working.  (Easiest way will be to clone the ufront repo and all submodules, and then run ./setupDev to use the latest versions of each library, and the externs etc.)
If that works, then experiment with other more complex things.

Currently ufront-orm is based entirely on sys.db, so won't work on NodeJS.  That also means it won't work with ufront-easyauth or ufront-ufadmin.  D'OH!  I have a plan to make ufront-orm work with an asynchronous database manager, but it might take a while.  In the mean time, it would be good to:

Create some externs that work with UFCache - Maybe Redis or Memcached or similar?  These would let you use CacheSession and a few other goodies.
Create a UFAuthHandler that works using something easy on NodeJS.  Maybe an auth system that works with express already, something that uses NoSQL, etc.

Dreaming: I would love to implement Haxe remoting over web sockets with socket.io or similar :)

So thanks for the offer to help - honestly the most helpful thing will be to try get the environment up and running, compile the hello world, and experiment and let me know what I should be fixing or working on next :)
I'm going to close this issue - but feel free to open as many as you want with bug reports or feature requests or ideas... and if you have questions or need help ask on Gitter and I'll do my best to help.


How to achieve facial recognition trial wearing

I want to try on AR glasses with a front facing camera and load a remote GLB file. How can I achieve this function? I can't switch the camera. Thank you.

I want to try on AR glasses with a front facing camera and load a remote GLB file. How can I achieve this function? I can't switch the camera. Thank you.

did you find anything??


 Takes upwards of 10 or more mins. This is about 5x less if built directly on the same Mac.
Need to investigate what’s different. Seems like a recent regression.

I do not think this is an issue anymore.

I do not think this is an issue anymore.

It's still an issue; it's just that builds are so much faster in general that the docker slowdown is not as painful....


Ensure that ECP low-level modular arithmetic operates on statically sized MPIs

Dependency: Based on #5377.
Context: This PR is part of an ongoing effort to (a) reduce the number of heap allocations in the ECP module, and (b) prepare the ECP module for the introduction of curve-specific optimized modular arithmetic subroutines. #5377 takes a first step in this direction by (1) wrapping all low-level modular arithmetic by macros for ease of modification, (2) reducing the number of local MPIs, and, thereby, the number of heap allocations.
This PR refines the ECP modular arithmetic macros to compute intermediate results in a single double-width temporary, while the output remains standard-size provided the inputs are. In order to guarantee standard-sized inputs, this PR (a) modifies ECP group constants to be of standard size, (b) introduces EC point and MPI initialization macros which grow MPIs to standard size after initialization, (c) convert arguments to public API, the size of which we do not control, to standard size before passing them on to lower level routines. Overall, this establishes the desired property that the ECP modular arithmetic macros are only ever invoked with standard-sized MPIs.

 This is not intended nor expected, and needs to be analyzed.

Current code size impact compared to development (GCC 8.3.1, M0+, -Os)
library/ecp.o, 10226, 9406, 820, 8.72%
library/ecp_curves.o, 37684, 38192, -508, -1.33%

Speed, heap usage and heap allocations:
  ECDHE-secp256r1          :     457 full handshake/s (dev:399)  3856 heap bytes (dev:4496),    307 allocs (dev: 10937)

CI failing because of API/ABI checker only (an internal field has been added to mbedtls_ecp_group).

Rebased on top of development.

It makes more sense to directly opening a PR introducing the internal ECP interface, if that's what the team wants. Closing this PR.


docs: initial overview docs for button - dialog

Initial overview docs for button, button-toggle, card, checkbox, and dialog. Will need more examples added later.
cc @topherfangio @DevVersion if you want to do something similar for your components

@jelbourn Yeah I will do the docs for the slide-toggle and toolbar.

Good catches- comments addressed.

lgtm

This had an funny commit in snackbar-ref that is breaking the tests. Check out #2298 for the removal of the line.


Migrate to Coco

Fixes #1
Coco implements an epoch GC which calls destructors - this therefore shouldn't leak memory, and is properly lock-free for reads.
See crossbeam-rs/crossbeam#134 for some discussion of Coco's epoch GC.

Work from coco is currently in the process of being merged into crossbeam, so in the foreseeable future this crate should be able to use Atomic with destructors.


Write a blog post related to Ballerina security

Description:
For the Ballerina marketing rotation, we need to write a blog post related to Ballerina security.

Published the blog:
https://medium.com/@ldclakmal/microservices-security-with-ballerina-e9d430f05373


import error of peewee-async

/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/peewee_async.py in ()
753 ###################
754
--> 755 RESULTS_NAIVE = peewee.RESULTS_NAIVE
756 RESULTS_MODELS = peewee.RESULTS_MODELS
757 RESULTS_TUPLES = peewee.RESULTS_TUPLES
AttributeError: module 'peewee' has no attribute 'RESULTS_NAIVE'
I'm puzzled by the basic usage of peewee-async.Can you help me about this?

Recently have got the issue, while was writing an custom integration plugin for Sanic Framework with Peewee ORM.
@solomn1991 The following error
AttributeError: module 'peewee' has no attribute 'RESULTS_NAIVE'

you're getting because the latest Peewee ORM releases isn't compatible with current state of this package. After some tries, I've figured out that this package will work good with 2.* releases. Therefore, in the requirements.txt file just replace this dependency on something like peewee==2.10.2
But yeah, it will be great if this library will be updated relatively to the latest Peewee ORM releases

Thank you very much.Will the peewee_async be compatible with peewee in the future?