New translation batch for es

New translation batch for Spanish. Product of this workflow.
360 files reverted.
Listed in localization-support#489
247 files:

[ ] translations/es-ES/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md
[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md
[ ] translations/es-ES/content/actions/creating-actions/creating-a-docker-container-action.md
[ ] translations/es-ES/content/actions/deployment/about-deployments/index.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/index.md
[ ] translations/es-ES/content/actions/deployment/managing-your-deployments/index.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/index.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
[ ] translations/es-ES/content/actions/hosting-your-own-runners/about-self-hosted-runners.md
[ ] translations/es-ES/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md
[ ] translations/es-ES/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
[ ] translations/es-ES/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
[ ] translations/es-ES/content/actions/index.md
[ ] translations/es-ES/content/actions/learn-github-actions/contexts.md
[ ] translations/es-ES/content/actions/learn-github-actions/environment-variables.md
[ ] translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md
[ ] translations/es-ES/content/actions/quickstart.md
[ ] translations/es-ES/content/actions/security-guides/automatic-token-authentication.md
[ ] translations/es-ES/content/actions/using-github-hosted-runners/about-github-hosted-runners.md
[ ] translations/es-ES/content/actions/using-github-hosted-runners/customizing-github-hosted-runners.md
[ ] translations/es-ES/content/admin/enterprise-management/caching-repositories/about-repository-caching.md
[ ] translations/es-ES/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md
[ ] translations/es-ES/content/admin/enterprise-management/caching-repositories/index.md
[ ] translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md
[ ] translations/es-ES/content/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration.md
[ ] translations/es-ES/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md
[ ] translations/es-ES/content/admin/enterprise-management/index.md
[ ] translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
[ ] translations/es-ES/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md
[ ] translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md
[ ] translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md
[ ] translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
[ ] translations/es-ES/content/admin/github-actions/managing-access-to-actions-from-githubcom/using-the-latest-version-of-the-official-bundled-actions.md
[ ] translations/es-ES/content/admin/guides.md
[ ] translations/es-ES/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
[ ] translations/es-ES/content/admin/overview/about-enterprise-accounts.md
[ ] translations/es-ES/content/admin/overview/creating-an-enterprise-account.md
[ ] translations/es-ES/content/admin/overview/index.md
[ ] translations/es-ES/content/admin/packages/enabling-github-packages-with-minio.md
[ ] translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
[ ] translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md
[ ] translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
[ ] translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
[ ] translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/index.md
[ ] translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md
[ ] translations/es-ES/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md
[ ] translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md
[ ] translations/es-ES/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md
[ ] translations/es-ES/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
[ ] translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md
[ ] translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
[ ] translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md
[ ] translations/es-ES/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md
[ ] translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
[ ] translations/es-ES/content/authentication/troubleshooting-ssh/error-ssh-add-illegal-option----k.md
[ ] translations/es-ES/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md
[ ] translations/es-ES/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md
[ ] translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
[ ] translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md
[ ] translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md
[ ] translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md
[ ] translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md
[ ] translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md
[ ] translations/es-ES/content/code-security/getting-started/github-security-features.md
[ ] translations/es-ES/content/code-security/getting-started/securing-your-organization.md
[ ] translations/es-ES/content/code-security/getting-started/securing-your-repository.md
[ ] translations/es-ES/content/code-security/guides.md
[ ] translations/es-ES/content/code-security/index.md
[ ] translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md
[ ] translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
[ ] translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
[ ] translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
[ ] translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
[ ] translations/es-ES/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md
[ ] translations/es-ES/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md
[ ] translations/es-ES/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md
[ ] translations/es-ES/content/codespaces/developing-in-codespaces/creating-a-codespace.md
[ ] translations/es-ES/content/codespaces/developing-in-codespaces/deleting-a-codespace.md
[ ] translations/es-ES/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md
[ ] translations/es-ES/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
[ ] translations/es-ES/content/codespaces/developing-in-codespaces/index.md
[ ] translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md
[ ] translations/es-ES/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md
[ ] translations/es-ES/content/codespaces/getting-started/deep-dive.md
[ ] translations/es-ES/content/codespaces/index.md
[ ] translations/es-ES/content/codespaces/overview.md
[ ] translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-dotnet-project-for-codespaces.md
[ ] translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md
[ ] translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md
[ ] translations/es-ES/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md
[ ] translations/es-ES/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md
[ ] translations/es-ES/content/communities/documenting-your-project-with-wikis/about-wikis.md
[ ] translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
[ ] translations/es-ES/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms.md
[ ] translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop.md
[ ] translations/es-ES/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md
[ ] translations/es-ES/content/developers/webhooks-and-events/events/issue-event-types.md
[ ] translations/es-ES/content/discussions/guides/best-practices-for-community-conversations-on-github.md
[ ] translations/es-ES/content/discussions/index.md
[ ] translations/es-ES/content/education/guides.md
[ ] translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md
[ ] translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
[ ] translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
[ ] translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/leave-feedback-with-pull-requests.md
[ ] translations/es-ES/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
[ ] translations/es-ES/content/get-started/quickstart/be-social.md
[ ] translations/es-ES/content/get-started/quickstart/fork-a-repo.md
[ ] translations/es-ES/content/get-started/quickstart/git-and-github-learning-resources.md
[ ] translations/es-ES/content/get-started/quickstart/github-flow.md
[ ] translations/es-ES/content/get-started/using-git/about-git-rebase.md
[ ] translations/es-ES/content/get-started/using-git/getting-changes-from-a-remote-repository.md
[ ] translations/es-ES/content/get-started/using-git/pushing-commits-to-a-remote-repository.md
[ ] translations/es-ES/content/get-started/using-git/resolving-merge-conflicts-after-a-git-rebase.md
[ ] translations/es-ES/content/get-started/using-github/github-command-palette.md
[ ] translations/es-ES/content/get-started/using-github/keyboard-shortcuts.md
[ ] translations/es-ES/content/github-cli/github-cli/github-cli-reference.md
[ ] translations/es-ES/content/github/copilot/index.md
[ ] translations/es-ES/content/github/index.md
[ ] translations/es-ES/content/graphql/overview/breaking-changes.md
[ ] translations/es-ES/content/index.md
[ ] translations/es-ES/content/issues/tracking-your-work-with-issues/about-task-lists.md
[ ] translations/es-ES/content/issues/tracking-your-work-with-issues/creating-an-issue.md
[ ] translations/es-ES/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
[ ] translations/es-ES/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md
[ ] translations/es-ES/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md
[ ] translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md
[ ] translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
[ ] translations/es-ES/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
[ ] translations/es-ES/content/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md
[ ] translations/es-ES/content/organizations/managing-membership-in-your-organization/index.md
[ ] translations/es-ES/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md
[ ] translations/es-ES/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md
[ ] translations/es-ES/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md
[ ] translations/es-ES/content/organizations/managing-organization-settings/renaming-an-organization.md
[ ] translations/es-ES/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md
[ ] translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
[ ] translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
[ ] translations/es-ES/content/organizations/organizing-members-into-teams/index.md
[ ] translations/es-ES/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md
[ ] translations/es-ES/content/packages/learn-github-packages/deleting-and-restoring-a-package.md
[ ] translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md
[ ] translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/index.md
[ ] translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md
[ ] translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md
[ ] translations/es-ES/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md
[ ] translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md
[ ] translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/working-with-pre-receive-hooks.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/reverting-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/index.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/viewing-a-pull-request-review.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
[ ] translations/es-ES/content/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/index.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/index.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/index.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/differences-between-commit-views.md
[ ] translations/es-ES/content/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/index.md
[ ] translations/es-ES/content/pull-requests/index.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md
[ ] translations/es-ES/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md
[ ] translations/es-ES/content/repositories/creating-and-managing-repositories/duplicating-a-repository.md
[ ] translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md
[ ] translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files.md
[ ] translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md
[ ] translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
[ ] translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository.md
[ ] translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md
[ ] translations/es-ES/content/repositories/releasing-projects-on-github/about-releases.md
[ ] translations/es-ES/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md
[ ] translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-a-projects-contributors.md
[ ] translations/es-ES/content/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository.md
[ ] translations/es-ES/content/repositories/working-with-files/managing-files/creating-new-files.md
[ ] translations/es-ES/content/repositories/working-with-files/managing-files/moving-a-file-to-a-new-location.md
[ ] translations/es-ES/content/repositories/working-with-files/managing-files/renaming-a-file.md
[ ] translations/es-ES/content/repositories/working-with-files/managing-large-files/collaboration-with-git-large-file-storage.md
[ ] translations/es-ES/content/rest/overview/other-authentication-methods.md
[ ] translations/es-ES/content/search-github/searching-on-github/searching-code.md
[ ] translations/es-ES/content/search-github/searching-on-github/searching-commits.md
[ ] translations/es-ES/content/search-github/searching-on-github/searching-in-forks.md
[ ] translations/es-ES/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
[ ] translations/es-ES/data/reusables/package_registry/authenticate-packages.md

broken liquid tags
113 files:

[ ] translations/es-ES/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-net.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-powershell.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-python.md
[ ] translations/es-ES/content/actions/automating-builds-and-tests/building-and-testing-ruby.md
[ ] translations/es-ES/content/actions/deployment/about-deployments/about-continuous-deployment.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md
[ ] translations/es-ES/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md
[ ] translations/es-ES/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md
[ ] translations/es-ES/content/actions/learn-github-actions/environment-variables.md
[ ] translations/es-ES/content/actions/managing-workflow-runs/manually-running-a-workflow.md
[ ] translations/es-ES/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md
[ ] translations/es-ES/content/actions/managing-workflow-runs/skipping-workflow-runs.md
[ ] translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md
[ ] translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md
[ ] translations/es-ES/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
[ ] translations/es-ES/content/actions/publishing-packages/publishing-docker-images.md
[ ] translations/es-ES/content/actions/security-guides/encrypted-secrets.md
[ ] translations/es-ES/content/actions/security-guides/security-hardening-for-github-actions.md
[ ] translations/es-ES/content/actions/using-jobs/using-conditions-to-control-job-execution.md
[ ] translations/es-ES/content/actions/using-workflows/about-workflows.md
[ ] translations/es-ES/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
[ ] translations/es-ES/content/actions/using-workflows/storing-workflow-data-as-artifacts.md
[ ] translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md
[ ] translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md
[ ] translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
[ ] translations/es-ES/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md
[ ] translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md
[ ] translations/es-ES/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md
[ ] translations/es-ES/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
[ ] translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md
[ ] translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md
[ ] translations/es-ES/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md
[ ] translations/es-ES/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md
[ ] translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md
[ ] translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md
[ ] translations/es-ES/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
[ ] translations/es-ES/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md
[ ] translations/es-ES/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md
[ ] translations/es-ES/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
[ ] translations/es-ES/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md
[ ] translations/es-ES/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md
[ ] translations/es-ES/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md
[ ] translations/es-ES/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
[ ] translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
[ ] translations/es-ES/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md
[ ] translations/es-ES/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md
[ ] translations/es-ES/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md
[ ] translations/es-ES/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md
[ ] translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
[ ] translations/es-ES/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
[ ] translations/es-ES/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md
[ ] translations/es-ES/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
[ ] translations/es-ES/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md
[ ] translations/es-ES/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
[ ] translations/es-ES/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md
[ ] translations/es-ES/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
[ ] translations/es-ES/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md
[ ] translations/es-ES/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students.md
[ ] translations/es-ES/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md
[ ] translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
[ ] translations/es-ES/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
[ ] translations/es-ES/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md
[ ] translations/es-ES/content/get-started/exploring-projects-on-github/following-organizations.md
[ ] translations/es-ES/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
[ ] translations/es-ES/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
[ ] translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
[ ] translations/es-ES/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md
[ ] translations/es-ES/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
[ ] translations/es-ES/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md
[ ] translations/es-ES/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md
[ ] translations/es-ES/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md
[ ] translations/es-ES/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
[ ] translations/es-ES/content/pages/getting-started-with-github-pages/about-github-pages.md
[ ] translations/es-ES/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
[ ] translations/es-ES/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md
[ ] translations/es-ES/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
[ ] translations/es-ES/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md
[ ] translations/es-ES/content/repositories/creating-and-managing-repositories/deleting-a-repository.md
[ ] translations/es-ES/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md
[ ] translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
[ ] translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md
[ ] translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md
[ ] translations/es-ES/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md
[ ] translations/es-ES/content/support/learning-about-github-support/about-github-support.md
[ ] translations/es-ES/data/reusables/actions/release-trigger-workflow.md
[ ] translations/es-ES/data/reusables/audit_log/audit-log-action-categories.md
[ ] translations/es-ES/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md
[ ] translations/es-ES/data/reusables/enterprise_installation/hardware-rec-table.md
[ ] translations/es-ES/data/reusables/gated-features/packages.md
[ ] translations/es-ES/data/reusables/package_registry/authenticate-to-container-registry-steps.md
[ ] translations/es-ES/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md
[ ] translations/es-ES/data/reusables/package_registry/publish-docker-image.md
[ ] translations/es-ES/data/reusables/package_registry/visibility-and-access-permissions.md
[ ] translations/es-ES/data/reusables/support/premium-support-features.md

Uploading<EMAIL_ADDRESS>Uploading<EMAIL_ADDRESS>Uploading<EMAIL_ADDRESS>Uploading<EMAIL_ADDRESS>


Docker proposal

Follow up to https://github.com/nteract/hydrogen/pull/524
I think the simplest way is a dockerfile:
FROM python:2
ARG TINI_VERSION=v0.10.0
ADD https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini /tini
RUN chmod +x /tini
RUN pip install jupyter_kernel_gateway
ENV KG_LIST_KERNELS=True

A docker-compose:
version: '2'
services:
  jupyter:
    context: .
    entrypoint: ["/tini", "--"]
    command: ["jupyter", "kernelgateway", "--ip=<IP_ADDRESS>", "--port=8888"]

And a kernel settings default:
[{"name": "docker", "options": {"baseUrl": "http://localhost:8888"}}]

I'd propose this replaces basically all the README from L250-580. But probably I'm missing something and there's useful stuff there?
Questions:

Do we need a docker-compose file, or should we just the commands in the dockerfile?
Should we map the current path by default? This would allow you to run the code you're working on
What else are we missing?

Thanks for opening the issue. Unfortunately I don't know much about Docker.
@tiangolo May be able to answer your questions.

Thanks for the response @tiangolo !

...But in that case, wouldn't it be easier to use a Jupyter Docker stack?

Yes, good idea.

Or the equivalent docker-compose.yml, probably both options.

Agreed

The kernel settings wouldn't necessarily be like you specified above, as many users won't run that from a Linux machine but rather from Windows or Mac, and in those cases it will mostly be a Virtual Machine with a local IP (as <IP_ADDRESS>).

I use Docker for Mac and localhost worked for me. What makes you think you need the IP?

So it should probably be kept for backward compatibility.

Your call, but there is a lot there! Might be simpler as a link to a 'Further detail' / 'Previous implementation' page. For a first time user, there's a lot of detail that's not really needed, and makes it look arduous to set this up when it's surprisingly simple. I'm sure there are several good approaches for making it simpler, though.

I think I can easily add that to the README.md (it's almost already written in this issue 😆 ). Or do you want to take a stab at it and create a PR?

If you want to add it I would be honored! If you prefer me to, I'm happy to take a stab in the near future.

Excellent @MaximilianR !
Let's try with a Jupyter Docker stack.

I use Docker for Mac and localhost worked for me. What makes you think you need the IP?

Interesting that it just works in Mac! I didn't know. In Docker for Windows, and in Docker Toolbox (at least in Windows) it doesn't work like that, the VM gets an IP in the local (VM) network, so you have to use that IP (it is not bound to the localhost).
On the other side, if the user is connecting to a Docker running in a different machine in the same network, the IP would also be different.

Your call, but there is a lot there! Might be simpler as a link to a 'Further detail' ...

You're right. It is a lot indeed. Maybe we can split it in a separate file KERNEL_CONNECTION.md and link to it from the main README.md as with the plug-ins.

So, the steps to do would be:

Move everything from the section Custom Kernel Connection to a file KERNEL_CONNECTION.md and link to it from that section with a short note explaining what it is and that the easier method would probably be the Kernel Gateway "documented above".

In the Example Kernel Gateway section add a sub-section with instructions on how to set it up with a Jupyter Docker Stack. Including:

A Dockerfile
How to build and run it with docker commands
How to build and run it with docker-compose
A note with a link to jump to the Connect Atom section as those instructions would also apply unmodified.

The section Testing it gets a note to generalize it to both Dockerfiles.

In the section Terminate the connection and container add a note explaining how to do it with the Jupyter Docker Stack (that would be a lot simpler).

Is that right @MaximilianR ?
Would that be OK @lgeiger ?

Beautiful, @tiangolo

In the section Terminate the connection and container add a note explaining how to do it with the Jupyter Docker Stack (that would be a lot simpler).

That's just Ctrl-C now 💃

@tiangolo @MaximilianR Thank you a lot for those excellent explanations! I'm sure that this will help a lot of users 🎉
I love the idea of a separate KERNEL_CONNECTION.md file!

Would that be OK @lgeiger ?

That sounds awesome!

Excellent! I'll test the setup and work on a PR.

As the PR is already merged, I think we can close this issue.


Add a synchronous mapping API

Can be used to traverse or map elements contained
in any nested container or tuple-like type.
Meant for replacing the internal API of
hpx::util::unwrapped and some functions
which are used to wait on futures.

This is the first PR for my GSoC project, which implements the unified (synchronous) internal API
for re-implementing unwrapped as well as providing helper methods for synchronous functions
that wait on futures like wait_all.
ToDo:

[x] I need to fix allocator remapping across containers, which is implemented
but only working for trivially constructible allocators as of now.
[x] We need to find a solution for defining the HPX_HAVE_EXPRESSION_SFINAE macro accordingly.
The issue is that I can't find a particular minimalistic example which could be used to detect the
capability of the compiler to compile the API.
All I know is, that Visual Studio isn't capable as of now to evaluate the expression SFINAE correctly.
This leads to a less performant implementation on Windows which traverses elements although they
contain no element, which is effectively accepted by the mapper.

Tested Compilers:

Visual Studio 2015 Update 3 (without HPX_HAVE_EXPRESSION_SFINAE)
Visual Studio 2017 (without HPX_HAVE_EXPRESSION_SFINAE)
GCC 4.9 (with HPX_HAVE_EXPRESSION_SFINAE)
GCC 5.4 (with HPX_HAVE_EXPRESSION_SFINAE)
Clang 3.9 (with HPX_HAVE_EXPRESSION_SFINAE)

@sithhell First of all thanks for your review, I highly appreciate that.
As of now, I don't have any plans on making this API more customizable than it is, mainly due to the circumstance that this API does provide enough features to implement my project and possible future requirements are not known for me.
However, the API is really adaptable in the way that we can map or traverse arbitrary types (this isn't tied to futures like in unwrapped), so my opinion is that it's most generic as possible when taking a look at the current known requirements.
Additionally, the API can be easily refactored and extended through adapting the container_match_tag, that is responsible for providing the special mapping for a particular type category (like container or tuple-like types).

Makes sense. Are you planning on doing the unchecked TODO items within that PR or will you submit following ones? If the latter, I would like to ask you to move the missing TODOs into a separate issue so that we are able to track process.

I plan to resolve the outstanding ToDo list items before this PR gets merged (the allocator issue will be resolved by tomorrow and for the capability macro I need some help from the maintainers, since I don't know how to solve it while keeping the conformance to the current practices).

Did you have a look at this:
https://github.com/STEllAR-GROUP/hpx/blob/master/cmake/tests/cxx11_sfinae_expression.cpp?
This test is compiled during the CMake configuration run. If compiled successful, the define HPX_HAVE_CXX11_SFINAE_EXPRESSION should be set (https://github.com/STEllAR-GROUP/hpx/blob/master/cmake/HPX_PerformCxxFeatureTests.cmake#L27-L28). If this test doesn't fully cover your needs, we need to think about extending it. A backtrace to what is failing might be valuable here.

Sadly HPX_HAVE_CXX11_SFINAE_EXPRESSION passes on MSVC 2017 (or is automatically set to true).
Microsoft did a lot of work on expression SFINAE recently, however it fails to evaluate the nested expression SFINAE I used, but it is capable of evaluating simple expressions.
On stackoverflow I found an example case that still fails: https://stackoverflow.com/questions/35669239/the-c-detection-idiom-is-not-working-as-expected-in-visual-studio-2015-update however, I don't think that we can reduce the issue I have in this API to a minimalistic example.
Probably the best way to test the capability would be to try out, whether we can compile the API with HPX_HAVE_EXPRESSION_SFINAE and if it doesn't compile, we undefine it.

Probably the best way to test the capability would be to try out, whether we can compile the API with  HPX_HAVE_EXPRESSION_SFINAE  and if it doesn't compile, we undefine it.

Sure this would be a viable feature test.

@hkaiser Today, I tried to add a feature test like described above, however I'm facing two major issues:

The feature test would require dependency includes (like boost), however those depend on other feature tests for configuration. -> I could move this single feature test behind the dependency setup.
But the major issue is that the implementation implicitly depends on the hpx/config/defines.hpp  header that is generated as a result of this feature test. I can't remove this dependency since it's effectively used in other header. -> Maybe I could generate a second define.hpp just for this feature test

@Naios: inspect is still unhappy with this: https://7080-4455628-gh.circle-artifacts.com/0/tmp/circle-artifacts.B1i3Bir/hpx_inspect_report.html

@hkaiser Thanks for noticing, I corrected this.
Also the two outstanding points are fixed now:

Allocators are correctly detected and remapped through the facilities of the standard library
Full expression SFINAE support is detected through a special feature test, that uses my implementation. Therefore the generic possibility was added to specify feature tests which use header only parts of HPX to test the compiler for a particular capability.

From my side this PR finished and thus ready for the final review and merge.

@hkaiser Thank you for your feedback, I corrected all mentioned points.


Change in scss file does trigger recompilation but not reloading

OS?
Windows 7

Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.

create new project ng new sassy-project --style=sass
run ng serve
make changes in app.component.scss
Expected: reloading page
Actual: not reloading page :smirk:

The log given by the failure. Normally this include a stack trace and some
more information.

No log

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

This looks obsolete as coming version of cli will use webpack instead of brocolli, Let us know if this is still reproducible in master

It is working on master. I have another issue with sass but I'll post that in a new issue report.


Can't use * class for every type of file for SharpContextMenu

When you try to do the following:
[COMServerAssociation(AssociationType.ClassOfExtension, "*")]
public class ShellExtension : SharpContextMenu

RegAsm will fail and complain that The specified path is invalid. After digging through the code really quickly, not having much experience with shell extensions yet, it seems that it's trying to get the default value of HKCL\*, which is null in all cases, where as every other class such as .txt actually have a correct default value: txtfile for example.
Is it not possible to implement a handler for *? Is there a workaround for this, or will there be a fix?
Thanks for the great library, by the way!

Closing stale issues to focus on ones with end-user activity.


Composite.get is slow

I'm trying to create my own renderer, and did the following, which turned out to be slow, any tips? I'm using bitECS and a canvas. To link an entity to the matter.js body I created a component Physics with the attribute id that is given the id of the Body of matter.js
(world: IWorld) => {
   const blocks = blocksQuery(world)

   for (let i = 0; i < blocks.length; i++) {
      const eid = blocks[i]
      const body = (<Matter.Body>Composite.get(engine.world, Physics.id[eid], 'body')).position

      ctx.strokeStyle = '#FFFF00'
      ctx.strokeRect(Math.floor(body.x / 5 - 10), Math.floor(body.y / 5 - 10), 20, 20)
   }

   return world
},

Any ideas how to achieve a link between a library that focuses on ECS and matter.js?

Why not reference the body directly? You should have a reference to it when you create it, right? Composite.get will search the whole tree starting with engine.world for every call.
I see also you're using .position, but maybe better to store the actual body, which can easily access the .position when needed, depending on your needs.

Yeah exactly as @ggorlen mentioned, you should just keep hold of a direct reference rather than searching.

I see. Well, yeah, the problem is that ECS doesn't quite like objects, that's sad.

I have created a table that connects entity id's with the references that binds the ecs package with matter.js While not the cleanest solution, definitely a possible one.


Deprecator overrides global warnings

Describe the bug
This line attempts to restore the previous state of warnings which is changed on line 42. Unfortunately it assumes that the previous state is 'default' which is not always the case. If you have elsewhere set ENV variables to define your python warnings behavior this will override them.
This bug was surfaced by this commit
Your environment
Linux-3.10.0-957.12.2.el7.x86_64-x86_64-with-centos-7.7.1908-Core
('Python', '2.7.15 (default, Dec 11 2018, 21:06:48) \n[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]')
('pyfakefs', '3.7.2')

Thanks - good catch! Will probably have a look tonight.


Core stack when test causes core dump

Added a log for taking stack trace of any core if existed after the test run.

👍

Test PASSed.


Indicate if Webpack V2 is supported in the Readme

I'm submitting a feature request
Webpack version:
2.3.2
Webpack Karma version:
2.0.3
Karma version:
1.5.0
Please tell us about your environment:
Windows 7
Current behavior:
Read Me does not indicate if the documentation is for Webpack 2 or for Webpack 1
Expected/desired behavior:
The Read Me would clearly indicate if the examples are for Webpack 2 or Webpack 1 (or both)

What is the motivation / use case for changing the behavior?
So that users of the project can know if errors they are having are due to incompatibility with Webpack 2.

super important , co's that is karma-webpack

Note that if you installs karma-webpack, then later add webpack 2.x to package.json, you need to delete the webpack installed for karma-webpack (i.e. there's no peer webpack version so karma-webpack will install and use its own webpack at node_modules/karma-webpack/node_modules/webpack), because it'll be version 1.x.

So, if update to webpack 2, what is the minimum required version of karma-webpack?

Just to mention webpack 3 is out now too, so would be good to mention that too.


Digger minimal node client backbone

Minimal example for digger node.js client
Supported methods:

login
job creating
triggering build
fetching logs

Review @aliok @matzew

VERY COOL! @wtrocki  :-)
BTW. @aliok is on PTO today

@wtrocki We are not using shrinkwrap, riight ?  At least I hope so :-)

I am getting this, locally w/ the client:
➜  digger-node git:(31eba05) ✗ node ./bin/digkins.js login https://jenkins-digger.osm3.feedhenry.net
Username: admin
Password: ****************
bin/digkins.js login <url> [user] [password]

Options:
  --version   Show version number                                      [boolean]
  -h, --help  Show help                                                [boolean]

auth.createJenkinsOptions is not a function

node --version
v6.9.1

@wtrocki do I need different node version ?

@matzew
No shrinkwrap used because I'm using fixed versions in package.json. So we should not have shrinkwrap here and possibly no shrinkwrap in any other projects.
Good point about node version. I would mark that we support node>=4 in package.json

Using this GH project:
https://github.com/wtrocki/helloworld-android-gradle
returns in this error:
node ./bin/digkins.js log matzew-android 94
## Starting streaming build 1 log
Started by user Jenkins Admin
Cloning the remote Git repository
Cloning repository https://github.com/wtrocki/helloworld-android-gradle
 > git init /var/lib/jenkins/jobs/matzew-android/workspace@script # timeout=10
Fetching upstream changes from https://github.com/wtrocki/helloworld-android-gradle
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/wtrocki/helloworld-android-gradle +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url https://github.com/wtrocki/helloworld-android-gradle # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/wtrocki/helloworld-android-gradle # timeout=10
Fetching upstream changes from https://github.com/wtrocki/helloworld-android-gradle
 > git fetch --tags --progress https://github.com/wtrocki/helloworld-android-gradle +refs/heads/*:refs/remotes/origin/*
Seen branch in repository origin/Android-N
Seen branch in repository origin/FH-v3.10.0
Seen branch in repository origin/FH-v3.10.1
Seen branch in repository origin/FH-v3.11.0
Seen branch in repository origin/FH-v3.11.1
Seen branch in repository origin/FH-v3.12.0
Seen branch in repository origin/FH-v3.13.0
Seen branch in repository origin/FH-v3.13.1
Seen branch in repository origin/FH-v3.14.0
Seen branch in repository origin/FH-v3.15.0
Seen branch in repository origin/FH-v3.7.0
Seen branch in repository origin/FH-v3.8.0
Seen branch in repository origin/FH-v3.8.1
Seen branch in repository origin/FH-v3.9.0
Seen branch in repository origin/FH-v3.9.1
Seen branch in repository origin/RHMAP-3243_Forms-App-PDF-CSV-Export
Seen branch in repository origin/master
Seen branch in repository origin/revert-16-Android-N
Seen branch in repository origin/update
Seen 19 remote branches
Multiple candidate revisions
Checking out Revision 51406d8f429d4c9f31057314284273c0ab02955c (origin/Android-N)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 51406d8f429d4c9f31057314284273c0ab02955c
First time build. Skipping changelog.
ERROR: /var/lib/jenkins/jobs/matzew-android/workspace@script/Jenkinsfile not found
Finished: FAILURE

So, I could fetch the log file, with the node client (yay), but there is something wrong w/ the client ?

@matzew - Tested, it works fine.

COOL

@josemigallas can you test this too, before we merge it ?
Feel free to test against OSM3, shared cluster

I trriggered a build, and did fetch the logs:
 node ./bin/digkins.js log matzew-android 97

First time: worked good
Now, running that above comment a second time, to fetch the logfile again, I am getting:
error: Cannot fetch build log for matzew-android

@wtrocki Not sure I get what's the number (97 in this case) means.
the build job on Jenkins itself is #3:
https://jenkins-digger.osm3.feedhenry.net/job/matzew-android/3/

@matzew When triggering build it's placed in the queue (there is no build number initially because build may wait a little for possible executors). 97 is just jenkins queue number that would allow you to query your request all the time. Later when your build would start you get this '#3' number and you can use it as well, but 97 number is easyer from the api point of view because you do not need to pull jenkins until job would be scheduled. Making some final cuts to the client

node ./bin/digkins.js log matzew-android 3  gives me no log as well

@matzew that's strange. I'm going to investigate this once I would deal with other comments.
Thanks for really good review guys!

@matzew I replicated problem with logging and it looks like issue with jenkins. Some kind of variation of: https://issues.jenkins-ci.org/browse/JENKINS-27256.
Basically jenkins removes them after a while, which is against their documentation.

@wtrocki number 97 in @matzew 's case is not related to the job. So, the call could be
node ./bin/digkins.js log 103

or
node ./bin/digkins.js log 3

Fetching logs didn't work in my trial as well.

@aliok This was just client backbone and I explained wht this fails and how we going to resolve it. Looks like queue item is disappearing shortly after work is build, so we would need to wait until work would be queued to build (this can take time depending on other jobs running) and then use job number to retrieve job details. We can clearly inspire here by other clients like nestor:
https://github.com/cliffano/nestor


Support for existing content (pull from a source peer)

Is your feature request related to a problem? Please describe.

Support for existing content (pull from a source peer)

Describe the solution you'd like

A new endpoint to tell delta to pull a CID from a remote Peer.
The metadata request will need to include an array of source peers.

I'm going to add two new states

pull-requested

pull-on-going

pinned (the first state of a content being pinned).


SyntaxError in FireFox 52

Versions
nuxt: 2.15
node: v10.12.0
firefox 52 xubuntu
Reproduction
After updating nuxt from 2.14.12 to 2.15 there is an error in firefox 52 console
SyntaxError: invalid property id
Link to reproduce

@danielroe Link to sandbox is already in the issue description. Or you can use starter nuxt template with 2.15 version of Nuxt


Help with installation

System Details

OS: [e.g.  Ubuntu 22.04]
Thorium Version [e.g.126.0.6478.246]

Problem
Hello, I just started using linux, there was a problem with installing thorium.
Tried to install using these instructions - https://thorium.rocks/docs/building.html
Stuck on this step:

I get this response:

It says that there is no such file or directory at this path.
Can you please tell me where I got it wrong?
Did you read the FAQ?
Yes

https://github.com/Alex313031/thorium/releases
Please download the ready-made installation package from the above webpage without compiling it (unless you want to spend a lot of time and resources to do so)

Thank you very much.


Increment version for servicelinker releases

Increment package version after release of Azure.ResourceManager.ServiceLinker

API change check
API changes are not detected in this pull request.


Title: Android App for Covid 19 Vaccine Slot find Available check using PIN code

Is your feature request related to a problem? Please describe.
Covid 19 Vaccine Slot Available application 📱 built using Java ♨ and showing best practices of 🛠 API
Describe the solution you'd like.
GitHub Link : https://github.com/maityamit/covid_19_vaccine_slot_find
App Link : https://drive.google.com/file/d/1bSiO13LAU5NEyg6Hj9WSK1Sv1PNWO3a7/view
Describe alternatives you've considered.
This is built using Java language.
Add any other context or screenshots about the feature request here.
No response

@Kushal997-das  Kindly assign this issue to me


Revert wrong K8s minor version displays in v1.20 docs

This is a backport of this suggestion.
[As-is]

[To-be]

[Related issues/PRs]

#31551
#34349
#34346
...

[CC]

@sftim (from #34349)
@tengqm (from #34346)

/lgtm
/approve


Adds whats new page

Add a What's new page to Whitehall.
This page will update users on the new things that are being released.
This page exists in the content publisher and has been a way to communicate with users on what new features are being released.
https://trello.com/c/jNkqHsRV/712-add-whats-new-page

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

Hey bud, looks good just some minor updates.
Can you update the class to govuk-heading-l for the following headlines:

Moving to the design system
Recent changes
Publisher guidance, updates to GOV.UK and previous changes to Whitehall pubisher

Are the individual recent changes headline govuk-headling-m?
Also, mind updating the date's color to $govuk-secondary-text-colour

Hey bud, looks good just some minor updates.
Can you update the class to govuk-heading-l for the following headlines:

Moving to the design system
Recent changes
Publisher guidance, updates to GOV.UK and previous changes to Whitehall pubisher

Are the individual recent changes headline govuk-headling-m?
Also, mind updating the date's color to $govuk-secondary-text-colour

Recent changes is already govuk-heading-l, the other two are govuk-heading-m.
The individual updates are styled using govspeak, which I believe is govuk-heading-s.
Regarding the date colour, it is styled using the govuk-caption-m class - do you want to move away from this?

Thanks Kevin - will co-ordinate the release after the period is over.

From Carlos

Hey. Looks good. I just checked the spaces and it looks okay now.


Meta issue: gitlab issues

There are 12 open issues on the Drasil gitlab (https://gitlab.cas.mcmaster.ca/smiths/drasil/issues).  Some of these probably should be ported to here.  All of them should be reviewed for 'relevance' and re-assigned as appropriate.

Hello Jacques.  Good point.  I have gone through those issues.  Most of them should have been closed a long time ago.  I did find an issue that was not sorted out, so I have recreated in our GitHub repo as issue #196 .


Delete and truncate problematic tables #patch

The step to "truncate potentially problematic tables" left out tables that might cause issues. Only the NumberSequenceReference tables was truncated. NumberSequenceScope and NumberSequenceTable had rows that were related, but they were not deleted.
The step to remove problematic tables is now part of scale Unit Installation. This means that NumberSequence records can no longer be created between initializing the environment and installing workloads, which could cause the SYS package to fail.
This has been tested by running full deployment on SingleOnebox.
Resolves #113

Tested using the single execution deploy option, everything works as expected


[KB] fix formatting, edit grammar

https://ctliotest.atlassian.net/browse/CTLIO-1245

@JimGreene30 Please fix bad link


File change browsing on PRs

V1 can be read only (no commenting)

show change summary in PR
tap to go to file browser
each file shows change summary
tap to view changes

Nobody start on this yet. Going to be large and needs fleshed out more. Esp to prep for adding comments to files.

Would definitely love to get syntax highlighting working with this as well

simple version done!


fixed example passwords

These passwords in the showcase on the top page are invalid (too short). This will be inconvenient for newcomers who tried to copy-paste the snippet to see how PocketBase works.

Thank you but I don't think it is necessary. The code snippet are just an example and note that the min password length can be edited from the collection settings anyway.


require user to acknowledge bucket security advise before proceeding

Issue #, if available:
Description of changes:
Require users to acknowledge bucket security advice in the build script before uploading solution source code.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

skipping code review since this is a trivial change


React Todo App

In this branch, I have added the following;

[ ] Create a components folder to store the components.
[ ] Props to pass data to the child components.
[ ] Use hooks to update the state.
[ ] Use events to handle user interactions.
[ ] Lift state up.
[ ] Add readme file.

Hi, @Kaghenimbale, Thank you! :hugs:


merge folder

biz and biz_server can merge into a new folder (example im or chat,...) similar to the nbfs

Do not combine, then split biz_server, such as independent auth_server, etc.


Support duckdb semi and anti joins

https://duckdb.org/docs/sql/query_syntax/from.html

Also positional.


Invalid "invalid cyclic type reference" error

Description:
import ballerina/io;
type F function() returns function?;
// I should be able to write: type F function() returns F?;
// Even type F function() returns F

function f(int i) returns F? {
    if i == 10 {
        io:println(i);
        return ();
    }
    return f(i+1);
}

public function main() {
    F? k = f(0);
}

I think this should be possible.
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Duplicate of https://github.com/ballerina-platform/ballerina-lang/issues/32735.

Ohh my bad


bluebird as peer dependency

Can bluebird be moved in a peerDependency?
On the frontend otherwise it can not pay nice with other promises in the code that use a different version.

Good idea. Done in #22.


When preview API would become GA?

Somehow I didn't find any related information on internet. Thanks.

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

ID: a107ff90-611f-c6fc-539b-4ff061b868f5
Version Independent ID: 4cd881b1-41bc-07b2-7be4-22ef360e267a
Content: API for Dynamics 365 Business Central - Dynamics NAV
Content Source: dynamics-nav/fin-graph/index.md
Service: dynamics365-financials
Product: unspecified
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Hello,
Thanks for your feedback, there were indeed two links in the reported topic that did not work. This has been fixed and will work when the docset is refreshed. In the meantime, for your reference, I am pasting in the links that the topic was supposed to link to: Getting Started Developing Connect Apps for Dynamics 365 Business Central and Development in AL. As for the question in the title of this feedback, I do not have any update.
Thanks again for reporting this.


Performance

Okay, so a while back I pointed out the performance of this plugin, and got told to wait for 12.06. Well the release of 12.06 has come and gone, and the stutters remain. Overall fps is higher, which tells me LR did something, so I am highly suspect this plug-in is the issue. It’s a great one, but I would love to see some performance improvements in the near future.

I also have a problem with performance. 80% of the time fps is in the 30s or 40s but for some reason, it drops to 20fps for 30-60 seconds. I suspect it has something to do with new tiles being loaded.

This issue is still present in V0.7.1 with X-Plane 12.07  and X-Plane 12.08-Beta-1.

Not only does the frame rate drop, also ATC becomes extremely laggy or even unresponsive for a minute or even longer (had it for 3-4 minutes lately.
Tested on 12.0.8-rc3

Im in the same boat at @tzimpel I think. The issue has persisted since 0.5 which I just attributed to the newness of program.
The biggest annoyance I have is what I call the last 2000ft. On final into an airport and frames just take a dump because I assume its rendering new tiles. Need the program render new tiles/ distance based on speed/ alt.


Weird glitches when dialog changes size (redraws/remeasures)

@teslacoil that shake issue is still there.
I came across it while creating a FAQ dialog for Moonshine icon pack's redesigned dashboard (which I'm helping the dev out with).
It seems as though there's an infinite redraw loop going on here or something.

If it doesn't shake, then it seems to move up for a second, and then move down once measured.

Do you have sample code to reproduce? (and the device/screen size/dpi you're testing against).
Just taking a quick look, 81197a67 seemed to add conditional titlebar padding, I'd guess that it needs similar constraints as the bottom margin in setDividerVisibility ("Only enable the bottom margin if our available window space can hold the margin")
The conditional padding is a pain. A custom root view that does the measures and applies the padding might be easier to maintain than having callbacks and checks in the Dialog, this might also help with the slow remeasure/relayouts as we should be able to do it in one pass, whereas it seem something is taking multiple passes here.

Well at the moment, it's noticeable with this library's sample project (the folder chooser).
It feels very laggy, and if the title divider appears for the first time it pushes the content down after 1-2 seconds.

I'm almost tempted to rebuild a lot of this library to use less programatic setup, but that would obviously take quite a bit of time.

@teslacoil actually, here's a good example. It's noticeable if you tap the "FAQ" option. When you tap to expand items in that dialog (more so when you do it a few times), the dialog lags and skips around: https://drive.google.com/file/d/0B3ztrEIRfGuCTDZEWEVlSHJkeUU/view?usp=sharing

The shaking issue was showing the divider, triggering a relayout, and hiding the divider, so they wouldn't just wiggle once but continuously shake. (it didn't fully block the UI thread, but it was barely usable) This at least only happens once (per layout change).
The dividers could be simplified to be either VISIBLE or INVISIBLE, so they never cause layout changes, but the padding is killer, and the padding in the button bar changes the size of the content (which can change the size of the button bar, which we prevent, but I think still causes another measure/layout pass, and it changes the size of the window which might also cause a measure/layout pass).
There's also a user experience issue here, even without the lag, is it a good experience to have an on screen dialog change size? I'd say no. The FAQ example would be better if the first time you view the dialog it was full sized and clicking a question didn't change the window size/position. The folder chooser example would look a bit sparse when you're in an empty directory if the dialog didn't shrink back down, but personally I think the chooser is already bad UX for a number of reasons (file choosers in general though I admit there is a use at times, no clear way to know if back will cancel or go back, window drastically changes size, position of title and OK/Cancel move), so it might be better to ignore that use case and focus on ones like the FAQ.
I'm not personally using any dialogs that change size while on screen, so I don't have that strong of feelings on how they should work. Killing the button bar padding is kind of a shame for small dialogs, but it would simplify things. An option to force the divider/padding/scrollable mode regardless of content is kind of a workaround and awkward to name the parameter or document, but would be easy.
I can take a look at doing a custom root view that more intelligently handles the dividers and padding, preferably with just one pass (or at least one layout pass, maybe two measures). But it will likely need to wait until either I add require a dialog that changes size, or after I get my update released as stable.

@afollestad @teslacoil We noticed the issue when using MaterialEditText.  The MaterialEditText view typically does a resize animation when making room to display an error message.  When inside of a MaterialDialog the resize animation seems to happen, but the text doesn't appear until it is over.  Here is a screen capture showing the issue.

I was getting glitches when using the sample Folder Chooser dialog and with my "fix" I believe it is not happening anymore.
The only problem, is I can't fix the glitch with hiding the 8dp margin below the buttons once the bottom divider is shown. It seems that when you set that margin to 0, it is actually applied later than the rest, so you see the buttons move down into place. The only way I could stop this was removing the 8dp bottom margin, but that made the normal dialog buttons look too close to the edge.

The recent pull request didn't fix this, it messed up some spacing in the process.
I undid it.

Oh okay, fair enough. The Folder Chooser sample seemed to be much less glitchy, so thought it had improved it. Ah well!

@andrewlord1990 can you issue a pull request to @afollestad ? that resizing bug its pretty annoying and i don't want to fork just for that since you already fixed it

I'm really sorry. I did a pull request with my changes, as I observed the Folder Chooser sample was much more stable, but @afollestad has said that I didn't actually fix it, so it was reverted. Sorry.

It looks like the major issue now is that padding is invalidated in onShow() of MaterialDialog.java. There's a short delay from when the dialog actually shows, and when the OnShow callback is invoked by the Android framework.

I've started on this, I created a custom MDRootLayout that does it's own measure/layout of the root elements (titlebar, content, buttons) and it can make the padding/stacking decisions all from onMeasure (so no need to invalidate after onShow). The folder chooser is so much faster and doesn't wiggle or draw at the wrong size momentarily or anything. I still need to verify the padding for various things as it's implemented a bit different now, but hopefully I can submit a pull request soon.

Awesome, sounds good. Whenever that's done, I will push another release along with the new progress dialog theming stuff.

Here we go: https://github.com/afollestad/material-dialogs/pull/392

https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>


transparent background navigationcontroller

HI,
I have a strange problem. If I make transition by navigation controller from 1 to 2 view controller and 2nd viewcontroller has a transparent background so it get for some ms black. but it is possible to observe. Do you know how to solve it?
Thanks.

I would be happy to help, please connect on Material Gitter. Thank you!


Provide PLOT4ai threat categories

Describe what problem your feature request solves:
PLOT4ai is a library containing threats related to AI/ML.  It would be good to have the categories of this library, which are based on LINDDUN, available in Threat Dragon
Describe the solution you'd like:
Provide PLOT4ai categories:

Technique & Processes
Accessibility
Identifiability & Linkability
Security
Safety
Unawareness
Ethics & Human Rights
Non-compliance

Additional context:
a pull request was recently added #683 that could be used to guide the changes for PLOT4ai

Thanks for taking this on @rhite-tech


Separate Kernel Specs & Python envs in kernel pick

Fixes #11927
Part of #11904

Codecov Report

Merging #11926 (415019e) into main (3c58033) will decrease coverage by 5%.
The diff coverage is 77%.

@@           Coverage Diff            @@
##            main   #11926     +/-   ##
========================================
- Coverage     62%      57%     -6%
========================================
  Files        490      491      +1
  Lines      34602    34702    +100
  Branches    5616     5624      +8
========================================
- Hits       21691    19949   -1742
- Misses     10831    12678   +1847
+ Partials    2080     2075      -5

Impacted Files
Coverage Δ

src/kernels/raw/types.ts
100% <ø> (ø)

...llers/kernelSource/notebookKernelSourceSelector.ts
10% <40%> (+<1%)
:arrow_up:

src/platform/common/utils/localize.ts
69% <71%> (-7%)
:arrow_down:

...raw/finder/contributedLocalPythonEnvFinder.node.ts
76% <76%> (ø)

src/kernels/internalTypes.ts
100% <100%> (ø)

...aw/finder/contributedLocalKernelSpecFinder.node.ts
75% <100%> (ø)

src/kernels/serviceRegistry.node.ts
100% <100%> (ø)

src/platform/common/utils/text.node.ts
14% <0%> (-81%)
:arrow_down:

src/platform/common/experiments/telemetry.node.ts
22% <0%> (-78%)
:arrow_down:

src/kernels/installer/pipenv.node.ts
13% <0%> (-67%)
:arrow_down:

... and 125 more


Implement support for PROXY Protocol

What do these changes do?
Implements support for the PROXY Protocol, notably the version as documented in v2.3.0 of the HAProxy program.
Are there changes in behavior for the user?
Should not affect existing users.
Related issue number
Closes #174
Checklist

[x] I think the code is well written
[x] Unit tests for the changes exist
[x] tox testenvs have been executed in the following environments:

[x] Windows 10 (via PyCharm tox runner): (ALL)
[x] Windows 10 (via PSCore 7.1.1): (ALL)
[x] Windows 10 (via Cygwin): qa,py-nocov
[x] Ubuntu 18.04 on WSL 1.0: (ALL) + pypy3-{nocov,cov,diffcov}
[x] FreeBSD 12.2 on VBox: (ALL) + pypy3-{nocov,cov,diffcov}
[x] OpenSUSE Leap 15.2 on VBox:  (ALL) + pypy3-{nocov,cov,diffcov}

[x] Documentation reflects the changes
[x] Add a news fragment into the NEWS.rst file

This pull request introduces 1 alert when merging 64111e5 into 6404ab2 - view on LGTM.com
new alerts:
* 1 for `__eq__` not overridden when adding attributes

Oh for cryin' out loud!
IT WAS INTENTIONAL. DOESN'T THE "SUPPRESSION" INDICATE THAT ALREADY

@pepoluan Feel free to ping me for review of this one, once it's good. It appears a proper rebase should be done?

@pepoluan Feel free to ping me for review of this one, once it's good. It appears a proper rebase should be done?

Actually, I've been merging back from master for every change, so no additional rebase is necessary.
Even if there's a conflict, I prefer to merge from master then pushing back.
If there's no conflict, we can go direct to squamerging and all should be well.

Actually, I've been merging back from master for every change, so no additional rebase is necessary.

Looking at the diff and the huge number of more than 400 to-be-merged commits it looks like something went wrong. This PR as of right now appears to include unrelated changes.

Actually, I've been merging back from master for every change, so no additional rebase is necessary.

Looking at the diff and the huge number of more than 400 to-be-merged commits it looks like something went wrong. This PR as of right now appears to include unrelated changes.

It was due to all the rebasing that messes up the git history. That is why I don't want to rebase anymore.
(When squamerged it will all play out, no worry about that.)
If you check "Files changed", you will also see that there are lots of ".rst" files being changed. This is because this PR is finalized after #245 was finalized, and I cannot make a clean change to master that also applies cleanly to #245 due to the numer & shape of changes. So I merged from #245.
If you want to review the changes, your best bet is to use the "Files changed" tab and either (1) focus only on ".py" files ignoring others, or (2) wait until #245 gets merged, which should prune the number of files changed greatly.

FWIW sometimes a rebase will collect more commits than necessary - use git rebase --interactive and make sure you only have the commits you're interested in.

FWIW sometimes a rebase will collect more commits than necessary - use git rebase --interactive and make sure you only have the commits you're interested in.

Thanks! That's a powerful tool, indeed!
I've carried out an interactive rebase, and now it's down to 108 commits.
I'll merge master to the latest state, and do another commitpush.

I've carried out an interactive rebase, and now it's down to 108 commits.

Thanks, that's looking much better now. I'll see when I have a bit of time to look deeper into this. Thanks for taking the time to work on this, especially with including all my wishes :smiley:

Did not do another functional test after the recent adjustments. I trust that you know what you are doing here. As my remarks have been resolved this LGTM now. Thank you for taking the time to tackle this and also for taking all my suggestions / complaints into account 😃

No problem!
It has been a good exercise for me 😉
This will get merged no later than next Wednesday in 1.4.0.
Currently am focusing on releasing 1.3.1 because 1.3.0 broke people's servers 😓

Final checks. If all these succeeds, then I'll squamerge.

[ ] Windows 10 (via PyCharm tox runner): (ALL)
[ ] Windows 10 (via PSCore 7.1.2): (ALL)
[ ] Windows 10 (via Cygwin): (ALL)
[ ] Ubuntu 18.04 on WSL 1.0: (ALL) + static + pypy3-{nocov,cov,diffcov}
[ ] FreeBSD 12,2 on VBox: (ALL) + static + pypy3-{nocov,cov,diffcov}
[ ] OpenSUSE Leap 15.2 on VBox: (ALL) + static + pypy3-{nocov,cov,diffcov}

This post is undergoing edits.


Improvement in UI

Hi, Hope you are doing well.
So while scrolling through the website I noticed that the buttons of adopt me are kind of merged into the Card:

and second I noticed that the news section is not well managed in a card:

Please Assign this issue to be so I can fix it. Thank you.
Best Regards,
Muzamil Khan.

its not currently needed for website


Feature request: CSV output option when printing available accounts

When running
$ alks developer accounts

would like an option to print those accounts in a clean CSV format. Something like
$ alks developer accounts -o csv

990000000099/ALKSReadOnly - awstest,ReadOnly,Standard

This doesn't do CSV.. but might help?
alks developer accounts -e


Migrate progress indicator code into package

In https://github.com/kris-nova/kubicorn/pull/172, we've added an anonymous function to kubicorn/cmd/delete.sh, which indicates progress to a user during the execution of a long running task by repeatedly logging a symbol.
Goals

Integrate this function into a package sleeper or similar.
Symbol and interval (ms) shall be configurable.

@kris-nova and @xmudrii: Anything to add?

Feel free to assign this to me.

This sounds like a good idea to me. :+1: :smile:

Also agree - please take a stab at coding this @metmajer!


Several statsd logging bits

This PR contains several bits of statsd logging infrastructure.
In summary, it has the ability to log generation time and build time.

I like the usage of xchammer_config 👍


Correct the comment on absorb in SimpleHashFiatShamirRng

Description
Notice that the seed is updated in a way that is of a different order, we here modify the comment.
We may also want to do a quick double-check that this ensures a reasonable level of domain separation.
This is related to #86

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Updated relevant documentation in the code
[x] Re-reviewed Files changed in the Github PR explorer

N/A:

[ ] Wrote unit tests
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md

I assume that as long as the digest algorithm D and the random number generator R are different, then this should be fine.
One more problem about this sponge: the seed does not change when it is being squeezed more times.


Chores/initial project

Context
In this pull request, I continue the step of initialization after creating project by vitamin boilerplate.
Changes

introduce ADR (architecture decision record) to record every technical decision
update README
remove unnecessary boilerplate files
update eslint config
draft home page

Screenshot

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@8295a44). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff            @@
##             main        #1   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         1
  Lines           ?         3
  Branches        ?         1
========================================
  Hits            ?         3
  Misses          ?         0
  Partials        ?         0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


API GET /flow/{id} does not include database nodes configuration

Hey
if I have a database node and I GET the flow containing the node via API  GET localhost:1880/flow/{flowId} then the configuration of the database node is not included, however, it is included in the export of the node-red UI.
I have tested it using influxdb node and mongodb node
Thanks
API
{
  "id": "4880e9bc.a5c798",
  "label": "Flow 2",
  "nodes": [
    {
      "id": "126af684.cc3459",
      "type": "mongodb out",
      "z": "4880e9bc.a5c798",
      "mongodb": "5efe8db7.bf6ee4",
      "name": "",
      "collection": "test",
      "payonly": false,
      "upsert": false,
      "multi": false,
      "operation": "store",
      "x": 324.5,
      "y": 263,
      "wires": [

      ]
    }
  ]
}

Export
[
    {
        "id": "126af684.cc3459",
        "type": "mongodb out",
        "z": "4880e9bc.a5c798",
        "mongodb": "5efe8db7.bf6ee4",
        "name": "",
        "collection": "test",
        "payonly": false,
        "upsert": false,
        "multi": false,
        "operation": "store",
        "x": 324.5,
        "y": 263,
        "wires": []
    },
    {
        "id": "5efe8db7.bf6ee4",
        "type": "mongodb",
        "z": "",
        "hostname": "<IP_ADDRESS>",
        "port": "27017",
        "db": "mongo",
        "name": ""
    }
]
``

for general questions we prefer the mailing list (google group) or slack channel - both linked from the home page.
the config for the node is (by default) held globally ("on all pages") so you need to fetch the whole flow to get them - though people can specify them to go on a particular flow by selecting the button in the bottom right of a config page - in which case the config would be with that same flow id

Thanks for your response, yes normally I use the mailing list, however, I thought this was an issue.
I haven't noticed this part of the configuration in the online documentation though, but now everything goes into place.
Thank you


Error running built binary outside debugger

I'm getting an abort trap running ./ortho after building:
> ./ortho
Abort trap: 6
>

So, I ran it in the debugger, hoping to get a stack trace ... but it works fine there.
OS: macOS Big Sur 11.7.4 x86_64
Compiler:
> cc --version
Apple clang version 13.0.0 (clang-13<IP_ADDRESS>)
Target: x86_64-apple-darwin20.6.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
>

valgrind is only available for 10.x in MacPorts, or I'd try that.  Any other suggestions?

Did you code-sign your binary? On the new macs and Apple OSes code signing is required.
Abort trap may also be an assertion tripping, but then you would get a message on stderr. If you did code-sign it and/or that's not the problem, try running it in a debugger like lld (e.g. lld ortho)


chore(sqllab): Relocate user in SqlLab to root

SUMMARY
As a part of SQLLab SPA initiative, the SqlLab state will be consolidated into SPA redux store. In order to match the existing user state, this commit relocates the user property in SqlLab into root.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
After:

Before:

TESTING INSTRUCTIONS
Go to SQLLab and working without errors
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

I'm looking forward to this feature. Yey @justinpark!


Common format for compilation errors

Describe the use-case for this feature
Currently rust-analyzer doesn't support reporting compilation errors very well when the build system is not cargo (see https://github.com/rust-lang/rust-analyzer/issues/13437). A suggestion is this should be the responsibility of the BSP.
What do you propose
I propose extending the response of BuildTargetCompile to include compilation errors and their locations in the source files. This way, these errors could be shown via a generic integration between editors and the BSP.
I've checked to make sure there isn't already a way to support this in the current protocol

[X] I've checked the existing protocol and there isn't a way to do this currently

Maintainer approval (This is for the maintainers)

[ ] Jetbrains
[ ] Metals
[ ] Scala Center

I guess this would have to be language-specific though, so maybe not.

But we do already have https://build-server-protocol.github.io/docs/specification/#onbuildpublishdiagnostics-notification :)


Add Germinate

Insert URLs to the project here: https://github.com/germinateplatform/germinate-vue

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All new projects listed will be posted on our Mastodon channel.

@sebastian-raubach

@sebastian-raubach

Hi there, thanks for including us in this directory! We've got other tools that may be of interest:
https://github.com/cropgeeks

@sebastian-raubach Thanks for the tip.Unfortunately, I have to say that my expertise in bioinformatics is very limited, which makes it very difficult for me to assess which open source projects in this area are relevant to environmental sustainability.
I'll dig into cropgeeks to get a better understanding 👍


Update tr.po

Updated Turkish translations.

Hi, thanks for working on this! Most of CI builds are broken because of some syntax error on line 602 — can you please fix that?

Hi, thanks for working on this! Most of CI builds are broken because of some syntax error on line 602 — can you please fix that?

Fixed.

JFYI the FreeBSD 11.4 and Travis coverage builds are failing for an unrelated reason. I'll submit a PR fixing those in a couple minutes.


Added file.Close() call to file cache Get() method

The Get() method for the file cache was not closing files
that it opened. This will eventually cause an issue with
too many file descriptors being open.
closes #586

Pull Request Test Coverage Report for Build 88149d38e-PR-810

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 45.029%

Totals

Change from base Build 5013d2756:
0.009%

Covered Lines:
5439

Relevant Lines:
12079

💛  - Coveralls


CAT NOT use Jinja2 extends features with html-webpack-plugin

jinja2 templates:
base.html
{% block content %}
a.html
{% extends 'base.html' %}
{% block content %}
balabala
{% endblock %}
b.html
{% extends 'base.html' %}
{% block content %}
balabala
{% endblock %}
there's no way to inject output code.

Have you tried the 2.x beta branch with a loader?

thank you for reply, is there a example?

The 2.0 readme is a good start: https://github.com/ampedandwired/html-webpack-plugin/tree/feature/loaders
And there is an example for jade which should be very similar to your case:
https://github.com/ampedandwired/html-webpack-plugin/tree/feature/loaders/examples/jade-loader