commit | 931ec382d40f67e89788fa97d6be37fc55084fb7 | [log] [tgz] |
---|---|---|
author | Martin Kustermann <kustermann@google.com> | Wed Jun 25 02:56:21 2025 -0700 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jun 25 02:56:21 2025 -0700 |
tree | c5791679d0365c56532d5ac4bf9a2ec941d30dc7 | |
parent | fecf1b0750ce8767e05d7d817dd923e8013bda8a [diff] |
[io/gardening] Fix client address binding & fix standalone/io/socket_local_port_test Various changes to the stanalone/io/socket_local_port_test: * Make server ports ephemeral: The test is testing client-side binding of address & port, the server part can use ephemeral ports. => This eliminates the issue of another process using the hard-coded port * Close sockets normally instead of using `Socket.destroy()` * Make dead code alive: There were test in the tests that were not invoked by `main()`. * Align the individual test helper functions. * ... Then we change the dart:io implementation of `Socket::CreateBindConnect` to set the `SO_REUSEADDR` socket option. We do this already for the server side in `Socket::CreateBindListen`, now we do it also for the client side. => This will ensure that one can bind the client side socket to specific address/source despite there being an old closed socket that's now in `TIME_WAIT` state. => This is the same reason we also do it in `Socket::CreateBindListen`. Fuchsia doesn't implement `Socket::CreateBindConnect` and on Windows the socket option seemingly has different semantics (we also don't use `SO_REUSEADDR` on windows for the server socket, but another option). Issue https://github.com/dart-lang/sdk/issues/51477 TEST=standalone/io/socket_local_port_test Change-Id: I7d07becad0cd98c3a9b973ef2f9037730d3f8b19 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/436902 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Slava Egorov <vegorov@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.