BigQuery Working with Google App Engine

Is there a way to have the BigQuery Go Library with a version that works with Google App Engine.  Have it working with the flexible model, but want to have it work with the standard model as well.

You'll likely have to wait for App Engine Standard to upgrade past Go 1.6.

I don't think this has to do with the go version. All of the client libraries should support go 1.6.

@jba @zombiezen

Looked further and believe the problem is more to do with the http call. AppEngine requires "urlfetch" to be used while the normal calls use the standard http client

@Peteratrapporr Can you please provide the exact error you are seeing from your application and how you are creating your *bigquery.Client? dial.go should be autodetecting that you're in the App Engine Standard environment and use urlfetch.

The error is generated within this call. The code works perfectly with the Flexible environment
client, err := bigquery.NewClient(ctx, "appname")
    ctx := context.Background()
log.Printf("UrlSessionA")
client, err := bigquery.NewClient(ctx, "appname")
log.Printf("UrlSessionB")
if err != nil {
	log.Printf("Logging error %v", err)
}
log.Printf("UrlSessionC")
t := client.Dataset("sessionlogging").Table("app").Uploader()
log.Printf("Client %s", t)

I get a panic attack in the code on the NewClient call.
Dump below
2017/05/08 22:30:48 UrlSession
2017/05/08 22:30:48 UrlSessionA
2017/05/08 22:30:48 http: panic serving <IP_ADDRESS>:54872: runtime error: invalid memory address or nil pointer dereference
goroutine 13 [running]:
net/http.(*conn).serve.func1(0xc820375a00)
/Users/petertippett/go/goroot/src/net/http/server.go:1389 +0xc1
panic(0x81e680, 0xc82000a070)
/Users/petertippett/go/goroot/src/runtime/panic.go:443 +0x4e9
google.golang.org/appengine/internal.fullyQualifiedAppID(0xf335d0, 0xc8201967e0, 0x0, 0x0)
/Users/petertippett/go/src/google.golang.org/appengine/internal/identity_classic.go:27 +0x4f
google.golang.org/appengine/internal.FullyQualifiedAppID(0xf335d0, 0xc8201967e0, 0x0, 0x0)
/Users/petertippett/go/src/google.golang.org/appengine/internal/api_common.go:74 +0xe2
google.golang.org/appengine/internal.AppID(0xf335d0, 0xc8201967e0, 0x0, 0x0)
/Users/petertippett/go/src/google.golang.org/appengine/internal/identity.go:13 +0x37
google.golang.org/appengine.AppID(0xf335d0, 0xc8201967e0, 0x0, 0x0)
/Users/petertippett/go/src/google.golang.org/appengine/identity.go:20 +0x37
golang.org/x/oauth2/google.FindDefaultCredentials(0xf335d0, 0xc8201967e0, 0xc8203cacc0, 0x1, 0x1, 0xc8203cacc0, 0x0, 0x0)
/Users/petertippett/go/src/golang.org/x/oauth2/google/default.go:86 +0x5a8
golang.org/x/oauth2/google.DefaultTokenSource(0xf335d0, 0xc8201967e0, 0xc8203cacc0, 0x1, 0x1, 0x0, 0x0, 0x0, 0x0)
/Users/petertippett/go/src/golang.org/x/oauth2/google/default.go:43 +0x6b
google.golang.org/api/transport.NewHTTPClient(0xf335d0, 0xc8201967e0, 0xc8204331b8, 0x3, 0x3, 0x0, 0x0, 0x0, 0x0, 0x0)
/Users/petertippett/go/src/google.golang.org/api/transport/dial.go:74 +0x669
cloud.google.com/go/bigquery.NewClient(0xf335d0, 0xc8201967e0, 0x96ac40, 0xa, 0x0, 0x0, 0x0, 0xc8203e50b0, 0x0, 0x0)
/Users/petertippett/go/src/cloud.google.com/go/bigquery/bigquery.go:54 +0x448
bigquery.UrlSession(0xc820388fc0)
bigquery/bigquery.go:22 +0x120
analytics.getconnectUsageV3(0xf38d88, 0xc8203f8750, 0xc820388fc0)
analytics/getconnect.go:239 +0xbe0
net/http.HandlerFunc.ServeHTTP(0xaf5cd0, 0xf38d88, 0xc8203f8750, 0xc820388fc0)
/Users/petertippett/go/goroot/src/net/http/server.go:1618 +0x3a
mux.(*Router).ServeHTTP(0xc82000cf50, 0xf38d88, 0xc8203f8750, 0xc820388fc0)
mux/mux.go:116 +0x57a
net/http.(*ServeMux).ServeHTTP(0xc82000ea80, 0xf38d88, 0xc8203f8750, 0xc820388fc0)
/Users/petertippett/go/goroot/src/net/http/server.go:1910 +0x17d
appengine_internal.handleFilteredHTTP(0xf38d88, 0xc8203f8750, 0xc820388fc0)
/Users/petertippett/go/goroot/src/appengine_internal/api_dev.go:105 +0x44c
net/http.HandlerFunc.ServeHTTP(0xaf5da0, 0xf38d88, 0xc8203f8750, 0xc820388fc0)
/Users/petertippett/go/goroot/src/net/http/server.go:1618 +0x3a
net/http.serverHandler.ServeHTTP(0xc820374700, 0xf38d88, 0xc8203f8750, 0xc820388fc0)
/Users/petertippett/go/goroot/src/net/http/server.go:2081 +0x19e
net/http.(*conn).serve(0xc820375a00)
/Users/petertippett/go/goroot/src/net/http/server.go:1472 +0xf2e
created by net/http.(*Server).Serve
/Users/petertippett/go/goroot/src/net/http/server.go:2137 +0x44e

Ah, you need to be passing the App Engine context to NewClient. This is actually just #523 from a different angle.  You should run go get -u google.golang.org/appengine to see the better error message.

This generates an error if you do this
cannot use context (type "appengine".Context)
as type context.Context in argument to "cloud.google.com/go/bigquery".NewClient:

@rakyll @broady do you know if there's a way to convert btwn appengine context and std context?

App Engine request context is a context.Context, see https://godoc.org/google.golang.org/appengine#NewContext.
@Peteratrapporr, are you sure that you are using the latest version of the appengine package? Please run the following if not:
go get -u google.golang.org/appengine/...

Yes, running the latest version of everything.
When you look at the big query code, it doesn't import "app engine urlfetch".  Same problem happens with any data writing as well as expecting the Background Context and using the standard http client model.
You get an error of "not an App Engine context" and when you pass the App Engine context you get the other error type which also flows on to the "put" command to write the data.

Hey @Peteratrapporr I'm not sure what you're running into here. Can you paste some code snippets?
For reference, this works for me:
package main

import (
	"fmt"
	"net/http"

	"cloud.google.com/go/bigquery"
	"google.golang.org/api/iterator"
	"google.golang.org/appengine"
)

func init() {
	http.HandleFunc("/", handle)
}

func handle(w http.ResponseWriter, r *http.Request) {
	ctx := appengine.NewContext(r)

	client, err := bigquery.NewClient(ctx, "<MY-PROJECT-ID>")
	if err != nil {
		panic(err)
	}

	q := client.Query(`
    SELECT year, SUM(number) as num
    FROM [bigquery-public-data:usa_names.usa_1910_2013]
    WHERE name = "William"
    GROUP BY year
    ORDER BY year
`)
    // ... iterate
    fmt.Fprint(w, values)
}

I did a full delete and rebuild yesterday and did the change on the code again to do appengine.NewContext and now fully working where before when I did that it errored.  Something with the normal updating of code hadn't updated something which has now been updated.
Can now close this

Late to the party, but see this, too:
https://github.com/GoogleCloudPlatform/golang-samples/tree/master/appengine/bigquery


[Bug]: ./entrypoint.sh: line 15:  3718 Segmentation fault      $PY rag/svr/task_executor.py $1   ./entrypoint.sh: line 28:  3730 Segmentation fault      $PY api/ragflow_server.py

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
5b4b252895b66627dec65570eb8f0f3c087543e0
Other environment information
Hardward:cpu  8700k, GPU RTX4090
OS types: WINDOW 10
PYTHON3: 3.12.0
Docker Engine v27.2.0

Actual behavior
when I input "docker logs -f ragflow-server" into the terminal opened by administrator. I can't successfully run.
errors and warning occured.
[WARNING] [2024-10-11 00:53:52,065] [synonym.init] [line:40]: Realtime synonym is disabled, since no redis connection.                                                                                [WARNING] [2024-10-11 00:53:52,073] [synonym.init] [line:40]: Realtime synonym is disabled, since no redis connection.                                                                                [WARNING] [2024-10-11 00:53:53,315] [synonym.init] [line:40]: Realtime synonym is disabled, since no redis connection.                                                                                [WARNING] [2024-10-11 00:53:53,322] [synonym.init] [line:40]: Realtime synonym is disabled, since no redis connection.                                                                                ./entrypoint.sh: line 15:  6406 Segmentation fault      $PY rag/svr/task_executor.py $1                                                                                ./entrypoint.sh: line 28:  6418 Segmentation fault      $PY api/ragflow_server.py
Expected behavior
output:

Running on all addresses (<IP_ADDRESS>)
Running on http://<IP_ADDRESS>:9380
Running on http://x.x.x.x:9380

Steps to reproduce
1. open a windows terminal
2. git clone this project
3. cd ragflow/docker
4. docker compose -f docker-compose.yml up -d
5. docker logs -f ragflow-server

Additional information
No response

Weird! What about pulling and using dev version of docker images?

this is my docker image ,
is there any suggestion for the version of docker image.

Thansk you KevinHush,
After Update docker image to dev version insteam of dev-slim.
I got this.
[WARNING] [2024-10-11 16:02:00,124] [synonym.__init__] [line:40]: Realtime synonym is disabled, since no redis connection.                                                                                [WARNING] [2024-10-11 16:02:00,132] [synonym.__init__] [line:40]: Realtime synonym is disabled, since no redis connection.                                                                                [WARNING] [2024-10-11 16:02:00,305] [synonym.__init__] [line:40]: Realtime synonym is disabled, since no redis connection.                                                                                [WARNING] [2024-10-11 16:02:00,313] [synonym.__init__] [line:40]: Realtime synonym is disabled, since no redis connection.                                                                                [WARNING] Load term.freq FAIL!                                                                                [WARNING] Load term.freq FAIL!                                                                                ____   ___    ______ ______ __                                                                                / __ \ /   |  / ____// ____// /____  _      __                                                                         / /_/ // /| | / / __ / /_   / // __ \| | /| / /                                                                        / _, _// ___ |/ /_/ // __/  / // /_/ /| |/ |/ /                                                                        /_/ |_|/_/  |_|\____//_/    /_/ \____/ |__/|__/                                                                                [INFO] [2024-10-11 16:02:12,694] [_internal._log] [line:96]: WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.                                                              * Running on all addresses (<IP_ADDRESS>)                                                                                * Running on http://<IP_ADDRESS>:9380                                                                                * Running on http://xxx.xx.x.x:9380                                                                                [INFO] [2024-10-11 16:02:12,696] [_internal._log] [line:96]: Press CTRL+C to quit

It seems normal.


NPM has version 2.153.0 that is broken

CDK Team:
In the process of publishing cdk-assets as a stand-alone repository, it appears that the aws-cdk repository continued to publish versions v2.152-153.0. These versions do not have any fixes or features added by commits to this repository.
The most significant fix was to enable the version mismatch verification to only check the major version rather than the minor or patch version, resulting in errors of the form Error: Canot read asset manifest 'dist/shopping-api-dev.assets.json': Cloud assembly schema version mismatch: Maximum schema version supported is 36.0.0, but found 36.0.14
These errors can be easily identified as the new error message says Maximum schema version supported is 36.x.x rather than 36.0.0.
This is causing problems with our dependency upgrades since we are pulling in the highest version from NPM, 2.153.0, while a patch version such as 2.151.31 is the latest.
To fix this, we likely need to bump the minor version of this library twice to at least 2.153.1. Publishing 2.152/3.0 to NPM will likely fail due to the versions already existing. It may be best to go to 2.154.0 since 2.152/3.0 are both behind feature-wise.
We may also want to look into unlisting v2.152/3.0.

Original Report:
NPM seems to have version 2.153.0 of the cdk-assets package: https://www.npmjs.com/package/cdk-assets/v/2.153.0 while the latest version posted in this repo's releases is 2.151.17
The 2.153.0 version seems to be broken with followin message:
Running command yarn cdk-assets publish --path dist/shopping-api-dev.assets.json --verbose
Error: Canot read asset manifest 'dist/shopping-api-dev.assets.json': Cloud assembly schema version mismatch: Maximum schema version supported is 36.0.0, but found 36.0.14

Also, the version 2.153.0 is not verified accordsing to NPM.
Could you check where this version came from?

Found a workaround.
I am using yarn added to package.json
{
  "resolutions": {
    "@aws-cdk/cloud-assembly-schema": "^2.153.0"
  }
}

For npm add to package.json
{
  "overrides": {
    "@aws-cdk/cloud-assembly-schema": "^2.153.0"
  }
}

@kimmoahokas I added context to the description of the ticket.
Also, I would recommend you pin to a patch version of 2.151.x as your workaround, if that works for you.

@kimmoahokas I added context to the description of the ticket.
Also, I would recommend you pin to a patch version of 2.151.x as your workaround, if that works for you.

Thank you!
For us pinning to previous version works just fine. Just wanted to know if there is a possibility of some adversary publishing malicious version of the package or something like that. Glad to hear that was not the case and apparently the problem causing the faulty package publishing has been fixed.


move interpreter detection to package.yml

Goes with your app.exec.ts rewrite, @mxcl.
Requires https://github.com/teaxyz/pantry.core/pull/33

Can't pass checks (fails tea -x setup.py until pantry is merged).

wonderful.

lets add a test


Change var to const in some exercises

As explained in #324 , I changed some variable declaration to constants. I also tried to update the comments when it made sense.
Some variable could be changed to constant like num1 here in 039_pointers.zig but it would require to also change num1_pointer to be *const u8.
https://github.com/ratfactor/ziglings/blob/08e8a0f1e48954c4b4657c0078bb5b3ef0c8d13d/exercises/039_pointers.zig#L25-L36
Since this exercise is trying to explain how pointers works I assumed it would not be a good idea to make the change. The same applies to exercise 066_comptime.zig and after, where we already make use of const and comptime.
I also understand that changing variables to constants may give away the answer to some exercise. Feel free to not merge some changes to some exercises if you think it's not worth it.
Everything was built and run with zig 0.11.0-dev.3747
NB: I also updated outdated comments referencing the change in builtin casts as I forgot to check those in my previous PR. (see: #327)

Thanks!


Research storage migrations

We need a proper way to introduce type changes without breaking the runtime storage.
some information: https://substrate.dev/docs/en/knowledgebase/runtime/upgrades#storage-migrations

This PR includes the node interfaces and storage migration. Need to test if this works!
https://github.com/threefoldtech/tfchain_pallets/pull/36


Makefile command for env-report

Summary
https://github.com/linkedin/Liger-Kernel/issues/112

Will be helpful to provide a CLI (called something like liger_env_report?) that queries:
triton ver
torch ver
HF ver
OS
python ver
...
so user can paste the output when creating bug report issue

Testing
Implemented as a makefile command.
> make env-report
Environment Report:
-------------------
Operating System: Linux basil 6.5.0-44-generic #44~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jun 18 14:36:16 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Python version: Python 3.10.13
PyTorch version: 2.3.0
CUDA version: 12.1
Triton version: 2.3.0
Transformers version: 4.42.3

ready for review

Would it be more helpful to make it either a CLI entry point or a module where folks can do python -m liger_kernel.xxx, for users who simply install stable version with pip install liger-kernel  instead of cloning the source? 🤔

Ah that makes a ton of sense. Will amend it to that.

Updated

Should we update the .github/ISSUE_TEMPLATE/bug_report.yaml "Versions" section to point users to run this script when filing bug report?

Thanks! Looks like I need a maintainer to merge


ADD: Custom add domain

There were 6 errors:

1) IndicoIo\Test\CollectionTest::testListCollections
Undefined index: domain

/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/IndicoIo/IndicoIo.php:300
/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/tests/CollectionTest.php:38
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:186
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:138

2) IndicoIo\Test\CollectionTest::testTrainPredict
Undefined index: domain

/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/IndicoIo/IndicoIo.php:300
/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/tests/CollectionTest.php:53
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:186
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:138

3) IndicoIo\Test\CollectionTest::testAddSingle
Undefined index: domain

/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/IndicoIo/IndicoIo.php:300
/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/tests/CollectionTest.php:66
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:186
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:138

4) IndicoIo\Test\CollectionTest::testRemoveExample
Undefined index: domain

/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/IndicoIo/IndicoIo.php:300
/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/tests/CollectionTest.php:78
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:186
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:138

5) IndicoIo\Test\CollectionTest::testClearCollection
Undefined index: domain

/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/IndicoIo/IndicoIo.php:300
/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/tests/CollectionTest.php:97
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:186
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:138

6) IndicoIo\Test\CollectionTest::testTrainPredictImage
Undefined index: domain

/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/IndicoIo/IndicoIo.php:300
/home/rof/src/github.com/IndicoDataSolutions/IndicoIo-PHP/tests/CollectionTest.php:113
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:186
/home/rof/.composer/vendor/phpunit/phpunit/src/TextUI/Command.php:138


brave: 1.58.137 -> 1.59.117

https://community.brave.com/t/release-channel-1-59-117/509958
Description of changes
version bump

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 260530 run on x86_64-linux 1

1 package built:

brave

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

brave:

warning: EvalError
Cannot evaluate attribute ‘brave’ in ‘/nix/store/98mgwsv98qh3zgya6ncnm8yv9w4pzizg-nixpkgs’.


Unable to read Iceberg table with hadoop conf passed in as options

We use spark options to send hadoop configurations (specifically mentioned below), to read/write to Iceberg table. These options have helped in reading/writing when we have multiple SparkSession (which shares hadoop configuration on Global spark Context), each belonging to a tenant, and each tenant can potentially have different creds (have different ACLs as well).
There is multi tenant configuration also available like dfs.adls.oauth2.client.id.{accountName}, which can be set on sparkContext, but we don't want to expose the creds from one session to other. Make sense? I think it will help in scenarios, when even multi tenant hadoop configuration aren't supported by underlying store.
NOTE: This is already supported here.
Working on a fix.
hadoop.dfs.adls.oauth2.client.id={clientId}

PR https://github.com/apache/incubator-iceberg/pull/1066

Fixed by the mentioned PR!


A Wonderful App,but can you introduce the principle of software？

Why can it search so fast？
how does it work?
Thank you!

@ymyguang thank you, its explained in the section: https://github.com/webbersmak/Orvina#under-the-hood


feat: add source repo clone dir input

Changes
Summary of changes included in this PR:

[x] Adds a new (optional) input to allow users to override the directory the source repo is cloned into
[x] Updates to tfx-cli to v0.7.9 which includes the fix for invalid task name validation
[x] Minor doc updates

Related Issues

Resolves #51

I also set up a few additional test pipelines in our Task Validation org with this new version, including the multiple task instances with the same repo name
https://dev.azure.com/swellaby-azp-task-validation/OpenSource/_build?definitionId=7&_a=summary
https://dev.azure.com/swellaby-azp-task-validation/OpenSource/_build?definitionId=8&_a=summary
CC - @traviskosarek @calebcartwright

Circle job is failing because Sonar is missing the branch property required for PR builds 🙄 I really need to get #47 done


userDN hardcoded to CN

Lovely piece of software you got here, trying it out right now.
One thing I noticed is you hardcoded the userDN to CN in some places like here, while this might work fine with openldap it does not with FreeIPA.
Changeing cn to uid on lines 14, 24 and 52 fixed it for me (only tested with FreeIPA).

Hello @jkaberg ,
Thank you! That is true, I hardcoded it so that it fitted to my needs and I did not try it with FreeIPA. Do not hesitate to contribute with a PR if your code works and tests are green. I would be glad to review and add your name in the contributors list.

@clems4ever, PR submitted https://github.com/clems4ever/authelia/pull/15

@jkaberg, pull request #18 is a long-term solution to what you are trying to do.


How to get holography

Hello, what is the relationship between the phase in the code and the hologram, how can I use a picture to get a hologram, and after loading this hologram on the SLM, the image can be reconstructed

Hi there. In this project we focus on holographic imaging, that is how we can recover the amplitude and phase of the unknown object based on the diffraction patterns. We don't necessarily need an SLM in our configuration. The phase in the code corresponds to the phase of the unknown object we try to recover. For more details, you may refer to our paper: https://doi.org/10.1364/OE.434449. If you are interested in holographic display (or computer generated holography, CGH), this is beyond the scope of this project. Nevertheless, I think the hologram synthesis and reconstruction problems have something in common.

OK,Thanks


[5.3] Keep files in the  $data array after hydration

Let's say we have this validator instance:
    $file = new File(__FILE__, false);
    $v = new Validator($trans, ['files' => [$file]], ['files' => 'Required']);

When hydrateFiles() is called $validator->data will be empty, and $validator->files will look like:
['files.1' => /** File Instance **/];

So when the required rule runs, it expects a files key to be present, but that key was removed during hydration so the rule will fail although there are files present in the Validator instance.
This PR prevents removing the files from $validator->data which will make such rule pass.
In 5.4 we removed the hydration step entirely.

Honestly since this itself is a small breaking change because the content of $data will be different, maybe the answer is to just backport the 5.4 change. validator->getFiles() is not documented and I'm not sure what it would ever be used for. It's probably used to make our own testing easier more than anything.

Will open a new PR with a backport for the changes we made in the 5.4 branch.


Add accessibility testing

Please add some testing for people with vision impairment, along with making sure the best practices you propose don't mess with things like screen readers.
I bring this up because quite a few people have complained about the very low contrast between your default text and background, along with the default font's weight, and I agree with them.
I'm also not sure why the default font color is slightly blue shifted, but that's personal preference. I'd like to see it grayscale.

The default font color has been adjusted to #767676 by another reviewer's suggestion. Funny, it was wonky because I myself am fairly colorblind.
I'm looking into integrating some automated accessibility testing. Do you have any suggestions for a good tool for this?


New currency is not added

FIL  xch    not   added

How do we add a new currency when there is a new coin listing ?
Do we have to modify Currency.java and recompile each time?

just use Currency.getInstance("CURRENCY_CODE_HERE")


Update Laravel database advisory

The previous fix could be bypassed, so new versions were released.
Source:

https://github.com/laravel/framework/pull/35865#discussion_r561578503
https://github.com/laravel/framework/pull/35972

I think this should rather be added as separate advisories linking to https://blog.laravel.com/security-laravel-62012-7303-released instead of updating the existing one while keeping the old link.

I think this should rather be added as separate advisories linking to https://blog.laravel.com/security-laravel-62012-7303-released instead of updating the existing one while keeping the old link.

@stof I don't know why @taylorotwell didn't update the advisory (https://github.com/advisories/GHSA-3p32-j457-pg5x).
But as you can see in PR https://github.com/laravel/framework/pull/35972, another fix was required to address the security issue. It was tagged with the versions I specified in the this PR.

@stof I don't know why @taylorotwell didn't update the advisory (https://github.com/advisories/GHSA-3p32-j457-pg5x).
But as you can see in PR https://github.com/laravel/framework/pull/35972, another fix was required to address the security issue. It was tagged with the versions I specified in the this PR.

The files were already moved to the correct CVE locations in https://github.com/FriendsOfPHP/security-advisories/pull/529 so this conflicts now - was there any feedback/response on creating an additional advisory / at least updating the announcement blog post?

The files were already moved to the correct CVE locations in https://github.com/FriendsOfPHP/security-advisories/pull/529 so this conflicts now - was there any feedback/response on creating an additional advisory / at least updating the announcement blog post?

@naderman Not from an official side: https://github.com/laravel/framework/pull/35972#issuecomment-767846044

@naderman Not from an official side: https://github.com/laravel/framework/pull/35972#issuecomment-767846044

@jaylinski Maybe instead of modifying this issue, you can make a separate one for the newer versions which simplify references https://blog.laravel.com/security-laravel-62012-7303-released as a link as that's public confirmation those versions were still vulnerable? That way the existing CVE issue matches what was reported on the issue, but the newer versions are marked insecure via the yet to be created file? Thanks!


docker registry logs are lacking and can be verbose and not useful

Problem
The docker registry logs are lacking and can be verbose and not useful.
Solution
Review the logging calls in https://github.com/docker/docker/tree/master/registry and use our standard log package github.com/Sirupsen/logrus to make meaningful log messages.
It could be helpful to remove all existing log calls and then go through and log meaning requests, warnings, errors, and debug messages for the API.

Could you provide further examples of the issues with registry logging? We are already using github.com/Sirupsen/logrus as of docker/distribution#151. Also, they are not primarily meant to be human readable, as is the theme of the logrus package. Perhaps, adding tools for reading logs would be helpful.

@jfrazelle Just read the link more carefully: agreed, this is a problem with the registry package. Should we hold off on this until we integrate the v2 client from docker/distribution?

op sorry we can close these were party issues so i wasnt the original author ;)


fix: panic from calling 'record' on page cache misses

This is currently a part of the diff of #308 and #306. Separating out for clarity.
Calling record with a metric that's not a timer causes a runtime panic when pages are not cached.

#310  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rphmeier and the rest of your teammates on  Graphite


Unified logging everywhere

Fix j.logger.log
Make sure it's being consistently used throughout the codebase

Can we have nice colors too ?

For colors, you can use http://docs.fabfile.org/en/1.10/api/core/colors.html which is already part of Jumpscale :)

Some documentation on how the new logging system works : https://gig.gitbooks.io/jumpscale8/content/Core/logging.html

see #124


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter rmb-bhkw for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ioBroker.rmb-bhkw
   -

ERRORS:

[x] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 3.0.4 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[x] :heavy_exclamation_mark: [E036] @iobroker/testing 4.1.0 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[x] :heavy_exclamation_mark: [E039] "keywords" within package.json must contain some keywords besides "ioBroker, template, Smart Home, home automation" related to adapter
[x] :heavy_exclamation_mark: [E162] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[x] :heavy_exclamation_mark: [E204] Version "0.0.1" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.

WARNINGS:

[x] :eyes: [W028] Minimum node.js version 18 recommended. Please adapt "{'engines' : { 'node' >= '16' } }" at package.json.
[x] :eyes: [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[x] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[x] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[x] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence

All issues reported earlier seem to be fixed now.
THANKS for your support.
This issue can be closed.
your
ioBroker Check and Service Bot


Revamped Hub Search

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/197
Originally created by @alexmarple on 2022-02-11 17:27:15

Meltano Hub needs to be revamped with the following feature updates:

A search bar available when you first hit the Meltano Hub site.
The search bar looks for exact word searches but also looks for keywords and descriptions (e.g. a search for Excel would turn up tap-spreadsheets-anywhere
A details grid would be returned when searching that would allow for better readability of results as well as allow for filtering (preferably with a toggle interface).

View 3 previous comments from the original issue on GitLab


Fix token lists #233

LGTM

Test and merge please

Tests are fine - Travis just lost an Enviroment var so it's crashing after. Merged.

Thanks. Any chance for seeing a new release with this fix? Datejs is the last thing in our project which is not bowerified only because of this issue.

I just pushed the last few updates to a production build. So it's in github. It's not npm released tho.
Do you need an npm release to do that?

A release as in https://github.com/abritinthebay/datejs/releases. Bower looks for tarballs on Github associated with git tags.

Ahhh ok, a tagged release. There's a couple of fixes I want to get in before I do another RC release. Will attempt to get those in in the next couple of weeks.

Could you please do a tagged release with this fix?


Help

Im trying to achieve a certain style with the radial gradient.
Is there anyway to do hard color stops instead of blending so I can get an effect like this
Thanks

May be this is useful - http://stackoverflow.com/questions/31853859/radial-gradient-background-in-swift


Handle mounting of default_gh_config.yaml in model repo build process

Goals + Background
https://replicahq.atlassian.net/browse/RAD-5578
The main goal here is to support conceptually moving the main graphhopper config file(s) to the model repo - the TN CDP, specifically. The "main" configs in this context are the ones used to build prod routers, not the more static configs related to GTFS validator/sandbox/etc. In these initial changes, I'm aiming to keep existing behavior intact wrt how custom profiles work in the router/get ingested+combined, and just change where the configs are stored + how they're "piped through" to graphhopper.
The ability to support this is heavily tied to parameters of the setup we use in the model repo to build routers - especially the GraphHopperGraphBuilder data manager, and the graphhopper_data_builder.template.pod.yaml file where the exact java calls to the import / gtfs-links graphhopper commands get exercised.
Everything in this PR is tied directly to the changes in the corresponding model repo PR; I'd suggest looking at both sets of changes in order to understand the decisions I made here.
Changes in this PR

Delete the existing "main" graphhopper config, default_gh_config.yaml, and move the "prod" custom car profiles currently in use to the test data folder. I do this mainly to enforce that the prod configs should now live in the model repo, and to avoid annoying issues with filename collisions in the model repo-side router building process (see that PR for details)
In Dockerfile.server, update the java call that actually spins up a router upon container startup to use a config located at transit_data/configs/default_gh_config.yaml, instead of the old default_gh_config.yaml. This is an important detail,  dictated by the fact that in the model repo, constraints exist such that it's easiest to "mount" new config files (specified via data configs, for example) into routers during the building process by including them in the /transit_data subfolder of the graphhopper codebase (where we currently store the build graph files that are outputs of the router building process). See the corresponding model repo PR for details
Due to the above point, it makes sense to simply relocate all other existing configs to the new location, for consistency (also makes config-finding a bit easier). So, I moved the "non-base" configs we're keeping around into transit_data/configs too
Due to subtleties in how query_functional_test.sh, I updated the folder that gtfs link mappings get stored in very subtly, to allow those files to be more granularly mounted during the docker steps carried out in that script. I think the script is clever, but perhaps too clever - it can make changes like these kind of unsightly to deal with

Testing
In conjunction with https://github.com/replicahq/model/pull/6277, successfully built the graphhopper_graph_builder DM for mini_nor_cal 2021_Q4, and spun it up successfully locally with the run-graphhopper script

I've gotten to look through this and the accompanying PR at a medium-high level. I think that I follow the technical approach here, and it makes for a reasonable way for the router config to be injected by the model repo. At a strategic level, I did have a (non-blocking) suggestion.
We've talked as a team in the past about working more incrementally. When I see something like "these two changes need to be landed at the same time", that always makes me raise my eyebrows. Is there a way that this could be constructed so that we did not need to land changes in two repos in sync? I could imagine a world where the model repo starts providing its version of the config, before the graphhopper repo requires it. Or, a world where the graphhopper repo accepts a caller-provided config, but does not require it.
I know that you're familiar with all the reasons that we typically give for wanting to make incremental changes, so I won't rehash all that. But I wanted to flag this as a case where it seems like we have to make a couple of decent-sized changes in sync, but with some attention, could construct our changes so that they can be applied independently.

Synced offline with @danielhfrank about the above note. Our conclusion was that in a perfect world, the two PRs here might have been spit up in such a way that we could merge only a subset of them and still be in a state where everything was functional (ie each change is totally independent, until perhaps one final "flip switch" change that "turns on" the new feature).
There are a few aspects of this feature in particular that make this paradigm slightly harder to follow:

The "piping" that passes these various file paths through the graphhopper build pipeline in the model repo, and through to the docker-defined build setup used in the graphhopper repo (and its CI), is fairly complex. This means that initial development of features like this often involves working the problem in both ends, until you have 2 PRs that work together in unison
The separation that already exists between the graphhopper + model repos, and between the TN CDP and the downstream consumers of the router, means that even these larger changes are "gated" in some sense. Merging the java PR doesn't affect anything in the model repo; merging the model repo PR doesn't change anything instantly for consumers of the TN CDP (as they wouldn't be forced to bump to the new version)

There are still drawbacks to not splitting these further, the main one being that if I'm pulled away into something else and only got one of the two PRs in, it could leave things in a messy half-state (this is kinda the point of smaller incremental PRs). Given the state these changes are in now (ready to be merged one-after-another, relatively contained from the consumers of the router), I'm going to move forward with things as-is, but will keep this pattern in mind more when planning implementations of future projects


Customizable templates

Is your feature request related to a problem? Please describe.
There isn't any way to customize the templates in https://github.com/googleapis/release-please/blob/main/templates/
Describe the solution you'd like
Some way to customize them (via config or another file path)
Describe alternatives you've considered
None

hello I would love this feature too, any news ?
Should I investigate myself and propose a PR ?


[Bug] parsing Error

i tryed your helper yesterday the first time and it worked great. today i could not log into character with the helper, always got a parsing error, but only with this character, not all
OS: Win11
Version: 0.2.2
helper.log

yeah, they released an update (22.000) to their servers, which broke a few things. I am working on fixing it

Should be fixed in the newest release. The S&F update is pretty big, so there may be more things wrong, that I have not found yet. If you see any other errors, feel free to open a new issue 😄

that was quick, big thanks. its working again. eu13 here i come


Typo

Summary
Just a minor typo fix in mkdeps.
Impact
N/A
Testing
N/A

Hi @fjpanag this is not just a Typo, this patch is removing the "stm32_pwr_enableoverdrive()". If stm32_pwr_enableoverdrive() is not working, then we need to fix it, instead of removing it. Maybe someone at ST could help us.

@acassis
??? I don't understand... The stm32_pwr_enableoverdrive is already removed in #1841... And nevertheless this is not what Github showed me when I created the PR...
Can we fix that? Or should I make a new PR?

Hmmm... Indeed it shows 3 commits, but only one file changed...

@acassis
??? I don't understand... The stm32_pwr_enableoverdrive is already removed in #1841... And nevertheless this is not what Github showed me when I created the PR...
Can we fix that? Or should I make a new PR?

I think forgot to sync your branck with mainline before submitting this PR.
Normally I do this way: https://acassis.wordpress.com/2020/03/31/syncing-my-github-fork/
After submitting your PR and it was incorporated on upstream, you need to pull our upstream branch and sync your master with it.  Nevertheless, I think it is fixed now.
(Thank you for your advice on how to fix this!)

Thank you Fotis, it is fine now!


Move pre-command hook to environment hook

We need this to work with https://github.com/buildkite-plugins/ecr-buildkite-plugin which runs as an environment (as pre-command this will always run after and thus logging into ECR will not used the assumed credentials).

Ooops! Wrong place. Sorry.


Fdg 8028 displaying wrong report

https://federal-spending-transparency.atlassian.net/browse/FDG-8028

I can change it to truthy...


Promises in onItemInserting not working

Problem statement:
I would like to obtain server data during the onItemInserting: method using a Promise. However the new item is inserted whilst the Promise is incomplete; followed by the code (in this test case) within setTimeout

Note:

The methodology to obtain server data works correctly outside the jsTable framework and employs ES6 async/await.

I spent several hours looking into jsgrid.js to better understand - to no avail

Demo code herewith usingsetTimeout() to illustrates the problem
            onItemInserting: (args)=> {
                return new Promise((resolve, reject) => {
                    console.log('Pre grid insert - start');
                    let payload = new Object();
                    payload.barcode = args.item.barcode;
                    args.cancel = false;
                    // Code runs OK to this point
                    setTimeout( () => {
                        args.cancel = true;
                        resolve();
                    }, 1000);
                    //Grid insert happens before the resolve in setTimeout
                });
            },

Your assistance to understand if Promises are allowed within the jsGrid framework
Google Chrome is up to date - Version 81.0.4044.138 (Official Build) (64-bit)
/*

jsGrid v1.5.3 (http://js-grid.com)
(c) 2016 Artem Tabalin
Licensed under MIT (https://github.com/tabalinas/jsgrid/blob/master/LICENSE)
*/

AFAIK promises aren't supported on those callbacks, if you want to achieve that look at my answer for issue https://github.com/tabalinas/jsgrid/issues/1320


Add fallback for opendistro_security_config.ssl_dual_mode_enabled

opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)
Refactoring

Github Issue # or road-map entry, if available:

Description of changes:
Add fallback for the Dynamic setting opendistro_security_config.ssl_dual_mode_enabled

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)
UT

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Just found
 logger.warn("opendistro_security_config.ssl_dual_mode_enabled is enabled but plugins.security.ssl_only mode is disabled. "
                + "SSL Dual mode is supported only when security plugin is in ssl_only mode");

in org/opensearch/security/ssl/transport/SSLConfig.java
gonna change this.

Codecov Report

Merging #1190 (e6bbca9) into main (88e4e78) will decrease coverage by 0.02%.
The diff coverage is 85.71%.

:exclamation: Current head e6bbca9 differs from pull request most recent head c7150b5. Consider uploading reports for the commit c7150b5 to get more accurate results

@@             Coverage Diff              @@
##               main    #1190      +/-   ##
============================================
- Coverage     64.52%   64.49%   -0.03%
  Complexity     3169     3169
============================================
  Files           244      245       +1
  Lines         17125    17128       +3
  Branches       3035     3035
============================================
- Hits          11050    11047       -3
- Misses         4535     4540       +5
- Partials       1540     1541       +1

Impacted Files
Coverage Δ

...g/opensearch/security/support/ConfigConstants.java
94.44% <ø> (ø)

.../opensearch/security/support/SecuritySettings.java
66.66% <66.66%> (ø)

.../opensearch/security/OpenSearchSecurityPlugin.java
81.22% <100.00%> (+0.03%)
:arrow_up:

...g/opensearch/security/ssl/transport/SSLConfig.java
90.00% <100.00%> (-0.48%)
:arrow_down:

...security/configuration/DlsFlsFilterLeafReader.java
59.76% <0.00%> (-0.71%)
:arrow_down:

...a/org/opensearch/security/tools/SecurityAdmin.java
47.26% <0.00%> (-0.27%)
:arrow_down:

Continue to review full report at Codecov.

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


Terminal tab giving error: create terminal viewer: the server could not find the requested resource

What steps did you take and what happened:
Go to any pod and click on the Terminal tab
The page displays error "create terminal viewer: the server could not find the requested resource"
This has been working until recently.  Probably something that's changed on our kubernetes cluster, but our kubernetes platform engineer is lost to why this would start to happen.  BTW I can start a terminal session using kubectl from the command line.
Any advise on what could be causing this error, or what Octant needs to be enabled in kubernetes would be most appreciated.
What did you expect to happen:
A terminal session to start
Environment:

Octant version (use octant version): 0.20.0

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:18:45Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.6", GitCommit:"8a62859e515889f07e3e3be6a1080413f17cf2c3", GitTreeState:"clean", BuildDate:"2021-04-15T03:19:55Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}

OS (macOS 10.15, Windows 10, Ubuntu 19.10 etc): Window 10

Hi, here's a screen grab of the error if it helps at all:

There is a known issue with Terminals and AKS virtual nodes. Just want to double check what vendor/flavor of Kubernetes you're running.

I don't currently have access to the exact information, but I do know that Kubernetes was hosted on a recent version of Ubuntu on the company's own IT infrastructure by an member of staff.

Is there a specific set of perms you need in Kubernetes to allow Octant to start a terminal session?  As I say I can start a terminal session via kubectl.  Perhaps there's a set of additional options Octant specifies when starting a session that I don't set from the command line that are having a negative effect?

There is a known issue with Terminals and AKS virtual nodes. Just want to double check what vendor/flavor of Kubernetes you're running?

While not the original requestor, I'm having this issue also.  I am not running AKS, but instead this is in a microk8s environment on Ubuntu 20.04 - v1.21.5-3+83e2bb7ee39726


test for reminder bot

I will write the about section of this page.
/remind me to add about page in 2 days

I will write the about section of this page.
/remind me to add about page in 2 days


Cannot find the underlying climate entity - Log Spam

Hey. Im using your Integration to control my climate device.
But whenever i restart my home Assistant the whole System gets unresponsive for a while because its spamming the anove error into my log. 75.105 Times the same error
Cannot find the underlying climate entity. The error comes because it takes a while for HA to connect to the mqtt Broker and list all devices.

Maybe u can add a Pause of 30secs or something and try then again to Start the integration
Thanks in advance

I'm seeing this error (it's not warning but error) about 60 times on each startup, as a thread network needs a few minutes to make all devices available to HA.

I will change this to a Warning level as it is only a warning if it is temporary. But this can be also a misconfiguration if this persists.

I reinstalled my HA today because everything was crashing and HA rebooted all the time on its own.
Now the 75.000 log entries are gone :D
Now only a few. 2-10.
Sorry for the report. I will Mark it as resolved. Thanks for the Quick Support


Add camera proxy

Description:
As per discussion in #11577, this is an implementation of a camera proxy.  Its primary purpose is to reduce the bandwidth utilization of streaming images to the frontend.
Note that this does not implement dynamic sizing as requested by the frontend as that part of #11577 was more controversial.  I may try to implement that capability in a separate patch in the future.
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
camera:
  - platform: foscam
    ip: xx.xx.xx.xx
  - platform: proxy
    entity_id: camera.proxy
    max_stream_width: 360
    max_image_width: 480
    stream_quality: 60
    image_refresh_rate: 10

Checklist:

[x] The code change is tested and works locally.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

As far as further default values in voluptous, I don't see any places where it will help.  The only defualt parameter that would make any sense would be image quality, but I want to distinguish between a user specifying a value vs not, and using a default value would mean I just need a different set of logic to get the same result.


Client.Timeout a concern?

Hi,
I'm working with many (>10) large (> 1 Gb) mounted files on an AWS EC2.  Variably I get this message in my logs with certain programs accessing these files:
2021/06/13 04:33:39.461498 fuse.ERROR *fuseops.ReadFileOp error: net/http: request canceled (Client.Timeout exceeded while reading body)
Sometimes it just appears once or twice, but I have one program that is frequently seeing 100s of lines like this in a 2.5 hour run (64 threads).  Is this something that I should be concerned about (i.e., given the variable nature of this error, if I run the same job multiple times should I expect to get different results)?
Thanks!

goofys verion is: 0.24.0-45b8d78375af1b24604439d2e60c567654bcdf88

if you see this, then some read requests have failed. Depends on your application, it may or may not have retried. It doesn't seem like the workload should have triggered this though, do you have more debug logs? What kind of instance are you running this on?

Hello,
I have this same error.
I have goofys mounted to an S3 and on my server NGINX uses the goofys mount to serve up .jpg & .mp4 files.  The logs of tons of these errors so not sure if this is just the visitor closing the connection on purpose or the visitor is viewing a mp4 and suddenly it closes.  If I can help troubleshoot this please let me know what to do. Thanks much

@kahing Following up for @phil-grayson here.
We most frequently see this error when running a program called VEP, which requires mounting ~400Gb of files (using goofys) and is used to annotate variants (operating on VCF files). We are using a very large, compute optimized server in the AWS Cloud (c5n.18xlarge). This machine has 72 threads, 64 of which we are dedicating to our job while leaving some remaining for goofys/system usage with ~80Gb EBS storage. We notice anywhere from 80 to 400 of these error messages during these jobs. We've compared results from several runs with and without goofys (so we download the needed files directly instead of mounting). We don't see any meaningful difference in the results with or without the mounting (even in the presence of these errors).
I've attached a file with the full output from one of our runs. Since we are getting no errors from VEP, do you suspect that this error is totally non-affecting?


Added new term Toll receptor ligand protein activation cascade. Fixes #23378.

Hi Raymond,

You have 'by' twice
"A protein activation cascade that contributes to the generation of an active peptide ligand for the Toll receptor and consists of the cascade of enzymatic reactions initiated by by extracellular recognition factors, leading to the cleavage of the inactive form of spatzle family of ligands."

I would change 'contributes to the generation of an active peptide ligand for the Toll receptor and ' to 'generates the Toll receptor ligand.

Add a comment: This term specifically mentions the Toll receptor and its ligand spatzle because this is the only known example of such an activation cascade for a ligand.

Thanks, Pascale

Thanks. Redo.


Providing cell segmentation as a cell label column

If I'm using a cell label column in the molecules table to give Baysor information about a prior segmentation, how would I indicate molecules that don't belong to any cell? Is this supported? I have a prior nuclei segmentation, but because it only includes nuclei there are many molecules outside the nuclei that aren't assigned to cells.

Yes, this is supported and works exactly in the same way as a segmentation mask: you set the labels of non-assigned molecules to 0. It will not force them to be background (indeed, there is no such option currently), but will set them as unlabeled.


[flutter_releases] Flutter stable 3.13.4 Framework Cherrypicks

Flutter stable 3.13.4 Framework
Scheduled Cherrypicks

CC: @zanderso


Abnormal liquidation

I've deposit twice with BNBs:
5BNB
https://bscscan.com/tx/0xf0ca817fc07e348f99eb00e935c3630cfd2073b5c1eb3800092d6a8621208fce
3.8BNB
https://bscscan.com/tx/0xb63703bf2036c9d0a83a5b8db6bfef030981ff8999038899166f2164d78073e5
and I borrowed 3 times with USDCs:
500 USDC
https://bscscan.com/tx/0x862683ccf133508d77bbef5be7904c8388a935a40f6f222ea758911a31981d79
600 USDC
https://bscscan.com/tx/0xd31d8e87ef6c9188da84d4239a9f207c12ecc968e647ca22596e25835800dacb
310 USDC
https://bscscan.com/tx/0x5ec0ad6ade8fb6f1c9f777da4918da7663cffb27021765ee030660fcfcbaf45b

After the third event the BNB balance becomes: 5.89 and USDC balance becomes 705, which is supposed to be 8.8 and 1410 respectively.

It seems that there is a liquidation event being triggered selling 3 of my BNB for 705 USDC at a price of 235$, which is way less than the market price (265$ at the moment).
The white paper mentioned that:  However, if a user’s collateral value drops below 75%, or whichever collateral ratio percentage that a certain asset has, it could cause a Liquidation event, which will be discussed later, later the white paper mentioned A user’s collateral may be liquidated if it falls below the thresholds required for the borrow or stablecoin side of a specific coin market.   In my case, the ratio is 50%, but at the time when I brrow USDC the value of my BNB is 8.8*265=2332 which is much more than 1410, why this can trigger liquidation?
why 50% of borrowed fund are liquidated? Is it mentioned in the white paper?
If there is a liquidation happend, why there is no according event log in BSC?

Can you please triage the code, or provide the piece of the code to me?  It does not only affect me but also all of the user in Venus protocol, if Venus can explain to the users that this behavior is WAI, could you please just update the white paper to explain clearly what triggers a liquidation (1 or 2) event like below:

collateral value * ratio < borrowed value
collateral value < borrowed value

I think the standard definition should go with 2, that's how I understand.

all collateral factor is 60% for now therefore your supplied collateral was in range of liquidation.

Thanks, I think you did not answer all of my question though, could you please update the information in your white paper, which should serve as the user agreement, which is a very serious deal considering this platform is a financial hub.

In the white paper doesnt mention any Fix Collateral factor, it says "Typically collateral ratios are set any where from 40% to 75%" and for each asset different factor.later on since 01/02/21 they publish this  :

Clarification: As of today 01/02/21, all have a collateral factor of 60%, but it can be changed in future proposals.

3=> How much do they liquidate us?
They liquidate us enough to pay our loan + 10% on that value that remains of profit for the liquidator.

Do they liquidate our entire guarantee?
No, the liquidator can pay up to a maximum of 50% of the value of the loan, paying us the corresponding value in our deposited currency plus its added 10%.
Resource :

If the collateral have different collateral factor, example: XVS 60%, BNB 80%, BTC 75%, ETH 70%, how the liquidation work? The whitpaper seems didn't have explication for these?
and the Venus how to handle the "Black swan"? I think this is a very important part for VAI.

If the collateral have different collateral factor, example: XVS 60%, BNB 80%, BTC 75%, ETH 70%, how the liquidation work? The whitepaper seems didn't have explication for these?
and the Venus how to handle the "Black swan"? I think this is a very important part for VAI.

Clarification: As of today 01/02/21, all have a collateral factor of 60%, but it can be changed in future proposals.

If the collateral have different collateral factor, example: XVS 60%, BNB 80%, BTC 75%, ETH 70%, how the liquidation work? The whitepaper seems didn't have explication for these?
and the Venus how to handle the "Black swan"? I think this is a very important part for VAI.

Clarification: As of today 01/02/21, all have a collateral factor of 60%, but it can be changed in future proposals.

I know that, but what i say is "if"...

it will be resolved by vai liquidation logic to liquidate vai borrow with vai liquidate in vai controller

it will be resolved by vai liquidation logic to liquidate vai borrow with vai liquidate in vai controller

You still didn't answer the question: "how to handle the “Black swan” of VAI and other lending system".

See this: https://twitter.com/VenusProtocol/status/1394892979190513664
The way you treat the bug finally leads to an incident, this is not how Venus go to the moon.


Fixing issue for SDP avigilon when activating onvif backchannel #479

This will skip the C: attribute when containing SM. This is added by Avigilon cameras, and make the current SDP formatter fail. Original issue: https://github.com/bluenviron/gortsplib/issues/479

@cedricve this can be surely merged but first can you post the troublesome SDP in text format, so i can add it to automatic tests? thanks

@aler9  yes I noticed that. Please find the relevant SDP here.
v=0
o=-<PHONE_NUMBER>694<PHONE_NUMBER>694 IN IP4 <IP_ADDRESS>
s=Live
t=0 0
m=audio 0 RTP/AVP 0
c=IN IP4 <IP_ADDRESS>
a=control:rtsp://<IP_ADDRESS>/defaultPrimary/micCfg0/trackID=9?mtu=1440&streamType=u
a=recvonly
m=audio 0 RTP/AVP 0 97
c=IN IP4 <IP_ADDRESS>
c=SM SM spk0_trackID2
a=control:rtsp://<IP_ADDRESS>/defaultPrimary/spk0/trackID=2?mtu=1440&streamType=u
a=sendonly
a=rtpmap:0 pcmu/8000
a=rtpmap:97 opus/48000/2
m=video 0 RTP/AVP 96
c=IN IP4 <IP_ADDRESS>
a=control:rtsp://<IP_ADDRESS>/defaultPr

merged, thanks

thanks @aler9, will we make a new release?

@aler9 after applying this fix, we have managed to have audio backchannel activates (setup) for Avigilon cameras, however after sending data over the backchannel no audio is streamed through the speaker. So this might not have completely fixed the issue, we expect Avigilon cameras do something very specific.


Localize boolean output

setup rspec
localize boolean output
add localized default of Yes/No values: [feels more natural; can emojified on gusto]

🇬🇧 🇺🇸 🇩🇪 🇪🇸 🇫🇷 🇮🇹 🇳🇱 🇨🇿 🇵🇹 🇷🇺 🇫🇮 🇯🇵 🇰🇷

add customize section to docs

Fixes #1

@neumayr Thanks for submitting this PR!
For the sake of keeping a clean history, I’m going to cherry-pick the RSpec setup commit right into master (thanks for setting that up, by the way!) and I’ll rebase this branch in order to keep just the i18n-related changes on it. I’ve also noticed some style inconsistencies that I’m going to address.
Excellent job on this PR! Hope to have it merged and released later today.

Closed via c88170573aedc734963343e2b21c64c6e78de40c and released v0.1.0.


Integrate 3D printing features/tests

Paul Hvass quote:

The most significant change, I believe, relates to our use case in additive manufacturing. Your current method dilates the surface to create a normal mesh, but then rasters/cuts on a flat even pitch along a user-defined axis. We desire to define the cutting surface (mesh) and then raster at a constant arc-distance away from that surface (refer to the attached pic). It is basically like dilating along the surface to create the raster paths. This need arises in order to deposit (3D print) a constant rate of material as the tool travels along the path.

[ ] Modify existing features and/or add "specific" 3D printing modes.
[ ] Add a use case (ideally provided by SwRI) to test the features.
[ ] Document everything (Doxygen + MarkDown tutorial).
[ ] Change the project description; it's not limited to grinding.

+1


Accept const &str as argument to path and context_path in the path macro

Currently, only string literals are accepted in the path attribute macro for the path and context_path fields:
#[utoipa::path(get, path = "/operation")]
fn operation() {}

I'm trying to get a different path depending on whether I'm building locally or on a server, which I would like to pass with environment variables:
const CONTEXT_PATH: &str = env!("CONTEXT_PATH");
#[utoipa::path(get, path = "/operation", context_path=CONTEXT_PATH)]
fn operation() {}

However, this doesn't currently work, since string literals are the only accepted input for path and context_path.
Is this the best way to approach this issue. and is this a lot of work to implement?
Thanks in advance!

Hey,
This is actually related to this https://github.com/juhaku/utoipa/issues/518. I belive this shouldn't be a too big of an issue and frankly quite easy to implement. Only one thing need to be careful with, that is when implemented, the support would not be added to too many places.
I am planning to have this done sometime in future.
Currently the only feasible wayt around this is to manually implement the paths but that is a lot of cumbersome work at the moment. But then macros should be leveraged there as well. One could also change the path with Modifier but that would also be somewhat clumsy.

Hi,
I think you're right. This is definitely the same issue. Are you accepting PR's? What scope would I have to cover to make an addition?
Thanks!

Sorry for late reply, sure though there is a PR coming soon that provides this implementation. The support came out relatively easily.


Pull Request needs a maintainer?  Making sure I don't need to do anything else.

I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[x ] question about how to use this project

I'm new to this and made a pull request about 3 hours ago.  It says it needs a maintainer to review it?  Is that an actual person that must approve it and thus will take longer?  I'm not in any hurry, I just more or less want to make sure I'm not required to do anything further.
https://github.com/solana-labs/token-list/pull/16397
Thank you!

please leave the issue open so that the bot can run automated checks

I found my error and closed the pull request but forgot to close this issue.  My apologies.


Mac_IL2CPP component installer

Fixes #125
If anyone knows where the path for the Mac_IL2CPP playback engine is we can address that before merge.
I don't have a mac to go and search it out on.

We'll look into finding the Mac_IL2CPP path this week I hope.

Here's the path to the il2cpp folder
@jwittner @StephenHodgson

Hmmm, odd that it'd be under the ios folder.

@awolowiecki720 you sure that's correct for the Mac_IL2CPP?

Alex is running a more controlled test now. Should have results today still.

Actually, looks like this is the install location. Right-click on the Editor.app and "Show Package Contents". IL2CPP installs to this path (before and after pics) @jwittner @StephenHodgson

I wonder what each variation folder's full name is.

Oh, I see, lol. @awolowiecki720 - can you drop in the path to the development_il2cpp folder? The name is collapsed in the images.

Oops. Yea it's
/Applications/Unity/Unity.app/Contents/PlaybackEngines/MacStandaloneSupport/Variations/macosx64_development_il2cpp
@jwittner @StephenHodgson

Can verify that Mac_IL2CPP installs successfully, but I noticed 2 merge conflicts in your code when testing @StephenHodgson
@jwittner what are next steps?

@StephenHodgson If you can resolve your merge conflicts I'll merge this in. =)

Actually I resolved the merge conflict through the cool GitHub tools. =)


Abhaykumar ps patch 1 auto 1

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

f3e2210 Update Makefile
33bde74 Update Makefile
f4c5234 Update config.yml
d90eba3 Update config.yml
adc5d96 Update config.yml
4a07fa7 Update config.yml
7effc9e Merge pull request #1 from abhaykumarPS/abhaykumarPS-patch-1-auto
8e2bd68 Update config.yml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhaykumarPS: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: abhaykumarPS
To complete the pull request process, please assign fjogeleit after the PR has been reviewed.
You can assign the PR to them by writing /assign @fjogeleit in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@abhaykumarPS: There is not a label identifying the kind of this PR.
Please specify it either using /kind <group> or manually from the side menu.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


its that a repackage tools？

im www.cc8.cc websitemaster...this thing is interesting

It's using this http://www.bladeandsouldojo.com/topic/71574-release-bnsdat-xmldat-de-compression-tool/ as an built in function

I had planned to make it capable of unpacking and repacking upk's. I don't have a lot of free me to work on it though.

If you can try to re-package, I would like to donate this project.

I can try to do it. I have a few ways I wanted to test after working with Tera's GPK file. I'll see what I can work up over the month in my free time.

This is good when you begin, please inform me and I hope to get it after this approach, we will help the player creation clothing.
<EMAIL_ADDRESS>发件人： Arisu Miyako
发送时间： 2016-04-06 21:44
收件人： kitsune94/BnSArk
抄送： wh000wh000
主题： Re: [kitsune94/BnSArk] its that a repackage tools？ (#1)
I can try to do it. I have a few ways I wanted to test after working with Tera's GPK file. I'll see what I can work up over the month in my free time.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


add backstage yaml

Figma reference/Github issue
ArCo meeting follow up
https://www.notion.so/casavo/c57399e600c94a4cba24a424d6ec5b25?pvs=4
What
adding Backstage catalog config file
https://www.notion.so/casavo/Spotify-Backstage-Usage-89944cf4477d44d6a285d6dbab4635a4?pvs=4
Why
to enhance the internal software catalog, and to have other projects refer to Habitat as a dependency

@elleuca there are very few info right now since this will be a dependency for other project. Do we want to consider components as APis?

@moebiusmania now you can add it though https://backstage.staging.int.casavo.tech/catalog-import ;-)


Make tensorflow model and git features seperate branches

Just like https://github.com/intel/dffml/tree/binsec

Meh, this is tricky, I think we might just want our own org

since git tags get all messed up

bad idea


Add option to configure zip file name and to produce zip file and exit

Ok, I've made that change and rebased against master.

Cool. Thanks very much!

FYI: Released you changes to PyPi.
https://pypi.python.org/pypi/lambkin
Cheers.

Thanks!


Question 1: Logo/Bug Set On a Time Option?

This is my new favorite app and have been using it daily. My question though is I noticed the logo or "bug" as it is called at tv stations has no option for a timed automatic display (such as having the bug appear once every 10 minutes for 10 seconds). Is there a way to make this happen or add as an option?
The other logo/bug question I had was...would it be possible to add the option to display more than one bug? Such as a bug that displays once per hour at the start of the hour for a set duration automatically during a program...and the other bug displaying elsewhere on the screen at the same time for another set time, or through entire program?
Example logo/bug 1: "This program Broadcasts in 4k" displays at the top of every hour for 10 seconds duration.
and the other logo/bug displays and has its own duration settings somewhere else on the screen at the same time?

These are both interesting ideas. Not very straight forward to do, mostly because of how we rely on ffmpeg filters to draw the watermarks...
If you enable the option that makes the bug go away after some time. It will appear at the beginning of a video and then it will go away until the next video starts playing. This is not exactly what you want in your first suggestion, but in practice, it is really close.

Hello, Yes the current option available for the bug to go away after a certain amount of time is still a nice option, it displays at the start of the clip, but it is better than nothing for a timed watermark/logo.  Thanks for your reply and clearing that up, and for taking what I asked about into consideration for any future additions, even if it can be done or not.  If ffmpeg filters draw the watermarks than I understand how it could be a complex process.


Add percentage text to drive allocation indicator in properties #3131

Resolved / Related Issues

Closes #3131

Details of Changes

Added text in the center of the allocation chart which displays the percentage rounded to the nearest whole number.

Screenshots (optional)

@oleitao is it possible to just modify the WinUI progress ring? We'd like to avoid taking on additional dependencies if posible.


LM - Training sanity check

Today, if the LM training crashes it may results in a usable but incomplete LM.
We should add a sanity check suring the training phase.
If the sanity check fail the training must abort with an error message.
Important but not priority, assigning to milestone 0.13

I am already working on this
Any suggestion how to run tests on this?
We should create critical situations and verify whether the software is able to spot them.
Nicola

Isn't the easiest way to determine crashes to check exit codes?

use "set -e" in bash scripts to make them exit immediately if something
goes wrong
never pipe or write to the final output file directly; pip/write into a
temporary file and rename at the end
if a program produces several output files, write into a temporary
directory and then move the contents of that directory to the final
destination.

E.g.,
#!/bin/bash
set -e
myprogram > output.tmp && mv output.tmp output.final
On Mon, Mar 7, 2016 at 3:48 PM, Nicola Bertoldi<EMAIL_ADDRESS>wrote:

I am already working on this
Any suggestion how to run tests on this?
We should create critical situations and verify whether the software is
able to spot them.
Nicola
—
Reply to this email directly or view it on GitHub
https://github.com/ModernMT/MMT/issues/106#issuecomment-193307445.

--
Ulrich Germann
Senior Researcher
School of Informatics
University of Edinburgh

These scripts are no longer used in MMT (currently we use KenLM as base LanguageModel)


Screen reader: say " connected" instead of "connected "

"connected <device name>" kinda makes sense, so I left it like that for a while, but, it's really not supposed to be announcing the fact that you connected a device, but that a device is now connected/available.
Particularly, if you turn on a device, rather than plug it in, "<device name> connected" should make more sense. It's like, the device is connecting to the system, it's not you (or the application) explicitly connecting the device.

This is fine tbh.


Authentication kit improvements

Moved away from the Connected, New Session Connected and Resumed Session Connected WalletConnect events to make the process more reliable
Added retry button for connecting and signing on Android and iOS
Only OpenDeepLink if we need to accept a new connection
Updated WalletConnect to latest version and enable timeout refresh and QR loading animation
Change State names to better reflect the state
Fixed Web3 not getting set up on stored session
Added extra ReadyForUserPrompt check on Android and iOS with 15 seconds timeout to help with unresponsive bridges
Updated default server settings
Only download medium wallet images to speed up iOS wallet list

LGTM
Reveiwed the code and ran battery of integration tests


Revert "Only for #hacktoberfest"

Reverts MicrosoftDocs/mixed-reality#635
This was a junk Hacktoberfest PR that made bad changes to the metadata. Those PRs should get the "invalid" flag added to them so they are filtered out of the program

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/app-views.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

I don't understand. When I looked at the markdown, they looked exactly the same. I know the PR is unnecessary, but what in the changes is "bad" (just for my own edification)?

The metadata attributes are supposed to be lower case


swagger-codegen upgrade

Thanks for the contribution.  Apparently, the new version of codegen requires gson-fire.  Could you add this dependency to see if build succeeds ?


ScottPlot 5: Stiatistical distribution issue

Issue:
We are update code from ScottPlot 4 to 5 and we have a very simple graph like https://scottplot.net/cookbook/4.1/category/statistics/#histogram-stdev.
We observed that when we add the Function the function does't take the graph limits.

Our code is the following:
var probabilityCurve = hist.GetProbabilityCurve(data);
Func<double, double> probabilityCurveDouble = (x) =>
{
	var y = probabilityCurve.Invoke(x);
	return y.HasValue ? y.Value : 0;
};
var function = myPlot.Add.Function(probabilityCurveDouble);
function.MaxX = data.Max();
function.MinX = data.Min();

The issue is in the function Add Function not set axis limit
we try this code
var probabilityCurve = hist.GetProbabilityCurve(data);
Func<double, double> probabilityCurveDouble = (x) =>
{
	var y = probabilityCurve.Invoke(x);
	return y.HasValue ? y.Value : 0;
};
var functionSource = new FunctionSource(probabilityCurveDouble)
{
	RangeX = new CoordinateRange(hist.Min, hist.Max),
};

var function = myPlot.Add.Function(functionSource);

the issue remain
we fixed like that
double delta = (maxValue - minValue) / 100;
for (double x = minValue; x < maxValue; x += delta)
{
	double x0 = x;
	double x1 = x + delta;

	double? y0 = probabilityCurve.Invoke(x0);
	double? y1 = probabilityCurve.Invoke(x1);

	if (y1 == null || y0 == null)
	{
		continue;
	}

	Coordinates pt1 = new Coordinates(x0, y0.Value);
	Coordinates pt2 = new Coordinates(x1, y1.Value);
	var line = myPlot.Add.Line(pt1, pt2);
	line.MarkerSize = 0;
	line.LineWidth = 2;
	line.LinePattern = LinePattern.Solid;
	line.Color = ScottPlot.Colors.DarkRed;
}

Hi @linefinc, thanks for reporting this!
The code examples fall a bit short because there's not a program in  this comment I can run on my machine to reproduce the issue... but I think I understand the problem

The issue is in the function Add Function not set axis limit

It sounds like this is the core problem.
Does setting the function's MinX and MaxX properties resolve this issue?
https://scottplot.net/cookbook/5.0/Function/FunctionLimitX/


KING step reports an error when no related individuals are detected

Also an issue reported from Travyse. We need to consider this and make the step more robust.

After a fix, we are able to produce the unrelated.bed, using king properly when there is no related individual. However, I wonder whether we should avoid checking the related.bed because the related.bed will not always be produced.


Column names with TEXT format

When using TEXT as an import format, I couldn't find a way of configuring the column name. The column name seems to be evaluated as long as we don't specify * in the SELECT statement which we have to do for TEXT files. Am I missing something?
Here's an example:
cat /tmp/test.txt | spyql -Otable=domains 'Select * as colname from text To SQL'
INSERT INTO "domains"("col1") VALUES ('aaaaaaaaaa'),('bbbbbbbbb'),('cccccccccc'),('dddddddddd'),('eeeeeeeeee');

cat /tmp/test.txt | spyql -Otable=domains 'Select 1 as colname from text To SQL'
INSERT INTO "domains"("colname") VALUES (1),(1),(1),(1),(1);

Expected result would be:
cat /tmp/test.txt | spyql -Otable=domains 'Select * as colname from text To SQL'
INSERT INTO "domains"("colname") VALUES ('aaaaaaaaaa'),('bbbbbbbbb'),('cccccccccc'),('dddddddddd'),('eeeeeeeeee');

Can you please try the following?
cat /tmp/test.txt | spyql -Otable=domains 'Select col1 as colname from text To SQL'

Columns in spyql can be accessed by index using the syntax colX where X is the index of the column, starting in 1. So, col1 gives you access to the 1st column. In the case of the text input format, there's only 1 input column and there isn't any other way to access it since the text input format does not support headers.
The alias is ignored in *... probably spyql should report an error in your query...

Thanks, that worked!
I would suggest add this info to the documentation for future reference.

Makes perfect sense :-) Thank you for trying out spyql!!


Screenshot Integration tests CI feature

Follow up issue from https://github.com/lit/lit.dev/pull/463
We need a way to generate playwright screenshot goldens using the CI environment. Otherwise there are render issues between operating systems.

Done!


feat(app): introduce action needed text for module and deck section in ProtocolRunSetup

Overview
introduce action needed text for module and deck
design
https://www.figma.com/file/Nx7ORMnfyJNP4FQYxN4e5x/Primary%3A-Desktop-App?type=design&node-id=1867-195872&mode=design&t=zcW1Zvf2uvAo4qhI-4
conditions for status text
When a module needs to be connected, needs to be calibrated or has been connected - show the same status as the pipettes
Module not connected, Fixtures not configured, Location conflict with deck configuration, firmware update required on pipette = “Action needed”
Module has not been calibrated yet = “Calibration needed”
Everything connected, configured and calibrated = “Calibration ready”

also updates location conflict modal text for modules
closes RAUT-869, RAUT-836
Test Plan

Changelog

update ProtocolRunSetup and its test
update ProtocolRunHeader and its test

Review requests
For notCompatible, the current implementation is to detect not configured / location conflict.
Any suggestions are appreciated If there is better way to do that and an accurate name for that.

Risk assessment

notCompatible changed to isFixtureMismatch determined by utility getIsFixtureMismatch


modem: ubx: fix incoming byte processing

ret holds the amount of bytes received from the modem. However during processing of the bytes its value is overwritten by the return value of modem_ubx_process_received_byte, in practice discarding all but the first byte read.
To prevent this, store the length in a separate variable.

Found an unhandled possible malloc null-pointer ref.


Request validation at compile-time

Is your feature request related to a problem? Please describe.
Currently, requests are validated at runtime, before they are sent out to the server.
It would be better if the requests are validated at compiletime, so that developers using our library can create more robust code with as little runtime errors as possible, creating a smoother developing experience in the end.
Describe the solution you'd like
Thomas suggested using the (TypeState) builder pattern, so that only requests that are complete have an implemented build() method.

Note: currently the single_ledger_request_builder does not have the validation (in order to solve just one problem at a time, which is implementing the builder pattern at this time). Must remember to add (re)add validation at a more completed stage of the builder pattern.


ClientRetryPolicy: Adds Cross Regional Retry Logic on 429/3092 and 410/1022

Pull Request Template
Description
This PR is covering two CRI scenarios in general:

Gone Exception (Status Code: 410) with Lease Not Found (Sub Status Code: 1022).
Request Throttled (Status Code: 429) with System Resource Unavailable (Sub Status Code: 3092).

The behavior changes are described below in detail:
Background: In general 410/1022 is used as a signal to indicate that a region is not part of the dynamic quorum - meaning in global strong with dynamic quorum all reads from the secondary region kicked out of the quorum will return 410/1022.

Today when a read region loses the read lease it returns 410/LeaseNotFound - the client will then retry locally for up-to 60 seconds (for global strong) and up-to 30 seconds (for others) (catch-all 410 retry like for 410/0 or connectivity related 410) for any.
Instead the 410/LeaseNotFound(1022) should be mapped immediately to a 503 to allow the cross-regional retry to happen as quickly as possible. Retrying in the next preferred region like usual for reads is acceptable. This has been taken care in the Cosmos.Direct release 3.36.0 and this PR is upgrading the Cosmos.Direct version to 3.36.0 to reflect the change.

For 429/3092 (Request Throttled/ SystemResourceUnavailable), we would only want to short-circuit this to retry cross-region quickly when we can actually retry cross region (not a write in single master) - and for reads only when it is returned from all replica in a region. The latter is extremely unlikely - so, I would probably compromise on a pragmatic approach and simply short-circuit by mapping 429/3092 to a 503 for write operations when multi-master is enabled (and there is >1 write regions).
That way we get the cross-region retry in the scenario where this is most critical.

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Closing issues
To automatically close an issue: closes #4656, #4390

Since you are updating the direct package in this PR it might be good to include a summary of the changes in the PR description as well.


esphome: 2021.12.0 -> 2021.12.1

Motivation for this change
https://github.com/esphome/esphome/releases/tag/2021.12.1
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

esphome


elixir-ls builds not actually compatable with OTP 21

Elixir & Erlang versions (elixir --version):Erlang/OTP 21 [erts-10.2.4] [source] [64-bit] [smp:32:32] [ds:32:32:10] [async-threads:1]
Elixir 1.10.4 (compiled with Erlang/OTP 21)

Operating system: Debian 10
Editor or IDE name (e.g. Emacs/VSCode): None
Editor Plugin/LSP Client name: None

The README says that OTP 21 is the minimum required versiont, but when I run language_server.sh from https://github.com/elixir-lsp/elixir-ls/releases/download/v0.7.0/elixir-ls-1.10.4.zip on my system, I get an error about the OTP version being too old, even though I am running with the version of OTP stated in the error message.  The build from elixir-ls-1.9.zip (same release) does not work either, saying it uses opcode 164 instead of 169, but elixir-ls-1.8.2.zip does run successfully.  If I build elixir-ls from the source tarball from the same release, it also works as expected.
$ /path/to/elixir-ls-1.10.4/language_server.sh

09:54:48.977 [error] Loading of /path/to/elixir-ls-1.10.4/language_server-0.7.0.ez/language_server-0.7.0/ebin/Elixir.ElixirLS.LanguageServer.CLI.beam failed: :badfile

09:54:48.978 [error] beam/beam_load.c(1878): Error loading module 'Elixir.ElixirLS.LanguageServer.CLI':
  This BEAM file was compiled for a later version of the run-time system than 21.
  To fix this, please recompile this module with an 21 compiler.
  (Use of opcode 169; this emulator supports only up to 163.)

09:54:48.978 [error] Loading of /path/to/elixir-ls-1.10.4/language_server-0.7.0.ez/language_server-0.7.0/ebin/Elixir.ElixirLS.LanguageServer.CLI.beam failed: :badfile

09:54:48.978 [error] beam/beam_load.c(1878): Error loading module 'Elixir.ElixirLS.LanguageServer.CLI':
  This BEAM file was compiled for a later version of the run-time system than 21.
  To fix this, please recompile this module with an 21 compiler.
  (Use of opcode 169; this emulator supports only up to 163.)

** (UndefinedFunctionError) function ElixirLS.LanguageServer.CLI.main/0 is undefined (module ElixirLS.LanguageServer.CLI is not available)
    ElixirLS.LanguageServer.CLI.main()
    (stdlib 3.7.1) erl_eval.erl:680: :erl_eval.do_apply/6
    (elixir 1.10.4) lib/code.ex:341: Code.eval_string_with_error_handling/3

We are officially supporting last 3 OTP releases, that wold be 22-24

We are officially supporting last 3 OTP releases, that wold be 22-24

OK, so then it sounds like this is a documentation bug, since the README says that 21 is the minimum supported release.

@aidalgol thanks for pointing that out. I'm updating the docs in https://github.com/elixir-lsp/elixir-ls/pull/561


documentation error

In the pyuvdata.UVData documentation, the baseline_array attribute says the following
"Array of baseline indices, shape (Nblts), type = int; baseline = 2048 * (ant2+1) + (ant1+1) + 2^16"
which should read w/ ant1 and ant2 switched.

Thank you for catching this @nkern. Can you review the PR to fix it? (#357)


Failure to write when output folder doesn't exist.

Many tools that process textures often have subfolders that need to be created.  I noted that cuttlefish was failing to write on these cases when I'd wipe the parent directory.  It would be useful to have cuttlefish build subdirectories if they don't exist when providing an output path to simplify scripting and repeatability of texture processing.
I was trying cuttlefish after switching off PVRTexToolCLI, and this was one notable difference and breakage in the texture processing between these utilities.
This is the basic source to create the full path of directories and then open a file.  This could be split out into a mkdir call, and the fopen call could just proceed normally then.  Current behavior is a rather cryptic failure to write message,, so so I thought the encoder was failing.
// https://stackoverflow.com/questions/7430248/creating-a-new-directory-in-c

void rek_mkdir(char *path) {
    char *sep = strrchr(path, '/');
    if(sep != NULL) {
        *sep = 0;
        rek_mkdir(path);
        *sep = '/';
    }
    if(mkdir(path, 0777) && errno != EEXIST)
        printf("error while trying to create '%s'\n%m\n", path);
}

FILE *fopen_mkdir(char *path, char *mode) {
    char *sep = strrchr(path, '/');
    if(sep) {
        char *path0 = strdup(path);
        path0[ sep - path ] = 0;
        rek_mkdir(path0);
        free(path0);
    }
    return fopen(path,mode);
}

Workaround for now is in scripts to call this before calling cuttlefish.
mkdir -p "$(dirname "$output")"

What version of PVRTexToolCLI and on what operating system were you running? When running PVRTexToolCLI 4.23 (from the 2019.R2 install) on Linux, I get the following error message if the parent directory doesn't exist:

Error: Unable to save texture as requested format, please check the format being used is supported.

It's been my impression that tools that output a single file by path (as opposed to providing an output directory) error out if the parent directory doesn't exist. To verify this, I tried a few other tools such as gcc and another texture conversion tool I found online, and none of them create the parent directory for you.
While I agree it can be useful, it's also good practice to make as few changes to the filesystem as possible inside the tool. Since the general trend among similar tools is to not create the parent directories, I would be hesitant to do so for cuttlefish.

Yeah, I found most tools don't create directories including PVTexToolCLI.   I was working with a script that was failing when I switched to Cuttlefish, but I found out later it needed that directory creation for PVRTexToolCLI as well.  There's a workaround, but it means more scripting instead of keeping it all in C++.  EtcTool does have some directory creation calls inside it.

I feel it's better to keep consistent with the conventions used with other command-line utilities, since it offers fewer surprises when working with multiple tools. While it can be useful to create the parent directories for you, it can also be useful to be given an error if you passed it the wrong directory name. (e.g. you get an error if you have a typo in the directory name rather than creating the directory)
Rather than calling mkdir -p "$(dirname "$output")" before invoking Cuttlefish for each texture, I would recommend creating your directory structure at the start of the build process. That is pretty common practice, will provide some protections if you accidentally put something in the wrong place, and will also work more gracefully when integrating other tools into your build process.

I this case I want to let the artists to organize their content they way they feel best, so new folders could appear/disappear at any time.  Draconian measures to stuff all textures into a flat hierarchy aren't always best, but certainly easier for the engine to deal with then.

I was thinking along the lines of building an asset package, but in the case of a tool for artists I agree it would ideally follow the directory structure of their source images.
Since I think the default behavior should stay as it is, as a compromise I can add a command-line argument to have Cuttlefish create the parent directory for you.

You can now use the --create-dir command-line argument in version 2.1.0.


Update network validation script

Testing

Errors shown when no rules are added for Security Lists.

No errors, when all the required rules are added for Security Lists.

Errors shown when no rules are added for Network Security Groups.

No errors, when all the required rules are added for Network Security Groups.

Updated Testing
Now, when https_port and wls_lb_port are provided, it would check for that. If not provided, it by default checks for 9002 and 7004. Also the switch between IDCS and Managed Server port supports both secured and non-secured production mode.