profile
viewpoint

CryZe/AdventOfCode 4

Solutions for Advent of Code written in Rust

CryZe/AHatInTimeAutoSplitter 1

Auto Splitter for A Hat in Time

CryZe/CheatTables 1

Useful Cheat Tables for the games I work with

CryZe/demangle-tww 1

A Demangler for Wind Waker's framework.map files

CryZe/dolphin 1

Dolphin is a GameCube / Wii emulator, allowing you to play games for these two platforms on PC with improvements.

CryZe/42-GBmu 0

A GB Emulator Written in Rust

CryZe/approx 0

Approximate floating point equality comparisons and assertions

push eventCryZe/WindWakerSaves

gymnast86

commit sha 05eeba0e991b333ff6254bfd408fd95cc23b5393

Added modern Any% saves and restructured directory to preserve older saves

view details

Christopher Serr

commit sha e8b4aa6ee324cb16ce20e6eb5f186fbdc5c987ab

Merge pull request #6 from gymnast86/master Added modern Any% saves (both JP and NTSC) and restructured the directory

view details

push time in 4 days

PR merged CryZe/WindWakerSaves

Added modern Any% saves (both JP and NTSC) and restructured the directory

I figure these should probably be updated.

+24 -0

0 comment

77 changed files

gymnast86

pr closed time in 4 days

pull request commentAmanieu/parking_lot

Update lock_api and instant to most recent versions

That's not the case, if both 0.1.4 and 0.1.7 are depended on cargo will only pull in 0.1.7, unless they both specify them as "=0.1.4" and "=0.1.7" respectively.

j-vanderstoep

comment created time in 5 days

pull request commentAmanieu/parking_lot

Update lock_api and instant to most recent versions

This should not be necessary, Rust will never select 0.1.4 and 0.1.7 as incompatible crates were it would compile in both versions.

j-vanderstoep

comment created time in 5 days

issue openedrust-analyzer/rust-analyzer

Opening Documentation for module opens parent module

If you try to open the documentation for a module, it directs you to the parent module instead.

Steps to reproduce:

  1. Write something like this use std::mem::swap;
  2. Put the cursor on mem
  3. Run Rust Analyzer: Open docs under cursor
  4. The documentation for std itself and not the mem module opens.

created time in 5 days

issue commentLiveSplit/LiveSplitOne

Error compiling

I assume it isn't in the PATH then. Glad you figure out a workaround though. 👍

3top1a

comment created time in 7 days

pull request commentabonander/img_hash

Remove unnecessary indirect dependencies

Sorry for pinging again, but it would be great if this somehow could be resolved. I'd still be up for co-maintaining.

CryZe

comment created time in 7 days

issue commentLiveSplit/LiveSplitOne

Error compiling

/bin/sh: wasm-bindgen: command not found

This is the problem. You need to install wasm-bindgen like it says in the README:

cargo install wasm-bindgen-cli
3top1a

comment created time in 7 days

push eventCryZe/korean-phonetics-transcriber

Christopher Serr

commit sha 47149dc9fa0b319fa17240294cea838344d86d54

Minor fixes & allow inputting pronunciation

view details

push time in 12 days

issue commentrust-lang/rfcs

Pod & Packed traits

You may want to take a look at the safe transmute working group.

mahkoh

comment created time in 12 days

push eventCryZe/AHatInTimeAutoSplitter

Carlos

commit sha d04a3646dfcc42e4943e1aa3f035225b5caf6621

Added detailed time piece splits Added act pointers, and time piece split options for most acts.

view details

Carlos

commit sha aeaf005dad34219011427a465d39f48e1f8d5a11

Trying to fix branch... Updating master while having a branch kind of confused me, let's see if this fixes it... Edit: it worked, checkout successful

view details

Carlos

commit sha 8122dd2b0029b68317d9c218b29bd8e867bb6d1c

Added many splits, changing split block structure Act entry not tested

view details

Carlos

commit sha db6ba64ffbc2c892c6b811fa0ebdc41ca0afa032

Added many split conditions, faster loading times Splits: checkpoint, checkpoint+pause, checkpoint+pause+position, position, act entry. Signature scanner now checks memory pages backwards which finds the signature a lot faster.

view details

Carlos

commit sha fe435f643c0197cb470ce852996c9a3258b00d49

Fixed all act entries and position splits

view details

Carlos

commit sha 5adab92481134b41b39dc410643613854c3cac73

Added generic act entry split and avoid reset at intro

view details

Carlos

commit sha 7f8ed223f99780193af86ca95837868507ed0cf8

Added rift splits and small fixes Look like it's completed finally. Testing time.

view details

Carlos

commit sha 26c625fd4906ccd95b422087648a28f13a52433c

Various split fixes

view details

Carlos

commit sha 1499c4ab193ed86f8c73d4841fd7b65f7c0b380f

Various small bug fixed and improvements

view details

Carlos

commit sha bf03b5384315de5a6a85da4ea8d23324ceab0e2b

Reworked position splits completly Should be done with fixes and upgrades for now. If tests go well this will be a pull request.

view details

Carlos

commit sha b8e602b9e5ee2860d9b1e07cc196c4493d92ab18

Various small improvements Improved some split key volumes, improved act entry splits, added a split event subscription and added a double split prevention

view details

Carlos Barahona

commit sha 90a68ed3fdd2e6db34ad0096c7ef548c88572b65

Merge branch 'master' into detailed-splits

view details

Carlos Barahona

commit sha 907d7f4ee50ba142e16df5077480d184504688d5

Merge pull request #1 from cccarl/detailed-splits Add many customizable splits

view details

Carlos

commit sha 851f358662077c2766ad4e7804a7ecf4a5c60465

Fixed small inconsistency in the generic act entry splits.

view details

Carlos

commit sha a92056d890aa2f6b595f1ff3313cc2b00597dc80

Fixed small inconsistency in the generic act entry splits.

view details

Carlos

commit sha bc25439157019dafe3759c00524e1babeb74ce34

Merge remote-tracking branch 'origin/master'

view details

Carlos

commit sha 79adff87a0ff78ea2c45dc15456abdb71a30828e

Very small optimization Rifts won't be detected if the user isn't using detailed splits.

view details

Christopher Serr

commit sha 1e835e7691c95c4afad8fb769190854e13aa6db0

Merge pull request #5 from cccarl/master Add many customizable split options and improve load time.

view details

push time in 13 days

PR merged CryZe/AHatInTimeAutoSplitter

Add many customizable split options and improve load time.
  • Added a new settings tree, "Detailed Splits", with many customizable split options for all acts and time rifts, including time piece grabs, delayed time grabs, new checkpoints, position splits, act entries and more.

  • The initial load of the auto splitter when the game is already open is now much faster.

  • Renamed "Splits" settings tree to "Simple Splits" and added to it "Act Entries" as an option.

  • Added a setting to avoid resetting when immediately going back to main menu when opening a new file.

+377 -29

0 comment

1 changed file

cccarl

pr closed time in 13 days

push eventCryZe/korean-phonetics-transcriber

Christopher Serr

commit sha b68976874b66a5526d4b15ce37af793bc9ac53ed

Create README.md

view details

push time in 14 days

create barnchCryZe/korean-phonetics-transcriber

branch : master

created branch time in 14 days

created repositoryCryZe/korean-phonetics-transcriber

Transcribes the phonetics of (mostly english) text into 한글.

created time in 14 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha cc83cffd6f3c78787e04757a5faa22c867897110

deploy: fcd1a3d811546edfa267991a2a188cdf421303c9

view details

push time in 15 days

push eventLiveSplit/LiveSplitOne

dependabot[bot]

commit sha eceb4fafc5f2929505eb9457aff8e5a56a73d05a

deploy: 33447af70fd86bf7ff2de3217771e55163bfcb5c

view details

push time in 15 days

Pull request review commentrust-lang/blog.rust-lang.org

release blog post for Rust 1.47

+---+layout: post+title: "Announcing Rust 1.47.0"+author: The Rust Release Team+release: true+---++The Rust team is happy to announce a new version of Rust, 1.47.0. Rust is a+programming language that is empowering everyone to build reliable and+efficient software.++If you have a previous version of Rust installed via rustup, getting Rust+1.47.0 is as easy as:++```console+rustup update stable+```++If you don't have it already, you can [get `rustup`][install] from the+appropriate page on our website, and check out the [detailed release notes for+1.47.0][notes] on GitHub.++[install]: https://www.rust-lang.org/tools/install+[notes]: https://github.com/rust-lang/rust/blob/master/RELEASES.md#version-1470-2020-10-08++## What's in 1.47.0 stable++This release contains no new language features, though it does add one+long-awaited standard library feature. It is mostly quality of life+improvements, library stabilizations and const-ifications, and toolchain+improvements. See the [detailed release notes][notes] to learn about other+changes not covered by this post.++#### Traits on larger arrays++Rust does not currently have a way to be generic over integer values. This+has long caused problems with arrays, because arrays have an integer as part+of their type; `[T; N]` is the type of an array of type `T` of `N` length.+Because there is no way to be generic over `N`, you have to manually implement+traits for arrays for every `N` you want to support. For the standard library,+it was decided to support up to `N` of 32.++We have been working on a feature called "const generics" that would allow+you to be generic over `N`. Fully explaining this feature is out of the scope+of this post, because we are not stabilizing const generics just yet.+However, the core of this feature has been implemented in the compiler, and+it has been decided that the feature is far enough along that we are okay+with [the standard library using it to implement traits on arrays of any+length](https://github.com/rust-lang/rust/pull/74060/). What this means in+practice is that if you try to do something like this on Rust 1.46:++```rust+fn main() {+    let xs = [0; 34];+    +    println!("{:?}", xs);+}+```++you'd get this error:++```text+error[E0277]: arrays only have std trait implementations for lengths 0..=32+ --> src/main.rs:4:22+  |+4 |     println!("{:?}", xs);+  |                      ^^ the trait `std::array::LengthAtMost32` is not implemented for `[{integer}; 34]`+  |+  = note: required because of the requirements on the impl of `std::fmt::Debug` for `[{integer}; 34]`+  = note: required by `std::fmt::Debug::fmt`+  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)+```++But with Rust 1.47, it will properly print out.++This should make arrays significantly more useful to folks, though it will+take until the const generics feature stabilizes for libraries to fully be+able to do this kind of implementation for their own traits. We do not have+a current estimated date for the stabilization of const generics.++#### Shorter backtraces++Back in Rust 1.18, we [made some changes to the backtraces `rustc` would+print on panic](https://github.com/rust-lang/rust/pull/38165). There are a+number of things in a backtrace that aren't useful the majority of the time.+However, at some point, [these+regressed](https://github.com/rust-lang/rust/issues/47429). In Rust 1.47.0,+the culprit was found, and [this has now been+fixed](https://github.com/rust-lang/rust/pull/75048). Since the regression,+this program:++```rust+fn main() {+    panic!();+}+```++would give you a backtrace that looks like this:++```text+thread 'main' panicked at 'explicit panic', src/main.rs:2:5+stack backtrace:+   0: backtrace::backtrace::libunwind::trace+             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86+   1: backtrace::backtrace::trace_unsynchronized+             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66+   2: std::sys_common::backtrace::_print_fmt+             at src/libstd/sys_common/backtrace.rs:78+   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt+             at src/libstd/sys_common/backtrace.rs:59+   4: core::fmt::write+             at src/libcore/fmt/mod.rs:1076+   5: std::io::Write::write_fmt+             at src/libstd/io/mod.rs:1537+   6: std::sys_common::backtrace::_print+             at src/libstd/sys_common/backtrace.rs:62+   7: std::sys_common::backtrace::print+             at src/libstd/sys_common/backtrace.rs:49+   8: std::panicking::default_hook::{{closure}}+             at src/libstd/panicking.rs:198+   9: std::panicking::default_hook+             at src/libstd/panicking.rs:217+  10: std::panicking::rust_panic_with_hook+             at src/libstd/panicking.rs:526+  11: std::panicking::begin_panic+             at /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libstd/panicking.rs:456+  12: playground::main+             at src/main.rs:2+  13: std::rt::lang_start::{{closure}}+             at /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libstd/rt.rs:67+  14: std::rt::lang_start_internal::{{closure}}+             at src/libstd/rt.rs:52+  15: std::panicking::try::do_call+             at src/libstd/panicking.rs:348+  16: std::panicking::try+             at src/libstd/panicking.rs:325+  17: std::panic::catch_unwind+             at src/libstd/panic.rs:394+  18: std::rt::lang_start_internal+             at src/libstd/rt.rs:51+  19: std::rt::lang_start+             at /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libstd/rt.rs:67+  20: main+  21: __libc_start_main+  22: _start+```++Now, in Rust 1.47.0, you'll see this instead:++```text+thread 'main' panicked at 'explicit panic', src/main.rs:2:5+stack backtrace:+   0: std::panicking::begin_panic+             at /rustc/d6646f64790018719caebeafd352a92adfa1d75a/library/std/src/panicking.rs:497+   1: playground::main+             at ./src/main.rs:2+   2: core::ops::function::FnOnce::call_once+             at /rustc/d6646f64790018719caebeafd352a92adfa1d75a/library/core/src/ops/function.rs:227+```++This makes it much easier to see where the panic actually originated, and+you can still set `RUST_BACKTRACE=full` if you want to see everything.++#### LLVM 11++We have [upgraded to LLVM 11](https://github.com/rust-lang/rust/pull/73526/).+The compiler still supports being compiled with LLVM versions as old as 8,+but by default, 11 is what you'll be getting.++#### Control Flow Guard on Windows++`rustc` [now supports](https://github.com/rust-lang/rust/pull/73893/) `-C+control-flow-guard`, an option that will turn on [Control Flow+Guard](https://docs.microsoft.com/en-us/windows/win32/secbp/control-flow-guard)+on Windows. Other platforms ignore this flag.++### Library changes++[Rustdoc has gained support for the Ayu theme](https://github.com/rust-lang/rust/pull/71237/).

That feels weird to call out as a library change.

steveklabnik

comment created time in 18 days

PullRequestReviewEvent

startedtermhn/ultraviolet

started time in 21 days

create barnchLiveSplit/livesplit-core

branch : dev-container

created branch time in 22 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 1201e50a23fbfe6336c312b2111df097b7864363

deploy: e5133c07041a641334a3375311454e5ecde1e202

view details

push time in 24 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha a03ce9dd5dbc5afe33a2e66c52f8030afaeb0209

deploy: d1b3d6549d843b3ae0c5ffe382e56bb18fc8e664

view details

push time in 24 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 3e909432e31699b777735ccf17acca6ca83a8ba0

deploy: 7699dcfb14a133068a158333e5f43108fa221d28

view details

push time in 24 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 6dffd8ed76e37050c5e358d09b7462573314dc1b

deploy: b3628595e955ba0edb16d75be608a945275e1fd0

view details

push time in 24 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 2f744fb813616d59d0182a5a52ea1bc21a3f121d

deploy: ad39d520783d29f42c4f51d25a957fbcfd1062f5

view details

push time in 24 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 12ee8dda230f9656fbdcbc64aa58047589b144f7

deploy: 1dc06885e446fa1399f2a7986ce6108a5caa4eb4

view details

push time in 24 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha d4471e239801565d7d8487c3161f97665a8c939b

deploy: 8f30b1b9b1bdf4f61d1bac8a03602190ff633651

view details

push time in 24 days

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha e896ec1140ef1e71ff1df199383425c95ec78db5

deploy: cdcb021391ae862a93fb938ec853ce23c9b7402b

view details

push time in 24 days

pull request commentrust-lang/rust

Fix is_absolute on WASI

I believe to some degree that's intentional. There's various documentation stating there's no absolute paths on WASI.

RReverser

comment created time in 24 days

issue commentchronotope/chrono

#478 breaks illumos

I haven't reported it yet, but I'm running into the same issue: https://github.com/LiveSplit/livesplit-core/runs/1180564388?check_suite_focus=true#step:6:255

papertigers

comment created time in 25 days

push eventLiveSplit/livesplit-core

Christopher Serr

commit sha 39d5c9d2093de1044b15218362ed068a19b4e0b2

Don't layer the find calls

view details

push time in a month

push eventLiveSplit/livesplit-core

Christopher Serr

commit sha 90258ec7ade06b300934bcaad63558f0fab4b621

Skip benchmarking the library

view details

push time in a month

startedchmoder/criterion.dev

started time in a month

issue openedchmoder/criterion.dev

The action doesn't seem to work if you have tests

When I run cargo bench on my project, it seems to also look for benchmarks in my tests or so (?) at which point it fails to recognize the options passed to criterion and cargo bench errors out. This then causes the action to fail.

https://github.com/LiveSplit/livesplit-core/runs/1179311859?check_suite_focus=true#step:3:385

created time in a month

push eventLiveSplit/livesplit-core

Christopher Serr

commit sha 907168a575453f961c1526d63ea75c082b8fc25e

Fix benchmarks

view details

push time in a month

push eventLiveSplit/livesplit-core

Christopher Serr

commit sha 8f7375aa6c13e44288f1f124f57a2e2862b2a39a

Create bench.yml

view details

push time in a month

pull request commentchronotope/chrono

The wasm-bindgen code refers to oldtime::Duration and is failing

Looks like this fixes my build issues 👍

quodlibetor

comment created time in a month

pull request commentchronotope/chrono

Absorb the time crate

Seems like wasm here seems to unconditionally depend on oldtime and I'm not using default-features, so yeah exactly what @jhpratt described broke my crate.

jjpe

comment created time in a month

pull request commentchronotope/chrono

Absorb the time crate

Doesn't seem like chrono even builds by itself:

 Compiling chrono v0.4.16
error[E0433]: failed to resolve: use of undeclared type or module `oldtime`
   --> C:\Users\Christopher Serr\.cargo\registry\src\github.com-1ecc6299db9ec823\chrono-0.4.16\src\offset\local.rs:155:27       
    |
155 |         local -= oldtime::Duration::seconds(offset.local_minus_utc() as i64);
    |                           ^^^^^^^^ not found in `oldtime`
    |
help: consider importing one of these items
    |
9   | use Duration;
    |
9   | use wasm_bindgen::__rt::core::time::Duration;
    |
jjpe

comment created time in a month

issue commentrust-lang/rust

Inlining of `let` should preserve borrowing soundness on "pure" left arguments

What Jonas seemed wanted to basically say is that there is already work ongoing towards the problem that you encountered. The solution is to extend the borrow checker to support two-phase borrows, i.e. a borrow happens earlier, but isn't used until later. This is roughly the solution that you propose as far as I can tell. Two-phase borrows were intended to be part of Rust 2018, but got disabled again. If I recall correctly it's unclear how to integrate it into the stacked borrows memory model, which defines which pointer interactions are defined behavior and which are not. The order of borrowing is really important in that case. So not only does it affect the borrow checker but also potential aliasing semantics that allow certain optimizations and cause certain undefined behavior. Don't quote me on all that though, that's just roughly what I recall. Nonetheless, all that work is tracked in the linked issue, which is why your issue got closed as basically a duplicate. Feel free to contribute to two-phase borrows though.

jeapostrophe

comment created time in a month

Pull request review commentrust-lang/rust

Make char::is_ascii_whitespace branchless on 64-bit targets

 impl char {     #[rustc_const_stable(feature = "const_ascii_ctype_on_intrinsics", since = "1.47.0")]     #[inline]     pub const fn is_ascii_whitespace(&self) -> bool {-        match *self {-            '\t' | '\n' | '\x0C' | '\r' | ' ' => true,-            _ => false,+        #[cfg(target_pointer_width = "64")]

Seems a bit unfortunate of a gate as target pointer width doesn't always correlate with whether 64-bit registers are available, such as on the x32 ABI and WASM32.

lnicola

comment created time in a month

PullRequestReviewEvent

issue closedLiveSplit/LiveSplitOne

Cant get horizontal splits to work

Whenever i try to get horizontal splits to work in the layout options, it just stays vertical despite having horizontal selected.

closed time in a month

tac0tac0tac0

issue commentLiveSplit/LiveSplitOne

Cant get horizontal splits to work

Yeah, horizontal splits are not supported yet. There's already an open issue, so I'm closing it in favor of that: #159

tac0tac0tac0

comment created time in a month

pull request commentLiveSplit/livesplit-core

Add a Linux-only tool needed for Auto Splitting to work correctly.

I'd like to see a significant amount of documentation why this is necessary, why there's no other option and how someone using auto splitting on Linux needs to use this. Also keep in mind that the auto splitter runtime is meant to be a library that can be used outside of LiveSplit One / livesplit-core, so a general explanation is necessary. Preferably all of that would be in the README that you already created.

DarkRTA

comment created time in a month

Pull request review commentLiveSplit/livesplit-core

Add support for Auto Splitting to the c api.

 authors = ["Christopher Serr <christopher.serr@gmail.com>"] edition = "2018"  [dependencies]-livesplit-core = { path = "..", default-features = false, features = ["std"] }+livesplit-core = { path = "..", default-features = false, features = ["std", "auto-splitting"] }

This is the reason why I didn't pull it in yet. The problem is that unconditionally depending on auto splitting will break for example the web version. So this needs to be an optional feature. However at least atm we don't support features in the binding generator. So either the C API needs to stub out the implementation or we need to improve our binding generator.

DarkRTA

comment created time in a month

PullRequestReviewEvent
PullRequestReviewEvent

push eventCryZe/livesplit-one-desktop

Christopher Serr

commit sha fc11973e8a26f6967ab17d86d3eec185337242d3

Update dependencies

view details

Christopher Serr

commit sha bc77ebaa4a8341b3ca146efc9f30a78893fc7771

WIP

view details

push time in a month

push eventCryZe/livesplit-one-desktop

Christopher Serr

commit sha fc11973e8a26f6967ab17d86d3eec185337242d3

Update dependencies

view details

push time in 2 months

PR closed CryZe/livesplit-core

Auto-splitting for Linux

After discussion in discord where it was noted that the external crates I chose to use in #1 were unmaintained, it was decided to pull the relevant code into our crate. So, this is a re-written (and up to date) version of #1.

Still TODO unchecked items have been punted for now to future PRs:

  • [ ] The current implementation effectively requires running as root, even for processes owned by the local user.
    • there is a commonly set mitigation nowadays that only parent processes can ptrace/read memory from a process. So, if we launch the game via livesplit (or some helper program), it'd (probably) work.
  • [x] Process::scan_signature is mostly code that can be shared between the platforms, but it needs to have access to OS specific things for listing memory pages.
  • [x] Process::read is unsound. using bytemuck
  • [x] Linux: /proc/PID/maps is parsed line by line as a String, because it was far more convienent to do so. This should not be passing through String as it is not guaranteed to be UTF-8. Using nom instead (for now)
  • [ ] Reading memory of a 64 bit process from a 32 bit process will currently fail in both implementations. Granted, wasmtime currently fails to build for i686 targets.
    • [ ] Windows: ReadMemory takes pointer of native size
      • https://stackoverflow.com/a/36798492. In short, the 64bit version of ntdll is also loaded in WOW64 processes, so we can call the 64 bit version of ReadMemory. This might fail on Windows installed as 32bit, though.
    • [x] Linux: process_vm_readv takes pointer of native size using /proc/pid/mem instead.
  • Autosplitter API (can wait for another PR or something)
  • env::read_into_buf should really return an errorcode if it isn't already.
  • set_process_name is somewhat insufficient for autosplitters that want to be able to run for e.g. "hl2.exe", "hl2_linux", "portal2.exe", and "portal2_linux".
  • I may take the time to implement more platforms, but I would be completely unable to test them.
  • process::Error is... not a particularly useful error type in it's current iteration.
+512 -195

7 comments

4 changed files

kitlith

pr closed time in 2 months

pull request commentCryZe/livesplit-core

Auto-splitting for Linux

The current auto-splitting branch is now in the livesplit-core repository containing your changes, so this can be closed. Feel free to open PRs against that branch in the main livesplit-core repo:

https://github.com/LiveSplit/livesplit-core/tree/auto-splitting

kitlith

comment created time in 2 months

issue commentLiveSplit/livesplit-core

Implement Auto Splitting

This branch is now the official branch that we are working on. Feel free to do PRs against it:

https://github.com/LiveSplit/livesplit-core/tree/auto-splitting

CryZe

comment created time in 2 months

create barnchLiveSplit/livesplit-core

branch : auto-splitting

created branch time in 2 months

push eventCryZe/livesplit-one-desktop

Christopher Serr

commit sha c6a496a5bad7ab6b907d5872afabb6671c4ba4f1

Update dependencies

view details

push time in 2 months

push eventCryZe/livesplit-core

wooferzfg

commit sha 0c4e790682b4962cfc3f28bcf8480ea42de56f53

Use img_hash for rendering tests

view details

Christopher Serr

commit sha b8eb5686f81e35c2557d770dd7fca4b2e841e6fb

Merge pull request #292 from wooferzfg/perceptual-hashing Use img_hash for rendering tests

view details

Christopher Serr

commit sha eafe14bff6dd57a81d236fc7ebdf544314e562dd

Improve Annotations on CI

view details

Christopher Serr

commit sha c18aa5fcf6ddf6eaf6f6459c7facca90b5ac1995

Fix some Annotations

view details

Dark

commit sha 1b52a7f73f93d97f0aec096d534fd733dcd0515c

Run Fixing Algorithms when opening splits closes #21

view details

Christopher Serr

commit sha 8988f95aa7ba51dd1632b75f48bef7d16b9e8f75

Merge pull request #294 from CryZe/ci-clippy Improve Annotations on CI

view details

Christopher Serr

commit sha a9c0ebc1a4ba7e5def31ee7ce82a0e568d91c79a

Merge pull request #295 from TheEssenceOfDarkness/fix-splits Run Fixing Algorithms when opening splits

view details

Sergey Papushin

commit sha 18bc6e8c6f818586519028ed6e563a74435a6f70

Fix up README

view details

Christopher Serr

commit sha d4bc439bb24a330ad68ab61c3af1ff21b8b88ef9

Remove emscripten It's not feasible to maintain emscripten support anymore. We don't use emscripten and it breaks all the time. Fixing it is hard because without it being used anywhere, you don't know if the fix actually worked. Additionally Edge is now using Chromium and we are long past supporting Internet Explorer. If anyone ever intends to use a JS version of livesplit-core again, they can use `wasm2js` to still compile the wasm that we produce to JS. The output is quite large, but it should work.

view details

Christopher Serr

commit sha 37f91220c98ed8a8e9ef08b35673cdcf82a7ebae

Merge pull request #299 from CryZe/remove-emscripten Remove emscripten

view details

Dark

commit sha baeaf9f807d515b6dce88232471a47c1e6f39fa1

capi: Make minor fixes

view details

Christopher Serr

commit sha 71283fb09b948d491b75a4f4edf206953b452393

Merge pull request #290 from TheEssenceOfDarkness/misc-fixes capi: Make some minor fixes

view details

Dark

commit sha a49a4c27effdf3226492b248b98b63d0fe01e9d6

capi: Expose Layout State object

view details

Christopher Serr

commit sha fe55323d5504544d0b7374a4f37bfdefec7761f7

Merge pull request #289 from TheEssenceOfDarkness/layout-state-capi capi: Expose Layout State object

view details

Christopher Serr

commit sha a612a46ce2224aac1cbd8533ec2dfbcdf335cac7

Improve compile times We are bottlenecked by syn and snafu when doing a release build. Rust 1.41 introduces a way to compile them without optimizations, which almost reduces our clean release build times from around 2m 40s to 1m 27s, which is huge.

view details

Christopher Serr

commit sha facd63472f6edad5d82027ef267ef46edd638ace

Deactive RISC-V without atomics in CI

view details

Christopher Serr

commit sha 2e3b1bf87c8a773a41f6fabf05e348b54a6e4bb4

Do periodic security audits

view details

Christopher Serr

commit sha 5cde45b4e2a8f71f9f8a209d52d2b6f192764640

Use hashbrown 0.7.0

view details

Christopher Serr

commit sha 48c669bc173042302c4197fb63f65d7fbb2d9633

Manually install Rust compiler for Audit Check

view details

Christopher Serr

commit sha 64edb9a7fa931fb46226333aaeabfad78a02ae96

Update image to 0.23.0 This also finally gets rid of 0.x versions of syn, which is a slow dependency to compile.

view details

push time in 2 months

push eventCryZe/AHatInTimeAutoSplitter

Carlos

commit sha 893beeb8ecc09e64fd6a1212e76411322cd28f62

Disabled splits while in main menu Also added a detected patch condition in the death wish back to hub split, and replaced tabs with spaces

view details

Christopher Serr

commit sha 65f1306bcff827717cd6401b7a31c282f5a4f076

Merge pull request #4 from cccarl/master Disabled splits while in main menu and other small changes.

view details

push time in 2 months

PR merged CryZe/AHatInTimeAutoSplitter

Disabled splits while in main menu and other small changes.

A runner was getting random splits in the main menu since they start their timer manually so I fixed it for them.

Also added a detected patch condition in the death wish back to hub split, and replaced tabs with spaces.

+24 -19

0 comment

1 changed file

cccarl

pr closed time in 2 months

issue commentrust-lang/rust

WASM-blob built by rustc fails in binaryen's validator

Exported mutable globals were not a thing in the MVP but are now part of the spec. So this sounds more like that validator is misconfigured or out of date.

https://github.com/WebAssembly/mutable-global/blob/master/proposals/mutable-global/Overview.md#importexport-mutable-globals

lukaslueg

comment created time in 2 months

Pull request review commentrust-lang/rust

Add format_to! macro

 impl String {         let slice = self.vec.into_boxed_slice();         unsafe { from_boxed_utf8_unchecked(slice) }     }++    #[unstable(feature = "liballoc_internals", issue = "none", reason = "implementation detail")]+    #[doc(hidden)]+    pub fn __push_fmt(&mut self, args: fmt::Arguments<'_>) {

Well I guess it would have to have the same signature. So I guess the unwrapping would unfortunately stay in that case.

matklad

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentrust-lang/rust

Add format_to! macro

 impl String {         let slice = self.vec.into_boxed_slice();         unsafe { from_boxed_utf8_unchecked(slice) }     }++    #[unstable(feature = "liballoc_internals", issue = "none", reason = "implementation detail")]+    #[doc(hidden)]+    pub fn __push_fmt(&mut self, args: fmt::Arguments<'_>) {

Why can't it just be an inherent write_fmt method, so write!(...) always works on String instead of introducing a semi-hidden method and a whole new macro?

matklad

comment created time in 2 months

PullRequestReviewEvent

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha bc55f5fe87c1f98a0ef54395328ac9ee38726b53

deploy: 6a3f4da3e0683bdaf4c3a5e4aefb42c11a281da4

view details

push time in 2 months

issue commentrust-lang/rust

Implement likely/unlikely intrinsic (tracking issue for RFC 1131)

Similar to the attributes on match cases, the attributes could be applied to enum variants, so it would be

enum Result<T, E> {
    #[likely]
    Ok(T),
    Err(E),
}
nikomatsakis

comment created time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 42c165829d240e8b53cd9321cfa797060ac09496

deploy: f9accde0e8805ae53d358e84b0307bb4fe24d848

view details

push time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 997f3cd67849864992d0769078a84b203390326f

deploy: 3c0db925cb2634de6f922fdcea8ac10664343cf8

view details

push time in 2 months

push eventLiveSplit/LiveSplitOne

CryZe

commit sha 4a71af326f18f1b9da8a7166ab96031a2767132b

deploy: a65a435324c9e1ea465feec3b933f5178e3dcd76

view details

push time in 2 months

push eventLiveSplit/LiveSplitOne

CryZe

commit sha 8172591f8b8326a6e4d70c532f8fde46cca2a1ff

deploy: 9bffe2f8a44328391096a05e021b03cf0e139571

view details

push time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 61f835e7adfd95c5bc4cec5990f44927521a9679

deploy: 687bca8f5e54073cf2ae52aea54b52e19ad6416b

view details

push time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 218b88f498e7fba64cc0ac89b45911a7b1acaba1

deploy: ecca87ecf3db408ec5788a1411073dc66a0b2001

view details

push time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha d6c054a1409f1a3a87200cb874fcd4720cdf45b9

deploy: 87d3be930a2a9b845995d408b3ecff513d1cd7e0

view details

push time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha d5d30edb0a4dba824a1a870e87a0c92b87caaf2f

Bump react-resizable from 1.10.1 to 2.0.0 Bumps [react-resizable](https://github.com/STRML/react-resizable) from 1.10.1 to 2.0.0. - [Release notes](https://github.com/STRML/react-resizable/releases) - [Changelog](https://github.com/STRML/react-resizable/blob/master/CHANGELOG.md) - [Commits](https://github.com/STRML/react-resizable/compare/v1.10.1...v2.0.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

Christopher Serr

commit sha a65a435324c9e1ea465feec3b933f5178e3dcd76

Merge pull request #410 from LiveSplit/dependabot/npm_and_yarn/react-resizable-2.0.0 Bump react-resizable from 1.10.1 to 2.0.0

view details

push time in 2 months

PR merged LiveSplit/LiveSplitOne

Bump react-resizable from 1.10.1 to 2.0.0 dependencies

Bumps react-resizable from 1.10.1 to 2.0.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/STRML/react-resizable/blob/master/CHANGELOG.md">react-resizable's changelog</a>.</em></p> <blockquote> <h3>2.0.0</h3> <ul> <li>⚠ Breaking Change! <ul> <li><code><Resizable></code> used to pass unknown props onto its child. For example: <pre lang="js"><code><Resizable foo="bar"><div /></Resizable> </code></pre> In this example, when <code><Resizable></code> wrapped its child <code>div</code>, it would pass on <code>foo="bar"</code>. This has been removed.</li> <li>I do not expect meaningful breakage in the wild from this change, as the behavior in 1.x was unexpected and not generally useful.</li> <li>If this change breaks your use case, please pass props directly to the child component rather than expecting <code><Resizable></code> to pass it downward.</li> <li>See <a href="https://github-redirect.dependabot.com/STRML/react-resizable/pull/133">#133</a> for more details.</li> </ul> </li> <li>➕ Feature: <code><ResizableBox></code> now takes a <code>style</code> prop which will be applied on the wrapping <code><div></code>. <code>width</code> and <code>height</code> in this prop are ignored.</li> <li>🐛 Bugfix: remove unknown Prop <code>handle</code> from div children in Resizable <code>React.cloneElement</code>. <a href="https://github-redirect.dependabot.com/STRML/react-resizable/issues/124">#124</a></li> <li>🐛 Bugfix: Fix top and left resizing jerkiness. Thanks <a href="https://github.com/conor-kelleher">@conor-kelleher</a>. <a href="https://github-redirect.dependabot.com/STRML/react-resizable/pull/136">#136</a></li> <li>✏ Chore: Improved test suite. Please contribute tests for your use cases if you have the time, I would really appreciate it! Thanks very much, <a href="https://github.com/Danielecina">@Danielecina</a></li> <li>✏ Chore: Minor internal refactors and additional tests.</li> <li>✏ Chore: Additional examples.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/STRML/react-resizable/commit/d423898fa1b2596da18e3dc652899b7c02f59143"><code>d423898</code></a> v2.0.0</li> <li><a href="https://github.com/STRML/react-resizable/commit/d5527955d639b457247e63f06c35e82541ac1d7b"><code>d552795</code></a> docs(changelog): prepare for 2.0.0, again</li> <li><a href="https://github.com/STRML/react-resizable/commit/69b804a7e9c9de07b576910f6e9454f552192644"><code>69b804a</code></a> feat(test): fixup test definitions in package.json</li> <li><a href="https://github.com/STRML/react-resizable/commit/7086c55e148c3c474876f92a3c21a972804e1c55"><code>7086c55</code></a> feat(ResizableBox): Accept a "style" param</li> <li><a href="https://github.com/STRML/react-resizable/commit/ef2a9226a952417c2cb02d8fdaa8854d2b1442ee"><code>ef2a922</code></a> test(Resizable): transformScale tests</li> <li><a href="https://github.com/STRML/react-resizable/commit/280869e16c4ebe1daea9378d3001a9e15972d1d5"><code>280869e</code></a> refactor(Resizable): apply transformScale only once and add examples</li> <li><a href="https://github.com/STRML/react-resizable/commit/3178a83d73eb65f6649f9dca90a7db2eec4738d0"><code>3178a83</code></a> refactor(Resizable): just store the DOMRect as lastHandleRect</li> <li><a href="https://github.com/STRML/react-resizable/commit/6f33d033b6ba04208770bee23685b704021a9889"><code>6f33d03</code></a> refactor(Resizable): simplify <Resizable> logic and update tests</li> <li><a href="https://github.com/STRML/react-resizable/commit/0ba35f7891173ef9076de5625e9a35652e576e72"><code>0ba35f7</code></a> refactor(example): clean up css, class names, some language</li> <li><a href="https://github.com/STRML/react-resizable/commit/6684a5b14ceb04eeaaba5ff2075bc259c83255dc"><code>6684a5b</code></a> Fix top-left resizing - account for new position when calling back onResize (...</li> <li>Additional commits viewable in <a href="https://github.com/STRML/react-resizable/compare/v1.10.1...v2.0.0">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will not automatically merge this PR because it includes an out-of-range update to a production dependency.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+7 -7

0 comment

2 changed files

dependabot-preview[bot]

pr closed time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 975b98b160fb49efc004e8bf85f7f2ae7dcdaff8

Bump sass-loader from 8.0.2 to 10.0.1 Bumps [sass-loader](https://github.com/webpack-contrib/sass-loader) from 8.0.2 to 10.0.1. - [Release notes](https://github.com/webpack-contrib/sass-loader/releases) - [Changelog](https://github.com/webpack-contrib/sass-loader/blob/master/CHANGELOG.md) - [Commits](https://github.com/webpack-contrib/sass-loader/compare/v8.0.2...v10.0.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

Christopher Serr

commit sha 9bffe2f8a44328391096a05e021b03cf0e139571

Merge pull request #414 from LiveSplit/dependabot/npm_and_yarn/sass-loader-10.0.1 Bump sass-loader from 8.0.2 to 10.0.1

view details

push time in 2 months

PR merged LiveSplit/LiveSplitOne

Bump sass-loader from 8.0.2 to 10.0.1 dependencies

Bumps sass-loader from 8.0.2 to 10.0.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/webpack-contrib/sass-loader/releases">sass-loader's releases</a>.</em></p> <blockquote> <h2>v10.0.1</h2> <h3><a href="https://github.com/webpack-contrib/sass-loader/compare/v10.0.0...v10.0.1">10.0.1</a> (2020-08-25)</h3> <h3>Chore</h3> <ul> <li>update deps</li> </ul> <h2>v10.0.0</h2> <h2><a href="https://github.com/webpack-contrib/sass-loader/compare/v10.0.0-rc.0...v10.0.0">10.0.0</a> (2020-08-24)</h2> <h3>Bug Fixes</h3> <ul> <li>handle absolute windows path in source maps</li> </ul> <p>See notes for <a href="https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.0-rc.0">https://github.com/webpack-contrib/sass-loader/releases/tag/v10.0.0-rc.0</a> release</p> <h2>v10.0.0-rc.0</h2> <h2><a href="https://github.com/webpack-contrib/sass-loader/compare/v9.0.3...v10.0.0-rc.0">10.0.0-rc.0</a> (2020-08-24)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>loader generates absolute <code>sources</code> in source maps, also avoids modifying <code>sass</code> source maps if the <code>sourceMap</code> option is <code>false</code></li> </ul> <h2>v9.0.3</h2> <h3><a href="https://github.com/webpack-contrib/sass-loader/compare/v9.0.2...v9.0.3">9.0.3</a> (2020-08-05)</h3> <h3>Bug Fixes</h3> <ul> <li>resolution algorithm (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/875">#875</a>) (<a href="https://github.com/webpack-contrib/sass-loader/commit/ea73cfab047c751e1055d0c2ec58ef503f7dbe36">ea73cfa</a>)</li> </ul> <h2>v9.0.2</h2> <h3><a href="https://github.com/webpack-contrib/sass-loader/compare/v9.0.1...v9.0.2">9.0.2</a> (2020-07-07)</h3> <h3>Bug Fixes</h3> <ul> <li>resolution algorithm for <code>node-sass</code> (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/866">#866</a>) (<a href="https://github.com/webpack-contrib/sass-loader/commit/4584c9054befbc56661e2781a55df96fb9f94673">4584c90</a>)</li> </ul> <h2>v9.0.1</h2> <h3><a href="https://github.com/webpack-contrib/sass-loader/compare/v9.0.0...v9.0.1">9.0.1</a> (2020-07-03)</h3> <h3>Bug Fixes</h3> <ul> <li>do not crash on errors (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/860">#860</a>) (<a href="https://github.com/webpack-contrib/sass-loader/commit/e8549330f8d9373ff8baccffbfd3e0c3b6f3ef61">e854933</a>)</li> </ul> <h2>v9.0.0</h2> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/webpack-contrib/sass-loader/blob/master/CHANGELOG.md">sass-loader's changelog</a>.</em></p> <blockquote> <h3><a href="https://github.com/webpack-contrib/sass-loader/compare/v10.0.0...v10.0.1">10.0.1</a> (2020-08-25)</h3> <h3>Chore</h3> <ul> <li>update deps</li> </ul> <h2><a href="https://github.com/webpack-contrib/sass-loader/compare/v10.0.0-rc.0...v10.0.0">10.0.0</a> (2020-08-24)</h2> <h3>Bug Fixes</h3> <ul> <li>handle absolute windows path in source maps</li> </ul> <h2><a href="https://github.com/webpack-contrib/sass-loader/compare/v9.0.3...v10.0.0-rc.0">10.0.0-rc.0</a> (2020-08-24)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>loader generates absolute <code>sources</code> in source maps, also avoids modifying <code>sass</code> source maps if the <code>sourceMap</code> option is <code>false</code></li> </ul> <h3><a href="https://github.com/webpack-contrib/sass-loader/compare/v9.0.2...v9.0.3">9.0.3</a> (2020-08-05)</h3> <h3>Bug Fixes</h3> <ul> <li>resolution algorithm (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/875">#875</a>) (<a href="https://github.com/webpack-contrib/sass-loader/commit/ea73cfab047c751e1055d0c2ec58ef503f7dbe36">ea73cfa</a>)</li> </ul> <h3><a href="https://github.com/webpack-contrib/sass-loader/compare/v9.0.1...v9.0.2">9.0.2</a> (2020-07-07)</h3> <h3>Bug Fixes</h3> <ul> <li>resolution algorithm for <code>node-sass</code> (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/866">#866</a>) (<a href="https://github.com/webpack-contrib/sass-loader/commit/4584c9054befbc56661e2781a55df96fb9f94673">4584c90</a>)</li> </ul> <h3><a href="https://github.com/webpack-contrib/sass-loader/compare/v9.0.0...v9.0.1">9.0.1</a> (2020-07-03)</h3> <h3>Bug Fixes</h3> <ul> <li>do not crash on errors (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/860">#860</a>) (<a href="https://github.com/webpack-contrib/sass-loader/commit/e8549330f8d9373ff8baccffbfd3e0c3b6f3ef61">e854933</a>)</li> </ul> <h2><a href="https://github.com/webpack-contrib/sass-loader/compare/v8.0.2...v9.0.0">9.0.0</a> (2020-07-02)</h2> <h3>⚠ BREAKING CHANGES</h3> <ul> <li>minimum supported Nodejs version is <code>10.13</code></li> <li>prefer <code>sass</code> (<code>dart-sass</code>) by default, it is strongly recommended to migrate on <code>sass</code> (<code>dart-sass</code>)</li> <li>the <code>prependData</code> option was removed in favor the <code>additionalData</code> option, see <a href="https://github.com/webpack-contrib/sass-loader#additionaldata">docs</a></li> <li>when the <code>sourceMap</code> is <code>true</code>, <code>sassOptions.sourceMap</code>, <code>sassOptions.sourceMapContents</code>, <code>sassOptions.sourceMapEmbed</code>, <code>sassOptions.sourceMapRoot</code> and <code>sassOptions.omitSourceMapUrl</code> will be ignored.</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/b3a19813a5574ee26f7bbc4b035c236d9edaa3df"><code>b3a1981</code></a> chore(release): 10.0.1</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/716d2bf585600e43df46028020c91ffdf5b26cce"><code>716d2bf</code></a> chore(deps): update (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/884">#884</a>)</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/d1517085071692480db70f1b06b113bbf8231427"><code>d151708</code></a> chore(release): 10.0.0</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/32491c1f347399cfde9c0ac9f7c612daef8ac33f"><code>32491c1</code></a> refactor: improve <code>sources</code> checks (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/883">#883</a>)</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/7d8b8ab0e583486ce05ddf3eaa5b92919cf51c33"><code>7d8b8ab</code></a> chore(release): 10.0.0-rc.0</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/769a06e0901c297ca1ce6c08742643ad5c9d4dca"><code>769a06e</code></a> fix: generate absolute sources for source maps (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/882">#882</a>)</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/d2b532c3f5b3fa32be4ddff6126c9e49ccf3b60c"><code>d2b532c</code></a> refactor: export a decoupled Sass importer (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/874">#874</a>)</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/a8383177d030d6367be3658921e83c4dc2eb8212"><code>a838317</code></a> test: source maps (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/881">#881</a>)</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/d873b1574f5ac75d76a02f3e4bd20d7b470e27d7"><code>d873b15</code></a> chore(release): 9.0.3</li> <li><a href="https://github.com/webpack-contrib/sass-loader/commit/a255a9c46eb1dd3fbb4d2e72b9fc528c8ac6c29e"><code>a255a9c</code></a> refactor: code (<a href="https://github-redirect.dependabot.com/webpack-contrib/sass-loader/issues/877">#877</a>)</li> <li>Additional commits viewable in <a href="https://github.com/webpack-contrib/sass-loader/compare/v8.0.2...v10.0.1">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will not automatically merge this PR because it includes an out-of-range update to a development dependency.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+72 -45

0 comment

2 changed files

dependabot-preview[bot]

pr closed time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 5dfd7940ca3228d2b0518d998da826e8859337bb

Bump react-twemoji from 0.2.3 to 0.3.0 Bumps [react-twemoji](https://github.com/zxmys/react-twemoji) from 0.2.3 to 0.3.0. - [Release notes](https://github.com/zxmys/react-twemoji/releases) - [Commits](https://github.com/zxmys/react-twemoji/compare/0.2.3...0.3.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

view details

Christopher Serr

commit sha 4dd99b7baac46014884a04b584dd6297b163b247

Merge pull request #415 from LiveSplit/dependabot/npm_and_yarn/react-twemoji-0.3.0 Bump react-twemoji from 0.2.3 to 0.3.0

view details

push time in 2 months

PR merged LiveSplit/LiveSplitOne

Bump react-twemoji from 0.2.3 to 0.3.0 dependencies

Bumps react-twemoji from 0.2.3 to 0.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/zxmys/react-twemoji/releases">react-twemoji's releases</a>.</em></p> <blockquote> <h2>0.3.0</h2> <ul> <li>Update to Twemoji 13.0</li> <li>Also update other deps</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ZxMYS/react-twemoji/commit/7152ade40fd622b0effb6dbc60ac8d60d6570943"><code>7152ade</code></a> Publish 0.3.0</li> <li><a href="https://github.com/ZxMYS/react-twemoji/commit/8d67095cc2adc9e615bff001904beef7816ed4a3"><code>8d67095</code></a> Support new emojis (<a href="https://github-redirect.dependabot.com/zxmys/react-twemoji/issues/15">#15</a>)</li> <li><a href="https://github.com/ZxMYS/react-twemoji/commit/2bd964b0c5168a32e200c315ea6d40cdb0464ea2"><code>2bd964b</code></a> Bump elliptic from 6.4.1 to 6.5.3 (<a href="https://github-redirect.dependabot.com/zxmys/react-twemoji/issues/14">#14</a>)</li> <li><a href="https://github.com/ZxMYS/react-twemoji/commit/3ff80d42218112fb14cb262d58122e23fbde295e"><code>3ff80d4</code></a> Bump lodash from 4.17.11 to 4.17.19 (<a href="https://github-redirect.dependabot.com/zxmys/react-twemoji/issues/13">#13</a>)</li> <li><a href="https://github.com/ZxMYS/react-twemoji/commit/416856789bfdf401b92274ab9197bdae9d9c06d6"><code>4168567</code></a> Bump acorn from 6.1.1 to 6.4.1 (<a href="https://github-redirect.dependabot.com/zxmys/react-twemoji/issues/12">#12</a>)</li> <li><a href="https://github.com/ZxMYS/react-twemoji/commit/ef80f3783619b69e4ffd3072ce89fabb94858600"><code>ef80f37</code></a> Bump mixin-deep from 1.3.1 to 1.3.2 (<a href="https://github-redirect.dependabot.com/zxmys/react-twemoji/issues/11">#11</a>)</li> <li><a href="https://github.com/ZxMYS/react-twemoji/commit/06cc54b0ab0aa37debf840a6e00060db5252b3bc"><code>06cc54b</code></a> Bump eslint-utils from 1.3.1 to 1.4.2 (<a href="https://github-redirect.dependabot.com/zxmys/react-twemoji/issues/10">#10</a>)</li> <li>See full diff in <a href="https://github.com/zxmys/react-twemoji/compare/0.2.3...0.3.0">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will not automatically merge this PR because it includes an out-of-range update to a production dependency.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

</details>

+19 -42

0 comment

2 changed files

dependabot-preview[bot]

pr closed time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 2fdf7d3913b2b8aa9606e1a34f39c9d1c2ac14d0

deploy: 182be3af69f42a545f8201374730d5e6cf2c6a38

view details

push time in 2 months

push eventLiveSplit/LiveSplitOne

dependabot-preview[bot]

commit sha 5fcad0283c9f95f99d4a571d17c8513f5a2996b6

deploy: aea75fff2bcc0bf0d75a50db8984e1574f59545b

view details

push time in 2 months

Pull request review commentrust-lang/rust

Make String a must_use type

 impl DocFolder for Cache {         });          if pushed {-            self.stack.pop().expect("stack already empty");+            let _ = self.stack.pop().expect("stack already empty");

I agree with @scottmcm here. If it's on String, then it should be on Vec too, and if it's on Vec, then it should also be on every container. At which point you'd have to somewhat argue why it's not on basically everything that's not Copy.

lzutao

comment created time in 2 months

PullRequestReviewEvent

issue commentrust-analyzer/rust-analyzer

[Semantic Highlighting] Consuming modifier should apply to other cases

The current consuming highlighting doesn't seem to care about lvalues at all either, so I'd say that can be considered a separate issue.

CryZe

comment created time in 2 months

issue openedrust-analyzer/rust-analyzer

Consuming modifier should apply to other cases

At the moment it only seems to apply to the self argument of method calls. However the other arguments of the call may be consumed as well. Additionally cases like let y = x; should probably be covered too.

created time in 2 months

pull request commentrust-lang/blog.rust-lang.org

release blog post for Rust 1.46.0

I think it's weird how the blog post is labeling this release as a fairly minor release despite const fn being insanely powerful now while before you couldn't do any control flow at all. If you compare this to the 1.45 release blog post, it labels the fairly minor soundness fixes to floating point casts (which affected close to no one) as big changes. Seems a bit off to me.

steveklabnik

comment created time in 2 months

push eventCryZe/AHatInTimeAutoSplitter

Carlos

commit sha 69a2ebf451aee4cde14bd2c611f359b4fbbebddf

Added new features -Version detection -Split options for time pieces and death wish -IL mode -Option to start the timer only when opening empty files -Option to ask the user if game time should be used instead of real time when opening the game

view details

Christopher Serr

commit sha 5c830903b1e0693a73f5d5ba31c3c9eb3bd2cf36

Merge pull request #3 from cccarl/new-features Added new features

view details

push time in 2 months

PR merged CryZe/AHatInTimeAutoSplitter

Added new features
  • Version detection
  • Split options for time pieces and death wish
  • IL mode
  • Option to start the timer only when opening empty files
  • Option to ask the user if game time should be used instead of real time when opening the game
+72 -6

0 comment

1 changed file

cccarl

pr closed time in 2 months

issue commentrust-lang/rust-clippy

Slow suggestion of single_char_pattern

For non-ASCII it still seems to be slightly slower, but yeah, I'd say it's fine to recommend char now.

CryZe

comment created time in 2 months

issue closedrust-lang/rust-clippy

Slow suggestion of single_char_pattern

For str::starts_with using a single char string literal generates much better code as it can just compare the single byte of the str literal, while comparing against a char involves decoding possibly multiple bytes of the text. Here is the Godbolt for it: https://rust.godbolt.org/z/V_Arel

Therefore the single_char_pattern lint should not apply for str::starts_with (and possibly ends_with) and instead it should possibly even advice against using a char.

clippy 0.0.212 (b2601beb 2018-11-27)

closed time in 2 months

CryZe

pull request commentrust-lang/rust

Add the convenience method `Option::is_some_and`

You wouldn't need that, that's just .is_none() || ...

LukasKalbertodt

comment created time in 2 months

pull request commentrust-lang/rust

Add `[T; N]::as_ref` and `[T; N]::as_mut`

I'd actually say that Vec totally should have map as well, because it can potential reuse its backing memory if the target type has the same size and alignment. So map not existing (yet?) on Vec is not really an argument.

LukasKalbertodt

comment created time in 2 months

pull request commentrust-lang/rust

Add `[T; N]::as_ref` and `[T; N]::as_mut`

@scottmcm's arraytools calls them as_[mut/ref]_array

LukasKalbertodt

comment created time in 2 months

issue commentrust-analyzer/rust-analyzer

dbg postfix doesn't automatically close with semicolon

Why would you want a semi colon though? In a lot of cases the dbg! macro is used as an expression, not a statement.

GopherJ

comment created time in 2 months

push eventCryZe/AHatInTimeAutoSplitter

Carlos

commit sha 327314f5727f6b7fb82b9642dc6f789000b8b14a

Fix broken splits. Fix "rumbi factory" not splitting in patch DLC 2.1 and fixed splits happening once per frame after completing the finale.

view details

Christopher Serr

commit sha 7a4f06e3901e3c52ba30c95ed0850afdc42af42f

Merge pull request #2 from cccarl/SplitFix Fix broken splits.

view details

push time in 3 months

PR merged CryZe/AHatInTimeAutoSplitter

Fix broken splits.

Fixed "rumbi factory" not splitting in patch DLC 2.1 and fixed splits happening once per frame after completing The Finale.

Rumbi Factory example.
This happens because in that patch the Act Timer is not active for this time rift for some reason (most likely a mistake from GFB).

Finale splits example. This one happens because of the condition "vars.timerState.Current == 2".

Completely unrelated but this is my first time doing a pull request so I hope I didn't make any mistake here.

+1 -1

0 comment

1 changed file

cccarl

pr closed time in 3 months

Pull request review commentrust-lang/rust

Add `array` lang item and `[T; N]::map(f: FnMut(T) -> S)`

 macro_rules! array_impl_default { }  array_impl_default! {32, T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T T}++#[lang = "array"]+#[cfg(not(bootstrap))]+impl<T, const N: usize> [T; N] {+    /// Returns an array of the same aize as self, with `f` applied to each element.+    ///+    /// # Examples+    /// ```+    /// let x = [1,2,3];+    /// let y = x.map(|v| v + 1);+    /// assert_eq!(y, [2,3,4]);+    /// ```+    #[unstable(feature = "array_map", issue = "77777")]+    fn map<F, S>(self, f: F) -> [S; N]+    where+        F: FnMut(T) -> S,+    {+        use crate::mem::MaybeUninit;+        let dst = MaybeUninit::uninit_array::<N>();+        for (i, e) in self.into_iter().enumerate() {+            dst[i] = MaybeUninit::new(f(e));

Of dest because it's MaybeUninit so nothing will get dropped automatically.

JulianKnodt

comment created time in 3 months

issue openedzesterer/euc

Consider reexporting vek

vek's types are used in the public API. So a user of this crate needs to also depend on vek. Keeping both in sync however has been reasonably painful. Especially because dependabot is now sending me PRs all the time with new versions of vek that are incompatible with euc. It would probably make sense to either not publicly depend on vek or reexport it either entirely or enough to not have to depend on it as a user of euc.

created time in 3 months

issue commentrust-lang/rust

The way to use `include_bytes!` in a cross-platform way is not discoverable

Could it make sense for the include_*! macros to allow syntax like include_bytes!(env!("OUT_DIR") / "myfile")?

Shnatsel

comment created time in 3 months

issue commentmagcius/noclip.website

Doesn't work with Safari WebGL2 Experimental Beta

At least on iOS it seems to mostly works, but the shaders are super broken.

image

OKNoah

comment created time in 3 months

more