deno: 1.29.3 -> 1.29.4

Description of changes

Update deno to 1.29.4
Also added some simple tests to run on any auto updates. Covers the bases we usually try.
I have avoided using any remote libraries & used features I expect to be very stable. If these features change then fixing the test should be basic and will also be a sign that we shouldn't just backport the update.
Things done

Built on platform(s)

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

[X] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 211227 run on x86_64-linux 1

2 packages built:

deno
quarto

Why not adding a simple test to nixosTests and calling them with
passthru.tests = nixosTests.deno;

:)

From my point of view, the organization of the tests is over complicated. Could we move them into a single .js/.ts file with assertions inside, and run that instead.

Why not adding a simple test to nixosTests and calling them with

because a VM isn't necessary for these tests

From my point of view, the organization of the tests is over complicated. Could we move them into a single .js/.ts file with assertions inside, and run that instead.

because 4/5 of the tests require a second file


Komi Republic, Russia

Data for the northerly Komi Republic

This server is a bit slow, but I got it working locally. Is it possible to set the default timeout to something like 300 seconds?

Yes, I think I can do that! I'm unsure where it’s set now, but: https://github.com/openaddresses/machine/issues/528
@sergiyprotsiv, would you like to be added to the OA Github org so you can work on branches directly in this repository?

Re-run this please.

Re-run this please.

Re-run this please.

Nooo, it got 616K out of 640K and died. Try again, otherwise will upload a cached version.

The "TYPE_S" field refers to the thoroughfare type e.g. улица, so maybe it should be:
"street":  ["TYPE_S", "NAME_S"],

or perhaps the inverse order?

Can this be merged?

I think this one is fine too, though only a fraction of building s contain an address

LGTM


Increase Electron max-header-size by default

Trying to provision / publish to Azure sometimes fails with a 431 if the token in the header is too large.
See #5377 for reference
Currently there is a workaround by setting the following environment variable before starting Composer:
set NODE_OPTIONS="--max-http-header-size=<some size in bytes>"
Ex: set NODE_OPTIONS="--max-http-header-size=16000"

Version
1.3.x
Expected behavior
It would be nice if the user did not have to set this explicitly after running into the error, and if we could just set this at the time of invoking Composer.
However, I was experimenting with this the other day, and it seems like this cannot be set at runtime in the application code, but must be set when / before invoking the Electron binary to start our app.

Notes about the issue:

Might be worth trying to use app.appendCommandLineSwitch() to provide this default
Since Node 13, this default value has been increased from 8 KB to 16 KB (source)

Electron v11 is only at Node v12.8.3 right now, so we would have to wait for a newer version with Node v13.x, and then maybe bumping to the newer version would resolve this

Could possibly try bumping up the limit on a per-request basis using the Node http.request options property maxHeaderSize (docs]

Notes about the issue:

Might be worth trying to use app.appendCommandLineSwitch() to provide this default
Since Node 13, this default value has been increased from 8 KB to 16 KB (source)

Electron v11 is only at Node v12.8.3 right now, so we would have to wait for a newer version with Node v13.x, and then maybe bumping to the newer version would resolve this

Could possibly try bumping up the limit on a per-request basis using the Node http.request options property maxHeaderSize (docs]

hi @tonyanziano , does the workaround with setting the environment variable works also with the pre compiled version of Composer?
I'm setting the variable before opening it but I still get the same error.
Thanks!


Adding Azure-specific disk instructions

This PR adds the instructions for configuring the Kubernetes cluster to enable provisioning PersistentVolumes when running on Azure. I chose not to re-number the entire page's hyperlinks, but I'm happy to do that if it would be helpful.
Also, I'll update these instructions when ACS is updated in the next month or so, and will then require no Azure-specific configuration to get up-and-running.

Can confirm this working! I just deployed successfully to Azure! Thank you very much Jonathan! :)

@markfejes Awesome! Thanks for confirming.

Just confirmed. Thanks again


Dead links pointing to the old ENES Portal

@SophieMacadamia here are a few dead links that are currently pointing to the old ENES Portal site:
ERROR: https://portal.enes.org/community/community-workshops/fifth-workshop-on-coupling-technologies-for-earth-system-models gives HTTP Error 404: Not Found
ERROR: https://portal.enes.org/community/announcements/events/joint-is-enes3-esiwace2-virtual-workshop-on-new-opportunities-for-ml-and-ai-in-weather-and-climate-modelling gives HTTP Error 404: Not Found
ERROR: https://portal.enes.org/community/community-workshops/7th-enes-hpc-workshop-barcelona-2022 gives HTTP Error 404: Not Found
If you tell me which are the new ones on the new portal then I will change them :beer:

the good news is that, after deploying to the perm site, these and the DKRZ links from https://github.com/IS-ENES3/IS-ENES-Website/issues/2 are the only broken links :grin:

Hi Valeriu,
I think these are the links:
(1) https://is-enes3.github.io/IS-ENES-Portal-Website/coupling-workshops-detailed#CW2020
(2) https://is.enes.org/workshops-detailed/#ML-AI-WS
(3)  for this one, I need to clarify something with Sophie to prevent redundancy.

@fannyadloff you can find out where they are using grep e.g.
valeriu@valeriu-PORTEGE-Z30-C:~/IS-ENES-Website$ grep "https://portal.enes.org/community/community-workshops/fifth-workshop-on-coupling-technologies-for-earth-system-models" -r pages
pages/presentations-posters.md:[Fifth Workshop on Coupling Technologies for Earth System Models (CW2020)](https://portal.enes.org/community/community-workshops/fifth-workshop-on-coupling-technologies-for-earth-system-models) | ENES Portal Link

so that is linked from presentations-posters.md :beer:

Hi Valeriu, I think these are the links: (1) https://is-enes3.github.io/IS-ENES-Portal-Website/coupling-workshops-detailed#CW2020 (2) https://is.enes.org/workshops-detailed/#ML-AI-WS (3) for this one, I need to clarify something with Sophie to prevent redundancy.

indeed those the links, can we change them to existing ones on the portal.enes.org or we just dump them?

No, we should change them to the one I gave you above.
For (3) it's: https://portal.enes.org/hpc-workshops-detailed/#hpc7
I can't do a grep on github.
(I don't have a local repository)..
If you tell me where (2) and (3) are, I'll change them!
Same for the brocken DKRZ links.

I fixed (1) & (2), can't find where is (3) located?

that's a ghost, I reran the test and it didn't show up anymore, must be @SophieMacadamia fixing the page in the meantime :grin: Brilliant, cheers @fannyadloff - no more broken links from the Portal :partying_face:


1inch logo changed

https://alphawallet.com/browser/
The latest is:
https://avatars.githubusercontent.com/u/43341157?s=200&v=4
@colourfreak

Or here:
https://github.com/1inch/gnosis.1inch.exchange/blob/master/src/assets/logo.svg

what is wrong here?

It's different.


Mac Warning

Mention that processing is slower on Mac

You have provided a warning in test file and consolidated file documentation. Do you want to provide one in code too?

Closing this.


Update Lark to 1.0

Hey, congrats on 1.0! As I said in #8, I'll be slow to attend to these PRs, so feel free to merge it yourself if the tests pass. The changes look fine to me.


Define Default Device

Use case

Whenever I load up a project and run flutter run I sometimes forget to change the device. For projects such as my website where the default platform isn't mobile it is kinda a pain to have to change the device every time.
Proposal

Define in your pubspec.yaml the default device or platform. For example default: macOS

This does not belong in the pubsec.yaml, (perhaps flutter config) but configuring a default device seems like a reasonable feature.


Fix deb java dependency

Rebased #289.

This pull request is now managed with CodeReviewHub. Refresh.


Export SQL Database with CDC

What happened:
I was told to use Prepare-ExportDatabaseJobFile.ps1 that would prepare a json file that would help me export databases with CDC.
What you expected to happen:
could not get this to work with server that had multiple instances but would on one that did not.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
once I have a json file how does that help me with restoring a database that has Change Data Capture

CDC requires you to restore the database with additional commands. Those commands are not available via Rubrik. The way you do it via the prepare script is run it like you normally would. When you look at the JSON file, you will see a field that says FinishRecovery. This by default is set to true. If you set this to false, your database will be recovered and left in NORECOVERY mode. You can then add to your process to say RESTORE DATABASE [DBNAME] WITH KEEP_CDC.  If you had replication enabled in the database you would do a similar thing, except using KEEP_REPLICATION.
From: rwyoung01<EMAIL_ADDRESS>Sent: Wednesday, October 7, 2020 3:29 PM
To: rubrikinc/rubrik-scripts-for-powershell<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [rubrikinc/rubrik-scripts-for-powershell] Export SQL Database with CDC (#158)
What happened:
I was told to use Prepare-ExportDatabaseJobFile.ps1 that would prepare a json file that would help me export databases with CDC.
What you expected to happen:
could not get this to work with server that had multiple instances but would on one that did not.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
once I have a json file how does that help me with restoring a database that has Change Data Capture
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frubrikinc%2Frubrik-scripts-for-powershell%2Fissues%2F158&data=02|01||eda85a1877a6496316c708d86af74282|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637376957483809928&sdata=cjNLkFWMOFHzBF9bFyMlupLCQOSxaebMDbTKZprW2Bs%3D&reserved=0, or unsubscribehttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFKMBSF7XXKQZILS2A4SOSLSJS6QDANCNFSM4SHZ7ONA&data=02|01||eda85a1877a6496316c708d86af74282|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637376957483819921&sdata=9ULO9%2BrwOlbFPRelPZbva2fMYUbBb3rEqUPG%2FCWd0d0%3D&reserved=0.


Update index.html

It appears that the index.html file was changed elsewhere after the last commit (made on July 2nd), so I copied it from the site and modified it to fix issue #5.

I just noticed that we might be on the wrong repo. Is troops2coders.github.io the repo that we should be working on, instead?

Should only be one, but was tinkering around and may have inadvertently created more than one repo

On Sep 21, 2016, at 2:38 PM, Ronald Rihoo<EMAIL_ADDRESS>wrote:
I just noticed that we might be on the wrong repo. Is troops2coders.github.io the repo that we should be working on, instead?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


each navigateAction call increases history length by 2, stuffs up browser back button?

Every navigateAction calls handleHistory:componentDidUpdate twice
first for  NAVIGATE_START
second for  NAVIGATE_SUCCESS
Back button is not working properly because of this.

Hi @mailaneel, could you look at https://github.com/yahoo/fluxible-router/issues/66 and see if this is the same issue you are seeing?

@mridgway thanks same issue.
I am using transform on route to solve https://github.com/yahoo/fluxible-router/issues/65 which returns transformed url.
So when we compare they are do not match. Any Suggestions
Transform: /?q=test#comments => /comments?q=test

My bad works fine now, I am doing it in reverse instead of transform
thanks once again @mridgway


Start SCSS to CSS migration: update webpack rules and migrate shared components

Description

Updated webpack configs to load CSS files
Updated Storybook settings
Migrated SCSS variables to styles/design-tokens.css
Migrated other SCSS partials in the styles directory
Migrated shared components (contents of the shared directory), except for the helpArticle component

Files left to migrate:
find . -type f -name "*scss" | wc -l
     179

Related JIRA Issue(s)
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-2075
Deployment URL(s)
http://scss-to-css.review.ensembl.org

Noticed the use of --color. Aren't we supposed to use UK spelling colour?

Noticed the use of --color. Aren't we supposed to use UK spelling colour?

I was afraid you were going to say that. Personally, I am strongly opposed to this extra letter, because browsers, and CSS in particular, favour American English (color without the u in the names of CSS rules). Yes, I know we said several years ago that we were going to use British spelling in code; but every time I try, it just feels so awkward and wrong.

It's sad that American English has taken over the original English 😞 That aside, do we know of the consensus across Ensembl on which spelling to use?

haha not me. I prefer -color. But it was Anne who brought this up before, so I just recollected that. Good to respect css rules and also a letter less to type :-) So now we have a consensus between us @imransl  :-)


New package: SR v0.1.0

Registering package: SR
Repository: https://github.com/MilesCranmer/SymbolicRegression.jl
Created by: @MilesCranmer
Version: v0.1.0
Commit: 24760f851a9500269a04e1beb677d0ea64c00c26
Git reference: master

Block automerge

Block automerge

FYI: I have renamed the package to SymbolicRegression.jl to satisfy the naming requirements.

FYI: I have renamed the package to SymbolicRegression.jl to satisfy the naming requirements.


Rebase javascriptcontext

And add linux build options. @matteblair may I push this to 'javascriptcontext' so that it's easier for me to test changes on this branch?

@hjanetzek Yeah you can push these changes to javascriptcontext, it'll be good to be benchmark both engines. Thanks!


fix lock scope

This should fix a bug where the second app being backed up would sometimes deadlock.

Second try and it locks/ stops

@Blu-J are you saying this doesn't work?

@ProofOfKeags Yes it doesn't seem to fix it
Sometimes it gets through;
Sometimes it gets stuck on btc pay server;
Sometimes gets stuck on Mastodon

how are you assessing stuck?
Part of the backup process is to save off the .s9pk and Mastodon is 1GB.

Will do a few more, the mastodon was more premptive. The btc -pay one was stuck there an hour, but I have done 5 more backups without issue. So will test throughout the night

we have deadlock detection so maybe we need to kick up the logging around the lock acquisition.


Add expected value CLI and plugin

Add a plugin and CLI to calculate the expected value from a probability distribution.
The expected value is the mean of random outcomes (eg. ensemble members) and can be used to produce a deterministic "best guess" forecast from a probabilistic forecast as processed by IMPROVER. The expected value will often be similar to the 50th percentile, but may differ, such as in the case of a positively or negatively skewed (asymmetrical) distribution.
The calculation of expected value for threshold probability data added here is a quick to implement method using existing IMPROVER functionality for conversion to percentiles - this has the correct input and output interfaces, but has high memory usage and has an impact on the accuracy of the output data. I expect to add direct calculation from threshold data (via numerical integration over the threshold values) in a future pull request.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

Something for a reviewer to consider. This PR calculates the mean value of the ensemble members, and the meta-data is updated to say exactly this. An "Expected Value" is a weighted mean, but this PR provides no mechanism for weighting the members. Should the CLI / plugin be renamed?


d3.blur

import * as d3 from 'd3'
d3.blur

Property 'blur' does not exist

blur was added in v3.2.0 https://github.com/d3/d3-array/releases/tag/v3.2.0


JSON to Serde doesn't handle keywords or spaces

I guess this is two issues in one, but these are things I've noticed while trying to use it.

It doesn't handle renaming keywords. I've seen this issue with APIs that will return something like

{
    "type": 1
}

Output will give you the following struct:
#[derive(Serialize, Deserialize)]
struct RootInterface {
  type: i64,
}

But it should be giving something like this:
#[derive(Serialize, Deserialize)]
struct RootInterface {
  #[serde(rename = "type")]
  kind: i64,
}

Key with spaces will produce invalid Rust. For instance, the following JSON will produce the following struct with an invalid identifier:

{
  "cat dog": 1
}

#[derive(Serialize, Deserialize)]
struct RootInterface {
  "cat dog": i64,
}

How do suggest to rename them ?

for spaces I can change it to camel case
for reserved keyword - prefix / postfix ?

Any suggestion for the second one ?

I'm a fan of just adding a underscore to the beginning.  type -> _type.

fix deployed.


Enable turn off table of contents

For very short documents with a single section, it would be great if we could turn off table of contents with a metadata field.

Ah, I was wondering why you wanted to do this, given that ToCs are very useful. ^_^
I'd probably want it to automatically turn back on if you gained more sections and forget to remove the metadata; so maybe just an option that explicitly suppresses the ToC if the construction algorithm would only insert a single heading into it?

+1 that sounds good.
In particular, I'd want no table of contents if I have no sections, even if I have normative references/an appendix of terms/auto-generated sources.

Oh, hm. Those are all included by default, yeah.
But they're not numbered! So perhaps I key it off of numbered sections, rather.


Configure Error

Hi,
I'm on Fedora 16 3.3.7-1.fc16.i686.PAE
When I run ./configure then following error appears :
configure: error: *** Required libusb-1.0 >= 1.0.0 not installed ***
and script stops.
Latest version of libusb is installed :
$ sudo yum install libusb
Loaded plugins: langpacks, presto, refresh-packagekit
Repository google-chrome is listed more than once in the configuration
Package 1:libusb-0.1.3-9.fc16.i686 already installed and latest version
Nothing to do
I did install libusb (version greater than 1.0.0) using source and running script again doesn't resolve the issue.
If I run : sudo yum remove libusb (to remove installed libusb) then it also throws message to remove dependencies mounting to 1GB.
May anyone point out the issue ?

I completely forgot to close this issue. Indeed, moving to Ubuntu worked. If I recall correctly, then the way Fedora used to package libusb was the main reason for above issue.
To future developers/contributors working with ARM toolchains, please set up your development environment on Ubuntu/Debian, these have best support for ARM development compared to other Linux Box in terms of lib and other packages.


Not working with https enabled registry

Hi ,
My private docker local registry is https enabled. I am able to connect with docker cli but not able to connect with this application.
it shows below mentioned error
Get https://slave-node1:5000/v2/: dial tcp: lookup slave-node1 on <IP_ADDRESS>:53: no such host
time="2020-04-12T09:13:50Z" level=info msg="Using registries located in /app with file name registries" file=allregistries.go line=161 source=app
time="2020-04-12T09:13:50Z" level=error msg="Failed to connect to validated registry: Get "https://slave-node1:5000/v2/\": dial tcp: lookup slave-node1 on <IP_ADDRESS>:53: no such host" file=registry.go line=297 source=app
time="2020-04-12T09:13:50Z" level=fatal msg="Failed to create registry (https://slave-node1): Get "https://slave-node1:5000/v2/\": dial tcp: lookup slave-node1 on <IP_ADDRESS>:53: no such host" file=allregistries.go line=198 source=app
regestries.yml description
registries:
localRegistry:
displayname: localhost-registry:5000
url: https://slave-node1 # Example https://localhost, http://remotehost.com
port: 5000  # Example: 443, 8080, 5000
username: admin
password: admin
refresh-rate: "5m" # Example: 60s, 5m, 1h
skip-tls-validation: false # REQUIRED for self signed certificates
dockerhub-integration: true # Optional - compares to dockerhub to determine if image up to date
Please help.

HI @crazypersonboyz,
I have this application connected with multiple https-enabled registries and it is working just fine. Looking at your registries.yml file, you should probably change the port number from 5000 to 443.


Single quote must be escaped otherwise ''' is generated instead of '''.

Single quote must be escaped otherwise ''' is generated instead of '\'' which results in a compiler error (e.g.: CS1011, C1012, etc.).
For example, the current version generates the following code for SDL_keycode.h:

public enum SDL_KeyCode
{
    SDLK_QUOTE = (byte)(''')
}

instead of

public enum SDL_KeyCode
{
    SDLK_QUOTE = (byte)('\'')
}

Thanks for the contribution!


Regarding output ports mapping to BLIF/verilog

Hi ,
In the  dot file generated , the outputs are named as po*. But in the verilog/blif files as input , the names are of course different for both inputs and outputs.
How to know the mapping of input/output for input blif/verilog to the dot file ?
108 -> po3 [style=solid]
111 -> po4 [style=solid]
120 -> po5 [style=dashed]
122 -> po6 [style=solid]
127 -> po7 [style=solid]
{rank = same; po0; po1; po2; po3; po4; po5; po6; po7; }
Thanks !

Any feedback on this ?

Unfortunately the labels in the graph are not tied to the names coming in, but are pretty much arbitrary. This graphing is handled by mockturtle.

Hey,
The input names are now preserved in the dot file; the PO names are numbered in the order they are given in the verilog.


SPARK-5744 [CORE] RDD.isEmpty / take fails for (empty) RDD of Nothing

Handle take, isEmpty for parallelize(Seq()).
As a knock-on effect of that fix: correctly handle 0 partitions in histogram.
Plus tests.

Test build #27441 has started for   PR 4591 at commit 2390a3f.

This patch merges cleanly.

Test build #27441 has finished for   PR 4591 at commit 2390a3f.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27441/
Test FAILed.

To recap:
If you parallelize a Seq of Nothing or Null, you end up with an ArrayStoreException in the part of the code that collects results from partitions. It's just a Java-Scala compatibility thing that has to be worked around. I don't think there's a complete solution.
We can solve the case of Seq[Nothing] by special-casing empty Seq, which at least handles the "sc.parallelize(Seq())" case. I used EmptyRDD for this since it's logic to make an empty RDD in this case. However an EmptyRDD has no partitions, while some code relies on it to have 1 or more empty partitions. So I made that possible.
Then I found some code will ultimately call compute() on an EmptyRDD if it starts to be returned from parallelize(), and that threw an exception. I had it return an empty Iterator.
That ends up putting us back where we started. Except that we can make sc.parallelize(Seq()).isEmpty() work by writing sc.parallelize(Seq(), 0).isEmpty() now.
(Along the way I discovered that calling histogram() on an EmptyRDD fails, so I touched that up.)
The rest is tests.
Question: since it doesn't seem possible to totally fix the "Seq()" case, and the improvement here for this trouble is small, is it worth doing this or just accepting this as a known issue / corner case?
I could trim this PR down to just the histogram fix and tests (that pass) and call it a day too.
Thoughts? CC @mateiz @pwendell @rxin as it's kind of a core API issue.

Test build #27496 has started for   PR 4591 at commit 7439b31.

This patch merges cleanly.

Test build #27496 has finished for   PR 4591 at commit 7439b31.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class JavaStatefulNetworkWordCount

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27496/
Test PASSed.

It seems to me it is a corner case. We might be better off just documenting it rather than adding an empty partition to the rdd, since conceptually I expect a empty RDD to have no partition.

@rxin So I should emphasize that the result of parallelizing an empty Seq right now is an RDD with many empty partitions, rather than no partitions. It almost works to return an empty RDD with no partitions, except that I found one case in the Python API, in its own paralleize() implementation, where it builds a result for xranges by mapping the empty partitions of the result of parallelize([]) to the desired partitions with a generator function.
This is basically the much simpler state after my first commit in this PR. If you can think of a better way to implement that bit of the Python API that doesn't rely on getting back an RDD with many empty partitions, that could be a way forward. The nice thing is that that version solves the problem of parallelize(Seq()) for all numbers of partitions. I suppose it introduces a small behavior change, in that you get back a 0-partition RDD here not one with the default # of partitions.
Anyhow, otherwise, I tend to agree with just documenting this and moving on.
I'll pause a day for more thoughts.

I'm going to abandon this and make a new PR that just documents this behavior. The fix just raises some other issues. (However I'll probably keep the fix for histogram in the new PR as a souvenir for the trouble...)

Sounds good. Thanks Sean.
On Feb 19, 2015 1:26 PM, "Sean Owen"<EMAIL_ADDRESS>wrote:

I'm going to abandon this and make a new PR that just documents this
behavior. The fix just raises some other issues. (However I'll probably
keep the fix for histogram in the new PR as a souvenir for the trouble...)
—
Reply to this email directly or view it on GitHub
https://github.com/apache/spark/pull/4591#issuecomment-75139291.


Window buttons when the tabs on bottom

Is it possible to move window buttons (minimize, maximize and close the window) to the right of the address bar to the very top right of the window when the tabs are at the bottom?

This mode is classic. You may need to activate the title bar in the settings.


Testing improvements

Run integration tests directly in Travis

@cwjohnston @luckymike PRs not building for some odd reason

@tas50 I'm at a loss here. This PR isn't present in Travis at all, and, unlike a webhook integration, I don't see a way to re-fire a notification to the Travis CI "service" in the repo settings.

@cwjohnston odd. I'll look around tomorrow and see if there's some magical fix for this

Turns out I was blocking builds off develop. Oops


⚠ Processors has degraded performance

In 333d962, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 161 ms

Resolved: Processors performance has improved in 4f49c98.


Publish to crates.io

Would it be possible to publish the latest version on crates.io? Thanks a lot!

@callanoc I will.

I need to address several clippy warnings before I can upload it. I'm sorry for the delay - will try finding time tomorrow.

@callanoc hello.
I published the package to crates under 0.26.11. Sorry for the long awaiting.


python310Packages.gql: 3.4.0 -> 3.4.1

Changelog: https://github.com/graphql-python/gql/releases/tag/v3.4.1
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 230480 run on x86_64-linux 1

14 packages built:

home-assistant-component-tests.tibber
python310Packages.gql
python310Packages.gradient
python310Packages.pytibber
python310Packages.skytemple-dtef
python310Packages.skytemple-files
python310Packages.skytemple-ssb-debugger
python311Packages.gql
python311Packages.gradient
python311Packages.pytibber
python311Packages.skytemple-dtef
python311Packages.skytemple-files
python311Packages.skytemple-ssb-debugger
skytemple


The instructions for verifying Downloads is incorrect

Expected Behaviour
it should return the hashsum
Actual behaviour
Assuming the ISO is in the downloads folder, copy and pasting "shasum -a 256 elementaryos-0.3.2-stable-i386.20151209.iso" into the terminal will fail as most terminals starts in the home folder
Steps to reproduce the behaviour

Open a terminal
copy and paste the command line

System

OS X
10.11
Firefox
44.0.2

A simple fix would be to have something like cd Downloads; shasum -a 256 elementaryos-0.3.2-stable-i386.20151209.iso
Edit: this also affects Linux/Ubuntu obviously as it uses the same command.

Why not something like:
cd ~/Downloads && shasum -a 256 elementaryos-0.3.2-stable-i386.20151209.iso

Make sure that the terminal emulator will move to the Downloads folder regardless of in which directory the terminal is in and just shasum it, all in one command.

Not sure why I forgot how the command line works, but shasum -a 256 ~/Downloads/elementaryos.iso would also work.

We could ls the downloads folder, grep for any elementary isos, then shasum, but I think that might be a little too much.  Not sure about how the wildcards work on osx and the shell

I think we should use shasum -a 256 ~/Downloads/elementaryos-0.3.2-stable-i386.20151209.iso and add a note about the user changing the directory as needed. "assuming you have saved the download in your downloads folder..."

That would probably be the most straightforward and simple. I think it's relatively safe to assume that's gonna work for most people


Why I can't play this game?

Question
Why I can't play this game?

For starters: which game? And what (error?) stops you from playing it?


I had an issue where the *. m3u8 would only fill 1kb.

Can you do some more error checking to make sure that it retries again if the file only comes being about 1kb big?
To my understanding the file is going to be at least 10-100kb big.
Maybe there could be a grace period of retrying a couple of times within 5-10 minutes span if file is under amount

maybe its one with proxy? and proxy not working then that happpens


Wrapping the slate plugin

Is your feature request related to a problem? Please describe.
I have created some plugins based on the slate plugin but wrapped in a component. An example for such a component could be an existing headline compontent with a property for different themes like "Title", "Sub", "Minor", ... you name it.
Slate will get the global styling from this parent component, but also allow to use the hover buttons to add a link or underline a certain part. In the toolbar you will find the controls for the headline component properties like "theme".
My solution is working but:

I have to use some parts of the slate plugin, which are not officialy exported. Like: '@react-page/plugins-slate/lib/serialization/createInitialState' or '@react-page/plugins-slate/lib/types/component'
I had to replace/extend the (un-)serialization to handle also the states for the parent component properties
I don't get TypeScript to accept my plugin type, maybe because of missing SerializationFunctions in my component?

Is there a nicer way to get this to work?
Should the create-plugin-materialui provide factories to build own plugins based on slate?
Additional context
Here my example code. I removed/skipped some parts (properties, type definitions, defaults, ...) to keep it short:
Plugin:
import React from 'react';
import { lazyLoad } from '@react-page/core';
import SlatePlugin from '@react-page/plugins-slate';
import createInitialState from '@react-page/plugins-slate/lib/serialization/createInitialState';
import { SlateProps } from '@react-page/plugins-slate/lib/types/component';
import Component from '@react-page/plugins-slate/lib/Component';

import { serialize, unserialize } from '../../utils/slate';
import { hoverPlugins } from '../../utils/HoverToolbar';

import { defaultHeadingState } from './default/state';
import HeadingRenderer from './Renderer';

const TitleIcon = lazyLoad(() => import('@material-ui/icons/Title'));
const HeadingControls = lazyLoad(() => import('./Controls'));

const slate = SlatePlugin();

const Heading = {
  ...slate,
  Component: (props: SlateProps) => (
    <Component
      Renderer={HeadingRenderer}
      Controls={HeadingControls}
      plugins={hoverPlugins}
      serializeFunctions={{}}
      {...props}
    />
  ),
  name: 'teamshirts/content/heading',
  version: '0.0.1',
  IconComponent: <TitleIcon />,
  text: 'Heading',
  description: 'Show a Headline',
  createInitialState: () => ({
    ...createInitialState(),
    ...defaultHeadingState,
  }),
  serialize: serialize(slate.serialize),
  unserialize: unserialize(slate.unserialize),
};

export default Heading;

Renderer:
import React, { FunctionComponent } from 'react';
import Renderer from '@react-page/plugins-slate/lib/Renderer';
import Heading from<EMAIL_ADDRESS>
import { HeadingControlsProps } from '../types/controls';

const HeadingRenderer: FunctionComponent<HeadingControlsProps> = props => {
  const { state, plugins } = props;

  const { theme } = state;

  return (
    <Heading
      theme={theme}
    >
      <Renderer state={state} plugins={plugins} />
    </Heading>
  );
};

export default HeadingRenderer;

Controls:
import React, { FunctionComponent } from 'react';
import { Editor } from 'slate-react';
import { BottomToolbar } from '@react-page/ui';
import FormControl from '@material-ui/core/FormControl/FormControl';
import InputLabel from '@material-ui/core/InputLabel/InputLabel';
import Select from '@material-ui/core/Select/Select';
import Input from '@material-ui/core/Input/Input';
import MenuItem from '@material-ui/core/MenuItem/MenuItem';
import FormControlLabel from '@material-ui/core/FormControlLabel/FormControlLabel';
import Switch from '@material-ui/core/Switch/Switch';
import { withStyles } from '@material-ui/styles';
import Heading from<EMAIL_ADDRESS>
import { darkTheme } from '../../../../../../config/theme';
import { bottomToolbarStyles, handleChange } from '../../../utils/component';
import LeaderInput from '../../../controls/LeaderInput';
import TrailerInput from '../../../controls/TrailerInput';
import { HeadingControlsProps } from '../types/controls';

const themes = [
  'title',
  'sub',
  'minor',
];

const HeadingControls: FunctionComponent<HeadingControlsProps> = props => {
  const { state, onChange, focused, readOnly, plugins, classes } = props;

  const {
    editorState,
    theme,
  } = state;

  const onStateChange = ({ value }) =>
    onChange({ ...state, editorState: value });

  return (

      <Heading
        theme={theme}
      >
        <Editor
          onChange={onStateChange}
          readOnly={Boolean(readOnly)}
          className="ory-plugins-content-slate-container"
          value={editorState}
          plugins={plugins}
          placeholder="Your Headline here ..."
        />
      </Heading>
      {readOnly ? null : (
        <BottomToolbar open={focused} theme={darkTheme}>
          <FormControl className={classes.formControl}>
            <InputLabel htmlFor="theme-helper">Theme</InputLabel>
            <Select
              name="theme"
              value={theme || 'title'}
              onChange={event => handleChange(event, onChange)}
              input={<Input name="theme" id="theme-helper" />}
            >
              {themes.map(themeItem => (
                <MenuItem value={themeItem} key={themeItem}>
                  {themeItem}
                </MenuItem>
              ))}
            </Select>
          </FormControl>
        </BottomToolbar>
      )}

  );
};

export default withStyles(bottomToolbarStyles)(HeadingControls);

I don't 100% understand the question. The goal is to switch a "theme" on the whole slate area or just on a component?

An example for such a component could be an existing headline compontent with a property for different themes like "Title", "Sub", "Minor", ... you name it.

that sound more like just using three heading types (level 1, 2 and 3) or so (?)
If you just want to have one Toolbar button, but want to display a dialog where you can customize the component (e.g. with a select-field that choses the "theme"), you can do it like in the example: https://github.com/react-page/react-page/blob/feat/uniforms-in-slate/examples/src/customSlatePlugin.tsx
So in your case, it could look very similar:
import { pluginFactories } from '@react-page/plugins-slate';
import React from 'react';

export default pluginFactories.createComponentPlugin<{
  color: string;
}>({
  addHoverButton: false,
  addToolbarButton: true,
  type: 'CUSTOMHEADING',
  object: 'block',
  replaceOnRemove: 'PARAGRAPH/PARAGRAPH', // if you set this property, the plugin will replace the paragraph with a the Component below, If you don't set it, the Component will wrap whathever currently is there (typically a paragraph)
  icon: ...,
  Component: props => {
    const theme = props.data.get('theme')
    return (
     // you can do whathever you want with that theme property, e.g. have some object where all diferent styles are defined

{props.children}

    );
  },
  schema: {
    type: 'object',
    required: ['theme'],
    properties: {
      theme: {
        type: 'string',

        enum: ['fancy', 'classic', 'glorious', 'punky', 'avantgarde'],
      },
    },
  },
});

this would be a customizable heading. What you could also do is wrapping the current block with a
 that sets a certain class. This looks very similar, but notice that it does not set replaceOnRemove:
import { pluginFactories } from '@react-page/plugins-slate';
import React from 'react';

export default pluginFactories.createComponentPlugin<{
  color: string;
}>({
  addHoverButton: false,
  addToolbarButton: true,
  type: 'THEMEBLOCK',
  object: 'block',
  icon: ...,
  Component: props => {
    const theme = props.data.get('theme')
    return (
      <div className={`theme-${theme}`}>{props.children}

    );
  },
  schema: {
    type: 'object',
    required: ['theme'],
    properties: {
      theme: {
        type: 'string',

        enum: ['fancy', 'classic', 'glorious', 'punky', 'avantgarde'],
      },
    },
  },
});

Some more answers

Should the create-plugin-materialui provide factories to build own plugins based on slate?

--> no, but slate plugin factories now use that too, if you provide a schema property, so you don't need to import that package

I have to use some parts of the slate plugin, which are not officialy exported. Like: '@react-page/plugins-slate/lib/serialization/createInitialState' or '@react-page/plugins-slate/lib/types/component'

Yea, you should not do that, because that might break in future versions. Also /lib is es5 code and tree-shaking might not work properly anymore. if you really need something from there, you can send in a PR that adds that to the export
Also in your example, you seem to replace the whole slate plugin with a Heading plugin, which is not logical to me. Maybe there is a confusion about the plugins:

react-page has different plugins, that represent a block in the editor, e.g. images, videos and text-areas
slate itself is a text-editor and the slate()-plugin is a react-page plugin that shows a rich-text area in a block
slate itself has also plugins, "slate-plugins", which can themself be blocks, inline elements or marks (e.g. em, strong).
Some stuff make sense to be added as slate-plugins, some are more suitable as react-page plugins. Headings for example make most sense as slate-plugins, like it is in the default configuration

If you want to have different slate plugins, e.g. one with only heading and a paragraph, others with links, all headings, lists, etc. then you can just use the slate plugin with different configurations:

const slate1 = slate([slatePlugins.headings.h1(), slatePlugins.paragraph()];
const slate2 = slate(); // all default plugins
const fancyHeading = slatePlugins.headings.h1(def => ({...def, Component: FancyHeading}))
const slate3 = slate([fancyHeading, slatePlugins.paragraph()]

make the slate plugin itself configurable for the user is not yet so easy, but we could also change the api a bit so that it's easier to customize e.g. with a schema-based form

Sorry, that I haven't been clear enough. I will try again:
We have a whole set of react components to build our page, like heading, text, button, accordion ... Each of this components has a list of properties to change the styling and behavior.
Now we want to use react-page to build a landingpage configurator, to allow our marketing team to build special pages via drag-an-drop while using our set of components.
So we need for each of our components one react-page plugin with controls for each property.
This is really working fine, but for some spezial components like text or heading, I would like to use slate to allow inline typing instead of inserting the content/text via a input control.
So my current solution described above is, to wrap my heading component around the slate editor.
I think I can't achieve that with a slate plugins or different slate instances.
Here a screenshot where the headline and the text could be changed inline but using our components.

you could make layoutPlugins that have one slate element inside:
import { v4 } from "uuid";

export default createLayoutPlugin({
  Renderer: props =>
{props.children}
,
  name: "heading",
  version: "0.0.1",
  // IconComponent: ,
  text: "Heading",
  description: "Heading",
  schema: {
     .... you could use the schema to create your complex form below
     ... altough we might could need some more layout options to it, so that the form controls float like in your example
 },
  createInitialChildren: () => {
    // wee https://github.com/react-page/react-page/issues/714
    const slateInst = new LayoutPlugin(slate([slatePlugins.emphasize(), slatePlugins.link(), slatePlugins.paragraph()]);
    return {
      id: v4(),
      rows: [
        {
          id: v4(),
          cells: [
            {
              size: 12,
              content: {
                plugin: slateInst,
                state: slateInst.createInitialState(),
              },
              id: v4(),
            },
          ],
        },
      ],
    };
  },
});

or you could send in a pr, what would allow this api:
const mySlate = slate(defaultConfig => ({
  ...defaultConfig,
  plugins: defaultConfig.plugins,
  Component: props => <MyWrapper><Component {...props} />
})

that would be more similar to the new plugin factories

0.10.0-beta.3 should have this new api, see the release log
won't solve it completly, but is a step forward

Wow, thats really cool of you. Thx!
I'm really sorry, but I don't get it. I didn't get this Renderer and my own Controls to work.
Maybe the slate plugin needs a small change? Like this:
  return {
    Component: (props: SlateProps) => (
      <Component
        Renderer={*settings.*Renderer}
        Controls={*settings.*Controls}
        plugins={plugins}
        translations={settings.translations}
        serializeFunctions={serializeFunctions}
        {...props}
      />
    ),

And do you have any idea, how to solve the serialization problem?
Actually I have replace serialize and unserialize directly (see my first post) to also serialize also my other props and not only the slate editorState. But this behavior didn't replace the serializeFunctions.
import { SlateState } from '@react-page/plugins-slate/lib/types/state';
import { ValueJSON } from 'slate';

export const unserialize = originalUnserialize => (
  slateState: SlateState,
): SlateState => {
  // eslint-disable-next-line @typescript-eslint/no-unused-vars
  const { importFromHtml, serialized, editorState, ...rest } = slateState;

  return {
    ...originalUnserialize(slateState),
    ...rest,
  };
};

export const serialize = originalSerialize => (
  slateState: SlateState,
): { serialized: ValueJSON } => {
  // eslint-disable-next-line @typescript-eslint/no-unused-vars
  const { editorState, ...rest } = slateState;

  return {
    ...originalSerialize(slateState),
    ...rest,
  };
};

@Fivedark can you show a more complete example? How do you use your unserialize and serialize functions? And what change do you propose in the slate plugin?

I wrapped my changes in *, but this wasn't flashy enought: I add the setting. to Renderer and Controls to use them from the settings and not the imported ones.
Like shown in my first post here, I added the following lines to my plugin config:
  serialize: serialize(slate.serialize),
  unserialize: unserialize(slate.unserialize),

@Fivedark I need a more complete example using the slate() plugin. Something like:
slate(originalConfig => ({
   ...originalConfig,
   serialize: // what do you suggest here?
   unserialize: // same same,
   Renderer: // what do you need here?

})

@macrozone I'm not sure, how it should look like, I just tried to use the API you added. But I didn't get it to work. So I had a look at your code changes and thought that there is missing something. The Renderer and so  in your Example is never called, in my opinion.
To make it more clear, here your example, but MyWrapper will not render:
const mySlate = slate(defaultConfig => {
const DefaultRenderer = defaultConfig.Renderer;
return {
  ...defaultConfig,
  plugins: defaultConfig.plugins,
  Renderer: props => <MyWrapper><DefaultRenderer {...props} /></MyWrapper>
}
}

For serialization, I think, it is maybe the best to extend the existing functions of the slate plugin to also handle other properties than the editorState.

@Fivedark which version do you use?

@Fivedark oooooh, sorry, sorry, sorry. There is indeed a bug! wait a moment...

@Fivedark can you try 0.10.2 or higher? (0.11.0 is latest)

@macrozone Thank you! I've tested 0.11.0 and the Renderer is working now, except the properties of my wrapper component. They are lost, because of the (un)serialization methods. Is it possible to extend the methods in the slate plugin like this:
const unserialize = ({
  importFromHtml,
  serialized,
  editorState,
  ...rest
}: // tslint:disable-next-line:no-any
SlateState): SlateState => {
  if (serialized) {
    // tslint:disable-next-line:no-any
    return { editorState: (Value.fromJSON as any)(serialized), ...rest };
  } else if (importFromHtml) {
    return { editorState: htmlToSlate(importFromHtml), ...rest };
  } else if (editorState) {
    return { editorState, ...rest };
  }

  return { ...createInitialState(), ...rest };
};

// tslint:disable-next-line:no-any
const serialize = ({
  editorState,
  ...rest
}: SlateState): { serialized: ValueJSON } => ({
  // tslint:disable-next-line:no-any
  serialized: (editorState.toJSON as any)(editorState),
  ...rest,
});

@Fivedark can you send in a PR?

Sorry, I'm not able to send in a PR at the moment, because I'm not able to install the react-page project on my windows machine anymore.
The problem is the new find in the clean command in package.json. The windows find command use another parameter structure than the linux version, so an error is occured.
yarn install v1.17.3
[1/5] Resolving packages...
success Already up-to-date.
$ npm-run-all clean bootstrap build:lib
yarn run v1.17.3
$ lerna run clean && find . -name tsconfig-es.tsbuildinfo  -delete && find . -name tsconfig.tsbuildinfo  -delete
lerna notice cli v3.6.0
lerna info Executing command in 13 packages: "yarn run clean"
lerna info run Ran npm script 'clean' in '@react-page/core' in 0.4s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/plugins-divider' in 0.4s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/plugins-default-native' in 0.5s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/ui' in 0.5s:
$ rimraf "lib/**/*" && rimraf "lib-es/*"
lerna info run Ran npm script 'clean' in '@react-page/plugins-html5-video' in 0.5s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/plugins-image' in 0.6s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/plugins-spacer' in 0.6s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/plugins-video' in 0.6s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/create-plugin-materialui' in 0.6s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/plugins-background' in 0.6s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/plugins-parallax-background' in 0.6s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/plugins-slate' in 0.4s:
$ rimraf "lib" && rimraf "lib-es"
lerna info run Ran npm script 'clean' in '@react-page/renderer' in 0.4s:
$ rimraf "lib" && rimraf "lib-es"
lerna success run Ran npm script 'clean' in 13 packages in 2.4s:
lerna success - @react-page/core
lerna success - @react-page/plugins-divider
lerna success - @react-page/plugins-html5-video
lerna success - @react-page/plugins-image
lerna success - @react-page/plugins-default-native
lerna success - @react-page/plugins-slate
lerna success - @react-page/plugins-spacer
lerna success - @react-page/plugins-video
lerna success - @react-page/create-plugin-materialui
lerna success - @react-page/plugins-background
lerna success - @react-page/plugins-parallax-background
lerna success - @react-page/renderer
lerna success - @react-page/ui
FIND: Parameterformat falsch
error Command failed with exit code 2.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "clean" exited with 2.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

Even on a MINGW64 (linux based console on windows) console crashes the install process, with an unspecified error and some permission problems.

@Fivedark you can comment out the find calls in package.json, maybe there is even a polyfill for find that works in both windows and linux/unix?
Hab leider lange nicht mehr auf windows entwickelt :-/

Sorry for my late response, but I'm working only two days a week on this project.
To create the PR I tried to comment out the find calls, but got some other problems. yarn install crashed because it couldn't find @react-page/core on ui and other packages. Maybe a poblem with symlinks in windows, but how could it work a few weeks ago?
Never mind I setup a docker container to run the project inside. It is not really comfortable, because watch isn't working, but I was able to check if the example is still working.

The new Slate Plugin API is working fine! Thanks again.


flutter升级到2.5.1以后ios模拟器运行报错

ld: in /Users/luowei/work/Flutter/SDK/flutter/.pub-cache/hosted/pub.dartlang.org/tencent_kit-2.1.0/ios/Libraries/TencentOpenAPI.framework/TencentOpenAPI(QQObject.o), building for iOS Simulator, but linking in object file built for iOS, for architecture arm64

见 issues/54


ci: add prow OWNERS file

Strengthen reviewing controlling
add approvers and reviewers from community team members, but limit the contributors to this repository.
Close #360
Ref: https://github.com/tikv/community/blob/master/teams/tikv/team.json

LGTM


[BUG] .NET Maui throws build exception on iOS

Description
.NET Maui throws the following exception on iOS when I try to build my project
Severity	Code	Description	Project	File	Line	Suppression State
Error		clang++ exited with code 1:
ld: framework not found System
clang: error: linker command failed with exit code 1 (use -v to see invocation)	Myproject	C:\Program Files\dotnet\packs\Microsoft.iOS.Sdk\16.2.1024\targets\Xamarin.Shared.Sdk.targets	1225

Code
I tried with
<AdditionalArgs>
    --linkskip=SkiaSharp.Extended.UI.Maui
</AdditionalArgs>

and by installing the other dependencies directly into the prject and then adding a LinkSkip like so:
 <Target Name="AddSkia" Condition="'$(TargetFramework)'=='net7.0-ios'" AfterTargets="_LoadLinkerOutput" BeforeTargets="_ComputeLinkNativeExecutableInputs">
		<ItemGroup>
			<_LinkerFrameworks Include="SkiaSharp" />
			<_LinkerFrameworks Include="SkiaSharp.Views.Maui.Controls" />
			<_LinkerFrameworks Include="SkiaSharp.Extended.UI.Maui" />
			<_LinkerFrameworks Include="SkiaSharp.Views.Maui.Core" />
		</ItemGroup>
	</Target>

getting the same error...
Basic Information

Version with issue:  2.0.0-preview 61
Last known good version:  --
IDE:  Visual Studio and Visual Studio for Mac
Platform Target Frameworks:

iOS:  16.2, 14.3

Target Devices:

iPhone SE and X
Simulator

Exact same problem here, also running iOS 16.2 and XCode 14.3.
It seems this should be working since 14.3 is now fully supported as per #17561


refactor: make use of the consul server address in the configuration

This PR address an issue when the consul provider. The current behaviour is such that one will have to pass in as an option the consul server address even if it is set in the configuration before the provider can pick it. That will result in dial tcp <IP_ADDRESS>:8500: connect: connection refused". The only way to solve that is to do something like this:
serverAddr := "consul.contoso.com:8600"
consul.NewWithConfig(&api.Config{Address: serverAddr}, consul.WithConsulServerAddress(serverAddr))

With this PR one just have to do this:
serverAddr := "consul.contoso.com:8600"
consul.NewWithConfig(&api.Config{Address: serverAddr})

Very nice!


feat(GroupedSelect) Support Grouped Select

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature
What is the new behavior (if this is a feature change)?
Grouped Select support
Please check if the PR fulfills these requirements

[x] The commit messages follow our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] A unit test has been written for this change.
[x] Running npm run build produced a successful build. (Unit testing can be done by running npm test;)
[x] My code has been linted. (npm run lint to do this. npm run build will fail if there are files not linted.)

Please provide a screenshot of this feature before and after your code changes, if applicable.
Other information:

Current coverage is 84.91% (diff: 100%)

Merging #278 into master will not change coverage

@@             master       #278   diff @@
==========================================
  Files            18         18
  Lines           643        643
  Methods         140        140
  Messages          0          0
  Branches        151        151
==========================================
  Hits            546        546
  Misses           97         97
  Partials          0          0

Powered by Codecov. Last update cd3ac30...0b50ffd


Investors are stored as CPID 0000000 in CBlockIndex

The CPID that is stored in blocks seems to be stored as 0x00 in CBlockIndex when staked by an investor. The actual boinc block contains the correct information
    result.push_back(Pair("CPID", bb.cpid));
    result.push_back(Pair("CPID_index", blockindex->GetCPID()))

 ./gridcoinresearchd -testnet getblockbynumber 457384
...
    "CPID" : "INVESTOR",
    "CPID_index" : "00000000000000000000000000000000",

This probably stems from #221 which changed the internal CPID representation from a string to an uint128_t.

this part "result.push_back(Pair("CPID_index", blockindex->GetCPID()))" you used just for show how lockindex->GetCPID() return 0x00? Can't find it in code so I am asking.

Confirmed. This is upsetting but everything appears to be working.

Note that the blockchain must be reindexed for #1058 to take effect.


New terminolgy - ExperimentalMeasurement

@lzehl @UlrikeS91 Following the ontology meeting, we consider adding a new terminology "experimental measurement".
Suggested terms for this terminology would be the following (not an exhaustive list):

action potential
alpha activity
beta activity
gamma activity
inhibitory postsynaptic potential
inhibitory postsynaptic current
excitatory postsynaptic potential
excitatory postsynaptic current
local field potential
miniature inhibitory postsynaptic current
multi-unit activity
single-unit activity
slow oscillation
spike time dependent plasticity
spontaneous inhibitory postsynaptic current

@apdavison Would this fit your needs for the ephys extension as well?

We already have "measured quantity", which mostly contains terms at the sub-cellular level at the moment (https://github.com/HumanBrainProject/openMINDS_controlledTerms/tree/v1/instances/measuredQuantity), but I think more macroscopic quantities like some of those in the list above would also fit (all of the "potential"s, "current"s, "activity"s).
However, some of the terms in the list, e.g. spike time dependent plasticity, are not measured quantities, but more "studied phenomena".

As far as I understand, this is actually to replace the "measured quantity" that is currently there now (please confirm @lzehl ). The reason for this is that some of these quantities are measured and some are calculated, according to Tom. Hence, this might need to be merged. We wanted to discuss this on GitHub to align the different properties.

@apdavison the idea was indeed to merge the macroscopic quantities into the "measured quantity" list and rename this terminology to  "experimental measurement" which fits better with the ontological interpretation of the joint terms.
Could you elaborate which terms exactly besides "spike time dependent plasticity" you would consider rather as "phenomena" and why?
My problem with "phenomena" vs "measured quantity" is that most phenomena are measured (directly or indirectly) and then what is measured is called the same as the phenomena (or the other way around). For example all potentials are measured biological phenomena (e.g. membrane potential).
The idea with "experimental measurement" to loosen the context a bit and join all terms that can be/are typically measured in experiments and could also be potential study targets (e.g., also "temperature", "BOLD signal", "peak latency", "long-term potentiation", "long-term depression", "light intensity", etc.)
Here a joint list of the term in "measured quantity" and the new terms with my assessment which of them could also classify as biological phenomena:

chloride reversal potential (biological phenomena)
compensation current
input resistance
liquid junction potential (biological phenomena)
measured holding potential (why not just holding potential?)
membrane potential (biological phenomena)
seal resistance
series resistance
action potential (biological phenomena)
alpha activity (biological phenomena)
beta activity (biological phenomena)
gamma activity (biological phenomena)
inhibitory postsynaptic potential (biological phenomena)
inhibitory postsynaptic current (biological phenomena)
excitatory postsynaptic potential (biological phenomena)
excitatory postsynaptic current (biological phenomena)
local field potential (biological phenomena)
miniature inhibitory postsynaptic current (biological phenomena)
multi-unit activity (biological phenomena)
single-unit activity (biological phenomena)
slow oscillation (biological phenomena)
spike time dependent plasticity (biological phenomena)
spontaneous inhibitory postsynaptic current (biological phenomena)

@apdavison what do you think about our approach? do you have any better idea of how to handle this without introducing too many terminologies which are difficult to maintain regarding the decision of what term should go where? (I would also like to avoid repetition of terms in different terminologies)

Could you explain what is motivating this proposal? (i.e. what is the use case, how would this information be used in the KG and the UI).
It seems it is less closely related to "measured quantity" than I initially thought.
For ephys it is important that we can check that the units provided are consistent with what is being measured, so the physical dimensions of what is being measured are required, e.g.:

chloride reversal potential: voltage (e.g. mV)
input resistance: electrical resistance (e.g. Mohm)
beta activity: unclear, could be frequency, or power at a given frequency
single-unit activity: time^-1 (e.g. spikes/second)
slow oscillation: frequency (e.g. Hz) - but "slow" is irrelevant in this use case, it would be "oscillation frequency"
spike time dependent plasticity: completely unclear, there are many different attributes of STDP you could measure.

Probably we are looking at two schemas, with not much repetition/overlap. I don't think "experimental measurement" is a good name for the new schema given the range of terms you propose to include. "biological phenomenon", or "neuroscience concept" seem like better fits.
p.s. "(why not just holding potential?)" - because we also have "target holding potential", which is a parameter rather than a measurement.

@apdavison motivation is that we want to cover as many terms in the openMINDS libraries of controlled terms as possible. Currently there are many undefined term suggestions around "biological phenomenons" or "neuronal signals". The list above is an extraction of those undefined terms.
The "terminology" divisions of controlled terms into terminology schemas was mainly done to be able to target a subset of controlled terms as linked types for certain properties. For this reason the openMINDS terminologies do not follow necessarily the ontological super-classes which are more fine-grained and not necessarily intuitive for the typical community. Also we don't want openMINDS to rebuild the relations between terms, but want to leave this to the ontology.
I'm happy about any suggestions for the terms discussed above. It could be one or two terminologies.
General guidelines for terminologies:

Terms should be registered once, meaning in one terminology, not multiple ones (avoiding duplicates also across terminologies).
Adding new terms to the terminologies should be easy meaning avoiding classifications which are not intuitive to extend (avoiding the repeating question: should new term go to terminology A or B?).
Terms of one terminologies should be potentially meaningful in context of one property. A property could expect terms from one or multiple terminologies (e.g., subject/ageCategory -> AgeCategory terms, datasetVersion/studyTarget -> all Terminologies of category studyTarget, etc.) .

@apdavison did we come to a solution for this issue? if not do we need to have a meeting to discuss in person?

@apdavison @UlrikeS91 : @MaaikevS @tgbugs and I discussed this one again. here our result :
We keep all "single-value" stuff that can be directly or indirectly measured (e.g. membrane potential, chloride reversal potential, input resistence) in MeasuredQuantity. @apdavison here it would be good though to replace "measuredHoldingPotential" with just "holdingPotential" and move the "measured" vs "target"(?) to the property name (and/or instruction) of the schema where you use it.
All more complex things (e.g. local field potential, alpha oscillation, single-unit activity, etc) we keep under BiologicalProcess (this would be a new terminology grouping).
Both terminologies ( MeasuredQuantity and BiologicalProcess ) should be added to the potential study target list (and later also be an option for keywords ).
We hope this is a good solution which satisfies all our needs. Do you agree?

Sounds good to me, but I also don't have a strong opinion about this anyway.

@lzehl sounds fine to me. I've fixed the "holding potential" issue in #230

@apdavison and @UlrikeS91 perfect! The PR #230 is already merged.
@MaaikevS do you want to take over the PR for the BiologicalProcess schema + instances (initial selection)? Please let me know if you don't have the time at the moment.

If I interpret this correctly, the only open issue here is the biological process, right? I made an issue for this specifically and close this issue for now. @lzehl feel free to reopen it, if my interpretation was wrong 🙂

The earlier discussion in this issue refers to many of these concepts as biological phenomenon, whereas the conclusion is to make a new schema called BiologicalProcess. I think BiologicalPhenomenon is much better because none of the concepts listed in the first post fit well with the definition of a process. A process is generally understood as " a series of actions or operations conducing to an end" (merriam webster).
On the other hand, a phenomenon is defined as "an observable fact or event". I agree that this is similar to a measured quantity but I think it has some notable differences. Let's take an action potential as an example. What is measured is the membrane potential whereas the action potential is an observable event that happens in a short time window. It is also not a process, because it does not lead to anything. The propagation of the action potential on the other hand might be considered a process...?
When it comes to oscillations, they are definitely not processes (its not even clear what the biological fingerprint is or if it has biological relevance), they are quantities that are derived from measurements. You don't measure the oscillations, you measure the extracellular potential or the EEG and you compute the power of the signal within frequency bands. They are observable and they are often also observed with time intervals (events) so they can also fall in under the phenomena definition.
For some of the others e.g inhibitory postsynaptic potential, inhibitory postsynaptic current, excitatory postsynaptic potential, excitatory postsynaptic current, they are measured quantities (membrane potentials), but at specific locations... I therefore do not think it is right to classify them as phenomena, since they are more directly related to actual measurements (also they are not considered events).

On second thought, IPSP/EPSP/IPSC/EPSC are similar to action potentials, so they should not be considered measured quantities...

@ehennestad you are fully right. We agreed in 'measured quantities' we only keep single valued elements (e.g., membrane potential). Everything more complex should be registered as BiologicalProcess. We can also name this terminology BiologicalPhenomenon @UlrikeS91 & @tgbugs any objections?

I like BiologicalPhenomenon better. Based on the terms that I found for the terminology, it would make more sense.


Update initial cf deployment's wait-time suggestions

Hey @bwasmith , thanks for pointing this out. Another way we could solve this is by updating the deploy instructions to include the -n flag, which makes the command non-interactive and automatically "approves" the deploy:
bosh -n deploy cf-deployment/cf-deployment.yml ....

Would that be better?

I don't know.
As someone who uses the bosh cli somewhat regularly, I think it is important, in general, to know about deployment diffs (difference between the new manifest and the currently deployed manifest)
That being said, onboarding users will come across this later in the process when they upgrade diego cells. And, with this initial cf deployment, it is not important to see deployment diffs.

I'll update the document

Rebased off master to include bbl commit as well


Fix typos in chapter 2.3 and 3.1

Fixes several typos in explainers and code cells.

ACK. Thanks!


fix(locale): correcting language to use "kuki" instead of "cookie" for lo…

📚 Description
change language to use "kuki" instead of "cookie" for Bahasa
📝 Checklist

[x] All commits follow the Conventional Commit format
[x] The PR's title follows the Conventional Commit format

:tada: This PR is included in version 8.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


CI test before service type support PR27

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes (Trello link here OR reason to fix if not on Trello)
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)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] I have performed a self-review of my own code
[ ] New and existing system tests pass locally with my changes (when applicable)
[ ] Any dependent changes have been merged and published in downstream modules

@lij-oci Do we still need this draft PR? It looks like we resolved your questions and have moved on.


uproot4.lazy fails to read TBranch of type std::vector

uproot4.lazy fails to read branches of type std::vector<TLorentzVector> that uproot4.open and uproot4.concatenate read successfully.
I am using uproot version 4.0.11, ROOT 6.20/00.
The following script reproduces the problem:
import ROOT
import uproot4
from importlib.metadata import version

# some C++ code that generates an example file
ROOT.gInterpreter.GenerateDictionary("std::vector<TLorentzVector>", "vector;TLorentzVector.h")
ROOT.gInterpreter.ProcessLine("""
#include <vector>
#include "TLorentzVector.h"

void write_file() {
    TFile tfile("example.root", "RECREATE");
    TTree tree("tree", "tree");
    std::vector<TLorentzVector> fourMomentum;
    tree.Branch("fourMomentum", &fourMomentum);
    fourMomentum.push_back({1.0, 2.0, 3.0, 4.0});
    tree.Fill();
    tree.AutoSave();
    return;
}
""")

if __name__ == "__main__":
    ROOT.write_file()

    # check versions
    print(version("uproot")) # prints: 4.0.11
    print(ROOT.gROOT.GetVersion()) # prints: 6.20/00

    # read with uproot
    tree = uproot4.open("example.root:tree")
    print(tree.arrays(library="ak").fourMomentum)
    # prints: [[{fP: {fX: 1, fY: 2, fZ: 3}, fE: 4}]]

    # read with uproot concatenate
    tree = uproot4.concatenate(["example.root:tree"], library="ak")
    print(tree.fourMomentum)
    # prints: [[{fP: {fX: 1, fY: 2, fZ: 3}, fE: 4}]]

    # read lazily with uproot
    tree = uproot4.lazy(["example.root:tree"], library="ak")
    print(tree.fourMomentum) # raises ValueError

This produces the error message:
/home/epp/phskaj/work/t2k/ncfgd7/ncfgd/env/ncfgd/lib/python3.8/site-packages/uproot/reading.py:186: FutureWarning: XRootD 4.11.3 is not fully supported; either upgrade to 5.2.0+ or set

    open.defaults["xrootd_handler"] = uproot.MultithreadedXRootDSource

  warnings.warn(message, FutureWarning)
TTree::Bronch:0: RuntimeWarning: Using split mode on a class: TLorentzVector with a custom Streamer
4.0.11
6.20/00
[[{fP: {fX: 1, fY: 2, fZ: 3}, fE: 4}]]
[[{fP: {fX: 1, fY: 2, fZ: 3}, fE: 4}]]
Traceback (most recent call last):
  File "possible_bug_in_uproot.py", line 42, in <module>
    print(tree.fourMomentum) # raises ValueError
  File "/home/epp/phskaj/work/t2k/ncfgd7/ncfgd/env/ncfgd/lib/python3.8/site-packages/awkward/highlevel.py", line 1278, in __str__
    return self._str()
  File "/home/epp/phskaj/work/t2k/ncfgd7/ncfgd/env/ncfgd/lib/python3.8/site-packages/awkward/highlevel.py", line 1298, in _str
    return ak._util.minimally_touching_string(
  File "/home/epp/phskaj/work/t2k/ncfgd7/ncfgd/env/ncfgd/lib/python3.8/site-packages/awkward/_util.py", line 1567, in minimally_touching_string
    rgt = next(rightgen)
  File "/home/epp/phskaj/work/t2k/ncfgd7/ncfgd/env/ncfgd/lib/python3.8/site-packages/awkward/_util.py", line 1553, in forever
    for token in iterable:
  File "/home/epp/phskaj/work/t2k/ncfgd7/ncfgd/env/ncfgd/lib/python3.8/site-packages/awkward/_util.py", line 1509, in backward
    for token in backward(x[i], sp):
  File "/home/epp/phskaj/work/t2k/ncfgd7/ncfgd/env/ncfgd/lib/python3.8/site-packages/awkward/partition.py", line 231, in __getitem__
    return PartitionedArray.from_ext(self._ext.getitem_at(where))
ValueError: generated array does not conform to expected form:

{
    "class": "ListOffsetArray64",
    "offsets": "i64",
    "content": {
        "class": "RecordArray",
        "contents": {
            "@fBits": "uint32",
            "@fUniqueID": "uint32",
            "@instance_version": "uint16",
            "@num_bytes": "uint32",
            "@pidf": "uint16",
            "fE": "float64",
            "fP": {
                "class": "RecordArray",
                "contents": {
                    "@fBits": "uint32",
                    "@fUniqueID": "uint32",
                    "@instance_version": "uint16",
                    "@num_bytes": "uint32",
                    "@pidf": "uint16",
                    "fX": "float64",
                    "fY": "float64",
                    "fZ": "float64"
                },
                "parameters": {
                    "__record__": "TVector3"
                }
            }
        },
        "parameters": {
            "__record__": "TLorentzVector"
        }
    }
}

but generated:

{
    "class": "ListOffsetArray64",
    "offsets": "i64",
    "content": {
[example.zip](https://github.com/scikit-hep/uproot4/files/6907761/example.zip)

        "class": "RecordArray",
        "contents": {
            "fP": {
                "class": "RecordArray",
                "contents": {
                    "fX": "float64",
                    "fY": "float64",
                    "fZ": "float64"
                },
                "parameters": {
                    "__record__": "TVector3"
                }
            },
            "fE": "float64"
        },
        "parameters": {
            "__record__": "TLorentzVector"
        }
    }
}

(https://github.com/scikit-hep/awkward-1.0/blob/1.2.3/src/libawkward/virtual/ArrayGenerator.cpp#L46)```

I have also attached example.root to this issue.
example.zip

My awkward version in the above test was: 1.2.3.
I have updated to latest (1.4.0) and see the same error.

I'll take a look at example.zip, although it's strange that it fails while this one succeeds (also a std::vector<TLorentzVector>):
>>> import uproot, skhep_testdata
>>> skhep_testdata.data_path("uproot-HZZ-objects.root")
'/home/jpivarski/.local/skhepdata/uproot-HZZ-objects.root'
>>> f = uproot.open(skhep_testdata.data_path("uproot-HZZ-objects.root"))
>>> t = f["events"]
>>> t.show()
name                 | typename                 | interpretation
---------------------+--------------------------+-------------------------------
jetp4                | std::vector<TLorentzV... | AsJagged(AsStridedObjects(M...
jetbtag              | std::vector<float>       | AsJagged(AsDtype('>f4'), he...
jetid                | std::vector<bool>        | AsJagged(AsDtype('bool'), h...
muonp4               | std::vector<TLorentzV... | AsJagged(AsStridedObjects(M...
muonq                | std::vector<int32_t>     | AsJagged(AsDtype('>i4'), he...
muoniso              | std::vector<float>       | AsJagged(AsDtype('>f4'), he...
electronp4           | std::vector<TLorentzV... | AsJagged(AsStridedObjects(M...
electronq            | std::vector<int32_t>     | AsJagged(AsDtype('>i4'), he...
electroniso          | std::vector<float>       | AsJagged(AsDtype('>f4'), he...
photonp4             | std::vector<TLorentzV... | AsJagged(AsStridedObjects(M...
photoniso            | std::vector<float>       | AsJagged(AsDtype('>f4'), he...
MET                  | TVector2                 | AsStridedObjects(Model_TVec...
MC_bquarkhadronic    | TVector3                 | AsStridedObjects(Model_TVec...
MC_bquarkleptonic    | TVector3                 | AsStridedObjects(Model_TVec...
MC_wdecayb           | TVector3                 | AsStridedObjects(Model_TVec...
MC_wdecaybbar        | TVector3                 | AsStridedObjects(Model_TVec...
MC_lepton            | TVector3                 | AsStridedObjects(Model_TVec...
MC_leptonpdgid       | int32_t                  | AsDtype('>i4')
MC_neutrino          | TVector3                 | AsStridedObjects(Model_TVec...
num_primaryvertex    | int32_t                  | AsDtype('>i4')
trigger_isomu24      | bool                     | AsDtype('bool')
eventweight          | float                    | AsDtype('>f4')
>>> t["jetp4"].array()
<Array [[], [{fP: {, ... fE: 33.9}], []] type='2421 * var * TLorentzVector["fP":...'>

Nevermind: I missed the fact that you saw this behavior in uproot.lazy and not in eager array-reading. Got it.

Yes that's right. It seems to just be lazy causing errors. Everything else seems to work as expected.
I have just tried the example file that you are looking at and I see the same error if I do:
wget "https://github.com/scikit-hep/scikit-hep-testdata/blob/main/src/skhep_testdata/data/uproot-HZZ-objects.root?raw=true" -O hzz.root
python -c "import uproot4; print(uproot4.lazy('hzz.root:events'));"

So it seems to be reproducible with different input files. Of course, that doesn't eliminate the possibility that it might just be a problem on my system / installation.

It's not an installation issue; PR #403 should fix it.
The fields that start with "@" symbols are TObject members that are unlikely to be meaningful in an analysis, but they're necessary for deserialization. The default Interpretations drop these fields (I put the "@" sign there as an indicator to later code of what to drop). In lazy arrays, the reading is deferred for later, but there are a lot of operations that can proceed if they only know the type of the data, so lazy arrays have a Form object (detailed type) to answer those questions without invoking a disk-read. However, when the array is finally read, if its actual type differs from what it's been telling everybody, that needs to be an error. In this case, the "@" fields were not removed from the Form as they are removed from the data that gets read—this was inconsistent, and Awkward Array (which knows nothing about all this) raised an error because of the inconsistency. That's what its error was saying: the first Form had a bunch of fields with "@" signs in them; the second didn't. The fix was to make the Forms consistent with the data by removing fields that start with "@" signs.
That's the long explanation.


[TypingIndicator] Issue: Does not work in Server list

Screenshots

Information (please complete the following information):
Stable 123887 (00d8cb1)
BetterDiscord 1.5.3
Host 1.0.9004 Windows 10 64-Bit (10.0.19044

The plugin still functions as normal, this only affects the indicator that's supposed to appear in the server list

yes

Still not working on serverlist


Aetest processor for failed assertions

Hello folks,
I have set of tests with various assertions. After each test execution, we get a TestResult object that contains info about result code, name, tims. But there is no info about error/fail reason in case of test failure.
I have found a temporary workaround using @aetest.processor feature (https://pubhub.devnetcloud.com/media/pyats/docs/aetest/processors.html?highlight=processors). But it has one drawback - it catches only exceptions. That means that I have to replace all assert statements with a custom implementation of the Exception class and raise exceptions in case some condition was not met. That is nasty and wrong approach.
So my question is - how can I get a failed assertion message in a more friendly way?
Maybe I'm missing something obvious?

when you do self.failed() or self.passed(), the API it self also supports, reason, and data
self.failed('because I needed to fail, data = {})
https://pubhub.devnetcloud.com/media/pyats/docs/aetest/results.html#
if you are using assert i think that's not being filled - but if you use result apis it would help.
does that answer the question?

Thanks, @simingy! It did the trick!


Build native and not quilt

Hello @androniychuk, this PR seems to contain  more than just switching the source format from quilt to native, can you provide that both in the commit and MR description ?

the definition of native means there are no patches, so that summarizes everything

@androniychuk but it does not explain why we removed an existing patch


ACSet Homomorphism Serialization

We need to extend the write_json_acset function to write CSet homomorphisms. @kris-brown, have you done something similar for any of your projects?

I have not. No special insights - I’d just do “dom” “codom” and “components” keys. If we wanted to do diagram to json then this would be a special case for walking arrow shape.

Yeah, the diagram of ACSet serialization would make sense. I guess we would store the FreeDiagram ACSet to store the shape of the diagram and then each of the objects in the diagram in a list and then each of the arrows as just a named tuple of the underlying components. We should probably do that rather than a special case for a single arrow.
Is there anything to do about redundancy? It seems like for many cases the Dom, Codom, components encoding will be wasteful.


powermanager - New option to automatically calibrate the battery

Sets the battery calibration value after 3 hours of charging without reloads.

Nice idea - thanks!


lax silently zeros large integers outside x64 mode

Repro, with jax_enable_x64=False:
>>> from jax import lax
>>> lax.neg(1 << 32)
DeviceArray(0, dtype=int32)

If the input is too large for int64, it leads to an error. I would expect a similar error above.
>>> lax.neg(1 << 64)
---------------------------------------------------------------------------
OverflowError                             Traceback (most recent call last)
<ipython-input-6-785fd456fe87> in <module>()
----> 1 lax.lt(483290843902849032849023842309,<PHONE_NUMBER>32840239842390480983420932849023)

/usr/local/lib/python3.6/dist-packages/jax/lax/lax.py in lt(x, y)
    364 def lt(x: Array, y: Array) -> Array:
    365   r"""Elementwise less-than: :math:`x < y`."""
--> 366   return lt_p.bind(x, y)
    367
    368 def convert_element_type(operand: Array, new_dtype: DType) -> Array:

/usr/local/lib/python3.6/dist-packages/jax/core.py in bind(self, *args, **kwargs)
    271     top_trace = find_top_trace(args)
    272     if top_trace is None:
--> 273       return self.impl(*args, **kwargs)
    274
    275     tracers = map(top_trace.full_raise, args)

/usr/local/lib/python3.6/dist-packages/jax/interpreters/xla.py in apply_primitive(prim, *args, **params)
    227   """Impl rule that compiles and runs a single primitive 'prim' using XLA."""
    228   compiled_fun = xla_primitive_callable(prim, *unsafe_map(arg_spec, args), **params)
--> 229   return compiled_fun(*args)
    230
    231 @cache()

/usr/local/lib/python3.6/dist-packages/jax/interpreters/xla.py in _execute_compiled_primitive(prim, compiled, result_handler, *args)
    326 def _execute_compiled_primitive(prim, compiled, result_handler, *args):
    327   device, = compiled.local_devices()
--> 328   input_bufs = [device_put(x, device) for x in args if x is not token]
    329   out_bufs = compiled.execute(input_bufs)
    330   if FLAGS.jax_debug_nans:

/usr/local/lib/python3.6/dist-packages/jax/interpreters/xla.py in <listcomp>(.0)
    326 def _execute_compiled_primitive(prim, compiled, result_handler, *args):
    327   device, = compiled.local_devices()
--> 328   input_bufs = [device_put(x, device) for x in args if x is not token]
    329   out_bufs = compiled.execute(input_bufs)
    330   if FLAGS.jax_debug_nans:

/usr/local/lib/python3.6/dist-packages/jax/interpreters/xla.py in device_put(x, device)
    113
    114 def device_put(x, device: Optional[Device] = None):
--> 115   x = canonicalize_dtype(x)
    116   try:
    117     return device_put_handlers[type(x)](x, device)

/usr/local/lib/python3.6/dist-packages/jax/interpreters/xla.py in canonicalize_dtype(x)
    134   typ = type(x)
    135   handler = canonicalize_dtype_handlers.get(typ)
--> 136   if handler: return handler(x)
    137   for typ in typ.mro():
    138     handler = canonicalize_dtype_handlers.get(typ)

/usr/local/lib/python3.6/dist-packages/jax/interpreters/xla.py in _canonicalize_python_scalar_dtype(typ, x)
    145 def _canonicalize_python_scalar_dtype(typ, x):
    146   return onp.asarray(
--> 147       x, dtypes.canonicalize_dtype(dtypes.python_scalar_dtypes[typ]))
    148
    149 canonicalize_dtype_handlers: Dict[Any, Callable] = {core.Unit: identity}

/usr/local/lib/python3.6/dist-packages/numpy/core/_asarray.py in asarray(a, dtype, order)
     83
     84     """
---> 85     return array(a, dtype, copy=False, order=order)
     86
     87

OverflowError: Python int too large to convert to C long

Looking at this a bit, it turns out JAX's matches Numpy's here:
>>> import numpy as np
>>> np.array(1 << 32, dtype='int32')
array(0, dtype=int32)

I think it's a bit bigger problem for JAX with the 32-bit default, because the user may not be thinking about integer overflow in this context:
>>> import jax.numpy as jnp
>>> jnp.array(1 << 32)
DeviceArray(0, dtype=int32)

Where I discovered this issue was looking into a bug that manifested as breaking JIT invariance in the jax.random.poisson implementation. Simplified version of the issue looks like this:
import jax.numpy as np
from jax import jit

a = 0
b = jnp.iinfo(jnp.int64).max

def less(a, b):
  return a < b

print(less(a, b))
# True
print(jit(less)(a, b))
# False

And this comparison was deep inside a while_loop that was inside a scan, and the result was random values with the wrong distribution. So the effects of this can be quite subtle & pernicious in practice.


cssrem can't use ,  px Cannot be converted to  rem

VSCode Version:
OS Version:

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

Please give more information and steps to reproduce.

Sorry, because IntelliSense for CSS class Names in HTML shows only one line by default and does not expand, I apologize for the inconvenience caused.

Sorry, I still don't know how to reproduce. How did you get the second screenshot?
Is this because the suggest widget did not expand fully?

Yes, it is because of this plug-in: IntelliSense for CSS class names in HTML, the default display only a line, it needs the drop-down to display all suggest that, in fact, unit conversion is complete, just because of the similar to overflow: hidden this attribute let I didn't see, so I thought it was the cssrem plug-in problems, has now been solved, the problem I apologize.As for the picture, it is the code hint that has been expanded, indicating that I can see the unit conversion. The picture may be distorted because of cross-domain, and I can do nothing about it. Sorry for troubling you.

Can the issue be closed then?

yes, yes,  thanks


Update speech docs to remove incorrect warnings.

@dhermes Once this is merged, is it possible to only regenerate the docs? (There is no code change so I hate to do a release just for this.)

@lukesneeringer Which docs? Some docs get built on every "push" build.


Linting not working

In a project with a mix of .js and .jsx files, no lint warnings or errors appear in the editor if you do mistakes, e.g. bad syntax.
In VS Code using the official Deno extension such lint errors are reported in the editor, so I don't think it's a problem with my Deno project.
I haven't tried .ts or .tsx files yet with Nova and this extension, so I don't know if they lint as expected.

Ok, linting is not working for .ts files either:

Does it need to be enabled somehow?
I'm using the latest Deno, and the CLI is installed:
$ deno --version
deno 1.12.2 (release, x86_64-apple-darwin)
v8 <IP_ADDRESS>
typescript 4.3.5

Possible clues...
When I open a Nova Deno project with an open .js file, here is what appears in the extension console:

With a .jsx file:

Issue persists after downgrading Deno to the version mentioned in the extension readme:
deno upgrade --version 1.10.3

I think I've fixed this in v0.2 when I refactored user configurations. It should be up in the extension library soon, so let me know if it fixes the issue for you.

@jaydenseric Are you still having this problem?

I think this is working now, thanks for your work :)
I've been on Node.js projects the past few days, but am back on Deno work again now so I'll be able to try out the fix more thoroughly. I did notice the other day the linting wasn't working for a bit, but I managed to coax it into working again by restarting the editor or something, I can't remember. If it happens again I'll report back.


support plus, minus operators

I want to use these operators(operator+, operator-) in multi_index.

We are trying to follow the C++ convention of not adding operations to the iterators that would give the developer an impression of a low cost computation when in fact its implementation requires a large amount of computation.
To provide some context, look at the iterators for std::vector vs std::list. An std::vector uses a RandomAccessIterator which does implement the plus and minus operator. On the other hand, an std::list uses only a BidirectionalIterator which does not implement the plus and minus operators, just the increment and decrement operators.
This should hopefully make sense considering that a vector consists of its fixed-size elements located contiguously in memory which makes jumping from one element in the vector to any other a constant time operation (since it enables random access to any of its elements by just constructing the appropriate address). But a list is implemented by holding pointers to the previous and next nodes within each node of the list. That means the only way to, for example, add some number N to an iterator pointing to some element of a list is to call the function that advances to the next element (the advancing operation is O(1)) N number of times which  makes the overall operation O(N).
The eosio::multi_index class is implemented in a way that makes it analogous to std::list in terms of traversing through the sequence of elements in any given index. (In reality it is a little worse in time complexity because the native EOSIO side must map the WebAssembly-side handle integer value to a particular object managed by boost::multi_index, which is not a O(1) operation but rather an O(logC) operation where C is the number of cached items in the iterator cache within the execution context of the action.) Implementing const_iterator operator+(int n) would requiring calling const_iterator& operator++() repeatedly n times.
We do not want to encourage contract developers to use such an addition operation by adding it into CDT because its existence may mislead contract developers into false belief that it is just as cheap as adding an integer to an iterator of std::vector. If a contract really needs such functionality, they can simply use std::advance.


[FEATURE] Add Password to join team or Only let team owner add members to the team

Is your feature request related to a problem? Please describe.
Anyone can join any team and spy :(
Describe the solution you'd like
Only Team owners will be able to invite players to the team (Toggle option in config.yml) Or add a password to join the team
Describe alternatives you've considered
Idk
Additional context
?

You can toggle if a team is invite-only or open to everyone using the command /team open.
You can change the permissions of what rank a player must be to invite other players in teampermissions.yml

check the section shown above.
If you have any other questions, let me know

Thanks


fix __call() override

The __call function in src/Bican/Roles/HasRole.php causes issues with Laravel's where() and possibly other methods.
For example:
User::where('role_id', '=', 1);

Gives me:
BadMethodCallException in HasRole.php line 200:
Method [where] does not exist.

I believe it's because you are overriding the __call function in Illuminate\Database\Eloquent\Model. So I've pulled code out of Model and put it in HasRole so it will still work. This is probably not the best way to fix the issue but it works for now.

Yeah, you're right. Thanks for PR.
What if we do it like this?
    public function __call($method, $parameters)
    {
        if (starts_with($method, 'is'))
        {
            // code
        }
        elseif (starts_with($method, 'can'))
        {
            // code
        }

        return parent::__call($method, $parameters);
    }

I think this is the best and probably also the only solution. What do you think?

Ah, yes. I think so, too. I didn't realize I could parent::_call()!
Thanks,
Ryan
—
Ryan Kent
Interphased
http://interphased.com
On Sun, Feb 8, 2015 at 5:46 PM, Roman Bičan<EMAIL_ADDRESS>wrote:

Yeah, you're right. Thanks for PR.
What if we do it like this?
    public function __call($method, $parameters)
    {
        if (starts_with($method, 'is'))
        {
            // code
        }
        elseif (starts_with($method, 'can'))
        {
            // code
        }
        return parent::__call($method, $parameters);
    }

I think this is the best and probably also the only solution. What do you think?
Reply to this email directly or view it on GitHub:
https://github.com/romanbican/roles/pull/3#issuecomment-73437037


Changed new Buffer() to Buffer.from()

new Buffer() has been depreciated.
fixes #1272

Thank you!


Add "min_exponent" to "LogTickFormatter"

This enables to opportunity to print ticks without exponent on axis, if the axis of logarithmic.

[ ] issues: fixes #11007

Is is obsolet sincem the code is included in #11185.


Move from Kubernetes Platfrom v 1.14 to v 1.25 for all operator test cases

Test name
Status

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-self-healing
failure

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

service-per-pod
passed

sidecars
passed

smart-update
failure

tls-cert-manager
passed

users
passed

version-service
passed

We run 30 out of 30

commit: https://github.com/percona/percona-server-mysql-operator/pull/471/commits/882d39c7c49de32c6879250c37c9c1c1359ac295
image: perconalab/percona-server-mysql-operator:PR-471-882d39c

Test name
Status

async-ignore-annotations
passed

auto-config
passed

config
passed

config-router
passed

demand-backup
passed

gr-demand-backup
passed

gr-demand-backup-haproxy
passed

gr-haproxy
passed

gr-ignore-annotations
passed

gr-init-deploy
passed

gr-one-pod
passed

gr-recreate
passed

gr-scaling
passed

gr-self-healing
passed

gr-tls-cert-manager
passed

gr-users
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring
passed

one-pod
passed

operator-self-healing
passed

recreate
passed

scaling
passed

service-per-pod
passed

sidecars
passed

smart-update
passed

tls-cert-manager
passed

users
passed

version-service
passed

We run 30 out of 30

commit: https://github.com/percona/percona-server-mysql-operator/pull/471/commits/882d39c7c49de32c6879250c37c9c1c1359ac295
image: perconalab/percona-server-mysql-operator:PR-471-882d39c