You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ok, did a bit of digging in the code and I worked out the problem.
create table project__schedule
(
id integer primary key autoincrement,
template_id int not null,
project_id int not null,
cron_format varchar(255) not null,
repository_id int null,
last_commit_hash varchar(40) null,
foreign key (`template_id`) references project__template(`id`) on delete cascade,
foreign key (`project_id`) references project(`id`) on delete cascade,
foreign key (`repository_id`) references project__repository(`id`)
)
The problem is with the last_commit_hash field which is defined as 40 characters.
40 chars is the length of a SHA1 commit hash...
The git repo I'm using is set to use SHA256, which translates in a hash of 64 hex characters.
pommetjehorlepiep
changed the title
Problem: pq: value too long for type character varying(40)" error="Failed to update task commit
Problem: Semaphore won´t work with git repos using SHA256 commit hashes (Postgres db as backend)
Mar 7, 2025
Issue
Trying to run a simple bash task to create a file in the /tmp folder on the target host,
The task shows/keeps running in the UI, but Semaphore is actually terminated with a stacktrace.
Impact
Web-Frontend (what users interact with)
Installation method
Binary
Database
Postgres
Browser
No response
Semaphore Version
2.12.14-685c726-1739570559
Ansible Version
Logs & errors
No response
Manual installation - system information
OS: Alpine 3.21
Configuration
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: