Activities of "burkay"

Hello Maliming,

Thank you for the follow up. NavigationHelper method works. So, we can wait for the fix in the framework. I intend to close this issue by then:)

You asked for the logs of our test using v9.1.1. Unfortunately, I reverted to v9.1.0 when I could not make it work and do not have the logs available now. I need to start from scratch to generate them again.

Hello again,

First of all thank you for the reply and also for the refund. We really appreciate your prompt responses.

I got the following notification in an e-mail: "Question #9039 has been marked as a bug/problem by the team, ..."

In that case, I think this solution should be built-in the ABP framework as it is considered a bug. I do not think future users should add that configuration once they started a new project using ABP.

Applying your previous suggestion (NavigationHelper), we already have a solution. In that case, what is the use of removing that and adding some other configuration? I just want to know if this will get resolved in a release, and the version number if it will.

Thank you again. Burkay

Hello,

As you wrote in your linked post, we added the following code to our EntityFrameworkCore project:

    using Microsoft.EntityFrameworkCore.ChangeTracking;
    using Volo.Abp.DependencyInjection;
    using Volo.Abp.EntityFrameworkCore.ChangeTrackers;
    using Volo.Abp.OpenIddict.Tokens;
    
    namespace Ptr.EntityFrameworkCore;
    
    [Dependency(ReplaceServices = true)]
    [ExposeServices(typeof(AbpEfCoreNavigationHelper))]
    public class PtrAbpEfCoreNavigationHelper : AbpEfCoreNavigationHelper
    {
        public override void ChangeTracker_Tracked(object? sender, EntityTrackedEventArgs e)
        {
            if (e.Entry.Entity.GetType() == typeof(OpenIddictToken))
            {
                return;
            }
    
            base.ChangeTracker_Tracked(sender, e);
        }
    
        public override void ChangeTracker_StateChanged(object? sender, EntityStateChangedEventArgs e)
        {
            if (e.Entry.Entity.GetType() == typeof(OpenIddictToken))
            {
                return;
            }
    
            base.ChangeTracker_StateChanged(sender, e);
        }
    }

With this in place, we ran some tests. We waited for half an hour in 4 tabs. All of them sent requests to connect/token twice at each 15th minute. The system does not kick users out. Thank you! Now we have two questions:

1. We still see the concurrency exception in logs: [ERR] The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded. See https://go.microsoft.com/fwlink/?LinkId=527962 for information on understanding and handling optimistic concurrency exceptions. Volo.Abp.Data.AbpDbConcurrencyException: The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded. See https://go.microsoft.com/fwlink/?LinkId=527962 for information on understanding and handling optimistic concurrency exceptions.

2. In your above reply, you said this will be fixed in v9.1.1. It is released, we tested using it but the error persisted. When this issue gets fixed in ABP itself, we will remove the above code from our codebase. Could you tell us in which version will this be fixed?

Thank you again and best wishes.

• Exception message and full stack trace:
  Volo.Abp.Data.AbpDbConcurrencyException: The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded. See https://go.microsoft.com/fwlink/?LinkId=527962 for information on understanding and handling optimistic concurrency exceptions. ---> Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException: The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded. See https://go.microsoft.com/fwlink/?LinkId=527962 for information on understanding and handling optimistic concurrency exceptions.

• Steps to reproduce the issue:

  1. Set the 'Prevent Concurrent Login' setting to 'Logout from all devices.' or 'Logout from same type devices.'
  2. Open up any page of the application on multiple tabs
  3. Wait for token refresh, which typically happens in 15 minutes.
  4. Observe log outs.

This is reproducible on https://demo.abp.io/ as well. We created a new project and observed that it may not happen with two tabs sometimes. To share logs, we opened up 8 tabs and observed the logout behavior. Logs are at https://qtext.io/rgzn . Dev console of one of those tabs is below:

This may be somehow related to https://abp.io/support/questions/5257/Occasionally-logging-out-due-to-validating-access-token-error

We are currently experiencing this issue with our web application which is in production. Specifically, when users attempt to access the application through multiple tabs simultaneously, we encounter a concurrency exception that results in unexpected logouts. To temporarily mitigate the issue, we have asked our users to limit their access to a single tab. However, this workaround is inconvenient and reflects poorly on the user experience.

Could you kindly assist us by providing a fix for this issue or suggest an alternative workaround to address the problem? Given the urgency of the situation, we would greatly appreciate your timely support.

Thank you in advance for your help. We look forward to hearing from you soon.

Hello Shiwei,

Thank you for your response.

Best, Burkay

Hello Shiwei,

I got an email saying this is closed by ServiceBot. You mentioned that you would be reaching out to the team for input, and I was wondering if there have been any updates or developments regarding it.

Thank you for your help, and I look forward to hearing back from you!

Best, Burkay

I created a new project with ABP CLI 8.3.3 as you suggested earlier. The problem is fixed. Thank you for the fix and for the refund :)

Hello,

Thank you for all the efforts you put into this framework. We have been happily using ABP Suite for a while now.

For our customers to report issues, we need a ticketing system pretty much like "ABP Support." We believe that such a feature would greatly enhance customer experience and streamline the support process for both your customers and ours. We just wanted to ask if you have any intentions of publishing this as a module in the near future?

We appreciate your consideration and look forward to your response.

Burkay

Thank you! I wlll check it as soon as possible. Meanwhile, since this required a fix on your part, could you refund our question credit?

Hello.

I used ABP CLI 8.3.2 to generate a new project. Below is the command I used and its output:

abp new Acme.BookStore -u angular -dbms PostgreSQL -m none --theme leptonx-lite -csf ABP CLI 8.3.2 Creating your project... Project name: Acme.BookStore DBMS: PostgreSQL UI Framework: Angular Output folder: d:\Source\Acme.BookStore Using cached template: app, version: 8.3.2 Theme: LeptonXLite Check out the documents at https://abp.io/docslatest/solution-templates/layered-web-application 'Acme.BookStore' has been successfully created to 'd:\Source\Acme.BookStore' Creating initial migrations... Initial migrations are created. Installing client-side packages... Found 2 projects. d:\Source\Acme.BookStore\angular d:\Source\Acme.BookStore\aspnet-core\src\Acme.BookStore.HttpApi.Host Running Yarn on d:\Source\Acme.BookStore\angular yarn install v1.22.22 info No lockfile found. [1/4] Resolving packages... warning eslint@8.57.1: This version is no longer supported. Please see https://eslint.org/version-support for other options. warning eslint > @humanwhocodes/config-array@0.13.0: Use @eslint/config-array instead warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported warning eslint > file-entry-cache > flat-cache > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported warning eslint > file-entry-cache > flat-cache > rimraf > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. warning karma > glob@7.2.3: Glob versions prior to v9 are no longer supported warning karma > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported [2/4] Fetching packages... [3/4] Linking dependencies... warning "@abp/ng.account > @abp/ng.theme.shared > @ng-bootstrap/ng-bootstrap@16.0.0" has incorrect peer dependency "@angular/common@^17.0.0". warning "@abp/ng.account > @abp/ng.theme.shared > @ng-bootstrap/ng-bootstrap@16.0.0" has incorrect peer dependency "@angular/core@^17.0.0". warning "@abp/ng.account > @abp/ng.theme.shared > @ng-bootstrap/ng-bootstrap@16.0.0" has incorrect peer dependency "@angular/forms@^17.0.0". warning "@abp/ng.account > @abp/ng.theme.shared > @ng-bootstrap/ng-bootstrap@16.0.0" has incorrect peer dependency "@angular/localize@^17.0.0". warning "@abp/ng.components > ng-zorro-antd@17.4.1" has incorrect peer dependency "@angular/animations@^17.0.0". warning "@abp/ng.components > ng-zorro-antd@17.4.1" has incorrect peer dependency "@angular/common@^17.0.0". warning "@abp/ng.components > ng-zorro-antd@17.4.1" has incorrect peer dependency "@angular/forms@^17.0.0". warning "@abp/ng.components > ng-zorro-antd@17.4.1" has incorrect peer dependency "@angular/core@^17.0.0". warning "@abp/ng.components > ng-zorro-antd@17.4.1" has incorrect peer dependency "@angular/platform-browser@^17.0.0". warning "@abp/ng.components > ng-zorro-antd@17.4.1" has incorrect peer dependency "@angular/router@^17.0.0". warning "@abp/ng.components > ng-zorro-antd > @ant-design/icons-angular@17.0.0" has incorrect peer dependency "@angular/common@^17.0.1". warning "@abp/ng.components > ng-zorro-antd > @ant-design/icons-angular@17.0.0" has incorrect peer dependency "@angular/core@^17.0.1". warning "@abp/ng.components > ng-zorro-antd > @ant-design/icons-angular@17.0.0" has incorrect peer dependency "@angular/platform-browser@^17.0.1". warning " > @abp/ng.theme.lepton-x@3.3.2" has unmet peer dependency "@abp/ng.account.core@~8.3.2". warning " > @angular-eslint/eslint-plugin@18.1.0" has unmet peer dependency "@typescript-eslint/utils@^7.11.0 || ^8.0.0-alpha.37". warning "@angular-eslint/eslint-plugin > @angular-eslint/utils@18.1.0" has unmet peer dependency "@typescript-eslint/utils@^7.11.0 || ^8.0.0-alpha.37". warning " > @angular-eslint/eslint-plugin-template@18.1.0" has unmet peer dependency "@typescript-eslint/utils@^7.11.0 || ^8.0.0-alpha.37". warning " > @angular-eslint/schematics@18.1.0" has unmet peer dependency "@angular-devkit/core@>= 18.0.0 < 19.0.0". warning " > @angular-eslint/schematics@18.1.0" has unmet peer dependency "@angular-devkit/schematics@>= 18.0.0 < 19.0.0". [4/4] Building fresh packages... success Saved lockfile. Done in 85.25s. Running Yarn on d:\Source\Acme.BookStore\aspnet-core\src\Acme.BookStore.HttpApi.Host yarn install v1.22.22 info No lockfile found. [1/4] Resolving packages... [2/4] Fetching packages... [3/4] Linking dependencies... warning "@abp/aspnetcore.mvc.ui.theme.leptonxlite > @abp/aspnetcore.mvc.ui.theme.shared > @abp/bootstrap > bootstrap@5.3.3" has unmet peer dependency "@popperjs/core@^2.11.8". [4/4] Building fresh packages... success Saved lockfile. Done in 16.34s. UPDATE angular.json (6635 bytes) UPDATE src/app/app.module.ts (2092 bytes)

Below is the content of home.component.html right after above command returns:

<div class="my-3 text-center">
  <h3>Let's improve your application!</h3>
  <p>Here are some links to help you get started:</p>
</div>
<div class="card mt-4 mb-5">
  <div class="card-body">
    <div class="row text-center justify-content-md-center">
      <ng-container
        *ngTemplateOutlet="
          starterLinkTemplate;
          context: {
            $implicit: {
              title: 'Learn the ABP Framework',
              description:
                'Explore the comprehensive documentation to learn how to build a modern web application.',
              links: [
                {
                  href: 'https://abp.io/docs/latest?ref=tmpl',
                  label: 'See Documents'
                }
              ]
            }
          }
        "
      ></ng-container>

      <ng-container
        *ngTemplateOutlet="
          starterLinkTemplate;
          context: {
            $implicit: {
              title: 'Samples',
              description: 'See the example projects built with the ABP Framework.',
              links: [
                {
                  href: 'https://abp.io/docs/latest/samples?ref=tmpl',
                  label: 'All samples'
                }
              ]
            }
          }
        "
      ></ng-container>

      <ng-container
        *ngTemplateOutlet="
          starterLinkTemplate;
          context: {
            $implicit: {
              title: 'ABP Community',
              description: 'Get involved with a vibrant community and become a contributor.',
              links: [
                {
                  href: 'https://abp.io/community/',
                  label: 'Community'
                },
                {
                  href: 'https://abp.io/docs/latest/contribution?ref=tmpl',
                  label: 'Contribute'
                }
              ]
            }
          }
        "
      ></ng-container>
    </div>
    <div class="row text-center mt-lg-3 justify-content-md-center">
      <ng-container
        *ngTemplateOutlet="
          starterLinkTemplate;
          context: {
            $implicit: {
              title: 'ABP Blog',
              description: 'Take a look at our recently published articles.',
              links: [
                {
                  href: 'https://abp.io/blog?ref=tmpl',
                  label: 'See Blog'
                }
              ]
            }
          }
        "
      ></ng-container>
      
      <ng-template #githubButtonsTemplate>
        <p class="mb-1">
          <iframe
            scrolling="no"
            src="https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fabpframework%2Fabp&title=&aria-label=Star%20tabalinas%2Fjsgrid%20on%20GitHub&data-icon=octicon-star&data-text=Star&data-size=large&data-show-count=true"
            style="
              width: 122px;
              height: 28px;
              border: none;
              display: inline-block;
              margin-right: 4px;
            "
          ></iframe>
          <iframe
            scrolling="no"
            src="https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fabpframework%2Fabp%2Fissues&title=&aria-label=Issue%20tabalinas%2Fjsgrid%20on%20GitHub&data-icon=octicon-issue-opened&data-text=Issue&data-size=large"
            style="
              width: 72px;
              height: 28px;
              border: none;
              display: inline-block;
              margin-right: 4px;
            "
          ></iframe>

          <iframe
            scrolling="no"
            src="https://buttons.github.io/buttons.html#href=https%3A%2F%2Fgithub.com%2Fabpframework%2Fabp%2Ffork&title=&aria-label=Fork%20tabalinas%2Fjsgrid%20on%20GitHub&data-icon=octicon-repo-forked&data-text=Fork&data-size=large&"
            style="width: 72px; height: 28px; border: none; display: inline-block"
          ></iframe>
        </p>
      </ng-template>
    </div>
  </div>
</div>

This file is missing some parts such as welcome message, login button and template definitions. Welcome message and login button is not critical, but the lack of template definitions causes angular compilation error.