windmill-labs/windmill · error
GIT is not supported
Error message
GIT is not supported
What it means
Raised by the Ruby gem installer when a gemfile block declares a `gem` with a `:git` option. Windmill's inline Ruby dependency management installs gems only from registered gem sources; git-sourced gems are rejected before installation since there is no git fetch/lock support in the worker's cache.
Source
Thrown at backend/windmill-worker/src/ruby_executor.rs:668
"gem.cmd"
} else {
GEM_PATH.as_str()
})
};
cmd.env_clear()
.current_dir(&job_dir)
.envs(vec![
("PATH".to_owned(), PATH_ENV.clone()),
// Make sure there is nothing written to actual home
// This way we keep everything clean, organized and maintable
("HOME".to_owned(), RUBY_CACHE_DIR.to_owned()),
])
.envs(RUBY_PROXY_ENVS.clone());
// Figure out source
let source = {
let source = match dependency.custom_payload.source {
FinalSource::GIT { .. } => return Err(anyhow!("GIT is not supported").into()),
FinalSource::GEM { remote } => remote,
}
.trim()
.to_owned();
let src_url = Url::parse(&source)?;
repos
.iter()
.find(|inst_url| {
inst_url.domain().is_some()
&& (inst_url.domain(), inst_url.path())
== (src_url.domain(), src_url.path())
})
.map(Url::to_string)
.unwrap_or(source)
};
cmd.args(&[View on GitHub (pinned to e474e8803c)
Solutions
- Replace the git-sourced gem with a published version from a gem source
- Ask an administrator to vendor or publish the gem on a supported source
- Fork the gem to a registry if it has no published release
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at backend/windmill-worker/src/ruby_executor.rs:668 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of windmill-labs/windmill@e474e8803c (2026-09-03).
Data as JSON: /api/errors/b011ae753a3a1be3.
Report an issue: GitHub.