Käyttäjän "rcalv002" toiminnot

Anjali,

I tried that, but it just causes more inconsistencies, rabbit hole of dependency problem. All abp packages should be on same version to avoid this, thats what im trying to do but it doesnt work either.

I create a brand new project at v 7.2.2 then i tried to update the project to 7.2.3 and i got the same update errors so it doesn't seem project specific. Can we have a screenshare?

I did perform the steps above.

I'm reporting that I have a solution that i need to update, it is currently on 7.2.2. Part of the update is to run abp update on this solution which will update the abp components from 7.2.2 to 7.2.3. So I run abp update, and you can see the failures above. I **cannot **simply start a brand new project on a newer version and copy all my code.

I have a bugfix I must deliver to a client, but I cannot build the solution because i receive this error in authserver.

Even though I have checked and auth server explicitly has this reference, i still get the error and cannot build.

so then i went to update my solution to 7.2.3 via abp update -v 7.2.3 and it fails. I need to resolve this asap.

Your assistance please, I need to update a project and this is holding the task

Your assistance please, I need to update a project and this is holding the task

Thanks for your help. Same problem

PS D:\Dev\Modules\Cns.Modules.ServiceLayerProxy> abp update -v 7.2.3 ABP CLI 7.2.3 Unable to update package "Volo.Abp.AspNetCore.Components.WebAssembly.Theming" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.MongoDB" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.EntityFrameworkCore" version v7.2.3 to v7.2.3. Updating package "Volo.Abp.AspNetCore.Mvc" from v7.2.2 to v7.2.3. Unable to update package "Volo.Abp.Autofac" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Ddd.Application.Contracts" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Mvc" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Autofac" version v7.2.3 to v7.2.3. Could not parse package "Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" version v2.2.-. Skipped. Could not parse package "Volo.Abp.AspNetCore.Components.Server.LeptonXTheme" version v2.2.-. Skipped. Updating package "Volo.Abp.Autofac" from v7.2.2 to v7.2.3. Could not parse package "Volo.Abp.AspNetCore.Mvc.UI.Theme.LeptonX" version v2.2.-. Skipped. Unable to update package "Volo.Abp.Http.Client" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Autofac" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Autofac.WebAssembly" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Autofac" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Ddd.Domain" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Components.Server.Theming" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AutoMapper" version v7.2.3 to v7.2.3.

1. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.commercial.suitetemplates/index.json with an error: 404-The specified blob does not exist.. Waiting 2 secs for the next try... Unable to update package "Volo.Abp.AspNetCore.Mvc" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Validation" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Http.Client.IdentityModel" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Caching" version v7.2.3 to v7.2.3.
2. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.leptontheme.management.blazor.server/index.json with an error: 404-The specified blob does not exist.. Waiting 2 secs for the next try...
3. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.components.webassembly.leptontheme/index.json with an error: 404-The specified blob does not exist.. Waiting 2 secs for the next try... Updating package "Volo.Abp.AspNetCore.Mvc.UI.MultiTenancy" from v7.2.2 to v7.2.3.
4. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.leptontheme.management.web/index.json with an error: 404-The specified blob does not exist.. Waiting 2 secs for the next try... Unable to update package "Volo.Abp.Authorization.Abstractions" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Authorization" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Caching.StackExchangeRedis" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Mvc.UI.Theme.Shared" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AutoMapper" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Autofac" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Caching" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Caching.StackExchangeRedis" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Caching.StackExchangeRedis" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Ddd.Domain" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Mvc.Client" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Components.Web.Theming" version v7.2.3 to v7.2.3. Updating package "Volo.Abp.Autofac" from v7.2.2 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Mvc.UI.MultiTenancy" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Ddd.Application" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.SettingManagement.Blazor" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.TestBase" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.EntityFrameworkCore.SqlServer" version v7.2.3 to v7.2.3. Updating package "Volo.Abp.Caching.StackExchangeRedis" from v7.2.2 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Authentication.OpenIdConnect" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AutoMapper" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.EntityFrameworkCore.Sqlite" version v7.2.3 to v7.2.3. Updating package "Volo.Abp.EntityFrameworkCore.SqlServer" from v7.2.2 to v7.2.3. Unable to update package "Volo.Abp.Swashbuckle" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.Http.Client.IdentityModel.Web" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.SettingManagement.Domain" version v7.2.3 to v7.2.3. Updating package "Volo.Abp.Swashbuckle" from v7.2.2 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Serilog" version v7.2.3 to v7.2.3. Updating package "Volo.Abp.AspNetCore.Serilog" from v7.2.2 to v7.2.3. Unable to update package "Volo.Abp.Http.Client.Web" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.PermissionManagement.EntityFrameworkCore" version v7.2.3 to v7.2.3.
5. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.leptontheme.management.httpapi/index.json with an error: 404-The specified blob does not exist.. Waiting 2 secs for the next try... Unable to update package "Volo.Abp.Swashbuckle" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.SettingManagement.EntityFrameworkCore" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AspNetCore.Serilog" version v7.2.3 to v7.2.3. Unable to update package "Volo.Abp.AuditLogging.EntityFrameworkCore" version v7.2.3 to v7.2.3.
6. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.web/index.json with an error: 404-The specified blob does not exist.. Waiting 2 secs for the next try...
7. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.entityframeworkcore/index.json with an error: 404-The specified blob does not exist.. Waiting 2 secs for the next try...
8. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.commercial.suitetemplates/index.json with an error: 404-The specified blob does not exist.. Waiting 4 secs for the next try...
9. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.aspnetcore.components.webassembly.leptontheme/index.json with an error: 404-The specified blob does not exist.. Waiting 4 secs for the next try...
10. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.leptontheme.management.web/index.json with an error: 404-The specified blob does not exist.. Waiting 4 secs for the next try...
11. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.leptontheme.management.blazor.server/index.json with an error: 404-The specified blob does not exist.. Waiting 4 secs for the next try...
12. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.leptontheme.management.httpapi/index.json with an error: 404-The specified blob does not exist.. Waiting 4 secs for the next try...
13. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.abp.identity.pro.web/index.json with an error: 404-The specified blob does not exist.. Waiting 4 secs for the next try...
14. HTTP request attempt failed to https://api.nuget.org/v3-flatcontainer/volo.saas.entityframeworkcore/index.json with an error: 404-The specified blob does not exist.. Waiting 4 secs for the next try...

Trying to run abp update -v 7.2.3 i receive many errors with 404 blob not found, when i go to the https://nuget.abp.io/myprivatekey where the key comes from my https://commercial.abp.io/my-organizations I can see links but when i click any link i receive 404.

My project is not building due to some inconsistency with abp multitenancy requirement on lepton.

Thanks but I don't think that's an option for me, since all my projects are already using the abp provided implementation, and we don't want to re-implement something the framework is offering, it would be great of the abp implementation could add a property object with information of the particular task so that we can then use BackgroundJob to requeue it..

You mean stop using

transactionProcessingJob : AsyncBackgroundJob<TArgs> ??

Hi,

I had already tried something with BackgroundJob before I posted, I just couldn't get it to work and Is till don't understand how to apply this. In essence a class that processes a type of job

public class TransactionProcessingJob : AsyncBackgroundJob<TransactionProcessingArgs>, ITransientDependency

has method

public override async Task ExecuteAsync(TransactionProcessingArgs args)
{
    
    try
    {
        IUnitOfWorkManager unitOfWorkManager = _serviceProvider.GetRequiredService<IUnitOfWorkManager>();
        using (unitOfWorkManager.Begin())
        {
            // stuff in here
        }
    }

    catch (Exception ex)
    {
        Logger.LogError(ex, "Unable to process transaction {TransactionId}", args.TranId);
        await _emailSender.QueueAsync(
                to: _config["Notifications:Recipients"],
                subject: $"Error processing transaction {args.TranId} {args.Channel} {args.ObjectType} {args.ExternalID} for Tenant: {tenantId}",
                body: $"{ex.Message}</br>{ex.InnerException?.Message}"
            );

        using (_currentTenant.Change(tenantId != default ? tenantId : null))
        {
            var transaction = await _transactionRepository.GetAsync(args.TranId);
            transaction.Error = $"{ex.Message}\n{ex?.InnerException?.Message}";
            await _transactionRepository.UpdateAsync(transaction);
        }

        throw;
    }

}

In the catch block, it'd be nice to capture job id and set it on a property of the transaction, this way from a dashboard page, using TransactionAppService

The user can retry that transaction.

I had already tried to do this adapating an implementation in one of the modules that grabs a distributed lock and IBackgroundJobStore to use FindAsync(guid) to retrieve the job, but since I don't have the job id I can't use IBackgroundJobExecuter to execute the job.

• ABP Framework version: v7.2.2
• UI Type: Blazor Server
• 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:

I'm having a problem with jobs that are processed via hangfire module. When a job fails it can be requeued through the hangifre ui, but this interface is more backend than frontend user. I have a page in the application for front end user to see jobs in error state. I want them to be able to click a button and retry this job (not enqueue again, but reprocess failed job just like in backend ui). I've tried many things but in the end I always reach a point where I get stuck.

During job execution can I capture the job id somehow to set it in the error property of my transaction and then use this to retry the job when the user presses the button to retry?