ca66061b28
* WIP : first cut at changed schema files for oracle Define Oracle as DbType and handle necessary case match switches for it recomputed shas for oracle migration scripts Oracle fixtures get things compiling Able to connect to Oracle Working through getting schema definitions functional with Oracle runnable schema definitions only for active tables on oracle delete commented lines in schema scripts use oracle enterprise correct inadvertently changed postgres schemas WIP - latest oracle-ificiation passing upload packages spec add additional test for package upload entry read correct typo in oracle database spec name use BLOB for parties ledger_offset package_entries use hex version of offset for range queries reformat and update shas for sql scripts binary numeric implicit conversion for oracle correct duplicate exception text for oracle parties test passing on oracle add additional column to hold hex offset for party_entries party_entries working for all dbs scalafmt Configuration ledger_offset should be BLOB update sha of oracle sql files enable passing tests in order remove misleading null comments define additional custom VARRAY types add participant-integration-api-oracle tests to linux-oracle job Add TODO for places where we need to deal with separate implicit imports for Oracle vs Postgres/H2 oracle implicit conversions for custom arrays and other problematic types Do not override default debug level for all tests in participant-integration-api CHANGELOG_BEGIN Ledger API and Indexer Oracle Support CHANGELOG_END passing TransactionWriterSpec passing JdbcLedgerDaoCompletionsSpec JdbcLedgerDaoDivulgenceSpec passing JdbcLedgerDaoContractsSpec All Oracle tests passing apart from one post-commit validation test * Remove JdbcLedgerDaoValidatedOracleSpec as this is only relevant for classic postgres-backed sandbox * rebase to master -- offsets are now varchar2 rather than blob * remove use of DBMS_LOB operations * remove all greater than/less than variants for DBMS_LOB * revert postgres files that need not be touched * code review feedback : avoid code duplication * avoid indirection in type names for oracle arrays * code review: HexString implicit conversions are not needed * code review: Oracle case is not yet implemented for appendonlydao * code review: Oracle case is not yet implemented for appendonlydao (cleanup import) * code review: revert files that should not be touched * address code review feedback: db specific imports for command completion become part of queries * code review: perform db-specific reserved word escape to avoid case match * code review: remove all dbms_lob comparison operations * use simpler insert into with ignore dupes hint for oracle * code review: avoid db specific match case in events range, use db specific limitClause * code review: restore group by on Binary and Array fields for H2 and Postgres, disable for Oracle * code review: restore group by on Binary and Array fields for H2 and Postgres, disable for Oracle * code review: restore group by on binary and array fields for non-oracle dbs, honour the calculation of limit size from QueryParty.ByArith * code review: honour the calculation of limit size from QueryParty.ByArith * code review: drop user after oracle test * code review: remove drop user as it throws errors due to dangling sessions * code review: revert incorrectly changed postgres schema files * code review: clean up TODOs * Remove // before hostname for consistency with other oracle connection strings * code review: unambiguously scope table column referenced in select and where queries * code review: correct duplicate table alias |
||
---|---|---|
.github | ||
.vscode | ||
3rdparty | ||
bazel_tools | ||
build-scripts | ||
ci | ||
compatibility | ||
compiler | ||
daml-assistant | ||
daml-lf | ||
daml-script | ||
dev-env | ||
docs | ||
extractor | ||
ghc-lib | ||
infra | ||
language-support | ||
ledger | ||
ledger-api | ||
ledger-service | ||
libs-haskell | ||
libs-scala | ||
navigator | ||
nix | ||
release | ||
replacements | ||
rules_daml | ||
runtime-components | ||
scala-protoc-plugins | ||
templates | ||
triggers | ||
.bazelignore | ||
.bazelrc | ||
.dadew | ||
.envrc | ||
.gitattributes | ||
.gitignore | ||
.hie-bios | ||
.hlint.yaml | ||
.mergify.yml | ||
.scalafmt.conf | ||
azure-cron.yml | ||
azure-pipelines.yml | ||
BAZEL-bash.md | ||
bazel-haskell-deps.bzl | ||
BAZEL-haskell.md | ||
bazel-java-deps.bzl | ||
BAZEL-JVM.md | ||
BAZEL.md | ||
BUILD | ||
build.ps1 | ||
build.sh | ||
CHANGELOG | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
COPY | ||
daml-logo.png | ||
deps.bzl | ||
dotfiles | ||
fmt.sh | ||
ghcide_snapshot_windows.json | ||
ghcide_snapshot.json | ||
ghcide-snapshot.yaml | ||
LATEST | ||
LICENSE | ||
maven_install_2.12.json | ||
maven_install_2.13.json | ||
NOTICES | ||
NOTICES.md | ||
package.json | ||
Pipfile | ||
README.md | ||
release.sh | ||
SECURITY.md | ||
stack-snapshot.yaml | ||
stackage_snapshot_windows.json | ||
stackage_snapshot.json | ||
tsconfig.json | ||
unreleased.sh | ||
Upgrading.md | ||
WORKSPACE | ||
workspace_status.sh | ||
yarn.lock |
Copyright (c) 2021 Digital Asset (Switzerland) GmbH and/or its affiliates. All Rights Reserved. SPDX-License-Identifier: Apache-2.0
Welcome to the Daml repository!
This repository hosts all code for the Daml smart contract language and SDK, originally created by Digital Asset. Daml is an open-source smart contract language for building future-proof distributed applications on a safe, privacy-aware runtime. The SDK is a set of tools to help you develop applications based on Daml.
Using Daml
To download Daml, follow the installation instructions. Once installed, to try it out, follow the quickstart guide.
If you have questions about how to use Daml or how to build Daml-based
solutions, please join us on the Daml forum. Alternatively, if you prefer
asking on StackOverflow, please use the daml
tag.
Contributing to Daml
We warmly welcome contributions. If you are looking for ideas on how to contribute, please browse our issues. To build and test Daml:
1. Clone this repository
git clone git@github.com:digital-asset/daml.git
cd daml
2. Set up the development dependencies
Our builds require various development dependencies (e.g. Java, Bazel, Python), provided by a tool called dev-env
.
Linux and Mac
On Linux and Mac dev-env
can be installed with:
- Install Nix by running:
bash <(curl -sSfL https://nixos.org/nix/install)
- Enter
dev-env
by running:eval "$(dev-env/bin/dade assist)"
If you don't want to enter dev-env
manually each time using eval "$(dev-env/bin/dade assist)"
,
you can also install direnv. This repo already provides a .envrc
file, with an option to add more in a .envrc.private
file.
Windows
On Windows you need to enable long file paths by running the following command in an admin powershell:
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem' -Name LongPathsEnabled -Type DWord -Value 1
Then start dev-env
from PowerShell with:
.\dev-env\windows\bin\dadew.ps1 install
.\dev-env\windows\bin\dadew.ps1 sync
.\dev-env\windows\bin\dadew.ps1 enable
In all new PowerShell processes started, you need to repeat the enable
step.
3. First build and test
We have a single script to build most targets and run the tests. On Linux and Mac run ./build.sh
. On Windows run .\build.ps1
. Note that these scripts may take over an hour the first time.
To just build do bazel build //...
, and to just test do bazel test //...
. To read more about Bazel and how to use it, see the Bazel site.
On Mac if building is causing trouble complaining about missing nix packages, you can try first running nix-build -A tools -A cached nix
repeatedly until it completes without error.
4. Installing a local copy
On Linux and Mac run daml-sdk-head
which installs a version of the SDK with version number 0.0.0
. Set the version:
field in any Daml project to 0.0.0 and it will use the locally installed one.
On Windows:
bazel build //release:sdk-release-tarball
tar -vxf .\bazel-bin\release\sdk-release-tarball-ce.tar.gz
cd sdk-*
daml\daml.exe install . --activate
That should tell you what to put in the path, something along the lines of C:\Users\admin\AppData\Roaming\daml\bin
.
Note that the Windows build is not yet fully functional.
Caching: build speed and disk space considerations
Bazel has a lot of nice properties, but they come at the cost of frequently rebuilding "the world".
To make that bearable, we make extensive use of caching. Most artifacts should be cached in our CDN,
which is configured in .bazelrc
in this project.
However, even then, you may end up spending a lot of time (and bandwidth!) downloading artifacts from
the CDN. To alleviate that, by default, our build will create a subfolder .bazel-cache
in this
project and keep an on-disk cache. This can take about 10GB at the time of writing.
To disable the disk cache, remove the following lines:
build:linux --disk_cache=.bazel-cache
build:darwin --disk_cache=.bazel-cache
from the .bazelrc
file.
If you work with multiple copies of this repository, you can point all of them to the same disk cache
by overwriting these configs in either a .bazelrc.local
file in each copy, or a ~/.bazelrc
file
in your home directory.
Shared memory segment issues
On macOS at least, it looks like our setup does not always properly close the resources PostgreSQL uses. After a number of test runs, you may encounter an error message along the lines of:
FATAL: could not create shared memory segment: No space left on device
DETAIL: Failed system call was shmget(key=5432001, size=56, 03600).
HINT: This error does *not* mean that you have run out of disk space. It occurs either if all available shared memory IDs have been taken, in which case you need to raise the SHMMNI parameter in your kernel, or because the system's overall limit for shared memory has been reached.
The PostgreSQL documentation contains more information about shared memory configuration.
child process exited with exit code 1
In this case, this is a memory leak, so increasing SHMNI
(or SHMALL
etc.)
as suggested will only delay the issue. You can look at the existing shared
memory segments on your system by running ipcs -mcopt
; this will print a line
per segment, indicating the process ID of the last process to connect to the
segment as well as the last access time and the number of currently connected
processes.
If you identify segments with no connected processes, and you are confident you
can remove them, you can do so with ipcrm $sid
, where $sid
is the process
ID displayed (as the second column) by ipcs
. Not many macOS applications use
shared memory segments; if you have verified that all the existing memory
segments on your machine need to be deleted, e.g. because they have all been
created by PostgreSQL instances that are no longer running, here is a Bash
invocation you can use to remove all shared memory segments from your system.
This is a dangerous command. Make sure you understand what it does before running it.
for shmid in $(ipcs -m | sed 1,3d | awk '{print $2}' | sed '$d'); do ipcrm -m $shmid; done
Haskell profiling builds
To build Haskell executables with profiling enabled, pass -c dbg
to
Bazel, e.g. bazel build -c dbg damlc
. If you want to build the whole
SDK with profiling enabled use daml-sdk-head --profiling
.