75ad160559
[*] cascade errors here plox
2023-05-02 11:27:06 +01:00
fca5b90b85
[*] adjust tls coefficients
2023-04-30 14:46:36 +01:00
7c1a1566fd
[*] missing tls impersonation in bd94b73d
2023-04-30 09:05:14 +01:00
448d840e4c
[*] missing free in bd94b73d
2023-04-30 09:02:13 +01:00
bd94b73dde
[+] New TLSView implementation
...
[+] AuTLSVariable
2023-04-30 08:24:27 +01:00
37472e508e
[+] AuMemory::SharedByteBuffer
...
[+] AuMemory::ByteBuffer.flagNoFree
[*] SetBuffer(MemoryViewRead readView, bool bMoveWriteHeadForReaders = true);
...added bMoveWriteHeadForReaders
[-] AuMemory::SetBuffer(const void *in, AuUInt length)
[-] AuMemory::SetBuffer(const AuList<AuUInt8> &buffer)
[*] Harden AuMemory::ByteBuffer::RemainingBytes bc it is a high level api that is not called excessively. Invalid head states should not mess with ::CanRead/::CanWrite
[*] Harden AuMemory::ByteBuffer::RemainingWrite bc it is a high level api that is not called excessively. Invalid head states should not mess with ::CanRead/::CanWrite
2023-04-30 02:39:42 +01:00
e0d672ae9b
[+] ByteBuffer::SetBuffer(MemoryViewRead readView)
...
[*] revert 6317a563
2023-04-29 14:04:31 +01:00
c3a986495c
[*] AuByteBuffers should be able to .Write<std::string_view>()
2023-04-29 07:50:56 +01:00
6317a5631d
[*] update ResetPositions
2023-04-29 07:46:35 +01:00
e4e3e70be2
[*] sanitize these AuByteBuffer utilities to prevent exploitation
2023-04-29 07:38:16 +01:00
cc317882e9
[*] clamp head positions during non-circular realloc
2023-04-29 07:34:00 +01:00
6683d3cfdc
[+] IProtocolPiece.GetNextPiece
...
[+] IProtocolPiece.ReallocateDrainBuffer
[*] Harden protocol piece use after destroy
2023-04-29 07:00:29 +01:00
c787d85485
[*] bug: fix process time counters under win32
2023-04-29 05:26:53 +01:00
0175809d0a
[*] Compression pipe now returns false should an error occur
2023-04-29 03:10:08 +01:00
4086fc94bb
[*] bug fix: RNG strings werent deterministic
2023-04-28 04:59:09 +01:00
d791725438
[*] remove extra whiteline introduced in da69428d
2023-04-28 02:44:39 +01:00
da69428d7e
[+] IProtocolStack::PrependInterceptorEx
...
[+] IProtocolStack::PrependSingleFrameProcessor
[+] IProtocolStack::PrependSingleFrameProcessorEx
[+] IProtocolStack::GetArrayOfInterceptors
[+] IProtocolStack::GetInterceptorAtIndex
[+] IProtocolPiece::ToInputWriter
[+] IProtocolPiece::GetExtendedInterceptor
[+] IProtocolPiece::GetShortPipeInterceptor
2023-04-28 02:41:45 +01:00
f8219542c5
[*] precache socket network state errors here before the last transaction is released
2023-04-27 10:44:15 +01:00
eb4ee3143d
[*] bug: missing link
2023-04-27 10:26:41 +01:00
f1e9a7262b
[*] pipe processors with a stack attached to them should destroy the stack to forcefully break circular references in user code
2023-04-27 06:10:09 +01:00
f70d6392d9
[*] harden
2023-04-27 01:34:29 +01:00
efadd964be
[*] Improved disconnect reason reporting: HasErrorCode under the NT network async stream object
2023-04-26 20:32:25 +01:00
4b79aa902b
[*] i dont think this path should ever be hit, but just to be certain, lets check the networks output channel translation object for an error if the socketbase doesnt know of the last fatal error code
2023-04-26 20:22:11 +01:00
b8540c77a7
[*] improved network error reporting
2023-04-26 20:13:17 +01:00
044fb5b7e4
[*] added additional arg checks to ByteBuffers constructors
2023-04-26 07:43:56 +01:00
3f0368b99d
[*] cache these adapter allocations away
2023-04-26 07:37:14 +01:00
30b0c2e0ba
[*] Preemptive GetOverlappedResult fast-paths under WaitMultiple2 that rely on the alertable yield under next read/write cannot be trusted if the read count is zero.
...
Direct IO-specific quirk?
Windows 7 specific quirk?
Direct IO under Win7 specific quirk?
idk, but this fixes it
2023-04-26 07:25:45 +01:00
22c4d25759
[*] amend cdf5a499, bKillPipeOnFirstRootLevelFalse not respected
2023-04-25 12:57:15 +01:00
48fc0cdaed
[*] amend SysPanic2 to support 0 args
2023-04-25 12:23:22 +01:00
cdf5a499cb
[*] Improved pipe work awareness under protocol stack to allow for propagation of error conditions such that the top most interceptor can kill the pipe work
2023-04-25 12:13:16 +01:00
e0d7bbea01
[*] stream regression
2023-04-25 10:09:37 +01:00
664eb270dc
[+] IIOPipeWork::GetBytesProcessedInterframe
...
[*] IOPipeProcessors will now cap reported progression to the requested length if the requested page size would mean we overrun it.
2023-04-25 07:38:36 +01:00
f52175d7ce
[*] build error
2023-04-25 02:59:18 +01:00
36dee459ca
[*] TryLockRead was unware of RWRenterableLocks specifications
...
(not an issue for regular blocking lock paths)
2023-04-24 19:39:36 +01:00
8dcf857da5
[*] updated comments
2023-04-23 19:39:54 +01:00
f74a41e286
[*] Refactor our thread primitives for an SOO change, where the SOO[_t]-suffix is no longer required, resulting a new type conflict issue
2023-04-23 19:25:37 +01:00
5fd655b501
[*] further deprecate
2023-04-22 23:08:49 +01:00
772d08fee6
[*] amend 2a33d61e
2023-04-22 23:04:46 +01:00
2a33d61e63
[*] further deprecate high res clock
...
[*] further posix resolution reporting
2023-04-22 22:58:20 +01:00
945d54ef78
[*] i did a dumb
2023-04-22 22:38:37 +01:00
62c29d0600
[*] clock switcheroo
2023-04-21 22:35:33 +01:00
4d84e8f7f3
[+] AURORA_ASSERTIONS_FORCE_EXPRESSIONS
2023-04-21 22:21:28 +01:00
4d9d6ae474
[+] SysUnreachable
2023-04-21 22:09:01 +01:00
6d73dde240
[+] Thread + Process clocks
2023-04-21 22:08:56 +01:00
92af491fe8
[*] if (count == 1) *
2023-04-21 18:52:30 +01:00
4b0dfabd67
[*] Comments
2023-04-21 05:58:24 +01:00
36c163d90c
[*] 2af2eadf cont
2023-04-19 23:57:56 +01:00
d7d514c6b7
[*] protocol-stack ticks now check against the buffers error flags to ensure Writes/Reads weren't being silently dropped in user code
2023-04-19 23:46:56 +01:00
2af2eadfa8
[*] Resolve: protocol-stack link bug (multiple append failure / missing next link)
2023-04-19 23:35:48 +01:00
00129255f8
[*] changed this to be a soft-failure
2023-04-19 04:03:49 +01:00
