Starts in:
2 DAYS
2 HRS
40 MIN
14 SEC
Starts in:
2 D
2 H
40 M
14 S

Activities of "scott7106"

We have been experiencing intermittent but frequent issues today (2023-01-09) in our automated github builds and on our development machines when trying to download the commercial packages from ABP's nuget server.

And we fixed proxy generation. The fix will be available in 6.0.2

@muhammedalhug You indicated in the thread above that a fix for proxy generation would be in 6.0.2. Is there a timeframe on that release?

This had occurred in a solution we upgraded from rc.3 to the final release build. When we created a new project, the issue is not there. We have tracked down and resolved the issue in our existing project. Thanks!

If you're creating a bug/problem report, please include followings:

  • ABP Framework version: v6.0.0
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): no

The save button on a new tenant is disabled until all inputs pass validation. This creates a scenario where the user enters data into all the fields but the save button is still disabled because the password does not meet length and complexity requirements. There is no feedback to the user about what is wrong with the form data.

The UI experience should direct the user when the password does not meet the required length and complexity requirements. In my opinion, this should be trigged after the client types something in the password field.

  • ABP Framework version: v5.3.3
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): no
  • Exception message and stack trace:
  • Steps to reproduce the issue:"

We were getting an error when trying to update the users profile information. The error was due to a missing RequestVerificationToken header when trying to send the update to the API. We tracked the issue down to an entry for AbpAccountPublic in our environment.config file for Angular under the apis section.

  apis: {
    default: {
      url: '',
      rootNamespace: 'OtisEd.Synergyz',
    },
    AbpAccountPublic: {
      url: oAuthConfig.issuer,
      rootNamespace: 'AbpAccountPublic',
    },
  },

Why would this setting cause the RequestVerificationToken to be missing? There is something here we do not understand. The application works by simply removing that section from the config, but we would like to understand how that setting caused the issue.

Thanks!

I would be Ok with an option to enable/disable AuditLogActionInfo entirely. I have yet to find a use-case where we use the data in this table. So far, the AuditLogInfo and Entity*ChangeInfo tables have provided all the data we need.

This is not the answer to the question I asked. The logging I am asking about is in the AbpAuditLogActions table, it is not the entity logs.

According to your documentation https://docs.abp.io/en/abp/latest/Audit-Logging, the audit logging should be turned off for Get requests by default. I enable it using the property IsEnabledForGetRequests if I want to turn it on. I have not set that property, yet I am seeing audit log records for Get requests in the AbpAuditLogActions table.

  • ABP Framework version: v5.3.3
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): no

The documentation states that audit logging for get requests is turned off by default and can be turned on by setting the IsEnabledForGetRequests property of the AbpAuditingOptions object. However, if I look in my AbpAuditLogActions table, I have over 100K entries for various Get requests even though I have not set the IsEnabledForGetRequests property (see pic below). We have added an IgnoredUrl to AbpAspNetCoreAuditingOptions to get rid of some of the auditing records for hangfire which were cluttering up the tables.

What do I need to get rid of these audit logs for Get requests? I do not want these recorded.

Configure<AbpAspNetCoreAuditingOptions>(options =>
{
    options.IgnoredUrls.Add("/hangfire/stats");
});

I would agree except that I undid all my changes and ran this multiple times and it was the same on all attempts. That does not make sense that a network related issue would occur in the same place on each attempt.

After upgrading the CLI to rc.3, I get this error during the update command for the project.

[08:29:25 WRN] 1. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.leptonx/index.json with an error: 404-Not Found. Waiting 2 secs for the next try... [08:29:27 WRN] 2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.leptonx/index.json with an error: 404-Not Found. Waiting 4 secs for the next try... [08:29:31 WRN] 3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.mvc.ui.theme.leptonx/index.json with an error: 404-Not Found. Waiting 7 secs for the next try... [08:29:39 INF] Updating package "Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" from v1.0.0-rc.3 to v1.0.0-rc.4.

It looks like the fourth attempt was different in some way and worked. But the first 3 attempts for this package failed.

Showing 41 to 50 of 117 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06