Skip to content
This repository has been archived by the owner on Nov 1, 2024. It is now read-only.

Releases: dart-archive/bazel_worker

package:bazel_worker v1.1.1

07 Mar 16:05
8619b92
Compare
Choose a tag to compare
  • Fix a bug where if spawnWorker threw an error, work requests would hang
    forever instead of failing.

bazel_worker version 1.1.0

31 Aug 18:07
f950bbf
Compare
Choose a tag to compare
  • Add constructors with named parameters to
    the generated worker protocol messages.
  • Include comments on the generated worker protocol API.

package:bazel_worker v1.0.3

16 Jun 15:43
f7b714e
Compare
Choose a tag to compare
  • Require package:protobuf >= 3.0.0.
  • Require Dart SDK >= 2.19.0

0.1.9

16 Jan 15:00
Compare
Choose a tag to compare

Update the worker_protocol.pb.dart file with the latest proto generator.

0.1.7

21 Nov 17:06
2ed92e7
Compare
Choose a tag to compare
  • Update the BazelWorkerDriver class to handle worker crashes, and retry work
    requests. The number of retries is configurable with the new int maxRetries
    optional arg to the BazelWorkerDriver constructor.

0.1.6

03 Nov 18:22
352ec46
Compare
Choose a tag to compare
  • Update the worker_protocol.pb.dart file with the latest proto generator.
  • Add support for package:async 2.x and package:protobuf 6.x.

0.1.5

03 Nov 17:18
Compare
Choose a tag to compare

Changes TestStdinAsync.controller to StreamController<List> (instead of using dynamic as the type argument).

0.1.4

26 Apr 20:45
Compare
Choose a tag to compare
  • Added BazelWorkerDriver class, which can be used to implement the bazel side
    of the protocol. This allows you to speak to any process which knows the bazel
    protocol from your own process.
  • Changed WorkerConnection#readRequest to return a FutureOr<WorkRequest>
    instead of dynamic.

0.1.3

20 Mar 17:30
Compare
Choose a tag to compare
  • Add automatic intercepting of print calls and append them to
    response.output. This makes more libraries work out of the box, as printing
    would previously cause an error due to communication over stdin/stdout.
    • Note that using stdin/stdout directly will still cause an error, but that is
      less common.

0.1.2

19 Jan 23:11
Compare
Choose a tag to compare

More robust error handling when reading from stdin