enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-10-04 00:33:36 +03:00
Code Issues Projects Releases Wiki Activity
81726a6e47
enso/Cargo.lock

4703 lines
104 KiB
Plaintext
Raw Normal View History

Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
version = 3
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "Inflector"
version = "0.11.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fe438c63458706e03479442743baae6c88256498e6431708f6dfc520a26515d3"
dependencies = [
"lazy_static",
"regex",
]
[[package]]
name = "addr2line"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.17.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "b9ecd88a8c8378ca913a680cd98f0f13ac67383d35993f86c90a70e3f137816b"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"gimli",
]
[[package]]
name = "adler"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "1.0.2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "aho-corasick"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.7.18"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "1e37cfd5e7657ada45f742d6e99ca5788580b5c529dc78faf11ece6dc702656f"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"memchr",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "analytics"
version = "0.1.0"
dependencies = [
"js-sys",
"wasm-bindgen",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "anyhow"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.0.56"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "4361135be9122e0870de935d7c439aef945b9f9ddd4199a553b5270b49c82a27"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "approx"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f0e60b75072ecd4168020818c0107f2857bb6c4e64252d8d3983f6263b40a5c3"
dependencies = [
"num-traits",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "approx"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f2a05fd1bd10b2527e20a2cd32d8873d115b8b39fe219ee25f42a8aca6ba278"
dependencies = [
"num-traits",
]
Add tests for debug mode and zoom restriction. (#3289) This PR adds integration tests created during acceptance process of [181181159](https://www.pivotaltracker.com/story/show/181181159) and [181181203](https://www.pivotaltracker.com/story/show/181181203). The PRs for those tasks were merged, because I hadn't realized they should not. Additionally, as the `wasm-bindgen` version was bumped, I extended the timeout of integration tests and made them headless.
2022-02-22 19:43:37 +03:00
[[package]]
name = "approx"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cab112f0a86d568ea0e627cc1d6be74a1e9cd55214684db5561995f6dad897c6"
dependencies = [
"num-traits",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "assert_approx_eq"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3c07dab4369547dbe5114677b33fbbf724971019f3818172d59a97a61c774ffd"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "ast"
version = "0.1.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"ast-macros",
"derive_more",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-prelude",
"enso-shapely",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-text",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"failure",
"lazy_static",
"regex",
"serde",
"serde_json",
"shrinkwraprs 0.2.3",
"uuid",
]
[[package]]
name = "ast-macros"
version = "0.1.0"
dependencies = [
"Inflector",
"enso-macro-utils",
"enso-prelude",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
[[package]]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
name = "async-channel"
version = "1.6.1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "2114d64672151c0c5eaa5e131ec84a74f06e1e559830dabba01ca30605d66319"
dependencies = [
"concurrent-queue",
"event-listener",
"futures-core",
]
[[package]]
name = "async-executor"
version = "1.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "871f9bb5e0a22eeb7e8cf16641feb87c9dc67032ccf8ff49e772eb9941d3a965"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"async-task",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"concurrent-queue",
"fastrand",
"futures-lite",
"once_cell",
"slab",
]
[[package]]
name = "async-global-executor"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "2.0.4"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "c290043c9a95b05d45e952fb6383c67bcb61471f60cfa21e890dba6654234f43"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
dependencies = [
"async-channel",
"async-executor",
"async-io",
"async-mutex",
"blocking",
"futures-lite",
"num_cpus",
"once_cell",
]
[[package]]
name = "async-io"
version = "1.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a811e6a479f2439f0c04038796b5cfb3d2ad56c230e0f2d3f7b04d68cfee607b"
dependencies = [
"concurrent-queue",
"futures-lite",
"libc",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"once_cell",
"parking",
"polling",
"slab",
"socket2 0.4.4",
"waker-fn",
"winapi 0.3.9",
]
[[package]]
name = "async-lock"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "2.5.0"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "e97a171d191782fba31bb902b14ad94e24a68145032b7eedf871ab0bc0d077b6"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
dependencies = [
"event-listener",
]
[[package]]
name = "async-mutex"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "479db852db25d9dbf6204e6cb6253698f175c15726470f78af0d918e99d6156e"
dependencies = [
"event-listener",
]
[[package]]
name = "async-std"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.11.0"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "52580991739c5cdb36cde8b2a516371c0a3b70dda36d916cc08b82372916808c"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
dependencies = [
"async-channel",
"async-global-executor",
"async-io",
"async-lock",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"crossbeam-utils 0.8.8",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures-channel",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"futures-core",
"futures-io",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures-lite",
"gloo-timers",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"kv-log-macro",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"memchr",
"num_cpus",
"once_cell",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"pin-project-lite 0.2.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"pin-utils",
"slab",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"wasm-bindgen-futures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "async-task"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "4.2.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "30696a84d817107fc028e049980e09d5e140e8da8f1caeb17e8e950658a3cea9"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "atomic-waker"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "065374052e7df7ee4047b1160cca5e1467a12351a40b3da123c870ba0b8eda2a"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "atty"
version = "0.2.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
dependencies = [
"hermit-abi",
"libc",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"winapi 0.3.9",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "autocfg"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.1.8"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "0dde43e75fd43e8a1bf86103336bc699aa8d17ad1be60c76c0bdfd4828e19b78"
dependencies = [
"autocfg 1.1.0",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "autocfg"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.1.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "backtrace"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.3.65"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "11a17d453482a265fd5f8479f2a3f405566e6ca627837aaddb85af8b1ab8ef61"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"addr2line",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"cc",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"cfg-if 1.0.0",
"libc",
"miniz_oxide",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"object 0.28.3",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"rustc-demangle",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "base64"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "489d6c0ed21b11d038c31b6ceccca973e65d73ba3bd8ecb9a2babf5546164643"
dependencies = [
"byteorder",
"safemem",
]
[[package]]
name = "base64"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0b25d992356d2eb0ed82172f5248873db5560c4721f564b13cb5193bda5e668e"
dependencies = [
"byteorder",
]
Support source maps for JS-based visualizations (#3208)
2022-01-11 15:31:43 +03:00
[[package]]
name = "base64"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b41b7ea54a0c9d92199de89e20e58d49f02f8e699814ef3fdf266f6f748d15c7"
[[package]]
name = "base64"
version = "0.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "904dfeac50f3cdaba28fc6f57fdcddb75f49ed61346676a78c4ffe55877802fd"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "bimap"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "783204f24fd7724ea274d327619cfa6a6018047bb0561a68aadff6f56787591b"
dependencies = [
"cfg-if 0.1.10",
]
[[package]]
name = "bit_field"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dcb6dd1c2376d2e096796e234a70e17e94cc2d5d54ff8ce42b28cef1d0d359a4"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "bitflags"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
[[package]]
name = "block-buffer"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0940dc441f31689269e10ac70eb1002a3a1d3ad1390e030043662eb7fe4688b"
dependencies = [
"block-padding",
"byte-tools",
"byteorder",
"generic-array 0.12.4",
]
[[package]]
name = "block-padding"
version = "0.1.5"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "fa79dedbb091f449f1f39e53edf88d5dbe95f895dae6135a8d7b881fb5af73f5"
dependencies = [
"byte-tools",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "blocking"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.2.0"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "c6ccb65d468978a086b69884437ded69a90faab3bbe6e67f242173ea728acccc"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
dependencies = [
"async-channel",
"async-task",
"atomic-waker",
"fastrand",
"futures-lite",
"once_cell",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "boolinator"
version = "2.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cfa8873f51c92e232f9bac4065cddef41b714152812bfc5f7672ba16d6ef8cd9"
[[package]]
name = "bstr"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.2.17"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "ba3569f383e8f1598449f1a423e72e99569137b47740b1da11ef19af3d5c3223"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"lazy_static",
"memchr",
"regex-automata",
"serde",
]
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
[[package]]
name = "build-scripts"
version = "0.1.0"
dependencies = [
"glob",
"toml",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "bumpalo"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "3.9.1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "a4a45a46ab1f2412e53d3a0ade76ffad2025804294569aae387231a0cd6e0899"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "byte-tools"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e3b5ca7a04898ad4bcd41c90c5285445ff5b791899bb1b0abdd2a2aa791211d7"
[[package]]
name = "bytecount"
version = "0.5.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "be0fdd54b507df8f22012890aadd099979befdba27713c767993f8380112ca7c"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "byteorder"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "1.4.3"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "bytes"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.4.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "206fdffcfa2df7cbe15601ef46c813fce0965eb3286db6b56c583b814b51c81c"
dependencies = [
"byteorder",
"iovec",
]
[[package]]
name = "bytes"
version = "0.5.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0e4cec68f03f32e44924783795810fa50a7035d8c8ebe78580ad7e6c703fba38"
[[package]]
name = "bytes"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c4872d67bab6358e59559027aa3b9157c53d9358c51423c17554809a8858e0f8"
[[package]]
name = "bzip2"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6afcd980b5f3a45017c57e57a2fcccbb351cc43a356ce117ef760ef8052b89b0"
dependencies = [
"bzip2-sys",
"libc",
]
[[package]]
name = "bzip2-sys"
version = "0.1.11+1.0.8"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "736a955f3fa7875102d57c82b8cac37ec45224a07fd32d58f9f7a186b6cd4cdc"
dependencies = [
"cc",
"libc",
"pkg-config",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "cache-padded"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c1db59621ec70f09c5e9b597b220c7a2b43611f4710dc03ceb8748637775692c"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "cast"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.2.7"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "4c24dab4283a142afa2fdca129b80ad2c6284e073930f964c3a1293c225ee39a"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"rustc_version 0.4.0",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "cc"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.0.73"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "2fff2a6927b3bb87f9595d67196a70493f627687a71d87a0d692242c33f58c11"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "cfg-if"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "chrono"
version = "0.4.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73"
dependencies = [
"libc",
"num-integer",
"num-traits",
"serde",
"time",
"winapi 0.3.9",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "clap"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "2.34.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "a0610544180c38b88101fecf2dd634b174a62eef6946f84dfc6a7127512b381c"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"bitflags",
"textwrap",
"unicode-width",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
dependencies = [
"bitflags",
]
[[package]]
name = "code-builder"
version = "0.1.0"
dependencies = [
"enso-prelude",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "colored"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b3616f750b84d8f0de8a58bda93e08e2a81ad3f523089b05f1dffecab48c6cbd"
dependencies = [
"atty",
"lazy_static",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"winapi 0.3.9",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "concurrent-queue"
version = "1.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "30ed07550be01594c6026cff2a1d7fe9c8f683caa798e12b68694ac9e88286a3"
dependencies = [
"cache-padded",
]
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
[[package]]
name = "config-reader"
version = "0.1.0"
dependencies = [
"Inflector",
"serde",
"serde_yaml",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "console_error_panic_hook"
version = "0.1.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a06aeb73f470f66dcdbf7223caeebb85984942f22f1adb2a088cf9668146bbbc"
dependencies = [
"cfg-if 1.0.0",
"wasm-bindgen",
]
SDF-based mechanism for making letters bold (#3385) Fixes [181641027](https://www.pivotaltracker.com/story/show/181641027). There are new methods of text::Area for making some letters bolder, without moving them nor any other letters in the line. Tested on DejaVuSans text: ![image](https://user-images.githubusercontent.com/3919101/162199723-524f7560-535f-4c98-bcb4-6b760ad8cb04.png) ![image](https://user-images.githubusercontent.com/3919101/162199806-e6582c56-3071-4653-8ad2-114df86cd6b7.png) ![image](https://user-images.githubusercontent.com/3919101/162199880-1836e902-8663-4696-bcb7-2b15c3c243c6.png) On MacOS: <img width="824" alt="Screenshot 2022-04-07 at 14 54 40" src="https://user-images.githubusercontent.com/3919101/162203730-ffda3096-7aab-443f-a45a-bfa18784ba36.png"> <img width="379" alt="Screenshot 2022-04-07 at 14 54 52" src="https://user-images.githubusercontent.com/3919101/162203751-f5ca2e26-fdb6-4521-9821-999111b80ac0.png"> <img width="160" alt="Screenshot 2022-04-07 at 14 54 58" src="https://user-images.githubusercontent.com/3919101/162203769-3c367f81-67bb-48aa-994c-42eeb131017e.png">
2022-04-12 20:39:08 +03:00
[[package]]
name = "const_format"
version = "0.2.22"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "22bc6cd49b0ec407b680c3e380182b6ac63b73991cb7602de350352fc309b614"
dependencies = [
"const_format_proc_macros",
]
[[package]]
name = "const_format_proc_macros"
version = "0.2.22"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ef196d5d972878a48da7decb7686eded338b4858fbabeed513d63a7c98b2b82d"
dependencies = [
"proc-macro2",
"quote",
"unicode-xid",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "convert_case"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6245d59a3e82a7fc217c5828a6692dbc6dfb63a0c8c90495621f7b9d79704a0e"
[[package]]
name = "core-foundation"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.9.3"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "194a7a9e6de53fa55116934067c844d9d749312f75c6f6d0980e8c252f8c2146"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"core-foundation-sys",
"libc",
]
[[package]]
name = "core-foundation-sys"
version = "0.8.3"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "5827cebf4670468b8772dd191856768aedcb1b0278a04f989f7766351917b9dc"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
[[package]]
name = "crc32fast"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.3.2"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "b540bd8bc810d3885c6ea91e2018302f68baba2129ab3e88f32389ee9370880d"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
dependencies = [
"cfg-if 1.0.0",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "criterion"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.5"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "1604dafd25fba2fe2d5895a9da139f8dc9b319a5fe5354ca137cbbce4e178d10"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"atty",
"cast",
"clap",
"criterion-plot",
"csv",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itertools 0.10.3",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"lazy_static",
"num-traits",
"oorandom",
"plotters",
"rayon",
"regex",
"serde",
"serde_cbor",
"serde_derive",
"serde_json",
"tinytemplate",
"walkdir",
]
[[package]]
name = "criterion-plot"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.4.4"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "d00996de9f2f7559f7f4dc286073197f83e92256a59ed395f9aac01fe717da57"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"cast",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itertools 0.10.3",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
name = "crossbeam-channel"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.5.4"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "5aaa7bd5fb665c6864b5f963dd9097905c54125909c7aa94c9e18507cdbe6c53"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"cfg-if 1.0.0",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"crossbeam-utils 0.8.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "crossbeam-deque"
version = "0.8.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "6455c0ca19f0d2fbf751b908d5c55c1f5cbc65e03c4225427254b46890bdde1e"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"cfg-if 1.0.0",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"crossbeam-epoch",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"crossbeam-utils 0.8.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "crossbeam-epoch"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.9.8"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "1145cf131a2c6ba0615079ab6a638f7e1973ac9c2634fcbeaaad6114246efe8c"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"autocfg 1.1.0",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"cfg-if 1.0.0",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"crossbeam-utils 0.8.8",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"lazy_static",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"memoffset",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"scopeguard",
]
[[package]]
name = "crossbeam-utils"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.7.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3c7c73a2d1e9fc0886a08b93e98eb643461230d5f1925e4036204d5f2e261a8"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"cfg-if 0.1.10",
"lazy_static",
]
[[package]]
name = "crossbeam-utils"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.8.8"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "0bf124c720b7686e3c2663cf54062ab0f68a88af2fb6a030e87e30bf721fcb38"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"cfg-if 1.0.0",
"lazy_static",
]
[[package]]
name = "csv"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "1.1.6"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "22813a6dc45b335f9bade10bf7271dc477e81113e89eb251a0bc2a8a81c536e1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"bstr",
"csv-core",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itoa 0.4.8",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"ryu",
"serde",
]
[[package]]
name = "csv-core"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2b2466559f260f48ad25fe6317b3c8dac77b5bdb5763ac7d9d6103530663bc90"
dependencies = [
"memchr",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "ctor"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.1.22"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "f877be4f7c9f246b183111634f75baa039715e3f46ce860677d3b19a69fb229c"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
Component Group View with static header and without icons (#3373) Add an initial version of the visual component for displaying the Component Group View. The component contains a header (for displaying the Group Name) and a list of labels (for displaying the component names). https://www.pivotaltracker.com/story/show/181724889 #### Visuals A screenshot from a debug scene demonstrating the component: <img width="251" alt="Screenshot 2022-04-13 at 20 07 56" src="https://user-images.githubusercontent.com/273837/163243304-21c3ad78-4813-4368-b3bb-844d979da699.png"> Screenshots from other debug scenes (`list_view` and `text_area`), demonstrating that the other components still display correctly: <img width="202" alt="Screenshot 2022-04-13 at 20 08 56" src="https://user-images.githubusercontent.com/273837/163243428-de9dc1c7-5a9f-45e0-9325-db60cece9768.png"> <img width="403" alt="Screenshot 2022-04-13 at 20 08 48" src="https://user-images.githubusercontent.com/273837/163243432-895061d9-5bd9-4349-8679-eb63b0f6724d.png"> A screenshot of the Node Searcher's list, showing that long entries in a ListView are now truncated, and an ellipsis character is added in place of removed characters: <img width="651" alt="Screenshot 2022-04-13 at 20 10 16" src="https://user-images.githubusercontent.com/273837/163243664-5b671969-7aa0-4bef-8fd2-825602d85848.png"> # Important Notes - Adding support for the text truncation feature in `ListView` required some changes in the`list_view::Entry`-related APIs. - An embedded font was added (DejaVuSans-Bold) for use in the Component Group View debug scene, and 5 unused embedded fonts were removed.
2022-04-14 13:37:40 +03:00
[[package]]
name = "debug-scene-component-group"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
"ensogl-hardcoded-theme",
"ensogl-list-view",
"ensogl-text-msdf-sys",
"ide-view-component-group",
"wasm-bindgen",
]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
[[package]]
name = "debug-scene-interface"
version = "0.1.0"
dependencies = [
"ast",
"enso-frp",
"ensogl",
"ensogl-hardcoded-theme",
"ensogl-text-msdf-sys",
"ide-view",
"parser",
"span-tree",
"uuid",
"wasm-bindgen",
]
[[package]]
name = "debug-scene-visualization"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl",
"ensogl-hardcoded-theme",
"ensogl-text-msdf-sys",
"ide-view",
"js-sys",
"nalgebra 0.26.2",
"serde_json",
"wasm-bindgen",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "derivative"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
version = "2.2.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
checksum = "fcc3dd5e9e9c0b295d6e1e4d811fb6f157d5ffd784b8d202fc62eac8035a770b"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"syn",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
name = "derive_more"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.99.17"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "4fb810d30a7c1953f91334de7244731fc3f3c10d7fe163338a35b9f640960321"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"convert_case",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"rustc_version 0.4.0",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"syn",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "difference"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "524cbf6897b527295dff137cec09ecf3a05f4fddffd7dfcd1585403449e74198"
[[package]]
name = "digest"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f3d0c8c8752312f9713efd397ff63acb9f85585afbf179282e720e7704954dd5"
dependencies = [
"generic-array 0.12.4",
]
[[package]]
name = "double-representation"
version = "0.1.0"
dependencies = [
"ast",
"engine-protocol",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-logger",
"enso-prelude",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-text",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"failure",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itertools 0.10.3",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"parser",
"regex",
"serde",
"uuid",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "downcast"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4bb454f0228b18c7f4c3b0ebbee346ed9c52e7443b0999cd543ff3571205701d"
[[package]]
name = "dtoa"
version = "0.4.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56899898ce76aaf4a0f24d914c97ea6ed976d42fec6ad33fcbb0a1103e07b2b0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "either"
version = "1.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e78d4f1cc4ae33bbfc157ed5d5a5ef3bc29227303d595861deb238fcec4e9457"
[[package]]
name = "enclose"
version = "1.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1056f553da426e9c025a662efa48b52e62e0a3a7648aa2d15aeaaf7f0d329357"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "encoding_rs"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.8.31"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "9852635589dc9f9ea1b6fe9f05b50ef208c85c834a562f0c6abb1c475736ec2b"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"cfg-if 1.0.0",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "engine-protocol"
version = "0.1.0"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bytes 0.5.6",
"chrono",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-build-utilities",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-logger",
"enso-prelude",
"enso-shapely",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-text",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-web",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"failure",
"flatbuffers",
"flatc-rust",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures 0.3.21",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"hex",
"json-rpc",
"mockall",
"reqwest",
"serde",
"serde_json",
"sha3",
Backend Communication Profiling (#3382)
2022-04-19 14:30:29 +03:00
"strum",
"strum_macros",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"tokio",
"uuid",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"zip",
"zip-extensions",
]
[[package]]
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
name = "enso-automata"
version = "0.2.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"enso-prelude",
]
[[package]]
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
name = "enso-build-utilities"
version = "0.1.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"path-clean",
"reqwest",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "enso-callback"
version = "0.1.0"
dependencies = [
"enso-prelude",
]
[[package]]
name = "enso-config"
version = "0.1.0"
dependencies = [
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"config-reader",
"enso-logger",
"enso-prelude",
"ensogl",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"semver 1.0.7",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
name = "enso-data-structures"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.2.0"
dependencies = [
"criterion",
"enso-prelude",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"itertools 0.9.0",
"rustversion",
"serde",
"typenum",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
[[package]]
name = "enso-debug-scene"
version = "0.1.0"
dependencies = [
Component Group View with static header and without icons (#3373) Add an initial version of the visual component for displaying the Component Group View. The component contains a header (for displaying the Group Name) and a list of labels (for displaying the component names). https://www.pivotaltracker.com/story/show/181724889 #### Visuals A screenshot from a debug scene demonstrating the component: <img width="251" alt="Screenshot 2022-04-13 at 20 07 56" src="https://user-images.githubusercontent.com/273837/163243304-21c3ad78-4813-4368-b3bb-844d979da699.png"> Screenshots from other debug scenes (`list_view` and `text_area`), demonstrating that the other components still display correctly: <img width="202" alt="Screenshot 2022-04-13 at 20 08 56" src="https://user-images.githubusercontent.com/273837/163243428-de9dc1c7-5a9f-45e0-9325-db60cece9768.png"> <img width="403" alt="Screenshot 2022-04-13 at 20 08 48" src="https://user-images.githubusercontent.com/273837/163243432-895061d9-5bd9-4349-8679-eb63b0f6724d.png"> A screenshot of the Node Searcher's list, showing that long entries in a ListView are now truncated, and an ellipsis character is added in place of removed characters: <img width="651" alt="Screenshot 2022-04-13 at 20 10 16" src="https://user-images.githubusercontent.com/273837/163243664-5b671969-7aa0-4bef-8fd2-825602d85848.png"> # Important Notes - Adding support for the text truncation feature in `ListView` required some changes in the`list_view::Entry`-related APIs. - An embedded font was added (DejaVuSans-Bold) for use in the Component Group View debug scene, and 5 unused embedded fonts were removed.
2022-04-14 13:37:40 +03:00
"debug-scene-component-group",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"debug-scene-interface",
"debug-scene-visualization",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "enso-flexer"
version = "0.2.1"
dependencies = [
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"enso-automata",
"enso-lazy-reader",
"enso-logger",
"enso-macro-utils",
"enso-prelude",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"itertools 0.8.2",
"nonempty",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"syn",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"unicode-segmentation",
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
Init
2022-03-10 06:47:00 +03:00
[[package]]
name = "enso-formatter"
version = "0.1.0"
dependencies = [
"lazy_static",
"regex",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "enso-frp"
version = "0.1.0"
dependencies = [
"Inflector",
"enso-callback",
"enso-generics",
"enso-logger",
"enso-prelude",
Frp profiling stats (#3323)
2022-03-23 14:06:25 +03:00
"enso-profiler",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-web",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"keyboard-types",
"nalgebra 0.26.2",
"percent-encoding 2.1.0",
"unicode-segmentation",
"wasm-bindgen",
"web-sys",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
[[package]]
name = "enso-generics"
version = "0.2.0"
dependencies = [
"nalgebra 0.21.1",
"serde",
]
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
[[package]]
name = "enso-gui"
version = "0.1.0"
dependencies = [
"analytics",
"ast",
"bimap",
"console_error_panic_hook",
"double-representation",
"engine-protocol",
"enso-callback",
"enso-config",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"enso-debug-scene",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"enso-frp",
"enso-logger",
"enso-prelude",
Profiling framework: core performance-logging implementation (#3238) * profiling instrumentation * Support native testing with mock impl of `mod js` * Add benchmarks * Wrapper: support methods. * `#[profile]`: work in any context * feature-gate lineno info that breaks IDE * Support async; more docs; add perf analysis * docs & formatting
2022-02-10 20:24:29 +03:00
"enso-profiler",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"enso-shapely",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-text",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"enso-web",
"ensogl",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-component",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"ensogl-drop-manager",
"ensogl-examples",
Revert "Implement basic performance logging API. (#3169)" This reverts commit 178cfb0404909ed7b8d45abf1d0951157cc29b78.
2022-01-14 15:40:03 +03:00
"ensogl-hardcoded-theme",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"ensogl-text-msdf-sys",
"failure",
"flo_stream",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures 0.3.21",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"fuzzly",
"ide-view",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itertools 0.10.3",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"js-sys",
"json-rpc",
"mockall",
"nalgebra 0.26.2",
"parser",
"regex",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"semver 1.0.7",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"serde",
"serde_json",
"sha3",
"span-tree",
"uuid",
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactor gui/src/rust/ide to two app/gui and app/ide-desktop (#3157)
2021-11-16 12:04:56 +03:00
"web-sys",
"websocket",
]
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
[[package]]
name = "enso-integration-test"
version = "0.1.0"
dependencies = [
Add tests for debug mode and zoom restriction. (#3289) This PR adds integration tests created during acceptance process of [181181159](https://www.pivotaltracker.com/story/show/181181159) and [181181203](https://www.pivotaltracker.com/story/show/181181203). The PRs for those tasks were merged, because I hadn't realized they should not. Additionally, as the `wasm-bindgen` version was bumped, I extended the timeout of integration tests and made them headless.
2022-02-22 19:43:37 +03:00
"approx 0.5.1",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"enso-frp",
"enso-gui",
"enso-prelude",
The EnsoGL Component abstraction with special dropping behavior (#3322) In this branch: * The workaround for cursor-not-being-updated-after-closing-searcher bug (discovered while testing #3278) is reverted. * The proper fix was introduced: created an abstraction for EnsoGL component, which, when dropping, will not immediately drop the FRP network and model, but instead put it into the Garbage Collector. The Collector ensures, that all "component hiding" effects and events will be handled, and drops FRP network and model only after that. * I run clippy for wasm32 target out of curiosity. There was one warning, and I fixed it on this branch.
2022-04-04 18:55:55 +03:00
"enso-shortcuts",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"enso-web",
"ensogl",
Return creating node with (+) button & fix a regression (#3338) * Creating a new node with the (+) button (#3278) [The Task](https://www.pivotaltracker.com/story/show/180887253) A new (+) button on the left-bottom corner appeared. It may be clicked to open searcher in the middle of the scene, as an alternative to tab key. https://user-images.githubusercontent.com/3919101/154514279-7972ed6a-0203-47cb-9a09-82dba948cf2f.mp4 * The window_control_buttons::common was extracted to separate crate `ensogl-component-button` almost without change. * This includes a severe refactoring of adding nodes in general in the Graph Editor. The whole responsibility of adding new nodes (and starting their editing) was moved to Graph Editor - the Project View only reacts for GE events to show searcher properly. * The status bar was moved from the bottom-left corner to the middle-top of the scene. It does not collide with (+) button, and plays "notification" role anyway. * The `interface` debug scene was buggy. The problem was with one expression's span-tree. When I replaced it, the scene works. * I've removed "new searcher" API, as it is completely outdated. * I've changed code owners of integration tests to GUI team, as it is the team writing mostly the integration tests (int rust) * Fix regression #181528359 * Add docs & remove unused function * Fix & enable native Rust tests * Fix formatting Co-authored-by: Adam Obuchowicz <adam.obuchowicz@enso.org> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-03-16 21:02:47 +03:00
"ordered-float 2.10.0",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen",
"wasm-bindgen-test",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "enso-lazy-reader"
version = "0.2.0"
dependencies = [
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"enso-prelude",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"itertools 0.8.2",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "enso-logger"
version = "0.3.1"
dependencies = [
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"enso-prelude",
"enso-shapely",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"js-sys",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "enso-macro-utils"
version = "0.2.0"
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"syn",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
[[package]]
name = "enso-optics"
version = "0.2.0"
dependencies = [
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"enso-prelude",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "enso-prelude"
version = "0.2.6"
dependencies = [
"anyhow",
"backtrace",
"boolinator",
"bumpalo",
"cfg-if 1.0.0",
"colored",
"derivative",
"derive_more",
"enclose",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"enso-shapely",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"failure",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures 0.3.21",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"ifmt",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itertools 0.10.3",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"lazy_static",
"nalgebra 0.26.2",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"num",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"object 0.24.0",
Revert "Revert "Fixed rate animation loop fixes"" (#3399)
2022-04-14 20:58:53 +03:00
"paste 1.0.7",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"serde",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"serde_json",
"shrinkwraprs 0.3.0",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"smallvec 1.8.0",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"weak-table",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"web-sys",
]
Profiling framework: core performance-logging implementation (#3238) * profiling instrumentation * Support native testing with mock impl of `mod js` * Add benchmarks * Wrapper: support methods. * `#[profile]`: work in any context * feature-gate lineno info that breaks IDE * Support async; more docs; add perf analysis * docs & formatting
2022-02-10 20:24:29 +03:00
[[package]]
name = "enso-profiler"
version = "0.1.0"
dependencies = [
"enso-profiler-macros",
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
"enso-web",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures 0.3.21",
API for storing metadata (#3291) API for storing metadata. See: https://www.pivotaltracker.com/story/show/181149277 # Important Notes **New APIs**: - Storing metadata is implemented with `profiler::MetadataLogger`. - A full metadata storage/retrieval example is in [the top-level doctests](https://github.com/enso-org/enso/blob/wip/kw/profiling-metadata-api/lib/rust/profiler/data/src/lib.rs) for profiler::data, a crate which implements an API for profiling data consumers (it abstracts away the low-level details of the event log, and checks its invariants in the process) [after review of this new API here I'll open a PR to add it to the design doc]. **Implementation**: - `profiler::Event` is parameterized by a metadata type, so that different types of metadata can be dependency-injected into it. - A data consumer defines its metadata type as an enum of all the kinds of metadata it is interested in. - Producing the metadata enum is accomplished without defining its type (which would require dependencies from around the app): A `MetadataLogger` internally use a serialization helper `Variant` to serialize its variant of the metadata enum without knowledge of the other possible variants. **Performance impact**: still in the low ns/measurement range, comparable to pushing to a vec. *Note*: `LocalVecBuilder` is currently present under the name `Log`, which is accurate but probably too overloaded. I'd like to find the right name for it, document it with examples, and move it to its own crate under data-structures, but I don't want doing that to hold up this PR.
2022-02-28 12:55:56 +03:00
"serde",
"serde_json",
Profiling framework: core performance-logging implementation (#3238) * profiling instrumentation * Support native testing with mock impl of `mod js` * Add benchmarks * Wrapper: support methods. * `#[profile]`: work in any context * feature-gate lineno info that breaks IDE * Support async; more docs; add perf analysis * docs & formatting
2022-02-10 20:24:29 +03:00
"wasm-bindgen",
]
API for storing metadata (#3291) API for storing metadata. See: https://www.pivotaltracker.com/story/show/181149277 # Important Notes **New APIs**: - Storing metadata is implemented with `profiler::MetadataLogger`. - A full metadata storage/retrieval example is in [the top-level doctests](https://github.com/enso-org/enso/blob/wip/kw/profiling-metadata-api/lib/rust/profiler/data/src/lib.rs) for profiler::data, a crate which implements an API for profiling data consumers (it abstracts away the low-level details of the event log, and checks its invariants in the process) [after review of this new API here I'll open a PR to add it to the design doc]. **Implementation**: - `profiler::Event` is parameterized by a metadata type, so that different types of metadata can be dependency-injected into it. - A data consumer defines its metadata type as an enum of all the kinds of metadata it is interested in. - Producing the metadata enum is accomplished without defining its type (which would require dependencies from around the app): A `MetadataLogger` internally use a serialization helper `Variant` to serialize its variant of the metadata enum without knowledge of the other possible variants. **Performance impact**: still in the low ns/measurement range, comparable to pushing to a vec. *Note*: `LocalVecBuilder` is currently present under the name `Log`, which is accurate but probably too overloaded. I'd like to find the right name for it, document it with examples, and move it to its own crate under data-structures, but I don't want doing that to hold up this PR.
2022-02-28 12:55:56 +03:00
[[package]]
name = "enso-profiler-data"
version = "0.1.0"
dependencies = [
Profiling: intervals tool and devtools-file generator (#3359) * Profiling: intervals tool * devtools profile generator * docs * ignore open intervals, because devtools does * intervals tool: show interval counts * Re-add a doc comment. Was accidentally deleted. * Implement review. * DURATION_FLOOR_MS * Rename methods that apply a profile's contents to self * Description of chrome format * Link to profile.json format documentation is design doc * Implement profiling-level switch described in design doc * lint
2022-04-11 16:08:09 +03:00
"enso-prelude",
API for storing metadata (#3291) API for storing metadata. See: https://www.pivotaltracker.com/story/show/181149277 # Important Notes **New APIs**: - Storing metadata is implemented with `profiler::MetadataLogger`. - A full metadata storage/retrieval example is in [the top-level doctests](https://github.com/enso-org/enso/blob/wip/kw/profiling-metadata-api/lib/rust/profiler/data/src/lib.rs) for profiler::data, a crate which implements an API for profiling data consumers (it abstracts away the low-level details of the event log, and checks its invariants in the process) [after review of this new API here I'll open a PR to add it to the design doc]. **Implementation**: - `profiler::Event` is parameterized by a metadata type, so that different types of metadata can be dependency-injected into it. - A data consumer defines its metadata type as an enum of all the kinds of metadata it is interested in. - Producing the metadata enum is accomplished without defining its type (which would require dependencies from around the app): A `MetadataLogger` internally use a serialization helper `Variant` to serialize its variant of the metadata enum without knowledge of the other possible variants. **Performance impact**: still in the low ns/measurement range, comparable to pushing to a vec. *Note*: `LocalVecBuilder` is currently present under the name `Log`, which is accurate but probably too overloaded. I'd like to find the right name for it, document it with examples, and move it to its own crate under data-structures, but I don't want doing that to hold up this PR.
2022-02-28 12:55:56 +03:00
"enso-profiler",
"futures 0.3.21",
"serde",
"serde_json",
]
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
[[package]]
name = "enso-profiler-enso-data"
version = "0.1.0"
dependencies = [
"chrono",
"csv",
"enso-profiler",
"enso-profiler-data",
"ensogl-core",
"serde",
]
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
[[package]]
name = "enso-profiler-flame-graph"
version = "0.1.0"
dependencies = [
"enso-profiler",
"enso-profiler-data",
"futures 0.3.21",
]
Profiling framework: core performance-logging implementation (#3238) * profiling instrumentation * Support native testing with mock impl of `mod js` * Add benchmarks * Wrapper: support methods. * `#[profile]`: work in any context * feature-gate lineno info that breaks IDE * Support async; more docs; add perf analysis * docs & formatting
2022-02-10 20:24:29 +03:00
[[package]]
name = "enso-profiler-macros"
version = "0.1.0"
dependencies = [
"Inflector",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Profiling framework: core performance-logging implementation (#3238) * profiling instrumentation * Support native testing with mock impl of `mod js` * Add benchmarks * Wrapper: support methods. * `#[profile]`: work in any context * feature-gate lineno info that breaks IDE * Support async; more docs; add perf analysis * docs & formatting
2022-02-10 20:24:29 +03:00
"syn",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "enso-shapely"
version = "0.2.0"
dependencies = [
"derivative",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"enso-prelude",
"enso-shapely-macros",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"paste 0.1.18",
"rustversion",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"shrinkwraprs 0.3.0",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
[[package]]
name = "enso-shapely-macros"
version = "0.2.1"
dependencies = [
"Inflector",
"boolinator",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"enso-macro-utils",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"itertools 0.8.2",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"syn",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "enso-shortcuts"
version = "0.1.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-automata",
"enso-frp",
"enso-logger",
"enso-prelude",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-web",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"js-sys",
"nalgebra 0.26.2",
"serde",
"serde_json",
"wasm-bindgen",
"web-sys",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
[[package]]
name = "enso-text"
version = "0.1.0"
dependencies = [
"enso-prelude",
"enso-types",
"serde",
"xi-rope",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "enso-types"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
version = "0.1.0"
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"assert_approx_eq",
"nalgebra 0.26.2",
"num-traits",
Revert "Revert "Fixed rate animation loop fixes"" (#3399)
2022-04-14 20:58:53 +03:00
"paste 1.0.7",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
[[package]]
name = "enso-web"
version = "0.1.0"
dependencies = [
"async-std",
"console_error_panic_hook",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-logger",
"enso-prelude",
"failure",
"gloo-timers",
"js-sys",
"nalgebra 0.26.2",
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"web-sys",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "ensogl"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
version = "0.1.0"
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"ensogl-core",
"ensogl-text",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Return creating node with (+) button & fix a regression (#3338) * Creating a new node with the (+) button (#3278) [The Task](https://www.pivotaltracker.com/story/show/180887253) A new (+) button on the left-bottom corner appeared. It may be clicked to open searcher in the middle of the scene, as an alternative to tab key. https://user-images.githubusercontent.com/3919101/154514279-7972ed6a-0203-47cb-9a09-82dba948cf2f.mp4 * The window_control_buttons::common was extracted to separate crate `ensogl-component-button` almost without change. * This includes a severe refactoring of adding nodes in general in the Graph Editor. The whole responsibility of adding new nodes (and starting their editing) was moved to Graph Editor - the Project View only reacts for GE events to show searcher properly. * The status bar was moved from the bottom-left corner to the middle-top of the scene. It does not collide with (+) button, and plays "notification" role anyway. * The `interface` debug scene was buggy. The problem was with one expression's span-tree. When I replaced it, the scene works. * I've removed "new searcher" API, as it is completely outdated. * I've changed code owners of integration tests to GUI team, as it is the team writing mostly the integration tests (int rust) * Fix regression #181528359 * Add docs & remove unused function * Fix & enable native Rust tests * Fix formatting Co-authored-by: Adam Obuchowicz <adam.obuchowicz@enso.org> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-03-16 21:02:47 +03:00
[[package]]
name = "ensogl-button"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
name = "ensogl-component"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.1.0"
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
dependencies = [
Return creating node with (+) button & fix a regression (#3338) * Creating a new node with the (+) button (#3278) [The Task](https://www.pivotaltracker.com/story/show/180887253) A new (+) button on the left-bottom corner appeared. It may be clicked to open searcher in the middle of the scene, as an alternative to tab key. https://user-images.githubusercontent.com/3919101/154514279-7972ed6a-0203-47cb-9a09-82dba948cf2f.mp4 * The window_control_buttons::common was extracted to separate crate `ensogl-component-button` almost without change. * This includes a severe refactoring of adding nodes in general in the Graph Editor. The whole responsibility of adding new nodes (and starting their editing) was moved to Graph Editor - the Project View only reacts for GE events to show searcher properly. * The status bar was moved from the bottom-left corner to the middle-top of the scene. It does not collide with (+) button, and plays "notification" role anyway. * The `interface` debug scene was buggy. The problem was with one expression's span-tree. When I replaced it, the scene works. * I've removed "new searcher" API, as it is completely outdated. * I've changed code owners of integration tests to GUI team, as it is the team writing mostly the integration tests (int rust) * Fix regression #181528359 * Add docs & remove unused function * Fix & enable native Rust tests * Fix formatting Co-authored-by: Adam Obuchowicz <adam.obuchowicz@enso.org> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-03-16 21:02:47 +03:00
"ensogl-button",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-drop-down-menu",
"ensogl-drop-manager",
"ensogl-file-browser",
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
"ensogl-flame-graph",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-label",
"ensogl-list-view",
"ensogl-scroll-area",
"ensogl-scrollbar",
"ensogl-selector",
"ensogl-shadow",
"ensogl-text",
"ensogl-toggle-button",
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "ensogl-core"
version = "0.1.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"Inflector",
"assert_approx_eq",
"bit_field",
"code-builder",
"console_error_panic_hook",
"enso-callback",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-frp",
"enso-generics",
"enso-logger",
"enso-optics",
"enso-prelude",
Generate reports about profiling results of top-level sections of the application. (#3306)
2022-03-15 05:12:39 +03:00
"enso-profiler",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-shapely",
"enso-shortcuts",
"enso-types",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-web",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"ensogl-text-embedded-fonts",
"ensogl-text-msdf-sys",
"enum_dispatch",
"failure",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itertools 0.10.3",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"js-sys",
"nalgebra 0.26.2",
"num-traits",
"num_enum",
"rustc-hash",
Backend Communication Profiling (#3382)
2022-04-19 14:30:29 +03:00
"serde",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"shrinkwraprs 0.3.0",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"smallvec 1.8.0",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"typenum",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"web-sys",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
[[package]]
name = "ensogl-drop-down-menu"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
"ensogl-hardcoded-theme",
"ensogl-list-view",
"ensogl-text",
]
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
[[package]]
name = "ensogl-drop-manager"
version = "0.1.0"
dependencies = [
"enso-frp",
"enso-logger",
"enso-prelude",
"enso-web",
"js-sys",
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-futures",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"web-sys",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
name = "ensogl-example-animation"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.1.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-frp",
"enso-prelude",
"ensogl-core",
"ensogl-text-msdf-sys",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-complex-shape-system"
version = "0.1.0"
dependencies = [
"ensogl-core",
"wasm-bindgen",
]
Allowing EnsoGL mouse to interact with more than 4096 sprites (#3369)
2022-03-30 05:50:55 +03:00
[[package]]
name = "ensogl-example-custom-shape-system"
version = "0.1.0"
dependencies = [
"enso-frp",
"enso-profiler",
"ensogl-core",
"wasm-bindgen",
]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
[[package]]
name = "ensogl-example-dom-symbols"
version = "0.1.0"
dependencies = [
"ensogl-core",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"nalgebra 0.26.2",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-drop-manager"
version = "0.1.0"
dependencies = [
"enso-frp",
"enso-prelude",
"ensogl-core",
"ensogl-drop-manager",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-futures",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
]
[[package]]
name = "ensogl-example-easing-animator"
version = "0.1.0"
dependencies = [
"ensogl-core",
"js-sys",
"nalgebra 0.26.2",
"wasm-bindgen",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"web-sys",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
name = "ensogl-example-glyph-system"
version = "0.1.0"
dependencies = [
"ensogl-core",
"ensogl-text",
"ensogl-text-msdf-sys",
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-list-view"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.1.0"
dependencies = [
"enso-frp",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"enso-text",
"ensogl-core",
"ensogl-hardcoded-theme",
"ensogl-list-view",
"ensogl-text-msdf-sys",
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-mouse-events"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
"ensogl-text-msdf-sys",
"wasm-bindgen",
]
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
[[package]]
name = "ensogl-example-profiling-run-graph"
version = "0.1.0"
dependencies = [
"enso-frp",
"enso-profiler",
Backend Communication Profiling (#3382)
2022-04-19 14:30:29 +03:00
"enso-profiler-data",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"enso-profiler-enso-data",
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
"enso-profiler-flame-graph",
"enso-web",
"ensogl-core",
"ensogl-flame-graph",
"ensogl-hardcoded-theme",
"ensogl-text",
"ensogl-text-msdf-sys",
"futures 0.3.21",
Backend Communication Profiling (#3382)
2022-04-19 14:30:29 +03:00
"serde",
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
"wasm-bindgen",
Backend Communication Profiling (#3382)
2022-04-19 14:30:29 +03:00
"wasm-bindgen-futures",
"web-sys",
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
]
Generate reports about profiling results of top-level sections of the application. (#3306)
2022-03-15 05:12:39 +03:00
[[package]]
name = "ensogl-example-render-profile"
version = "0.1.0"
dependencies = [
"enso-frp",
"enso-profiler",
"enso-profiler-data",
"enso-profiler-flame-graph",
"enso-web",
"ensogl-core",
"ensogl-flame-graph",
"ensogl-hardcoded-theme",
"ensogl-text",
"ensogl-text-msdf-sys",
"futures 0.3.21",
"wasm-bindgen",
"wasm-bindgen-futures",
"web-sys",
]
Profiling application details (#3332) * Profiling application details Add enough profiling to account for every missed frame during startup. See https://www.pivotaltracker.com/story/show/181499507 * Build ActiveInterval hierarchy in profiler_data * update doctests / await_! * docs/formatting/naming * more graph modes * increase WASM size Due to new render-profile-flamegraph scene. We should remove these from the main release WASM blob one way or another. * lint * fix a test * Organization (feedback) * Add @wdanilo to Cargo.lock CODEOWNERS As discussed after my previous PR got stuck waiting for Cargo.lock review. * fix doctests * Update docs. Removed a limitation.
2022-03-21 21:09:56 +03:00
[[package]]
name = "ensogl-example-render-profile-flamegraph"
version = "0.1.0"
dependencies = [
"enso-frp",
"enso-profiler",
"enso-profiler-data",
"enso-profiler-flame-graph",
"enso-web",
"ensogl-core",
"ensogl-flame-graph",
"ensogl-hardcoded-theme",
"ensogl-text",
"ensogl-text-msdf-sys",
"futures 0.3.21",
"wasm-bindgen",
"wasm-bindgen-futures",
"web-sys",
]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
[[package]]
name = "ensogl-example-scroll-area"
version = "0.1.0"
dependencies = [
"ensogl-core",
"ensogl-hardcoded-theme",
"ensogl-scroll-area",
"ensogl-text-msdf-sys",
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-shape-system"
version = "0.1.0"
dependencies = [
Allowing EnsoGL mouse to interact with more than 4096 sprites (#3369)
2022-03-30 05:50:55 +03:00
"enso-profiler",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-core",
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-slider"
version = "0.1.0"
dependencies = [
"ensogl-core",
"ensogl-hardcoded-theme",
"ensogl-selector",
"ensogl-text-msdf-sys",
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-sprite-system"
version = "0.1.0"
dependencies = [
EnsoGL context abstraction (#3293)
2022-03-04 17:13:23 +03:00
"enso-web",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-core",
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-sprite-system-benchmark"
version = "0.1.0"
dependencies = [
"ensogl-core",
"nalgebra 0.26.2",
"wasm-bindgen",
]
[[package]]
name = "ensogl-example-text-area"
version = "0.1.0"
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"ensogl-core",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"ensogl-hardcoded-theme",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"ensogl-text",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-text-msdf-sys",
"wasm-bindgen",
]
[[package]]
name = "ensogl-examples"
version = "0.1.0"
dependencies = [
"ensogl-example-animation",
"ensogl-example-complex-shape-system",
Allowing EnsoGL mouse to interact with more than 4096 sprites (#3369)
2022-03-30 05:50:55 +03:00
"ensogl-example-custom-shape-system",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-example-dom-symbols",
"ensogl-example-drop-manager",
"ensogl-example-easing-animator",
"ensogl-example-glyph-system",
"ensogl-example-list-view",
"ensogl-example-mouse-events",
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
"ensogl-example-profiling-run-graph",
Generate reports about profiling results of top-level sections of the application. (#3306)
2022-03-15 05:12:39 +03:00
"ensogl-example-render-profile",
Profiling application details (#3332) * Profiling application details Add enough profiling to account for every missed frame during startup. See https://www.pivotaltracker.com/story/show/181499507 * Build ActiveInterval hierarchy in profiler_data * update doctests / await_! * docs/formatting/naming * more graph modes * increase WASM size Due to new render-profile-flamegraph scene. We should remove these from the main release WASM blob one way or another. * lint * fix a test * Organization (feedback) * Add @wdanilo to Cargo.lock CODEOWNERS As discussed after my previous PR got stuck waiting for Cargo.lock review. * fix doctests * Update docs. Removed a limitation.
2022-03-21 21:09:56 +03:00
"ensogl-example-render-profile-flamegraph",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-example-scroll-area",
"ensogl-example-shape-system",
"ensogl-example-slider",
"ensogl-example-sprite-system",
"ensogl-example-sprite-system-benchmark",
"ensogl-example-text-area",
]
[[package]]
name = "ensogl-file-browser"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
]
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
[[package]]
name = "ensogl-flame-graph"
version = "0.1.0"
dependencies = [
"enso-frp",
"enso-profiler",
"enso-profiler-flame-graph",
"ensogl",
"ensogl-core",
"ensogl-gui-component",
"ensogl-hardcoded-theme",
"ensogl-text",
]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
[[package]]
name = "ensogl-gui-component"
version = "0.1.0"
dependencies = [
"enso-frp",
"enso-logger",
"ensogl-core",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"float_eq",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
name = "ensogl-hardcoded-theme"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.1.0"
dependencies = [
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"ensogl-core",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
[[package]]
name = "ensogl-label"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
"ensogl-hardcoded-theme",
"ensogl-shadow",
"ensogl-text",
]
[[package]]
name = "ensogl-list-view"
version = "0.1.0"
dependencies = [
Selectable Header in Component Group View. (#3418) * The List View component was refactored: it allows for hiding the internal selection widget, and exposes information where the widget should be placed. This allows us to create selection widget in component list panel, so it can be animated between component groups and sections. * Fixed some warnings when checking WASM code. * Adjusted the style of Component Group View a little, so it better reflects the design doc. Still not ideal, because the list_view has some weird design regarding padding, but I don't want to stuck in some bigger refactoring. I will add a video in a few minutes. # Important Notes https://user-images.githubusercontent.com/3919101/165507826-60329f9e-7de3-4eb2-9271-292e45568cb2.mov
2022-04-30 17:48:52 +03:00
"approx 0.5.1",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"enso-frp",
"ensogl-core",
"ensogl-hardcoded-theme",
"ensogl-shadow",
"ensogl-text",
]
[[package]]
name = "ensogl-scroll-area"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
"ensogl-scrollbar",
]
[[package]]
name = "ensogl-scrollbar"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
"ensogl-gui-component",
"ensogl-hardcoded-theme",
"ensogl-selector",
]
[[package]]
name = "ensogl-selector"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
"ensogl-hardcoded-theme",
"ensogl-shadow",
"ensogl-text",
"ensogl-toggle-button",
"float_eq",
]
[[package]]
name = "ensogl-shadow"
version = "0.1.0"
dependencies = [
"ensogl-core",
"ensogl-hardcoded-theme",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "ensogl-text"
version = "0.1.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
SDF-based mechanism for making letters bold (#3385) Fixes [181641027](https://www.pivotaltracker.com/story/show/181641027). There are new methods of text::Area for making some letters bolder, without moving them nor any other letters in the line. Tested on DejaVuSans text: ![image](https://user-images.githubusercontent.com/3919101/162199723-524f7560-535f-4c98-bcb4-6b760ad8cb04.png) ![image](https://user-images.githubusercontent.com/3919101/162199806-e6582c56-3071-4653-8ad2-114df86cd6b7.png) ![image](https://user-images.githubusercontent.com/3919101/162199880-1836e902-8663-4696-bcb7-2b15c3c243c6.png) On MacOS: <img width="824" alt="Screenshot 2022-04-07 at 14 54 40" src="https://user-images.githubusercontent.com/3919101/162203730-ffda3096-7aab-443f-a45a-bfa18784ba36.png"> <img width="379" alt="Screenshot 2022-04-07 at 14 54 52" src="https://user-images.githubusercontent.com/3919101/162203751-f5ca2e26-fdb6-4521-9821-999111b80ac0.png"> <img width="160" alt="Screenshot 2022-04-07 at 14 54 58" src="https://user-images.githubusercontent.com/3919101/162203769-3c367f81-67bb-48aa-994c-42eeb131017e.png">
2022-04-12 20:39:08 +03:00
"const_format",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-frp",
"enso-prelude",
"enso-shapely",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-text",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-types",
"ensogl-core",
"ensogl-text-embedded-fonts",
"ensogl-text-msdf-sys",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"xi-rope",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "ensogl-text-embedded-fonts"
version = "0.1.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-build-utilities",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-prelude",
"zip",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "ensogl-text-msdf-sys"
version = "0.1.0"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-build-utilities",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-prelude",
"ensogl-text-embedded-fonts",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures 0.3.21",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"js-sys",
"nalgebra 0.26.2",
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
[[package]]
name = "ensogl-toggle-button"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "enum_dispatch"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.8"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "0eb359f1476bf611266ac1f5355bc14aeca37b299d0ebccc038ee7058891c9cb"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"once_cell",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "event-listener"
version = "2.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "77f3309417938f28bf8228fcff79a4a37103981e3e186d2ccd19c74b38f4eb71"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "failure"
version = "0.1.8"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "d32e9bd16cc02eae7db7ef620b392808b89f6a5e16bb3497d159c6b92a0f4f86"
dependencies = [
"backtrace",
"failure_derive",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "failure_derive"
version = "0.1.8"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "aa4da3c766cd7a0db8242e326e9e4e081edd567072893ed320008189715366a4"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
"synstructure",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "fastrand"
version = "1.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3fcf0cee53519c866c09b5de1f6c56ff9d647101f81c1964fa632e148896cdf"
dependencies = [
"instant",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "flatbuffers"
version = "0.5.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "ea0c34f669be9911826facafe996adfda978aeee67285a13556869e2d8b8331f"
dependencies = [
"smallvec 0.6.14",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "flatc-rust"
version = "0.1.3"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "fdce2ac68e3bccc405e0255e9b56d7841c06f6c7d36a8aa8b2966fbb3995bd9a"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "flate2"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.0.23"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "b39522e96686d38f4bc984b9198e3a0613264abaebaff2c5c918bfa6b6da09af"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"cfg-if 1.0.0",
"crc32fast",
"libc",
"miniz_oxide",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "flo_stream"
version = "0.4.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "b02e0d3667b27514149c1ac9b372d700f3e6df4bbaf6b7c5df12915de2996049"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures 0.3.21",
"smallvec 1.8.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "float-cmp"
version = "0.8.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "e1267f4ac4f343772758f7b1bdcbe767c218bbab93bb432acbf5162bbf85a6c4"
dependencies = [
"num-traits",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "float_eq"
version = "0.5.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "fb23b6902f3cdc0544f9916b4c092f46f4ff984e219d5a0c538b6b3539885af3"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "fnv"
version = "1.0.7"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "foreign-types"
version = "0.3.2"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"foreign-types-shared",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "foreign-types-shared"
version = "0.1.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "form_urlencoded"
version = "1.0.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "5fc25a87fa4fd2094bffb06925852034d90a17f0d1e05197d4956d3555752191"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"matches",
"percent-encoding 2.1.0",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "fragile"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.2.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "e9d758e60b45e8d749c89c1b389ad8aee550f86aa12e2b9298b546dda7a82ab1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "fuchsia-cprng"
version = "0.1.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "fuchsia-zircon"
version = "0.3.3"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bitflags",
"fuchsia-zircon-sys",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "fuchsia-zircon-sys"
version = "0.3.3"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "futures"
version = "0.1.31"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "3a471a38ef8ed83cd6e40aa59c1ffe17db6855c18e3604d9c4ed8c08ebc28678"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "futures"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "f73fe65f54d1e12b726f517d3e2135ca3125a437b6d998caf1962961f7172d9e"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"futures-channel",
"futures-core",
"futures-executor",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "futures-channel"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "c3083ce4b914124575708913bca19bfe887522d6e2e6d0952943f5eac4a74010"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"futures-core",
"futures-sink",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "futures-core"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "0c09fd04b7e4073ac7156a9539b57a484a8ea920f79c7c675d05d289ab6110d3"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "futures-executor"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "9420b90cfa29e327d0429f19be13e7ddb68fa1cccb09d65e5706b8c7a749b8a6"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"futures-core",
"futures-task",
"futures-util",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "futures-io"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "fc4045962a5a5e935ee2fdedaa4e08284547402885ab326734432bed5d12966b"
[[package]]
name = "futures-lite"
version = "1.12.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7694489acd39452c77daa48516b894c153f192c3578d5a839b62c58099fcbf48"
dependencies = [
"fastrand",
"futures-core",
"futures-io",
"memchr",
"parking",
"pin-project-lite 0.2.8",
"waker-fn",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "futures-macro"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "33c1e13800337f4d4d7a316bf45a567dbcb6ffe087f16424852d97e97a91f512"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "futures-sink"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "21163e139fa306126e6eedaf49ecdb4588f939600f0b1e770f4205ee4b7fa868"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "futures-task"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "57c66a976bf5909d801bbef33416c41372779507e7a6b3a5e25e4749c58f776a"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "futures-util"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.21"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "d8b7abd5d659d9b90c8cba917f6ec750a74e2dc23902ef9cd4cc8c8b22e6036a"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"futures-channel",
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"pin-project-lite 0.2.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"pin-utils",
"slab",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "fuzzly"
version = "0.1.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-prelude",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "generic-array"
version = "0.12.4"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "ffdf9f34f1447443d37393cc6c2b8313aebddcd96906caf34e54c68d8e57d7bd"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"typenum",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "generic-array"
version = "0.13.3"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "f797e67af32588215eaaab8327027ee8e71b9dd0b2b26996aedf20c030fce309"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"typenum",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "getrandom"
version = "0.1.16"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "8fc3cb4d91f53b50155bdcfd23f6a4c39ae1969c2ae85982b135750cccaf5fce"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"cfg-if 1.0.0",
"libc",
"wasi 0.9.0+wasi-snapshot-preview1",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "getrandom"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.2.6"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "9be70c98951c83b8d2f8f60d7065fa6d5146873094452a1008da8c2f1e4205ad"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"cfg-if 1.0.0",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"js-sys",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"libc",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"wasi 0.10.0+wasi-snapshot-preview1",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"wasm-bindgen",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "gimli"
version = "0.26.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "78cc372d058dcf6d5ecd98510e7fbc9e5aec4d21de70f65fea8fecebcd881bd4"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
[[package]]
name = "glob"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "gloo-timers"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.2.4"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "5fb7d06c1c8cc2a29bee7ec961009a0b2caa0793ee4900c2ffb348734ba1c8f9"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"futures-channel",
"futures-core",
"js-sys",
"wasm-bindgen",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "h2"
version = "0.2.7"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "5e4728fd124914ad25e99e3d15a9361a879f6620f63cb56bbb08f95abb97a535"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bytes 0.5.6",
"fnv",
"futures-core",
"futures-sink",
"futures-util",
"http",
"indexmap",
"slab",
"tokio",
"tokio-util",
"tracing",
"tracing-futures",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "half"
version = "1.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eabb4a44450da02c90444cf74558da904edde8fb4e9035a9a6a4e15445af0bd7"
[[package]]
name = "hashbrown"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ab5ef0d4909ef3724cc8cce6ccc8572c5c817592e9285f5464f8e86f8bd3726e"
Backend Communication Profiling (#3382)
2022-04-19 14:30:29 +03:00
[[package]]
name = "heck"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2540771e65fc8cb83cd6e8a237f70c319bd5c29f78ed1084ba5d50eeac86f7f9"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "hermit-abi"
version = "0.1.19"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "62b467343b94ba476dcb2500d242dadbb39557df889310ac77c5d99100aaac33"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"libc",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "hex"
version = "0.4.3"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "http"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.6"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "31f4c6746584866f0feabcc69893c5b51beef3831656a968ed7ae254cdc4fd03"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bytes 1.1.0",
"fnv",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itoa 1.0.1",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "http-body"
version = "0.3.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "13d5ff830006f7646652e057693569bfe0d51760c0085a071769d142a205111b"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bytes 0.5.6",
"http",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "httparse"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.7.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "6330e8a36bd8c859f3fa6d9382911fbb7147ec39807f63b923933a247240b9ba"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "httpdate"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "494b4d60369511e7dea41cf646832512a94e542f68bb9c49e54518e0f468eb47"
[[package]]
name = "hyper"
version = "0.10.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0a0652d9a2609a968c14be1a9ea00bf4b1d64e2e1f53a1b51b6fff3a6e829273"
dependencies = [
"base64 0.9.3",
"httparse",
"language-tags",
"log 0.3.9",
"mime 0.2.6",
"num_cpus",
"time",
"traitobject",
"typeable",
"unicase 1.4.2",
"url 1.7.2",
]
[[package]]
name = "hyper"
version = "0.13.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a6f157065790a3ed2f88679250419b5cdd96e714a0d65f7797fd337186e96bb"
dependencies = [
"bytes 0.5.6",
"futures-channel",
"futures-core",
"futures-util",
"h2",
"http",
"http-body",
"httparse",
"httpdate",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itoa 0.4.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"pin-project",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"socket2 0.3.19",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"tokio",
"tower-service",
"tracing",
"want",
]
[[package]]
name = "hyper-tls"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d979acc56dcb5b8dddba3917601745e877576475aa046df3226eabdecef78eed"
dependencies = [
"bytes 0.5.6",
"hyper 0.13.10",
"native-tls",
"tokio",
"tokio-tls 0.3.1",
]
[[package]]
name = "ide-view"
version = "0.1.0"
dependencies = [
"ast",
"engine-protocol",
"enso-config",
"enso-frp",
"enso-logger",
"enso-prelude",
"enso-shapely",
"ensogl",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-component",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"ensogl-hardcoded-theme",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"ensogl-text",
"ensogl-text-msdf-sys",
"ide-view-graph-editor",
"js-sys",
Developers should find the ide-gui controller codebase logical and easy to work with. (#3188)
2021-12-15 13:40:14 +03:00
"multi-map",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"nalgebra 0.26.2",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"ordered-float 2.10.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"parser",
"serde",
"serde_json",
"span-tree",
"uuid",
"wasm-bindgen",
"web-sys",
Add Root View and Welcome Screen View (#3164)
2021-11-30 18:23:46 +03:00
"welcome-screen",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
Component Group View with static header and without icons (#3373) Add an initial version of the visual component for displaying the Component Group View. The component contains a header (for displaying the Group Name) and a list of labels (for displaying the component names). https://www.pivotaltracker.com/story/show/181724889 #### Visuals A screenshot from a debug scene demonstrating the component: <img width="251" alt="Screenshot 2022-04-13 at 20 07 56" src="https://user-images.githubusercontent.com/273837/163243304-21c3ad78-4813-4368-b3bb-844d979da699.png"> Screenshots from other debug scenes (`list_view` and `text_area`), demonstrating that the other components still display correctly: <img width="202" alt="Screenshot 2022-04-13 at 20 08 56" src="https://user-images.githubusercontent.com/273837/163243428-de9dc1c7-5a9f-45e0-9325-db60cece9768.png"> <img width="403" alt="Screenshot 2022-04-13 at 20 08 48" src="https://user-images.githubusercontent.com/273837/163243432-895061d9-5bd9-4349-8679-eb63b0f6724d.png"> A screenshot of the Node Searcher's list, showing that long entries in a ListView are now truncated, and an ellipsis character is added in place of removed characters: <img width="651" alt="Screenshot 2022-04-13 at 20 10 16" src="https://user-images.githubusercontent.com/273837/163243664-5b671969-7aa0-4bef-8fd2-825602d85848.png"> # Important Notes - Adding support for the text truncation feature in `ListView` required some changes in the`list_view::Entry`-related APIs. - An embedded font was added (DejaVuSans-Bold) for use in the Component Group View debug scene, and 5 unused embedded fonts were removed.
2022-04-14 13:37:40 +03:00
[[package]]
name = "ide-view-component-group"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl-core",
"ensogl-gui-component",
"ensogl-hardcoded-theme",
"ensogl-list-view",
"ensogl-text",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "ide-view-graph-editor"
version = "0.1.0"
dependencies = [
"analytics",
"ast",
Support source maps for JS-based visualizations (#3208)
2022-01-11 15:31:43 +03:00
"base64 0.13.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bimap",
"engine-protocol",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-config",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-frp",
"enso-logger",
"enso-prelude",
"enso-shapely",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-text",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"ensogl",
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
"ensogl-component",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"ensogl-drop-manager",
"ensogl-hardcoded-theme",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"ensogl-text-msdf-sys",
"failure",
"js-sys",
"nalgebra 0.26.2",
"ordered-float 1.1.1",
"serde",
"serde_json",
Support source maps for JS-based visualizations (#3208)
2022-01-11 15:31:43 +03:00
"sourcemap",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"span-tree",
"uuid",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "idna"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "38f09e0f0b1fb55fdee1f17470ad800da77af5186a1a76c026b679358b7e844e"
dependencies = [
"matches",
"unicode-bidi",
"unicode-normalization",
]
[[package]]
name = "idna"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "418a0a6fab821475f634efe3ccc45c013f742efe03d853e8d3355d5cb850ecf8"
dependencies = [
"matches",
"unicode-bidi",
"unicode-normalization",
]
Support source maps for JS-based visualizations (#3208)
2022-01-11 15:31:43 +03:00
[[package]]
name = "if_chain"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cb56e1aa765b4b4f3aadfab769793b7087bb03a4ea4920644a6d238e2df5b9ed"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "ifmt"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7dd0f8e1404f15475d8a2ca84c2942aa00ac17804ce555294a96f6b5cdf80750"
dependencies = [
"ifmt-impl",
"proc-macro-hack",
]
[[package]]
name = "ifmt-impl"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e50385662f423431a619ab28ba2beeab3063b581a0d1a943765e23911c502904"
dependencies = [
"lazy_static",
"proc-macro-hack",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"regex",
"syn",
]
[[package]]
name = "indexmap"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.8.1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "0f647032dfaa1f8b6dc29bd3edb7bbef4861b8b8007ebb118d6db284fd59f6ee"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"hashbrown",
]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "instant"
version = "0.1.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a5bbe824c507c5da5956355e86a746d82e0e1464f65d862cc5e71da70e94b2c"
dependencies = [
"cfg-if 1.0.0",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "iovec"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b2b3ea6ff95e175473f8ffe6a7eb7c00d054240321b84c57051175fe3c1e075e"
dependencies = [
"libc",
]
[[package]]
name = "ipnet"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "2.5.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "879d54834c8c76457ef4293a689b2a8c59b076067ad77b15efafbb05f92a592b"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "itertools"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f56a2d0bc861f9165be4eb3442afd3c236d8a98afd426f65d92324ae1091a484"
dependencies = [
"either",
]
[[package]]
name = "itertools"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "284f18f85651fe11e8a991b2adb42cb078325c996ed026d994719efcfca1d54b"
dependencies = [
"either",
]
[[package]]
name = "itertools"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.10.3"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "a9a9d19fa1e79b6215ff29b9d6880b706147f16e9b1dbb1e4e5947b5b02bc5e3"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"either",
]
[[package]]
name = "itoa"
version = "0.4.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b71991ff56294aa922b450139ee08b3bfc70982c6b2c7562771375cf73542dd4"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "itoa"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1aab8fc367588b89dcee83ab0fd66b72b50b72fa1904d7095045ace2b0c81c35"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "js-sys"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.55"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "7cc9ffccd38c451a86bf13657df244e9c3f37493cce8e5e21e940963777acc84"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"wasm-bindgen",
]
[[package]]
name = "json-rpc"
version = "0.1.0"
dependencies = [
"enso-prelude",
Backend Communication Profiling (#3382)
2022-04-19 14:30:29 +03:00
"enso-profiler",
Integrate Ensogl stats with profiling framework (#3388) Add logging of EnsoGL performance stats to the profiling framework. Also extends the visualization in the debug scene to show an overview of the performance stats. We now render a timeline of blocks that indicate by their colour the rough FPS range we are in: https://user-images.githubusercontent.com/1428930/162433094-57fbb61a-b502-43bb-8815-b7fc992d3862.mp4 # Important Notes [ci no changelog needed] Needs to be merged after https://github.com/enso-org/enso/pull/3382 as it requires some changes about metadata logging from there. That is why this PR is currently still in draft mode and based on that branch.
2022-04-21 12:38:26 +03:00
"enso-profiler-data",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-shapely",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-web",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"failure",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures 0.3.21",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"serde",
"serde_json",
"shrinkwraprs 0.3.0",
]
[[package]]
name = "keccak"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "67c21572b4949434e4fc1e1978b99c5f77064153c59d998bf13ecd96fb5ecba7"
[[package]]
name = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
dependencies = [
"winapi 0.2.8",
"winapi-build",
]
[[package]]
name = "keyboard-types"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a989afac88279b0482f402d234b5fbd405bf1ad051308595b58de4e6de22346b"
dependencies = [
"bitflags",
"serde",
"unicode-segmentation",
]
[[package]]
name = "kv-log-macro"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0de8b303297635ad57c9f5059fd9cee7a47f8e8daa09df0fcd07dd39fb22977f"
dependencies = [
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "language-tags"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a91d884b6667cd606bb5a69aa0c99ba811a115fc68915e7056ec08a46e93199a"
[[package]]
name = "launcher-shims"
version = "0.1.0"
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
[[package]]
name = "lexer"
version = "0.1.0"
dependencies = [
"criterion",
"enso-flexer",
"enso-prelude",
"lexer-definition",
]
[[package]]
name = "lexer-definition"
version = "0.1.0"
dependencies = [
"enso-flexer",
"enso-prelude",
"uuid",
]
[[package]]
name = "libc"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.2.124"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "21a41fed9d98f27ab1c6d161da622a4fa35e8a54a8adc24bbf3ddd0ef70b0e50"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "libm"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.2"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "33a33a362ce288760ec6a508b94caaec573ae7d3bbbd91b87aa0bad4456839db"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "linked-hash-map"
version = "0.5.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7fb9b38af92608140b86b693604b9ffcc5824240a484d1ecd4795bacb2fe88f3"
[[package]]
name = "lock_api"
version = "0.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c4da24a77a3d8a6d4862d95f72e6fdb9c09a643ecdb402d754004a557f2bec75"
dependencies = [
"scopeguard",
]
[[package]]
name = "log"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e19e8d5c34a3e0e2223db8e060f9e8264aeeb5c5fc64a4ee9965c062211c024b"
dependencies = [
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "log"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.4.16"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "6389c490849ff5bc16be905ae24bc913a9c8892e19b2341dbc175e14c341c2b8"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"cfg-if 1.0.0",
"value-bag",
]
[[package]]
name = "matches"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a3e378b66a060d48947b590737b30a1be76706c8dd7b8ba0f2fe3989c68a853f"
[[package]]
name = "matrixmultiply"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "916806ba0031cd542105d916a97c8572e1fa6dd79c9c51e7eb43a09ec2dd84c1"
dependencies = [
"rawpointer",
]
[[package]]
name = "matrixmultiply"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.2"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "add85d4dd35074e6fedc608f8c8f513a3548619a9024b751949ef0e8e45a4d84"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"rawpointer",
]
[[package]]
name = "maybe-uninit"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "60302e4db3a61da70c0cb7991976248362f30319e88850c487b9b95bbf059e00"
[[package]]
name = "memchr"
version = "2.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "308cc39be01b73d0d18f82a0e7b2a3df85245f84af96fdddc5d202d27e47b86a"
[[package]]
name = "memoffset"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.6.5"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "5aa361d4faea93603064a027415f07bd8e1d5c88c9fbf68bf56a285428fd79ce"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "mime"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ba626b8a6de5da682e1caa06bdb42a335aee5a84db8e5046a3e8ab17ba0a3ae0"
dependencies = [
"log 0.3.9",
]
[[package]]
name = "mime"
version = "0.3.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2a60c7ce501c71e03a9c9c0d35b861413ae925bd979cc7a4e30d060069aaac8d"
[[package]]
name = "mime_guess"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "2.0.4"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "4192263c238a5f0d0c6bfd21f336a313a4ce1c450542449ca191bb657b4642ef"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"mime 0.3.16",
"unicase 2.6.0",
]
[[package]]
name = "miniz_oxide"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.5.1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "d2b29bd4bc3f33391105ebee3589c19197c4271e3e5a9ec9bfe8127eeff8f082"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"adler",
]
[[package]]
name = "mio"
version = "0.6.23"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4afd66f5b91bf2a3bc13fad0e21caedac168ca4c707504e75585648ae80e4cc4"
dependencies = [
"cfg-if 0.1.10",
"fuchsia-zircon",
"fuchsia-zircon-sys",
"iovec",
"kernel32-sys",
"libc",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"miow",
"net2",
"slab",
"winapi 0.2.8",
]
[[package]]
name = "miow"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ebd808424166322d4a38da87083bfddd3ac4c131334ed55856112eb06d46944d"
dependencies = [
"kernel32-sys",
"net2",
"winapi 0.2.8",
"ws2_32-sys",
]
[[package]]
name = "mockall"
version = "0.7.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "01458f8a19b10cb28195290942e3149161c75acf67ebc8fbf714ab67a2b943bc"
dependencies = [
"cfg-if 0.1.10",
"downcast",
"fragile",
"lazy_static",
"mockall_derive",
"predicates",
"predicates-tree",
]
[[package]]
name = "mockall_derive"
version = "0.7.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a673cb441f78cd9af4f5919c28576a3cc325fb6b54e42f7047dacce3c718c17b"
dependencies = [
"cfg-if 0.1.10",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
Developers should find the ide-gui controller codebase logical and easy to work with. (#3188)
2021-12-15 13:40:14 +03:00
[[package]]
name = "multi-map"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bba551d6d795f74a01767577ea8339560bf0a65354e0417b7e915ed608443d46"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "nalgebra"
version = "0.21.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d6b6147c3d50b4f3cdabfe2ecc94a0191fd3d6ad58aefd9664cf396285883486"
dependencies = [
"approx 0.3.2",
"generic-array 0.13.3",
"matrixmultiply 0.2.4",
"num-complex 0.2.4",
"num-rational 0.2.4",
"num-traits",
"rand 0.7.3",
"rand_distr",
"serde",
"serde_derive",
"simba 0.1.5",
"typenum",
]
[[package]]
name = "nalgebra"
version = "0.26.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "476d1d59fe02fe54c86356e91650cd892f392782a1cb9fc524ec84f7aa9e1d06"
dependencies = [
"approx 0.4.0",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"matrixmultiply 0.3.2",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num-complex 0.3.1",
"num-rational 0.3.2",
"num-traits",
"serde",
"simba 0.4.0",
"typenum",
]
[[package]]
name = "native-tls"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.2.10"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "fd7e2f3618557f980e0b17e8856252eee3c97fa12c54dff0ca290fb6266ca4a9"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"lazy_static",
"libc",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"openssl",
"openssl-probe",
"openssl-sys",
"schannel",
"security-framework",
"security-framework-sys",
"tempfile",
]
[[package]]
name = "net2"
version = "0.2.37"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "391630d12b68002ae1e25e8f974306474966550ad82dac6886fb8910c19568ae"
dependencies = [
"cfg-if 0.1.10",
"libc",
"winapi 0.3.9",
]
[[package]]
name = "nonempty"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4f962080273ac958f790079cfc886b5b9d722969dbd7b03f473902bdfe5c69b1"
[[package]]
name = "normalize-line-endings"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "61807f77802ff30975e01f4f071c8ba10c022052f98b3294119f3e615d13e5be"
[[package]]
name = "num"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "43db66d1170d347f9a065114077f7dccb00c1b9478c89384490a3425279a4606"
dependencies = [
"num-bigint",
"num-complex 0.4.0",
"num-integer",
"num-iter",
"num-rational 0.4.0",
"num-traits",
]
[[package]]
name = "num-bigint"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f93ab6289c7b344a8a9f60f88d80aa20032336fe78da341afc91c8a2341fc75f"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num-integer",
"num-traits",
]
[[package]]
name = "num-complex"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6b19411a9719e753aff12e5187b74d60d3dc449ec3f4dc21e3989c3f554bc95"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num-traits",
"serde",
]
[[package]]
name = "num-complex"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "747d632c0c558b87dbabbe6a82f3b4ae03720d0646ac5b7b4dae89394be5f2c5"
dependencies = [
"num-traits",
"serde",
]
[[package]]
name = "num-complex"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "26873667bbbb7c5182d4a37c1add32cdf09f841af72da53318fdb81543c15085"
dependencies = [
"num-traits",
]
[[package]]
name = "num-integer"
version = "0.1.44"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d2cc698a63b549a70bc047073d2949cce27cd1c7b0a4a862d08a8031bc2801db"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num-traits",
]
[[package]]
name = "num-iter"
version = "0.1.42"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b2021c8337a54d21aca0d59a92577a029af9431cb59b909b03252b9c164fad59"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num-integer",
"num-traits",
]
[[package]]
name = "num-rational"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c000134b5dbf44adc5cb772486d335293351644b801551abe8f75c84cfa4aef"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num-integer",
"num-traits",
]
[[package]]
name = "num-rational"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "12ac428b1cb17fce6f731001d307d351ec70a6d202fc2e60f7d4c5e42d8f4f07"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num-integer",
"num-traits",
]
[[package]]
name = "num-rational"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d41702bd167c2df5520b384281bc111a4b5efcf7fbc4c9c222c815b07e0a6a6a"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num-bigint",
"num-integer",
"num-traits",
]
[[package]]
name = "num-traits"
version = "0.2.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a64b1ec5cda2586e284722486d802acf1f7dbdc623e2bfc57e65ca1cd099290"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"libm",
]
[[package]]
name = "num_cpus"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.13.1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "19e64526ebdee182341572e50e9ad03965aa510cd94427a4549448f285e957a1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"hermit-abi",
"libc",
]
[[package]]
name = "num_enum"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.5.7"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "cf5395665662ef45796a4ff5486c5d41d29e0c09640af4c5f17fd94ee2c119c9"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"num_enum_derive",
]
[[package]]
name = "num_enum_derive"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.5.7"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "3b0498641e53dd6ac1a4f22547548caa6864cc4933784319cd1775271c5a46ce"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"proc-macro-crate",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
[[package]]
name = "object"
version = "0.24.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a5b3dd1c072ee7963717671d1ca129f1048fda25edea6b752bfc71ac8854170"
dependencies = [
"flate2",
]
[[package]]
name = "object"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.28.3"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "40bec70ba014595f99f7aa110b84331ffe1ee9aece7fe6f387cc7e3ecda4d456"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"memchr",
]
[[package]]
name = "once_cell"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.10.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "87f3e037eac156d1775da914196f0f37741a274155e34a0b7e427c35d2a2ecb9"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "oorandom"
version = "11.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ab1bc2a289d34bd04a330323ac98a1b4bc82c9d9fcb1e66b63caa84da26b575"
[[package]]
name = "opaque-debug"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2839e79665f131bdb5782e51f2c6c9599c133c6098982a54c794358bf432529c"
[[package]]
name = "openssl"
version = "0.10.38"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c7ae222234c30df141154f159066c5093ff73b63204dcda7121eb082fc56a95"
dependencies = [
"bitflags",
"cfg-if 1.0.0",
"foreign-types",
"libc",
"once_cell",
"openssl-sys",
]
[[package]]
name = "openssl-probe"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.1.5"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "ff011a302c396a5197692431fc1948019154afc178baf7d8e37367442a4601cf"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "openssl-sys"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.9.72"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "7e46109c383602735fa0a2e48dd2b7c892b048e1bf69e5c3b1d804b7d9c203cb"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"cc",
"libc",
"pkg-config",
"vcpkg",
]
[[package]]
name = "ordered-float"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3305af35278dd29f46fcdd139e0b1fbfae2153f0e5928b39b035542dd31e37b7"
dependencies = [
"num-traits",
]
[[package]]
name = "ordered-float"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "2.10.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "7940cf2ca942593318d07fcf2596cdca60a85c9e7fab408a5e21a4f9dcd40d87"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"num-traits",
]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "parking"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "427c3892f9e783d91cc128285287e70a59e206ca452770ece88a76f7a3eddd72"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "parking_lot"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f842b1982eb6c2fe34036a4fbfb06dd185a3f5c8edfaacdf7d1ea10b07de6252"
dependencies = [
"lock_api",
"parking_lot_core",
"rustc_version 0.2.3",
]
[[package]]
name = "parking_lot_core"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b876b1b9e7ac6e1a74a6da34d25c42e17e8862aa409cbbbdcfc8d86c6f3bc62b"
dependencies = [
"cfg-if 0.1.10",
"cloudabi",
"libc",
"redox_syscall 0.1.57",
"rustc_version 0.2.3",
"smallvec 0.6.14",
"winapi 0.3.9",
]
[[package]]
name = "parser"
version = "0.1.0"
dependencies = [
"ast",
"bytes 0.5.6",
"console_error_panic_hook",
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
"enso-build-utilities",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-prelude",
Profiling application details (#3332) * Profiling application details Add enough profiling to account for every missed frame during startup. See https://www.pivotaltracker.com/story/show/181499507 * Build ActiveInterval hierarchy in profiler_data * update doctests / await_! * docs/formatting/naming * more graph modes * increase WASM size Due to new render-profile-flamegraph scene. We should remove these from the main release WASM blob one way or another. * lint * fix a test * Organization (feedback) * Add @wdanilo to Cargo.lock CODEOWNERS As discussed after my previous PR got stuck waiting for Cargo.lock review. * fix doctests * Update docs. Removed a limitation.
2022-03-21 21:09:56 +03:00
"enso-profiler",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-text",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"failure",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"futures 0.3.21",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"js-sys",
"matches",
"reqwest",
"serde",
"serde_json",
"shrinkwraprs 0.2.3",
"tokio",
"uuid",
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"websocket",
]
[[package]]
name = "parser-new"
version = "0.1.0"
dependencies = [
"criterion",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-logger",
"enso-prelude",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itertools 0.10.3",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"lexer",
]
[[package]]
name = "paste"
version = "0.1.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "45ca20c77d80be666aef2b45486da86238fabe33e38306bd3118fe4af33fa880"
dependencies = [
"paste-impl",
"proc-macro-hack",
]
[[package]]
name = "paste"
Revert "Revert "Fixed rate animation loop fixes"" (#3399)
2022-04-14 20:58:53 +03:00
version = "1.0.7"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert "Revert "Fixed rate animation loop fixes"" (#3399)
2022-04-14 20:58:53 +03:00
checksum = "0c520e05135d6e763148b6426a837e239041653ba7becd2e538c076c738025fc"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "paste-impl"
version = "0.1.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d95a7db200b97ef370c8e6de0088252f7e0dfff7d047a28528e47456c0fc98b6"
dependencies = [
"proc-macro-hack",
]
[[package]]
name = "path-clean"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ecba01bf2678719532c5e3059e0b5f0811273d94b397088b82e3bd0a78c78fdd"
[[package]]
name = "percent-encoding"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "31010dd2e1ac33d5b46a5b413495239882813e0369f8ed8a5e266f173602f831"
[[package]]
name = "percent-encoding"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d4fd5641d01c8f18a23da7b6fe29298ff4b55afcccdf78973b24cf3175fee32e"
[[package]]
name = "pin-project"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.10"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "58ad3879ad3baf4e44784bc6a718a8698867bb991f8ce24d1bcbe2cfb4c3a75e"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.10"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "744b6f092ba29c3650faf274db506afd39944f48420f6c86b17cfe0ee1cb36bb"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
[[package]]
name = "pin-project-lite"
version = "0.1.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "257b64915a082f7811703966789728173279bdebb956b143dbcd23f6f970a777"
[[package]]
name = "pin-project-lite"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.8"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "e280fbe77cc62c91527259e9442153f4688736748d24660126286329742b4c6c"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
[[package]]
name = "pkg-config"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.3.25"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "1df8c4ec4b0627e53bdf214615ad287367e482558cf84b109250b37464dc03ae"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "plotters"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "32a3fd9ec30b9749ce28cd91f255d569591cdf937fe280c312143e3c4bad6f2a"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"num-traits",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"plotters-backend",
"plotters-svg",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"wasm-bindgen",
"web-sys",
]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "plotters-backend"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d88417318da0eaf0fdcdb51a0ee6c3bed624333bff8f946733049380be67ac1c"
[[package]]
name = "plotters-svg"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "521fa9638fa597e1dc53e9412a4f9cefb01187ee1f7413076f9e6749e2885ba9"
dependencies = [
"plotters-backend",
]
[[package]]
name = "polling"
version = "2.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "685404d509889fade3e86fe3a5803bca2ec09b0c0778d5ada6ec8bf7a8de5259"
dependencies = [
"cfg-if 1.0.0",
"libc",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"wepoll-ffi",
"winapi 0.3.9",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "ppv-lite86"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.16"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "eb9f9e6e233e5c4a35559a617bf40a4ec447db2e84c20b55a6f83167b7e57872"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "predicates"
version = "1.0.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f49cfaf7fdaa3bfacc6fa3e7054e65148878354a5cfddcf661df4c851f8021df"
dependencies = [
"difference",
"float-cmp",
"normalize-line-endings",
"predicates-core",
"regex",
]
[[package]]
name = "predicates-core"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.3"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "da1c2388b1513e1b605fcec39a95e0a9e8ef088f71443ef37099fa9ae6673fcb"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "predicates-tree"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.5"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "4d86de6de25020a36c6d3643a86d9a6a9f552107c0559c60ea03551b5e16c032"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"predicates-core",
"termtree",
]
[[package]]
name = "proc-macro-crate"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.1.3"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "e17d47ce914bf4de440332250b0edd23ce48c005f59fab39d3335866b114f11a"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"thiserror",
"toml",
]
[[package]]
name = "proc-macro-hack"
version = "0.5.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dbf0c48bc1d91375ae5c3cd81e3722dff1abcf81a30960240640d223f59fe0e5"
[[package]]
name = "proc-macro2"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.0.37"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "ec757218438d5fda206afc041538b2f6d889286160d649a86a24d37e1235afd1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"unicode-xid",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "quote"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.0.18"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "a1feb54ed693b93a84e14094943b84b7c4eae204c512b7ccb95ab0c66d278ad1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "rand"
version = "0.6.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d71dacdc3c88c1fde3885a3be3fbab9f35724e6ce99467f7d9c5026132184ca"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 0.1.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"libc",
"rand_chacha 0.1.1",
"rand_core 0.4.2",
"rand_hc 0.1.0",
"rand_isaac",
"rand_jitter",
"rand_os",
"rand_pcg",
"rand_xorshift",
"winapi 0.3.9",
]
[[package]]
name = "rand"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
dependencies = [
"getrandom 0.1.16",
"libc",
"rand_chacha 0.2.2",
"rand_core 0.5.1",
"rand_hc 0.2.0",
]
[[package]]
name = "rand_chacha"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "556d3a1ca6600bfcbab7c7c91ccb085ac7fbbcd70e008a98742e7847f4f7bcef"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 0.1.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"rand_core 0.3.1",
]
[[package]]
name = "rand_chacha"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4c8ed856279c9737206bf725bf36935d8666ead7aa69b52be55af369d193402"
dependencies = [
"ppv-lite86",
"rand_core 0.5.1",
]
[[package]]
name = "rand_core"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
dependencies = [
"rand_core 0.4.2",
]
[[package]]
name = "rand_core"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c33a3c44ca05fa6f1807d8e6743f3824e8509beca625669633be0acbdf509dc"
[[package]]
name = "rand_core"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
dependencies = [
"getrandom 0.1.16",
]
[[package]]
name = "rand_distr"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "96977acbdd3a6576fb1d27391900035bf3863d4a16422973a409b488cf29ffb2"
dependencies = [
"rand 0.7.3",
]
[[package]]
name = "rand_hc"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7b40677c7be09ae76218dc623efbf7b18e34bced3f38883af07bb75630a21bc4"
dependencies = [
"rand_core 0.3.1",
]
[[package]]
name = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
dependencies = [
"rand_core 0.5.1",
]
[[package]]
name = "rand_isaac"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ded997c9d5f13925be2a6fd7e66bf1872597f759fd9dd93513dd7e92e5a5ee08"
dependencies = [
"rand_core 0.3.1",
]
[[package]]
name = "rand_jitter"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1166d5c91dc97b88d1decc3285bb0a99ed84b05cfd0bc2341bdf2d43fc41e39b"
dependencies = [
"libc",
"rand_core 0.4.2",
"winapi 0.3.9",
]
[[package]]
name = "rand_os"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7b75f676a1e053fc562eafbb47838d67c84801e38fc1ba459e8f180deabd5071"
dependencies = [
"cloudabi",
"fuchsia-cprng",
"libc",
"rand_core 0.4.2",
"rdrand",
"winapi 0.3.9",
]
[[package]]
name = "rand_pcg"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "abf9b09b01790cfe0364f52bf32995ea3c39f4d2dd011eac241d2914146d0b44"
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 0.1.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"rand_core 0.4.2",
]
[[package]]
name = "rand_xorshift"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cbf7e9e623549b0e21f6e97cf8ecf247c1a8fd2e8a992ae265314300b2455d5c"
dependencies = [
"rand_core 0.3.1",
]
[[package]]
name = "rawpointer"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "60a357793950651c4ed0f3f52338f53b2f809f32d83a07f72909fa13e4c6c1e3"
[[package]]
name = "rayon"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.5.2"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "fd249e82c21598a9a426a4e00dd7adc1d640b22445ec8545feef801d1a74c221"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"autocfg 1.1.0",
"crossbeam-deque",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"either",
"rayon-core",
]
[[package]]
name = "rayon-core"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.9.2"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "9f51245e1e62e1f1629cbfec37b5793bbabcaeb90f30e94d2ba03564687353e4"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"crossbeam-channel",
"crossbeam-deque",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"crossbeam-utils 0.8.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"num_cpus",
]
[[package]]
name = "rdrand"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
dependencies = [
"rand_core 0.3.1",
]
[[package]]
name = "redox_syscall"
version = "0.1.57"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
[[package]]
name = "redox_syscall"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.2.13"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "62f25bc4c7e55e0b0b7a1d43fb893f4fa1361d0abe38b9ce4f323c2adfe6ef42"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"bitflags",
]
[[package]]
name = "regex"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.5.5"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "1a11647b6b25ff05a515cb92c365cec08801e83423a235b51e231e1808747286"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"aho-corasick",
"memchr",
"regex-syntax",
]
[[package]]
name = "regex-automata"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6c230d73fb8d8c1b9c0b3135c5142a8acee3a0558fb8db5cf1cb65f8d7862132"
[[package]]
name = "regex-syntax"
version = "0.6.25"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f497285884f3fcff424ffc933e56d7cbca511def0c9831a7f9b5f6153e3cc89b"
[[package]]
name = "remove_dir_all"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
dependencies = [
"winapi 0.3.9",
]
[[package]]
name = "reqwest"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.10.10"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "0718f81a8e14c4dbb3b34cf23dc6aaf9ab8a0dfec160c534b3dbca1aaa21f47c"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"base64 0.13.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bytes 0.5.6",
"encoding_rs",
"futures-core",
"futures-util",
"http",
"http-body",
"hyper 0.13.10",
"hyper-tls",
"ipnet",
"js-sys",
"lazy_static",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"mime 0.3.16",
"mime_guess",
"native-tls",
"percent-encoding 2.1.0",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"pin-project-lite 0.2.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"serde",
"serde_urlencoded",
"tokio",
"tokio-tls 0.3.1",
"url 2.2.2",
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-futures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"web-sys",
"winreg",
]
[[package]]
name = "rustc-demangle"
version = "0.1.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7ef03e0a2b150c7a90d01faf6254c9c48a41e95fb2a8c2ac1c6f0d2b9aefc342"
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
dependencies = [
"semver 0.9.0",
]
[[package]]
name = "rustc_version"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
dependencies = [
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"semver 1.0.7",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "rustversion"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.6"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "f2cc38e8fa666e2de3c4aba7edeb5ffc5246c1c2ed0e3d17e560aeeba736b23f"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "ryu"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.9"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "73b4b750c782965c211b42f022f59af1fbceabdd026623714f104152f1ec149f"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "safemem"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ef703b7cb59335eae2eb93ceb664c0eb7ea6bf567079d843e09420219668e072"
[[package]]
name = "same-file"
version = "1.0.6"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
dependencies = [
"winapi-util",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "schannel"
version = "0.1.19"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "8f05ba609c234e60bee0d547fe94a4c7e9da733d1c962cf6e59efa4cd9c8bc75"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"lazy_static",
"winapi 0.3.9",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "scoped-tls"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ea6a9290e3c9cf0f18145ef7ffa62d68ee0bf5fcd651017e586dc7fd5da448c2"
[[package]]
name = "scopeguard"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
[[package]]
name = "security-framework"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "2.6.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "2dc14f172faf8a0194a3aded622712b0de276821addc574fa54fc0a1167e10dc"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bitflags",
"core-foundation",
"core-foundation-sys",
"libc",
"security-framework-sys",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "security-framework-sys"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "2.6.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "0160a13a177a45bfb43ce71c01580998474f556ad854dcbca936dd2841a5c556"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"core-foundation-sys",
"libc",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "semver"
version = "0.9.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"semver-parser",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "semver"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.0.7"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "d65bd28f48be7196d222d95b9243287f48d27aca604e08497513019ff0502cc4"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"serde",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "semver-parser"
version = "0.7.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "serde"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.136"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "ce31e24b01e1e524df96f1c2fdd054405f8d7376249a5110886fb4b658484789"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"serde_derive",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "serde_cbor"
version = "0.11.2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "2bef2ebfde456fb76bbcf9f59315333decc4fda0b2b44b420243c11e0f5ec1f5"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"half",
"serde",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "serde_derive"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.136"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "08597e7152fcd306f41838ed3e37be9eaeed2b61c42e2117266a554fab4662f9"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "serde_json"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.0.79"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "8e8d9fa5c3b304765ce1fd9c4c8a3de2c8db365a5b91be52f186efc675681d95"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"itoa 1.0.1",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"ryu",
"serde",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "serde_urlencoded"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.7.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "d3491c14715ca2294c4d6a88f15e84739788c1d030eed8c110436aafdaa2f3fd"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"form_urlencoded",
"itoa 1.0.1",
"ryu",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"serde",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "serde_yaml"
version = "0.8.14"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "f7baae0a99f1a324984bcdc5f0718384c1f69775f1c7eec8b859b71b443e3fd7"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"dtoa",
"linked-hash-map",
"serde",
"yaml-rust",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "sha1"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c1da05c97445caa12d05e848c4a4fcbbea29e748ac28f7e80e9b010392063770"
dependencies = [
"sha1_smol",
]
[[package]]
name = "sha1_smol"
version = "1.0.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "ae1a47186c03a32177042e55dbc5fd5aee900b8e0069a8d70fba96a9375cd012"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "sha3"
version = "0.8.2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "dd26bc0e7a2e3a7c959bc494caf58b72ee0c71d67704e9520f736ca7e4853ecf"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"block-buffer",
"byte-tools",
"digest",
"keccak",
"opaque-debug",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "shrinkwraprs"
version = "0.2.3"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "83695fde96cbe9e08f0e4eb96b1b56fdbd44f2098ee27462dda964c7745fddc7"
dependencies = [
"bitflags",
"itertools 0.8.2",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "shrinkwraprs"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e63e6744142336dfb606fe2b068afa2e1cca1ee6a5d8377277a92945d81fa331"
dependencies = [
"bitflags",
"itertools 0.8.2",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
[[package]]
name = "simba"
version = "0.1.5"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "fb931b1367faadea6b1ab1c306a860ec17aaa5fa39f367d0c744e69d971a1fb2"
dependencies = [
"approx 0.3.2",
"num-complex 0.2.4",
"num-traits",
"paste 0.1.18",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "simba"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5132a955559188f3d13c9ba831e77c802ddc8782783f050ed0c52f5988b95f4c"
dependencies = [
"approx 0.4.0",
"num-complex 0.3.1",
"num-traits",
Revert "Revert "Fixed rate animation loop fixes"" (#3399)
2022-04-14 20:58:53 +03:00
"paste 1.0.7",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "slab"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.4.6"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "eb703cfe953bccee95685111adeedb76fabe4e97549a58d16f03ea7b9367bb32"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "smallvec"
version = "0.6.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b97fcaeba89edba30f044a10c6a3cc39df9c3f17d7cd829dd1446cab35f890e0"
dependencies = [
"maybe-uninit",
]
[[package]]
name = "smallvec"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.8.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "f2dd574626839106c320a323308629dcb1acfc96e32a8cba364ddc61ac23ee83"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "socket2"
version = "0.3.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "122e570113d28d773067fab24266b66753f6ea915758651696b6e35e49f88d6e"
dependencies = [
"cfg-if 1.0.0",
"libc",
"winapi 0.3.9",
]
[[package]]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
name = "socket2"
version = "0.4.4"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "66d72b759436ae32898a2af0a14218dbf55efde3feeb170eb623637db85ee1e0"
dependencies = [
"libc",
"winapi 0.3.9",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
Support source maps for JS-based visualizations (#3208)
2022-01-11 15:31:43 +03:00
[[package]]
name = "sourcemap"
version = "6.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6e031f2463ecbdd5f34c950f89f5c1e1032f22c0f8e3dc4bdb2e8b6658cf61eb"
dependencies = [
"base64 0.11.0",
"if_chain",
"lazy_static",
"regex",
"rustc_version 0.2.3",
"serde",
"serde_json",
"url 2.2.2",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "span-tree"
version = "0.1.0"
dependencies = [
"ast",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-data-structures",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"enso-prelude",
Profiling application details (#3332) * Profiling application details Add enough profiling to account for every missed frame during startup. See https://www.pivotaltracker.com/story/show/181499507 * Build ActiveInterval hierarchy in profiler_data * update doctests / await_! * docs/formatting/naming * more graph modes * increase WASM size Due to new render-profile-flamegraph scene. We should remove these from the main release WASM blob one way or another. * lint * fix a test * Organization (feedback) * Add @wdanilo to Cargo.lock CODEOWNERS As discussed after my previous PR got stuck waiting for Cargo.lock review. * fix doctests * Update docs. Removed a limitation.
2022-03-21 21:09:56 +03:00
"enso-profiler",
Refactored `enso-data` crate and text utilities. (#3166)
2021-11-25 13:45:42 +03:00
"enso-text",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"failure",
"parser",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-test",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
Backend Communication Profiling (#3382)
2022-04-19 14:30:29 +03:00
[[package]]
name = "strum"
version = "0.24.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e96acfc1b70604b8b2f1ffa4c57e59176c7dbb05d556c71ecd2f5498a1dee7f8"
[[package]]
name = "strum_macros"
version = "0.24.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6878079b17446e4d3eba6192bb0a2950d5b14f0ed8424b852310e5a94345d0ef"
dependencies = [
"heck",
"proc-macro2",
"quote",
"rustversion",
"syn",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "syn"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "1.0.91"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "b683b2b825c8eef438b77c36a06dc262294da3d5a5813fac20da149241dcd44d"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
"unicode-xid",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "synstructure"
version = "0.12.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f36bdaa60a83aca3921b5259d5400cbf5e90fc51931376a9bd4a0eb79aa7210f"
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"unicode-xid",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
]
[[package]]
name = "tempfile"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "3.3.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "5cdb1ef4eaeeaddc8fbd371e5017057064af0911902ef36b39801f67cc6d79e4"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"cfg-if 1.0.0",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"fastrand",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"libc",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"redox_syscall 0.2.13",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"remove_dir_all",
"winapi 0.3.9",
]
[[package]]
name = "termtree"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.4"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "507e9898683b6c43a9aa55b64259b721b52ba226e0f3779137e50ad114a4c90b"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "textwrap"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"unicode-width",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "thiserror"
version = "1.0.30"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "854babe52e4df1653706b98fcfc05843010039b406875930a70e4d9644e5c417"
dependencies = [
"thiserror-impl",
]
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "thiserror-impl"
version = "1.0.30"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "aa32fd3f627f367fe16f893e2597ae3c05020f8bba2666a4e6ea73d377e5714b"
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "time"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.1.44"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "6db9e6914ab8b1ae1c260a4ae7a49b6c5611b40328a735b21862567685e73255"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"libc",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"wasi 0.10.0+wasi-snapshot-preview1",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"winapi 0.3.9",
]
[[package]]
name = "tinytemplate"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be4d6b5f19ff7664e8c98d03e2139cb510db9b0a60b55f8e8709b689d939b6bc"
dependencies = [
"serde",
"serde_json",
]
[[package]]
name = "tinyvec"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.5.1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "2c1c1d5a42b6245520c249549ec267180beaffcc0615401ac8e31853d4b6d8d2"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"tinyvec_macros",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tinyvec_macros"
version = "0.1.0"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "cda74da7e1a664f795bb1f8a87ec406fb89a02522cf6e50620d016add6dbbf5c"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio"
version = "0.2.25"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "6703a273949a90131b290be1fe7b039d0fc884aa1935860dfcbe056f28cd8092"
dependencies = [
"bytes 0.5.6",
"fnv",
"futures-core",
"iovec",
"lazy_static",
"memchr",
"mio",
"num_cpus",
"pin-project-lite 0.1.12",
"slab",
"tokio-macros",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-codec"
version = "0.1.2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "25b2998660ba0e70d18684de5d06b70b70a3a747469af9dea7618cc59e75976b"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bytes 0.4.12",
"futures 0.1.31",
"tokio-io",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-executor"
version = "0.1.10"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "fb2d1b8f4548dbf5e1f7818512e9c406860678f29c300cdf0ebac72d1a3a1671"
dependencies = [
"crossbeam-utils 0.7.2",
"futures 0.1.31",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-io"
version = "0.1.13"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "57fc868aae093479e3131e3d165c93b1c7474109d13c90ec0dda2a1bbfff0674"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bytes 0.4.12",
"futures 0.1.31",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-macros"
version = "0.2.6"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "e44da00bfc73a25f814cd8d7e57a68a5c31b74b3152a0a1d1f590c97ed06265a"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"syn",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-reactor"
version = "0.1.12"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "09bc590ec4ba8ba87652da2068d150dcada2cfa2e07faae270a5e0409aa51351"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"crossbeam-utils 0.7.2",
"futures 0.1.31",
"lazy_static",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"mio",
"num_cpus",
"parking_lot",
"slab",
"tokio-executor",
"tokio-io",
"tokio-sync",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-sync"
version = "0.1.8"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "edfe50152bc8164fcc456dab7891fa9bf8beaf01c5ee7e1dd43a397c3cf87dee"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"fnv",
"futures 0.1.31",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-tcp"
version = "0.1.4"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "98df18ed66e3b72e742f185882a9e201892407957e45fbff8da17ae7a7c51f72"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"bytes 0.4.12",
"futures 0.1.31",
"iovec",
"mio",
"tokio-io",
"tokio-reactor",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-tls"
version = "0.2.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "354b8cd83825b3c20217a9dc174d6a0c67441a2fae5c41bcb1ea6679f6ae0f7c"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"futures 0.1.31",
"native-tls",
"tokio-io",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-tls"
version = "0.3.1"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "9a70f4fcd7b3b24fb194f837560168208f669ca8cb70d0c4b862944452396343"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"native-tls",
"tokio",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tokio-util"
version = "0.3.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "be8242891f2b6cbef26a2d7e8605133c2c554cd35b3e4948ea892d6d68436499"
dependencies = [
"bytes 0.5.6",
"futures-core",
"futures-sink",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"pin-project-lite 0.1.12",
"tokio",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "toml"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.5.9"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "8d82e1a7758622a465f8cee077614c73484dac5b836c02ff6a40d5d1010324d7"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"serde",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tower-service"
version = "0.3.1"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "360dfd1d6d30e05fda32ace2c8c70e9c0a9da713275777f5a4dbb8a1893930c6"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tracing"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.1.34"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "5d0ecdcb44a79f0fe9844f0c4f33a342cbcbb5117de8001e6ba0dc2351327d09"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"cfg-if 1.0.0",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"pin-project-lite 0.2.8",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"tracing-core",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tracing-core"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.1.26"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "f54c8ca710e81886d498c2fd3331b56c93aa248d49de2222ad2742247c60072f"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"lazy_static",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "tracing-futures"
version = "0.2.5"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "97d095ae15e245a057c8e8451bab9b3ee1e1f68e9ba2b4fbc18d0ac5237835f2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"pin-project",
"tracing",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "traitobject"
version = "0.1.0"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "efd1f82c56340fdf16f2a953d7bda4f8fdffba13d93b00844c25572110b26079"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "try-lock"
version = "0.2.3"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "59547bce71d9c38b83d9c0e92b6066c4253371f15005def0c30d9657f50c7642"
Update to GraalVM 21.1.0 (#1738)
2021-05-14 15:08:39 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "typeable"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1410f6f91f21d1612654e7cc69193b0334f909dcf2c790c4826254fbb86f8887"
[[package]]
name = "typenum"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.15.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "dcf81ac59edc17cc8697ff311e8f5ef2d99fcbd9817b34cec66f90b6c3dfd987"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "unicase"
version = "1.4.2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "7f4765f83163b74f957c797ad9253caf97f103fb064d3999aea9568d09fc8a33"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"version_check 0.1.5",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "unicase"
version = "2.6.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "50f37be617794602aabbeee0be4f259dc1778fabe05e2d67ee8f79326d5cb4f6"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"version_check 0.9.4",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
name = "unicode-bidi"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a01404663e3db436ed2746d9fefef640d868edae3cceb81c3b8d5732fda678f"
[[package]]
name = "unicode-normalization"
version = "0.1.19"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "d54590932941a9e9266f0832deed84ebe1bf2e4c9e4a3554d393d18f5e854bf9"
dependencies = [
"tinyvec",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "unicode-segmentation"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "1.9.0"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "7e8820f5d777f6224dc4be3632222971ac30164d4a258d595640799554ebfd99"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "unicode-width"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.1.9"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "3ed742d4ea2bd1176e236172c8429aaf54486e7ac098db29ffe6529e0ce50973"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "unicode-xid"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8ccb82d61f80a663efe1f787a51b16b5a51e3314d6ac365b08639f52387b33f3"
[[package]]
name = "url"
version = "1.7.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dd4e7c0d531266369519a4aa4f399d748bd37043b00bde1e4ff1f60a120b355a"
dependencies = [
"idna 0.1.5",
"matches",
"percent-encoding 1.0.1",
]
[[package]]
name = "url"
version = "2.2.2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "a507c383b2d33b5fc35d1861e77e6b383d158b2da5e14fe51b83dfedf6fd578c"
dependencies = [
"form_urlencoded",
"idna 0.2.3",
"matches",
"percent-encoding 2.1.0",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "uuid"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.8.2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "bc5cf98d8186244414c848017f0e2676b3fcb46807f6668a97dfe67359a3c4b7"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"getrandom 0.2.6",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"serde",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"sha1",
]
[[package]]
name = "value-bag"
version = "1.0.0-alpha.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "79923f7731dc61ebfba3633098bf3ac533bbd35ccd8c57e7088d9a5eebe0263f"
dependencies = [
"ctor",
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"version_check 0.9.4",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "vcpkg"
version = "0.2.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "accd4ea62f7bb7a82fe23066fb0957d48ef677f6eeb8215f372f52e48bb32426"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "version_check"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "914b1a6776c4c929a602fafd8bc742e06365d4bcbe48c30f9cca5824f70dc9dd"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "version_check"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.9.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
[[package]]
name = "waker-fn"
version = "1.1.0"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "9d5b2c62b4012a3e1eca5a7e077d13b3bf498c4073e33ccd58626607748ceeca"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "walkdir"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
version = "2.3.2"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
checksum = "808cf2735cd4b6866113f648b791c6adc5714537bc222d9347bb203386ffda56"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"same-file",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"winapi 0.3.9",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"winapi-util",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "want"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1ce8a968cb1cd110d136ff8b819a556d6fb6d919363c61534f6860c7eb172ba0"
dependencies = [
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"try-lock",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "wasi"
version = "0.9.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "wasi"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
version = "0.10.0+wasi-snapshot-preview1"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
checksum = "1a143597ca7c7793eff794def352d41792a93c481eb1042423ff7ff72ba2c31f"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "wasm-bindgen"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.78"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "632f73e236b219150ea279196e54e610f5dbafa5d61786303d4da54f84e47fce"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"cfg-if 1.0.0",
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"serde",
"serde_json",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.78"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "a317bf8f9fba2476b4b2c85ef4c4af8ff39c3c7f0cdfeed4f82c34a880aa837b"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"bumpalo",
"lazy_static",
Multi-process profiles. (#3395) See: [#181837344](https://www.pivotaltracker.com/story/show/181837344). I've separated this PR from some deeper changes I'm making to the profile format, because the changeset was getting too complex. The new APIs and tools in this PR are fully-implemented, except the profile format is too simplistic--it doesn't currently support headers that are needed to determine the relative timings of events from different processes. - Adds basic support for profile files containing data collected by multiple processes. - Implements `api_events_to_profile`, a tool for converting backend message logs (#3392) to the `profiler` format so they can be merged with frontend profiles (currently they can be merged with `cat`, but the next PR will introduce a merge tool). - Introduces `message_beanpoles`, a simple tool that diagrams timing relationships between frontend and backend messages. ### Important Notes - All TODOs introduced here will be addressed in the next PR that defines the new format. - Introduced a new crate, `enso_profiler_enso_data`, to be used by profile consumers that need to refer to Enso application datatypes to interpret metadata. - Introduced a `ProfileBuilder` abstraction for writing the JSON profile format; partially decouples the runtime event log structures from the format definition. - Introducing the conversion performed for `ProfilerBuilder` uncovered that the `.._with_same_start!` low-level `profiler` APIs don't currently work; they return `Started<_>` profilers, but that is inconsistent with the stricter data model that I introduced when I implemented `profiler_data`; they need to return profilers in a created, unstarted state. Low-level async profilers have not been a priority, but once #3382 merges we'll have a way to render their data, which will be really useful because async profilers capture *why* we're doing things. I'll bring up scheduling this in the next performance meeting.
2022-04-21 17:44:03 +03:00
"log 0.4.16",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"syn",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"wasm-bindgen-shared",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "wasm-bindgen-futures"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.4.28"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "8e8d7523cb1f2a4c96c1317ca690031b714a51cc14e05f712446691f413f5d39"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
"cfg-if 1.0.0",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"js-sys",
"wasm-bindgen",
"web-sys",
]
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "wasm-bindgen-macro"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.78"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "d56146e7c495528bf6587663bea13a8eb588d39b36b679d83972e1a2dbbdacf9"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"quote",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.78"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "7803e0eea25835f8abdc585cd3021b3deb11543c6fe226dcd30b228857c5c5ab"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Use libraries merged from `rust-lib` directly (#3137)
2021-11-05 18:55:55 +03:00
"syn",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.2.78"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "0237232789cf037d5480773fe568aac745bfe2afbc11a863e97901780a6b47cc"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "wasm-bindgen-test"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.28"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "96f1aa7971fdf61ef0f353602102dbea75a56e225ed036c1e3740564b91e6b7e"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
dependencies = [
"console_error_panic_hook",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
"js-sys",
"scoped-tls",
"wasm-bindgen",
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"wasm-bindgen-futures",
"wasm-bindgen-test-macro",
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "wasm-bindgen-test-macro"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.28"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "6006f79628dfeb96a86d4db51fbf1344cd7fd8408f06fc9aa3c84913a4789688"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
Integration Test Framework (#3257)
2022-02-11 15:19:02 +03:00
"proc-macro2",
"quote",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
[[package]]
name = "weak-table"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.2"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "323f4da9523e9a669e1eaf9c6e763892769b1d38c623913647bfdc1532fe4549"
single wprkspace, update ci
2021-10-30 16:04:07 +03:00
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "web-sys"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
version = "0.3.55"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
checksum = "38eb105f1c59d9eaa6b5cdc92b859d85b926e82cb2e0945cd0c9259faa6fe9fb"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
dependencies = [
"js-sys",
"wasm-bindgen",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "websocket"
version = "0.23.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b255b190f412e45000c35be7fe9b48b39a2ac5eb90d093d421694e5dae8b335c"
dependencies = [
"base64 0.10.1",
"bitflags",
"byteorder",
"bytes 0.4.12",
"futures 0.1.31",
"hyper 0.10.16",
"native-tls",
"rand 0.6.5",
"sha1",
"tokio-codec",
"tokio-io",
"tokio-reactor",
"tokio-tcp",
"tokio-tls 0.2.1",
"unicase 1.4.2",
"url 1.7.2",
]
Add Root View and Welcome Screen View (#3164)
2021-11-30 18:23:46 +03:00
[[package]]
name = "welcome-screen"
version = "0.1.0"
dependencies = [
"enso-frp",
"ensogl",
"wasm-bindgen",
"web-sys",
]
Bump Rust toolchain to `nightly-2022-01-20`. (#3255)
2022-02-16 15:58:02 +03:00
[[package]]
name = "wepoll-ffi"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d743fdedc5c64377b5fc2bc036b01c7fd642205a0d96356034ae3404d49eb7fb"
dependencies = [
"cc",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "winapi"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "winapi-build"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
"winapi 0.3.9",
Add API for dataflow errors (#1422)
2021-01-25 17:41:20 +03:00
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Refactoring: merge utils into prelude; merge workspaces. (#3151)
2021-11-10 16:36:08 +03:00
[[package]]
name = "winreg"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0120db82e8a1e0b9fb3345a539c478767c0048d842860994d96113d5b667bd69"
dependencies = [
"winapi 0.3.9",
]
[[package]]
name = "ws2_32-sys"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d59cefebd0c892fa2dd6de581e937301d8552cb44489cdff035c6187cb63fa5e"
dependencies = [
"winapi 0.2.8",
"winapi-build",
]
[[package]]
name = "xi-rope"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c1266c6612194a86462905372bc7bbc9887e3f3826da6b82ea4a35492bc65d5a"
dependencies = [
"bytecount",
"memchr",
"regex",
"unicode-segmentation",
]
[[package]]
name = "yaml-rust"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56c1936c4cc7a1c9ab21a1ebb602eb942ba868cbd44a99cb7cdc5892335e1c85"
dependencies = [
"linked-hash-map",
]
[[package]]
name = "zip"
version = "0.5.13"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93ab48844d61251bb3835145c521d88aa4031d7139e8485990f60ca911fa0815"
dependencies = [
"byteorder",
"bzip2",
"crc32fast",
"flate2",
"thiserror",
"time",
]
[[package]]
name = "zip-extensions"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9adcf027b355870f62cabaed021f9028231d2d84cad6e30a7abdaa4dc0390edd"
dependencies = [
"zip",
]
Reference in New Issue Copy Permalink