text:
[corehttp] add support for multipart file tuples and for simultaneous data and file input

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/check-enforcer override


text:
[AutoRelease] t2-appcontainers-2024-10-10-38427(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/5587
Recording test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=4772

issue link:https://github.com/Azure/sdk-release-request/issues/5587

source: gharchive/pull-request

repo: Azure/azure-sdk-for-python

license: MIT

license_type: permissive

license_source: github-api


text:
Increment version for ml releases

Increment package version after release of azure-ai-ml

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


text:
[AutoPR cognitiveservices/resource-manager/cognitiveservices/data-plane/FormRecognizer/cognitiveservices/data-plane/QnAMaker] chore: jsonfmt cognitiveservices

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6318

(message created by the CI based on PR content)


text:
[AutoPR cost-management/resource-manager] CostManagement RP- Introducing API Version 2019-10-01 plus adding Modern Commerce Account Scopes to Query and Dimension APIs.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/7491

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/7904


text:
Convert CRLF to LF

Having some files using CRLF makes things extremely messy when
using tarballs on Linux, as the git repository gets automatically
converted, but the tarball stores the original line ending,
so the two do not match anymore.
Please consider adding automated conversion/checks to make the life of packagers easier. Thanks!

Ping

Another ping.

Hi @bluca
Sorry for the late answer here. I'm not sure I actually understand the problem, but that seems fair to me for licence files to be in LF anyway.

authors: bluca lmazuel


text:
Unexpected InvalidBlockList error when processing Multipart upload

Hey all, I'm trying to figure out how to upload Multipart stream to Azure Blob storage, but hitting InvalidBlockList error that does not provide much information on how to fix it. I'd be grateful if someone could have a look into what's going on.
Error: Error {
    context: Full(
        Custom {
            kind: HttpResponse {
                status: BadRequest,
                error_code: Some(
                    "InvalidBlockList",
                ),
            },
            error: HttpError {
                status: BadRequest,
                details: ErrorDetails {
                    code: Some(
                        "InvalidBlockList",
                    ),
                    message: None,
                },
                headers: {
                    "date": "Tue, 15 Aug 2023 19:40:18 GMT",
                    "server": "Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0",
                    "content-type": "application/xml",
                    "x-ms-version": "2019-12-12",
                    "content-length": "221",
                    "x-ms-request-id": "d058ea49-801e-0040-20b0-cf699e000000",
                    "x-ms-error-code": "InvalidBlockList",
                },
                body: b"\xef\xbb\xbf<?xml version=\"1.0\" encoding=\"utf-8\"?><Error>InvalidBlockList<Message>The specified block list is invalid.\nRequestId:d058ea49-801e-0040-20b0-cf699e000000\nTime:2023-08-15T19:40:19.2199377Z</Message></Error>",
            },
        },
        "server returned error status which will not be retried: 400",
    ),
}

Here's the code I'm using:
pub async fn upload(
    Extension(state): Extension<GlobalState>,
    mut multipart: Multipart,
) -> Result<Response, StatusCode> {
    let account = std::env::var("STORAGE_ACCOUNT").unwrap_or(STORAGE_ACCOUNT.to_string());
    let access_key  ="xxx";
    let container = std::env::var("STORAGE_CONTAINER").unwrap_or(STORAGE_CONTAINER.to_string());
    let blob_name = "test.mp4";

    let storage_credentials = StorageCredentials::access_key(account.clone(), access_key);
    let blob_client =
        ClientBuilder::new(account, storage_credentials).blob_client(&container, blob_name);

    while let Some(mut field) = multipart.next_field().await.unwrap() {
        let filename = if let Some(filename) = field.file_name() {
            filename.to_string()
        } else {
            continue;
        };

        let mut blocks = 0;
        let mut block_list = BlockList::default();
        let mut upload_futures = vec![];

        while let Some(chunk) = field.chunk().await.map_err(|_| StatusCode::BAD_REQUEST)? {
            println!("received {} bytes", chunk.len());

            let block_id = format!("block-{}", blocks.to_string());
            let data = chunk;
            let task = blob_client.put_block(block_id.clone(), data).into_future();

            upload_futures.push(task);
            block_list
                .blocks
                .push(BlobBlockType::new_uncommitted(block_id.clone()));

            blocks += 1;
        }

        let stream = futures::stream::iter(upload_futures).buffer_unordered(2);
        let results = stream.collect::<Vec<_>>().await;

        let resp = blob_client
            .put_block_list(block_list)
            .await
            .map_err(move |err| {
                println!("Error: {:#?}", err);
                StatusCode::INTERNAL_SERVER_ERROR
            })?;
        println!("resp: {:#?}", resp);

        return Ok(Response::builder()
            .status(StatusCode::CREATED)
            .body(boxed("OK".to_string()))
            .unwrap());
    }

    Err(StatusCode::INTERNAL_SERVER_ERROR)
}

Okay, it seems the error was caused either by existing blob in the blobstore, or by blob size - after looking at https://github.com/microsoft/avml/blob/main/src/upload/blobstore.rs for inspiration, I managed to get the streaming upload working.

source: gharchive/issue

repo: Azure/azure-sdk-for-rust


text:
[BreakingChangeTool] Fails to report breaking change due to runtime exception

This is the runtime exception reported in the spec PR.

Rule
Message

❌ Runtime Exception
"new":"https://github.com/Azure/azure-rest-api-specs/blob/1628d55466662ec03975068d8ec9a7ea760b0474/specification/vmware/resource-manager/Microsoft.AVS/stable/2023-09-01/vmware.json","old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/vmware/resource-manager/Microsoft.AVS/stable/2023-03-01/vmware.json","details":"incompatible properties : tags "

Rule
Message

❌ Runtime Exception
"new":"https://github.com/Azure/azure-rest-api-specs/blob/1628d55466662ec03975068d8ec9a7ea760b0474/specification/vmware/resource-manager/Microsoft.AVS/stable/2023-09-01/vmware.json","old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/vmware/resource-manager/Microsoft.AVS/preview/2021-01-01-preview/vmware.json","details":"incompatible properties : tags "

@konrad-jamrozik , can you have a look if this is a known issue? We would like to understand the real breaking change for this GA version.

Related:

https://github.com/Azure/azure-sdk-tools/issues/5981

@raych1 this is an old PR so the error message doesn't provide exact offending line. The actual problem is likely similar to the one discussed here. That is: The breaking change tool internally uses AutoRest v2 and AutoRest v2 is unable to parse the OpenAPI spec, thus the tool cannot run and throws runtime exception. The "incompatible properties: tags" error means, on a high level, that OpenAPI spec tries to reconcile two separate definitions of tags and they are incompatible with each other.
I would recommend reproducing this problem with a newer PR to get a better error message. And also see the discussion above.

@konrad-jamrozik , can we run this tool locally to compare the 2023-09-01 version with previous stable version? The reason is that the 2023-09-01 version is in main and any change to the spec won't trigger the expected comparison. See this PR I created for testing.

@konrad-jamrozik , can we run this tool locally to compare the 2023-09-01 version with previous stable version? The reason is that the 2023-09-01 version is in main and any change to the spec won't trigger the expected comparison. See this PR I created for testing.

I can run the tool locally and output the diffs comparing to previous version.

@raych1 instructions here:

https://github.com/Azure/openapi-diff/blob/main/CONTRIBUTING.md#reproduce-specs-pr-ci-failure-of-swagger-breakingchange-or-breakingchangecross-version

@mikeharder is investigating related, other issues of form incompatible properties.

repo: Azure/azure-sdk-tools


text:
Fix Github to GitHub

Our Docs.Ms is using Github instead of the right name GitHub. Fixed the naming in PR.

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

authors: azure-sdk sima-zhu


text:
Update NotificationConfiguration NuGet package version to 1.0.0-dev.20230216.1 to enable CODEOWNERS regex matcher everywhere

This PR is a follow-up to:

#5487
#5452

As in subject; the following PR gets deployed with this change:

https://github.com/Azure/azure-sdk-tools/pull/5487

As a result, all build failure notification recipients will be determined based on the new regex-based, wildcard-supporting CODEOWNERS matcher, as opposed to the obsolete prefix-based one.
As a result, after this PR is merged, the next run of the pipeline automation - build-failure-notification-subscriptions will change the build failure notification recipients.
Related work:

#2770

/check-enforcer override


text:
Board Review: Introducing Spring Cloud Azure 4.0

Thank you for starting the process for approval of the client library for your Azure service.  Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.
Please reference our review process guidelines to understand what is being asked for in the issue template.
Before submitting, ensure you adjust the title of the issue appropriately.
Note that the required material must be included before a meeting can be scheduled.
Contacts and Timeline

Main contacts:

Strong Liu (@stliu, Spring Cloud Azure team lead)
Sean Li (@seanli1988, Spring Cloud Azure PM)
Xiaolu Dai (@saragluna)

Expected GA date for this library:

mid-March, 2022

About the Service
Spring is the most popular application development framework for enterprise Java. There are many Spring projects in the Spring ecosystem to take care of the different needs in application development. The Spring Cloud Azure team is working on the integration between Azure and Spring. We provide Azure support for different Spring projects, such as Spring Boot, Spring Data, Spring Integration, Spring Security, and Spring Cloud Stream.

Link to documentation introducing/describing the service:

https://spring.io/
https://docs.microsoft.com/en-us/azure/developer/java/spring-framework/

Link to the service REST APIs:
N/A
Is the goal to release a Public Preview, Private Preview, or GA?
The Spring Cloud Azure libraries exist for years, and this time we are going to GA a major version, the Spring Cloud Azure 4.0, which is a refactored new version.

About the client library

Name of client library:
Spring Cloud Azure is our project name. And we will ship ~40 artifacts this time:

spring-cloud-azure-core
spring-cloud-azure-service
spring-cloud-azure-resourcemanger
spring-cloud-azure-trace-sleuth
spring-messaging-azure
spring-messaging-azure-eventhubs
spring-messaging-azure-servicebus
spring-messaging-azure-storage-queue
spring-integration-azure-core
spring-integration-azure-eventhubs
spring-integration-azure-servicebus
spring-integration-azure-storage-queue
spring-cloud-azure-stream-binder-eventhubs
spring-cloud-azure-stream-binder-eventhubs-core
spring-cloud-azure-stream-binder-serviceubs
spring-cloud-azure-stream-binder-serviceubs-core
spring-cloud-azure-autoconfigure
spring-cloud-azure-actuator
spring-cloud-azure-actuator-autoconfigure
spring-cloud-azure-starter
spring-cloud-azure-starter-activedirectory
spring-cloud-azure-starter-activedirectory-b2c
spring-cloud-azure-starter-actuator
spring-cloud-azure-starter-appconfiguration
spring-cloud-azure-starter-cosmos
spring-cloud-azure-starter-data-cosmos
spring-cloud-azure-starter-eventhubs
spring-cloud-azure-starter-keyvault-secrets
spring-cloud-azure-starter-servicebus
spring-cloud-azure-starter-servicebus-jms
spring-cloud-azure-starter-storage-blob
spring-cloud-azure-starter-storage-file-share
spring-cloud-azure-starter-storage-queue
spring-cloud-azure-starter-integration-eventhubs
spring-cloud-azure-starter-integration-servicebus
spring-cloud-azure-starter-integration-storage-queue
spring-cloud-azure-starter-stream-eventhubs
spring-cloud-azure-starter-stream-servicebus

Link to library reference documentation:
https://microsoft.github.io/spring-cloud-azure/4.0.0-beta.3/4.0.0-beta.3/reference/html/index.html
Is there an existing SDK library? If yes, provide link:
Yes, we have shipped these libraries before, but the artifact names are changed in this version.
https://repo1.maven.org/maven2/com/azure/spring/

Step 1: Champion Scenarios
Ultimately the library should be easy to use for common scenarios that developers want. Consider the following questions when thinking about champion scenarios:

What is the app the developer is building that uses your client library?
Typically a Spring or Spring Boot application.
Who is the end-user of the application (the developer's customer)?
The developer's customer.
What features of the API need to be explained in the sample so that someone could use this API in real app?
Will explain in the champion scenarios.
How does the authentication workflow look?
Build on top of azure sdks and azure-identity.

See Champion Scenario section here.
Code is appreciated but optional. Pseudocode is fine.

Use the auto-configuration provided by Spring Boot: https://gist.github.com/saragluna/7e1754a7d17d0820f223ddba8621e2c7.
Use Resource Handling abstractions provided by Spring Framework: https://gist.github.com/backwind1233/0f5a5e11ed9856db141f4cdc1c285971.
Use Enterprise Integration Patterns (EIP) supported by Spring Integration: https://gist.github.com/yiliuTo/352b071a717fd90c984bcf03ec5d0fb9.

Step 2: Quickstart Samples (Optional)
Include samples demonstrating how to consume the client library if available:
We have a sample repo hosting all our sample projects: https://github.com/Azure-Samples/azure-spring-boot-samples/tree/spring-cloud-azure_4.0.0-beta.3
Thank you for your submission!

scheduled for 1/19 4-6pm pst

Recording[MS INTERNAL ONLY]

authors: lilyjma saragluna tg-msft

repo: Azure/azure-sdk


text:
Harden host ID generation to allow characters that are valid in function app name

From @mathewc in issue: https://github.com/projectkudu/AzureFunctionsPortal/issues/883

The Function runtime imposes some restrictions on the format for HostId, and HostId is derived from the Function App name by default. E.g. runtime restrictions on HostId are here.

This can result in issues where someone can successfully create a Function App in the portal, but it fails at runtime - we've had cases of this.

Ideally we'd find a way to prevent names we know are going to fail. This is somewhat complicated by the fact that we have logic that derives the HostId from the Function App name here.

The right fix is to change the script host to handle these characters. Otherwise, we need to do the following:

Change the Web Apps RP to disallow these function app names at the API layer
Update Ibiza and FunkyUX to validate
Update Visual Studio

Many of the character restrictions on HostID are due to the fact that host ID is used in the names of several different storage artifacts (e.g. blob names, queue names, etc.). We can't break any of that - lots of downstream assumptions are made on the current longstanding restrictions.

@mathewc Is there a way to escape these illegal characters?  If not, we have to start a fairly big chunk of work to disallow them.

@lindydonna  can you provide some examples of Function-App name? Was there any customer pushback?

Won't fix for now

authors: fabiocav lindydonna mathewc

repo: Azure/azure-webjobs-sdk-script


text:
Docker container cannot start due to permission errors?

We're trying to use the Azure driver to externalize our volumes for Docker in order to run MongoDB. I've setup the azurefile-dockervolumedriver and created two volumes. This created the shares in our Azure Storage account.
However when I try to run a MongoDB container it shuts down again immediately with the following errors for which I have no idea on how to solve it as I followed all procedures:
kernel: aufs au_opts_verify:1597:dockerd[1594]: dirperm1 breaks the protection by the permission bits on the lower branch
kernel: aufs au_opts_verify:1597:dockerd[3695]: dirperm1 breaks the protection by the permission bits on the lower branch
systemd-udevd[37637]: Could not generate persistent MAC address for vethf345bd2: No such file or directory
kernel: device veth97a0c1e entered promiscuous mode
kernel: IPv6: ADDRCONF(NETDEV_UP): veth97a0c1e: link is not ready
systemd-udevd[37638]: Could not generate persistent MAC address for veth97a0c1e: No such file or directory
kernel: eth0: renamed from vethf345bd2
kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth97a0c1e: link becomes ready
kernel: docker0: port 1(veth97a0c1e) entered forwarding state
kernel: docker0: port 1(veth97a0c1e) entered forwarding state
kernel: docker0: port 1(veth97a0c1e) entered disabled state
kernel: vethf345bd2: renamed from eth0
kernel: docker0: port 1(veth97a0c1e) entered disabled state
kernel: device veth97a0c1e left promiscuous mode
kernel: docker0: port 1(veth97a0c1e) entered disabled state

Any suggestions would be greatly appreciated.

@ropstah have you tried using it with a regular volume? Where are the kernel: logs coming from, where do you see these logs?

@ropstah please consider closing if you are no longer seeking an answer.

@ahmetalpbalkan you are right. I found the problem is not related to the driver but to MongoDb in conjunction with Docker.

authors: ahmetalpbalkan ropstah

repo: Azure/azurefile-dockervolumedriver

license_source: bigquery


text:
added wvd-backplane example

added wvd-backplane example

Codecov Report

Merging #1009 (009bea6) into main (018b398) will increase coverage by 0.47%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1009      +/-   ##
==========================================
+ Coverage   94.25%   94.73%   +0.47%
==========================================
  Files         328      324       -4
  Lines       15809    15658     -151
  Branches       12        0      -12
==========================================
- Hits        14901    14833      -68
+ Misses        908      825      -83

Flag
Coverage Δ

dotnet
94.73% <ø> (-0.09%)
:arrow_down:

typescript
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...cep.Core.UnitTests/FileSystem/FileResolverTests.cs
79.31% <0.00%> (-20.69%)
:arrow_down:

.../Bicep.Core.UnitTests/Assertions/BaselineHelper.cs
63.63% <0.00%> (-15.91%)
:arrow_down:

src/Bicep.Core/FileSystem/PathHelper.cs
96.15% <0.00%> (-3.85%)
:arrow_down:

src/Bicep.Core.UnitTests/Utils/CompilerFlags.cs
33.33% <0.00%> (ø)

...Bicep.Core.UnitTests/FileSystem/PathHelperTests.cs
100.00% <0.00%> (ø)

src/vscode-bicep/src/utils/logger.ts

src/vscode-bicep/src/language/client.ts

src/vscode-bicep/src/extension.ts

src/vscode-bicep/src/utils/telemetry.ts

authors: codecov-io fberson

repo: Azure/bicep


text:
Revert "Bump MSTest.TestAdapter from 2.1.2 to 2.2.1"

Reverts Azure/bicep#1673. The original PR was accidentally merged due to auto merge being enabled. The library has an issue with data-driven tests in VS. The MSTest team is working on rolling out the fix (link in the reverted PR).

Codecov Report

Merging #1831 (280a633) into main (25bb943) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1831      +/-   ##
==========================================
- Coverage   95.50%   95.44%   -0.07%
==========================================
  Files         367      367
  Lines       21739    21716      -23
==========================================
- Hits        20762    20726      -36
- Misses        977      990      +13

Flag
Coverage Δ

dotnet
95.44% <ø> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

.../Bicep.Core.UnitTests/Assertions/BaselineHelper.cs
63.63% <0.00%> (-15.91%)
:arrow_down:

...cep.Core.UnitTests/FileSystem/FileResolverTests.cs
88.23% <0.00%> (-8.83%)
:arrow_down:

src/Bicep.Core/FileSystem/PathHelper.cs
96.15% <0.00%> (-3.85%)
:arrow_down:

src/Bicep.Core.UnitTests/Utils/OutputHelper.cs
96.55% <0.00%> (-3.45%)
:arrow_down:

src/Bicep.Core.UnitTests/Utils/CompilerFlags.cs
33.33% <0.00%> (ø)

...Bicep.Core.UnitTests/FileSystem/PathHelperTests.cs
100.00% <0.00%> (ø)

authors: codecov-io majastrz


text:
Use --password-stdin

For users using their own jumpbox, on the HOL #2 step:
docker login --username $ACR_USER --password $ACR_PWD $ACR_SERVER

... they may receive the following message:
WARNING! Using --password via the CLI is insecure. Use --password-stdin.

The solution is to use vi to write the password to a txt file (e.g. ~/acr-pw.txt) and then use this alternative login command:
 cat ~/acr-pw.txt | docker login $ACR_SERVER -u $ACR_USER --password-stdin

Is this deserving of a PR? Perhaps it's a bit out of scope.

This is probably out of scope and might only lead to confusion. Some things are good to leave in there and lead to questions and discussion.

repo: Azure/blackbelt-aks-hackfest


text:
Multiple-create: Authorization

Why make this change?
Since GraphQL insertions now support nested insertions, we need to authorize entity and fields not only for the top-level entity in the insertion, but also the nested entities and fields. This PR aims to address that logic of collecting all the unique entities and fields belonging to those entities in a data structure, and then sequentially iterate over all entities and fields to check whether the given role is authorized to perform the action (here nested insertion).
What is this change?

The presence of the model directive on the output type of the mutation object will be used to determine whether we are dealing with a point mutation or a nested insertion. Presence of model directive indicates we are doing a point insertion while its absence indicates the opposite. This logic is added to SqlMutationEngine.ExecuteAsync() method. This logic determines whether the input argument name is item (for point mutation) or items (for insert many).
A new method SqlMutationEngine.AuthorizeEntityAndFieldsForMutation() is added. The name is kept generic (instead of using 'Insertion') because the same method can be used later for nested updates as well. As the name indicates, this method iterates over all the entities and fields and does the required authorization checks.
The method mentioned in the point above depends on another newly added method SqlMutationEngine.PopulateMutationFieldsToAuthorize() whose job is to populate all the unique entities referred in the mutation and their corresponding fields into a data structure of the format:
Dictionary<string, HashSet<string>> entityAndFieldsToAuthorize - where for each entry in the dictionary:
-> Key represents the entity name
-> Value represents the unique set of fields referenced from the entity
The method SqlMutationEngine.PopulateMutationFieldsToAuthorize() recursively calls itself for nested entities based on different criteria explained in code comments.
When the field in a nested mutation is a list of ObjectFieldNode (fieldName: fieldValue) or the field has an object value, the fields are added to the data structure mentioned in (3) using a newly added method: SqlMutationEngine.ProcessObjectFieldNodesForAuthZ() which sequentially goes over all the fields and add it to the list of fields to be authorized. Since a field might represent a relationship- and hence a nested entity, this method again calls its parent caller i.e. SqlMutationEngine.PopulateMutationFieldsToAuthorize().
The method SqlMutationEngine.ProcessObjectFieldNodesForAuthZ() contains the logic to ensure that the fields belonging to linking tables are not added to the list of fields to be authorized.
Moved the method GetRoleOfGraphQLRequest() from Cosmos/SqlMutationEngine to AuthorizationResolver.

How was this tested?
To be added.
Sample Request(s)

Config:

Request/Response - AuthZ failure because piecesAvailable field is not accessible to test_role_with_excluded_fields_on_create role.

Request/Response: Removing piecesAvailable field from request body leads to successful authz checks (request fails during query generation).

Can you elaborate on the expected behavior of what happens when authorization requirements are met for some, but not all of the input? e.g. A single component of the input failing authorization fails the entire request?
in your example in PR description of inserting multiple review objects: reviews [ {title: "mytitle"}, {body: "reviewBody" ]  if "body" column is permitted, but "title" is not, then the whole request fails?

Can you elaborate on the expected behavior of what happens when authorization requirements are met for some, but not all of the input? e.g. A single component of the input failing authorization fails the entire request?
in your example in PR description of inserting multiple review objects: reviews [ {title: "mytitle"}, {body: "reviewBody" ]  if "body" column is permitted, but "title" is not, then the whole request fails?

Whether the role lacks the permission for create operation on any entity or any field belonging to any entity referenced in the mutation, AuthZ check will fail.
So, to your question, the answer is yes, the whole request will fail.

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

The PR description example doesn't touch on authorization of "multiple mutations." Yes, there is a relationship field in the mutation, but your example doesn't demonstrate authorization of fields/entities defined by that relationship field.

/azp run

repo: Azure/data-api-builder


text:
Unable to refresh token with Web app

With a App registration with the type Web app I get the following error message from the API when attempting a 2nd refresh of a token:
adal: Refresh request failed. Status Code = '401'. Response body: {"error":"invalid_client","error_description":"AADSTS70002: The request body must contain the following parameter: 'client_secret or client_assertion'

Step to reproduce:
spt, err := adal.NewServicePrincipalTokenFromAuthorizationCode(
	*oauthConfig,
	applicationID,
	clientSecret,
	authorizationCode,
	redirectURI,
	resource,
	callback,
)

if err != nil {
	fmt.Println(err)
	os.Exit(1)
}

// The refresh is required, call above just creates the struct
err = spt.Refresh()
if err != nil {
	fmt.Println(err)
	os.Exit(1)
}

// This call errors
err = spt.Refresh()
if err != nil {
	fmt.Println(err)
	os.Exit(1)
}

It appears the issue is coming from here.
Is this me using the client incorrectly?

Thanks for reporting this issue, this is a bug in our refresh logic.  I hope to have a fix soon.

This is fixed in go-autorest 10.9.2.  Thanks for the bug report!  https://github.com/Azure/go-autorest/releases/tag/v10.9.2

authors: dramich jhendrixMSFT

repo: Azure/go-autorest


text:
Adding forward DLQ to management option

adding ability to set a custom queue for DLQ forwarding

LGTM
the integration test failure is ACI related when using MSI.
the other auth mechanism worked fine, so I'd say merge it

repo: Azure/go-shuttle


text:
weird authorization error when authenticating via service principal

I was following this guide to authenticate against my cluster via service principal. So what I did was:

Firstly register an app in EntraID
Grant the app some permissions via RBAC

kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: ado-svc-role
rules:
  - apiGroups: [""]
    resources: ["pods", "services", "deployments"]
    verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: ado-svc-role-binding
subjects:
  - apiGroup: rbac.authorization.k8s.io
    kind: User
    name: <app_object_id>
roleRef:
  kind: ClusterRole
  name: ado-svc-role
  apiGroup: rbac.authorization.k8s.io

Auth and verification

export AAD_SERVICE_PRINCIPAL_CLIENT_ID=<app-client-id>
export AAD_SERVICE_PRINCIPAL_CLIENT_SECRET=<app-secret-id>

az login --service-principal -u <app-client-id> -p <app-client-secret> --tenant <tenant-id>

az aks get-credentials --subscription <subscription-id> --resource-group <resource-group-name> --name <cluster-name> --file ./custom-kubeconfig

export KUBECONFIG=$(pwd)/custom-kubeconfig

kubelogin --kubeconfig "${KUBECONFIG}" convert-kubeconfig -l spn --client-id ${AAD_SERVICE_PRINCIPAL_CLIENT_ID} --client-secret ${AAD_SERVICE_PRINCIPAL_CLIENT_SECRET} \
    --tenant-id <tenant-id>

kubectl get nodes

Expected Result
Command returns nodes information.
Actual Result
kubectl get nodes command returns error below:
Error from server (Forbidden): nodes is forbidden: User "xxxx" cannot list resource "nodes" in API group "" at the cluster scope

Comments
The user xxxx cannot be linked to the app I've used to login in any way - the uuid of the user (masked by xxxx) is unknown to me.

the uuid of the user, masked by xxx, is the object ID of the service principal.
you can verify that by az ad sp show --id xxxx

@weinong Thanks for getting back. That command returns a different object id than that of my app on EntraID. Any idea why?
However, it still throws the same error even after I set the name of subject  to the one returned from cli. Not sure if I've done anything wrong?

first of all, your cluster role doesn't have permission to list nodes. this is the reason you got Forbidden.
in your cluster role binding, <app_object_id> should match the object ID on the portal.

@weinong sorry a copy & paste mistake - I'd have used kubectl get pods -n main --kubeconfig ${KUBECONFIG}. However, this command gives me the exact same auth error.
I can also confirm the role points to the object_id of my service principal even though it's different than the one shown in the error message.

Close it as I've mistaken application object id for service principal object id. They are fundamentally different.

repo: Azure/kubelogin


text:
Opt-in for AllMetrics diagnostic settings

Benefit/Result/Outcome
The Diagnostics Setting for AllMetrics is verbose, costly, and not always necessary for SCCA compliance. Instead of being turned on by default, we can make this an opt-in decision.
Description
The Diagnostic Settings resources are currently created for the firewall, the firewall Public IP addresses, and all network security groups. Update these diagnostic settings resources with metrics collections that by default do not configure the AllMetrics category, but given a boolean parameter, include that AllMetrics category.
Acceptance Criteria

The AllMetrics diagnostic setting is not enabled by default on the firewall, public IP addresses, and network security groups.
The firewall, public IP, and network security groups have separate boolean parameters that default to false which can be overridden to enable AllMetrics on any of the resource types listed above, i.e., three boolean parameters that control their respective AllMetrics settings.
The parameters are available in Bicep and Terraform.
The parameters are visible in the portal form.

@glennmusa apologies for asking this after triage happened on this item.
I updated the acceptance criteria to add more detail. I want to verify that there is currently no diagnostic setting applied to NSGs (unless it's the default) and we want to add one. The description says NSGs currently have AllMetrics applied to them but I don't find it in the code.
Questions:

Do you think the default should be true instead of false for AllMetrics because that's our current setting, and changing it would change the behavior of MLZ, which could be unexpected for some people?
As part of this backlog item are we adding a setting for NSGs? (I added it to the acceptance criteria but I want to confirm.)

authors: brooke-hamilton glennmusa

repo: Azure/missionlz


text:
add e2e test for pod-identity mode

What this PR does / why we need it:

Adds e2e tests for pod-identity mode

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #
Special notes for your reviewer:

/azp run pr-e2e-azure


text:
chore: repository governance

Repository governance update
This PR was automatically created by the AVM Team hive-mind using the grept governance tool.
We have detected that some files need updating to meet the AVM governance standards.
Please review and merge with alacrity.
Grept config source: git::https://github.com/Azure/Azure-Verified-Modules-Grept.git//terraform
Thanks! The AVM team :heart:

Supersceeded by #30


text:
chore: repository governance

Repository governance update
This PR was automatically created by the AVM Team hive-mind using the grept governance tool.
We have detected that some files need updating to meet the AVM governance standards.
Please review and merge with alacrity.
Grept config source: git::https://github.com/Azure/Azure-Verified-Modules-Grept.git//terraform
Thanks! The AVM team :heart:

Supersceeded by #48

authors: lonegunmanb segraef


text:
Wiki sync - update on release publish

Update wiki sync on release publish, not push to main.
Means we can update wiki source asyns whilst preparing for a release, without changing active documentation
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows?ref=hackernoon.com#release

/azp run unit

authors: krowlandson matt-FFFFFF


text:
Add configuration for recovery_services_vault

Resource rules: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules
Slug: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations

Closing this as I just noticed it is already included

repo: Azure/terraform-azurerm-naming


text:
Adding ingress support

Hi I just tested ingress support - worked locally. Sorry for the whitespace changes - VSCode forced me to clean things up

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

@arehmandev Thanks for the contribution!  It will go out in the next release.

authors: arehmandev itowlson msftclas

repo: Azure/vscode-kubernetes-tools


text:
[Bug] byte[] values in JwtPayload et al. are serialized as arrays instead of base64.

Which version of Microsoft.IdentityModel are you using?
Microsoft.IdentityModel 7.x.x
Where is the issue?

[ ] M.IM.JsonWebTokens
[ ] M.IM.KeyVaultExtensions
[ ] M.IM.Logging
[ ] M.IM.ManagedKeyVaultSecurityKey
[ ] M.IM.Protocols
[ ] M.IM.Protocols.OpenIdConnect
[ ] M.IM.Protocols.SignedHttpRequest
[ ] M.IM.Protocols.WsFederation
[ ] M.IM.TestExtensions
[x] M.IM.Tokens
[ ] M.IM.Tokens.Saml
[ ] M.IM.Validators
[ ] M.IM.Xml
[ ] S.IM.Tokens.Jwt
Other (please describe)

Is this a new or an existing app?
The app is in production and I have upgraded to a new version of Microsoft.IdentityModel.*
Repro
Console.WriteLine(new JwtPayload { { "Fail", new byte[] { 0x21, 0x62, 0x36, 0x34 } } }.SerializeToJson());
//6.x.x - {"Fail":"IWI2NA=="}
//7.x.x - {"Fail":["33","98","54","52"]}

Expected behavior
byte[] arrays are serialized as base64.
Actual behavior
byte[] arrays are serialized as arrays.
Possible solution

Additional context / logs / screenshots / links to code
Prior to 7.0.0, byte[] arrays were serialized as base64. This is both the default behavior of System.Text.Json and Json.NET. However since 7.0.0 this changed to serialize them as arrays. If this was intentional, it is an undocumented breaking change affecting backwards compatibility and interoperability with other systems expecting the older format!

@brentschmaltz , can you take a look please?

@LeadAssimilator @keegan-caruso I will have a look.


text:
Recent JWE implementation flaw findings

Have you guys seen that:
http://blog.intothesymmetry.com/2017/03/critical-vulnerability-in-json-web.html

@leastprivilege yes I have seen that.

@leastprivilege we do plan on supporting KeyExchange, when we do we will do the right thing.

authors: brentschmaltz leastprivilege


text:
new release or patched pypi release

As pint-0.18 broke weldx-0.5.0 we have to decide what to do about the borken pypi 0.5.0 release. On conda-forge we just released an updated build of 0.5.0, but this aint possible for PyPI. We have to choose between the following choices:

quick release 0.5.1
upload a patched source archive with a different format and delete the old one

I think the first option is cleaner. I have performed option 2. in the past and it works. I just do not like that the tagged version from git does not match the source archive in this case. But that may be a neglect able detail.

we are basically ready for 0.5.1 pending #621 and #622, my plan was to release in the next days

I see, there were no issues assigned to the 0.5.1 milestone. I think we could postpone these PRs for 0.5.2 as they add new features, right? The pypi issue is a blocker. Nothing relying on units does work (which is essentially everything).

I see, there were no issues assigned to the 0.5.1 milestone. I think we could postpone these PRs for 0.5.2 as they add new features, right? The pypi issue is a blocker. Nothing relying on units does work (which is essentially everything).

it works with the master or pint 0.17

authors: CagtayFabry marscher

repo: BAMWelDX/weldx


text:
Feature multi reset

Sequence to prepare and reset an arbitrary number of qubits
--DR

@dieris it looks like this should also work for a single qubit so should we just call it Reset?

authors: CoherenceController caryan

repo: BBN-Q/PyQLab


text:
Docker permission issue with WSL, and proposed Docker changes

So... while working on an unrelated project I realize the Docker permission issue that has been haunting me since the start of this project is caused by building the Docker image in WSL then running the container in WSL. Building the Docker image in Windows then run the container, and it works perfectly in both WSL and native Windows (I don't fucking understand why)
This leads me to rethink how we are currently handling our Docker containers. We are using a custom-built image for Orthanc since we have to add libpqxx to the image, which the official Orthanc image lacks. However, how we are currently achieving this is I'm first building the image on my machine, then pushing the image to my personal Docker repository, then referencing the repository in docker-compose.
Moving forward, I propose that instead of referencing a pre-built image in docker-compose, we instead build our own image locally. This is an easy change and should resolve and mitigate those weird platform-related bugs. The only downside will be having to wait for the image to build (you only need to do it once), which might take a while.
Thoughts?

This has been done

repo: BCCF-UBCO-AD/Orthanc-TMI


text:
BA-977 - Bootstrap4 styling - Update users module (authentication) views

styling(users module - authentication)

Deleted views from this module that were not in use
minor adjustments to padding and columns
Moved calls-to-action around Sign Up to a separate section on homepage to make actual Sign In view simpler; minor styling (colors, padding) on homepage section while I was at this

Fixes #BA-977

Wait, don't merge this yet! I just retested this branch and noticed that clicking on the Sign In link from the navbar is causing a page not found. Will investigate.

repo: BCDevExchange/devex


text:
Fix async writing of files to jobstore in caching (resolves #966)

resolves #966
asyncWrite is now a class method and CachedFileStore overloads it with a cache-friendly version

Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.

Pending verification by author of #966.

I would like this rebased, too much has happened on master in the past two days.

OK check out build 1492.
FileJobStore fails with the expected error.
AwsJobStore is slightly different. It is failing at line 1005 in aws/jobStore.py mostly because self.content is None. This is because job C in jobCacheTest has asked for the file before the async write process in B could finish writing to the job store (possibly hasn't even started). This will all be addressed in the next commit

Build 1493 shows that the tests pass in both AWS and File job stores.
@adderan this should fix your issue. It looks a little complicated setting up cactus so it would be great if you could test this on your cactus script.

@hannes-ucsc Alden has  confirmed this works on Cactus! This is ready for review

Build failure tracked in #760.

Ran out of domains/buckets again.

Jenkins, test this please.

This is already pretty good. My main concern is that we can move more code into HarbingerFile.
Now that we identified a class, we should strive to hide the the habinger file logic from the rest of the program. Encapsulation!

@hannes-ucsc i implemented the suggested changes

Well done.

Thanks!

authors: arkal hannes-ucsc


text:
dwi and fmap images not on same grid

Originally listed in #19.
Currently, the script concatenates any SE-EPI data present in the fmap/ directory with the DWIs stored in the dwi/ directory, so that denoising can be applied to these images (the denoising process requires a large number of volumes; if just the contents of fmap/ were provided to dwidenoise, it would not work); it additionally means that mrdegibbs need only be executed once.
However this makes a fundamental assumption: The images in the fmap/ directory are defined on the same voxel grid as those in the dwi/ directory. If this is not the case, then mrcat will fail.
To avoid this, it is necessary to explicitly test whether or not these images lie on the same voxel grid. If they are, then processing can be performed as it is currently. If they are not, then:

The concatenation of DWI and fmap data should be skipped.
dwidenoise should be applied exclusively to the DWIs.
mrdegibbs should be applied separately to DWI and fmap images.
The mrconvert calls to separate DWI and fmap data from concatenation should be skipped.

#62 changes the pipeline to no longer perform concatenation of DWI and fmap data. Any issues with different image grids are deferred to MRtrix3's dwifslpreproc, where the input DWIs and the input to the -se_epi option don't need to be on the same voxel grid.


text:
unwatch() was undefined

# Wait for customer to be hydrated
await new Promise (resolve) ->
	unwatch = store.watch ((state) -> state.customer.hydrated)
	, ((hydrated) -> unwatch() && resolve() if hydrated)
	, immediate: true

Also, aside... I was running into more coffeescript transpiling issues. For the time being, I dropped these in a middlewares folder in the DD Pro project. That fixed for the time being, but I know that's not ideal

yikes that dumb paste, sorry, it was the auth middlewares

@weotch this is still an issue, and like you said to help figure out what's going on I'm making a demo. I'm almost done and I'll let you know when that demo is ready to run locally and I'll give you an env. But the demo was having some netlify failures which I'm still trying to figure out, see: https://app.netlify.com/teams/bukwild/builds/624db9fbdeffb900080e3603

repo: BKWLD/cloak-customer


text:
blake3 single thread is slower than sha256 on Apple silicon

On intel cpus I see ~10x speedup for the C implementation, but on Apple silicon it
is 1.3x times slower than sha256.
I built the C version both with cmake and manually (based on README.md), both show
same performance, matching b3sum performance with single threads.
cmake build:
% cmake -B build -S . -DCMAKE_BUILD_TYPE=Release
-- The C compiler identification is AppleClang 14.0.3.14030022
-- The ASM compiler identification is Clang with GNU-like command-line
-- Found assembler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
--
 * NEON SIMD intrinsics, The library uses NEON SIMD intrinsics.

-- Configuring done (0.2s)
-- Generating done (0.0s)
-- Build files have been written to: /Users/nir/src/BLAKE3/c/build

% cmake --build build
[ 20%] Building C object CMakeFiles/blake3.dir/blake3.c.o
[ 40%] Building C object CMakeFiles/blake3.dir/blake3_dispatch.c.o
[ 60%] Building C object CMakeFiles/blake3.dir/blake3_portable.c.o
[ 80%] Building C object CMakeFiles/blake3.dir/blake3_neon.c.o
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
[100%] Linking C static library libblake3.a
[100%] Built target blake3

Manual build:
% mkdir build
% gcc -shared -O3 -o build/libblake3.so -DBLAKE3_USE_NEON=1 blake3.c blake3_dispatch.c \
    blake3_portable.c blake3_neon.c

Building the example:
% cc example.c -O3 -L build -lblake3 -o build/example

Creating test file:
% dd if=/dev/zero bs=1M count=4096 of=test.data

Testing read throughput from pipe:
 % time dd bs=64K of=/dev/null status=none < test.data
dd bs=64K of=/dev/null status=none < test.data  0.02s user 0.34s system 99% cpu 0.355 total

Measuring hash throughput:
% time openssl sha256 < test.data
8479e43911dc45e89f934fe48d01297e16f51d17aa561d4d1c216b1ae0fcddca
openssl sha256 < test.data  1.71s user 0.49s system 99% cpu 2.202 total

% time build/example < test.data
7dde7c9fed144013fedbe2b0bbf2d82f004b60b589485851cdec29b27be408d7
build/example < test.data  2.58s user 0.36s system 99% cpu 2.942 total

 % time b3sum < test.data
7dde7c9fed144013fedbe2b0bbf2d82f004b60b589485851cdec29b27be408d7  -
b3sum < test.data  2.59s user 0.36s system 99% cpu 2.951 total

 % time b3sum --num-threads 1 < test.data
7dde7c9fed144013fedbe2b0bbf2d82f004b60b589485851cdec29b27be408d7  -
b3sum --num-threads 1 < test.data  2.58s user 0.36s system 99% cpu 2.935 total

Note: testing with openssl sha256 since both shasum -a 256 and sha256sum
(from coreutils) are extremely slow (~6x times slower) on macOS.
Looking in openssl code, sha256 is using sha256-armv8.S on this machine.
Tested on MacBook Pro M2 Max.

ARM NEON only provides 128-bit vector registers, compared to the 512-bit registers available on Intel CPUs that support AVX-512, and that's a big part of the difference you're seeing. There are lots of other details besides just vector size that also come into play here; see for example @sneves' comment on another recent thread.
ARM SVE and SVE2 can potentially provide larger vectors, but I'm not aware of any consumer hardware that supports those. It'll probably make sense for BLAKE3 to provide an SVE implementation at some point.

Apple Silicon also happens to have fast SHA-256 dedicated instructions. This is why openssl sha256 is much faster, since it uses them instead of a pure software implementation.

Updating results, we now only 12-13% difference.
Tested with:

OpenSSL 3.2.1 30 Jan 2024 (Library: OpenSSL 3.2.1 30 Jan 2024)

b3sum 1.5.0 (from brew)

3 versions from git commit 8fc36186b84385d36d8339606e4d1ea6ff471965

example-brew - linked with blake3 1.5.0 from brew
gcc -O3 -o example-brew c/example.c $(pkg-config --libs libblake3)

example-neon - built from source with neon support
gcc -O3 -o example-neon -DBLAKE3_USE_NEON=1 c/example.c c/blake3.c c/blake3_dispatch.c c/blake3_portable.c c/blake3_neon.c

example-portable - built from source without neon support
gcc -O3 -o example-portable -DBLAKE3_USE_NEON=0 c/example.c c/blake3.c c/blake3_dispatch.c c/blake3_portable.c

% hyperfine -w 2 "openssl sha256 < /var/tmp/1g.img" \
                 "b3sum < /var/tmp/1g.img" \
                 "./example-brew < /var/tmp/1g.img" \
                 "./example-neon < /var/tmp/1g.img" \
                 "./example-portable < /var/tmp/1g.img"
Benchmark 1: openssl sha256 < /var/tmp/1g.img
  Time (mean ± σ):     553.2 ms ±   1.2 ms    [User: 428.8 ms, System: 112.5 ms]
  Range (min … max):   550.5 ms … 555.4 ms    10 runs

Benchmark 2: b3sum < /var/tmp/1g.img
  Time (mean ± σ):     621.3 ms ±   1.2 ms    [User: 536.2 ms, System: 72.9 ms]
  Range (min … max):   619.1 ms … 622.9 ms    10 runs

Benchmark 3: ./example-brew < /var/tmp/1g.img
  Time (mean ± σ):     626.7 ms ±   1.1 ms    [User: 542.9 ms, System: 71.1 ms]
  Range (min … max):   624.8 ms … 628.0 ms    10 runs

Benchmark 4: ./example-neon < /var/tmp/1g.img
  Time (mean ± σ):     619.1 ms ±   1.2 ms    [User: 534.1 ms, System: 70.8 ms]
  Range (min … max):   617.5 ms … 622.1 ms    10 runs

Benchmark 5: ./example-portable < /var/tmp/1g.img
  Time (mean ± σ):      1.315 s ±  0.004 s    [User: 1.204 s, System: 0.084 s]
  Range (min … max):    1.308 s …  1.322 s    10 runs

Summary
  'openssl sha256 < /var/tmp/1g.img' ran
    1.12 ± 0.00 times faster than './example-neon < /var/tmp/1g.img'
    1.12 ± 0.00 times faster than 'b3sum < /var/tmp/1g.img'
    1.13 ± 0.00 times faster than './example-brew < /var/tmp/1g.img'
    2.38 ± 0.01 times faster than './example-portable < /var/tmp/1g.img'

authors: nirs oconnor663 sneves


text:
Remove python -m pip install pillow tifffile from CI

This was added back in https://github.com/BMCV/galaxy-image-analysis/pull/126
but should be obsolete after https://github.com/galaxyproject/planemo/pull/1471

@bernt-matthias Is there anything else to be done so that the most recent planemo is used?

The planemo-ci-action automatically takes the last release, but we would need a new release first. Ping @mvdbeek

You're a maintainer @bernt-matthias, you can create releases: https://planemo.readthedocs.io/en/latest/developing.html

authors: bernt-matthias kostrykin mvdbeek

repo: BMCV/galaxy-image-analysis

license: mit


text:
Url.isEmptyQuery true/false tesztje

Írtam gyorsan egy tesztet az Url.isEmptyQuery-re, hogy true/false esetén helyeset ad-e viszza. Kapcsolódik a #9 issuehoz

Szerintem minden rendben van, még egy valaki ránézhet azért.

Jó lesz

authors: CHMarcell hellcsaba t-botond


text:
Params and users

Hello! This API that you've made is great. The code is awesome. I'm not sure if these changes will be useful for you or others, but figured I'd let you take a look. Also, I'm not sure I've followed your style sufficiently, apologies for the hacks.
In general - I was wanting a couple things: first, to be able to add tickets from our CRM, and add a user if needed. So with these mods, we can first check if the user existed in OST, and if they didn't, add them automatically.
Second, the tickets from this API were not using the 'status' field in some views, and the title was displaying differently from manually created tickets. I added some insert queries to add form table data, where it seems those are stored? The result looks more 'complete' in my environment when reviewing tickets.
Finally, we wanted a way to add internal notes when a ticket is created from our CRM. It's a useful way to get agents up to speed, without having that info viewable. So, I added this via some new "optionalParameters" hacking...
Most other things were minor. Apologies for the 'spacing' changes, it seems my VIM does that automatically...
Thanks again for this project and all the best!

Hey,
Im glad it helped you to achieve what you wanted.
I will take a look, thank you!

authors: BMSVieira halcyonyarn

repo: BMSVieira/osticket-api


text:
🛑 Laman Umum BSrE is down

In 97316af, Laman Umum BSrE (https://bsre.bssn.go.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Laman Umum BSrE is back up in a5337ea after 38 minutes.

repo: BSrE-ID/monitor


text:
Verification

As the co-founder of the Mempool Open Source project at https://github.com/mempool/mempool I am excited to return to Nashville and hangout with some Bitcoiners.

This is Mike aka LifeSizeBox from Vegas Crypto Group and InformEmpower.com - trusting but verifying! Thank you!

authors: lifesizebox softsimon


text:
Feature: Upgrade to NUnit 2.6.3

Upgrade to NUnit 2.6.3
This work item was migrated from CodePlex
CodePlex work item ID: '10517'
Assigned to: 'tfabraham'
Vote count: '1'

[UnknownUser@2/10/2014]
Resolved with changeset 74543: Update to NUnit 2.6.3 (#10517)

repo: BTDF/DeploymentFramework


text:
Deployement Project Template not referenced

Hello,
I have just built and installed BTDF on my environment in version 6.0. I have Visual Studio 2013 Update 3 and BizTalk Server 2013 R2 installed.
The build and installation works fine, but when I try to create a new BTDF project, the template is not referenced. The tools are well referenced.
The DeploymentFrameworkForBizTalkProjectTemplate5_0.zip is copied in the C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\ProjectTemplates directory.
The assembly DFBTVisualStudioAddIn.ProjectWizard, Version=5.5.100.0, Culture=neutral, PublicKeyToken=e748234cd372cc72 is in the .Net 4 GAC.
Have you ever encountered this issue ?
Thanks in advance for your help.
This work item was migrated from CodePlex
CodePlex work item ID: '10712'
Vote count: '1'

[tfabraham@8/27/2014]
Try
"Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv" /InstallVSTemplates

[UnknownUser@8/27/2014]

Issue closed by tfabraham with comment
Fixed in latest V6.0 source branch
Reason closed
Fixed


text:
Fail task when agents are abused

Describe the new feature you'd like
Currently, tasks will not go terminal if agents have crashed or been damaged, ie if the rotors of the UAV hit something, it has flipped upside down, etc.
We should make it so the agent will fail a task if it has excessive forces applied to it, like if the android falls of a cliff or something.

We cannot have a robot uprising on our hands

After talking to the oracle @jaydenmilne it seems that it would be better if we added an abuse sensor that simply returns a true or false if the agent has been abused, and the value changes based on which agent it's attached to. The user can then handle how to interpret abuse (negative rewards, terminal, etc.) so we won't mess with the task values.
It might be useful if the sensor returned more complex info, like how hard it was hit or if it flipped over or something like that, but I think a simple abuse sensor is a start.

✅ in changelog

authors: MaxRobinsonTheGreat jaydenmilne

repo: BYU-PCCL/holodeck


text:
Fix issue(s) with bone map

Using the bones array is not enough - some bones have a negative index and should not be displayed.
This fixes two issues - the name of the bones were displayed incorrectly (because of a difference between index in the array and the actualy index of the bone), and the length of the sliders was fixed (now according to the length of active bones).

@RaananW LGTM feel free to merge when all good on your side.

authors: RaananW sebavan


text:
API Documentation

Hello,
I am giving Handesk a try and I would like to integrate it with one app that I have been working on and I'd like to use the provided API but I can't find any documentation whatsoever.
I managed to get a few things working by reading the source code but I feel like there's more to unveil.
Where could I read more about the API?
Thanks!

if you want to integrate to the api through php you can simply use the handesk-php package, and it has its methods well documented here:
https://github.com/BadChoice/handesk-php
if you are trying to use it using your custom integration (swift, ios, java..) there is no package yet (event it would be very welcome if you do it) and there is no documentation yet :(
The easiest way to see al the available methods is through the test cases as I have them all there
https://github.com/BadChoice/handesk/tree/dev/tests/Feature/Api
Let me know if I can help you more

authors: BadChoice sikrew

repo: BadChoice/handesk


text:
Improve ConvertTo-PodeWebPage output textbox

Describe the Change
When objects get passed to Pode.Web, they can look pretty bad coming to the textbox.
Even changing the line to something like this with a json conversion is a lot better:
(. $cmd @_args) | ConvertTo-Json | Out-PodeWebTextbox -Multiline -Preformat

Current output:

An improved output:

Have not tested against simple outputs, but most cmdlets emit objects and primitives generally play decently nice with ConvertTo-Json, so I wouldn't call it a big concern.
May want to do the same for the exception handling that is down 2 lines as well.

Don't forget that ConvertTo-Json depth wreaks havoc sometimes, so we will want to test carefully if we do use ConvertTo-Json as the solution. Maybe set depth to a specific value.


text:
gui 에 사용될 모듈 변화

현재 tkinter 모듈을 이용하여 제작 중인데 기술상의 문제와 코드가 매우 읽기에 부적절하여 보다 간편하고 더 잘 꾸밀 수 있는 pyQt5 모듈을 사용하려고 합니다. 혹시 궁금한 점 있으면 말씀해 주십쇼,

확실히 인터페이스 방식을 만드는 데에 tkinter 보다 수월할 거 같습니다. 그 외에 작동 방식에서 변화가 생기는 문제점은 없는건가요?

서로 비슷한 방식으로 작동하고 코드를 작성하고 작동시켜본 결과 따로 문제가 없었습니다. 그리고 Pyqt5의 경우 designer 모듈이 있어 거기서 디자인이 가능하여 tkinter 모듈 보다 효율적인 것 같습니다.

그렇다면 gui 예시 사진을 한 번 올려주시는 것도 저희가 비교하고 판단한는데 도움이 될 것 같습니다.

사실 서로 차이점이 없다고 생각합니다. 하지만 PyQt가 화면을 꾸미기에 더 효율적입니다.

authors: Bakhyoungwoo MuHaRVEY wan-su-2020

repo: Bakhyoungwoo/Opensource-destiny-


text:
Added new Tables

Created new tables to lower the level of nesting. Made changes to /users/signup, /boards, /addBoards, /login to reflect the same. Will make changes for other end points after your review

Found no conflict, approving merge!


text:
Updating the overall UI to modern, good-looking UI

Updation of UI means..

Changing the look and feel of buttons
Changing the background
Expressing the messages with cute vector images.
more if any.

Can take references from templates like

instaflutter
dribble


text:
Feature/GitHub actions integration

Initialize create react app, add githubs and heroku integration

Merging as this is required for automated deployment.

repo: BanklessDAO/bounty-board


text:
🛑 Legislative Assembly is down

In 6722cbe, Legislative Assembly (https://www.ntassembly.ca) was down:

HTTP code: 403
Response time: 290 ms

Resolved: Legislative Assembly is back up in d2a3ab3.

repo: Barctic/gnwt-monitor


text:
🛑 Industry, Tourism and Investment is down

In 7b2604d, Industry, Tourism and Investment (https://www.iti.gov.nt.ca) was down:

HTTP code: 504
Response time: 243 ms

Resolved: Industry, Tourism and Investment is back up in 11228ba after 7 minutes.


text:
🛑 Environment and Natural Resources is down

In 607f2e4, Environment and Natural Resources (https://www.enr.gov.nt.ca) was down:

HTTP code: 504
Response time: 214 ms

Resolved: Environment and Natural Resources is back up in d8c41cc after 7 minutes.


text:
🛑 Infrastructure is down

In 4500b58, Infrastructure (https://www.inf.gov.nt.ca) was down:

HTTP code: 504
Response time: 290 ms

Resolved: Infrastructure is back up in 6f1ad6b after 10 minutes.


text:
🛑 Finance is down

In 2f68e1f, Finance (https://www.fin.gov.nt.ca) was down:

HTTP code: 503
Response time: 9974 ms

Resolved: Finance is back up in 68b8208 after 7 minutes.


text:
Extended APIs delegate merge

Handlers for three different exit reasons have been added. The implementation right now is working,
but has alot of room for improvement I think. For starters, it should probably try to reuse some functionality across similar reasons (e.g. rdmsr and wrmsr). However, I think we should wait until more handlers are written before we try to generalize it.
Now, each exit reason is represented as a small class. The following pseudocode shows their basic function
auto key = make_key(vmcs)
auto handler = handler.at(key);
handler(vmcs);

What differs between the classes (and what I think should be generalized) is what makes up a "key". I view it as basically a snapshot of additional state/information about the exit e.g. right now, the wrmsr
key is the msr address (vmcs->save_state()->rcx), but it very well could be the address and the value written. This would allow for entities interested in wrmsrs to not have to worry about exceptional values written to the msr (and perhaps an exception susbsystem would only subscribe to exceptional write values).
What are some other ways/ideas that we could do this? Should we do this? The example code is mainly in exit_handler/{rdmsr,wrmsr,cr_access}.{h,cpp}. They are created in the vcpu_factory.cpp

I will start work on this tomorrow

authors: connojd rianquinn


text:
🛑 Filebrowser in Server is down

In 486aaea, Filebrowser in Server (https://files.jonthan.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Filebrowser in Server is back up in 0f48516.

repo: Baronhez/upptime


text:
🛑 QBitTorrent webUI is down

In bde3298, QBitTorrent webUI (https://qbittorrent.local.jonthan.xyz) was down:

HTTP code: 404
Response time: 670 ms

Resolved: QBitTorrent webUI is back up in d78038e after 6 minutes.


text:
🛑 QBitTorrent webUI is down

In 7119d90, QBitTorrent webUI (https://qbittorrent.jonthan.xyz) was down:

HTTP code: 404
Response time: 469 ms

Resolved: QBitTorrent webUI is back up in 25ea5a1 after 6 minutes.


text:
🛑 QBitTorrent webUI is down

In 9b5efb2, QBitTorrent webUI (https://qbittorrent.local.jonthan.xyz) was down:

HTTP code: 404
Response time: 517 ms

Resolved: QBitTorrent webUI is back up in 6147ab9 after 6 minutes.


text:
🛑 QBitTorrent webUI is down

In 6f76c7b, QBitTorrent webUI (https://qbittorrent.local.jonthan.xyz) was down:

HTTP code: 404
Response time: 705 ms

Resolved: QBitTorrent webUI is back up in 223f85f after 6 minutes.


text:
Микитенко Иван. КВБО-02-21. 21К0664

Проверьте пожалуйста 3 - 4.1 практические работы

Пока не вижу изменений для проверки :)


text:
FusedLocationClient.java uses or overrides a deprecated API.

🐛 Bug Report
When build for debug, compiler says geolocator_android-4.1.7\android\src\main\java\com\baseflow\geolocator\location\FusedLocationClient.java uses or overrides a deprecated API.
Terminal output
Note: C:\Users\faher\AppData\Local\Pub\Cache\hosted\pub.dev\geolocator_android-4.1.7\android\src\main\java\com\baseflow\geolocator\location\FusedLocationClient.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

Expected behavior
AssembleDebug in VSCODE
Version: 4.1.7
Platform:

[ ] :iphone: iOS
[X] :robot: Android

same issue occurred.

Same issue

I had this issue but  I realize that I forget to put the permissions in  AndroidManifest, when I added it, it works fine.
I don't know was that the real cause or not?

The solution is described in the package.
Usage->Android

On Android you'll need to add either the ACCESS_COARSE_LOCATION or the ACCESS_FINE_LOCATION permission to your Android Manifest. To do so open the AndroidManifest.xml file (located under android/app/src/main) and add one of the following two lines as direct children of the  tag (when you configure both permissions the ACCESS_FINE_LOCATION will be used by the geolocator plugin):

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

Starting from Android 10 you need to add the ACCESS_BACKGROUND_LOCATION permission (next to the ACCESS_COARSE_LOCATION or the ACCESS_FINE_LOCATION permission) if you want to continue receiving updates even when your App is running in the background (note that the geolocator plugin doesn't support receiving and processing location updates while running in the background):

<uses-permission android:name="android.permission.ACCESS_BACKGROUND_LOCATION" />

same issue here

Same issue here also

Same issue here but...
...not a train smash, no fix - but ONLY if 'deprecated' bothers you as much as it does me...
https://developers.google.com/android/guides/releases#october_13_2022
...a quick workaround ONLY to get rid of the 'geolocator_android-4.1.7\android\src\main\java\com\baseflow\geolocator\location\FusedLocationClient.java uses or overrides a deprecated API.' message:
Find (windows) X:\Users\xxxx\AppData\Local\Pub\Cache\hosted\pub.dev\geolocator_android-4.1.7\android\src\main\java\com\baseflow\geolocator\location\FusedLocationClient.java
Find (Line 85):
private static LocationRequest buildLocationRequest(@Nullable LocationOptions options) {
LocationRequest locationRequest = LocationRequest.create();
if (options != null) {
  locationRequest.setPriority(toPriority(options.getAccuracy()));
  locationRequest.setInterval(options.getTimeInterval());
  locationRequest.setFastestInterval(options.getTimeInterval() / 2);
  locationRequest.setSmallestDisplacement(options.getDistanceFilter());
}

return locationRequest;

}
Replace with:
private static LocationRequest buildLocationRequest(@Nullable LocationOptions options) {
LocationRequest locationRequest = new LocationRequest.Builder(Priority.PRIORITY_HIGH_ACCURACY, 1000)
.setWaitForAccurateLocation(false)
.setMinUpdateIntervalMillis(500)
.setMaxUpdateDelayMillis(1000)
.build();
return locationRequest;

}
No fix! Just a suggestion.

Replace with:
private static LocationRequest buildLocationRequest(@nullable LocationOptions options) {
LocationRequest locationRequest = new LocationRequest.Builder(Priority.PRIORITY_HIGH_ACCURACY, 1000)
.setWaitForAccurateLocation(false)
.setMinUpdateIntervalMillis(500)
.setMaxUpdateDelayMillis(1000)
.build();
return locationRequest;

@jangopper This code basically fixes the problem so, instead of temporarily fixing it in your local package cache, you could make this a PR and fix it for everyone! (assuming the maintainers merge it).

@ozaner Why can't we use the solution from the package? I wrote about it above.

@ozaner Why can't we use the solution from the package? I wrote about it above.

I already had the ACCESS_FINE_LOCATION and the ACCESS_BACKGROUND_LOCATION in my manifest when I got the warning.
Although I don't seem to be getting the warning anymore, with or without the changes to the manifest, so I honestly don't know...

@ozaner Why can't we use the solution from the package? I wrote about it above.

I already had the ACCESS_FINE_LOCATION and the ACCESS_BACKGROUND_LOCATION in my manifest when I got the warning.
Although I don't seem to be getting the warning anymore, with or without the changes to the manifest, so I honestly don't know...

Idk if I did it right, but I added all 3 fields to the manifest and that fixed the problem for me.  Although, perhaps, 1 of the first two options was enough.

Same here, and I already have  in the manifest

//	private static LocationRequest buildLocationRequest(@Nullable LocationOptions options) {
 //	LocationRequest locationRequest = LocationRequest.create();

 // if (options != null) {
 //    locationRequest.setPriority(toPriority(options.getAccuracy()));
 //    locationRequest.setInterval(options.getTimeInterval());
 //    locationRequest.setFastestInterval(options.getTimeInterval() / 2);
 //    locationRequest.setSmallestDisplacement(options.getDistanceFilter());
  }
 // return locationRequest

 // Replace with:
	private static LocationRequest buildLocationRequest(@nullable LocationOptions options) {
		LocationRequest locationRequest = new LocationRequest.Builder(Priority.PRIORITY_HIGH_ACCURACY, 1000)
		.setWaitForAccurateLocation(false)
		.setMinUpdateIntervalMillis(500)
		.setMaxUpdateDelayMillis(1000)
		.build();

     return locationRequest;
 // End replace
  }

it's look like this after?

This warning comes out after doing flutter clean first and then flutter build apk. Even adding the configuration parameters in the androidManifest at least in my case, the warning message comes out. My fear is that from one day to the next geolocation doesn't work anymore and I can't publish.
Is there any way to fix this?
I saw that in 2020 the manufacturer created a new version that fixed the problem. Is it possible to have a version with the resolution of the problem?

any update on this issue?

This issue is solved with version 4.2.1 of the geolocator_android package. To update please run flutter pub upgrade.

authors: Arcttyx FabienZE Horned-Nonsense Kumar-71 Saipreetham0 battlecook danilocatalanoapsystem gommido hanifmhd haulinhen jangopper mvanbeusekom onghuisheng ozaner

repo: Baseflow/flutter-geolocator


text:
Windows / Desktop getCurrentPosition without Network Causes Crash

🐛 Bug Report

Expected behavior
on  Windows / Desktop getCurrentPosition without Network Causes Crash
Reproduction steps
On Windows, Turn off all Network Connections and Then Try :
      final position = await Geolocator.getCurrentPosition(
        desiredAccuracy: LocationAccuracy.high,
      );

It will Crash the App. Try-Catch Didn't Help
Configuration
Version: 9.0.2
Platform:
Windows

Dear @AndreLuizNogueira,
Can you explain something outbox your environment (windows version and possibly device gps chip) and paste the output of flutter doctor -v below this issue? And do you have the output of the crashlog? Because it is unclear to me how I can reproduce this issue.

Dear @AndreLuizNogueira,
Can you explain something outbox your environment (windows version and possibly device gps chip) and paste the output of flutter doctor -v below this issue? And do you have the output of the crashlog? Because it is unclear to me how I can reproduce this issue.

Dear @AndreLuizNogueira,
Can you explain something outbox your environment (windows version and possibly device gps chip) and paste the output of flutter doctor -v below this issue? And do you have the output of the crashlog? Because it is unclear to me how I can reproduce this issue.

Sorry for The Delay.  the problem still ocurs. Here in my github I pushed a sample app that get location on click. if you run this on windows, with network off it will crash.
I know it can't get the location without internet, but it should'nt crash my app.
https://github.com/AndreLuizNogueira/flutter_application_1

It also crashes if the location service is off altogether in the windows settings:

Unless this is on, then the getCurrentPosition works.


text:
How to change collor in date

How to change collor in date

The color definition should be in the theme file - please take a look there.

repo: Bash-it/bash-it


text:
fix: fix broken concepts link

Description

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

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

authors: bt-platform-eng bweber


text:
Bug: limit of batch size too high with authentication

Change from 500 to 50.

Fixed in version 1.1.0

authors: BauwenDR deregtervictor

repo: BauwenDR/osta-wikipedia-extension


text:
🛑 Bawantha is down

In 2778348, Bawantha (https://www.bawantha.me) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bawantha is back up in e03af7a after 20 minutes.

repo: Bawanthathilan/mysite-uptime


text:
Admin -> Editor: Monaco editor integration

Load an instance of https://github.com/microsoft/monaco-editor for template fields to write markdown and html.
HEEx may be supported with a custom lang config, but that's not blocking and can be done in a following PR.

Support Elixir, HEEx, HTML, Markdown

@leandrocp appreciate your job and efforts

authors: AZholtkevych leandrocp

repo: BeaconCMS/beacon


text:
Add recipe for basic page authentication

This recipe describes how to create and implement your own plug for basic authentication on your app, using Plug.BasicAuth.

Nice!

authors: cbroeren leandrocp


text:
Goals

Here's my goals:

Improve WebSockets. The server should handle translating from the SDS godawful XML and other fields into usable data. We can leave a "raw" mode in on WS, but I think all communication otherwise should be via good old JSON
Add audio support. Want to be able to accept a line in and stream it out via HTTP. Maybe HLS. Eventually, I'd like to support Broadcastify Calls and outputting individual transmissions as individual WAV files
Build a iOS and Mac app for listening and control

What do you think @rabarar? I think this can all get done within a week or two.

Sounds like a good plan!

On Jun 18, 2020, at 11:39 PM, Robbie Trencheny notifications@github.com wrote:

Here's my goals:
Improve WebSockets. The server should handle translating from the SDS godawful XML and other fields into usable data. We can leave a "raw" mode in on WS, but I think all communication otherwise should be via good old JSON
Add audio support. Want to be able to accept a line in and stream it out via HTTP. Maybe HLS. Eventually, I'd like to support Broadcastify Calls and outputting individual transmissions as individual WAV files
Build a iOS and Mac app for listening and control
What do you think @rabarar? I think this can all get done within a week or two.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Now that we have audio going, going to suggest we add a database component, at least for long term storage/querying of metadata.

repo: Bearcatter/bearcatter


text:
Inconsistent handling of SS vs BL replays

I just tested the new replay feature and its pretty awesome, but I find some inconsistencies between the replay handling.
BeatLeader replays do not smooth at all, whereas the same map with the ScoreSaber replay does get smoothed by Camera2.
I can provide examples if necessary.
Edit: I'm reporting it here, since you bundle Camera2 in the release - and therefore think it's part of your responsibility to fix

Thanks for your report. I found the problem. As soon as you touch any camera setting in Camera2, it will update previous config and add limits field in the camera .json file. After this everything works just fine
old config:
"Smoothfollow": {
    "position": 10.0,
    "rotation": 5.0,
    "forceUpright": false,
    "followReplayPosition": true,
    "pivotingOffset": false
  }

After touching any camera setting:
"Smoothfollow": {
    "position": 10.0,
    "rotation": 1.1,
    "followReplayPosition": true,
    "limits": {
      "pos_x": "-Infinity:Infinity",
      "pos_y": "-Infinity:Infinity",
      "pos_z": "-Infinity:Infinity",
      "rot_x": "-Infinity:Infinity",
      "rot_y": "-Infinity:Infinity",
      "rot_z": "-Infinity:Infinity"
    },
    "pivotingOffset": false
  }

Looks like Kinsi unintentionally added backwards incompatible feature with adding support for BL replays. Sadly, it cannot be gracefully handled on our side :c
please go over to Camera2 github and forward this issue to Kinsi 🙏

That is not what is happening - Camera2 configs always get updated / migrated on game start - So if you update from the pre-limits version and start the game, the config file is updated right on game start
That being said, the limits have nothing to do with smoothing, thats just for limiting positional / rotational ranges
The issue here is probably that Scoresaber replays get smoothed twice - Once by scoresaber itself, and then again by Camera2. This is becase the only values that I can get from Scoresaber are already smoothed by it for usage with its own replay system. I have asked Umbra multiple times if I could somehow get unsmoothed values but to no avail.
So that its probably why it feels like SS is smoothed but BL is not, because SS is oversmoothed to hell and back. If you up the smoothing in Cam2 you would get a similar result.

nono, I propose changing the slider top limit, not the logic. I doubt that anyone uses values larger than 10, if 5 already looks like an earthquake :DD
But anyway, returning to the original topic. The only solution I can see (without changes from the SS team) - is separate smoothing settings for SS replays in Camera2. We won't add additional smoothing to compensate the difference. Cam2 will have full and predictable control over the camera behavior in BL replays

I might just go ahead and disable cam2 smoothing in SS replays until I get raw values from SS on the next full moon, maybe.

authors: Reezonate kinsi55 raineio

repo: BeatLeader/beatleader-mod


text:
language fixes

please see:
https://github.com/Behat/Mink/pull/180

Please, remove merge commits from your PR.

The needed commands are the following:
first create a topic branch for the changes: git branch language_fixes
then rebase this branch on develop: git rebase --onto upstream/develop upstream/master language_fixes
then you can push this feature branch to github and send a PR.
and you will probably want to reset your master branch to avoid having a diverging one

this PR is outdated
there is more langs(10) : cs,de,es,fr,ja,nl,pl,pt,ru,sv.

I'll check out all new again + resend
I had checked out https://github.com/Lennaert/Mink

authors: Erkan-Yilmaz everzet radepal stof

repo: Behat/Mink


text:
Correct 1-2 errors and 2-4 erasures with a lookup table

All possible permutations of error patterns or characters that could have been erased can be checked for a good checksum.
A more efficient algorithm later will allow correcting 4 substitution errors and 8 random erasures or 13 contiguous erases.
Write this in python and add to my codex32/ms32.py library
Consider testing performance of even more error/erasure correcting ability but if it does not run in Real time do not use.

all naive implementations correct 2 edits in 5-60 seconds which is too slow for restoring a wallet, in most cases the user could correct their mistakes off paper much faster than that defeating the point.
A separate utility can do deeper error correction for those needing to wait because their shares can't be read or were legitimately wrote down wrong.
However the real-time implementation may be able to do a final 1 delete pass on all candidate strings > VALID_LENGTH after the single edit is exhausted. delete is 32 times cheaper than insert and 30 times cheaper than substitution. This should run in about 1 second, which is perfect.

The error correction is working well for all 2 and some 3 error patterns.
The GUI needs to be beautified with color to highlight the suggested corrections vs what they input and the old dialogs should still give feedback., might need some sleep commands or to refactor input_share

Erasure correction by marking illegible characters with "?" and characters outside of the bech32 CHARSET has not been implemented and should be.

Also while waiting for the ECC to run, highlight the easily known wrong characters: ? , wrong case, non-bech32 CHARSET, wrong hrp, wrong separator, wrong threshold, wrong identifier, repeated share index, mark these as erasures for the ECC processor or substitute the correct or probably correct value (B=8, last valid share's threshold & identifier, the correct case.)
Display and highlight the initial corrections. So it's similar to the next dialog that highlights the corrections.
This dialog displays how the user typed it, the next one with the corrections is ALL CAPS.
Use the same color to mark the location of mistakes that can't be easily corrected as used in create seed which only shows locations of wrong characters not the correction.

repo: BenWestgate/Bails


text:
Asteroid Proc-Gen (Grid Proc-Gen)

This is what the 'Mining Tiles' are in Mining Station 14..
This feature is required for randomization of the Mining Asteroid..
Might be a good idea to also look in to Crystal Punks BiomeSpawners, it looks like a more advanced version of the miningtiles.. might be a good idea to merge those...
If we merge BiomeSpawners from Crystal Punk, then this might be considered an EASY task.. so im putting both EASY and MEDIUM tags

#6 Resolves This.


text:
On-premise node support

Motivation
We need to be able to support on-premise clusters and hybrid-cloud clusters.

We have an idea how to handle LB DNS in on-premise use cases.

Implement support for "externally pre-made" DNS records.
User would manually create a DNS record pointing to pre-selected LB machines beforehand.
Then, the user would input the DNS hostname into Claudie inputManifest, e.g. via a new field externally-premade: .
Claudie would assume the DNS record for that hostname already exists, and not manage it (i.e. no healthchecks and no self-healing).
Claudie would attempt to create the cluster utilizing that DNS record as the kube-api endpoint.

This might be relevant to bootstrapping connectivity across private networks.
https://tailscale.com/blog/how-nat-traversal-works/

authors: MarioUhrik bernardhalas

repo: Berops/claudie


text:
Vertical shift

Is it possible to create vertical shift for beyondar objects, which are placed in one direction and overlap each other?

Was there any advance or solution for this bug?, this is extremely important for augmented reality geo based.

mey dey, mey dey, help please! :(

If somebody still have this problem here is my simple solution.
I take all points and sort them from nearest to farest (this is not necessary but it will ensure that nearest objects are on bottom and farest on top). Then i create ARGeoObject  which will compute alternative gps coordiante in fixed distance of user  and check if there is collision with previous objects (for nearest item there is empty list of objects so i just add him) and then add him into mARGeoObjects list. If object has collision with previous object i just increase level ( for every collision).  You just need to play with constants - fixedDistance for radius of gray circle, collisionDistance for minimum distance between big red dots, and altitudeMultiplier for stacking size of objects on your screen(depends on your marker size)
On image are small red dots (original gps). And bigger red dots in fixedDistance radius from user.
btw ignore java syntax its written in browser and also one missing red dot on image:D hope it helps:-)

double altitudeMultiplier = 5.5;
	double fixedDistance = 15;
	double collisionDistance = 5;
	private ArrayList<ARGeoObject> mARGeoObjects = new ArrayList<>();

for(Location  location : locations)
{
ArGeoObject temp = checkGeoObject(new ArcGeoObject(location.getLatitude(), location.getLongitude(), computeDistanceFromUser(location))
mARGeoObjects.add(temp)
	GeoObject geoObject = new GeoObject(new Random().nextInt());
		geoObject.setGeoPosition(location.getLatitude(), location.getLongitude(), temp.level * altitudeMultiplier);
}
	class ARGeoObject {
		double latitude;
		double longitude;
		double level = 0;
		double originalLongitude;
		double originalLatitude;
		double distance;
		Location loc;

		ARGeoObject(double originalLatitude, double originalLongitude, double distance) {
			this.originalLatitude = originalLatitude;
			this.originalLongitude = originalLongitude;
			loc = getFixedLocation(originalLatitude, originalLongitude, distance);
			this.distance = distance;
			latitude = loc.getLatitude();
			longitude = loc.getLongitude();
		}

		public double getDistance(ARGeoObject arGeoObject) {
			return loc.distanceTo(arGeoObject.loc);
		}
	}

	private ARGeoObject checkGeoObject(ARGeoObject geoObject) {
		if (mARGeoObjects != null && mARGeoObjects.size() != 0) {
			for (ARGeoObject arGeoObject : mARGeoObjects) {
				if (geoObject.getDistance(arGeoObject) < collisionDistance) {
					geoObject.level++;
				}
			}
		}
        return geoObject;
	}

Did anyone find a solution to geoObjects Overlapping problem? The textures overlap and it looks really bad for Geo based augmented reality.

repo: BeyondAR/beyondar


text:
Missing is_sorted() function in algorithm.

Recently I have just checked this repo, I found the is_sorted() function is missing. This is_sorted() function which is related to the Algorithm.  Can I make my first contribution by adding this function?

Hi, I am new to this project and want to contribute. Can you please guide me from where should I start.

Im new to open source and would like to contribute in this project

Hi! I would like to contribute to this project. Could you please assign to me this part?


text:
Switching to Z-Schema

removed tests with using strings and dates in fields minimum/maximum
changed mechanism of "no required" (from "schema.required = [];" to "delete schema.required;")
delete schema.required if we copy schema from param  and if required is boolean

Hi.  Thanks for the PR.  It's much appreciated, and I'll definitely take a look at it as soon as I get a chance.  It may be a few days though, since things are super busy for me right now.

This pull request includes the changes of #26. Maybe that can be split up?

BigstickCarpet, where are you? We are miss you!
Looks like z-schema is not planning support of json-schema v5 in the near future.
May be better switch to ajv?

I'm in India on a business trip.  working around the clock.  no time to work on code right now.  But I'll get back to it when I return to the U.S. in a couple weeks

Really? a couple weeks?

authors: BigstickCarpet Santinell winniehell


text:
Closing and opening new tabs will end up in a crash after some time

Steps to reproduce
First search for nekopara (Don't know if you do need multipele sources enabled but I have
Sankaku complex, gelbooru, konachan and yande.re enabled)
After that just open a new tab with the '+' symbol on the right or ctrl +T
Now directly close the new tab and repeat this process a couple times behind each other (but let the first tab with nekopara stay open)
After a couple times (Sometimes just 2 sometimes 5 or more) it will result in a crash
(Could also maybe be in some kind related to the other topic's I posted)
System information
Windows 10 with the latest nightly version

Indeed! 👍
After some investigation, guaranteed reproduction steps are:

Close a tab placed before a non-closable tab (i.e. Downloads, Favorites, or Log tab), so that after closing the tab, a non-closable tab is selected
Create a new tab
Crash

repo: Bionus/imgbrd-grabber


text:
Manage desktop wallpaper

Describe the solution you'd like
what about making this wallpaper desktop changing tool since it already have capabilities to fetch image from a big pool of sources.
so basically what i ask for is an option to make the app able to change desktop background from a given sources (with search queries and tags defined).
then it automatically get some images randomly (like it already does) then apply them to monitors as wallpapers then cache the images on desktop or the urls at least. with the option to blacklist images or urls if needed. also a setting to control if i want to save or remove the image after use will be very good (defaults to set save location already)
Describe alternatives you've considered
binaryfortress  display fusion app https://www.displayfusion.com/
jhon's background switcher https://johnsad.ventures/software/backgroundswitcher/windows/

Wouldn't you be able to achieve this by having a monitor set to download images to a given directory, then having Windows use this directory as a wallpaper?

authors: Bionus xEyad


text:
Cannot download any images from gelbooru/danbooru

The title says it all. I just tried downloading all the Hyperdimension Neptunia images from both gelbooru and danbooru (since for some reason they have different ammounts of images), and when I click download, it loads it all, starts individually downloading the images like it's supposed to, then I get the red ball of death and it errors every image I download.

Alright, nevermind. Reinstalling the program seems to have fixed it. Go figure.


text:
Refactoring PAML naming to LabOP

Per https://github.com/Bioprotocols/paml/issues/107 & Dan's recent email to the mailing list (https://groups.google.com/g/bioprotocols/c/ijV7jHK5t2w) PAML is being renamed to LabOP.
Clearly there are a lot of places to make this replacement rename, and it might take awhile to be fully accomplished. Here is a short list that can start taking a crack at...
(1) This repo name itself & included documentation pamled
(2) The Github landing page (https://github.com/Bioprotocols) (excluding the logo as of 2022-10-18)
(3) The Bioprotocols.org landing page (https://bioprotocols.github.io/paml/ <- note paml in URL)
(4) Places in code in various repos... "labop" repo
(5) Documentation on Open Collective (https://opencollective.com/bioprotocols)

Suggest we unpack these into individual issues.  The rationale is that if we bundle multiple to-do items into one issue, then it is very hard for us to tell if/when they are done and what remains to do.
Need to carefully maintain all the old pointers, as well.
Not sure what to do with the OWL stuff -- we're all just at the mercy of what the various tools can do with redirection/sameAs.

I pushed e807e5fb3544fc41b2cb5db7913210f9cfd49bbf, which renames PAML to LabOP.  This take of 1 and 4 (for this repo).

I fixed it.

On Oct 18, 2022, at 10:25 AM, Timothy R. Fallon, PhD @.***> wrote:
Hi @rpgoldman , I'm totally in support of separate issues - I'm personally planning on sticking to renaming in the documentation & letting others rename in code so I don't break thing. But, if making separate issues, might be nice to have them make a bidirectional link to this issue just so they're easy to find.
Regarding (2), I've updated the text documentation, but I don't know how to change the overall logo at the top left of the page. Maybe @danbryce has that authorization?
I'll edit & strike out the finished items on my first post in this issue.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

I believe this is probably completed? Closing if so. Can reopen if not.

authors: danbryce photocyte rpgoldman

repo: Bioprotocols/labop


text:
Update Installation via Virtual Machine with QuickStart Guide instructions

Edit or replace Installation via Virtual Machine with Install Option 2: Import a BitCurator Virtual Appliance in VirtualBox from Quickstart Guide.

Branched and ready for review! There's an extended description on this commit that needs some attention, since I wasn't sure best course of action for a link.

repo: BitCurator/documentation


text:
Future developments

[x]  Add size for table & paginator (default more bigger with sm, md, lg and custom setting)
[ ] Api fetch and local management items
[ ] Stacked heading
[ ] Moving documentation to a new site (such as Vercel)

Update Future developments:

Stacked heading
Moving documentation to a new site (such as Vercel)

repo: BitTheCat/tailwind-vue-data-table


text:
Fix for #12 : Card-Improvement

Fixes:
Fix for #12

Added responsiveness to the card section
Created a separate component for Cards
Changed from static to dynamic update for cards
Improved the legibility of the text for the description
added the google font in the css file so that it can be accessible to all

Suggestions:

To use a better typeface
Revamp the whole landing page to one interactive one

Hey @samalsubrat ,
Congratulations on your contribution! 🎉
Your efforts are truly valued. Keep up the great work, and continue contributing your talents!

repo: Bitbox-Connect/Bitbox


text:
Bug: create same URL

In hash function, I use base64 algorithm. Because almost every url start with http:// or https:// , shortened urls have same hash prefix.
I'll try to find a solution.

I think that rather than URL-based, ID-based hashing can fix it. And more easier to shorten because id's data type is Int.

Additionally, 5 character with base 62 encoding accomodate 916,132,832 urls.
Maybe maximum url size is 2048, require storage size is about 2TB.(simply url string data size is 1,876,240,039,936 Byte).
I think that this project dont need to expand scalability. So I use 5 character.

I think that rather than URL-based, ID-based hashing can fix it. And more easier to shorten because id's data type is Int.

Eventually I choose URL-based with some trick.
First, pad URL with zeros to make it's size 2048 bytes.
Second, split url bytes into 4 bytes.
Third, calculate sum of bytes with modular by maximum id value 916,132,832.

reference : https://www.geeksforgeeks.org/how-to-design-a-tiny-url-or-url-shortener/

MAP = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789"
MAXIMUM_ID = 916132831
PADDING_WIDTH = 2048
SPLIT_SEP = 4
BASE_NUM = len(MAP)

def preprocessing(origin_url:str)-> bytes:
    origin_url_bytes = origin_url.encode('ascii')
    if len(origin_url_bytes) < PADDING_WIDTH:
        origin_url_bytes = origin_url_bytes.zfill(PADDING_WIDTH)

    return sum([int.from_bytes(origin_url_bytes[i:i+SPLIT_SEP], byteorder='big') \
            for i in range(0, len(origin_url_bytes), SPLIT_SEP)]) \
            % MAXIMUM_ID

def make_hashable_url(origin_url:str) -> str:
    shortURL = ""

    id = preprocessing(origin_url)
    # for each digit find the base 62
    while(id > 0):
        shortURL += MAP[id % BASE_NUM]
        id //= BASE_NUM

    # reversing the shortURL
    return shortURL[len(shortURL): : -1]

repo: BiteSnail/URLshortener


text:
Update instagram.py

Ttttttttt

Are you being serious right now ?

authors: Alex-MHR Imambaeha


text:
Add repository information to the package.json file

Closes #3

I will add your change to our GitLab repository and it will be mirrored here. Your contribution will be acknowledged in the git commit :slightly_smiling_face:


text:
Consider moving all library code into delaunay.h to make a single header library

Considering the size of vector2.h, numeric.h, triangle.h and edge.h, these could fit into delaunay.h easily and would allow people to easily add delaunay.h to their projects without dragging four other header files with it.

OK,I see.Thank you very much!
---Original---
From: "Abe"notifications@github.com
Date: Thu, May 23, 2019 02:25 AM
To: "Bl4ckb0ne/delaunay-triangulation"delaunay-triangulation@noreply.github.com;
Cc: "Subscribed"subscribed@noreply.github.com;
Subject: [Bl4ckb0ne/delaunay-triangulation] Consider moving all library code into delaunay.h to make a single header library (#16)
Considering the size of vector2.h, numeric.h, triangle.h and edge.h, these could fit into delaunay.h easily and would allow people to easily add delaunay.h to their projects without dragging four other header files with it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I agree, the code is long due for maintenance, design wise and performance wise. I'll try to find some time in a near future to take care about that. If it's too urgent, I will gladly review any PR.

I'm happy to submit a PR if you don't get around to it. I was mostly making sure this is work that you'd be open to instead of throwing a random PR at you.

I started to think about a new design for the code. This will be my first priority in the next few weeks.
I'll make issues to tonight to guide our work, I'd like to change more than a few things :D

I commented in #34 with some code that would make short work of this issue, too.
The functionality is contained in 200 lines, but it would take a small amount of plumbing to have this not be a breaking change.
https://pastebin.com/NtVzLSCn
All the best!

authors: Bl4ckb0ne abetusk chetgnegy jianyancheng


text:
resume-date not right-justified when set print to letter portrait.

Hi,
Thank you for this template, it has been fun to play with.
When I create a printer-friendly CSS style, the resume-date' are underneath the resume-content instead of justified-right like a column. This occurs when I set:

@media print {
@page {
size: Letter portrait;
margin: 1.0cm;
}
... }

How do I get the resume-date back on the right side in print-preview?
Below is the full code and a screenshot:

@media print {
@page {
size: Letter portrait;
margin: 1.0cm;
}
body {
padding-top: 6rem!important;
}
h1,
h2,
h3,
h4,
h5 {
page-break-after: avoid;
}
.m-0,
.m-0 *,
.dont-print,
.dont-print * {
display: none!important;
}
.double,
.double * {
line-height: 1!important;
}
section.resume-section {
margin-top: -10rem!important;
padding-top: 0rem!important;
padding-bottom: 0rem!important;
page-break-after: avoid;
}
}

Thank you for any advise

Solved it, for my particular case...not a general (framework) solution:
@media print {
@page {
size: Letter auto;
margin: 1.0cm;
}
body {
padding-top: 10rem!important;
}
.m-0,
.m-0 *,
.dont-print,
.dont-print * {
display: none!important;
}
.double,
.double * {
line-height: 1!important;
}
.page-break {
page-break-before: always;
padding-top: 5rem;
}
#education {
margin-top: -66rem!important;
}
section.resume-section {
margin-top: -42rem!important;
padding-top: 0rem!important;
padding-bottom: 0rem!important;
}
}

repo: BlackrockDigital/startbootstrap-resume


text:
Audio Upload not working in production

Uploading images locally to the cloudinary bucket works fine but when uploading from the production environment, a [net::ERR_HTTP2_PING_FAILED] is thrown and the file never gets sent to the server. All other requests work perfectly with no issues.
What could be causing the problem?

Well seems the problem came from the server on which the backend was hosted. It has adjusted and now audio uploads work great.