Fossil Forum

fossil open reports: not found: main

fossil open reports: not found: main

fossil open reports: not found: main

(1.1) By John Rouillard (rouilj) on 2022-06-16 22:11:45 edited from 1.0 [source]

Hmm, something weird started happening on my server.

fossil open ~/.museum/fossil_skins.fossil 

not found: main

This is with a locally built fossil version 2.19 [29a24941ed] 2022-05-12 15:09:32 UTC. It also occurs with the current tip: b0f84d8d17.

I did a rebuild on the repo in question in case it was a schema change of some sort.

I can run all the other functions: update, commit .... in an already checked out repo without an issue.

bisect points to as 24420b4e63 the first failing copy.

12:41:07 [24420b4e63] *CURRENT* Fix the "fossil open" command so that it honors
         global settings. (user: drh tags: trunk)

Maybe I am missing a main setting in my global settings?

(2) By Stephan Beal (stephan) on 2022-06-17 01:30:13 in reply to 1.1 [link] [source]

not found: main

Curious. The only(?) "main" referenced by fossil is the "main" database, which is the name automatically given to a database opened by sqlite3_open() and friends.

Unfortunately i'm unable to reproduce this.

If you comment out that one line in fossil:24420b4e63, does the problem disappear?

(3) By John Rouillard (rouilj) on 2022-06-17 03:07:12 in reply to 2 [link] [source]

Thanks for the idea.

It looks like I had a global setting for main-branch that was set to main. The repo I was using for testing didn't have a main branch, only a trunk.

I think that was set to change the default branch from trunk to main on new repos, but I don't remember.

At the very least a message like:

  Unable to find a main-branch named 'main'
would be helpful in tracking this down. I killed off the global setting and set the main-branch locally on the one repo I have that has a main branch.

(4) By Stephan Beal (stephan) on 2022-06-17 11:07:30 in reply to 3 [link] [source]

Unable to find a main-branch named 'main'

We unfortunately can't make it quite that specific because it happens levels deeper than what you're trying to do and doesn't have enough context to be that specific, but the message was just changed to "cannot resolve name: main" so that it's at least less cryptic. That same error message still appears in two places, but they're unambiguously files/dirs in those cases so i've left those.