Skip to content

Instantly share code, notes, and snippets.

View fu5ha's full-sized avatar
🏳️‍🌈

Gray Olson fu5ha

🏳️‍🌈
View GitHub Profile
@fu5ha
fu5ha / peacock.md
Last active December 27, 2022 16:03

Leaderboards / same contract

This is the only argument I actually buy. That said, it should be totally doable to make the /leaderboard bot integrate with peacock's leaderboards. Peacock already allows downloading and playing contracts directly provided by f7sc on official epic and steam servers through hitmaps' api.

Server outage verification

It should be very easy to verify a major service outage by simply attempting to connect to the server with any other player's or admin's game copy; this is a non-issue IMO.

@fu5ha
fu5ha / parse.rs
Last active August 24, 2020 06:43
#[derive(Debug)]
enum PersonParseError {
Malformed,
AgeParseError(std::string::ParseError),
}
impl fmt::Display for PersonParseError {
fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
match *self {
PersonParseError::Malformed => write!(f, "Malformed or empty input string"),
benchmark ultraviolet nalgebra ultraviolet_f32x4 nalgebra_f32x4 ultraviolet_f32x8 nalgebra_f32x8 nalgebra_f32x16 ultraviolet_f64 nalgebra_f64 ultraviolet_f64x2 nalgebra_f64x2 ultraviolet_f64x4 nalgebra_f64x4
euler 3d x10000 31.77 us 31.8 us 10.28 us 11.58 us 8.324 us 8.447 us 8.778 us 31.37 us 26.79 us 22.3 us 26.37 us 20.72 us 20.62 us
G28 ; home
M420 S Z5 ; call on the auto level gods
G1 X25 Y25 F1500 ; avoid binder clips
G1 Z0.3 X25 Y20 F3000 ; get ready to prime
G92 E0 ; reset extrusion distance
G1 Y200 E20 F1000 ; prime nozzle
G1 X25.5 F1000; Move over slightly
G1 X25.5 Y20 E40 F1000; Wipe back
G92 E0 ; reset extrusion distance
G1 X15 Y20 F9000; Quick wipe then print
Finished dev [unoptimized + debuginfo] target(s) in 2.44s
Running `target\debug\examples\gltf.exe`
[WARN][rendy_factory::factory] Slow safety checks are enabled! Disable them in production by enabling the 'no-slow-safety-checks' feature!
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', /rustc/6c2484dc3c532c052f159264e970278d8b77cdc9\src\libcore\slice\mod.rs:2539:10
stack backtrace:
0: std::sys::windows::backtrace::set_frames
at /rustc/6c2484dc3c532c052f159264e970278d8b77cdc9\/src\libstd\sys\windows\backtrace\mod.rs:94
1: std::sys::windows::backtrace::unwind_backtrace
at /rustc/6c2484dc3c532c052f159264e970278d8b77cdc9\/src\libstd\sys\windows\backtrace\mod.rs:81
2: std::sys_common::backtrace::_print
#version 150 core
uniform sampler2D textureAtlas;
in vec2 v_TexCoord;
out vec4 Target0;
void main() {
Target0 = texture(textureAtlas, v_TexCoord);
}
warning: failed to automatically apply fixes suggested by rustc to crate `rendy_wsi`
after fixes were automatically applied the compiler reported errors within these files:
* wsi\src\lib.rs
This likely indicates a bug in either rustc or cargo itself,
and we would appreciate a bug report! You're likely to see
a number of compiler warnings after this message which cargo
attempted to fix but failed. If you could open an issue at
Finished dev [unoptimized + debuginfo] target(s) in 0.30s
Running `C:\Users\Gray\Code\rendy\target\debug\examples\quads.exe`
WARN 2018-12-05T08:27:25Z: gfx_backend_vulkan: Unable to find extension: VK_KHR_xlib_surface
WARN 2018-12-05T08:27:25Z: gfx_backend_vulkan: Unable to find extension: VK_KHR_xcb_surface
WARN 2018-12-05T08:27:25Z: gfx_backend_vulkan: Unable to find extension: VK_KHR_wayland_surface
WARN 2018-12-05T08:27:25Z: gfx_backend_vulkan: Unable to find extension: VK_KHR_mir_surface
WARN 2018-12-05T08:27:25Z: gfx_backend_vulkan: Unable to find extension: VK_KHR_android_surface
INFO 2018-12-05T08:27:25Z: rendy_factory::factory: Physical devices:
[
AdapterInfo {
  • Graphs and graph traversal
    • BFS
      • Applying directed/undirected graph
      • Distances (number of hops from origin to node), predecessors, layers, and BFS tree
    • DFS
      • Applying to DFS to a directed/undirected graph
      • Time stamps (discovered, finished), predecessors, DFS tree
    • O(n + m) time for graph with n vertices and m edges for both DFS and BFS
  • Strongly connected components
    • Means that every vertex can be reached (there is some directed path that exists) from every other vertex in the strongly connected group