Activités de "paul.harriman"

Just making sure case doesn't get closed for inactivity

MyGet is still down, I decided to take your suggestion and go manual

Manually upgraded packages from 7.2.3 => 7.3.0. Then abp install-libs. Also needed to add Hangfire.Core. When trying to run the backend the restores take about 10 minutes (usually ~1 minute) and then we get this error (i clipped it as it is very long). I got to this point yesterday before the issues w/ myget.

previous restores are all succesful and then this:

c:\appdev\otised\OtisEd.Synergyz\aspnet-core\src\OtisEd.Synergyz.HttpApi.Host\OtisEd.Synergyz.HttpApi.Host.csproj : error NU1106: Unable to satisfy conflicting requests for 'Volo.Abp.MultiTenancy': Volo.Abp.MultiTenancy (>= 7.3.0)

.....

package/Volo.Abp.MultiTenancy.Abstractions 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.MultiTenancy.Abstractions 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.Localization 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.MultiTenancy.Abstractions 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.MultiTenancy.Abstractions 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.Localization 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.Localization 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3.0) (via package/Volo.Abp.Localization 7.3.0), Volo.Abp.VirtualFileSystem (>= 7.3 Failed at 'command: "dotnet.exe" restore c:\appdev\otised\OtisEd.Synergyz\aspnet-core\OtisEd.Synergyz.sln --interactive' (994572ms) with error: ERROR ExitCode(null)

so this morning abp update runs normally. the ~10 minute restore is back to normal. the long error still exists when i try and run the backend. Scott and I are looking at it now

c:\appdev\otised\OtisEd.Synergyz\aspnet-core\src\OtisEd.Synergyz.HttpApi.Host\OtisEd.Synergyz.HttpApi.Host.csproj : error NU1106: Unable to satisfy conflicting requests for 'Volo.Abp.MultiTenancy': Volo.Abp.MultiTenancy (>= 7.3.0) (via package/Volo.Abp.

lepton-x is at 2.3.0

host/package.json "@volo/abp.aspnetcore.mvc.ui.theme.leptonx": "~2.3.0",

angular/package.json "@volosoft/abp.ng.theme.lepton-x": "^2.3.0",

upgraded to 7.3.1, then i get

• ABP Framework version: v7.2.3
• UI Type: Angular
• Database System: EF Core SQL Server
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

The GDPR Consent Cookie Component is creating a date of 6 months in the future for the cookie expiration, but b/c of the way the cookie create is coded, the expiration is Session.

The first screen shot, uses code:

• document.cookie = this.CookieKey + '=true;' + expireDate + ';path=/';

the second screen shot shows with updated code of: document.cookie = this.CookieKey + '=true;expires=' + expireDate + ';path=/';

I agree, 6 months is good, but as it is coded currently it is a session time, NOT 6months.

We are experiencing the same issue. we generate the proxies, no problems. then we try and build or start the angular project, then we get errors. if we remove the generics issues from the proxies, eveything builds. what error logs are you looking for?

Error: src/app/proxy/client-models/models.ts:6:15 - error TS2305: Module '"../models"' has no exported member 'TKey'.

6 import type { TKey } from '../models'; ~~~~

Error: src/app/proxy/models.ts:2:15 - error TS2303: Circular definition of import alias 'T'.

2 import type { T } from './models'; ~ Error: src/app/proxy/models.ts:2:15 - error TS2459: Module '"./models"' declares 'T' locally, but it is not exported.

2 import type { T } from './models'; ~ src/app/proxy/models.ts:2:15 2 import type { T } from './models'; ~ 'T' is declared here.

please tell me where to to send them to. there is some sensitive info in them.

• i started the backend up.
• did a generate proxy
• started up the front end, got the angular error
• made a copy of todays log. doesn't look like much besides normal stuff

i did not see any error in the logs. the code that i think is causing the issue has been there for a year, so it is not new code. generate proxies is creating the issue. you can see it in the git differences that it is new code. are you saying we can no longer use generics in our method signatures/entities?

public virtual async Task<PagedResultDto<CompareLookupDto<int?>>> GetLookupAsync(LookupRequestDto input) { return await _modelAppService.GetLookupAsync(input); }

public class CompareLookupDto<TKey>: LookupDto<TKey> { public bool IsPublic { get; set; } }

• ABP Framework version: v8.0.4
• UI Type: Angular
• Database System: EF Core SQL Server
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

When we upgraded our websites from 7 to 8.0.4 we ran into several issues when running our backend tests

System.InvalidOperationException : SqliteConnection does not support nested transactions. => we added code to disable uow when running tests

An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module Volo.Abp.OpenIddict.AbpOpenIddictDomainModule, Volo.Abp.OpenIddict.Domain, Version=8.0.4.0, Culture=neutral, PublicKeyToken=null: Timeout expired. The timeout elapsed prior to obtaining a distributed lock on the 'lock:recurring-job:HangfirePeriodicBackgroundWorkerAdapter<TokenCleanupBackgroundWorker>.DoWorkAsync' resource.. See the inner exception for details.. ==> If we run all the backend tests, some would fail, if we re-ran each individual test, they would pass. we implemented a fix which ran all the tests serially

Volo.Abp.AbpInitializationException : An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module OtisEd.Synergyz.SynergyzTestBaseModule, OtisEd.Synergyz.TestBase, Version=7.2.1.0, Culture=neutral, PublicKeyToken=null: The transaction object is not associated with the same connection object as this command.. See the inner exception for details. ==> backend tests run fine locally, but in github ci/cd they fail, sometimes, flaky

Do you have any suggestions?

Maybe is a way to remove hangfire from the tests. Mock the hangfire service instead of providing an actual database using in memory

we have 2 websites, made sure they matched exactly what you had, one passed tests, the other did not

Error Message: Volo.Abp.AbpInitializationException : An error occurred during the initialize Volo.Abp.Modularity.OnApplicationInitializationModuleLifecycleContributor phase of the module OtisEd.Synergyz.SynergyzTestBaseModule, OtisEd.Synergyz.TestBase, Version=7.2.1.0, Culture=neutral, PublicKeyToken=null: The transaction object is not associated with the same connection object as this command.. See the inner exception for details. ---- System.InvalidOperationException : The transaction object is not associated with the same connection object as this command.