[feature] materialized view resource

Fix #379
Add support for materialized view
Test Plan

[x] acceptance tests

[x] unit test

References

https://docs.snowflake.com/en/sql-reference/ddl-table.html#materialized-view-management
https://docs.snowflake.com/en/user-guide/views-materialized.html

@ryanking Would you check this? Thanks.

@ryanking Would you check this? Thanks.

@ryanking would you review this again?

@ryanking would you review this again?

/ok-to-test sha=e0a097312673d35749868d9641f5aa2979978efb

/ok-to-test sha=e0a097312673d35749868d9641f5aa2979978efb

@yohei1126 check out that test run, there are some failures.

@yohei1126 check out that test run, there are some failures.

/ok-to-test sha=d72a443bdf0255b751babde0c5222772c7cb85c4

/ok-to-test sha=d72a443bdf0255b751babde0c5222772c7cb85c4

integration test should work

integration test should work

@ryanking Would you check this again? Thanks

@ryanking Would you check this again? Thanks

Thanks will fix it

Thanks will fix it

@ryanking @alldoami Would you check this again? Thanks

@ryanking @alldoami Would you check this again? Thanks

/ok-to-test sha=597690b

/ok-to-test sha=597690b

@yohei1126 can you update the branch?

@yohei1126 can you update the branch?

@alldoami done

@alldoami done

/ok-to-test sha=4f8c098

/ok-to-test sha=4f8c098

did rebase main again

did rebase main again

/ok-to-test sha=59962e9

/ok-to-test sha=59962e9

@alldoami How can I check the test result?

@alldoami How can I check the test result?

@yohei1126 we append a comment on the same comment above https://github.com/chanzuckerberg/terraform-provider-snowflake/pull/385#issuecomment-759606420

@yohei1126 we append a comment on the same comment above https://github.com/chanzuckerberg/terraform-provider-snowflake/pull/385#issuecomment-759606420

OK found it. I do not know why this happended though.
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:35: Step 1/1 error: Error running pre-apply refresh: 2021/01/13 17:36:56 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: Incorrect attribute value type

          on config223903047/terraform_plugin_test.tf line 12, in resource "snowflake_materialized_view" "test":
          12: 	cluster_by = "ROLE_NAME"

        Inappropriate value for attribute "cluster_by": list of string required.

--- FAIL: TestAcc_MaterializedView2 (1.47s)
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:15: Step 1/1 error: Error running pre-apply refresh: 2021/01/13 17:36:58 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: Incorrect attribute value type

          on config912500339/terraform_plugin_test.tf line 12, in resource "snowflake_materialized_view" "test":
          12: 	cluster_by = "ROLE_NAME"

        Inappropriate value for attribute "cluster_by": list of string required.

OK found it. I do not know why this happended though.
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:35: Step 1/1 error: Error running pre-apply refresh: 2021/01/13 17:36:56 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: Incorrect attribute value type

          on config223903047/terraform_plugin_test.tf line 12, in resource "snowflake_materialized_view" "test":
          12: 	cluster_by = "ROLE_NAME"

        Inappropriate value for attribute "cluster_by": list of string required.

--- FAIL: TestAcc_MaterializedView2 (1.47s)
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:15: Step 1/1 error: Error running pre-apply refresh: 2021/01/13 17:36:58 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: Incorrect attribute value type

          on config912500339/terraform_plugin_test.tf line 12, in resource "snowflake_materialized_view" "test":
          12: 	cluster_by = "ROLE_NAME"

        Inappropriate value for attribute "cluster_by": list of string required.

locally fixed it. will run acceptance test locally.

locally fixed it. will run acceptance test locally.

@yohei1126 can you push your changes and we test here again?

@yohei1126 can you push your changes and we test here again?

@alldoami will do next week

@alldoami will do next week

@alldoami I have done rebase to main but got this error. Do you know why this happened?
=== CONT  TestAccSystemGetAWSSNSIAMPolicy_basic
    system_get_aws_sns_iam_policy_acceptance_test.go:22: Step 1/1 error: Check failed: Check 2/2 error: data.snowflake_system_get_aws_sns_iam_policy.p: Attribute 'aws_sns_topic_policy_json' expected "{\"Version\":\"2012-10-17\",\"Statement\":[{\"Sid\":\"1\",\"Effect\":\"Allow\",\"Principal\":{\"AWS\":\"arn:aws:iam::494544507972:user/3gmi-s-ssca3411\"},\"Action\":[\"sns:Subscribe\"],\"Resource\":[\"arn:aws:sns:us-east-1:1234567890123456:mytopic\"]}]}", got "{\"Version\":\"2012-10-17\",\"Statement\":[{\"Sid\":\"1\",\"Effect\":\"Allow\",\"Principal\":{\"AWS\":\"arn:aws:iam::532029211228:user/154a-s-sgss5425\"},\"Action\":[\"sns:Subscribe\"],\"Resource\":[\"arn:aws:sns:us-east-1:1234567890123456:mytopic\"]}]}"
--- FAIL: TestAccSystemGetAWSSNSIAMPolicy_basic (18.16s)
FAIL
coverage: 71.4% of statements
FAIL    github.com/chanzuckerberg/terraform-provider-snowflake/pkg/datasources  18.201s
?       github.com/chanzuckerberg/terraform-provider-snowflake/pkg/db   [no test files]

@alldoami reported this issue. https://github.com/chanzuckerberg/terraform-provider-snowflake/issues/439

/ok-to-test sha=4de7962

Added table resource as well since materialized view only can specify single table only.
Do you know why this error is caused?
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:42: Step 1/1 error: Error running apply: 2021/02/02 03:29:28 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view BITSCXFTTE: 002003 (42S02): SQL compilation error:
        Object 'IEVYSHCJYE.WRMSYADHGO.LGYLHQKDKU' does not exist or not authorized.

--- FAIL: TestAcc_MaterializedView2 (30.27s)
=== CONT  TestAcc_InternalStage
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:18: Step 1/1 error: Error running apply: 2021/02/02 03:29:37 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view EXDMERVEJH: 002003 (42S02): SQL compilation error:
        Object 'SITIFFMONN.PNCMMZZUVR.ZFOPJRGUCP' does not exist or not authorized.

/ok-to-test sha=99b79b6

@alldoami How can I avoid this?
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:42: Step 1/1 error: Error running apply: 2021/02/02 03:45:44 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view OHNGEMQUEM: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

do not know why this happened
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:18: Step 1/1 error: Error running apply: 2021/02/02 03:45:48 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view OHOQJFIETC: 002003 (42S02): SQL compilation error:
        Object 'UNVDWZIOZF.YOFRYBNATZ.DOPZKQWZNT' does not exist or not authorized.

@yohei1126 for the first error - we might need to take a warehouse as a provider-level parameter.

I noticed that in the second error, it's trying to create a view OHOQJFIETC but getting an error with UNVDWZIOZF.YOFRYBNATZ.DOPZKQWZNT which has three names, it's not clear if it is database.schema.view-possibly?

or the first error - we might need to take a warehouse as a provider-level parameter.
@ryanking What do you mean? How can I do this?

I have confirmed these statements are valid but CREATE SECURE MATERIALIZED VIEW might have run before CREATE TABLE. So we need to create table first.
CREATE DATABASE "MTZBSYTJTG";
SHOW DATABASES LIKE 'MTZBSYTJTG';
CREATE SCHEMA "MTZBSYTJTG"."XBOWHTHATS" DATA_RETENTION_TIME_IN_DAYS = 1;
SHOW SCHEMAS LIKE 'XBOWHTHATS' IN DATABASE "MTZBSYTJTG";
CREATE TABLE "MTZBSYTJTG"."XBOWHTHATS"."TVUTNNTZWN" ("ID" INT, "DATA" TEXT);
SHOW TABLES LIKE 'TVUTNNTZWN' IN SCHEMA "MTZBSYTJTG"."XBOWHTHATS";
CREATE SECURE MATERIALIZED VIEW "MTZBSYTJTG"."XBOWHTHATS"."TKHLAGAMPO" COMMENT = 'Terraform test resource' CLUSTER BY (ID,DATA) AS SELECT ID, DATA FROM TVUTNNTZWN WHERE ID LIKE 'foo%';

Materialized view requires computing resource so we need to resume warehouse.

No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

Error: error creating view OHOQJFIETC: 002003 (42S02): SQL compilation error:
Object 'UNVDWZIOZF.YOFRYBNATZ.DOPZKQWZNT' does not exist or not authorized

Now the test hast 2 steps and create table first. This issue has been solved.

No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

I will try to fix this issue by creating a warehouse.

resource "snowflake_warehouse" "w" {
		name    = "%s"
}

Added warehouse resource but got this error.
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:53: Step 2/2 error: Error running apply: 2021/02/03 06:15:36 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view JNAAPHNNAH: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

This terraform code tries to create table and materiazed view at the same time. So it fails with this error Object 'UNVDWZIOZF.YOFRYBNATZ.DOPZKQWZNT' does not exist or not authorized. since the table does not exist at the moment.
resource "snowflake_database" "test" {
	name = "%s"
}

resource "snowflake_schema" "test" {
	database  = snowflake_database.test.name
	name      = "%s"
}

resource "snowflake_table" "test" {
	database = snowflake_database.test.name
	schema   = snowflake_schema.test.name
	name     = "%s"

	column {
		name = "ID"
		type = "NUMBER(38,0)"
	}

	column {
		name = "DATA"
		type = "VARCHAR(16777216)"
	}
}

resource "snowflake_materialized_view" "test" {
	name      = "%s"
	comment   = "Terraform test resource"
	database  = snowflake_database.test.name
	schema    = snowflake_schema.test.name
	is_secure = true
	or_replace = false
	cluster_by = %s
	statement = "%s"
}

Is it possible to create table before creating materialized view?

I've changed the tests to 2 steps. 1st step creates database, schema and table. 2nd step creates materialized view.
	resource.ParallelTest(t, resource.TestCase{
		Providers: providers(),
		Steps: []resource.TestStep{
			{
				Config: targetTableConfig(dbName, schemaName, tableName),
			},
			{
				Config: materializedViewConfig(dbName, schemaName, viewName, []string{"ID", "DATA"}, fmt.Sprintf("SELECT ID, DATA FROM \\\"%s\\\" WHERE ID LIKE 'foo%%';", tableName)),
				Check: resource.ComposeTestCheckFunc(
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "name", viewName),
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "database", dbName),
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "schema", schemaName),
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "comment", "Terraform test resource"),
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "cluster_by", "[\"ID\",\"DATA\"]"),
					checkBool("snowflake_materialized_view.test", "is_secure", true),
				),
			},
		},
	})

Now we need to activate warehouse.
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:45: Step 2/2 error: Error running apply: 2021/02/03 08:19:59 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view LTWCSTNKIE: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

--- FAIL: TestAcc_MaterializedView2 (10.30s)
=== CONT  TestAcc_MaskingPolicy
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:18: Step 2/2 error: Error running apply: 2021/02/03 08:20:03 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view ZEVTEBEFFL: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

@ryanking Any advice to activate warehouse for the acceptance test? How can I create a warehouse and specify it as provider?

/ok-to-test sha=d9bdd11

@ryanking Any advice to activate warehouse for the acceptance test? How can I create a warehouse and specify it as provider?

Is it possible to create table before creating materialized view?

Use depends_on

Use depends_on docs.
@ryanking Thanks. I fixed it.

Now we need to think about how to create a warehouse and activate it for the acceptance tests.

/ok-to-test sha=efd2e51

The acceptance tests failed as expected since no active warehouse.
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:42: Step 1/1 error: Error running apply: 2021/02/04 02:05:23 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0
        Error: error creating view JHTEXDABTZ: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:18: Step 1/1 error: Error running apply: 2021/02/04 02:05:29 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view RWMVUBGXVO: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

@yohei1126 Thanks for sticking with this! We've discussed what the best approach would be for this, and we've concluded that you should require a warehouse for this resource. This warehouse is only needed at runtime and is unique compared to the other resources that only make DDL changes. It would be great if you could name the warehouse something like reflects the purpose of it (possibly connection-warehouse?). Let us know if you have any questions!
cc: @ryanking

Ok will try soon

I do not know why this happened...
[DEBUG] extracting view query CREATE SECURE MATERIALIZED VIEW "YIJUYZZBKJ"."QUINQHKFDI"."QMHYFJUABV" COMMENT = 'Terraform test resource' CLUSTER BY (ID,DATA) AS SELECT ID, DATA FROM "EQGXXRXRMS" WHERE ID LIKE 'foo%';
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:42: Step 1/1 error: Check failed: Check 5/6 error: snowflake_materialized_view.test: Attribute 'cluster_by' not found
--- FAIL: TestAcc_MaterializedView2 (11.90s)
[DEBUG] extracting view query CREATE SECURE MATERIALIZED VIEW "CTWYVDGCML"."XPKBFAPHTX"."INVGJHVMWM" COMMENT = 'Terraform test resource' CLUSTER BY (ID,DATA) AS SELECT ID, DATA FROM "PBMPNRMUJB";
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:18: Step 1/1 error: Check failed: Check 5/6 error: snowflake_materialized_view.test: Attribute 'cluster_by' not found

@ryanking @alldoami

[DEBUG] extracting view query CREATE SECURE MATERIALIZED VIEW "YIJUYZZBKJ"."QUINQHKFDI"."QMHYFJUABV" COMMENT = 'Terraform test resource' CLUSTER BY (ID,DATA) AS SELECT ID, DATA FROM "EQGXXRXRMS" WHERE ID LIKE 'foo%';

This debug code comes from parser.go. Do  I have to do something here? Do we need Extract for materialized view?
func (e *ViewSelectStatementExtractor) Extract() (string, error) {
	fmt.Printf("[DEBUG] extracting view query %s\n", string(e.input))
	e.consumeSpace()
	e.consumeToken("create")
	e.consumeSpace()
	e.consumeToken("or replace")
	e.consumeSpace()
	e.consumeToken("secure")
	e.consumeSpace()
	e.consumeToken("recursive")
	e.consumeSpace()
	e.consumeToken("view")
	e.consumeSpace()
	e.consumeToken("if not exists")
	e.consumeSpace()
	e.consumeIdentifier()
	// TODO column list
	// TODO copy grants
	e.consumeComment()
	e.consumeSpace()
	e.consumeComment()
	e.consumeSpace()
	e.consumeToken("as")
	e.consumeSpace()

/ok-to-test sha=d6939b7

It generates valid SQL and succeeded.
CREATE SECURE MATERIALIZED VIEW "EQCEWUQNKE"."OQTJTAGWKY"."NOOGVWERUE" COMMENT = 'Terraform test resource' CLUSTER BY (ID,DATA) AS SELECT ID, DATA FROM "UQAQXXNVDG" WHERE ID LIKE 'foo%';

but the acceptance test still failed to read cluster_by.
[DEBUG] extracting materialized view query: CREATE SECURE MATERIALIZED VIEW "EQCEWUQNKE"."OQTJTAGWKY"."NOOGVWERUE" COMMENT = 'Terraform test resource' CLUSTER BY (ID,DATA) AS SELECT ID, DATA FROM "UQAQXXNVDG" WHERE ID LIKE 'foo%';
=== CONT  TestAcc_MaterializedView2
    materialized_view_acceptance_test.go:42: Step 1/1 error: Check failed: Check 5/6 error: snowflake_materialized_view.test: Attribute 'cluster_by' not found
--- FAIL: TestAcc_MaterializedView2 (12.88s)

@yohei1126 I think the cluster_by attribute is not being added to the terraform state.

@alldoami I know. It should be set. https://github.com/chanzuckerberg/terraform-provider-snowflake/pull/385/files#diff-9fa9cb5b99443c25944ad76b8949ace0af61ec2ab3f932928bd58c5dcadf6887R220

@yohei1126 can you debug by adding logging statements around that line and test that locally?

commented out check for  cluster_by
	resource.ParallelTest(t, resource.TestCase{
		Providers: providers(),
		Steps: []resource.TestStep{
			{
				Config: materializedViewConfig(dbName, schemaName, tableName, viewName, []string{"ID", "DATA"}, fmt.Sprintf("SELECT ID, DATA FROM \\\"%s\\\";", tableName)),
				Check: resource.ComposeTestCheckFunc(
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "name", viewName),
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "database", dbName),
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "schema", schemaName),
					resource.TestCheckResourceAttr("snowflake_materialized_view.test", "comment", "Terraform test resource"),
					//resource.TestCheckResourceAttr("snowflake_materialized_view.test", "cluster_by", "[\"ID\",\"DATA\"]"),
					checkBool("snowflake_materialized_view.test", "is_secure", true),
				),
			},
		},
	})

Now I got this error.
[DEBUG] extracting materialized view query: CREATE SECURE MATERIALIZED VIEW "NSFHFRGZNE"."NAIGHWWNDR"."AAOAMHDDOG" COMMENT = 'Terraform test resource' CLUSTER BY (ID,DATA) AS SELECT ID, DATA FROM "ZOCPCKHRXN";
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:18: Step 1/1 error: After applying this test step, the plan was not empty.
        stdout:

        An execution plan has been generated and is shown below.
        Resource actions are indicated with the following symbols:
          ~ update in-place

        Terraform will perform the following actions:

          # snowflake_materialized_view.test will be updated in-place
          ~ resource "snowflake_materialized_view" "test" {
              ~ cluster_by = [
                  - "LINEAR(ID",
                  - "DATA)",
                  + "ID",
                  + "DATA",
                ]
                comment    = "Terraform test resource"
                database   = "NSFHFRGZNE"
                id         = "NSFHFRGZNE|NAIGHWWNDR|AAOAMHDDOG"
                is_secure  = true
                name       = "AAOAMHDDOG"
                or_replace = false
                schema     = "NAIGHWWNDR"
                statement  = "SELECT ID, DATA FROM \"ZOCPCKHRXN\";"
            }

        Plan: 0 to add, 1 to change, 0 to destroy.

Hmm this is a bit weird:
~ cluster_by = [
                  - "LINEAR(ID",
                  - "DATA)",
                  + "ID",
                  + "DATA",
                ]

@alldoami deleted all cluster related code. now acceptance tests have passed.

/ok-to-test sha=b76cece

thanks. will check it tonight

Set initially_suspended = false to warehouse but the warehouse did not start while testing materialized view.
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:18: Step 1/1 error: Error running apply: 2021/02/12 12:51:59 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.10.0

        Error: error creating view LOBOFXPRIN: 000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

@yohei1126 can you trying requiring a warehouse on the resource?

already did it

@alldoami Added multiExec functionality. Do you know why this happened?
=== CONT  TestAcc_MaterializedView
    materialized_view_acceptance_test.go:19: Step 1/1 error: Error running apply: exit status 1
        2021/02/25 15:44:30 [DEBUG] Using modified User-Agent: Terraform/0.12.29 HashiCorp-terraform-exec/0.13.0

        Error: Provider produced inconsistent result after apply

        When applying changes to snowflake_materialized_view.test, provider
        "registry.terraform.io/-/snowflake" produced an unexpected new value for was
        present, but now absent.

        This is a bug in the provider, which should be reported in the provider's own
        issue tracker.

--- FAIL: TestAcc_MaterializedView (25.33s)

@ryanking @alldoami Now it should work. Would you check this?

/ok-to-test sha=d7140f3

@yohei1126 could you update your branch 😄

already updated

/ok-to-test sha=62128fa


Non-Note Events

The Problem
Some events are defined in relation to other notes, and so requiring their own note causes bulk and overhead. For example:

There is a leader of a state who has a note describing them. They have various dates associated with them, including birth, death, their first election where they lost, the next election where they won, the date they took office, the date they left office, etc.. To include these on a timeline, the user must create new notes for each of these events (some may be notes with start and end dates).

Proposed Solution
Parse existing notes for a new block, which could be defined similarly to (e.g.) for the above example:
'''aat-event
[Name of Timeline 1, Name of Timeline 2]
name: Birth of Alex Person
start-date: 01-01-1950
'''
'''aat-event
[Name of Timeline 1, Name of Timeline 2]
name: 1990 Election Loss
start-date: 01-01-1990
desc: Took only 5% of the vote
'''
'''aat-event
[Name of Timeline 1, Name of Timeline 2]
name: 2005 Election Win
start-date: 01-01-2005
desc: Won with 95% of the vote
'''
'''aat-event
[Name of Timeline 1, Name of Timeline 2]
name: 2010 Election Loss and Leaves Office
start-date: 01-01-2005
desc: Lost with only 10% of the vote
'''
'''aat-event
[Name of Timeline 1, Name of Timeline 2]
name: Death of Alex Person
start-date: 01-01-2020
desc: Died of natural causes
'''
In this way, multiple events directly relating to a single note can be defined inline and appear on timelines. The card produced could be unclickable, or could be anchored to where the event is defined within the note.

Damn, this is another great idea.
I will most definitly end up implementing this.
For the moment I need to polish up #31 then move on to your previous feature request (#37)
So this will definitly take up some time, but thank you so much for this :pray:

Hey @Aereanor I'm very much overjoyed to tell you that
Inline notes are now available in version 0.7.0. It was a bit of an undertaking but the end result is really worth it
https://github.com/April-Gras/obsidian-auto-timelines/assets/1866440/454c04c0-8739-4376-8904-90fd4c4551a1
I'm sure you'll get some good use out of it
Thank you again for the submission, lmk if anything goes wrong

Hi @April-Gras, thank you for yourwork into this and my other suggestions. I am very grateful for your efforts.


Make s390x repo name shorter for Leap

z/VM parmfile has a length line limit of 72 characters.

Remove "openSUSE-" prefix to make the name 10 characters shorter
Dedicate directory to get rid of aarc64-ppc64le-x86_64 in the
directory name

https://github.com/os-autoinst/openqa-trigger-from-obs/pull/126


Fix tooltips don't appear for PopupMenus

Fixed #49077
I can't say that the change I made on viewport.cpp is very good, but the system here needs to change. Read this for explanation: https://github.com/godotengine/godot/issues/49077#issuecomment-902343554
https://user-images.githubusercontent.com/12533045/130163857-9c2c6ba9-3594-4105-8a78-c409fe2645ef.mp4

Updated commit message.


OSXFUSE prefpane appears to no longer be selected by default

When installing OSXFUSE on macOS 10.13, it seems like the PrefPane is no longer installed by default. Because Munki still expects it to be installed, this causes it to install OSXFUSE over and over. This pull request adds a choice change for the PrefPane to always install it.

Ah, yes, that would be a good thing to fix. Thanks!
-Josh


Correct rounded π value in checkJS.md

Corrects π value in checkJs examples.

Thanks for merging, @jakebailey!


hspec 2.5

hspec-2.5.0 (Simon Hengel<EMAIL_ADDRESS>@sol) is out of bounds for:

[ ] fold-debounce-<IP_ADDRESS> (>=2.1.7 && < 2.5). Toshio Ito<EMAIL_ADDRESS>@debug-ito. @debug-ito. Used by: test-suite
[ ] stb-image-redux-<IP_ADDRESS> (>=2.1.5 && < 2.5). Alexis Williams<EMAIL_ADDRESS>@typedrat. @typedrat. Used by: test-suite
[ ] stopwatch-<IP_ADDRESS> (< 2.5). Toshio Ito<EMAIL_ADDRESS>@debug-ito. @debug-ito. Used by: test-suite
[ ] wide-word-<IP_ADDRESS> (>=2.3 && < 2.5). Trevor L. McDonell<EMAIL_ADDRESS>@tmcdonell. @erikd. Used by: test-suite

In the interest of keeping constraints to a minimum for the new ghc-8.4.1 nightlies, I've marked the four above test suites as skipped.

I updated fold-debounce and stopwatch. Could you re-enable tests for these packages?
Thanks in advance.

@debug-ito done! Thanks for the quick update.

hspec-2.5.0 is out of bounds for:

[ ] glabrous-0.3.4 (>=2.1.10 && < 2.5). Michel Boucey<EMAIL_ADDRESS>@MichelBoucey. @MichelBoucey. Used by: test-suite

Added to skipped-tests

hspec-2.5.0 is out of bounds for:

[ ] aeson-picker-<IP_ADDRESS> (==2.4.*). Bogdan Neterebskii<EMAIL_ADDRESS>@o
zzzzz. @ozzzzz. Used by: test-suite

Added to skipped-tests.

Bounds updated in version aeson-picker-<IP_ADDRESS>.
Thank you.
All the best,
Bogdan
2018-03-14 18:13 GMT+03:00 Dan Burton<EMAIL_ADDRESS>
hspec-2.5.0 is out of bounds for:

aeson-picker-<IP_ADDRESS> (==2.4.*). Bogdan Neterebskii<EMAIL_ADDRESS>@o https://github.com/o
zzzzz. @ozzzzz https://github.com/ozzzzz. Used by: test-suite

Added to skipped-tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fpco/stackage/issues/3376#issuecomment-373057374, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFdIYLU2KKi2yP7-Dq80N6ydGff55klFks5teTOegaJpZM4SqZyT
.

Wide-word version <IP_ADDRESS> with bumped upper bound is on Hackage.


{Network} Fix az network application-gateway private-link add failed to create resources

Description

Fix bug https://github.com/Azure/azure-cli/issues/20708
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

/azp run

/azp run

Network

Please fix CI errors.


Docs site blanks intermittently

Several users reported blank pages on the docs site this morning around 11 am (Wednesday, August 22, 2018).
Screenshot from a user experiencing the issue of errors in their console:

This particular page appears to consistently not load -- if you look at the source or try to load it using curl, the source code is cut off right in the middle of an <input> tag. No idea how this happened beyond that, though.

@j-low, @mjibson, any ideas as to what's happening? Something with netlify?

I have no idea, but it is almost certainly related to netlify. I think the best we can do is continue to monitor this. Netlify did a major change of their SSL handling a few days ago and maybe this was fallout. We should keep watching and ask our employees to tell us anytime they see a blank page load.

This has been resolved.


Is there a way to recognize a person and determine where he or she has a joint?

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win10

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC

SDK Version
Latest

Language
C++/C#

Segment
others

Issue Description

I want to get the angle of a specific joint through image processing. I tried with Kinect sensor but this time I want to do it with RealSense.
My first thought process is as follows:

Recognize people through image processing
Judge the points of each joint and calculate the three points of the joint to get the angle.

I don't know how to determine if I am a person through image processing and find out where his joints are.

Can you please tell me something?
Is there a recommendation method or API? Is there anything I can refer to?
Thank you for your answer.

The best software available for joint tracking is a commercial package called Nuitrack SDK.  It has a licence fee of $40 a year but has a free trial version.
https://nuitrack.com/
The link below suggests a method for calculating joint angle with Nuitrack.
https://community.nuitrack.com/t/calculate-the-angle-between-two-joints/1121

@MartyG-RealSense
I searched and found it was compatible with the D435.
Thank you very much. You are my job saver(?).


Feature/dds-core-xtypes

Added compiled headers corresponding to xtypes and core that xtypes uses.

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows


Unable to Integrate Receiver: Receiving Unexpected Exception

I cannot integrate my receiver (VSX-822). Whenever I submit the following message appears after it loads for a bit:

Here are the settings I'm using:

The screenshots don't provide enough context to work out where the exception is being raised.
Can you supply the messages in your HA log relating to pioneer_async and aiopioneer? It looks like a bug parsing the response from your AVR, and the log should help pinpoint the response being parsed.

Hia, sorry for not uploading the logs. Not getting much information thought. This is what it is saying:
Home Assistant Core:
2024-11-11 15:29:39.404 INFO (MainThread) [aiopioneer.pioneer_avr] determining available listening modes
2024-11-11 15:29:39.419 INFO (MainThread) [aiopioneer.pioneer_avr] AVR connection established
2024-11-11 15:29:39.420 INFO (MainThread) [aiopioneer.pioneer_avr] querying device information
2024-11-11 15:29:43.501 INFO (MainThread) [aiopioneer.pioneer_avr] Global: model: None -> VSX-822 (<001><VSX-822/CUXESM >)
2024-11-11 15:29:45.529 INFO (MainThread) [aiopioneer.pioneer_avr] determining available listening modes
2024-11-11 15:29:45.529 INFO (MainThread) [aiopioneer.pioneer_avr] querying available zones on AVR
2024-11-11 15:29:45.538 INFO (MainThread) [aiopioneer.pioneer_avr] Zone 1: power: None -> True (0)
2024-11-11 15:29:45.642 INFO (MainThread) [aiopioneer.pioneer_avr] Zone 1: volume: None -> 71 (071)
2024-11-11 15:29:45.644 INFO (MainThread) [aiopioneer.pioneer_avr] Zone 1 discovered
2024-11-11 15:29:51.740 INFO (MainThread) [aiopioneer.pioneer_avr] querying AVR source names
2024-11-11 15:29:53.743 ERROR (MainThread) [custom_components.pioneer_async.config_flow] unexpected exception: cannot access local variable 'response' where it is not associated with a value
2024-11-11 15:29:53.761 INFO (MainThread) [aiopioneer.pioneer_avr] AVR connection closed

I saw the same issue, should be fixed by https://github.com/crowbarz/aiopioneer/pull/37. As a workaround, you can also disable "Query sources from AVR".

This solved my issue! Thanks @webmeister!


Release app version 0.3

when all tickets are done , release the app.

Available on Play Market
https://play.google.com/store/apps/details?id=io.horizontalsystems.bankwallet


Query can return both strings and parseable JSON

Bug/feature report
System info: 1.2.4 - HTTP query response
Steps to reproduce:

http://localhost:8086/query?q=select+*+from+circuits+limit+4&db=&chunked=true&chunk_size=5
http://localhost:8086/query?q=select+*+from+circuits+limit+6&db=&chunked=true&chunk_size=5

Expected behavior: I would expect both of these queries to return similar types of responses.
Actual behavior: Step 1 returns parseable JSON.  Step 2 returns a string that has to be split with "/n".  While this example coerces the behavior of the response, similar scenarios can happen with any data<chunk_size compared to data>chunk_size.
Results for 1: {"results":[{"statement_id":0,"series":[{"name":"circuits","columns":["time","circuitFunction","colorStr","freeze","friendlyName","lightgroup","name","number","numberStr","status"],"values":[["2017-05-17T14:40:02.285055781Z","Spa","off",0,"SPA","-1","SPA","1","circuit1",0],["2017-05-17T14:40:02.285865363Z","Intellibrite","off",0,"POOL LIGHT","4","POOL LIGHT","8","circuit8",0],["2017-05-17T14:40:02.285865365Z","Intellibrite","off",0,"PATH LIGHTS","4","PATH LIGHTS","9","circuit9",0],["2017-05-17T14:40:02.285867742Z","Generic","off",0,"WATERFALL MEDIUM","-1","WtrFall 2","13","circuit13",0]]}]}]}
Results for 2:
{"results":[{"statement_id":0,"series":[{"name":"circuits","columns":["time","circuitFunction","colorStr","freeze","friendlyName","lightgroup","name","number","numberStr","status"],"values":[["2017-05-17T14:40:02.285055781Z","Spa","off",0,"SPA","-1","SPA","1","circuit1",0],["2017-05-17T14:40:02.285865363Z","Intellibrite","off",0,"POOL LIGHT","4","POOL LIGHT","8","circuit8",0],["2017-05-17T14:40:02.285865365Z","Intellibrite","off",0,"PATH LIGHTS","4","PATH LIGHTS","9","circuit9",0],["2017-05-17T14:40:02.285867742Z","Generic","off",0,"WATERFALL MEDIUM","-1","WtrFall 2","13","circuit13",0],["2017-05-17T14:40:02.285872332Z","Generic","off",0,"AIR BLOWER","-1","AIR BLOWER","3","circuit3",0]],"partial":true}],"partial":true}]}
/n
{"results":[{"statement_id":0,"series":[{"name":"circuits","columns":["time","circuitFunction","colorStr","freeze","friendlyName","lightgroup","name","number","numberStr","status"],"values":[["2017-05-17T14:40:02.285878446Z","Generic","off",0,"WATERFALL HIGH","-1","WtrFall 3","14","circuit14",0]]}]}]}
This make is very unfriendly to try to programmatically deal with responses because we need to first test to see if the response is a string or a JSON (and this precludes the use of $.getJSON if a string is being returned).  Then additional logic is needed to split the string and then parse those into JSON.
Additional info: I do see similar issues/PRs but not sure if they are solving this exact problem.
https://github.com/influxdata/influxdb/pull/8477
https://github.com/influxdata/influxdb/issues/8450
Also, this part "]],"partial":true}],"partial":true}]}" doesn't look quite correct.  Are there supposed to be two partial:"true" elements in the object?

Remove chunked=true from your URL.

Yes, clearly I could remove chunked=true for a small sample like this.  My point, however, is that my code was working as I did my development on a manageable (~20k rows) dataset.  When I put my code in production Influx automatically started chunking my results and my code broke.  I didn't add the chunked=true.  It took me 3 days to track down this "behavior" which is the reason I'm logging this as a bug.
There is also no mention of this artifact in the docs either here or here when talking about chunking data back.  There also isn't any indication that the InfluxDB definition of chunked responses is different from a traditional chunked encoding which also took some time to understand.
Love the DB!  Just pointing out things that are really hard to understand and not consistent within the product/docs.

This is intentional and we'll work on improving the documentation for the current behavior. The two "partial": true values are also intentional. One of them says that the series is partial (and will be returned in the next result returned) and the second says that the result is partial (and should be merged with the first).
I know this is confusing which is the reason why #8450 exists to try and simplify this structure so we can retire the existing syntax. While we won't eliminate the current method since that would be backwards incompatible, the new method would offer an easier way to get the same thing in an easier to parse way.
I hope that helps clarify it a bit. I'll leave this open until I create the issue for documenting the chunking format in more detail.


Example

Issue: https://github.ibm.com/goldeneye/issues/issues/2184
Description
Please include a summary of the change and which issue is fixed. Also, please include the motivation and context for the change. List any dependencies that are required for this change.
Check the relevant boxes:

[ ] Bug fix (nonbreaking change that fixes an issue)
[ ] New feature (nonbreaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI related update (pipeline, etc.)

Checklist

[ ] If relevant, a test for the change has been added or updated as part of this PR.
[ ] If relevant, documentation for the change has been added or updated as part of this PR.

Merge

Merge using "Squash and merge".
Make sure to use a relevant conventional commit message that is based on the PR contents. The commit message determines whether a new version of the modules needs to be released, and if so, which semver number to use).

Ok pre-commit and terratest passing on this branch - merging with first branch.


diffusers dependency

Please do not bind specified diffusers version,  lead to pip dep resolve conflict with other library that requires newer version of diffusers
xinference[audio,embedding,image,rerank,transformers,vllm] 0+unknown depends on diffusers>=0.29.0; extra == "image"
deepcache 0.1.0 depends on diffusers
matcha-tts <IP_ADDRESS> depends on diffusers==0.25.0
xinference[audio,embedding,image,rerank,transformers,vllm] 0+unknown depends on diffusers>=0.29.0; extra == "image"
deepcache 0.1.0 depends on diffusers
matcha-tts <IP_ADDRESS> depends on diffusers==0.25.0

Hello,
I have bound the version because of reproducibility, in case someone wants to reproduce, they can go to the previous tag and use the source code from there. Feel free to remove it as long as it works for you.

Done!
I uploaded it to pypy as well future: pip install -U matcha-tts should not include the fixed diffusion version of matcha tts.
PyPi: https://pypi.org/project/matcha-tts
Binaries: https://github.com/shivammehta25/Matcha-TTS/releases/tag/v0.0.7
Commit: https://github.com/shivammehta25/Matcha-TTS/commit/77804265f877b0c42f13cfdece6541dde7838090


Merge Develop into master

UnitTests.cs fails:
Expected: 08/02/23 12.37.38
Actual: 08/02/23 12:37:38
Change . to : in the second argument for each unit tests.


libguestfs 1.29.5 build fails on 17.03 due to missing buildInput

Issue description
Building libguestfs on 17.03 fails with cannot find -lapparmor. This works fine on unstable as it includes libapparmor in buildInputs.
2f73d5f856d2448a4779401d54a64b55ba6f6bae should be backported to 17.03 in order to fix this.
The following commit cf68f546b1d5648c1d83f33e265c019c9f971c10 introduced more dependencies, but building the current version (1.29.5) succeeds without them.
Steps to reproduce
Try installing libguestfs on NixOS 17.03. It fails to compile. Adding this to configuration.nix fixes the build:
nixpkgs.config.packageOverrides = pkgs: {
  libguestfs = pkgs.libguestfs.overrideAttrs (oldAttrs: rec {
    buildInputs = oldAttrs.buildInputs ++ [ pkgs.libapparmor ];
  });
};

Technical details

System: NixOS 17.03.1016.c558d093ab (Gorilla)
Nix version: nix-env (Nix) 1.11.8
Nixpkgs version: 17.03.1016.c558d093ab

The fix should be included in the next release channel update.

Thanks!


RPM Specfile addition for intial RPM building process

Initial SPEC file for RPM creation of TSN Testbench

Do you want this merged as this? This is labeled as draft.

Hi Kurt, I left it as draft as I'm doing some testing with it, I would like to use extra vars for the release (now hardcoded to 5) with the goal to tie a new release with an automatic triggering of rpmbuild (both binary and srpm) for each release.
With the current SPEC I can get both rpm's created on my system and later install the binary rpm correctly.
If you're ok, we can merge and work in iterations over the remaining pieces

Hi Kurt, I left it as draft as I'm doing some testing with it, I would like to use extra vars for the release (now hardcoded to 5) with the goal to tie a new release with an automatic triggering of rpmbuild (both binary and srpm) for each release.
With the current SPEC I can get both rpm's created on my system and later install the binary rpm correctly.
If you're ok, we can merge and work in iterations over the remaining pieces

OK, I see. Then, I'll leave it open until you're testing is finished. Thanks!

I did set some of the vars as variables, that need to be provided via rpmbuild CLI and I'll try to get github build the repo RPM  automatically via another PR


Adding MTV ForkliftController resource

Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

/verified

/lgtm

/verified

/verified

/approve


added support for inline RadioList

In DefaultFormRenderer you could traditionally set RadioList to render its items inline by calling $type->getSeparatorPrototype()->setName(null);. This patch mimics that behaviour.

Just removed the superfluous call of $control->getSeparatorPrototype()->setName(null), simplifying it a bit.

please, space after if and ping me, thank you!  :-)

@hrach ok, the coding style should be fixed

Thank you!


zkg: init at 2.13.0

Description of changes
Package manager for Zeek
https://github.com/zeek/package-manager

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

6 packages built:

python310Packages.btest
python310Packages.btest.dist
python311Packages.btest
python311Packages.btest.dist
zkg
zkg.dist


[Snyk] Security upgrade node from 18.6.0-alpine to 18.20.2-alpine

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 5 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

Dockerfile

We recommend upgrading to node:18.20.2-alpine, as this image has only 6 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Buffer Overflow SNYK-UPSTREAM-NODE-3092933
  721

Out-of-bounds Write SNYK-ALPINE316-ZLIB-2976176
  714

Buffer Overflow SNYK-UPSTREAM-NODE-3092932
  625

HTTP Request Smuggling SNYK-UPSTREAM-NODE-3035795
  621

HTTP Request Smuggling SNYK-UPSTREAM-NODE-5741793
  621

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Checkmarx One – Scan Summary & Details – 98c26f9e-8b47-46d1-ab3c-df8106b91f0f
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2021-23440
Npm-set-value-2.0.0
Vulnerable Package

CVE-2021-23440
Npm-set-value-0.4.3
Vulnerable Package

CVE-2022-24999
Npm-qs-0.6.6
Vulnerable Package

CVE-2022-24999
Npm-qs-6.2.1
Vulnerable Package

CVE-2022-24999
Npm-qs-6.3.2
Vulnerable Package

CVE-2022-24999
Npm-qs-6.5.2
Vulnerable Package

CVE-2022-24999
Npm-qs-5.2.1
Vulnerable Package

CVE-2022-25883
Npm-semver-5.3.0
Vulnerable Package

CVE-2022-25883
Npm-semver-5.6.0
Vulnerable Package

CVE-2022-25883
Npm-semver-5.7.0
Vulnerable Package

CVE-2022-3517
Npm-minimatch-3.0.2
Vulnerable Package

CVE-2022-3517
Npm-minimatch-3.0.3
Vulnerable Package

CVE-2022-3517
Npm-minimatch-3.0.4
Vulnerable Package

CVE-2022-3517
Npm-minimatch-0.3.0
Vulnerable Package

CVE-2022-38900
Npm-decode-uri-component-0.2.0
Vulnerable Package

CVE-2023-25344
Npm-swig-1.4.2
Vulnerable Package

CVE-2023-25345
Npm-swig-1.4.2
Vulnerable Package

CVE-2023-26136
Npm-tough-cookie-2.3.4
Vulnerable Package

CVE-2023-26136
Npm-tough-cookie-2.4.3
Vulnerable Package

CVE-2023-26136
Npm-tough-cookie-2.3.1
Vulnerable Package

CVE-2023-26136
Npm-tough-cookie-2.2.2
Vulnerable Package

CVE-2023-45311
Npm-fsevents-1.2.9
Vulnerable Package

CVE-2024-27088
Npm-es5-ext-0.10.12
Vulnerable Package

CVE-2024-4068
Npm-braces-2.3.2
Vulnerable Package

CVE-2024-4068
Npm-braces-1.8.5
Vulnerable Package

Cx10578cb2-c0fc
Npm-cypress-3.3.1
Vulnerable Package

Insecure_Storage_of_Sensitive_Data
/app/data/user-dao.js: 21
Attack Vector

Insecure_Storage_of_Sensitive_Data
/app/data/profile-dao.js: 65
Attack Vector

Insecure_Storage_of_Sensitive_Data
/app/data/profile-dao.js: 62
Attack Vector

Insecure_Storage_of_Sensitive_Data
/app/data/profile-dao.js: 53
Attack Vector

Insecure_Storage_of_Sensitive_Data
/app/data/user-dao.js: 25
Attack Vector

Insecure_Storage_of_Sensitive_Data
/server.js: 82
Attack Vector

CVE-2017-20162
Npm-ms-0.7.1
Vulnerable Package

CVE-2023-0842
Npm-xml2js-0.4.4
Vulnerable Package

CVE-2023-28155
Npm-request-2.79.0
Vulnerable Package

CVE-2023-28155
Npm-request-2.67.0
Vulnerable Package

CVE-2023-28155
Npm-request-2.36.0
Vulnerable Package

CVE-2023-28155
Npm-request-2.88.0
Vulnerable Package

CVE-2023-28155
Npm-request-2.75.0
Vulnerable Package

CVE-2024-28863
Npm-tar-4.4.8
Vulnerable Package

CVE-2024-28863
Npm-tar-2.2.1
Vulnerable Package

CVE-2024-29041
Npm-express-4.16.4
Vulnerable Package

CVE-2024-4067
Npm-micromatch-3.1.10
Vulnerable Package

CVE-2024-4067
Npm-micromatch-2.3.11
Vulnerable Package

Container Traffic Not Bound To Host Interface
/docker-compose.yml: 10
Incoming container traffic should be bound to a specific host interface

Healthcheck Not Set
/docker-compose.yml: 4
Check containers periodically to see if they are running properly.

Healthcheck Not Set
/docker-compose.yml: 13
Check containers periodically to see if they are running properly.

Memory Not Limited
/docker-compose.yml: 4
Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than t...

Memory Not Limited
/docker-compose.yml: 13
Memory limits should be defined for each container. This prevents potential resource exhaustion by ensuring that containers consume not more than t...

Missing_Encryption_of_Sensitive_Data
/app/data/user-dao.js: 21
Attack Vector

Missing_Encryption_of_Sensitive_Data
/artifacts/db-reset.js: 31
Attack Vector

Missing_Encryption_of_Sensitive_Data
/artifacts/db-reset.js: 23
Attack Vector

Missing_Encryption_of_Sensitive_Data
/artifacts/db-reset.js: 15
Attack Vector

Missing_Encryption_of_Sensitive_Data
/app/data/user-dao.js: 105
Attack Vector

Missing_Encryption_of_Sensitive_Data
/app/data/user-dao.js: 92
Attack Vector

Missing_Encryption_of_Sensitive_Data
/app/data/profile-dao.js: 65
Attack Vector

Missing_Encryption_of_Sensitive_Data
/app/data/profile-dao.js: 62
Attack Vector

Missing_Encryption_of_Sensitive_Data
/app/data/profile-dao.js: 53
Attack Vector

Missing_HSTS_Header
/app/routes/allocations.js: 25
Attack Vector

Privacy_Violation
/app/routes/session.js: 53
Attack Vector

Privacy_Violation
/app/routes/session.js: 53
Attack Vector

Privacy_Violation
/app/routes/session.js: 53
Attack Vector

Security Opt Not Set
/docker-compose.yml: 4
Attribute 'security_opt' should be defined.

Security Opt Not Set
/docker-compose.yml: 13
Attribute 'security_opt' should be defined.

Chown Flag Exists
/Dockerfile: 13
It is considered a best practice for every executable in a container to be owned by the root user even if it is executed by a non-root user, only e...

Container Capabilities Unrestricted
/docker-compose.yml: 4
Some capabilities are not needed in certain (or any) containers. Make sure that you only add capabilities that your container needs. Drop unnecessa...

Container Capabilities Unrestricted
/docker-compose.yml: 13
Some capabilities are not needed in certain (or any) containers. Make sure that you only add capabilities that your container needs. Drop unnecessa...

Cpus Not Limited
/docker-compose.yml: 4
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests

Cpus Not Limited
/docker-compose.yml: 13
CPU limits should be set because if the system has CPU time free, a container is guaranteed to be allocated as much CPU as it requests

Healthcheck Instruction Missing
/Dockerfile: 1
Ensure that HEALTHCHECK is being used. The HEALTHCHECK instruction tells Docker how to test a container to check that it is still working

Missing_CSP_Header
/app/routes/allocations.js: 25
Attack Vector

Using Unnamed Build Stages
/Dockerfile: 11
This query is used to ensure that build stages are named. This way even if the Dockerfile is re-ordered, the COPY instruction doesn’t break.

Fixed Issues

Severity
Issue
Source File / Package

CVE-2021-35065
Npm-glob-parent-2.0.0

CVE-2021-35065
Npm-glob-parent-3.1.0

Cx3ec48c7c-8c0c
Npm-handlebars-4.0.5

Cx6f6f1276-7a2e
Npm-tar-2.2.1

Cx9b722ba4-719b
Npm-handlebars-4.0.5

Cx65603961-769c
Npm-debug-4.1.1

Cx65603961-769c
Npm-debug-2.6.9

Cx65603961-769c
Npm-debug-3.2.6

Cx65603961-769c
Npm-debug-2.2.0

Chown Flag Exists
/Dockerfile: 13

Healthcheck Instruction Missing
/Dockerfile: 1


Extra page with years

There was an extra pages with disabled years on datepicker when i try to set for example minDate as 11/12/2001 and maxDate as 11/12/2016.
http://prntscr.com/7yu7uw

Confirmed: http://jsfiddle.net/zcvq0yhh/2/


why .form-control is required?

there may be number of cases when this is not possible due to form markup. One possible solution is to use *[name] instead .form-control['name']
seems it breaks only one spec which tests .form-control class for existence. So there is no reason to restrict to .form-control.
just one of use cases may be directives similar to ui-select or other no standard form controls.

+1 because not requiring form-control would also mean that this would work on bootstrap radio buttons, which was added in 2.2.0 but reverted away from in 2.3.0.

FYI, this was broken to fix #13.


Solve Opera Bug

Opera loads and runs the extension fine,
<!DOCTYPE html><html><head><tit... in options gives a security error...? Stemmed from #17.

I'm having a really hard time replicating this, but it looks like Chrome does it to. You need to gulp and import the dist as an unpacked plugin. On the first rule match, the page throws a unsafe script error, but erasing that match and trying it again doesn't replicate it - it's only a fresh reinstall.
Anyone have any hints? The extension works just fine, but the error is on anonymous function on line 1 of options.html (even when it's unpacked - <DOCTYPE> declarations don't much look like an anonymous function to me). I'm stumped.


fix: single-character-flags with values are now supported

Youtube-dl does not support -foo=bar styled single-character-flags.
This commit disables such styling completely, by using spaces instead of =

@foxscore thanks for this, I added github action on master, can you rebase it?

@foxscore thanks for this, I added github action on master, can you rebase it?

First time doing this, so it took a while.

@Kikobeats I also updated the test\args.js file, as to match the new style format (the checks failed for that exact reason)


Stub migrations

Convert migration files to stub and generate the migrations on install

Functions added on this commit: https://github.com/anibalealvarezs/projectbuilder-package/commit/f5a797f46fc73ba4e6a9dddca77b5e2f443915a4


Adyen Highly Recommended 3DS2 fields and Risk Product fields

Is your feature request related to a problem? Please describe.
Adyen recommends sending the shopperEmail when performing 3DS2 but mention in the documentation that it should be captured beforehand.  Business channels integrating are complaining why the Drop-in component would support Billing Address but not other fields for this purpose.
Describe the solution you'd like
Adyen Drop-in to allow capturing of recommended fields like shopperEmail so they are not captured seperately outside the Drop-in
Similarly the Risk product has a set of required fields which includes shoppername and telephone and delivery address.
For the Drop-in widget to be an all-in one widget solution should it not allow capturing of all highly recommended fields for 3DS2 and support the fields required for the standard Revenue Protect product?
Describe alternatives you've considered
Having business units implement themselves but experiencing understandable resistance to this.
Additional context
For Email Adyen documentation even states it should be collected beforehand as it is required by schemes. This is a good case to include in the Drop-In

Hi @Philip-Hel - to be clear, is this related specifically to the Credit Card component?

Hi @sponglord
Thanks for the response, I have taken that into consideration for the general request around the fields.
Specifically Considering the credit card component and shopperEmail.    Why is billingAddress different from shopperEmail.  Both are required for 3DS2 per the API Explorer info?
See in both images API Explorer clearly state they are required for 3DS2.

Hi @Philip-Hel - We explicitly have the option to ask for billingAddress in the card component because we need that for AVS checks.
Regarding 3DS2  - according to EMVCo, billingAddress is required unless local regulations restrict sending it. However, merchants can choose not to send it even if there's no restriction from local regulations, but schemes suggest sending it for lower challenge rate and higher conversion rate.
And the same applies to shopperEmail


Search functionality

I actually don't want to add any additional UI to the component itself, but I think it would be good to accept a "search" prop and then filter accordingly. I'd even handle the debouncing, so the external Search input can be pretty simple.

Solved by #39


Exception when running async_server

We observed this error in our app. I have not figured the root cause. This is definitely not caused by load as I can see that the transactions are less frequent.
terminate called after throwing an instance of
'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >'
what():  remote_endpoint: Bad file descriptor

Hi @carun -- can you provide details, like what version of Boost you're using, what version of cpp-netlib, using what compiler? Also, if you can provide a means of reproducing it, it will increase the chances for actually getting it fixed.

Hi @deanberris, the issue happened on production box (running on docker) to which we don't have any access. I'm unable to reproduce it locally. I'll update if I manage to reproduce it.
OS: Ubuntu 16.04 (64 bit).
Compiler: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
We use Boost (1.58) and cpp-netlib (0.11.2) are packed with the distro. So we don't custom build against the latest versions.

Thanks @carun -- while I'm happy to see whether we can patch 0.11-devel (if users actually require this version, then it still makes sense to support it longer term) it may be that we'd need to find a few volunteers to back-port fixes to bugs from newer versions back to 0.11-devel. I currently do not have time to do this myself, but I'm still happy to do code reviews if you (or someone else) were willing to do some of it.

@deanberris Sure. I will keep you posted in any case. Thanks for your help.

This doesn't happen on 0.13-release branch, so closing the issue.


Breaking change in 2.0.10 ?

Hi,
I just upgraded to 2.0.10 and renaming Hole broke neverland. Or did I miss something?
P.S.: I just started with neverland/lighterhtml and I appreciate the experience so far, thanks!

uhm ... a rename should've not broken anything, but I'm on it, and apologies for the issue

I'm also testing out parcel 2 (beta) and rollup at the same time. But reverting to 2.0.9 fixed my issue.

If it turns out to be a breaking change, could you deprecate 2.0.10 and publish a 2.0.11 (same as 2.0.9, basically) + a 3.0.0 version with the rename? I think this should be the way to move forward.

is 2.0.11 ok? I've just published it

I'm super sorry, I was sure Hole was a direct export, and I've messed up. Thank you so much for filing this right away, so I could revert the change right away.

Yes, just tested and it's all good now. Thanks for the quick response!

No, thank you!

P.S.
npm deprecate<EMAIL_ADDRESS>'I have messed up a rename'

so not 2.0.10 is properly deprecated 👋

Indeed https://www.npmjs.com/package/lighterhtml/v/2.0.10


World Get - Using Model[] models

Example...
public static Prop GetClosestProp(Vector3 position, float radius, params Model[] models)
models is converted to a ModelHash list.
Since the storage of a hash list is simpler than the storage of whole models.
Would it not make sense for these functions to expect a ModelHash list.
Then instead, expose the ModelListToHashList function for those who are working with whole models.
If in an example i was to spawn a vehicle using...
Create Model from Hash.
Create Vehicle from Model.
Store ModelHash.
Dispose of Model.
I can not use the Dispose of Model, since i will need this to later locate the vehicle in World.GetClosestVehicle().
Or i will need to generate a new model to be passed to World.GetClosestVehicle()
even though World.GetClosestVehicle() does not need a model.
Model[] models = Array.ConvertAll<VehicleHash, Model>(StoredVehicleHashes.ToArray(), hash => new Model(hash));
Please correct me if i am wrong :)

The idea behind using params is to make it easier for the user

It shouldn't be too difficult to convert the function to accept a ModelHash array as the third parameter, and then provide an overload for a Models[] parameter that calls the ModelHash version.

That would make sense then both options can be kept but simplified.


[New Port Request] PJSIP (include PJSUA)

Library name: PJSIP
Library description:
PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. It combines signaling protocol (SIP) with rich multimedia framework and NAT traversal functionality into high level API that is portable and suitable for almost any type of systems ranging from desktops, embedded systems, to mobile handsets.
Source repository URL: https://www.pjsip.org/
Project homepage (if different from the source repository):
https://github.com/pjsip/pjproject.git
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


Update configure-endpoints-gp.md

Updated the doc as environments that have NTLM disabled will have problems using the NetBIOS name.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5787

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5785

@mjcaparas Please merge this PR. Thanks


Clean up the OSB client

Fixes #883
Fixes #884
Replaces #885 (which was reverted)
Replaces #886 (which doesn't work the way it appears)

Stops sending request body on delete
Deals with query parameters in a more idiomatic way

The previous way worked only via use of format strings and that does not at all account for query parameter values that must be url-encoded

Also once you remove sending the body in last operation poll, you need to remove L102 in fake_** that fails if there's no body.

I'm glad to see this patch, but I do not think that the broker api client should live in our repo long term, or for much longer. I've been whittling on a replacement for our client here: https://github.com/pmorie/go-open-service-broker-client (note: this is WIP and i have taken a couple days off. Should have test coverge at about 90% in the next couple days).  I will definitely be incorporating the changes in this PR.

For the record, I do not mean to imply at all that i am against is patch, just trying to disclose fully :-)

LGTM if CI is happy


[Share-ng root endpoint]Can't update expiration date for shared project drive

Describe the bug
user attempted to modify the expiration date of a shared project drive but encountered a 500 status code. However, when trying to update the expiration date with a specific role, a 200 status code was returned successfully. Therefore, the issue seems to be related to changing the expiration date alone.
Steps to reproduce

create project project1
share project project1 using POST /drives/{driveID}/root/invite with expiration date
update share permission expiration date using PATCH /drives/{driveID}/root/permissions/{permissionID}

curl --request PATCH 'https://localhost:9200/graph/v1beta1/drives/480b89c5-bc98-4278-a659-da42d2e92589$aa2c1f37-8aed-4ab5-a800-169fec41256e/root/permissions/u:4c510ada-c86b-4815-8820-42cdf82c3d51' \
--data '{
    "expirationDateTime":"2025-07-15T14:00:00Z"
}'
-------------------Response ----------------------
{
    "error": {
        "code": "generalException",
        "innererror": {
            "date": "2024-04-19T09:13:42Z",
            "request-id": "amrita-OptiPlex-3090/nysBpiUMXC-001893"
        },
        "message": "rpc error: code = Internal desc = runtime error: invalid memory address or nil pointer dereference"
    }
}

Expected behavior
expiration date should be able to be modified
Actual behavior
expiration date should changed if body contains role value only similar to body containing both role and expiration date
curl --location --request PATCH 'https://localhost:9200/graph/v1beta1/drives/480b89c5-bc98-4278-a659-da42d2e92589$aa2c1f37-8aed-4ab5-a800-169fec41256e/root/permissions/u:4c510ada-c86b-4815-8820-42cdf82c3d51' \
--data '{
    "roles":["58c63c02-1d89-4572-916a-870abc5a1b7d"],
    "expirationDateTime":"2025-07-15T14:00:00Z"
}'
--------------------Response----------------
{
    "expirationDateTime": "2025-07-15T19:45:00+05:45",
    "grantedToV2": {
        "user": {
            "displayName": "Albert Einstein",
            "id": "4c510ada-c86b-4815-8820-42cdf82c3d51"
        }
    },
    "id": "u:4c510ada-c86b-4815-8820-42cdf82c3d51",
    "roles": [
        "58c63c02-1d89-4572-916a-870abc5a1b7d"
    ]
}

Setup
Please describe how you started the server and provide a list of relevant environment variables or configuration files.

OCIS_XXX=5.1.0-prealpha+78202793d2

Additional context
Add any other context about the problem here.

Fixed by the reva PR https://github.com/cs3org/reva/pull/4656


Avoid keeping references to local op metadata in pending state manager

Description
We currently store the entire pending message in savedOps despite not needing its local op metadata at usage. We noticed this memory leak in some SharedTree usage, which puts a copy of the tree's schema in local op metadata (schema has cheap copy, but still seemed reasonable to fix).

TODO this needs a test.
I also wonder if we can do any better than only clearing savedOps entirely on resubmit.

I also wonder if we can do any better than only clearing savedOps entirely on resubmit.

We can't today, as on replay we assume the client id of the clients who'd ops we stashed, so we need to replay all the ops of that client even if they were ack'd


Hosts can be removed / re-added prematurely

In iml-agent-comms we are overly-aggressive when removing hosts.
Instead of removing and re-creating the hosts, we should only look to clear out any stale sessions.
Fixes #876.
Signed-off-by: Joe Grund<EMAIL_ADDRESS>

Codecov Report

Merging #877 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #877   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

Continue to review full report at Codecov.

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


fix: set instant from inputs in NumericalSolver::integrateTime

@kyle-cochran I believe L120 has already been addressed?
And L258 cannot be done via setting the endInstant as it is a condition based solve, so we do not know when the end Instant is. The provided end Instant is a maximum propagation time that is used to prevent infinite loops.


fix: empty intercept list item sizing bug

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


simple example to demonstrate export to pdf action

Coverage remained the same at 98.567% when pulling 81fc9ea58b0088e08a2a9abdb3cc73ff1b5abfe0 on CarlyLanglois:example/export-pdf into 787d7641ff5d5dd8d4b0e170580b8747af8728a0 on boundlessgeo:master.

closed. feature added in sdk-iron repo, pr #20.


Require Chef 12.14 and remove yum dep

Remove some old Chef 11 compatibility code in the metadata. Require a mildly current Chef 12 release and yank the yum dep. Remove duplicate apt deps. Cleanup docs for cookbook deps.

@jlruizmlg  can we get this merged?

@devsibwarra should be good to go now thanks to @curiositycasualty

Hi @tas50, @curiositycasualty,
Thank you for contributing to Wazuh; Wazuh really gets improved by the community proposals and contributions.
This PR's changes are considered outdated due to the huge amount of changes and refactoring we added to the repository of wazuh-chef, so we will close it.
Kind regards,
Rshad


Refactor Readme.md

Rewrite readme.md as a stylised welcome page.
Can take notes from any of the top forked/starred repos.

Use/Submit PRs to the readme branch for this issue.


FLUX transactions

Overview
Implement Flux transactions and broadcasting
Outcome
Fully functioning Flux transactions with tx signing and broadcasting

closed in #25


fix: race condition with sync.WaitGroup

Codecov Report

Merging #8 (db40ed7) into main (6f5a675) will decrease coverage by 1.27%.
The diff coverage is 95.34%.

@@            Coverage Diff             @@
##             main       #8      +/-   ##
==========================================
- Coverage   92.45%   91.17%   -1.28%
==========================================
  Files           3        5       +2
  Lines          53       68      +15
==========================================
+ Hits           49       62      +13
- Misses          2        4       +2
  Partials        2        2

Impacted Files
Coverage Δ

shutdown_on_interrupt.go
87.50% <87.50%> (ø)

application.go
95.23% <100.00%> (-0.42%)
:arrow_down:

util.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Exclusive fullscreen capability detection is not accurate

It has regressed and doesn't show that I'm running exclusive fullscreen on an Intel iGPU anymore.
Running git bisect on osu-framework points to 17 commits in PR https://github.com/ppy/osu-framework/pull/5483 as potential first bad commits.
Here's a description of the process I followed to arrive at it:
First of all, osu.Framework.Tests didn't log the exclusive fullscreen capability properly until a later commit, which is way after the regression occured, but it would display in osu!, so I ran git bisect on the osu! repo first, starting from https://github.com/ppy/osu/pull/20506 and got until the point where exclusive fullscreen detection was wrong (a framework bump)
osubisect.log
Then, once I was on that commit, I noted down framework version from osu.Game.csproj, executed .\UseLocalFramework.ps1, and tested two versions of osu-framework, 2022.1219.0 and 2022.1216.1, confirming that the latter was functioning correctly.
Afterwards I ran git bisect on osu-framework for those tags and tested osu! on each specific commit to narrow it down. I had to do git bisect skip on a bunch of commits that didn't build individually (neither osu.Framework.Tests nor osu.Desktop), and this is the resulting git bisect log:
frameworkbisect.log

I have asked a friend w/ an Nvidia GPU to check the latest osu! release and they confirmed Exclusive Fullscreen capability is being detected properly on their end, which makes me believe this has something to do with an Intel specific check introduced in https://github.com/ppy/osu-framework/pull/5432 failing after the PR mentioned in OP.

Which renderer? It's known to not work under direct x, for instance.

OpenGL (Legacy). I have made sure to always be on it at every bisect step, since the check is supposed to work only on OpenGL (Legacy)

Just to make sure (since neither framework nor osu! log or show which renderer they use at that point in time), I used RenderDoc to see which API the game is using. I also used PresentMon to check whether the game is entering the same Present Mode
Before the PR:

After:


Static class field allows colon value with no assignment

🔎 Search Terms
static
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about static

⏯ Playground Link
https://www.typescriptlang.org/play?#code/MYGwhgzhAEBiD29oG8BQ0PQgFzNglsNAEZgBOAXNNmQK4CmA3KgL6qrDwB2E8I9AOhDwA5gAoE8AaTIBKRtAD0i6LS4ATegDN8XeutRA
💻 Code
class Foo {
    static bar: true;
}

console.log(Foo.bar); // undefined

🙁 Actual behavior
I spotted this in production code.
The developer intended to write
class Foo {
    static bar = true;
}

which makes sense. TypeScript gives no errors or warnings with the colon-value. While you can use a colon to specify a type when assigning a value, that does not seem to be what is happening here. I can see no reason why anyone would intentionally write the original code.
🙂 Expected behavior
TypeScript reports an error.
Additional information about the issue
No response

This technically may not a bug but a missing feature.  In any case, duplicate of https://github.com/microsoft/TypeScript/issues/27899.

I can see no reason why anyone would intentionally write the original code.

It can sometimes make sense to write code like this, if you intend to do the actual initialization in a static block:
class Foo {
    static bar: boolean;
    static {
        bar = isBar();
    }
}

Note that true is a valid literal type; in fact boolean is equivalent to true | false.

Closing as duplicate.


[Bug] effectScatter-bmap，Downloading the sample will not open and will not display. Importing Angular from the sample code will not display

Version
5.3.1
Link to Minimal Reproduction
https://echarts.apache.org/examples/zh/editor.html?c=effectScatter-bmap
Steps to Reproduce
effectScatter-bmap，Downloading the sample will not open and will not display. Importing Angular from the sample code will not display
https://echarts.apache.org/examples/zh/editor.html?c=effectScatter-bmap
Current Behavior
effectScatter-bmap，Downloading the sample will not open and will not display. Importing Angular from the sample code will not display
https://echarts.apache.org/examples/zh/editor.html?c=effectScatter-bmap
Expected Behavior
effectScatter-bmap，Downloading the sample will not open and will not display. Importing Angular from the sample code will not display
https://echarts.apache.org/examples/zh/editor.html?c=effectScatter-bmap
Environment
effectScatter-bmap，Downloading the sample will not open and will not display. Importing Angular from the sample code will not display

https://echarts.apache.org/examples/zh/editor.html?c=effectScatter-bmap

Any additional comments?
effectScatter-bmap，Downloading the sample will not open and will not display. Importing Angular from the sample code will not display
https://echarts.apache.org/examples/zh/editor.html?c=effectScatter-bmap

This example uses Baidu Map, please make sure this service is available in your area.
Please you have uncommented these two lines and replace the ak with your own.

<script type="text/javascript" src="https://api.map.baidu.com/api?v=2.0&ak=<Your Key Here>"></script>
<script type="text/javascript"<EMAIL_ADDRESS>

Presents version 13
Echarts version 5.3.1 was introduced
Add it to angular.json
"node_modules/echarts/dist/echarts.min.js",
"Node_modules/echarts/dist/extension/bmap js." "
Added to main.ts
import * as echarts from 'echarts/core';
import 'echarts/dist/extension/bmap.min.js';
import _m from 'echarts/extension-src/bmap/BMapView';
import _v from 'echarts/extension-src/bmap/BMapModel';
import { version } from 'echarts/extension-src/bmap/bmap';
Added to module
NgxEchartsModule. ForRoot ({
echarts
}),
Added to index.ts

The map is still not displayed。。。。

@18336380660 Please describe your problem with more detail. Like any errors in the console?

There is no exception on the console


The book does not get published properly

As pointed out by @therealprof the book is supposed to be published after merges to master branch using https://github.com/rust-embedded/discovery/blob/master/ci/after-success.sh .
Unfortunately, at least from May 2020 the book was not updated on https://docs.rust-embedded.org/discovery/ .
For example, the following 3 PRs are not reflected on the website: https://github.com/rust-embedded/discovery/pull/179, https://github.com/rust-embedded/discovery/pull/148 and https://github.com/rust-embedded/discovery/pull/252 .
https://github.com/rust-embedded/discovery/tree/gh-pages gets updated, but not the website itself.

OK. I think I see what happens. https://docs.rust-embedded.org/discovery/ does not get updated, but https://rust-embedded.github.io/discovery/ does get correctly updated.
https://github.com/rust-embedded/docs is supposed to somehow rebuild 3 books (embedded, discovery, and embedonomicon), but does in practice.
Somewhat related issue: https://github.com/rust-embedded/docs/issues/23

I think that might be linked to https://github.com/rust-embedded/docs ?

This issue is a duplicate of https://github.com/rust-embedded/wg/issues/457

@therealprof Can you please take a look https://github.com/rust-embedded/docs/pull/24 ? Thanks.

Closed by https://github.com/rust-embedded/docs/pull/24


Feature enhancements (provide more variables to mustache templates)

PR for #91.
Provides the following additional variables to mustache templates (with a few other minor changes):

Variable Name
Type
In
Condition

hasBodyParameters
Boolean
method
If one or more parameters are in body (parameter.in === "body")

hasPathParameters
Boolean
method
If one or more parameters are in body (parameter.in === "path")

hasQueryParameters
Boolean
method
If one or more parameters are in body (parameter.in === "query")

hasHeaderParameters
Boolean
method
If one or more parameters are in body (parameter.in === "header")

hasFormDataParameters
Boolean
method
If one or more parameters are in body (parameter.in === "formData")

hasFormDataParameters
Boolean
method
If one or more parameters are in body (parameter.in === "formData")

hasBodyParameters
Boolean
parameter
If a schema is present and is of type "object" (parameter.schema.type === "object")

bodyParams
Array
parameter
If parameter.hasBodyParameters === true and parameter schema properties are defined. Array contains objects are in JSON Schema v4.0 format with an added parameter name.

hasSingularBodyParameter
Boolean
parameter
If a schema is present and is of type "number", "string", or "array" (parameter.schema.type === "number/string/array")

bodyParam
Object
parameter
If parameter.hasSingularBodyParameter === true. Only contains the type of the parameter.

typeIn
Array
bodyParam
If bodyParams are included and the defined type is an object or array of types, rather than a single type.

responses
Array
method
If responses are defined for the method.

security
Array
method
If security definitions are included for the method.

Wow, that table did not format correctly. This is what it should look like:
Provides the following additional variables to mustache templates:

Variable Name
Type
In
Condition

hasBodyParameters
Boolean
method
If one or more parameters are in body (parameter.in === "body")

hasPathParameters
Boolean
method
If one or more parameters are in body (parameter.in === "path")

hasQueryParameters
Boolean
method
If one or more parameters are in body (parameter.in === "query")

hasHeaderParameters
Boolean
method
If one or more parameters are in body (parameter.in === "header")

hasFormDataParameters
Boolean
method
If one or more parameters are in body (parameter.in === "formData")

hasFormDataParameters
Boolean
method
If one or more parameters are in body (parameter.in === "formData")

hasBodyParameters
Boolean
parameter
If a schema is present and is of type "object" (parameter.schema.type === "object")

bodyParams
Array
parameter
If parameter.hasBodyParameters === true and parameter schema properties are defined. Array contains objects are in JSON Schema v4.0 format with an added parameter name.

hasSingularBodyParameter
Boolean
parameter
If a schema is present and is of type "number", "string", or "array" (parameter.schema.type === "number/string/array")

bodyParam
Object
parameter
If parameter.hasSingularBodyParameter === true. Only contains the type of the parameter.

typeIn
Array
bodyParam
If bodyParams are included and the defined type is an object or array of types, rather than a single type.

responses
Array
method
If responses are defined for the method.

security
Array
method
If security definitions are included for the method.

After a few commits, jshint is happy. Please let me know how you feel about the changes.

Another variable that has been added is mainResources, which has been added to the global "data" variable. This basically provides an arranged list of the methods by the first part of the path.
For example, if the following paths are included in the Swagger spec:
/users/{id}
/posts/{id}

There would be two entries in mainResource, each with a subset of methods. This allows the mustache templates to group resource definitions into, for example, various classes.

@mm-gmbd What is the motivation of providing these variables? Could you give me an example?

@wcandillon, more variables == more flexibility for custom templates, no?
I've already provided reasoning for the mainResources variable. It essentially provides method grouping by a common base portion of the path.
The motivation behind the hasXXXXParameters variables was to allow to format the auto-generated code differently based on whether or not that type of parameter existed. For example, if no body parameters existed, I may want to generate "null" rather than an empty array or object. Also, this helps with formatting of code differently when one chooses to set beautify to false, which I have done.
The reason for bodyParams is explained in #91 (and the hasBodyParameters that is a part of parameter, hasSingularBodyParam, and typeIn, are all inherently included for the same reason). The inclusion of these variables allows for auto-generated client-side validation of body parameters, which was not possible before.
The responses seem to have completely been left out of the template variables, so with the inclusion of responses by method, response handlers for the various possible responses can be auto-generated.
Also, security was in the same boat as responses -- now client-side validation of security can be enforced. For example, if security for a method was set to oauth2, but the headers did not include the correct security parameters, this could be detected (in an auto-generated fashion) on the client.

@wcandillon, any further thoughts on this? Thanks!

@wcandillon, just dropping a note on this, wondering if you'd looked into this any further. Happy new year!

+1 on this.  This would be really useful for not only validating body parameters but also building the body when there are additional readonly attributes of the passed in object for the body.


Capsule proxy not validating the user requests after certain time after the Kubernetes upgrade to 1.30.1

Bug description
Capsule proxy requests are rejected with 401 unauthorized error . The user get this following error
Error: error validating "STDIN": error validating data: failed to download openapi: the server has asked for the client to provide credentials; if you choose to ignore these errors, turn validation off with --validate=false
To fix temporarily , we have to restart the capsule proxy pod every one hour. So whenever the pod get restarted , the users not facing any issue for about 40 to 50 mins.
How to reproduce
Steps to reproduce the behavior:
Expected behavior
The user requests are validated and authorized without any error
Logs
No logs apart from this , we have enabled log level 10
{"level":"Level(-4)","ts":"2024-11-28T13:15:44.994Z","logger":"proxy","msg":"impersonating for the current request","username":"1e3b32dc-7117-47eb-8efc-488dd0ea7d12","groups":["7cadb0b3-8d95-4a7b-a2c3-1883a7387756","0ac5bef3-d2f4-4139-a7b8-8ec12b7ff0a8","system:authenticated"],"uri":"/openapi/v2"}
{"level":"Level(-5)","ts":"2024-11-28T13:15:44.994Z","logger":"proxy","msg":"debugging request","uri":"/openapi/v2?timeout=32s","method":"GET"}
Additional context

Capsule-Proxy version: 0.7.0
Helm Chart version: capsule-proxy-0.7.0
Kubernetes version: 1.30.1

I'd say this is a duplicate if #565, may I ask you to give a try with the v0.8.0 release, please?

#565

@prometherion  Thanks for sharing the other related bugs. But I dont see version 0.8.0 released .

Sorry but I'm not getting your point: v0.8.0 has been released using GitHub releases, as well as OCI image hosted on GHCR and related Helm Chart.

Thanks @prometherion , I found the latest version and deployed as a fix in our environments. We will monitor for few days

Thanks, feel free to open this in case the issue persists!


ruby-grafana-reporter does not listen to <IP_ADDRESS> and only listen at ::1 no other way to change to custom binding address

as I mentioned in the title, the web service only listen to ::1 at port we can configured.. but I could not configured the binding address. I am not sure if this is intended for security or something else. I also could not find any reference on the documentation.

Currently it is only possible to configure the webservice-port in your configuration file. So listening to port 1, as you mentioned looks like this has been configured in your personal config file, correct?
Anyway: configuring another address is not possible. Could you maybe describe, what you would like to achieve? At first glance your requirement could be met by adding NGINX proxy in front of your server.

Currently it is only possible to configure the webservice-port in your configuration file. So listening to port 1, as you mentioned looks like this has been configured in your personal config file, correct?
yes
Anyway: configuring another address is not possible. Could you maybe describe, what you would like to achieve? At first glance your requirement could be met by adding NGINX proxy in front of your server.
it would be easier just to change the binding address.. anyway.. I did try with nginx.. but encounter some error.. never mind.. I will look at it later..


New OS, new arch, automated builds

I'm happy to add your platform/arch as amount of assets isn't limited on gh! :smiley:
On wiki there is summary of current and eventually future OSes and arches.
Before you go:

There must be also a C and C++ compiler as some dependency uses them
Before you request, see rust platform support page if rust compiles there
Pull Requests are much more welcome than do-it-for-me request
If you want me to register somewhere where you have custom runers etc. Don't expect me to do so in the first place as I would rather stay without additional mess and yet another company stealing my data.
32-bit architectures aren't accepted, generally only modern ones are good to go
Other architectures than amd64 and aarch64 won't be included in the table because it lowers its readability
Generally build systems rarely supports anything other than amd64/aarch64 so if you want to do cross-compilation, you need to make sure you set up all tools and envs properly
Linux builds won't be ever made on Debian-based distros because of dramatically outdated stuff. Sth. like Fedora/Void/Arch are good to go
Make sure rust toolchain in repo is new enough, else use rustup
Workflow must include calculating and uploading sha256 hash
packages like deb rpm aren't accepted as workflow with assets, because whole sense of packages are signing them by the repo owner.
if you want a package for your platform, please prepare a template.

In this issue, there will be log and update of changes regarding oses and arches

Added windows aarch64 builds

Regression: Removed DragonflyBSD builds, rust tier 3 support, version from dfly repo is too old.

Regression: Leaved unchanged: Linux musl aarch64, linking with 'cc' failed see upstream issue

Info: Successful native builds on OpenSUSE Tumbleweed for:

armv6l
armv7l
i586
ppc64
ppc64le
s390x

see build on OBS

Info: OpenBSD vmactions runner has been fixed, support will be added with release 0.1.4+


Fix typo in README.md

Pull Request Test Coverage Report for Build 338969901

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

Totals

Change from base Build 337974133:
0.0%

Covered Lines:
259

Relevant Lines:
623

💛  - Coveralls

Good catch! Too easy to only read what you expect to be there when checking ones own writing.


Updated AV interop section to include Defender

@SibonayK : Thanks for your contribution! The author, @wmgries, has been notified to review your proposed change.

@Sibonay, can you close this PR and open in the private repo (azure-docs-pr)? You're supposed to as a Microsoft employee. Also, put "Resolve: " that way when it merges it auto-resolves.


Support nodeos 1.8 send_transaction

nodeos 1.8 adds /v1/send_transaction to replace the legacy /v1/push_transaction.
push_transaction reproduces the legacy trace format; this increases the load on nodeos.
send_transaction produces the new trace format.
See Issue 539 in the eosjs repo.

See: https://github.com/EOSIO/eosjs/pull/545
See: https://github.com/EOSIO/eosjs/issues/539

Resolved in https://github.com/EOSIO/eosio-swift/pull/232.


Initial version of basic Material Design based header and app drawer

Fixes #29

Demo: https://jonas.github.io/metadoc/

Looks like it also improves mobile somehow

I just tested this locally. I really like the new look. Would it make sense to change the white background in the drawer when changing the theme to dark?

Another thing I noticed, which may be unrelated to this PR, would it be possible to switch the theme by clicking anywhere on "theme" form field? Currently, it only switches when clicking on the slider, but not for example when clicking on "Editor theme"

Thanks for testing. Yes, it makes sense to change the background for the dark theme and I will see if I can make the toggle change when clicking anywhere. BTW, I tried to change the toggle to a select so we can also provide the hc-black theme, but was not able to get the select component working without resorting to a lot of extra boilerplate which makes me wonder if this is the right path to take.

What other forms than theme toggle do we want to put in there? it would be nice to get rid of as much configuration as possible. Also, the big Scalameta logo in the top-left corner above the strong blue background of the sidebar is a bit weird. The small logo next to the filename looks nice, could we get rid of the other logo?

What's the status on this PR? After running locally, I feel it needs a bit more work before merging. We should also discuss whether we need a sidebar or not, ideally we should try to avoid having custom UI options but I suspect we must eventually face the wrath of configuration options.

I'll see if I can move the theme toggling to a menu drop down and remove the sidebar. If all works out we can then add a search button that transforms the titlebar into a search field. It would still look different from Monaco's UI but it is a start.
It's also possible to put overlays in Monaco if we want to create a start page. But for now I will try to make this PR super focused to get the ball rolling.

I'll see if I can move the theme toggling to a menu drop down and remove the sidebar.

That would be super cool. It would be very intuitive to use the monaco search/action bar to toggle the theme. I am also very interested in exploring how to add custom actions to implement services such as "open file by filename" or "go to symbol in workspace" (not only current active document).

@olafurpg Please take another look. It's live here: https://jonas.github.io/metadoc

Wow 😍 much nicer! LGTM 👍
btw, did you know this option already existed in the command palette?

Merging since the build is green after restarting the test script: https://travis-ci.org/scalameta/metadoc/builds/280266870


[Enhancements] Not everything is good to throw away !

Simple idea to not lose all of the items when failing a crafting check.

Nut sure i will think about it:

It is mostlikly a breaking change as the old flag will vanish for several flags on the ingredients and currency.
Also checking or unchecking all like now has then increased complexity, or the uis complexity increase.
Maybe when i invent crafting macros it is more simpler to lose or keep items via macro. ofc this renders this feature for advanced users only as not everyone can or is willing to write macors. I have to think about it.

Aaah. Understood. Let's not ruin a good cake with extra things on it.  I think since Toolkit will be added, I don't need this that much. Thanks for your hardwork and again, that's a really great module !


Why you added fixed "If-Modified-Since" header?

$httpProvider.defaults.headers[method]['If-Modified-Since'] = 'Mon, 26 Jul 1997 05:00:00 GMT'
Why? What this date means? Is it your birthday?
Do you understand how it affects on HTTP caching? You have totally broken all browser caching mechanism. The browser should have an ability to decive what to cache or not, and the server can answer with 200 (content) or 304 (without content) depends on real datetime in this header.


Use different libwbxml methods in C python module

The original  python-wbxml library didn't allow me to communicate with an Exchange server with ActiveSync.
Conversions are now configurable via keyword arguments (see Python docstrings).
I had to integrate the source files of libwbxml within the repo, because some methods that were not available from the publicly available library (libwbxml-dev) were needed.

@mathieurodic i don't have time to review everything currently. I could make you a contributor if you want.

I would be honored ^^

@mathieurodic i made you a collaborator, i am also thinking of just using cffi for easier integration and also if we can enable python3 support.


Persist article references across restarts

Related to https://github.com/libero/prc/issues/32
The assumption is that an article (reference) can exist without any reviews being attached to it, hence we need an independent persistence of these Aggregates. This could be just the article DOIs for example.

We are not doing this as a design choice at the moment, as articles only appear when review or review requests are present.


SCA with Php Inspections (EA Extended)

@keradus : static local variables and newly added preg_quote 2nd parameters are reverted now.
Would you please check if the rest part of the PR looks good?

Thank you @kalessil.

Thank you @kalessil.


[Feature Request] Macro activation when actor with effect is attacked

Hi!
Predefined option for when actor with effect is attacked would be cool (to the selection of Combat started, Combat ended, etc)!
I am trying macro the Sanctuary spell activation (wisdom saving throw).

Being 'attacked' is system specific. What system would this be for?
Secondly, how is 'being attacked' defined in clear Foundry terms?

Oh sorry, let me add more details. :)
System is Dnd5e.
What I mean 'being attacked', is that when a creature/enemy is attempting to roll a attack roll on the actor with the effect. Before the attack roll is made, the effects macro activates. I understand that in Dnd5e system there are multiple ways to attack to the actor with the effect and this may be a bit tricky.

Several issues here.

Rolling an attack "on the actor" is not necessarily applicable, since making an attack roll does not require having a target.
Executing a script on the target's client before the attack is completed is not possible, since the pre-hook would need to be transmitted to the target's client before the roll is completed - this is axiomatically asynchronous, which the dnd5e.preRollAttack hook is not (no hooks are, they cannot be awaited).

An entirely different approach would be needed.

Oh I see. So it would need a change in the system itself. Thanks for the quick responses. :)


Replacing RxJava version 1 with 2

Interesting stuff. I've only quickly gone through this without pulling the branch. There's a handful of small revisions needed. I'll need to confirm the TestSubscriber vs TestObserver usage too.

@tomaszpolanski I've two more review comments about making sure that Disposables are added to the Composite in bind().


The DNS resolver may uncontrollably flood daemon.log

I have discovered this morning that my daemon.log is some 36G after seemingly failing to resolve the master server overnight.
While I have not been able to analyse the 36G daemon.log because I had to restore a backup of my VPS I surmise that it was caused by this as the stdout was flooded with the following message:
Failed to resolve hostname
before daemonded finally died with:
terminate called after throwing an instance of 'std::system_error' what():  No space left on device after my VPS's virtual disk was filled completely.
Please can this be investigated as a matter of urgency - either stop the spam (and enabling logs.suppression.enabled is not the answer because this breaks other things on the server console) or prevent it from logging this garbage to the disk (not really the answer either, because some server owner may run this as a systemd daemon, which means it would just flood the journal anyway).

I don't know how to reproduce. Share your server configuration files?
Do you build daemon with any custom patches?

No custom configuration here aside from logs.suppression.enabled set to 0; it looks like it lost connection to the master server and flooded the log. At the same time, issues were reported with the master server on IRC.

I do, but I don't believe they're relevant to this problem in particular. My cvars are all gameplay related (g_*) aside from setting the sv_maxclients, download settings and hostname.

Looks like this one is also caused by time wrapping. The resolver is written with the assumption that Sys::Milliseconds() will never overflow but it does with the same period as svs.time. Due to implementation details, the time overflow can cause a dummy DNS query with the empty string as the hostname to be looked up triggering the Failed to resolve hostname %s message.
I'll look into making Sys::Milliseconds 64-bit, but it's unlikely I'll find all time overflow related bugs, so your best bet is to configure your server to restart at least once every 24 days.

it does with the same period as svs.time

I should say, this is not quite accurate. The svs.time overflow prevention code triggers after 21.7 days of uptime, but Sys::Milliseconds only overflows after 24.6 days.

I'm thinking the problem where log file size are unbounded is a more generic one though. I'm not sure this is a good idea to allow the gamelogic to fill up the hard drive if it decides.
I remember @bmorel was symlinking the daemon log files to /dev/null because he had a similar problem. So I'm tempted to reopen.

Make a new issue, don't recycle this one

I remember @bmorel was symlinking the daemon log files to /dev/null because he had a similar problem. So I'm tempted to reopen.

I did not had the problem of disk being full, but I did noticed that shitload of logs are kept around for nothing, and symlinked that folder to /dev/null, because this data can also be gathered through stderr and have no value to me.
This problem is not related to this issue though, as it's expected behavior, where this ticket is about a bug.