Embed Post fix

Surprisingly, not that broken. Thought about using WinChatty at first, but realized it just needed some TLC.
I'm testing against a random post with Chatty links in it.

I've included a commit for the Shame Switcher script not picking up some author id's since the nuShack design happened (fixes #95).

I'll also be including a commit that fixes #96 in a day or two if this PR stays open, or I could push it into the upcoming socials-feature fork.


change delay to 3 seconds

I am sorry. This pull request got created by mistake.
I was learning github, randomly clicked some button and this came up.


Keep Pub/Sub message attributes in CloudEvent data

Closes #266
This PR ensures we pass the Pub/Sub message untouched to the CloudEvent data — instead of keeping just the Data attribute — so that message attributes are preserved.
Sample event:
☁  cloudevents.Event
Context Attributes,
  specversion: 1.0
  type: com.google.cloud.pubsub.message
  source: projects/cebuk-01/topics/antoine-dev
  id:<PHONE_NUMBER>330575
  time: 2021-11-13T18:28:35.66Z
  datacontenttype: application/json
Extensions,
  pubsubmsganotherattribute: another value
  pubsubmsgmycustomattribute: a value
Data,
  {
    "Data": {                                  // <-- Data is now nested
      "msg": "Hello, TriggerMesh!"
    },
    "ID": "3440408504330575",
    "Attributes": {                            // <-- Attributes are now propagated untouched
      "Another~attribute": "another value",
      "My Custom Attribute": "a value"
    },
    "PublishTime": "2021-11-13T18:28:35.66Z",
    "DeliveryAttempt": null,
    "OrderingKey": ""
  }

Bonus: Added a JSON schema for the com.google.cloud.pubsub.message event type.

Assuming lazy consensus and merging.


Replace camera implementation with something more standard and less limited.

Doesn't handle rotation metadata, doesn't let me zoom or focus etc, doesn't let me take photos by pressing volume buttons. We need to ditch it in favour of the native controls or use a camera library of some kind

rotation meta fails if the phone is rotationlocked (unlike the native camera control)

We really should ditch our custom camera control in favour of something which plays well with the latest features and hardware, especially with the iPhone X round the corner.

Cool, I'm on it. @ara4n anything I should know?
I know my way around swift and git flow, but new to the crypto world and status.

@ara4n @giomfo I branched off develop locally, but can't push my branch onto remote to create a Pull Request. I think you might have to add me to your organization so I can push my changes and create a PR.
Let me know how you want to proceed.

Hi @GreyEcologist, you have to fork riot-ios in your account.
see https://github.com/vector-im/riot-ios/blob/master/CONTRIBUTING.rst for more details

Thanks! will send a PR tomorrow morning.

On Dec 19, 2017, at 1:43 AM, giomfo<EMAIL_ADDRESS>wrote:
Hi @GreyEcologist https://github.com/greyecologist, you have to fork riot-ios in your account.
see https://github.com/vector-im/riot-ios/blob/master/CONTRIBUTING.rst https://github.com/vector-im/riot-ios/blob/master/CONTRIBUTING.rst for more details
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/vector-im/riot-ios/issues/638#issuecomment-352691272, or mute the thread https://github.com/notifications/unsubscribe-auth/ABFsy_CnHdUq3he_A9jZUNbBJqNxCDN3ks5tB4U6gaJpZM4J_CmD.

Hi @giomfo, I submitted a PR for this a couple weeks ago.  Could I get some feedback on it please?

ping

Hi @knocte: we are waiting for @ianscott313 's feedbacks

Hey guys sorry i haven't wrapped this up yet

Status on the last PR and this bounty?

Hi @debragail the bounty is still available.
Feel free to submit a PR (The existing one has never been updated according to the requested changes).
About the requirement you are free to kill our custom camera implementation or at least provide the normal one as an option.
A Swift implementation is now acceptable.


Fix ttl for the SQLiteStorage

Replace bigger than sign with smaller in sync and async in _remove_expired_caches for sqlite.
Add two test cases for sync and async to test sqlite cache lifecycle.

You can write only the async code and then run ./scripts/lint to generate the sync one.
Can we also have a changelog?

I have a little bit simplified the tests, so we don't have a special test for sqlite storage.
Thanks for this pull request :pray: I will schedule a release for tomorrow :tada:


Adds awesome azd as default template source when not defined

Adds awesome-azd as the default template source when template sources has not been defined.

When template.sources is not defined in config.json => Add awesome-azd
When template.sources is empty => Empty template sources

Use case: 1st run experience after release
template.sources will not be defined, awesome-azd will automatically get added and saved
Use case: User manually removes all templates sources
User has used azd template source remove <key> for all registered template sources.  New sources will need to be manually registered for anything to show up in azd template list or azd init experience.

[!NOTE]
Minimal will still show in azd init experience with empty template sources.

Use case: User manually clears config.json or azd config reset
Fallback to 1st run experience above where template sources have not been defined.

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/2637/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2637/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2637 --version '' --verbose --skip-verify

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

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2637/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/2637/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2637' -Version '' -SkipVerify -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2637/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/2637/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/2637/azd-linux-arm64-beta.tar.gz

MacOS -

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

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

MSI

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

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

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference
description: This article explains the syntax and parameters for the various Azure Developer CLI commands.
author: alexwolfmsft
ms.author: alexwolf
ms.date: 08/16/2023
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference
This article explains the syntax and parameters for the various Azure Developer CLI 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.
      --docs         Opens the documentation for azd in your web browser.
  -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. (Beta)
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines. (Beta)
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies. (Beta)
azd template: Find and view template details. (Beta)
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
      --docs   Opens the documentation for azd auth in your web browser.
  -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.
      --docs                                   Opens the documentation for azd auth login in your web browser.
      --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
      --docs   Opens the documentation for azd auth logout in your web browser.
  -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
      --docs   Opens the documentation for azd config in your web browser.
  -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
      --docs   Opens the documentation for azd config get in your web browser.
  -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
      --docs   Opens the documentation for azd config list in your web browser.
  -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
      --docs   Opens the documentation for azd config list-alpha in your web browser.
  -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
      --docs    Opens the documentation for azd config reset in your web browser.
  -f, --force   Force reset without confirmation.
  -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
      --docs   Opens the documentation for azd config set in your web browser.
  -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
      --docs   Opens the documentation for azd config unset in your web browser.
  -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
      --docs                  Opens the documentation for azd deploy in your web browser.
  -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
      --docs                 Opens the documentation for azd down in your web browser.
  -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
      --docs   Opens the documentation for azd env in your web browser.
  -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.

See also

azd env get-values: Get all environment values.
azd env list: List environments.
azd env new: Create a new environment and set it as the default.
azd env refresh: Refresh environment settings by using information from a previous infrastructure provision.
azd env select: Set the default environment.
azd env set: Manage your environment settings.
Back to top

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

Options
      --docs                 Opens the documentation for azd env get-values in your web browser.
  -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
      --docs   Opens the documentation for azd env list in your web browser.
  -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 and set it as the default.
azd env new <environment> [flags]

Options
      --docs                  Opens the documentation for azd env new in your web browser.
  -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 <environment> [flags]

Options
      --docs                 Opens the documentation for azd env refresh in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.
      --hint string          Hint to help identify the environment to 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
      --docs   Opens the documentation for azd env select in your web browser.
  -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
      --docs                 Opens the documentation for azd env set in your web browser.
  -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. Must be used with a template argument (--template or -t).
      --docs                  Opens the documentation for azd init in your web browser.
  -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. (Beta)
azd monitor [flags]

Options
      --docs                 Opens the documentation for azd monitor in your web browser.
  -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
      --docs                 Opens the documentation for azd package in your web browser.
  -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. (Beta)
Options
      --docs   Opens the documentation for azd pipeline in your web browser.
  -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: Configure your deployment pipeline to connect securely to Azure. (Beta)
Back to top

azd pipeline config
Configure your deployment pipeline to connect securely to Azure. (Beta)
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.
      --docs                         Opens the documentation for azd pipeline config in your web browser.
  -e, --environment string           The name of the environment to use.
  -h, --help                         Gets help for config.
      --principal-id string          The client id of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-name string        The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role stringArray   The roles to assign to the service principal. By default the service principal will be granted the Contributor and User Access Administrator roles. (default [Contributor,User Access Administrator])
      --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. (Beta)
Back to top

azd provision
Provision the Azure resources for an application.
azd provision [flags]

Options
      --docs                 Opens the documentation for azd provision in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.
      --preview              Preview changes to Azure resources.

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. (Beta)
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd restore in your web browser.
  -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. (Beta)
Options
      --docs   Opens the documentation for azd template in your web browser.
  -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. (Beta)
azd template show: Show details for a given template. (Beta)
azd template source: View and manage template sources. (Beta)
Back to top

azd template list
Show list of sample azd templates. (Beta)
azd template list [flags]

Options
      --docs            Opens the documentation for azd template list in your web browser.
  -h, --help            Gets help for list.
  -s, --source string   Filters templates by source.

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. (Beta)
Back to top

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

Options
      --docs   Opens the documentation for azd template show in your web browser.
  -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. (Beta)
Back to top

azd template source
View and manage template sources. (Beta)
Options
      --docs   Opens the documentation for azd template source in your web browser.
  -h, --help   Gets help for source.

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. (Beta)
azd template source add: Adds an azd template source at the specified key (Beta)
azd template source list: Lists the configured azd template sources. (Beta)
azd template source remove: Removes the specified azd template source (Beta)
Back to top

azd template source add
Adds an azd template source at the specified key (Beta)
azd template source add <key> [flags]

Options
      --docs              Opens the documentation for azd template source add in your web browser.
  -h, --help              Gets help for add.
  -l, --location string   Location of the template source.
  -n, --name string       Display name of the template source.
  -t, --type string       Kind of the template source.

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 source: View and manage template sources. (Beta)
Back to top

azd template source list
Lists the configured azd template sources. (Beta)
azd template source list [flags]

Options
      --docs   Opens the documentation for azd template source list in your web browser.
  -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 source: View and manage template sources. (Beta)
Back to top

azd template source remove
Removes the specified azd template source (Beta)
azd template source remove <key> [flags]

Options
      --docs   Opens the documentation for azd template source remove in your web browser.
  -h, --help   Gets help for remove.

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 source: View and manage template sources. (Beta)
Back to top

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

Options
      --docs                 Opens the documentation for azd up in your web browser.
  -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
      --docs   Opens the documentation for azd version in your web browser.
  -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

To summarize my understanding of the experience:

awesome-azd is a configurable option. Users can opt-out by azd template source remove awesome-azd.
Otherwise, it's expected that awesome-azd will show up in config.json, which includes after azd config reset. The way it shows up is technically when you run anything that "lists templates", it gets lazily added. This is an internal implementation detail that doesn't matter unless the user cares about having a "stable" config.json, or that user touches config.json, in which case the user needs understanding that template.sources == nil is not the same as template.sources == [].

I think the design has definite merits in it uses the extensible feature it was built upon. I could also see a more streamlined (but perhaps less educating) experience where:

awesome-azd is a feature that is always enabled. And there is a config key azd config set template.show.awesome-azd false that changes the behavior. It's not treated as an extensible "template source" feature.

The good part of the design is that it avoids the config complication and defines the concrete default behavior in a straightforward way for product maintainers and also for users. But perhaps this is a minutia and the exposure of template source itself is the bigger ticket item.

@savannahostrowski - Loading community templates by default might lead to confusion by end user on which templates are MS vs non-MS.  Also, there might be security risks involved, etc.  Time to intro a disclaimer to this command?

Yeah - we can definitely add a notice to the top of the table output here to indicate that there are risks running 3rd party code (we already include this notice on init too).


Missing documentation on how the extensions option is used.

I experience some unexpected behaviour when I pass the extensions option and can't find any information on how this option is used so that I can debug my usage of this package.

See the third bullet point under https://github.com/substack/node-resolve#resolveid-opts-cb, and below that, the default value of extensions: [ '.js' ]


Progress Not Being Pushed To GA

Hey Guys,
Having an issue where the progress events are not appearing in GA (The 25%'s and the 10% and 90%).
Everything appears fine from a GTM point of view, and the tags are firing, however they simply dont appear in GA.
Play, Pause and Watch to End fine.
Any help appreciated.

Hi, same problem

Uncaught TypeError: Cannot read property 'value' of undefined
at l (froogaloop2.min.js:1)

I suppose:
"Frogaloop was retired apparently, but that doesn't explain why only half the CDN servers return it nad the other half cause 504 errors. Anyway, the solution is to migrate off frogaloop. See https://github.com/vimeo/player.js#migrate-from-froogaloop"


Something missing in the RBAC section

The section https://docs.microsoft.com/en-us/azure/security/security-identity-management-overview#rbac refers to a list of "four fundamental built-in roles.", but there is no such list shown in the section or page.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4c24e0e2-d91c-e902-1fc3-8a5443f96740
Version Independent ID: a51cb910-d3fe-4106-ab88-090272cc26c1
Content: Azure security features that help with identity management
Content Source: articles/security/security-identity-management-overview.md
Service: security
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

Thanks for the feedback! We are currently investigating and will update you shortly.

@cowinr
The RBAC Built-In Roles are documented here. Owner, Contributor, Reader are the basic roles.

We will be closing this thread now. Let us know if you need further help.

@cowinr @neeleshray - I think the text "four fundamental built-in roles" can cause confusion. I will open a PR to fix. Thanks, Richard, for pointing this out.

I just added a new comment, but didn't realize this was the same issue. It was raised a year ago, but was never fixed.


Bug: upgrading vitality gives 10 health, not 20

When upgrading Vitality the descriptions says it will increase your current and max health by 20.
Here my character had 8/100 health, I upgraded Vitality and now have 18/120. Expected 28/120.

Fixed with recent patch:
OLD
let (new_adventurer) = AdventurerLib.add_health(10, updated_stat_adventurer);
NEW
let (new_adventurer) = AdventurerLib.add_health(20, updated_stat_adventurer);


Show secrets

Clear and concise description of the problem
Secrets cannot be displayed after they have been saved.
Suggested solution
Add a button to show/hide secrets.
Alternative
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

This is kind a tricky one as it could pose security threats (it's not shown for a reason). Correctly this would be implemented to ask for password but this is not really option for us...

For now, we can't edit a secret wihout set the value:  https://github.com/woodpecker-ci/woodpecker/blob/master/web/src/components/secrets/SecretEdit.vue#L14
The API removes the secret value: https://github.com/woodpecker-ci/woodpecker/blob/master/server/api/repo_secret.go#L124

@lafriks some CI sytems like Gitlab allow to show secrets. That could be an option to allow it.

why would we weaken the security ?!?
if you have a secret saved that is not saved somewhere else, it's either a token that should be regenerated anyway if you change something, or a secret that you should have managed in some password-manager anyway ...

well that github does not follow best-practice in security from time to time and prevere convinience is not something we should adapt - in my opinion.
If you really need to extract the secret well, just make an sql call as admin ... that should be a fair enough burden to only be the last resort but still be possible

if you have a secret saved that is not saved somewhere else, it's either a token that should be regenerated anyway if you change something, or a secret that you should have managed in some password-manager anyway ...

Show secrets is useful when you want to:

check the value
fix a typo in the value
use the value in other project (eg: mail server configuration for notifications)

IMHO allowing changes to secrets or revealing them is a horrible decision from a security standpoint.

For now, we can't edit a secret wihout set the value: https://github.com/woodpecker-ci/woodpecker/blob/master/web/src/components/secrets/SecretEdit.vue#L14

This alone opens the door for abuse, as you could remove a plugin requirement or permitted image and by doing this exfiltrate the secrets value...
Scenario
To show why it's a bad Idea, I'm painting a scenario here... (it's a case that could/would apply to a project I'm participating in)
The project has different people with different levels of access to things that go into secrets. Not all Admins on the repo have full access to those secrets (think stuff like signing keys).
If someone managing the signing key adds the secret, limits its usage to plugin and sets the image, as long as the image is secure, you can't exfiltrate the key.
Now lets assume (which sadly already happened) the secret is editable without the need to reenter the value: Another admin can go in, change the setting of that secret, and e.g. allow the use on pull_requests, remove the plugin only and / or image restriction. Now it's possible for that user to push (or just PR) a pipeline, that accesses that secret, but allows them to exfiltrate the value (base64 encode so the log doesn't masquarade it, upload to a http connection...)
Conclusion / thoughts

Making secrets editable or revealable increases the security risk associated with them.
If you don't have the secret noted anywhere else (or you don't have access to that note), it should either be easy to regenerate / exchange, you should not be changing it, or your process is already broken beforehand
While checking values can be "nice", just overriding with what should be in there anyway should suffice (esp. once we have CI envs, for which many including me currently abuse secrets)
Some of these issues may be easily overlooked / ignored / non-issues in setups where there is only 1 user on the instance, all users have the same access to the secrets (and likely some other cases, where security isn't really a concern)

I use Woodpecker only for my personal projects, so I'm the only one who has access to the Project, which means there is not really a security risk. Having the Option to view the Secrets can help me debugging (e.g. check if I updated my Credentials for the project after changing it). I also think we should not bother with advanced permissions models at this time. Just a Checkbox "The value of this secret can be revealed" should be enough currently. So people who use Woodpecker only for personal projects (like me) or smaller teams where everybody know the Secrets can use this feature. If you use Woodpecker in a more complex environment, than it's the best to just keep the Secrets hidden in Woodpecker UI.

i would like to second the opposition to such a feature. the ci system is not a secret management tool, it is supposed to blackbox entered values. it is trivial to do so, hence debugging by adding different values in the editor (which shows the values initially) should be sufficient.
any option to retrospectively view secrets weakens the security model and raises all kinds of flags when used in regulated environments (think PCI-DSS, etc.).
please keep the system as simple as it currently is, it does not need to be easy.

-> #1556


Improve Service provider DAO layer

Currently, service provider update operation does multiple UPDATE DB calls to update separate columns of the same table. These can be combined to a single Update DB call. This would reduce the load on the DB significantly during the SP update.
Example:
https://github.com/wso2/carbon-identity-framework/blob/d25b13f2491c50e290eb5b5614a14dcb9f0ebf84/components/application-mgt/org.wso2.carbon.identity.application.mgt/src/main/java/org/wso2/carbon/identity/application/mgt/dao/impl/ApplicationDAOImpl.java#L1238-L1329
There can be other places like this where we can cut down the number of DB calls by combining multiple DB calls.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


for generated cell types using the user annotation the generated DEGs are not shown

it's for sure calculated and written into the database. must be due to some changes for multiomics

fixed in https://github.com/Bayer-Group/cellenium/commit/e1923dedc357cdf8e3a1c61fd967b9dbb639c1fc


"Toggle between light/dark themes" always changes my theme to "default high contrast"

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.72.0 (system setup)
OS Version: Windows NT x64 10.0.19044

When I run "Toggle between Light/Dark Themes", the color theme always toggles between "Default High Contrast" and "Default High Contrast Light", regardless of what I have set in workbench.preferredLightColorTheme and workbench.preferredDarkColorTheme.
Steps to Reproduce:

set workbench.preferredLightColorTheme and workbench.preferredDarkColorTheme
run "Toggle between Light/Dark Themes"

The command first looks at the current theme to decide whether to use high contrast or not.
So If you are in a high contrast theme it will stay in high contrast and use workbench.preferredHighContrastColorTheme and workbench.preferredHighContrastLightColorTheme.
If you are not in a high contrast theme it will stay in high contrast and use workbench.preferredLightColorTheme and workbench.preferredDarkColorTheme.
Do you see different behavior? What is the theme you are starting with? What is the OS theme?

Thanks for the explanation, I didn't know the last part.
My dark theme is abyss, but I was actually using an high contrast theme for my light theme (cause my screen isn't very bright), so I guess that's why it kept switching to the default high contrast dark theme instead of abyss.
I've changed my light theme to a non-high contrast one and now it works fine.


Finetune, cuda out of memory

I am using your code to make Finetune, but "cuda out of memory" is displayed. What is the memory space required by Finetune? I used an A100 with 40GB of RAM. I think the reason is that the size of the picture is too large (512). Is there a smaller picture size available from Finetune?

I responded to this here
https://github.com/hotshotco/Hotshot-XL/issues/45#event-11402451913
It will be a challenge to fine tune on a A100 40gb at that resolution.


Use standard cache directories

Currently installing electron caches the zip file in a folder called .electron in the user's home directory.
This is contrary to:

The recommended spec on Linux.
~/Library/Caches on macOS.
The generally used %LOCALAPPDATA% on Windows.

I would be willing to submit a PR to use these directories on the respective systems, if this sounds like a good idea.

I see there is a PR for this in electron-download.


Ability to parse all valid type aliases

Currently function parse_type_string (in src/unitxt/test_utils.py) fails when a user passes built-in non-capitalised type aliases, for example: list instead of List, which is valid since Python 3.9.
The same happens when using a "bitwise or operator" for union types, for example: int | str instead of Union[int, str].
The function also fails when a type string contains full module name for example: typing.Dict.
Suggestion: expanding the functionality so that parse_type_string can process all valid type aliases

@elronbandel what do you think about this idea?

@pawelknes it could be fixed easily but if i. understand correctly it wont work with python 3.8 no?

@pawelknes it could be fixed easily but if i. understand correctly it wont work with python 3.8 no?

Since parse_type_string accepts strings I was thinking about adding a step which will firstly preprocess string so that it's compatible with typing no matter if version is before or after Python 3.9, maybe like this snippet (just an initial idea):
def format_type_string(type_string: str) -> str:
    types_map = {"list": "List", "dict": "Dict", "tuple": "Tuple", "typing.": ""}
    for k, v in types_map.items():
        type_string = type_string.replace(k, v)
    return type_string

And it could also deal with | into Union. I can make a PR if you accept the idea (or am I missing something?)

You are right. Sounds cool and should work!

https://github.com/IBM/unitxt/pull/772


Laravel 11 support

Updated the tests workflow to include Laravel 11.

@edwinvdpol Could you fix the dependencies? Tests are failing


'sourceReference' is missing

debugged a C# app that uses Tasks
found exception in the dev tools console
I believe this error is coming from the C# debug adapter
the newest vscode should always send a sourceReference when it is available, when do you exactly throw this error?

//Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:117
source: property 'sourceReference' is missing: Error: source: property 'sourceReference' is missing
    at file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:79:17181
    at Object.p [as _notify] (file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:23:22802)
    at Object.__dirname.undefined.F.enter (file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:23:26130)
    at __dirname.undefined.t.Class.define._run (file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:23:27451)
    at __dirname.undefined.t.Class.define._error (file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:23:26968)
    at file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:79:12410
    at t.e.dispatch (file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:79:13482)
    at t.e.handleData (file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:79:13006)
    at Socket.<anonymous> (file:////Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:79:12276)
    at emitOne (events.js:90:13)e.onUnexpectedError @ //Applications/Visual Studio Code - Alpha.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:117
winjs.base.js:47WARNING: Promise with no error callback:undefined

This looks like a problem with VS Code rather that the debug adapter. Here is the code:
    public virtual DebugResult Dispatch(string command, dynamic args)
    {
        int thread;

        switch (command)
        {

...
case "source":
int sourceRef = GetInt(args, "sourceReference", -1);
if (sourceRef == -1)
{
return new DebugResult(1010, "source: property 'sourceReference' is missing");
}
return Source(sourceRef).Result;
Notes:

The C# debug adapter never uses source references. So it is probably a bug to ever send us that command.
This code came from the VS Code team and we have never touched it.


Python code confidence is an array not a number

Upon running the python code I am getting:
    if confidence >= 0.4:
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

And when trying condfidence.any() it won't work as well. Any advice?

have u found a solution?

pip uninstall opencv-python
pip install opencv-python==<IP_ADDRESS>

Nope
On Tue, 6 Sept 2022 at 00:20, hasimiali @.***> wrote:

have u found a solution?
—
Reply to this email directly, view it on GitHub
https://github.com/doleron/yolov5-opencv-cpp-python/issues/20#issuecomment-1237499833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFA3ZIY4U5UZ7TMAXQB5B3LV4ZW3DANCNFSM6AAAAAAQFHTDMI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi, I had the same problem, solved with:
pip uninstall opencv-python
pip install opencv-python==<IP_ADDRESS>
my numpy version is 1.23.3
running on Win 10 with python 3.8.10

Upon running the python code I am getting:
    if confidence >= 0.4:
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

And when trying condfidence.any() it won't work as well. Any advice?

i've done
when you call
wrap_detection(input_image = img, output_data=output_data[0])
don't forget to get only array [0] in output_data


functional tests: Add new test with systemd-proxyd

Setting ptp template network and IP address in systemd unit during
test. Updated also docs with example.

review request...

LFTM

I didn't know systemd-socket-proxyd. It looks cool :)
@joshix , can you review the changes in Documentation/using-rkt-with-systemd.md? Thanks:)

@joshix review request.

@joshix  review request.

@woodbor I have the two little nits noted inline. After those are fixed, the docs part LGTM. Thanks!

done

I also have two little nits noted inline. After that, LGTM.

done

Thanks.
The TestFetch failure is not related to the patch.


bug importing a project folder

Operating system or device, Godot version, GPU Model and driver (if graphics related):
linux mint 18.2 optimus nvidia 520 intel sandybridge
Issue description:

handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6() [0x30004354b0] (??:0)
[2] Node::get_child_count() const (??:0)
[3] CanvasItemEditor::_draw_locks_and_groups(Node*, Transform2D const&) (??:0)
[4] CanvasItemEditor::_draw_viewport() (??:0)
[5] MethodBind0::call(Object*, Variant const**, int, Variant::CallError&) (??:0)
[6] Object::call(StringName const&, Variant const**, int, Variant::CallError&) (??:0)
[7] Object::emit_signal(StringName const&, Variant const**, int) (??:0)
[8] Object::emit_signal(StringName const&, Variant const&, Variant const&, Variant const&, Variant const&, Variant const&) (??:0)
[9] CanvasItem::_update_callback() (??:0)
[10] MethodBind0::call(Object*, Variant const**, int, Variant::CallError&) (??:0)
[11] Object::call(StringName const&, Variant const**, int, Variant::CallError&) (??:0)
[12] MessageQueue::_call_function(Object*, StringName const&, Variant const*, int, bool) (??:0)
[13] MessageQueue::flush() (??:0)
[14] SceneTree::iteration(float) (??:0)
[15] Main::iteration() (??:0)
[16] OS_X11::run() (??:0)
[17] /godot/godot-v3.0-x11.64(main+0xaf) [0x93b64f] (??:0)
[18] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x3000420830] (??:0)
[19] /godot/godot-v3.0-x11.64() [0x93c860] (??:0)
-- END OF BACKTRACE --
Steps to reproduce:
just loading a 2d project
Link to minimal example project:

What version of Godot? Can you provide a project that reproduces the issue?

I think this bug was fixed. Are you using the last master ?

ok sorry this was from 3 days ago, it seems fixed now.

Closing then.


What are the values of the special tokens ([CLM], [Match], etc)?

Hello, I'm working to apply the CodeT5+ model on my own dataset.
In the paper there is discussion of special task specific tokens: [CLM], [MASK*], [CLS], [Match], [CDec], [TDec], etc.
What are the values of these tokens? I can't seem to find it on the Github or HuggingFace repo.
Thanks

Hi there, only the models after two stages of pretraing will have such special tokens. In the tokenizer for our CodeT5+ 110M embedding model, you can find these special tokens (see here), i.e.  [ENC]: 32100 (stand for [Match]), [TDEC]: 32101, [CDEC]: 32102. Some special tokens have a different form represented in the paper for the readability purpose. Specificially, we reuse the <unk> token for [CLM], <s> for [CLS], and <extra_id_*> for [MASK*]. Hope this clarify your confusion.


diffdelete messed if set cursorcolumn on when vimdiff

Describe the bug
highlight of diffdelete disappeared/messed if set cursorcolumn on when vimdiff and cursor on some specific place..
To Reproduce
1, e.g file 'x' had following content:
aa

cc

2, e.g file 'y' had following content:
aa
bb
cc

3, vimdiff --clean x y -c 'set cursorcolumn'
4, put cursor on first line, then compare the highlight different between cursor on 1st letter 'a' and 2ed letter 'a'.
5, if cursorcolumn off, highlight is no different.
Expected behavior
vimdiff highlight is no different, whatever cursorcolumn on or off.
Screenshots

// cursor on 1st letter 'a'

// cursor on 2ed letter 'a'
Environment (please complete the following information):
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Nov  5 2020 11:32:05) Included patches: 1-1955

OS: Ubuntu 18.04
Terminal: xfce-term

Additional context
n/a

isn't that just the Cursor Highlighting that you see there?

pls check 'screenshot', so far the difference/mess i can see is highlight of diffdelete (the 2ed line - in this case).

So you would expect to see the cursorcolumn highlighting to be shown on top of the deleted line?
Please be precise, it's not clear what you mean.

this ticket title said this is about 'diffdelete', regardless 'cursorcolumn' hightlight, but this triggered this mess. clear?
or could you pls just try to reproduce and compare by :
move cursor on 1st letter 'a' -vs- 2ed letter 'a' when :
vimdiff --clean x y -c 'set cursorcolumn' -vs- vimdiff --clean x y
-or- just check the 'screenshots'.

I am not sure this is a "mess", it is just vim doesn't highlight anything on "deleted lines" as there are no actual lines:

I did, but I find it hard to understand your wording, sorry.
And please note, those are deleted lines, they are not really there. Can't you please answer my question:

So you would expect to see the cursorcolumn highlighting to be shown on top of the deleted line?

I am not sure this is a "mess", it is just vim doesn't highlight anything on "deleted lines" as there are no actual lines:

@habamax no, if started vimdiff withOut 'cursorcolumn' on, you'll see 'diffdelete' showed on whereever your cursor placed.
-vs- if started vimdiff With 'cursorcolumn' on, where is the cursor looked like a trick, if at the linehead, 'diffdelete' disappeared.

@Shane-XB-Qian I don't understand to be fair, sorry.

so you are saying, that the diffeleted highlighting is different depending on the setting of the cursorcolumn option is set?

@chrisbra  let's just focus on issue/bug itself, pls ..
pls just try to reproduce the case, note the 2ed line which 'bb' located, once you moved cursor on 1st 'a', or 2ed 'a', you will see 'diffdelete' is disappeared (if cursorcolumn set on -and- cursor put on linehead (1st 'a')).

@chrisbra let's just focus on issue/bug itself, pls ..

That's what I am trying to do. However, I don't understand your wording. That's why I am asking the questions....

pls just try to reproduce the case

Yes, so what is the case here?

@chrisbra  at ticket description To Reproduce section, if you had trouble to reproduce it, pls just describle your 'trouble'.

@Shane-XB-Qian I am asking the questions, because I do not understand what issue you are having here.
or perhaps I'll just leave this here for somebody else to understand. I am sorry.

@habamax  pls started vim with '--clean', then diffdelete was there not matter had lines or lines deleted.

@chrisbra what's your 'question' on reproducing, or you did not see the difference when reproducing ? let me know and try to help you understood the steps.
there 2 conditions: cursorcolumn on/off and cursor position, (plus '--clean'), then note the different on 2ed line where 'bb' located.
// or if you felt my english not very clear, then yes, i am not a native english speaker, if you are arguing that.

Are you talking about that the background color of the 2nd line is changed from gray to cyan when the cursor is moved from the 1st column to the 2nd column?
Does it occur when you use a different terminal or gvim?

I suppose you are talking about this effect here:
https://asciinema.org/a/Ojpi8RPnXl6kMH5eRLQvdhm2d
note, how the DiffDelete color changes just by moving the cursor by one character in the first window

Are you talking about that the background color of the 2nd line is changed from gray to cyan when the cursor is moved from the 1st column to the 2nd column?

@k-takata  correct!

Does it occur when you use a different terminal or gvim?

yes, i tried xfce-term, ternintor, xterm(330). same issue.
no, i only use tui vim.

btw: the default diffdelete highlight is cyan.

when the cursor is moved from the 1st column to the 2nd column?

actually, this is not accurate, since cyan (diffdelete) disappeared when cursor on the 1st line (where 'aa' located).
-vs- if cursor located on 3rd line (where 'cc' located), then no matter cursor moved from 1st column or 2ed column.
// here, 'aa', 'bb', 'cc' is what file 'y' had -vs- file 'x' only had 'aa', 'cc'.

just by moving the cursor by one character in the first window

@chrisbra looks you reproduced the case now, and yes, in this case it is 'one char', but actually the difference was cursor on linehead or not-linehead, and if there was blank-line (for example: input a empty line after 'cc' in 'x') and cursor on that, then same issue: diffdelete (cyan) disappeared from 2ed line.

I suppose you are talking about this effect here:
https://asciinema.org/a/Ojpi8RPnXl6kMH5eRLQvdhm2d
note, how the DiffDelete color changes just by moving the cursor by one character in the first window

Aha!
Can't reproduce on gvimdiff and vimdiff on windows 8.2.1947
Also can't reproduce on WSL debian 8.2.1955

If my git bisect magic was good, then this is caused by https://github.com/vim/vim/commit/ad5e5631c5dc93a50bbe63

can you check, if this patch fixes it:
diff --git a/src/drawline.c b/src/drawline.c
index 82738f13c..c61cdfd55 100644
--- a/src/drawline.c
+++ b/src/drawline.c
@@ -2778,10 +2778,14 @@ win_line(
        // Also highlight the 'colorcolumn' if 'breakindent' and/or 'showbreak'
        // options are set
        vcol_save_attr = -1;
-       if ((draw_state == WL_LINE ||
+       if (((draw_state == WL_LINE ||
             draw_state == WL_BRI ||
             draw_state == WL_SBR) && !lnum_in_visual_area
                && search_attr == 0 && area_attr == 0)
+# ifdef FEAT_DIFF
+                       && filler_lines == 0
+# endif
+               )
        {
            if (wp->w_p_cuc && VCOL_HLC == (long)wp->w_virtcol
                                                 && lnum != wp->w_cursor.lnum)

Okay, was able to repro -- file contents in OP initial post is not correct:
it should be
aa
cc

not
aa

cc

@chrisbra  yes, i tried. this patch / maco looks got rid this concern case.
however, not sure or if it passed ci tests, then should be good to go. thx.


rename the Arch Linux package to dysk

See https://archlinux.org/packages/extra/x86_64/dysk/

replaces: lfs

Thanks!


[FLINK-34082][core] Remove deprecated methods of Configuration

What is the purpose of the change

[FLINK-34082][core] Remove deprecated methods of Configuration

Brief change log

[FLINK-34082][core] Remove deprecated methods of Configuration

Verifying this change
This change is already covered by existing tests
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers:  no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector:  no

Documentation

Does this pull request introduce a new feature? no

Thanks @Sxnan for the review, merging~


Provide consistent interface for Synthetic Agents API

Issue: KNTK-378

LGTM
I'm not sure how changes in cloud export examples (and related API code) are relevant to "synthetic agents", but they look OK to me.
Please, rebase the change and I'll merge it.

Changes in cloud exports are not related to agents, but I didn't bother creating separate PR for such small changes.
I rebased the branch and added SiteName field to update payload, because the API returns an error without it. It wasn't the case before.


refueling rate

With the new version, i can not see the refuelling rate option. It used to be 28Kg/sec as default and modfiyable. Reading the RL fuelling, it appears to be around 12-15kg/sec. Is there a way i can modify that?

It is the same as it used to be. What is "RL fuelling"?
What is your Text Scaling set to in Windows?

Screenshot of UI pls

RL=real life fueling

RL=real life fueling

Ah, now I get it. It is about using another Rate, not that about that the actual Rate differs from the configured Value!
Well it is strange - I tested the UI with different Text Scaling Options on my Machine and did not saw that. 🤔
What is your Resolution / Text-Scaling set to? The Screenshot seems a little strange to me: it is 4K but still the Window does not fit entirely on the Screen?!
What you could do as Work-Around for the Moment is to set it directly in the .config File (while Fenix2GSX is not running). It is the refuelRate and it is always given in kg/s (the unit is only for displaying comfort)

Thanks a lto for such a prompt reply. it works with the change in config file.

Yeah sure!
But still would interesting to know why the automatic Scaling does not work as I had hoped.
So: What can you tell me Resolution and Scaling Wise on your Setup? 😉

I have a  4k TV as monitor with 3840X2160  resolution. No idea about scaling. Where do i find it?

Ah okay, so it is native 4k what I saw in the Screenshot
Should be System -> Display in English I think - something with Scale there.

scaling is 250%

I'm unable to reproduce that. When I set my Resolution to 4k (Nvidia DSR, since I don't have 4k Monitors) and even Scaling to 350% the the Refuel Rate Text-Box is not cut off.
What was interesting: even with that high Scaling, the Fenix2GSX did not look that big like in your Screenshots. It did look like that when I moved it to my other monitor still running 1440p - but even then not fitting on the whole Screen there was nothing cut off.
I'm a bit clueless right now tbh. There must be something different in your Setup which causes this 🤔

Was able to reproduce that - it seems you have an Additional Text-Scaling on Top of that general Scaling: Ease of Access -> Display -> Make text bigger.
Please confirm.
Still need to figure out what to do about that. The GUI is 100% standard WPF configured to automatically Scale with its Contents. So that is Windows Presentation Framework not working as intended on Windows - a classical Microsoft 😅

with new link, its working perfectly. Thanks a lot. I can see refuelling rate option and modify it.

Excellent! Then happy Flights! 😃


I clone this repo and conda to setup a correct env, what do I miss? please help, thanks!
macOS Sonoma 14.0

I think it's possible that you are using Intel CPU.

Adding this parameter should generate a normal picture, but it is quite slow. You can try it.
--compute-units cpuOnly

Adding this parameter should generate a normal picture, but it is quite slow. You can try it. --compute-units cpuOnly

Thank you so much @czkoko
It take around 60x times to complete the image.

Intel cpu can use diffusionBee app

Intel cpu can use diffusionBee app

Thanks, will try to use it!


Zanshin database schedule maintenance

The Zanshin maintenance finished on August 31, 2024, at 3:04 pm UTC.


Allow collective admins to delete expense

User story
As a Collective admin, I can delete expenses submitted to my collective to get rid of spam.
As seen with #2741, expenses are a growing vector of spam. Some use it to submit expenses to promote their services, others probably hope that collective admins will mistakenly pay them.
Best solution for this problem
Today we allow host admins to delete expenses after they are rejected. I don't see any reason not to give this permission to collective admins too.

Collective admins being able to delete expenses was actually part of the initial specs for https://github.com/opencollective/opencollective/issues/2337.


feat: Add dashboard search filter support

Summary of Changes

Include search filter for dashboard
Refactor filter API to be generic with base API
rename search table filter API from search_table to search_table_filter to make it consistent across all entities.

Tests
Add API test and change related backend tests.
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

Codecov Report

Merging #112 into master will decrease coverage by 0.51%.
The diff coverage is 72.41%.

@@            Coverage Diff             @@
##           master     #112      +/-   ##
==========================================
- Coverage   75.28%   74.76%   -0.52%
==========================================
  Files          17       18       +1
  Lines         615      650      +35
  Branches       77       85       +8
==========================================
+ Hits          463      486      +23
- Misses        127      135       +8
- Partials       25       29       +4

Impacted Files
Coverage Δ

search_service/api/table.py
100.00% <ø> (ø)

search_service/proxy/elasticsearch.py
73.50% <65.76%> (-3.08%)
:arrow_down:

search_service/api/filter.py
93.75% <93.75%> (ø)

search_service/proxy/atlas.py
49.03% <100.00%> (ø)

search_service/proxy/base.py
68.18% <100.00%> (ø)

Continue to review full report at Codecov.

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

@jinhyukchang @ttannis update the pr and test it on staging
cc @dikshathakur3119 @Golodhros


The rsa 4096 bits key generation has about 50% performance degradation in alpha5 compare to 1.1.1f version.

 When i use  "openssl genrsa -out rsakey.pem 4096" to generate the rsa key, need about 6s  to generate five keys in 1.1.1f,but need about 11s in openssl 3.0.0 alpha5.
so ,i wonder if there any big difference in rsa key generation to lead to the above result?

OpenSSL now uses different RSA key generation method according to FIPS 186-4 B.3.6 for (non-multiprime) keys >= 2048 bits which is slower.

OpenSSL now uses different RSA key generation method according to FIPS 186-4 B.3.6 for (non-multiprime) keys >= 2048 bits which is slower.
thanks for reply ，and another question is that if i don't want to use the new method as the performance don't fits my requirements，is there any other way i can use the old method?

Currently the code says this:
    /*
     * Only multi-prime keys or insecure keys with a small key length will use
     * the older rsa_multiprime_keygen().
     */
    if (primes == 2 && bits >= 2048)
        ok = ossl_rsa_sp800_56b_generate_key(rsa, bits, e_value, cb);
#ifndef FIPS_MODULE
    else
        ok = rsa_multiprime_keygen(rsa, bits, primes, e_value, cb);

So selecting an insecure key length <2048, or generating a multi prime key will get you the old key gen. Otherwise you get the new one.

ok ,get it ,thanks,maybe multi prime is a choice

Why is key generation performance so critical?
This generally isn't something that should be done often.

Why is key generation performance so critical?
It's a important point to the applicant's design,so should use with extra careful

ok ,get it ,thanks,maybe multi prime is a choice

Before using more than 2 primes, I suggest that you look into what
that all means.

Why is key generation performance so critical?
It's a important point to the applicant's design,so should use with extra careful

RSA key generation has never been a fixed time. You try to find
primes. Sometimes that goes faster than other times. Even if I
test it using 1.1.1 just a few times I see a factor of more than 30
between the fastest and slowest. I was able to find 2 primes in
100 ms, and also in 3.6 seconds.
If the performance is so important, you might need to consider
doing it differently. You could for instance do it at a different
time when the user doesn't wait for it, or use an EC key.

For 3.0, a decision needs to be made to either always use the old path outside of FIPS or leave this as it stands.

There is a paper that claims to be able to fingerprint OpenSSL generated keys due to biases in the old generation method.

I Just fund that the prime test desig change related to this issue may be the Biggest reason for this performance degradation:https://github.com/openssl/openssl/pull/9272.When i not use the api provided by openssl to gen the rsa key pair,but just use the bn function to gen,there is performance degradation too,when i modify to code to the old version,the  performance is the same.which i change are BN_is_prime_fasttest_ex->bn_check_prime_int->bn_mr_min_checks(modify)->bn_is_prime_int->calc_trial_divisions(modify to return 2048 as the old version code).

What you might see is that we now always use 64 rounds of the
Miller-Rabin test, while it used to be fewer. See #9272.

64 rounds

yes ,i modify this to BN_prime_checks_for_size from bn_mr_min_checks

The extra checks are deliberate then.

So if I understand things correctly, the difference is time is because of the different amount of Miller-Rabin test, and not because we switched to the FIPS algorithm. So does that mean we can close this issue?

I think this can be closed.  There are good reasons to want the extra iterations.

I wonder whether we should expand the CHANGES entry a little more to explain the consequences of this. Currently it doesn't mention RSA at all:
 * Change generating and checking of primes so that the error rate of not
   being prime depends on the intended use based on the size of the input.
   For larger primes this will result in more rounds of Miller-Rabin.
   The maximal error rate for primes with more than 1080 bits is lowered
   to 2^-128.

   *Kurt Roeckx, Annie Yousar*

A CHANGES update is worthwhile IMO.

See #13439 for a possible CHANGES entry.


Proposal to lower target video bitrates (again)

Proposal to lower target video bitrates (again)
The 0.6 release of the video_transcoding Gem contained perhaps the most significant change to the transcode-video tool since the deprecated --big option became the default behavior. Not only was the ratecontrol system enhanced to produce higher quality, the target bitrates for 480i and 720p content were lowered to limit the higher bitrates produced by that higher quality.
For the upcoming 0.7 release, I propose to lower those video bitrate targets again, and not just for 480i and 720p content. The targets for 2160p (4K/UHD) content would also be lowered. However, I'm not proposing any change to bitrate targets for 1080p.
Also different for 0.7 would be lowering the targets when using the --small or --small-video options.
Default target video bitrate

Input resolution
Version 0.5.x
Version 0.6
Proposed 0.7

2160p or 4K/UHD video
16000 Kbps
(same)
12000 Kbps

1080p or Blu-ray video
8000 Kbps
(same)
(same)

720p
6000 Kbps
5000 Kbps
4000 Kbps

480i, 576p or DVD video
3000 Kbps
2500 Kbps
2000 Kbps

Target video bitrate with --small or --small-video

Input resolution
Version 0.5.x
Version 0.6
Proposed 0.7

2160p or 4K/UHD video
10000 Kbps
(same)
8000 Kbps

1080p or Blu-ray video
5000 Kbps
(same)
(same)

720p
4000 Kbps
(same)
3000 Kbps

480i, 576p or DVD video
2000 Kbps
(same)
1600 Kbps

OK, what's the rationale for doing this?
First, the new ratecontrol system introduced in version 0.6 with a constant rate factor (CRF) quality target of 1 does much better at putting pressure on x264 to hit that target bitrate than the old quality target of 16 ever did. So, bitrates are higher now. Weirdly, 480i and 720p content is suddenly too good. And that seems very wasteful of space.
Second, these proposed targets seem to be more in line with what Apple, Netflix, warez (you know what I mean), etc. are doing now as opposed to what they were doing when the project started.
This makes sense to me and my tests so far indicate that quality is still good with lower target video bitrates.
BTW, you can try any of these targets yourself by setting vbv-maxrate directly like this:
transcode-video --encoder-option vbv-maxrate=4000 "/path/to/Movie.mkv"

So, I'm asking for your feedback. Let me know what you think. Soon. Because I'm liable to make the change as early as next week.
Thanks.

I've got nothing to add to your proposal, I just want to say I really appreciate the work you do on this tool, and what a great maintainer you are in general.
In the limited time I've spent trying to learn about the nuances of encoding, I've realized I don't have time to learn about the nuances of encoding. Having this available has enabled me to completely offload the actual video encoding, and instead focus my time and energy on the rest of the automated processing pipeline. It means a lot that I can fully trust that the tool you put out is going to 'do the right thing' and give me the best shot at optimizing any video I throw at it. And I've not had to spend any time debugging issues due to anything your tool has been responsible for.
So, keep it up and thanks again!

@J-Swift Wow! Such praise will just go to my head. :) Seriously, thank you so much! People like yourself are exactly why I keep doing this. (Well, you and the fact that I'm completely nuts.)

Don,
What effect do you expect your changes to have on the file sizes of DVD-sourced video? I know the answer is probably "It depends", but I just wanted to make sure.
I took 9 movies that I had previously encoded with 0.5.x and the --big flag, and ran them through transcode-video again with 0.6, using default options. I then ran them through again, using --encoder-option vbv-maxrate=2000.
Visual exam: I wouldn't call my eyesight super-sharp by any stretch of the imagination, but in doing a quick review of the video files generated, the 0.6 files look better than the 0.5.x files, and I couldn't really tell the difference between the files generated with 0.6 defaults and 0.6 with --encoder-option vbv-maxrate=2000. So my vote is to go ahead and make that change moving forward for DVD-type sources, IMVHO.
What I wasn't sure about was if the file sizes should then move consistently as well. In my 9 test files, 5 of them got smaller between 0.5.x and 0.6, while 4 of them got larger. In the case of Spectre, it grew by 50%.
When comparing 0.5.x with 0.6 and --encoder-option vbv-maxrate=2000, 6 of the files were smaller, and 3 were larger, but by a much smaller percentage.
Here are the movies I ran the tests on (please don't judge) and the different file sizes that resulted, in GB.

Filename
0.5.x with --big
0.6 default options
0.6 with vbv-maxrate=2000

101 Dalmatians (1961)
1.6
1.45
1.17

Alvin & Chipmunks Road Chimp (2015)
1.75
1.93
1.62

Ghostbusters (1984)
2.4
2.34
1.96

Ghostbusters 2 (1989)
2.45
2.4
2.01

Hotel Transylvania 2 (2015)
1.44
1.82
1.52

Spectre (2015)
2.03
3.19
2.66

Spider-Man (2002)
2.79
2.66
2.23

The Good Dinosaur (2015)
2
1.98
1.66

The Peanuts Movie (2015)
1.41
1.77
148

This this about what you expected to happen?
And, if I may be so bold: I echo @J-Swift sentiments above.

I'm just re-posting here what I replied to Don on Twitter: I'm onboard.
I couldn't tell any difference between any of the transcodes in terms of quality but I really like the file size reduction:

I'm sure the file size reduction isn't gonna be as good on every transcode (and they might even become bigger as the person above me has noted) but if just a majority of them are smaller that's alot of freed up space.

@bpharriss This is great data! Thanks do doing all these tests and collating the results so nicely!
(And don't apologize for your title selection. I have most of the same movies. :)
Yes, this is what I expected, i.e. that the size of some DVD transcodings will actually be larger between 0.5.x and 0.6. That's due to the new ratecontrol system moving bitrates closer to the targets. Which, of course, is why I want to lower the targets for 0.7. Now, that won't lower all sizes below 0.5.x levels, but the average size will be slightly lower if multiple videos are considered together.
Hopefully, they will look as good, if not better, too. Which I think is what you're seeing.
And thank you for the kind praise! Much appreciated, sir.

@lambdan Thanks for posting this in the GitHub issue! I was just going to do that after responding to you on Twitter. :)
And thanks for doing all these tests!
Yes, the sizes will vary somewhat depending on complexity, grain, etc., but overall they should be slightly smaller if several are considered together.
I'm glad you like the visual results, too, with a vote of confidence. The new ratecontrol system is finally making some of my old, grainy black and while full frame movies look halfway decent.

Update: After more testing by myself and others (thank you all), I'm much more confident in my proposed video bitrate target changes for 480p and 720p content.
However, I'm now doubting the wisdom of changing the 2160p (4K) targets. This is because no matter how low I set the target, I can't get the bitrate below 10000 Kbps for any of my, admittedly few, 2160p samples using the new ratecontrol system.
Since I don't even document that transcode-video supports 2160p and nobody has complained about any bitrate bloat yet, I'll probably just leave these untouched for version 0.7.

OK, version 0.7.0 of transcode-video has been released! A bit early, I suppose. :) As always, just...
gem update video_transcoding

...to get the latest version.
Thanks again for all your help!


swhkd: init at unstable-2023-10-16

Description of changes
Adding new package SWHKD
Things done
Defined the derivation

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Related issue: https://github.com/NixOS/nixpkgs/issues/180942
Prior work: https://github.com/NixOS/nixpkgs/pull/255374

Using merge commits in PRs is not that nice as that makes resolving merge conflicts if they happen to be on those commits, near impossible.
Closing in favor of #299648


Improve & Fix Examples - Parse text from any block type

Change NOTION_KEY to NOTION_API_KEY (.env.example)
Install devDependencies dotenv
Improve README about installation

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Connect signals to specified class only

Problem
Currently the initialize_tracker was called for all models which is not efficient and flooded in Sentry performance logs
Solution
Connect the signal to specified class only with least changes
Related issue: https://github.com/jazzband/django-model-utils/pull/556
Commandments

[ ] Write PEP8 compliant code.
[ ] Cover it with tests.
[ ] Update CHANGES.rst file to describe the changes, and quote according issue with GH-<issue_number>.
[ ] Pay attention to backward compatibility, or if it breaks it, explain why.
[ ] Update documentation (if relevant).

With https://github.com/jazzband/django-model-utils/pull/556 merged, is this PR still relevant?


Consistent format for hardware requirements for various services

Preview is available here:http://developers-pr761.previews.kube001.services.stellar-ops.com

@ElliotFriend, it looks like there were some discrepancies between https://developers.stellar.org/docs/data/requirements and https://developers.stellar.org/docs/data/rpc/admin-guide#hardware-requirements, specifically with disk/storage space. We should look at that before merging.

@briwylde08 Yeah, good catch. Wonder where I got 30GB from? 🤔

Preview is available here:http://developers-pr761.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr761.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr761.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr761.previews.kube001.services.stellar-ops.com


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In 013c89a, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 7066 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in c53037d after 41 minutes.


Add spell check automation

Yes this is ready to merge.
Not sure why the CI job is not picked up by Github Actions...


Set different layouts for different virtual desktops

Description of the new feature / enhancement
For different virtual desktops (calling it by win+tab), we need different fancy zone layouts as default (I do not want to change it manually every time).
Scenario when this would be used?
I am used to setting up several virtual desktops for different tasks, e.g., emailing, programming, etc. But all the VDs have the same set of FZ layouts, I hope I can customize the layouts varying in different VD.
Supporting information
No response

@EricLauber I think your suggestion is useful for setting the FancyZone template to be used when initially creating the Virtual Desktop or even when you want to change it, but not every time you switch Virtual Desktops.  I can only speak for myself but maybe others are similar, I use Virtual Desktops to minimize the impact of context switching. I get a call and I need to shift focus to a different project, switch to that Virtual Desktop and everything I need (websites, editors, terminals, etc) is open and ready to go. I can "hit the ground running". My hope with FancyZones was that it would take that to the next level by offering optimized layouts per Virtual Desktop.  One VD needs a simple vertical split screen. Another needs 3 vertical columns, one of which is divided into two. Another VD has another layout entirely.
Of course this gets complicated when windows are available on all desktops because then when you switch, that window moves to a different zone and is resized. I could see that being more to code but if it all just works from a user perspective, wow, that would be glorious! And that is not to take away from what FancyZones does already. Just to say, it would be next-level if it could do this other thing.

@ShanePresley I prefer what you are suggesting. I wonder if my suggestion could be a "first pass" at accomplishing that goal. If you can pick different FancyZones each time, independent of virtual desktop, that might be a step toward having virtual desktop-specific FancyZones. Incremental improvement.

So long as they "begin with the end in mind" :)  In the meantime I am getting by with the combination of Windows snapping and in some cases overlapping FancyZones.  Just have to figure out which application windows I want in which layout mechanism.

/dup #18913

This issue is solely discussing use of fancyzones with virtual desktops. In my case I have one display that I want to be organized differently based on the chosen virtual desktop.  The dupe interchanges display and desktop but makes no mention of "virtual desktops". A developer could resolve this issue and not address multiple displays. Likewise a developer could address the other issue to the users satisfaction and not address virtual desktops. And of course, so long as the developer understands both requirements could address it in one shot but they are different issues.


refactor Clear unnecessary status in pipeline fragment context

…
Proposed changes
Issue Number: close #xxx

run buildall


Atomicrex workflow broken

@Leimeroth  Currently the atomicrex workflow gives the following issue.
---------------------------------------------------------------------------
212
Exception encountered at "In [4]":
213
---------------------------------------------------------------------------
214
StdinNotImplementedError                  Traceback (most recent call last)
215
<ipython-input-4-5a80c2a3b254> in <module>
216
      1 pr = Project("WorkshopPotential")
217
----> 2 pr.remove_jobs()
218

219
/usr/share/miniconda/envs/test/lib/python3.7/site-packages/pyiron_base/project/generic.py in remove_jobs(self, recursive)
220
    997                 confirmed = input(
221
    998                     "Are you sure you want to delete all jobs from "
222
--> 999                     + f"'{self.base_name}'? y/(n)"
223
   1000                     ).lower()
224
   1001             else:
225

226
/usr/share/miniconda/envs/test/lib/python3.7/site-packages/ipykernel/kernelbase.py in raw_input(self, prompt)
227
    844         if not self._allow_stdin:
228
    845             raise StdinNotImplementedError(
229
--> 846                 "raw_input was called, but this frontend does not support input requests."
230
    847             )
231
    848         return self._input_request(str(prompt),
232

233
StdinNotImplementedError: raw_input was called, but this frontend does not support input requests.

This was working before so please compare to the previous version.

This is because remove_jobs asks for confirmation, either use remove_jobs_silently or just drop that cell from uploaded version.

I did. It still fails building but not within the notebook


Slightly faster PortRef comparisons

Use Python slots for faster lookup and try-except instead of if-else.
I found this to be somewhat faster for exporting Spice. What do you think?
Relates to #227

Surprising!
My guess is the topic referenced in issue #150 (the set/list combo... actually being one) would move the needle much more.
The Set/List combo is "turned off" for reasons I don't entirely remember, but certainly included "caused weird failures I didn't understand elsewhere" in the causal chain.
That reminds me, in any case we've gotta get the tests passing. I think (hope) it's mostly #152 (codecov) in the way. But until that works, who knows. I may be able to get to that late in the week, or you're welcome to roll it in here.

Now that #230 is done - recommend merging main into here.
That'll give the CI tests a chance of passing.

Older Python + Pydantic combinations appear to not automagically handle the slotted class, there might be a manual flag to add in the dataclass decorator I assume.


Fails to launch lldb on OSX

Which OS: OSX 10.13.2
Which extension version: 0.7.4
Which LLDB version: lldb-900.0.64 (The exact version string is 'lldb-900.0.64\nSwift-4.0')
Which VSCode version:  1.20.0
What is the problem and how did you get there: the extension cannot find lldb. I ran through the troubleshooting page on the wiki (even though it says its outdated, just in case). I try to start debugging and two messages get displayed:

I can debug stuff on the command line without issue; this looked similar to #84 so maybe it's a regression?

I checked the debug console, and the output there was:
--- Checking version ---
--- Done ---

Sorry about that!   Should be fixed in 0.7.5

Awesome! Any idea when that might be? Thanks again for the quick response, and for writing this in the first place!

0.7.5 is already published.  Just update your extension.

Which OS: Fedora 27
Which extension version: 0.7.5
Which LLDB version: lldb version 5.0.1
Which VSCode version: 1.20.1

Same issue on Linux, with the latest version.

@jbolila: since this is a different OS, let's track this in a new bug: #94


Not able to open agm-snazzy-info-window using agm-overlays

I need to open agm-snazzy-info-window with the agm-overlays but I am unable to do so. Can you help?

Haven’t heard of it but will look into next week unless someone else can get to it

I am also not able to close agm infowindow by clicking outside on the map. Please help.

Yup, next week. Try the demo page to see if it works there. This code is in use by many and in production on our servers

Also I don’t know if the info windows are supposed to close when you click outside. That just might be what you expect.

I did my research on your reported issue:

agm-snazzy-info-window only works when its @Host() is matched to an AgmMarker class
1.1 As seen in this link, the agm snazzy code will only work when AgmMarker class is found
1.2 The only foreseen way to make AgmOverlay work with snazzy info window, is to have AgmOverlay inherit aka extend AgmMarker on this linked line of code
1.3 I've tried extending AgmMarker in the past and remember too many incompatibilities had me walk away from inheriting AgmMarker in the past

Not able to close agm infowindow by clicking outside the map
2.1 I have found that this is just how agm-info-window works and I too like it that way
2.2 No changes will be made

So, I don't care much at all about some snazzy info window and I am happy with how things are the way they are. You will need to make a pull request, a giant one that has AgmOverlay extend AgmMarker, to get these requested features of yours.

If so then can we prevent on agm-overlay click, when call the output event (mapClick) of agm-map? As the agm-overlay is clickable on this event but agm-marker does not reach on (mapClick)

Please reread yourself and try again. I’m having a hard time relating and coralating your issue to your last message’s request

I think you’re asking me to hack the events to have an info window close auto close on click outside........ if so, again, I’m happy with how things work. You will find no changes to come from here for that request.
I’m just going to close this issye

I think you are very unclear on the developers request. If so feel free to go with you flow which definitely have a bug. If a map has info window open then it must be close if click on the map. you can check it with agm-marker. Since you have created an overlay which works like a marker then it must have that feature too. And Snazzy-info-window is nothing but a customize agm info window, that must be suppose to work on this flow. But its unfortunately not happening. You close this issue as I found my solution editing your directive.

I solved this by making standalone snazzy-info-windows and then showing them with a (click) handler on the overlay. Not as easy, but it works.