Getting 404 Not found error for all HTTP request

Downloaded jar mockserver-netty-5.6.1-jar-with-dependencies.jar
Started mock server using command java -jar   -serverPort 1080
Created one js file and added below code
var mockServerClient = require('mockserver-client').mockServerClient; mockServerClient("localhost", 1080).mockAnyResponse({  "httpRequest": {      "method": "GET",      "path": "/test",      "headers": {          "Accept": ["application/json"],          "Accept-Encoding": ["gzip, deflate, br"]      }  },  "httpResponse": {      "body": "some_response_body"  } }).then(  function () {      console.log("expectation created");  },  function (error) {      console.log(error);  } );

Now When I am testing the request with postman (http://localhost:1080/test), I am always getting 404 Not found error

I am using the docker images and have the same issue since downloading a new version of the container. I used mockserver-5.5.1
jamesdbloom/mockserver                                                                mockserver-5.5.1           sha256:914c035c5d90370979b716c6a955eeea30d9202bc93f40770bf342b991637787   8 months ago        153MB

which worked but the later download of the same image and the newer 5.6.1 image:
jamesdbloom/mockserver                                 mockserver-5.6.1    sha256:6ceacf025ade8461aea00dc41c6d89d6a32c025127140468eaf31cd55944f0e1   08b8a60e6470        5 weeks ago         152MB
jamesdbloom/mockserver                                 mockserver-5.5.1    sha256:50c5208622435c32e8ac1b3cc29f91fb70a87608dd3b8bc9364e1950d55341f9   914c035c5d90        8 months ago        153MB

both don't work anymore.
Getting the logs results in only a log of the creation of the expectation but no active expectation

The problem is that when you submit the curl request you are not passing all the headers that you have required for your expectation to match.  If you look at your log you should see error as follows:
2019-09-20 06:57:19,953 INFO o.m.m.HttpStateHandler request:

	{
	  "method" : "GET",
	  "path" : "/test",
	  "headers" : {
	    "Host" : [ "localhost:1080" ],
	    "User-Agent" : [ "curl/7.54.0" ],
	    "Accept" : [ "*/*" ],
	    "content-length" : [ "0" ]
	  },
	  "keepAlive" : true,
	  "secure" : false
	}

 didn't match expectation:

	{
	  "httpRequest" : {
	    "method" : "GET",
	    "path" : "/test",
	    "headers" : {
	      "Accept" : [ "application/json" ],
	      "Accept-Encoding" : [ "gzip, deflate, br" ]
	    }
	  },
	  "times" : {
	    "unlimited" : true
	  },
	  "timeToLive" : {
	    "unlimited" : true
	  },
	  "httpResponse" : {
	    "headers" : {
	      "Content-Type" : [ "application/json; charset=utf-8" ],
	      "Cache-Control" : [ "no-cache, no-store" ]
	    },
	    "body" : "some_response_body"
	  }
	}

 because:

	method matched,
	path matched,
	query matched,
	body matched,
	headers didn't match,
	cookies matched,
	keep-alive matched,
	ssl matched

If you modify your curl request to add the missing header then you will no longer get a 404 error, as follows:
curl -v http://localhost:1080/test -H "Accept: application/json" -H "Accept-Encoding: gzip, deflate, br"

This can also be seen in the log as follows:
2019-09-20 06:59:54,402 INFO o.m.m.HttpStateHandler request:

	{
	  "method" : "GET",
	  "path" : "/test",
	  "headers" : {
	    "Host" : [ "localhost:1080" ],
	    "User-Agent" : [ "curl/7.54.0" ],
	    "Accept" : [ "application/json" ],
	    "Accept-Encoding" : [ "gzip, deflate, br" ],
	    "content-length" : [ "0" ]
	  },
	  "keepAlive" : true,
	  "secure" : false
	}

 matched expectation:

	{
	  "httpRequest" : {
	    "method" : "GET",
	    "path" : "/test",
	    "headers" : {
	      "Accept" : [ "application/json" ],
	      "Accept-Encoding" : [ "gzip, deflate, br" ]
	    }
	  },
	  "times" : {
	    "unlimited" : true
	  },
	  "timeToLive" : {
	    "unlimited" : true
	  },
	  "httpResponse" : {
	    "headers" : {
	      "Content-Type" : [ "application/json; charset=utf-8" ],
	      "Cache-Control" : [ "no-cache, no-store" ]
	    },
	    "body" : "some_response_body"
	  }
	}

2019-09-20 06:59:54,404 INFO o.m.m.HttpStateHandler returning response:

	{
	  "headers" : {
	    "Content-Type" : [ "application/json; charset=utf-8" ],
	    "Cache-Control" : [ "no-cache, no-store" ]
	  },
	  "body" : "some_response_body"
	}

 for request:

	{
	  "method" : "GET",
	  "path" : "/test",
	  "headers" : {
	    "Host" : [ "localhost:1080" ],
	    "User-Agent" : [ "curl/7.54.0" ],
	    "Accept" : [ "application/json" ],
	    "Accept-Encoding" : [ "gzip, deflate, br" ],
	    "content-length" : [ "0" ]
	  },
	  "keepAlive" : true,
	  "secure" : false
	}

 for action:

	{
	  "headers" : {
	    "Content-Type" : [ "application/json; charset=utf-8" ],
	    "Cache-Control" : [ "no-cache, no-store" ]
	  },
	  "body" : "some_response_body"
	}


[Bug]: panic: runtime error: invalid memory address or nil pointer dereference

Terraform CLI Version
1.5.7
Terraform Provider Version
0.91.0
Terraform Configuration
I have two providers in my code. A standard terrafrom one and a snowflake one. Ive added an extra default_tag to the standard terrafrom provider tags.
When creating a plan i get the following issue.

`panic: runtime error: invalid memory address or nil pointer dereference`

There aren't actually any changes being deployed to snowflake, just tags in associated resources in our cloud :

Category
category:resource
Object type(s)
No response
Expected Behavior
Plan builds
Actual Behavior
Error: Plugin did not respond

The plugin encountered an error, and failed to respond to the
plugin6.(*GRPCProvider).ConfigureProvider call. The plugin logs may contain
more details.

Stack trace from the terraform-provider-snowflake_v0.91.0 plugin:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x140320c]

goroutine 49 [running]:
crypto/rsa.(*PrivateKey).Public(...)
	crypto/rsa/rsa.go:122
github.com/snowflakedb/gosnowflake.prepareJWTToken(0xc00096aa00)
	github.com/snowflakedb/gosnowflake@v1.10.0/auth.go:476 +0x2c
github.com/snowflakedb/gosnowflake.createRequestBody(0xc0008ba240, 0xc000536880?, {{0xc000528159, 0x1c}, {0x206fe36, 0x5}, {0xc000510e08, 0x8}, {0x2082a8c, 0x9}, ...}, ...)
	github.com/snowflakedb/gosnowflake@v1.10.0/auth.go:439 +0x479
github.com/snowflakedb/gosnowflake.authenticate.func1()
	github.com/snowflakedb/gosnowflake@v1.10.0/auth.go:339 +0x65
github.com/snowflakedb/gosnowflake.(*retryHTTP).execute(0xc000a0dce0)
	github.com/snowflakedb/gosnowflake@v1.10.0/retry.go:310 +0x20a
github.com/snowflakedb/gosnowflake.postAuthRestful({0x242ef80?, 0x3417cc0?}, 0x208dfc4?, 0xc0008e8dd0?, 0xc000a0dec8?, 0xc000a0deb0?, 0xc000a0de50?, 0x418688?)
	github.com/snowflakedb/gosnowflake@v1.10.0/restful.go:199 +0xef
github.com/snowflakedb/gosnowflake.postAuth({0x242ef80, 0x3417cc0}, 0xc000926d00, 0x8?, 0xc0008e8dd0, 0xffffffffffffff9c?, 0xc0008a65a0?, 0xc000a0e028?)
	github.com/snowflakedb/gosnowflake@v1.10.0/auth.go:231 +0x372
github.com/snowflakedb/gosnowflake.authenticate({0x242ef80, 0x3417cc0}, 0xc0008ba240, {0x0, 0x0, 0x0}, {0x0, 0x0, 0x0})
	github.com/snowflakedb/gosnowflake@v1.10.0/auth.go:359 +0x11e8
github.com/snowflakedb/gosnowflake.authenticateWithConfig(0xc0008ba240)
	github.com/snowflakedb/gosnowflake@v1.10.0/auth.go:553 +0x33e
github.com/snowflakedb/gosnowflake.SnowflakeDriver.OpenWithConfig({}, {_, _}, {{0xc000528120, 0x7}, {0xc000528100, 0x1e}, {0xc000528100, 0x0}, {0x0, ...}, ...})
	github.com/snowflakedb/gosnowflake@v1.10.0/driver.go:44 +0x165
github.com/snowflakedb/gosnowflake.SnowflakeDriver.Open({}, {0xc000528100, 0xf7})
	github.com/snowflakedb/gosnowflake@v1.10.0/driver.go:27 +0x106
github.com/luna-duclos/instrumentedsql.dsnConnector.Connect(...)
	github.com/luna-duclos/instrumentedsql@v1.1.3/connector.go:53
github.com/luna-duclos/instrumentedsql.wrappedConnector.Connect({{{0x2415e60, 0x218dae0}, {0x2418a00, 0x3417cc0}, 0x0, 0x0}, {0x241e918, 0xc0000bd600}, 0xc000532dc0}, {0x242ef80, ...})
	github.com/luna-duclos/instrumentedsql@v1.1.3/connector.go:33 +0x1ec
database/sql.(*DB).conn(0xc000926a90, {0x242ef80, 0x3417cc0}, 0x1)
	database/sql/sql.go:1387 +0x717
database/sql.(*DB).PingContext.func1(0x60?)
	database/sql/sql.go:850 +0x3a
database/sql.(*DB).retry(0xc00093e960?, 0xc000a0ee40)
	database/sql/sql.go:1538 +0x42
database/sql.(*DB).PingContext(0xc000926a90, {0x242ef80?, 0x3417cc0})
	database/sql/sql.go:849 +0x94
database/sql.(*DB).Ping(...)
	database/sql/sql.go:867
github.com/jmoiron/sqlx.Connect({0x20b10eb?, 0x16?}, {0xc000528100?, 0xc000532d80?})
	github.com/jmoiron/sqlx@v1.3.5/sqlx.go:642 +0x48
github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/sdk.NewClient(0x0?)
	github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/sdk/client.go:151 +0x12f
github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/provider.ConfigureProvider(0x20735ae?)
	github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/provider/provider.go:788 +0x19d2
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Provider).Configure(0xc0007e25a0, {0x242efb8, 0xc000891b00}, 0xc000894280)
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.33.0/helper/schema/provider.go:296 +0x1b8
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ConfigureProvider(0xc0000103d8, {0x242efb8?, 0xc000890d80?}, 0xc0007042d0)
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.33.0/helper/schema/grpc_provider.go:611 +0x3a9
github.com/hashicorp/terraform-plugin-mux/tf5to6server.v5tov6Server.ConfigureProvider({{0x2445c40?, 0xc0000103d8?}}, {0x242efb8?, 0xc000890d80?}, 0xc000704270?)
	github.com/hashicorp/terraform-plugin-mux@v0.15.0/tf5to6server/tf5to6server.go:86 +0x182
github.com/hashicorp/terraform-plugin-mux/tf6muxserver.(*muxServer).ConfigureProvider(0xc000b84000, {0x242efb8?, 0xc000890a80?}, 0xc000890a50?)
	github.com/hashicorp/terraform-plugin-mux@v0.15.0/tf6muxserver/mux_server_ConfigureProvider.go:28 +0x14f
github.com/hashicorp/terraform-plugin-go/tfprotov6/tf6server.(*server).ConfigureProvider(0xc0007e61e0, {0x242efb8?, 0xc000890240?}, 0xc000532300)
	github.com/hashicorp/terraform-plugin-go@v0.22.2/tfprotov6/tf6server/server.go:558 +0x2db
github.com/hashicorp/terraform-plugin-go/tfprotov6/internal/tfplugin6._Provider_ConfigureProvider_Handler({0x1ffb1e0?, 0xc0007e61e0}, {0x242efb8, 0xc000890240}, 0xc0005d4080, 0x0)
	github.com/hashicorp/terraform-plugin-go@v0.22.2/tfprotov6/internal/tfplugin6/tfplugin6_grpc.pb.go:464 +0x169
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0009ae200, {0x242efb8, 0xc0008901b0}, {0x2440e00, 0xc0005c0180}, 0xc0008c2000, 0xc000101ef0, 0x33d3930, 0x0)
	google.golang.org/grpc@v1.63.2/server.go:1369 +0xe23
google.golang.org/grpc.(*Server).handleStream(0xc0009ae200, {0x2440e00, 0xc0005c0180}, 0xc0008c2000)
	google.golang.org/grpc@v1.63.2/server.go:1780 +0x1016
google.golang.org/grpc.(*Server).serveStreams.func2.1()
	google.golang.org/grpc@v1.63.2/server.go:1019 +0x8b
created by google.golang.org/grpc.(*Server).serveStreams.func2 in goroutine 20
	google.golang.org/grpc@v1.63.2/server.go:1030 +0x135

Error: The terraform-provider-snowflake_v0.91.0 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Steps to Reproduce
As Above
How much impact is this issue causing?
High
Logs
No response
Additional Information
No response
Would you like to implement a fix?

[ ] Yeah, I'll take it 😎

The provider is configured like this:
terraform {
  backend "s3" {}

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = "~> 5.48"

    }
    snowflake = {
      source  = "Snowflake-Labs/snowflake"
      version = "0.91.0"
    }
  }
}

provider "aws" {
  profile = var.aws_profile
  region  = var.aws_region
  default_tags {
    tags = local.default_tags
  }
}

if i remove the tag i added to default_tags the plan builds fine. i add a new tag and it doesnt

Hey @RichYoungHaven. Thanks for reaching out to us.
This looks similar to several other reported issues (e.g., https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/2645 and https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/2765). Please check your private key configuration.

It does look similiar @sfc-gh-asawicki but if i remove the tag the plan builds fine. So it seems me adding a map-migrated tag to the provider default tags is the cause of the issue. There is a workaround (put an override_tf in the project with the provider but without that tag) but it would be good if we could identify the underlying cause

@RichYoungHaven but you are adding it to the AWS provider, not to the Snowflake provider, so I don't think this is the issue with our provider.
I don't know how you use it underneath and if you use it to set up the Snowflake provider but as I said, the problem is with the improper private key passed to our provider.

how does the key work without that tag then? Little confused...... shouldn't the key either work or not work?

I don't know what your configuration looks like, and you did not share how the private key is set. But as I said, you are altering other provider's config, so:

you may be using it to set the key in our provider or it messes up your setup for the snowflake provider (can't say not knowing your setup)
something changed externally and it's not connected with the default_tags at all

This is how the key is used (starred out sensitive data):
provider "snowflake" {
  account                = "*****.eu-west-1"              # required if not using profile. Can also be set via SNOWFLAKE_ACCOUNT env var
  user                   = "*****.terraform.transform.dev" # required if not using profile or token. Can also be set via SNOWFLAKE_USER env var
  private_key            = data.aws_ssm_parameter.snowflake_private_key.value
  private_key_passphrase = data.aws_ssm_parameter.snowflake_passphrase.value
  authenticator          = "JWT"
  role                   = "*****_terraform_transform_dev"
}

The key is set with a data source so shouldnt be effected by a provider tag. the only external change is adding the extra tag to the local.default_tags.

Thanks for sharing the config @RichYoungHaven. So what I see here:

data.aws_ssm_parameter.snowflake_private_key.value is not returning the proper private key when you set default_tags on the AWS provider - as I pointed out earlier, this is the behavior of the AWS provider, not ours;
you are setting the provider based on the output of datasource in another provider - AFAIK, this is not the correct setup of the provider in general, please check my answer and referenced links here: https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/2127#issuecomment-1766576750

that cant be the case as there are other tags already being set (starred for privacy):

Not sure it its updating the list of tags that is causing an issue with your provider? The datasource has been working perfectly fine.

Seems like we are going around in circles on this. I tested your approach and as expected it had the same results in that it doesn't work. The data source looks at an exiting resource and always pulls the same value back regardless of the extra tag being there or not. As such i'm leaving it with my override workaround.

@RichYoungHaven, setting the private_key is one of the most commonly used ways to configure our provider. Since there is no crowd commenting that this provider configuration method is broken, this raises the possibility that the configuration is incorrect (it results in the same error as in other issues resulting from the incorrect configuration).
I have linked you the comment referencing the terraform documentation (this one https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/2127#issuecomment-1766576750) which explains why you may encounter problems like this with your current setup. From the Terraform docs on provider configuration:

You can use expressions in the values of these configuration arguments, but can only reference values that are known before the configuration is applied. This means you can safely reference input variables, but not attributes exported by resources (with an exception for resource arguments that are specified directly in the configuration).

Setting both private_key and private_key_passphrase correctly and explicitly (not the datasource returned values) is the widely used method, so maybe you did not set them correctly while checking my suggestion.

Closing due to inactivity.


Add plugin: Leaflet.UTFGrid

Note: this is different than the existing Leaflet.utfgrid plugin already listed on plugins page.

I like the highlighting.
Do you think this should replace the existing utfgrid plugin?

@danzel we created Leaflet.UTFGrid based on Leaflet 1.0, and have been trying to track Leaflet versions with this and other plugins we've created - so other than the feature highlighting, that is probably one of the bigger differences between the two at the moment.
This was inspired quite a bit by Leaflet.utfgrid (thanks for the work there!), but it looks like that plugin hasn't been updated in quite some time?  I haven't checked it for compatibility with Leaflet 1.0; if it is not it might make a case for at least labeling that one with the highest supported version of Leaflet in the plugin registry and README for that plugin.


[BUG] ChatOllama: LLM run errored with error: "llama3 does not support tools"

Describe the bug
When running the flow and providing an animal name as example, no result is generated and logs of flowise provide the following error:
2024-10-15 17:56:26 2024-10-15 15:56:26 [INFO]: [server]: Chatflow a20007d3-7ec1-42ef-a1b7-11abf61e7778_e42bfafa-d579-40ca-92ef-0b56876f87e4 added into ChatflowPool 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/start] [1:chain:LangGraph] Entering Chain run with input: { 2024-10-15 17:56:26   "input": "" 2024-10-15 17:56:26 } 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/start] [1:chain:LangGraph > 2:chain:__start__] Entering Chain run with input: { 2024-10-15 17:56:26   "messages": [ 2024-10-15 17:56:26     { 2024-10-15 17:56:26       "lc": 1, 2024-10-15 17:56:26       "type": "constructor", 2024-10-15 17:56:26       "id": [ 2024-10-15 17:56:26         "langchain_core", 2024-10-15 17:56:26         "messages", 2024-10-15 17:56:26         "HumanMessage" 2024-10-15 17:56:26       ], 2024-10-15 17:56:26       "kwargs": { 2024-10-15 17:56:26         "content": "cat", 2024-10-15 17:56:26         "additional_kwargs": {}, 2024-10-15 17:56:26         "response_metadata": {} 2024-10-15 17:56:26       } 2024-10-15 17:56:26     } 2024-10-15 17:56:26   ] 2024-10-15 17:56:26 } 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/end] [1:chain:LangGraph > 2:chain:__start__] [0ms] Exiting Chain run with output: {} 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/start] [1:chain:LangGraph > 3:chain:supervisor] Entering Chain run with input: { 2024-10-15 17:56:26   "messages": [ 2024-10-15 17:56:26     { 2024-10-15 17:56:26       "lc": 1, 2024-10-15 17:56:26       "type": "constructor", 2024-10-15 17:56:26       "id": [ 2024-10-15 17:56:26         "langchain_core", 2024-10-15 17:56:26         "messages", 2024-10-15 17:56:26         "HumanMessage" 2024-10-15 17:56:26       ], 2024-10-15 17:56:26       "kwargs": { 2024-10-15 17:56:26         "content": "cat", 2024-10-15 17:56:26         "additional_kwargs": {}, 2024-10-15 17:56:26         "response_metadata": {} 2024-10-15 17:56:26       } 2024-10-15 17:56:26     } 2024-10-15 17:56:26   ], 2024-10-15 17:56:26   "next": null, 2024-10-15 17:56:26   "instructions": null, 2024-10-15 17:56:26   "team_members": null 2024-10-15 17:56:26 } 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/start] [1:chain:LangGraph > 3:chain:supervisor > 4:chain:RunnableLambda] Entering Chain run with input: { 2024-10-15 17:56:26   "messages": [ 2024-10-15 17:56:26     { 2024-10-15 17:56:26       "lc": 1, 2024-10-15 17:56:26       "type": "constructor", 2024-10-15 17:56:26       "id": [ 2024-10-15 17:56:26         "langchain_core", 2024-10-15 17:56:26         "messages", 2024-10-15 17:56:26         "HumanMessage" 2024-10-15 17:56:26       ], 2024-10-15 17:56:26       "kwargs": { 2024-10-15 17:56:26         "content": "cat", 2024-10-15 17:56:26         "additional_kwargs": {}, 2024-10-15 17:56:26         "response_metadata": {} 2024-10-15 17:56:26       } 2024-10-15 17:56:26     } 2024-10-15 17:56:26   ], 2024-10-15 17:56:26   "next": null, 2024-10-15 17:56:26   "instructions": null, 2024-10-15 17:56:26   "team_members": null 2024-10-15 17:56:26 } 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/start] [1:chain:LangGraph > 3:chain:supervisor > 4:chain:RunnableLambda > 5:chain:RunnableSequence] Entering Chain run with input: { 2024-10-15 17:56:26   "messages": [ 2024-10-15 17:56:26     { 2024-10-15 17:56:26       "lc": 1, 2024-10-15 17:56:26       "type": "constructor", 2024-10-15 17:56:26       "id": [ 2024-10-15 17:56:26         "langchain_core", 2024-10-15 17:56:26         "messages", 2024-10-15 17:56:26         "HumanMessage" 2024-10-15 17:56:26       ], 2024-10-15 17:56:26       "kwargs": { 2024-10-15 17:56:26         "content": "cat", 2024-10-15 17:56:26         "additional_kwargs": {}, 2024-10-15 17:56:26         "response_metadata": {} 2024-10-15 17:56:26       } 2024-10-15 17:56:26     } 2024-10-15 17:56:26   ], 2024-10-15 17:56:26   "next": null, 2024-10-15 17:56:26   "instructions": null, 2024-10-15 17:56:26   "team_members": null, 2024-10-15 17:56:26   "signal": {} 2024-10-15 17:56:26 } 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/start] [1:chain:LangGraph > 3:chain:supervisor > 4:chain:RunnableLambda > 5:chain:RunnableSequence > 6:prompt:ChatPromptTemplate] Entering Chain run with input: { 2024-10-15 17:56:26   "messages": [ 2024-10-15 17:56:26     { 2024-10-15 17:56:26       "lc": 1, 2024-10-15 17:56:26       "type": "constructor", 2024-10-15 17:56:26       "id": [ 2024-10-15 17:56:26         "langchain_core", 2024-10-15 17:56:26         "messages", 2024-10-15 17:56:26         "HumanMessage" 2024-10-15 17:56:26       ], 2024-10-15 17:56:26       "kwargs": { 2024-10-15 17:56:26         "content": "cat", 2024-10-15 17:56:26         "additional_kwargs": {}, 2024-10-15 17:56:26         "response_metadata": {} 2024-10-15 17:56:26       } 2024-10-15 17:56:26     } 2024-10-15 17:56:26   ], 2024-10-15 17:56:26   "next": null, 2024-10-15 17:56:26   "instructions": null, 2024-10-15 17:56:26   "team_members": null, 2024-10-15 17:56:26   "signal": {} 2024-10-15 17:56:26 } 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/end] [1:chain:LangGraph > 3:chain:supervisor > 4:chain:RunnableLambda > 5:chain:RunnableSequence > 6:prompt:ChatPromptTemplate] [1ms] Exiting Chain run with output: { 2024-10-15 17:56:26   "lc": 1, 2024-10-15 17:56:26   "type": "constructor", 2024-10-15 17:56:26   "id": [ 2024-10-15 17:56:26     "langchain_core", 2024-10-15 17:56:26     "prompt_values", 2024-10-15 17:56:26     "ChatPromptValue" 2024-10-15 17:56:26   ], 2024-10-15 17:56:26   "kwargs": { 2024-10-15 17:56:26     "messages": [ 2024-10-15 17:56:26       { 2024-10-15 17:56:26         "lc": 1, 2024-10-15 17:56:26         "type": "constructor", 2024-10-15 17:56:26         "id": [ 2024-10-15 17:56:26           "langchain_core", 2024-10-15 17:56:26           "messages", 2024-10-15 17:56:26           "SystemMessage" 2024-10-15 17:56:26         ], 2024-10-15 17:56:26         "kwargs": { 2024-10-15 17:56:26           "content": "You are a supervisor tasked with managing a conversation between the following workers: storyauthor, headlineauthor.\nGiven the following user request, respond with the worker to act next.\nEach worker will perform a task and respond with their results and status.\nWhen finished, respond with FINISH.\nSelect strategically to minimize the number of steps taken.\nYou start wit the StoryAuthor and pass the result to the HeadlineAuthor.", 2024-10-15 17:56:26           "additional_kwargs": {}, 2024-10-15 17:56:26           "response_metadata": {} 2024-10-15 17:56:26         } 2024-10-15 17:56:26       }, 2024-10-15 17:56:26       { 2024-10-15 17:56:26         "lc": 1, 2024-10-15 17:56:26         "type": "constructor", 2024-10-15 17:56:26         "id": [ 2024-10-15 17:56:26           "langchain_core", 2024-10-15 17:56:26           "messages", 2024-10-15 17:56:26           "HumanMessage" 2024-10-15 17:56:26         ], 2024-10-15 17:56:26         "kwargs": { 2024-10-15 17:56:26           "content": "cat", 2024-10-15 17:56:26           "additional_kwargs": {}, 2024-10-15 17:56:26           "response_metadata": {} 2024-10-15 17:56:26         } 2024-10-15 17:56:26       }, 2024-10-15 17:56:26       { 2024-10-15 17:56:26         "lc": 1, 2024-10-15 17:56:26         "type": "constructor", 2024-10-15 17:56:26         "id": [ 2024-10-15 17:56:26           "langchain_core", 2024-10-15 17:56:26           "messages", 2024-10-15 17:56:26           "HumanMessage" 2024-10-15 17:56:26         ], 2024-10-15 17:56:26         "kwargs": { 2024-10-15 17:56:26           "content": "Given the conversation above, who should act next? Or should we FINISH? Select one of: FINISH, storyauthor, headlineauthor", 2024-10-15 17:56:26           "additional_kwargs": {}, 2024-10-15 17:56:26           "response_metadata": {} 2024-10-15 17:56:26         } 2024-10-15 17:56:26       } 2024-10-15 17:56:26     ] 2024-10-15 17:56:26   } 2024-10-15 17:56:26 } 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [llm/start] [1:chain:LangGraph > 3:chain:supervisor > 4:chain:RunnableLambda > 5:chain:RunnableSequence > 7:llm:ChatOllama] Entering LLM run with input: { 2024-10-15 17:56:26   "messages": [ 2024-10-15 17:56:26     [ 2024-10-15 17:56:26       { 2024-10-15 17:56:26         "lc": 1, 2024-10-15 17:56:26         "type": "constructor", 2024-10-15 17:56:26         "id": [ 2024-10-15 17:56:26           "langchain_core", 2024-10-15 17:56:26           "messages", 2024-10-15 17:56:26           "SystemMessage" 2024-10-15 17:56:26         ], 2024-10-15 17:56:26         "kwargs": { 2024-10-15 17:56:26           "content": "You are a supervisor tasked with managing a conversation between the following workers: storyauthor, headlineauthor.\nGiven the following user request, respond with the worker to act next.\nEach worker will perform a task and respond with their results and status.\nWhen finished, respond with FINISH.\nSelect strategically to minimize the number of steps taken.\nYou start wit the StoryAuthor and pass the result to the HeadlineAuthor.", 2024-10-15 17:56:26           "additional_kwargs": {}, 2024-10-15 17:56:26           "response_metadata": {} 2024-10-15 17:56:26         } 2024-10-15 17:56:26       }, 2024-10-15 17:56:26       { 2024-10-15 17:56:26         "lc": 1, 2024-10-15 17:56:26         "type": "constructor", 2024-10-15 17:56:26         "id": [ 2024-10-15 17:56:26           "langchain_core", 2024-10-15 17:56:26           "messages", 2024-10-15 17:56:26           "HumanMessage" 2024-10-15 17:56:26         ], 2024-10-15 17:56:26         "kwargs": { 2024-10-15 17:56:26           "content": "cat", 2024-10-15 17:56:26           "additional_kwargs": {}, 2024-10-15 17:56:26           "response_metadata": {} 2024-10-15 17:56:26         } 2024-10-15 17:56:26       }, 2024-10-15 17:56:26       { 2024-10-15 17:56:26         "lc": 1, 2024-10-15 17:56:26         "type": "constructor", 2024-10-15 17:56:26         "id": [ 2024-10-15 17:56:26           "langchain_core", 2024-10-15 17:56:26           "messages", 2024-10-15 17:56:26           "HumanMessage" 2024-10-15 17:56:26         ], 2024-10-15 17:56:26         "kwargs": { 2024-10-15 17:56:26           "content": "Given the conversation above, who should act next? Or should we FINISH? Select one of: FINISH, storyauthor, headlineauthor", 2024-10-15 17:56:26           "additional_kwargs": {}, 2024-10-15 17:56:26           "response_metadata": {} 2024-10-15 17:56:26         } 2024-10-15 17:56:26       } 2024-10-15 17:56:26     ] 2024-10-15 17:56:26   ] 2024-10-15 17:56:26 } 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [llm/error] [1:chain:LangGraph > 3:chain:supervisor > 4:chain:RunnableLambda > 5:chain:RunnableSequence > 7:llm:ChatOllama] [26ms] LLM run errored with error: "llama3 does not support tools\n\nResponseError: llama3 does not support tools\n    at checkOk (/usr/local/lib/node_modules/flowise/node_modules/ollama/dist/shared/ollama.9c897541.cjs:72:9)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async post (/usr/local/lib/node_modules/flowise/node_modules/ollama/dist/shared/ollama.9c897541.cjs:120:3)\n    at async Ollama.processStreamableRequest (/usr/local/lib/node_modules/flowise/node_modules/ollama/dist/shared/ollama.9c897541.cjs:253:22)\n    at async ChatOllama._streamResponseChunks (/usr/local/lib/node_modules/flowise/node_modules/@langchain/ollama/dist/chat_models.cjs:455:32)\n    at async ChatOllama._generate (/usr/local/lib/node_modules/flowise/node_modules/@langchain/ollama/dist/chat_models.cjs:407:26)\n    at async Promise.allSettled (index 0)\n    at async ChatOllama._generateUncached (/usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/language_models/chat_models.cjs:177:29)\n    at async ChatOllama.invoke (/usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/language_models/chat_models.cjs:61:24)\n    at async RunnableSequence.invoke (/usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/runnables/base.cjs:1146:33)\n    at async agentNode (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:608:24)\n    at async RunnableLambda.supervisorNode [as func] (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:582:57)\n    at async /usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/runnables/base.cjs:1513:34" 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/error] [1:chain:LangGraph > 3:chain:supervisor > 4:chain:RunnableLambda > 5:chain:RunnableSequence] [29ms] Chain run errored with error: "llama3 does not support tools\n\nResponseError: llama3 does not support tools\n    at checkOk (/usr/local/lib/node_modules/flowise/node_modules/ollama/dist/shared/ollama.9c897541.cjs:72:9)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async post (/usr/local/lib/node_modules/flowise/node_modules/ollama/dist/shared/ollama.9c897541.cjs:120:3)\n    at async Ollama.processStreamableRequest (/usr/local/lib/node_modules/flowise/node_modules/ollama/dist/shared/ollama.9c897541.cjs:253:22)\n    at async ChatOllama._streamResponseChunks (/usr/local/lib/node_modules/flowise/node_modules/@langchain/ollama/dist/chat_models.cjs:455:32)\n    at async ChatOllama._generate (/usr/local/lib/node_modules/flowise/node_modules/@langchain/ollama/dist/chat_models.cjs:407:26)\n    at async Promise.allSettled (index 0)\n    at async ChatOllama._generateUncached (/usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/language_models/chat_models.cjs:177:29)\n    at async ChatOllama.invoke (/usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/language_models/chat_models.cjs:61:24)\n    at async RunnableSequence.invoke (/usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/runnables/base.cjs:1146:33)\n    at async agentNode (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:608:24)\n    at async RunnableLambda.supervisorNode [as func] (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:582:57)\n    at async /usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/runnables/base.cjs:1513:34" 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/error] [1:chain:LangGraph > 3:chain:supervisor > 4:chain:RunnableLambda] [30ms] Chain run errored with error: "Aborted!\n\nError: Aborted!\n    at agentNode (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:614:15)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async RunnableLambda.supervisorNode [as func] (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:582:57)\n    at async /usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/runnables/base.cjs:1513:34" 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/error] [1:chain:LangGraph > 3:chain:supervisor] [30ms] Chain run errored with error: "Aborted!\n\nError: Aborted!\n    at agentNode (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:614:15)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async RunnableLambda.supervisorNode [as func] (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:582:57)\n    at async /usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/runnables/base.cjs:1513:34" 2024-10-15 17:56:26 2024-10-15 15:56:26 [VERBOSE]: [chain/error] [1:chain:LangGraph] [33ms] Chain run errored with error: "Aborted!\n\nError: Aborted!\n    at agentNode (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:614:15)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async RunnableLambda.supervisorNode [as func] (/usr/local/lib/node_modules/flowise/node_modules/flowise-components/dist/nodes/multiagents/Supervisor/Supervisor.js:582:57)\n    at async /usr/local/lib/node_modules/flowise/node_modules/@langchain/core/dist/runnables/base.cjs:1513:34"
To Reproduce
Steps to reproduce the behavior:
Run the flow providing animal.
Expected behavior
Flow should utlize Ollama as the chat model agent.
Screenshots
If applicable, add screenshots to help explain your problem.
Flow
Have look at the exported flow, there is no magic.
Setup

Installation: Flowise (Port 3000) & Ollama (Port 11434) running inside a Docker container having a shared network.
Flowise Version 2.1.2 & Ollama Version 0.3.13
OS: macOS
Browser: Microsoft Edge

Offer Generator Agents.json

Docker Compose:
`
version: '3.1'
services:
flowise:
image: flowiseai/flowise
restart: always
environment:
- PORT=${PORT}
- CORS_ORIGINS=${CORS_ORIGINS}
- IFRAME_ORIGINS=${IFRAME_ORIGINS}
- FLOWISE_USERNAME=${FLOWISE_USERNAME}
- FLOWISE_PASSWORD=${FLOWISE_PASSWORD}
- FLOWISE_FILE_SIZE_LIMIT=${FLOWISE_FILE_SIZE_LIMIT}
- DEBUG=${DEBUG}
- DATABASE_PATH=${DATABASE_PATH}
- DATABASE_TYPE=${DATABASE_TYPE}
- DATABASE_PORT=${DATABASE_PORT}
- DATABASE_HOST=${DATABASE_HOST}
- DATABASE_NAME=${DATABASE_NAME}
- DATABASE_USER=${DATABASE_USER}
- DATABASE_PASSWORD=${DATABASE_PASSWORD}
- DATABASE_SSL=${DATABASE_SSL}
- DATABASE_SSL_KEY_BASE64=${DATABASE_SSL_KEY_BASE64}
- APIKEY_PATH=${APIKEY_PATH}
- SECRETKEY_PATH=${SECRETKEY_PATH}
- FLOWISE_SECRETKEY_OVERWRITE=${FLOWISE_SECRETKEY_OVERWRITE}
- LOG_LEVEL=${LOG_LEVEL}
- LOG_PATH=${LOG_PATH}
- BLOB_STORAGE_PATH=${BLOB_STORAGE_PATH}
- DISABLE_FLOWISE_TELEMETRY=${DISABLE_FLOWISE_TELEMETRY}
- MODEL_LIST_CONFIG_JSON=${MODEL_LIST_CONFIG_JSON}
ports:
- '${PORT}:${PORT}'
networks:
- app-network
volumes:
- ~/.flowise:/root/.flowise
entrypoint: /bin/sh -c "sleep 3; flowise start"
ollama:
image: ollama/ollama
environment:
- OLLAMA_DEBUG=1
ports:
- "${OLLAMA_PORT}:${OLLAMA_PORT}"
networks:
- app-network
volumes:
- ~/.ollama:/root/.ollama
restart: always
networks:
app-network:
driver: bridge
`

llama 3 does not support tools - as mentioned its not able to run multi agents, because under the hood there are tools involved. So you will have to use llama 3.2 https://ollama.com/library/llama3.2

Many thanks for clarification.
Llama 3.2 works!


ddev composer --version fails because there is no command

Is there an existing issue for this?

[X] I have searched the existing issues

Run a Diagnostic and Paste Link Here
I am unable to provide pastebins or gists as they are blocked by our corporate network.
Current Behavior
ddev composer --version
Error: unknown flag: --version
Usage:
  ddev composer [command] [flags]
  ddev composer [command]

Examples:
ddev composer install
ddev composer require <package>
ddev composer outdated --minor-only
ddev composer create drupal/recommended-project

Available Commands:
  create         Executes 'composer create-project' within the web container with the arguments and flags provided
  create-project

Flags:
  -h, --help   help for composer

Global Flags:
  -j, --json-output   If true, user-oriented output will be in JSON format.

Use "ddev composer [command] --help" for more information about a command.

Expected Behavior
The same thing that happens when I run ddev exec composer --version
ddev composer --version
Composer version 2.3.10 2022-07-13 15:48:23

Steps To Reproduce
No response
Anything else?
No response

Yeah, the ddev composer command doesn't have a --version flag, so that's what's going on. I thought maybe @gilbertsoft 's recent PR https://github.com/drud/ddev/pull/4033 would have fixed this though.
But you can easily do:
ddev composer -- --version
ddev exec composer --version
ddev . composer --version

@gilbertsoft possibly we should do the same thing for composer cmd?

I hope that's working out for you. No response from OP so closing, happy to continue the conversation here or elsewhere.

This is still a bug on 1.20:
ddev composer --version
Error: unknown flag: --version
Usage:
  ddev composer [command] [flags]
  ddev composer [command]

It hasn't been addressed, because you have ddev composer -- --version and ddev exec composer --version and ddev . composer --version and because you sadly didn't even respond here. If there's some reason that you can't use the existing techniques, please speak up.

Ah, the alternatives work, it's just odd that this one doesn't, but I'm fine with it being as designed.

Mostly I was responding to the statement of "I thought maybe @gilbertsoft 's recent PR https://github.com/drud/ddev/pull/4033 would have fixed this though."

I keep getting tripped up by this with other things like ddev drush generate --help too. I wonder if we could work on making this work without needing a command argument for all these shortcut commands.

Want to try to fix it? You may be able to just do what https://github.com/drud/ddev/pull/4033 did, but in https://github.com/drud/ddev/blob/master/cmd/ddev/cmd/composer.go
You don't even have to have a dev environment to try, you can just use gitpod. https://ddev.readthedocs.io/en/latest/developers/building-contributing/


Can you share a demo please?

I built the jar package, but won't use it.
Can you share a demo please?
Thank ou very much.

Hello, I've updated the README file with more information on how to use jnr-winfsp with your (Maven) project.
Please take a look at the implementation of our MemFS in order to get started.
Note that you need to be familiarized with how WinFSP works in order to understand which file system callbacks to implement.
Feel free to ask any additional questions you might have.


voting amount displayed on the bar is different from the actual voted amount.

Expected behavior

The value amount displayed on the voting bar is incorrect.
It should be multiplied by feed price of STEEM.
Actual behavior

The value amount on the voting bar is incorrect.
How to reproduce

You can try to vote any post on busy.org

Browser: Crome
Operating system:  Windows 7

It has been fixed and should work on staging.busy.org
Can you try there?

I think there is a bug again.
The displayed value is too large for this version. Please check it.
100% VP shows $11,791.93.
Right now, I have 18,625SP and 80.94% VP.

staging.busy.org shows too big number. This is also incorrect.
Regards.
Jin Ho Jung
From: Wiktor Tkaczyński<EMAIL_ADDRESS>Sent: Friday, December 29, 2017 5:37 PM
To: busyorg/busy
Cc: multiwhs; Author
Subject: Re: [busyorg/busy] voting amount displayed on the bar is different from the actual voted amount. (#1281)
It has been fixed and should work on staging.busy.org
Can you try there?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/busyorg/busy/issues/1281#issuecomment-354415969 , or mute the thread https://github.com/notifications/unsubscribe-auth/Aa8kVY2uxq2KxTifLP_HvNKBGZ6UKR9Rks5tFKSngaJpZM4RO8QH .보낸 사람이 제거한 이미지입니다.

You mean this value is incorrect?

There is some difference with correct amount. I posted on steemit.com
We can communicate on the following post;
https://steemit.com/utopian/@tradingideas/bug-hunting-problems-with-estimated-voting-amount-1281
Thanks your your hard work...


About animation_lock and application_delay, is there any refer for these values?

As the title

Animation locks are generally assume if casted spells, or gotten from the Balance, I believe.
Application delays are here: https://docs.google.com/spreadsheets/d/1Emevsz5_oJdmkXy23hZQUXimirZQaoo5BejSzL3hZ9I/edit?gid=1868377879#gid=1868377879

Thanks, it definetly helps

No problem!


nuclei: 2.4.0 -> 2.4.1

Motivation for this change
Update to latest upstream release 2.4.1
Change log: https://github.com/projectdiscovery/nuclei/releases/tag/v2.4.1
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

nuclei


Removing Dragonfire

How can i remove dragonfire from my laptop?

@Shrinidhi1928 sudo apt-get remove dragonfire will easily remove Dragonfire from your system.

Thanks @mertyildiran


demo code not working

Hello
Nothing happens when I run the "sst_detect.py" code under the "demo" folder.
I am using python 3.7 on Windows 10.
regards,

@soso-maitha
Thank you for your comment!
Could you show me the execution command and the error message you got?


Upgrade terraform-provider-aws to v4.30.0

Fixes #2130
Fixes: #2125

Blocked by https://github.com/pulumi/pulumi-aws/issues/2138


 myIsolates .(2 ) FUTURE ERROR: 86: COMMUNICATIONS FAILURE 1119  ERR_CLOSED : Socket Closed while receiving

Any idea what might be causing this?
FUTURE ERROR: 86: COMMUNICATIONS FAILURE 1119  ERR_CLOSED : Socket Closed while receiving: iEvaluate[13] (,⍕(⍕rc),': ',(0⊃res),{(⍵∨.≠' ')/': ',⍵}1⊃res,'' '')iSpace.qsignal rc
runTests←{
⍺←0
⎕THIS.myIsolates←⍺{
~⍺:0
ok←⎕CY'isolate'
{isolate.New''}¨⍳4
}''
}
 myIsolates .(2 )

FUTURE ERROR: 86: COMMUNICATIONS FAILURE 1119  ERR_CLOSED : Socket Closed while receiving: iEvaluate[13] (,⍕(⍕rc),': ',(0⊃res),{(⍵∨.≠' ')/': ',⍵}1⊃res,'' '')iSpace.qsignal rc
myIsolates.(2)

I think this is #31, which is fixed in v19.0 and will be patched in older versions.


Hassio component missing after upgrade to 0.90.0b4

Today I installed a fresh instance of hassio (v. 2.10) on my pi 3B+. It then pulled HA 0.89.2 automatically.
I immediately updated to 0.90.0b4 without changing any config files.
After the upgrade the hassio: component was completely missing from the configuration.yaml file.
The /hassio/dashboard resulted in a 404 error.
@OttoWinter confirmed this issue:
https://ptb.discordapp.com/channels/330944238910963714/427516175237382144/556896802088157224
The only way to fix this, was to plug the sd card into a linux PC and manually re-add the hassio component.

I'm wondering if this could this have something to do with default_config:.

Would this default_config change remove an already existing discovery: ?
https://github.com/home-assistant/home-assistant/commit/95da6d41f9fe7f2c5d5d30783ba69bf52b75b80c#diff-579ab6a404463a7992f2626b9139dac2
hassio: is not the default on a fresh install. You would have to enter it manually (or restore from snapshot) and then have it removed...

Fixing it in latest beta, loading Hass.io component will no longer rely on discovery being present.


Brisa api method POST can't use json body

Describe the bug
Api POST can't use body. Brisa breaks.
To Reproduce
https://github.com/AlbertSabate/brisa-debug
Expected behavior
Should do the flow as expected. request send body -> server get body -> read & parse body -> return data -> client gets data.

I think it is 2 things:

The API Routes are thought to be called from the client (web-component). Being already in the server (in a server action), the problem I believe that when doing fetch you have to use the absolute route, not relative.  In this case, you have to use fetch(new URL('/api', request.url).href instead of fetch('/api').

Yes, there is a bug I guess related to Server Actions that you do a .json() without doing .clone() somewhere. I am going to investigate about this.

About the point 1
Instead of using the request.url it would be ideal to use the server address and port to ensure that it always travels internally without going out to the internet. I will expose a Server API that returns this information so it will be possible to do this:
import { getServer } from 'brisa/server';

// ...
const server = getServer();
/*
DebugHTTPServer {
  address: {
    address: "::",
    family: "IPv6",
    port: 63621,
  },
  development: true,
  fetch: [Function: fetch],
  hostname: "localhost",
  id: "",
  pendingRequests: 3,
  pendingWebSockets: 1,
  port: 63621,
  protocol: "http",
  publish: [Function: publish],
  ref: [Function: ref],
  reload: [Function: reload],
  requestIP: [Function: requestIP],
  stop: [Function: stop],
  subscriberCount: [Function: subscriberCount],
  timeout: [Function: timeout],
  unref: [Function: unref],
  upgrade: [Function: upgrade],
  url: URL {
    href: "http://localhost:63621/",
    origin: "http://localhost:63621",
    protocol: "http:",
    username: "",
    password: "",
    host: "localhost:63621",
    hostname: "localhost",
    port: "63621",
    pathname: "/",
    hash: "",
    search: "",
    searchParams: URLSearchParams {},
    toJSON: [Function: toJSON],
    toString: [Function: toString],
  },
  [Symbol(Symbol.dispose)]: [Function: dispose],
  */

@AlbertSabate what do you thing about this new API? It would be super simple to support it, and it can provide value to ensure internal travel without going through internet.
fetch(new URL('/api', getServer().url).href

Sorry, doing the reproduction I missed to add the fix for this. For point 1. How I solved it's like this:
const response = await fetch(`${new URL(finalURL).origin}/api`, {});

But won't hurt to have that object now that you mention...

Sorry, doing the reproduction I missed to add the fix for this. For point 1. How I solved it's like this:
const response = await fetch(`${new URL(finalURL).origin}/api`, {});

But won't hurt to have that object now that you mention... Maybe it's nicer to have getServer() instead of this finalURL string.

The problem of finalURL comes when you have a domain, so this finalURL is the domain that goes outside, to the internet to fetch, when you are already on the server.

Okay, I got what you mean now. Yeah it makes a lot of sense not to have to check the dns to get your domain ip, go to internet provider server and then come back to the server from the outside world once you are in the server already, did you know how many apps on the internet does this? 😮💨 Very good optimisation.

In the next Brisa version you can use fetch(new URL('/api', getServer().url).href) to fetch using the private URL of the server without outside

@AlbertSabate About the crash when doing .json(), it is to the response, because it does not go directly to the endpoint, it returns 404.

I'm going to check why it returns 404. I understand that once you enter the endpoint should work well the request.json() in the same way that works if you make the request from the browser.

@AlbertSabate is related to the "home" of /api. Adding /api/foo.ts and fetching to /api/foo works:

Naturally it is not correct. I will fix it.

@AlbertSabate I found the root of the problem:
https://github.com/brisa-build/brisa/blob/e492eb460b20a1208a501013038f0ea6e6e421a5/packages/brisa/src/cli/serve/serve-options.tsx#L251
This is working for all the entrypoints inside /api except the "home". I'm going to fix this

@AlbertSabate solve in 0.1.3-canary.2


Shader type usage consistency

Notice some inconsistent uses of types in many shaders, better to correct them for consistency.
Mixing unsigned int and uint
GLSL standard only defines uint as the valid type for unsigned integer, better to avoid unsigned int.
https://github.com/stephen-hqxu/superterrainplus/blob/8954eda5f00de90723ca87a1a23551ff180c5f56/SuperTerrain%2B/ModuleInterface/SuperRealism%2B/Shader/STPHeightfieldTerrain.frag#L32
Use of ^^^ unsigned int and vvv uint in the same file.
https://github.com/stephen-hqxu/superterrainplus/blob/8954eda5f00de90723ca87a1a23551ff180c5f56/SuperTerrain%2B/ModuleInterface/SuperRealism%2B/Shader/STPHeightfieldTerrain.frag#L175
Mixing float and int for textureLod function
textureLod function takes a float in the last argument.
https://github.com/stephen-hqxu/superterrainplus/blob/8954eda5f00de90723ca87a1a23551ff180c5f56/SuperTerrain%2B/ModuleInterface/SuperRealism%2B/Shader/STPBidirectionalScattering.frag#L38
^^^ Passing lod parameter as float and vvv as int.
https://github.com/stephen-hqxu/superterrainplus/blob/8954eda5f00de90723ca87a1a23551ff180c5f56/SuperTerrain%2B/ModuleInterface/SuperRealism%2B/Shader/STPAmbientOcclusion.frag#L48-L50

There are also style inconsistency for layout qualifier:
https://github.com/stephen-hqxu/superterrainplus/blob/3836fc2c8a7bc77c4f3b026a0aadb8901f7298d4/SuperTerrain%2B/ModuleInterface/SuperRealism%2B/Shader/STPDeferredShading.frag#L104
^^^ Without space between layout and (...) vvv with space.
https://github.com/stephen-hqxu/superterrainplus/blob/3836fc2c8a7bc77c4f3b026a0aadb8901f7298d4/SuperTerrain%2B/ModuleInterface/SuperRealism%2B/Shader/STPHeightfieldTerrain.frag#L86


[BEAM-11230] Fix a bug with decoding repeated fields

A user reported problem with decoding repeated, non-record BigQuery fields (see jira ticket's description).
Now all cases (repeatable, record; repeatable, non-record; non-repeatable, record; non-repeatable, non-record) should be supported by the coder.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @pabloem Would you like to take a look at this?

Run Python 3.8 PostCommit

do you know if this failure may be related? https://ci-beam.apache.org/job/beam_PostCommit_Python38_PR/170/testReport/apache_beam.examples.complete.game.hourly_team_score_it_test/HourlyTeamScoreIT/test_hourly_team_score_it/

LGTM
Feel free to merge if you get a green run and you're sure the failure is unrelated

do you know if this failure may be related? https://ci-beam.apache.org/job/beam_PostCommit_Python38_PR/170/testReport/apache_beam.examples.complete.game.hourly_team_score_it_test/HourlyTeamScoreIT/test_hourly_team_score_it/

Most likely it's not, it seems the cron version of Python PostCommit has the same problem since December 12th: https://ci-beam.apache.org/job/beam_PostCommit_Python38/635/. The same problem affects PostCommit 3.6 and 3.7 too.

Feel free to merge if you get a green run and you're sure the failure is unrelated

I'm going to merge it then. Thanks for your review!


Support for veeam using vCenter annotations

Enhancement Request
Description
Apparently veeam uses vCenter annotations to know which VMs to backup.
Use case
Being able to mark VMs for veeam backup within OpenNebula.
Interface Changes
Annotations section in the VM Template displayed in Sunstone
Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Just a point, Veeam uses vCenter annotations to show info, like the job name, date, backup folder..., about the last backup done, not to know if the VMs need to backup.

addressed in #4662 3912


Doc (website) has no meta title/desc

That's pretty weird.

This only happens on homepage.
May be add a title to https://github.com/MoOx/statinamic/blob/master/docs/content/index.md


Add new event banner system

Changes

Added new event banner system to docs.
Preview

Related PRs in the other repos
Next
Blog

@ptgott event.json file is not updating due to Vercel build failing. This causes for event not to show.

Hi @ptgott,
There were issues with the environment variables but that is fixed now. Looks like the banner is showing up properly now.

@valzuxx @PietiKinnunen , I know we've made a few changes to the banner. Can you PTAL at this PR


stockfish installation

Hi @calyri,
I followed the stockfish installation instruction to install. I can successfully make the src file. Then, I set the env val export STOCKFISH_EXECUTABLE="/home/jimmy/Downloads/stockfish-10-linux/src".
However, when I run the stockfish bot, I have the following bugs.
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/site-packages/reconchess/scripts/rc_bot_match.py", line 22, in main
    winner_color, win_reason, history = play_local_game(white_player_cls(), black_player_cls(), game=game)
  File "/home/jimmy/Downloads/reconchess/reconchess/bots/my_bot.py", line 33, in __init__
    self.engine = chess.engine.SimpleEngine.popen_uci(stockfish_path)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/site-packages/chess/engine.py", line 2409, in popen_uci
    return cls.popen(UciProtocol, command, timeout=timeout, debug=debug, setpgrp=setpgrp, **popen_args)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/site-packages/chess/engine.py", line 2401, in popen
    return run_in_background(background, debug=debug)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/site-packages/chess/engine.py", line 185, in run_in_background
    return future.result()
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/concurrent/futures/_base.py", line 384, in __get_result
    raise self._exception
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/site-packages/chess/engine.py", line 164, in background
    loop.run_until_complete(coroutine(future))
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/asyncio/base_events.py", line 484, in run_until_complete
    return future.result()
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/site-packages/chess/engine.py", line 2390, in background
    transport, protocol = await Protocol.popen(command, setpgrp=setpgrp, **popen_args)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/site-packages/chess/engine.py", line 894, in popen
    return await loop.subprocess_exec(cls, *command, **popen_args)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/asyncio/base_events.py", line 1211, in subprocess_exec
    bufsize, **kwargs)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/asyncio/unix_events.py", line 200, in _make_subprocess_transport
    **kwargs)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/asyncio/base_subprocess.py", line 39, in __init__
    stderr=stderr, bufsize=bufsize, **kwargs)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/asyncio/unix_events.py", line 706, in _start
    universal_newlines=False, bufsize=bufsize, **kwargs)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/subprocess.py", line 729, in __init__
    restore_signals, start_new_session)
  File "/home/jimmy/anaconda3/envs/reconchess/lib/python3.6/subprocess.py", line 1364, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: '/home/jimmy/Downloads/stockfish-10-linux/src'

So, could you please tell me what is the right way to install the stockfish engine?

@JiahaoYao The stockfish executable environment variable has to point to the actual executable, not the directory that has it.  Try updating your variable accordingly and let me know if this works.

@calyri acutally, this is the point I am confused about here. Could you tell me which should be executable directory?
.
├── AUTHORS
├── Copying.txt
├── Linux
│   ├── stockfish_10_x64
│   ├── stockfish_10_x64_bmi2
│   └── stockfish_10_x64_modern
├── Readme.md
├── Top\ CPU\ Contributors.txt
├── appveyor.yml
├── src
│   ├── Makefile
│   ├── benchmark.cpp
│   ├── bitbase.cpp
│   ├── bitboard.cpp
│   ├── bitboard.h
│   ├── endgame.cpp
│   ├── endgame.h
│   ├── evaluate.cpp
│   ├── evaluate.h
│   ├── main.cpp
│   ├── material.cpp
│   ├── material.h
│   ├── misc.cpp
│   ├── misc.h
│   ├── movegen.cpp
│   ├── movegen.h
│   ├── movepick.cpp
│   ├── movepick.h
│   ├── pawns.cpp
│   ├── pawns.h
│   ├── position.cpp
│   ├── position.h
│   ├── psqt.cpp
│   ├── search.cpp
│   ├── search.h
│   ├── syzygy
│   │   ├── tbprobe.cpp
│   │   └── tbprobe.h
│   ├── thread.cpp
│   ├── thread.h
│   ├── thread_win32.h
│   ├── timeman.cpp
│   ├── timeman.h
│   ├── tt.cpp
│   ├── tt.h
│   ├── types.h
│   ├── uci.cpp
│   ├── uci.h
│   └── ucioption.cpp
└── tests
    ├── instrumented.sh
    ├── perft.sh
    ├── reprosearch.sh
    └── signature.sh

Thank you so much!

If I understand your directories, then your environment variable should be set as:
export STOCKFISH_EXECUTABLE="/home/jimmy/Downloads/stockfish-10-linux/Linux/stockfish_10_x64
so that it points to the actual executable for your platform under the Linux folder.

Thank @calyri !


Add connection configuration

I am currently working in a project which would like to configure a aws managed airflow instance with terraform. Unfortunately that's not possible through AWS API at all so I thought this solution would be neat.
One thing we desperately need would be the ability to configure connections.
I would also offer to implement it. Would this be in the interest of this project?
According to the airflow api documentation, it doesn't look to hard to implement? https://airflow.apache.org/docs/apache-airflow/stable/stable-rest-api-ref.html#tag/Connection

Yes, it should be pretty straight to implement this. Let me know if you need any help with it :)

I have sad news... I really looked forward on implementing this but as we are using the AWS managed airflow it is quite problematic authorization wise to reach the airflow api and it turned out that configuring the AWS Managed Airflow Ressource to use the AWS Secrets Backend turns out to be the easier solution.
Sorry for maybe raising hopes on implementing new features. Maybe we can use the airflow api in the future as aws managed airflow further develops. Thanks for the fast response!


Enable gradle type-safe project accessors and replace all occurrences

Closes #638

CLA has been signed

I saw this project include some dependencies in the convention plugin. Do we need to change it?
https://github.com/android/nowinandroid/blob/main/build-logic/convention/src/main/kotlin/AndroidFeatureConventionPlugin.kt#L46

I saw this project include some dependencies in the convention plugin. Do we need to change it?
https://github.com/android/nowinandroid/blob/main/build-logic/convention/src/main/kotlin/AndroidFeatureConventionPlugin.kt#L46

Only works in build.gradle.kts file for me

@zsmb13 this looks good to me, is it good to merge?

I don't have strong feelings on this, it's quiet nice but it is still an incubating Gradle feature. Perhaps @borisf can comment on whether it makes sense for a sample to recommend it, or if it's too early.

Thanks Marton, Gradle type-safe project accesossors are incubating , thus have some rough edges https://github.com/gradle/gradle/issues?q=is%3Aopen+is%3Aissue+label%3Ain%3Aproject-accessors

The added benefit of type safety and IDE autocomplete seem to outweigh the "rough edges" so decided to add this in https://github.com/android/nowinandroid/pull/958.


Update win32.md

Added steps to view Browse tab in NuGet window.

Docs Build status updates of commit 99eec2d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/get-started/win32.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f996983:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/get-started/win32.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit bd59062:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/get-started/win32.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2dfd3aa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/get-started/win32.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f734cb8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/get-started/win32.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8de1c68:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/webview2/get-started/win32.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Script to run onnx-mlir from docker container

Convenient python script to run onnx-mlir from docker container
Check freopen failure in MainUtils.cpp:outputCode
Ignore invalid -o option values in main.cpp
Update README.md about the convenient python script

Signed-off-by: Gong Su<EMAIL_ADDRESS>

@sstamenova there were some Windows changes and the Windows CI is failing, could you take a look please?

I'm guessing the problem is that stderr is a constant on Windows. Not sure how to reopen stderr on Windows in this case.

I'm guessing the problem is that stderr is a constant on Windows. Not sure how to reopen stderr on Windows in this case.

That is indeed the case: https://docs.microsoft.com/en-us/cpp/c-runtime-library/stdin-stdout-stderr?view=msvc-160
D:\a\1\onnx-mlir\src\MainUtils.cpp(562,39): error C2106: '=': left operand must be l-value [D:\a\1\onnx-mlir\build\src\MainUtils.vcxproj]
D:\a\1\onnx-mlir\src\MainUtils.cpp(573,37): error C2106: '=': left operand must be l-value [D:\a\1\onnx-mlir\build\src\MainUtils.vcxproj]

I am not sure if it is possible to re-open stderr or stdout on Windows, but I was wondering - why do we need to do any redirection for stderr at all? As far as I know, the print() function can take any raw_ostream, so to print the output to a file, we just need to pass it to print instead of llvm::errs. Am I missing a use case?

I didn't write that code originally but did feel it's a bit strange with the redirection. Perhaps @tjingrant can offer some insights?

I didn't write that code originally but did feel it's a bit strange with the redirection. Perhaps @tjingrant can offer some insights?

@tjingrant @gongsu832 : I'd like to clean this bit of code (using stderr for file output) unless there's a reason to keep it as is. If you have any objections, please let me know, otherwise I'll follow up with a PR some time next week.

@tjingrant @gongsu832 : I'd like to clean this bit of code (using stderr for file output) unless there's a reason to keep it as is. If you have any objections, please let me know, otherwise I'll follow up with a PR some time next week.

@sstamenova  What is the status of this. Should we go with this PR as is, and you propose your cleanup in a different PR? That would appear the easiest way to go about it. Let me know, thanks

@tjingrant @gongsu832 : I'd like to clean this bit of code (using stderr for file output) unless there's a reason to keep it as is. If you have any objections, please let me know, otherwise I'll follow up with a PR some time next week.

@sstamenova What is the status of this. Should we go with this PR as is, and you propose your cleanup in a different PR? That would appear the easiest way to go about it. Let me know, thanks

This can't be checked in as is because it will fail the Windows build.

https://github.com/onnx/onnx-mlir/pull/784 makes the necessary changes to write directly to the output file

@gongsu832 I pushed #784 to the master branch, there are now conflict with this one as you forecasted. I let you fix them, thanks

@AlexandreEichenberger The conflict has been resolved and it's ready to go.

Jenkins Linux ppc64le Build #698 [push] - Convenient python scri... started at 10:09

Jenkins Linux amd64 Build #1560 [push] - Convenient python scri... started at 09:04

Jenkins Linux s390x Build #1558 [push] - Convenient python scri... started at 10:05

Jenkins Linux s390x Build #1558 [push] - Convenient python scri... passed after 42 min

Jenkins Linux amd64 Build #1560 [push] - Convenient python scri... passed after 51 min

Jenkins Linux ppc64le Build #698 [push] - Convenient python scri... passed after 54 min


Dependencies

Closes #17

Pull Request Test Coverage Report for Build 46

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 63.772%

Totals

Change from base Build 37:
0.0%

Covered Lines:
257

Relevant Lines:
403

💛  - Coveralls


Prerelease/qa one config

this is part of a set of PRs.  See https://salesforce.quip.com/kRtwAJN99VYE for explanation, sequence, and QA

What does this PR do?

use the unified ConfigAggregator and Config
that warns instead of throwing on deprecatedKeys, so much of the try/catch logic and NUTs had to change
where Config.set didn't return useful information about how it translates old to new names (it return all the properties so you can't tell what you changed) it was previously returning the name passed in.  The plugin command now determines the "new" value if necessary before calling Config.set
a new mixedNuts test that's mixing old and new keys to check for correct usage and prevent duplication between the two
adds plugin-deploy-retrieve as a dev-dep since some of the tests are using a config-meta that resides there and is not known to sfdx-core.  This required a change to the hooks UT
set all the nuts to not do hubAuth

What issues does this PR fix or reference?
@W-13048680@

QA Notes

setup
sfdx plugins install @salesforce/plugin-settings@qa

sfdx plugins --core
...
settings 1.5.0-qa.3 (qa)

❌ : thinks I have env vars set, suggests two similar vars... (doesn't happen with sf)
(node:64001) Warning: Deprecated environment variable: SFDX_AUTOUPDATE_DISABLE. Please use SF_AUTOUPDATE_DISABLE instead.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:64001) Warning: Deprecated environment variable: SFDX_DISABLE_AUTOUPDATE. Please use SF_DISABLE_AUTOUPDATE instead.

I don't have either of those set
➜  dreamhouse-lwc git:(main) ✗  hub:(DevHub<EMAIL_ADDRESS> ➜  env | grep SFDX
➜  dreamhouse-lwc

✅ : config set <deprecated> suggests/displays new
✅ : config get <deprecated> shows correct, warns
✅ : config get a value that's not set
✅ : config get a deprecated value not set
✅ : config get an env var with deprecated config name
✅ : config get an env var with current name
❓ : should config unset print old name?
 ➜  sfdx config unset defaultdevhubusername
Warning: Deprecated config name: defaultdevhubusername. Please use target-dev-hub instead.
Unset Config
===============================
| Name                  Success
| ───────────────────── ───────
| defaultdevhubusername true

❌ : does not respect the SFDX_REST_DEPLOY env var like others

doesn't show up in config list as an environment

✅ : env var warnings in every command
 ➜  sfdx force data soql query -q "SELECT MemberType, MemberName, RevisionCounter FROM SourceMember WHERE MemberType='PermissionSet'" -t
(node:76699) Warning: Deprecated environment variable: SFDX_MAX_QUERY_LIMIT. Please use SF_ORG_MAX_QUERY_LIMIT instead.

💡 : what do you think about a new command, migrate config that moves config/envs to clear these warnings
❌ : sf ignoring sfdx env vars... seems to just be related to the "rest" config/env
 ➜  env | grep SF
SFDX_REST_DEPLOY=true
SFDX_MAX_QUERY_LIMIT=1
➜  dreamhouse-lwc git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sf force source deploy -p force-app
Deploying v57.0 metadata to<EMAIL_ADDRESS>using the v57.0 SOAP API.
---
 ➜  env | grep SF
SFDX_MAX_QUERY_LIMIT=1
SF_ORG_METADATA_REST_DEPLOY=true
➜  dreamhouse-lwc git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sfdx force source deploy -p force-app
Deploying v57.0 metadata to<EMAIL_ADDRESS>using the v57.0 SOAP API.

❌ : warnings only when using sfdx
 ➜  sf config list
List Config
=============================================
| Name                     Value  Location
| ──────────────────────── ────── ───────────
| org-max-query-limit      1      Environment
| org-metadata-rest-deploy true   Environment
| target-dev-hub           DevHub Global
➜  dreamhouse-lwc git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sfdx config list
(node:80799) Warning: Deprecated environment variable: SFDX_MAX_QUERY_LIMIT. Please use SF_ORG_MAX_QUERY_LIMIT instead.

❌ : no more, "did you mean" interactivity?
 ➜  sfdx config set<EMAIL_ADDRESS>Error (1): Unknown config name: defaulttargetusername.

❌ : sf won't warn about deprecated env vars - maybe just related to the rest deploy - nope...
 ➜  export SFDX_REST_DEPLOY=true
➜  dreamhouse-lwc git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sf config list
List Config
============================================================

---
 ➜  export SFDX_MAX_QUERY_LIMIT=1
➜  dreamhouse-lwc git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sf config list
List Config

✅ : unsets with old name and prints new
➜  sf config unset maxQueryLimit
Warning: Deprecated config name: maxQueryLimit. Please use org-max-query-limit instead.
Unset Config
=============================
| Name                Success
| ─────────────────── ───────
| org-max-query-limit true

🏆 ✅ : interactivity is back
➜  dreamhouse-lwc git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sf config set defaultdevusern=test
? Did you mean disable-telemetry? No

✅ : sf warns about deprecated env vars, I know you're looking at this though
 ➜  SFDX_MAX_QUERY_LIMIT=3 sf config list
(node:89887) Warning: Deprecated environment variable: SFDX_MAX_QUERY_LIMIT. Please use SF_ORG_MAX_QUERY_LIMIT instead.

❌ : plugin-source might need to be updated
 ➜  sf config set restDeploy=true
Warning: Deprecated config name: restDeploy. Please use org-metadata-rest-deploy instead.
Set Config
========================================
| Name                     Value Success
| ──────────────────────── ───── ───────
| org-metadata-rest-deploy true  true
➜  dreamhouse-lwc git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sfdx force source deploy -p force-app
Warning: We plan to deprecate this command in the future. Try using the "project deploy start" command instead.
Error (1): Unknown config name: org-metadata-rest-deploy.
➜  dreamhouse-lwc git:(main) ✗  hub:(GLOBAL - DevHub<EMAIL_ADDRESS> ➜  sf force source deploy -p force-app
Warning: We plan to deprecate this command in the future. Try using the "project deploy start" command instead.
Error (1): Unknown config name: org-metadata-rest-deploy.

✅ : org-max-query-limit respected in every command, with appropriate warnings and deprecation messages
✅ : no warnings about auto-update env vars anymore when running from sfdx-cli
➜  sfdx-cli git:(sm/unified-config-aggregator)
 ➜  ./bin/run config:list
List Config
================================
| Name           Value  Location
| ────────────── ────── ────────
| target-dev-hub DevHub Global

closed in favor of #248


Search finds wrong item when playing on non-default player

Hi, the plex_assistant is great when using the default player. Excellent addition.
However it is very hit and miss when trying to play to other media players. An example is in the logs below: I request "boiler room" and it plays a seemingly unrelated documentary "Absolute Zero". Considering the wording in the request, I find that a bit surprising :)
It happens over and over with this film, even if the request text is "play the movie boiler room on the Bedroom Cast.
There are multiple players in the bedroom (android bravias have several players recognised by plex) but I get the same result regardless of how I refer to them.
Install: installed integration in Home Assistant docker
Trigger: mqtt calling the Home Assistant "plex_assistant.command", or the HA command directly (same results)
Logs:
2021-09-12 13:03:29 DEBUG (SyncWorker_1) [custom_components.plex_assistant.const] Processed Command: {'media': 'boiler room', 'device': 'bedroom tv'}
2021-09-12 13:03:29 DEBUG (SyncWorker_1) [custom_components.plex_assistant.const] PA Devices: {'Bravia Cast': {'entity_id': 'media_player.plex_bravia', 'device_type': 'plex'}, 'Bedroom speaker': {'entity_id': 'media_player.bedroom_speaker', 'device_type': 'cast'}, 'Bedroom Cast': {'entity_id': 'media_player.sonycast', 'device_type': 'cast'}, 'Lounge': {'entity_id': 'media_player.lounge', 'device_type': 'cast'}, 'Lounge speaker': {'entity_id': 'media_player.lounge_speaker', 'device_type': 'cast'}, 'Bedroom Plex': {'entity_id': 'media_player.plex_bedroomcast', 'device_type': 'plex'}, 'Plex (Plex for Android (Mobile) - SM-G975F)': {'entity_id': 'media_player.plex_plex_for_android_mobile_sm_g975f', 'device_type': 'plex'}}
2021-09-12 13:03:29 DEBUG (SyncWorker_1) [custom_components.plex_assistant.const] Device: Bedroom Cast
2021-09-12 13:03:29 DEBUG (SyncWorker_1) [custom_components.plex_assistant.const] Media: [<Episode:36431:Absolute-Zero-s01e01>, <Episode:36432:Absolute-Zero-s01e02>]```

This is a strange one as it's understanding and parsing the correct title 'media': 'boiler room'. Going to require some digging.

Hi - thanks for looking into it.
Yesterday I removed and re-added the cast integration from Home Assistant. In the process i had to remove and readd the Plex assistant.
I also changed the friendly-name for the casts, which means any subsequent queries on my part have been different.
Since then - touching wood - it has been accurate! So, strange as it was, it seems to have resolved, or maybe been avoided. If I can no longer reproduce it, I don't see the requirement in keeping this issue open?
Cheers
And PS - very glad I've found this integration, it's awesome


"extractions.YoutubeExtractor" in templates extract single quotes URL encoded (as ').

Issue
When I use the "extractions.YoutubeExtractor" in templates, single quotes are extracted URL encoded (as ').

Environment
Obsidian version: v1.2.6
Installer version: v1.1.9
Operating system: Windows 10 Home 10.0.22621
Login status: logged in
Text Generator v0.3.17
Steps to Reproduce (with "extractions.YoutubeExtractor")
1 - Paste a Youtube link on a note
2 - Open the command palette
3 - Select "Text Generator: Templates: Insert Template"
4 - Select a template that uses "extractions.YoutubeExtractor"
5 - Verify that the text is extracted
Unexpected Behaviour
Single quotes are extracted as
Ex.:
I'll leave a link in the description below and today we're going to go through this
is extracted as
I'll leave a link in the description below and today we're going to go through this
Expected Behaviour
Single quotes are extracted as "'"
Ex.:
I'll leave a link in the description below and today we're going to go through this

Closing the issue as the developer explained that using triple braces "{{{var}}}" instead of double braces "{{var}}" should prevents any encoding issues.
Worked like a charm.


Enable alt text in PFPs and Profile Banners

Describe the Feature
Enable alt text in PFPs and Profile Banners.
Attachments
No response
Describe Alternatives
No response
Additional Context
No response

Seconded. Alt Text is needed for all images on Bluesky

Agreed! The goal always should be to set new, higher, better standards of accessibility


[doc] Update devnotes

Hopefully clarifies a few of these steps for new users getting started on duos ui. The changes reflect areas that I was confused by.

Give more specifics to the use of./render-configs and make more prominent in the instructions.
Remove instructions that are covered by ./render-configs. We can use the script as documentation for the steps so that we do not need to maintain this in two places.
Update ./render-configs to differentiate between the parameters that set values (project) vs. boolean values (env -> write_env)
Bug: I found that I had to be in the scripts directory before calling ./render-configs.sh, so I've made that clear in the instructions. But, we may want to figure out how to run ./scripts/render-configs.sh directly.

Would you consider adding the newlines between coding blocks? Otherwise looks good and I'll close my PR.

For sure, done! Hopefully I didn't miss any.