CSV files only including data up until run time runs out, terminal output includes all data

Hi, first off I just want to say thank you for a great product, the idea to write load tests in Python is very welcomed.
Now, I noticed that when I'm using the switch "--run-time" together with the "--csv" option Locust is indeed stopping my tests when the run time runs out and is calling my on_stop method on all my users which in turn basically logs out my users before Locust completely exits. But when I compare the generated csv files (specifically the stats file) with the output Locust gives in the terminal there is a difference: the csv file is lacking the last few terminal outputs in its data and I guess this is because the csv file is only including data up until the point the run time runs out, would be great if the csv file also included this data since the terminal already is doing that.

I also noticed that if you use the "--html" switch you get an html file containing all data like the terminal output, data produced even beyond the run time. So it seems that only the csv files are lacking data in this case.


Blazor @ref for dynamically generated elements

I have a scenario where an @foreach loop iterates over an externally-provided List<> parameter to generate a series of Razor components from a third-party library. After the content is rendered, other interactions trigger certain methods on those components, but I don't see a clean way to use @ref to address them.
I'm going try pointing the @ref to a property setter and use that to store value in a dictionary but it feels pretty hacky, and I suspect that could leak those references if the component is re-rendered (maybe this calls for WeakReference<T>?)

@MV10 thanks for contacting us.
@SteveSandersonMS Will an array of element references work here?

This isn't something we specifically set out to support, but yes, you can use a dictionary. For example:
@foreach (var id in identifiers)
{
    <Index @ref="myComponents[id]" />
}

@code {
    private List<string> identifiers = new List<string> { "Alpha", "Beta", "Gamma" };
    private Dictionary<string, Index> myComponents = new Dictionary<string, Index>();
}

This will initally populate myComponents with three entries (for keys alpha/beta/gamma). If you add new items to identifiers later and re-render, it will add new entries to myComponents.
The tricky bit is that it doesn't give any obvious way to remove items from myComponents if they are removed from the UI. Presumably you can handle that in application code though. If you know you're removing something from identifiers, then also delete the corresponding keyed item from myComponents.


server support for klaipeda ragnarok

hi!!!
the klaipeda ragnarok server is already in the supported servers file but 4rtools does not recognize it
the data in the file is:
{
"name": "KlaipedaRO",
"description": "KlaipedaRO",
"site": "https://playklaipeda.net/",
"hpAddress": "0x01138DDC",
"nameAddress": "0x0113B7B0"
}
can you update it? im new with kind of tools but if there is a manual or something i can use to get the new info, please tell me.
thanks!

sorry, i did a bit of research and worked. here is the new data:
{
"name": "KlaipedaRO",
"description": "KlaipedaRO",
"site": "https://playklaipeda.net/",
"hpAddress": "0x011691E4",
"nameAddress": "0x01164800"
},

can we add RagnarokPlay on the supported servers
website :  http://www.ragnaplay.ragna.online/


[BUG] Name has space will throw DoubleEncodedException.

Library name and version
Azure Cosmos DB
Describe the bug
When both the database name and container name contain spaces, a Double Encoded Exception is thrown.
Set database name to "database 1" and container name to "container 1".
The container name will be encoded as container%201, and the database will be re encoded as database%25201.
Expected behavior
The name should not allow the use of spaces, or the database name should not be encoded.
Actual behavior
Double Encoded Exception
Reproduction Steps
1.Create a cosmos DB account resource.
2.Create a cosmos DB SQL database resource, database name contains space: e.g. "database 1".
3.Create a cosmos DB SQL Container resource, container name contains space: e.g. "container 1".
4.Get a cosmos DB SQL Container.
Environment
No response

@melina5656:  Please do not add tags when opening issues unless they are for your team.   This interferes with triage and the ability to route this appropriately.    In this case, it is unclear what package you're discussing, which matters because the CosmosDB management package is maintained in this repository but the client library is not.
Please clarify the full package name and version.


connlib: investigate using sendmmsg for TUN device

We are already using quinn-udp for the UDP socket which allows us to use GRO to read multiple network packets in a single syscall. Currently, we process those one by one and then write them out individually to the TUN device.
We should be able to use sendmmsg for the TUN device to be able to write multiple packets in a single syscall. This should increase throughput.

Looking into this a bit further:

fd of TUN devices are not sockets, so by default recvmmsg and sendmmsg don't work.
sendmmsg seems to be support as something called TSO: https://github.com/torvalds/linux/blob/741e9d668aa50c91e4f681511ce0e408d55dd7ce/include/uapi/linux/if_tun.h#L87-L94
I  don't know yet whether we can use recvmmsg at all

Also see https://tailscale.com/blog/throughput-improvements.

Some more useful notes: https://blog.cloudflare.com/virtual-networking-101-understanding-tap/

WIP code here: https://github.com/firezone/firezone/pull/4179
So TUN devices don't support recvmmsg at all. Instead, you need to use read and interpret the virtio-net-header that is prepended. What is kind of weird is that the payload seems to be:

IP header
TCP/UDP header
N payloads

Note to myself: Using readv doesn't work because that is just a vectored read in case we have more buffers to read into. But our issue isn't multiple buffers, it is wanting to do batch read of packets.


[WIP] Create security-policy.md

[x] Have you followed the contributing guidelines?
[x] Have you explained what your changes do, and why they add value to the Guides?

Related to #981, I have created a first draft of documentation which describes best practices for a security policy.

@jhutchings1 Looks good to me! When CI is green and you're ready for this to 🚢 give me a shout and I'll merge it in.

Cres que valla a funcionar??

I feel like security-policy is a more narrowly scoped than other guides. security on the other hand, would fill a big omission from the guides. Basically expand and reframe around keeping your project and its users secure. Having a security policy would be part of that guide-ance. Just a thought, feel free to disregard!

I like @mlinksva's idea. It would be nice to have a general security section in the https://opensource.guide/ that covers best practices and helps developers secure their GitHub projects.

[x]  Have you followed the contributing guidelines?
[x]  Have you explained what your changes do, and why they add value to the Guides?

Related to #981, I have created a first draft of documentation which describes best practices for a security policy.

Thanks all for the ✅ . I haven’t had the cycles to build this into the TOC properly, but I like the idea of a general security section as well. I’m catching up from vacation and GitHub summit, but will revisit this soon. If anyone wants to run with it in the interim, I’m 👍

Solo es la guia...
La aplicacion solo la tiene un sistema...

git@github.com:nodegui/react-nodegui.git

Just noticed you might want to consider revising the following passage under "How to Contribute to Open Source" since, in my opinion, this contradicts the advice in this pull request.
https://github.com/github/opensource.guide/blob/681597c6ec5181e953df9977a18e7b4f8db365b4/_articles/how-to-contribute.md#L418

@EdOverflow I don't think it does:

unless you need to share sensitive information (such as a security issue or serious conduct violation)

Am I missing something?

You are right, @mlinksva. I completely misread that. Thank you for pointing that out. :+1:

Is there somebody that works on this project that can help out with illustrations for this security page? That's a bit outside my skillset 😄

Also, the build is breaking as a result of not having localized versions of my new article. How do we get those created? Thanks!

@jhutchings1 might need to add something to tests to allow for not-yet-translated articles. I don't think any articles have been added since the original set so we haven't had the issue yet. Or maybe the right thing is to add stubs for to each translation for a new article asking for translations? Either would seem reasonable to me.
I believe @sophshep was the initial site designer and might be able to point you somewhere, maybe inside GitHub, regarding illustrations.

Is there somebody that works on this project that can help out with illustrations for this security page?
I believe @sophshep was the initial site designer and might be able to point you somewhere, maybe inside GitHub, regarding illustrations.

Yep, I was! These illustrations were done by @jeejkang who is no longer at GitHub, but @tonyjaramillo (manager of our art/illustration team) may be able to help.

I haven't had the cycles to get this over the line, so happy to leave this closed for now.

From 7f77bd09c252888a58bcbdcc2424acf81d32e130 Mon Sep 17 00:00:00 2001
From: Justin Hutchings<EMAIL_ADDRESS>Date: Mon, 3 Jun 2019 16:13:57 -0700
Subject: [PATCH 1/5] Create security-policy.md

_articles/security-policy.md | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
create mode 100644 _articles/security-policy.md
diff --git a/_articles/security-policy.md b/_articles/security-policy.md
new file mode 100644
index<PHONE_NUMBER>..7d93d54a61
--- /dev/null
+++ b/_articles/security-policy.md
@@ -0,0 +1,32 @@
+---
+lang: en
+title: Security policy
+description: Help users report security issues by providing a security policy
+class: best-practices
+image: /assets/images/cards/best-practices.png
+---
+
+## Why do I need a security policy?
+
+Even small projects in open-source can have a big impact because of the way ideas can move through the community. When it comes to software security, vulnerabilities can move through the community just as quickly as great ideas, so it's important that every open-source project think about their security policy. A security policy helps your community by a) letting them know what you will support in terms of security issues, and b) letting them know how to work with you when they discover security issues.
+
+## Components of a good security policy
+
+### Scope/Supported versions
+
+Tell users about the parts of your project which are within scope of the security policy. For example, if you will not accept security bugs on test collateral, or samples, you should describe those limitations here. If your project has any official releases or versions, you should let users know which ones are being officially supported here.
+
+### Disclosure policy
+
+In the disclosure policy section, describe how and where users should disclose security vulnerabilities here. This is the right place for a link to the private inbox you might host, a link to your HackerOne, or a link to your own custom website.
+
+If you have any security requirements on the communications (eg, no attachments, signed with a PGP key, etc), you should also list them here.
+
+### Safe harbor
+
+Safe harbor provisions are important in terms of setting boundaries as to what constitutes ethical hacking, vs unlawful hacking on your project. These sections are important, so if your company or project has lawyers, now's the time to call them. A good security policy should encourage security researchers to report security issues responsibly, and a good safe harbor provision gives those researches confidence that they won't be prosecuted for doing so. The GitHub Bug Bounty Program provides more information about how GitHub uses a safe harbor provision to protect hackers provided that they abide by certain limitations.
+
+## See also
+* HackerOne's security policy builder
+* Securitytxt.org
+* [NTIA Coordinated Vulnerability Disclosure template] (https://www.ntia.doc.gov/files/ntia/publications/ntia_vuln_disclosure_early_stage_template.pdf)
From 4f2bd1500f86b0851afb55a6c2015129ca214d75 Mon Sep 17 00:00:00 2001
From: Justin Hutchings<EMAIL_ADDRESS>Date: Thu, 22 Aug 2019 17:19:01 -0700
Subject: [PATCH 2/5] Update security-policy.md
Incorporating feedback
_articles/security-policy.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_articles/security-policy.md b/_articles/security-policy.md
index 7d93d54a61..5a8005eb22 100644
--- a/_articles/security-policy.md
+++ b/_articles/security-policy.md
@@ -8,7 +8,7 @@ image: /assets/images/cards/best-practices.png
Why do I need a security policy?
-Even small projects in open-source can have a big impact because of the way ideas can move through the community. When it comes to software security, vulnerabilities can move through the community just as quickly as great ideas, so it's important that every open-source project think about their security policy. A security policy helps your community by a) letting them know what you will support in terms of security issues, and b) letting them know how to work with you when they discover security issues.
+Even small projects in open-source can have a big impact because of the way ideas move through the community. When it comes to software security, vulnerabilities can move through the community just as quickly as great ideas, so it's important that every open-source project think about their security policy. A security policy helps your community by a) letting them know what you will support in terms of security issues, and b) letting them know how to work with you when they discover security issues.
Components of a good security policy
From 68085fd59071360ab5169da126be5d9c5317dafd Mon Sep 17 00:00:00 2001
From: Justin Hutchings<EMAIL_ADDRESS>Date: Thu, 22 Aug 2019 17:52:37 -0700
Subject: [PATCH 3/5] Broadening the security section

_articles/security-policy.md      | 32 ------------------
_articles/think-about-security.md | 54 +++++++++++++++++++++++++++++++
2 files changed, 54 insertions(+), 32 deletions(-)
delete mode 100644 _articles/security-policy.md
create mode 100644 _articles/think-about-security.md
diff --git a/_articles/security-policy.md b/_articles/security-policy.md
deleted file mode 100644
index 5a8005eb22..0000000000
--- a/_articles/security-policy.md
+++ /dev/null
@@ -1,32 +0,0 @@
-lang: en
-title: Security policy
-description: Help users report security issues by providing a security policy
-class: best-practices
-image: /assets/images/cards/best-practices.png

-## Why do I need a security policy?
-Even small projects in open-source can have a big impact because of the way ideas move through the community. When it comes to software security, vulnerabilities can move through the community just as quickly as great ideas, so it's important that every open-source project think about their security policy. A security policy helps your community by a) letting them know what you will support in terms of security issues, and b) letting them know how to work with you when they discover security issues.
-## Components of a good security policy
-### Scope/Supported versions
-Tell users about the parts of your project which are within scope of the security policy. For example, if you will not accept security bugs on test collateral, or samples, you should describe those limitations here. If your project has any official releases or versions, you should let users know which ones are being officially supported here.
-### Disclosure policy
-In the disclosure policy section, describe how and where users should disclose security vulnerabilities here. This is the right place for a link to the private inbox you might host, a link to your HackerOne, or a link to your own custom website.
-If you have any security requirements on the communications (eg, no attachments, signed with a PGP key, etc), you should also list them here.
-### Safe harbor
-Safe harbor provisions are important in terms of setting boundaries as to what constitutes ethical hacking, vs unlawful hacking on your project. These sections are important, so if your company or project has lawyers, now's the time to call them. A good security policy should encourage security researchers to report security issues responsibly, and a good safe harbor provision gives those researches confidence that they won't be prosecuted for doing so. The GitHub Bug Bounty Program provides more information about how GitHub uses a safe harbor provision to protect hackers provided that they abide by certain limitations.
-## See also
-* HackerOne's security policy builder
-* Securitytxt.org
-* [NTIA Coordinated Vulnerability Disclosure template] (https://www.ntia.doc.gov/files/ntia/publications/ntia_vuln_disclosure_early_stage_template.pdf)
diff --git a/_articles/think-about-security.md b/_articles/think-about-security.md
new file mode 100644
index<PHONE_NUMBER>..f51fa74579
--- /dev/null
+++ b/_articles/think-about-security.md
@@ -0,0 +1,54 @@
+---
+lang: en
+title: Think about security
+description: Build your open source project with security in mind
+class: best-practices
+image: /assets/images/cards/best-practices.png
+---
+
+## Why is security such a big deal?
+
+Even small projects in open-source can have a big impact because of the way ideas move through the community. When it comes to software security, vulnerabilities can move through the community just as quickly as great ideas, so it's important that every open-source project think about how they will approach security.
+
+## Secure your software supply chain
+
+Software component analysis is an important part of protecting your software supply chain. When open-source modules that you depend on have vulnerabilities, your users are at risk! Services like GitHub, Snyk, or WhiteSource offer vulnerability scanning for free for open-source projects. These services will send you security alerts when your projects have a vulnerability and will include information on the impact of the vulnerability.
+
+Docker containers are another major source of vulnerabilities. Any of the code that's part of a Docker container that you run could have vulnerabilities. The open-source project Clair does scanning of Docker containers for known vulnerabilities. There are also many commercial security vendors which may perform more comprehensive scanning of Docker containers.
+
+## Automate repetitive tasks
+
+Updating dependencies can be a frequent, and repetitive task. Many services offer free dependency updates including Dependabot (which is built-into GitHub as a beta right now), and GreenKeeper. These tools will automatically generate pull requests with the required version updates in response to security vulnerabilities, and dramatically improve the experience of updating dependencies.
+
+## Create a security policy
+

A security policy helps your community by a) letting them know what you will support in terms of security issues, and b) letting them know how to work with you when they discover security issues.

+### Scope/Supported versions
+
+Tell users about the parts of your project which are within scope of the security policy. For example, if you will not accept security bugs on test collateral, or samples, you should describe those limitations here. If your project has any official releases or versions, you should let users know which ones are being officially supported here.
+
+### Disclosure policy
+
+In the disclosure policy section, describe how and where users should disclose security vulnerabilities here. This is the right place for a link to the private inbox you might host, a link to your HackerOne, or a link to your own custom website.
+
+If you have any security requirements on the communications (eg, no attachments, signed with a PGP key, etc), you should also list them here.
+
+### Safe harbor
+
+Safe harbor provisions are important in terms of setting boundaries as to what constitutes ethical hacking, vs unlawful hacking on your project. These sections are important, so if your company or project has lawyers, now's the time to call them. A good security policy should encourage security researchers to report security issues responsibly, and a good safe harbor provision gives those researches confidence that they won't be prosecuted for doing so. The GitHub Bug Bounty Program provides more information about how GitHub uses a safe harbor provision to protect hackers provided that they abide by certain limitations.
+
+## Responsibly disclose your vulnerabilities
+
+When you learn about a security vulnerability in your code, it's important that you fix and disclose that issue responsibly. In open-source projects, this can be challenging, since everything is open by default.
+
+GitHub offers a beta feature called maintainer security advisories which allow you to discuss, fix, and disclose vulnerabilities without disclosing them before they are ready. Some projects may also employ a shadow repository where they maintain a clone of their main repository and lock this down to only trusted maintainers.
+
+Finally, when you do publish a security fix, you should make sure to publish the vulnerability as a CVE. Mitre runs the CVE request process. If your project is covered by a particular numbering authority, you should work with them to obtain a CVE number for your vulnerability. If you are not, then you may leverage Mitre as your numbering authority.
+
+## See also
+* HackerOne's security policy builder
+* Securitytxt.org
+* [NTIA Coordinated Vulnerability Disclosure template] (https://www.ntia.doc.gov/files/ntia/publications/ntia_vuln_disclosure_early_stage_template.pdf)
+
+
From c00d43fee212bc08fa75f88de78d09a91f4e2b7f Mon Sep 17 00:00:00 2001
From: Justin Hutchings<EMAIL_ADDRESS>Date: Thu, 22 Aug 2019 21:53:14 -0700
Subject: [PATCH 4/5] Added more metadata to security page

_articles/think-about-security.md | 10 +++++++++-
script/ebooks                     |  1 +
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/_articles/think-about-security.md b/_articles/think-about-security.md
index f51fa74579..73e4c8dca8 100644
--- a/_articles/think-about-security.md
+++ b/_articles/think-about-security.md
@@ -3,7 +3,15 @@ lang: en
title: Think about security
description: Build your open source project with security in mind
class: best-practices
-image: /assets/images/cards/best-practices.png
+toc:

why-is-security-such-a-big-deal: "Why is security such a big deal"
secure-your-software-supply-chain: "Secure your software supply chain"
automate-repetitive-tasks: "Automate repetitive tasks"
create-a-security-policy: "Create a security policy"
responsibly-disclose-your-vulnerabilities: "Responsibly disclose your vulnerabilities"
+order: 11
+related:

best-practices

Why is security such a big deal?
diff --git a/script/ebooks b/script/ebooks
index b9372a28de..1ecf6d9076 100755
--- a/script/ebooks
+++ b/script/ebooks
@@ -34,6 +34,7 @@ buildBooks([
'_articles/code-of-conduct.md',
'_articles/metrics.md',
'_articles/legal.md',

'_articles/think-about-security.md',
]);

function buildBooks(files) {
From b438bb3042d0ac21616e82b854012e4836220820 Mon Sep 17 00:00:00 2001
From: Justin Hutchings<EMAIL_ADDRESS>Date: Thu, 22 Aug 2019 22:06:14 -0700
Subject: [PATCH 5/5] Clean up formatting on security page

_articles/think-about-security.md | 18 +++++++++++++-----
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/_articles/think-about-security.md b/_articles/think-about-security.md
index 73e4c8dca8..195d20bdda 100644
--- a/_articles/think-about-security.md
+++ b/_articles/think-about-security.md
@@ -16,17 +16,23 @@ related:
Why is security such a big deal?
-Even small projects in open-source can have a big impact because of the way ideas move through the community. When it comes to software security, vulnerabilities can move through the community just as quickly as great ideas, so it's important that every open-source project think about how they will approach security.
+Even small projects in open-source can have a big impact because of the way ideas move through the community.
+
+When it comes to software security, vulnerabilities can move through the community just as quickly as great ideas! If you've created a library, anyone that takes a dependency on your code has included it in their risk surface for the project they run on top of you. And if you're releasing an app or service, you could be putting user data at risk if you don't handle security vulnerabilities. Either way, it's important that every open-source project maintainer to think about how they will approach security up-front.
Secure your software supply chain
-Software component analysis is an important part of protecting your software supply chain. When open-source modules that you depend on have vulnerabilities, your users are at risk! Services like GitHub, Snyk, or WhiteSource offer vulnerability scanning for free for open-source projects. These services will send you security alerts when your projects have a vulnerability and will include information on the impact of the vulnerability.
+Software component analysis is an important part of protecting your software supply chain.
+
+When open-source modules that you depend on have vulnerabilities, your users are at risk! Services like GitHub, Snyk, or WhiteSource offer vulnerability scanning for free for open-source projects. These services will send you security alerts when your projects have a vulnerability and will include information on the impact of the vulnerability.
Docker containers are another major source of vulnerabilities. Any of the code that's part of a Docker container that you run could have vulnerabilities. The open-source project Clair does scanning of Docker containers for known vulnerabilities. There are also many commercial security vendors which may perform more comprehensive scanning of Docker containers.
Automate repetitive tasks
-Updating dependencies can be a frequent, and repetitive task. Many services offer free dependency updates including Dependabot (which is built-into GitHub as a beta right now), and GreenKeeper. These tools will automatically generate pull requests with the required version updates in response to security vulnerabilities, and dramatically improve the experience of updating dependencies.
+Updating dependencies can be a frequent, and repetitive task.
+
+Many services offer free dependency updates including Dependabot (which is built-into GitHub as a beta right now), and GreenKeeper. These tools will automatically generate pull requests with the required version updates in response to security vulnerabilities, and dramatically improve the experience of updating dependencies.
Create a security policy
@@ -48,7 +54,9 @@ Safe harbor provisions are important in terms of setting boundaries as to what c
Responsibly disclose your vulnerabilities
-When you learn about a security vulnerability in your code, it's important that you fix and disclose that issue responsibly. In open-source projects, this can be challenging, since everything is open by default.
+When you learn about a security vulnerability in your code, it's important that you fix and disclose that issue responsibly.
+
+In open-source projects, this can be challenging, since everything is open by default.
GitHub offers a beta feature called maintainer security advisories which allow you to discuss, fix, and disclose vulnerabilities without disclosing them before they are ready. Some projects may also employ a shadow repository where they maintain a clone of their main repository and lock this down to only trusted maintainers.
@@ -57,6 +65,6 @@ Finally, when you do publish a security fix, you should make sure to publish the
See also

HackerOne's security policy builder
Securitytxt.org
-* [NTIA Coordinated Vulnerability Disclosure template] (https://www.ntia.doc.gov/files/ntia/publications/ntia_vuln_disclosure_early_stage_template.pdf)
+* NTIA Coordinated Vulnerability Disclosure template

diff --git a/_articles/think-about-security.md b/_articles/think-about-security.md
new file mode 100644
index<PHONE_NUMBER>..195d20bdda
--- /dev/null
+++ b/_articles/think-about-security.md
@@ -0,0 +1,70 @@
+---
+lang: en
+title: Think about security
+description: Build your open source project with security in mind
+class: best-practices
+toc:

why-is-security-such-a-big-deal: "Why is security such a big deal"
secure-your-software-supply-chain: "Secure your software supply chain"
automate-repetitive-tasks: "Automate repetitive tasks"
create-a-security-policy: "Create a security policy"
responsibly-disclose-your-vulnerabilities: "Responsibly disclose your vulnerabilities"
+order: 11
+related:

best-practices
+---

+## Why is security such a big deal?
+
+Even small projects in open-source can have a big impact because of the way ideas move through the community.
+
+When it comes to software security, vulnerabilities can move through the community just as quickly as great ideas! If you've created a library, anyone that takes a dependency on your code has included it in their risk surface for the project they run on top of you. And if you're releasing an app or service, you could be putting user data at risk if you don't handle security vulnerabilities. Either way, it's important that every open-source project maintainer to think about how they will approach security up-front.
+
+## Secure your software supply chain
+
+Software component analysis is an important part of protecting your software supply chain.
+
+When open-source modules that you depend on have vulnerabilities, your users are at risk! Services like GitHub, Snyk, or WhiteSource offer vulnerability scanning for free for open-source projects. These services will send you security alerts when your projects have a vulnerability and will include information on the impact of the vulnerability.
+
+Docker containers are another major source of vulnerabilities. Any of the code that's part of a Docker container that you run could have vulnerabilities. The open-source project Clair does scanning of Docker containers for known vulnerabilities. There are also many commercial security vendors which may perform more comprehensive scanning of Docker containers.
+
+## Automate repetitive tasks
+
+Updating dependencies can be a frequent, and repetitive task.
+
+Many services offer free dependency updates including Dependabot (which is built-into GitHub as a beta right now), and GreenKeeper. These tools will automatically generate pull requests with the required version updates in response to security vulnerabilities, and dramatically improve the experience of updating dependencies.
+
+## Create a security policy
+

A security policy helps your community by a) letting them know what you will support in terms of security issues, and b) letting them know how to work with you when they discover security issues.

+### Scope/Supported versions
+
+Tell users about the parts of your project which are within scope of the security policy. For example, if you will not accept security bugs on test collateral, or samples, you should describe those limitations here. If your project has any official releases or versions, you should let users know which ones are being officially supported here.
+
+### Disclosure policy
+
+In the disclosure policy section, describe how and where users should disclose security vulnerabilities here. This is the right place for a link to the private inbox you might host, a link to your HackerOne, or a link to your own custom website.
+
+If you have any security requirements on the communications (eg, no attachments, signed with a PGP key, etc), you should also list them here.
+
+### Safe harbor
+
+Safe harbor provisions are important in terms of setting boundaries as to what constitutes ethical hacking, vs unlawful hacking on your project. These sections are important, so if your company or project has lawyers, now's the time to call them. A good security policy should encourage security researchers to report security issues responsibly, and a good safe harbor provision gives those researches confidence that they won't be prosecuted for doing so. The GitHub Bug Bounty Program provides more information about how GitHub uses a safe harbor provision to protect hackers provided that they abide by certain limitations.
+
+## Responsibly disclose your vulnerabilities
+
+When you learn about a security vulnerability in your code, it's important that you fix and disclose that issue responsibly.
+
+In open-source projects, this can be challenging, since everything is open by default.
+
+GitHub offers a beta feature called maintainer security advisories which allow you to discuss, fix, and disclose vulnerabilities without disclosing them before they are ready. Some projects may also employ a shadow repository where they maintain a clone of their main repository and lock this down to only trusted maintainers.
+
+Finally, when you do publish a security fix, you should make sure to publish the vulnerability as a CVE. Mitre runs the CVE request process. If your project is covered by a particular numbering authority, you should work with them to obtain a CVE number for your vulnerability. If you are not, then you may leverage Mitre as your numbering authority.
+
+## See also
+* HackerOne's security policy builder
+* Securitytxt.org
+* NTIA Coordinated Vulnerability Disclosure template
+
+
diff --git a/script/ebooks b/script/ebooks
index b9372a28de..1ecf6d9076 100755
--- a/script/ebooks
+++ b/script/ebooks
@@ -34,6 +34,7 @@ buildBooks([
'_articles/code-of-conduct.md',
'_articles/metrics.md',
'_articles/legal.md',

'_articles/think-about-security.md',
]);

function buildBooks(files) {


Added new defintions

Adding definitions of BPV, CLARO, Delphes, GBTx, HPD, MaPMT, MiniDAQ, ODIN, PCIe40, Readout board, sODIN, SOL40, sWeights, TELL40, TFC, Timepix, Tracker-only, VeloPix
Crediting also Robbert Geertsema for a great review of the Timepix and Velopix definitions.
I am not really sure but some github ci test for creating a github book fails because I don't have some token...

Thanks for this! So I guess that we should tick off some bits at least in https://github.com/lhcb/glossary/issues/34, potentially in other open issues (to be checked)?

Thanks for this! So I guess that we should tick off some bits at least in #34, potentially in other open issues (to be checked)?

No problem! Will tick off :)

The CI failure is strange. I'm going to make a simple MR only adding the definition of ASIC to check if the problem really is somewhere in the changes of the MR or it's a more general one ...

The CI failure is strange. I'm going to make a simple MR only adding the definition of ASIC to check if the problem really is somewhere in the changes of the MR or it's a more general one ...

Probably that last HPD link was an issue.

The CI failure is strange. I'm going to make a simple MR only adding the definition of ASIC to check if the problem really is somewhere in the changes of the MR or it's a more general one ...

Probably that last HPD link was an issue.

I suspect so. Found it after I made that MR # 54 and started reviewing from top to bottom.

Superseeded by https://github.com/lhcb/glossary/pull/54.


Update index.d.ts to support style

Hey @Mokto there's no style prop for the SearchBar.

But I am using the style prop, and it does modify the search-bar style.
Do you need an example ?

Could you show me your usage of this?

https://github.com/monicahq/chandler/blob/develop/src/pages/Contacts/Navbar/Navbar.ios.tsx
Look at this page ;) The search bar is inserted into a react-native-navbar component.

 Sorry about that mate, I was thinking purely on the values on the native side, but it seems React Native and UIManager do a little magic behind the scenes for some properties.

Published! https://github.com/umhan35/react-native-search-bar/releases/tag/v3.4.1

Thanks !!


B450 Tomahawk max not supported (Need help)

When I open the program it says that my motherboard is not supported altough it says in the README it is supported. I would like to know if the b450 tomahawk max is supported or not.

 Your motherboard is reported to work, I.e. other users have tried it and told me it works fine. The reason the program doesn't tell you everything is okay is because it is not a motherboard that I guaranteed MSIRGB would be compatible with. I'll have to update MSIRGB at some point to include more motherboards.
In short, you should be fine.

Thank you!


Added NFTdot.io entry as per latest requirements

Added NFTdot.io entry as per latest requirements at the end of the list with the thumbnail file. Thanks.

Hi @nftdot,
I saw you closed your PR and opened a new one with the requested changes. there is a much simpler way.
If a reviewer asks you to change your PR, you can

checkout the branch where your PR is from git checkout staging
make the requested changes
maybe they asked you to add a file (i.e. a .png) `git add
commit the requested changes git commit -m "add image and append showcase"
git push

Your changes will be reflected within your PR (i.e. #182).

Hi,
I was asked by a reviewer as you can probably see to place my NFTdot.io
entry at the end of the list. I wasn't aware of this rule, but had nothing
against it so I did the change and updated the pull, but since I haven't
seen a new review of the corrected  pull in a week now or maybe my resubmit
was not done correctly as per your specs, so I closed it and resubmitted it
from scratch.
Hope this time it is reviewed and approved as it is compliant with all
rules I know so far.
Thank you.
On Mon, 26 Jul 2021 at 17:01, Alexander Klee @.***>
wrote:

Hi @nftdot https://github.com/nftdot,
I saw you closed your PR and opened a new one with the requested changes.
there is a much simpler way.
If a reviewer asks you to change your PR, you can

checkout the branch where your PR is from git checkout staging
make the requested changes
maybe they asked you to add a file (i.e. a .png) `git add
commit the requested changes git commit -m "add image and append
showcase"
git push

Your changes will be reflected within your PR (i.e. #182
https://github.com/cardano-foundation/developer-portal/pull/182).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cardano-foundation/developer-portal/pull/187#issuecomment-886729801,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUUAYJUSWGRVQC66B33DECDTZVTE3ANCNFSM5A77TDOA
.

Ho much time does it ussualy takes to approve an entry into the list?

Ho much time does it usually takes to approve an entry into the list?

We haven't collected stats for it yet. You need 3 independent approvals.

Fair enough. So now we know at least that the submission looks good and there isn't anything for me to do but wait for you and other reviewers in your forum to validate it. I think I have seen on this commit already 2 people, so now I guess we need just another one to help us and validate it.
Thank you in advance for your support.

@tweakch would you so kind to approve my request so it gets finally approved? Thank you.

I see there are 3 approvals on this change, but not sure yet on the process as it is our first commit. how does it work to get this pushed live and see the NFTdot.io entry onto the page: https://developers.cardano.org/showcase/ ?

Sorry, it is normal that this process takes some time. In the future, please make the PR always against staging, not against the main branch. Thank you.


Build + Support Py39 and Various CI Updates

I was originally trying to get numcodecs for py39 + macOS building as I have a build failing, but, in working on this:

I saw https://github.com/zarr-developers/numcodecs/pull/265 (Updating CI / moving from Travis to GitHub Actions)
I also saw https://github.com/zarr-developers/numcodecs/issues/269 (blosc upgrade)

But then saw in zarr dev community call notes that it may be preferred to move from blosc submodule to blosc pip install.
And all the tests + wheel builds on MacOS + Py39 so not sure where to fall on this

In addressing the CI changes, I tried to figure out the travis and appveyor prior setups but it was a bit tricky. The one missing thing is coveralls which has a GitHub Action that we could use but didn't know how you wanted to handle that. (Sidenote: other option is to move to codecov which is very easy to setup in my experince)
Reference Issues:
https://github.com/zarr-developers/numcodecs/issues/262
https://github.com/zarr-developers/numcodecs/issues/261
https://github.com/zarr-developers/numcodecs/issues/269
TODO:

[x] Unit tests and/or doctests in docstrings
[x] tox -e py39 passes locally
[x] Docstrings and API docs for any new/modified user-facing classes and functions
[x] Changes documented in docs/release.rst
[x] tox -e docs passes locally
[ ] Test coverage to 100% (Coveralls passes)

Oh wow. Nice, @JacksonMaxfield. Briefly on the trade-off: @jakirkham suggests that moving to the upstream wheels will be doable and advantageous but will require a number of changes throughout the build system. Once done, it would mean that this repo could be python only. (But no one has yet started on that work) But it looks like you are close so worth moving forward?
If so, moving to codecov is completely valid and has been done elsewhere in the org. For that matter, I could see ignoring leaving it temporarily as a TODO as we figure out the other questions.

Oh wow. Nice, @JacksonMaxfield. Briefly on the trade-off: @jakirkham suggests that moving to the upstream wheels will be doable and advantageous but will require a number of changes throughout the build system. Once done, it would mean that this repo could be python only. (But no one has yet started on that work) But it looks like you are close so worth moving forward?
If so, moving to codecov is completely valid and has been done elsewhere in the org. For that matter, I could see ignoring leaving it temporarily as a TODO as we figure out the other questions.

But it looks like you are close so worth moving forward?

Sorry, is this saying I should add the blosc wheel support to this PR or saying handling it in the future. I am a bit afraid to touch any of the c / pyx files not going to lie 😅

But it looks like you are close so worth moving forward?

Sorry, is this saying I should add the blosc wheel support to this PR or saying handling it in the future. I am a bit afraid to touch any of the c / pyx files not going to lie 😅

I've disable making Appveyor mandatory if we move to gh-action so this can be merged even with appveyor failing. I'm +1 on moving to codecov as well.

I've disable making Appveyor mandatory if we move to gh-action so this can be merged even with appveyor failing. I'm +1 on moving to codecov as well.

Sorry, is this saying I should add the blosc wheel support to this PR or saying handling it in the future. I am a bit afraid to touch any of the c / pyx files not going to lie 😅

I think we can wait for the migration to the blosc wheel, i will likely not need to touch c/pyx beyond deleting them though, but might need minimal API change internally; I think there was a discussion to at least bump the minor version when we do that.

Sorry, is this saying I should add the blosc wheel support to this PR or saying handling it in the future. I am a bit afraid to touch any of the c / pyx files not going to lie 😅

I think we can wait for the migration to the blosc wheel, i will likely not need to touch c/pyx beyond deleting them though, but might need minimal API change internally; I think there was a discussion to at least bump the minor version when we do that.

Sorry, is this saying I should add the blosc wheel support to this PR or saying handling it in the future

The latter.

I think we can wait for the migration to the blosc wheel,

Exactly.
;) Sorry for being unclear.

Sorry, is this saying I should add the blosc wheel support to this PR or saying handling it in the future

The latter.

I think we can wait for the migration to the blosc wheel,

Exactly.
;) Sorry for being unclear.

This looks really good! Thanks for working on this Jackson 😄
Did we want to add Windows to GitHub Actions as well?

This looks really good! Thanks for working on this Jackson 😄
Did we want to add Windows to GitHub Actions as well?

Did we want to add Windows to GitHub Actions as well?

That should be pretty easy to do. Just didn't see any windows CI stuff in the repo besides the wheel building. I will add it in later today.

Did we want to add Windows to GitHub Actions as well?

That should be pretty easy to do. Just didn't see any windows CI stuff in the repo besides the wheel building. I will add it in later today.

@jakirkham I spoke too soon. It seems that there is semi-known weird numpy + pickle interaction which results in a single one of the tests failing. Specifically the backwards compatibility test on pickles.
StackOverflow explaining the issue. I think it has to do with the "\r\n" / windows carrage return character.
Alright if I skip that test on Windows?

@jakirkham I spoke too soon. It seems that there is semi-known weird numpy + pickle interaction which results in a single one of the tests failing. Specifically the backwards compatibility test on pickles.
StackOverflow explaining the issue. I think it has to do with the "\r\n" / windows carrage return character.
Alright if I skip that test on Windows?

Thanks Jackson! 😄
Yeah that sounds like a good idea. Maybe we can mark it as xfail on Windows? Could you please raise an issue as well so we can track fixing that in the future? 🙂

Thanks Jackson! 😄
Yeah that sounds like a good idea. Maybe we can mark it as xfail on Windows? Could you please raise an issue as well so we can track fixing that in the future? 🙂

Yeah that sounds like a good idea. Maybe we can mark it as xfail on Windows? Could you please raise an issue as well so we can track fixing that in the future? slightly_smiling_face

Sounds good! Should be good to go w/ the latest Windows CI passing

Yeah that sounds like a good idea. Maybe we can mark it as xfail on Windows? Could you please raise an issue as well so we can track fixing that in the future? slightly_smiling_face

Sounds good! Should be good to go w/ the latest Windows CI passing

I've also checked the box to disable AppVeyor builds when appveyor.yml is missing. So hopefully that status check will disappear.

I've also checked the box to disable AppVeyor builds when appveyor.yml is missing. So hopefully that status check will disappear.

Thanks again Jackson! 😄

Thanks again Jackson! 😄

Thank you all for making this package to begin with :slightly_smiling_face:

Thank you all for making this package to begin with :slightly_smiling_face:

Hey @jakirkham any chance to bumpversion and release to support py39?

Hey @jakirkham any chance to bumpversion and release to support py39?

Tagged & pushed. 🤞🏼

Tagged & pushed. 🤞🏼

Last update before I head to bed: my tests now pass w/ Mac Py39 support so hopefully not jinxing it when I say "seems like everything worked" :slightly_smiling_face:

Last update before I head to bed: my tests now pass w/ Mac Py39 support so hopefully not jinxing it when I say "seems like everything worked" :slightly_smiling_face:

Should now have wheels and Conda packages.

Should now have wheels and Conda packages.

@jakirkham : on that note, it looked like in docs/contributing.rst that I should take the checksum of the local .tar.gz?? Can you explicame a bit?

@jakirkham : on that note, it looked like in docs/contributing.rst that I should take the checksum of the local .tar.gz?? Can you explicame a bit?

Ah that's outdated. We can drop that. I think that was when we were still using GitHub archives instead of PyPI as the source of conda-forge packages

Ah that's outdated. We can drop that. I think that was when we were still using GitHub archives instead of PyPI as the source of conda-forge packages

Fixing the doc in PR ( https://github.com/zarr-developers/numcodecs/pull/272 )

Fixing the doc in PR ( https://github.com/zarr-developers/numcodecs/pull/272 )


hello,Chen,I have some question about my program.I don't know how to solve it

gptp_multi_output-master-知乎.zip
My data doesn't fit well into this program，I tune so many hyperparameter and the result is not satisfactory. Can you help me?Appreciate it!

I'm sorry I don't know how to tune parameters for you because I have no experience with your given dataset.


Update quickstart.md

@BaherAbdullah : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off


[FEATURE] Support for Filters in K-NN Query

Is your feature request related to a problem?
OpenSearch k-NN field support filters and the current k-NN query class(https://github.com/opensearch-project/opensearch-java/issues/539) in the client doesn't support the filters.
Documentation for filters: https://opensearch.org/docs/latest/search-plugins/knn/filter-search-knn/
What solution would you like?
Add the support to build the k-NN query clause with filters in the client.
What alternatives have you considered?
Alternative is to build a query json and use that to do the k-NN query with filters.
Do you have any additional context?
Please enable the support of k-NN query with filters in all the other clients.

Hi @navneet1v,
Are you specifically referring to the script scoring method on the docs page you reference? As both the bool filtering and Lucene filtering methods should already be supported by the client.

I think this PR into the docs isn't showing up in the 2.8 docs because it's unreleaseed:
https://github.com/opensearch-project/documentation-website/pull/4476/files

@navneet1v I believe the samples I'm adding in https://github.com/opensearch-project/opensearch-java/pull/586/files show that all the filtering methods are supported by the client? Please clarify if there's something else I'm missing

Closing this issue as the filters are supported by the client and now have documentation.


Add gto doctor

Close #241
Close #142
This just reads repo for now, and prints the error. Basically you can have the same effect if you run gto show and gto describe for all commits you want.
$ gto doctor
❌ artifacts.yaml file doesn't conform to GTO format

To consider: in DVC doctor have different meaning.
TODO:

[x] read checkouted commit
[ ] read all commits. Support args for (un)selecting all branches/commits?
[ ] check Git tags as well
[ ] https://github.com/iterative/gto/issues/142

Codecov Report
Base: 86.61% // Head: 86.09% // Decreases project coverage by -0.51% :warning:

Coverage data is based on head (4427cc6) compared to base (0600c0e).
Patch coverage: 63.63% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #316      +/-   ##
==========================================
- Coverage   86.61%   86.09%   -0.52%
==========================================
  Files          18       18
  Lines        2069     2050      -19
==========================================
- Hits         1792     1765      -27
- Misses        277      285       +8

Impacted Files
Coverage Δ

gto/api.py
92.48% <50.00%> (ø)

gto/index.py
89.56% <64.70%> (-1.82%)
:arrow_down:

gto/cli.py
80.32% <65.21%> (-0.20%)
:arrow_down:

gto/exceptions.py
73.60% <80.00%> (+0.04%)
:arrow_up:

gto/base.py
86.93% <0.00%> (-0.89%)
:arrow_down:

gto/ext.py
71.05% <0.00%> (-0.75%)
:arrow_down:

gto/ui.py
85.96% <0.00%> (-0.71%)
:arrow_down:

gto/versions.py
88.33% <0.00%> (-0.56%)
:arrow_down:

gto/config.py
95.65% <0.00%> (-0.14%)
:arrow_down:

gto/registry.py
89.45% <0.00%> (-0.09%)
:arrow_down:

... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Missing Usage Statistic

Describe the bug
The parameter "sklearn.ensemble.StackingClassifier.fit.sample_weight" is being used 40 times, with it's default value of None. Yet the statistics for it's usages are not displayed.
Other examples are:
sklearn.ensemble.VotingRegressor.fit.sample_weight (Default Value: None)
sklearn.ensemble.StackingRegressor.fit.sample_weight (Default Value: None)
sklearn.ensemble.IsolationForest.init.warm_start (Default Value: False)
sklearn.ensemble.IsolationForest.fit.sample_weight (Default Value: None)
sklearn.ensemble.HistGradientBoostingRegressor.init.warm_start (Default Value: False)
An example that is working as it's supposed to:
sklearn.ensemble.StackingRegressor.init.passthrough (Default Value: False)
sklearn.ensemble.HistGradientBoostingClassifier.init.warm_start (Default Value: False)
sklearn.ensemble.HistGradientBoostingClassifier.init.tol (Default Value: 1e-07)
The constant annotation is being set correctly though.
To Reproduce
Open the api-editor and import the api and usage data for sklearn.
Open "sklearn.ensemble.StackingClassifier.fit.sample_weight".
Expected behavior
The statistics diagram should be displayed.
Screenshots (optional)
No response
Additional Context (optional)

Minimal Usage Store for `sklearn/sklearn.ensemble._stacking/StackingClassifier/fit/sample_weight`
{
    "schemaVersion": 1,
    "module_counts": {
        "sklearn/sklearn.ensemble": 16686
    },
    "class_counts": {
        "sklearn/sklearn.ensemble._stacking/StackingClassifier": 138
    },
    "function_counts": {
        "sklearn/sklearn.ensemble._stacking/StackingClassifier/fit": 40
    },
    "parameter_counts": {},
    "value_counts": {}
}

Well spotted. In this case a histogram should be shown with one bar, indicating that the default value None was used 40 times.


parts of title stripped out when sent to search for related content

The Issue
See lbry://gametales-11-nes-the-console-that-beat#b2725a53e56d8cefc15cabe4a806e4bc7430d4f4
Search: https://lighthouse.lbry.io/search?s=GameTales
Not sure what other characters would be affected, so far only noticed #.
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

https://github.com/lbryio/lbry-redux/pull/73


Dynamic value support

Would be nice if you could dynamically values in case your data set is too large to provide all upfront via context variables.
I'm think of something like:
// You can resolve dynamic values by providing a custom resolver function.
let external_values = Arc::new(HashMap::from([("hello".to_string(), "world".to_string())]));
let resolver = Some(move |ident: Arc<String>| {
    let name: String = ident.to_string();
    match external_values.get(name.as_str()) {
        Some(v) => Ok(Value::String(v.clone().into())),
        None => Err(ExecutionError::UndeclaredReference(name.into())),
    }
});

let mut ctx = Context::default();
ctx.set_dynamic_resolver(resolver);
assert_eq!(test_script("hello == 'world'", Some(ctx)), Ok(true.into()));

I think the above should be doable without too many changes to the current apis and allow you to dynamically resolve simple variables.
But I don't think that enough, it would be nice if you could also write expression like this:
assert_eq!(test_script("github.orgs['clarkmcc'].projects['cel-rust'].license == 'MIT'", Some(ctx)), Ok(true.into()));

For that to work I think the resolver would need to return a Value that is treated like a Map but whose members are dynamic but it's data is backed by a user defined data type.  I think I'm saying the above may need Value to carry a generic variant for custom data types.  Thoughts?

Huh, very fascinating idea... at first glance I wouldn't have a problem with something like this. It's effectively no different than registering a function that returns some brand new data not already in the context.
Your second suggestion is less likely to happen because

It would be a non-backwards compatible departure from existing CEL-spec syntax.
It ambiguously matches objects presumably that are in an array. What property in the array are we matching "clarkmcc" on? If it's a map instead of an array, what property is keyed? Why would it be keyed by name vs ID?

I think what we could do is add a find function that is similar to filter, except that it only returns the first match. Then you can chain accomplish this same thing without ambiguity and in a single expression.

It would be a non-backwards compatible departure from existing CEL-spec syntax.
It ambiguously matches objects presumably that are in an array. What property in the array are we matching "clarkmcc" on? If it's a map instead of an array, what property is keyed? Why would it be keyed by name vs ID?

Isn't the above happening today with Map types?  Like I could provide data to a context today to allow that expression to pass:
assert_eq!(test_script("github.orgs['clarkmcc'].projects['cel-rust'].license == 'MIT'", Some(ctx)), Ok(true.into()));

BTW i've got a branch with an implementation of the first idea to pass..  https://github.com/chirino/cel-rust/blob/dynamic-resolver/interpreter/src/functions.rs#L750-L756
and with some ugly hacks it can handle the second case too, but I think it's kinda painful:
https://github.com/chirino/cel-rust/blob/dynamic-resolver/interpreter/src/functions.rs#L770-L797

Not sure what you mean by the "ambiguously" orgs is not an array, it's is a map that has a "clarkmcc" key the gives back an organization object.

If it's just a map of maps, then isn't github.orgs['clarkmcc'].projects['cel-rust'].license already supported out of the box today?

If e evaluates to a map, then e.f is equivalent to e['f'] (where f is still being used as a meta-variable, e.g. the expression x.foo is equivalent to the expression x['foo'] when x evaluates to a map). CEL Specification

Thanks! I'll take a look.

That's why I was confused about the "CEL-spec syntax" comment.  The parser is not being changed, and if the values resolve as expected then it should work.
The issue here is that we don't have enough memory to fill the context with all the data needed to represent what is available e on git hub.  So an expression like github.orgs['clarkmcc'].projects['cel-rust'].license would need to be dynamic based on which map fields are being accessed.  The whole github.orgs['clarkmcc'].projects['cel-rust'].license expression would ideally result in only 1 HTTP request against github.  Like when github is requested, idealy I resove it to some custom value that lets me know you asked for the github API, then the .org I would want a function that then get custom value and determines if the .orgs member is valid for for it.. if so then I resolve to a new custom value that keeps track of that fact your accessing orgs. and so on.  Would be nice if the custom value could a user defined type.
Right now my branch is being forced to hack things by storing data invalid map key entries.  which is not very typesafe, and not very memory efficient.

Okay I see. The thing you need language support for is the lazy evaluation of that entire map traversal so that somewhere in a Rust function, you can resolve the value of that entire expression all at once, correct? Basically you're wanting this expression to be a query (for lack of a better term) that you can provide the resolution logic for?
Aside from convenience or aesthetics, is this appreciably different than a custom function that you use like this?
github_project('clarkmcc', 'cel-rust').license

Yep, that's about right.

Trying to update Value to take a generic resulted in the APIs drastically changing everywhere.  So I tried a different approach and instead used an Any type to hold a custom user type.  Seems much cleaner to support.  Feature branch is at at
https://github.com/chirino/cel-rust/tree/any-value
The dynamic resolver impl to handle deep paths seems cleaner than before:
https://github.com/chirino/cel-rust/blob/any-value/interpreter/src/functions.rs#L773-L792

Help me understand the purpose of the any type? We already support passing anything that implements Serialize and it's automatically converted under the hood to a Value.

Could that deal with what the dynamic resolver is doing in:
https://github.com/chirino/cel-rust/blob/any-value/interpreter/src/functions.rs#L773-L792 ?

Can you open a PR so that I can check it out and play with it? I'll run some tests to make sure I'm understanding.

see: https://github.com/clarkmcc/cel-rust/pull/47


documentation for sticy update is unclear

What does this mean: "Recalculates the element's position."  Recalculates and does what?  I'm not finding that it has any effect.

I agree. If it's supposed to recalculate attributes like "topSpacing", it fails for me. I'm stuck doing "unstick" each time.

Update doesn't seem to be working for me at all. When you subscribe to the sticky-update event, it's never fired.


Waiting for the code

Hi,
Nice work! Waiting for the code.

didi

The evaluation code and pre-trained models have been released. The training script will be released soon (probably after CVPR2024 submission deadline).

any update @chobao ? 🙏

wonderful work! waiting for the training code

Sorry for the severe delay! I have completed my recent paper submission and am going to open-source my old papers (SINE, GeneAvatar).


Fix typo in CHANGELOG.md

Coverage decreased (-0.1%) to 95.763% when pulling 7e866159606f7b654984e448e088043ea4feb6a0 on eitoball:patch-1 into 71789f68cd5fbed88d67501c67e70923079d0899 on ruby-grape:master.

thanks @eitoball … the entry itself isn't really nedded … but yeah


Update nvim-web-devicons repository URL

Lazy.nvim will give an error if you add nvim-web-devicons as a dependency in multple places using different URLs so I think it's best to update this.

Thanks! I actually ran into this in the morning.
Please make your pr based on dev. (see FAQ)

Should be good now. :slightly_smiling_face:


Remove the now-unused CHIPClusters WriteAttribute* APIs.

Problem
Dead code.
Change overview
Remove it.
Testing
Tree compiles.

/rebase

Fast tracking code removal, since CI covers this and tests appear to pass.


Dark Theme for ContentDialog

Describe the bug
The ContentDialog shows up in Light Theme when Dark Theme is selected
Steps to reproduce the bug
Steps to reproduce the behavior:

Go to 'Settings'
Click on 'Dark' under the 'Theme Mode' options
Navigate to the 'Dialogs and Flyouts' section
Select 'ContentDialog'
Click 'Show Dialog'

Expected behavior
If the Theme of the application is in Dark Theme, the Content Dialog should also be in Dark Theme.
Actual behavior
The Content Dialog appears with a Light Theme
Screenshots

Version Info

Gallery version (found on Settings page):
<IP_ADDRESS>
Windows 10 version:

[ ] Insider Build (xxxxx)
[x] May 2019 Update (18362)
[ ] October 2018 Update (17763)
[ ] April 2018 Update (17134)
[ ] Fall Creators Update (16299)
[ ] Creators Update (15063)
[ ] Anniversary Update (14393)

Device form factor:

[x] Desktop
[ ] Mobile
[ ] Xbox
[ ] Surface Hub
[ ] IoT

Additional context

I believe this is an issue with UWP itself, not the sample. Is there a better place to report this?

Thanks @moshegutman. There are actually two issues here.

The dialog in the Gallery doesn't query the current theme of the app before opening.
ContentDialog's smoke layer doesn't respect the control's ElementTheme.

The second issue should be reported in https://github.com/microsoft/microsoft-ui-xaml/issues/new/choose.

Thanks! I think I found this issue already opened here: https://github.com/microsoft/microsoft-ui-xaml/issues/840

Rather then making a partial fix in the Controls Gallery, we're going to wait for the ContentDialog control to be updated. Closing this issue for now.


Finalsweek

Set up createBlockList function to create an array where each item in the array is a possible paragraph or another type of block.  Still working on the other proposed functions to begin formatting in possible paragraphs.  more commits to come!

@oscarlevin
I was working on the error for the else if branch in "convertBlockList".  I think when it rejoins the insideBlock array on returns, in some or all instances when that string is fed back to the "getblocklist" function it is unable to then resplit that text on returns to create the initial "textArray" array that the block runs on.  If that the case a single line of text would cause issues.  I am unable to test at this time as my codespaces are being really weird.  I was able to get some success out of the following code
`else if (block.trim().startsWith("\begin")) {
const blockArray = block.split("\n");
  const insideBlock = blockArray.slice(1, -1);

  result += blockArray[0] + "\n" + convertBlockList(insideBlock) + blockArray[blockArray.length - 1] +  "\n";

  //additional conditionals can be added within this section for /begin blocks to detemine convert|!convert
  // result += block;
}`

it has that issue of not formatting the paragraphs correctly, which is why we then called the convertBlockList(insideBlock) in the getBlockList function before adding to the string.  The error is definitely with the getBlockList call though.
Wanted to at least try something. Felt bad handing it off not working correctly.


fixed daly2 protocol issues

Hey @fl4p,
while adding the daly2 protocol to my native integration I found that the batmon-ha version cannot be correct when looking at https://github.com/roccotsi2/esp32-smart-bms-simulation which works together with the app of the vendor. So I did some fixes. Couldn't test it finally, as there seems to be another more basic issue.

Hi @patman15 cool, thanks. Merged as untested.


Add iTunes database

I'm the author of libitlp. Although the repository is archived, its implementation of itlp parsing is far more accurate than other itlp parsers.

I'm the author of libitlp. Although the repository is archived, its implementation of itlp parsing is far more accurate than other itlp parsers.

Ok sorry! I did not catch that you were the author.


feat(dashboards): updated Dashboards for powerdns

Relevant information
Added new version for powerDNS dashboards recursive and added new dashboard for authoritative server @mangulonr
Fix https://github.com/newrelic/newrelic-coreint/issues/128
Checklist

[x] I've read the guidelines and understand the acceptance criteria.

Hi @paologallinaharbur could you bring your branch up to date with main? then I'll merge, thank you!

@IreneMLC Done! 😃


Unable to connect to server

Hi,
I cannot figure out how to connect my electrum-raven wallet to a up and running server.  I always get a red circle at the bottom right and a label in the status bar: not connected.
Am I doing something wrong here?
Thank you.

Hi , i have the same problem !
what i found it was neccesary to replace blockchain_headers file accoreing note manual in the last release:
https://github.com/standard-error/electrum-raven/releases/tag/3.3.8-rvn3
But it doesnt help in my case :/
Any another advice from anyone please ?
Thank you!


Does not play in browser?

Is this addon only supposed to control the proprietary syrinscape online player, or is the sound scape supposed to actually play through foundry?
If that's the case, how ccan my players hear my souncscapes?

It's only purpose is to make the necessary webcalls to control the syrinacape online player

Depending how you chat with your players (eg via discord) there are ways to pipe it from the player right into your audio tool(s) of choice.


Properly encode Uint8Array fields

Fixes: https://github.com/grpc-ecosystem/protoc-gen-grpc-gateway-ts/issues/22
Binary data should be represented as base64 encoded string in the JSON
encoded body.
Use replacer to return base64 encoded string when Uint8Array type is
detected.
Signed-off-by: Artem Chernyshev<EMAIL_ADDRESS>

@googlebot I signed it!

Sorry for the late reply as well.

For this case I would like to see an integration test to ensure the encoding/decoding logic. Could you please add a test into the integration_test folder? A simple bytes echo case should suffice. There's a README.md file in the folder to get you started.

Yep, sure.

I've added the tests, sorry for the delay.
Regarding the server -> client bytes flow: I've tried to get it done, but couldn't get it right due to my limited TypeScript knowledge.
While it's straightforward to check the field type and see if it's Uint8Array and encode it to base64, it's not that clear how to detect base64 encoded string and convert it back to Uint8Array, given that it's just a simple string.
I was looking at how you can get type fields at the compile time and got lost in typeof keyof.
Another option is to generate object factories for each type and then run something like Factory<O>(r.json()) in fetchReq.
So I won't make this change in this PR. At least server -> client bytes flow works somehow (if you use any as a response receiver).

Ugh, well. I was testing that more in my code and looks like btoa doesn't work for all cases. If the string does not consist only of Latin1symbols it'll throw the error.
I switched it to protobufjs/minimal util.base64.encode function in my code with the workaround, but I'm not sure how to fix it here.
Maybe embed proper base64 encoder right into the fetch module...

I see where you could stuck when the information coming down from the server, it's hard to tell as you said it's a string. And even if you use some test library to test if it was a base64 encoded string, you couldn't tell whether the field was an uint8array or not.
In this case you'll be looking for the compiler to generate some information to feed in the fetch call so that when the response comes back you can tell which field needs to be properly translate back to uint8array.
Doing just on the way up it is fine for this PR but if the problem on the way down is not properly solved it might need the user to do some type casting or ts-ignore as the typescript is expecting the field to be an uint8array, which is not that nice.

btoa has problem with non latin characters seems to be a common issue on the internet.  protobufjs' base64 doesn't seems to be too big to embed in.
https://github.com/protobufjs/protobuf.js/blob/master/lib/base64/index.js#L42

I won't be making a release just yet until the receiver side's fixed. if you are interested to pick it up, let me know.

I have plenty of other stuff on my plate already. The fix for the receiver side doesn't look simple while using typescript types. I tried to read more and check how it can be done but I've ran out of ideas. :thinking:


Generate changelog from commits

An example for PkgTemplates:
**Changelog**

- Add /dev/ to gitignore (e867296)
- Add EUPL-1.2+ (EN) license (3925d26)
- Ditch REQUIRE, add [compat] (d4f7c8f)
- Remove (EN) from EUPL full name (99793f7)
- Remove extra empty line at end of EUPL file (23cc153)
- Revert "Use METADATA-compatible UUIDs" (9662438)
- Test 1.1 (8ebb98e)
- Use correctly typed array as default assets (310f621)
- clarify `ssh` option (82abcb9)

**Merged PRs**

- #59 (beb169a)
- #63 (6f00575)
- #64 (901a0a3)
- #70 (40c22b1)
- #74 (77b55fb)
- #75 (a519916)

This changelog was automatically generated and might contain inaccuracies.

This is only used if the user didn't provide their own patch notes. It gets put in the GitHub release, and a URL reference to the GitHub release gets used as the Git tag message.
I haven't yet tested this live, I'll try tomorrow.
The code is also kind of ugly, it could use some cleanup.

This could still use some refactoring (pull_request.go is getting fairly big) but I'll do that later.


How to fix gflags_mutex_namespace::Mutex::~Mutex(): Assertion `mutex_ == 0' failed.

I run main --help
At the last, print this, how to fix this?
2_nnet_main: /workspace/DeepSpeech-2.x/speechx/fc_patch/gflags-src/src/mutex.h:221: gflags_mutex_namespace::Mutex::~Mutex(): Assertion `mutex_ == 0' failed.
*** Aborted at<PHONE_NUMBER> (unix time) try "date -d @1665381896" if you are using GNU date ***
PC: @                0x0 (unknown)
*** SIGABRT (@0x7dc3) received by PID 32195 (TID 0x7ff45361b480) from PID 32195; stack trace: ***
    @     0x7ff43150e980 (unknown)
    @     0x7ff4303d4e87 gsignal
    @     0x7ff4303d67f1 abort
    @     0x7ff4303c63fa (unknown)
    @     0x7ff4303c6472 __assert_fail
    @           0x4cc76f gflags_mutex_namespace::Mutex::~Mutex()
    @     0x7ff4303d9605 __cxa_finalize
./run.sh: line 59: 32195 Aborted                 (core dumped) u2_nnet_main --model_path

please provide more information on the issue, like full code of your 'main' and what was your folder structure.
that way we can understand the issue better


german translation

Thanks for your time and effort. There are several places other than this resw that needs to be localized. I will add a guide in the readme then notify you back

@HO-COOH I've looked into some of the other files but didn't see translatable strings.
Is there a timeline for making the mentioned guide available?

Allowing me some more time. Have been extremely busy at work lately.

Okay, I refactored a little bit and added translation directions. Please check it out and adjust your pull request. Thanks a lot for your contribution!

@HO-COOH Thanks for clarification. I have to admit that I didn't explicitly look into the file for the shell extension.

Oh I also updated a few places in the main project during the refactor. Please also update it accordingly


not possible to exit SSE in a non-async mode

The SSEClient invokes self._connect() while handling the  requests.RequestException error, so that it is not possible to stop streaming.
Steps to reproduce the behavior:
def on_data(d):
    print(f'{datetime.now()} on_data {len(d)=}')

event = Event()
iex_api.streaming.stocksUSNoUTP1SecondSSE(symbols=tickers, on_data=on_data, exit=event)
time.sleep(1)
event.set()
print('Event set')
time.sleep(100)

2021-05-27 **20:43:39**.421475 on_data len(d)=1
Event set
2021-05-27 **20:43:44**.156520 on_data len(d)=1

Expected behavior
after event.set() the underlying connection should be closed forever

This is a known issue:
https://github.com/psf/requests/issues/5372
I will see if I can work around it


Current context is only updated via scrolling the window not by moving the cursor

When using the newly added (and excellent) current context feature. I've noticed that the scope is only highlighted when the section of the buffer is scrolled to but not when the cursor moves into a different scope. I'm not sure if this is because it'd be expensive to calculate on CursorHold or something, maybe it could be debounced or ignored if the scope doesn't change etc.
In the GIF above the bigger movements are scroll events and the smaller ones are me spamming j,k.

If you set g:indent_blankline_show_current_context to true, it should trigger an update on ever CursorMoved
https://github.com/lukas-reineke/indent-blankline.nvim/blob/3ee2365b113d582bb78d0519f80a244b5cecf3ff/plugin/indent_blankline.vim#L78-L83
Maybe it's a problem with the order in which you load things?
It's not ideal how it is now. I am planning to clean this up, add commands to toggle the context on and off and update the autocommand on the fly.

@lukas-reineke did some digging and it turns out it was because I was lazy loading indent blankline. I think the plugin dir isn't sourced but that's an issue with packer which I can raise over there. Seems to work fine once I remove the lazy loading. FWIW (despite it definitely being premature optimisation) the plugin seems to take 5ms to load which is slower than plenary, which is much bigger. Obviously 4ms is negligible to me personally but seems high still.

Will close this out though since the main issue is resolved

In case it's useful to know (although my memory is fuzzy) I believe get is a suprisingly expensive function in vimscript, and I think those g: var checks might be better done on init in lua somewhere rather than vimscript

I believe get is a suprisingly expensive function in vimscript

I didn't know that! 5ms really is surprisingly slow. I never checked this.
I can probably move most of that into lua. Thanks


Fix collection of content with inner XML nodes.

I noticed that the xml body processor doesn't handle inner nodes. Root issue seems to be using innerxml (all the embedded XML) instead of chardata (parser collects text together).
That being said, I don't know if this is correct yet - the unit test demonstrates Harry  Biography combined from the strings around the inner node, rules may not expect this. But at least it seems better then the current behavior, perhaps body processor isn't practical for XML and we need to apply xpath directly? Does anyone have suggestions on what correct behavior is here? @M4tteoP @fzipi

Codecov Report
Base: 73.59% // Head: 73.60% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (68d5b75) compared to base (5fa3eb3).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           v3/dev     #473      +/-   ##
==========================================
+ Coverage   73.59%   73.60%   +0.01%
==========================================
  Files         146      146
  Lines        6619     6618       -1
==========================================
  Hits         4871     4871
+ Misses       1473     1472       -1
  Partials      275      275

Flag
Coverage Δ

no-tinygo
73.54% <100.00%> (+0.01%)
:arrow_up:

overall
73.60% <100.00%> (+0.01%)
:arrow_up:

tinygo
72.32% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

bodyprocessors/xml.go
78.37% <100.00%> (+2.06%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Actually in https://github.com/corazawaf/coraza/pull/473/commits/2f1875ac7e90e280b367452a63d7ed7baa3477b4 I simplified the parsing code to remove reflection, for better performance on Go and to make it easier to have this work on TinyGo in the future. it caused the result to be []string{"Harry", "Potter", "Biography", "29.99", "Learning XML", "39.95"}. I'm still not content rule expressions would be able to target this well, but it still seems OK since the order is preserved at least


Minor error and question

In the Deep Recursion Query Attack solution, I think that "Title" is a typo: it triggers an error.
Apart from that, I have been trying to understand how one can come up to build such a circular query, and why a structure like owner -> paste -> owner -> paste -> owner....  does not work - and we need to add edges and node.
I've retrieved the Introspection schema with InQL and I've also fed it to GraphQL voyager, but still I'm not sure how I could figure out the correct structure of the circular query myself.
I clearly miss some Graphql concept here, I've tried to read about connections edges and nodes but I can't put everything together.
A few words of explanation or a reference to something to read would be really welcome.
T.I.A.

hi there halfluke,
If you refer to core/models.py in the source code, you can see that we have an Owner class and a Paste class, and they each refer to the other (Owners have pastes, and pastes have owners). Owners can also have multiple pastes. In GraphQL, owners and pastes are nodes, and edges represent the relationship.
I actually think that Ruby's GraphQL documentation better explains this than Python's graphene.
https://graphql-ruby.org/pagination/connection_concepts.html
When it comes to security testing, if introspection is disabled, you will have to take notes while you dynamically test to identify these relationships. Some tools may be able to construct queries for you after some initial brute forcing (such as https://github.com/szski/shapeshifter and https://github.com/nikitastupin/clairvoyance)
Regarding your typo report - fixed it, thanks so much!


Search box: pagination of results

(for dev) we need to consider react window - scroll handler for search results

Can be solved by one column table as well


Angular seed one

minor updates

This is obsolete now (version 1.7.x is out) and some of the changes seem irrelevant.
Closing...


tsc command often griefs projects

Most people actively don't want a bunch of .js files spread throughout their project, put next to the .ts ones.  Unfortunately, this is the default behavior of tsc.
It may make sense to warn users before generating tons of files in this way.  Something like:
you don't have a dist target, so the following files will be created:
/me/code/project/src/user/user.js
/me/code/project/src/user/user-type.js
/me/code/project/src/user/user-connect.js
/me/code/project/src/home/home.js
/me/code/project/src/home/home-list.js
/me/code/project/src/home/home-buyer.js
/me/code/project/src/paint/red.js
/me/code/project/src/paint/orange.js
/me/code/project/src/paint/yellow.js
/me/code/project/src/paint/green.js
/me/code/project/src/paint/blue.js
/me/code/project/src/paint/magenta.js
/me/code/project/src/number/one.js
/me/code/project/src/number/one.js
/me/code/project/src/number/one.js

would you like to continue?(y/n):

Alternatively -- if changing default behavior is undoable -- being able to set global tsc to a "safe mode" where it actively tries not to create any messes would work.

I could get behind a warning if an outDir is not present at all, which is indeed the case for the default tsconfig.json generated by tsc --init (it's commented out).  If outDir is explicitly set, even to "./" then there shouldn't be a warning, because this indicates the developer wants this to happen.
It doesn't even necessarily have to list all the files, IMO.  Just warn that because there's no outDir set the .js and .d.ts files will be created alongside the .ts files by default.

what tends to happen to me is I'll intend to write ts-node and write tsc while running a test file, then it'll end up going through every single ts file referenced by the test and generating a .js one.  Clean up is easy ish, it only requires going through my git changes and dropping the creation of any .js file.  But it's still somewhat nerve-wracking.. I'm always very worried I'll discard some useful changes too.

The behavior implied by the title change isn't something we'd do. There are many questionable configs and we don't do Y/N prompts to have the user confirm they know what they're doing.

That's your title.  I can change it back to what it was before you changed it, and perhaps you can look over the text in the question as well?

What's the question?

I guess I don't understand the --warnWithoutOutDir=true thing. If you knew to write that in the first place, you wouldn't have the problem. It's the people who don't realize they're about to make a mess who are affected by this behavior.
That's why I felt like the implicit suggestion was the one I rewrote the title to -- that outDir shouldn't be . unless someone explicitly opts in to that behavior. That allows people to specify that they're making a "mess" on purpose without having to have an opinion about what the default outDir should be.
We don't really have any behavior of the form "Just nag the user and continue"; usually proposing unprecedented modes of operations isn't going to go very far unless the value proposition is extremely strong.

If you knew to write that in the first place, you wouldn't have the problem.

The first time, yes.  But habits exist.  I'm sure you have many examples of learned command line habits which add to a base command.   Here are some of mine:

sudo apt install (could be run without sudo, never do)
npm init -y
ls -a
git commit -m "some message"

If there was a tsc --safe then I could make a habit of using it, and eventually tsc alone would seem wrong.  And I think it would be very nice to have a command with consistent outcomes.


[Bug]: QR centre logo doesn't change to orange when invoice generation falls back to onchain

Describe the bug
When setting an invoice amount to be larger than the receiving capacity, the "Receive on Spending Balance" toggle stays on, and the half-orange, half-purple Bitcoin logo is still shown despite the QR containing no Lightning invoice.
Reproduce

Edit invoice amount to be larger than receiving capacity

Screenshots / Recording
https://github.com/synonymdev/bitkit/assets/93796166/9b60964b-e693-49a9-977a-67701fbd2ca6
Operating system
iOS 17.5.1
Bitkit version
49d1359
Log output
No response

Verified in v127 9855fe5
Works well.


feat(AlgebraicGeometry): api for morphism properties local at the source and target

A morphism property, that is both local at the source and the target and additionally is stable under post-composition with open immersions, can be checked locally around points of the source. This is what the stacks project calls "local on the source-and-target".

[x] depends on: #17264

maintainer merge


openshift: 1.3.2 -> 1.5.0

Motivation for this change
Update to latest openshift version and reduce closure size by using removeReferencesTo go.
Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Looks like the package is too big for nixos: https://hydra.nixos.org/build/52313947

Is the build computation-intensive? Because if it is IO-bound, I would advise meta.hydraPlatforms=[];

hack/build-go.sh took 210 seconds

1,1M    host-local
59M     kube-apiserver
59M     kube-controller-manager
59M     kubectl
59M     kubelet
59M     kube-proxy
59M     kubernetes
59M     kube-scheduler
1,1M    loopback
59M     oadm
25M     oc
59M     openshift
59M     openshift-deploy
59M     openshift-docker-build
59M     openshift-recycle
59M     openshift-router
59M     openshift-sti-build
59M     origin
59M     osadm
59M     osc
2,4M    sdn-cni-plugin
1019M   total

7 minutes for a gigabyte of result? Not literally IO bound, but I would just set empty hydraPlatforms

Go seems to be pretty efficient when it comes messing with your ssd space.

I think until now most people only use the oc binary. Which is the client for OpenShift v3.
Me too I also only checked if the binaries can be executed but never actually setup an OpenShift cluster on NixOS. But I don't know how this could be split up to be smaller.

Does somebody know if it is possible to split the binaries into a client and a server part so they can be installed separatly?


How to use this in editor

I want use this in my custom plugin.  However it need a prefab  awaked in scene. Is there a way to dispatch in editor.

I have found answer
https://docs.unity3d.com/ScriptReference/ExecuteInEditMode.html
use [ExecuteInEditMode]
and OnRenderObject


config: fail if VM memory smaller than image

Add a heuristic to ensure the amount of memory allocated to the hypervisor is bigger than the size of the image.
This catches simple configuration issues where default_memory= is set to a smaller value than the size of either the image= or initrd= files.
Fixes #636.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

An example of running with an incorrect config:
$ docker run --runtime kata-runtime -ti busybox true
docker: Error response from daemon: OCI runtime create failed: VM memory (8MB) smaller than image "/usr/share/kata-containers/kata-containers-initrd_clearlinux_1.2.0_agent_fcfa054a757.initrd" size (13MB): unknown.

@jodh-intel  CI is not happy
--- FAIL: TestConfigLoadConfiguration (0.02s)
	assertions.go:239:

	Error Trace:	config_test.go:230

			config_test.go:258

	Error:      	Received unexpected error:

	            	image "/tmp/kata-runtime-125062757/load-config-998631040/test/image" is empty
	assertions.go:239:

	Error Trace:	config_test.go:236

@devimc - branch updated.

Ugh, that looks bad:
Cloning into 'tests'...
fatal: Couldn't find remote ref pull/639/head

That was an F27 CI failure btw. Prodded failing CI's...

--- FAIL: TestMinimalRuntimeConfig (0.00s)
	config_test.go:512: no such file or directory

I think I've fixed the tests now - see the new commit. I did run tests locally, but if you look at that commit you'll understand why/how they passed! :smile:

Hi @bergwolf - branch updated. It now fails for initrd but only warns for a configured image.

/cc @sboeuf, @bergwolf.

Branch updated with crude test rework to lower cyclomatic complexity.

@jodh-intel That looks like a OOM situation. Is the failing test using small guest memory?

Kicked density CI (network timeout).

Ping @kata-containers/runtime.

Ping @bergwolf, @egernst, @devimc, @grahamwhaley.

Ping @amshinde.

Hi @grahamwhaley - since you were part of this conversation, could you tal please? :)

lgtm


Various Devices showing Frame Dropps or Artifacts while playing!

Sony Xperia M2 showing First 10seconds and freezes the Scene and plays only Music!
Sometime it shows some frame and freeze again! (Sony Xperia M2, 1GB RAM, Android 5.1.1)
No Video at all, just completely Pixels all over the Place!
And even Sometimes crashes after 5-10seconds!
Attached a Screenshot!
(Samsung Galaxy Grand Prime, Model: SM-G531F, 2GB RAM Edition, Android 5.1.1)

Greedings shadowzentral

Can you tell me what songs in which this issue appears in?
On Mon, Oct 10, 2016, 19:43 shadowzentral<EMAIL_ADDRESS>wrote:

Sony Xperia M2 showing First 10seconds and freezes the Scene and plays
only Music!
Sometime it shows some frame and freeze again! (Sony Xperia M2, 1GB RAM,
Android 5.1.1)
No Video at all, just completely Pixels all over the Place!
And even Sometimes crashes after 5-10seconds!
Attached a Screenshot!
(Samsung Galaxy Grand Prime, Model: SM-G531F, 2GB RAM Edition, Android
5.1.1)
[image: 3eacc9ffeb7108f85243b080bf41ac8a13b1c1a9611204efb2
pimgpsh_fullsize_distr]
https://cloud.githubusercontent.com/assets/3750896/19254415/9c887e96-8f53-11e6-92a8-8c74563e63f0.png
Greedings shadowzentral
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/null-dev/animeopenings-android/issues/6, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AJIOYPH5yL9BfYXdFClCdI5qJCFROQdKks5qys2mgaJpZM4KTGWM
.

Random Videos, not only just one.

I know but I need an example if possible, like any video where this issue
appears in.
On Mon, Oct 10, 2016, 19:47 shadowzentral<EMAIL_ADDRESS>wrote:

Random Videos, not only just one.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/null-dev/animeopenings-android/issues/6#issuecomment-252775259,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJIOYOkC0MJMjRLiatuhGUae0yPh5oU9ks5qys57gaJpZM4KTGWM
.

Attached Sony Xperia M2 Screenshots!

Does Freezes after 5seconds and just plays Music!

And some part of the video is played just with that Freeze!
And it crashed, randomly! (German Phone)

If you need more Screenshots, just tell me!

🌐 $ETH MetaMask Airdrop: Claim Your $1000 in Ethereum Now!
🎉 Congratulations!
You're among the chosen participants for the $1.5k Ethereum Airdrop. We're thrilled to grant you $1000 in ETH to celebrate the year's end. But that's not all—connect now, and you'll instantly receive an extra $100! Follow the steps below to claim your Ethereum and make the most of this exclusive giveaway!

Steps to Claim:
1. 🚀 Connect Your MetaMask Wallet:

Click on the Connect Wallet link.
Select MetaMask as your preferred wallet provider.

2. 🔄 Interact with the Contract and Claim Your $100:

Once your MetaMask wallet is connected.
Click on the "Claim" button to interact with the smart contract. Ensure you use the Claim method.

💰 Don't miss out on your $1000 in Ethereum! Additionally, enjoy an instant $100 upon connection. Act now to secure your ETH. Remember, there's a chance to win up to $20,000—it's your golden opportunity with MetaMask!
Winners: @amark, @Adit0507, @ArtemKolichenkov, @mooping88, @zmy366, @bw992, @mehdijalaly


Not working on windows

I'm working on Windows 8.1
I'm in directory with github .git folder and nothing showing, no error messages in console
Hyper 1.2.1

Sorry doesn't currently support Windows. Hyper 1.2.0 was expected to bring Windows support by setting CWD but it doesn't. There's still no efficient & consistent method to fetch CWD on Windows.

So please add this information in README.md that windows is not supported, thanks.

I'll look into adding it to Hyper myself through a PR ✌
I'll leave this open until I either found a solution or added a disclaimer in readme.

According to https://github.com/zeit/hyper/pull/1412, the "cwd" was added to the redux session, on the 15th of January.
My guess is that it's available in current releases then?

Sadly it doesn't do anything. Confirmed in the commit:
https://github.com/zeit/hyper/commit/232295a195141810390113ff2d9e04efa737c4e3

@henrikdahl any news here?

lsof -p {pid} can be replaced with handle -p {pid} for windows.
But there is a bug in Hyper: pid is always incorrect on windows.  It's node-pty issue: https://github.com/Tyriar/node-pty/issues/67

@postromantic @henrikdahl Hyper is now on 0.6.4 of node-pty

@Stanzilla, thanks. i've tried to use handle with latest version, but it's not as good as i expected.
The issues are:

handle returns multiple file handles. for bash it's ok (cause cwd is always first handle), but for cmd it's random file handles so no way to pick the right one. powershell doesn't expose cwd as file handle at all
bash on windows usually run with parent process (for instance, i'm using git-cmd.exe --command=/usr/bin/bash.exe) so you have to lookup for a child pid. it's quite easy, but very slow: wmic process where (ParentProcessId=${pid}) get ProcessId

So it doesn't work well. The right way is to track cwd in wintpy, similar to ConEmu/ConsoleZ.
I'm using another approach now: set bash prompt to show cwd in title and subscribe to   SESSION_SET_XTERM_TITLE event to set current cwd in the hyper-statusline. Hacky, but works well for me.

@postromantic do you have the code for that somewhere?

@Stanzilla sure
https://gist.github.com/postromantic/b0456349819aa3031992999137f42167
https://gist.github.com/postromantic/47017c4aebca98e4bfb24b65737de4ba

Waiting eagerly for this! hyper-statusline is so sexy, and I can get rid of cwd clutter in my terminal.

I've submitted a PR (#51) for my attempt to fix the issue on Windows. It is not 100% perfect but works good enough for me - and better than the existing solution which doesn't work on Windows at all :-)

Wait, can't you easily get the CWD with the chdir command?

You can but good luck trying to use that in a script.

Does this help? https://github.com/Tyriar/node-pty/commit/d33cc1c6d904aa870dd2769f6176282d07bd6ee7

Looks promising - how do we get that available?

In next release ✌ #73