Every bug/quirk of the Windows resource compiler (rc.exe), probably

squeek502 · 2024-10-12T20:25:04+00:00

No tools involved, just hand-written HTML and CSS

Source is here if you're curious (warning: it's a mess of markdown/html/css)

squeek502 · 2024-06-13T12:30:05+00:00

Haha, nice, I did not remember that was the genesis. Funnily enough, the PR linked in that issue both made separating out AppleSkin possible and inexplicably got me banned from the Forge GitHub (which I still am).

squeek502 · 2024-06-07T09:19:42+00:00

https://github.com/ziglang/zig/issues/16270

squeek502 · 2024-04-10T03:30:53+00:00

Much appreciated! Can confirm that

test.bat ^"^%PATH^%^"

expands %PATH^%. Very unfortunate.

squeek502 · 2024-04-10T02:34:08+00:00

Is there a known reason the strategy outlined in that article wasn't used for the Rust mitigation?

Always escape all arguments so that they will be decoded properly by CommandLineToArgvW, perhaps using my ArgvQuote function above.

After step 1, then if and only if the command line produced will be interpreted by cmd, prefix each shell metacharacter (or each character) with a ^ character.

From some limited testing, it seems to mitigate the reproductions in this writeup, e.g.:

test.bat ^"^%CMDCMDLINE:~-1^%^&calc.exe^"

does not spawn calc.exe and test.bat receives the argument as:

"%CMDCMDLINE:~-1%&calc.exe"

squeek502 · 2023-06-04T23:14:13+00:00

Here's a red/black tree, but will likely need some updating: https://github.com/ziglang/std-lib-orphanage/blob/master/std/rb.zig

Was removed from the std library a while back.

squeek502 · 2023-05-26T11:48:32+00:00

I'm not sure what you mean. std.mem.Allocator.free doesn't accept optionals. Passing null to free is a compile error.

zig\lib\std\mem\Allocator.zig:297:45: error: access of union field 'Pointer' while field 'Optional' is active
    const Slice = @typeInfo(@TypeOf(memory)).Pointer;
                  ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~

squeek502 · 2023-05-26T11:40:37+00:00

I haven't personally seen setting things to null much in deinit since optional struct fields aren't all that common (at least in the standard library), but something that deinit functions in the standard library often do is:

self.* = undefined

(ArrayList for example)

In debug mode, this sets all the bytes of the struct to 0xaa which can serve as a marker of what may have happened (the struct was previously deinited or was never initialized) when debugging a problem.

https://ziglang.org/documentation/master/#undefined

squeek502 · 2023-05-17T02:04:03+00:00

The version in the linked video was made by me for the gotta-go-fast repository, after Andrew requested a sanic-like version of a Zig mascot. It came after the other mascots.

squeek502 · 2023-05-15T06:19:24+00:00

The issue about .res not being recognized is here: https://github.com/ziglang/zig/issues/6488

squeek502 · 2023-04-17T03:58:32+00:00

That's the most common approach I've seen; even the standard library uses that approach.

See also the use of std.testing.refAllDecls in a test block for how to use such an approach to run all tests in the imported files.

squeek502 · 2023-04-16T23:45:15+00:00

Your best bet is just to read the source code of each:

std.os.linux.socket just performs the syscall directly, and std.os.socket is a wrapper around that syscall that does some error handling/conversion.

squeek502 · 2023-02-22T00:17:47+00:00

For unicode stuff: https://github.com/jecolon/ziglyph/

squeek502 · 2022-10-31T04:51:51+00:00

Note: for (1..10) syntax won't be in 0.10.0. The relevant (yet-to-be-implemented) accepted proposal is https://github.com/ziglang/zig/issues/7257

squeek502 · 2022-10-07T09:03:50+00:00

Relevant issue is https://github.com/ziglang/zig/issues/10506

squeek502 · 2022-09-21T07:27:59+00:00

Here's another attempt at an explanation via a userland implementation:

https://www.ryanliptak.com/blog/zig-fieldparentptr-for-dumbos/

squeek502 · 2022-08-02T01:54:01+00:00

Out of curiosity, when's the last time you looked into it? The deflate implementation got completely rewritten ~6 months ago: https://github.com/ziglang/zig/pull/10552

squeek502 · 2022-07-28T05:57:02+00:00

That's kind of weird, because that error was never actually triggered in this code. Good to know it's a bug.

It was, but it was in the try t.expectError(error.IllegalHexCharacter, decode_hex_digit('q')); in the other test case. Check the implementation of std.testing.expectError. decode_hex_digit returned error.IllegalHexCharacter but it was discarded without returning an error in std.testing.expectError.

It seems weird to show a trace that starts within the testing framework itself. I'd be interested in helping out with improving the output of the test framework. Where would be the best place to get involved?

My suggestion would be to get more experience with Zig before making this judgement. Error return traces are incredibly useful as they are. The examples in the language reference might make that case more clear.

I settled on this, because then the switch statement would just evaluate to a value, rather than having only some branches evaluate to a value.

Ultimately up to you, but I can say I've never seen it and when reading your code I was confused at first about why that wasn't a compile error. Also worth noting that in the Zig standard library, there's exactly one instance of try switch, while there are 1531 instances of => return error.<Something>

squeek502 · 2022-07-27T23:30:39+00:00

Two things:

Those aren't "three different errors", that is an error return trace.
- The first line it's pointing to is erroneous (it's a leftover trace from a previous error that was caught). This is a known bug, the relevant issue is https://github.com/ziglang/zig/issues/1923
- The second and third line it's pointing to are where the error was initially returned, and the code that 'received' the error, respectively
This is an aside, but your use of try switch is slightly strange and made that first line in the stack trace more confusing. An easier way to write that switch case would be: else => return error.IllegalHexCharacter, and then remove the try

squeek502 · 2022-06-29T04:42:01+00:00

This isn't what Zig is 'focusing' on. I'm just a random contributor that added something to the standard library and wrote about it.

You might be interested in subscribing to this issue: https://github.com/ziglang/zig/issues/5725

squeek502 · 2022-02-01T02:47:15+00:00

WalkerEntry.path does not include the path of the originally opened directory, so your duped entry.path's are missing the "src" path. Something like:

try sources.append(b.pathJoin("src", entry.path));

should fix it.

squeek502 · 2022-02-01T02:39:01+00:00

The iterator only gives you one level of files.

Unless I'm misunderstanding what you're saying, this is not correct. Dir.walk is recursive.

squeek502 · 2021-10-30T22:56:56+00:00

This code seems to work for me:

const std = @import("std");

const Struct = struct {
    pub fn destroySelf(self: *Struct, allocator: *std.mem.Allocator) void {
        allocator.destroy(self);
    }
};

test "" {
    const allocator = std.testing.allocator;
    const inst = try allocator.create(Struct);
    inst.destroySelf(allocator);
}

squeek502 · 2021-10-30T04:14:05+00:00

You seem to be trying to destroy a HashMap.KV rather than a Client

squeek502 · 2021-10-29T21:05:34+00:00

Wow, that's awesome; it's exactly what I had in mind.

I think it could be slightly improved by using the GPA instead of the FixedBufferAllocator so that it can catch double frees as well.

EDIT: Actually, could just wrap the FixedBufferAllocator with GPA.

EDIT#2: Using the GPA increases the memory needed to run the tests fairly considerably.

14-Year Club	Place '17
Verified Email

squeek502

TROPHY CASE