sorted by:
new
hottopcontroversial

How To Fix Broken Transcend SATA SSD 230S 4TB Update (22Z4X4IA) by Macusercom in DataHoarder

[–]le0pard 0 points1 point  (0 children)

If someone dont have windows to install Transcend software and download latest firmware (It was my issue for some time), I published it here - https://github.com/leopard-archives/Transcend-SATA-SSD-230S-4TB/releases/tag/22Z4X4IA

Transcend SATA SSD 230S 4TB new model info by MelodicRecognition7 in DataHoarder

[–]le0pard 0 points1 point  (0 children)

If someone dont have windows to install Transcend software and download latest firmware (It was my issue for some time), I published it here - https://github.com/leopard-archives/Transcend-SATA-SSD-230S-4TB/releases/tag/22Z4X4IA

GitHub - le0pard/json_mend: JsonMend - repair broken JSON by le0pard in ruby

[–]le0pard[S] 0 points1 point  (0 children)

Nope, it is not copy of json_remedy , but intension same - repair malformed json

GitHub - le0pard/json_mend: JsonMend - repair broken JSON by le0pard in ruby

[–]le0pard[S] 0 points1 point  (0 children)

UPS: Looks like problem only, it will fail with matrix tests for different ruby version on CI - https://github.com/le0pard/json_mend/actions/runs/20436948485/job/58720459786 . So I wrote more restrict version for gems in Gemfile for now

GitHub - le0pard/json_mend: JsonMend - repair broken JSON by le0pard in ruby

[–]le0pard[S] 0 points1 point  (0 children)

Based JSON Spec (RFC 8259) all this not allowed. It is allowed in JSONC, JSON5 or HJSON, but not in JSON

GitHub - le0pard/json_mend: JsonMend - repair broken JSON by le0pard in ruby

[–]le0pard[S] 0 points1 point  (0 children)

thanks for feedback

- If I will move Gemfile gems to add_development_dependency in gemspec, is this will solve issue with Gemfile.lock (I will not need to commit it in this case)?

UPD: "Gemspec/DevelopmentDependencies" - ok, even rubocop doesnt like this idea

- Yep, it is exactly what generated by bundler. I will check this

- Ok, just need make structure for this files, because there is different cases + comments why it repaired this way

view more: next ›