emirmrkaljevic

Activity

Stars and mentions · Last 30 days, Oct 20 – Nov 18

GitHub stars0
Mentions53
036912Oct 20Nov 3Nov 18
UTC days · repositories emirmrkaljevic owns0 repositories

Top repositories

emirmrkaljevic’s repositories ranked by new forks, as on trending.

Loading

Contributes to

Repositories outside emirmrkaljevic’s account where emirmrkaljevic opened or reviewed pull requests in the past 365 days.

Who noticed emirmrkaljevic

Everyone who starred or forked emirmrkaljevic’s repositories since the archive began in 2011.

Notable accounts

Ordered by the stars their own repositories have received.

Biggest fans

Accounts that starred the most of these repositories.

Breakout weeks

Each repository’s best week of new stars, with the release published around it.

Mentions

51posts
Nov 190 posts
  1. this github activity is completely fake github.com/emirmrkaljevic t.co

    8 views
  2. Behave: black-box differential tests for CLI rewrites (found 40 bugs in uutils) Hi all. I have been sending small fixes to the uutils projects (the Rust rewrites of coreutils, findutils, sed and procps), and most of the bugs I found came from one tool I built for it, so I thought it might be useful to others here who are porting a CLI to Rust. behave runs the original binary (for example GNU sort) as a black box with lots of inputs: flags, stdin, files, empty arguments, error paths. It records stdout, stderr and the exit code of each run as plain YAML test cases. Then it replays the same cases against the rewrite and prints every difference. So far that has led to 40 upstream bug reports and 47 fix PRs, 33 of them merged. Most differences are small: a missing error message, a different exit code, an empty-operand edge case. Those are the ones a hand-written test suite tends to skip. behave itself is written in Go (single binary, MIT), but it does not care what language either side is in. The recorded cases are just YAML, so they can live in your repo and run in CI against your Rust build. Repo: emirmrkaljevic/behave List of the upstream findings: github.com/emirmrkaljevic/behave/blob/main/docs/u… If you are rewriting a CLI tool in Rust, I would like to hear whether this fits your workflow and what is missing.

  3. behave vs uutils procps (GNU procps-ng 4.0.4): sysctl -o/-x swallowed the next key: procps#835 pmap -XX was rejected as a repeated -X (fix now merged): procps#838 emirmrkaljevic/behave

  4. truediscount now also works on Notino in 25 countries. It reads the shop's own 'lowest price in the last 30 days' and tells you if the Black Friday deal is real, all locally in your browser. Free and open source: emirmrkaljevic/truediscount

  5. I just shipped usb-rea v0.7.12. Give it a USB capture of a Windows-only vendor app (case LCD, RGB, mouse) and it infers the protocol and writes a Linux pyusb driver. New: usb-rea lookup checks a VID:PID against liquidctl, rivalcfg and OpenDeviceDB first. emirmrkaljevic/usb-rea

  6. ใช้ REA แล้วเสือกทำรายเดือน เจริญพร emirmrkaljevic/usb-rea

    18 views
  7. What 27 merged PRs taught me about testing a Rust rewrite as a black box --- title: "What 27 merged PRs taught me about testing a Rust rewrite as a black box" published: true tags: rust, testing, cli, opensource --- I have been recording how GNU coreutils 9.12 behaves, then replaying the same cases against uutils, the Rust rewrite. The recorder is behave: a Go CLI (and MCP server) that probes flags from --help, odd stdin, missing files, and other corners, then diffs stdout, stderr and exit codes. So far that work has led to about 30 bug reports and 37 fix PRs upstream. 27 of those PRs are merged. Here is what those merges taught me about black-box testing a rewrite, with concrete examples. 1. Match the reference release, not "whatever is on PATH" CI on Ubuntu often ships an older GNU than the release the rewrite targets. I record from GNU 9.12 because that is what uutils aims at. A case that is correct on 9.12 can fail on 9.4 (for example how wc or expand counts a multi-byte character). Specs that depend on a version gap stay out of CI, or they teach people to ignore failures. Lesson: pin the reference binary. Diffing against a random system coreutils produces noise that looks like product bugs. 2. Option precedence is where rewrites disagree quietly uutils#15381 (merged): with both --check and --merge, GNU sort lets --check win. The rewrite preferred --merge. No crash, just the wrong mode. uutils#16114 (merged): seq treated an option-looking token before the first operand as data, so seq -inf 1 could loop. GNU parses those as options. uutils#15529 (merged): bare tail -c and obsolete +NUM under _POSIX2_VERSION did not match GNU. These are not exotic. They show up as soon as a probe walks every flag pair and every help-listed value. Unit tests written from the author's mental model rarely hit "both flags at once" or "option-shaped operand". 3. Limits and overflows hide in "it worked for small inputs" uutils#16181 (merged): base64 -w with a width too large to represent still tried to wrap. GNU turns wrapping off. uutils#16191 (merged): fmt could emit a line past WIDTH when no break fitted. GNU never does. Black-box recording does not need to invent these numbers. Help text and a few large or awkward values are enough. The failure is a wrong line of stdout, which a golden case catches on the first replay. 4. Error context is part of the contract I wrote a longer piece on this earlier. The short version from merges that landed since: - uutils#15692: cp now names the source when stat fails for a reason other than "missing". - uutils#15714: ln names the source it cannot access. - uutils#15868: chown/chgrp say cannot access unless the operand is a dangling symlink. - uutils#15825: mv -n on the same file skips the same-file error the way GNU does. Scripts and humans parse those messages. A rewrite that returns the right exit code with the wrong words still breaks tooling. 5. Checksums and parsers have "almost right" modes uutils#16167 (merged): checksum tools unescaped names only on lines that start with a backslash, matching GNU. A broader unescape looked fine in happy-path tests and failed on real check files. Golden cases from the reference tool encode the narrow rule without anyone writing a paragraph about it. What I would repeat on the next rewrite 1. Record from the release you claim compatibility with. Keep version-sensitive cases out of the shared CI job. 2. Let the probe walk help text. Enum values, flag pairs, and obsolete forms find precedence bugs that hand-written tests miss. 3. Assert stderr shape, not only exit codes. Context words are user-visible API. 4. File a fix with a test. Upstream reviewers move faster when the PR fails without the patch and passes with it. 5. Keep the README honest. Counts (reports, PRs, merges) change; update them when you publish. Try the same specs brew install emirmrkaljevic/tap/behave # or: go install github.com/emirmrkaljevic/behave/cmd/behave@latest behave run examples/seq behave diff examples/fmt --impl /path/to/uutils/fmt The specs under examples/ were recorded from GNU 9.12. The merged uutils PRs above are linked from the behave README findings table if you want the full list.

    1 reaction · 1 comment
  8. I built iotaudit, a free local CLI that shows what each smart device on your own network talks to: domains, countries, plaintext vs TLS, open ports, and an A to F grade. Consent first, data stays on your machine. pip install iotaudit sudo iotaudit auto emirmrkaljevic/iotaudit

  9. I built mesh2cad, an open source tool that turns STL meshes of simple mechanical parts back into editable CAD. New: a box with every edge rounded comes out as a CadQuery/OpenSCAD/FreeCAD script with one radius you can change, plus holes and bosses. emirmrkaljevic/mesh2cad

    2 likes · 1 repost
  10. Show HN: An MCP server that runs 27 small web and open-data scrapers

    1 point

Achievements

Awards earned by the repositories emirmrkaljevic owns. Select an award to embed its badge.

No awards yet

Repositories earn awards by reaching the top three in a completed trending day or week.

A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.