[VSCode Extension] UI enhancements

Generate code with user selected text only
Add right-click menus, "Generate Inline Code Completion" and "Generate Inline Code Completion In New Tab"

build_jenkins


Branch 2.3

Why I'm doing:
merge all the docs from docs.zh-cn into this repo, and keep all the commits
What I'm doing:
merge all the docs from docs.zh-cn into this repo
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.7 out of 8 committers have signed the CLA.:white_check_mark: hellolilyliuyi:white_check_mark: amber-create:white_check_mark: evelynzhaojie:white_check_mark: nshangyiming:white_check_mark: EsoragotoSpirit:white_check_mark: DanRoscigno:white_check_mark: jaogoy:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


Replace shelling out with kubernetes proxy

The conduit dashboard command asychronously shells out and runs "kubectl
proxy".
This change replaces the shelling out with calls to kubernetes proxy
APIs. It also allows us to enable race detection in our go tests, as the
shell out code tests did not pass race detection.
Fixes #173
Signed-off-by: Andrew Seigner<EMAIL_ADDRESS>

Thanks for looking at the initial feedback ✨  I'm testing this on my machine and will report results soon

@pcalcado i've filed #258 to track handling those error scenarios. i'm going to merge this as it's quite a big dependency change.


Create a card component using bootstrap classes.

Sample Output:

@Harikarthyk this one is done right?


Omero scripts

Hi Robert @haesleinhuepf , hi Johannes @jo-mueller ,
As previously discussed, I wrote this blog post to explain how to run an DL omero script, in this case a stardist 2D pretrained model. Could you please review it?
I wrote as if a broad audience could read this. Let me know if I should cut off the beginning for example.
Also, Robert @haesleinhuepf, it makes sense to add brief description of our server, doesn't it? I left some bold text to be edited.
Best,
Marcelo

Hi @zoccoler ,
I get an error when I try to log onto the omero server with the client I installed:

According to this issue  on image.sc, this could be due to missmatching Omero version on the server/client side - do you knwo which Omero version is running on the server?

Hi Johannes,
That's unfortunate. Here are the versions from Client and Server. Try using Insight 5.6.2.
Server version: 5.6.3
Client version: 5.6.2
os_version: 10.0
java_version: 1.8.0_275
os_arch: amd64
os_name: Windows 10

Best,
Marcelo

Strange - I'm receiving the same error for 5.6.2:

I do have it configured correctly, right?

My bad, with Omero Insight, the address is slightly different. I fixed the text.
Use this one : omero-int.biotec.tu-dresden.de

Use this one : omero-int.biotec.tu-dresden.de

This worked, thanks!

Also: All of the tutorial worked for me 💯
Maybe a small suggestion: Could you add a brief section on how to import data to the server space? When I logged on, I first had to upload some data to be processed by the scripts.

I think it would make sense to document the usage of the omero server via the browser. I think that's the default use-case. Only a minority of users will have the client installed. Would that be possible Marcelo @zoccoler ?

Could you add a brief section on how to import data to the server space?

@jo-mueller , I don't fully understand this, I pointed a link to the tutorial from omero where they show how to import data. I think it is well described there and I didn't want to replicate that part. Is that what you mean or something else?
@haesleinhuepf , it makes sense, I will replace the "running scripts" part by a web interface fashion, but I think you need either the application or the command line to import data. The options are presented here: https://omero-guides.readthedocs.io/en/latest/upload/docs/import.html

I changed to the web version, but import data is still done with Omero Insight and left as an external tutorial.

Talking to @jo-mueller Johannes today, it looked like a good idea to briefly enumerate first the possible ways to access the server, making it clear why we need the application at least to import data.
So I added a new section right in the beginning.
It looks good to me! What do you guys think?

Awesome, thanks Marcelo @zoccoler !


Add a aggregate_to_python method to BaseField, which allows customization of the data returned by QuerySet.sum and QuerySet.average

I noticed that you cannot easily change the datatype and/or actual data returned by queryset.sum(), this is sometimes useful when writing a BaseField subclass for things like Currency.
I added a "aggregate_to_python" method to BaseField. Any data returned by QuerySet.sum or QuerySet.average is passed to the field's aggregate_to_python method before being returned.
I also added a few lines to mongoengine/tests/queryset.py that ensures the proper behaviour for custom fields with a aggregate_to_python method.

Maybe this should be in the dev branch? Not to sure about this...

Closing.. will re-open to merge into dev instead.


Incoming NFT transfers

In order to display incoming ERC-721 transfers we need to adapt the transactions endpoint or have a seperate endpoint for incoming NFT transfers.

I can do it both ways, what do you think @rmeissner

yes, and maybe add a filter to allow filtering only incoming or only outgoing

yes, and maybe add a filter to allow filtering only incoming or only outgoing

It will be addressed on #80

I added tokenId to the endpoint for ERC721 transfers and type to make it easier for the frontend to see what kind of tx is each one

Example of the endpoint:
[
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-20T13:56:48Z",
blockNumber: 6170568,
transactionHash: "0xc03d6c84df51a36b50586200fcd3fe387bbc202ab0216d05893b59aff5eaa7c9",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "14",
tokenAddress: "0xa0b73b304F0BA1da5A0A80624747036B274Aca40",
from: "0x9913B9180C20C6b0F21B6480c84422F6ebc4B808"
},
{
type: "ERC20_TRANSFER",
executionDate: "2020-03-20T13:50:03Z",
blockNumber: 6170541,
transactionHash: "0xd5abcda89a7a943c5460dbe0f3e864c69e2f7ce63d205f47016e35d4787f9c4c",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "1025141000",
tokenId: null,
tokenAddress: "0x0014F450B8Ae7708593F4A46F8fa6E5D50620F96",
from: "0x9913B9180C20C6b0F21B6480c84422F6ebc4B808"
},
{
type: "ERC20_TRANSFER",
executionDate: "2020-03-20T13:45:03Z",
blockNumber: 6170521,
transactionHash: "0x6677f8fdd215cfcb58dfa497e387a1ede7ca405bb5f6cd58ecc5c99cb6d2a722",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "1000000000",
tokenId: null,
tokenAddress: "0x6D7F0754FFeb405d23C51CE938289d4835bE3b14",
from: "0x9913B9180C20C6b0F21B6480c84422F6ebc4B808"
},
{
type: "ERC20_TRANSFER",
executionDate: "2020-03-20T13:37:03Z",
blockNumber: 6170489,
transactionHash: "0x1912829b3f3dd4c28a3350e61957c6a78899ae2835d83a7e987281437553b239",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "1000000000000000000",
tokenId: null,
tokenAddress: "0x5592EC0cfb4dbc12D3aB100b257153436a1f0FEa",
from: "0x9913B9180C20C6b0F21B6480c84422F6ebc4B808"
},
{
type: "ERC20_TRANSFER",
executionDate: "2020-03-20T13:35:48Z",
blockNumber: 6170484,
transactionHash: "0xb479606951d28515591e4845df3039781ca425102989d60b84887448853fad32",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "30000000000000000",
tokenId: null,
tokenAddress: "0xc778417E063141139Fce010982780140Aa0cD5Ab",
from: "0x9913B9180C20C6b0F21B6480c84422F6ebc4B808"
},
{
type: "ERC20_TRANSFER",
executionDate: "2020-03-20T13:28:33Z",
blockNumber: 6170455,
transactionHash: "0xc2607b1ea1e7cf5bccf3532950f65db059d6e916dc0ccb1187a49d7d7e227297",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "100000000000000000",
tokenId: null,
tokenAddress: "0xc778417E063141139Fce010982780140Aa0cD5Ab",
from: "0x9913B9180C20C6b0F21B6480c84422F6ebc4B808"
},
{
type: "ERC20_TRANSFER",
executionDate: "2020-03-20T13:21:03Z",
blockNumber: 6170425,
transactionHash: "0x59503f82486be12f38c2142100c1e16e8ebdb4e4cfaffd67977086d6de3da13f",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "100000000000000000000",
tokenId: null,
tokenAddress: "0x5592EC0cfb4dbc12D3aB100b257153436a1f0FEa",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC20_TRANSFER",
executionDate: "2020-03-20T13:18:33Z",
blockNumber: 6170415,
transactionHash: "0x704d1feff147e46a398e01329879bb853122258f5bc4e23fbd88937ca9a54ece",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "500000000000000000",
tokenId: null,
tokenAddress: "0xc778417E063141139Fce010982780140Aa0cD5Ab",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-18T20:11:50Z",
blockNumber: 6160549,
transactionHash: "0x357fd69e21c7a850a0b9e656d2623008eb30191a814f000d2a76cdc4ba998c94",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "10",
tokenAddress: "0xBD5603813416b9bED6f5ED2E9B858BA19a4b8E29",
from: "0x6a3eC06886aE5F7a1c019C524021E9e079FF9c45"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-18T19:21:34Z",
blockNumber: 6160348,
transactionHash: "0x8679a1b46841b9d9c8d6130ae1dac182b6ce67d1c47217f9aa81893b614021ad",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "19",
tokenAddress: "0x2dfD872205A94308E5CeF193DCd5E2060B9a128B",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-16T17:48:54Z",
blockNumber: 6148462,
transactionHash: "0x9484be33cded4fa1988315853ddc7ae2d79d6d8cb00f8e75e73126b4255b4c47",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "689",
tokenAddress: "0x1571D1A3e1F09fC5eC2A9fa91E5069c1e50a900F",
from: "0x9913B9180C20C6b0F21B6480c84422F6ebc4B808"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T21:04:36Z",
blockNumber: 6127000,
transactionHash: "0x99acadf0805d931bd9412baf95287b915ad8082eb30e1edb5b823a1786680da8",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "6544",
tokenAddress: "0x16baF0dE678E52367adC69fD067E5eDd1D33e3bF",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T21:04:21Z",
blockNumber: 6126999,
transactionHash: "0x6ca05785aef6eb71c759f4c3f872900a7d9e75391a9c9c169dbd0936bbd2f04b",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "6546",
tokenAddress: "0x16baF0dE678E52367adC69fD067E5eDd1D33e3bF",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T21:03:36Z",
blockNumber: 6126996,
transactionHash: "0xb1953b627ba0327d7a4bf7a8c15030a2da94a9eba1fa2e772f7abc8a25fd4ba7",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "1",
tokenAddress: "0xE6431B6FCBCd8d41b09819115D189aC8e8DE3287",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T21:03:21Z",
blockNumber: 6126995,
transactionHash: "0xee9882e1afe14b73b906bd2572ab4fe08a2ac0a28973167c9db4de8ba5b6bb90",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "689",
tokenAddress: "0x1571D1A3e1F09fC5eC2A9fa91E5069c1e50a900F",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T21:03:06Z",
blockNumber: 6126994,
transactionHash: "0x4f2aa7cd8dbfbad46e2f87f6a3cff03ac99415b1d42e5dcc2dba75108d01fd0a",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "2159",
tokenAddress: "0x16baF0dE678E52367adC69fD067E5eDd1D33e3bF",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T21:02:51Z",
blockNumber: 6126993,
transactionHash: "0x5a9d405dfe010f5fbec3df23575ec800c81cf3e78da41f94af5d94a47f513255",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "5252",
tokenAddress: "0x16baF0dE678E52367adC69fD067E5eDd1D33e3bF",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T21:02:51Z",
blockNumber: 6126993,
transactionHash: "0x20cff1e92e13bef1d25f477d623caa301012ff04a2682834bfe6b81f7d3febdc",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "6557",
tokenAddress: "0x16baF0dE678E52367adC69fD067E5eDd1D33e3bF",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T20:54:34Z",
blockNumber: 6126960,
transactionHash: "0xea9ad6bafb2338617d70417ad6329aed9dd2d125e93cae2b730e9ecda7667f70",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "808",
tokenAddress: "0x1571D1A3e1F09fC5eC2A9fa91E5069c1e50a900F",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T20:51:33Z",
blockNumber: 6126948,
transactionHash: "0x2ae43f21ccdfe54fe46518c30b9c44efb91aaa2ad4c8a754ccf7bc22514ff7be",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "1",
tokenAddress: "0x8aC244a9C70624Aa5936De042AE950F8284cd85c",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T20:51:18Z",
blockNumber: 6126947,
transactionHash: "0xe35189e200835106e4567a5c9c3de8691ff155b03f650662dfb1676e2b961abe",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "11",
tokenAddress: "0x8aC244a9C70624Aa5936De042AE950F8284cd85c",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-12T19:20:08Z",
blockNumber: 6126584,
transactionHash: "0x2fc7e8872b4089c9c257003d933f9bec20180176feb3543f5b9e1a6e6907f308",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "81",
tokenAddress: "0x247f9c2Da9871b6AA8ecc030679c6135b5cDeeBb",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-11T17:46:31Z",
blockNumber: 6120474,
transactionHash: "0x8d0834b5b7aa85ab763996029ff0432ee2b48bfb82f5d493ee83f9bbe477d522",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "20",
tokenAddress: "0x2dfD872205A94308E5CeF193DCd5E2060B9a128B",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-03T12:57:02Z",
blockNumber: 6073286,
transactionHash: "0x3ca516b1a4d175428cb50586391562ad2476e9eb5e6e5bed58dce453059a8b1f",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "80",
tokenAddress: "0x247f9c2Da9871b6AA8ecc030679c6135b5cDeeBb",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-03T12:57:02Z",
blockNumber: 6073286,
transactionHash: "0x3ca516b1a4d175428cb50586391562ad2476e9eb5e6e5bed58dce453059a8b1f",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "599",
tokenAddress: "0x1571D1A3e1F09fC5eC2A9fa91E5069c1e50a900F",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-03-03T12:51:32Z",
blockNumber: 6073264,
transactionHash: "0xd668acbb90ee7b148cae3e27a99861a71d766f1a4d086c5d6ee61c891f7d9886",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "1",
tokenAddress: "0x0D967f8CA4D695e8E0b62C60054A826F0b34aE29",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-02-19T19:50:41Z",
blockNumber: 6000099,
transactionHash: "0x79105c357183f6253f69a81753662531d736de66df69cf1a01c126f867a4f53b",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "22",
tokenAddress: "0x2FDFfE9Cad323d3922195292E8806987B1fc1AAD",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-02-19T19:50:26Z",
blockNumber: 6000098,
transactionHash: "0x7402cbb8b218815c05d80a33b16c728e53bc68fd5e720bab10d76f8b38a30674",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "28",
tokenAddress: "0x8C64017cDD6B318f29610bB92AC9973eD1B85F44",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-02-19T19:50:11Z",
blockNumber: 6000097,
transactionHash: "0x747e672286455871295e856ad4befcc842889dd2e0f2a52c6a037d5811020c94",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "73350453981638397229828480902275940391628533349614653130397882891258950638056",
tokenAddress: "0x57f1887a8BF19b14fC0dF6Fd9B2acc9Af147eA85",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-02-19T19:49:56Z",
blockNumber: 6000096,
transactionHash: "0xf547363f8229e878dc5c77f4fe206609e332b216f1c700b9fe21098f9248c9b5",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "1162",
tokenAddress: "0x16baF0dE678E52367adC69fD067E5eDd1D33e3bF",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC721_TRANSFER",
executionDate: "2020-02-19T19:47:26Z",
blockNumber: 6000086,
transactionHash: "0xe53c46d95c49a67ab8650c7fd455a94a7b3e8fbacb6f74aa471d1b98778ac8a6",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: null,
tokenId: "1169",
tokenAddress: "0x16baF0dE678E52367adC69fD067E5eDd1D33e3bF",
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ETHER_TRANSFER",
executionDate: "2020-01-15T19:27:25Z",
blockNumber: 5798437,
transactionHash: "0xfdfe659c8d49b38165260060ebb7861eafe5d5f79ea2886c108aed495242ef9e",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "1000000000000000",
tokenId: null,
tokenAddress: null,
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ETHER_TRANSFER",
executionDate: "2020-01-15T14:05:40Z",
blockNumber: 5797150,
transactionHash: "0x10cb483f33f76da8b64df6b708f55046ce450c1defc419f5028dc1d1d117db8c",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "1000000000000000",
tokenId: null,
tokenAddress: null,
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
},
{
type: "ERC20_TRANSFER",
executionDate: "2020-01-09T18:37:00Z",
blockNumber: 5763689,
transactionHash: "0x3da240884812901921007bd29900075265d7041ae170877adc33304f39fb2aa6",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "100000000000000000000",
tokenId: null,
tokenAddress: "0x01BE23585060835E02B77ef475b0Cc51aA1e0709",
from: "0xa7a82DD06901F29aB14AF63faF3358AD101724A8"
},
{
type: "ETHER_TRANSFER",
executionDate: "2020-01-02T17:58:18Z",
blockNumber: 5723235,
transactionHash: "0xc1a9da7b6d7a82e8993b9b1ca4c40b10fe9df7ec6774e7e44e55bb7f7406d654",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "100000000000000",
tokenId: null,
tokenAddress: null,
from: "0x19433c47bF16f0D6E14Ff68ec4f5fafA2d9C8756"
},
{
type: "ETHER_TRANSFER",
executionDate: "2020-01-02T14:26:01Z",
blockNumber: 5722386,
transactionHash: "0xfe1f488b112a278214ab2d050b0cc0c0f5f628ea1d3ac2d65cf98ead7df039d3",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "100000000000000",
tokenId: null,
tokenAddress: null,
from: "0x19433c47bF16f0D6E14Ff68ec4f5fafA2d9C8756"
},
{
type: "ETHER_TRANSFER",
executionDate: "2020-01-02T13:49:01Z",
blockNumber: 5722238,
transactionHash: "0xa469920af2bf50c30d8ade2bcac438f954a60c4ef409cd44f0cedd1b20217ee1",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "10000000000000000",
tokenId: null,
tokenAddress: null,
from: "0x19433c47bF16f0D6E14Ff68ec4f5fafA2d9C8756"
},
{
type: "ETHER_TRANSFER",
executionDate: "2019-12-18T20:08:19Z",
blockNumber: 5637361,
transactionHash: "0x51c0f5d90077936bcd4cfb3254b9153af7600a323f1f1bda5f9114868e8730b9",
to: "0x441E604Ad49602c0B9C0B08D0781eCF96740786a",
value: "1000000000000000000",
tokenId: null,
tokenAddress: null,
from: "0x0E24B6e3BefF0b44b773F068343Bc2CB56cB3769"
}
]


Presenting Biblographies in Academic

I would like to know if there is an XML converter to hugo content. I have custom bibliographies, which I will continue to manage in Endnote, but if I could drop the xml file in the data folder and have hugo convert it to a bibliography in academic that would be awesome! I have also been wondering if it is more the Hugo way to use bibJSON and something like: https://www.npmjs.com/package/citation-js or https://github.com/Juris-M/citeproc-js/tree/master/demo Anyway I heard that some of you also use bibtex. I read there was a python script of some kind too. Any ideas on how to best approach the management of this content would be much appreciated.

#146 attempts to address bibliography import/sync. I'll try to find time this weekend to make an initial release. The first version is written in Python (which comes pre-installed on many computers and is fairly common in academia). It may be ported to Go at some stage, so that it becomes a fully stand-alone binary with no dependencies - like Hugo itself. Those JS libs look interesting, but it's unlikely Node will be used due to a number of reasons.


Lokalise: Translations update

This pull request was initiated by Lokalise (user Tian) at 2019-06-22 02:13:05

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add more context Information to OSM Notes

Is your feature request related to a problem? Please describe.
OSM Notes created with Wheelmaps are often quite short and ambiguous. Like "Doesn’t exist anymore" in https://www.openstreetmap.org/note/3675107 or https://www.openstreetmap.org/note/3675085. For the later I can't tell which OSM Node the Note is refering to.
Describe the solution you'd like
It would be good to automatically add context information to the notes. Similar to whow it is done in Organic Maps or StreetComplete. Mentioning Wheelmap as the editor would be good as well.
Organic Maps: https://www.openstreetmap.org/note/3782642
StreetComplete: https://www.openstreetmap.org/note/3769719

Thank your for your Email. I will be out of office until August 14th.
If you have any urgent requests, please contact @.***
all the best
Rainer


Resolver errors should include version requirements

Currently if the resolver fails the error messages give lots of information on the paths that caused the problems, like:
https://github.com/rust-lang/cargo/blob/0b530c30867da26a4b59146f490c9f1d5377c20a/tests/testsuite/build.rs#L1356-L1358
It would be nice to have the vershone requirements like: (wording needs improvement)
  previously selected package `bad v1.0.0`
    ... which is depended on by `bar v0.1.0` which requires `bad: "=1.0.0"`
    ... which is depended on by `incompatible_dependencies v0.0.1 ([..])` which requires `bar: "0.1.0"`

The data is easily available thanks to #5428 we just need to get it into the correct place, and find good wording. We almost had this working in #5402 before it bitroted.
I am willing to mentor someone on getting this done. It may be a good place to start looking at the resolver without having to stare into the void at its core. If it would be useful I can rebase #5452 so that only the wording is left.
cc @necaris would you be interested?

Duplicate of #6199


Changed Clear-DscLcmConfiguration to Public

Changed

Added LICENSE (fixes Issue #41).
Added standard badges to README.MD (fixes Issue #43).

Changed

Changed module manifest to include Tags, ProjectUri, LicenseUri, Logo
and changed AliasesToExport to empty (fixes Issue #42).
Changed Clear-DscLcmConfiguration to a public function so it can be called
directly by resource modules (fixes Issue #40).
Updated CI triggers to run on PRs against master branch and also run
against all branches.

Removed

Removed Deploy.PSDeploy.ps1 because it is not used (fixes Issue #44).
Removed commented out code from DscResource.Test.psm1
file (fixes Issue #45).

This change is

When you merge this, add something of this \s?(add|feature|minor) in the squash description so it raises minor version? I forgot that when I merged the previous PR.

Doh! I missed this comment! :(

We learn by the mistakes :p We fix that on the next merge (squash) 😄
Do you release a new version?

I recommend doing this when you create your new branch. If you will add a feature, call the branch f/.
If it's a fix, call it fix/

I had a commit starting with "Added" anyway. So it was OK this time.

No biggie but the test for that function should probably be moved to tests/Unit/Public/ as well (it's purely for consistency sake and making it easier on humans).

I did that in a subsequent PR (the one where I added the new test type). :)


Workspace - Xero / QBO setup page closes on the first try after creating a workspace

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Issue found when validating #41415
Version Number: 1.4.70-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:

Log in with a new expensifail account
Create a workspace
Enable "Accounting" on the WS settings page
Navigate to "Accounting"
Tap on the "Set up" button next to Xero

Expected Result:
Xero setup page shouldn't close.
Actual Result:
After a brief loading, Xero setup page closes on the first try after creating a workspace. It isn't closing if opened again. Affects Xero and Quickbooks too.
On prod, I'm getting a Hmm it's not here error after the "Set up" button and loading.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/38435837/0af31fa2-cd63-411d-bfbb-51a9158ff724
https://github.com/Expensify/App/assets/38435837/470f8fb6-771b-4119-a80f-04cbaf075db4

View all open jobs on GitHub

@adelekennedy FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

I'm not able to reproduce at the moment

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

I think this is fixed - when I follow the steps the xero login page stays steady for me - closing


Travis CI - linter and current Node.js LTS

You need to enable Travis for this repo here
Tests are currently red, but we need to start somehow 😉

Finally somebody got it to work:-)!
Thanks @igloczek, I’ll finalize it as I get to my computer

Travis enabled, merging


Validator performance in /metrics

What feature is it?
I would like to get validator performance information in /metrics. Pretty much everything that the validator keep track for internally, like number of peers, votes, attestation, and all other related data.
What problem does this feature solve?
Resolve: Impossible to keep track of the validator pods performance in our Kubernetes cluster using the /metrics endpoint directly.
Additional description
No response
This is not a duplicated feature request or new worker proposal

[X] I have searched existing issues to ensure this feature has not already been requested and this is not a New Worker.

There’s a way to check the node status at https://explorer.rss3.io/nodes/info. (See: https://docs.rss3.io/guide/for-node-operators/view-node-status). However, it only provides general information about the node API. We can certainly add more details about the pod itself! /cc @pseudoyu


Patch for YARN-6492. Generate queue metrics for each partition.

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

There is a conflict in QueueMetrics.java I have resolved, please carefully review QueueMetrics.java class
QueueMetricsForCustomResources.java is copied from branch-3.2


Using simple ITK ReadImage function under win10

Hi,
I am trying to open MRI documents  (.raw/.mhd) with simpleITK under win10(import) (64-bit) and  Ubuntu-derivate (64-bit). I tried different SimpleITK versions on Python 3.6 and 3.5(mainly). I installed them with conda and also use conda to create a virtual environment. When I want to open the MRIs with ReadImage, I always get the error message, that the file does not exists. But I tested existence and reading rights beforehand. Hence, if the file did nor exists, the ReadImage function would not be called.
I do not get the error on the Linux machine. In fact, all is working perfectly there. But windows functional is vital for me. I hope, that we can work that out!

To effectively help you with the problem we need more details with respect to the error (please cut and paste the complete error message).
Given that you only encountered the issue on windows it could be something with the path to the file, I am guessing here:

path length too long.
non ascii characters in path
spaces in the path
...

Please provide more information or let us know if your issue is resolved.

Thanks. That hint helped a lot!
I tested a bit on. It was the problem with the non ascii characters. Spaces have been "accepted".


[FEATURE] Use waitUntil in all tests vs thread.sleep

Currently in many of the tests for the Alerting plugin, we have thread.sleep to wait for background processes to complete for us to validate the tests. These should be replaced with OpenSearchTestCase.waitUntil

Hi, I would like to work on this issue.


MSAL sample

The doc currently only refers to ADAL. When are you going to add information for MSAL as well? This also applies to https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/application-proxy-configure-native-client-application

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

ID: b1951bcd-ef2d-2f76-a7aa-d3a53991e881
Version Independent ID: b8758151-424f-5a99-b8ab-c7cd31bb0ac7
Content: Access on-premises APIs with Azure AD Application Proxy
Content Source: articles/active-directory/manage-apps/application-proxy-secure-api-access.md
Service: active-directory
Sub-service: app-mgmt
GitHub Login: @jeevanbisht
Microsoft Alias: celested

@Skorfulose
Thanks for your feedback! We will investigate and update as appropriate.

Thanks! Your feedback has been shared with the content author.

Hi @Skorfulose, we've reached out to the product team and are working on including an MSAL sample. Just wanted to let you know we're actively tracking this internally, so for now we'll close this issue and update the article as soon as it's ready.
#please-close


Remove beneficial ownership

@jpmckinney I'm not sure if we should rename master to 1.1 and have 1.2 as a separate branch or we can merge this on master directly

We can merge on master. The Beneficial Owners extension is for 1.1 after all.

@yolile You'll need to add an exception here: https://github.com/open-contracting/standard-maintenance-scripts/blob/main/tests/test_readme.py#L177-L197


grafana: 6.5.1 -> 6.5.2

Motivation for this change
New patch release: https://github.com/grafana/grafana/releases/tag/v6.5.2
Things done

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

[x] NixOS (x86_64-linux & aarch64-linux)
[ ] macOS
[ ] other Linux distributions

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

@GrahamcOfBorg test grafana

before backporting this, see #74498

backported in ad1d9e6cb1898106d6c082c1b27de25170ccb0e3


Cython Compile Error ' Converting to Python object not allowed without gil' during installation

Hi,
I am facing issues whilst trying to install this library. I have Anaconda3, Python 3.7 and Cython 0.29.13.
pyross\deterministic.pyx:431:37: Converting to Python object not allowed without gil

Error compiling Cython file:
------------------------------------------------------------
...
            aa = bb*S[i]
            X[i]     = -aa
            X[i+M]   = aa - gI*I[i]

            for j in range(kk-1):
                X[i+(j+2)*M]   = gI*I[i+j*M] - gIa*I[i+(j+1)*M]
                                                 ^
------------------------------------------------------------

pyross\deterministic.pyx:431:50: Converting to Python object not allowed without gil
Traceback (most recent call last):
  File "setup.py", line 59, in <module>
    compiler_directives={"language_level": sys.version_info[0]},
  File "C:\Anaconda3\lib\site-packages\Cython\Build\Dependencies.py", line 1096, in cythonize
    cythonize_one(*args)
  File "C:\Anaconda3\lib\site-packages\Cython\Build\Dependencies.py", line 1219, in cythonize_one
    raise CompileError(None, pyx_file)
Cython.Compiler.Errors.CompileError: pyross\deterministic.pyx

@technOslerphile please can you pull the latest version and try again? Thanks

@rajeshrinet Thanks! It worked and the error mentioned in the original post is now solved.
However, I got two errors later which are:
1. vcvarsall.bat not found
2. cl.exe not found

I was able to fix these by installing Microsoft Visual Studio as mentioned here:
https://stackoverflow.com/questions/2817869/error-unable-to-find-vcvarsall-bat/60396650#60396650
Hope this will be useful to those who are having some issues in Windows.
By the way, your paper is phenomenal. I have never really found much COVID-19 mathematical model papers with this much clarity. Thank you very much!

@technOslerphile thanks very much for your kind words.
The solution for windows is very useful. I will share it with others. Thank you!


Incorrect typing in case statement with multiple conditions per clause

Correctly typed case (https://carc.in/#/r/1d0l):
def foo(foo)
  case foo
  when "foo"
    true
  else
    raise "Invalid operator"
  end
end

puts typeof(foo("foo")) # => Bool

Incorrectly typed case (https://carc.in/#/r/1d0m):
def foo(foo)
  case foo
  when "foo"
  when "bar"
    true
  else
    raise "Invalid operator"
  end
end

puts typeof(foo("foo")) # => (Bool | Nil)

Crystal 0.19.4

Are you sure you didn't mean case "foo", "bar" in the second example?

oh wow thats ugly

I think that the syntax for multiple conditions should become multiple adjacent "when" clauses. Using commas makes when foo, bar too close to when {foo, bar} (changing this frees up the former for special cases). When using long conditions it's ugly and you can't comment each clause:
case op
when "+", '+', :"+"
  Operator::Add
when "-", '-', :"-"
  Operator::Subtract
else
  raise "Invalid operator"
end

vs
case op
when "+"
when '+'
when :"+"
  Operator::Add
when "-"
when '-'
when :"-"
  Operator::Subtract
else
  raise "Invalid operator"
end

At the very least make adjacent when clauses an error, the example above looks like multiple conditions to me.

@RX14 👍, I've got bitten by the same perception once, although IMO it should be considered as alternative to listing conditions after comma.

Nope. This is very ugly in JavaScript, for example.
An empty when block is an empty block for the condition, not something that will skip to the next when block, skipping the when condition altogether, then skipping to next... until what? Without an explicit break, it's confusing. Do we mean to have a skip (like in JavaScript)? Or is it stopping whenever a block isn't empty? What about ignoring a value? A comment means an empty when, so... we'd need an explicit break, or require to specify nil so the block isn't empty? Or as you suggest, a blank line? But a blank line is an empty block... it's confusing, at best.
I, by far, prefer the Ruby syntax. You have a single when keyword followed by a comma separated list of possible conditions —that can be spanned on multiple lines— and a single block that applies. An empty block is merely an empty block, a there is nothing more. No confusion.

@ysbadden I prefer to think of it as grouping when statements when they are adjacent. There's no empty when block to be skipped. Likening it to c-based langauges with the explicit break condition (or explicit skip) is wrong.
As for ignoring values, I think that having an empty when condition without a blank line is simply incredibly confusing. Because there is no indent, no "space", it simply doesn't look empty, it looks grouped with the following when condition. For this reason, placing an empty line creates a visual break which make it clear the clauses are seperate. As an additional benefit, it also places a nice space for a comment to describe the reason you have this confusing, empty when clause.

I think the core of my argument is that adjacent whens look grouped, and that's confusing. Either we disallow that, or we change the grouping style to be adjacent when instead of ,. I believe that adjacent when is more powerful because it frees up syntax, and is much easier on the eyes than finding a ,.

Some people might prefer one option, some people might prefer the other. Both have pros and cons and each of us will have an opinion about which reason is stronger but in these cases there isn't always a clear winner.
Crystal inherits from Ruby most of the syntax and semantics, so it makes sense to copy the same rules here to avoid confusion. Ruby uses , to separate cases, so does Crystal.

I don't think we'll change the syntax of case/when, so I'm closing this.


Custom Sound sources play everywhere

I get LethalLib to fix up the audio mixers but they still play everywhere? I will try fixing them myself and see if it fixes it, otherwise will need to understand how audio attenuation works in the engine better.

fixed in 0.1.8


Kernel issue with librealsense with Ubuntu 14 on UP Board

Required Info

Camera Model
{ D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Linux (Ubuntu 14)

Kernel Version (Linux Only)
4.4.0-2-upboard

Platform
UP board

SDK Version
{ 2 }

Issue Description
I tried to run the script:
./scripts/patch-realsense-ubuntu-xenial.sh
but ended up getting this error:
sudo modprobe uvcvideo produces dmesg: uvc kernel module is not loaded
I think before running the script, I can actually detect have uvcvideo running fine showing in dmesg. Is there anyway to revert the patch or fix it through kernel support for 4.4.0-2-upboard (which is the latest support for ubuntu 14 on UP board)

[Realsense Customer Engineering Team Comment]
Hi @littlejohnyang
In addition to modify the patch, do you also consider to use Ubuntu 16.04 on the UP board? Then, you can try to install the uvcvideo modules provided by DKMS as below link.
https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md

I actually got it working now after reformat the whole PC and install from scratch again. What happened is that the ./scripts/patch-realsense-ubuntu-xenial.sh patch causes all the problem. So I can now get all the images without running that script. However, I am getting the following warning constantly even though everything is working fine:
Failed to read busnum/devnum. Device Path: /sys/bus/iio/devices/iio:device0
Anyone know how to solve the problem with this warning message?
Also from dmesg, I can see a message saying:
[16473.523394] uvcvideo: Unable to create debugfs 2-2 directory.
I'm not sure if this is going to be a problem. Otherwise it seems working fine except the constantly printed warning message.

[Realsense Customer Engineering Team Comment]
Hi @littlejohnyang,
Do you still use Ubuntu 14.04 + kernel 4.4.0-2? Suggest to have below patches for hid and camera formats, etc.
https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md
$ sudo apt-get install realsense-uvcvideo
Then, you can check if the warning message "Failed to read busnum/devnum" still there.

Somehow the realsense-uvcvideo isn't available for ubuntu14 I think. However, after a system reboot yesterday, the "Failed to read busnum/devnum" warning message disappeared now. However, it'll throw the following warning and error message despite the camera is still functioning correctly.
02/03 10:21:17,276 WARNING [140117030401792] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to installation chapter for details.
[ WARN] [1519946477.295799525]: Frame metadata isn't available! (frame_timestamp_domain = RS2_TIMESTAMP_DOMAIN_SYSTEM_TIME)
02/03 10:21:17,343 WARNING [140117006227200] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to installation chapter for details.
02/03 10:21:17,480 ERROR [140118019524544] (types.h:178) xioctl(VIDIOC_S_CTRL) failed Last Error: Numerical result out of range
[ WARN] [1519946477.482304720]: Reconfigure callback failed with exception xioctl(VIDIOC_S_CTRL) failed Last Error: Numerical result out of range:

[Realsense Customer Engineering Team Comment]
Hi @littlejohnyang
My configuration is Ubuntu 14.04.5 + kernel 4.4.0-31 + D410 on the UP board. There is no the warning/error messages.
Suggest to follow below instructions to install the required packages for Ubuntu 14.04 and build the librealsense 2.10.0.
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md
Once your librealsense build is done, you can innstall DKMS package without running the kernel patch script.
https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md
$ echo 'deb http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial main' | sudo tee /etc/apt/sources.list.d/realsense-public.list
$ sudo apt-key adv --keyserver keys.gnupg.net --recv-key 6F3EFCDE
$ sudo apt-get update
$ sudo apt-get install realsense-uvcvideo
$ reboot
After above update, you can run below command to see if uvcvideo driver is updated.
$ modinfo uvcvideo | grep ver
you should see 'version:  1.1.1.realsense-4.4.0'
Make sure above driver version is correct, then the app like rs-capture, realsense-viewer, etc should work normally without your warning/error messages.

Hi!
I also have a problem regarding this issue.
During the update process I get an error because my platform (armhf) is not supported by the patch. Is it perhaps in progress or it will not be officially supported?
Skipping acquire of configured file 'main/binary-armhf/Packages' as repository 'http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo xenial InRelease' doesn't support architecture 'armhf'

[Realsense Customer Engineering Team Comment]
Hi @hogyadenes
So far, the DKMS package doesn't support the ARM platform. which ARM platform do you use?
For Nvidia Jetson platform, need to modify the script "patch-realsense-ubuntu-xenial.sh" to patch.

Hi @littlejohnyang
Feel free to open a new issue if you need further assistance with patching


Doc of integration between bitbucket source connector and airbyte not found

Hello !
The docs about how to use bitbucket source connector within Airbyte is reaching “page not found “
Could you tell me how to integrate both or fix the docs ?

Yeah, we need to open a PR with Airbyte code repo to have it documented. @cjwooo is this the process?


Optimize performance of cancan_resource_class

No need to stringify all ancestors if InheritedResources is not even used in the project.

What about getting rid of it?

@coorasse what do you mean?

I was just wondering if we should get rid the support to InheritedResource since is not maintained anymore. I don't like to keep supporting libraries which are old and not maintained. But your PR is fine :+1:

Sounds like a good idea.

Any news on that? I have been doing some benchmarks with derailed_benchmarks and stackprof in one of our apps and, in some cases, this method accumulates 15% of CPU pct.
Thanks

Closed in favour of #370


Why the accuracy approarch to nearly 100% when I set the epoch_num = 200 in the CNN_baseline?

Why the accuracy approarch to nearly 100% when I set the epoch_num = 200 in the CNN_baseline?
Here is the result. csv, thank you so much for your explain!
9.76E+01 | 9.79E+01 | 9.76E+01 | 9.69E+01 | 9.74E+01
9.97E+01 | 9.98E+01 | 9.95E+01 | 1.00E+02 | 1.00E+02
9.76E+01 | 9.90E+01 | 9.88E+01 | 9.90E+01 | 9.93E+01
9.70E+01 | 9.74E+01 | 9.81E+01 | 9.88E+01 | 9.72E+01
9.97E+01 | 9.90E+01 | 9.88E+01 | 9.91E+01 | 9.84E+01
9.81E+01 | 9.81E+01 | 9.79E+01 | 9.72E+01 | 9.79E+01
9.97E+01 | 9.95E+01 | 9.97E+01 | 9.98E+01 | 9.95E+01
1.00E+02 | 9.98E+01 | 9.98E+01 | 9.98E+01 | 9.97E+01
9.70E+01 | 9.62E+01 | 9.69E+01 | 9.72E+01 | 9.64E+01
9.97E+01 | 9.97E+01 | 9.98E+01 | 9.98E+01 | 9.97E+01
9.36E+01 | 9.65E+01 | 9.48E+01 | 9.58E+01 | 9.53E+01
9.98E+01 | 9.93E+01 | 9.88E+01 | 9.98E+01 | 9.93E+01
9.93E+01 | 9.81E+01 | 9.84E+01 | 9.84E+01 | 9.79E+01
9.86E+01 | 9.79E+01 | 9.90E+01 | 9.88E+01 | 9.90E+01
9.76E+01 | 9.79E+01 | 9.72E+01 | 9.84E+01 | 9.79E+01
9.95E+01 | 1.00E+02 | 9.93E+01 | 9.98E+01 | 9.93E+01

Thank you very much for your interest in reproducing our code! Since the completion of this project has been some time ago, I may need some time to rerun these codes. I will finish reruning these codes within three days and investigate whether the baseline can indeed reach a level close to 100%. If it does, it will be very interesting.

Thank you for your replication and feedback. The reran code has been updated in the code repository. However, the result of "close to 100%" was not found. Our doubts and proof can be also found in the folder. Thank you again for your inquiry.


subject_alternative_names order will destroy/create even if no changes to script on apply only

This is very interesting and I didn't notice this until today.
When I created an aws_acm_certificate everything was fine. I didn't need to run apply on it again. Today, for reasons outside the scope of this issue, I ran another terraform apply to the same file with no changes made to it. To my surprise, it actually wanted to destroy the current cert and make a new one. All because the subject_alternative_names were in a different order. This is a bit concerning because the order of these did not change in the script. How the data was stored was not the order I had it in.
NOTE: this does not show anything if you run terraform plan
One would think, ok so perhaps just keep it in alphabetical order.. nope. The order seems to be whatever it wants. So it seems it's best to run terraform apply a second time afterwards and update your order in the script to match what is stored.
This cannot be expected behavior.
This is an area of concern because you would not expect this to happen without updating your script. Perhaps a note on the docs about this?
Example:
resource "aws_acm_certificate" "default" {
  domain_name       = "mydomain.com"
  validation_method = "DNS"

  subject_alternative_names = [
    "*.mydomain.com",
    "*.cdn.mydomain.com",
    "*.assets.cdn.mydomain.com"
  ]

  lifecycle {
    create_before_destroy = true
  }
}

Output is something like:
Terraform will perform the following actions:

  # aws_acm_certificate.default must be replaced
+/- resource "aws_acm_certificate" "default" {
      ~ arn                       = "arn:aws:acm:us-east-1:REMOVED:certificate/REMOVED" -> (known after apply)
        domain_name               = "ott.oly.cloud"
      ~ domain_validation_options = [REMOVED_AS_NOT_NECESSARY ] -> (known after apply)
      ~ id                        = "arn:aws:acm:us-east-1:REMOVED:certificate/REMOVED:REMOVED:certificate" -> (known after apply)
      ~ subject_alternative_names = [ # forces replacement
          + "*.mydomain.com",
            "*.cdn.mydomain.com",
            "*.assets.cdn.mydomain.com",
          - "*.mydomain.com",
        ]

      ~ validation_emails         = [] -> (known after apply)
        validation_method         = "DNS"
    }

Plan: 1 to add, 0 to change, 1 to destroy.

Looks directly related to https://github.com/terraform-providers/terraform-provider-aws/issues/8531

Looks like this problem have been solved
https://github.com/hashicorp/terraform-provider-aws/issues/8531#issuecomment-663562156
Would you be so kind to check if the module could be updated?

@SerhiiSokolov updated how?

@bryantbiggs I think it is related to #67 and #70 that are already on my short-list for review during this week.

ah ok 👍🏼


[SPARK-27778][PYTHON] Fix toPandas conversion of empty DataFrame with Arrow enabled

What changes were proposed in this pull request?
https://github.com/apache/spark/pull/22275 introduced a performance improvement where we send partitions out of order to python and then, as a last step, send the partition order as well.
However, if there are no partitions we will never send the partition order and we will get an "EofError" on the python side.
This PR fixes this by also sending the partition order if there are no partitions present.
How was this patch tested?
New unit test added.

Cherry-pick of https://github.com/apache/spark/pull/24650


Remove CustomEditText

Description (required)
Removes CustomEditText, simplifying DescriptionsAdapter and reducing potential for bugs in this key part of the upload flow.
Tests performed (required)
Tested 2.10.1-debug-remove-customedittext~e7ea3255c on Galaxy Nexus with API level 28.
Beta Commons Upload
Screenshots
No changes to the UI:

Upload page
Title dialog
Description dialog

Codecov Report

Merging #2640 into master will increase coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #2640      +/-   ##
=========================================
+ Coverage    2.77%   2.78%   +0.01%
=========================================
  Files         259     258       -1
  Lines       12373   12306      -67
  Branches     1117    1100      -17
=========================================
  Hits          343     343
+ Misses      12003   11936      -67
  Partials       27      27

Impacted Files
Coverage Δ

...r/free/nrw/commons/upload/DescriptionsAdapter.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Works perfectly fine @domdomegg , thanks!


Syntax error in array [,] parsed as [null]

Hello,
I'm using js-yaml in a code editor that supports json and yaml user input and then transforms the content (if it is valid) into javascript objects for further manipulation.
I've encountered the following bug: If an array contains an extra comma ,, instead of throwing an exception for invalid yaml or json, the parser transforms the value into null. Although I include several other options, this is the simplest case in which the error occurs.
Code snippet:
var yaml = require('js-yaml');

var result = yaml.safeLoad('[,,]');

Expected:
YAMLException is thrown
Actual:
result === [null, null]

Seems to be a bug. libyaml-based parsers return error

http://yaml-online-parser.appspot.com/
http://ben-kiki.org/ypaste/

@dervus ?

Fixed in https://github.com/nodeca/js-yaml/commit/adfee179ba85e5a2d2023f010d586b7209fdb083 (currently in dev branch, gonna be released as js-yaml 4 later).


Gateway and Network functionalities

The PR introduces basic functionalities of Network and Gateway which will be used to implement other higher level APIs

TODO: test cases and tutorial of the API usage.

TODO: test cases and tutorial/docs for the API usage.

TODO: test cases and tutorial/docs for the API usage.

Will start working on this!

please rebase to the tip of master

@ryjones
The branch is already up to date!


Syntax Error in log.py

Hey, I installed the package but while importing it throws up the following error:
File "", line 1, in
File "/home/ece/anaconda2/envs/sameer27/lib/python2.7/site-packages/test_tube/init.py", line 6, in
from .log import Experiment
File "/home/ece/anaconda2/envs/sameer27/lib/python2.7/site-packages/test_tube/log.py", line 366
header = f'''###### {self.name}, version {self.version}\n---\n'''
^
SyntaxError: invalid syntax
Thanks

use python 3.6+


Legion Prof: Regression - Missing Profiler Output

Looks like we are missing profiler output. The profiling preamble containing metadata gets printed, the application executes and terminates normally, but no profiling info is actually provided. Tested with cgsolver example on master.
./cgsolver -hl:prof 1 -cat legion_prof -level 2

The problem is the Realm TASK_ID_PROCESSOR_SHUTDOWN tasks are not being called on all the Realm processors before Realm exits.

Actually it looks like the problem is that they are only being called on utility processors.  It would probably be best if they were still called on all processors, especially for the case where there are no utility processors.

Looks like b14f957129b4f8a9547c8195994a7b5a31247691 fixed it. Thanks!


Maintained? Cannot build source. Dependencies are very far out of date

Before you open an issue, please check if a similar issue already exists or has been closed before.
Expected behavior
I expect to be able to build this from source.  No new tags, no new releases are listed on the repo page, but there were merges of PR's such as #47 which is what I need
Actual behavior
~/D/vscode-mjml ❯❯❯ npm install

><EMAIL_ADDRESS>postinstall
> node ./node_modules/vscode/bin/install

Detected VS Code engine version: ^1.23.0
Found minimal version that qualifies engine range: 1.23.0
Fetching vscode.d.ts from: https://raw.githubusercontent.com/Microsoft/vscode/7c7da59c2333a1306c41e6e7b68d7f0caa7b3d45/src/vs/vscode.d.ts
Error installing vscode.d.ts: TypeError: Cannot set properties of null (setting 'Authorization')
npm ERR! code 1
npm ERR! path /Users/kross/Downloads/vscode-mjml
npm ERR! command failed
npm ERR! command sh -c node ./node_modules/vscode/bin/install

And checking the dependencies - they are very far out of date:

Steps to reproduce the problem

npm install

Screenshot / GIF
Please attach screenshot/gif if you consider them as helpful to understand/reproduce the issue.

Specifications

VS Code version: 1.92.2
MJML extension version: master 0ffe95568452713f3f9ae70c4465b5344f7fd560
Operating system and version: OSX 14.6.1

Other information
I'm confused, a recently merged PR, very old tags, very old releases, VERY old dependencies.  There was a mention in #47 about a release this week, but there are no other branches....confused.

I have now the ownership of the extension so I should be able to update the version "soon". But my time is really limited for MJML so I do my best to handle support + continue dev on those projects.

Thank you @iRyusa
I don't know vscode extensions, but I'll take a swing at updates and see if I can get you a PR that moves this forward a little.
It looks like this needs a vscode migration that is old enough, I had to use the wayback machine to find it!
http://web.archive.org/web/20210505205913/https://code.visualstudio.com/api/working-with-extensions/testing-extension#migrating-from-vscode
I'll see if I can get updates working.

PR pushed, changes were reasonably straightforward, but it needs reviewed due to may lack of experience in this area.
Now I'll see if I can run it!

Should be good now 👍


Make a spatialite jdbc connection

System information:

Operating system (distribution) and version : Windows 10 64x
DBeaver : Latest

Connection specification:

Database name and version : Spatialite 3 (SQLite extension spatiale

Describe your question:
How can I configure en SQLITE with module spatialite ou directly a Spatialite JDBC connector
This is related to #6830 #5960

This article should help you https://github.com/dbeaver/dbeaver/wiki/Database-drivers


Add an api coverage feature

I feel like we could greatly benefit from a coverage tool. The idea is to:

have a percentage of "covered" path, meaning that all possibles requests/responses were validated.
have a percentage of "covered" components, meaning that the object was seen at least once in the responses.

The goal would be to give a good idea of how much of the API is tested and therefore make it possible to identify and address weak spots.

How would you implement this?

I'm not sure. We need some pytest-cov equivalent of https://github.com/viclovsky/swagger-coverage, but now that I'm thinking about it, it might be completely unrelated to the schema validation done here.
The only extra information coming from this tester is the validity of the response, whereas coverage is simply a matter of identifying not tested code.

Yeah this sounds like a cool idea, but maybe one that would be better implemented as it's own complementary or standalone package. There would be very little overlap with the existing package internals here, unfortunately.
If you want to experiment and open a PR, I'm not necessarily opposed to a feature like this, depending on how it turns out - but I suspect you would need to essentially write the equivalent of a standalone package, inside drf-openapi-tester, which sounds suboptimal.


Update Xcode version check for macOS doctor

In turning on doctor support for macOS, I just used the existing Xcode logic as-is. Since the desktop template will be (and the current FDE proto-template is) Swift-only, and the versioning support for Swift is pretty strict and fast-moving in Xcode, desktop requires a newer version than is being checked for iOS.
The Xcode check needs to have two different version checks, and error messages that communicate that meeting just the lower one will allow iOS development but not macOS development.
(Alternately, we could have a policy that we set the minimum version to max(min iOS version, min macOS version) for simplicity, but that would potentially impact iOS developers unnecessarily—I'd be curious whether that's true in practice given app store SDK requirements.)

#41231 will avoid the need for adding separate checks for macOS vs iOS targets, which makes this much simpler. Closing in favor of that.


F# Compiler Office Hours by @dsyme

For those of you not on Twitter, just to mention that I'm doing a once-a-week F# compiler office hours.
The session for this week will start in 10 minutes, a couple of hours earlier than usual, it's normally at 5pm UK time on Thursdays (12noon US East Coast).  It's not every week.
It's held on the #compiler Slack channel of the F# Software Foundation -
I think you might need to join as a member before participating (it's free!) http://foundation.fsharp.org
Come along and ask me anything about the compiler.  We will do a separate sessions for the F# Language Design.

Office hours over. If you'd like to catch up on the discussion, it's here: https://fsharp.slack.com/archives/C05325FDM/p1518116485000274

Follow up: Today I'll be holding my first F# Language Design office hours, 5pm GMT (a bit  over two hours). One hour open-door to ask questions, discuss suggestions, RFCs for F# language and core libraries, other topics if time permits. For now we'll use #compiler channel of FSSF Slack https://fsharp.slack.com/messages/C05325FDM (unless we manage to get a public #langdesign channel created sooner)


Add docs on multi-tier load-based rebalancing

Fixes #11240

These updates mostly look good to me, but the thing to note is that we had to temporarily revert https://github.com/cockroachdb/cockroach/pull/65379 because it introduced a new regression over the previous implementation.
We're going to fix the regression and unrevert that patch soon, but this won't make it in until 21.2.2. With that in mind, I assume we want to hold off on merging this change?

this won't make it in until 21.2.2. With that in mind, I assume we want to hold off on merging this change?

Ah ok, didn't realize.  Yes, sounds good - will pause on this until v21.2.2


Isa-l.h should be included in windows

This is available now in the latest upstream. Make sure to update the conda package accordingly.

Fixed.


Create a new resource stack

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details
When running pulumi new ... or pulumi stack init, it would be helpful if this provider could create new empty stacks and manage the stack through this provider.

Hello there!
Would you please explain the use case for a resource like that? Like, why would like to create empty stacks?
Normally, anytime you want to create new resources, a stack is created as part of pulumi up, through pulumi CLI or deployments, or whichever way.
This provider is for Pulumi Cloud resources, while Stacks are a concept whether you're using Pulumi Cloud or not.

Chatted on slack, the intent is to enforce a naming pattern on stacks, by essentially "reserving" a stack name, then adding TeamStackPermissions to a specific team to work on it.


Can't change background color of the sheet

I can't change the background color of the sheet.
I tried:
[data-rsbs-root] {     background-color: blue !important; }
`
.background {
background-color: green !important;
}
<BottomSheet
className={'background'}
style={{background: 'green'}}

.....
`
Is there a way to change this?

@DoronTorangy how did you do this at the end?

@andyrobert3 I did it with scss like this and mount the classes based on my theme
Example:
.light-bottomsheet {
 // update whole overlay
  div[data-rsbs-overlay] {
    background-color: white;
  }
}

.dark-bottomsheet {
 // update whole overlay
  div[data-rsbs-overlay] {
    background-color: black;
   // This is for updating round pill like shape in header (dk what its' called lol
    div[data-rsbs-header]::before {
      background-color:  red;
    }
  }
}


don't run compress, koji_tag plugins for scratch source builds

OSBS-8041

Signed-off-by: Robert Cerven<EMAIL_ADDRESS>Maintainers will complete the following section:

[x] Commit messages are descriptive enough
[x] "Signed-off-by:" line is present in each commit
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[x] Changes to metadata also update the documentation for the metadata
[x] Pull request includes link to an osbs-docs PR for user documentation updates

rn not updated: fix for unreleased feature


feat: start with data default option added

Description
We recently delivered an experiment for onboarding revamp, where 50% of the new users would see onboarding flow (with 3 options of start with data, start from scratch and start from templates), this experiment proved to be useful and as a next phase of that, we decided to experiment with providing start with data option as default, so when a new user signs up, they will see start with data option by default. This PR addresses that experiment.
Notion doc: https://www.notion.so/Productize-Onboarding-revamp-c67bdce04fcb451b95690d2ea2ac60c3
PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

New Features

Introduced a new feature flag to control the default behavior for starting applications with data.

Enhancements

Updated the application creation flow to conditionally render options based on the new feature flag.

UI/UX

Added styling to center align and adjust padding for a component in the Schema View mode.

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true recreate=true

/build-deploy-preview skip-tests=true recreate=true

/ok-to-test<EMAIL_ADDRESS>

/build-deploy-preview skip-tests=true recreate=true

/ok-to-test<EMAIL_ADDRESS>

/ok-to-test<EMAIL_ADDRESS>


Swallow Content-Type when sent from server --> client

Currently we hand this up to the application, but since it's really "protocol stuff" it should be consumed in the core library.

I think this also broke the C++ tests: in test/cpp/end2end/async_end2end_test.cc:
EXPECT_EQ(static_cast<size_t>(2), server_initial_metadata.size());
Needs to become 3. I guess this test needs to go ?


Add push jobs to delivery-base

This PR adds push-jobs to the base Delivery cookbook.

Add push-jobs package attributes
Include push-jobs default recipe
Depends on push-jobs plus updated information
Add chefspecs for push-jobs and platform support
Add a .rubocop.yml

This PR has passed 'Verify' and is ready for review and approval!
Use: '@delivery approve' when code review is complete.

@afiune Since this is a publicly exposed community cookbook, please add the necessary Apache license information. Also make sure to work with @tas50 to ensure that it meets any criteria he has outlined for community cookbooks.

@tduffield understood! Thank you.

This PR has passed 'Verify' and is ready for review and approval!
Use: '@delivery approve' when code review is complete.

@delivery approve

Change: c2105602-c210-438e-98ab-eda77174dcbb approved by: @tduffield

This PR has passed 'Acceptance' and is ready to be delivered!
Use: '@delivery deliver' when validated in acceptance.

@delivery deliver
Salim Afiune — Solutions Engineer
917.716.0448 –<EMAIL_ADDRESS>– *my: *Linkedin
http://www.linkedin.com/in/afiune  Twitter http://www.twitter.com/afiune
CHEF
  CHEF.IO <http://www.chef.io/>

TM
chef.io http://www.chef.io/   Blog http://www.chef.io/blog/   Facebook
https://www.facebook.com/getchefdotcom   Twitter
https://twitter.com/chef   Youtube https://www.youtube.com/getchef
On Wed, Oct 7, 2015 at 9:35 AM, chef-delivery<EMAIL_ADDRESS>wrote:

This PR has passed 'Acceptance' and is ready to be delivered!
Use: '@delivery https://github.com/delivery deliver' when validated in
acceptance.
—
Reply to this email directly or view it on GitHub
https://github.com/chef-cookbooks/delivery-base/pull/3#issuecomment-146212823
.

Failed to unknown change: c2105602-c210-438e-98ab-eda77174dcbb
Delivery does not understand this command. @afiune

@
delivery deliver

@delivery deliver

Failed to unknown change: c2105602-c210-438e-98ab-eda77174dcbb
Delivery does not understand this command. @afiune

@delivery deliver

Change: c2105602-c210-438e-98ab-eda77174dcbb delivered by: @afiune

The only other thing I'd suggest is adding additional platform releases to the Kitchen config.  We should test on everything we claim it works on so Ubuntu 12.04/14.04 should be in the and CentOS 6.7 / 7.1

So many things.. I will work through them as I can. Thank you @tas50


CI on OS X

At the moment, our CI is *nix only. While OS X specific issues are relatively rare, and we typically find those only when someone reports a problem.
Thanks to Matthew, there is an OS X CI facility on TravisCI, https://github.com/MacPython/scipy-wheels
It however is only set up to build the master branch, and is meant to upload the build artefacts for consumption downstream --- neither of which is particularly suitable for troubleshooting.
We probably want something lightweight: either an entry in our .travis.yml so that we check each push of each PR, or a separate repo where we could trigger an OS X build when need arises.

I don't know of any CI services that allow OSX builds for free.

So @matthew-brett pays for running the build services for the whole scipy stack? Wow.

:) - the OSX builds are free too.   You can add OSX builds to the current .travis.yml matrix by using the os: osx setting.  See the scikit-image travis setup for an example:
https://github.com/scikit-image/scikit-image/blob/master/.travis.yml

I guess nothing stops us from adding an always on OSX target to travis
(or switching one of the current ones to osx).

Excellent! I wonder when they made that change.

The conda forge project use a travis and appveyor setup to make osx and windows conda packages and upload the artefacts.  Its definitely worth adding an OSX target, is there much headspace left on how much travis resource we can play with?

Yes. We have had issues with the runtime of the full test suite timing out, but I don't think there's an issue with adding more entries to the build matrix.

Shame we can't run windows CI tests as well.

CircleCI supplies free Windows builds, I believe.

CircleCI supplies free Windows builds, I believe.

no Fortran compiler .....

no Fortran compiler .....

Ah, right.
I think I recall someone saying they use a docker image on CircleCI in order to compile Fortran, but I can't recall at the moment who or where that was...

Closed by #7607


chore: remove unused closing tag from indexed_merkle_tree.mdx

Quick fix for some crud which seems to be there by accident.

Docs Preview
Hey there! 👋 You can check your preview at https://6657165ef3ad33a5b6e1e7b0--aztec-docs-dev.netlify.app

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.
| Metric |  |
| - |  |
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,452
9,440
9,476

l1_rollup_execution_gas
616,093
616,081
616,117

l2_block_processing_time_in_ms
1,285
4,795
9,537

l2_block_building_time_in_ms
45,576
180,946
361,813

l2_block_rollup_simulation_time_in_ms
45,398
180,311
360,549

l2_block_public_tx_process_time_in_ms
24,494
102,451 (-1%)
209,834

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
9,460 (+1%)
14,532 (+1%)

node_database_size_in_bytes
14,479,440
21,368,912

pxe_database_size_in_bytes
18,071
29,868

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4
16.9
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.606
0.520
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.5
76.3
246
478 (+1%)
928
1,841
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.496
0.470
0.446
0.445 (+1%)
0.440
0.439
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
58.1
113 (+1%)
355
703 (+1%)
1,384
2,757
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
106
208
692
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.503
0.504 (+1%)
0.482
0.482 (+1%)
0.479
0.479
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
62.7

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
107

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.556

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
84,050
665,267

Transaction size based on fee payment method
| Metric |  |
| - |  |


Remove package monero

Repo has been removed from github.

It was incomplete and I do not plan to continue developing it. Someone has contacted me about it and I have given them the source, so they may choose to add it again later.


Init client package

Figure out how to auto-generate an npm package from our graphql api and auto publish it to GitHub package registry

Closed by c5b34da411805e3c66349f68e178e569c3a3d882


Visual Studio

Can vs development and design support the use of basic controls in the toolbox like devexpress or vs controls, and drag the layout design of controls directly? I think this pattern reflects the power of vs.

Unfortunately this is not easy to implement, it needs integration with xaml compiler, ide, and core library its very complex to implement which is why it hasnt been done.
Secondary to that drag and drop doesnt produce good xaml, it tends to lead to everything being positioned with absolute offsets.

I would like to add that what is really needed is to increase the stability of the code completion and the design view. At the moment they fall off time to time and force the user to reboot the IDE or fix prj file. And on the top of it design view never starts up the first time.


OMIA Non-Human Animal Diseases

Address issue #5585

General comments:

maybe we need higher-level classification, especially for the disease with "type x" that are related to a gene. For example: MONDO:1010173, 'mucopolysaccharidosis IIID, non-human animal', should have a non-human disease parent that would be "mycopolysaccharidosis". That would bring all these diseases together
We might need extra grouping terms, for examples "kidney disease, non-human". We should review the classification, compare to the human diseases, and see if extra high-level classification could be created
The reasoner is not able to classify diseases based on taxons, so we should add the subclassOf "cat disease" (for example) manually.
Note that all of these could be done in a separate PR.

The most important thing to change in this PR is to remove the terms that are "grouping term by generic gene", which will eventually cause problem because we cannot define them with an axiom referring to a "non-species specific gene" (see comments in the files changed. Note that almost all comments are the same).

These terms have been added via multiple other PR. Closing this issue.


feature: clear the unnecessary file in api folder

there are 2 same util.sh file in director of  api/hack and hack

/kind feature

@hangscer8


Several cosmetic problems on SAML Login Flow page

Again related to #34, #35, #36

[ ] App doesn't want to use its space on the right on the SAML Flow card
[ ] I think we should globally call these "SAML Login Flows" instead of abbreviating to "SAML Flows"
[ ] I'd be tempted to come up with a different null styling for State and User Attributes. I think User Attributes is in a better place because it has curly braces showing there's nothing there, but I don't think it's always obvious that an empty gray box represents null for State. Especially because State tends to confuse people already.

Hi @Ned-oleary,
I’m interested in working on this issue. Could you please assign this to me?

@Ned-oleary,
Which option do you prefer we use for null styling?


output: Support record_accessor in buffer's chunk keys

This patch add record_accessor's dot-notation support in chunk keys.
To support bracket-notation, we need to consider relax validation in many places.
So it is the future work.

@mururu Could you check this?


SVGO is breaking images

SVGO is breaking lots of our images. We actually use svgo but had to disable some of the optimizations. ('removeUnknownsAndDefaults' and 'mergePaths')
Could svgo be outright skipped with an option?

Could you send me some example-SVGs where this is happening?
If I remember correctly, SVGO is also used to get a correct image: The original image is already piped through imacss (purify/slugify/urify), so we only have an (uri)encoded image at this point.
Will have a look if that's correct...

source | broken
source | broken

Commenting out L34 lib/iconify.js doesn't seem to cause any errors and stops SVGO from mangling the images.

Okay, so line 37 needs to remain where it is, otherwise you'll get the base64 encoded image. Line 28-35 should be executed as an option. I think I'll make the option an opt-out one (optimize by default, production-ready files)... on the other hand, if SVGO is still not as 'stable' as I'd thought perhaps it really should be an opt-in... I could introduce an extra SVGO param-option (pass params to SVGO call).
FYI: https://github.com/svg/svgo/issues/217

Our workflow does the image optimization before iconify is started, so skipping SVGO entirely as an option would be great. For those that don't have the slightly more convoluted pipeline we do, being able to passin a custom SVGO options object would be useful.
Perhaps by default svgo is run with defaults, then an svgo option can either be set to false where it doesn't run, or an object that's passed directly to the svgo instance?

Fixed with: https://github.com/gavro/gulp-iconify/commit/c3bd2246050ca51d5394ae577504db8e84de86c5
See readme:
###Customized example
gulp.task('default', function() {
    iconify({
        src: './img/icons/*.svg',
        pngOutput: './img/icons/png',
        scssOutput: './scss',
        cssOutput:  './css',
        styleTemplate: '_icon_gen.scss.mustache'
        svgoOptions: {
            enabled: true,
            options: {
                plugins: [
                    { removeUnknownsAndDefaults: false },
                    { mergePaths: false }
                ]
            }
        }
    });
});

Note: To disable SVGO, just set svgoOptions: { enabled: ___ } to anything but true .

Brilliant. Cheers.


 component not compatible with @solid-primitives/i18n

Hello,
I'm trying to display localized content with @solid-primitives/i18n but when I try to display such content in  using  component I've got an error code like this:
An unhandled error occured: TypeError: object is not iterable (cannot read property Symbol(Symbol.iterator))
    at SeoTitle (/src/seo/SeoTitle.tsx:8:15)
    at Proxy.createComponent (/Users/tom/projects/test/node_modules/solid-js/dist/server.cjs:286:10)
    at Object.get children [as children] (/src/route-modules/Home.tsx:18:40)
    at eval (/@fs/Users/tom/projects/test/node_modules/@solidjs/meta/dist/index.jsx:179:22)
    at Array.map (<anonymous>)
    at Module.renderTags (/@fs/Users/tom/projects/test/node_modules/@solidjs/meta/dist/index.jsx:176:15)
    at eval (/@fs/Users/tom/projects/test/node_modules/solid-start/root/Meta.tsx:14:89)
    at Array.<anonymous> (/Users/tom/projects/test/node_modules/solid-js/web/dist/server.cjs:629:65)
    at injectAssets (/Users/tom/projects/test/node_modules/solid-js/web/dist/server.cjs:663:70)
    at doShell (/Users/tom/projects/test/node_modules/solid-js/web/dist/server.cjs:410:12)
    at complete (/Users/tom/projects/test/node_modules/solid-js/web/dist/server.cjs:428:9)
    at checkEnd (/Users/tom/projects/test/node_modules/solid-js/web/dist/server.cjs:312:24)

i18n works correctly when used with other/regular components...
Is there possibly a quick fix for this?
Thanks a lot

Can you show us how you used it?

Can you show us how you used it?

Please check repo https://github.com/tomexx/solid-start-primitives-i18n

Can you show us how you used it?

I've added more examples/commits. Not sure if it works like this by design... If yes, please feel free to close this issue.
https://github.com/tomexx/solid-start-primitives-i18n/commits/master

In setting up for SolidStarts next Beta Phase built on Nitro and Vinxi we are closing all PRs/Issues that will not be merged due to the system changing. If you feel your issue was closed by mistake. Feel free to re-open it after updating/testing against 0.4.x release. Thank you for your patience.

See https://github.com/solidjs/solid-start/pull/1139 for more details.


Datastore fails to sync if I restrict access to group

Describe the bug
When you set auth to {allow: groups, groups: ["admin"]} then entire datastore only works if admin logs in. If non admin logs in then other types that are {allow:owner} also don't sync. Everything stops working if non admin logs in.
DataStore - Sync error subscription failed Connection failed: {"errors":[{"errorType":"Unauthorized","message":"Not Authorized to access onUpdateNote on type Subscription"}]}
Amplify CLI Version
Amplify v4.16.1
To Reproduce

npx create-react-app blog --use-npm --template typescript
amplify init
amplify add auth select email for login and everything else default
amplify update auth add group admin & again add admin queries
amplify add api with conflict resolution to optmistic concurrency with following schema

type Blog @model
  @auth(rules: [ {allow: owner} ]) {
  id: ID!
  owner: String!
  title: String!
}

type Note @model
    @auth(rules: [ {allow: groups, groups: ["admin"]} ]) {
    id: ID!
    content: String!
}

EVERYTHING WORKS WHEN ADMIN LOGS IN
But if non admin logs in then I get following error
DataStore - Sync error subscription failed Connection failed: {"errors":[{"errorType":"Unauthorized","message":"Not Authorized to access onUpdateNote on type Subscription"}]}
Expected behavior
Datastore should sync even if non admin user logs in.
Desktop (please complete the following information):

OS: Ubuntu 18.04 from Windows 10 WSL
Node Version. 12.16.1

Additional context
Other than this issue being huge dealbreaker for me. I wanted to talk about what is working.
type Note @model
    @auth(rules: [
        {allow: owner},
        {allow: groups, groups: ["admin"]}
    ]) {
    id: ID!
    owner: String!
    content: String!
}

In combination with allow owner it works fine. But I don't want to add owner. I want to only restrict to the admin group.
type Note @model
    @auth(rules: [
        {allow: private}
    ]) {
    id: ID!
    content: String!
}

If I change to allow private then also it works fine. And when you fix this issue its easily upgradable to {allow: groups, groups: ["admin"]} without encountering error only one resolver allowed per field. Drawback is there are 100's of non admin users that will download data that they will never see on their UI. 10,000's of wasted requests and payload data costs that I am paying until you fix this issue for me. And its not just single Note type that is exlusive for admin. The admin has more data type exlusive for them than regular users.  So its much worse than you think.

Hello @apoorvmote looking at your schema for type Note the error seems related to the subscription operation onUpdateNote? It seems they are not authenticated if they are not in the "admin" group. Though on your schema for Note you listed Admin as the only allowed group to have access on that type. If you want to allow owner as well you could add owner in the rule list or make it private as you had listed below in your second schema.

@SwaySway Let's look at it from different angle. Instead of technical talk let's talk about my actual real world case and my attempt to convert into technical schema.
I have few things let's say type Finance that only admin group has read/write access. And normal users cannot read or write that translates to not sync finance with datastore.

If you want to allow owner as well you could add owner in the rule list or make it private as you had listed below in your second schema.

To reiterate I do not want normal users to download type Finance records because they are not authorized to view it and anything downloaded is pure waste.
For this use case I tried following schema that is failing.
type Blog @model
  @auth(rules: [
        {allow: owner},
        {allow: groups, groups: ["admin"]}
    ]) {
  id: ID!
  owner: String!
  title: String!
}

type Note @model
    @auth(rules: [ {allow: groups, groups: ["admin"]} ]) {
    id: ID!
    content: String!
}

The blog is for normal users only with admin override. And Note is basically Finance that is specific to admin group.
Clearly my schema is failing. What schema do you suggest to solve my problem??

@apoorvmote DataStore currently doesn't support this use-case currently but I'm we're working actively on supporting multiple auth types on a schema. Discussed with @amhinson offline and moving it to the JS repo.


[stable/fluent-bit] parsers.conf is never used

What this PR does / why we need it:
Currently, if you define custom regex rules on values.yml, they are completely ignored because file "parsers.conf" is never passed inside the fluent-bit container.
Special notes for your reviewer:
helm upgrade is enough to fix the bug on a current install.
helm lint is OK.

/assign @mattfarina

@kfox1111 @edsiper Can you please review this?
/ok-to-test

Please don't close this MR Mr robot :)

sorry for the late review. didn't notice it.
looks good to me, other then the version number needing to be bumped again as trunk has a newer version number.

Seems my patch has been override by https://github.com/helm/charts/pull/7474/ and is no longer necessary :(

If this is no longer necessary than we can close. If that is not the case we can re-open. Thanks for the work.


Use and require Java 23

Description
Use and require Java 23.
Do not merge yet.

Release notes
(x) Release notes are required, with the following suggested text:
* Require Java 23 for build and runtime.

@oneonestar is this ready to review?

I think this might also need an upgrade of airlift and airbase -- please check with @wendigo

Also .. we probably want a separate PR in parallel that runs with 24-ea similar to how we run it in Trino

is this ready to review?

@willmostly Yea.

I think this might also need an upgrade of airlift and airbase -- please check with @wendigo

Sure #529
Since Java 22 is already EOL, we should roll this out soon.

Let's ship it together with Trino. 🚀
https://github.com/trinodb/trino/pull/23783


Please add these Serbian ad hosts

Please block these hosts:
adrs.hit.gemius.pl
gars.hit.gemius.pl
hrgde.adocean.pl
ringierrs.adocean.pl
rs.adocean.pl

I tested them and didn't notice any adverse effects.
Thank you

Thank you for these @kalehrl.
I'm in no position to assess these, and you provide no actionable context.
Also .pl is the country code for Poland, not Serbia.  But what's 800 km, right?  500 miles.  Three, maybe four countries between them.

That's no problem. It's all Slavland. :)
In all seriousness, I used an Android phone with Adaway and your hosts.
Your default hosts got rid of all the ads within the Serbian news app Blic owned by Ringier Axel Springer.
However, some news articles are from external sources so that's where I found some ads whose hosts I analyzed using Adaway and put them in my block list. I rebooted the phone and tried the same news and, voila, the ads disappeared.
I can now remove the hosts from my personal block list.
Thank you.

Maybe the app was developed by Polish programmers.

Rather German programmers.

adocean = gemius = international (a lot of sites use this)

Also .pl tls is cheap so sometimes it's better to buy one than to go with .live.

I'm going to close this.  I'm not interested in carrying these since there's no backing.


Mirror prebuilt Docker image to ECR Public

What would you like to be added: Have a image available on ECR Public
Why is this needed: To avoid rate limit against DockerHub

Related to https://github.com/aws/amazon-eks-pod-identity-webhook/issues/5, do you have a plan to publish Docker images currently only available on DockerHub to ECR Public? It would be convenient to avoid rate limit error from DockerHub.

Any chance for traction on this issue?  This would be a huge improvement

Id even entertain publishing under ghcr.io if thats acceptable to get around rate limits. ECR public would be the best, but happy to pr the build action here to support a ghcr.io target.

@nckturner @emattiza looks like we can pick up this workflow from aws-ebs-csi-driver:
https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/.github/workflows/publish-ecr.yaml
and adapt it for us here?

I agree @dims, and there are some makefile tweaks and a ./hack/provenance buildx test script. Happy to be the code mover if someone can handle the secret provisioning that will be support the PR.

@emattiza please give it a shot! yea, i think we should be able to do the secret stuff


feat: notecard HIL actions

This PR adds:

a notehub_firmware_query action that can query the name of a firmware file from Notehub, given a version. A complete version can be specified, such as <IP_ADDRESS>45. (major.minor.patch.build) or a partial version can be specified, in which case the highest matching version is retrieved. Supports published and unpublished firmware.
a notehub_firmware_get action that downloads named firmware to a file, with md5 checks and also writes out the metadata to a .json file.
notecard_dfu_util action that uses DFU util to flash a firmware file to the notecard, given the device's serial port and DFU serial number. The action puts the device in bootloader mode before flashing the firmware.
an action that can update named firmware to a device using Notehub DFU.  It requires just the name of the firmware in Notehub and the serial port.

A fixture with a Notecard has has been set up on the HIL farm. This PR includes workflows that test these actions to validate they work as expected.
The actions are implemented using python to do most of the heavy lifting. Python CI runs docstyle, flake8 and pytest (with doctests).
I am sure there will be other features needed, but this represents a good starting point for automating firmware updates to Notecards in the HIL farm.

 create github action to automate installing firmware to Notecard


fix #869

New Website Logo: [WINK Streaming]
https://github.com/rust-lang/rust-www/issues/869

Thanks!


Frontend Project "PrimeFlix" 'Your favorite channels all in one place' Section Improved Alignment

Describe the Feature you want to end
Changing alignment styling property of this section to improve its design.
Expected behavior
Improved alignment of this section.
Screenshots (optional)
Current Design

Expected Updated Design

Additional context (optional )
N/A

@MohitGupta121 Kindly assign me this issue.


redirect doesn't work with aot: false

What version of Elysia.JS is running?
1.0.20
What platform is your computer?
WSL Ubuntu
What steps can reproduce the bug?
const app = new Elysia({ aot: false }).get('/', ({ redirect }) => redirect('/yay')).listen(8080)

What is the expected behavior?
redirect works
What do you see instead?
redirect is not a function
Additional information
reported on discord

Should be fixed on 321a7c5, published under 1.0.21


khiops command return error 1 without any message.

Description
When using khiops version 10.2.2 on Linux laptop, the khiops command return error 1 without any message.
After analysis, khiops fails when the KHIOPS_PROC_NUMBER environment variable is set to the number of available cores (20 on the laptop).
Previous version of khiops (10.2.0) was running fine with the same variable/value.
Questions/Ideas

remove the --quiet option from mpiexec command line

Context

Khiops version 10.2.2

#310


Not all HA icons are supported?

It appears that only a subset of HA's icons are supported in this, eg. mdi:home-lightning-bolt doesn't work.  Is there a way to improve this?

I am using an mdi-library for this. I will check if there are any updates that contain those missing icons.

As far as I see, all material design icons should be supported by the plugin. When I change the icon of an entity to "home-lightning-bolt", it is displayed correctly:

I am currently implementing a complete rework of how icons work in the plugin, so we will have to check back later and see if this problem persists.


Display Value and Content on Horizontal line using ChartJS Annotation plugin

I am using chartjs annotation plugin to show the horizontal line in chartjs.But the problem which i am facing is i am unable to display the value but able to draw the line.I have mentioned below the script which i am using so far.Also,i have attached the screen shot for your reference how i want to display value and content on my chart.Is it possible in chartjs.
annotations: [{
      id: 'hline1',
      type: 'line',
      mode: 'horizontal',
      scaleID: 'y-axis-0',
      value:42.3,
      borderColor: 'red',
      borderDash: [8,5],
      borderWidth: 1,
      label: {
         backgroundColor: "white",
         fontColor:"red",
         content:"Benchmark",
         enabled:true,
          position : "left",
         fontStyle: "bold",
         xPadding: 0,
         xAdjust: 10,
          fontSize: 14,
          yPadding: 0,
        yAdjust: 10
      }
   }, {
      id: 'hline2',
      type: 'line',
      mode: 'horizontal',
      scaleID: 'y-axis-0',
      value: 22.3,
      borderColor: 'green',
      borderDash: [8,5],
      borderWidth: 1,
      label: {
        backgroundColor: "white",
         fontColor:"green",
         fontStyle: "bold",
         content: this.Project_Target,
         enabled: true,
        position : "left",
        xPadding: 0,
        fontSize: 14,
          yPadding: 0,
        yAdjust: 10

      }
   }]
![annotation](https://user-images.githubusercontent.com/4999552/41822793-f13c4392-7812-11e8-8e45-dcea77594d2c.PNG)
I have posted same issue on stackoverbelow .Below i have mentioned the link:
[https://stackoverflow.com/questions/51013253/display-value-and-content-on-horizontal-line-using-chartjs-annotation-plugin](url)
Please suggest any work around how i can resolve my issue.

This appears correct. Without a reproduce, no way to get further


Anexia: return reserved IP when instance IPs are requested

What this PR does / why we need it:
When creating a machine at, we always first reserve an IP address for it. Later when retrieving the addresses of that machine, we rely on the vminfo API, which has some delay as it retrieves the IPs from the running VM.
This commit adds the reserved address to the list of addresses returned from an instance, which should reduce provisioning time a bit and make it more stable.
Also fixes a long-standing TODO comment: marking internal IPs as internal.
What type of PR is this?
/kind feature
Special notes for your reviewer:
As per this comment
Does this PR introduce a user-facing change? Then add your Release Note here:

NONE

Documentation:

NONE

/ok-to-test

/retest

@xrstf why did we close this?

I must have fatfingered something. Can't even remember closing this.

/retest