Activities of "FrancoisLabelle"

Hello,

• ABP Framework version: v7.0
• UI type: Blazor Server
• DB provider: EF Core
• **Tiered: Yes
• Exception message and stack trace:
• Steps to reproduce the issue:"
• 1 - Create a new project using the app-pro template. DbMigrator. Run. Everything is fine.
• 2 - Use ABP Suite, add the CmsKit Pro Module. The solution will not compile due to these errors about CmsKitProAdminBlazorServerModule and the namespace Volo.CmsKit.Pro.Admin.Blazor.Server.

By the way, during the process of adding the module... there is a prompt in background (command line window) asking to scroll and choose the version of the CmsKit pro... Why I should pick the version ?!?! Is this a default behavior of NuGet ?!?!

Thanks

I did another test using --with-public-website when creating my initial project, and then CmsKit Pro was already installed with all the needed package referenced.

But, let's say I don't want or need the public web site project in my solution...but still want to use some features of the CmsKit... Let's say I just want to use the UrlShorting feature in my Blazor project... Why adding the CmsKit Pro module is not worlking if my inital project don't have the public web part ? Should it work anyway ? I think so...

Any advice are welcome, thanks.

Hello,

I added this "question" just in case someone got this issue in the future... I already found found a work around...

But, maybe ABP Team can also do something to prevent this... ?

We have a non-tiered blazor server solution deployed in Azure, using version ABP 5.2.2. Everything is working well since months...

Nothing has changed recently (no new deployment) or any parameter changes on Azure.... (Well, something has changed... not in Azure...keep reading !)

But, we recently started to have a problem. We were not able anymore to access the /identity/users page anymore (where you can manage users). And other pages were all still working correctly...

This error was being logged in the default log file, but without any more details (before or after).

Unhandled exception rendering component: '0x1F' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.

System.Text.Json.JsonReaderException: '0x1F' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.
   at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes)
   at System.Text.Json.Utf8JsonReader.ConsumeValue(Byte marker)
   at System.Text.Json.Utf8JsonReader.ReadFirstToken(Byte first)
   at System.Text.Json.Utf8JsonReader.ReadSingleSegment()
   at System.Text.Json.Utf8JsonReader.Read()
   at System.Text.Json.JsonDocument.Parse(ReadOnlySpan`1 utf8JsonSpan, JsonReaderOptions readerOptions, MetadataDb& database, StackRowStack& stack)
   at System.Text.Json.JsonDocument.Parse(ReadOnlyMemory`1 utf8Json, JsonReaderOptions readerOptions, Byte[] extraRentedArrayPoolBytes, PooledByteBufferWriter extraPooledByteBufferWriter)
   at System.Text.Json.JsonDocument.Parse(ReadOnlyMemory`1 json, JsonDocumentOptions options)
   at System.Text.Json.JsonDocument.Parse(String json, JsonDocumentOptions options)
   at Volo.Abp.BlazoriseUI.Components.ObjectExtending.LookupExtensionProperty`2.GetLookupItemsAsync(String filter)
   at Volo.Abp.BlazoriseUI.Components.ObjectExtending.LookupExtensionProperty`2.SearchFilterChangedAsync(String filter)
   at Volo.Abp.BlazoriseUI.Components.ObjectExtending.LookupExtensionProperty`2.OnInitializedAsync()
   at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

After reading this post...

https://www.byteblocks.com/Post/0x1F-is-an-invalid-start-of-a-value (as of today, their TLS certificate is expired, continue on this site only if you want... I'm not telling you to do it).

... that is basically explaining that the issue might be related to compression / "gzip"... And, the post also mentioned that the person is using Cloudfare and that Coudfare might do compression while proxying the data in transit.

Bingo ! Lucky that I'm aware of this, but we recently moved some DNS management to Cloudfare... and all our DNS entries were set to their default mode "Proxied", meaning that the user does not directly hit Microsoft Azure server but reach Cloudfare server instead... Cloudfare doing the proxying.

Then. turning off the "proxied mode" to "DNS Only" fixed the issue instantly... The /identity/users pages restarted to work.

ABP Team, you appear to also use Cloudfare... so you could maybe try to reproduce this issue... or have already experienced it ?

Maybe you are already aware of this potential issue and maybe have already fixed it ?

By the way, we also have tiered solutions (api, ids, blazor server) deployed on Azure (but using 5.3.5) that were also "proxied" by Cloudfare and we did not had this issue... We did not took any chances and we turned off the proxy feature for now... but if ABP can confirm something about it, we might want to turn it back on in the future.

Regards

Hi,

Do you mean that or that

Regards

Well... the first post https://github.com/abpframework/abp/issues/10016#issuecomment-917707186 mentioned, at the end, that there is no such "abp downgrade" command and that you don't find that this feature would be useful...

So I guess that I have my answer... and that downgrading will remain very painfull... especialy in a large solution with custom modules.

Otherwise, what about this recuring error:

[10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.lepton/index.json with an error: 404-Not Found. Waiting 7 secs for the next try...

... repeating for all modules and several times during an update process ?

• ABP Framework version: v6.0.1 (version of ABP CLI)
• Steps to reproduce the issue:" > abp update -version 5.3.3

Is it possible to downgrade the Nuget packages of a solution ?

The documentation does not mention this... possible or impossible. Neither found a "support question" about this ?!?!?

I tried a downgrade, but I just received errors message without any detail: Unable to update package. (I woul like to know why).

E.g.

[10:38:41 WRN] Unable to update package "Volo.Abp.PermissionManagement.Application" version v5.3.4 to v5.3.3. [10:38:41 WRN] Unable to update package "Volo.Abp.PermissionManagement.Application.Contracts" version v5.3.4 to v5.3.3. [10:38:41 WRN] Unable to update package "Volo.Abp.FeatureManagement.Application" version v5.3.4 to v5.3.3. [10:38:41 WRN] Unable to update package "Volo.Abp.Caching.StackExchangeRedis" version v5.3.4 to v5.3.3. [10:38:41 WRN] Unable to update package "Volo.Abp.FeatureManagement.Application.Contracts" version v5.3.4 to v5.3.3.

Of course, I guess that when trying to do this, NuGet warns us about a package downgrade for other packages (not yet downgraded) ( NU1605 ) but this is something that I was expecting to be managed by the ABP CLI... There is certainly a way to ignore, at least temporary, these warning during the downgrade process ? I understand that we should not do this... (downgrade)... but let's say we are trying to debug something and we want to to try this downgrade... doing this manually is absolutely painful. !!!

At the same time. during an update procedure (even to upgrade to a higher version), there is a lot of these errorsthat I feel just slows down the overral process. Is this expected ? ...

[10:38:42 WRN] Unable to update package "Volo.Abp.BlobStoring.Database.Domain" version v5.3.4 to v5.3.3. [10:38:42 WRN] 1. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.entityframeworkcore/index.json with an error: 404-Not Found. Waiting 2 secs for the next try... [10:38:42 WRN] 1. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain/index.json with an error: 404-Not Found. Waiting 2 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.application/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.application.contracts/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.auditlogging.httpapi/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.httpapi.client/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.account.pro.public.application/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.lepton/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain.shared/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.entityframeworkcore/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:44 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.application/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.application.contracts/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.host.httpapi.client/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.account.pro.public.application/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.auditlogging.httpapi/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain.shared/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.lepton/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.entityframeworkcore/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:48 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.domain/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [10:38:56 WRN] Unable to update package "Volo.Saas.Host.Application" version v5.3.4 to v5.3.3. [10:38:56 WRN] 1. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.auditlogging.application/index.json with an error: 404-Not Found. Waiting 2 secs for the next try... [10:38:56 WRN] Unable to update package "Volo.Abp.Identity.Pro.Domain.Shared" version v5.3.4 to v5.3.3. ...

Thanks

Hello,

Version 6.0.0 (final release) is OK... well... after a second try. I have updated CLI to 6.0.0 and Suite to 6.0.0, started it... and I got errors while trying to update packages.

2022-10-06 11:08:11.223 -04:00 [ERR] Value cannot be null. (Parameter 'source') System.ArgumentNullException: Value cannot be null. (Parameter 'source') at System.Linq.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument) at System.Linq.Enumerable.TryGetFirst[TSource](IEnumerable1 source, Func2 predicate, Boolean& found) at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable1 source, Func2 predicate) at Volo.Abp.Cli.ProjectModification.VoloNugetPackagesVersionUpdater.GetLatestVersionFromMyGet(String packageId) in D:\ci\Jenkins\workspace\abp-commercial-release

I closed everything... deleted the suite.dll in my %temp% folder (because I had issues with this previously)... started ABP Suite and proceed to update... Then, everything went well, fast, and without any update of unwanted folders...

Thanks.

The version 6.6.0-rtc.5 is not really better. Well, not yet fully tested I guess...

Packages update is working from the main page. But, when you click on solution and goes the the "crud page"...

1. The Update menu is not the same. We miss the "switch to xxx " menu items.
2. If you launch the "update all packages", you will get the famous "An internal error has occurred"

The underlying error is path related. Let's say you have started abp-suite in a command prompt while being in a folder named C:\MyFolder, then, the error message will tell this: ERR] Could not find a part of the path 'c:\MyFolder\MySolutionName'. System.IO.DirectoryNotFoundException: Could not find a part of the path 'c:\MyFolder\MySolutionName'.

Again, it makes no sense !?!? Why appending the "startup folder" of abp-suite to the selected solution name... when you already have the full path of the solution selected (in my case, C:\Sources\MySolutionName). ?!?!?

Also, with 5.3.4 and 6 rc5, I recurrently have this error

ERR] The file 'C:\Users\flabelle\AppData\Local\Temp\Suite.dll' already exists. System.IO.IOException: The file 'C:\Users\flabelle\AppData\Local\Temp\Suite.dll' already exists. at System.IO.FileSystem.CopyFile(String sourceFullPath, String destFullPath, Boolean overwrite) at System.IO.File.Copy(String sourceFileName, String destFileName, Boolean overwrite) at System.IO.File.Copy(String sourceFileName, String destFileName) at Volo.Abp.Suite.Areas.AbpSuite.CrudPageGenerator.Services.SuiteAssemblyService.B6vUUTF0OS(String )

... Then I close Abp-suite, delete the suite.dll in the temp folder, and restart from scratch. Annoying !

• ABP Framework version: v5.3.4, ABP Suite
• Steps to reproduce the issue:"

1. Start abp-suite
2. Add an existing solution, eg. C:\Sources\ABigProject\ThBigSolution.sln
3. Return to the main screen
4. Click on the arrow beside the version number of the solution (for the solution just added)
5. Click on Update NPM packages...

For an unknown reason, there is a recursive search for files/folders that goes OUT of the expected selected solution folder...

I understand that searching subfolders below is just normal... (E.g. C:\Sources\MyMainProject* )

But, how could you go one folder UP and do a recursive search OUTSIDE of the selected one ?!?!?! ( E.g. C:\Sources* !!!!) It makes no sense at all !!! How can this be a good idea ? You will ending up updating other projects that no one asked you to update (or never figured it will) !!! Let's image how many updates will be done if someone, like me, has unziped all the samples projects, downloaded all modules source code, has made a lot of "test projects" as proof of concepts, has made backup of the main project, etc !!!

I have this issue since a long time... That is not a new bug. can't understand how no one has complained about it yet. That should have been noticed and fixed a long time ago !

That's a major issue. Please, make sure this is fixed soon and that will never occur again.

After waiting almost an hour... a message is displaying "The xxx solutions is updated !" Well, that is not true... because ALL solutions are updated.

Thanks

Hello,

Do you have any plan to improve the search feature on the community web site ? https://community.abp.io

There are plenty of good and useful posts, but without a search engine worthy of the name, the site loses much of its value.

If I key in 3 words in the search, especially if I used the word "to", I don't want to see all posts having one of my 3 words in the title...that's counter intuitive. I want the one having the 3 words firsts... then the ones with a combination of two of them... and so one...

I've tried using double quotes syntax ( "my three words" ) or the plus sign syntax ( my + three + words ) or with named logical operators ( my AND three AND words) and it's all the same sh** results... Well, in facts, it's even worst using AND

The search engine is really better and powerful on the support web site, then why not use the same search engine for both ?!?!

Yes, I know, I can use google search with the site:community.abp.io option, but I think that the search available on the page should just be improved.

Thanks

• ABP Framework version: v5.3.2, Suite
• UI type: Blazor
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes
• Exception message and stack trace: (see screenshot)
• Steps to reproduce the issue:"

1. Using ABP Suite, create a new solution: Blazor, EFCore, Tiered: Yes
2. In the module section, create a new module (MyNewModule) and wait... and wait... and wait...
   1. What can take so long ?!?!? Oh, yeah... the "super fast" yarn !!! 7 minutes run-time after the 20 seconds time taken to create the module ! But ?!?! Wait ! Where are the sub folders .\angular and .\hosts ?!?!? They got deleted ?!?!? This means that I had to wait 7 minutes for yarn to complete his tasks on projects/folder that got deleted at the end of the module creation process ?!?!? Come on ! Was this really needed ?!?!?
3. in VS, load/reload solution, compile, run and make sur everything works until now. (Should be good at this point !)
4. Add a new entity to the newly created module...
   1. Return to main screen and click "add an existing solution"
   2. Enter the path of the newly created module (a browse window would be nice here !)
   3. Add a new entity, with only one property and click save and generate (and be surprised of how fast it could be to generate almost 30 files in less than 2 seconds !!!)
   4. Try to compile and see all the errors...

After having struggled couples of minutes to find a work around, I had the idea to try something, add the "global::" prefix before the "namespace!" inside the the razor page and then I was able to compile the project without any error.

But, I'm not sure if it's a good thing and that we should do have to do this... Anyhow, ABP Suite needs a fix for this I think, right ?

Thanks

Hello Albert,

I agree that string primary key is not the best approach, and I will not persist that way since the ABP framework does not fully support this.

But in our situation, it was useful to have a human readable key because the staff refers to this code amongst others system.

The plan was to first import the legacy records and then allow them to create new ones too. I was expecting to be able to avoid coding something "special" for it and be able to use the auto-generated pages from ABP Suite but we can't.

Sadly, the more I use ABP Suite, and the more I find this tools useless and very buggy. We had great hope in this tools to help us improve our development speed, but it clearly lacks some useful advance features and the overall quality of the tool is not equal to the quality of the ABP framework itself. Hopefully the framework is more stable. But, yes, it still a good startup point for basic stuff.

Regards