xdiff as one of built-in functions

I sometimes set diffexpr option to modify the diff behavior. For example, the following script compares different windows line-by-line.
set diffexpr=LineByLineDiff()
function! LineByLineDiff()
    let opt = '-a --binary '
    if &diffopt =~ 'icase' | let opt .= '-i ' | endif
    if &diffopt =~ 'iwhite' | let opt .= '-b ' | endif
    let [fi, fn, fo] = [v:fname_in, v:fname_new, v:fname_out]
    call writefile(map(readfile(fi), 'v:key . ":" . v:val'), fi)
    call writefile(map(readfile(fn), 'v:key . ":" . v:val'), fn)
    call writefile(split(system('diff ' . opt . fi . ' ' . fn), '\n'), fo)
endfunction

Until patch 8.1.360, in which the internal xdiff library was build in vim, it has been necessary to use the the external diff command.
I am interested in using the xdiff as well in my script because it should be much faster and, more importantly, the diff command should not be required in a system.
Is it possible to implement the xdiff as one of built-in functions?

I had requested diff as a builtin function to be used in vimscript here. https://github.com/vim/vim/issues/4191#issuecomment-478213781


Replace smart quotes feature should not replace characters in code fence

This feature was added in #429 but it is not listed in the change log.
The feature does a global replace of all mapped characters, including characters inside of markdown code blocks and code spans. Text inside of code fences should be treated as literal text and should not be changed.
I ran into this problem recently when updating this article. This article talks about character encoding issues and includes character examples that are replaced by this feature. All the example characters are contain in code fences. The article is explicitly trying to show what happens when you don't use the correct character encoding. We need to show these characters as they are presented in real life.
For example:

an en-dash (–) appears as the characters â€"

gets changed to:

an en-dash (–) appears as the characters â@euro;"

cc: @IEvangelist
AB#281117

Hi @sdwheeler - hope all is well. This feature defaults to off, and is an exclusive opt-in feature. To turn it off, follow these steps here. I was already aware that it replaced text in code fences, I simply haven't had the bandwidth to fix that yet. For now the workaround is to disable this, and only toggle it on when you need it. Sorry for the inconvenience.

@IEvangelist, thanks. I knew about the configuration switch and turned it off.


How/when/where to trigger the computation of the residual

Currently the reaction force sensor assumes that a residual is given, which is hard coded in the linear elastic model, as this uses that sensor. This is not a good solution, just temporary and needs to be fixed

We had a similar discussion over at fenics-constitive, I remember.
The residual needs to be computed anyways, so I suggest having a residual member where the residual is stored before applying the boundary conditions. This is what I tried for dolfinx here.
One way to evaluate it is to pass this vector to a LoadSensor.__init__ and extract the DOF values in __call__.

will be addressed in fenicsXconcrete


Internal reporters

This PR refactors and cleans up all our output, makes it easier to test and introduces the possibility to change reporters and write new ones.
Note: it is not meant to be exposed to end users, this is only for internal usage.
This is a preparation for #359. After #359 we'll have 3 reporters:

verbose (current default reporter)
mini
tap

LGTM

LGTM

This cleans it up nicely :)


Handle unknown keys more gracefully

When a client connects with an unknown key type (e.g. ECDSA) to an awa-ssh server the server doesn't recognize the key type and gives up parsing. It would be more graceful if the server handles unknown keys by informing the client that the provided key isn't accepted.

at the same time, would it be worth to add more KEX to the server implementation? I can do that for you, or together with you, if you like :)

The ECDH key exchange algorithms are supported in #63 for the server. Still, only ED25519 and RSA hostkeys (client keys) - so I will leave this open.

done with #68


Fix react 'missing key' warning

<TableHeader/> was creating children via a loop
with no key property set. This causes a warning in React.
Added key (index) to the new children created.

@sirreal , Thanks for your contribution :)

My pleasure, and thanks for your work. I'm using this for a project right now and if I have some time I'll try to submit some more PRs with some of the work I've done.


Add camelCase methods to support drop-in replacement of thrift

In an effort to support both python 2 and 3, I am trying to use both the Apache Thrift python package and thriftpy.  One thing that makes it more difficult is that method names have been changed from the Apache camelCase to the more pythonic snake_case.  However, it would be convenient to have camelCase versions available so that I don't have to check the python version each time I want to invoke a method.
For example, thriftpy.transport.buffered.cybuffered.TCyBuffered.is_open while the Apache version would generate an isOpen method.
Thoughts?

We once used python sdks from both Apache Thrift and thriftpy internally for some time. In our situation, we wrap the client, so only the api calling part, such as client.ping() is opened to the outside, and the codes will stay the same.
I've considered this problem when developing the lib. The thriftpy was a rewrite based on 'pythonic thinking', so many code actually (including apis) differs from the upstream. Take TBinaryProtocol for example, the useless methods were all removed, and the read/write struct logic have a slight difference too.
The camelcase is one of many unpythonic things, if I keep the camelcase style, there will be snake_case and camelCase code mixed together in this lib. And keep the camelCase also means make the interface thing 100% compatiable with Apache Thrift, but the interface itself is just not pythonic, it's designed for java. When the interface is not 100% kept same in thriftpy, you'll find both lib have some unique methods, then the camelCase is not that important anymore.
So my suggestion is wrap the client and only expose that to your clients.

k, I'll close this issue.  Thanks!


Add support for async Cage runs to python

Why
Expose async Cage runs and specifying Cage version through the python SDK
How
Add an options parameter to the run function.
Also added tests, and did a small refactor around tracking the version and package metadata.

I think all the .pyc files aren't meant to be committed

I think all the .pyc files aren't meant to be committed

Hadn't realised they were being tracked. Deleted 'em and added to the .gitignore!


Cognito Auth role has incorrect ARNs for REST APIs

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum

Describe the bug
I have an API in my project that permits authenticated traffic only.
The Auth role for my Cognito user pool (created by Amplify CLI) has improperly formatted ARNs
This results in being unable to call the API successfully, calls are met with 403s from the API
Policy:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "execute-api:Invoke"
            ],
            "Resource": [
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/POST//*",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/POST/",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/GET//*",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/GET/",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/PUT//*",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/PUT/",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/PATCH//*",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/PATCH/",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/DELETE//*",
                "arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/DELETE/"
            ],
            "Effect": "Allow"
        }
    ]
}

To Reproduce
Steps to reproduce the behavior:

Add auth
Add REST API with restricted access
Call API
See 403 response

Expected behavior
Calls to the API should succeed
Additional context
CLI version 1.7.3

Hi @anatonie
When the Rest API is being added to your project, you need to provide answers to a series of prompted questions, one of them is Provide a path (e.g., /items), if you take the default value, it'll be /items, and the Resource in the policy statement will contain it, like this:
arn:aws:execute-api:us-west-2:239336166108:{APIID}/prod/POST/items/*
I was not able to reproduce the issue you reported using the default answers. Did you manually modify anything before you execute amplify push?

You are correct, I forgot I modified the path.
I modified the path from '/api' that I chose during setup to '/', so no bug here.
However I did this because using multiple lambdas for different paths is overkill, and the express function can handle multiple paths.
Using a separate function could increase wait times due to cold starts.
Is there a reason for this limitation?
API Gateway/Lambda support using a single lambda for all paths.

@anatonie Why would you use a separate lambda function for another path? You could just use amplify update api and add an additional path to an exisiting REST API in your project and then use the lambda function which is behind that REST API  endpoint. This seems to be a different question/query than the original issue. Could you please open another issue for this if you're still having more questions?


Security Slam 2023 Participation

Hello kubecost community!
In case you missed it, last week was the kickoff for the month-long Cloud Native Security Slam! You can read more about the event and find the kickoff webinar recording here.
In the kickoff last week, it was announced that there are 5 event badges that projects can pursue. There will be swag prizes and a $100 gift card awarded for the first 200 badges that are competed— that's up to $500 per project!
To help with work prioritization, we completed a survey of CNCF end users across multiple industries, including Construction, Cybersecurity, Aerospace & Defense, Game Development & Consumer Services, Consulting, and Nuclear.
Through this survey, end users have identified their interest in seeing security improvements to the projects they use. We've asked them to share which Security Slam goals are most interesting to them— and we've compiled the results in a hope that this will help your prioritization during the upcoming event.
While some users have not authorized us to share their name, we've still included their responses in our calculation for you. We CAN tell you that the kubecost responses included Epic Games and Infosys.
After calculating the responses according to the interest-weight, we've found these to be the most interesting things that kubecost end users would like to see, from the five possible Security Slam badges.

The Mechanizer
The Chronicler
The Inspector, The Cleaner (tie)

You can read more about the success metrics and find resources to help you achieve them here.
Join us in the #security-slam channel on the CNCF Slack to ask questions and get help from the community!

thanks eddie, closing for now


How to reload config and doc settings

Currently I have the following plugin which is supposed to let me change the indentation size and indentation type (tabs / spaces). But when the indentation has been changed, the settings are not active. So if I go from indentation level 2 -> 4, then it still uses the indentation level 2.
local core = require "core"
local config = require "core.config"
local command = require "core.command"
local Doc = require "core.doc"

command.add(nil, {
  ["indent:set-indentation-level"] = function()
    core.command_view:enter("Indent Size", function(text)
      config.indent_size = tonumber(text)

      -- Reload docs / settings here

      core.log("Set indentation level to %s", text)
    end)
  end
})

command.add(nil, {
  ["indent:set-indentation-type"] = function()
    core.command_view:enter("Indent Type", function(text)
      if text == "space" then
        config.tab_type = "soft"
      else
        config.tab_type = "hard"
      end

      -- Reload docs / settings here

      core.log("Set indentation type to %s", config.tab_type)
    end, function(text)
      return {"space", "tab"}
    end)
  end
})

I have a hunch this might be the detectindent plugin messing with your setting. It seems to override any existing settings every frame, but I'd ask @franko just to be sure.

Ah, that's very possible. I can test if this is true by disabling the detectindent plugin. But, when doing:
local config = require "core.config"
Is that the global config, or a local one? Do I have to override the config used for drawing?

The Lua module system works in this way:

the first time you call require "somemodule, it will look up the module somemodule and save it in the package.loaded table
each next time you try to require somemodule it will instead return the value stored in package.loaded

So core.config is loaded once and then shared between all subsequent require calls.

Ah, so when I do:
config.indent_size = 4
It is changed everywhere because there's only one shared config?

Exactly.

I confirm that "detectindent" override the indent_size setting. As from 1.16 plugins can be disabled from the config so the line:
config.detectindent = false

should be enough to disable it.

Doing: config.detectindent = false does not seem to work AFTER it has been loaded.
So doing:
local core = require "core"
local config = require "core.config"
local command = require "core.command"
local Doc = require "core.doc"

-- Disable "detect indent" plugin if exists
config.detectindent = false

command.add(nil, {
  ["indent:set-indentation-level"] = function()
    core.command_view:enter("Indent Size", function(text)
      config.indent_size = tonumber(text)

      core.log("Set indentation level to %s", text)
    end)
  end
})

command.add(nil, {
  ["indent:set-indentation-type"] = function()
    core.command_view:enter("Indent Type", function(text)
      if text == "space" then
        config.tab_type = "soft"
      else
        config.tab_type = "hard"
      end

      core.log("Set indentation type to %s", config.tab_type)
    end, function(text)
      return {"space", "tab"}
    end)
  end
})

Does not work.
detectindent overwrites the Doc:, so where do I disable the module before load?

You have to disable it in your init.lua (Core: Open User Module), as it is loaded before all plugins.

Yep, that fixes it.


Fix pg password errors when launching via docker compose

Hiya Kong Team!
I pulled this repo tonight and quickly ran into some issues when trying to launch the services defined in compose/docker-compose.yml. After a little debugging, I realized that this is due to the names of some environment variables defined in that file. I'd love to submit a tiny PR that fixes the issue.
Here's more detail about the situation:
At the current master sha (b6fed1072fae589543f71a1bd92dbde880a61850), docker-compose up fails to launch all but the db container, with errors that look like this:
kong-migrations_1     | Error: missing password, required for connect
kong-migrations_1     |
kong-migrations_1     |   Run with --v (verbose) or --vv (debug) for more details
compose_kong-migrations_1 exited with code 1

kong-migrations-up_1  | Error: missing password, required for connect
kong-migrations-up_1  |
kong-migrations-up_1  |   Run with --v (verbose) or --vv (debug) for more details
compose_kong-migrations-up_1 exited with code 1

kong_1                | 2020/04/15 05:19:21 [error] 1#0: init_by_lua error: /usr/local/share/lua/5.1/pgmoon/init.lua:271: missing password, required for connect
kong_1                | stack traceback:
kong_1                | 	[C]: in function 'assert'
kong_1                | 	/usr/local/share/lua/5.1/pgmoon/init.lua:271: in function 'auth'
kong_1                | 	/usr/local/share/lua/5.1/pgmoon/init.lua:211: in function 'connect'
kong_1                | 	.../share/lua/5.1/kong/db/strategies/postgres/connector.lua:202: in function 'connect'
kong_1                | 	.../share/lua/5.1/kong/db/strategies/postgres/connector.lua:489: in function 'query'
kong_1                | 	.../share/lua/5.1/kong/db/strategies/postgres/connector.lua:270: in function 'init'
kong_1                | 	/usr/local/share/lua/5.1/kong/db/init.lua:138: in function 'init_connector'
kong_1                | 	/usr/local/share/lua/5.1/kong/init.lua:389: in function 'init'
kong_1                | 	init_by_lua:3: in main chunk
kong_1                | nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/pgmoon/init.lua:271: missing password, required for connect
kong_1                | stack traceback:
kong_1                | 	[C]: in function 'assert'
kong_1                | 	/usr/local/share/lua/5.1/pgmoon/init.lua:271: in function 'auth'
kong_1                | 	/usr/local/share/lua/5.1/pgmoon/init.lua:211: in function 'connect'
kong_1                | 	.../share/lua/5.1/kong/db/strategies/postgres/connector.lua:202: in function 'connect'
kong_1                | 	.../share/lua/5.1/kong/db/strategies/postgres/connector.lua:489: in function 'query'
kong_1                | 	.../share/lua/5.1/kong/db/strategies/postgres/connector.lua:270: in function 'init'
kong_1                | 	/usr/local/share/lua/5.1/kong/db/init.lua:138: in function 'init_connector'
kong_1                | 	/usr/local/share/lua/5.1/kong/init.lua:389: in function 'init'
kong_1                | 	init_by_lua:3: in main chunk
compose_kong_1 exited with code 1

I believe the services - including the db itself - are not receiving a db password via the environment variables. I looked at the docker compose syntax doc around secrets, as well as the docs for the postgres image and kong image, and determined that the password environment variable names shouldn't end with _FILE.
With the following changes, docker-compose up seems to launch the services as intended:
diff --git a/compose/docker-compose.yml b/compose/docker-compose.yml
index de946b8..4fb761e 100644
--- a/compose/docker-compose.yml
+++ b/compose/docker-compose.yml
@@ -18,7 +18,7 @@ services:
       KONG_PG_DATABASE: ${KONG_PG_DATABASE:-kong}
       KONG_PG_HOST: db
       KONG_PG_USER: ${KONG_PG_USER:-kong}
-      KONG_PG_PASSWORD_FILE: /run/secrets/kong_postgres_password
+      KONG_PG_PASSWORD: /run/secrets/kong_postgres_password
     secrets:
       - kong_postgres_password
     networks:
@@ -38,7 +38,7 @@ services:
       KONG_PG_DATABASE: ${KONG_PG_DATABASE:-kong}
       KONG_PG_HOST: db
       KONG_PG_USER: ${KONG_PG_USER:-kong}
-      KONG_PG_PASSWORD_FILE: /run/secrets/kong_postgres_password
+      KONG_PG_PASSWORD: /run/secrets/kong_postgres_password
     secrets:
       - kong_postgres_password
     networks:
@@ -64,7 +64,7 @@ services:
       KONG_PG_USER: ${KONG_PG_USER:-kong}
       KONG_PROXY_ACCESS_LOG: /dev/stdout
       KONG_PROXY_ERROR_LOG: /dev/stderr
-      KONG_PG_PASSWORD_FILE: /run/secrets/kong_postgres_password
+      KONG_PG_PASSWORD: /run/secrets/kong_postgres_password
     secrets:
       - kong_postgres_password
     networks:
@@ -83,13 +83,13 @@ services:
     deploy:
       restart_policy:
         condition: on-failure
   db:
     image: postgres:9.5
     environment:
       POSTGRES_DB: ${KONG_PG_DATABASE:-kong}
       POSTGRES_USER: ${KONG_PG_USER:-kong}
-      POSTGRES_PASSWORD_FILE: /run/secrets/kong_postgres_password
+      POSTGRES_PASSWORD: /run/secrets/kong_postgres_password
     secrets:
       - kong_postgres_password
     healthcheck:

Happy to submit this change as a PR.
-Justin

Ah - hmm - I see what I actually did here. Just set the password to /run/secrets/kong_postgres_password.. I don't believe it's reading from the file anymore..

hi @hellojustin , I come to the same problem and realize kong still not support reading from file yet https://github.com/Kong/docker-kong/issues/91, hope it helps.

Thanks @jazztong - yeah, reading from secrets files seems to work for postgres:9.5 but not for kong:latest, which I believe points to kong:alpine-2.0.3. That image was released 6 days ago, which should include the changes from https://github.com/Kong/docker-kong/pull/348/files, which seems to be the PR where support for reading secrets files was added.. So I'm a little stumped still. Going back to plain-old env vars for now!

We had some challenges such that the official docker image builder wasn't appreciative of how we setup our Dockerfiles. As a result the docker-compose in master was dependent on a feature that never made it to the official images.
That should be resolved as of 2.0.4 ( https://github.com/docker-library/official-images/pull/7880 ) and I will backport the fix to 2.0.3.
In the meantime our unofficial docker images will work in a pinch https://hub.docker.com/repository/docker/kong/kong/tags?page=1

I have the same problems with password. Are there any wrong?? how to fix it???
kong-migrations_1     | kong-migrations_1     |   Run with --v (verbose) or --vv (debug) for more details compose_kong-migrations_1 exited with code 1 kong-migrations-up_1  | Error: missing password, required for connect kong-migrations-up_1  | kong-migrations-up_1  |   Run with --v (verbose) or --vv (debug) for more details compose_kong-migrations-up_1 exited with code 1 kong_1                | 2020/04/28 02:19:05 [error] 1#0: init_by_lua error: /usr/local/share/lua/5.1/pgmoon/init.lua:271: missing password, required for connect kong_1                | stack traceback: kong_1                |         [C]: in function 'assert' kong_1                |         /usr/local/share/lua/5.1/pgmoon/init.lua:271: in function 'auth' kong_1                |         /usr/local/share/lua/5.1/pgmoon/init.lua:211: in function 'connect' kong_1                |         .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:205: in function 'connect' kong_1                |         .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:492: in function 'query' kong_1                |         .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:273: in function 'init' kong_1                |         /usr/local/share/lua/5.1/kong/db/init.lua:138: in function 'init_connector' kong_1                |         /usr/local/share/lua/5.1/kong/init.lua:388: in function 'init' kong_1                |         init_by_lua:3: in main chunk kong_1                | nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/pgmoon/init.lua:271: missing password, required for connect kong_1                | stack traceback: kong_1                |         [C]: in function 'assert' kong_1                |         /usr/local/share/lua/5.1/pgmoon/init.lua:271: in function 'auth' kong_1                |         /usr/local/share/lua/5.1/pgmoon/init.lua:211: in function 'connect' kong_1                |         .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:205: in function 'connect' kong_1                |         .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:492: in function 'query' kong_1                |         .../share/lua/5.1/kong/db/strategies/postgres/connector.lua:273: in function 'init' kong_1                |         /usr/local/share/lua/5.1/kong/db/init.lua:138: in function 'init_connector' kong_1                |         /usr/local/share/lua/5.1/kong/init.lua:388: in function 'init' kong_1                |         init_by_lua:3: in main chunk

While waiting for Docker to merge / build 2.0.4 you can follow the docker-compose from the 2.0.2 tag https://github.com/Kong/docker-kong/tree/2.0.2/compose

I've triple checked the 2.0.4 image works with the docker secret supplied password per out docker-compose file.


branch-2.0 let arm gcc know some function no return

Proposed changes
Issue Number: close #xxx
https://github.com/apache/doris/pull/28157 couldn't auto merge
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Build plan support for check/test/doc builds

Build plans currently appear to only be obtainable for cargo build, but cargo {check,test,doc} are also of interest to tools.

Should be closed due to #7902


Unit Testing beef up

I have noticed the new ESClient is a bit hard to unit test.  I understand that not all features are in the new 8.x.x versions but it's seeming very difficult to test given the accessibility of things (unless im dumb, which is possible)
var resourcesFromElastic = await elasticSearchClient.Value.SearchAsync<Source>(searchRequest.Value);
if i try to mock the response using the TestableResponseFactory I dont see an easy way to create mock data to return.
   var expectedSearchResponse = new SearchResponse<Source>()     {       HitsMetadata = new HitsMetadata<Source>()       {         Hits = new List<Hit<Source>>() { new(), new() }       }     };
this was the best i got so far, but I'd rather fill it in with data (my Source object) and I cant due to Hit, is there a way to handle this? or is this coming in the future

Agreed, mocking is indeed a bit tricky.
The in-memory connection currently seems to work best for most of my scenarios. Unfortunately it isn't typed, but requires you to write the raw JSON as returned by Elasticsearch:
var response = @"{
    ""hits"": {
        ""hits"": [
            {
                // ...
            }
        ]
    }
}";

var pool = new SingleNodeConnectionPool(new Uri("http://localhost:9200"));
var settings = new ConnectionSettings(pool, new InMemoryConnection(Encoding.UTF8.GetBytes(response)));
var client = new ElasticClient(settings);

var response = await client.SearchAsync(...);

// TODO: Assertions

You can find plenty examples of this pattern in the client tests themselves.

Gotcha I see, i appreciate that.  I dont believe that in memory connection should be the default.

was able to do this so far.  but the amount of hoops is a bit rough.  circular depends in DTOs, read only fields, etc makes it pretty hard.

@RejectKid We are working on some documentation for our recommendations. We have seen examples where users try to test at the wrong abstraction level, often repeating our testing. Generally, we recommend that you abstract our types and then include a thin unit/integration testing layer to ensure the mapping of data from our types to your own. That way, your application code can depend on the types you own and can fully control for testing.
That said, you should be able to mock the search responses as follows:
var expectedSearchResponse = new SearchResponse<MySource>()
{
	HitsMetadata = new HitsMetadata<MySource>()
	{
		Hits = new List<Hit<MySource>>()
		{
			new() { Source = new MySource{ Name= "Name1" } },
			new() { Source = new MySource{ Name= "Name2" } }
		}
	}
};

var mockedSearchResponse = TestableResponseFactory.CreateSuccessfulResponse(expectedSearchResponse, 200);

var mockedClient = Mock.Of<ElasticsearchClient>(e =>
	e.Search<MySource>() == mockedSearchResponse);

var testResponse = mockedClient.Search<MySource>();

Note that this only sets the source value on the hits and none of the metadata, including the total number of hits etc., which can be pretty significant on a search response. As @philipproplesch suggested, for complex responses, it's often better and recommended to capture the JSON example of a response and use the InMemoryConnection since that way, you get an entirely constructed response.

@stevejgordon I created a wrapper to mock certain functionality in ElasticsearchClient like the below.
public class SearchClient : ISearchClient
{
	private readonly ElasticsearchClient _client;

	public SearchClient(ElasticsearchClient client)
	{
		_client = client;
	}

	public Task<SearchResponse<TDocument>> SearchAsync<TDocument>(Action<SearchRequestDescriptor<TDocument>> configureRequest, CancellationToken cancellationToken = default)
	{
		return _client.SearchAsync(configureRequest, cancellationToken);
	}

	public Task<TResponse> RequestAsync<TResponse>(HttpMethod method, string path, PostData data, RequestParameters parameters, CancellationToken token = default)
		where TResponse : TransportResponse, new()
	{
		return _client.Transport.RequestAsync<TResponse>(method, path, data, parameters, token);
	}
}

Unit test
var clientMock = new Mock<ElasticsearchClient>();
var searchClient = new SearchClient(clientMock.Object);

var method = HttpMethod.GET;
var path = "/index/_mapping";
var data = PostData.Serializable(new { });
var parameters = new RequestParametersMock();
var cancellationToken = new CancellationToken();

var response = new RequestResponseMock();
clientMock
	.Setup(x => x.Transport.RequestAsync<RequestResponseMock>(method, path, data, parameters, cancellationToken))
	.ReturnsAsync(response);

var result = await searchClient.RequestAsync<RequestResponseMock>(method, path, data, parameters, cancellationToken);

clientMock.Verify(
	x => x.Transport.RequestAsync<RequestResponseMock>(method, path, data, parameters, cancellationToken),
	Times.Once);

Assert.NotNull(result);

How do you mock properly the Transport?


opening file clears multiple selection in source-control window

Issue Type: Bug
this is a regression in 1.69

open a large git project on a remote machine via SSH
make lots of changes in many large files
open source-control panel
select one file in the source-control panel, then quickly shift-click another file to select a range of files
...
the first file eventually opens (it has to happen in this order, hence ssh & large files. if the first file opens before the shift-click then this does not repro. causing high CPU usage on the remote machine can help to increase the repro window)
the opening of the file causes the multiple-selection in the source-control window to be replaced with a single-file selection of the file that opened.


How to write heavy load to Influxdb?

Hi,
i am new in influxdb and trying to store sensor data in Influxdb with 400-500 Field and 1 Tag and Timestamp given manually with nanosecond accuracy. i try to store 300,000 point for one specific tag with c# client (https://github.com/MikaelGRA/InfluxDB.Client) in 1000 batch set and it take quite lot time to send it from client node. In One database have approximately 20 to 25 series.
configuration: Infludb Node:- 4gb RAM, corei5, HDD(Virtual node, 0.10 version of Influxdb)
Client Node:- 4gb RAM, corei5
i required it for my Master Project , if possible then please provide require hardware for improve performance.

There's a few simple things you can do that will likely speed things up:

Make sure your client is using the line protocol, not JSON, to write points. I couldn't tell which approach the library you mentioned is using, but influxdb-lineprotocol is a .net library that may help.
Prefer a solid state drive over an HDD.
On the server, 4GB of RAM will do okay, but you'll probably see better performance with more RAM.
Experiment with larger batch sizes.
Make sure you're using the TSM engine, not the b1 or bz1 engines that are deprecated and not present in 0.11+.
If possible, use InfluxDB 0.11 (it's in RC status now but the final cut is coming soon) rather than 0.10.

@mark-rushakoff  Thank you very much
i already using TSM engine and also tried with 1500, 2000, 3000 large batch size, but then it become even worse then 1000
i will try  influxdb-lineprotocol  and

Closing this out since it's not an issue that needs to be resolved.


#4562: normalize global operator

normalize global operator : compute global norm for a given rank-4 tensor

Reshape should work on multiple dims. Can you retry and post if there is an issue?

Reshape should work on multiple dims. Can you retry and post if there is an issue?

when was this change made ? curious

I don't recall there ever being an issue with reshape only working on one dim at a time.


change headres, add required files

Thanks for the updates - I believe this branch must now be updated to the latest develop version (there were some new classes added in other merges and there now is a conflict)

Thanks for the updates - I believe this branch must now be updated to the latest develop version (there were some new classes added in other merges and there now is a conflict)

My suggestion is to wait with the merge when we are in the Eclipse repo, the request is already out and it was mentioned that within a week that could be cleared.


Can't install a fresh Sveltepress instance with pnpm due to catalog import

Describe the bug
Same issue as https://github.com/SveltePress/sveltepress/issues/300, but it still exists so I'm opening a new ticket. When installing the latest Sveltepress with pnpm, the install fails with the following message:
ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER  @shikijs/twoslash@catalog: isn't supported by any available resolver.
In #300 it was suggested, that updating theme-default would fix this. However, the bug doesn't seem to originate from @sveltepress/theme-default but from @sveltepress/twoslash. More precisely pnpm doesn't seem to tolerate these catalog: dependencies:
https://github.com/SveltePress/sveltepress/blob/959d7fbd58228adb1f9105b20862bd5c74f5380a/packages/twoslash/package.json#L41-L42
Reproduction
I just tested this with a fresh sveltepress project and I get the same error message:
$ node --version
v22.5.1
$ pnpm --version
9.15.0
$ pnpm create @sveltepress@latest
✔ Project name: … sveltepress-project
✔ Use Javascript or Typescript for your new project? › Typescript

Scaffolding project in /Users/gregor.aisch/projects/test/sveltepress-project...

Done. Now run:

  cd sveltepress-project
  pnpm install
  pnpm run dev

$ cd sveltepress-project
$ pnpm i
 ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER  @shikijs/twoslash@catalog: isn't supported by any available resolver.

This error happened while installing the dependencies of<EMAIL_ADDRESS> at<EMAIL_ADDRESS>
An external package outside of the pnpm workspace declared a dependency using
the catalog protocol. This is likely a bug in that external package. Only
packages within the pnpm workspace may use catalogs. Usages of the catalog
protocol are replaced with real specifiers on 'pnpm publish'.

This is likely a bug in the publishing automation of this package. Consider filing
a bug with the authors of:

<EMAIL_ADDRESS>
Progress: resolved 142, reused 106, downloaded 4, added 0

Logs
No response
Screenshots
No response
Severity
blocking an upgrade

#306


Video looks blurry

in android example video in video room is blurry and foggy i tested on emulator and physical device but on the web there is no problem
is this problem relates to example or client it self?
how can i fix it?
and the video call problem still exist(after accepting call screen turns black) in android example if you guide me i would be glad to help any where in project
thanks 🙏

I think problem is filterQuality.
RTCVideoView(
  remoteStream.videoRenderer,
  // change low or none
  // filterQuality: FilterQuality.high,
  objectFit: RTCVideoViewObjectFit.RTCVideoViewObjectFitCover,
)

Also for what its worth setting up high bitrate increase overall quality of media at the expense of more cpu usage on both janus server and client device,
Therefore closing it for now in case you have other questions feel free to ask on discussions or gitter


Exporting the operator stft to ONNX opset version 9 is not supported

Hi, I have exported your MetricGAN+ model to ONNX (I called SpectralMaskEnhancement class from speechbrain.pretrained). However, I received the error message:
Exporting the operator stft to ONNX opset version 9 is not supported. Please feel free to request support or submit a pull request on PyTorch GitHub.

In addition, I have modified the forward function of the SpectralMaskEnhancement a bit
def forward(self, noisy):
    """Runs enhancement on the noisy input"""
    print("Hello line 2128")
    return self.enhance_batch(noisy, lengths=torch.tensor([1.]))

Many thanks!

Unfortunately torch.stft (used in many places, such a feature computation) is not ONNX exportable.  I'm running into the same problem, but I don't have a solution. It could be great to have this operation supported in ONNX, as many people are asking it.


Postgresql is not coming up. In pending state.

Checks

[X] I have checked for existing issues.
[X] This report is about the User-Community Airflow Helm Chart.

Chart Version
8.9.0
Kubernetes Version
Client Version: v1.29.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.10

Helm Version
version.BuildInfo{Version:"v3.15.1", GitCommit:"e211f2aa62992bd72586b395de50979e31231829", GitTreeState:"clean", GoVersion:"go1.22.3"}

Description
Postgresql pod is not coming up , in pending state with.
Relevant Logs
postgres itself is not coming up-

airflow-postgresql-0                                        0/1      Pending
│ airflow-scheduler-5df8fb6987-vmldv          0/2      Init:CrashLoopBackOff
│ airflow-sync-users-8867fd479-q2db8        0/1      Init:CrashLoopBackOff
│ airflow-triggerer-5786fc4f66-5xfx6             0/1      Init:CrashLoopBackOff
│ airflow-web-68dc78c8bf-zmwn7                  0/1      Init:CrashLoopBackOff

After checking log of  airflow-postgresql-0  : its blank.

After checking describe on airflow-postgresql-0   gettting below:
Events:                                                                                │
│   Type     Reason            Age                 From               Message                                                                                │
│   ----     ------            ----                ----               -------                                                                                │
│   Warning  FailedScheduling  23m                 default-scheduler  running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition                                                                                │
│   Warning  FailedScheduling  3m5s (x2 over 13m)  default-scheduler  running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition                                                                                │
│

Custom Helm Values
## DATABASE | Embedded Postgres
###################################
postgresql:
  ## if the `stable/postgresql` chart is used
  ## - [WARNING] the embedded Postgres is NOT SUITABLE for production deployments of Airflow
  ## - [WARNING] consider using an external database with `externalDatabase.*`
  ## - set to `false` if using `externalDatabase.*`
  ##
  enabled: true

  ## configs for the postgres container image
  ##
  image:
    registry: ghcr.io
    repository: airflow-helm/postgresql-bitnami
    tag: 11.22-patch.0
    pullPolicy: IfNotPresent

  ## the postgres database to use
  ##
  postgresqlDatabase: airflow

  ## the postgres user to create
  ##
  postgresqlUsername: postgres

  ## the postgres user's password
  ##
  postgresqlPassword: airflow

  ## the name of a pre-created secret containing the postgres password
  ##
  existingSecret: ""

  ## the key within `postgresql.existingSecret` containing the password string
  ##
  existingSecretKey: "postgresql-password"

  ## configs for the PVC of postgresql
  ##
  persistence:
    ## if postgres will use Persistent Volume Claims to store data
    ## - [WARNING] if false, data will be LOST as postgres Pods restart
    ##
    enabled: true

    ## the name of the StorageClass used by the PVC
    ##
    storageClass: oci-bv-oi

    ## the access modes of the PVC
    ##
    accessModes:
      - ReadWriteOnce

    ## the size of PVC to request
    ##
    size: 8Gi

@infa-kvaibhav this will almost certainly be an issue with your cluster not provisioning or binding the PersistentVolume correctly to the Pod.
Search around for running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition based on whatever CSI driver you are using.
Also, check the logs of the Pods for your CSI driver.

Because this is unrelated to the chart, I am going to close it, but feel free to provide an update if you figure out what was wrong with your cluster.


Some commands ignored.

Hello. I have setup my custom nadeko using the Windows installer (NadekoInstaller.bat), and some commands like any commands in the music group (http://nadekobot.readthedocs.io/en/latest/Commands List/#music), don't respond.
Better yet the commands are not even reported in the log (onscreen). So, with that I tried upgrading the bot and it did not work, I restarted it, and it's still not working.
The bot has all the necessary permissions to use voice, and it's not even being ran at all.
How can this happen?

You are on 1.3 with NadekoInstaller.bat and your commands lists are here
Upgrade to use the commands listed here

well i did upgrade as mentioned and the command list you posted is the same as the one i posted.

try .stats is it showing 1.4x or 1.3x

yep it is 1.3x

time to upgrade again

latest or stable build?

cool a new installer


add support for suggestions on inspec version in compliance reporting

User Story
We recently exposed the Chef InSpec version used to generate compliance reports on the node details page.
This issue covers the work to add a field to the compliance searchbar for inspec version, so users can easily filter their nodes to see which inspec version they are running.
Definition of Done
Can filter by Chef InSpec Version (let's talk to ux about naming) in the compliance reporting searchbar. This will include backend and a small amount of ui work.

InSpec Version makes the most sense to me. I would say roll with it.

remaining work for this card is to :

support suggestions for inspec version (https://github.com/chef/automate/compare/vj/suggest-inspec-version)
add the option in the ui

i'm having trouble with this branch:  https://github.com/chef/automate/compare/vj/suggest-inspec-version -- that should work but it is not. i'm not sure if that's because of the . in the version numbers?

It looks like this is a problem for all the current search types. If I add reports with the organization field with version numbers like 3.0.2. I see the same problem.
I am looking into why it is like that.

I found the problem we need to add the term 'punctuation' to the mapping here https://github.com/chef/automate/blob/master/components/compliance-service/ingest/ingestic/mappings/comp-rep-date.go#L25.
Without 'punctuation' term the tokenizer will create tokens for each number between the period. Since our version (3.1.0) only has one number between each period no tokens will be created because the minimum token size is two characters.
Below are the tokens for version "3.0.10"
{
  "_index": "comp-3-r-2019.06.21",
  "_type": "_doc",
  "_id": "4b3f975d-d162-4772-a496-cf4c66c07b9d",
  "_version": 1,
  "found": true,
  "took": 1,
  "term_vectors": {
    "version.engram": {
      "field_statistics": {
        "sum_doc_freq": 5,
        "doc_count": 1,
        "sum_ttf": 5
      },
      "terms": {
        "3.": {
          "term_freq": 1,
          "tokens": [
            {
              "position": 0,
              "start_offset": 0,
              "end_offset": 2
            }
          ]
        },
        "3.0": {
          "term_freq": 1,
          "tokens": [
            {
              "position": 1,
              "start_offset": 0,
              "end_offset": 3
            }
          ]
        },
        "3.0.": {
          "term_freq": 1,
          "tokens": [
            {
              "position": 2,
              "start_offset": 0,
              "end_offset": 4
            }
          ]
        },
        "3.0.1": {
          "term_freq": 1,
          "tokens": [
            {
              "position": 3,
              "start_offset": 0,
              "end_offset": 5
            }
          ]
        },
        "3.0.10": {
          "term_freq": 1,
          "tokens": [
            {
              "position": 4,
              "start_offset": 0,
              "end_offset": 6
            }
          ]
        }
      }
    }
  }
}

curl $ELASTICSEARCH_URL/comp-3-r-2019.06.21/_doc/4b3f975d-d162-4772-a496-cf4c66c07b9d/_termvectors?fields=version.engram

i wonder if this is the same issue that we are hitting on https://github.com/chef/automate/issues/633 ?

@vjeffrey I think that is another problem. The version number is a separate field. I will confirm.

Suggestion tokens are currently built with letters and digits. Punctuation is used as a separator for tokens. This works well for name/label-type fields, but for version number fields, suggestion tokens are not created. Below shows the differences between tokens for name fields vs version fields with punctuation added (a user needs to type the full token for the node to be added to the suggestions list).
Name example
"RedHat(2)-beta-nginx(f)-apache(s)-failed"
With punctuation added
"re", "red", "redh", "redha", "redhat", "redhat(", "redhat(2", "redhat(2)", "redhat(2)-", "redhat(2)-b", "redhat(2)-be", "redhat(2)-bet", "redhat(2)-beta", "redhat(2)-beta-", "redhat(2)-beta-n", "redhat(2)-beta-ng", "redhat(2)-beta-ngi", "redhat(2)-beta-ngin", "redhat(2)-beta-nginx"
With only letters and digits
"ap", "apa", "apac", "apach", "apache", "be", "bet", "beta", "fa", "fai", "fail", "faile", "failed", "ng", "ngi", "ngin", "nginx", "re", "red", "redh", "redha", "redhat"
Version example
"3.0.10"
With punctuation added
"3.", "3.0", "3.0.", "3.0.10"
With only letters and digits
no suggestions.
We might want to build tokens in two ways depending on the field type.
For fields that are primarily version numbers, add punctuation, and leave out punctuation for label/name-type fields.

We might want to build tokens in two ways depending on the field type.
For fields that are primarily version numbers, add punctuation, and leave out punctuation for label/name-type fields.

I think this ^^ sounds like the most reasonable approach

will this change require a migration?

@vjeffrey Without a migration of the existing indexes only the reports ingested after this change will have InSpec Version numbers show up in the search bar suggestions.


Research if hooking into response.push instead of response.emit might work as well

It might be slightly more elegant because there is no need to check for the right event

nope that didn't work


Merge pull request #1 from Microsoft/master

Update from original

I'm a bit confused on this PR. It doesn't seem like there is anything for me to do. Is there?


403 Forbidden Error issues with multisite and Polylang Pro

Thanks for the great plugin. We are using WP-Stateless on several multilingual multisite installations with Polylang Pro.
Recently however, we have started to experience some issues with it. Things start to get weird when a third language is installed. Then, upon image upload to the media library, the first two language versions work fine but the image for the third language version is grayed out / missing, and the console displays 403 Forbidden Error for it.

_wp_attachment_metadata is generated to my understanding correctly.
Tried in ephemeral and CDN modes.
WP-Stateless version 3.1.0
Polylang Pro version 2.8.2

Maybe permission issue with a bucket - any ideas where to start digging?

Please, check if those files are set to be publicly accessible in GCS.

Uploaded files are not accessible right away. Only after using the Regenerate and Sync with GCS functionality they get working urls. On upload urls are generated with wrong (main site) domain and accessing them results an 403.
For example:
URL after an initial upload:
https://www.cursor.fi/uploads/sites/9/2020/12/009a1bb6-tree-scaled.jpg - Not accessible (403)
URL after running the Regenerate and Sync with GCS:
https://www.visitkotkahamina.fi/uploads/2020/12/009a1bb6-tree-scaled.jpg - Works fine

Uploaded files are not accessible right away. Only after using the Regenerate and Sync with GCS functionality they get working urls. On upload urls are generated with wrong (main site) domain and accessing them results an 403.
For example:
URL after an initial upload:
https://www.cursor.fi/uploads/sites/9/2020/12/009a1bb6-tree-scaled.jpg - Not accessible (403)
URL after running the Regenerate and Sync with GCS:
https://www.visitkotkahamina.fi/uploads/2020/12/009a1bb6-tree-scaled.jpg - Works fine

I'm experiencing a similar issue that only gets resolved after selecting "Regenerate and Sync with GCS". I'm using WP-Stateless in conjunction with ShortPixel Image Optimizer. WP-Stateless is in Ephemeral mode, the GCS bucket is publicly accessible, and the ShortPixel Image Optimizer option is enabled. I only started experiencing this issue recently, have had no issues with these two plugins for several months.

I'm experiencing a similar issue that only gets resolved after selecting "Regenerate and Sync with GCS". I'm using WP-Stateless in conjunction with ShortPixel Image Optimizer. WP-Stateless is in Ephemeral mode, the GCS bucket is publicly accessible, and the ShortPixel Image Optimizer option is enabled. I only started experiencing this issue recently, have had no issues with these two plugins for several months.

Please, check if those files are set to be publicly accessible in GCS.

I put the URLs above. Is there anything else to check besides this?
Could it be an issue with Polylang? Would it be possible for you to try to replicate the bug to make sure of this?

Please, check if those files are set to be publicly accessible in GCS.

I put the URLs above. Is there anything else to check besides this?
Could it be an issue with Polylang? Would it be possible for you to try to replicate the bug to make sure of this?

If folder is set to multisite settings like /site/x/year/month, this will happen. If however you are running a multisite and set folder structure as single site, the third image path is correct BUT only when uploading from multisite's main site. For all other sites the third image will point to main site's URL and does not work. This can be fixed by regenerating and syncing.


[WIP] Prevent Longhorn upgrade failure due to changed StorageClass when using Helm installation/upgrade

Add the logic to storageclass.yaml template to detect the existing longhorn storageclass. There are 3 cases:

If there is no longhorn storageclass, storageclass.yaml template output a yaml file for longhorn storageclass. Helm install/upgrade will succeed.
If there is a longhorn storageclass with provisoner driver.longhorn.io, storageclass.yaml template outputs an identical storageclass. Helm install/upgrade will succeed.
If there is a longhorn storageclass but its provisoner is not driver.longhorn.io, storageclass.yaml template outputs an error. Helm install will fail. In this case, users have to follow the document to resolve the problem. (In short, users have to delete the existing longhorn storageclass and retry)

longhorn/longhorn#1527

I need to do more testing on this one.


software not detect modelCECH-ZCM2G

topic said i bough beatsaber psvr set. a psmove model CECH-ZCM2G is not detect by softwear after complete a process bar

Same here immediately crashes


Improve local linking doc

Hi all,
I think the documentation about the local linking is not very clear.
It is mentioned that the linking databases extensions and the configuration have to be done only on the proxy, but in this case the /linkaccount command is not available on the backend servers.
Shouldn't floodgate also be installed on these servers?
And if so, what configuration should be applied?

The docs are correct, floodgate only needs to be installed on the proxy for linking to work (and it wont work on the backend).
The /linkaccount command is available on the proxy because thats where you installed floodgate and setup linking.
I feel its clear enough that if you're using a proxy, floodgate on the proxy manages linking. Is there anything else?

Thanks for your answer. If I install floodgate only on the proxy I don't have access to the /linkaccount command in the game. Am I missing something?

Probably a permission :P

I finally got the local linking to work! It was indeed missing permissions, I installed the LuckPerms plugin and allowed the permissions mentioned here. Thanks for your help!


Is this ready for use?

Amazed at the void of browser based solutions for Voice Recognition.  Have high hopes for this plugin...but not sure if it's ready for use or works with iOS.
Thanks

Hi guys, can someone help me? i've spent a lot of time trying to figure out how to make this work on an angular module for an ionic app, any info?

moisesd37, open a new issue for this
but I have no idea about angular

ok jcesar, 1 more question, ¿does it work as continuous speech recognition?

Not right now, at least not the iOS part, you have to call the .start() function every time you want to listen

Hello all,
I'm trying on a nexus 5 with Android version 5.0.2 , but nothing seems to happen .
Someone recently tried to use this plugin ?

What did you try? the basic sample on the readme worked for me on a moto g with android 5.0.2

My index is this:

speech
<script type="text/javascript" charset="utf-8" src="cordova.js"></script>
<script type="text/javascript" charset="utf-8">

document.addEventListener("deviceready", onDeviceReady, false);

function onDeviceReady() {
    alert('ready');
}
</script>

<script type="text/javascript">
var recognition = new SpeechRecognition();
recognition.onresult = function(event) {
  if (event.results.length > 0) {
    q.value = event.results[0][0].transcript;
    q.form.submit();
  }
}

when I click button, speech recognizer not start...what wrong?


Add IndexedDB storage support

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

11 of 382 (2.88%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.9%) to 97.578%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

storages/idb-storage/src/convert.rs
0
25
0.0%

storages/idb-storage/src/lib.rs
1
347
0.29%

Totals

Change from base Build<PHONE_NUMBER>:
-0.9%

Covered Lines:
37904

Relevant Lines:
38845

💛  - Coveralls


Add a progress bar for the solver

Fix #2
Change const int progress_bar_width = 50; for desired progress bar width.

Thanks, I changed the code a little bit, but I like it for the simplicity.


Upgrade dependencies for current Cycle compatibility

Also upgrade tooling dependencies, to avoid:
https://github.com/DefinitelyTyped/DefinitelyTyped/issues/18025

The documentation has various small changes because of tooling update. The tooling update was necessary to avoid the type error described above. In turn this was caused by a non-sem verchange in the types for handlebars, which are used by the doc generation mechanism. I did not include the documentation diff in this PR because it creates links to the repo where it was generated (mine), instead of the correct links here.

Did it myself, because of merge conflicts, but thanks for the PR

Yes, that's one of the challenges of open source. There are a lot of PR's that statistically aren't worth creating, because the odds are that either the merge will be too difficult, or the maintainer just won't have time to consume the PR before it gets made obsolete by something else going in first. In a sense each PR is a bet that the work will pay off by beating the odds and making it first in line to potentially be merged before other work from inside the project or other PR's. You win some, you lose some. :-)


If a user only has one restaurant, redirect to that restaurant

In scheduling.py, the login() method should only send them to /welcome if they are employees of multiple restaurants.
Something like:
restaurant_count = len(set([r.role.restaurant_id for r in user.roles]))

Hey can you assign the issue to me.

@suryasis-hub Sorry, I didn't see your comment until I completed it this morning.


Revert #505, #507, #508

Paired with @fmlharrison on this.
This reverts https://github.com/alphagov/collections/pull/505, https://github.com/alphagov/collections/pull/507, and https://github.com/alphagov/collections/pull/508 which had some problems when it came to deploying. The automatic github revert didn't work so we did it the old school git revert <hash> method.

@tijmenb Child taxons in a content item don't have a 'phase', so the email alerts were being hidden in the accordion on pages like this: https://www.gov.uk/education/funding-and-finance-for-students


Add localhost deployment patch

What type of PR is this?
/kind documentation
What this PR does / why we need it:
This little helper can be used if the operator image has been built
locally on the via podman by running sudo make image. After that, the
patch can be applied to be able to run kubectl apply -f deploy/operator.yaml.
Which issue(s) this PR fixes:

None
Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

/test pull-security-profiles-operator-test-e2e

/test pull-security-profiles-operator-test-e2e

/retest

/lgtm


Update Bevy to 0.11

The only thing I wasn't sure about is with input mocking, .11 adds a window field to input events that I just populated with Entity::PLACEHOLDER when sending events because our test environment doesn't create a window so all the tests would fail trying to get a window.
Todo

[ ] Replace patched bevy_egui with the new version once it's released. See https://github.com/mvlabat/bevy_egui/pull/188
[x] Update RELEASES.md

Yep, placeholder is correct.
Why do we need TypePath now?

Why do we need TypePath now?

This line was complaining without it:
https://github.com/Leafwing-Studios/leafwing-input-manager/blob/dfbe44b22fae01434737fb498dfb10d5ca20057d/src/plugin.rs#L146
If you remove the TypePath requirement from Actionlike, it gives this error:
error[E0277]: the trait bound `A: TypePath` is not satisfied
   --> src\plugin.rs:146:29
    |
146 |         app.register_type::<ActionState<A>>()
    |                             ^^^^^^^^^^^^^^ the trait `TypePath` is not implemented for `A`
    |
note: required for `ActionState<A>` to implement `GetTypeRegistration`
   --> src\action_state.rs:85:80
    |
85  | #[derive(Resource, Component, Clone, Debug, PartialEq, Serialize, Deserialize, Reflect)]
    |                                                                                ^^^^^^^ unsatisfied trait bound introduced in this `derive` macro
86  | pub struct ActionState<A: Actionlike> {
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^
note: required by a bound in `App::register_type`
   --> D:\Packages\.cargo\registry\src\index.crates.io-6f17d22bba15001f\bevy_app-0.11.0\src\app.rs:816:29
    |
816 |     pub fn register_type<T: bevy_reflect::GetTypeRegistration>(&mut self) -> &mut Self {
    |                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ required by this bound in `App::register_type`
    = note: this error originates in the derive macro `Reflect` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider further restricting this bound
    |
82  | impl<A: Actionlike + bevy::reflect::TypePath> Plugin for InputManagerPlugin<A> {
    |                    +++++++++++++++++++++++++

I'm open to suggestions, was just added to get it to compile.

Opened an issue as it seems like it might be an unintentional restriction since it isn't mentioned in migration guides: https://github.com/bevyengine/bevy/issues/9094

Great; doesn't look like something we can work around here.

Once bevy_egui ships I'll merge this and then cut a release. Thanks a ton!

bevy_egui v0.21 is now live: once that's swapped over I'll merge this and cut a release <3

Done, looking good to go on my end!


About Dataset

Hello~ Could you please release the dataset for distillation? It will be nice of you to release the dataset~

Hi, thank you for your interest in our work :)
Unfortunately, we are unable to release the dataset for distillation at this moment. Our work is still in progress, and we are tuning the parameters of our adversarial distillation framework to improve its performance. We appreciate your understanding and hope to share the dataset in the future when it is ready.


Fix non animated gifs

Should fix #274

          1 Warning

:warning:
Any source code changes should have an entry in CHANGELOG.md or have #trivial in their title.

  Generated by :no_entry_sign: Danger


Possible typo in app settings: "Export Station"

In the app's settings, under "Import & Export", there is an "Export Station" option. Based on context, as well as the other settings, I believe the correct phrasing there would be "Export Stations", since the setting's description talks about the "entire collection of radio stations".

Hey!
Thank you for the report!
My main language is German.
I must not have discovered it since the language is set to German. 😃
The typo is fixed.
https://github.com/jamal2362/URL-Radio/commit/59ce1810b6c6032eb3960d64f1c200d3ec7a8386


Won't run at all

Whenever I try to use the koolo.exe it will flash then nothing?

It might happen, maybe a panic, or any other random bug. You can try to check the log.txt (if it has been generated). In case is not generated, you can try to run the koolo.exe from the command line so you will be able to see the crash output and the console will not close after it

goroutine 50 [running]:
github.com/hectorgimenez/koolo/internal/reader/map_client.GetMapData({0xc000220240?, 0xc000454060?}, {0xc0001bb75c?, 0x0?})
E:/projects/koolo/internal/reader/map_client/client.go:19 +0x3ac
github.com/hectorgimenez/koolo/internal/reader.(*GameReader).GetData(_, _)
E:/projects/koolo/internal/reader/reader.go:27 +0xf8
github.com/hectorgimenez/koolo/internal.(*Bot).Run(0xc00060c000, {0xc51970, 0xc0002fa050}, 0x1, {0xc000686000, 0x1, 0x1})
E:/projects/koolo/internal/bot.go:47 +0xc5
github.com/hectorgimenez/koolo/internal.(*SinglePlayerSupervisor).Start(0xc00006c680, {0xc51970, 0xc0002fa050}, {0xc000686000, 0x1, 0x1})
E:/projects/koolo/internal/single_supervisor.go:64 +0x29d
main.main.func2()
E:/projects/koolo/cmd/koolo/main.go:90 +0xab
golang.org/x/sync/errgroup.(*Group).Go.func1()
C:/Users/yast/go/pkg/mod/golang.org/x/sync@v0.2.0/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
C:/Users/yast/go/pkg/mod/golang.org/x/sync@v0.2.0/errgroup/errgroup.go:72 +0xa5

Yeah, there is no error control there, probably should be added some day. Also noticed that I should trimpath the binary... anyway, looks like your D2LoDPath param in config.yaml is not correctly pointing to your D2: LoD 1.13c directory.

Had to redownload another copy of D2Lod so got that all sorted now, thanks
Few other issues,
1, native 1600x1200 resolution monitors, even though the game is set to 1280x720 it seems the mouse is completely out for example its 2 rows under the stash tabs when trying to click.
2. stashing items that aren't in the pickit list, butchers pupil etc etc
3. It got stuck for 5 hours with gloves in its hand in a1 xD
2023-07-19T00:54:47.422+0800	DEBUG	action/item_pickup.go:93	Item Detected: SharkskinGloves [4] at X:22540 Y:9538
2023-07-19T00:54:47.422+0800	DEBUG	step/pickup_item.go:56	Picking up: SharkskinGloves [Magic]
2023-07-19T00:54:48.147+0800	INFO	step/pickup_item.go:45	Item picked up: SharkskinGloves [Magic]
2023-07-19T00:54:48.183+0800	DEBUG	action/item_pickup.go:110	No items detected, waiting a bit and will try again	{"waitMs": 232}
2023-07-19T00:54:48.570+0800	INFO	internal/bot.go:106	Run Andariel finished, length: 44.29s
2023-07-19T00:55:00.026+0800	INFO	internal/supervisor.go:132	Starting Game #108. Run list: Eldritch, Andariel, Pindleskin
2023-07-19T00:55:00.026+0800	DEBUG	internal/bot.go:46	Fetching map data...
2023-07-19T00:55:01.091+0800	DEBUG	internal/bot.go:48	Fetch completed	{"ms": 1065}
2023-07-19T00:55:01.091+0800	INFO	internal/bot.go:54	Running: Eldritch
2023-07-19T00:55:01.135+0800	DEBUG	internal/bot.go:83	Loading screen detected, waiting until loading screen is gone
2023-07-19T00:55:03.381+0800	DEBUG	internal/bot.go:89	Load completed, continuing execution
2023-07-19T00:55:03.381+0800	DEBUG	action/recover_corpse.go:13	Checking for character corpse...
2023-07-19T00:55:03.381+0800	DEBUG	action/recover_corpse.go:38	Character corpse not found :D
2023-07-19T00:55:03.381+0800	DEBUG	action/identify.go:19	Checking for items to identify...
2023-07-19T00:55:03.381+0800	INFO	action/identify.go:25	Identifying 2 items...
2023-07-19T00:55:06.159+0800	DEBUG	action/stash.go:27	Checking for items to stash...
2023-07-19T00:55:06.159+0800	DEBUG	action/stash.go:29	No items to stash...
2023-07-19T00:55:06.159+0800	INFO	action/vendor_refill.go:15	Visiting vendor...
2023-07-19T01:03:20.056+0800	WARN	internal/single_supervisor.go:71	Game finished with errors, reason: max game length reached, try to exit game: 500.02. Game total time: 500.02s
github.com/hectorgimenez/koolo/internal.(*SinglePlayerSupervisor).Start
C:/Users/yast/Desktop/koolo/internal/single_supervisor.go:71
main.main.func2
C:/Users/yast/Desktop/koolo/cmd/koolo/main.go:90
golang.org/x/sync/errgroup.(*Group).Go.func1
C:/Users/yast/go/pkg/mod/golang.org/x/sync@v0.2.0/errgroup/errgroup.go:75

I never tried with that resolution, do you have any kind of screen scale or something? Also, the way this thing is calculating the game area is super hacky and the window borders are hardcoded, so maybe if you are using some kind of custom window theme or accesibility things making the UI bigger/smaller can be part of the problem. Looks like all your problems are related to the resolution.

That was on an alternative computer the 1600x1200 resolution so that isn't the standing still with items in hand issue, 2560x1440 is main resolution.

I have two computers, one is running Windows 11 in 3840x2160 (with hidpi), the other one (VM) is using Windows 10 with the very standard 1920x1080 resolution. I had no problem at all. The thing is that the way the application is getting the game area offset is a bit tricky and the window title bar offset is pretty much hardcoded, so if you are using like a custom windows theme or you have set different window title bar size probably can contribute to this problem. Didn't tried on multi monitor systems also, so if it's your case, I don't know how it will work


Documentation typo : customHeading => customHeadingComponent

Griddle version
v1.3.1
Expected Behavior
When I pass custom component to ColumnDefinition as props in the name of customHeading, the given custom component has to be rendered. This is exactly how the document is explaining at http://griddlegriddle.github.io/Griddle/docs/customization/.
example
<Griddle data={fakeData}>
    <RowDefinition>
      <ColumnDefinition id="name" customComponent={CustomColumn} />>
      <ColumnDefinition id="state" customHeading={CustomHeading}/>
      <ColumnDefinition id="company" />
    </RowDefinition>
  </Griddle>

Actual Behavior
The custom component is not rendered.
So I checked your source code and found out the props name had to be customHeadingComponent. so when I changed it, it works as I expected.
<Griddle data={fakeData}>
    <RowDefinition>
      <ColumnDefinition id="name" customComponent={CustomColumn} />>
      <ColumnDefinition id="state" customHeadingComponent={CustomHeading}/>
      <ColumnDefinition id="company" />
    </RowDefinition>
  </Griddle>

I guess you should update docs.
Steps to reproduce
Pull request with failing test or storybook story with issue
While this step is not necessary, a failing test(s) and/or a storybook story will help us resolve the issue much more easily. Please see the README for more information.

This was fixed in https://github.com/GriddleGriddle/griddle-docs/pull/10, which I imagine will be deployed soon.

Yea - there will be a deploy of docs this weekend (if not sooner). Thanks!


Do optimizations and refactoring using coding principles as requested in my previous pull request

Refactor and optimize various modules in the discmoji project.

discmoji/_http.py

Reuse aiohttp.ClientSession instead of creating a new one for each request.
Refactor ratelimited method to avoid unnecessary async calls.
Optimize _send method to handle JSON decoding more efficiently.

discmoji/bot.py

Refactor connect method to avoid creating a new event loop and instead use the existing one.
Optimize GuildManager class to avoid synchronous calls to asyncio.run.

discmoji/channel.py

Optimize GuildTextChannel class by avoiding synchronous calls to asyncio.run.
Refactor constructor to handle asynchronous requests more efficiently.

discmoji/cli/_cli.py

Refactor __CLI__ class to improve readability and maintainability.
Optimize is_cmd_invoked method to handle command invocation more efficiently.

discmoji/command.py

Optimize Command class by handling errors asynchronously.
Refactor __call__ method to improve error handling.

discmoji/context.py

Optimize Invoked class by avoiding synchronous calls to asyncio.run.
Refactor _construct method to handle asynchronous requests more efficiently.

This pull request includes several changes to improve the asynchronous behavior and code readability of the discmoji library. The most important changes include converting synchronous code to asynchronous, refactoring methods for better readability, and updating type annotations.
Asynchronous Improvements:

discmoji/_http.py: Converted the ratelimited method from asynchronous to synchronous, simplifying its logic and ensuring proper type handling for the Retry-After header.
discmoji/bot.py: Updated the get_guild method to use await for the send_request call, ensuring it operates asynchronously.
discmoji/bot.py: Refactored the connect method to handle heartbeats and reconnections asynchronously, removing the need for a new event loop.
discmoji/context.py: Converted the _construct method to be asynchronous, ensuring that all HTTP requests within it are awaited.
discmoji/context.py: Updated the invoked_cmd_handler method to use await for asyncio.sleep and _construct calls.

Code Readability and Type Annotations:

discmoji/channel.py: Removed asyncio.run from the GuildTextChannel constructor and added an initialize method to handle asynchronous initialization. [1] [2]
discmoji/cli/_cli.py: Renamed the __CLI__ class to CLI, and updated type annotations and method names for better readability.
discmoji/command.py: Made the __call__ method asynchronous and updated error handling to be more robust.

Ok, i'll merge this into the optimization branch, but i'm going to request a review first

Since I see @mojidev-py based his decision on the review, I'm going to merge this...


[1.1.1][github-ci] Enable pyca external tests

This is based on #16252 and will need to be rebased once that is merged.
Tasks

[x] Enable the tests again
[ ] Fix the failure

@mattcaswell I refer to you for fixing pyca tests, any hints or hinsight to share?

The pyca tests had been disabled for a long time (see e.g. https://github.com/openssl/openssl/pull/10723), and then fixed by https://github.com/openssl/openssl/pull/15018. Pretty certain the latter should be backported.

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 61 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 92 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 123 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 154 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 185 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 216 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 247 days ago

Rebased on latest OpenSSL_1_1_1-stable: hopefully tests will now pass and we can review this for merging.

This pull request is ready to merge

Merged to 1.1.1 branch. Thank you.


Add fix for MC-88959.

Note: disabled by default since it can break some very specific update-order-related redstone contraptions.

Thanks! Could you just add a quick sideEffects note to the PatchDef indicating the potential update order issues?


Suggestions for README

Here are a few initial impressions and questions from trying to grok what this project is about based on reading the README.

Where is this project going? Is there a roadmap?
How does this fit with Google's other AI related efforts and tools?
Other tools like this often have a web-based composer. Is something like that planned?
How does this compare to what is available from others in this space (e.g. Microsoft, OpenAI, hugging-face, etc.)?

One more quick thought...  As a dev, I want generally to understand what some helper / tool / API /  abstractions are providing me v. doing things myself. When we introduce AI as the helper things can often be magically simple, but it can be a black box of confusion when things go wrong.
There is maybe a spectrum between (START) I do everything myself and (END) the AI tool does everything magically via some multi-modal input (text and images), e.g. "Hey Google, make an app for my friend to use my smart house for the next hour but don't let them lock me out!"
Obviously that end point doesn't exist... yet, but this project is definitely boosting me from that starting point. It seems like it'd be interesting and helpful for understanding to describe milestones between these points and how the various abstractions and APIs here fit into this and provide off ramps. For example, there's:

the kits here that help abstract over raw LLM APIs
breadboard graphs (node, wiring API)
declarative (JSON) representation of graphs
visual representation of graphs (the mermaid stuff)
interacting with graphs (playground)
visually constructing graphs (future playground?)
ui generation for interacting with graphs (future playground?)
constructing graphs using AI prompts  (future future playground?)

Related: #146.

Folding into #908.


transformer: research inserting helper methods with import or require

cjs vs esm 😡

Helper methods should already inserted as import statements / require depending on source_type. What's missing?

Babel uses numerous conditions to decide on what to insert: https://github.com/babel/babel/blob/54a8389fa31ce4fd18b0335b05832dc1ad3cc21f/packages/babel-helper-module-imports/src/import-injector.ts#L20-L78

There is one failing test case in monitor-oxc due to this confusion:
file:///home/runner/work/monitor-oxc/monitor-oxc/node_modules/.pnpm/@azure+core-rest-pipeline@1.18.0_supports-color@9.4.0/node_modules/@azure/core-rest-pipeline/dist/esm/policies/proxyPolicy.js:2
import { HttpProxyAgent } from "http-proxy-agent";
         ^^^^^^^^^^^^^^
SyntaxError: The requested module 'http-proxy-agent' does not provide an export named 'HttpProxyAgent'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:171:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:254:5)
    at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:482:26)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:117:5)

We inserted the wrong import in one of the files in http-proxy-agent

I'm confused. Our transforms only insert imports from @babel/runtime and react. We didn't insert that import.
It's present in the original source:

https://www.npmjs.com/package/@azure/core-rest-pipeline?activeTab=code

It transformed files in http-proxy-agent, which breaks node.js because it cannot detect esm  anymore.

Actual offending file<EMAIL_ADDRESS>I need to figure out why it's set as a module https://github.com/oxc-project/oxc/blob/6e4805910a474dbaa172d3b268b86191940f4c03/crates/oxc_transformer/src/common/module_imports.rs#L157-L164

I still don't get what's going on in that failing test with http-proxy-agent. So maybe I'm missing the point again, but...
In monitor-oxc, shouldn't we be determining whether a file is ESM or CommonJS by looking for a type field package.json? This code is running in NodeJS, so there should be no ambiguity, and no need to search the code for import / export statements to make a guess.
In the case of http-proxy-agent there is no type field present in package.json, so it should be treated as CommonJS.

I figured it out ...
In monitor-oxc, I set source type to unambiguous https://github.com/oxc-project/monitor-oxc/pull/75 and everything should work correctly.
Except ... it uncovers a parser logic that we need to handle: https://github.com/microsoft/TypeScript/blob/6f75783184328087627da983fe30a05fca4f6314/src/compiler/parser.ts#L1861
I temporarily hacked it by filter out these two error messages:

"The keyword 'await' is reserved" for const foo = await (async () => {})()
``await is only allowed within async functions and at the top levels of modules

I'll add a task to the backlog for fixing the "top level await unambiguous source type problem"


add compatible image format

test with each file format on view
resolve #3

".ico" is not supported now.


[Bug]: Failed to Retrieve Username

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
On the ODH Dashboard I have encountered the following error when attempting to access the dashboard route:
General loading error
Failed to retrieve username: Error getting Oauth Info for user, HTTP request failed

The odh-dashboard pod generated the following error log:
{"level":50,"time":1674232074445,"pid":79,"hostname":"odh-dashboard-7ff4cb9887-vb4t5","msg":"Error retrieving username: Error getting Oauth Info for user, HTTP request failed"}

It appears that my session/cookie may be invalid somehow and instead of redirecting me back to the login screen.  I am unable to access the dashbaord or force it to allow me to reauthenticate.
Expected Behavior
When encountering this error I would expect the dashboard to redirect me to login again.
Steps To Reproduce
I am not 100% sure how to reproduce the issue.
This issue occurred on a 4.10 RHPDS cluster.  My best guess is that it was caused by my logging into the dashboard and creating a session.  Then after the cluster shut down overnight something that was previously cached in a pod somewhere was lost and my cookie became invalid.
I can try and reproduce the issue and report back if I am able to reliably re-create the problem.
Workaround (if any)
I did attempt to restart both of the odh-dashboard pods but that didn't have any effect.
I was able to still access the dashboard by either access the page through another browser or incognito mode or by clearing cookies/cache from browser.
What browsers are you seeing the problem on?
Chrome
Open Data Hub Version
Operator: 1.4.0
Manisfests: v1.4

Anything else
No response

Apologizes for the inconvenience. We have recently debugged the scenario and I think we have a good solution for it. ODH 1.4.1 (should be released soon) should have a fix for this issue.
A solution in the interim is either:

Clear your cache each time it happens (annoying as it likely happens every 24h)
You can apply this change to your Dashboard Deployment. You likely have to turn the Operator pods down to zero so it doesn't try to reset back to the official 1.4.0 Dashboard Deployment setup

A little understanding of the issue if you're curious:
The issue is tied to the two level expiry of tokens. OpenShift Console has an OAuth container and our Dashboard has an OAuth Container dealing with the logged in token. In 1.4.0, the token in OpenShift Console would expire and the Dashboard wouldn't. So when a call goes through the Dashboard OAuth, it didn't see it as invalid. However, when we tried to make a call to the OpenShift Console / K8s backend to get information, it would read as expired. Kick it back to us and our generic error handling code picked it up and shows you the error. Basically, your browser has an expired token that the Dashboard is not properly expiring fast enough for it to avoid the issue.

I'll keep this ticket open until we get a 1.4.1 release for you and you can test out that it is resolved.
cc @LaVLaS

Thanks for the quick response and the details of what is going on!
It is even better to hear you already have a fix in the works :)

@strangiato would you be able to update to ODH 1.4.1 and see if this has improved?

@strangiato when you get a chance to test this out, and you still run into this issue -- we might need to look into it more. Please feel free to reopen this ticket or log a new one to restart this conversation.
I'm going to close this just to keep things organized on our end. I believe this has been fixed as I understand the issue.


WinSetView.hta does not start after updating to Windows 10 21H2 to 22H2 Pro - workaround?

Hello,
Windows 10 22H2 does not start the "WinSetView.hta" on my PC. In my case the message appears:
"This app cannot be run on the PC".
There are no problems with Windows 10 21H2.
Workaround 1:
Start the "Command Prompt" in admin mode and enter the following command:
--> "C:\Windows\system32\mshta.exe" "#PATH#\WinSetView.hta"  ( #PATH# = Path to the file )
Now the program starts correctly.
Workaround 2:
1.) Create a shortcut of the file "WinSetView.hta".
2.) Right click on shortcut: "Properties"; tab: "Shortcut"
3.) At "Target" insert the following before the file path: C:\Windows\System32\mshta.exe
(example: C:\Windows\System32\mshta.exe "#PATH#\WinSetView.hta" )
4) click "OK
5.) Double click on the shortcut to start the program.
With both workarounds the changed settings are applied.
Remark:
When trying to assign the *.hta to "mshta.exe" with "open with", I get the message "The selected program cannot be assigned to the file type. Select another program."

No, I do not use BitDefender. I have also tried with Antivir disabled. Same problem. There is no indication of any blocking events in the scanner log.

Same error reported here with a completely different app. OP fixed issue by applying Microsoft update KB5018427.

Please try updating to the latest Windows 11.  See this issue. Updating to  Windows 11 22H2 Build 22621.674 did the trick.


I need help with contact with Ledger Nano S

I have cloned this project and build it succed,but it can't connect my Ledger device,
Can anyone give me some help?

What do you mean by "can't connect"? Do you have any useful output in your terminal to share? Does the device appear in redux dev tools ?
Also note that the app is still in development, and you will not yet be able to use it for send/receive crypto.

Hi @shoxive , i'm sorry but we are not providing support for now as this app is under heavy development. we are soon going to close the Issues section , it will be opened again when our first MVP gets released.


laue.compute_rmsds y-axis should start at 0

It currently fits both the maximum and minimum RMSD values to the edges of the plot. A minimum of 0 (so that the y-axis is 0-max(RMSD)) would make for easier comparisons.

Additionally, we should an override for the upper limit of the plot in case the user wishes to compare multiple plots with the same range

Adding the option to output a CSV of RMSDs that the user can manipulate themselves should also work fine

Fixed by commits here and here.


JMS: Don't wait forever for listener threads to join

No idea why, but it was reported on the Google Group that threads are stalled there with Oracle AQ.

I will test this on monday! Thanks for now!

I've tested this commit. It works.

@Nonius Thanks for your feedback!


Go to function Definition is not working

Kindly fixe this issue
this feature is most usefull
i love VS Code
i always hard with using visual code but this issue is westing my time
kindly fix it

Please follow the issue reporting guideline: https://github.com/Microsoft/vscode/blob/master/CONTRIBUTING.md#reporting-issues.

Kindly fixe this issue
this feature is most usefull
i love VS Code
i always hard with using visual code but this issue is westing my time
kindly fix it

Please follow the issue reporting guideline: https://github.com/Microsoft/vscode/blob/master/CONTRIBUTING.md#reporting-issues.


Support recommendations on Certification report

On the useCase report example, every dimension has "Areas of strength" and "Opportunities for improvement".  There is currently no way to add this information to a submission.
Proposal 1:
Add two new Questions for each dimension in the survey builder:  Areas of Strength and Opportunities for Improvement".

Add a "None" option for associating the subdimension, so that these questions would be attached directly to the dimension.
Only privileged users (Policy Analyst role?) would be able to answer these questions
The questions could be answered by loading the survey logged in as a Policy Analyst and answering the questions that were not displayed.
The answers to the questions would be read from the submission and displayed in a table below the subdimensions as specified in the useCase report.

Proposal 2:
Create a totally new mechanism to store "recommendations" for each dimension in a submission and provide a UI in the report admin page to update the text.

If possible, add an "inline" text editor to the report where the administrator could directly add Areas of strength and Opportunities for improvement" to the report.
https://www.npmjs.com/package/react-inline-edit-input
If that's not possible, add a button to display a modal for each dimension to add he same information.
Store the resulting text directly in the Submissions collection in something that looks like this:
{   "_id": {       "$oid": "622805b825063b3fc37ed6a4"   },   "lifecycle": [],   "domain": [],   "region": [],   "roles": [],   "userId": {       "$oid": "6227782eb07594c837553e80"   },   "projectName": "Skynet",   "date": {       "$date": "2022-03-09T01:57:25.388Z"   },   "submission": {... },   "completed": true,   "__v": 0,   "recommendations": [{       "dimensionId": 2,       "strengths": "Quarterly model monitoring to be tweaked when deeded (by adding or removing variables)",       "improvements": "Inability to track ethical design choices and considerations post-model launch."   }] }

I think I prefer proposal 2, since it doesn't pollute the survey with information that is only added at the end.

@aaronlugo does this make sense to you?

Done


🐞 elixir: runtime crash when move the deps.get out of the entrypoint in runtime

What is the issue?
I'm trying to move deps.get out of the entrypoint in runtime and got this error:
Error: response from query: input: potato.containerEcho resolve: call function "ContainerEcho": process "mix cmd --cd /src/sdk/elixir/potato/potato mix do deps.get --only dev + dagger.invoke" did not complete successfully: exit code: 1

Stdout:
Resolving Hex dependencies...
Resolution completed in 0.035s
Unchanged:
  jason 1.4.4
  nimble_options 1.1.1
** (ArgumentError) errors were found at the given arguments:

  * 1st argument: not an already existing atom

    :erlang.binary_to_existing_atom("container_echo", :utf8)
    (dagger 0.0.0) lib/dagger/mod.ex:40: Dagger.Mod.invoke/6
    (dagger 0.0.0) lib/dagger/mod.ex:22: Dagger.Mod.invoke/2
    (mix 1.17.2) lib/mix/task.ex:495: anonymous fn/3 in Mix.Task.run_task/5
    (elixir 1.17.2) lib/enum.ex:987: Enum."-each/2-lists^foreach/1-0-"/2
    (mix 1.17.2) lib/mix/task.ex:495: anonymous fn/3 in Mix.Task.run_task/5
    (mix 1.17.2) lib/mix/cli.ex:96: Mix.CLI.run_task/2
    /usr/local/bin/mix:2: (file)
Stderr:
** (exit) 1
    (mix 1.17.2) lib/mix/tasks/cmd.ex:74: Mix.Tasks.Cmd.run/1
    (mix 1.17.2) lib/mix/task.ex:495: anonymous fn/3 in Mix.Task.run_task/5
    (mix 1.17.2) lib/mix/cli.ex:96: Mix.CLI.run_task/2
    /usr/local/bin/mix:2: (file)

Dagger version
0.12.7
Steps to reproduce
No response
Log output
No response

Found that it's because of the cache. Prune it can make this error disappear


Update message for users not eligible to top up

Changed title and added additional information.
Trello: https://trello.com/c/twwy5H0W/383-state-pension-top-up-calculator-and-information

This smart answer has been retired, so closing this Pull Request.


Unable to run the raindrop example on lambda1 node

from Sakib:
Unable to run the raindrop example fully on CSI. Because it was throwing a slightly different error for me than the usual visualization error running outside vnc session.
2024-06-24 17:11:15.838 ERROR [1376] [QSim::UploadComponents@155]  icdf null, snam::ICDF icdf.npy
terminate called after throwing an instance of 'OPTIX_Exception'
  what():  OPTIX_ERROR_INVALID_PTX: Optix call 'optixModuleCreateFromPTX( Ctx::context, &module_compile_options, &pipeline_compile_options, ptx.c_str(), ptx.size(), log, &sizeof_log, &module )' failed: /esi/opticks/CSGOptiX/PIP.cc:284)
Log:
H?sd

./opticks/g4cx/tests/G4CXTest_raindrop.sh: line 169:  1376 Aborted                 (core dumped) $bin
./opticks/g4cx/tests/G4CXTest_raindrop.sh : run error

This is related to issue https://github.com/BNLNPPS/esi-shell/issues/87 when we test the built images on other GPU systems


Fix Json stored as string with cast to any type

Revert "Temp fix: UI bug crashing parsing validation errors"
This reverts commit 8b32d6ddbb318a9c2bb0ca6b9191b032a97b964f.

Rebase, and merged.
Thanks for your contribution !


python312Packages.google-cloud-securitycenter: 1.35.0 -> 1.35.1

Changelog: https://github.com/googleapis/google-cloud-python/blob/google-cloud-securitycenter-v1.35.1/packages/google-cloud-securitycenter/CHANGELOG.md

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
25.05 Release Notes (or backporting 24.11 and 25.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 359395

x86_64-linux

:white_check_mark: 4 packages built:

python311Packages.google-cloud-securitycenter
python311Packages.google-cloud-securitycenter.dist
python312Packages.google-cloud-securitycenter
python312Packages.google-cloud-securitycenter.dist


Inconsistent "rhol_60Fs_mass" values for normal paraffins

(Perhaps this issue should be opened in chemicals... but since I'm using Thermo and you are the maintainer of both Thermo and Chemicals, I'm posting here)
The densities of the normal paraffins seem to be inconsistent. For example n-C30 (=n-triacontane=638-68-6) from thermo shows density=682.91. I have two online sources that claim the density to be 775.0 (link) and 779.7 (link).
Another example is tritriacontane (CAS=630-05-7), which Thermo reports 747.24, but it actually should be around 903.2 (source)
I observed this inconsistency for normal paraffins upto C50 (didn't check beyond that). Thermo gives acceptable density values for some, but some doesn't. The common sense is that the density should increase with increasing carbon number (or molecular weight) but the density reported by Thermo doesn't agree with this.
Example:
from thermo import ChemicalConstantsPackage

n_paraffins = ['n-C6', 'n-C7', 'n-C8', 'n-C9', 'n-C10',
 'n-C11', 'n-C12', 'n-C13', 'n-C14', 'n-C15', 'n-C16', 'n-C17', 'n-C18', 'n-C19', 'n-C20',
 'n-C21', 'n-C22', 'n-C23', 'n-C24', 'n-C25', 'n-C26', 'n-C27', 'n-C28', 'n-C29', 'n-C30',
 'n-C31', 'n-C32', 'n-C33', 'n-C34', 'n-C35', 'n-C36', 'n-C37', 'n-C38', 'n-C39', 'n-C40',
 'n-C41', 'n-C42', 'n-C43', 'n-C44', 'n-C45', 'n-C46', 'n-C47', 'n-C48', 'n-C49', 'n-C50']

constants = ChemicalConstantsPackage.constants_from_IDs(n_paraffins)
for a, b in zip(constants.names, constants.rhol_60Fs_mass):
    print("{0:20}: {1}".format(a, round(b, 3)))

hexane              : 663.383
heptane             : 687.596
octane              : 706.183
nonane              : 721.529
decane              : 733.863
undecane            : 743.692
dodecane            : 752.737
tridecane           : 756.957
tetradecane         : 765.155
pentadecane         : 770.036
hexadecane          : 775.049
heptadecane         : 774.043
octadecane          : 774.123
nonadecane          : 775.741
eicosane            : 771.17
heneicosane         : 796.868
docosane            : 778.837
tricosane           : 799.489
tetracosane         : 802.598
pentacosane         : 793.723
hexacosane          : 800.671
heptacosane         : 765.35
octacosane          : 797.185
nonacosane          : 777.126
triacontane         : 682.918
hentriacontane      : 752.603
dotriacontane       : 834.028
tritriacontane      : 747.243
tetratriacontane    : 744.29
pentatriacontane    : 739.241
hexatriacontane     : 625.765
heptatriacontane    : 735.882
octatriacontane     : 736.663
nonatriacontane     : 737.428
tetracontane        : 840.562
hentetracontane     : 738.813
dotetracontane      : 739.439
tritetracontane     : 740.005
tetratetracontane   : 844.711
pentatetracontane   : 741.159
hexatetracontane    : 741.654
heptatetracontane   : 742.141
octatetracontane    : 742.71
nonatetracontane    : 743.094
pentacontane        : 743.562

Hi Eric,
You are correct - this is an issue, one difficult to remedy today in thermo. Not all methods are available for all chemicals. Methods are based on different data sets, and developed by authors of varying capacities. Modifying your example to show the methods used for each chemical, we can see the HTCOSTALDFIT and MMSNM0 methods are somewhat sub-par and don't display the correct trend in all cases.
I hope a more accurate data source becomes available that can replace those two for these components. I am happy with the issue being in thermo and staying open until it is fixed; the HTCOSTALDFIT and MMSNM0 methods aren't buggy, just under performing.
Sincerely,
Caleb


Forcing ui to dark?

Various "dark" syntax themes cause materia-ui to switch to "light" (when I think it should be dark).
For example, material-ui switches to light when attempting to use any of the following syntax themes:

https://github.com/ssteinker/atom-twilight
https://github.com/cannikin/twilight-syntax
https://atom.io/themes/twilight-syntax-spacegray-eighties
https://atom.io/themes/twilight-syntax-spacegray-ui

What is the mechanism that triggers which light or dark scheme material-ui uses?
Is there an override available to force material-ui into either a light or dark mode, or do the syntax themes need to be updated somehow to be compatible with material-ui?

This is an issue with the syntax themes. They don't expose their syntax-variables. You can take a look at this PR I opened for spacegray-base16-ocean-dark fixing this problem.

Excellent, thanks for your help.

I'm the maintainer of 3 of those 4 themes you listed! I don't use atom at the moment, but if someone wants to open a PR for fixes I'll happily merge.


Use GeoTransform to get resolution for GeoBox?

Related to: opendatacube/datacube-core#752
Currently the resolution inside of the coordinate attributes are used:
https://github.com/opendatacube/datacube-core/blob/05093b75a8f15b643c7047502ae27b662af2d9b4/datacube/utils/xarray_geoextensions.py#L133-L139
GeoTransform is a property used by GDAL to store this information (https://gdal.org/drivers/raster/netcdf.html#georeference)
Here is an example of reading in this property:
https://github.com/corteva/rioxarray/blob/f658d5f829a88204b2ec7b239735aba31694ed0a/rioxarray/rioxarray.py#L540-L545
Thoughts about supporting this as well?

By the way this logic here only works when affine matrix is pure rotation and does not have "shear" component:
https://github.com/corteva/rioxarray/blob/f658d5f829a88204b2ec7b239735aba31694ed0a/rioxarray/rioxarray.py#L75-L76
To deal with shear odc-geo has this:
https://github.com/opendatacube/odc-geo/blob/4f9004720d899dff4bf0b208e4fe602790d055d7/odc/geo/math.py#L339-L360


530 the reset git repo function fails when head is detached

Closes #530 .
This Pull Request addresses the issues described in #530 by doing the following tasks:

When checkout a branch or a commit, use the --force flag of the git checkout command to reset the index and working tree, potentially remove any uncommitted changes. For more information on this flag, see here.
Remove the git_url.reset_git_repo function which create a stash and reset the index and working tree of the target repository before checking out any branch or commit.
Add a warning to the Sphinx documentation for the use case of Analyzing a locally cloned repository about Macaron's ability to reset the index and working tree of the target repository.

@behnazh-w Do you think we should use chore or fix in the squashed commit title of this PR?

@behnazh-w Do you think we should use chore or fix in the squashed commit title of this PR?

chore is good for this PR.


Basic connectivity test fails

I used arduino pro mini 3.3V and CP2102 with DWM1000. The power input given to both pro mini and DWM1000 is 3.3V. Still when I run basic connectivity test, i get this output. Please tell me what can be wrong with my arrangement.
DW1000 initialized ...
Committed configuration ...
Device ID: DECA - model: 255, version: 15, revision: 15
Unique ID: FF:FF:FF:FF:FF:FF:FF:FF
Network ID & Device Address: PAN: FFFF, Short Address: FFFF
Device mode: Data rate: 6800 kb/s, PRF: 16 MHz, Preamble: 128 symbols (code #4), Channel: #5

This was due to improper connection. After making proper connection everything worked out. Now I just want to know how to connect multiple anchors to one tag.

Hi,
Can you let me know what issue was with the connection, as I have same output with a module.

me too

hello karanmakharia  ,
i have having the same issue ,
please by saying connection what u have changed in your connection