reva VS MEGAsync

Before I deep dive into the architecture of what I rebuilt the app during the hackathon, I would like to tell about my experiences in my words. When I first came across #GO Hack Challenge on devpost, I was overwhelming to find related tracks which I could be fit for and tutorials to enrich my knowledge here and there to get into it. It was really a learning opportunity to someone who is newbie and contribute or build any stuff under the hood. I stepped into the open source projects under CERN Foundation, where I didn’t even know what the ecosystem around the project is. I was much curious then. Next, I delved into one of the projects for a few days and looked into a few issues and made a small contribution to it by fixing one of the bugs. I moved to another track where we needed to build any app based on golang. I came to know about use of generic function which is currently released and used in Go >= 18 Version. I managed to rebuild an app using Gin-Gonic framework and use the generic function usage in my app.

The advantage of that above just a simple "these tests are allowed to fail" is that, after adding a feature or fixing a bug, the developer is forced to look into the tests. If tests start to pass, the only job the developer has to do, is to remove them from the expected-to-fail list, and what a joy is that 🎉. From that point on the test has to pass in all future runs, and we are sure not to introduce any regressions. If we would only have an allowed-to-fail list, there would be no pressure to remove tests from that list, humans are humans, so they would forget or miss some. Potentially a bug could get fixed, then see some regression again and none of that would be noticed by the test-suite. So let the computers do what they are good at - automate!

But there is also a problem with libmedianfo in Fedora 38 where we cannot do anything either (the same issue is present in other projects https://github.com/meganz/MEGAsync/issues/795)

Looks like they've got build instructions here and you can find... Most of these dependencies already packaged...

I'm assuming you're looking at https://github.com/meganz/MEGAsync/issues/756

Good? It will crash on a Wayland session, and the issue has been open for nearly 2 years: https://github.com/meganz/MEGAsync/issues/501 Other than that, the MEGA cmd app doesn't support true incremental backup/deduplication, so you will quickly go through whatever storage you bought if you make multiple backups. Also, CPU usage is pretty high.

This function "encrypt" is only used to encrypt the local settings, It's only used here .

Mmm; good point. I went straight to tags, since Guix uses those, – originally – and there's definitely a v4.6.1.0_Linux tag available (https://github.com/meganz/MEGAsync/releases/tag/v4.6.1.0_Linux). But thanks for pointing that out, for me. I've packaged up a few smaller projects, already, for Guix and it'd be awesome if I was able to just sit down and get this one to work and be able to send it off as a patch.

I see here a better "fix" from moor-bryan - https://github.com/meganz/MEGAsync/issues/629

https://github.com/meganz/MEGAsync/issues/609 Seems to be the case :(

You can also automate it by following the tip mentioned here - https://github.com/meganz/MEGAsync/issues/443#issuecomment-633200813