Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/mono.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-12-30Socket.BeginMConnect() should not attempt connections on unsupported address ↵Martin Baulig
families. (#18302) Fixes #16513.
2019-12-19[System] Add additional hardening against race in MonoTlsStream (#18250)Alexander Köplinger
See https://github.com/mono/mono/issues/15805#issuecomment-567131297
2019-12-11Make Socket.Socket_icall static, as most icalls are, removing the first, ↵Jay Krell
unused parameter. (#18130) Also partial undo recent and append _icall to end. This is verbose, but maybe worthwhile to aid search. This is extracted from https://github.com/mono/mono/pull/17978.
2019-12-11Sockets: Foo_internal to Foo_icall and ves_icall_Foo_internal to ↵Jay Krell
ves_icall_Foo. (#18017) The first is to avoid requiring the signature matching in icall resolution. The second is just to shorten names.
2019-12-09[wasm][bcl][websockets] Add WebSocket support. (#18062)Kenneth Pouncey
Add the ability to initialize a `WebAssembly.Net.WebSockets::ClientWebSocket` from `System.Net.WebSockets.ClientWebSocket`. `System.Net.WebSockets.ClientWebSocket` will delegate all calls to the WebAssembly ClientWebSocket. - Add support for marshaling `Uri` class correctly. This was a cause of failures. - Add bindings tests for `Uri` marhaling.
2019-12-04[Wasm] Enable system nunit tests on ci (#17716)Maxim Lipnin
* [wasm][nunit tests] Enable nunit tests for System on CI * [wasm][nunit tests] Exclude failing MonoTests.System.Net.Mail.SmtpClientTest tests * Fix test suit name * [wasm][nunit tests] Exclude MonoTests.System.Net.HttpListenerPrefixCollectionTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.HttpListenerTest nunit tests * [wasm][nunit tests] Exclude MonoTests.System.Net.NetworkInformation.NetworkInterfaceTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.Sockets.UdpClientTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.ComponentModel.PropertyDescriptorCollectionTests nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Collections.Specialized.NameValueCollectionTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Collections.Concurrent.ConcurrentBagTests nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.ComponentModel.BackgroundWorkerTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.NetworkInformation.IPInterfacePropertiesTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.ComponentModel.EventDescriptorCollectionTests nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.ComponentModel.AsyncOperationManagerTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.HttpListenerRequestTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.ServicePointTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.Sockets.TcpListenerTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.WebClientTestAsync nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.WebProxyTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.WebRequestTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Security.Cryptography.X509Certificates.X509Certificate2CollectionTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Timers.TimerTest nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Net.HttpListenerTest.PropertiesWhenClosedSet3 test * [wasm][nunit tests] Increase timeout for System nunit tests * [wasm][nunit tests] Exclude failing MonoTests.System.Security.Cryptography.X509Certificates.X509Certificate2CollectionTest.Find_FindByIssuerName test * [wasm][nunit tests] Remove PNSE expectation in MonoTests.System.Net.Mail.SmtpClientTest tests * [wasm][nunit tests] Remove PNSE expectation in MonoTests.System.Net.HttpListenerPrefixCollectionTest nunit tests * [wasm][nunit tests] Remove PNSE expectation in MonoTests.System.Net.HttpListenerTest nunit tests * Increase CI timeout for System.Core nunit tests * [wasm][nunit tests] Remove PNSE expectation in MonoTests.System.Net.Sockets.UdpClientTest nunit tests * [wasm][nunit tests] Update NetworkInterface class to throw PNSE * [wasm][nunit tests] Ignore failing MonoTests.System.ComponentModel.PropertyDescriptorCollectionTests nunit tests * [wasm][nunit tests] Ignore failing MonoTests.System.Collections.Specialized.NameValueCollectionTest nunit tests * [wasm][nunit tests] Adjust the use of Ignore attribute * [wasm][nunit tests] Categorize failing MonoTests.System.Collections.Concurrent.ConcurrentBagTests nunit tests * [wasm][nunit tests] Categorize failing MonoTests.System.ComponentModel.BackgroundWorkerTest nunit tests * [wasm][nunit tests] Categorize failing MonoTests.System.Net.NetworkInformation.IPInterfacePropertiesTest nunit tests * [wasm][nunit tests] Ignore failing MonoTests.System.Net.NetworkInformation.IPInterfacePropertiesTest nunit tests * [wasm][nunit tests] Remove the category for passing MonoTests.System.Net.HttpListenerRequestTest nunit tests * [wasm][nunit tests] Exclude failing part of MonoTests.System.Net.ServicePointTest.DnsRefreshTimeout test * [wasm][nunit tests] Remove PNSE expectation in failing MonoTests.System.Net.Sockets.TcpListenerTest nunit tests. * [wasm][nunit tests] Exclude failing MonoTests.System.Net.WebProxyTest nunit tests due to libc issue * [wasm][nunit tests] Remove PNSE expectation in MonoTests.System.Net.WebRequestTest.DefaultWebProxy test * [wasm][nunit tests] Exclude failing MonoTests.System.Security.Cryptography.X509Certificates.X509Certificate2CollectionTest nunit tests due to compare info issue
2019-12-02Disable ConnectFailAsync test on AIX (#17975)Calvin Buckley
Hangs runtime; prevents CI from completing run. (Another test can also hang the runtime, but is hard to reproduce and inconsistent about that.) This should be fixed eventually, but...
2019-11-19Fixes https://github.com/mono/mono/issues/15805 at least in terms of what ↵Steve Pfister
may be making it crash. (#17270) Adds a null check around the sslStream before trying to dispose.
2019-10-24Cleaning up SslStream, MobileAuthenticatedStream and TaskToApm. (#17393)Martin Baulig
### Overview After the removal of the Legacy TLS Provider, we can make some cleanups and improvements to the `SslStream` class. Since both the remaining providers use the internal `MobileAuthenticatedStream` and support Task-async code, we can get rid of some of the Begin/End async logic and the the underlying `Stream` class handle it instead. This also fixes a nasty issue with some of those task objects leaking unobserved exceptions. The problem was that `SslStream.Dispose()` needs to clear out all resources, but in doing so also nulls out the `Impl` handle to the `MobileAuthenticatedStream` - so a subsequent `End*()` call will not reach it's corresponding `TaskToApm.End()` method. There are also some cleanups in the internal APIs that were only ever used internally and not intended for public consumption. ### Mono.Security.dll * `Mono.Security.Interface`: removed internal `ICertificateValidator2` interface. * `Mono.Security.Interface.IMonoSslStream`: this internal interface is only used by the web-tests, which only use it as a way to get the `SslStream` instance, so all those `Begin/End` async methods are now gone. * `Mono.Security.Interface.IMonoSslStream2`: removed another internal interface. * `Mono.Security.Interface.MonoTlsProvider`: removed some `internal abstract` methods; these have been moved into a new `Mono.Net.Security.MobileTlsProvider` inside `System.dll`. ### System.dll * `Mono.Net.Security.MobileTlsProvider`: New abstract internal base class, which received the aforementioned abstract internal methods. The naming is such to make it consistent with the already existing `MobileTlsContext` and `MobileAuthenticatedStream`. Since both `AppleTlsProvider` and `BtlsProvider` now have an abstract internal base class inside `System.dll`, they can use the `ChainValidationHelper` class directly and we can also avoid some `Mono.Security` dances like for instance that `MonoSslPolicyErrors` enum. This will also help make the code easier to read and maintainer. * `Mono.AppleTls.AppleTlsProvider` and `Mono.Btls.MonoBtlsProvider`: change base class into `MobileTlsProvider` and reflect above mentioned overload changes. * `Mono.AppleTls.AppleCertificateHelper`: use `ChainValidationHelper` as well. * `Mono.Net.Security.ChainValidationHelper`: only implement `ICertificateValidator`. The `ICertificateValidator` interface is still required because it is in use by the web-tests, but the previous `ICertificateValidator2` was an internal dance. * `Mono.Net.Security.MobileAuthenticatedStream`: largely cleaned up this class. - we now implement the current slimmer version of `IMonoSslStream`. - moved all those overloads into `SslStream` that only fill in default values for some of their arguments and then call another overloaded version of their own. - removed lots of `Begin/End` methods that are not used anymore. * `Mono.Net.Security.MonoTlsProviderFactory`: use `MobileTlsStream` everywhere. * `Mono.Net.Security.MonoTlsStream`: cleanup `SslStream` creation logic; instead of going throw `provider.CreateSslStream()`, we can now use an internal constructor directly, thus avoiding the `IMonoSslStream` interface while also making the code a lot easier to read and understand. * `System.Net.Mail.SmtpClient`: same here. * `System.Net.HttpWebRequest`: use `MobileTlsProvider`. * `System.Net.Security.SslStream`: largely cleaned up this class. - we now use `MobileAuthenticatedStream` directly instead of the `IMonoSslStream` interface and therefore could also get rid of `IMonoSslStream2`. - cleanup constructor logic to allow the internal constructor being used with a `MobileTlsProvider` instead of going through `provider.CreateSslStream()`. - all those overloads that are only filling in default values for some of their arguments before calling another overloaded version of their own now live here instead of in the `MobileAuthenticatedStream` class. The reason is to simply that `MobileAuthenticatedStream` is already quite a complex and difficult class, and removing some of that complexity out of it will make it easier to understand. - handle the `TaskToApm.Begin()` / `TaskToApm.End()` here to ensure that we are not leaking any task objects with unobserved exceptions. - removed `BeginRead()` and `BeginWrite()` overloads to let the underlying `Stream` class handle these. * Bump API snapshot submodule * [csproj] Update project files
2019-10-19Remove the Legacy TLS Provider. (#17391)Martin Baulig
* `MonoTlsProviderFactory` now treats "legacy" as an alias for "default". * `Mono.Net.Security/LegacySslStream`: Removed. This class also wasn't using the `MobileAuthenticatedStream` base class, thus preventing cleanups simplifications in that area. * `Mono.Net.Security/LegacyTlsProvider`: Removed. * `Mono.Security/Mono.Security.Protocol.Tls*`: Removed all the old legacy code. * `Mono.Security.Interface.MonoTlsProviderFactory`: Bump internal version to 4.
2019-10-18Enable GSS on Linux and Android (#17223)Egor Bogatov
2019-10-16Removing execution of network tests from WatchOs. (#17358)Thays Grazia
2019-10-14[System.Net.Http] Clean up HttpMessageHandler setup (#17252)Marek Safar
* [System.Net.Http] Clean up HttpMessageHandler setup to avoid reflection and not to be recursive Superseded #15051 and #15922 * [csproj] Update project files
2019-10-11[tests] Bump corefx to get Azure testhost change (#17275)Alexander Köplinger
* Bump corefx to get Azure testhost change See https://github.com/mono/corefx/pull/360 * Update ClientWebSocketTest as well
2019-10-01[wasm][xunit test] Exclude RemoteExecutorTests in bcl profile (#17120)Maxim Lipnin
`System/RemoteExecutorTests.cs` tests are excluded in the mobile test profiles. It makes sense to do the same for wasm. Fixes https://github.com/mono/mono/issues/17038.
2019-09-26 BeginConnect complete to early when not using callback. (#17035)Johan Lorensson
* BeginConnect complete to early when not using callback. The following commit, https://github.com/mono/mono/commit/068e8fe0424806753d7ab72a7b9bf0e54b58408b#diff-33b28a9dc0b8032650ed77213481a99f changed the way we do DNS resolve in BeginConnect using host name. Instead of doing a blocking DNS resolve, it switched to an async DNS resolve, followed by an async connect. The returned IAsyncResult was just representing the completion of the DNS resolve task and not the underlying connect. It also turns out that part of doing EndConnect, we did some validation of the used IAsyncResult making sure it was an instance of SocketAsyncResult, meaning that if EndConnect was called on the returned IAsyncResult from BeginConnect, EndConnect would throw and exception. NOTE, this only happens if you use pattern like this: var result = sock.BeginConnect (hostName, port, null, null); result.AsyncWaitHandle.WaitOne (2000); sock.EndConnect (result); It did not happened if you used callbacks, since then EndConnect would be called as part of callback and that IAsyncResult was of correct type, or if you did a BeginConnect with an EndPoint or IPAddress[] since that won't trigger the DNS resolve. Fix is to make sure we hand out the SocketAsyncResult instance that will be used in our internal connect calls from BeginConnect. We also make sure, we chain the DNS resolve task together with a task doing the async connect (using the same SocketAsyncResult instance). This will make sure the IAsyncResult returned from BeginConnect is the same one as used in internal connect call, so it will only complete when the connect call completes. * Adding test for BeginConnect using host name. * Bump API snapshot submodule
2019-09-25Update System.csprojAlexander Köplinger
2019-09-24Add RenamedEvent* to FSW sources from CoreFX (#16755)Marius Ungureanu
* Add RenamedEvent* to FSW sources from CoreFX Fixes #16486 - This was only partially fixed until now * [csproj] Update project files * Add test files which test these code paths on corefx * Remove old RenamedEvent* files
2019-09-20[System] Make FileSystemWatcher backend non-static (#16922)Aleksey Kliger (λgeek)
* [System] Make FileSystemWatcher backend non-static The FileSystemWatcher `watcher` field is the backend IFileWatcher that's supposed to be used for the actual operations. Each backend has a `bool GetInstance (out watcher)` method that returns a singleton object, so each new instance of FileSystemWatcher gets the same IFileWatcher instance. (They will get different `watcher_handle` instances which are used by some backends to uniquely identify this FileSystemWatcher). However when the first FileSystemWatcher instance is `Dispose`d, it will set `watcher = null` which will prevent the remaining instances from calling watcher?.StopDispatching (watcher_handle); watcher?.Dispose (watcher_handle); which means that the backend won't properly cleanup resources for any other FSW instances that have other `watcher_handle` values. Addresses https://github.com/mono/mono/issues/16709
2019-09-20Implement WriteCore and ReadCore in DeflateStream (#16951)Egor Bogatov
No idea why these were left unimplemented (probably were not used at that point). Fixes #16950
2019-09-19Use `NetworkStream` from CoreFX. (#16889)Martin Baulig
* Use `NetworkStream` from CoreFX. This brings the `NetworkStream` class and related tests from CoreFX. * `SocketAsyncEventArgs`: partially replace the following properties with the CoreFX version: `Buffer`, `BufferList`, `Offset`, `SetBuffer ()` as well as the internal `CopyBufferFrom ()`. * `SocketAsyncResult`: change `Buffer` from `byte[]` to `Memory<byte>`. * Add internal `Socket` overloads: - `Receive (Memory<byte> buffer, int, int, SocketFlags, out SocketError)` - `ReceiveFrom (Memory<byte>, int, int, SocketFlags, ref EndPoint, out SocketError)` - `SendTo (Memory<byte>, int, int, SocketFlags, EndPoint)` * Implement async task overloads from CoreFX (`Socket.Tasks.cs`) to `Socket`: - `int Read(Span<byte>)` - `Task<int> ReadAsync(byte[], int, int, CancellationToken)` - `ValueTask<int> ReadAsync(Memory<byte>, CancellationToken)` - `int ReadByte()` - `void Write(ReadOnlySpan<byte>)` - `Task WriteAsync(byte[], int, int, CancellationToken)` - `ValueTask WriteAsync(ReadOnlyMemory<byte>, CancellationToken)` - `void WriteByte(byte)` * remove internal unused `PooledStream` and `ConnectionPool` APIs. * bring new tests from CoreFX: - `System.Net.Sockets/tests/FunctionalTests/NetworkStreamTest.cs` - `System.Net.Sockets/tests/FunctionalTests/NetworkStreamTest.netcoreapp.cs` * corlib: add `System.IO.FileSystem` and `System.Net.Sockets` resources and update SR. * Update Socket.cs * [csproj] Update project files * Bump API snapshot submodule
2019-09-19[wasm] Switch to PNSE version of FileSystemWatcher and exclude xunit tests ↵Maxim Lipnin
(#16892) Fixes https://github.com/mono/mono/issues/16876
2019-09-17Exclude AppleTypes from orbis System.dll. (#16814)Johan Lorensson
* Exclude AppleTypes from orbis System.dll. * [csproj] Update project files
2019-09-10[wasm] test cleanup (#15727)Larry Ewing
* [wasm] stop excluding test_0_large_nullable_invoke on wasm * [wasm] remove wasm exclusion from test_0_simple_double_casts * Add category MultiThreaded to more of the concurrent collection tests * Add more MultiThreaded annotations to HttpListener2Test * Add category MultiThreaded to HttpWebRequestTest * [wasm] flag more tests that are taking down the runtime * [wasm] force sockets to throw PNSE in the ctor for now * [wasm] enable corlib interpreter tests * [wasm] Increase timeout for corlib tests * try to fix wasm-cross-win-release-configure on macos
2019-08-29Use the right FileSystemWatcher sources (#16539)Marius Ungureanu
* Use the right FileSystemWatcher sources The corefx code for FileSystemEventArgs has some changes to support constructing one with a null filename. Fixes #16486 * Remove the mono sources for the newly replaced files * [csproj] Update project files
2019-08-28Implement Read and WriteAsyncMemory in Mono DeflateStreamSteve Pfister
Resolves https://github.com/mono/mono/issues/16122 Since we put in the corefx version of GZipStream, it is expected that our version of DeflateStream actually implements Write+ReadAsyncMemory. This change does that by just calling the plain WriteAsync & ReadAsync methods until we decide (or not) to pull in the corefx DeflateStream.
2019-08-19Add missing `Dispose()` call on error in `MonoTlsStream.CreateStream()`. ↵Martin Baulig
(#16233) * Add missing `Dispose()` call on error in `MonoTlsStream.CreateStream()`. * Remove the `finally` block to make it more easy to read.
2019-08-16Exclude Authenticode tests on Watch (#16278)Jo Shields
1002a4de2b0d added Authenticode cert support on non-WatchOS. The tests, however, were not non-WatchOS-only. Fix this, so Watch doesn't try to run Authenticode tests.
2019-08-15X509CertificateImplBtls.PrivateKey should allow to actually set the key. ↵Martin Baulig
(#16212) The `X509CertificateImplBtls.PrivateKey` property setter was previously ignoring all values and always used `null`. This should help with #16189.
2019-08-07Swap bytes for tcp port number because windows API gives us port in network ↵Alex Thibodeau
order. (#16030) Addresses the FIXME in Win32IPGlobalProperties.cs :: FillTcpTable Fixed Unity issue: issuetracker.unity3d.com/issues/ipglobalproperties-dot-getactivetcpconnections-return-different-port-numbers-when-compared-to-cli-netstat-a-output
2019-08-06DeflateStream: check IsInvalid before disposing (#16048)Egor Bogatov
2019-08-06`SocketAsyncEventArgs` cleanups and preparations for the real thing. (#16001)Martin Baulig
Cleaning up the `SocketAsyncEventArgs` class and preparing it for it's eventual adaption from CoreFX. There are a few instance fields and property accessors with `internal` visibility, which the CoreFX version does not have. Replaced these with accessor methods. The `PolicyRestricted` property and it's related `SocketAsyncEventArgs (bool)` constructor is not used anywhere and the CoreFX version has a constructor with the same signature, but different semantics. In the CoreFX version, `Complete ()` does not call `DoComplete (this)` - renamed it into `Complete_internal ()` to avoid any ambiguities and help the transitioning.
2019-08-05Add finalizer to DeflateStream (#15879)Egor Bogatov
Fixes #15825
2019-08-02Use `MultipleConnectAsync` from CoreFX. (#15972)Martin Baulig
* Use `MultipleConnectAsync` from CoreFX. * [csproj] Update project files
2019-08-02Fix compiler warnings in System.dll. (#15971)Martin Baulig
* Merge the `System.Diagnostics/ProcessStartInfo.cs` part into the referencesource file to avoid CS0282. * Remove duplicate `using`. * Fix unreachable code warning that got introduced in my last PR.
2019-08-01Fix `Socket.ConnectAsync(SocketAsyncEventArgs)` behavior. (#15947)Martin Baulig
We need to clearly distinguish between synchronous and asynchronous completions and avoid any ambiguities and race conditions when it comes to error handling. On synchronous completion, we must not invoke the async completion delegate. In `System.Net.Sockets/Socket.cs`, the internal `BeginSConnect()` and `BeginMConnect()` now return a `bool` indicating whether or not an async operation is pending. If any error happens prior to starting the async operation, then we shall call `SocketAsyncResult.Complete(..., true)` and return `false`. And since this is a synchronous completion, it's `AsyncCallback` will not be invoked. In `referencesource/System/net/System/Net/Sockets/_MultipleConnectAsync.cs`, I compared the entire file against the CoreFX version and then copied the `AttemptConnection()` method from their implementation to adapt their behavior. The difference is that on synchronous completion, the `InternalConnectCallback(null, args)` should be invoked.
2019-07-26[wasm] Remove assemblies we don't want to distributeMarek Safar
2019-07-24[Coop] Convert System.Diagnostics.{FileVersionInfo,Process}. (#15789)Jay Krell
2019-07-15[System] Keep events from firing from a disposed 'DefaultWatcher' ↵Alexis Christoforides
FileSystemWatcher Fixes https://github.com/mono/mono/issues/8747 Also try to stop other implementations from dispatching events past Dispose(), without guaranteeing it
2019-07-15[System] Remove FileSystemWatcher tests from monotouch/xammacAlexander Köplinger
They were already excluded from watch and tv but they don't work on any mobile Apple profile.
2019-07-11[Mono.Security] Allow importing certificates from authenticode assemblies ↵Micah N Gorrell
(#14210) This change allows a number of games, such as DARK, to start successfully. The games use X509Certificate.CreateFromSignedFile() to load the certificate from their assemblies in order to verify them. * Added support for creating an AuthenticodeDeformatter for an assembly that has been loaded into memory * Allow importing a certificate from an assembly signed with authenticode when using BTLS * Allow importing a certificate from an assembly signed with authenticode when not using BTLS * Added a test for loading certificates from assemblies signed with authenticode
2019-07-11Add TypeForwards for FileSystemName & CryptographicOperations (#15652)Steve Pfister
* Add TypeForwards for: * System.IO.Enumeration.FileSystemName * System.Security.Cryptography.CryptographicOperations Since these were removed in NS 2.1 * Bump API snapshot submodule
2019-07-09[System]: Allow reading fully buffered `HttpWebResponse` body… (#15220)Martin Baulig
[System]: Allow reading fully buffered `HttpWebResponse` body after close. If we have already read the entire response body, then we should allow the user to read it even after the request has been aborted. * `WebConnectionStream.Read ()`: Move `Operation.ThrowIfClosedOrDisposed ()` call down after argument checks and call a new protected abstract method called `TryReadFromBufferedContent ()` prior to it. * `WebResponseStream.TryReadFromBufferedContent ()`: Implement it here. If the entire response body has been buffered, then `bufferedEntireContent` is true and `innerStream is BufferedReadStream` and we can call the new `BufferedReadStream.TryReadFromBuffer ()`. * `WebResponseStream.ReadAllAsync ()`: Set `bufferedEntireContent = true` after reading the entire response body. * `BufferedReadStream.TryReadFromBuffer ()`: New internal method. Fixes #10645.
2019-06-25[System] Fix monotouch_watch xunit tests buildAlexander Köplinger
Forgot to exclude one more file.
2019-06-25Exclude a few tests on monotouch_watch/xammac (#15397)Alexander Köplinger
* [System.Core] Exclude AnonymousPipe tests on monotouch/xammac profiles They should only be run on xammac_net_4_5. Fixes https://github.com/mono/mono/issues/15329 * [System] Exclude WebClient and WebSocket tests on monotouch_watch Fixes https://github.com/mono/mono/issues/15265.
2019-06-20Add Windows x64 Full AOT Interpreter support on CI. (#15127)Johan Lorensson
Add support to run full interpreter test suite on CI for Windows x64 Full AOT. Since Windows x64 Full AOT uses a different full AOT profile WinAOT a separate testing profile was setup for the interpreter testing. NOTE, this profile is pure for testing, inline with the other testing profiles. It is also reusing most of its sources from other sources files (mainly WinAOT) to reduce maintenance of the profile. Commit also includes some smaller adjustments needed in order to get full pass rate for Windows x64 Full AOT + Interpreter on CI.
2019-06-19[filewatcher] Fall back to default if a new instance cannot be createdAlexis Christoforides
2019-06-07Implement RSACertificateExtensions.CopyWithPrivateKey(). #14152. (#14860)Martin Baulig
* Implement RSACertificateExtensions.CopyWithPrivateKey(). #14152. * RSACertificateExtensions.CopyWithPrivateKey(): implement. Since `RSACertificateExtensions` lives in `System.Core` and only `mscorlib` internals (but not `System` internals) are visible to it, we need to use a little trick here: * System.Security.Cryptography.X509Certificates.X509CertificateImpl: add new abstract methods CopyWithPrivateKey() and CreateCertificate(). * System.Security.Cryptography.X509Certificates.X509Certificate2Impl: sealed implement them here. The `httpcfg` tool, only checks whether the key is valid, so we don't really need to call `CopyWithPrivateKey()` (which requires us to take a dependency on `System.Core`). * Do the same thing in HttpListener.
2019-06-06[wasm][bcl] Use zlib for DeflateStream on WASM profile (#14308)Kenneth Pouncey
* [wasm][bcl] Use zlib for DeflateStream on WASM profile - Add `-s USE-ZLIB=1` flag for the emscripten build of `mono.js` - Add new `zlib-helper` module build that is included in the `mono` wasm build. - This adds roughly 300 kb to the size. * Add zlib calls to `icall` for `WASM` profile * Address comments use `TARGET_WASM` instead of `HOST_WASM` * Hack around JS exception: RuntimeError: indirect call signature mismatch - Instead of using the function pointer from DeflateStream (Marshal.GetFunctionPointerForDelegate) obtain the callback functions from the object itself. * Update error messages and add exception parameter to `mono_runtime_invoke`. * Add `mono/support` zlib include sources files to make `package` target. * Add `zlib-helper` build to packager. - Note: Right now only supports zlib build from mono tree build. - Add `zlibtest.cs` scenario to compress and uncompress using DeflateStream and GZip. - Add test to make file to build and run aot version of ziplibtest. * Add copy of zlib header support files to `package-wasm-runtime` - The support library is not built for wasm but the zlib include files are needed to build support during wasm build. - See mono.js build and the use of the `-s USE_ZLIB=1` flag. - The include files will be used in packager.exe to build zlib support for wasm. * Use the zlib includes from support to build the zlib support. * Setup base tests for testing System.IO.Compression integration * Formatting * Add more ziparchive tests * Formatting and indentation * Add more Zip tests * Add more tests. - Add more tests for ZipArchive. - Add tests for Deflate - small, large and very large strings. - Add tests for GZipStream - small, large and very large strings. * Fix merge of EMCC_FLAGS * Add new option to packager to enable the use of zlib - --enable-zlib (enable the use of zlib for System.IO.Compression support) type: bool default: false - update packager doc * Address review comments - Change `enable-zlib` to `zlib`
2019-05-29[bcl] Add nunit exclude categories for monotouch/monodroid profiles (#14695)Alexander Köplinger
We didn't set all the categories that the products used in our profiles. Now that the products can consume the exclude categories from mono we need to unify the values. Removed ValueAdd since it's not used anymore and combined MacNotWorking into NotOnMac.