lineages | Resources for calling and describing the circulating | Continuous Deployment library

This one seems to do the trick:

Writing the intermediate data by saving the dataframe, or using a checkpoint is the only way to fix it. You're probably running into an issue where the optimizer is taking a really long time to generate the plan. The quickest/most efficient way to fix this is to use localCheckpoint. This materializes a checkpoint locally.

... is there a halfway convenient way to achieve [a sensible result]

No.

There's one command, git filter-branch, that can do it, but it's not halfway convenient, nor even 1/4th convenient. It's about 1000% inconvenient. :-)

The new git rebase --rebase-merges machinery is pretty obviously adaptable to doing this sort of thing in a more convenient way,¹ but it's not currently designed to rebase multiple branch names.

The new experimental git filter-repo is capable enough to do what you want, and probably less inconvenient than git filter-branch, but it's still swatting bugs with nuclear weapons—in this case, maybe a moderately large bug, not just a fly, but still serious overkill.

(I once wrote my own experimental thing to do this sort of rebase, but I never finished it. It did what I needed it to, when I needed it. It worked using the equivalent of repeated git rebase --onto operations and had a lot of corner cases.)

¹The key is to be able to label particular commits, so that after rebase copies them, you can pair up the hash-ID pairs, and otherwise jump around the graph structure from one chain to another as the rebase progresses. The old --preserve-merges code could not do that; the new --rebase-merges code can. Once you have these pieces in place, rebasing multiple branches "simultaneously" is just a matter of saving multiple branch names to force-adjust after the rebase completes. You then have the rebase list the correct commits and jump-points. The main bulk of the rebase operation consists of copying those commits. Last, using the old-to-new mapping, rebase can adjust each branch name, then reconnect HEAD to the one you want.

The remaining user-interface level problem lies in selecting the correct set of branch names to multi-rebase.

Your problem resides on the declaration of document on every function.

Your code is:

We need to use df.apply functionality of pandas

but I'm having trouble getting it pretty-printed

Because it is bytes object. Just decode the result: