digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-11-05 03:56:26 +03:00
Code Issues Projects Releases Wiki Activity
0749e7c840
daml/sdk/.dadew

21 lines
373 B
Plaintext
Raw Normal View History

open-sourcing daml
2019-04-04 11:33:38 +03:00
{
"version": "0.0.8",
"manifests": "dev-env\\windows\\manifests",
"tools": [
add toxiproxy to Windows (for #6114) (#6119) I have never used Scoop before and I'm not sure how to actually test this, but I thought this might at least get a conversation going. Plus, if my reading of the documentation of both toxiproxy and Scoop is correct, this may even work as is. CHANGELOG_BEGIN CHANGELOG_END
2020-05-27 14:37:55 +03:00
"bazel",
"cacert",
Update curl 7.73.0 --> 7.78.0 (#10655) The download link for the old version 7.73.0 returns 404. changelog_begin changelog_end Co-authored-by: Andreas Herrmann <andreas.herrmann@tweag.io>
2021-08-24 16:45:27 +03:00
"curl",
infra: add a Windows node on Azure (#16705)
2023-04-20 15:32:25 +03:00
"gcloud",
Update to Java 11 (#11512) * Update to Java 11 changelog_begin changelog_end * Fix RoundingMode deprecation warnings * Fix dep-ann warning * Integer constructor * JavaX annotation dependency * javax.xml.bind was removed in Java 11 Using Guava as a replacement, since it is already a project dependency. * JDK 11 no longer has a separate JRE tree * Remove unused jdk_nix import * remove now redundant jdk11_nix * Java 8 --> 9 increased Instant.now() precision See https://bugs.openjdk.java.net/browse/JDK-8068730 The precision of `Instant.now()` increased between Java 8 and Java 9. On Linux and MacOS this doesn't seem to be a problem, as the precision still seems to be at micro seconds. However, on Windows this now causes errors of the following form: ``` java.lang.IllegalArgumentException: Conversion of Instant 2021-11-05T13:58:56.726875100Z to microsecond granularity would result in loss of precision. ``` Suggesting that it now offers sub-microsecond precision. `TimestampConversion.instantToMicros` had a check to fail if the conversion lead to a loss of precision. In the specific failing test case this is not a concern, so this adds a `roundInstantToMicros` variant that avoids this kind of error. * TMP round timestamps * Revert "TMP round timestamps" This reverts commit af8e26127880bf43fb91ab4592e223465af816da. * Skip versions before 1.6.0 in migration tests changelog_begin changelog_end Co-authored-by: Andreas Herrmann <andreas.herrmann@tweag.io>
2021-11-18 17:48:37 +03:00
"ojdkbuild11",
add toxiproxy to Windows (for #6114) (#6119) I have never used Scoop before and I'm not sure how to actually test this, but I thought this might at least get a conversation going. Plus, if my reading of the documentation of both toxiproxy and Scoop is correct, this may even work as is. CHANGELOG_BEGIN CHANGELOG_END
2020-05-27 14:37:55 +03:00
"maven-3.6.1",
windows: use msys2 provided patch - fixes: #916 (#942)
2019-05-10 13:41:11 +03:00
"msys2",
fix gsg on node 18 (#15373) CHANGELOG_BEGIN CHANGELOG_END
2022-11-28 13:52:47 +03:00
"nodejs-14",
"nodejs-16",
Fix SDK integration tests on Windows (#1125) * Fix SDK integration tests on Windows * Switch to Haskell-based tar extraction
2019-05-14 22:55:45 +03:00
"nsis-3.04",
add toxiproxy to Windows (for #6114) (#6119) I have never used Scoop before and I'm not sure how to actually test this, but I thought this might at least get a conversation going. Plus, if my reading of the documentation of both toxiproxy and Scoop is correct, this may even work as is. CHANGELOG_BEGIN CHANGELOG_END
2020-05-27 14:37:55 +03:00
"python-3.8.2",
"stack",
"toxiproxy",
Update VC redist to 14.28.29325.2 (#8431) changelog_begin changelog_end Co-authored-by: Andreas Herrmann <andreas.herrmann@tweag.io>
2021-01-07 19:31:25 +03:00
"vcredist"
open-sourcing daml
2019-04-04 11:33:38 +03:00
]
}
Reference in New Issue Copy Permalink