Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
cloogle.org
cloogle.org
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Cloogle
  • cloogle.orgcloogle.org
  • Issues
  • #148

Closed
Open
Created Nov 01, 2017 by Camil Staps@cstaps🐟Owner

List of common errors / faults

I have long wanted to put together a list of common errors and faults on the Clean wiki or so, but perhaps Cloogle is the better place for it, as I see searches for some errors in the log.

What I have in mind is a new repository clean-cloogle/common-problems or so, with a single markdown file with a list of common problems. That file can be indexed in the frontend container when it is built, and when the search query matches any item from the list, the query is not sent to Cloogle but that result is returned instead. This is not an issue, because these errors typically have spaces in them (type error, cannot unify types, bus error, etc.) and Cloogle doesn't accept them as queries anyway. Alternatively, we can still run the query on Cloogle and do the search for errors on any request, interleaving the results, with the benefit that you can also search for one-word errors (so e.g. type would also give error results).

The result entry should link to the repository so that it encourages collaborative editing.

Thoughts?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None