Job deployed to nats connects to nats on own IP

During upgrades, if previous deployment does not have nats-tls or the
metrics-discovery-registrar job at all, deployment can fail because
nats.service.cf.internal does not return any healthy instances to
connect that also have nats-tls running.
The first nats intance to deploy that would have that job running is not
healthy until the metrics-discovery-registrar is running. But
metrics-discovery-registrar has no nats-tls job it can resolve with
bosh-dns because the only instance that has nats-tls running is the
same, first nats instance. But that instance isn't healthy yet because
the metrics-discovery-registrar job isn't running yet... you get the
idea.
One way around this is to change the bosh-dns-aliases query from "*" to
"q-s4". But that means anyone locating nats will get unhealthy instances
in the mix. That may be acceptable given how nats clients retry
connections. But this change is more localized and addresses the root
cause more directly.
With this change, when nats_instance_group is configured, the
metrics-discovery-registrar jobs that get deployed to the instance group
of that name will connect to the nats job running on the same VM by IP
address instead of using bosh-dns to find a random instance. The new
property has no default, so if it is not set, the current behavior is
preserved.

Just realized that we probably need/want to make the name used for comparison in the conditional a variable spec property that defaults to "nats". That would allow it to be overridden on deployments that use a different instance group name or different colocation strategy.

OK, PR has been updated with a new spec property nats_instance_group. There is no default for the new property, and if not set, the current behavior is preserved. Deployments can choose to set this property to the value of the instance group name they use in their deployment for running nats-tls if they have a need to do so.

One way around this is to change the bosh-dns-aliases query from "*" to
"q-s4". But that means anyone locating nats will get unhealthy instances
in the mix. That may be acceptable given how nats clients retry
connections. But this change is more localized and addresses the root
cause more directly.

One way around this is to change the bosh-dns-aliases query from "*" to
"q-s4". But that means anyone locating nats will get unhealthy instances
in the mix. That may be acceptable given how nats clients retry
connections. But this change is more localized and addresses the root
cause more directly.

What about "q-s3" for only healthy instances? Looked at TAS for inspiration and every other bosh dns alias uses "*". Would there be any issue to just changing this reach only healthy instances?

q-s3 would suffer from the same problem. The issue is that during this time in the deployment, the only instance that has the nats-tls job is unhealthy. The other instances are healthy, but do not yet have the nats-tls job, because they haven't rolled yet.

Is spec.ip the external or internal IP of the VM?

It's the IP address you see with bosh vms. It is reachable at that address from other VMs on the same network.

Does this mean that if the NATs TLS job on the VM went down, this would stop working?

The metrics-discovery-registrar job on that VM would stop working while nats-tls on that VM is unavailable.

How were you able to test these changes in an upgrade since it doesn't always fail?

The failure is 100% reproducible in the case where:

You are upgrading from a deployment that does not contain the metrics-discovery-registrar job
You are upgrading to a version that includes the job and connects to nats-tls
You have more than one nats instance

Can you elaborate on how NATs work when there are multiple instances?

Can you elaborate on how NATs work when there are multiple instances?

That's a pretty broad question. I'm not sure I'm interpreting it properly, but here goes:
Let's assume this is cf-deployment and there are three nats instances in the nats instance group. Each of those instances is running the following jobs (and others, but let's call these out for now):

nats
nats-tls
metrics-discovery-registrar

The nats and nats-tls jobs are configured as a "cluster" of 6 servers (2 processes on each instance). So each job connects with all 5 other jobs. Those connections all use TLS.
These servers also receive client connections from the following jobs:

metrics-discovery-registrar connects to nats-tls(currently on any instance due to the * query)
route-emitter on each diego-cell instance connects to nats-tls (on which ever instance it first connects to via the *  query)
gorouter on the router instance group connects to the nats job

Messages that are published to any nats or nats-tls server get shared with the other members of the cluster, so any subscriber to any one of those jobs will receive those messages.
So, if we change metrics-discovery-registrar on a nats instance to connect to the nats-tls job on that instance instead of any instance, it will still be able to publish to subscribers of any nats server in the cluster.
Does that answer your question? If not, can you be more specific?

Yes thanks! I'll chat with the team to see if there are any other questions, otherwise, I think we can merge this in.

Hi @mcwumbly,
Using spec.id makes sense to us. We tested it out locally, changing the spec.ip to #{spec.id}.#{nats.hostname} and saw it succeed. If you could update the PR accordingly (and as part of it, change the hardcoded default nats_hostname to retrieve it from the bosh link), that would be swell.
We haven't been able to reproduce the failure ourselves, but we have seen it in the field. When you tried connecting via IP and saw it succeed, did you still have the NATS TLS failover enabled? From our understanding, nats has a service discovery that would automatically detect other available hosts and would find a non-TLS host after failing the TLS host, and would still appear to work, just not over TLS (hence why using the IP might still work). Using the spec.id + hostname should match the cert and work with TLS.
Thanks
@louis-brann and @angelachin

When you tried connecting via IP and saw it succeed, did you still have the NATS TLS failover enabled?
I'm not sure about this configuration, but you must be right. On a cf-deployment with a single instance of nats, I just found the following:

Summary
When the non-TLS nats job is not running, all of the following values for env.NATS_HOSTS in /var/vcap/jobs/metrics-discovery-registrar/config/bpm.yml fail with a certificate error:

IP address
${instanceID}.nats.service.cf.internal
nats.service.cf.internal

This fails because it cannot find any server:

nats.default.cf.bosh

Only this works:

${instanceID}.nats.default.cf.bosh

Details
Here are the details showing the config lines used in each case above, and the error in metrics-discovery-registrar.stderr.log:
IP address:
NATS_HOSTS: nats://nats:$password@<IP_ADDRESS>:4224`
# 2020/10/20 16:27:01 Unable to connect to nats servers: x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs

${instanceID}.nats.service.cf.internal:
NATS_HOSTS: nats://nats:$password@ec21ab15-4d0c-4227-9ba4-f71ea7ee2312.nats.service.cf.internal:4224
# 2020/10/20 16:33:49 Unable to connect to nats servers: x509: certificate is valid for *.nats.default.cf.bosh, not ec21ab15-4d0c-4227-9ba4-f71ea7ee2312.nats.service.cf.internal

nats.service.cf.internal:
NATS_HOSTS: nats://nats:$password@nats.service.cf.internal:4224
# 2020/10/20 16:33:49 Unable to connect to nats servers: x509: certificate is valid for *.nats.default.cf.bosh, not nats.service.cf.internal

nats.default.cf.bosh:
NATS_HOSTS: nats://nats:$password@nats.default.cf.bosh:4224
# 2020/10/20 16:48:11 Unable to connect to nats servers: nats: no servers available for connection

${instanceID}.nats.default.cf.bosh:
NATS_HOSTS: nats://nats:$password@ec21ab15-4d0c-4227-9ba4-f71ea7ee2312.nats.default.cf.bosh:4224
# 2020/10/20 16:50:43 Metrics endpoint is listening on <IP_ADDRESS>:15821

Next steps
Maybe the certificate being generated for nats-tls is incorrect in the default cf-deployment? If so, that's probably something that needs to be addressed.
In the meantime, I'm going to update this PR as requested. I think ultimately it is the right change for this issue.

@mcwumbly

Maybe the certificate being generated for nats-tls is incorrect in the default cf-deployment? If so, that's probably something that needs to be addressed.

Do you have any ideas about how/why it might be wrong, and what it should be? We are about to cut v14 of cf-deployment to release the cert changes for NATS TLS, and would love to have confidence in the changes we have made before we do.
Based on your statement that only ${instanceID}.nats.default.cf.bosh works, is it possible that the BOSH DNS aliases defined in cf-deployment for NATS are wrong?

@davewalter I'm not sure. I was just surprised to see this error in particular:
NATS_HOSTS: nats://nats:$password@nats.service.cf.internal:4224
# 2020/10/20 16:33:49 Unable to connect to nats servers: x509: certificate is valid for *.nats.default.cf.bosh, not nats.service.cf.internal

I haven't had time to do further debugging yet, and am only able to follow up on this issue part time at the moment.
If you have time to look into it further, here are the minimal repro steps for the potential cert issue in cf-deployment:

Deploy cf-deployment with 1 instance of nats
Stop the nats job: monit stop nats
Restart metrics-discovery-registrar: monit restart metrics-discovery-registrar
Check the last line of metrics-discovery-registrar.stderr.log to see whether it connected successfully or failed with a certificate (or other) error.

Try the above before and after the change you made. The version I have deployed currently does not include your change, so it's possible that your change is exactly what fixes this issue.

@davewalter I just tested the above after applying your change, and now it works as expected for both of these cases:

${instanceID}.nats.service.cf.internal
nats.service.cf.internal

@louis-brann and @angelachin - I think this is ready to merge now if it looks good to you.

sweet, thanks @mcwumbly and @davewalter!


disconnecting players manually on server shutdown

Currently the players will be disconnected after all games were saved. This may result in saving games which are yet open and not contain 3 or more players, which will result in errors because when they're loaded they are considered closed.
There are two possible attemps to fix this:

either only closed games will be saved on server shutdown
or all players need to be disconnected before games will be saved.
Need to investigate which of those methods is the most efficient one.

my mistake, doesn't matter anymore.


Fix namespace example

The json section is not converted in v1beta3, although the version is set to v1beta3.
More importantly cluster/kubectl.sh config set-context dev --namespace=development won't work  as we introduced cluster name, and user.  We'll have to set the two context var as well in kubectl, which is a little cubersome, do we have a better default than emtpy string?

#7802 made the same effort. @nikhiljindal , maybe we can merge #7802 for now and tries to simplify it later?

rebase or close please.


net-cygwin crashes in threaded entry methods

Original issue: https://charm.cs.illinois.edu/redmine/issues/1270

No body.

Original date: 2016-10-27 23:15:33

Per autobuild results, this dates to at least September 8, well before the 64-bit ID changes were merged. We don't have results prior to that because of the long-standing ftime linker nonsense.

Original date: 2016-10-28 01:14:44

The failure of the callback test also occurred in examples/charm++/threaded_ring, even when I stripped it down to just calling the [threaded] entry method and exiting. Switching thread package seems to resolve the crash. Fix here:
~~https://charm.cs.illinois.edu/gerrit/#/c/1948/~~ https://github.com/UIUC-PPL/charm/commit/a0ebf4a549927d9930a4d302ae4ed069972aac6a


174789366: fixing scores endpoint so scores aren't returned, only ses…

…sion ID
Do we need an API test for this?

@biotom The API response should have:
Response
-- 201 response code indicating a recored has been created for the scoring
-- Session id (so that we can retrieve personal values and feed for this session)
Is it using 201?

@biotom The API response should have:
Response
-- 201 response code indicating a recored has been created for the scoring
-- Session id (so that we can retrieve personal values and feed for this session)
Is it using 201?

Thanks- it is now

@biotom
Good! But now the body submission is still not like how the story asks:
{
"quesionResponses": {
"SetOne": [
{ "questionId": 1, "answerId": 1 },
{ "questionId": 2, "answerId": 2 },
{ "questionId": 3, "answerId": 4 },
{ "questionId": 4, "answerId": 5 },
{ "questionId": 5, "answerId": 3 },
{ "questionId": 6, "answerId": 4 },
{ "questionId": 7, "answerId": 2 },
{ "questionId": 8, "answerId": 3 },
{ "questionId": 9, "answerId": 4 },
{ "questionId": 10, "answerId": 3 }
]
}
}

I also believe when I checked earlier that it wasn’t accepting the correct Json body. Can you test in postman that if give it the body attached in the story you get the correct response back? Nick
Sent from my iPhone

On 3 Oct 2020, at 00:07, Kameron Rodrigues<EMAIL_ADDRESS>wrote:

@biotom The API response should have:
Response
-- 201 response code indicating a recored has been created for the scoring
-- Session id (so that we can retrieve personal values and feed for this session)
Is it using 201?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub, or unsubscribe.

No, sorry, I didn't touch the JSON body part. @seanmajorpayne have you done any work on that?

The body JSON is described https://www.pivotaltracker.com/story/show/174789366/comments/218277875
@biotom

is there a typo in that json- "quesionResponses"? Should it be question?

@biotom yes, that's a typo. Good catch!

@rodriguesk sure- I've gone with "questions". Just be sure to update it when things are sent from the frontend, or it won't work.
I think this should do what we want. I've attached a new screenshot in pivotaltracker. I've checked, and it should also cover the error handling specified in the comments. I have to go to bed, but I can look again tomorrow if there's anything wrong.

…sion ID
Do we need an API test for this?

Good work @biotom! So I've got a response back from the api with the sessions id! 🙌
There is still one issue is that the integration tests are conflicting with the front end  as are both trying to use port 5000, and preventing the docker compose from starting. I commented out all the integration tests stuff docker compose worked.
Not sure if there's any implications of changing the port for the tests.... @mncharlton

I approve of the functioning of the code. Regarding the integration and tests, I'll leave that to @mncharlton to give final approval for merging. Things may need to be removed or fixed.

I approve of the functioning of the code. Regarding the integration and tests, I'll leave that to @mncharlton to give final approval for merging. Things may need to be removed or fixed.

In the short term the front end can develop against this branch so that unblocks us for now. Ideally we want api tests to flag up if things change as that would break any clients using the api.
Thanks @biotom @rodriguesk We can begin to work on the score submission now!!!! I'm excited.

Ok, I've reformatted the code. I also removed the integration test dockerfile and section of the docker-compose- I added it, and in retrospect I'm not sure it does much for us since the test can be run with pytest. I might be wrong about that!

Looks good. Please squash and merge @biotom . Thanks!

Feel free to comment with that screenshot you took earlier too.


Fix bad merge

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ec59766). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #222   +/-   ##
=========================================
  Coverage          ?   89.88%
=========================================
  Files             ?       96
  Lines             ?    18174
  Branches          ?        0
=========================================
  Hits              ?    16336
  Misses            ?     1838
  Partials          ?        0

Impacted Files
Coverage Δ

juniper/src/lib.rs
86.84% <ø> (ø)

juniper/src/integrations/serde.rs
50.91% <100%> (ø)

Continue to review full report at Codecov.

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

I'm not sure why I can't merge this :-(

@LegNeato does @tailhook have write permissions? If not, then that is probably the problem:
At least 1 approving review is required by reviewers with write access.

also only people with write access can actually merge afaik


Documentation for ActivityTrackingOptions.Tags

Hello,
There is absolutely no documentation on how to use ActivityTrackingOptions.Tags and Baggage.
How to add tags?
I think this is a crucial information that is missing to use the feature

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

ID: 7184a308-a254-9350-a5cd-5bced1f369ae
Version Independent ID: 726e3bf1-f367-d733-8933-bccc04da0e16
Content: Logging in .NET Core and ASP.NET Core
Content Source: aspnetcore/fundamentals/logging/index.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

See LoggerFactoryOptions.ActivityTrackingOptions Property (Link in the article) and Automatically log scope with SpanId, TraceId, ParentId, Baggage, and Tags. from the article.

I've seen those, but they don't explain how to add tags or fill in the Baggage. No info on that at all.

Gets or sets the activity tracking options to indicate which parts of the tracing context information should be included with the logging scopes.


Error adding the contracts pallet

Dear Substrate
I had to add
[dependencies]
#--snip--
jsonrpc-core = '14.0.5'

#--snip--
[dependencies.pallet-contracts-rpc]
git = 'https://github.com/paritytech/substrate.git'
rev = '013c1ee167354a08283fb69915fda56a62fee943'
version = '0.8.0-alpha.3'

[dependencies.sc-rpc]
git = 'https://github.com/paritytech/substrate.git'
rev = '013c1ee167354a08283fb69915fda56a62fee943'
version = '2.0.0-alpha.3'

when i run
cargo run --release -- --dev

i get the following error
error: failed to parse manifest at `/home/noone/substrate-node-template/node/Cargo.toml`

Caused by:
  could not parse input as TOML

Caused by:
  redefinition of table `dependencies` for key `dependencies` at line 114 column 1

Kind Regards,
Noah

You have to add
jsonrpc-core = '14.0.5'

to the table that already exists
[dependencies]
futures = '0.3.1'
log = '0.4.8'
structopt = '0.3.8'


[CLI]: Can't change save_dir in wandb + PyTorchLightning

Hi,
I'm trying to change the local save directory for my experiments so they don't get stored under the default "wandb" folder. I'm instantiating a WandbLogger instance from PyTorch Lightning as shown below, passing "save_dir" as one of the parameters. However, when running the code it seems like this does nothing. The new experiment is created (I can see it on the web app), but it doesn't seem to be saved anywhere locally.
Example:
# Imports
...
from pytorch_lightning.loggers import WandbLogger

# Instantiate logger
wandb_logger = WandbLogger(
        config=cfg,
        save_dir="results/EXP_NAME"
)

I've tried different combinations of this, for example adding only "save_dir='wandb'" in the configuration, and this creates a nested "wandb" folder inside the original "wandb" folder. Anything else though, such as "save_dir='results/EXP_NAME'" just lead to the above, where the local files are saved nowhere. So the only way is to remove the save_dir parameter and then have all my experiments save in the default wandb.
Can someone help debug this? Thanks in advance.
Environment
WandB version: 0.12.10
OS: Linux 5.13.0-1025-aws
Python version:3.8.12
Versions of relevant libraries:
pytorch-lightning         1.5.9
Additional Context
I'm also using hydra to instantiate the wandb object and pass the parameters, but I have tried doing it without it (like the code given above) for more simplicity, with the same problem.

Hi @azinonos ,
WandbLogger() save_dir expects the directory to already exist. It's  an absolute path to where metadata will be stored. You are correct that by default this is ./wandb if a user doesnt defines their own directory. If for example the directory results/EXP_NAME doesn't already exist when instantiating your logger ,
# Instantiate logger
wandb_logger = WandbLogger(
        config=cfg,
        save_dir="results/EXP_NAME"
)

wandb will log the warning
wandb: WARNING Path results/EXP_NAME/wandb/ wasn't writable, using system temp directory.
If the directory exists however, you will see wandb log
Run data is saved locally in results/EXP_NAME/wandb/run-20220722_055024-156puage
Please let me know if you have any questions. Additionally, please note we recommend our users to update to the latest CLI version, which is currently at wandb 0.12.21

Hi @azinonos, since we have not heard back from you we are going to close this request. If you would like to re-open the conversation, please let us know!

Thanks for the responses, and apologies for the slow response. Ok, sounds good. I'm wondering whether it would be better to throw an error instead of a warning, as the warning got lost among other output I had and I didn't see it, which led to a couple of hours of frustratingly trying to see where these files disappeared.

[CLI]: Wandb tries to write to /wandb/ even when dir argument is specified #4600

I think the save_dir should be created before wandb.init() in lightning.


Create orange-dao-ethcc.md

@WinsCodes New event, please add the host logo

@laeccles Event has been merged to PL Events PROD.


feat: Add Prisma Service generation

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

v3.1.0
GitHub release

Your semantic-release bot :package::rocket:


Bug: introduced because of pull request #199

What happened?
I confirmed changes locally before pushing however still there is some problem with CSS and a bug in which anybody can delete anyone's posts
Also few console remained were not removed
Add screenshots

What browsers are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue

@Girishbari If you click on the content of the post, it will open to the new page with detailed information of the post with comments. You can take up this issue so that user page will open when clicked on profile name, username or photo else it will open /post/postId

sure

I guess this issue should be closed now

@Sanchitbajaj02  this issue was sorted ..?

@Girishbari what was the fix?

@Girishbari thanks for mentioning, closing this issue


How to get the txtContent from an Multiple line text field - Enhanced rich text?

Important
I want to show one column Multiple line of text in the list formatting. Right now is showing the HTML and not the rich text.
Category

[X] Question
[ ] Bug
[ ] Enhancement

Observed Behavior

Steps to Reproduce
Column config.

JSON
{
"elmType": "div",
"style": {
"flex-grow": "1"
},
"children": [
{
"elmType": "span",
"style": {
"display": "block"
},
"attributes": {
"class": "ms-fontWeight-semibold ms-fontSize-m"
},
"txtContent": "Answer:"
},
{
"elmType": "span",
"style": {
"display": "=if([$Answer] == '', 'none', 'block')",
"padding-left": "8px"
},
"txtContent": "=toString([$Answer])",
"attributes": {
"class": "ms-fontSize-s ms-fontWeight-regular ms-fontColor-neutralSecondary"
}
},
{
"elmType": "span",
"style": {
"display": "=if([$Answer] == '', 'block', 'none')",
"padding-left": "8px"
},
"txtContent": "No answer entered",
"attributes": {
"class": "ms-fontSize-s ms-fontWeight-semilight ms-fontColor-neutralTertiary"
}
}
]
}

I'm struggling with the same issue.  Can't seem to find out how to strip out the HTML and just show the formatted text.

Any luck?

Hope we get something for this

Can we please reopen this ticket?

This is a question regarding out of the box list formatting. This issues list is for issues pertaining to the samples in this repository.
If you would like Microsoft to implement something to address this limitation please create a suggestion on SharePoint Development User Voice. Reopening this issue will have no impact on how things work. Thanks!

This suggestion seems related and has almost 150 votes: https://feedbackportal.microsoft.com/feedback/idea/fff8f364-de1c-ec11-b6e7-0022481f8914

@tomresing if you don't mind, replicate this request in feedback for Microsoft Lists.
https://feedbackportal.microsoft.com/feedback/idea/445d79c1-6906-ed11-a81b-6045bd864d4f

Do we have solution or workaround for this issue?

Maybe this can help https://youtu.be/rKh7DDjBurA

My case was trying to re-use the Description field in a Document Library (for videos). The Description field for the built-in video viewer actually uses an internal field called _ExtendedDescription.
I found that you can edit the Description field records (_ExtendedDescription) via Edit in grid view where this doesn't apply DOM elements or styling (wahoo). An alternative is PowerApps form. Doing it one of these ways display well in formatted views and the native video viewer. IE "txtContent": "[$_ExtendedDescription]": no DOM elements or formatting issue.

This suggestion seems related and has almost 150 votes: https://feedbackportal.microsoft.com/feedback/idea/fff8f364-de1c-ec11-b6e7-0022481f8914

Has this issue been deleted? Both this and the Lists one 404 for me.

@gormster I can't reach either, though I think the Lists link was meant to link to the Lists area of the portal.

Any progress on this?
I would like to use the JSON to keep the rich text editor from putting everything in Calibri 11 instead of Segoe UI 11...
Another "annoyance" from Sharepoint Lists...


Added Testing Procedure in README.txt

CI: No security warnings found

CI: No security warnings found


OLPEDGE-383. Shared libs ON. Libsegfault lib added.

Shared libs tuned ON.
Linux libsegfault library added for segmentation fault crash identification in logs.
Resolves: OLPEDGE-383

Fixed comment and updated branch with latest master fixes.


How to achieve ListView smooth scrolling in Flutter

I have created a list view with network images and when I am trying to scroll the listview it's scrolling is not smooths it feels like jerking. For caching I have used cached_network_image: any, this library itself working fine but listview is not getting scrolled smooth.

Could you provide a minimum code sample to reproduce the issue? Are you using a profile/release build to test performance? Could you also provide the output of flutter doctor -v?

[√] Flutter (Channel stable, v1.9.1+hotfix.6, on Microsoft Windows [version 10.0.18362.418], locale fr-FR)
• Flutter version 1.9.1+hotfix.6 at C:\Users\zoom\flutter
• Framework revision 68587a0916 (7 weeks ago), 2019-09-13 19:46:58 -0700
• Engine revision b863200c37
• Dart version 2.5.0
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
• Android SDK at C:\Users\zoom\AppData\Local\Android\sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
• All Android licenses accepted.
[√] Android Studio (version 3.5)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 39.0.3
• Dart plugin version 191.8423
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
[√] IntelliJ IDEA Ultimate Edition (version 2019.2)
• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2019.2
• Flutter plugin version 38.2.4
• Dart plugin version 192.6527
[!] Connected device
! No devices available

@override
Widget build(BuildContext context) {
Size media = MediaQuery.of(context).size;
return ListView.builder(
shrinkWrap: true,
physics: NeverScrollableScrollPhysics(),
itemCount: names.length + 1,
itemBuilder: (BuildContext context, index) {
if (index == names.length) {
return _buildProgressIndicator();
} else {
return InkWell(
onTap: () {
Navigator.push(
context,
SlideTopRoute(page: ShowPost(data: datax)),
);
},
child: Container(
width: media.width,
padding: EdgeInsets.only(
top: 10.0, right: 15.0, left: 15.0, bottom: 0.0),
constraints: BoxConstraints(
minHeight: 100.0),
decoration: BoxDecoration(
color: Color(0xffffffff),
border: Border(
bottom: BorderSide(
color: Color(0xfff7f7f7),
width: 10.0,
style: BorderStyle.solid,
),
),
),
child: Column(
mainAxisAlignment: MainAxisAlignment.start,
mainAxisSize: MainAxisSize.min,
crossAxisAlignment: CrossAxisAlignment.stretch,
children: [
Container(
child: Row(
mainAxisAlignment: MainAxisAlignment.spaceBetween,
children: [
Material(
color: Color(0xffffffff),
child: Row(
children: [
Container(
width: 45,
height: 45,
decoration: BoxDecoration(
shape: BoxShape.circle,
image: DecorationImage(
fit: BoxFit.cover,
image: NetworkImage(widget.avatar),
),
),
),
SizedBox(
width: 10,
),
Column(
crossAxisAlignment: CrossAxisAlignment.start,
children: [
Material(
color: Color(0xffffffff),
child: Text(widget.userName,
style: TextStyle(
fontWeight: FontWeight.bold,
fontSize: 12,
color: Color(0xFF404040))),
),
SizedBox(
height: 3,
),
Material(
color: Color(0xffffffff),
child: Text(widget.userGroup,
style: TextStyle(
fontWeight: FontWeight.normal,
fontSize: 11,
color: Color(0xff999999))),
)
],
),
],
),
),
GestureDetector(
onTap: () {
if (isSelected) {
setState(() {
isSelected = false;
Fluttertoast.showToast(msg: "");
});
} else {
setState(() {
isSelected = true;
Fluttertoast.showToast(msg: "");
});
}
},
child: Material(
color: isSelected ? Color(0xfff38181) : Color(0xffffffff),
child: Container(
padding: EdgeInsets.only(
top: 2.0,
right: 15.0,
bottom: 2.0,
left: 15.0),
decoration: BoxDecoration(
borderRadius:
BorderRadius.all(Radius.circular(5.0)),
border: Border.all(
width: 1,
style: BorderStyle.solid,
color: Color(0xfff38181))),
child: Text("FOLLOW",
style: TextStyle(
fontWeight: FontWeight.normal,
fontSize: 12,
color: isSelected ? Color(0xffffffff) : Color(0xfff38181))),
),
),
)
],
),
),
Container(
padding: EdgeInsets.only(top: 5, bottom: 5),
child: Text(widget.text,
style: TextStyle(
color: Color(0xff000000),
fontSize: 15,
),
),
),
widget.img.length > 0
? Container(
height: double.parse(widget.heightContainer),
child:
PosteImages(postId: widget.id, type: ''),
)
: Container(),
Container(
child: Text(widget.date,
style: TextStyle(
color: Color(0xFFb4b4b4),
fontSize: 11),
),
),
Divider(
height: 1,
color: Color(0xfff1f1f1),
),
Container(
margin: EdgeInsets.fromLTRB(0, 10, 0, 10),
child: Row(
mainAxisAlignment: MainAxisAlignment.spaceBetween,
children: [
Row(
children: [
Icon(IconData(0xeac3, fontFamily: "LineIcons"),
size: 16, color: Color(0xFF646464)),
SizedBox(
width: 10.0,
),
Text(widget.view,
style: TextStyle(
fontSize: 12,
color: Color(0xffa4a4a4)),
),
],
),
Row(
children: [
InkWell(
child: Row(
children: [
Icon(IconData(0xeaba, fontFamily: "LineIcons"),
size: 18, color: Color(0xFF86c580)),
SizedBox(
width: 10.0,
),
Text(widget.share,
style: TextStyle(
fontSize: 12,
color: Color(0xffa4a4a4)),
),
],
),
onTap: () {
final RenderBox box = context.findRenderObject();
Share.share('share',
sharePositionOrigin:
box.localToGlobal(Offset.zero) &
box.size);
},
),
],
),
Row(
children: [
Icon(IconData(0xe99a, fontFamily: "LineIcons"),
size: 16, color: Color(0xFF646464)),
SizedBox(
width: 10.0,
),
Text(widget.reply,
style: TextStyle(
fontSize: 12,
color: Color(0xffa4a4a4)),
),
],
),
],
),
)
],
),
),
);
        }
      },

controller: _scrollController
);
}

@dimiril  Is all of that code really required to reproduce the issue? Can you reduce it further?

How to reduce the code

?

up

Delete everything which doesn't influence scrolling process, basically to try to find the part of code which causes the jerk scrolling or at which point it becomes so.

@dimiril
is it still an issue?
if yes, provide at least complete reproducible code sample

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.

I'm using listview.builder for showing images from the list, every other thing are working fine but when banner ads with 5 item gap load filter inside that listview a half sec lag comes, does anyone know that how to fix, please if anyone knows


Missing VK_COLOR_SPACE_DCI_P3_LINEAR_EXT

This enum variant was recently renamed to VK_COLOR_SPACE_DISPLAY_P3_LINEAR_EXT in Vulkan, but the old name was kept as an alias. In Ash 0.35 though it seems only the new name is available, even though I believe Ash's practice is to include aliases as well?

#502


⚠ Bofrost.es has degraded performance

In 5f2abc6, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1261 ms

Resolved: Bofrost.es performance has improved in 2fe60b3 after 9 minutes.


Allow Secret Key Name Static Prefix

Either via annotation or flag, it would be nice to allow for a static prefix to be added to all externalSecret key names. At the moment if you have multiple kubernetes clusters with the same applications but different secrets, you need to specify "locality" information in both the namespace annotation and the externalSecrets key name. Here are some examples:
Namespace annotation:
kind: Namespace
metadata:
  name: prometheus
  annotations:
    externalsecrets.kubernetes-client.io/permitted-key-name: "12345678/prometheus/.*"

ExternalSecret:
apiVersion: 'kubernetes-client.io/v1'
kind: ExternalSecret
metadata:
  name: aws-credentials
  namespace: prometheus
spec:
  backendType: secretsManager
  dataFrom:
    - 12345678/prometheus/aws-credentials

It would be nice to add an annotation to the namespace that will automatically prefix the secret key name, so the above mentioned externalSecret could instead not contain any locality info:
Namespace:
kind: Namespace
metadata:
  name: prometheus
  annotations:
    externalsecrets.kubernetes-client.io/permitted-key-name: "12345678/prometheus/.*"
    externalsecrets.kubernetes-client.io/key-prefix: "12345678/prometheus/"

ExternalSecret:
apiVersion: 'kubernetes-client.io/v1'
kind: ExternalSecret
metadata:
  name: aws-credentials
  namespace: prometheus
spec:
  backendType: secretsManager
  dataFrom:
    - aws-credentials

Still valid?


Any plan for integration with reanimated

Is your feature request related to a problem? Please describe.
Since Animated from react-native works not so smooth on web, so do u have any plan for integration with react-native-reanimated to improve the animation performance?
Additional context
<EMAIL_ADDRESS>has problem with react-native-web, use 2.2.3 instead.

I can help with PR if possible.

+1 for reanimated 2

You might want to check this video by Takuya: https://www.youtube.com/watch?v=k2h7usLLBhY
Here is an example of how to use it with Reanimated: https://github.com/craftzdog/react-native-animated-todo/blob/master/src/components/animated-color-box.tsx

You might want to check this video by Takuya: https://www.youtube.com/watch?v=k2h7usLLBhY
Here is an example of how to use it with Reanimated: https://github.com/craftzdog/react-native-animated-todo/blob/master/src/components/animated-color-box.tsx

I actually started to use Native Base on prod because of this video 😅
But I was talking about integrate it inside of Native Base components. In case you also find this useful

Oh, that's great to hear! We want to keep the core light and flexible for adoption. But, your point is noted. Let us revisit this decision.


Validate unix domain socket for GRPC communication

Validate

Unix domain socket
Named pipes (only windows?)

Note for containers:
Containers need to share sock files via volumes

UDS is supported on Windows 10/Windows Server 2019 or later. We are still at server 2016 and as per Hamid, we will move to 2022 in few months.
Named pipes (windows) is supported from .net 8 onwards only.
https://learn.microsoft.com/en-us/aspnet/core/grpc/interprocess?source=recommendations&view=aspnetcore-6.0#configure-client-and-server


5.1.0 - Incorrect variable reference in _reboot.scss

On line 30 of _reboot.scss
The CSS variable is named var(--#{$variable-prefix}-root-font-size), however there shouldn't be a hyphen before "root". This stops custom root font sizes from working.
The correct variable is var(--#{$variable-prefix}root-font-size).
Thanks

Already fixed in #34679 — thanks for reporting, though! 👌


tcp filter

is it possible to write a tcp(not http) filter that can parse the content of tcp stream and route accordingly?

It is possible, but going to be quite complex. See https://github.com/envoyproxy/envoy/tree/1d1b708c7bf6efa02c41d9ce22cbf1e4a1aeec2c/source/extensions/filters/network for some example such as thrift proxy, dubbo proxy etc. Thanks!


crash with unhandled entity type 7

Starting 29th of Nov at 13:00 CET our dockerized rpki-client no longer produces any files.
Docker logging:
2022-11-30T08:30:50.064813443Z rpki-client: rpki-rps.arin.net/repository/8a848ade7fb71aa9017fdd9c5dd324c7/0/EB1DD8AA3E2B6864E06379C751DBFFFCC6418350.mft: no valid mft available
2022-11-30T08:30:50.100377723Z rpki-client: rpki-rps.arin.net/repository/8a848ade7fb71aa901800003287f4402/0/2BF7605B8927C87448B3B294A8B61D8E983248E0.mft: no valid mft available
2022-11-30T08:30:50.287559589Z rpki-client: rpki-rps.arin.net/repository/8a848adf7fb722e9017ffead9f534ac5/0/BFA2750976CA07F56A68976B0F01EB862F17C3B3.mft: no valid mft available
2022-11-30T08:31:05.479810276Z rpki-client: unhandled entity type 7
2022-11-30T08:31:05.566212488Z rpki-client: poll[0]: bad fd
2022-11-30T08:31:05.566249456Z rpki-client: write[0]: Broken pipe
2022-11-30T08:31:05.566256810Z rpki-client: parser process exited abnormally
2022-11-30T08:31:05.571419260Z rpki-client: not all files processed, giving up
2022-11-30T08:31:05.966877368Z rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(713) [Receiver=3.2.4]

We are still using rpki-client 7.9
sudo docker inspect --format='{{index .RepoDigests 0}}' rpki/rpki-client:7.9
rpki/rpki-client@sha256:81f6c17b508e5184185a15e33f6f9f578d454ed6e78d67fa78c9182bf5f911ce

This problem has been fixed in the 8.0 release.
It was caused by improper handling of .asa files. It seems a CA added a .asa file triggering this bug.

However 8.0 had this issue blocking some folks from using it https://github.com/rpki-client/rpki-client-openbsd/commit/ec0949ce76d706aa232c119d53258eeca197ff73

In that case a quick fix would be to downgrade to 7.8 until 8.1 is out. It does not have this problem with .asa files.

However 8.0 had this issue blocking some folks from using it rpki-client/rpki-client-openbsd@ec0949c

https://github.com/rpki-client/rpki-client-container/commit/a1eed1d6b27e874506e310848ba8384f947f0c57 was added to a re-tagged 8.0 container image (including a fixed rsync).

Thanks, we are running 7.8 and the latest 8.0 on our test environment at the moment. If no problems occur we will switch back to 7.8. We prefer a solid tag for a release, and 7.8 has already done some time in our production environment.

rpki-client 8.2 finally was released which has both the .asa file exception and the proxy port handling fixed.
So this should be solved for good now.


Clock stop event

Add an onStop Event to the Clock which is called when the clock reaches its stopTime.

Thank you so much for the pull request @dwastberg! I noticed this is your first pull request and I wanted to say welcome to the Cesium community!
The Pull Request Guidelines is a handy reference for making sure your PR gets accepted quickly, so make sure to skim that.

:x: Missing CONTRIBUTORS.md entry.

Please add yourself to the contributors file!

:x: Missing CLA.

Please send in a Contributor License Agreement (CLA) and comment back here to let us know to check this!

:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

CLA has been sent

Thanks again for the contribution, @dwastberg.  We received your CLA.

Thanks @dwastberg!  This PR looks fine to me.  Can you please explain a scenario where this event is useful?

I'm using the clock to control a looping simulation and at the end of each loop I want to clean up some objects placed in the scene and make some changes to my GUI.

Thanks @dwastberg!  Just that one comment.  And please add a note under the Additions section of CHANGES.md

Just wondering if there is anything else needed to merger this?

Thanks for the reminder @dwastberg!  We don't get notifications when you add more commits, so it's a good idea to make a comment to let us know when a PR is ready for another look.
This all looks good to me.
Does anyone else have feedback?  If not, I'll merge this by the end of the day

Thanks again @dwastberg!


Typo on line 124 of examples/index.html

War
Should be:
War

Thanks. Updated.


[SPARK-32602][SQL] Fix issue where data with date type are saved into…

[SPARK-32602][SQL] Fix issue where data with date type are saved into hive table with wrong value '1970-01-01'
What changes were proposed in this pull request?
Data with date type are saved into hive table with wrong value '1970-01-01'
scala> spark.sql("create table t1(d date)")
res2: org.apache.spark.sql.DataFrame = []
scala> spark.sql("insert into table t1 values(cast('2020-08-09' as date))")
res3: org.apache.spark.sql.DataFrame = []
scala> spark.sql("select d from t1").show
+----------+
|         d|
+----------+
|1970-01-01|
+----------+
Spark 3.0 introduced DaysWritable which extends DateWrite from hive to handle date type. DaysWritable.toString() is called to write its value into hive table. DateWrite.toString() is defined as:
@Override
public String toString() {
// For toString, the time does not matter
return get(false).toString();
}
public Date get(boolean doesTimeMatter) {
return new Date(daysToMillis(daysSinceEpoch, doesTimeMatter));
}
DaysWritable didn't override toString(), neither get(boolean doesTimeMatter)。It did override get():
override def get(): Date = new Date(DateWritable.daysToMillis(julianDays))
but this didn't help with toString(), so with daysSinceEpoch in DateWritable always as 0, calls to DaysWritable.toString() will always return '1970-01-01', and as a result date value stored into hive table will always have value '1970-01-01'。
This pull request overrides DaysWritable.get(boolean doesTimeMatter) so that it's toString() behaves properly.
Why are the changes needed?
Fix the correctness issue describe above.
Does this PR introduce any user-facing change?
'No'.
How was this patch tested?
New test.

Can one of the admins verify this patch?

Can one of the admins verify this patch?


Creating and signing transactions without API (v4)

Hi,
I'm trying to create a transaction without neoscan API but can't find the right way to do it.
I have all the required data for the transaction: rpc endpoint, balance, private key... so I don't want to use neoscan API to retrieve data I already have (nor to be dependent on it).
These docs  are outdated and relating older version, e.g. if I try to use Neon.create.tx I get an error (not a function...)
I went through this but I don't understand if this process can be done without relying on the API (looks to me that not, maybe with override?).
I've noticed that the new version has transaction class and constructor so I can create 'new Transaction', this creates the transaction body with attributes, inputs, outputs... (which seems like the right direction for me) but I'm not really sure how to fill it with data (what exactly is required, data format etc.) and couldn't find any reference in the docs for that.
Can you please advise what's the proper way of creating a transaction (build, sign, broadcast...) without using external API (like neoscan)?
Any docs I missed covering it?
A working code example would be much appreciated.
My env: JavaScript, Node.js (v9), neon-js (v4.0.2)
Thanks!

It is mentioned in the guide but maybe its too small and indirect:
You may override any of these retrievals by populating the properties first. For example, if you wish to direct your calls to a specific NEO node, you should populate url with your intended url.

The function skips the calls towards neoscan when you pre-fill whatever it intends to retrieve. Just fill the fields in and you should be good.

so I need to use this?:
export interface apiConfig {
api: Provider; // The Provider to request UTXO and node information from
account: wallet.Account; // An account.
url?: string; // Optional override for RPC node.
fees?: number; // Any priority fees
override?: object; // Any overrides for transaction
signingFunction?: (
tx: string,
publicKey: string
) => Promise<string | string[]>; // A signing function if the account does not contain the private key
tx?: T;
response?: {
result: boolean;
txid?: string;
};
sendingFromSmartContract?: string; // The smart contract script hash if using assets from it
}
how can I override the balance? (so it won't be fetched from the api)
like this?:  override: balance { balance obj }

balance will go into balance, etc


Clarify default key generation and storage

LGTM, except do not touch the 3.0.0 docs. They will be deleted and recreated. We agreed that for now, all our doc changes to 2.9 or into the draft section.

Ok good to know, reverted the changes on 3.0.0.


feat: Postgres Addon (export & save)

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

GitHub release
v1.4.0

Your semantic-release bot :package::rocket:


CLI Should have Create and Delete for sensors.

Currently, there is no way via the CLI to delete a sensor...or create one for that matter.
vagrant@st2vagrant:~/st2docs$ st2 sensor --help
usage: st2 sensor [-h] {list,get,enable,disable} ...

An adapter which allows you to integrate StackStorm with external system

positional arguments:
  {list,get,enable,disable}
                        List of commands for managing sensortypes.
    list                Get the list of sensortypes.
    get                 Get individual sensor.
    enable              Enable an existing sensor.
    disable             Disable an existing sensor.

optional arguments:
  -h, --help            show this help message and exit```

In my case, I'm doing development and have decided that a particular sensor's name (or ref in the context of st2 sensor list output) is less than useful, and I've changed it (logically speaking, the reference sensor no longer exists). I'd like to maintain a "clean" list of sensors that can "actually be enabled". Do I need to remove some data from the database directly?


"prefix" is breaking if library overwrites jupyter settings in prefix

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
❯ pixi init
❯ pixi add python solara
  × Is a directory (os error 21)

Issue description
This code installs solara. Solara sets a default value for Jupyter to enable server rendering, this is done under prefix/etc/jupyter/....
pixi sets prefix as a file with text, pointing to the .pixi folder.
I believe, as solara is installable using micromamba, that pixi does this in an incorrect way.
Expected behavior
Installation to work correctly.

It would be an easy fix to rename the prefix file to something else, but I think that in this case it shows that solara has an issue. As the prefix in prefix/etc/jupyter/.. seems to actually be referring to etc/jupyter "in" the "prefix" which isn't called prefix but .pixi/envs/default in this example.
We actually have the correct location for the Jupyter related files in .pixi/envs/default/etc/jupyter

Fun note
This is why `prefix.dev` is called prefix because we install in prefixes.

We should move the prefix file to conda-meta/prefix instead, to avoid clobbering any packages.

I'll make a separate request for solara to fix their thing 😊👍
But it seems based on final comment there's something for you to fix too, feel free to close ticket if not!

Looking at https://github.com/widgetti/solara/commit/6ad9bae61f9f9860900d0fa547327952f6dec38e I think i did something wrong with refactoring from flit to hatchling.
@iisakkirotko fixed this by adding the line in https://github.com/widgetti/solara/commit/080894e12e152e7502fa5c9813daf33bdc8294c0 but we should have removed the weird "prefix" = "prefix line.
As @maartenbreddels said, I think removing the "prefix" = "prefix"-line should fix the issue, although I don't think I can verify this, since it seems like pixi doesn't support installing from path/github yet. Do let me know if there is a way to do this. Interesting name collision indeed :)

I just checked, and the install works with Solara 1.29.1


Sleep some more time in ansible targeted refresh

the sleep here is also needed because tower needs some time
to actually propagate it's updates
if we would return immediately it could be that the we get
the old playbooks
So we always sleep 1 second after the update has finished
the whole sleep business is a workaround anyway until we get
proper polling via https://github.com/ManageIQ/manageiq/pull/14405
adresses https://bugzilla.redhat.com/show_bug.cgi?id=1442170
@miq-bot add_label bug, providers/ansible_tower

@miq-bot assign @agrare


Saving DPP compilation time

Is your feature request related to a problem? Please describe.
The first compilation takes a lot of time when I need to solve the DPP problem repeatedly.
Describe the solution you'd like
I want to save the DPP compilation result and load it directly the next time I run the same code.
Describe alternatives you've considered
I hope I can output a file to save the compilation result so that I can load the file directly next time.
Additional context
Thanks a lot for your work.

You could use CVXPYgen (https://github.com/cvxgrp/cvxpygen). This will compile the problem into C code (using DPP), in a way that's easy to call from Python. Alternatively, you could pickle the problem after you solve it once and load it from the pickle file.

@jfpios we are in the process of building a benchmarking tool and collect real world examples for that. It would be great if you could provide the code that produces the slow compiling problem, if possible.

Thank you for your kind reply. I will try to use CVXPYgen. I am working on a project now, and there is still a long way from finishing it. I will share my code after I get a satisfying result.


Add a wiki: HoloCure Wiki

Link to origin wiki: https://holocure.fandom.com/wiki/HoloCure_Wiki
Link to destination (independent) wiki: https://holocure.wiki.gg/wiki/HoloCure_Wiki
Announcement post: https://reddit.com/r/holocure/comments/18xdz5y/holocure_wiki_has_moved_to_holocurewikigg/

Thanks for the submission! Added in v3.4.0, now available for both Chrome + Firefox.


Created a new section in about us page

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes #223

Mark the task you have completed ✅
created a new section in about us page

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for review.

Thank you soo much for contributing to our repository 💗

I have created a new pull request
pls review that #285


Can't compile to wasm

  Compiling proc-macro-hack v0.5.19
   Compiling futures-core v0.3.15
   Compiling tinyvec v1.2.0
error: the wasm32-unknown-unknown target is not supported by default, you may need to enable the "js" feature. For more information see: https://docs.rs/getrandom/#webassembly-support
   --> /home/dylan/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.3/src/lib.rs:219:9
    |
219 | /         compile_error!("the wasm32-unknown-unknown target is not supported by \
220 | |                         default, you may need to enable the \"js\" feature. \
221 | |                         For more information see: \
222 | |                         https://docs.rs/getrandom/#webassembly-support");
    | |_________________________________________________________________________^

error[E0433]: failed to resolve: use of undeclared crate or module `imp`
   --> /home/dylan/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.2.3/src/lib.rs:246:5
    |
246 |     imp::getrandom_inner(dest)
    |     ^^^ use of undeclared crate or module `imp`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0433`.
error: could not compile `getrandom`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
Error: Compiling your crate to WebAssembly failed
Caused by: failed to execute `cargo build`: exited with exit status: 101
  full command: "cargo" "build" "--lib" "--release" "--target" "wasm32-unknown-unknown"

This is most likely due to std leakage of the build-dependencies.
the master branch includes a fix that should solve this: https://github.com/scs/substrate-api-client/pull/120

The fix only solves your issue if the api-client is the top-level crate, otherwise you need to add "resolver = 2" to your top-level Cargo.toml.

@clangenb Does not seem to work by adding "resolver = 2"

@clangenb https://github.com/DylanVerstraete/rust-wasm-substrate/blob/master/Cargo.toml
can you check this repo please?

Well, when you want to compile to wasm you need to disable the std-features of the api-client with default-features = false
But this will strip most functionalitiy.

I have just checked up on that and found out that std does not inherently break wasm support - but some std-libs do.
So, I reckon we'd need to make some adjustments to be able to support wasm with the std feature enabled. Without should be fine - as far as I know.

If I disable default-features I get:
....
  Compiling sp-wasm-interface v4.0.0-dev (https://github.com/paritytech/substrate.git?branch=master#cf086eeb)
   Compiling sp-arithmetic v4.0.0-dev (https://github.com/paritytech/substrate.git?branch=master#cf086eeb)
   Compiling primitive-types v0.10.1
   Compiling sp-runtime-interface v4.0.0-dev (https://github.com/paritytech/substrate.git?branch=master#cf086eeb)
   Compiling sp-core v4.0.0-dev (https://github.com/paritytech/substrate.git?branch=master#cf086eeb)
   Compiling sp-io v4.0.0-dev (https://github.com/paritytech/substrate.git?branch=master#cf086eeb)
   Compiling frame-metadata v14.0.0-dev (https://github.com/paritytech/substrate.git?branch=master#cf086eeb)
   Compiling sp-inherents v4.0.0-dev (https://github.com/paritytech/substrate.git?branch=master#cf086eeb)
   Compiling sp-application-crypto v4.0.0-dev (https://github.com/paritytech/substrate.git?branch=master#cf086eeb)
error[E0046]: not all trait items implemented, missing: `Pair`
   --> /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/lib.rs:241:3
    |
241 |         impl $crate::CryptoType for Public {}
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing `Pair` in implementation
    |
   ::: /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/ed25519.rs:29:5
    |
29  |     crate::app_crypto!(super, ED25519);
    |     ----------------------------------- in this macro invocation
    |
    = note: this error originates in the macro `$crate::app_crypto_public_not_full_crypto` (in Nightly builds, run with -Z macro-backtrace for more info)
    = help: implement the missing item: `type Pair = Type;`

error[E0046]: not all trait items implemented, missing: `Pair`
   --> /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/lib.rs:442:3
    |
442 |         impl $crate::CryptoType for Signature {}
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing `Pair` in implementation
    |
   ::: /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/ed25519.rs:29:5
    |
29  |     crate::app_crypto!(super, ED25519);
    |     ----------------------------------- in this macro invocation
    |
    = note: this error originates in the macro `$crate::app_crypto_signature_not_full_crypto` (in Nightly builds, run with -Z macro-backtrace for more info)
    = help: implement the missing item: `type Pair = Type;`

error[E0046]: not all trait items implemented, missing: `Pair`
   --> /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/lib.rs:241:3
    |
241 |         impl $crate::CryptoType for Public {}
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing `Pair` in implementation
    |
   ::: /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/sr25519.rs:29:5
    |
29  |     crate::app_crypto!(super, SR25519);
    |     ----------------------------------- in this macro invocation
    |
    = note: this error originates in the macro `$crate::app_crypto_public_not_full_crypto` (in Nightly builds, run with -Z macro-backtrace for more info)
    = help: implement the missing item: `type Pair = Type;`

error[E0046]: not all trait items implemented, missing: `Pair`
   --> /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/lib.rs:442:3
    |
442 |         impl $crate::CryptoType for Signature {}
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing `Pair` in implementation
    |
   ::: /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/sr25519.rs:29:5
    |
29  |     crate::app_crypto!(super, SR25519);
    |     ----------------------------------- in this macro invocation
    |
    = note: this error originates in the macro `$crate::app_crypto_signature_not_full_crypto` (in Nightly builds, run with -Z macro-backtrace for more info)
    = help: implement the missing item: `type Pair = Type;`

error[E0046]: not all trait items implemented, missing: `Pair`
   --> /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/lib.rs:241:3
    |
241 |         impl $crate::CryptoType for Public {}
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing `Pair` in implementation
    |
   ::: /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/ecdsa.rs:29:5
    |
29  |     crate::app_crypto!(super, ECDSA);
    |     --------------------------------- in this macro invocation
    |
    = note: this error originates in the macro `$crate::app_crypto_public_not_full_crypto` (in Nightly builds, run with -Z macro-backtrace for more info)
    = help: implement the missing item: `type Pair = Type;`

error[E0046]: not all trait items implemented, missing: `Pair`
   --> /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/lib.rs:442:3
    |
442 |         impl $crate::CryptoType for Signature {}
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ missing `Pair` in implementation
    |
   ::: /home/dylan/.cargo/git/checkouts/substrate-7e08433d4c370a21/cf086ee/primitives/application-crypto/src/ecdsa.rs:29:5
    |
29  |     crate::app_crypto!(super, ECDSA);
    |     --------------------------------- in this macro invocation
    |
    = note: this error originates in the macro `$crate::app_crypto_signature_not_full_crypto` (in Nightly builds, run with -Z macro-backtrace for more info)
    = help: implement the missing item: `type Pair = Type;`

error: aborting due to 6 previous errors

For more information about this error, try `rustc --explain E0046`.
error: could not compile `sp-application-crypto`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
Error: Compiling your crate to WebAssembly failed
Caused by: failed to execute `cargo build`: exited with exit status: 101
  full command: "cargo" "build" "--lib" "--release" "--target" "wasm32-unknown-unknown"

There seemed to be a tiny feature-flag bug on our side. Fixed in https://github.com/scs/substrate-api-client/pull/137

@clangenb okay, will I be able to do anything with the client without std-features?

Currently, it is essentially the compose_extrinsic_offline! macro, which is not really much. It allows you only to compose and to sign an extrinsic.

@clangenb although it compiles now I get following error trying to import the API
➜ wasm-pack build
[INFO]: Checking for the Wasm target...
[INFO]: Compiling to Wasm...
   Compiling rust-substrate-api-client v0.1.0 (/home/dylan/Projects/rust-substrate-api-client)
error[E0432]: unresolved import `substrate_api_client::Api`
  --> src/lib.rs:13:5
   |
13 | use substrate_api_client::Api;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ no `Api` in the root

error: aborting due to previous error

For more information about this error, try `rustc --explain E0432`.
error: could not compile `rust-substrate-api-client`

To learn more, run the command again with --verbose.
Error: Compiling your crate to WebAssembly failed
Caused by: failed to execute `cargo build`: exited with exit status: 101
  full command: "cargo" "build" "--lib" "--release" "--target" "wasm32-unknown-unknown"

If you disabled std in the client you ony get access to compose_extrinsic_offline! macro. This no part of the Api strut, but exported to top-level.
use substrate_api_client::compose_extrinsic_offline;


Add OpenRailwayMap

This is a useful overlay extracting railway data.

Thanks for your contribution!
JOSM layers can be added and updated with the extract.mjs script using yarn layers and the ID defined in the JOSM Maps Wiki (I need to document that). So I added a second commit switching to that.


SAE needs to allow EMAPA IDs

Although the SAE allows me to autocomplete EMAPA IDs for mouse anatomy terms (as you can see in attached picture), it then shows them with an error, saying it is expecting an Uberon ID instead.

Here's the model: http://<IP_ADDRESS>:8910/workbench/simple-annoton-editor/?model_id=gomodel:5a98684700000052

This looks like the same basic issue as #32 . @cmungall can you also address this one?  @tmushayahama, for both of these when you are reading the graph to populate the SAE form and check validity, you'll need to recognize additional prefixes (EMAPA and WBbt) as valid anatomy terms, just like UBERON.

These two are different. #32 is dependent on me merging in the uberon-to-wbbt bridge, which will done after validation.
We already have uberon-bridge-to-emapa.owl merged in, which means that mapped EMAPA classes will show up as subclasses of uberon anatomical entity. I confirmed this:
http://noctua-golr.berkeleybop.org/select?q=bronchus&defType=edismax&qt=standard&indent=on&wt=json&rows=10&start=0&facet=true&facet.mincount=1&fq=document_category:"ontology_class"&fq=isa_closure:"UBERON:0001062"&qf=annotation_class^3&qf=annotation_class_label_searchable^5.5&qf=synonym_searchable^1&fl=id,annotation_class_label,idspace
you can see this includes EMAPA bronchus (as well as Uberon. We need curator guidelines as to what to pick when, especially as we increasingly annotate outside our species).
It looks like @tmushayahama is implementing an addition constraint such that the ID is expected to be in the Uberon ID space. I generally discourage making any assumptions about IDs, for ontologies, or databases. Use the ontology to discover semantics.

can you double check on this one.


Route handlers are not registered correctly

Hi,
I'm trying to create a simple project with this library, but I have some trouble. I think the routes registration are not handled correctly. The handler is called twice every time.
Let's take this simple example. By registering a middleware or a route, the behavior will be what I described above .
import HyperExpress, { MiddlewareNext, Request, Response } from 'hyper-express';

const webserver = new HyperExpress.Server();

const specificMiddleware1 = (request: Request, response: Response, next: MiddlewareNext) => {
 // This is called twice
  console.log('route specific middleware 1 ran!');
  next();
};

const specific_middleware2 = (request: Request, response: Response, next: MiddlewareNext) => {
  // This is called twice
  console.log('route specific middleware 2 ran!');
  next();
};

// webserver.use(specificMiddleware1);
// webserver.use(specific_middleware2);

webserver.get(
  '/',
  //   {
  //     middlewares: [specificMiddleware1, specific_middleware2],
  //   },
  (request: Request, response: Response) => {
    // This is called twice
    console.log('called');
    response.send('Hello World');
  },
);

webserver.listen(3000);

`

Hello, It seems that you misunderstood how the middleware binding works. After trying your snippet above, I am seeing the following behavior:

The route handler aka. called log only gets logged once no matter what.
The specific middleware 1 and 2 only run twice If you do webserver.use() AND also specify a middlewares property on the route options. By doing this, you are effectively binding the same middleware twice.

The webserver.use() call is binding a global middleware meaning the middleware being assigned will run on ALL routes on the server.
On the contrary, the middlewares object specified on the route options will only run those middlewares on that route's requests.
The route handler should never be called twice. You can validate that the route handler never gets called by using code like below:
webserver.get('/', (request, response) => {
   // The below code will only log the warning if the same request is called twice on the handler
   if (request.called_already) console.warn('Detected the same route handler being called twice with the same request');
   request.called_already = true;
});

With that said, this does not seem to be a bug in hyper-express but rather incorrect usage. Hope that helps!


Offer language versions of EpiDoc files in EFES

(See how this is handled in Kiln and especially cf. IOSPE)
The iospe.5.*.xml files all have content in both English (@xml:lang='en') and Russian (@xml:lang='ru'). Currently, sending the file name along should return the English version; sending [filename]-ru.html should return the Russian version. I guess this will require a change in EpiDoc Example XSLT?
Maybe see if we can figure out a way to return both strings, and choose between them in the Cocoon view?

(Maybe this is subsumed in an existing ticket in the customization suite, in which case please feel free to close this issue. There will in any cases be differences in implementation to what I was imagining two years ago.)

Support for this (though in a slightly different fashion, with the language code being the first element in the URL path) was added in commit d79087907b82a7d36f7fe6585b4b29f0fb9b29a1.


🐛 build: fix image push job by disabling CGO when building kustomize

What this PR does / why we need it:
Passes CGO=enabled to building kustomize from tools folder to be able to build it within the container successfully
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #132
Related to: https://github.com/kubernetes-sigs/cluster-api/issues/8784
Try it:
$docker run -it --entrypoint /bin/bash gcr.io/k8s-staging-test-infra/gcb-docker-gcloud:v20220609-2e4c91eb7e
bash-5.1# export CGO_ENABLED=0
bash-5.1# go install<EMAIL_ADDRESS>bash-5.1# which kustomize
/go/bin/kustomize

Additional notes:
Copy of https://github.com/kubernetes-sigs/cluster-api/pull/6231. All credits to @sbueringer 🎉

/cc @alexander-demicev @Fedosin @damdo @JoelSpeed

/lgtm


Want to contribute to the repo

I am also building a ChatLLM as project and faced same issue of that the OpenAI api are costly and trying to figure out a way to add Open Source LLM as API but didn't find for TypeScript and came across your project.
I would love to contribute to the this project.

That sounds great! You might want to have a look at this issue to get started:
https://github.com/fardjad/node-llmatic/issues/132

Sure I will check it out.


Add More Scroll Functionality

Propose to add ScrollIntoView, ScrollBy, ScrollTo, ScrollToTop, ScrollToBottom, GetScrollHeight...
Please Note: ScrollIntoView and my version of ExecuteScript both take a WebElement (not a WebElement ID string) as argument - see WebElement ID Issue discussion...
Also, could add following related sub to WebElement Class:
Public Sub ScrollIntoView(Optional ByVal AlignTop As Boolean = True)
    Driver_.ScrollIntoView Me, AlignTop, SessionId_
End Sub

@GCuser99 Thank you!
This PR requires ExecuteScript, doesn't it?


Rebuild

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

FYI: cling with C++14/C++17 is broken with GCC 9.5.0 due to a GCC bug https://github.com/conda-forge/clad-feedstock/pull/10#issuecomment-1281725889
Ideally we should make a repodata patch.

Ideally we should make a repodata patch.

Sorry for the newbie question, but what doe sthat mean? Patching the feedstock of gcc 9.5?

Ideally we should make a repodata patch.

Sorry for the newbie question, but what does that mean? Patching the feedstock of gcc 9.5?

I mean modifying the channels metadata to fix the dependencies of already built packages, i.e. in this case making a pull request to conda-forge-repodata-patches-feedstock to make all cling builds depend on gxx_linux-64 !=9.5.0.
See also: https://conda-forge.org/docs/orga/guidelines.html#fixing-broken-packages

Ok, avoiding it in the run_constrained section here for now, I will make a PR on repodata after (and I will probably need some guidance)


Bug: load_from_checkpoint() of GPyTorch model causes TypeError: 'Tensor' object is not callable

🐛 Bug
The goal is to integrate checkpointing by PyTorch Lightning where the model is a GPyTorch-based Gaussian Process model (useful for time series modeling).
The training works great.
The problem is that loading a saved checkpoint results in the follow traceback:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
[<ipython-input-27-46754cae787b>](https://localhost:8080/#) in <module>()
----> 1 model = MyPyTorchLightningGPyTorchModule.load_from_checkpoint(checkpoint_path, train_x, train_y)

6 frames
[/usr/local/lib/python3.7/dist-packages/pytorch_lightning/core/saving.py](https://localhost:8080/#) in load_from_checkpoint(cls, checkpoint_path, map_location, hparams_file, strict, **kwargs)
    130         with pl_legacy_patch():
    131             if map_location is not None:
--> 132                 checkpoint = pl_load(checkpoint_path, map_location=map_location)
    133             else:
    134                 checkpoint = pl_load(checkpoint_path, map_location=lambda storage, loc: storage)

[/usr/local/lib/python3.7/dist-packages/pytorch_lightning/utilities/cloud_io.py](https://localhost:8080/#) in load(path_or_url, map_location)
     36     fs = get_filesystem(path_or_url)
     37     with fs.open(path_or_url, "rb") as f:
---> 38         return torch.load(f, map_location=map_location)
     39
     40

[/usr/local/lib/python3.7/dist-packages/torch/serialization.py](https://localhost:8080/#) in load(f, map_location, pickle_module, **pickle_load_args)
    605                     opened_file.seek(orig_position)
    606                     return torch.jit.load(opened_file)
--> 607                 return _load(opened_zipfile, map_location, pickle_module, **pickle_load_args)
    608         return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
    609

[/usr/local/lib/python3.7/dist-packages/torch/serialization.py](https://localhost:8080/#) in _load(zip_file, map_location, pickle_module, pickle_file, **pickle_load_args)
    880     unpickler = UnpicklerWrapper(data_file, **pickle_load_args)
    881     unpickler.persistent_load = persistent_load
--> 882     result = unpickler.load()
    883
    884     torch._utils._validate_loaded_sparse_tensors()

[/usr/local/lib/python3.7/dist-packages/torch/serialization.py](https://localhost:8080/#) in persistent_load(saved_id)
    855         data_type, key, location, size = data
    856         if key not in loaded_storages:
--> 857             load_tensor(data_type, size, key, _maybe_decode_ascii(location))
    858         storage = loaded_storages[key]
    859         return storage

[/usr/local/lib/python3.7/dist-packages/torch/serialization.py](https://localhost:8080/#) in load_tensor(data_type, size, key, location)
    844
    845         storage = zip_file.get_storage_from_record(name, size, dtype).storage()
--> 846         loaded_storages[key] = restore_location(storage, location)
    847
    848     def persistent_load(saved_id):

[/usr/local/lib/python3.7/dist-packages/torch/serialization.py](https://localhost:8080/#) in restore_location(storage, location)
    828     else:
    829         def restore_location(storage, location):
--> 830             result = map_location(storage, location)
    831             if result is None:
    832                 result = default_restore_location(storage, location)

TypeError: 'Tensor' object is not callable

To Reproduce
https://colab.research.google.com/drive/1M_xhxauoDZObXjN264iBnHJE_qmuxgiS?usp=sharing
Expected behavior
Load from checkpoint should work.
Environment

CUDA:

GPU:

Tesla T4

available:         True
version:           11.1

Packages:

numpy:             1.21.5
pyTorch_debug:     False
pyTorch_version:   1.10.0+cu111
pytorch-lightning: 1.5.10
tqdm:              4.62.3

System:

OS:                Linux
architecture:

64bit

processor:         x86_64
python:            3.7.12
version:           #1 SMP Tue Dec 7 09:58:10 PST 2021

Additional context
Same problem on Windows 10 and doesn't matter if model was trained on CPU or GPU.

try this:
model = MyPyTorchLightningGPyTorchModule.load_from_checkpoint(checkpoint_path, train_x=train_x, train_y=train_y)

ref: https://pytorch-lightning.readthedocs.io/en/latest/common/lightning_module.html#load-from-checkpoint

Thanks. That worked.


Fetchart: add fetching artwork from Wikipedia

Query DBpedia using SPARQL to obtain the filename of the album's cover, as it is used on the relevant Wikipedia article. The direct image url is then obtained using Wikipedia's API.

Interesting approach ! Hadn't heard of dbpedia before.

Looks good, I just fixed buckets tests that made the Travis build failed.
Could you have  a look at the flake8 warnings and add an updated version of the plugin doc to your PR?

Wow, very cool! This is a nifty use of dbpedia.
Thanks, @Kraymer, and I agree: this will be totally ready to merge once flake8 and docs are ready.

@Kraymer, given a recent refactorisation your work cannot be cleanly merged any more. Could you update it? You simply have to create a class Wikipedia(ArtSource), turn your function into its get method and the constants into its class variables.

@brunal je crois que tu voulais t'adresser à tomjaspers non ? ;)

Right... @tomjaspers could you update that PR to make it mergeable?

@brunal I was waiting until the refactorisation was merged. I'll do an update tomorrow.

@sampsyo Is this good to be merged, or need I do something else ?

Looks good; thank you, @tomjaspers! I blame the week-long delay here on GitHub, who does not notify me when people add new commits to a pull request. Thanks for commenting, which brought my attention back. Merging now.


MM-20422 Migrate 'components/user_profile' module and associated tests to TypeScript

Summary
Migrate 'components/user_profile' module and associated tests to TypeScript
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/16152
Jira ticket: https://mattermost.atlassian.net/browse/MM-20422

Hello @lmammino,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

There a couple of failures in the rendering (relative to default props) that I am not sure I understand. I'd love some guidance, please :)

/update-branch

what's the next step on this one? Is there any action required on my side?

Thank you @lmammino
Apologize for the delay in testing
Tested, looks good to merge.

Verified profile popover still works as expected.
Seeing one small issue, where incoming webhook profile popover fails to open when viewed on the right hand side thread. Since it also reproduces on master and release, I will file that separately for follow up.
Thanks again for your contribution! 🙂

@lmammino This is almost ready to merge, can you fix the lint errors? I'll merge when that's done.
/root/mattermost/mattermost-webapp/components/overlay_trigger.tsx
  13:21  error  Expected a semicolon  @typescript-eslint/member-delimiter-style

/root/mattermost/mattermost-webapp/components/user_profile/index.ts
  13:20  error  Expected a semicolon  @typescript-eslint/member-delimiter-style

/root/mattermost/mattermost-webapp/components/user_profile/user_profile.tsx
  21:10  error  Expected a space after the '?:'  @typescript-eslint/type-annotation-spacing

@lmammino This is almost ready to merge, can you fix the lint errors? I'll merge when that's done.
/root/mattermost/mattermost-webapp/components/overlay_trigger.tsx
  13:21  error  Expected a semicolon  @typescript-eslint/member-delimiter-style

/root/mattermost/mattermost-webapp/components/user_profile/index.ts
  13:20  error  Expected a semicolon  @typescript-eslint/member-delimiter-style

/root/mattermost/mattermost-webapp/components/user_profile/user_profile.tsx
  21:10  error  Expected a space after the '?:'  @typescript-eslint/type-annotation-spacing

hey @devinbinnie, it should be updated now...

hey @devinbinnie, it should be updated now...

@lmammino Looks like there's still errors. We've made some changes to our eslint config recently, so you might need to sync your branch with master to get all of those errors fixed.

@lmammino Looks like there's still errors. We've made some changes to our eslint config recently, so you might need to sync your branch with master to get all of those errors fixed.

🤞

🤞


builtins: implement ST_ConvexHull

PR: https://github.com/cockroachdb/cockroach/pull/51446
From release notes:

Implemented the ST_ConvexHull function on GEOMETRY types. [#51446][#51446] {% comment %}doc{% endcomment %}

Fixed in #8581


Few qestions about PIP8048 Max

Hello.
I use 2424mse1 branch.
Is it possible to get data on pv2 (Voltage, current, etc.)?
And is it possible to get the data of solar energy production for the day that is stored in the inverter?

Is it possible to get data on pv2 (Voltage, current, etc.)?

A second PV string is supported by the pip8048 branch. I've pushed the support of long QPIGS responses here too now. Could you try this branch again?
external_components:
  - source: github://syssi/esphome-pipsolar@pip8048
    refresh: 0s

Some entities/sensors are named differently here. This example configuration YAML should help:
https://github.com/syssi/esphome-pipsolar/blob/pip8048/esp32-example.yaml
https://github.com/syssi/esphome-pipsolar/blob/pip8048/esp8266-example.yaml

And is it possible to get the data of solar energy production for the day that is stored in the inverter?

The retrieval of this property isn't supported yet. I'm aware of voices that claim the values are not very accurate.

Seems to work :)
But again there are a few questions:

My inverter has a maximum charge current of 150A and a minimum of 10A. can i just change the yaml?
I can not understand what the "charging discharging control" parameter is responsible for. I searched for information in the document from the comment, but without success.

Yes. The default options are just defaults. You can override these defaults at the YAML. Just search the name of the select entity in the issues of this project. I assume you will find some more hints/examples.
I can just provide the issued command so you can try to look it up at the protocol description. Does this help?

Yes. The default options are just defaults. You can override these defaults at the YAML. Just search the name of the select entity in the issues of this project. I assume you will find some more hints/examples.
I can just provide the issued command so you can try to look it up at the protocol description. Does this help?

it's work, thanks
Yes :)

  - platform: pipsolar
    pipsolar_id: inverter0
    charging_discharging_control:
      # See MAX_Communication_Protocol_20200526.pdf page 18
      name: "${name} charging discharging control"
      optionsmap:
        "111": "PBATCD111"
        "011": "PBATCD011"
        "101": "PBATCD101"
        "110": "PBATCD110"
        "010": "PBATCD010"
        "100": "PBATCD100"
        "001": "PBATCD001"
        "000": "PBATCD000"
      statusmap:
        "111": "111"
        "011": "011"
        "101": "101"
        "110": "110"
        "010": "010"
        "100": "100"
        "001": "001"
        "000": "000"

Please try to lookup the PBATCD command. See MAX_Communication_Protocol_20200526.pdf page 18.


Added OHS implementation

The format of the test-result.json file is slightly different, e.g., it has a result.reason field for tests that we skip. I'll update the documentation in a follow-up PR.
This PR also removes the duplicated implementations.json to fix #237.

If you want to preview what the test report will look like, you can run the app inside the test_report up locally.

If you want to preview what the test report will look like, you can run the app inside the test_report up locally.

Thanks for the tip; I ran the app locally and also updated some of the instructions. As a side effect, I also fixed #237 and updated documents accordingly.

You've got the test result directly within the test object:
{
  "name": "basic attribute",
  "passed": true
}

It needs to be nested inside a "result" field, like this:
{
  "name": "basic attribute",
  "result": {
    "passed": true
  }
}

This is now fixed in the latest version of our test report.

Thanks @johngrimes for merging this. Looking at the implementations page it cannot fetch Pathling's test report. It seems it throws a CORS error; can you please take a look?


INTERNAL_ERROR: received a stateless reset with token

This should be able to be replicated with the following code:
hclient.Get("https://r1---sn-a5mlrn7r.googlevideo.com/videoplayback?aitags=133%2C134%2C135%2C136%2C137%2C160%2C242%2C243%2C244%2C247%2C248%2C278&c=WEB&clen=11054481&dur=304.480&ei=dlOUX_3ZBta0vgTWzoO4Cw&expire=1603577814&fvip=1&gir=yes&id=o-AERHNDqF6H0wkq5HUbqMCfDxAG-QaZ4l_3HkzOniXQ3R&initcwndbps=246250&ip=<IP_ADDRESS>&itag=135&keepalive=yes&lmt=1603548283508500&lsig=AG3C_xAwRgIhAO_srXrjzs0go5oyXPWIqQXuChuq_bd_d-g7TwcfU6hJAiEA0rQSjjmR_sV8XWp2ckNkbnlumRYGrGfLPj7snXohPHk%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&mh=as&mime=video%2Fmp4&mm=31%2C29&mn=sn-a5mlrn7r%2Csn-a5meknzl&ms=au%2Crdu&mt=1603556085&mv=m&mvi=1&pl=20&requiressl=yes&sig=AOq0QJ8wRAIgPgv_Izutiw5x8OQWCPTb9_2-OP4LtgRJ3NSgeW_ZJm8CICErEU_tHMOeEH2w6TgEB1fYrw5lkYMH4F5qQxiHLwwr&source=youtube&sparams=expire%2Cei%2Cip%2Cid%2Caitags%2Csource%2Crequiressl%2Cvprv%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&txp=6432432&vprv=1")

This is the error log I get when doing so:
2020/10/24 21:51:12 Get "https://r1---sn-a5mlrn7r.googlevideo.com/videoplayback?aitags=133%2C134%2C135%2C136%2C137%2C160%2C242%2C243%2C244%2C247%2C248%2C278&c=WEB&clen=11054481&dur=304.480&ei=dlOUX_3ZBta0vgTWzoO4Cw&expire=1603577814&fvip=1&gir=yes&id=o-AERHNDqF6H0wkq5HUbqMCfDxAG-QaZ4l_3HkzOniXQ3R&initcwndbps=246250&ip=<IP_ADDRESS>&itag=135&keepalive=yes&lmt=1603548283508500&lsig=AG3C_xAwRgIhAO_srXrjzs0go5oyXPWIqQXuChuq_bd_d-g7TwcfU6hJAiEA0rQSjjmR_sV8XWp2ckNkbnlumRYGrGfLPj7snXohPHk%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&mh=as&mime=video%2Fmp4&mm=31%2C29&mn=sn-a5mlrn7r%2Csn-a5meknzl&ms=au%2Crdu&mt=1603556085&mv=m&mvi=1&pl=20&requiressl=yes&sig=AOq0QJ8wRAIgPgv_Izutiw5x8OQWCPTb9_2-OP4LtgRJ3NSgeW_ZJm8CICErEU_tHMOeEH2w6TgEB1fYrw5lkYMH4F5qQxiHLwwr&source=youtube&sparams=expire%2Cei%2Cip%2Cid%2Caitags%2Csource%2Crequiressl%2Cvprv%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&txp=6432432&vprv=1": INTERNAL_ERROR: received a stateless reset with token 185e83196a61b7f44198653ef82f6d68

That's interesting. Looks like a bug on Google's side though, not in quic-go.

Interesting, how do you know that tho, the same URL works fine on chromium 🤔 (used by YouTube)

I guess it’s binding some session information to this request.

To add more details to my answer: A stateless reset is sent when a server receives a QUIC packet that it doesn't know how to decrypt (e.g. because it was recently rebootet). It can also show that there's a routing problem (e.g. packets exchanged during the handshake are routed to one backend server, but packets after completion of the handshake are routed to another server).

Another question, does quic-go only support the latest draft? Is there support for the h3-Q050 version of QUIC?


WIP: Add Jsdocs

Description of the problem this pull request fixes:
Adding JS doc and a minimal theme less hideous than the regular js doc theme
Steps to functionally test this:

run npm run docs
open simple server
got to:  http://localhost:8000/docs

There isn't much here. I plan on going in and adding place holders around all the areas we need to add more docs.
I also am trying to think of the best way to handle design consistency with the jekyll site. I might fork the theme over the weekend and then update it to be prettier.

Additional stuff you can do with JSdocs.  If for some reason methods aren't compiled to the class they belong on you can use @memberof Class  and if they still aren't compiling right, you can use @memberof! class

@kadamwhite cleaned it up :)


Update release workflow for new repo

Update repo name to fix failed workflow: https://github.com/spiffe/helm-charts-hardened/actions/runs/6486573870

https://github.com/spiffe/helm-charts/pkgs/container/helm-charts%2Fspire
The permissions on existing registry where fixed.


WIP: feat: Multi log support

Signed-off-by: Andrii Soluk<EMAIL_ADDRESS>

Codecov Report

Merging #43 (abee1ed) into main (f1185c0) will decrease coverage by 0.82%.
The diff coverage is 81.25%.

@@            Coverage Diff             @@
##             main      #43      +/-   ##
==========================================
- Coverage   85.18%   84.36%   -0.83%
==========================================
  Files          13       13
  Lines        1701     1720      +19
==========================================
+ Hits         1449     1451       +2
- Misses        147      153       +6
- Partials      105      116      +11

Impacted Files
Coverage Δ

pkg/controller/command/models.go
100.00% <ø> (ø)

pkg/controller/command/command.go
79.43% <65.38%> (-4.67%)
:arrow_down:

pkg/controller/rest/operation.go
83.47% <68.42%> (-3.20%)
:arrow_down:

cmd/vct/startcmd/start.go
86.02% <95.83%> (+1.60%)
:arrow_up:

pkg/client/vct/client.go
90.16% <100.00%> (+0.08%)
:arrow_up:

Continue to review full report at Codecov.

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


automate form generation

ref:
templates.organizations.form.html
question: how to automate form generation based on pydantic models/schemas, to make it reusable ?

Not sure why you would like to automate the form generation?
There is this library that I've never used but it could do the trick: https://github.com/boardpack/reforms
Otherwise you could use WTForms https://wtforms.readthedocs.io/en/3.0.x/ in combination with https://github.com/wtforms/wtforms-sqlalchemy for example.


Fleetd should prevent to run more than one daemon

Currently, fleetd doesn't prevent to run more than one daemon, it may has some potential problem. Should create fleet.pid in /var/run/

From #1229:

I don't think this is necessary, and will prevent legitimate use cases where multiple fleet daemons can run on the same machine. Solving #615 solves the actual issue here.

I believe we will solve this more appropriately via #615


On-the-fly reprojection of tile maps

One that I've discussed with @jorisvandenbossche offline and now have made some impromptu progress. Currently, contextily only supports Web Mercator so, whatever CRS the original data is expressed in, if the user wants to combine them with tile maps, they need to move their data to WM. In some cases, that's OK but, in other contexts, that might be expensive and it might be a lot better to reproject (warp) the tile map.
To get started, here's a tentative function that does this:
from rasterio.io import MemoryFile
from rasterio.vrt import WarpedVRT
from rasterio.enums import Resampling

def warp_tiles(img, ext,
               t_crs='EPSG:4326',
               resampling=Resampling.bilinear):
    '''
    Reproject (warp) a Web Mercator basemap into any CRS on-the-fly
    ...

    Arguments
    ---------
    img         : ndarray
                  Image as a 3D array of RGB values (e.g. as returned from
                  `contextily.bounds2img`)
    ext         : tuple
                  Bounding box [minX, maxX, minY, maxY] of the returned image
    t_crs       : str/CRS
                  [Optional. Default='EPSG:4326'] Target CRS, expressed in any
                  format permitted by rasterio. Defaults to WGS84 (lon/lat)
    resampling  : <enum 'Resampling'>
                  [Optional. Default=Resampling.bilinear] Resampling method for
                  executing warping, expressed as a `rasterio.enums.Resampling
                  method

    Returns
    -------
    img         : ndarray
                  Warped Image as a 3D array of RGB values
    ext         : tuple
                  Bounding box [minX, maxX, minY, maxY] of the returned (warped)
                  image
    '''
    h, w, b = img.shape
    # --- https://mapbox.github.io/rasterio/quickstart.html#opening-a-dataset-in-writing-mode
    minX, maxX, minY, maxY = ext
    x = np.linspace(minX, maxX, w)
    y = np.linspace(minY, maxY, h)
    resX = (x[-1] - x[0]) / w
    resY = (y[-1] - y[0]) / h
    transform = from_origin(x[0] - resX / 2,
                            y[-1] + resY / 2, resX, resY)
    # --- Write basemap into memory file
    with MemoryFile() as memfile:
        with memfile.open(driver='GTiff', height=h, width=w, \
                          count=b, dtype=str(img.dtype.name), \
                          crs='epsg:3857', transform=transform) as mraster:
            for band in range(b):
                mraster.write(img[:, :, band], band+1)
            # --- Virtual Warp
            with WarpedVRT(mraster, crs=t_crs,
                           resampling=resampling) as vrt:
                src_wm = vrt.read().transpose(1, 2, 0)
    bb = vrt.bounds
    extent = bb.left, bb.right, bb.bottom, bb.top
    return src_wm, extent

I'm putting it in this precarious format, rather than as a PR so:

Folks quickly say if this API works

We can discuss where it could go (my first thought is on tile.py but haven't thought too much about it

Folks can also chip in on how this could be exposed to end-users. For now, this is all I can think of:

As a standalone function warp_tiles that can be piped with bounds2img
Through a t_crs argument in add_basemap that defaults to EPSG:3857 and adds a warped basemap to a set of provided matplotlib.Axes
Through the Place API, where the user can also specify a t_crs argument when initialising and the response is returned in that CRS (maybe @choldgraf has some input on this?).

Ideas/suggestions?

Discussion currently moved over to the PR for this #49

Closing as implemented in #49


feat: give pallpark gas estimates

Partially addresses near/devx#235
This is a largely a rewrite of our previous gas document
git is terrible at formatting such diffs; I recommend viewing this work primarily by looking at the preview: https://docs-pr-422.onrender.com/docs/concepts/gas (but please do come back and comment on specific lines in the "Files changed" tab here)

I've merged in its current state at @amgando's request, since he wanted the new document ahead of a workshop he's running in a few hours.
Please keep feedback coming in, and I will address it in follow-up PRs. Thanks!


Policy Condition failed: ["starts-with", "$utf8", ""]

<Error>AccessDenied<Message>Invalid according to Policy: Policy Condition failed: ["starts-with", "$utf8", ""]</Message><RequestId>A1AA13A9F53FC78F</RequestId><HostId>mjV4fhkvwUKnSk+fllWtqcr63DRRUAi91kInaMHdbQPr9Y87U5t0Y+OoFcSaWzijOab9ekeM9NI=</HostId></Error>

I'm using Dropzone.js and a react component that inlines all the required properties as props. However, I can't get it to upload because of this issue. Here is what is passed through:
------WebKitFormBoundaryqf7zhaXVP3LfObjb
Content-Disposition: form-data; name="utf-8"

------WebKitFormBoundaryqf7zhaXVP3LfObjb
Content-Disposition: form-data; name="key"

uploads/b597673b-a6c8-4116-a6b6-89fe3e9ef2de/${filename}
------WebKitFormBoundaryqf7zhaXVP3LfObjb
Content-Disposition: form-data; name="AWSAccessKeyId"

[redacted]
------WebKitFormBoundaryqf7zhaXVP3LfObjb
Content-Disposition: form-data; name="acl"

public-read
------WebKitFormBoundaryqf7zhaXVP3LfObjb
Content-Disposition: form-data; name="success_action_status"

201
------WebKitFormBoundaryqf7zhaXVP3LfObjb
Content-Disposition: form-data; name="policy"

[redacted]
------WebKitFormBoundaryqf7zhaXVP3LfObjb
Content-Disposition: form-data; name="signature"

5cSmzzAg5m7YLPrj4dtfwSRyPrs=
------WebKitFormBoundaryqf7zhaXVP3LfObjb
Content-Disposition: form-data; name="file"; filename="Screen Shot 2016-03-30 at 4.17.13 PM.png"
Content-Type: image/png

------WebKitFormBoundaryqf7zhaXVP3LfObjb--

I fixed it - I was using utf-8 instead of utf8 in the form data.
    this.dropzone.on('sending', (_, xhr, formData) => {
      ...
      formData.append('utf8', '');
      ...
    });

Thanks for posting this. I've been struggling to get this working for hours now!
I couldn't seem to find anything in the carrierwave_direct or Amazon S3 docs that explain what this utf8 parameter is doing...

The utf8 parameter isn't used by S3, and our documentation does a poor job describing it's purpose.
It's a by product of using the rails form builder to build the POST form to S3.  Rails 4.0 and below always includes a hidden field to force IE to respect UTF-8 encoding on form submission.
With that attribute present, we have to include a [ "starts-with", "$utf8", "" ] condition in the policy to tell S3 to allow that field in the form (even though S3 ignores it).
Rails 4.1 and above now allows that hidden field to be removed through an option when building the form, but completely removing it from the policy would be backwards incompatible.

Aha, that makes sense. Thanks for clarifying, @nddeluca.
I saw the option to disable this functionality by passing uploader.policy(enforce_utf8: false), and that @object.policy(enforce_utf8: true) is hard-coded into the form builder.
Think there's any value in allowing this parameter to be configured when used inside CarrierwaveDirect's form builder? In my case I was using the builder to generate all the required hidden fields, but am submitting the file to S3 via AJAX. It'd be cool if I could use the builder and omit the $utf param so I don't need to use formData.append('utf8', ''); as a workaround.
If there's interest, I could take a stab at something like this. I think it would be cool if CarrierwaveDirect offered more functionality for AJAX use cases 👍

This issue is resolved. Please give it a try! one side note is that the frontend code is a bit buggy and the redirect may not be working right now but I'm working on it.


next/release

:tada: This PR is included in version 3.2.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add line breaks in Markdown code

Related issue: #27657 (Some lines are too long in Markdown code)

Direct links to the preview:

https://deploy-preview-27658--kubernetes-io-master-staging.netlify.app/docs/setup/production-environment/container-runtimes/
https://deploy-preview-27658--kubernetes-io-master-staging.netlify.app/docs/setup/production-environment/windows/intro-windows-in-kubernetes/
https://deploy-preview-27658--kubernetes-io-master-staging.netlify.app/docs/setup/production-environment/windows/user-guide-windows-containers/

In issue #27657 I recommended we discuss this change before moving forward.
I'm going to add
/hold
pending that discussion.

I performed a rebase.

from a windows content standpoint this lgtm but as this is a largely a formatting change id like a sig-docs reviewer to comment here, @sftim as you marked this on hold I will defer to you but let me know if I can help!
/cc @sftim

Ah, we discussed this in the SIG Docs weekly meeting and I'm happy to unhold it
/hold cancel

/approve

/lgtm


Nathan/vagrant

Add a Vagrant VM Box to project

Include <IP_ADDRESS> skilltree.dev in your hosts file

wrong repo sorry