Activities of "cfd000"

The license already requires paying, but they don't break the build with the license file requirement until you target 4.0.0 - if you're using version 3 without paying you're already violating their license - this is their article from 4 years ago: https://sixlabors.com/posts/license-changes/

If ABP already makes multiple image options available, why not default to SkiaSharp, which has the most permissive license? We pay for source code so we can build ourselves (in case of zero day vulnerabilities that we have to push before a sanctioned fix is available), but any change that requires us to manually manipulate the ABP source directly prior to building is onerous. We would prefer to only build the packages we need without edits.

• Steps to reproduce the issue: Compile ABP open source framework while targeting SixLabors.ImageSharp version 4.0.0 or higher, and an error will tell you that a license file is required.

https://sixlabors.com/posts/licence-enforcement-changes/

Is there a plan to migrate away from SixLabors? Cost - I don't begrudge them needing to earn money from their work product, but our work product is not yet revenue generating and we have hundreds of dependencies, paying them all is not possible.

Licensing - Their license is complicated and makes it challenging for us to prove we are in compliance, especially since we try to build as much of the project as we can internally rather than rely on packages for everything

Hi everyone,

We sincerely apologize for the issue caused by the recent release with a 3rd party component. The affected versions are 9.0.7 and 9.1.0, other versions don't have any issue. We understand how frustrating it is, especially when it affects live systems. The ABP project, like other software solutions, includes many 3rd party components, and sometimes there may be problems with them. We contacted our 3rd party vendor and completely fixed the case.

The issue is now resolved, and here's the quick fix:

1. Run this command on your development computer to clear your local NuGet cache: dotnet nuget locals all --clear

2. Uninstall and install ABP Suite again: abp suite remove abp suite install

3. Rebuild your ABP solution and publish it again to your live environment

Thank you for your patience, and we truly appreciate the feedback. We're taking extra measures to prevent this in future releases.

– ABP Team

I'm sorry, that is not an explanation of what went wrong, and gives us no reassurance that it won't happen again.

We have customers that cannot tolerate an outage like this, and saying "someone else will fix it in the next day" is NOT an acceptable answer. Being may time zones away that means we are effectively shutting down their business for at least a day.

We put a LOT of effort into creating an offline build so that we are not affected by a temporary outage of any NuGet servers, but this problem stopped logins in code that was already functional and deployed. That means that 1 of 2 things happened, both of which are unacceptable:

1. A component in our compiled code is reaching out to a server live to determine if it is allowed to run
2. A license code embedded in our dependencies has an expiration date that we do not know about

We need to answer our organizations with a specific cause for this outage, or we will be forced to abandon ABP entirely (which we do not want to do).

How did it suddenly stop working? We had a functional 9.1.0 build that was working without errors.

We also need additional information. We have created an air-gapped build system specifically to avoid problems like these, and we are doing an offline build (we have local copies of all NuGet dependencies). How did this problem get through? What can we do to make sure that this doesn't happen in the future?

What do I do in the meantime? What is the workaround?

I'm still awaiting a response.

https://abp.io/support/questions/8530/Uncaught-TypeError-leptonxmobileNavbarcloseMenu-is-not-a-function

This issue is still happening, although it says that it was fixed 2 months ago. There is no information in the ticket explaining a workaround, or what version to expect the fix in. I have tried creating new projects using 9.0.5 and also updating to 9.1.0-rc.2 and both still give me the same error.

What is the status of this ticket, and how do I get a fix or workaround right now?

We have always used fewer questions than we are allotted. Our subscription renewed about 2 months ago. Why does the counter say we have used 79 questions? I am only counting 5 (2 from me, and 3 from spospisil).

Also, why are 2 separate copies of our license required? Why would we be required to keep multiple pieces of the same information, and track it in different places? This is exactly the type of maintenance burden that ABP is supposed to alleviate