profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ruslangabitov/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

ruslangabitov/azure-sdk-for-go 0

azure-sdk-for-go

ruslangabitov/azure-xplat-cli 0

Microsoft Azure Cross Platform Command Line

ruslangabitov/docker 0

Docker - the open-source application container engine

ruslangabitov/node 0

evented I/O for v8 javascript

push eventAzure/azure-sdk-for-go

Azure SDK Bot

commit sha 413f79e39c6b2711a03cf3cdf490f9836ac37ae9

Move SetTestPipelineVersion.ps1 to eng/common (#14389) Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

view details

Azure SDK Bot

commit sha 6ce9129d348546d0ec5c2f3d729a5180a77aa56f

Fix PackageName typo (#14391) Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

view details

Azure SDK Bot

commit sha ec8c8221ad43262b4a08efed7b41c6cd290db61e

Enable APIView status check (#14390) Co-authored-by: praveenkuttappan <55455725+praveenkuttappan@users.noreply.github.com>

view details

Azure SDK Bot

commit sha 6fa03faa82697de294d0b6335583fd5030585e63

Sync eng/common directory with azure-sdk-tools for PR 1448 (#14386) * Added more logging to API view create * Updated logs with arch board rescue email address * Fix as per review comments * Update logging to show API URL Co-authored-by: praveenkuttappan <prmarott@microsoft.com>

view details

Azure SDK Bot

commit sha 5ba9bc64b7fee104b148140d300ae6db297ae387

Fix bug where imported matrix parameter duplicates are not overrided (#14394) Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>

view details

Azure SDK Bot

commit sha 66e4cea1db91979b316c1499800022880abfce22

Fix logic in SetTestPipelineVersionInEngCommon (#14397) Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

view details

Joel Hendrix

commit sha 4b53918c307514f40850af0534ded078aa74cf45

Storage fixes (#14395) Omit x-ms-blob-type request header for AppendBlock() operation. Fixed XML error unmarshalling for some table APIs.

view details

Azure SDK Bot

commit sha 1b5e008a20b6382007c576c991be7c4c95f496eb

move SetTestPipeline into its own template (#14398) Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

view details

Arcturus

commit sha 9e724d22b0bd1be237c6946748ad6f8579c33bb4

update the changelog's header format in generator (#14260)

view details

Chidozie Ononiwu

commit sha 24cec554e153a92d3c56955d2e5f65b8a0fb9f58

Update Package Properties Logic, make prepare release require only 1 argument, make rerun of Get-PkgProperties in Update-Changelog not required

view details

Chidozie Ononiwu

commit sha aced4fa95764018cbcc286951363ffc5d69af8c1

Remove ServiceDirectory parameter from PrepareRelease.ps1

view details

Chidozie Ononiwu

commit sha da71a984d866b6e524271b2b97216bb748f09da5

changes to argument names

view details

Chidozie Ononiwu

commit sha c12208dbc7e9e55edea84770a20a9d71e35a38dd

pass service directory to Get-AllPackageInfoFromRepo

view details

Chidozie Ononiwu

commit sha e2ce04aaa1780234305fe8f9db0737ac656c4158

Remove changes in Update-ChangeLog.ps1

view details

Chidozie Ononiwu

commit sha d87542ac8c9caf1517e17a88182ae15333089cb1

updates to Package-Properties.ps1

view details

push time in 12 minutes

issue closedAzure/azure-sdk-for-go

Proposal: discontinue support for multiple API versions in the track 2 SDK

Please add a :+1: reaction if you support this proposal. If you do not, please leave a comment describing why.

In track 1, we added support for side-by-side API versions as a means to insulate customers against breaking changes across API versions. Now that we have a solid versioning story via Go modules, the side-by-side model is somewhat obsolete for this purpose.

Simply put, each RP (compute, network, redis, etc) would have its own module. When an RP releases a new API version, a new major version of its module would be released, targeting the new API version.

For example, we release a v1 module for compute at its latest API version (2020-06-03). When the next API version for compute is published (e.g. 2021-03-01) a v2 module would be released targeting that version.

This would consolidate the directory structure. Today we have this.

/services/compute/mgmt/<api version>/compute
/services/compute/mgmt/<api version>/compute
/services/compute/mgmt/<api version>/compute

With the new proposal it would condense to this.

/sdk/armcompute

There is a question of what this means for Azure stack and the sovereign clouds and am researching further.

We also plan to update the track 2 codegen to include an optional API version parameter as an escape-hatch. It would be used to specify an older API version to use with the current codegen in the event that a specific API version of a service is required but there is no module version available.

closed time in 2 hours

jhendrixMSFT

issue commentAzure/azure-sdk-for-go

Proposal: discontinue support for multiple API versions in the track 2 SDK

Current POR is to continue to support multiple API versions side-by-side.

jhendrixMSFT

comment created time in 2 hours

issue openedAzure/azure-sdk-for-go

[Storage] Getting error "StatusCode=400, ErrorCode=InvalidHeaderValue, ErrorMessage=The value for one of the HTTP headers is not in the correct format." while using batch operations on tables and sasToken client.

Bug Report

Paths: github.com/Azure/azure-sdk-for-go/storage

Version: v52.3.1

What happened?

After creating storage client using NewAccountSASClientFromEndpointToken everything works correctly. When trying to create storage client using NewAccountSASClientFromEndpointToken there is always an error while using batch operations on tables (storage: service returned error: StatusCode=400, ErrorCode=InvalidHeaderValue, ErrorMessage=The value for one of the HTTP headers is not in the correct format.). Standard operations work correctly.

What did you expect or want to happen?

Working with client created by NewAccountSASClientFromEndpointToken method.

How can we reproduce it?

  1. Create storage account
  2. Generate sasToken
  3. Create table
  4. Run below code
import (
	azstorage "github.com/Azure/azure-sdk-for-go/storage"
)

//...

client, _ := azstorage.NewAccountSASClientFromEndpointToken(host, sasToken)

tableService := client.GetTableService()

table := tableService.GetTableReference(tableName)

tableBatch := table.NewBatch()

entity := table.GetEntityReference("partkey1", "rowkey1")

tableBatch.InsertOrReplaceEntityByForce(entity)

err := tableBatch.ExecuteBatch()
println(err.Error())

Returns:

storage: service returned error: StatusCode=400, ErrorCode=InvalidHeaderValue, ErrorMessage=The value for one of the HTTP headers is not in the correct format.
RequestId:628b8b14-3002-008e-4e17-143c18000000
Time:2021-03-08T12:35:27.9143308Z, RequestInitiated=Mon, 08 Mar 2021 12:35:27 GMT, RequestId=628b8b14-3002-008e-4e17-143c18000000, API Version=

created time in 6 hours

push eventAzure/azure-sdk-for-go

Arcturus

commit sha 9e724d22b0bd1be237c6946748ad6f8579c33bb4

update the changelog's header format in generator (#14260)

view details

push time in 12 hours

PR merged Azure/azure-sdk-for-go

Reviewers
[SDK automation] update the changelog's header format in generator

Update the generator to apply the changes from #14164

<!-- Thank you for contributing to the Azure SDK for Go.

Please verify the following before submitting your PR, thank you! -->

  • [ ] The purpose of this PR is explained in this or a referenced issue.
  • [ ] The PR does not update generated files.
  • [ ] Tests are included and/or updated for code changes.
  • [ ] Updates to CHANGELOG.md are included.
  • [ ] Apache v2 license headers are included in each file.
+10 -10

2 comments

1 changed file

ArcturusZhang

pr closed time in 12 hours

pull request commentAzure/azure-sdk-for-go

[SDK automation] update the changelog's header format in generator

Will this change be compatible with old version of changelog? Or maybe this question doesn't make sense?

This does not change anything in the release. Releases are made in separate tool. This only change the CHANGELOG in Preview SDK Change PRs

ArcturusZhang

comment created time in 13 hours

pull request commentAzure/azure-sdk-for-go

[ReleasePR hybriddatamanager/mgmt/2016-06-01/hybriddata] Fix issue 13147 for HybridDataManager

Thank you for your contribution openapi-sdkautomation[bot]! We will review the pull request and get back to you soon.

openapi-sdkautomation[bot]

comment created time in 15 hours

pull request commentAzure/azure-sdk-for-go

[ReleasePR hybriddatamanager/mgmt/2019-06-01/hybriddata] Fix issue 13147 for HybridDataManager

Thank you for your contribution openapi-sdkautomation[bot]! We will review the pull request and get back to you soon.

openapi-sdkautomation[bot]

comment created time in 15 hours

pull request commentAzure/azure-sdk-for-go

[SDK automation] update the changelog's header format in generator

Will this change be compatiable with old version of changelog?

ArcturusZhang

comment created time in 15 hours

issue commentAzure/azure-sdk-for-go

Azure Functions for Go

@josephspurrier Is there any performance impact in choosing custom handlers vs the languages that are supported natively?

joshgav

comment created time in a day

issue commentAzure/azure-sdk-for-go

Azure Functions for Go

There is a December 2020 video on Azure custom handlers for Go in the meantime: https://www.youtube.com/watch?v=RPCEH247twU

joshgav

comment created time in 2 days

push eventAzure/azure-sdk-for-go

Azure SDK Bot

commit sha 1b5e008a20b6382007c576c991be7c4c95f496eb

move SetTestPipeline into its own template (#14398) Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>

view details

push time in 3 days

delete branch Azure/azure-sdk-for-go

delete branch : sync-eng/common-SetTestPipelineVersionInEngCommon-1472

delete time in 3 days

PR merged Azure/azure-sdk-for-go

Sync eng/common directory with azure-sdk-tools for PR 1472 Central-EngSys EngSys

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/1472 See eng/common workflow

+15 -0

0 comment

1 changed file

azure-sdk

pr closed time in 3 days

issue openedAzure/azure-sdk-for-go

Support Gen2 for PowerBI Embedded

Feature Request

<!-- To help us better serve you, describe the feature you'd like and how it will help you.

Note that this is for SDK specific features. For Service API feature requests, use https://github.com/Azure/azure-rest-api-specs. -->

Current version of the SDK supports only Gen 1 for Power BI Embedded. Please, add support for Gen 2. ARM templates already support that: https://docs.microsoft.com/en-us/power-bi/developer/embedded/azure-pbie-create-capacity?tabs=ARM-template#embedded-gen2-preview

That will allow to add support for PBI Embedded Gen 2 to terraform azurerm provider https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/powerbi_embedded

created time in 3 days

PR opened Azure/azure-sdk-for-go

Sync eng/common directory with azure-sdk-tools for PR 1472

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/1472 See eng/common workflow

+15 -0

0 comment

1 changed file

pr created time in 3 days

push eventAzure/azure-sdk-for-go

adreed-msft

commit sha 6e9d87478a7bca313d753785cf7d000642bb24d8

Port examples from Track 1.5 + A slew of changes suggested in the Azure SDK sync. (#14344) * Fixed compiling issues with azcore 0.13.4 and generator 4.0.0-preview.8 * Implement return method for errors in listing wrappers * Fix tests, work out API more * Port examples * storageError port POC * Remove cause from storageError * Update examples to use to SDK * Port error handling example, add InternalError * Make minor changes suggested in API review * Additional APIView changes * Add SAS generation to storage clients * Resolve errors in tests Co-authored-by: zezha-msft <zezha@microsoft.com> Co-authored-by: Mohit Sharma <65536214+mohsha-msft@users.noreply.github.com>

view details

push time in 3 days

issue closedAzure/azure-sdk-for-go

[Storage] Getting error "Could not insert data: invalid character '<' looking for beginning of value" while using batch operations on tables and sasToken client.

Bug Report

Paths: github.com/Azure/azure-sdk-for-go/storage

Version: v51.3.0

What happened?

After creating storage client using NewAccountSASClientFromEndpointToken everything works correctly. When trying to create storage client using NewAccountSASClientFromEndpointToken there is always an error while using batch operations on tables (Could not insert data: invalid character '<' looking for beginning of value). Standard operations work correctly.

What did you expect or want to happen?

Working with client created by NewAccountSASClientFromEndpointToken method.

How can we reproduce it?

  1. Create storage account
  2. Generate sasToken
  3. Create table
  4. Run below code
import (
	azstorage "github.com/Azure/azure-sdk-for-go/storage"
)

//...

client, _ := azstorage.NewAccountSASClientFromEndpointToken(host, sasToken)

tableService := client.GetTableService()

table := tableService.GetTableReference(tableName)

tableBatch := table.NewBatch()

entity := table.GetEntityReference("partkey1", "rowkey1")

tableBatch.InsertOrReplaceEntityByForce(entity)

err := tableBatch.ExecuteBatch()
println(err.Error())

Returns Could not insert data: invalid character '<' looking for beginning of value

closed time in 3 days

rafalrygas

issue commentAzure/azure-sdk-for-go

[Storage] Getting error "Could not insert data: invalid character '<' looking for beginning of value" while using batch operations on tables and sasToken client.

This is due to attempting to unmarshall an XML response as JSON. It's been fixed in v52.3.1

rafalrygas

comment created time in 3 days

created tagAzure/azure-sdk-for-go

tagv52.3.1

Microsoft Azure SDK for Go

created time in 3 days

release Azure/azure-sdk-for-go

v52.3.1

released time in 3 days

push eventAzure/azure-sdk-for-go

Joel Hendrix

commit sha 4b53918c307514f40850af0534ded078aa74cf45

Storage fixes (#14395) Omit x-ms-blob-type request header for AppendBlock() operation. Fixed XML error unmarshalling for some table APIs.

view details

push time in 3 days

PR merged Azure/azure-sdk-for-go

Storage fixes

Omit x-ms-blob-type request header for AppendBlock() operation. Fixed XML error unmarshalling for some table APIs.

<!-- Thank you for contributing to the Azure SDK for Go.

Please verify the following before submitting your PR, thank you! -->

  • [ ] The purpose of this PR is explained in this or a referenced issue.
  • [ ] The PR does not update generated files.
  • [ ] Tests are included and/or updated for code changes.
  • [ ] Updates to CHANGELOG.md are included.
  • [ ] Apache v2 license headers are included in each file.
+165 -152

1 comment

5 changed files

jhendrixMSFT

pr closed time in 3 days