Skip to content

S
spring-framework

爱吃血肠 / spring-framework

通知 1
Star 0
Fork 0
S
spring-framework

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 12 6月, 2019 1 次提交
  3. 23 5月, 2019 1 次提交
  5. 21 5月, 2019 1 次提交
  7. 07 5月, 2019 1 次提交
  9. 03 5月, 2019 1 次提交
  11. 17 4月, 2019 1 次提交
    • R
      LeakAwareDataBuffer related fixes · 375090bb
      由 Rossen Stoyanchev 提交于 
      Following on 3ebbfa21 where the local
refCount was removed in favor of using the internal refCount of the
native data buffer, this commit ensures that LeakAwareDataBufferFactory
uses a PooledDataBufferFactory delegate by default.

There are also fixes for test issues with eager allocation uncovered by
these changes in StringDecoder and ResourceDecoder.
      375090bb
  13. 11 4月, 2019 1 次提交
    • R
      Fix refCount issue in LeakAwareDataBuffer · 3ebbfa21
      由 Rossen Stoyanchev 提交于 
      LeakAwareDataBuffer was keeping its own refCount rather than checking
through the delegate. This leads to false leak reports in a sequence
where an allocated buffer is retained and then sliced since it is not
aware of the changes to the refCount through the slice.
      3ebbfa21
  15. 10 4月, 2019 1 次提交
  17. 09 4月, 2019 1 次提交
  19. 08 4月, 2019 1 次提交
  21. 04 4月, 2019 1 次提交
  23. 29 3月, 2019 1 次提交
    • R
      Uncomment buffer leak tests in DataBufferUtils · beae1fbb
      由 Rossen Stoyanchev 提交于 
      Following a response on
https://github.com/reactor/reactor-core/issues/1634 apparently
FluxSink is respecting doOnDiscard but there is a race condition
in DataBufferUtils with file reading.

This commit makes two changes:
1) Add more checks for onDispose to detect cancellation signals
as well as to deal with potentially concurrent such signal.
2) Do not close the channel through the Flux.using callback but
rather allow the current I/O callback to take place and only then
close the channel or else the buffer is left hanging.

Despite this tests still can fail due to a suspected issue in Reactor
itself with the doOnDiscard callback for FluxSink. That's tracked under
the same issue https://github.com/reactor/reactor-core/issues/1634
and for now the use of DefaultDataBufferFactory is enforced as a
workaround until the issue is resolved.

See gh-22107
      beae1fbb
  25. 28 3月, 2019 3 次提交
  27. 27 3月, 2019 1 次提交
    • R
      Buffer leak fixes · c5435578
      由 Rossen Stoyanchev 提交于 
      Address issues where buffers are allocated (and cached somehow) at or
before subscription, and before explicit demand.

The commit adds tests proving the leaks and fixes. The common thread
for all tests is a "zero demand" subscriber that subscribes  but does
not request, and then cancels without consuming anything.

Closes gh-22107
      c5435578
  29. 25 3月, 2019 1 次提交
  31. 23 3月, 2019 1 次提交
  33. 04 3月, 2019 1 次提交
    • A
      Fix repeated calls to DataBuffer.write(CharSequence, Charset) · 090aceb3
      由 Andrew Tulloch 提交于 
      Prior to this commit, repeated calls to `DataBuffer.write(CharSequence,
Charset)` would not write the given chars to the expected position in
the original buffer.

This commit fixes that by writing to the `outBuffer.position()`, offset
by the current `DataBuffer.writePosition()`.

Fixes gh-22484
      090aceb3
  35. 14 2月, 2019 1 次提交
  37. 12 2月, 2019 1 次提交
  39. 18 1月, 2019 1 次提交
    • B
      Fix error when writing empty String to DataBuffer · 2b65d0e5
      由 Brian Clozel 提交于 
      Prior to this commit, `DataBuffer.write` would throw an
`IllegalStateException` when called with an empty `String`, since the
`CharsetEncoder` would be flushed on an incorrent state.

This commit skips entirely the encoding phase for empty `String`.

Fixes #22262
      2b65d0e5
  41. 09 1月, 2019 2 次提交
  43. 25 12月, 2018 1 次提交
  45. 21 12月, 2018 3 次提交
    • A
      Add test for calculateCapacity · 5a8b8b11
      由 Arjen Poutsma 提交于 
      Issue: SPR-17558
Closes gh-2054
      5a8b8b11
    • B
      Use DataBuffer.write in CharSequenceEncoder · 4955d08f
      由 Brian Clozel 提交于 
      Since SPR-17558, `DataBuffer` now offers a new method to write Strings
to them. This commit makes `CharSequenceEncoder` use that.

Issue: SPR-17558
      4955d08f
    • B
      Write CharSequence instances to DataBuffers · 6361b0cb
      由 Brian Clozel 提交于 
      Prior to this commit, one could write a `CharSequence` to an existing
`DataBuffer` instance by turning it into a byte array or `ByteBuffer`
first. This had the following disadvantages:

1. Memory allocation was not efficient (not leveraging pooled memory
when available)
2. Dealing with `CharsetEncoder` is not always easy
3. `DataBuffer` implementations, like `NettyDataBuffer` can use
optimized implementations in some cases

This commit adds a new `DataBuffer#write(CharSequence, Charset)` method
for those cases and also an `ensureCapacity` method useful for checking
that the current buffer has enough capacity to write to it..

Issue: SPR-17558
      6361b0cb
  47. 13 12月, 2018 1 次提交
  49. 04 12月, 2018 1 次提交
  51. 24 11月, 2018 1 次提交
  53. 23 11月, 2018 1 次提交
  55. 21 11月, 2018 2 次提交
  57. 19 11月, 2018 3 次提交
  59. 16 11月, 2018 2 次提交
  61. 14 11月, 2018 1 次提交