silverdr

@cblavier - this doesn't seem to work. At least with Erlang/OTP 25…

> > @cblavier - this doesn't seem to work. At least with Erlang/OTP 25… > > the following has worked for me as a quick fix: > > ```ini >...

OK, so the current "quick fix" for OTP 25 is: ``` {:neotoma, "~> 1.7.3", manager: :rebar3, override: true}, ``` followed by `mix local.rebar`, which deals with the above mentioned error.

In current project I do it like I described here: https://silverdrs.wordpress.com/2022/02/17/rendering-svelte-components-in-phoenix-templates/ (the last code snippet on that page) so generally yes, I can control said code. Currently I have two...

Roger. Simply removing didn't help (I tried) but shall check the full commit and report, tnx.

OK - the compilation goes further now. I still don't get anything close to usable binary in the end, but that's for another issue. We can close this one.

Another situation: ``` rsync: send_files failed to open "/04B81CFC0A0102ABs": Permission denied (13) rsync: send_files failed to open "/19228148A9E5D347s": Permission denied (13) rsync error: some files/attrs were not transferred (see previous...

> What should be a suitable behaviour for the backup solution, while still letting the user know, that something has not been backed up? That's obviously a good question. "Thinking...

FWIW I recall using both colons and slashes w/o problems for quite some time. So might it be that the "upstream" change in `slime-lang/slime` was all that was needed?

This issue seems to be open for some time now so the question would be how does the LiveView support for Phoenix 1.6+ looks as of now?