Граф коммитов

486 Коммитов

Автор SHA1 Сообщение Дата
Joel Hendrix 3dc3aeb614
Prepare for patch release (#295) 2024-01-09 10:23:26 -08:00
dependabot[bot] f0486fb3e3
Bump gopkg.in/yaml.v3 from 3.0.0-20210107192922-496545a6307b to 3.0.0 (#290)
Bumps gopkg.in/yaml.v3 from 3.0.0-20210107192922-496545a6307b to 3.0.0.

---
updated-dependencies:
- dependency-name: gopkg.in/yaml.v3
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-01-08 15:53:55 -08:00
dependabot[bot] fecd883c2a
Bump golang.org/x/crypto from 0.14.0 to 0.17.0 (#294)
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.14.0 to 0.17.0.
- [Commits](https://github.com/golang/crypto/compare/v0.14.0...v0.17.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-01-08 15:48:25 -08:00
dependabot[bot] d6058c9a93
Bump golang.org/x/net from 0.8.0 to 0.17.0 (#293)
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.8.0 to 0.17.0.
- [Commits](https://github.com/golang/net/compare/v0.8.0...v0.17.0)

---
updated-dependencies:
- dependency-name: golang.org/x/net
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2024-01-08 13:21:43 -08:00
Joel Hendrix 07e5a11a61
Mark module as deprecated (#289) 2023-07-31 15:59:56 -07:00
Joel Hendrix c07509cff9
Update to the GA version of go-amqp (#288)
* Update to the GA version of go-amqp

Updated readme message with GA announcement of azeventhubs.

* update changelog and version info

* update internal pipeline to supported version of Ubuntu

* check for specific error conditions that are now explicitly returned
2023-05-24 15:53:35 -07:00
Joel Hendrix 1761881894
Update to latest azure-amqp-common-go and go-amqp modules (#287)
* Update to latest azure-amqp-common-go and go-amqp modules

* fix test fake and update go-amqp with race fix

* fix bug in lease renal logic
2023-03-31 12:38:42 -07:00
Richard Park 153d3ccfa6
Upgrading golang.org/x/net/websocket package to v0.8.0 (#286)
Updating golang.org/x/net to address dependabot findings.
2023-03-23 09:50:33 -07:00
Joel Hendrix 0e9e4ef2a1
Prepare v3.4.0 release (#283) 2022-12-06 11:14:18 -08:00
Joel Hendrix 8a67a58a98
Update to latest go-amqp and common module (#281)
* Update to latest go-amqp and common module

* fix detection of closed links

* clean up lint

* cleanup

* make detach errors recoverable

* update to latest common and tagged go-amqp
2022-12-06 11:03:37 -08:00
Joel Hendrix 519593c461
Update CI to latest version of Go (#282)
* Update CI to latest version of Go

Update to latest linter.

* fix formatting

* more formatting
2022-12-05 15:00:49 -08:00
microsoft-github-policy-service[bot] 8a7b58b74b
Microsoft mandatory file (#264)
Co-authored-by: microsoft-github-policy-service[bot] <77245923+microsoft-github-policy-service[bot]@users.noreply.github.com>
Co-authored-by: Richard Park <51494936+richardpark-msft@users.noreply.github.com>
2022-11-28 12:52:40 -08:00
Richard Park 571caa480f
Updating to let people know that there's a new beta package if they'd like to try it (#278)
Updating readme so people know that azeventhubs (the newer package) is heading towards GA and the beta is something we'd like people to try out.
2022-11-09 16:27:42 -08:00
Richard Park d9a88501ef
Fixing issue with a lease existing on start (#277)
Storage failures don't return a Response, and require us to do an errors.As() and check the returned error instead. This checks for the two codes that can come back if the blob already exists (409) or if the blob exists _and_ it has an active storage lease (412).

Also, fixed a race condition in the LeaseReceiver that was causing Storage/TestMultiple() to fail.

Fixes #276
2022-11-08 15:47:40 -08:00
Richard Park adc9788f66
Vendor the azblob 0.6.0 dependency so customers can upgrade to later blobs packages (#262)
* vendoring 0.6.0 of azure-storage-blob-go

* updating internal references

* Attempting internal vendoring for some pieces, public interface coming from 'azblob'.

* slight modifications

* linter clean-up

* skip lint and gocyclo vendored azblob

* fix additional formatting

* skip gocyclo and linting azblob in integration tests

* use gocyclo ignore instead of finding files

* Even though they're the vendored and non-vendored azblob's ServiceCodeTypes are strings they don't "match" when it comes to determining if they're the same type. Aliasing should work just fine here.

* fix incorrect comment

* Update version and changelog

Co-authored-by: ripark <ripark@microsoft.com>
Co-authored-by: Joel Hendrix <jhendrix@microsoft.com>
2022-10-21 10:39:34 -07:00
Joel Hendrix d88c0a040d
fix run command for golangci-lint in makefile (#270) 2022-07-26 15:44:57 -07:00
Joel Hendrix a3e806ebc3
install golangci-lint for integration tests (#269) 2022-07-26 15:37:55 -07:00
Joel Hendrix d735432aab
switch makefile to use golangci-lint (#268) 2022-07-26 15:31:41 -07:00
Joel Hendrix 59429b3e87
add gocyclo back to integration CI (#267)
It's used by the makefile and was inadvertently removed.
2022-07-26 15:24:36 -07:00
Joel Hendrix ddda381a9a
update integration CI to latest version of Go (#266) 2022-07-26 15:12:58 -07:00
Joel Hendrix 21382524b6
update CI to latest versions of Go (#263)
* update CI to latest versions of Go

* update dependencies

* switch to golangci-lint

* lint and format clean-up

* switch to go install
2022-07-26 15:02:58 -07:00
Richard Park 15b4b52d1a
Fixing changelog and version - it was behind so my version bump was incorrect. (#254)
Changelog and version.go were actually behind by more than one release, so I needed to correct it.
2022-04-28 10:22:16 -07:00
Richard Park e473b7e4f6
Fixing race condition in LeaserCheckpointer where it can fail with a ContainerAlreadyExists error #253
There's a slight race condition between checking the store exists and the container being created.
    
We can handle it easily if we just allow ContainerAlreadyExists to be considered successful. Also, since the storage tests were failing (unrelated to my change) in race detection I also fixed that as well.

Fixes #252
Fixes #225
2022-04-28 10:12:14 -07:00
Richard Park 73b7c0f7b2
Update to handle use *amqp.DetachError instead of ErrLinkDetached (go-amqp change) (#245)
Updating to the latest go-amqp and azure-amqp-common-go

* go-amqp will return *amqp.DetachError now instead of ErrLinkDetached (which is being removed).
* Now that we can set fields to nil they can be properly omitted.

Misc: Fixing a unit test that was broken.
2021-12-07 17:06:42 -08:00
Richard Park bb122cac0a
Exporting a subset of AMQP message properties (#239)
Exporting a small subset of read-only (ie, not sendable) properties from the AMQP message. This mimics the structure of what we have in other SDKs but stops short of allowing them to be sent.
2021-10-11 16:29:59 -07:00
Richard Park c168808e24
*amqp.Sender renamed ID() to LinkName() (#238) 2021-10-05 15:52:55 -07:00
Joel Hendrix 96e6508b93
Update to latest go-amqp (#236)
Includes update due to API breaking changes.
Fixed some linter bugs.
2021-10-01 15:23:42 -07:00
Richard Park e9f5ac3a5b
Using new option in go-amqp that lets us keep the link alive after disposition errors #234
go-amqp would, prior to the recent change in https://github.com/Azure/go-amqp/pull/47, close the link if any disposition errors were returned by the service.

This premature link closing would cause us to unnecessarily thrash if we were being throttled. It could also cause us to return errors even when a batch of messages _had_ been committed by Event Hubs - the disconnect would either interrupt or override the successful result. This was particularly bad when doing many parallel sends on the same link.

We now (for senders) configure the link to not detach on disposition errors. Errors will still be bubbled up to the client but they will be properly sent to the call that failed, rather than to all callers.
2021-08-17 13:42:53 -07:00
richardpark-msft 2278e1124a Updating throttling.go to validate messages after sending 2021-08-17 13:36:46 -07:00
richardpark-msft 24a55158e5 Update with the correct version number 2021-08-16 17:30:00 -07:00
richardpark-msft fa1fdd1d73 empty commit 2021-08-16 16:38:30 -07:00
richardpark-msft fe908f327f Fix spelling mistake 2021-08-16 16:25:37 -07:00
richardpark-msft b3cb1b921c Updating changelog with PR 2021-08-16 16:10:26 -07:00
richardpark-msft 329b8caa5d Using new option in go-amqp that lets us keep the link alive, even when we get disposition errors.
From what we've seen disposition errors are not link-ending errors. One of the more common ones is when the service indicates that you are being throttled.

_Some_ sends will complete (and some will fail) but closing the link means we can't tell which are which.
2021-08-16 16:03:16 -07:00
Richard Park 3d81e00128
Adding in a sample using EventHubs with OpenCensus #233
Adding in an Event Hubs sample that shows how to integrate with OpenCensus.
2021-08-10 16:46:26 -07:00
richardpark-msft e45ed571f9 empty commit 2021-08-10 16:36:30 -07:00
Richard Park 833a40726b Merge branch 'eh-logging-sample' of github.com:Azure/azure-event-hubs-go into eh-logging-sample 2021-08-04 22:48:18 +00:00
Richard Park bf5b15cb31 rebuild 2021-08-04 22:48:12 +00:00
Richard Park b44410bf57
Merge branch 'master' into eh-logging-sample 2021-08-04 15:08:55 -07:00
Richard Park d65a4e3721 Let's go ahead and comment the blank lines too... 2021-08-04 20:41:30 +00:00
Richard Park 8b838e2dd1 Creating a sample to show how to activate logging within EventHubs using OpenCensus 2021-08-04 20:36:43 +00:00
Richard Park b794b15677
Merge pull request #232 from Azure/recovery-changes
The recovery algorithm could get into a cycle where two goroutines could continue to recover, even when a new link was in place. This can cause a lot of thrash since each recovery of the link will interrupt any in-progress sends, causing even more recoveries, etc...

This PR fixes that by checking the link ID that we are trying to recycle. If it doesn't match then the link must already have been recovered so we can no-op and early return.
2021-08-03 12:39:14 -07:00
Richard Park 4a2d1e6e23 force rebuild 2021-08-03 19:33:21 +00:00
Richard Park c257820f32 Rename file to match what it does and add in comments for linting. 2021-08-03 18:17:03 +00:00
Richard Park b3e3b9b4fb Comment no longer applies. Will need to revisit in the future. 2021-08-03 18:14:42 +00:00
Richard Park 74c90a77d5 Add in some tests for block 1 of the recovery code.
Not perfect (maybe even repulsive) but they work and can support us for more changes later.
2021-08-03 06:22:58 +00:00
Richard Park 0ce0412a84 Removing the code that tries to minimally recreate the link. newSessionAndLink is a little too modest about it's capabilities - it also creates a new connection.
This part wasn't the highest value for recovery compared to just skipping recovery altogether if the link had cycled, so for now I'll just remove it and replace it with a TODO.
2021-08-03 02:32:34 +00:00
Richard Park ee14f14fcd Added test that shows ErrLinkClosed vs ErrLinkDetached 2021-08-03 01:30:11 +00:00
Richard Park 489579cbd9 If the expectedLinkID is empty we just skip the ID check altogether and fallback to the normal recovery checks. 2021-08-03 01:20:28 +00:00
Richard Park 26a33e68d8 Update changelog with fix we just made. 2021-08-03 00:25:54 +00:00