best effort continuation

[rxgrant]

"Missing required value for field conversation.tools.web_fetch.source."

I pulled some JP changes, and planned to apply to my project with JP's help. It broke. Sure, it says where it's broken, but I don't need web_fetch at all to proceed. JP should have a --best-effort way to proceed, so that I can ask it to debug this.

[JeanMertz]

I agree we need some way to make this nicer.

For my understanding; you pulled the changes on main in this Git repository into a separate project? Am I correct in assuming you pulled the changes locally first and then copy/pasted .jp into your own project? If not, what was the workflow you used?

For reference, here are a few related (draft) RFDs:

• https://jp.computer/rfd/drafts/D32-jp-tracing-infrastructure
• https://jp.computer/rfd/drafts/D15-structured-logging-infrastructure
• https://jp.computer/rfd/drafts/D28-interactive-conversation-repair
• https://jp.computer/rfd/drafts/D27-granular-recovery-for-stored-conversation-configs

(I note that none of these capture the situation in this issue, so this is definitely a gap in the current implementation and in any proposed RFDs)

[rxgrant]

I periodically review which changes to .jp I want to integrate into my projects. I take a working local-project .jp and rsync dcdpr/jp/.jp over it, and restore/edit/add hunks until I'm happy.

This time I was going to ask JP to do the work.

[JeanMertz]

I see. Let me think on this.

I guess one non-ideal, but workable, way to do this right now is to actually mount your own project(s) into the jp workspace (see #727), so that you can run jp q ... inside JP's workspace, asking it to suggest/modify your my-custom-project/.jp files where applicable?

[rxgrant]

I had a project doing something similar with rsync. I'll review the new syntax.