| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
* chore(release): prepare for release 18.5.0
* update workflow ubuntu version
* revert because dist checks lol
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
* chore: upgrade to 2024 edition
* ugh unsafe
* format
* nixxxxxxxxxxx why
|
| |
|
|
|
| |
* chore(release): prepare for release 18.5.0-beta.1
* no codespell on contributors
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* test: add env ATUIN_TEST_LOCAL_TIMEOUT to control test timeout of SQLite
This make it possible to control the timeout of SQLite operations in
test. And ATUIN_TEST_LOCAL_TIMEOUT defaults to the default local_timeout,
which is actually used in the client. Instead of a small timeout (0.1),
this change makes the test less likely to fail and better imitate the
default behavior.
SQLite operation timeout was first introduced from #1590, including
connection and store timeout. The env ATUIN_TEST_SQLITE_STORE_TIMEOUT
which added by #1703 only specify the store timeout. This commit doesn't
deprecate ATUIN_TEST_SQLITE_STORE_TIMEOUT, but control it by setting its
default to the new env ATUIN_TEST_LOCAL_TIMEOUT.
* test!: replace ATUIN_TEST_SQLITE_STORE_TIMEOUT with ATUIN_TEST_LOCAL_TIMEOUT
This deprecate ATUIN_TEST_SQLITE_STORE_TIMEOUT for simplicity as the new
env ATUIN_TEST_LOCAL_TIMEOUT can control both connection and store
timeout of SQLite in test. Details see 4d88611.
Revert: #1703.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* feat(gui): add runbook list, ability to create and delete, sql storage (#2282)
* wip
* saving works :))
* functioning delete button
* persist selection properly
* update contributors
* update changelog
|
| |
|
|
|
| |
* chore(release): prepare for release v18.4.0-beta.1
* remove full release test
|
| |
|
|
|
|
|
|
|
| |
* chore(release): prepare for release v18.3.0
* build full release
* Revert "build full release"
This reverts commit 65e7718b51927ca6cb03a411cce781b81cb64eaa.
|
| |
|
|
|
|
|
| |
* chore(release): v18.3.0-prerelease.1
* update contributors
* changelog, plan only on prs
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [rmp](https://github.com/3Hren/msgpack-rust) from 0.8.12 to 0.8.14.
- [Release notes](https://github.com/3Hren/msgpack-rust/releases)
- [Commits](https://github.com/3Hren/msgpack-rust/commits/rmp/v0.8.14)
---
updated-dependencies:
- dependency-name: rmp
dependency-type: direct:production
update-type: version-update:semver-patch
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* fix(dotfiles): allow clearing aliases, disable import
At the moment there are far too many edge cases to handle importing
aliases.
1. We need an interactive shell to print aliases. Without it, most
shells won't report much.
2. Many people have their shells print things on startup (graphics,
fortunes, etc). This could be detected as an attempt to set an alias.
Rather than spend the next year finding import edge cases, I'm
disabling it for now. There's probably a better way we can do this?
* clippy
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There's a bunch of duplication here!
I'd also like to support syncing shell "snippets", aka just bits of
shell config that don't fit into the structure here. Potentially special
handling for PATH too.
Rather than come up with some abstraction in the beginning, which
inevitably will not fit future uses, I'm duplicating code _for now_.
Once all the functionality is there, I can tidy things up and sort a
proper abstraction out.
Something in atuin-client for map/list style synced structures would
probably work best.
|
| |
|
|
|
| |
* fix(dotfiles): unquote aliases before quoting
* tests
|
| |
|
| |
Serves me right for assuming fish mostly is POSIX.
|
| | |
|
| | |
|
|
|
I'd like to tidy up the root a little, and it's nice to have all the
rust crates in one place
|
