Support
Help with Hop comes from the community, in the open. Everything below is volunteer effort — which is also why a well-formed question tends to get answered fast.
Where to go
Ask a question
Post to the users mailing list. The whole community reads it, and the answer stays in a public archive for the next person with the same problem.
Report a bug
Open an issue on GitHub. The checklist below is what turns a report into something a developer can act on.
Ask in public, and prefer the mailing list. It is not about protecting anyone's time: the list is archived and indexed, so an answer there is still helping people in a year. A reply in a chat channel, or in a direct message to a committer, helps exactly one person and is gone by the following week.
What to include
The more of this you can answer up front, the fewer round trips it takes to get you unstuck.
- Which versions?
- Hop itself, plus anything it is talking to — the database, the driver, the runtime. This is the single most useful thing you can include.
- Which platform and JDK?
- Operating system and Java version. If you are running in a container, which image and which tag.
- The whole stack trace
- Not the first few lines. Exceptions get wrapped, and the cause at the bottom is usually the one that matters. We are good at skimming past the rest.
- Logs, at debug level
- Raising the log level often turns a puzzling failure into an obvious one.
- The pipeline or workflow
- A small file that reproduces the problem is worth several paragraphs describing it — and it is the fastest route to a fix.
- Did it work before?
- A version, a configuration change or an upgrade that lines up with the breakage narrows things down enormously.
- Has it been reported?
- A quick search of the issue tracker and the mailing list archive sometimes finds the answer outright.
Getting an answer sooner
Reproduce it in something small
A cut-down pipeline, workflow or unit test that shows the problem removes all the guesswork. If you think it is a bug, a failing test case makes it undeniable.
Send a fix
If you are already in the code, a pull request is very welcome — and it is the quickest possible path from problem to resolution.
Commercial support
The community answers questions for free, but it cannot promise a response time. If you need an SLA, training, mentoring or a migration done for you, several companies offer that around Hop. The Hop PMC does not endorse, rank or vet them — the list is there for information.
Elsewhere on the web
Plenty of people write about Hop outside the project. Those sites are not maintained by the Hop community and can go out of date, but they are often useful: search the web, or browse write-ups and technical blogs.