Mark HBase RPMs as noarch

I've poked around in the HBase repo and could not find any instance where native code is compiled as part of the HBase build process. I've poked around in /usr/lib/hbase on one of our RegionServers, and could not find any native code installed directly into the filesystem.
I did find a number of dependency JARs that provide native libraries inside them. All of these except one provide numerous builds so they work on a variety of architectures. The one exception is the brotli4j library, which only offers native support for x86-64, at least as our build process packages it. We could potentially change our build process to package more brotli JARs to close this gap. I don't believe Hubspot uses the related feature anyways.
I've tested running HBase out of this RPM on my personal cluster and it seems normal. I don't yet have the ability to set up an arm64 RegionServer to see how it behaves there.

I have not read all of these, but there are a number of HBase JIRAs related to aarch64 and arm64. Here's the aarch64 link: https://issues.apache.org/jira/browse/HBASE-19547?jql=project %3D HBASE AND text ~ aarch64. Just change the last keyword to arm64 to see those.
We should go over those closely for anything that might influence our RPM or install process. I see something related to netty epoll for example, which could be a big issue if it didn't perform well (but again did not read any of it closely).

Alright let's go through these:

HBASE-25170	supporting hbase on aarch64 platform

Claims that leveldbjni dependency contains native code without aarch64 support. I ran unzip -l leveldbjni-all-1.8.jar to see for myself. The relevant lines are    0  10-17-2013 09:18   META-INF/native/
    0  10-17-2013 09:18   META-INF/native/linux32/

699040  10-16-2013 10:01   META-INF/native/linux32/libleveldbjni.so
0  10-17-2013 09:18   META-INF/native/linux64/
752803  10-16-2013 09:53   META-INF/native/linux64/libleveldbjni.so
0  10-17-2013 09:18   META-INF/native/osx/
480504  10-16-2013 12:31   META-INF/native/osx/libleveldbjni.jnilib
0  10-17-2013 09:18   META-INF/native/windows32/
225792  10-17-2013 08:53   META-INF/native/windows32/leveldbjni.dll
0  10-17-2013 09:18   META-INF/native/windows64/
267264  10-17-2013 09:14   META-INF/native/windows64/leveldbjni.dllI guess I missed this on my earlier search because it doesn't even use "x86" in the file names. If I take "linux64" to mean x86-64 then this could be an issue. More comments below.

HBASE-19547	HBase fails building on AArch64 due to asciidoctor-maven-plugin.

Fixed, and we're not necessarily concerned with build problems

HBASE-24266	Document of Hbase on Aarch64

Documentation only, and not interesting at that

HBASE-26602	[aarch64] TestAsyncNonMetaRegionLocator is flaky

cannot reproduce, and affects test only

HBASE-24178	some tests of org.apache.hadoop.hbase.TestZooKeeper.* failed on aarch64

just affects unit tests

HBASE-26600	[branch-2, create-release] Private per build Maven caches won't work on aarch64 MacOS

build issue, not important

HBASE-27113	add Netty epoll support for aarch64

could be significant

HBASE-25565	test fails on AArch64, Fedora 33, but build worked

just affects unit tests

HBASE-19146	Hbase3.0  protobuf-maven-plugin do not support Arm64(only for x86)

not relevant to 2.x

HBASE-26563	TestCacheOnWrite and TestCompactingToCellFlatMapMemStore use too many file descriptors

just affects unit tests, and unclear if this is an aarch64 specific-issue at all anyways

HBASE-26761	TestMobStoreScanner (testGetMassive) can OOME

fixed, and wasn't aarch64-specific

HBASE-26492	[branch-2, hbase-thirdparty, Java 8] TestUnloadAccessController and other unit tests fail to start due to ByteBuffer link error

fixed, and wasn't aarch64-specific

HBASE-27103	All MR UTs are broken because of ClassNotFound

fixed

HBASE-27065	Build against Hadoop 3.3.3

More of leveldbjndi issue, see my comments below

HBASE-27054	TestStochasticLoadBalancerRegionReplicaLargeCluster.testRegionReplicasOnLargeCluster is flaky

Not aarch64-specific

HBASE-26844	Fix flaky TestBasicWALEntryStreamFSHLog.testSizeOfLogQueue

only affects tests

HBASE-26983	Upgrade JRuby to <IP_ADDRESS>

Claims that hbase shell doesn't work on aarch64 unless you get the new JRuby. This ticket is resolved but not in 2.5.x, so we might really have a problem here.

HBASE-27101	support commons-crypto version 1.1.0

fixed in 2.5.0

HBASE-22792	using ASYNC_WAL in hbase sequentialWrite, but RS crashes

Not likely an architecture-specific issue

HBASE-20459	Majority of scan CPU time in HBase-1 spent in size estimation

Not likely an architecture-specific issue

HBASE-27106	HBase site generation should use its own JRuby

Does not affect 2.x

HBASE-19387	HBase-spark snappy.SnappyError on Arm64

Only affects hbase-spark module

HBASE-27075	TestUpdateRSGroupConfiguration.testCustomOnlineConfigChangeInRSGroup is flaky

Not an architecture-specific issue

HBASE-27072	TestCoprocessorEndpointTracing.traceAsyncTableEndpoint is flaky

Not likely an architecture-specific issue

HBASE-27071	TestMemStoreLAB is flaky

Not likely an architecture-specific issue

HBASE-27074	TestProcedureSchedulerConcurrency.testConcurrentWaitWake is flaky

Not likely an architecture-specific issue

HBASE-27073	TestReplicationValueCompressedWAL.testMultiplePuts is flaky

Not likely an architecture-specific issue

HBASE-26493	[branch-2] TestLruBlockCache is flaky

Not likely an architecture-specific issue

HBASE-26717	[hbase-thirdparty] hbase-shaded-jersey packages unshaded classes

Not likely an architecture-specific issue

HBASE-26541	hbase-protocol-shaded not buildable on M1 MacOSX

Build-only problem, but could affect us if we do an aarch64 build

HBASE-26825	TestBasicWALEntryStreamFSHLog testSizeOfLogQueue is flaky

Not likely an architecture-specific issue

HBASE-19386	HBase UnsafeAvailChecker returns false on Arm64

fixed

HBASE-19398	Unit Tests failed in hbase-3.0.0 on Arm64 and x86

Unclear how this is an aarch64 problem

HBASE-26470	Use openlabtesting protoc on linux arm64 in HBASE 2.x
Fixed, and besides we have our own protoc aarch64 build now
HBASE-19146	Hbase3.0  protobuf-maven-plugin do not support Arm64(only for x86)

We already know about protoc stuff

HBASE-27338	brotli compression lib tests fail on arm64

We know about this potential issue already

HBASE-23612	Update pom.xml to use another 2.5.0 protoc as external protobuf

We already know about protoc stuff

HBASE-24259	[thirdparty] Update Protobuf to 3.11.4

I believe this affects 3.x only

HBASE-27167	s390x: Skip tests on unsupported compression libs

Not actually about aarch64

Summary of issues:

leveldbjni aarch64 support

There is a different JAR that provides aarch64 support for leveldb. If we built an aarch64 RPM I believe we could have it in there.

netty+epoll support

Investigation required

hbase shell / JRuby support

Investigation required

Thanks for summarizing. Do you want to move the investigation into your main issue then? I don't mind merging this since it seems relatively harmless for now, but we should probably investigate those before long.

Running this now, I did some basic tinkering with hbase shell, and it seems fine


Document: OwnedEntities requires AsNoTracking when queried separately

The code below just crashes with "A tracking query projects owned entity without corresponding owner in result. Owned entities cannot be tracked without their owner":
.Select(x => new A
{
     OwnedEntity = x.OwnedEntity
});

It worked fine on EF Core 2. No single word about that in the breaking changes doc!
I have had a hard time finding this comment:
https://github.com/aspnet/EntityFrameworkCore/issues/17617#issuecomment-529162589
I believe this pattern of querying data is quite often. At least I used to it since EF 6. Adding AsNoTracking() in these cases doesn't make sense for me considering the pattern. I understand it's too late to re-consider but please describe that behavior in the breaking changes at least.

I have a domain layer that is provided with an IQueryable<TAggregate> that in reality is a DbSet<TAggregate> created by the persistence layer. The domain layer now wants to do such a projection but out of a sudden gets an Exception, that yesterday wasn't there.
Plus: The domain layer has no idea what Entity Framework is. It is persistent agnostic, so there is no .AsNoTracking(). I am basically forced to do a load of the whole table into memory, just to prevent someone who copies code from the documentation without reading the documentation to shoot themseves into the foot.
Sadly, this is a recurrent pattern with Entity Framework Core: you spent too much energy on the "Demoware" use cases, but leave behind the serious architectual concepts like domain driven design. Don't get me wrong, I really love EF Core, but the time I spent to make thing such as an aggregate working is really high and I start thinking that an implementation at lower level like Dapper would be easier in the end, and using EF Core only as query implementation as the Q in CQRS

One of our customers reported this error, though the scenario is slightly different. JsonApiDotNetCore  dynamically produces LINQ queries of the following form when the API request contains sparse fieldsets (basically selecting a subset of the entity properties and navigations).
var customers = db.Customers.Select(c => new Customer()
{
    Id = c.Id,
    Address = c.Address
});

When no owned entities are involved, this works without explicitly setting a tracking behavior. The entities won't get tracked (obviously), which is fine because we only do this on read-only requests. But when owned entities are used, we now need to explicitly mark the query as non-tracking.
I understand that the rules when tracking occurs are complex, but the current experience is pretty inconsistent: We've all been building queries for years that weren't trackable, and we never cared. Now we suddenly need to rationalize and specify when we want to track or not, which is a pain because it may heavily affect performance. It would make more sense to me to downgrade this exception to a warning, which we can suppress in configuration. As a workaround, we're now setting the tracking behavior to NoTrackingWithIdentityResolution for all read-only requests.
Aside from that, in our example query there is actually an owner, so the error message does not seem to apply. Is this a bug?

@bkoelman We will discuss.

Note from triage: we discussed this again, but we still believe that the error is useful for preventing people falling into a pit of failure with tracking queries. We are not going to make changes here.

I don't get this. We cannot track primitives or anonymous types either but we don't explode if we happen to project to something else untrackable; why should these explode? .AsNoTracking() is not possible when I am outside of EF with an IQueryable (unless I really had to add it to my interfaces). I would think the Owned Entity should just be seen as a named set of fields and if I project to it then I am effectively projecting to those fields (which I could do manually already right?). I don't get the reason for the error; I already know my type is not a full entity and that I would lose tracking by narrowing to it; but there are lots of queries where that is true and they don't explode...

@ajcvickers Is it even possible to track entities in a query that uses projection? If not, for me the error only makes sense when not using projection at all.


Replace hyphen with underscore in check IDs

Replace hyphen with underscore in check IDs
Fixes #3536

I will only merge this after the 0.8.9 release because I think it may affect existing users who may be referencing the checks by id on build & check scripts for their font projects.
Let's give them time to adapt to the changes

@felipesanches I don't understand the logic. #3536 has been open for a while, and has been assigned to several releases since then. I saw it in the queue for 0.8.9 and decided to help in getting that release out. This PR touches on a bunch of files and now it's going to be left out to dry; by the time you decide that is time to merge it it'll likely have a bunch of conflicts. I'm not happy 😡 !

The logic is that I'm making an attempt to care about the users and reducing any potential impact on their existing build and check scripts.
I'll take care of any eventual conflicts that may surface when merging this PR.
One way to mitigate the problem could be to add code that accepts dashes as being equivalent to underscores, so that old IDs would still work (at lease for a while, with a DeprecationWarning message perhaps)

Another thing we should consider here is that this will likely need a code-test that ensure we do not end up creating new checks with hyphens in their IDs in the future. Not using dashes would then become a project policy and we should ideally also update the documentation to say that. No need to rush here. I'd prefer to be careful with this kind of decision making.
I appreciate that you're offering help towards a new release. I also gotta mention that my past weeks were a bit slow due to personal health issues. But I'll do my best to cut a new release very soon. And it will not include all of the remaining issues on that milestone because I think we already got a large set of improvements to the program that would benefit the users. I will then reassign all the remaining issues to upcoming release milestones.


Fix a fatal error not-terminating issue in Windows

Instead of llvm.trap because it may not terminate the process and may leave the process state in limbo. For example, llvm.trap is turned into the ud2 instruction on X86 which can cause an infinite sigill on Windows.

@compnerd

@swift-ci please test

Merging this for now, but I think that we should consider the portable alternative as well.


Token Auth for Azure SQL Server to Store ASP.NET Session State

Is there a feature in the roadmap already for in the roadmap to implement a layer to allow developers to use Azure SQL token authorization for the Sql Provider to store the ASP.NET Session State? Are there other providers for Azure that fill a similar role such as Azure Cache for Redis.

Is this for ASP.NET Core? or ASP.NET?

This is in ASP.NET. Does this need to thus move to another repo?

Yes. https://github.com/aspnet/AspNetSessionState, we should be able to transfer the issue


Ensure well-formed and concrete types before IR gen

The IR stage is written such that any unresolved types are an internal compiler error. This is an invariant of the IR according to @otrho and therefore should be upheld as an ICE.
This PR adds a pass before the IR stage that ensures all types are well-formed and not insufficiently specified before IR gen. Eventually we could make a new tree type that uses a specified Type enum without any unspecified variants. That would get us compile-time proofs of correctness and allow us to drop the type engine after type checking. However, it would be a ton of copy/paste as we would have to recreate our AST type, so I'm deeming it out of scope for now.
before:

after:

I like this change very much. A verification pass for each major step in the compiler helps detecting and debugging errors. Also helps achieve a #beyondmonolithic compiler 😁

Wait, there's a 14 MB binary files added in this change called nvim.appimage 😨

I'll all for Neovim advocacy but this is a bit much. 😉


Need Help.Problem deploying in IIS

2022-02-05 15:54:48.815 +08:00 [ERR] An unhandled exception has occurred while executing the request.
System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.
---> System.IO.IOException: IDX20804: Unable to retrieve document from: 'System.String'.
---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.IO.IOException: Cannot determine the frame size or a corrupted frame was received.
at System.Net.Security.SslStream.ReceiveBlobAsync[TIOAdapter](TIOAdapter adapter)
at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken)
at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(String address, CancellationToken cancel)
--- End of inner exception stack trace ---
at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(String address, CancellationToken cancel)
at Microsoft.IdentityModel.Protocols.OpenIdConnect.OpenIdConnectConfigurationRetriever.GetAsync(String address, IDocumentRetriever retriever, CancellationToken cancel)
at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)    --- End of inner exception stack trace ---    at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsyncInternal(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsync(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler1.ChallengeAsync(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)    at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)    at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)    at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)    at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.CspMiddleware.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task) 2022-02-05 15:54:48.879 +08:00 [ERR] An exception was thrown attempting to execute the error handler. System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.    at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsyncInternal(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsync(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler1.ChallengeAsync(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)    at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)    at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)    at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)    at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.CspMiddleware.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.HandleException(HttpContext context, ExceptionDispatchInfo edi) 2022-02-05 15:54:48.885 +08:00 [ERR] Connection ID "17437937763084140568", Request ID "80000019-0001-f200-b63f-84710c7967bb": An unhandled exception was thrown by the application. System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.  ---> System.IO.IOException: IDX20804: Unable to retrieve document from: 'System.String'.  ---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.  ---> System.IO.IOException: Cannot determine the frame size or a corrupted frame was received.    at System.Net.Security.SslStream.ReceiveBlobAsync[TIOAdapter](TIOAdapter adapter)    at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)    at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)    --- End of inner exception stack trace ---    at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)    at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken)    at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(String address, CancellationToken cancel)    --- End of inner exception stack trace ---    at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(String address, CancellationToken cancel)    at Microsoft.IdentityModel.Protocols.OpenIdConnect.OpenIdConnectConfigurationRetriever.GetAsync(String address, IDocumentRetriever retriever, CancellationToken cancel)    at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)
--- End of inner exception stack trace ---
at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)    at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsyncInternal(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsync(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.AuthenticationHandler1.ChallengeAsync(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)
at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.CspMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.HandleException(HttpContext context, ExceptionDispatchInfo edi)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)
at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT1.ProcessRequestAsync() 2022-02-05 17:08:29.036 +08:00 [ERR] An unhandled exception has occurred while executing the request. System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.  ---> System.IO.IOException: IDX20804: Unable to retrieve document from: 'System.String'.  ---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.  ---> System.IO.IOException: Cannot determine the frame size or a corrupted frame was received.    at System.Net.Security.SslStream.ReceiveBlobAsync[TIOAdapter](TIOAdapter adapter)    at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)    at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)    --- End of inner exception stack trace ---    at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)    at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken)    at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(String address, CancellationToken cancel)    --- End of inner exception stack trace ---    at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(String address, CancellationToken cancel)    at Microsoft.IdentityModel.Protocols.OpenIdConnect.OpenIdConnectConfigurationRetriever.GetAsync(String address, IDocumentRetriever retriever, CancellationToken cancel)    at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)
--- End of inner exception stack trace ---
at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)    at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsyncInternal(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsync(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.AuthenticationHandler1.ChallengeAsync(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)
at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.CspMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)
2022-02-05 17:08:29.107 +08:00 [ERR] An exception was thrown attempting to execute the error handler.
System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.
at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)    at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsyncInternal(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsync(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.AuthenticationHandler1.ChallengeAsync(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)
at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.CspMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.HandleException(HttpContext context, ExceptionDispatchInfo edi)
2022-02-05 17:08:29.113 +08:00 [ERR] Connection ID "15564440313803046962", Request ID "80000033-0000-d800-b63f-84710c7967bb": An unhandled exception was thrown by the application.
System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.
---> System.IO.IOException: IDX20804: Unable to retrieve document from: 'System.String'.
---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.IO.IOException: Cannot determine the frame size or a corrupted frame was received.
at System.Net.Security.SslStream.ReceiveBlobAsync[TIOAdapter](TIOAdapter adapter)
at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm)
at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Boolean async, Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.DiagnosticsHandler.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.SendAsyncCore(HttpRequestMessage request, HttpCompletionOption completionOption, Boolean async, Boolean emitTelemetryStartStop, CancellationToken cancellationToken)
at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(String address, CancellationToken cancel)
--- End of inner exception stack trace ---
at Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(String address, CancellationToken cancel)
at Microsoft.IdentityModel.Protocols.OpenIdConnect.OpenIdConnectConfigurationRetriever.GetAsync(String address, IDocumentRetriever retriever, CancellationToken cancel)
at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)    --- End of inner exception stack trace ---    at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel)
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsyncInternal(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleChallengeAsync(AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.AuthenticationHandler1.ChallengeAsync(AuthenticationProperties properties)    at Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)    at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)    at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)    at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)    at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.CspMiddleware.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)    at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)    at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.HandleException(HttpContext context, ExceptionDispatchInfo edi)    at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task)    at Microsoft.AspNetCore.Server.IIS.Core.IISHttpContextOfT1.ProcessRequestAsync()

have the same problem，I debug it  with the vs2022
IOException: Received an unexpected EOF or 0 bytes from the transport stream.
System.Net.Security.SslStream.g__InternalFillHandshakeBufferAsync|187_0(TIOAdapter adap, ValueTask task, int minSize)
HttpRequestException: The SSL connection could not be established, see inner exception.
System.Net.Http.ConnectHelper.EstablishSslConnectionAsync(SslClientAuthenticationOptions sslOptions, HttpRequestMessage request, bool async, Stream stream, CancellationToken cancellationToken)
IOException: IDX20804: Unable to retrieve document from: 'System.String'.
Microsoft.IdentityModel.Protocols.HttpDocumentRetriever.GetDocumentAsync(string address, CancellationToken cancel)
InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.
Microsoft.IdentityModel.Protocols.ConfigurationManager.GetConfigurationAsync(CancellationToken cancel)

thank you   but  i have  another problem ;   follow this  https://github.com/skoruba/IdentityServer4.Admin/issues/654


Nollup Integration

Still need to figure out how to use the common utils. Hopefully switching to ESM will resolve the issue and won't affect Webpack.

Maybe we should do a similar solution to @prefresh/vite where we use cjyes to get a cjs and esm variant?

Updated with feedback addressed! :)

@PepsRyuu This is now released as well as a fix for the peerDependencies of @prefresh/core, this won't require webpack as of 0.6.1. Made a small mistake there 😅 Let me know if you feel this is ready to merge, if you give the go I'll publish it! Thank you so much for your efforts

Updated the dependency. I think it's ready to go if you have no objections. :) Thanks for accepting the plugin! Developing with Preact is already awesome, this is going to make developing even more enjoyable! :D


redis: 7.0.9 -> 7.0.10

Description of changes
https://github.com/redis/redis/releases/tag/7.0.10

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Can you add something like "Fixes CVE-2023-28425" to the commit message?

Can you add something like "Fixes CVE-2023-28425" to the commit message?

Good idea! I added the CVE reference. Thanks!


Subscription callback never get called. please help!

GraphiQL is working, Web and iOS are working
for Android, no callback is called when message received.
Please help me out. Thanks! : )
OkHttpClient
private OkHttpClient getOkHttpClient() {
        OkHttpClient.Builder builder = new OkHttpClient.Builder();

        HttpLoggingInterceptor loggingInterceptor = new HttpLoggingInterceptor();
        loggingInterceptor.setLevel(HttpLoggingInterceptor.Level.BODY);
        builder.addInterceptor(loggingInterceptor)
                .addInterceptor(new RequestInterceptor())
                .pingInterval(5, TimeUnit.SECONDS)
                .retryOnConnectionFailure(true);
        return builder.build();
}

private class RequestInterceptor implements Interceptor {
        public RequestInterceptor() {
        }

        @Override
        public Response intercept(Chain chain) throws IOException {
            Request request = chain.request();
            Request.Builder requestBuilder = request.newBuilder();
            requestBuilder.addHeader("AuthToken", "AUTH_TOKEN");
            return chain.proceed(requestBuilder.build());
        }
    }

apolloClient
apolloClient = ApolloClient.builder()
        .serverUrl(BASE_URL)
        .okHttpClient(okHttpClient)
        .subscriptionTransportFactory(new WebSocketSubscriptionTransport.Factory(SOCKET_BASE_URL, okHttpClient))
        .build();

init Sokcet
final MessageReceivedSubscription subscription = MessageReceivedSubscription.builder().build();
        ApolloSubscriptionCall<MessageReceivedSubscription.Data> subscriptionCall =
                application.apolloClient().subscribe(subscription);
        disposables.add(Rx2Apollo.from(subscriptionCall)
                .subscribeOn(Schedulers.io())
                .observeOn(AndroidSchedulers.mainThread())
                .subscribeWith(new DisposableSubscriber<Response<MessageReceivedSubscription.Data>>() {
                    @Override
                    public void onNext(Response<MessageReceivedSubscription.Data> response) {
                        Log.d(TAG, "subscription received: " + content);
                    }

                    @Override
                    public void onError(Throwable t) {
                        Log.d(TAG, "subscription failure: " + t.getMessage());
                    }

                    @Override
                    public void onComplete() {
                        Log.d(TAG,"subscription exhausted");
                    }
                })
        );

Thank you for response! After check the WebSocketListener, I think I am getting one step forward.
But currently the onMessage is getting
{"type":"connection_error","payload":{"message":"Cannot read property 'authToken' of undefined"}}
I am sure the "authToken" is a valid header params and works on GraphiQL.

problem solved. The "authToken" should be put in subscribeConnectionParams, instead of OkHttp header. Thanks!


Recursive object properties

Well, it's me again :smile:  I currently use this plugin heavily to implement the use case already mentioned in #93. I am currently generating mock plugins to perform isolation tests. It would be very helpful if I could not only get the object type for decorators but also the properties of this object (already mentioned in #92). Something like this:
app.decorate('objectDecorator', {
  str: 'hello',
  recursiveObj: {}
})

would result in
{
  name: 'objectDecorator',
  type: 'object',
  recursive: [
    { name: 'str', type: 'string' },
    { name: 'recursiveObj', type: 'object', recursive: ... }
  ]
}

The user of this plugin could control the depth of the recursive object properties by a plugin option like maxDecoratorDepth or something similar. If this is outside the scope of this plugin this is fine and I can implement it outside this plugin, but it would be nicer and usable for others within this plugin 😄  If you are open for a PR, I am happy to provide a first implementation :)
Thanks for all your work!

What about the onDecoratorDefinition function option?

This method would then be called with the above example as follows?
onDecoratorDefinition('server', 'objectDecorator', {
  str: 'hello',
  recursiveObj: {}
})

What would then be done with the return value of this method?

You mean like in #96 with the onRouteDefinition? This could work pretty well.

What would then be done with the return value of this method?

Correct, so the user can decorate the "base" fastify-overview object adding a whatever datastructure such as the schema of the object itself

My only doubt - set 3 different functions? Maybe it is better

onRequestDecorator
onReplyDecorator
onServerDecorator

I would prefer the 3 different functions as options. It would have the following advantages:

It's more Fastify style since we also have 3 different decorate functions
we can avoid that the devs have to Check the decorator type within the single function
If one want to use the Same function for all three types, just use one function for all three options

I have implemented the first version and changed my mind. It is much easier to implement if you only have one option onDecoratorDefinition. In addition, you will probably use the same logic for all 3 types of decorators more often than less and if you want separate logic for the 3 decorators, you can do this with a simple case distinction.


Docker configuration error does not get logged

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/MinaProtocol/mina/issues
[X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/MinaProtocol/mina/discussions

Description
When running on Docker with a recent build, with a configuration error, the node simply prints the below lines with no additional information as to the error.
[ERROR] Entrypoint script /entrypoint.d/. is not a regular file, ignoring
Mina process exited with status code 1

Steps to Reproduce
Start Mina daemon with a configuration issue e.g. wrong path to block producer keypair
Expected Result
Docker provides the logs to identify the configuration issue.
Actual Result
https://github.com/MinaProtocol/mina/discussions/11840#discussioncomment-3668496
Also, see this Discird user on <IP_ADDRESS> https://discord.com/channels/484437221055922177/746316198806814760/1034182872401195048
How frequently do you see this issue?
Always
What is the impact of this issue on your ability to run a node?


Has the -layout argument been removed?

This function is about 40x faster than anything else I've tried but it interlaces columns. I've read that there is a 'layout' argument that fixes this but it doesn't figure in the help documentation. Is it available anywhere?
Thanks!

I guess it's not mentioned in the README, but it is in the help output:
$ python
>>> import pdftotext
>>> help(pdftotext.PDF)

Help on class PDF in module pdftotext:

class PDF(builtins.object)
 |  PDF(pdf_file, password="", raw=False) -> new PDF document
 |
 |  Methods defined here:
 |
 |  __getitem__(self, key, /)
 |      Return self[key].
 |
 |  __init__(self, /, *args, **kwargs)
 |      Initialize self.  See help(type(self)) for accurate signature.
 |
 |  __len__(self, /)
 |      Return len(self).
 |
 |  __new__(*args, **kwargs) from builtins.type
 |      Create and return a new object.  See help(type) for accurate signature.

Here's an example for getting the raw layout:
import pdftotext

with open("lorem_ipsum.pdf", "rb") as f:
    pdf = pdftotext.PDF(f, raw=True)

for page in pdf:
    print(page)

Hope it helps!

The help output could definitely make what each option does more obvious. I'll keep this issue open until I make an improvement there.

Improved the help doc in v2.1.2:
>>> import pdftotext
>>> help(pdftotext.PDF)

Help on class PDF in module pdftotext:

class PDF(builtins.object)
 |  PDF(pdf_file, password="", raw=False)
 |
 |  Args:
 |      pdf_file: A file opened for reading in binary mode.
 |      password: Unlocks the document, if required. Either the owner
 |          password or the user password works.
 |      raw: If True, page text is output in the order it appears in the
 |          content stream, rather than in the order it appears on the
 |          page.
 |
 |  Example:
 |      with open("doc.pdf", "rb") as f:
 |          pdf = PDF(f)
 |      for page in pdf:
 |          print(page)


Dropbox module

Hwo to Create a New Module in Trigger Happy
dropbox api

made a Wiki page as "a Box of Ideas" https://github.com/foxmask/django-th/wiki/Modules-To-Do

waiting for news from Dropbox Paper API - https://github.com/dropbox/dropbox-sdk-python/issues/87

will reopen once dropbox/dropbox-sdk-python#87 be done

TODO : testing SDK

import dropbox
from dropbox.exceptions import ApiError
from dropbox.paper import ImportFormat, PaperDocCreateError

key = '8m89s4gfphhg7zr'
sec = 'w988lcdvuvju8mf'

dbx = dropbox.Dropbox("_access_token_")

content = b"
My title

my content
"

try:
    r = dbx.paper_docs_create(content, ImportFormat('html'))
    print(repr(r))
    print(r)
except PaperDocCreateError as e:
    print("PaperDocCreateError ERROR %s" % e)
except ApiError as e:
    print("API ERROR %s" % e)

for entry in dbx.files_list_folder('').entries:
    print(entry.name)

see

after 2 tries, I reach RateLimit of 100 new docs in a raw, it's complicated to use Dropbox Paper in that conditions.


[Bug] [UI] Edit datasource port show error

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
Edit datasource port show error

What you expected to happen
show correct, as backend return.
How to reproduce
use 3.0.0-release and create datasource, refresh page, and edit it.
Anything else
No response
Version
3.0.0
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

I will fix it.


Describe Mage-OS release process

Added my DRAFT notes to the main README.

Hi @cmuench, what do you think it's missing from this PR in order to merge it? I think it's great information and should definitely be in the readme

@cmuench I helped Vinai to prepare a Mage-OS Release some month ago. This are my notes of this session.
@rhoerr asked me if I can share my notes. In the meantime Ryan was already responsible to several releases. The idea was to docuement the release process. Maybe Ryan can review it.

Thanks @cmuench!
@rhoerr could you help finalizing this PR so that we can merge it?


Add stats derived off of event positions

Especially for shot events, i.e. angle, distance from net, etc

Completed in #3.


[Segment Replication + Remote Store] SegRep with N2N with Index level overide should not be allowed to enable Remote store

When the cluster is configured with SegRep with N2N (Node to Node) with index level override — configuration change should prevent user from enabling Remote Store.
Describe the solution you'd like
Upon detecting that the user is trying to enable Remote Store on a cluster with SegRep with N2N with index level override, the config should fail and keep the original configuration. The user should be notified of the failure and a proper error message with details should be provided.
Example error message : "Enabling Remote Store on clusters with SegRep with N2N and index level override is not allowed"
Additional context
This limitation should be documented in our docs.

Already part of requirements in https://github.com/opensearch-project/OpenSearch/issues/8497. Closing in favour of https://github.com/opensearch-project/OpenSearch/issues/8497.


Better image support

Hi @stephansann ,
I would make an enhancement request.
There should be a zoom support when you open images, because if I open a large picture like this:

I can't see anything of it because it is displayed in a simple ImageView.
I had to implement a good zooming support for images in my project, so I can recommend you to have a look at GestureFX, it allows you to build a zoomable pane around your node (in this case image-view).
Best regards
Daniel

Hi @Dansoftowner
A slightly related note:
I just introduced the rotation of images based on EXIF data:
https://repository.sophisticatedapps.com/snapshots/com/sophisticatedapps/archiving/document-archiver/2.1.0-SNAPSHOT/document-archiver-2.1.0-20210513.141304-4-linux.zip
Anyhow I nailed it only 80%.
javafx.scene.Node#setRotate was giving me a hard time. After hours of trial and error I now got to a point where everything is rotated correctly and the image is not only shown in one half, is being misplaced or similar misconducts I saw on my attempts.
But still images which are rotated 90 degrees get cropped to a square. Now I'm on my wits' end.
You said you have some experience with ImageViews!? Any idea from your side? This is my current code:
    protected static class DisplayImageNodeAssembler implements DisplayFileNodeAssembler {

        @Override
        public Region assemble(DisplayFilePaneController aDisplayFilePaneController, File aFile, Stage aStage,
                               double aPrefWidth, double aPrefHeight) {

            ImageUtil.OrientationInformation tmpOrientationInformation = ImageUtil.getOrientationInformation(aFile);
            double tmpImageRotationCw = tmpOrientationInformation.getRotationCw();
            boolean tmpImageTilted = ((tmpImageRotationCw != 0) && (tmpImageRotationCw != 180));

            try (BufferedInputStream tmpInputStream = new BufferedInputStream(new FileInputStream(aFile))) {

                // Creating the Image and ImageView objects.
                Image tmpImage = new Image(tmpInputStream);
                ImageView tmpImageView = new ImageView(tmpImage);

                // Do we need to rotate?
                if (tmpImageRotationCw > 0) {

                    double tmpViewPortWidth = (tmpImageTilted ? tmpImage.getHeight() : tmpImage.getWidth());
                    double tmpViewPortHeight = (tmpImageTilted ? tmpImage.getWidth() : tmpImage.getHeight());
                    tmpImageView.setViewport(new Rectangle2D(0, 0, tmpViewPortWidth, tmpViewPortHeight));

                    tmpImageView.setRotate(tmpImageRotationCw);
                }

                //Setting the image view parameters
                tmpImageView.setX(0);
                tmpImageView.setY(10);
                tmpImageView.setPreserveRatio(true);
                adjustHorizontalSize(tmpImageView, tmpImageTilted, aPrefWidth);

                GesturePane tmpPane = new GesturePane(new Pane(tmpImageView));
                tmpPane.widthProperty().addListener((anObservable, anOldValue, aNewValue) ->
                        adjustHorizontalSize(tmpImageView, tmpImageTilted, aNewValue.doubleValue()));

                return (tmpPane);
            }
            catch (Exception e) {

                throw (new RuntimeException("Image could not be loaded."));
            }
        }

        private void adjustHorizontalSize(ImageView anImageView, boolean anIsTilted, double aSize) {

            if (!anIsTilted) {

                anImageView.setFitWidth(aSize);
            }
            else {

                anImageView.setFitHeight(aSize);
            }
        }
    }

Thanks and best regards
Stephan


Remove deprecated merge_single_qubit optimizer

This optimizer has moved to transformers.

Automerge cancelled: A required status check is not present.
Missing statuses: ['Pytest Windows (3.8)', 'Pytest Windows (3.9)']


from pandas.io.common import EmptyDataError

Aim: Need to update code in /blast/__init__.py to make it more agnostic to pandas version.
Issue: new pandas versions > 1.0.5 do not support from pandas.io.common import EmptyDataError statement described in this reference
Action: Need to update code in /blast/__init__.py to more general from pandas.errors import EmptyDataError for the next MOB-Suite release

Addressed in software version 3.0.1


2 names are wrong

For Privileges for vCenter 6.0 and 6.5
Global.SetCustomFields should be Global.SetCustomField
VirtualMachine.Config.AdvanceConfig should be VirtualMachine.Config.AdvancedConfig

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 56ab6c2f-0846-e344-2613-808078b627cb
Version Independent ID: 4afbc90f-4e26-e4e1-b1ec-b4cddb402447
Content: Back up VMware servers with Azure Backup Server
Content Source: articles/backup/backup-azure-backup-server-vmware.md
Service: backup
GitHub Login: @rayne-wiselman
Microsoft Alias: adigan

@Agazoth Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

This is now fixed. #please-close

@Agazoth We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


use universal suggestion widgets for all editors

Resolves
Issue #126
What's new
This PR replaces the previous seed suggestion implementation. Rather than defining suggestion seeds for each editor, it uses the same suggestion widgets for all editors only displaying them on active editors. It fixes the flickering of the restore page on scroll. It also fixes briefly displayed suggestions for the previously active editor when selecting another one.

your first and second bullet points was implemented on the last push. Your last bullet point would be on a separate pull request. This PR is only to fix the suggestion seeds flickering on scroll.


ApacheRestfulClientFactory does not use system properties for proxy configuration

Describe the bug
ApacheRestfulClientFactory provide HTTP client whose proxy is not configured with system parameters (http.proxyHost, http.proxyPorts). Configuration must be done by hand:
String proxyHost = System.getProperty("http.proxyHost");
String proxyport = System.getProperty("http.proxyPort");
if (proxyHost != null && proxyport != null) {
    fhirContext.getRestfulClientFactory().setProxy(proxyHost, Integer.parseInt(proxyport));
}

On the other hand, the OkHttpRestfulClientFactory does take those system properties into account.

Expected behavior
HTTP client provided by ApacheRestfulClientFactory should consider proxy system parameters.

This feels like it would be a reasonable addition. Would you be willing to
submit a PR with tests?
On Mon, Nov 23, 2020 at 4:37 AM paulleseute<EMAIL_ADDRESS>wrote:

Describe the bug
ApacheRestfulClientFactory provide HTTP client whose proxy is not
configured with system parameters (http.proxyHost, http.proxyPorts).
Configuration must be done by hand.
Expected behavior
HTTP client provided by ApacheRestfulClientFactory should consider proxy
system parameters.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jamesagnew/hapi-fhir/issues/2192, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2N7HLWLNQO2E63APVIIADSRIUPLANCNFSM4T7HQYSQ
.

The http client can be built by calling useSystemProperties() method of the builder. This will then set the default proxy settings from the environment (http(s).proxy(Host|Port)) if not explicitly provided. However, this will also apply the default settings of:

supported protocols (env. variable https.protocols)
supported Cipher suites (env. variable https.cipherSuites)
SSL connection factory
keep alive (env. variable http.keepAlive which defaults to true)
http max connections (env. variable http.maxConnections which defaults to 5)
reuse strategy (depending on the variable http.keepAlive; defaults to DefaultClientConnectionReuseStrategy that is the same as if no reuse strategy configured)
user agent header (env. variable http.agent)
credentials provider (considering env. variables like http.auth.ntlm.domain, http(s).proxyUser, http(s).proxyPassword, etc)

By using system properties there will be no change in the current behaviour. Just that the following would be possible to alter with env. variables;

reuse strategy
user agent header
proxy
All the others are explicitly provided in the ApacheRestfulClientFactory.

I'm happy to submit a PR if you like ;)

@jamesagnew, is this ok? Could you please review the PR?


Apple $99 developer fee extortion reports “smolmenubar is damaged and can’t be opened." but its actually fine

Using macbook pro m1 pro. After downloading the arm64 binary file, and trying to open. It shows the below.
Tried deleting and reinstalling, same issue.

thank you. this is an intermittent issue due to Apple wanting to charge $99 to publish apps.

i have just tried to sign up for Apple Developer, and wasted 30 minutes trying and failing for them to accept my ID. i give up. please let me know if theres some other way to do this.

Cools, thanks!
Just wanna say cool program! It's like having three different tutors when I want to learn a concept and ask for examples from each.

there's 4 now :)

update: you can do this https://www.howtogeek.com/803598/app-is-damaged-and-cant-be-opened/
To do this, open a new Terminal window and type (or paste the following command):
xattr -d com.apple.quarantine /path/to/app.app

You’ll need to replace /path/to/app.app with the target location of the file you want to release from quarantine. One easy way of doing this is to drag the file into the Terminal window, right after the initial command.

@andrewsiah v0.10 has notarization now https://github.com/smol-ai/menubar/releases/tag/v0.0.10 can you download and retry?
i still have not been able to figure out how to upload to testflight/mac app store.

Cools it works, thanks!


Add "severity" attr to dependencies and health checks

Is your feature request related to a problem? Please describe.
In the future, we want to provide more specific messaging to the user when a service has a dependency error or health check error, depending on its severity.
The binary (critical vs non-critical) UX is acceptable for 0.3.0 launch, but it would be preferable to switch to an enum implementation now for a smoother transition and backwards compatibility later.
Describe the solution you'd like
critical bool should be removed from dependencies and health checks. A optional severity enum will be added in its place. Options are currently limited to "warning" and "critical", with "warning" being the default.

what are the desired semantics of each label? We should be clear on what each designation means if we are going to expand it like this. If we are not it will create more confusion which is what I think this ticket was cut to avoid. The questions I would like answered are:

What constitutes warning?
What constitutes critical?
What is an example of a 3rd label? All 2 point enums are isomorphic to booleans (which is the current implementation). This means that this hypothetical third label must exist in order for any benefit to be observable from this change.
How do we intend to communicate the semantics of each label to the user?

This is all about messaging to the user and enabling or preventing functionality. The ones we discussed were "info", "warning", "error", and "critical".
Info: benign in nature, expected
Warning: may experience issues, fine to run
Error: will not work as expected, recommended not to run
Critical: likely to cause harm, cannot run
This is just a rough hypothesis. Doesn't need to be decided now because we have the ability to easily extend later.

Should this be moved to 0.3.1?

No, because then every service would have to migrate or we would have to acquire tech debt to build in backwards compatibility. It's an investment. A few minutes now will save us a few hours later. And it actually is a few minutes, I think.

Info: benign in nature, expected
Warning: may experience issues, fine to run
Error: will not work as expected, recommended not to run
Critical: likely to cause harm, cannot run

I'm satisfied with this as a demonstration of hypotheticals, however it does not solve the need for building in tech debt as a result of backwards compatibility. We would need to handle the case (somewhere, be it os, sdk, etc.) where a package specifies a value that is not recognized by the current version of embassy-sdk.

This is only the case if a value is removed from the enum. Also, is your comment specific to this issue to or the idea of backwards compatibility in general?

This is (at least) a few minutes of work per service

That sounds about right.

Swapping myself in-place of @dr-bonez since this is very close to the names/descriptions feature I am already on.

Tracking service update progress here https://github.com/Start9Labs/embassy-os/issues/832#issuecomment-980141784


Add support for gRPC probe

Our probe rewrite needs to handle https://github.com/kubernetes/enhancements/issues/2727

Hello @howardjohn, are we gonna rewrite the original probe to http probe, or just rewrite the port/service and introduce a grpc server in pilot-agent?

Hmm good question.. Is the gRPC always the standard GRPC health service? Or. somehow allows custom services?
I am leaning towards rewrite it to http. It doesn't really matter to users what the protocol to the agent is, just what protocol we use when forwarding which will of course be gRPC?

Thanks for your reply!

Is the gRPC always the standard GRPC health service? Or. somehow allows custom services?

Yes it must be a standard GRPC health service, please refer to k8s doc

I am leaning towards rewrite it to http. It doesn't really matter to users what the protocol to the agent is, just what protocol we use when forwarding which will of course be gRPC?

Agree, I'm trying to implement it

Ack, thanks for the info. I would lean towards rewriting to http o
probe and then the agent forwarding as gRPC. That seems simplest to me and
should not have negative side effects for users
On Wed, Dec 22, 2021, 8:23 PM dwq @.***> wrote:

Thanks for your reply!
Is the gRPC always the standard GRPC health service? Or. somehow allows
custom services?
Yes it must be a standard GRPC health service, please refer to k8s doc
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#probe-check-methods
I am leaning towards rewrite it to http. It doesn't really matter to users
what the protocol to the agent is, just what protocol we use when
forwarding which will of course be gRPC?
Agree, I'm trying to implement it
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/36314#issuecomment-1000033413, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXJ7ZQL3ACPTXDFGC23USKP5DANCNFSM5JDDVZYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Add autoreleasepool to release autorelease objects in advance when using GCD

New Pull Request Checklist

[x] I have read and understood the CONTRIBUTING guide

[x] I have read the Documentation

[x] I have searched for a similar pull request in the project and found none

[ ] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

[ ] I have added the required tests to prove the fix/feature I am adding

[ ] I have updated the documentation (if necessary)

[ ] I have run the tests and they pass

[ ] I have run the lint and it passes (pod lib lint)

This merge request fixes / reffers to the following issues: ...
Pull Request Description
Fixes #2427 .
We use GCD to do some progressive or decode work, it would produce some big size autorelease objects. But actually, GCD would not guarantee when to drain these objects, sometimes would leads to crash, like #2427 . So we need to add a explicitly autoreleasepool to  drain them timely.
PS. Apple Documents

If your block creates more than a few Objective-C objects, you might want to enclose parts of your block’s code in an @autorelease block to handle the memory management for those objects. Although GCD dispatch queues have their own autorelease pools, they make no guarantees as to when those pools are drained. If your application is memory constrained, creating your own autorelease pool allows you to free up the memory for autoreleased objects at more regular intervals.

The PR targets to 5.x, but master also has issues. The big difference between 5.x and master, I think it maybe a little bother to merge. Maybe we should solve some 4.x issues asap and release 5.0.

Codecov Report

:exclamation: No coverage uploaded for pull request base (5.x@f22a698). Click here to learn what that means.
The diff coverage is 93.33%.

@@          Coverage Diff           @@
##             5.x    #2474   +/-   ##
======================================
  Coverage       ?   78.01%
======================================
  Files          ?       47
  Lines          ?     6623
  Branches       ?        0
======================================
  Hits           ?     5167
  Misses         ?     1456
  Partials       ?        0

Flag
Coverage Δ

#iOS
77.95% <93.33%> (?)

#macOS
76.81% <93.33%> (?)

Impacted Files
Coverage Δ

SDWebImage/SDWebImageDownloaderOperation.m
89.5% <92.3%> (ø)

SDWebImage/SDWebImageManager.m
87.8% <94.11%> (ø)

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 f22a698...703631d. Read the comment docs.

@dreampiggy do you agree?

Does that the autorelease object during thsee GCD block actually increate the memory heap ? Maybe we need some profile result to check this issue. Currentlly there is no any result to indicate that adding autoreleasing pool can solve that memory peek and OOM issue.
And I think, the mosts autoreleasing object, was created during the image decoding. So if we can ensure this solve the problem, we just need to add these autoreleasing pool into the decoding method call. (That autoreleasing pool inside storeImage: method is not necessary)

@dreampiggy Please see my PR description, you can try #2427, it 100% crashes in very little time.
I don't think we need to add autoreleasepool in decode function, it's the problem to GCD, call it multiple times and maybe not release in timely.

PS. add autoreleasepool is not 100% safe. I'll make a PR or Issue to describe later. The another issue is we create one queue to one operation. if we have multiple operations, which means may have multiple decoding operations running. Has a much big risky to crash.

@zhongwuzw Autorelease pool is not really cheap cost. It need to allocate the object, need TLS creation, etc. So if the block logic not create too much of autoreleasing object, it's no need to create a local one. Just use the runloop autoreleasing pool and let it been released.
I don't means this issue is not solved, I think since this is a performance enhancement, maybe we should take more experience on it. Use a profile result and compare the different result is much better. Which is suitable for framework developement, but not just write code like we assume. (This may because I fell in the trap by this when I was graduate from the college. So I graduatlly relay on the profile result to do performance fix)

@zhongwuzw  we create one queue to one operation is the decision made from 4.2.0 via #2199 . The aim of that PR is aim to solve the issue that we decoding each of different images into the same delegate queue, and cause the "final callback response" take more times than expected. It's the root case.
That change is actually a double-edged sword. It allows the multiple decodig process happed, for better performance. However, the cost is that this may result a higher rate of memory peak. This is another issue that mentioned before. But it seems hard to answer a final result.

@dreampiggy

Autorelease pool is not a really cheap cost. It need to allocate the object to consturct a stack, need TLS creation, etc. So if the block logic does not create too much of autoreleasing object, it's no need to create a local one. Just use the runloop autoreleasing pool and let all objects been released is better.

From your comments, I assume you read the related source code. I just push a new Autorelease pool on Autorelease pool stack, see Apple documents. GCD always have its own Autorelease pool, so the cost is I create a new Autorelease pool struct, one page size. Autorelease operation is always exist, I just let it in advance, so no big cost like you said, nearly no cost, and maybe you miss up the relations of Runloop and GCD, GCD has its own threads pool, so no runloop would exist. only main thread has a setup runloop.
Just like I said above, it would crash very quickly, but if you wants to see the profile, I did it, the original code screenshot like below, it would leads to 2.6G and crash very quickly,

After added the autorelease pool, the spikes is 1.3G, and works well. Just like below.

This is great @zhongwuzw. Thanks for measuring and detailing. I want to merge this PR and make the same adjustments for 4.x

@bpoplauschi I make a PR for 4.x, we can merge if @dreampiggy has no any consideration.

This PR is OK. Maybe we can merge it.
But I'm considerating something like to totally revert that #2199. It's the root case of all "evil".
Because for progressive decoding, we do decoding each time new data is available, and for huge images, the decoding speed is much slower than URLSession callback speed. Even when the network download already finished, the decoding queue is full of previous progressive task and cause the completionBlock logic not been finished.
There are many solution. For example, seperate the progerssive decoding queue && final full pixel image decoding queue. For progressive, use the URL session queue. For full pixel, use the non-shared queue. Or we can give user a option, to control whether put the decoding queue seperate from URLSession queue. I'll open a issue and try some attempt.

@dreampiggy I think the improvement on decoding is a different discussion than this one. These autoreleasepools will just help keep the allocations not spiking, which is great. I will merge this one and the one to master as well. We can discuss on other PRs/issues about other improvements.
But keep in mind we should just really close on the 5.0 release, we can't just keep adding stuff :) So join me on #2285 where I created a list of remaining things for a beta4 release. Let's keep this list minimal. We can always make other improvements in future versions without changing the API (no breaking changes).


Setting Java keywords library on classpath for runrobot

If I have a custom keywords library (written in Java) for my tests, runrobot does not see it. It is in the same directory as the RF tests file, but it must not be on the classpath for runrobot. I have attempted to modify my global classpath variable, but that also does not seem to fix the problem.

custom libraries jars have to be put on gradles buildscript classpath.
I have prepared an example for that. Please have a look an that and come back if it doesn't solve your problem.
https://github.com/cthiele42/gradle-robot/tree/master/examples/javaKeywordLib

OK. I have solved the problem (sort of) using your example (perhaps not the best way since I'm new to Gradle). My situation is that I have RF keywords that have to be defined in Java files, and I'd like to keep those source files in the same directory as my tests .txt file (src/test/acceptancetest). So I have to compile them, jar them, and then make runrobot find them in order to run the tests. I set up a "robotFramework" task for that so that it would do those things in order (I think).
This is the relevant part of my build file:
buildscript {
    dependencies {
        classpath fileTree(dir: 'build/libs', include: '*.jar')
    }
}
plugins {
  id "org.roboscratch.robot" version "0.1.1"
}
apply plugin: 'java'

// Unimportant stuff... I think...

task acceptanceKeywordsCompile(dependsOn: jar, type: JavaCompile) {
    destinationDir = file('build/classes/test/acceptancetest')
    classpath = fileTree(dir: 'build/libs/', include: '*.jar')
    source = fileTree(dir: 'src/test/acceptancetest', include: '**/*.java')
}
task acceptanceKeywordsJar(dependsOn: acceptanceKeywordsCompile, type: Jar) {
    baseName = 'custom-keywords'
    destinationDir = file('build/libs')
    from 'build/classes/test/acceptancetest'
}
task acceptanceKeywordsCompile(dependsOn: jar, type: JavaCompile) {
    destinationDir = file('build/classes/test/acceptancetest')
    classpath = fileTree(dir: 'build/libs/', include: '*.jar')
    source = fileTree(dir: 'src/test/acceptancetest', include: '**/*.java')
}
task acceptanceKeywordsJar(dependsOn: acceptanceKeywordsCompile, type: Jar) {
    baseName = 'acceptance-keywords'
    destinationDir = file('build/libs')
    from 'build/classes/test/acceptancetest'
}
task robotFramework(dependsOn: acceptanceKeywordsJar, type: org.roboscratch.gradle.RunRobot)

The problem I'm having now is that the first time I run gradle robotFramework, it fails to find the jar file the first time I run it (complaining about an import error because no module is named whatever I call my module). The jar file certainly exists, because I can see it and have looked inside to verify that it has the class files.  It also fails to remove that keywords jar file when I run gradle clean (unable to delete file). I don't know if these issues are related. Perhaps you can show me where I've made a mistake?

What you want to achieve seems to be a valid usecase: compileing a java keyword lib and testing it using runrobot in the very same gradle build run.
But this is colliding in some way with the gradle lifecycle.
In a first phase, gradle builds a classpath for all tasks to be used in the buildscript.
In a subsequent phase, this classpath will be used to execute all tasks including javaCompile and runRobot.
The gradle daemon plays its own role in this game: The classpath for gradle tasks built on the first daemon start cannot be modified on subsequent gradle build executions using the daemon.
The 'unable to delete file' error possibly comes from a special behavior on Windows: A jar referenced by the JVM is locked and cannot be deleted.

The buildscript classpath will be constructed referencing the custom library jar
The clean task will run and tries to delete the jar - but this is locked (under Windows)

But there is a solution - a bit dirty but possibly acceptable in your case:
There is an example again demonstrating it: https://github.com/cthiele42/gradle-robot/tree/master/examples/javaKeywordLibDev
We do not package a jar - this is not needed for custom keyword libs.
Instead of this, we put the class files on classpath. Classfiles are not locked and scanned lazy in time of class loading.
The build has to started with the commandline option --no-daemon. The start of the robot tests will take a while because the JPython system has to be initialized with each and every build run. This way, the newly compiled classes will be accepted during the test run.

OK. I have modified my code to use your approach. Everything works, but I still have the issue of having to run gradle runrobot twice in order for the robot tests to run and pass. (They fail the first time because robot can't find the keyword library, even though it's there.) That's true whether I use --no-daemon or not.
For completeness and to help others trying to do this sort of thing, I'm attaching a zip file with my example project that shows how this all goes together.
custom-widget.zip
In this example, I have created a custom widget that contains a square in the center (sized at half of the smallest dimension). The square is yellow (deselected), and clicking on the square (but not outside of it) causes it to toggle (selected turns it blue). It also generates a custom event that listeners can register, as in the example application where a label is updated with "SELECTED" or "NOT SELECTED" accordingly.
Feel free to do with it what you will. As far as I'm concerned, this issue is now closed to my satisfaction. Thank you for all of your help.

Thank you for providing the example code. I was able to reproduce the problem:
The directory build/classes/main has to exist to be added to the classpath - this is not the case after a fresh project start or after a clean was running.
It can be fixed with the following change:
classpath files(mkdir('build/classes/main'))
I opened issue #2 to provide a reliable solution for the use case behind.

Perfect! That worked as advertised.
You had mentioned in the Gradle file comment about using properties of the java task instead of (I presume) the hard-coded directory structure. Would that be something that would still work with the mkdir thing? I suppose it would be something like sourceSets.main.output.classesDir. When I try it with that (with and without the mkdir), Gradle complains about that "variable" or whatever not existing. Is that because the java plugin doesn't exist until later in the script? Or do I just have no clue as to what I'm doing here?


InvertedCircularReaveal

This is a feature request. When next screen is reveal through circular reveal it would be very convinient and estethicaly pleasing to use inverted reveal when navigating back.
How invertedCircularReveal would work. Circle (with specified centerX, centerY) starts at MAX radius and shrinks to 0 dp or any other end-radius and dissapears, instead of revealing view inside the circle it reveals the view outside of circle's fill area (so the inside of the circle is the 'transaprent area' instead of outside as it is in the regular circle reveal).

may be i do not understand, aren't you talking about this

I tried to attack an image what the idea I have in mind.
Top left shows how the animation looks shortly after reveal start. B is the view that was on showing and A is the view being revealed (C is mask scale pivot center).
So with typical reveal you have a opacity mask like on bottom left (white is visible, black is hidden part). While bottom right shows the mask for inverted reveal (again white is the part being revealed, black is hidden a.k.a view underneath)

If i understand right, you mean to reveal parent (but, keep child visible, hm it's impossible for now)
Try this one and reveal FrameLayout

<io.codetail.widget.RevealFrameLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

   <FrameLayout <!-- This layout will made inverting -->
    android:id="@+id/inverted"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

          <android.support.v7.widget.CardView
        xmlns:app="http://schemas.android.com/apk/res-auto"
        android:id="@+id/awesome_card"
        style="@style/CardView"
        app:cardBackgroundColor="@color/material_deep_teal_500"
        app:cardElevation="2dp"
        app:cardPreventCornerOverlap="false"
        app:cardUseCompatPadding="true"
        android:layout_marginLeft="8dp"
        android:layout_marginRight="8dp"
        android:layout_marginTop="8dp"
        android:layout_width="300dp"
        android:layout_height="300dp"
        android:layout_gravity="center_horizontal"
        />

   </FrameLayout>

</io.codetail.widget.RevealFrameLayout>

Thanks. I can't run code atm, but will try it back home tonight.
Well if by "keep child visible" you're refering to the top right image, that is not nescessarely then end of animation, B can be as small as 0dp.
The main difference between this and "reversed circular reveal" you referenced is that view A is being revieald from the sides to some (x, y) center instead of B being hidden. Here, A is on top of B and not the other way arround.

I guess this means feature request was rejected?

oops, i thought problem was solved

Excuse my photoshop skills, but I tried to make an animation how it would work.
Note that it is not the first screen disapearing, but rather the second screen (email/password) appearing in an inverted fashion.

Finally got it, will do my best to implement this feature

Hi, well i added reverse feature, check it out in last version, i hope i understood well and did it right, if no please re-open issue

is there any way to close reveal animation with Drag(using gestures) like snap chat and wats app status


Unnecessary left padding in select control

I have noticed unnecessary left padding in select

fixed on develop branch. Will be added in next release :)


Copy all TaskRunner related classes from 'Command Task Runner'

Copy all TaskRunner related classes from 'Command Task Runner'
Replace commands.json with tasks.vs.json
Replace CommandTask class with new structure

ps. Really wanted to test the new GitHub 'Draft Pull Request' 😄

ps. Really wanted to test the new GitHub 'Draft Pull Request' smile

Gitlab allows to use WIP in MR title. Much better IMO.

i think we're good to merge this for now.

i guess we can't merge it until @sboulema changes from draft.

Will continue with this tomorrow! Haven't even locally tested this yet...


Validate query parameters that are objects

More info: https://swagger.io/docs/specification/describing-parameters/#query-parameters
Currently these are not validated at all.

https://swagger.io/docs/specification/serialization/#query possibly also useful.

Fixed in b63ce9309edd7170e8c4badafafb1cafcec37be2


TensorFlow upgrade to 1.0.1

I upgraded my server from 1.0.0 (ubuntu):
pip install --upgrade https://storage.googleapis.com/tensorflow/linux/cpu/tensorflow-1.0.1-cp27-none-linux_x86_64.whl
But I get the following discrepancy:
(tensorflow)$ pip list | grep tensorflow
tensorflow (1.0.0)
(tensorflow)$ python -c 'import tensorflow as tf; print(tf.version)'
1.0.1

What env manager are you using?
Did you uninstall 1.0.0 before upgrading to 1.0.1? If it's causing concern I would try uninstalling and reinstalling. It shouldn't do any harm.

I am using virtualenv
No didn’t. But it should upgrade smoothly without uninstall and then install.

Best Regards,
Neha Dave

From: jubjamie<EMAIL_ADDRESS>Reply-To: tensorflow/tensorflow<EMAIL_ADDRESS>Date: Tuesday, 21 March 2017 at 9:13 PM
To: tensorflow/tensorflow<EMAIL_ADDRESS>Cc: "Dave, Neha"<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [tensorflow/tensorflow] TensorFlow upgrade to 1.0.1 (#8586)
What env manager are you using?
Did you uninstall 1.0.0 before upgrading to 1.0.1? If it's causing concern I would try uninstalling and reinstalling. It shouldn't do any harm.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tensorflow/tensorflow/issues/8586#issuecomment-288120122, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYkejUoW5cSzh3qUK2--iakSbRL7pU-xks5rn_AagaJpZM4Mj7pb.

The upgrade process is completely managed by PIP package manager.
PIP is just a tool we use to deliver tensorflow.
Unfortunately, it at times has bugs. Looks like you ran into one of these.
It looks like TF actually upgraded, but pip was not able to record the metadata correctly.
If you are not using virtualenv, you may need to use "sudo" to when running pip. If you are in a virtualenv, make sure you did not accidentally run pip command with sudo previously.
Also, most pip issues are resolved when you rerun the command.
Finally, as this looks like a PIP issue, there is not much we can do to help with this.
You can try reporting an issue to pypi, through http://pypi.org


OWNERS: spruce up list

Description: we have had some more participants since this was first written. Updating to include people.
Signed-off-by: Jose Nino<EMAIL_ADDRESS>

Thanks @junr03!


check uploader during TUS uploads

Previously when a user initiated an upload and another user sent data to the initialized endpoint the request was not rejected.

See https://github.com/owncloud/ocis/issues/1141 for more information.


Directions on adding SSO connection with OIDC

Hi there,
I am using the starter kit and let me firstly appreciate how awesome this project is!
My issue is when setting up SSO connection with OIDC: even after adding the respective client credentials and OpenID discovery path, there isn't any SSO button on the login screen.
I wanted to know if there are any explicit instructions for the same as I saw instructions/videos only with respect to the SAML-SSO connection.

@abhiavadhani-zelar You have to enable the saml auth provider here .

Well, that added the button on the login screen.
Thanks @niwsa , it worked!
Although, can we find these instructions somewhere for essential features like SSO, Directory Sync, etc.?


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 08:39:29 on 2023.04.14
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 5, errors out: 0
Original problem ID: 16947
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=16947

Problem has been resolved in 6m 0s at 08:45:29 on 2023.04.14
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 16947


"Propose new terms" section of the "How to Contribute" guide shouldn't be localized

Part of the new language package, it is required to localize the The "How to Contribute" guide at  https://glossary.cncf.io/contribute/ .
There's a "Propose new terms" section in that guide, which I saw localized into other languages, but as is.
My logic is this:

Proposing a new term is only possible with "English" as the entry point

If the person who wants to propose a new term knows English, they can go and check the same section in the English guide and learn how to propose a new term.

If they don't know English, they cannot propose a new term anyway.

Am I missing a point or a case?
Instead, I think this section should be basically clearly saying:

English is the entry language for new terms
Here's the procedure on how to do that (link to "Propose new terms")

I have been working on localizing this guide to Turkish and I found it a bit weird that I am writing text that explains how to create a new English term in Turkish :)

cc @CathPag @seokho-son

cc @jihoon-seo

Thank you, @aliok. First and foremost, I appreciate your efforts in considering and identifying this issue!
The Korean localization team (and perhaps other language teams as well) has previously deliberated on this matter.
The Korean localization team has considered the logic behind points 2 and 3, and we have subsequently localized "Propose new terms" section in the contribution guide. The rationale for our decision is as follows:

"1. Proposing a new term is only possible with "English" as the entry point"

--> Yes (as is)

"2. If the person who wants to propose a new term knows English, they can go and check the same section in the English guide and learn how to propose a new term."

--> Even for Koreans who can use English (not necessarily at a native level, but competent enough to suggest new terms in English), having the guide in Korean makes it relatively easier and quicker for them to understand the process.

"3. If they don't know English, they cannot propose a new term anyway."

--> Even for Koreans who aren't proficient in English, while they might not propose new terms themselves, having the guide in Korean can make them easily aware of the procedure (our efforts to make it official and community-driven) we have in the Glossary project for suggesting new terms.
Is this rationale acceptable to your team ? :)

Thanks for the feedback @seokho-son
I think we can accept that :)
/close


Darwin fixes

Things done:

[ ] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
[ ] Built on platform(s): NixOS / OSX / Linux
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md

Maybe you should update the meta.platforms attributes of gnubg and mplayer to reflect that they are supported on darwin.
When trying to build mplayer on mac osx 10.11.3, I get the following error:
In file included from input/ar.c:26:
In file included from /nix/store/dfvrzc0p99vp3gx2q7w79iiq14drj851-IOKit-osx-10.10.5/Library/Frameworks/IOKit.framework/Headers/hid/IOHIDLib.h:31:
/nix/store/dfvrzc0p99vp3gx2q7w79iiq14drj851-IOKit-osx-10.10.5/Library/Frameworks/IOKit.framework/Headers/hid/IOHIDDevice.h:315:1: error: expected function body after function declarator
AVAILABLE_MAC_OS_X_VERSION_10_10_AND_LATER;
^

I have no clue what that means.

@vbgl I'm getting that too now. You can manually edit the file to comment out AVAILABLE_MAC_OS_X_VERSION_10_10_AND_LATER and everything works ok.
I think it has to do with IOKit being 10.10 but CF is still at 10.9. Not a nice fix for it...


Execute test plan/framework and document

First draft can be found here: https://docs.google.com/document/d/10Zyrvintz1-tPWTVJYBjrBHEjbOTpPTM2H6eq_lpJhg/edit#

Relevant test cases from the plan in issue #65 should be executed
Our algorithms needs to be challenged as much as possible; we can learn from this and add some great notes on the algorithm weaknesses in the report

Sakila

[x] Execute relevant tests
[x] Develop confusion matrixes
[x] Show results as graphs in the report

Company DB

[x] Execute relevant tests
[x] Develop confusion matrixes
[x] Show results as graphs in the report

General

[x] Write down weaknesses and findings during the experiments
[x] Prepare places in the report for the mention of these weaknesses ("Limitations" of chapter 5 may be used)
[ ] Describe appropriate findings + weaknesses in the report

Resultater kan findes her: https://docs.google.com/document/d/1cI8klLchqEXrrZOOGmbyP-9SmHnwGUYKjxd7FmylxU8/edit#
Rapporten opdateres med resultater ifbm. #91


Fix context example code - tea, milk and honey

The intent_handler and corresponding function were mismatched.
Changed self.milk = true to indicate wanting milk, rather than not wanting
Added context modification to YesMilkIntent handler

Nice pickup @krisgesling. Terima kasih!
LGTM, merging.


Replaced question.md issue-template with contact_links (fix bom)

Followup to #4912

We could only test it after merge? Or maybe at a fork?
I see the indents on https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser, so not sure if this would fix things

Yes testing it now. there is some BOM-issue

now it works

Yes indeed! Nice!