Need to quickly fix subtitles?

My free online SRT Subtitle Editor helps you easily upload .srt files, edit text, merge blocks, and undo changes — all inside your browser. No installations, no accounts, no tracking.

Features:

  • Upload and view your SRT subtitles instantly
  • Edit subtitle text block by block
  • Merge or delete subtitle entries
  • Undo/redo any changes (with history stack)
  • Export your edited .srt with a single click

No data is uploaded to any server. Everything stays local in your browser.

Link: https://d8devs.com/srt-editor.html or Menü > Tools > SRT Tool – SRT Combine & Edit

Views: 1

After several trials and experiments, I’ve finally completed my first successful fine-tuning of a LLaMA-based model using my own real-world internal IT documentation. This project fine-tunes a 3B parameter model to understand and respond to Symfony command usage, Chameleon CMS workflows, and developer issues like rsync errors or Xdebug debugging failures.

The result is now publicly available on Hugging Face: kzorluoglu/chameleon-helper

Setup Overview

I used the excellent Unsloth Synthetic Data Kit and trained the model on a curated dataset of 32 instruction-based Q&A pairs, written in natural German developer language.

Instead of the usual instruction/input/output JSON format, I opted for a more human-friendly wiki-style documentation format to keep the prompt more intuitive and domain-specific.

Training Pipeline

The model used was unsloth/Llama-3.2-3B-Instruct, fine-tuned via LoRA on Google Colab using:

  • 60 training steps
  • 4-bit quantization
  • 2048 token context window
  • TRL’s SFTTrainer (Supervised Fine-Tuning Trainer)

Only ~1–10% of parameters were updated thanks to LoRA, making the process lightweight and efficient.

Inference Results

I ran a couple of test prompts using the trained model:

Example 1

Prompt:
Welche Symfony-Command wurden ausprobiert, um Daten im 'outbox'-Ordner zu erzeugen?
Model Response:
app/console assets:install web ist die korrekte Command<|eot_id|>

Perfect result! Matches my internal documentation exactly.

Prompt:
Wie erfahre ich, welche Datenbank-Migrationen im Chameleon CMS noch ausstehen?
Model Response:
Die Daten können durch Ausführung des Befehrs `app/console ch:a:u:l` ermittelt werden.<|eot_id|>

Slight typo (“app/console ch:a:u:l” instead of “app/console ch:u:l”), but the core answer was semantically correct.

Lessons Learned

  • This successful fine-tuning came after several iterations refining the dataset and formatting.
  • With just 32 well-written examples, the model already shows strong understanding of custom internal logic.
  • A few spelling issues remain, but I expect these to decrease significantly with a larger, higher-quality dataset (e.g., 200–500 examples).

Model on Hugging Face

You can try the fine-tuned model directly here:
kzorluoglu/chameleon-helper on Hugging Face

Views: 23

Gestern war ich beim Symfony PHP Meetup in Basel..

1️⃣ hurl – ein leichtes Testing-Tool in Rust, für einfache API-Tests.

2️⃣ Ein Plugin zur Absicherung von JSON-Requests – mi einem Symfony-Plugin zur Absicherung eingehender JSON-Requests. Besonders interessant war:

Die Flow-Erklärung,

Der Einsatz von Compiler Passes,

Und warum das Event nicht auf der Request-Ebene, sondern auf der Controller-Ebene ausgelöst wird – eine bewusste Designentscheidung für bessere Kontrolle und Trennung.

3️⃣ Symfony Clock Component – mit einem kleinen Live-Demo. Sie eignet sich ideal für testbare zeitbasierte Logik und wurde als internes Werkzeug für künftige Entwicklungen empfohlen.

Danke an alle Speaker & PHP Symfony User Group Basel !

#symfony #basel #php #lörrach #freiburg

Views: 7

If you encounter the error:

“Failed to eject USB-DRIVE. Another program may be using the drive.”

this means that the Cura application requires Snap permissions to access removable media.

Fix:

Run the following command to grant the necessary permission:

snap connect cura-slicer:removable-media

After running this command, you should be able to eject the USB drive without issues.

Views: 7

When working with SQLite databases stored in WSL2 and accessing them via PhpStorm, you might encounter the following error:

Error encountered when performing Introspect schema main: [SQLITE_BUSY] The database file is locked (database is locked)

This issue arises due to SQLite’s file locking mechanisms, which are not fully compatible with WSL2’s file system when accessed through tools like PhpStorm.

Problem

When you drag and drop an SQLite file from the WSL2 folder into PhpStorm’s Database tab, PhpStorm generates a default connection URL like this:

jdbc:sqlite:\\wsl.localhost\Ubuntu\projects\database\database.sqlite

This URL does not include parameters to prevent locking issues. As a result, SQLite encounters file locks, even if no other process is actively using the database.

Solution: Modify the JDBC URL with nolock=1

To fix this issue, you need to modify the JDBC connection URL by appending the ?nolock=1 parameter. This parameter disables file locking in SQLite, making it compatible with WSL2.

Steps:

Save the configuration.

Open PhpStorm’s Database tab.

Right-click on the SQLite connection and select Properties or Edit Data Source.

Modify the JDBC URL:

jdbc:sqlite:file:\\wsl$\Ubuntu\projects\database\database.sqlite?nolock=1

Click Test Connection to ensure it works.

Views: 68