status-im
/
status-desktop
mirror of https://github.com/status-im/status-desktop.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-desktop/.gitmodules

122 lines
4.3 KiB
Plaintext
Raw Permalink Normal View History

Adding nimbus-build-system
2020-05-14 14:58:08 +00:00
[submodule "vendor/nimbus-build-system"]
path = vendor/nimbus-build-system
Nim library upgrades, pt1 (#9703) This PR upgrades a number of libraries as well as nim itself, to address security issues and crashes that we've worked to solve over the past few months on the nimbus-eth2 side leading up to its 1.6 migration - they include changes that are safe to use in both 1.2 and 1.6 without requiring 1.6, making the code compatible with both versions. In particular, 1.6 becomes more strict in several ways including exception handling, style and certain langauge constructs related to memory safety - as a result, we've cleaned up said libraries and improved their stability overall, including fixing several crashes. * nim 1.2.18 - this is the last release in the 1.2 series we produced together with upstream based on nimbus' needs - between the version Desktop is using today and v1.2.18, changes are predominantly backports from newer Nim versions that we asked for while working on stability in Nimbus itself. * chronicles - cleanups * confutils - cleanups * faststreams - cleanups & crash fixes * nim-json-serialization - several important crash fixes for json parsing edge cases * metrics - cleanups & threading fixes * secp256k1 - upstream updates (including security fixes) * serialization - cleanups * stew - many convenience fixes and updates to common low-level utilities, such as Result and hex / base64 / etc parsing * stint - cleanups * zlib - cleanups * nimPNG - cleanups * nimcrypto - cleanups This is part 1 of library upgrades and focuses on the low-level libraries - part 2 will upgrade the network stack (chronos, json-rpc, web3, etc), keeping the two separate so as to limit the potential impact of this PR.
2023-03-03 10:14:10 +00:00
url = https://github.com/status-im/nimbus-build-system.git
Nim 1.6 Upgrade Nim compiler to 1.6. The necessary changes are related to how `for` loops now implicitly create a `lent` type, which is Nim's way of creating a "temporary" reference to an item inside a collection - this helps performance by avoiding a copy of the data, but it also means that the copy that previously was implicit in the for loop must be made explicit in the code.
2023-03-15 09:03:30 +00:00
branch = status-desktop
fix: signal handler integration with status-go
2020-05-16 23:46:46 +00:00
[submodule "vendor/nimqml"]
path = vendor/nimqml
.gitmodules: fix URLs so `make github-ssh` works as intended
2020-05-28 16:45:58 +00:00
url = https://github.com/status-im/nimqml.git
feat: onboarding generate new account Generates 5 random accounts with identicons, allows user to enter password, then stores the account and logs in to the statusgo node. Add EventEmitter that notifies nim_status_client.nim once node has started and is logged in (likely needs some refactoring to include the eventemitter in the base controller class). Add QML StateMachine for the onboarding view. Add nimcrytpo, uuids, eventemitter, isaac dependencies via submodules. Add button to Intro view to randomly gen account.
2020-05-19 13:22:38 +00:00
[submodule "vendor/uuids"]
path = vendor/uuids
.gitmodules: fix URLs so `make github-ssh` works as intended
2020-05-28 16:45:58 +00:00
url = https://github.com/pragmagic/uuids.git
feat: show qr codes
2020-06-23 17:17:58 +00:00
[submodule "vendor/QR-Code-generator"]
path = vendor/QR-Code-generator
url = https://github.com/status-im/QR-Code-generator
adding missing deps
2020-09-03 16:06:51 +00:00
[submodule "vendor/chroma"]
path = vendor/chroma
url = https://github.com/treeform/chroma
[submodule "vendor/nimPNG"]
path = vendor/nimPNG
url = https://github.com/jangko/nimPNG/
[submodule "vendor/nimage"]
path = vendor/nimage
url = https://github.com/Ethosa/nimage/
feat: command-line option can be used to specify app's data directory In the repo: ``` $ bin/nim_status_client --help ``` In the packaged app (macOS example): ``` $ cd /Applications/Status.app/Contents/MacOS $ ./nim_status_client --help ``` Output: ``` Usage: nim_status_client [OPTIONS]... The following options are available: -d, --dataDir Status Desktop data directory. ``` **Using the option** ``` $ cd ~/status-ci-builds/master/Status.app/Contents/MacOS $ ./nim_status_client --dataDir:"${HOME}/status-dirs/master" ``` In another terminal: ``` $ cd ~/status-ci-builds/PR-4242/Status.app/Contents/MacOS $ ./nim_status_client --dataDir:"${HOME}/status-dirs/PR-4242" ``` The path supplied can be relative or absolute, and can be specified with `--dataDir:[path]`, `--dataDir=[path]`, `-d:[path]`, or `-d=[path]`. Either `:` or `=` must be used, i.e. this *will not* work: `--dataDir [path]` or `-d [path]`. The name of the option follows Nim's partial case-insensitivity rules, so `--dataDir`, `--datadir`, and `--data_dir` are all equivalent. See [Identifier equality][ieq] in the Nim Manual. It is possible to run the same build in multiple terminals by supplying different `--dataDir`, i.e. this works: ``` $ cd /Applications/Status.app/Contents/MacOS $ ./nim_status_client --dataDir="${HOME}/temp/some1" ``` In another terminal: ``` $ cd /Applications/Status.app/Contents/MacOS $ ./nim_status_client --dataDir="${HOME}/temp/some2" ``` **Windows** It is recommended to use a Git Bash or MSYS2 terminal when invoking `bin/nim_status_client.exe` (development build) or `bin/Status.exe` (production build) on the command-line. The reason is that if the exe is invoked in a session of `cmd.exe` it will return to the prompt immediately; the app will run but there will be no output in the terminal. In any case, the `--dataDir` option will take effect whether the exe is invoked in `cmd.exe` or a recommended terminal. For development builds, when invoking `bin/nim_status_client.exe` directly instead of via `make run`, because e.g. you wish to use the `--dataDir` option, it is required to first setup the `PATH` environment variable correctly. See the `run-windows` target in this repo's Makefile for more information. **Linux** The `--dataDir` option may be passed to command-line invocation of a production (AppImage) build in the same way as passing it to a development build: ``` $ Status.AppImage --dataDir:/path/to/wherever ``` For development builds, when invoking `bin/nim_status_client` directly instead of via `make run`, because e.g. you wish to use the `--dataDir` option, it is required to setup the `LD_LIBRARY_PATH` environment variable correctly. See the `run-linux` target in this repo's Makefile for more information. --- BREAKING CHANGE: The `qt` subdir of the app's data directory is now a sibling of the status-go directory rather than a subdir of the status-go directory: ``` Status (app data directory) ├── data (status-go directory) ├── qt └── tmp ``` Because app settings are stored in the `qt` directory that means that existing installations will lose their customized settings. At app startup, it would be possible to detect `Status/data/qt` and if `Status/qt` doesn't exist yet then copy `Status/data/qt` to `Status/qt`. However, there was some concern that behavior could lead to problems later on if we forget the workaround is in place. So for now that settings preservation strategy has not been implemented, but it might be before this commit is merged pending full team awareness/consensus. --- Command-line option support is provided by [nim-confutils](https://github.com/status-im/nim-confutils). The environment variable `NIM_STATUS_CLIENT_DEV` has been removed in favor of passing a "define" option to the Nim compiler: `-d:development` for development builds (e.g. `make V=1`) and `-d:production` for packaged builds (e.g. `make V=1 pkg`). Passing the correct option is handled automatically by the Makefile. A make variable named `RELEASE` has been introduced, which defaults to `false`. Presently the `RELEASE` variable should not be set on the command-line nor in CI as more work needs to be done to toggle the proper compiler flags. In the case of Status Desktop, "release vs. debug" is a concern orthogonal to "production vs. development". At present, production builds and development builds are all debug builds, but that will likely change in the future: we can have non-release CI production builds and local development builds be debug builds, while release builds in CI would be production builds with `RELEASE=true` (the compiled executable will be fully optimized). Prior to the changes in this PR, symmetry is somewhat lacking between development and production (packaged) builds with respect to the concept of the "data directory". In development builds the root of the repo effectively serves as the `Status` directory used by production builds, e.g. on macOS `~/Library/Application Support/Status`. Also, there's a bit of confusion as to whether "data directory" refers to a directory for the desktop app's overall data (including status-go data) or to the specific directory used by status-go. This PR attempts to provide symmetry and reduce confusion: * The term "data directory" means the directory used by the desktop app to store multiple kinds of data and is not a reference to the subdirectory used by status-go. * For development builds the "data directory" defaults to `./Status/` relative to the root of the repo. * For production builds the "data directory" default is the same as before, e.g. on macOS it's ` ~/Library/Application Support/Status/`. The directory used by status-go is `Status/data/`. To be clear, that should be referred to as the "status-go directory" and not the app's "data directory". It would nice if we could rename it from `Status/data/` to `Status/status-go/`. We can do that, I already checked that it works correctly; however, for existing installations it would require that at app launch we check for the presence of `Status/data/` and rename it to `Status/status-go`. While simple enough to do, I was concerned that there might be edge cases where the directory rename could cause a problem (e.g. if another copy of the app is running) so chose for now to stick with the status-go directory being `Status/data/`. --- **NOTES** More work needs to be done to ensure that all data written by the app is contained in the default or cli-specified data directory. Currently, both development and production (packaged) builds are writing to common directories outside of the data directory, e.g. located within `~/Library/` on macOS. Changing that behavior seems like it will mainly involve changing defaults related to Qt components such as the web engine. See: https://github.com/status-im/status-desktop/issues/1141. In general, additional refactoring could be done in the future. For example, implementing `StatusDesktopConfig` in `src/status/libstatus/accounts/constants.nim` (as done in this PR) works fine for now, but better code organization is desirable. --- Closes #2268 [ieq]: https://nim-lang.org/docs/manual.html#lexical-analysis-identifier-equality
2021-04-19 12:20:07 +00:00
[submodule "vendor/nim-confutils"]
path = vendor/nim-confutils
url = https://github.com/status-im/nim-confutils.git
feat: Version Updating Fixes #1290
2021-06-17 18:41:11 +00:00
[submodule "vendor/semver.nim"]
path = vendor/semver.nim
url = https://github.com/euantorano/semver.nim
Nim library updates, pt 2 (#9734) This is part 2 of the nim library updates targeting networking and ETH libraries: * bearssl: upstream security updates, refactoring * chronos: significant stability updates across the board - ie better connection management, async fixes, updates, refactoring etc * eth: updates across the board, including EIP support, discv5, etc * http-utils: fixes * json-rpc: replaced websocket engine with in-house nim-websock (vs news which is no longer supported) * libp2p: lots of updates, but not relevant to status-desktop as of yet * web3: new API and conformance updates based on execution API spec * semver: crash fix, branch name * news: removed in favour of nim-websock
2023-03-20 06:34:56 +00:00
branch = main
refactor: creating module for bookmarks and provider
2021-10-14 14:29:33 +00:00
[submodule "vendor/nim-result"]
path = vendor/nim-result
url = https://github.com/arnetheduck/nim-result
refactor(@desktop/general): repo cleaning - all unused/unnecessary files remove - `status-lib` references updated due to cleaning on that side - necessary submodules added (those removed from status lib)
2022-01-31 09:45:48 +00:00
[submodule "vendor/edn.nim"]
path = vendor/edn.nim
url = https://github.com/status-im/edn.nim
[submodule "vendor/nim-faststreams"]
path = vendor/nim-faststreams
url = https://github.com/status-im/nim-faststreams.git
[submodule "vendor/nim-stew"]
path = vendor/nim-stew
url = https://github.com/status-im/nim-stew.git
[submodule "vendor/nimcrypto"]
path = vendor/nimcrypto
url = https://github.com/cheatfate/nimcrypto.git
[submodule "vendor/nim-eth"]
path = vendor/nim-eth
url = https://github.com/status-im/nim-eth
[submodule "vendor/nim-libp2p"]
path = vendor/nim-libp2p
url = https://github.com/status-im/nim-libp2p
[submodule "vendor/nim-chronos"]
path = vendor/nim-chronos
url = https://github.com/status-im/nim-chronos.git
[submodule "vendor/isaac"]
path = vendor/isaac
url = https://github.com/pragmagic/isaac.git
[submodule "vendor/nim-bearssl"]
path = vendor/nim-bearssl
url = https://github.com/status-im/nim-bearssl
[submodule "vendor/nim-secp256k1"]
path = vendor/nim-secp256k1
url = https://github.com/status-im/nim-secp256k1
[submodule "vendor/nim-metrics"]
path = vendor/nim-metrics
url = https://github.com/status-im/nim-metrics
[submodule "vendor/nim-json-rpc"]
path = vendor/nim-json-rpc
url = https://github.com/status-im/nim-json-rpc
[submodule "vendor/nim-web3"]
path = vendor/nim-web3
url = https://github.com/status-im/nim-web3.git
[submodule "vendor/nim-chronicles"]
path = vendor/nim-chronicles
url = https://github.com/status-im/nim-chronicles.git
[submodule "vendor/nim-websock"]
path = vendor/nim-websock
url = https://github.com/status-im/nim-websock
[submodule "vendor/nim-http-utils"]
path = vendor/nim-http-utils
url = https://github.com/status-im/nim-http-utils
[submodule "vendor/nim-zlib"]
path = vendor/nim-zlib
url = https://github.com/status-im/nim-zlib
[submodule "vendor/nim-json-serialization"]
path = vendor/nim-json-serialization
url = https://github.com/status-im/nim-json-serialization.git
[submodule "vendor/nim-serialization"]
path = vendor/nim-serialization
url = https://github.com/status-im/nim-serialization.git
chore: issues after massive `base_bc` rebase fixed
2022-02-01 11:14:15 +00:00
[submodule "vendor/fcitx5-qt"]
path = vendor/fcitx5-qt
url = https://github.com/fcitx/fcitx5-qt
chores(@general): remove status-lib deps
2022-02-03 14:23:51 +00:00
[submodule "vendor/status-go"]
path = vendor/status-go
url = https://github.com/status-im/status-go
[submodule "vendor/nim-status-go"]
path = vendor/nim-status-go
url = https://github.com/status-im/nim-status-go.git
[submodule "vendor/nim-stint"]
path = vendor/nim-stint
url = https://github.com/status-im/nim-stint.git
[submodule "vendor/nim-keycard-go"]
path = vendor/nim-keycard-go
url = https://github.com/status-im/nim-keycard-go
feat(@desktop/keycard): initial keycard implementation Keycard implementation affected onboarding/login flows. - new user - first run - new keys into keycard - new user - first run - import seed phrase into keycard - old user - first run - login importing from keycard - login the app using keycard Fixes: #5972
2022-07-21 11:29:18 +00:00
[submodule "vendor/status-keycard-go"]
path = vendor/status-keycard-go
url = https://github.com/status-im/status-keycard-go.git
chore(general): add SortFilterProxyModel submodule It's necessary as a result of StatusQ merge
2022-09-21 15:56:22 +00:00
[submodule "vendor/SortFilterProxyModel"]
move qzxing and SortFilterProxyModel to vendor folder Lets avoid creating chaos by having multiple vendor folders. Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-03-23 08:55:18 +00:00
path = vendor/SortFilterProxyModel
chore(general): add SortFilterProxyModel submodule It's necessary as a result of StatusQ merge
2022-09-21 15:56:22 +00:00
url = https://github.com/status-im/SortFilterProxyModel.git
fix(NimThreadpool): Implement lightweight threadpool Motivation: reduce memory usage. The previous implementation was using 400+ mb of memory for a threadpool with 16 threads.
2023-02-20 15:00:04 +00:00
[submodule "vendor/nim-taskpools"]
path = vendor/nim-taskpools
url = https://github.com/status-im/nim-taskpools.git
move qzxing and SortFilterProxyModel to vendor folder Lets avoid creating chaos by having multiple vendor folders. Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-03-23 08:55:18 +00:00
[submodule "vendor/qzxing"]
path = vendor/qzxing
QR code scanner (QML component) (#9464) Co-authored-by: Richard Ramos <info@richardramos.me>
2023-03-07 16:08:38 +00:00
url = https://github.com/status-im/qzxing.git
chore: update to nim 2.0
2024-10-04 22:18:14 +00:00
[submodule "vendor/checksums"]
path = vendor/checksums
url = https://github.com/nim-lang/checksums.git
ignore = untracked
branch = master