digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-11-10 10:46:11 +03:00
Code Issues Projects Releases Wiki Activity
2d5094160e
daml/compiler/scenario-service/server/BUILD.bazel

48 lines
1.6 KiB
Python
Raw Normal View History

update copyright headers (#12240) New year, new copyright, new expected unknown issues with various files that won't be covered by the script and/or will be but shouldn't change. I'll do the details on Jan 1, but would appreciate this being preapproved so I can actually get it merged by then. CHANGELOG_BEGIN CHANGELOG_END
2022-01-03 19:36:51 +03:00
# Copyright (c) 2022 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
open-sourcing daml
2019-04-04 11:33:38 +03:00
# SPDX-License-Identifier: Apache-2.0
Replace silencer plugin with built-in warning configuration (#12543) Since Scala 2.13.2, Scala introduced built-in support to manage warnings in a more granular fashion, thus making the silencer plugin we are currently using no longer strictly useful. Removing compiler plugins also removes friction from migrating to Scala 3 in the future. As a cherry on top, the built-in warning configuration also allows to check whether a `@nowarn` actually does anything, allowing us to proactively remove unused warnings should the need arise. [Here][1] is s a blog post by the Scala team about it. Warnings have been either solved or preserved if useful, trying to minimize the scope (keeping it at the single expression scope if possible). In particular, all remaining usages of the Scala Collection API compatibility module have been removed. Using the silencer plugin also apparently hid a few remaining usages of compatibility libraries that were used as part of the transition from Scala 2.12 to Scala 2.13 that are no longer needed. Removing those warnings highlighted those. changelog_begin changelog_end [1]: https://www.scala-lang.org/2021/01/12/configuring-and-suppressing-warnings.html
2022-01-24 18:01:35 +03:00
load("//bazel_tools:scala.bzl", "da_scala_binary")
open-sourcing daml
2019-04-04 11:33:38 +03:00
genrule(
Enforce consistent formatting of BUILD files. (#412) * Add buildifier targets. The tool allows to check and format BUILD files in the repo. To check if files are well formatted, run: bazel run //:buildifier To fix badly-formatted files run: bazel run //:buildifier-fix * Cleanup dade-copyright-headers formatting. * Fix dade-copyright-headers on files with just the copyright. * Run buildifier automatically on CI via 'fmt.sh'. * Reformat all BUILD files with buildifier. Excludes autogenerated Bazel files.
2019-04-12 14:10:16 +03:00
name = "scenario_service_jar",
srcs = [":scenario-service-raw_deploy.jar"],
outs = ["scenario-service.jar"],
cmd = "cp $< $@",
visibility = ["//visibility:public"],
open-sourcing daml
2019-04-04 11:33:38 +03:00
)
da_scala_binary(
Enforce consistent formatting of BUILD files. (#412) * Add buildifier targets. The tool allows to check and format BUILD files in the repo. To check if files are well formatted, run: bazel run //:buildifier To fix badly-formatted files run: bazel run //:buildifier-fix * Cleanup dade-copyright-headers formatting. * Fix dade-copyright-headers on files with just the copyright. * Run buildifier automatically on CI via 'fmt.sh'. * Reformat all BUILD files with buildifier. Excludes autogenerated Bazel files.
2019-04-12 14:10:16 +03:00
name = "scenario-service-raw",
srcs = glob(["src/main/scala/**/*.scala"]),
Use com.daml as root package (#5343) Packages com.digitalasset.daml and com.daml have been unified under com.daml Ledger API and DAML-LF DEV protos have also been moved from `com/digitalasset` to `com/daml` on the file system. Protos for already released DAML LF versions (1.6, 1.7, 1.8) stay in the package `com.digitalasset`. CHANGELOG_BEGIN [SDK] All Java and Scala packages starting with ``com.digitalasset.daml`` and ``com.digitalasset`` are now consolidated under ``com.daml``. Simply changing imports should be enough to migrate your code. CHANGELOG_END
2020-04-05 20:49:57 +03:00
main_class = "com.daml.lf.scenario.ScenarioServiceMain",
Preload packages to engine during upload (#2860) * Preload packages to engine during upload * Improve logging in KeyValueCommitting and add timing information * Fix scenario service tests now that logging is done in interpreter
2019-09-13 15:31:52 +03:00
resources = glob(["src/main/resources/*"]),
Port damlc dependencies to Scala 2.13 (#8423) * Port damlc dependencies to Scala 2.13 I got a bit fed up by the fact that going directory by directory didn’t really work since there are two many interdependencies in tests (e.g., client tests depend on sandbox, sandbox tests depend on clients, engine tests depend on DARs which depend on damlc, …). So before attempting to continue with the per-directory process, this is a bruteforce approach to break a lot of those cycles by porting all dependencies of damlc which includes client bindings (for DAML Script) and Sandbox Classic (also for DAML Script). If this is too annoying to review let me know and I’ll try to split it up into a few chunks. changelog_begin changelog_end * Update daml-lf/data/src/main/2.13/com/daml/lf/data/LawlessTraversals.scala Co-authored-by: Stephen Compall <stephen.compall@daml.com> * fixup lawlesstraversal changelog_begin changelog_end * less iterator more view changelog_begin changelog_end * document safety of unsafeWrapArray changelog_begin changelog_end Co-authored-by: Stephen Compall <stephen.compall@daml.com>
2021-01-08 09:22:38 +03:00
scala_deps = [
"@maven//:com_typesafe_scala_logging_scala_logging",
"@maven//:org_scalaz_scalaz_core",
Drop scenarios from the user-facing SDK (#12128) * Add --enable-scenarios hidden flag * Fail LFConversion when a scenario is defined and --enable-scenarios=no * Remove unused optIsGenerated=True test cases * Refactor getIntegrationTests * Add no-scenarios-enabled tests * Add enable-scenarios flag to scenario-service server * Add test ensuring that scenario-returning functions are still allowed * Remove 'enable scripts' option (--daml-script) * Add --scripts synonym to --scenarios * Rephrase scenarios flags descriptions changelog_begin changelog_end
2021-12-15 15:39:14 +03:00
"@maven//:com_github_scopt_scopt",
Port damlc dependencies to Scala 2.13 (#8423) * Port damlc dependencies to Scala 2.13 I got a bit fed up by the fact that going directory by directory didn’t really work since there are two many interdependencies in tests (e.g., client tests depend on sandbox, sandbox tests depend on clients, engine tests depend on DARs which depend on damlc, …). So before attempting to continue with the per-directory process, this is a bruteforce approach to break a lot of those cycles by porting all dependencies of damlc which includes client bindings (for DAML Script) and Sandbox Classic (also for DAML Script). If this is too annoying to review let me know and I’ll try to split it up into a few chunks. changelog_begin changelog_end * Update daml-lf/data/src/main/2.13/com/daml/lf/data/LawlessTraversals.scala Co-authored-by: Stephen Compall <stephen.compall@daml.com> * fixup lawlesstraversal changelog_begin changelog_end * less iterator more view changelog_begin changelog_end * document safety of unsafeWrapArray changelog_begin changelog_end Co-authored-by: Stephen Compall <stephen.compall@daml.com>
2021-01-08 09:22:38 +03:00
],
Remove unused dependencies to da_scala_binary (#3937) * Inline all scala_binary dependencies * Run //:buildifier-fix * da_scala_binary: Enable unused dependency checker * //compiler/scenario-service/server:scenario-service-raw * //language-support/scala/codegen:codegen-main * //daml-lf/encoder:encoder_binary * //daml-lf/repl:repl * //language-support/codegen-main:codegen-main * //language-support/scala/examples:quickstart-scala-bin * //ledger-api/rs-grpc-akka:rs-grpc-akka-perf * //ledger-service/jwt:jwt-bin * //ledger/api-server-damlonx/reference-v2:reference-v2 * //ledger/api-server-damlonx/reference-v2:ephemeral-postgres-reference-server * //ledger/ledger-api-auth:ledger-api-auth-bin * //ledger/ledger-api-test-tool:ledger-api-test-tool * //ledger/participant-state/kvutils/tools:integrity-check * //navigator/integration-test:navigatortest-jar * Run //:buildifier-fix Co-authored-by: Andreas Herrmann <andreash87@gmx.ch>
2020-01-06 15:58:56 +03:00
runtime_deps = [
"@maven//:ch_qos_logback_logback_classic",
],
Enforce consistent formatting of BUILD files. (#412) * Add buildifier targets. The tool allows to check and format BUILD files in the repo. To check if files are well formatted, run: bazel run //:buildifier To fix badly-formatted files run: bazel run //:buildifier-fix * Cleanup dade-copyright-headers formatting. * Fix dade-copyright-headers on files with just the copyright. * Run buildifier automatically on CI via 'fmt.sh'. * Reformat all BUILD files with buildifier. Excludes autogenerated Bazel files.
2019-04-12 14:10:16 +03:00
deps = [
"//compiler/scenario-service/protos:scenario_service_java_proto",
daml-lf: rename daml_lf_archive_scala target to daml_lf_archive_reader (#3168) * daml-lf: rename daml_lf_archive_scala target to daml_lf_archive_reader * fix release
2019-10-14 17:53:50 +03:00
"//daml-lf/archive:daml_lf_archive_reader",
Enforce consistent formatting of BUILD files. (#412) * Add buildifier targets. The tool allows to check and format BUILD files in the repo. To check if files are well formatted, run: bazel run //:buildifier To fix badly-formatted files run: bazel run //:buildifier-fix * Cleanup dade-copyright-headers formatting. * Fix dade-copyright-headers on files with just the copyright. * Run buildifier automatically on CI via 'fmt.sh'. * Reformat all BUILD files with buildifier. Excludes autogenerated Bazel files.
2019-04-12 14:10:16 +03:00
"//daml-lf/data",
"//daml-lf/interpreter",
cleanup daml-lf scala packages (#1581) * cleanup daml-lf scala packages * Address Stephen's Comments * update maven coordinates of language package
2019-06-12 18:55:48 +03:00
"//daml-lf/language",
Enforce consistent formatting of BUILD files. (#412) * Add buildifier targets. The tool allows to check and format BUILD files in the repo. To check if files are well formatted, run: bazel run //:buildifier To fix badly-formatted files run: bazel run //:buildifier-fix * Cleanup dade-copyright-headers formatting. * Fix dade-copyright-headers on files with just the copyright. * Run buildifier automatically on CI via 'fmt.sh'. * Reformat all BUILD files with buildifier. Excludes autogenerated Bazel files.
2019-04-12 14:10:16 +03:00
"//daml-lf/scenario-interpreter",
"//daml-lf/transaction",
"//daml-lf/validation",
Extend the scenario service with DAML Script support (#6929) * Extend the scenario service with DAML Script support This adds most of the infrastructure for running DAML Script via the scenario service which means it runs as part of DAML Studio and `daml test`. This is hidden behind a feature flag so we can land this and parallelize the remaining tasks. The main things that are missing are: 1. `createAndExerciseCmd` and `exerciseByKeyCmd`. 2. Party management needs some work and listing parties is unsupported. 3. Time management 4. Potentially some better error handling (we need to go through SResult and SError and see what is relevant for us). Overall, it is already in a very usable state and there is a decent range of tests. closes #3688 changelog_begin changelog_end * Update compiler/damlc/daml-ide-core/src/Development/IDE/Core/Rules/Daml.hs Co-authored-by: Andreas Herrmann <42969706+aherrmann-da@users.noreply.github.com> * Fix name for actor system and pool changelog_begin changelog_end Co-authored-by: Andreas Herrmann <42969706+aherrmann-da@users.noreply.github.com>
2020-08-05 13:56:09 +03:00
"//daml-script/runner:script-runner-lib",
"//language-support/scala/bindings",
"//language-support/scala/bindings-akka",
"//ledger-api/rs-grpc-bridge",
LF: Add LoggingContext to Speedy Machine (#12976) This advances the state of #12208 CHANGELOG_BEGIN CHANGELOG_END
2022-02-21 15:34:46 +03:00
"//libs-scala/contextualized-logging",
Replace bazel-deps by rules_jvm_external (#3253) * Update bazel-common to fix javadoc issues Specifically, to fix the following error ``` ERROR: /home/aj/tweag.io/da/da-bazel-1.1/ledger-api/rs-grpc-bridge/BUILD.bazel:7:1: in javadoc_library rule //ledger-api/rs-grpc-bridge:rs-grpc-bridge_javadoc: Traceback (most recent call last): File "/home/aj/tweag.io/da/da-bazel-1.1/ledger-api/rs-grpc-bridge/BUILD.bazel", line 7 javadoc_library(name = 'rs-grpc-bridge_javadoc') File "/home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/com_github_google_bazel_common/tools/javadoc/javadoc.bzl", line 27, in _javadoc_library dep.java.transitive_deps object of type 'JavaSkylarkApiProvider' has no field 'transitive_deps' ``` * Define Maven deps using rules_jvm_external * Pin artifacts * Remove bazel-deps generated targets * Remove bazel-deps * Switch to rules_jvm_external targets * update bazel documentation * pom_file: There are no more bazel-deps targets * BAZEL-JVM.md `maven_install` typo
2019-10-28 15:53:14 +03:00
"@maven//:com_google_protobuf_protobuf_java",
"@maven//:io_grpc_grpc_api",
bind localhost for json-api and scenarios (#4576) Both were previously binding 0.0.0.0, which is inherently insecure. More importantly to me, that meant running `bazel test //...` essentially rendered my computer unusable for however long it took (which is _long_), as it kept popping up focus-stealing dialogs about whether or not I wanted to trust "java" to open an incoming network connection. The ScenarioService does not seem to have an existing setup for CLI args and my Scala-fu is not good enough to add one, so I just changed the hard-coded path. The JSON API already had an option, just with the wrong default. This is technically a breaking change, but I'm hoping to pass it under the "experimental" flag we still have on the JSON API. CHANGELOG_BEGIN - [JSON API - Experimental] As a security improvement, the JSON API server will now bind on ``127.0.0.1`` by default. Previous behaviour was to bind on ``0.0.0.0``; you can get that behaviour back by passing in the (existing) flag ``--address 0.0.0.0``. - [DAML SDK] The Scenario Service will now bind on ``127.0.0.1``. Previous behaviour was to bind on ``0.0.0.0``. CHANGELOG_END
2020-03-05 19:10:49 +03:00
"@maven//:io_grpc_grpc_core",
"@maven//:io_grpc_grpc_netty",
Replace bazel-deps by rules_jvm_external (#3253) * Update bazel-common to fix javadoc issues Specifically, to fix the following error ``` ERROR: /home/aj/tweag.io/da/da-bazel-1.1/ledger-api/rs-grpc-bridge/BUILD.bazel:7:1: in javadoc_library rule //ledger-api/rs-grpc-bridge:rs-grpc-bridge_javadoc: Traceback (most recent call last): File "/home/aj/tweag.io/da/da-bazel-1.1/ledger-api/rs-grpc-bridge/BUILD.bazel", line 7 javadoc_library(name = 'rs-grpc-bridge_javadoc') File "/home/aj/.cache/bazel/_bazel_aj/5f825ad28f8e070f999ba37395e46ee5/external/com_github_google_bazel_common/tools/javadoc/javadoc.bzl", line 27, in _javadoc_library dep.java.transitive_deps object of type 'JavaSkylarkApiProvider' has no field 'transitive_deps' ``` * Define Maven deps using rules_jvm_external * Pin artifacts * Remove bazel-deps generated targets * Remove bazel-deps * Switch to rules_jvm_external targets * update bazel documentation * pom_file: There are no more bazel-deps targets * BAZEL-JVM.md `maven_install` typo
2019-10-28 15:53:14 +03:00
"@maven//:io_grpc_grpc_stub",
Enforce consistent formatting of BUILD files. (#412) * Add buildifier targets. The tool allows to check and format BUILD files in the repo. To check if files are well formatted, run: bazel run //:buildifier To fix badly-formatted files run: bazel run //:buildifier-fix * Cleanup dade-copyright-headers formatting. * Fix dade-copyright-headers on files with just the copyright. * Run buildifier automatically on CI via 'fmt.sh'. * Reformat all BUILD files with buildifier. Excludes autogenerated Bazel files.
2019-04-12 14:10:16 +03:00
],
open-sourcing daml
2019-04-04 11:33:38 +03:00
)
Reference in New Issue Copy Permalink