update to 0.16.2

Updating bicep after bugfix: https://github.com/Azure/bicep/releases/tag/v0.16.2

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

bash:
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196 --version '' --verbose --skip-verify

pwsh:
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/uninstall-azd.ps1' -OutFile uninstall-azd.ps1; ./uninstall-azd.ps1
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/install-azd.ps1' -OutFile install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196' -Version '' -SkipVerify -Verbose

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196' -Version '' -SkipVerify -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/azd-windows-amd64.msi' -OutFile azd-windows-amd64.msi; msiexec /i azd-windows-amd64.msi /qn"

Standalone Binary

Linux -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/azd-linux-arm64.tar.gz

MacOS -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/azd-darwin-amd64.zip
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/azd-darwin-arm64.zip

Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/azd-windows-amd64.zip

MSI

https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2196/azd-windows-amd64.msi

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-2196

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference (preview)
description: This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
author: alexwolftmsft
ms.author: alexwolf
ms.date: 05/12/2023
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference (preview)
This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
azd
The Azure Developer CLI (azd) is an open-source tool that helps onboard and manage your application on Azure
Options
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
  -h, --help         Gets help for azd.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
azd config: Manage azd configurations (ex: default Azure subscription, location).
azd deploy: Deploy the application's code to Azure.
azd down: Delete Azure resources for an application.
azd env: Manage environments.
azd init: Initialize a new application.
azd monitor: Monitor a deployed application.
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines.
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies.
azd template: Find and view template details.
azd up: Provision Azure resources, and deploy your project with a single command.
azd version: Print the version number of Azure Developer CLI.

azd auth
Authenticate with Azure.
Options
  -h, --help   Gets help for auth.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth login: Log in to Azure.
azd auth logout: Log out of Azure.
Back to top

azd auth login
Log in to Azure.
Synopsis
Log in to Azure.
When run without any arguments, log in interactively using a browser. To log in using a device code, pass
--use-device-code.
To log in as a service principal, pass --client-id and --tenant-id as well as one of: --client-secret,
--client-certificate, or --federated-credential-provider.
azd auth login [flags]

Options
      --check-status                           Checks the log-in status instead of logging in.
      --client-certificate string              The path to the client certificate for the service principal to authenticate with.
      --client-id string                       The client id for the service principal to authenticate with.
      --client-secret string                   The client secret for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --federated-credential-provider string   The provider to use to acquire a federated token to authenticate with.
  -h, --help                                   Gets help for login.
      --redirect-port int                      Choose the port to be used as part of the redirect URI during interactive login.
      --tenant-id string                       The tenant id or domain name to authenticate with.
      --use-device-code[=true]                 When true, log in by using a device code instead of a browser.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
Back to top

azd auth logout
Log out of Azure.
Synopsis
Log out of Azure
azd auth logout [flags]

Options
  -h, --help   Gets help for logout.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd auth: Authenticate with Azure.
Back to top

azd config
Manage azd configurations (ex: default Azure subscription, location).
Synopsis
Manage the Azure Developer CLI user configuration, which includes your default Azure subscription and location.
Available since azure-dev-cli_0.4.0-beta.1.
The easiest way to configure azd for the first time is to run azd init. The subscription and location you select will be stored in the config.json file located in the config directory. To configure azd anytime afterwards, you'll use azd config set.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
Options
  -h, --help   Gets help for config.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config get: Gets a configuration.
azd config list: Lists all configuration values.
azd config list-alpha: Display the list of available features in alpha stage.
azd config reset: Resets configuration to default.
azd config set: Sets a configuration.
azd config unset: Unsets a configuration.
Back to top

azd config get
Gets a configuration.
Synopsis
Gets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config get <path> [flags]

Options
  -h, --help   Gets help for get.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config list
Lists all configuration values.
Synopsis
Lists all configuration values in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config list [flags]

Options
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config list-alpha
Display the list of available features in alpha stage.
azd config list-alpha [flags]

Options
  -h, --help   Gets help for list-alpha.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config reset
Resets configuration to default.
Synopsis
Resets all configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable to the default.
azd config reset [flags]

Options
  -h, --help   Gets help for reset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config set
Sets a configuration.
Synopsis
Sets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config set <path> <value> [flags]

Examples
azd config set defaults.subscription <yourSubscriptionID>
azd config set defaults.location eastus

Options
  -h, --help   Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd config unset
Unsets a configuration.
Synopsis
Removes a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config unset <path> [flags]

Examples
azd config unset defaults.location

Options
  -h, --help   Gets help for unset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage azd configurations (ex: default Azure subscription, location).
Back to top

azd deploy
Deploy the application's code to Azure.
azd deploy <service> [flags]

Options
      --all                   Deploys all services that are listed in azure.yaml
  -e, --environment string    The name of the environment to use.
      --from-package string   Deploys the application from an existing package.
  -h, --help                  Gets help for deploy.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd down
Delete Azure resources for an application.
azd down [flags]

Options
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for down.
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd env
Manage environments.
Options
  -h, --help   Gets help for env.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

Back to top

azd env get-values
Get all environment values.
azd env get-values [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-values.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env list
List environments.
azd env list [flags]

Options
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env new
Create a new environment.
azd env new <environment> [flags]

Options
  -h, --help                  Gets help for new.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env refresh
Refresh environment settings by using information from a previous infrastructure provision.
azd env refresh [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env select
Set the default environment.
azd env select <environment> [flags]

Options
  -h, --help   Gets help for select.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env set
Manage your environment settings.
azd env set <key> <value> [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd init
Initialize a new application.
azd init [flags]

Options
  -b, --branch string         The template branch to initialize from.
  -e, --environment string    The name of the environment to use.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       The template to use when you initialize the project. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd monitor
Monitor a deployed application.
azd monitor [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for monitor.
      --live                 Open a browser to Application Insights Live Metrics. Live Metrics is currently not supported for Python apps.
      --logs                 Open a browser to Application Insights Logs.
      --overview             Open a browser to Application Insights Overview Dashboard.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd package
Packages the application's code to be deployed to Azure. (Beta)
azd package <service> [flags]

Options
      --all                  Deploys all services that are listed in azure.yaml
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd pipeline
Manage and configure your deployment pipelines.
Options
  -h, --help   Gets help for pipeline.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline config: Create and configure your deployment pipeline by using GitHub or Azure Pipelines.
Back to top

azd pipeline config
Create and configure your deployment pipeline by using GitHub or Azure Pipelines.
azd pipeline config [flags]

Options
      --auth-type string        The authentication type used between the pipeline provider and Azure for deployment (Only valid for GitHub provider). Valid values: federated, client-credentials.
  -e, --environment string      The name of the environment to use.
  -h, --help                    Gets help for config.
      --principal-name string   The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role string   The role to assign to the service principal. (default "contributor")
      --provider string         The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines).
      --remote-name string      The name of the git remote to configure the pipeline to run on. (default "origin")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline: Manage and configure your deployment pipelines.
Back to top

azd provision
Provision the Azure resources for an application.
Synopsis
Provision the Azure resources for an application.
The command prompts you for the following values:

Environment name: The name of your environment.
Azure location: The Azure location where your resources will be deployed.
Azure subscription: The Azure subscription where your resources will be deployed.

Depending on what Azure resources are created, running this command might take a while. To view progress, go to the Azure portal and search for the resource group that contains your environment name.
azd provision [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd restore
Restores the application's dependencies.
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for restore.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd template
Find and view template details.
Options
  -h, --help   Gets help for template.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template list: Show list of sample azd templates.
azd template show: Show details for a given template.
Back to top

azd template list
Show list of sample azd templates.
azd template list [flags]

Options
  -h, --help   Gets help for list.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details.
Back to top

azd template show
Show details for a given template.
azd template show <template> [flags]

Options
  -h, --help   Gets help for show.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Find and view template details.
Back to top

azd up
Provision Azure resources, and deploy your project with a single command.
azd up [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for up.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd version
Print the version number of Azure Developer CLI.
azd version [flags]

Options
  -h, --help   Gets help for version.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

Maybe we should just go forward to 0.17.1?  I confirmed that neither this (no 0.17.1) solve the issue we were seeing in devcontainers on M1 macs when running under emulation.  I am starting to become more and more confident that the issue with that is related to some bug in .NET 7 itself.

Maybe we should just go forward to 0.17.1

It should be straightforward to update to 0.16.2 as it only adds a hotfix. For 0.17.1, we might need to maybe run all manual tests again?

I confirmed that neither this (no 0.17.1) solve the issue

Then I don't think we should update, as we might need to update again once they fix this.

related to some bug in .NET 7 itself.

Did you try updating/installing .NET for mac? https://learn.microsoft.com/en-us/dotnet/core/install/macos ?  (just curious)


Attach multiple decorators

I was under the assumption that you could attach more than one decorator.
We are attempting to have 2 decorators. One for editing, and one for validating.
Although it appears that you can only have one decorator per element.
So I guess this is a feature request to have more than one decorator per element.
http://jsfiddle.net/M3MkH/

Just searched for this after I ran into the same issue. Perhaps a format of decorator-name="options" and if no options are needed, a simple boolean attribute like, <input decorator-autofill> where name is the exported name of the decorator.

I second @briancray 's suggestion - the decorator-{decoratorName} format kind of matches the on-{eventName} convention.

+1 for decorator-name="options"

Although this is a relatively old topic, I have to agree that this proposed change is at least worth discussing. Perhaps this can be readdressed after the 0.8 release.

Until the use of multiple decorators is supported by Ractive natively, I've create a "Meta"-Decorator, for combining multiple decorators on one element.
In contrast to Ractive-decorator-helpers  you  can use my solution out of the box with your existing decorators, because you don't have to change the way to write your decorators (which I don't like about Ractive-decorator-helpers).
Usage

 Text

Nothing els to do!
Here it is:
/**
 * Meta-Decorator to use multiple decorators on a single HTML-element
 * usage: decorator="combine:{decorator1:[param1, param2], decorator2:param}"
 */
Ractive.decorators.combine = function (node, data) {
	var decoratorName, decorator, parameters;
	var instance = this;
	var decorators = data || {};

	for (decoratorName in decorators) {
		if ((decorator = instance.decorators[decoratorName])) {
			parameters = makeArray(decorators[decoratorName]);
			parameters.unshift(node);
			decorators[decoratorName] = decorator.apply(instance, parameters);
		} else {
			delete decorators[decoratorName];
		}
	}

	return {
		teardown: function () {
			var decoratorName, decorator;

			for (decoratorName in decorators) {
				decorator = instance.decorators[decoratorName];
				decorator.teardown && decorator.teardown();
			}
		},
		update: function (data) {
			var decoratorName, decorator, parameters;

			for (decoratorName in decorators) {
				decorator = decorators[decoratorName];
				parameters = makeArray(data[decoratorName]);
				decorator.update && decorator.update.apply(instance, parameters);
			}
		}
	};
};

@LeJared  brilliant!!

@LeJared how is that different from the multi decorator mentioned a few comments above ? By @martypdx ?

To use the multi decorate from above or Ractive-decorator-helpers  you have to change the way you create and assign your decorators to your Ractive instance. I don't like that, because you can't use exiting decorators out of the box, but have to create special combined versions of your decorators, to use them togethe. This also means, You have to create as create a new "combined decorator" for every combination separately!
Using my solution, you only have to change the way you assign your decorators in then templates and you can use any combinations of any decorators on the fly by just adding them in the template.
Benefit: once, Ractive supports multiple decorators natively, you only have to change your templates (you'll have to do this anyway!) but you don't need to change your decorators them selfs.
BTW: I've fixed a bug in the code above.

@LeJared

you have to change the way you create and assign your decorators to your Ractive instance

I guess the initial idea of @martypdx that was true, but see my comment above, which basically was a slight improvement
https://github.com/ractivejs/ractive/issues/399#issuecomment-64007822
that's how you use it in the template - all other decorators remain the same, and you don't have to create a combination before hand.

Yeah, after I wrote that I realized that you could just look them up from global registry.
What I find interesting is that I have yet to need to double up decorators on an element.

What I find interesting is that I have yet to need to double up decorators on an element.

The only situation where I've needed to double up a decorator is for a 'truncate' decorator, where I also want to have a 'tooltip' decorator on the element. I didn't need to have a multi-decorator plugin, though. I just instantiated the tooltip decorator from the truncate decorator manually. I'm not sure if that strategy is generally applicable however.

@martypdx & @akhoury: Sorry, I missed that. So then both solutions are doing essentially the same.
@martypdx: What do you mean by have yet to need to double up decorators on an element? (Sorry, I'm not native english speaker).

What do you mean by have yet to need to double up decorators on an element?

@LeJared:  I haven't needed a multi decorator.

I slapped up @akhoury's solution as a repo and put it up on npm as ractive-multi-decorator

@JonDum :+1:
Maybe it should be ractive-each-decorator:

Use case for multiple decorators:  I have a list of items that I want to be able to both drag-drop AND click a button to add or remove items from the list.  Would use:

Sortable
Addable (in progress)

@zaus I'm using @JonDum's repo too and works great.

updated @JonDum's repo to avoid unnecessary updates on decorators which arguments haven't changed.

hey @browniefed, may i ask why is this being closed? I thought it was labeled as a future enhancement.
Has it been decided that this feature won't be supported in core?

@akhoury ah sorry I assumed it was already implemented for some reason haha, was cleaning up all my old open issues. Will keep thsi open

This now possible in edge with multiple as-${decorator} directives 😄

BOOYAH.  What version will it be released in?  Is Edge 0.8, 0.9, or even farther out?

Edge is 0.8. I'm planning on cutting an alpha week after next.


Linux version

It would be awesome if we could have a Linux version of Buzz. You could look at AppImage or FlatPak to generate the packages.

Also, this could be of your interest since you are using poetry:
https://github.com/flatpak/flatpak-builder-tools/tree/master/poetry

Yes, would be nice, especially because original whisper is shown by demo on linux.

Hi, yes, Buzz initially had a Linux version, but I had to remove it as it had some bugs, and I could not replicate as I don't have a Linux desktop to test: https://github.com/chidiwilliams/buzz/issues/116. I'll give it another go soon.

Linux is pretty easy to emulate for testing, there is windows subsystem for linux, or you can boot it straight off of a USB or VM.

The app runs on Linux using poetry instructions (tested just now)

As I was unable to easily use this on Linux, I built a similar web-based app which can be used on any platform supporting Docker: https://codeberg.org/pluja/web-whisper


Is there a way to access protected deployed web apps without logging in (with token)?

Is there a way where I can access a deployed protected web app such as with a link: https://script.google.com/macros/s/#######/exec without having to log in? Perhaps with an access token? like https://script.google.com/macros/s/#######/exec?access_token=23423asldkfjsdf? It seems there always has be a user login to access web app.

This seems to be a question about Apps Script, and not this library in particular. In general if you wish to call an Apps Script from another system we recommend you use the Apps Script API:
https://developers.google.com/apps-script/api/how-tos/execute


Sorry if there has been a misunderstanding about how #1065 in involved here, I meant that we backport this patch on top of current release else tests fails, but we already patched for that since 1.6.7.
The error is unrelated and new, it did not occur in 1.7.1. I’m not sure I have tried rebuilding 1.7.1 recently though, I should check whether it does still build fine or if the regression comes from a dependency change.

No problem. We are looking forward to seeing your test result. Let me know when you have a new result.

Same failures on 1.7.1 (+TestDecompression.testLzoLong that was fixed since). So there has been a dependency related change. Since they are not a lot of dependencies involved (I don’t know for this particular tests, but you might be able to tell me), given what changed on our side in this lapse of time, it seems it could be either protobuf (that went from 3.17.3 to 3.19.4) or gcc (11.1 to 11.2). Unfortunately trying older version of those is quite involved, so I’ll not be able to pinpoint any of those if they are the culprit.

According to the context, the root cause is unclear to me either.

The error is unrelated and new, it did not occur in 1.7.1.

Same failures on 1.7.1

Back to the basic, it's hard to consider something as a bug if we cannot reproduce it. In addition, we don't know what you have in your fork or what you have in your Arch Linux build and test system yet. We have four releases like the following. Could you confirm that which tag is the last working tag for you?

https://github.com/apache/orc/releases/tag/v1.7.0
https://github.com/apache/orc/releases/tag/v1.7.1
https://github.com/apache/orc/releases/tag/v1.7.2
https://github.com/apache/orc/releases/tag/v1.7.3

Thank you for the details, @ArchangeGabriel . Given the analysis, I'm closing this issue Tests failure on 1.7.3.
As you mentioned here, we had better restart with a new narrow-downed specific GitHub issue for the specific failure later.


Remove rst compiled doc and notebooks from repository

The current documentation relies on sphinx-gallery which cannot be executed on readthedoc so we have to compile everything to rst and notebooks for a proper documentation.
This will make the repo explode so we should find a way to have an updated doc (staying on readthedoc if possible) probably by keeping a compiled version of the doc on a separate repository.
The compiled notebooks also are very nice (they allow a quick look at how the toolbox works) but should be stored also in a separate repo.

FYI this script:
https://github.com/mne-tools/mne-python/blob/master/circle.yml
builds automatically
http://mne-tools.github.io/stable/index.html


Cleanup all unused Azure resources

All the unused Azure resources needs to be cleaned up

Get control on secrets and certificates!

We should try getting an overview over the overall costs. We have some in Azure and Radix - we should collect and get an overview of this.
Could/should Infra have this overall responsibility?


Add a "landing page" feature to tasks

While you're working on the task features, I'd like to request that tasks have a property that can specify what pane to open when the task completes. For instance, I'd like my test task to land the user on the problems pane to view the problems surfaced by the problem matcher.

Hi @mattmcnabb - I am doing a short user research study on this issue. If you have time this week can you sign up? https://calendly.com/anjfer/vscode

Dups #34094


chore: promote react-spring to version 0.0.20

this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

react-spring
Changes in version 0.0.20
Chores

release 0.0.20 (jenkins-x-bot)
add variables (jenkins-x-bot)

Other Changes
These commits did not use Conventional Commits formatted messages:

debug wolfi 7 (iMckify)
debug wolfi 6 (iMckify)

[jx-info] Hi, we've detected that the pipelines in this repository are using a syntax that will soon be deprecated.
We'll continue to update you through PRs as we progress. Please check #8589 for further information.

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

Needs approval from an approver in each of these files:

OWNERS

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


Chrome debugger: Use port forwarding to open URL when running with a remote

Testing https://github.com/microsoft/vscode-remote-release/issues/754
When the launch config has a url and the window is connected to a remote, the URL should be opened with the same smarts as openExternal() has on the remote side. /cc @mjbvz

What API do you need? A way to force vscode.env.openExternal to use port forwarding even though it is a UI extension?

In this case the chrome debug adapter is running as a UI extension, but it knows the port on the remote. It looks like asExternalUri won't help in this case right?

@roblourens Yes that's correct; the current api would be a noop in that case. Maybe we need a way to force a uri to be resolved as if the extension were remote?

I think this is supported in js-debug


Attempted import error: createColorModeProvider is not exported from @xstyled/core.

🐛 Bug Report
In my React application, I have installed:
 "@xstyled/core": "^3.6.0",
"@xstyled/styled-components": "^3.6.0",
"styled-components": "^5.3.5"

and I got this error:

To Reproduce
Install the same versions of packages in the React application and run the project

I ran into the same issue as this. It seems to be when using xstyled v3 with  react v17 / react-scripts v4. It works all fine with react v18

It has been fixed.


Implement Natural/show

As the title says + I also renamed the exprF01,exprF02,... to something (hopefully) more meaningful, because it became a little unwieldy ;)
Also relates to #49

Looks great!  Also, good call on properly renaming those parsers :)


When the USB interface is disconnected and reconnected, the graphics tablet cannot draw lines again on ppInk.

Sometimes the USB interface of my Wacom tablet is disconnected and reconnected, and when ppInk has been launched, lines cannot be drawn through ppInk. At this time, it can only be solved by closing ppInk and reopening it. Such a situation does not require reopening after closing in gInk.
Windows 11 23H2
Wacom CTL-672(usb tablet)
ppInk v1.90
gInk v1.20

In order to speed up ink startup , many objects are only built at start up. This may have induce the side effect you are observing
try this version but you will have to modify config.ini file with
Init_At_Each_Unfold = True
ppInk with Reset.zip

It works, it can be used normally now. thanks a lot!

Do not hesitate to star the project if you like it ;)


Proposal: Develop a uniform naming convention

The existing Pull requests are slightly different from the existing code in the core repository in terms of function names and test names. Is it necessary to develop a unified standard to manage?

As well as doc strings.
I would +1 to an overall style guideline in addition to the current CONTRIBUTING tutorial. However, I also understand that things are still moving fast at this early stage and perhaps a loose standard is preferred.

If it is a simple restriction identifier style (such as snake_case or CamelCase), it should not have any impact. The current overall code style is snake_case.


MudBreadcrumbs: Change HTML structure and semantics for accessibility

Description

Part of https://github.com/MudBlazor/MudBlazor/issues/9063
Changes the breadcrumbs list from an unordered list to an ordered list and wraps that in a nav element. This is pretty standard among the ones I checked (Bootstrap, MUI, Ant)
Attributes etc are still applied to the list itself but if the ul was directly referenced or the structure in CSS this will change it for the user.
How Has This Been Tested?

visually
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

The diff is largely whitespace changes.
Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

Migration Guide:

MudBreadcrumbs: The ul element is now an ol wrapped in a nav in order to improve accessibility semantics.

Thanks @danielchalmers. Added to v8.0.0 Migration Guide


feat: use key file to encrypt

change lmdb_encryption_key_data to lmdb_encryption_key,
which refers to a key file in the disk.
change lmdb_encryption_type to lmdb_encryption_mode.

feel free to merge after the comment above is addressed


Feature/update drugtable other fixes

This merge updates the gene/drug mapping table to the latest version, updates command-line options, fixes a few other small issues, and updates the README.md for release. Some of the fixes include:

Auto-fitting column widths in Excel (issue #7), done in Search.py. Also only print 2 decimal places in Excel output.
Inverts command-line options so you have to pass --exclude-negatives and --exclude-resistance-phenotypes to exclude those results (issue #2). Done in Search.py.
Groups together common command-line options. Done in Search.py.
Adds in many command-line options for defining specific output files (for Galaxy tool). Done in Search.py.

Thanks for the general comments. For version, I guess it's not so important, but there still is a few additions that need to be added.  Mainly, I want to add support for the other organisms beyond salmonella for the PointFinder database.  That will be for a later release, and I'd like to name that one 1.0.0 and keep this one pre-1.0.
What do you think?

@apetkau I think that's a good idea if there's still a major feature you want to add. This software is looking pretty much production ready though!

@peterk87 thanks for the comment.  I think I will keep this release as 0.2.0 and use 1.0.0 for the next release.


Fix Cache doesn't work on test-agent workflow

Fixes https://github.com/metalbear-co/mirrord/issues/251

Sure, I did almost nothing really :) Just followed @aviramha's suggestion


[Discussion]: Support relative paths (via resolve-url-loader)

https://github.com/bholloway/resolve-url-loader

TBH at this point I'm not even sure what it is about so I guess not relevant.


Flowmeter

Can you please comment a bit on the changes? To me it looks like a lot is simplyfied (most of the code is removed), but it still works?

ping

I can't really comment on this, because this branch is entirely Antonios and Thomas work. I never worked with this branch and our current module qc environment does not use the changes in it. I can look into this.

@matthias-schuessler Why do you always force-push? If it does not work with a regular push, your local history is messed up.

@cbespin I did this, since I just performed a rebase of flowmeter onto the current version of master (basil release 3.3.0). From what I gathered from documentation, a force-push is necessary after a rebase.

Yes, please have a look. In the longterm we want to use the flowmeter for our setup and it would be nice to check if the code changes actually work. Thanks! :)

The flowmeter changes in here are working properly after rebase and can be considered ready for merge.

You do not need a force-push after a rebase. This is the idea of a rebase ;) force-push overwrites the remote history. Always try with a normal push and if you encounter errors, deal with them first before considering a force-push.
I added myself as reviewer and will take a look as soon as possible


Upgraded to PHP 7.x

Hi!
I upgraded the api to use PHP 7.x. Let me know if you need anything else!
God bless

@nicolasguzca thanks very much. Hard to fin a christian developer. If you are interested to share knowledge and experience please contact me<EMAIL_ADDRESS>

Awesome! Will do.


3D objects not working

Describe the bug
When creating any 3d related object or fixture
21H1 Windows 10 Pro
Github Version 2.9.6 (x64)
Processor	AMD Ryzen 7 3800X 8-Core Processor                3.89 GHz
Installed RAM	15,9 GB
Graphics Radeon RX 570 Driver version 30.0.14011.3017
GeoPix 2.0.15485 / Touchdesigner Non-Commercial 2021.15800
Steps to reproduce the behavior

Go to 'Create'
Click on 'objects then Primitive or import Geo' or "Geometry"

Expected behavior
Adding Primitive, Object or Geometry
Actual behavior
Red and/or blue viewport  or when clicking 'Geometry' a complete freeze
Screenshots

Logs From Errors and Diagnostics (first System then GLSL)
======= Newest Errors at the Top =======
SOURCE: COMP : 3 : /UberGui/CustomFixtureEditor/container_Channels
ERROR: (1) TypeError: float() argument must be a string or a number, not 'NoneType'
Context:(Parameter: Offset)
SOURCE: COMP : 3 : /UberGui/UiMapper/Body/Drivers/driverMaps/driverPoolScrollable/container1_template
ERROR: (9) TypeError: float() argument must be a string or a number, not 'NoneType'
Context:(Parameter: Background Color)
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
+++++++++++++++
/UberGui/CustomFixtureEditor/Viewer/FROXEL_BLOCK/geo_AABB_Froxel_Block/glsl_light_CULL_shader
+++++++++++++++
=============
Vertex Shader Compile Results:
Vertex shader failed to compile with the following errors:
ERROR: 0:12: error(#110) Invalid Directive: include
ERROR: 0:13: error(#110) Invalid Directive: include
ERROR: 0:48: error(#143) Undeclared identifier: RetrieveLightType
ERROR: 0:48: error(#202) No matching overloaded function found: RetrieveLightType
ERROR: 0:48: error(#160) Cannot convert from: "const float" to: "highp unsigned int"
ERROR: 0:52: error(#143) Undeclared identifier: testAABB_PointLight
ERROR: 0:52: error(#202) No matching overloaded function found: testAABB_PointLight
ERROR: 0:67: error(#143) Undeclared identifier: testAABB_ConeLight
ERROR: 0:67: error(#202) No matching overloaded function found: testAABB_ConeLight
ERROR: error(#273) 9 compilation errors.  No code generated
=============
=============
=============
Pixel Shader Compile Results:
Compiled Successfully
=============
=============
Program Link Results:
Vertex shader(s) were not successfully compiled before glLinkProgram() was called.  Link failed.
Additional context
Add any other context about the problem here.

Radeon cards are very hit or miss. it has to do with some models not supporting #include statements.
Out of curiosity, have you double checked all video drivers are up to date? Sometimes that can fix it if they are out of date.

I just spoke with a developer at Derivative, their newest experimental branch of TD that just came out will have this #include issue solved. The experimental JUST came out though, and it will likely not function well, or at all for some time. So all I can say if the driver update doesn't fix it, is to wait a while.
Early next year it might be possible to start using it, and if so, I'll start a new branch here as well for that one.

Thanks for the info Lucas,
Yes tried the newest and also older drivers to be sure.
On Fri, Dec 17, 2021 at 11:41 PM LUCAS M MORGAN @.***>
wrote:

Closed #50 https://github.com/EnviralDesign/GeoPix/issues/50.
—
Reply to this email directly, view it on GitHub
https://github.com/EnviralDesign/GeoPix/issues/50#event-5787192247, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AW55FKDP5L5WWRGYKOBYM73URO4DBANCNFSM5KGESS6A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Update README.md

Change the footer in the main README.md file from Y22 to Y21

Pull request completed


Improvements for keeping an up-to-date providers.json

I think it would be useful to make this package easier to use with the latest providers.json source.
A couple of ideas:

A package.json script that performs a basic request to update the package.json file in this package (quicker publishing)
Ability to pass in a custom providers list to the hasProvider and extract methods

allows module consumers to keep their own providers.json file up to date

thanks for your idea. I would consider to implement these useful things.


review terraform examples in light of terraform 0.12 changes

related #176

terraform 0.12checklist didn't reported anything significant in all examples.


🛠 [TASK] : ADR - Proposal structure for M2

Description
Define ADR for proposal structure for M2.

blocked by https://github.com/input-output-hk/catalyst-voices/issues/254


fix leaf encoding

In previous PRs, the leaf encoding was changed, and cells were saved sequentially to cell_pointers. This change was ok but incomplete, which led me to suspect it was a mistake. In this state, the cell range could not properly be defined for the last value in the leaf.
Currently, the documentation describes what is implemented. If you believe it would be better to store cell_pointers and cells sequentially, we need to find another way to store the length of the values.
This also removes tests and LeafInsertionResult, which are not used anymore.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#222  👈
#218 : 1 other dependent PR (#219 )
master

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

Join @gabriele-0201 and the rest of your teammates on  Graphite

actually, it was just a mistake - I see now that the values are right-justified.


README claims nonsense feature "Permanils to linting results and statistics"

Just glanced at the README and the word "Permanils" jumped out at me as nonsense under the list of features:

Permanils to linting results and statistics

Not quite sure exactly what the wording was intended to be - perhaps there was a moment thinking about permalinks but we don't yet expose those.

Yes, permalinks were meant. We should remove it from the list.


feat(native select): adding the native select component

Codecov Report

Merging #262 (977a9d9) into dev (e5be3e2) will increase coverage by 0.05%.
The diff coverage is 90.90%.

@@            Coverage Diff             @@
##              dev     #262      +/-   ##
==========================================
+ Coverage   92.55%   92.61%   +0.05%
==========================================
  Files         117      118       +1
  Lines        3169     3180      +11
  Branches     1072     1074       +2
==========================================
+ Hits         2933     2945      +12
+ Misses        110      109       -1
  Partials      126      126

Impacted Files
Coverage Δ

...a-dom/src/components/NativeSelect/NativeSelect.tsx
90.90% <90.90%> (ø)

...act-magma-dom/src/components/Dropdown/Dropdown.tsx
85.50% <0.00%> (+2.89%)
:arrow_up:

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 e5be3e2...977a9d9. Read the comment docs.


fix #617(iii, iv): Asteroids break into smaller pieces and then into tiny rocks. Small pieces drop loot.

Description

Rubble created from destroying asteroid also now create smaller pieces when destroyed.
CreatesRubbleOnDestruction component is not added for tiny rocks.
DropsMoneyOnDestruction component added to rubble also except the tiny rocks.

Testing

Break the golden asteroid.
Observe that it does not collapse into tiny pieces of rocks straight away. Instead, it acts like normal asteroids in the game.
The smaller pieces when broken also drop loot.

P.S: The newly created pieces of asteroid do not break(fixed in #653). To test, add the health component to the rubble entities.
Pre Pull Request Checklist:

[x] Code has been scanned with SonarLint
[x] There are no errors present in the project
[x] Code has been formatted and indented
[x] Methods have appropriate Javadoc (How to write Javadoc)

@BenjaminAmos Thnkx for the review. I have made the corrections.

Rebased to develop


Add support for textures

There are image blobs in the database that can be loaded with SDL2_image.

Images blobs can now be loaded from the textures table of the database. Diffuse textures are supported in the example.


Added maven enforcer plugin and fixed warnings

This resolves a number of duplicate classes and multiple concurrent versions of dependencies which go undetected without the enforcer plugin.

Thanks for the PR. Feel free to add yourself as a developer in the pom.


How to run async code from current class in pymethods

From your example we can run async code like this. However, it's not clear to me how I can invoke async functions from the same class. Image I have to call another async method from this, how would I do that?
impl Counter {
     async fn incr_async(self_: pyo3::Py<Self>) -> pyo3::PyResult<usize> {
        pyo3::Python::with_gil(|gil| {
            let mut this = self_.borrow_mut(gil);
            this.0 += 1;
             Ok(this.0)
       })
   }
}

Example.
impl Counter {
     async fn incr_async(self_: pyo3::Py<Self>) -> pyo3::PyResult<usize> {
        pyo3::Python::with_gil(|gil| {
            let mut this = self_.borrow_mut(gil);
            // This does not compile because the context is sync.
            Ok(this.another_sync_method().await)
       })
   }
}

Also, I cannot return a future here because the gil lifetime will expire. I can use the async_std::task::block_on inside the GIL block but it would be nice to have something cleaner that keeps living on the same async loop.

@wyfo I guess I'm a bit lucky. I just want to write a async data loading framework for deep learning today. After searching all day, I find your promising work. Looking forward to using it soon。


excelent (hn brought me here)

I'm sure you know you are on home page of hacker news :-).
And I love this idea and plan to use it. I'd love an even simpler tutorial.

How can I help?

a step by step tutorial or out of box demo ? The example can not run.

Thanks, A lot  - The Idea is super cool! :)

Btw if you have a green project, without any dependency on an old projects, you still go with this approach?

The example doesn't work @eavichay
try to build and run also each app separately and get an error on build:

in react app I got:
**Failed to compile.

./src/index.js
Line 8:15:  'AppContext' is not defined  no-undef
Search for the keywords to learn more about each error.**

in angular app error such:
**ERROR in node_modules/@angular-redux/store/components/ng-redux.d.ts(10,31): error TS2420: Class 'NgRedux' incorrectly implements interface 'ObservableStore'.
Property '[Symbol.observable]' is missing in type 'NgRedux' but required in type 'ObservableStore'.

ℹ ｢wdm｣: Failed to compile.**

I'll check out the examples and see why they don't work. I use the examples in live sessions/talks (as-is). Can you specify the node version you're working with?
Also, in order for this to work, you cannot browse to any of the dev-server except of the shell. The AppContext object exists only on the shell and is injected to the other applications - they are not standalone anymore.

Node v 14.0, latest one


pwa base project

:tada: This PR is included in version 1.0.0-beta.7 :tada:
The release is available on:

GitHub release
v1.0.0-beta.7

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
v1.0.0

Your semantic-release bot :package::rocket:


There is obvious delay of response when move focus back to Atom on Windows platform

I have tried Atom1.2.4 and 1.4.0, both have this isssue.
I lunched Atom, open a project, open a file or not, then click on any free space of the desktop to make Atom lose the focus, then back to Atom with a click to any part of Atom, the Atom editor cannot response to my mouse click (or keyboard hit) immediately, there is about 3-5 seconds delay. (The Atom window does not freeze, but it just cannot allow me to edit open file immediately)
I am using Windows7 with i5 + 4GB Memory.

Thanks for the report! This looks like a duplicate of https://github.com/atom/atom/issues/9544 – feel free to subscribe there for updates.


Binding of IBus

Contact Details
<EMAIL_ADDRESS>Version
8.x
On which operating system(s) are you experiencing the issue?
Windows
Using which broker(s) did you encounter the issue?
RabbitMQ
What are the steps required to reproduce the issue?
1. Go to Startup.cs
2. Try to register MassTransit for RabbitHealthCheck (Request\Response pattern)
3. Create HealthCheck (sending simple request)
4. Try to consume message.

What is the expected behavior?
As I understood, when we send request, MassTransit creates custom queue and binds consumer to it. So I want to get this behavior.
What actually happened?
In my case, I get 5 different custom queues (generated by MassTransit Request) and no queue with name equal to addresses in sent message. I think this problem is because of  incorrect registration of MassTransit. In IServiceCollectionConfigurator there is no method for binding IBus (photo 1), so I try to register it straight when creating HealthCheck (because I need a RequestClient) (photo 2).

I want to know how to register MassTransit properly in my case. No any info for old versions in docs. I am using:

Related log output, including any exceptions
-

Link to repository that demonstrates/reproduces the issue
No response

This is not an issue with MassTransit. If you have a support question, you should contact Support.


Update format.py

corrected indents and hyphens

[ ] My submission is formatted according to the guidelines in the contributing guide
[ ] My addition is ordered alphabetically
[ ] My submission has a useful description
[ ] The description does not have more than 100 characters
[ ] The description does not end with punctuation
[ ] Each table column is padded with one space on either side
[ ] I have searched the repository for any relevant issues or pull requests
[ ] Any category I am creating has the minimum requirement of 3 items
[ ] All changes have been squashed into a single commit

Hi @tsv19su254052
Thanks for your contribution ;)
We have some problems with Public APIs, so we won't be able to review/add this improvement right now.
Read this issue for more information, please: https://github.com/public-apis/public-apis/issues/3104


CI: Fix MacOS vcpkg libgeotiff build

Something about the update of libgeotiff from 1.7.0#1 to 1.7.1 is breaking on MacOS on CI, even though it builds fine for me on local MacOS 10.15:
Contents of libgeotiff/config-x64-osx-dynamic-rel-err.log:
CMake Error at /usr/local/share/vcpkg/installed/x64-osx-dynamic/share/unofficial-sqlite3/unofficial-sqlite3-targets.cmake:55 (set_target_properties):
  The link interface of target "unofficial::sqlite3::sqlite3" contains:

    Threads::Threads

  but the target was not found.  Possible reasons include:

    * There is a typo in the target name.
    * A find_package call is missing for an IMPORTED target.
    * An ALIAS target is missing.

Call Stack (most recent call first):
  /usr/local/share/vcpkg/installed/x64-osx-dynamic/share/unofficial-sqlite3/unofficial-sqlite3-config.cmake:7 (include)
  /usr/local/share/vcpkg/scripts/buildsystems/vcpkg.cmake:816 (_find_package)
  /usr/local/Cellar/cmake/3.23.0/share/cmake/Modules/CMakeFindDependencyMacro.cmake:47 (find_package)
  /usr/local/share/vcpkg/installed/x64-osx-dynamic/share/proj/proj-config.cmake:13 (find_dependency)
  /usr/local/share/vcpkg/scripts/buildsystems/vcpkg.cmake:816 (_find_package)
  CMakeLists.txt:118 (FIND_PACKAGE)

I can't directly help with the build failure on Mac (I would maybe report the build failure upstream at https://github.com/microsoft/vcpkg, since it worked before; it's a bit a pity that the dynamic osx build it not one of the built-in triplets, which would make it less likely to get broken).
But, maybe we should try to pin the build to an exact "baseline" for which we know it works (https://devblogs.microsoft.com/cppblog/take-control-of-your-vcpkg-dependencies-with-versioning-support/#baselines), and then only from time to time manually update the version.

This should now be using the vcpkg manifest approach for all builds, which includes a baseline commit in the vcpkg repository (set to just before libgeotiff 1.7.1 was merged), and a pinned version of libgeotiff that works.  We'll occasionally need to bump this version / baseline commit.
The instructions weren't particularly clear; given the basline that I set, it shouldn't have tried to install libgeotiff 1.7.1 at all, but it did so until I added an override to pin that to a prior version.
I couldn't reproduce the libgeotiff error locally, so hopefully that will be fixed at a later point.  I'm not seeing anything obvious to call attention to in the vcpkg setup for it, so I'm not sure what we would log out there as an issue other than it doesn't build in our specific environment.

Since this worked on last test of building the wheels, I'm going to go ahead and merge this so we can get closer to cutting an 0.4.0 release that builds wheels.  We can add future PRs to fix things here if needed.

Sorry for the late review here, and thanks a lot for fixing this!

In any case it is a nice solution!

Until it broke on CI, at time of merge.  Because CI is... fun... (investigating now, further fixes will be a in a different PR)

Until it broke on CI, at time of merge. Because CI is... fun... (investigating now, further fixes will be a in a different PR)

But the Mac build passed :)

The GDAL data files probably changes again location on windows ..


Ability to collect/count malformed rows in the DROPMALFORMED mode

Need a way to be able to collect malformed rows in the csv. The DROPMALFORMED mode works great but gobbles the malformed rows, leaving the client without a way to report them or generate stats like error count.
A possible approach would be to introduce another mode, say REPORTMALFORMED, wherein the DataFrame is appended with a status column that contains one of the values amongst {PARSED, DROPPED}. For the rows which were dropped, the column values could be null/don't care.

This seems very worthwhile. I'm not the most qualified person, but I'd be happy to take a stab at a pull request for this issue.

Actually, for Spark-internal JSON source (Spark 2.0) will support _corrupt_record in PERMISSIVE mode. I think this feature might be helpful if added in CSV as well.

Agree. This would be great feature to have. Since spark-csv is nearing maintenance phase, I suggest we address this in upstream Apache Spark.

Hello,
I am faced to this exact problem of catching rejected lines after a dropmalformed. Does anyone have an answer or a tips on how ot do it ? That would be great :)

Hey guys, have you managed to find any workaround on this matter?

You may be able to create 2 dataframes and then subtract the resulting DROPMALFORMED from the original with all data such as...
df_bad = df_all.subtract(df_dropped_malformed)

Also needs a way to retrieve bad (skipped) lines. In production, this may help log the lines that where rejected from processing while injecting a new csv.

Has the feature been picked for any release. It would be really helpful to have this feature in.

Would also really like to see this.

@alfredox10
I like the idea of trying to get subtract from df_all.
but how u will be able to load the df_all as when reading the data you will be facing same issue
as you are trying to read same record.


[objc] Map System.DateTime with NSDateTime

Add back and forth conversion between .NET System.DateTime and Foundation NSDateTime.
Similar to https://github.com/mono/Embeddinator-4000/issues/254 (for decimal support) but requires extra timezone / UTC support.
WRT to DateTimeKind.Unspecified we should document it to follow MSDN documentation [1],

Unspecified
This instance of DateTime is assumed to be a UTC time, and the conversion is performed as if Kind were Utc.

[1] https://msdn.microsoft.com/en-us/library/system.datetime.tolocaltime(v=vs.100).aspx

PR https://github.com/mono/Embeddinator-4000/pull/344 Merged


Rust 1.82+ enables reference-types / multivalue wasm target features

Rust 1.82 coming to stable on Oct 17th updates to using LLVM 19.
reference-types and multivalue are enabled, which will change how the WASM binaries are built.
From the announcement blog post:

any WebAssembly module with an indirect function call (which is almost always the case for Rust code) will produce a WebAssembly binary that cannot be decoded by engines and tooling that do not support the reference-types proposal

Ref: https://blog.rust-lang.org/2024/09/24/webassembly-targets-change-in-default-target-features.html
We have these features disabled in wasmi in Protocol 21 (current protocol) and in Protocol 22 (the next protocol), which means builds of contracts with Rust 1.82+ will be rejected by the network. This will require contract developers to use Rust 1.81 or earlier for a time until we can catch up.
We need to also in general check that our tooling are updated to be able to decode the new types of wasm files if they can't already.
### Tasks
- [ ] Add compile error to Rust sdk usage to prevent building with the target features (temporary) cc @stellar/contract-committers https://github.com/stellar/rs-soroban-sdk/pull/1353
- [ ] Update wasmi usage to allow the target features cc @stellar/contract-committers
- [ ] Check if Rust SDK can decode and extract contract specs from imported contracts built with the features enabled cc @stellar/contract-committers
- [ ] Remove compile errors from the Rust SDK once target features are enabled cc @stellar/contract-committers
- [ ] Check if JS Stellar SDK can decode and extract contract specs from contracts built with the features enabled cc @Shaptic @stellar/devx
- [ ] Check if Stellar CLI can decode and extract contract specs from contracts built with the features enabled cc @stellar/devx
- [ ] Answer the question: How do we find out about breaking changes to rust like this sooner?

Links:

https://github.com/WebAssembly/tool-conventions/issues/233

We should also evaluate extended-const, nontrapping-fptoint, simd128 and relaxed_simd target features. Found them when comparing rustv1.74.0 with rustv1.81.0,


[FEATURE] OpenSearch Project Distribution and Integration Test Build Analytics

Is your feature request related to a problem?
Coming from the comment https://github.com/opensearch-project/opensearch-build/issues/4171#issuecomment-2147976422, ingest the OpenSearch and Dashboard plugins distribution and Integration test build results. Similar to what we have today with OpenSearch Gradle Check Metrics ingesting the build and Integration test results should give us lot of insights and data regarding the build failures data for a given release and this would give us trends over the period. This is also one of the main requirement for Central Release Dashboard as proposed here.
Having this distribution and Integration test build results in metrics cluster should also the release management for the release manager where the visualizations links can be shared directly instead of parsing through build jobs and logs and create a complex markdown table for failures for each plugin, distribution, architecture etc. Example from past release https://github.com/opensearch-project/opensearch-build/issues/3616#issuecomment-1636583248, https://github.com/opensearch-project/opensearch-build/issues/3616#issuecomment-1638704742
What solution would you like?

Create a Jenkins library and use it in post section that can collect the build data in the following format. Having a library gives us would give us advantage of synchronous data ingestion to the metrics cluster which can collect and push the data at the end of the build.

Distribution Build
{
  component: alerting
  component_repo_url: https://github.com/opensearch-project/alerting
  version: 2.16.0
  ref: abcgdtxgrsggvgfcfds
  distribution_build_number: 10020
  distribution_build_url: https://build.ci.opensearch.org/job/distribution-build-opensearch/10020/display/redirect
  build_start_time: <JENKINS_BUILD_TIME>
  component_build_result: failed
  rc: false
  rc_number: 0
}

Integration Test Build
{
  component: securityDashboards
  repo_url: https://github.com/opensearch-project/security-dashboards-plugin
  version: 1.3.18
  build_number: 6040
  build_url: https://build.ci.opensearch.org/job/integ-test-opensearch-dashboards/6040/display/redirect
  distribution_build_number: 7791
  distribution_build_url: https://build.ci.opensearch.org/job/distribution-build-opensearch-dashboards/7791/display/redirect
  build_start_time: <JENKINS_BUILD_TIME>
  component_build_result: failed
  rc: false
  rc_number: 2
  platform: windows
  architecture: x64
  distribution: zip
  test_report_manifest: https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/test-report.yml
  with-security: failed
  with-security_build_yaml: https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/with-security/securityDashboards.yml
  with-security_cluster_stdout: [https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/with-security/local-cluster-logs/id-0/stdout.txt, https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/with-security/local-cluster-logs/id-1/stdout.txt]
  with-security_cluster_stderr: [https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/with-security/local-cluster-logs/id-0/stderr.txt, https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/with-security/local-cluster-logs/id-1/stderr.txt]
  without-security: failed
  without-security_build_yaml: https://ci.opensearch.org/ci/dbc/integ-test/1.3.18/10042/windows/x64/zip/test-results/8364/integ-test/k-NN/without-security/k-NN.yml
  without-security_cluster_stdout: [https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/without-security/local-cluster-logs/id-2/stdout.txt, https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/without-security/local-cluster-logs/id-3/stdout.txt]
  without-security_cluster_stderr: [https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/without-security/local-cluster-logs/id-2/stderr.txt, https://ci.opensearch.org/ci/dbc/integ-test-opensearch-dashboards/1.3.18/7791/windows/x64/zip/test-results/6040/integ-test/securityDashboards/without-security/local-cluster-logs/id-3/stderr.txt]
}

Once the data is collected the library should parse and index the data to opensearch-integration-test-results-${formattedDate}, opensearch-distribution-build-results-${formattedDate}.

Create useful visualizations like data table that can be filtered by release, component, rc, with-security, without-security etc and get the log details from the links along with other information about the number of rc's.

Having this data over the period should give trends (using time series graphs) about the release and mainly with failing builds and tests for a given release.

Adding @getsaurabh02 @peterzhuamazon @reta @dblock to please take a look.
Thank you

We can reduce the url length but it is a good start 👍 .
Will use these as part of the Central Release Dashboards here: #51 .
Thanks.

Certainly +1, thanks a lot @prudhvigodithi !

Able to collect the data and index to my test cluster, will create the library PR's shortly.

We can reduce the url length but it is a good start 👍 .

Yes Peter, we should either use some open source tiny URL framework or we can leverage dashboard scripted fields to do this, for every URL fields have an associated scripted field for the short URL.
Thanks

Created visualizations that contain all the build and integration test information. Please check them at OpenSearch Metrics Dashboard. With this setup, we can easily filter by build (RC build number) to get all the build and integration test details for both with-security and without-security configurations, including URLs to download the test reports. There are many other filters available, allowing us to slice and dice the data by architecture, distribution, platform, OS, or OSD components.

Closing this issue as the metrics dashboard now has the OpenSearch Project Distribution Build and Integration Test Analytics. Readme PR https://github.com/opensearch-project/opensearch-metrics/pull/60.
This dashboard is used for 2.16.0 to track the build and integration test failures per RC and post the release updates, example https://github.com/opensearch-project/opensearch-build/issues/4771#issuecomment-2273857626.
Thanks
@getsaurabh02


Force macOS pkg to use user networking mode

Keep the system networking mode for the fat binary.

No changes are needed in the preflight checks?

If the user was using system networking, it will be now user networking.

This means there are no longer any fallbacks if the user hits usermode networking limitations. Have we gathered enough feedback already to be confident that nobody will need that fallback while we fix some usermode networking bugs/missing features?

1.26.0 was released one month ago and we had no issue about this. The release is in 1 week so I guess it is safe to merge this at the last minute if there is still no issue.

I don't understand why we want to force it without any fallback options. In case of pkg we are already setting UserMode for network as default. This way until user manually set network-mode to system it is by default using user mode. With this change he will never able to go back on system mode.  If the plan is to drop system mode for mac then I am OK but until then I am in favor to provide user an option to choose.

Yes the goal is to remove the system network mode.
The system network mode is only useful for the fat binary. I keep it only because of IDEs still consume it.
When the system mode is removed we can:

run hyperkit as normal user
remove the driver binary and compile it directly in crc binary

Right now, this PR removes a potential workaround for usermode networking issues, but as you pointed out, it cannot remove all the non-usermode yet. Since the code for non-usermode will still be there, I don't see what benefit we get from this PR, I'd favour not merging this, and just remove the old code when possible.

/hold

We are going to keep this on hold till we have proxy tests are in for vsock/userland networking side.

Proxy test OK:

Run mitmproxy (port 8080)
Install crc
Run crc setup
crc config set https-proxy http://<IP_ADDRESS>:8080 (this my network card IP)
crc config set http-proxy http://<IP_ADDRESS>:8080
crc config set proxy-ca-file /Users/guillaumerose/.mitmproxy/mitmproxy-ca-cert.cer
Start the cluster as usual.

/hold cancel

Follow up issue #2475


Timestamps are not sorted in the parallel_nightly notebook

They should be sorted reverse chronologically.

This issue is fixed now

Thanks.