https://github.com/temperlang/temper
A programming language for libraries translated to all the others
https://github.com/temperlang/temper
distributed-systems interoperability programming-language reliability-engineering translation
Last synced: 3 days ago
JSON representation
A programming language for libraries translated to all the others
- Host: GitHub
- URL: https://github.com/temperlang/temper
- Owner: temperlang
- License: apache-2.0
- Created: 2023-08-11T01:42:51.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2026-01-10T05:08:18.000Z (11 days ago)
- Last Synced: 2026-01-10T20:11:01.507Z (11 days ago)
- Topics: distributed-systems, interoperability, programming-language, reliability-engineering, translation
- Language: Kotlin
- Homepage: https://temperlang.dev/
- Size: 13.5 MB
- Stars: 76
- Watchers: 7
- Forks: 2
- Open Issues: 126
-
Metadata Files:
- Readme: README-extra.md
- Contributing: CONTRIBUTING.md
- License: LICENSE-APACHE
- Support: supported-backends/build.gradle
- Copyright: COPYRIGHT
Awesome Lists containing this project
README
# Extra content
## Minimal steps to creating a new subproject
Terminology note: [according to Gradle](https://docs.gradle.org/current/userguide/multi_project_builds.html), this
is a "multi-project build" with a "root project" and many "subprojects." IntelliJ says it's a "project" with many
"modules." We're using Gradle's terminology since it's the source of truth.
We'll go over a checklist of items to set up `new-subproject`. This isn't meant to be all-inclusive, but
hopefully it will save you thirty minutes of staring at Gradle errors.
1. In `settings.gradle` add `include ':new-subproject'` to the list of includes.
2. Make the directory `new-subproject`.
3. Copy a `build.gradle` file for either a multi-platform project or a jvm project.
* To see what existing subprojects are, look for `ext.temperProject`
* That's an external (gradle's term for user-defined) setting
* That's used in the `afterEvaluate` clause in the root `build.gradle` to do some common configuration.
* TODO: factor that logic into a local gradle plugin
### Verifying
Besides creating a dummy function and a test, you'll want to check that IntelliJ accepts this project.
In IntelliJ, go to either gradle file you're editing and click the gradle elephant to sync.
* The Project view should show your subproject, and mousing over it should indicate it's a Module.
* Open File / Project Structure, compare your subproject to others
* Check all three tabs, Sources, Paths, Dependencies and make sure they make sense.
## Signing git commits
Temper uses Github's [vigilant mode][] which prefers signed commits. When it's working, you should see a shiny green
"Verified" sticker next to your commits.
A point of confusion is managing all these keys. You can have a key in the web interface that's different from your
device, and most people submit pull requests from the web interface.
That means you can commit using a GPG key loaded in your Github profile, and not notice that your local device isn't
configured.
### Additional reading
This isn't intended to be a comprehensive guide, and you may find you're able to skim all of this and just run the
commands. If you run into issues:
* [Github generating a GPG key][]
* [Github signature verification][]
* [Signing Your Work][]
### Setting up a GPG key
See the github docs, but generally you just want to do this to get prompted for everything. We recommend that you
have one key corresponding to your email address.
```bash
$ gpg --full-generate-key
```
Then [add it to your Github account][adding-GPG-key].
### Selecting your git key
You can safely skip most of this section and go to the last part where you confirm that your email selects the key
you just generated.
You need to set your signing key in your git config. We'll briefly excerpt some man pages that may help you understand
what's going on:
```
$ man git-commit
-S[], --gpg-sign[=], --no-gpg-sign
GPG-sign commits. The keyid argument is optional and defaults to the committer identity ...
$ man git-config
user.signingKey
... you can override the default selection with this variable. This option is passed unchanged to gpg’s
--local-user parameter, so you may specify a key using any method that gpg supports. ...
$ man gpg
--sign
... The signing key is chosen by default or can be set explicitly using the --local-user and --default-key
options.
```
You can list your keys with `--list-keys`, but it won't tell you what any fields are. We can figure it out by
asking it to specify a distinct format:
```bash
$ gpg --list-keys --keyid-format=0xshort
/home/yours/.gnupg/pubring.kbx
----------------------------
...
pub rsa3072/0x68A712FE 2021-12-08 [SC] [expires: 2026-12-07]
0B7F3E7172FA3012E343091BEA2E9968A712FE
uid [ultimate] Yours Truly (github @yours)
sub rsa3072/0x1217ADC0 2021-12-08 [E] [expires: 2026-12-07]
```
The keyid in this case is `68A712FE`. If you have two keys with the same email, this is how you select the specific
one you want.
There's no way to ask `gpg` directly what `--local-user` will select, but this is Unix, and we can use a pipeline:
```bash
$ echo 'test' | gpg --sign --local-user 'yours-truly@temper.systems' | gpg --verify -
gpg: Signature made Tue 26 Jul 2022 05:23:40 PM EDT
gpg: using RSA key 0B7F3E7172FA3012E343091BEA2E9968A712FE
gpg: issuer "yours-truly@temper.systems"
gpg: Good signature from "Yours Truly (github @yours) " [ultimate]
```
That long hex should match the fingerprint from `gpg --list-keys`. As of this writing, `--list-keys` silently ignores
`--local-user`.
### Configuring git
Edit either your global config `~/.gitconfig` or the repo config `.git/config` and add these blocks:
```ini
[user]
name = Yours Truly
email = yours-truly@temper.systems
signingkey = yours-truly@temper.systems
[commit]
gpgsign = true
```
The `[commit]` block is there to set `-S` by default for you when you run `git commit`.
### Verifying that it all works
Commit something to a repo and verify it's being signed with:
```bash
$ git log --show-signature
commit 761c7878d93f29af5221923e93858c59c398c137 (HEAD -> docs, origin/docs)
gpg: Signature made Tue 26 Jul 2022 10:46:23 AM EDT
gpg: using RSA key 0B7F3E7172FA3012E343091BEA2E8C9968A712FE
gpg: issuer "yours-truly@temper.systems"
gpg: Good signature from "Yours Truly (github @yours) " [ultimate]
Author: Yours Truly
Date: Mon Jul 25 17:17:52 2022 -0400
```
## Verbose tests
For verbose logging of test actions, add this to the subproject's `build.gradle`:
tasks.withType(Test) {
testLogging {
showCauses = true
showExceptions = true
showStackTraces = true
showStandardStreams = true
exceptionFormat = "full"
}
}
[Github signature verification]: https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification
[Github generating a GPG key]: https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key
[adding-GPG-key]: https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account
[Signing Your Work]: https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work
[vigilant mode]: https://docs.github.com/en/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits