"creating commit failed" Error

[Dirk Hohndel]

So you are running Subsurface 2.4.1 on your Cray II running Dynix 5.2a while opening your cloud log that you have stored in clear text on punch cards.

Am I guessing correctly?

If not, would you let us know the basics of what would help us help you?

Like - what OS are you running?
Which version of Subsurface are you running?
How are you trying to open the dive log?

/D

> On Aug 29, 2022, at 5:35 PM, Moetaz Thabet <moetazthabet at gmail.com> wrote:
> 
> Ok. i am a bit lost honestly. i am not sure how to run the application from a terminal. 
> 
> the application was running fine. had no issues syncing with cloud for a couple of years now. until last month everything was working fine.
> 
> i just updated my last 9 dives today. This issue only appeared that one time. not sure what you want me to do.
> 
> 
> 
> On Tue, Aug 30, 2022 at 2:23 AM Linus Torvalds <torvalds at linux-foundation.org <mailto:torvalds at linux-foundation.org>> wrote:
> On Mon, Aug 29, 2022 at 5:04 PM Moetaz Thabet <moetazthabet at gmail.com <mailto:moetazthabet at gmail.com>> wrote:
> >
> > this is the only comment that appeared in a red bar at the bottom of the window. Is there a way i can send you the error log file ?
> 
> Argh. We use "report_error()" and I *thought* we ended up with
> multiple lines there, but maybe we only show the last line. Very
> annoying.
> 
> And kind of stupidly, we don't seem to log our errors anywhere, unlike
> our SSRF_INFO informational things.
> 
> But that can't be true, and I must be missing something. Dirk will know.
> 
> What happens if you start subsurface from a terminal window with "-vv"
> (for very verbose) as an argument? Do you get more data.
> 
> And Dirk, if we really don't log our 'report_error()' strings, maybe
> something like the attached would make sense? I didn't follow the
> whole chain of report_error() -> UI.
> 
>               Linus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20220829/89f4d902/attachment.htm>