EF Core 5 support

We will use this issue to track the progress on supporting EF Core 5.

@ChrisJollyAU I think we should make this one comply with what's expected for EF Core 5, ensure the tests that did run before still run now, and get this out the door. Split queries are basically a must for Jet.
I propose moving any real new features and major work to the EF Core 6 support, so we can release in parallel to their release upstream in November.

So more of a compatibility update? Can do go with that

Do you plan to publish the daily builds in your Azure DevOps feed?
Thanks in advance for your all your work!

Do you plan to publish the daily builds in your Azure DevOps feed?

@francescomazzurco Yes, every merge automatically makes it into the daily build feed.

@lauxjpn What's the current plan? .Net 6 is already here

@lauxjpn @bubibubi Hello there! How can I obtaion some test build with EF Core 5 (or even EF Core 6) Support? Thank you.

@bairog

I have scheduled time on Sunday to fix the tests and merge this.

@bairog If you feel like it, give the attached a try. They are currently a work in progress. The EF5/Net5 is at the exact stage the the .Net 5 pull request is at. Compiled from my net5structure branch https://github.com/ChrisJollyAU/EntityFrameworkCore.Jet/tree/net5structure
The .Net 6 (my branch https://github.com/ChrisJollyAU/EntityFrameworkCore.Jet/tree/net6) is copied from the .Net 5 and updated so that it can compile. I've done some basic reading and writing in it but no idea on the more complex stuff
ef6.zip
ef5.zip
Unzip to the project and manually add as reference.
If you prefer a nuget package, you may have to wait for @lauxjpn to finish the tests and merge so that it will show in the nightly builds

@ChrisJollyAU Thank you for your work.
I've tried to test your ef6.zip.
Database that I need to query has a lot of specific: table names are Cyrillic, tables has no primary key, colums names are Cyrillic.
So I've created .NET 6.0 class library, added EntityFrameworkCore.Jet.dll as a library reference and wrote the following code:

My entites and DbContext in a .NET 6.0 class library
public partial class TechnicalLibraryCatalogItem
    {
        public Int32? OrderNo { get; set; }

        public String? InventoryNo { get; set; }
    }

public partial class TechnicalLibraryContext : DbContext
    {
        public TechnicalLibraryContext()
        {
        }

        public TechnicalLibraryContext(DbContextOptions<TechnicalLibraryContext> options)
            : base(options)
        {
        }

        public virtual DbSet<TechnicalLibraryCatalogItem> TechnicalLibraryCatalogItems { get; set; }

        protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        {
            if (!optionsBuilder.IsConfigured)
            {
                optionsBuilder.UseJet(@"Provider=Microsoft.ACE.OLEDB.12.0;Data Source=EKTB.mdb;");
            }
        }

        protected override void OnModelCreating(ModelBuilder modelBuilder)
        {
            modelBuilder.Entity<TechnicalLibraryCatalog>().HasNoKey();
            modelBuilder.Entity<TechnicalLibraryCatalog>().ToTable("Каталог ТБ");
            modelBuilder.Entity<TechnicalLibraryCatalog>().Property(tlc => tlc.OrderNo).HasColumnName("№ п/п");
            modelBuilder.Entity<TechnicalLibraryCatalog>().Property(tlc => tlc.InventoryNo).HasColumnName("Инв  №");
        }
    }

My code to read data from ASP .NET Core 6.0 Web App
using (var scope = app.Services.CreateScope())
    {
        var services = scope.ServiceProvider;

        using (var context = services.GetRequiredService<TechnicalLibraryContext>())
        {
             var lst = context.TechnicalLibraryCatalogItems.ToList();
        }
    }

I've compiled it but get the following error in runtime at .UseJet() line

System.TypeLoadException: 'To use OLE DB in conjunction with Jet, please reference the 'System.Data.OleDb' (version >= 5.0.0) NuGet package.'

I've added a nuget reference for latest System.Data.OleDb 6.0.0 to a class library project and now I have the following error on context.TechnicalLibraryCatalogItems.ToList() line:

System.ArgumentNullException: "Value cannot be null. (Parameter 'provider')"

Stack trace
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.CreateModel(Boolean designTime)
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.get_Model()
   at Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkServicesBuilder.<>c.<TryAddCoreServices>b__8_4(IServiceProvider p)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass2_0.<RealizeService>b__0(ServiceProviderEngineScope scope)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
   at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices()
   at Microsoft.EntityFrameworkCore.DbContext.get_Model()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.get_EntityType()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.CheckState()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.get_EntityQueryable()
   at Microsoft.EntityFrameworkCore.Internal.InternalDbSet`1.System.Collections.Generic.IEnumerable<TEntity>.GetEnumerator()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Program.<<Main>$>g__CreateDatabaseIfNotExists|0_3(WebApplication app) in D:\Tabit.NET_DBPlanov\DBPlanov.Web\Program.cs:line 109

After that I've tried to reverse engineer my existing MS Access database as advised in wiki.
In Package Manager Console (Tools –> NuGet Package Manager –> Package Manager Console) I've wrote
Install-Package Microsoft.EntityFrameworkCore.Tools
and after that:
Scaffold-DbContext -Connection "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=D:\MyDB.mdb;" -Provider EntityFrameworkCore.Jet
But it failed with an error:

System.InvalidOperationException: Unable to resolve service for type 'Microsoft.EntityFrameworkCore.Diagnostics.IDiagnosticsLogger`1[Microsoft.EntityFrameworkCore.DbLoggerCategory+Scaffolding]' while attempting to activate 'EntityFrameworkCore.Jet.Scaffolding.Internal.JetDatabaseModelFactory'.

Stack trace
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.CreateArgumentCallSites(Type implementationType, CallSiteChain callSiteChain, ParameterInfo[] parameters, Boolean throwIfCallSiteNotFound)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.CreateConstructorCallSite(ResultCache lifetime, Type serviceType, Type implementationType, CallSiteChain callSiteChain)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.TryCreateExact(ServiceDescriptor descriptor, Type serviceType, CallSiteChain callSiteChain, Int32 slot)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.CreateCallSite(Type serviceType, CallSiteChain callSiteChain)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.GetCallSite(Type serviceType, CallSiteChain callSiteChain)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.CreateArgumentCallSites(Type implementationType, CallSiteChain callSiteChain, ParameterInfo[] parameters, Boolean throwIfCallSiteNotFound)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.CreateConstructorCallSite(ResultCache lifetime, Type serviceType, Type implementationType, CallSiteChain callSiteChain)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.TryCreateExact(ServiceDescriptor descriptor, Type serviceType, CallSiteChain callSiteChain, Int32 slot)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.CreateCallSite(Type serviceType, CallSiteChain callSiteChain)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteFactory.GetCallSite(Type serviceType, CallSiteChain callSiteChain)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor(Type serviceType)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
   at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.EntityFrameworkCore.Design.Internal.DatabaseOperations.ScaffoldContext(String provider, String connectionString, String outputDir, String outputContextDir, String dbContextClassName, IEnumerable`1 schemas, IEnumerable`1 tables, String modelNamespace, String contextNamespace, Boolean useDataAnnotations, Boolean overwriteFiles, Boolean useDatabaseNames, Boolean suppressOnConfiguring, Boolean noPluralize)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.ScaffoldContextImpl(String provider, String connectionString, String outputDir, String outputDbContextDir, String dbContextClassName, IEnumerable`1 schemaFilters, IEnumerable`1 tableFilters, String modelNamespace, String contextNamespace, Boolean useDataAnnotations, Boolean overwriteFiles, Boolean useDatabaseNames, Boolean suppressOnConfiguring, Boolean noPluarlize)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.ScaffoldContext.<>c__DisplayClass0_0.<.ctor>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.<>c__DisplayClass3_0`1.<Execute>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)

In MS docs there is only Microsoft.EntityFrameworkCore.Diagnostics.IDiagnosticsLogger for EF Core 5.0, not for EF Core 6.0.
So I'm in a deadend for now. Any advices are appreciated. Thank you in advance.

You might be missing some references

Need all 3

@ChrisJollyAU
Unfortunatelly I've already tried that with no success (errors are the sane). All three libraries (as well as System.Data.OleDb.dll) are present in output directory. I've updated my initial post here.

I don't see any thing related to Jet in the stack traces. Looks like it's just around in ef core.
Also, not sure what you're trying to do with the scope and serviceProvider.
DbContextOptionsBuilder builder = new DbContextOptionsBuilder<ModelContext>();             builder.UseJet("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\\test\\recent.mdb;").UseLazyLoadingProxies();             context = new ModelContext((DbContextOptions<ModelContext>)builder.Options);
That's how I do it in my console program. Then just use context as normal

@ChrisJollyAU
Just changed my code to this - unfortunatelly same error
DbContextOptionsBuilder builder = new DbContextOptionsBuilder<TechnicalLibraryContext>();
builder.UseJet("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\\MyDB.mdb;");
var context = new TechnicalLibraryContext((DbContextOptions<TechnicalLibraryContext>)builder.Options);
var lst = context.TechnicalLibraryCatalogItems.ToList();

Ok, I will try to perform a test with "traditional" MS database (with English table names and column names) - maybe that is the core of the problem here,,,

@ChrisJollyAU
Same error with "traditional" MS database. Could you please share you test example full code (including test database) - so I could finally find the real core of my problem? Thank you in advance..

Actually, might have the same problem on ef6. It is experimental right now. Also perhaps should have a separate issue for ef6 experimental stuff

@bairog @ChrisJollyAU I moved the recent posts to #111.

A 5.0 alpha is now available via our daily builds feed.

For the 5.0 GA release, we have to ensure that all tests that worked in 3.1 are still working.
We will also need feedback from the community regards any issue their existing applications have with the new release.

A 5.0 alpha prerelease is now available via our daily builds feed.

@lauxjpn @ChrisJollyAU
I've tested 5.0 alpha prerelease in my console application with .net5.0-windows7.0 TFM. Basic reading with .Where() filtering is working as expected.
P. S. I have x86 version of MS Office 2010 Plus installed. And in my test project I had to switch to x86, because I got an error with AnyCPU:

The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine

Is there any way to make you provider work in AnyCPU test projects?
Installing x64 version of Microsoft Access Database Engine 2010 Redistributable (even with a /passive flag trick) is not an option for me - it breaks my existing x86 MS Office installation.
Wiki page tells us that The provider published on NuGet is compiled with AnyCPU Platform. - so I suppose there should be a workaround for this.
Thank you in advance.

@bairog If the provider you have installed is x86 you have to target your project for x86. Similar for x64. It's just one of those things with using the access database engine - target the platform of the engine you have installed. And as you have found out, it's also not really doable/easy to have x86 and x64 installed side by side
As to the nuget being as AnyCPU, that's just so that the same package can be used in projects that target either x86 or target x64. Otherwise you may have ended up with a nuget package specifically for x86 projects and a different package for x64 and you would have to change the package if you changed your target platform
Also as to the project targeting AnyCPU, as far as I understand it, on a 32 bit OS it will run as 32bit/x86 (and you probably wouldnt notice any problems). On x64 systems it will run as x64

@bairog AnyCPU basically means "I can and will be compiled to whatever the target OS or host process architecture is when I am being executed". Nowadays, most machines run a 64 bit OS version.
If the app is compiled to 64 bit, it runs in a 64 bit process. A 64 bit process can only load 64 bit compiled libraries. Because of that, there is also a 64 bit dedicated registry hive for COM components (OLE DB is implemented using COM). If no 64 bit compiled ACE/Jet OLE DB provider has been registered in that hive, your 64 bit app cannot use it to access ACE/Jet databases via OLE DB.
The same is true for 32 bit apps respectively.

If you cannot install a 64 bit version of ACE/Jet, then you app needs to run as a 32 bit process to access the 32 bit libraries (either the ones explicitly installed by you, or the legacy ones that ship with Windows).
Since you are building a .NET 5 app, there should be at least two options for you to run your app as 32 bit:

Compile the app as 32 bit and run its exe file
Compile the app as AnyCPU and run it via the 32 bit .NET Host Process (default location: C:\Program Files (x86)\dotnet\dotnet.exe)

In my daily use, the 5.0 bits work fine.
So unless there are any objections, I suggest we publish those bits as a beta and then go GA after that.

I think there have been some fixes in the 3.1 branch since this was merged to the main branch. Just to confirm those have been ported to the .Net5 main branch?
If so then should be fine for beta

Anyone have issues with transactions? These were good in the 3x versions.
Invalid SQL statement; expected 'DELETE', 'INSERT', 'PROCEDURE', 'SELECT', or 'UPDATE'.

@horseyhorsey Please open a new issue and post us some code, so we can take a look at it. Thanks!

Can we close this topic? .Net 5 is already out of support so no use continuing on with this. Better to work on .Net 6/EF Core 6 and EF Core 7 support


Not able to run the project

hello,
i have done the following steps as mentioned for installation but getting this error, can you please check
Fatal error: Uncaught mysqli_sql_exception: Access denied for user 'root'@'localhost' (using password: YES) in C:\xampp\htdocs\projects\aa\CoffeeShop\includes\db_connect.php:7 Stack trace: #0 C:\xampp\htdocs\projects\aa\CoffeeShop\includes\db_connect.php(7): mysqli_connect('localhost', 'root', Object(SensitiveParameterValue), 'coffeeshop') #1 C:\xampp\htdocs\projects\aa\CoffeeShop\index.php(56): include_once('C:\xampp\htdocs...') #2 {main} thrown in C:\xampp\htdocs\projects\aa\CoffeeShop\includes\db_connect.php on line 7

hello,
i have done the following steps as mentioned for installation but getting this error, can you please check
Connected successfully to database: coffeeshop
Fatal error: Uncaught mysqli_sql_exception: Table 'coffeeshop.administrator' doesn't exist in C:\xampp\htdocs\CoffeeShop-Website-main\CoffeeShop\admin_panel\index.php:15 Stack trace: #0 C:\xampp\htdocs\CoffeeShop-Website-main\CoffeeShop\admin_panel\index.php(15): mysqli_prepare(Object(mysqli), 'SELECT admin_id...') #1 {main} thrown in C:\xampp\htdocs\CoffeeShop-Website-main\CoffeeShop\admin_panel\index.php on line 15


Android, swipe left-right not triggering tab change.

Android, swipe left-right not triggering tab change.
Each Tab item is a ScrollView. I guess it's because of that. Is there a chance to force it work same as on IOS (that is working fine even with Scroll View as a child).

I am having the same issue.

I figure it out, You need to follow steps described here: https://reactnavigation.org/docs/en/getting-started.html

I figure it out, You need to follow steps described here: https://reactnavigation.org/docs/en/getting-started.html

Thank you so much! (:


Why did you disable React-router links in documentation?

What happened to react-router. Don't you support it anymore?

Because it is not written yet, I think : https://github.com/reactjs/redux/blob/master/docs/advanced/UsageWithReactRouter.md

Yeah, there's a couple sections of the docs that were sketched out, but never actually written.  PRs totally welcome! :)

But there was a link. And I followed it. I read docs about react-router. Don't understand it.


Exposing Sha256 signature when supported.

Hi
Looking at the code, some archive formats like RAR use a Sha256 hash signature internally for every entry, is that correct?
If it is, is there any way in the API to retrieve the Sha256 of a given entry?
Supporting Sha256 can be useful to find files in archives without actually requiring to read the whole files.

PRs are welcome to improve this. Been out of it for personal reasons.


Getting Run Time Error!

java.lang.NoClassDefFoundError: Failed resolution of: Lkotlinx/coroutines/experimental/BuildersKt;

Please help me to solve this issue

yep same here. this project looks dead.

yep same here. this project looks dead.

Yes, unfortunately, you're right. It's easy to fix bugs (if you need it) but to continue developing the project requires refactoring.

Yes, unfortunately, you're right. It's easy to fix bugs (if you need it) but to continue developing the project requires refactoring.


sGTM Logs standardisation.

Init Query:
Our enterprise clients use sGTM and they need to have the ability to log all requests and their responses for debugging purposes. And if there was an error in execution then properly parse it and send it to engineers.
Problem:
Snowplow tag doesn't have the ability to log outgoing requests and their responses.
Solution:
At Stape we created a standard for all sGTM tag logs. Currently, all Stape tags already support our standardized logging format. And we already proposed our idea to other sGTM tags, and some of them already accepted this initiative.
Short description of the log standard rules:

Each log line must be a valid JSON object. (This allows parse logs by ELK, CloudWatch, Loki, etc.)
Each log object must contain at least Type, Name, TraceId fields.
Field Type must contain one of these values "Request", "Response", "Message". Witch helps easily filter logs.
TraceId must contain a unique identifier of the current incoming request. This field is used for stitching all logs done by all tags/clients during one request.
Name must contain tag name.

Here is an example of code from one of the tags: https://github.com/stape-io/facebook-tag/blob/main/template.js#L63
And here is an example of UI:

I hope you accept the idea of this initiative as we used your tags a lot and this will allow us to use the version from the template gallery instead our own repo.
If you like this idea I prepare PR with changes to your tag.
p.s. Thanks for a great open-source product and great sGTM template.

This certainly seems to be a reasonable idea and I'd be more than happy to accept a PR (and others across our other Tags).
I should be able to get someone on the team to take a look at the PR reasonably quickly once the PR is open 👍


Error: Unable to synchronously open file

On occasion, we see an error like the following in the logging output of a DPS job:
2023-06-28 18:44:24,674 [ForkPoolWorker-7:gedi_subset] [WARNING] Skipping granule SC:GEDI02_A.002:2432603210 [failed to read /projects/gedi-subsetter/output/GEDI02_A_2019218190402_O03679_04_T04561_02_003_02_V002.h5: Unable to synchronously open file (truncated file: eof =<PHONE_NUMBER>, sblock->base_addr = 0, stored_eof =<PHONE_NUMBER>)]

This indicates that the file in question was either corrupt to begin with, or it was not fully/properly downloaded. To determine which case it is, I downloaded the granule file directly via Earthdata Search and ran the following in the directory containing the file (in a Python env with h5py installed):
>>> import h5py
>>> with h5py.File('GEDI02_A_2019218190402_O03679_04_T04561_02_003_02_V002.h5') as f:
...     print(f)
...
<HDF5 file "GEDI02_A_2019218190402_O03679_04_T04561_02_003_02_V002.h5" (mode r)>

This indicates that the newly downloaded file is not corrupt, and thus neither is the original file. Therefore, the error above must be the result of a bad download.
We should detect such cases and retry the download up to 5 times.
CRITICAL: Since granule files are downloaded by maap-py, and maap-py will not overwrite an existing files by default, as part of the proposed retry logic, we must either explicitly remove the corrupt file, or pass overwrite=True to maap-py's getData method to force overwriting it upon retries.

The root cause of "bad" downloads was that the MAAP API was not passing through HTTP errors to maap-py, but instead passed HTTP success, causing the error message (HTML) to be saved as the file contents. This was fixed by this PR: https://github.com/MAAP-Project/maap-api-nasa/pull/93


Compile Android

I happy I found this plugin for Android/IOS. The iOS works fine but I cannot compile for Android.
I'm getting this msg:
error: constructor ReactNativeHeadingPackage in class ReactNativeHeadingPackage cannot be applied to given types;
new ReactNativeHeadingPackage(),
^
required: Activity
found: no arguments
reason: actual and formal argument lists differ in length
1 error
I'm trying to search how to fix, although I don't have much experience with Java/Android. If you could have a look at it.

Hello,
This error will be fixed, if the author publish a new version of his module on npm, with the sources on master.

Cool, that's what I'm hopping, haha.. I hope is checking the project. 👍

published v1.0.0. let me know if that fixes your problem

@yonahforst it worked, thanks a lot.


feature/adds ods build java task

fixes #75

@felipecruz91 @michaelsauter this is WIP at the moment. The creation of Docker image with java, maven and gradle works. As next I need to work on the tests. Could you please have a quick look and verify that I'm going in the right direction? Thanks!

@stitakis You're going in the right direction :) There are a few minor changes we did that will need to be corrected in some of your files, but I'd rather go through them with you in a call.

@felipecruz91 @michaelsauter I did the code changes suggested in review. My plan is to create the corresponding tests for a maven java project and also a gradle java project.

Looks good so far! If you need help, shout!

@stitakis Please pay attention to #134. I know make is not that common in Java land, but I believe it to be worthwhile to have the same base packages installed across the builder images.

@oalyman IIRC you also proposed to have the build tool in here. What about ods-build-java-gradle?

@michaelsauter I would even start with simply ods-build-gradle. Did not check the current task in detail but it will most probably be able to be used for kotlin, groovy and scala as well without any changes. So IMHO no point in putting the language in the name.
And if someone starts using it for C++ whatsoever we could name the new task more specific.

@oalyman Wouldn't you need e.g. sbt for Scala? And something else for Kotlin? These are not installed in the task yet ...

@michaelsauter For kotlin you would use gradle as well and then it's basically a special gradle plugin you use.
I already use kotlin with our existing ods jenkins-slave for gradle and didn't need to tweak anything...
For scala you could use gradle as well (personally I wouldn't do that but its possible) and it's just a different plugin as well.
Bcs. they are both JVM languages all should be able to be setup within your gradle build file by specifying the needed dependencies and in the end your build task would spit out the app.jar.
The ods-build-sbt I will hopefully be able to "start soon"™...

@stitakis Please pay attention to #134. I know make is not that common in Java land, but I believe it to be worthwhile to have the same base packages installed across the builder images.

I oversaw this. I'll add it.
btw... apart from renaming to ods-gradle-build are we good to go and merge this PR?

@oalyman Thanks for the details! Then I support renaming to ods-build-gradle 👍 Let's have a follow-up on testing.
@stitakis I went through the changes one more time and added some really minor comments. Let's rename and merge! As a heads up, I've created #210 today, which would need to be adapted for this new task as well.

@michaelsauter @oalyman I have renamed to ods-build-gradle and pushed the changes, I'm waiting for the tests to complete.


RHMAP-8377 - dockerfile for UPS

Customized dockerfile for UPS from dockerfiles repo

Closing unmerged. There is no sense to have Dockerfile in code repo. We would use separate repository for this purpose.


Fixed some issues found by code scanning tool

Fixed some linter issues
Motivation and context

How has this been tested?
Manually tested
Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage remained the same at 66.695% when pulling<PHONE_NUMBER>a690f8568183c229c25757c94aed29 on az/fix_linter into d4129f2868f2a56f41fd1f2fd23f0fe3ab8b6277 on develop.


Fix for data_version in file output, using SWE as an example

Change Summary
Right now, most instruments are not setting the Data_version global attribute correctly. This input value should come from the CLI and correspond to the version of the output file (in the filename, the "V002", for example) and not come from the code version (the "ground_software_version" attribute).
This change proposes a fix and a change to the CDF attribute manager which would allow for some dynamic values to be inserted into the CDF attributes.
Overview

Updated the class to include a dyanamic way to add global variables
Updated SWE as an example for what this would look like

Alternatives
An alternative idea would be to make Data_version a required input into ImapCdfManager rather than allowing for dynamic input of global attributes. The add_global_attribute method is more flexible, but also might encourage misuse.

@subagonsouth I do think it should be removed from there, thanks for catching it. If it is not included anywhere, attempting to generate the attributes should fail, so we can know right away.

As for the question about how the CLI knows, that's something that we need to do in sds-data-manager. As of now, I believe it just takes the version number of the input file, but @tech3371  has some drafts for version management that will solve it.

Can you merge this when you get chance? I have updated other instruments but will need to use new method for some instruments.


Final step

Hi guys, hopefully it is the last time I bother you,
I've used this guide to do a transfer: https://3ds.guide/dsiware-downgrade-(app-injection-and-second-3ds)
Now that the transfer is over, I do not know how to launch homebrew or anything. Ive clicked on ''sub wars'' but it says an error occurred and sends me back to the home page.
Any leads? Thank you.
Marika

I've just realized ive done something wrong.. the section 4 with steelhax...
Starting at number 18... I didnt do the rest about the target n3ds... what should I do now? :(

If Steeldiver gives you an error, that means that you didn't install it for the right version. If you installed it for version 11.2 but your target is 11.1 then you can try updating the target to see if it works then. Otherwise, you'll need another homebrew entrypoint (see Homebrew Launcher (No Browser)).
If Steeldiver isn't showing up at all, this could be because you used Tikshop in the past and you had a fake ticket, so the real one didn't transfer. In this case, just go into the eShop and download Steeldiver again. It'll give an error saying you don't need to redownload it, but then it will appear in your menu.
Hope this helps. In future, any problems you should ask on the GBATemp forums.

Thank you for your respond. My target is 11.2.0 - 35U, so I guess the update wont work.. And my source is an old3ds. You think my best option is to go No browser or to start the process all over again? Thank you for your help. And if you can send me the link to the best option I would appreciate it. I got lost alot during the process, especially that English isnt my first language X_X.

If you choose wrong version during steelhax installation. And Steel Diver crashes after transfer. I think you still be able to access homebrew. See troubleshooting, in section After System Transfering steelhax, it crashes to a black screen on the target 3DS

Thank you for trying... it seems like I still get the black screen. And then '' an error has occurred '' ... I guess I will redo the process again. Man I'm disappointed ... hopefully the same thing doesn't happen again.

What if I add the new bin in this file ? http://prntscr.com/dksn7q


crash application on retriving data from firebase

My applicatoin giving crash in FirebaseRecyclerAdapter class
public T getItem(int position) {
    return parseSnapshot(mSnapshots.getItem(position));
}
protected T parseSnapshot(DataSnapshot snapshot) {
    return snapshot.getValue(mModelClass);
}

and
@Override
public void onBindViewHolder(VH viewHolder, int position) {
    T model = getItem(position);
    populateViewHolder(viewHolder, model, position);
}

can ayone give me solution?

@juned3247 What's the crash?

problem solved by adding default constructor in Message(my class)
public Message() { }
thanks @SUPERCILEX  for replying


TypeError: Cannot read properties of undefined (reading 'speechRecognitionPermission')

Thanks for creating this package. I downloaded the source code and able to run the example. I installed the package on brand new expo app and tried to run npm run ios, I get the below error.  Same thing happens for an existing expo app.
Can you please suggest if I am missing anything?

my bad, I am able to resolve this issue. I had misconfigured plugin in app.json. Thanks for sharing this library.

What was the fix for this? I'm hitting this too and trying to figure out what i'm doing wrong:
VSCode highlights it: Plugin definition is empty, expected a file or dependency name(PLUGIN_DEFINITION_INVALID)

@elongstreet88 You need to wrap it in square brackets:
 "plugins: [
    "expo-router",
    [
      "expo-speech-recognition",
      {
        "microphonePermission": "Allow $(PRODUCT_NAME) to use the microphone.",
        "speechRecognitionPermission": "Allow $(PRODUCT_NAME) to use speech recognition.",
        "androidSpeechServicePackages": ["com.google.android.googlequicksearchbox"]
      }
    ]
  ],

AH, that took an embarrassing amount of time to notice.
It might be worth adding the "expo-router" to the README show this syntax for additional plugins, as i don't think its terribly intuitive.
Or maybe i'm just slow :).
Thanks!


Expand collapse in NavMenu is not working

Things to check

[X] I have searched the existing issues for this bug
[X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type
Component
Component name
MudNavMenu
What happened?
I'm created a collapsable MudNaveMenu as  per this documentation. https://mudblazor.com/components/MudNavMenu#basic-usage. I'm attaching the same of what I created this also herewith. When I click on collapse icon in menu, it is not working.
MudBlazorWebApp1.zip
Expected behavior
If you execute the attached code then I expect that in clicking on the collapse button the menu should collapse but that is not happening
Reproduction link
https://try.mudblazor.com/snippet/mYcobGPJvsnWQxSs
Reproduction steps

Extract zip file.
2.Execute the server project from visual studio. The browser will open with the application
Click on the collapse icon in menu. It is not working
...

Relevant log output
No response
Version (bug)
8.*
Version (working)
No response
What browsers are you seeing the problem on?
Edge
On which operating systems are you experiencing the issue?
Windows
Pull Request

[X] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Reproduction link
https://try.mudblazor.com/snippet/mYcobGPJvsnWQxSs

I tried your snippet on latest code, it work flawlessly.

MudBlazorWebApp1.zip

You selected a per-page interactive location, which means that only individual pages marked with @rendermode InteractiveWebAssembly will have interactivity.  If you want your root to be interactive and use features like drawers, menus, etc., you need to use the global interactive mode. If you wish to continue with per-page mode, you need to understand what is statically rendered and what is not. In the case of MainLayout, use components that work with pure JS/CSS only, since our components require C# interactivity.

Reproduction link
https://try.mudblazor.com/snippet/mYcobGPJvsnWQxSs

I tried your snippet on latest code, it work flawlessly.

MudBlazorWebApp1.zip

You selected a per-page interactive location, which means that only individual pages marked with @rendermode InteractiveWebAssembly will have interactivity.  If you want your root to be interactive and use features like drawers, menus, etc., you need to use the global interactive mode. If you wish to continue with per-page mode, you need to understand what is statically rendered and what is not. In the case of MainLayout, use components that work with pure JS/CSS only, since our components require C# interactivity.

Hi, It is true that I have selected per-page. So please let me know how I can have this working or alternatively let me know how do I change this to Global interactive mode with pre-rendering as false. If you can modify the above sample and share me then it will be of immense help

The easiest fix would be to just to recreate the project using MudBlazor official templates with sectioning "global" as interactive location.
If you want to use per-page, I can't help you here. You have to figure out it yourself, for example here is the drawer workaround https://github.com/MudBlazor/Templates/issues/478#issuecomment-2425233973, and for nav menu you would also need to do similarly what https://github.com/0phois/MudBlazor.StaticInput does.

I think in that case MudBlazor project template should not give per component/site option itself. Or At least in each control documentation a call out to this has to be made


Add Typist Middleware to Extension Directory

Per pull request #150, @cleemullins mentioned to create a GitHub issue to add some middleware to the wiki.
Link to github repository: https://github.com/RyanDawkins/botframework-typist

Due to the changes released I'm remedying my middleware. I'll reopen once I have fixed it due to the new changes.

Middleware now works with the latest.

@RyanDawkins What text would you like me to add to the Directory?
If you give me a bit of Markdown, I'll add it.

added


fix: Added missing job tag key in hive_sample_dag.py

[FIX]
Summary of Changes
Running "create_table_metadata_databuilder_job()" was giving an Exception :
""ConfigMissingException" : No Configuration setting found for key job_publish_tag."
Hence,
Adding a missing key for job_publish_tag in "create_table_metadata_databuilder_job()" of hive_sample_dag.py.
Tests
Ran the modified function and checked neo4j for the graphs. They were being built.
Documentation
None
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

Codecov Report

Merging #308 into master will decrease coverage by 0.28%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #308      +/-   ##
==========================================
- Coverage   74.30%   74.02%   -0.29%
==========================================
  Files         105      105
  Lines        4492     4492
  Branches      419      396      -23
==========================================
- Hits         3338     3325      -13
- Misses       1049     1053       +4
- Partials      105      114       +9

Impacted Files
Coverage Δ

databuilder/loader/file_system_neo4j_csv_loader.py
83.33% <0.00%> (-5.96%)
:arrow_down:

...ilder/transformer/regex_str_replace_transformer.py
92.85% <0.00%> (-3.58%)
:arrow_down:

...tabuilder/extractor/postgres_metadata_extractor.py
93.54% <0.00%> (-1.62%)
:arrow_down:

...abuilder/extractor/snowflake_metadata_extractor.py
93.75% <0.00%> (-1.57%)
:arrow_down:

databuilder/extractor/mssql_metadata_extractor.py
94.02% <0.00%> (-1.50%)
:arrow_down:

...tor/dashboard/redash/redash_dashboard_extractor.py
91.50% <0.00%> (-0.95%)
:arrow_down:

databuilder/publisher/neo4j_csv_publisher.py
83.49% <0.00%> (-0.95%)
:arrow_down:

databuilder/task/neo4j_staleness_removal_task.py
84.16% <0.00%> (-0.84%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update faa795c...5d7bb79. Read the comment docs.


Fixed edge case for array decoding. Improved benchmarks and tests.

Codecov Report

Merging #256 into master will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #256      +/-   ##
==========================================
+ Coverage   62.14%   62.17%   +0.02%
==========================================
  Files          38       38
  Lines        1284     1285       +1
  Branches        6        8       +2
==========================================
+ Hits          798      799       +1
  Misses        486      486

Impacted Files
Coverage Δ

core/src/main/scala/laserdisc/protocol/RESP.scala
87.30% <100.00%> (+0.10%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3834bb4...1d83c93. Read the comment docs.


Bluetooth enabled failing

I've tried adding this plugin to an iOS app for an iPad (9.3.5) and whenever I run isBlueToothEnabled(), I get back false. I then installed the demo app https://github.com/EddyVerbruggen/nativescript-bluetooth-demo on the same device and am getting that it is not enabled there as well. My bluetooth is definitely enabled and it works as I am able to pair with a device using a different app (not one I developed).

Strange.. it's this line: https://github.com/EddyVerbruggen/nativescript-bluetooth/blob/1907f7643e3f8c781dc68080ca0559db7b1358b5/bluetooth.ios.js#L311
Perhaps you can console.log the actual state on that device?

It's being logged as undefined. Could this be an older iOS version thing?

Hmm, older versions should be better than newer actually, because CBCentralManagerStatePoweredOn seems to be deprecated now.
I'll have to investigate and change the implementation I'm afraid. Perhaps it's best to not rely too much on that method for now..

Ok. I can just have it return true for now and see if that lets me connect

Returning true seemed to allow the rest of the plugin to work normally

This seems to be issue also with latest ios for ipod touch 5th generation. Any idea how this could be fixed? I’m now also returning true always, but that not actual fix.

It would be very useful to know if changing this bit in bluetooth.ios.js:
https://github.com/EddyVerbruggen/nativescript-bluetooth/blob/25ccc7067f22f2fe19a1a241900e24fb9ed5982d/bluetooth.ios.js#L340-L342
to
Bluetooth._isEnabled = function () {
  return Bluetooth._state.manager.state === CBManagerState.PoweredOn;
};

would fix the problem. Can anyone try that perhaps?

Both CBCentralManagerStatePoweredOn and CBManagerStatePoweredOn (without dot) are returning number 5.
The issue is that for one reason Bluetooth._state.manager.state is undefined.

Ah, I see. Could be it's a timing issue. Can you check that method again a few seconds after you checked it the first time?

Same, still undefined.

Hmm if it still works when undefined on your device then I may need to return true when undefined or state equals PoweredOn.. the latter seems to work for most devices, and the former is a fallback. I have no clue how to approach this in any other way.

I think your idea is good. I just tried also with simple cordova app, and I'm getting the same undefined there also.

This change somehow didn't make it into the 1.3.1 release. The function is still:
Bluetooth._isEnabled = function () {
return Bluetooth._state.manager.state === CBCentralManagerStatePoweredOn;
};

@dbenninger You're right. I intended to do that but somehow screwed it up. Will now be part of the soon-to-be-released 2.0.0 version.

Thanks, how soon?

Depends on how much time I can spend in my IDE vs responding to Github issues 😘


[SPARK 6013][ml] Add more Python ML examples for spark.ml

@mengxr @jkbradley , can you please review these examples?

Merged build triggered.

Merged build started.

Test build #33616 has started for   PR 6443 at commit 925ca86.

Test build #33616 has finished for   PR 6443 at commit 925ca86.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33616/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #33617 has started for   PR 6443 at commit 5f9b8c3.

Test build #33617 has finished for   PR 6443 at commit 5f9b8c3.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33617/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #33618 has started for   PR 6443 at commit 121c211.

Test build #33618 has finished for   PR 6443 at commit 121c211.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33618/
Test PASSed.

@harsha2010  Thanks for the examples!  I added comments but haven't tested the examples myself yet.  I'll try them out soon.

Merged build triggered.

Merged build started.

Test build #33710 has started for   PR 6443 at commit 732506e.

@jkbradley , thanks for the review feedback, have incorporated it in the checkin.

Test build #33710 has finished for   PR 6443 at commit 732506e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

LGTM.  I ran these and they worked.  Thanks!
Merging with master and branch-1.4


rxchart-app: Mutate the Medicine.Drug field to trim()

Closed. Moved to https://github.com/RyanNerd/rxchart-app/issues/45


release timeline for upcoming code

Could you please provide an estimated timeline for when the new code will be made available?

Hi! Thank you for your interest in our work. The source code and corresponding dataset will be made public after the paper is accepted (June to July).

Hi, thanks for the good work, but when can we try to launch it? Certain files are missing and the link to the dataset is not working :(


Add MQTT client authentication

Proposed changes
This commit adds 2 new config options: mqtt.client.auth.cert_file and mqtt.client.auth.key_file to facilitate MQTT client authentication. The client certificate needs to be signed by the same CA as the server certificate for the authentication to work, that's why new settings were added instead of using a thin-edge device certificate located in /etc/tedge/device-certs, which is self-signed and adding the option of using CA to tedge cert command will not be trivial.

Note: this PR is the second part of #1785 and requires server authentication to be present, which is why it contains commits from the server authentication PR (#1816). I anticipate #1816 to be merged before this PR which might need some more discussion and fixes, which is why I'm putting it as a draft. When #1816 is merged, the first 2 commits should disappear, leaving this PR with only commits related to client authentication.

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

#1785

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[x] I used cargo clippy as mentioned in CODING_GUIDELINES
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
Some more thought needs to be put into how to integrate client authentication with device certificates generated by the tedge cert create command. The certificates generated by the command are currently self-signed, but for client authentication to work, both server and client need to use certificates signed by the same CA. A CA certificate is usually located on another device, to which the subject sends a CSR and receives back a signed certificate. So unless we want to keep it as it is now, where we use a certificate different from thin-edge device certificate, and which needs to be deployed by the user manually, the tedge cert command would have to be heavily modified.

The client certificate needs to be signed by the same CA as the server certificate for the authentication to work,

There is a misunderstanding here. This would be a too strong constraint. See mosquitto documentation: This means that any CA certificates you include in cafile or capath will be able to issue client certificates that are valid for connecting to your broker.
It means that to accept connections from some client, one must add in the mosquitto capath directory the signing certificate of this client certificate. Note that (still according mosquitto documentation):
     For capath to work correctly,
     the certificates files must have ".pem" as the file ending
     and you must run "openssl rehash <path to capath>" each time you add/remove a certificate.

that's why new settings were added instead of using a thin-edge device certificate located in /etc/tedge/device-certs,

These two settings are required but for another reason. One needs to use different certificates and signing authority to authenticate the device in the cloud and to authenticate a local process or child-device.

There is a misunderstanding here. This would be a too strong constraint. See mosquitto documentation: This means that any CA certificates you include in cafile or capath will be able to issue client certificates that are valid for connecting to your broker.
It means that to accept connections from some client, one must add in the mosquitto capath directory the signing certificate of this client certificate. Note that (still according mosquitto documentation):

You're right, CAs trusted by the broker and the clients can actually be different.

These two settings are required but for another reason. One needs to use different certificates and signing authority to authenticate the device in the cloud and to authenticate a local process or child-device.

Okay, then tedge cert create is probably not relevant. What prompted me to ask about it was that we have quite a lot of configuration options and I'm not sure whether or not I'm needlessly duplicating them instead of using some other options. E.g. for root trust store, e.g. I wondered instead of adding a key in mqtt.client, paths to trusted certificates should not be global, with some ability to override, e.g. with an options to add more paths or certificates in certain contexts, like HTTP or MQTT.

Okay, then tedge cert create is probably not relevant. What prompted me to ask about it was that we have quite a lot of configuration options and I'm not sure whether or not I'm needlessly duplicating them instead of using some other options. E.g. for root trust store, e.g. I wondered instead of adding a key in mqtt.client, paths to trusted certificates should not be global, with some ability to override, e.g. with an options to add more paths or certificates in certain contexts, like HTTP or MQTT.

Indeed, we start to have quite a lot of MQTT related options !
$ tedge config list --all | grep mqtt
mqtt.bind_address=<IP_ADDRESS>
mqtt.client.host=localhost
mqtt.client.port=1883
mqtt.port=1883
mqtt.client.ca_file=
mqtt.client.ca_path=
mqtt.client.auth.cert_file=
mqtt.client.auth.key_file=
mqtt.external.port=
mqtt.external.bind_address=
mqtt.external.bind_interface=
mqtt.external.capath=
mqtt.external.certfile=
mqtt.external.keyfile=

The two added by this PR make sense and are related to the former ones

mqtt.external.* are used to configure a listener on mosquitto.
mqtt.external.port and mqtt.client.port should be the same for the client to connect that listener. Same for the addresses.
mqtt.external.capath is where to put the signing certificate of a device certificate mqtt.client.auth.cert_file.
mqtt.client.ca_path must contains a copy of the mqtt.external.certfile.

The more issue is more that tedge_conf.toml is mixing unrelated things: configuring mosquitto, configuring the tedge daemons and configuring tedge clients.
PS: Writing this comment, I noticed that something needs to be fixed: the client and external settings use the same names except an extra underscore (capath vs ca_path). @reubenmiller : what's your preference?

One point is missing though: this needs to be added to mqtt_channel too and used by the misc tedge daemons.

I think there's one issue with mqtt_channel as it is now. Because it itself does not read thin-edge configuration, and uses a config builder, every extension using it has to read configuration and set common options, like hostname, port, or certificate paths. If I'm somewhat correct in thinking that mqtt_channel is supposed to be an abstraction which is supposed to be used by plugins to connect to thin-edge local broker and reduce some boilerplate resulting from all our plugins being MQTT clients, then it's not performing its task very well because when we add something that changes the behaviour of the broker, all the clients using mqtt_channel have to be updated as well.
I think that instead of starting with Config::default(), which does not take config into account, we should provide a function that reads the thin-edge configuration and constructs Config from it. We could then allow plugins to override any fields they want, although It's not clear to me why they would even want to do so. All the information needed to connect to the broker is inside the config file, so I think there's no advantages to forcing clients to handle, or even be aware, of the transport protocol that is being used.
For the time being, I'll take the long road and just update all usages adding server and client authentication (in server authentication PR i updated mqtt_channel, but forgot to update usages). Please tell me if I'm understanding something wrong and whether or not the kind of changes that I propose above is something worth considering.

In a48bdbc, I did a first try in extracting common MQTT configuration options into one place. Made it just another impl function, because only a part of the configuration is extracted, and it involves calling builder methods on mqtt_channel::Config, so I think From wouldn't be the best fit. Made it in another module because it introduced a dependency on mqtt_channel in tedge_config so we can perhaps gate this module behind a feature flag if necessary.
Still, I'm not really satisfied with this, because by generating MQTT config from tedge config, now we need to pass &TEdgeConfig everywhere where we previously only needed host and port. This is particularly annoying in tests, and because constructing TEdgeConfig from scratch would be very painful, and because parsing configuration file in tests sounds like a bad idea, I've made it optional in some parts so it could be None in unit tests, but it's not supposed to be permanent. Now I'd like to try and run some tests that make use of all the affected components, and after I've confirmed that it works, I'll try to fix this "how to pass config" issue. My best guess would be to group host, port and tls into one object, but that would introduce nesting to mqtt_channel's config builder which might be a bit awkward to use.

In a48bdbc,

This link is broken.

I did a first try in extracting common MQTT configuration options into one place. Made it just another impl function, because only a part of the configuration is extracted, and it involves calling builder methods on mqtt_channel::Config, so I think From wouldn't be the best fit. Made it in another module because it introduced a dependency on mqtt_channel in tedge_config so we can perhaps gate this module behind a feature flag if necessary.

The function TEdgeConfig::mqtt_config() seems perfect.  Adding a feature flag might be not necessary as of today all the components have an MQTT dependency.

Still, I'm not really satisfied with this, because by generating MQTT config from tedge config, now we need to pass &TEdgeConfig everywhere where we previously only needed host and port. This is particularly annoying in tests, and because constructing TEdgeConfig from scratch would be very painful, and because parsing configuration file in tests sounds like a bad idea, I've made it optional in some parts so it could be None in unit tests, but it's not supposed to be permanent. Now I'd like to try and run some tests that make use of all the affected components, and after I've confirmed that it works, I'll try to fix this "how to pass config" issue. My best guess would be to group host, port and tls into one object, but that would introduce nesting to mqtt_channel's config builder which might be a bit awkward to use.

Here, there is something I don't understand. Why &TEdgeConfig  is now required where only  host and port were previously needed? Why not replace  host and port  parameters by an mqtt_channel::Config and let the caller use TEdgeConfig::mqtt_config() if required?
I agree that constructing TEdgeConfig from scratch is very painful but I would really avoid to make config parameter optional to ease testing. Test helpers can be added in tedge_test_utils.
Also keep in mind that  TEdgeConfig is under refactoring, and that it would be then feasible to write tests helpers as TEdgeConfig::default().with_client_mqtt_port(1234).

I realised that I haven't updated any markdown documentation, but it would probably be good to inform users about this new functionality there. As such, one more commit with documentation will likely be coming.

Added fixups addressing review comments.
Also renamed mqtt.client.ca_file/dir to mqtt.client.auth.cafile/dir so options related to authentication are all grouped together.

Thank you for the fixups.
Please, rebase and squash the fixup commits. And I will merge this PR.

@didier-wenzek squashed

@didier-wenzek squashed

Unfortunately, two system tests are failing on a certificate issue.
Cargo audit, is also failing: did you rebase once your fix merged?

Cargo audit is also failing: did you rebase once your fix merged?
My bad, forgot to rebase, will fix


Custom attribute handling

Didn't know if you would mind a PR, but this change addresses #1

did you test this with and without the rel attribute?

Yes, it still passes all of the unit tests, and I tested manually with and without the rel attribute

Note this is very Vanilla Quotes -> NodeBB syntax specific. NodeBB specific in the fact that it prepends an @ symbol and appends  said:

ok published
<EMAIL_ADDRESS>and
<EMAIL_ADDRESS>which now uses the latest html-md-optional_window

im taking your word for it :P

thanks!


add example client with connection error handling

What are your thoughts on updating the example to use some of the new 'setup' event stuff?
It was intended to make client initialization easier. (And should be documented before 0.8 is cut)

use some of the new 'setup' event stuff

I don't know much about this. My app was throwing exceptions when it couldn't connect to the LDAP server so I blundered about until I found where to add those event handlers for connection errors.

It doesn't help that I haven't written docs for it yet.
Here's a short example of using the setup event to bind:
https://github.com/joyent/node-ufds/blob/c7aa5635871aad7a630c897be2fcf059fed2e9dd/lib/index.js#L439-L455
ldapjs will run the 'setup' handlers sequentially after establishing a TCP connection but before emitting 'connect' to the client consumer.  The idea is to simplify event handling in the face of connect/reconnect scenarios.

Mmm, that does look like a much nicer interface.

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


The interactive lesson layout on mobile is a bit weird

The chapter name is first, while the Back and Show solution buttons are second, making them hard to access.

This can be fixed using themes. Closing.


[BUG]: Cannot use gradio.live link from colab notebook as Local AI Base URL or LMStudio Base URL

How are you running AnythingLLM?
AnythingLLM desktop app
What happened?
usually when I run program that depends on Local AI i can simply put in my gradio.live link which comes from my google colab notebook which is hosting mistral 7b v.2 and it will act as if I am running it locally. However I get an error that my link must contain a "/v1" I have never experienced anything like this before on other applications. This is my first time using anything LLM and I am trying to avoid having to run mistral 7b on my PC locally and would prefer to run it through my google colab.
Are there known steps to reproduce?
No response

If you are using LocalAI, the endpoint for inferencing with LocalAI API requires /v1 because it uses the OpenAI format to communicate - which is what AnythingLLM uses. Is there an API endpoint you can use on Gradio to generate a response? Because if using LocalAI this would still require the /v1 since that is just how LocalAI works for its API.


No implementation found for method placemarkFromCoordinates on channel flutter.baseflow.com/geocoding

Hi there, trying to get the place from coordinates but getting this error:
No implementation found for method placemarkFromCoordinates on channel flutter.baseflow.com/geocoding
Have done other steps on the https://pub.dev/packages/geocoding page.

I cannot reproduce this problem. One thing you can try is make sure to clear your cache by running flutter clean. If this doesn't help please provide the following information:

Which version of the plugin are you using?
Which platform are you testing on (Android or iOS)?
Can you provide some example code on how you are calling the plugin?

Hi there, I managed to resolve, thank you. It was just a case of restarting the app.
Regards
Robyn King
+27 79 517 4125

On 21 Sep 2020, at 14:42, Maurits van Beusekom<EMAIL_ADDRESS>wrote:

I cannot reproduce this problem. One thing you can try is make sure to clear your cache by running flutter clean. If this doesn't help please provide the following information:
Which version of the plugin are you using?
Which platform are you testing on (Android or iOS)?
Can you provide some example code on how you are calling the plugin?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

This occurs when i'm using this package in flutter web, to read the result of camera updated position.

@Puspharaj the geocoding plugin doesn't have support for the web platform. At the moment only Android and iOS are supported.

The geocoding plugin does not work for the web platform .


Internal Server Error

Hello,
I'm getting the following error when my app is redirected to the keycloak login page:
 ERROR [org.keycloak.forms.login.freemarker.FreeMarkerLoginFormsProvider] (executor-thread-1) Failed to process template: org.keycloak.theme.FreeMarkerException: Failed to process template login.ftl
It makes the app crash.
I'm on keycloak 24.0.3, using keycloakify ^9.3.1.
This is happening when i'm using my custom theme.
If I pick another theme from the keycloak admin console for my app (ex. the base keycloak theme, without keycloakify customization), the error is gone ...
Can anyone help ?
Thank you in advance,
Pietro

Hello @PietroFalcetti,
I'm very sorry you are experiencing this issue.
It's due to the fact that you're still using Keycloakify 9.
Despite the fact that keycloakify 10 is still il release candidate (because I didn't fully complete the documentation and the migration guide from v9 to v10) the v10 of keycloakify is the only one that supports the latest versions of Keycloak.
v10 is production ready you can go ahead and implement it.
Here is the starter for it:
https://github.com/keycloakify/keycloakify-starter
And here is the documentation:
https://docs.keycloakify.dev/
If you have any aditional question you're welcome to join our discord server:
https://discord.gg/kYFZG7fQmn


chore(release): v1.1.2 🎉

:robot: I have created a release *beep* *boop*
1.1.2 (2021-11-09)
Bug Fixes

run: ensure that static assets are included in published pkg (9938ba7)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/uladkasach/simple-artifact-builder/releases/tag/v1.1.2 :sunflower:


MB-8094 Zeplin Connected Components

Description
This branch installs the Zeplin Command Line Tools (Zeplin CLI), and Zeplin's CLI Connect Storybook plugin. It sets up a .zeplin directory in the repo, which contains the components.json file that links our storybook components to their Sketch symbol/ zeplin component counterparts. The goal of this branch is to increase visibility of Storybook components and make it easier for engineers to find the things they need, especially as our design system grows and expands.
This branch sets up many of the things found in our C O M P O N E N T S section on Storybook. We (design) plan to add the remaining, more specific components, incrementally as new deliverables are created.
Reviewer Notes
I will need to introduce documentation about how this works so not I only hold the keys on this!
Components with tickets currently not included, because not in Storybook

Brand assets
Callout, Tooltip

Components to be connected that are in Storybook:

Contact Info

Setup
visit our Zeplin Styleguide (ping me if you want view access and don't have it!), and try out clicking on some of the Storybook links you see! they can be found in the right sidebar.

Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
Zeplin CLI docs
Zeplin CLI Storybook Plugin Docs
Zeplin - MilMove Design System

Screenshots

Warnings

:warning:

It looks like you updated the Cypress package dependency in one of two required places.
Please update it in both the root package.json and the cirlcleci-docker/milmove-cypress/ folder's separate package.json

Messages

:book:
:link: MB-8094

  Generated by :no_entry_sign: dangerJS against 90610f03407576cfd3e0cd6ffce31214660d8636


First Android app: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-first-app?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-1-pathway-2%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-first-app#1
In which task and step of the codelab can this issue be found?
Task 2: Create a project using the template
Step 9: Click Split on the top right of Android Studio, this allows you to view both code and design. You can also click Code to view code only or click Design to view design only.
Describe the problem
The "Split" button isn't where the tutorial says it should be.
Steps to reproduce?
Just follow the tutorial.
Versions
Android Studio version: I have no idea, look at the date of this bug report, look at the current studio version for that date, and figure it out yourself.
  I literally downloaded the IDE ten minutes ago, I can't get through the tutorial without running into problems, and now you want to know what API version I'm using?  Yesus Freaking Cristos
Additional information
Include screenshots if they would be useful in clarifying the problem.

Hi @dcrookston
Thank you for writing in.
Attached is a screenshot of Android Studio Jellyfish (the latest stable version) showing the "Split" button in the top right corner.

If you are still having issues, please create a new GitHub issue with the requested information so we can help you further.
Hope you are enjoying the course!
Regards.


can't start after it opens

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[ ] My answer given in the checkbox above is a lie.

What problem did you encounter?

Can you send the log file please?


make import doens't working

Hi,
I have recntly intalled CARLA 0.9.11 in a new computer. I'm trying to import a map that i have created in RoadRunner.
Unfortunalley by "make import ARGS="--package <package_name> --no-carla-materials" the package in Content folder aren't being created and no .json file appears in the Import folder. And i'm getting no error in Terminal:
`make import ARGS="--package EuroNCAP_map --no-carla-materials"
-[Setup]: [Batch params]: --boost-toolset msvc-14.1
-[Setup]: Asynchronous jobs:  16
-[Setup]: Boost toolset:      msvc-14.1
-[Setup]: Install directory:  "C:\Users\z239023\carla\Build"
-[Setup]: Installing zlib...
-[install_zlib]: [Batch params]: --build-dir "C:\Users\Username\carla\Build"
-[install_zlib]: A zlib installation already exists.
-[install_zlib]: Delete "C:\Users\Username\carla\Build\zlib-install" if you want to force a rebuild.
-[install_zlib]: Exiting...
-[Setup]: Installing libpng...
-[install_libpng]: [Batch params]: --build-dir "C:\Users\Username\carla\Build" --zlib-install-dir "C:\Users\z239023\carla\Build\zlib-install"
-[install_libpng]: A libpng installation already exists.
-[install_libpng]: Delete "C:\Users\Username\carla\Build\libpng-1.2.37-install" if you want to force a rebuild.
-[install_libpng]: Exiting...
-[Setup]: Installing rpclib...
-[install_rpclib]: [Batch params]: --build-dir "C:\Users\Username\carla\Build"
-[install_rpclib]: A rpclib installation already exists.
-[install_rpclib]: Delete "C:\Users\Username\carla\Build\rpclib-install" if you want to force a rebuild.
-[install_rpclib]: Exiting...
-[Setup]: Installing Google Test...
-[install_gtest]: [Batch params]: --build-dir "C:\Users\Username\carla\Build"
-[install_gtest]: A Google Test installation already exists.
-[install_gtest]: Delete "C:\Users\Username\carla\Build\gtest-install" if you want to force a rebuild.
-[install_gtest]: Exiting...
-[Setup]: Installing "Recast & Detour"...
-[install_recast]: [Batch params]: --build-dir "C:\Users\Username\carla\Build"
-[install_recast]: A "Recast & Detour" installation already exists.
-[install_recast]: Delete "C:\Users\Username\carla\Build\recast-cdce4e-install" if you want to force a rebuild.
-[install_recast]: Exiting...
-[Setup]: Installing Boost...
-[install_boost]: [Batch params]: --build-dir "C:\Users\Username\carla\Build" --toolset msvc-14.1 --version 1.72.0 -j 16
-[install_boost]: A Boost installation already exists.
-[install_boost]: Delete "C:\Users\Username\carla\Build\boost-1.72.0-install" if you want to force a rebuild.
-[install_boost]: Exiting...
1 Datei(en) kopiert.
1 Datei(en) kopiert.
-[Setup]: Installing Xercesc...
-[install_xercesc]: [Batch params]: --build-dir "C:\Users\Username\carla\Build"
-[install_xercesc]: A xerces installation already exists.
-[install_xercesc]: Delete "C:\Users\z239023\carla\Build\xerces-c-3.2.3-install" if you want to force a rebuild.
-[install_xercesc]: Exiting...
-[Setup]: Creating "CMakeLists.txt.in"...
-[Setup]:
###########
SUCCESS
###########
IMPORTANT!
All the CARLA library dependences should be installed now.
(You can remove all "*-src" folders in C:\Users\Username\carla\Build\ directory)
You only need the ASSET PACK with all the meshes and textures.
This script provides the assets for CARLA 0.9.11:
You can download the assets from here:
   http://carla-assets.s3.amazonaws.com/20201222_232b876.tar.gz

Unzip it in the "C:\Users\Username\carla\Unreal\CarlaUE4\Content\Carla" folder.
If you want another version, search it in C:\Users\Username\carla\Util\ContentVersions.txt.
-[BuildLibCarla]: [Batch params]: --server
-- Selecting Windows SDK version 10.0.17763.0 to target Windows 10.0.19042.
-- Build debug:   ON
-- Build release: ON
-- Build test:    ON
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Users/Username/carla/Build/libcarla-visualstudio
Microsoft (R)-Build-Engine, Version 15.9.21+g9802d43bc3 für .NET Framework
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
carla_server.vcxproj -> C:\Users\Username\carla\Build\libcarla-visualstudio\LibCarla\cmake\server\Release\carla_server.lib
carla_server_debug.vcxproj -> C:\Users\Username\carla\Build\libcarla-visualstudio\LibCarla\cmake\server\Release\carla_server_debug.lib
-- Install configuration: "Release"
-[BuildLibCarla]: LibCarla server has been successfully installed in "C:\Users\Username\carla\Unreal\CarlaUE4\Plugins\Carla\CarlaDependencies"!`
Have anyone any idea what is the problem here?
Thanks

unluckily, i have the same problem, don't know hwo to deal with it


Question about the use of "leading-" with plugin

Hey David,
First of all thank you so much for this plugin!
It seems like I cannot do the following:
className="leading-snug text-base"

The leading does not seems to change anything about the fluid text. My question is, is this intended? if so, is there a work-around to this issue?

Hey @solojungle
thank you!
If you use the default config there is a line-height for each fluid step defined. You've to remove this like here:
https://play.tailwindcss.com/vCYxBuNAqR
module.exports = {
  mode: 'jit',
  theme: {},
  variants: {},
  corePlugins: {},
  plugins: [
        require('tailwindcss-fluid-type')({
            // your fluid type settings
            // works only with unitless numbers
            // This numbers are the defaults settings
            settings: {
                fontSizeMin: 1.125, // 1.125rem === 18px
                fontSizeMax: 1.25, // 1.25rem === 20px
                ratioMin: 1.125, // Multiplicator Min
                ratioMax: 1.2, // Multiplicator Max
                screenMin: 20, // 20rem === 320px
                screenMax: 96, // 96rem === 1536px
                unit: 'rem', // default is rem but it's also possible to use 'px'
                prefix: '' // set a prefix to use it alongside the default font sizes
            },
            // Creates the text-xx classes
            // This are the default settings and analog to the tailwindcss defaults
            // Each `lineHeight` is set unitless and we think that's the way to go especially in context with fluid type.
            values: {
                'xs': -2,
                'sm': -1,
                'base': 0,
                'lg': 1,
                'xl': 2,
                '2xl': 3,
                '3xl': 4,
                '4xl': 5,
                '5xl': 6,
                '6xl': 7,
                '7xl': 8,
                '8xl': 9,
                '9xl': 10,
            },
        }),
    ],
}

Or when you use TailwindCSS 3.3 you can the new shorthand like this:
https://play.tailwindcss.com/Z8fAiDOUG4

The quick brown fox jumps over the lazy dogs

text-9xl/snug :) It's explained here: https://tailwindcss.com/blog/tailwindcss-v3-3#new-line-height-shorthand-for-font-size-utilities
Or... you use important like this: className="!leading-snug text-base"
but I think solution 1 or 2 is a better approach.
Hope that helps!

David thank you so much for the response. These are some great suggestions, really appreciate it!

Hey David,
First of all I really like this plugin. Consequently, I have found myself in this situation several times.
In the past, I have always chosen the solution approach via important.
After coming across this issue, I would prefer approach 2 via the shorthand. It would be a much cleaner solution to the problem. However, the plugin does not support the shorthand.
As you can also see in your Playground, only the tailwind default plugin is executed there. Accordingly, the font size does not change between different screen sizes.
The generated CSS with the shorthand:

The generated CSS without the shorthand:

As you can see, it does not work as you would expect.
Would it be possible to support it?

Ah, here was the comment :D
I'm a bit busy this week. I'll look into that, but I'm not sure if that's possible.


Using a service account via the CLI requires log api keys

Frodo CLI version
0.24.5
Describe the issue
I've just wasted a few hours with this command:
# assume the variables are set correctly
conn add --sa-id $FR_SVC_ACC_ID --sa-jwk-file service.jwk $FR_TENANT

The error I get is Incomplete or no credentials!
However, after examining the code and taking a wild guess at what's going wrong, I realised that if I provided the log api keys, even if they didn't work, the bit of the code which adds existing service accounts would execute:
conn add --sa-id $FR_SVC_ACC_ID --sa-jwk-file service.jwk --log-api-key IGNORE --log-api-secret IGNORE $FR_TENANT

While it might be reasonable to think that I should have added the --no-log-api switch instead, that doesn't work.
It's all down to this code here:
https://github.com/rockcarver/frodo-cli/blob/main/src/cli/conn/conn-save.ts#L80
This seems to require us to provide a log api key and secret, no matter what we do. Yet the addExistingServiceAccount piece is independent of the logs API.
As a minimum, the documentation for the CLI should offer a lot more help on how to use this, but overall, I think there's some confusion in the code.

This works better, now, @ashleyfrieze. I'm still not happy with all the silent magic the frodo conn save command performs but I believe your use case is now handled properly. Eventually we might have to add a whole set of connection profile management sub-commands to allow the setting of individual options/values.


Add additional WWLLN test

Description:
Per @MartinHjelmare's suggestion, this PR adds another test to ensure the WWLLN integration starts up with an existing config flow. In so doing, it adjusts when the integration saves objects to hass.data; this won't affect anything operational – it is merely a change to help this test.
Related issue (if applicable): N/A
Pull request with documentation for home-assistant.io (if applicable): N/A
Example entry for configuration.yaml (if applicable):

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist

I was thinking we should test setting up the component with async_setup_component and have that import a config entry. That way we really test the config values the whole flow to entry creation.


[Contract Interaction] Support Hex Encoded Payload

closes #959

Travis automatic deployment:
https://pr1038--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1038--safereact.review.gnosisdev.com/app

The Custom contract works for me.
Tested using a data that transfers 3 tokens to an account
Data:
0xa9059cbb00000000000000000000000061a0c717d18232711bc788f19c9cd56a43cc887200000000000000000000000000000000000000000000000029a2241af62c0000
DAI token for rinkeby:
0x5592EC0cfb4dbc12D3aB100b257153436a1f0FEa
Note:
Not convinced with the position of the toggle button. I think it should be at the top

@lukasschor thoughts?

The Custom contract works for me.
Tested using a data that transfers 3 tokens to an account
Data:
0xa9059cbb00000000000000000000000061a0c717d18232711bc788f19c9cd56a43cc887200000000000000000000000000000000000000000000000029a2241af62c0000
DAI token for rinkeby:
0x5592EC0cfb4dbc12D3aB100b257153436a1f0FEa
Note:
Not convinced with the position of the toggle button. I think it should be at the top

@lukasschor thoughts?

I think it's fine as it is. If users will be confused, we can always place it somewhere else later. It also preserves the data while switching to custom data, so if you have already selected method and parameters, it will automatically encode them when toggling the switch, which is useful when interacting with proxy contracts.

Travis automatic deployment:
https://pr1038--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1038--safereact.review.gnosisdev.com/app

@fernandomg

Typings are important, but this whole SendForm section feels like really needs a refactor.
The functionality added back worked fine in previous releases.

could you please create ticket for that in this case? so we're keeping track of tech debt

@fernandomg

Typings are important, but this whole SendForm section feels like really needs a refactor.
The functionality added back worked fine in previous releases.

could you please create ticket for that in this case? so we're keeping track of tech debt

sure, I'll do it right away

Travis automatic deployment:
https://pr1038--safereact.review.gnosisdev.com/app


Can't plot in polar projections

Dear Andrew,
first of all many thanks for this nice module!
I am trying to use it in IPython notebook, and experience problems with plotting polar projections. It seems like proj='npstere' in mapset does not have any effect...
Here is an example (I use NCEP reanalysis data)
http://nbviewer.ipython.org/gist/koldunovn/6eeaaf5b4741fefc14f1

Dear koldunovn,
I'm really sorry I haven't replied earlier - I've just seen your issue as it's the first one.
I've just tested your code with the latest cfplot (1.7.3) and it looks fine and produces a polar plot as expected.  Could you try again with the new cfplot and let me know how you get on?
Regards
Andy


NPM vs. YARN: the former currently breaks shared-js build, missing URI.js dependency in node_modules / package-lock.json

See:
https://groups.google.com/forum/#!topic/readium-dev/Q39SRBLFoI0

CC @JCCR

Explanation: Yarn was somewhat behaving differently than NPM when fetching default / implicit branches of GitHub dependencies. Now all references are explicit in ReadiumJS, and the build works again. Problem closed.

Also useful to analyse the tree of dependencies and update the package.json ^a.b.c versions accordingly:
https://david-dm.org/readium/readium-js-viewer
https://david-dm.org/readium/readium-js
https://david-dm.org/readium/readium-shared-js
https://david-dm.org/readium/readium-cif-js


[vcpkg] Add fixed changelog generator.

This PR is a continuation of https://github.com/microsoft/vcpkg/pull/15271 except fixed to be actually functional. The "structure" of the script and most implementation credit go to @grdowns , although I fixed a ton of problems in trying to actually make it functional again.
In addition to what was discussed in that pr, I made these changes:
84: Pass StartDate and EndDate to Get-MergedPullRequests instead of special casing only Credentials
109+130: Fix calculating negative progress caused by seeing PRs in the future because GitHub returns times in UTC
268: Actually make filtering for infrastructure PRs functional
303: Fix extraction of port-version from vcpkg.json. This really should be handled by diffing baseline.json in the future.
374-382: Fix expression ordering and casting problem which prevented non-CONTROL ports from ever being considered "new"
Also skip emitting headers for empty blocks, update and sort current triplet list, and move infrastructure bits below
port modifications.
Example output:
vcpkg (2022.02.19 - 2022.02.22)
Total port count:
Total port count per triplet (tested):

triplet
ports available

x86-windows
NUM

x64-windows
NUM

x64-windows-static
NUM

x64-windows-static-md
NUM

x64-uwp
NUM

arm64-windows
NUM

arm-uwp
NUM

x64-osx
NUM

x64-linux
NUM

The following 2 ports have been added:

port
version

libcurl-simple-https
2022-02-14

triton
0.9

The following 18 ports have been updated:

polyhook2 2022-02-06#0 -> 2022-02-21#0

(#23203) [polyhook2] Update to latest (2022-02-21) (by @acidicoala)

graphviz 2.49.1#1 -> 2.49.1#2

(#23148) [graphviz] Fix tools (by @Ace314159)

itk 5.1.0#7 -> 5.2.1#0

(#23158) [ITK] update to v5.2.1 (by @Adela0814)

qhull 8.0.2#2 -> 8.0.2#3

(#23129) [qhull] Fix copyright, pc files, cmake usage (by @dg0yt)

tgui 2021-04-19#2 -> 2021-04-19#3

(#23211) [tgui] fix absolute paths (by @autoantwort)

json-dto 0.3.0#0 -> 0.3.1#0

(#23224) [json-dto] Update to 0.3.1 (by @eao197)

leveldb 1.22#4 -> 1.22#5

(#23180) [leveldb] Fix homepage (by @MarcoFalke)

openxr-loader 1.0.22#0 -> 1.0.22#1

(#23191) [openxr-loader] Fix build failure in world rebuild CI. (by @Hoikas)

ngspice 35#1 -> 35#2

(#23151) [ngspice] Fix error C2065 (by @Cheney-W)

openmvg 2.0#1 -> 2.0#2

(#23114) [cereal] Update to 1.3.1 (by @mapret)

lazy-importer 2021-10-23#0 -> 2022-02-09#0

(#23192) [lazy-importer] Update to 2022-02-09 (by @Thomas1664)

gstreamer 1.19.2#3 -> 1.19.2#4

(#23125) [gstreamer] Support arm-windows and add features (by @JackBoosY)

charls 2.2.0#2 -> 2.3.4#0

(#23189) [charls] Update to 2.3.4 (by @Thomas1664)

arrow 7.0.0#0 -> 7.0.0#1

(#23188) [arrow] add plasma support for non Windows platforms (by @fran6co)

trantor 1.5.4#0 -> 1.5.5#0

(#23182) [trantor] Update to 1.5.5 (by @an-tao)

capstone 4.0.2#2 -> 4.0.2#3

(#23122) [capstone] Use static runtime if capstone wants to be statically linked (by @illera88)

gainput 1.0.0#4 -> 1.0.0#5

(#23219) [gainput] Support Linux (by @JackBoosY)

cereal 1.3.0#1 -> 1.3.1#0

(#23114) [cereal] Update to 1.3.1 (by @mapret)

The following additional changes have been made to vcpkg's infrastructure:

(#23045) [vcpkg docs] Update ko_KR translation (by @jnooree)
(#23181) [vcpkg doc] Fixes typo in vcpkg_download_distfile.cmake (by @acd1034)

-- vcpkg team<EMAIL_ADDRESS>Thu, 24 February 00:29:57 -0800

I merged this on grounds of being effectively the status quo and welcome further improvements in subsequent PRs. (I want to mint releases :) )


user-docs: Trim mute-a-topic.md.

@rishig

Merged with a few changes, thanks @Lyla-Fischer! I dropped the down-chevron change, since probably we should just get rid of that macro.


build(deps): update to Angular v17.3.x

build(deps): update to Angular v17.3.x
build: update Renovate config with v17.3.x compats

#335  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @davidlj95 and the rest of your teammates on  Graphite