dspace create-administrator loop after yes

After there was a database issue, every access to the database did throw an error. (Was ill, and the old admin found a mistake that all files bigger than 1MB could not get uploaded, i think might have been a tomcat issue. He started to delete wrong unused files. Then the dspace installation was suddenly not working and giving all the time an error.) Not sure if there an autoupgrade of postgres happened. I decided to delete the database and make it new. After the install instructions.
However when I started dspace create-administrator It never finishes it, after the y for yes, he is in an endless loop.
Therefore I cannot Login.
Is there a postgres direct command line to create the admin for dspace?
System debain
Backend version 7.1.1*
Flyway 6.5.7
Postgres 13.5
maven 3.6.3-5
tomcat9 9.0.43-2
To Reproduce
Steps to reproduce the behavior:

Drop database
createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
psql --username=postgres dspace
CREATE SCHEMA extensions;
CREATE EXTENSION pgcrypto SCHEMA extensions;
GRANT USAGE ON SCHEMA extensions TO dspace;
SELECT set_config('search_path',current_setting('search_path') || ',extensions',false) WHERE current_setting('search_path') !~ '(^|,)extensions(,|$)';
ALTER DATABASE dspace SET search_path FROM CURRENT;
[dspace]/bin/dspace database migrate
[dspace]/bin/dspace create-administrator

Tried with running dspace instance and running tomcat and solr, and also with everything not running
Expected behavior
create Database user
Related work
Issue 8083
This is the tail of dspace.log
2022-02-24 14:31:23,743 WARN  unknown unknown org.hibernate.cfg.annotations.EntityBinder @ HHH000482: @org.hibernate.annotations.Cache used on a non-root entity: ignored for [org.dspace.content.Site]. Please see the Hibernate documentation for proper usage.
2022-02-24 14:31:23,746 WARN  unknown unknown org.hibernate.cfg.annotations.EntityBinder @ HHH000482: @org.hibernate.annotations.Cache used on a non-root entity: ignored for [org.dspace.eperson.EPerson]. Please see the Hibernate documentation for proper usage.
2022-02-24 14:31:23,749 WARN  unknown unknown org.hibernate.cfg.annotations.EntityBinder @ HHH000482: @org.hibernate.annotations.Cache used on a non-root entity: ignored for [org.dspace.eperson.Group]. Please see the Hibernate documentation for proper usage.
2022-02-24 14:31:24,242 WARN  unknown unknown org.hibernate.orm.cache @ HHH90001007: Using legacy cache name [org.hibernate.cache.spi.UpdateTimestampsCache] because configuration could not be found for cache [default-update-timestamps-region]. Update your configuration to rename cache [org.hibernate.cache.spi.UpdateTimestampsCache] to [default-update-timestamps-region].
2022-02-24 14:31:24,244 WARN  unknown unknown org.hibernate.orm.cache @ HHH90001007: Using legacy cache name [org.hibernate.cache.internal.StandardQueryCache] because configuration could not be found for cache [default-query-results-region]. Update your configuration to rename cache [org.hibernate.cache.internal.StandardQueryCache] to [default-query-results-region].
2022-02-24 14:31:24,296 INFO  unknown unknown org.hibernate.validator.internal.util.Version @ HV000001: Hibernate Validator 6.0.18.Final
2022-02-24 14:31:56,772 INFO  unknown unknown org.dspace.eperson.EPersonServiceImpl @ anonymous::create_eperson:eperson_id=7a5bed27-f3a7-41a3-9054-a2ad769dc755
2022-02-24 14:31:57,142 INFO  unknown unknown org.dspace.eperson.PasswordHash @ Initialized a random number stream using NativePRNG provided by {Signature.SHA256withDSA KeySize=2048, Alg.Alias.Signature.2.16.8<IP_ADDRESS>.4.3.1=SHA224withDSA, Alg.Alias.Signature.2.16.8<IP_ADDRESS>.4.3.2=SHA256withDSA, Alg.Alias.KeyPairGenerator.1.2.840.10040.4.1=DSA, Alg.Alias.AlgorithmParameterGenerator.1.2.840.10040.4.1=DSA, CertPathValidator.PKIX=sun.security.provider.certpath.PKIXCertPathValidator, Alg.Alias.KeyPairGenerator.OID.1.2.840.10040.4.1=DSA, KeyStore.JKS=sun.security.provider.JavaKeyStore$DualFormatJKS, SecureRandom.NativePRNG ThreadSafe=true, MessageDigest.SHA-256 ImplementedIn=Software, MessageDigest.SHA-512/224=sun.security.provider.SHA5$SHA512_224, MessageDigest.SHA-512/224 ImplementedIn=Software, Alg.Alias.Signature.SHA1/DSA=SHA1withDSA, CertStore.com.sun.security.IndexedCollection ImplementedIn=Software, Alg.Alias.CertificateFactory.X509=X.509, Alg.Alias.Signature.SHA-1/DSA=SHA1withDSA, Signature.SHA224withDSA=sun.security.provider.DSA$SHA224withDSA, MessageDigest.SHA3-384=sun.security.provider.SHA3$SHA384, Signature.SHA256withDSA ImplementedIn=Software, Signature.SHA1withDSA SupportedKeyClasses=java.security.interfaces.DSAPublicKey|java.security.interfaces.DSAPrivateKey, Signature.SHA224withDSA SupportedKeyClasses=java.security.interfaces.DSAPublicKey|java.security.interfaces.DSAPrivateKey, Alg.Alias.Signature.OID.2.16.8<IP_ADDRESS>.4.3.2=SHA256withDSA, Alg.Alias.Signature.OID.2.16.8<IP_ADDRESS>.4.3.1=SHA224withDSA, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.1=SHA-256, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.3=SHA-512, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.2=SHA-384, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.5=SHA-512/224, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.4=SHA-224, Alg.Alias.Signature.DSAWithSHA1=SHA1withDSA, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.7=SHA3-224, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.6=SHA-512/256, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.9=SHA3-384, Alg.Alias.KeyFactory.<IP_ADDRESS>.2.12=DSA, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.8=SHA3-256, Alg.Alias.Signature.RawDSA=NONEwithDSA, MessageDigest.SHA=sun.security.provider.SHA, CertPathBuilder.PKIX=sun.security.provider.certpath.SunCertPathBuilder, Signature.NONEwithDSA KeySize=1024, Provider.id version=11, AlgorithmParameters.DSA ImplementedIn=Software, MessageDigest.SHA-512/256 ImplementedIn=Software, CertificateFactory.X.509 ImplementedIn=Software, Alg.Alias.AlgorithmParameters.<IP_ADDRESS>.2.12=DSA, Provider.id info=SUN (DSA key/parameter generation; DSA signing; SHA-1, MD5 digests; SecureRandom; X.509 certificates; PKCS12, JKS & DKS keystores; PKIX CertPathValidator; PKIX CertPathBuilder; LDAP, Collection CertStores, JavaPolicy Policy; JavaLoginConfig Configuration), CertPathBuilder.PKIX ValidationAlgorithm=RFC5280, Provider.id className=sun.security.provider.Sun, MessageDigest.SHA-512 ImplementedIn=Software, MessageDigest.SHA-224=sun.security.provider.SHA2$SHA224, CertPathBuilder.PKIX ImplementedIn=Software, SecureRandom.NativePRNGNonBlocking ThreadSafe=true, MessageDigest.SHA3-256=sun.security.provider.SHA3$SHA256, AlgorithmParameterGenerator.DSA ImplementedIn=Software, Alg.Alias.MessageDigest.<IP_ADDRESS>.2.26=SHA, AlgorithmParameters.DSA=sun.security.provider.DSAParameters, SecureRandom.SHA1PRNG=sun.security.provider.SecureRandom, MessageDigest.SHA3-224 ImplementedIn=Software, Provider.id name=SUN, MessageDigest.MD2=sun.security.provider.MD2, MessageDigest.MD5=sun.security.provider.MD5, KeyFactory.DSA=sun.security.provider.DSAKeyFactory, KeyPairGenerator.DSA KeySize=2048, SecureRandom.NativePRNG=sun.security.provider.NativePRNG, SecureRandom.NativePRNGNonBlocking=sun.security.provider.NativePRNG$NonBlocking, MessageDigest.SHA-512=sun.security.provider.SHA5$SHA512, SecureRandom.DRBG ImplementedIn=Software, Signature.SHA1withDSA KeySize=1024, SecureRandom.SHA1PRNG ThreadSafe=true, Alg.Alias.AlgorithmParameterGenerator.OID.1.2.840.10040.4.1=DSA, Alg.Alias.AlgorithmParameterGenerator.<IP_ADDRESS>.2.12=DSA, MessageDigest.MD2 ImplementedIn=Software, Signature.NONEwithDSA=sun.security.provider.DSA$RawDSA, Signature.SHA224withDSA ImplementedIn=Software, Alg.Alias.Signature.DSS=SHA1withDSA, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.10=SHA3-512, Alg.Alias.Signature.<IP_ADDRESS>.2.13=SHA1withDSA, Signature.SHA1withDSA=sun.security.provider.DSA$SHA1withDSA, CertificateFactory.X.509=sun.security.provider.X509Factory, Signature.NONEwithDSA ImplementedIn=Software, KeyStore.DKS ImplementedIn=Software, KeyStore.DKS=sun.security.provider.DomainKeyStore$DKS, Alg.Alias.Signature.OID.1.2.840.10040.4.3=SHA1withDSA, Signature.SHA256withDSAinP1363Format=sun.security.provider.DSA$SHA256withDSAinP1363Format, MessageDigest.SHA3-512=sun.security.provider.SHA3$SHA512, Alg.Alias.MessageDigest.SHA-1=SHA, MessageDigest.SHA3-512 ImplementedIn=Software, MessageDigest.SHA-384 ImplementedIn=Software, KeyStore.JKS ImplementedIn=Software, Alg.Alias.Signature.DSA=SHA1withDSA, Signature.NONEwithDSA SupportedKeyClasses=java.security.interfaces.DSAPublicKey|java.security.interfaces.DSAPrivateKey, Signature.SHA224withDSA KeySize=2048, Alg.Alias.AlgorithmParameters.OID.1.2.840.10040.4.1=DSA, KeyStore.PKCS12=sun.security.pkcs12.PKCS12KeyStore$DualFormatPKCS12, Alg.Alias.Signature.SHAwithDSA=SHA1withDSA, SecureRandom.SHA1PRNG ImplementedIn=Software, MessageDigest.SHA-256=sun.security.provider.SHA2$SHA256, KeyStore.CaseExactJKS=sun.security.provider.JavaKeyStore$CaseExactJKS, Policy.JavaPolicy=sun.security.provider.PolicySpiFile, Alg.Alias.MessageDigest.SHA1=SHA, MessageDigest.SHA-224 ImplementedIn=Software, Signature.SHA1withDSAinP1363Format=sun.security.provider.DSA$SHA1withDSAinP1363Format, KeyFactory.DSA ImplementedIn=Software, SecureRandom.DRBG=sun.security.provider.DRBG, MessageDigest.SHA3-224=sun.security.provider.SHA3$SHA224, CertStore.com.sun.security.IndexedCollection=sun.security.provider.certpath.IndexedCollectionCertStore, CertStore.Collection=sun.security.provider.certpath.CollectionCertStore, Signature.SHA1withDSA ImplementedIn=Software, AlgorithmParameterGenerator.DSA KeySize=2048, Alg.Alias.Signature.SHA/DSA=SHA1withDSA, CertPathValidator.PKIX ValidationAlgorithm=RFC5280, MessageDigest.SHA-384=sun.security.provider.SHA5$SHA384, KeyStore.CaseExactJKS ImplementedIn=Software, CertPathValidator.PKIX ImplementedIn=Software, Alg.Alias.Signature.1.2.840.10040.4.3=SHA1withDSA, MessageDigest.SHA ImplementedIn=Software, MessageDigest.MD5 ImplementedIn=Software, Configuration.JavaLoginConfig=sun.security.provider.ConfigFile$Spi, KeyPairGenerator.DSA ImplementedIn=Software, Alg.Alias.KeyFactory.1.2.840.10040.4.1=DSA, MessageDigest.SHA3-384 ImplementedIn=Software, SecureRandom.NativePRNGBlocking ThreadSafe=true, Alg.Alias.Signature.<IP_ADDRESS>.2.27=SHA1withDSA, Alg.Alias.KeyPairGenerator.<IP_ADDRESS>.2.12=DSA, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.1=SHA-256, AlgorithmParameterGenerator.DSA=sun.security.provider.DSAParameterGenerator, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.3=SHA-512, SecureRandom.DRBG ThreadSafe=true, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.2=SHA-384, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.5=SHA-512/224, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.4=SHA-224, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.7=SHA3-224, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.6=SHA-512/256, MessageDigest.SHA3-256 ImplementedIn=Software, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.9=SHA3-384, Alg.Alias.MessageDigest.2.16.8<IP_ADDRESS>.4.2.8=SHA3-256, Alg.Alias.AlgorithmParameters.1.2.840.10040.4.1=DSA, MessageDigest.SHA-512/256=sun.security.provider.SHA5$SHA512_256, Signature.NONEwithDSAinP1363Format=sun.security.provider.DSA$RawDSAinP1363Format, Alg.Alias.MessageDigest.OID.<IP_ADDRESS>.2.26=SHA, Signature.SHA256withDSA=sun.security.provider.DSA$SHA256withDSA, Signature.SHA224withDSAinP1363Format=sun.security.provider.DSA$SHA224withDSAinP1363Format, CertStore.Collection ImplementedIn=Software, Alg.Alias.KeyFactory.OID.1.2.840.10040.4.1=DSA, Signature.SHA256withDSA SupportedKeyClasses=java.security.interfaces.DSAPublicKey|java.security.interfaces.DSAPrivateKey, Alg.Alias.MessageDigest.OID.2.16.8<IP_ADDRESS>.4.2.10=SHA3-512, KeyPairGenerator.DSA=sun.security.provider.DSAKeyPairGenerator$Current, SecureRandom.NativePRNGBlocking=sun.security.provider.NativePRNG$Blocking}
2022-02-24 14:31:57,158 INFO  unknown unknown org.dspace.eperson.EPersonServiceImpl @ anonymous::update_eperson:eperson_id=7a5bed27-f3a7-41a3-9054-a2ad769dc755
2022-02-24 14:31:57,197 INFO  unknown unknown org.dspace.eperson.GroupServiceImpl @ anonymous::update_group:group_id=1497fe3b-a4de-41e2-b18e-517524b8c245

@WolfgangT71 : Please check you dspace.log and the PostgreSQL log file for any errors that occur when you attempt to login.  Additionally, you should check if errors were reported in the dspace.log when you ran ./dspace database migrate.
It sounds likely that some part of the dspace database migrate failed and reported something in the logs.  That failure could then result in create-administrator not working properly.  But, it's impossible to say what the fix may be without knowing what error may have occurred during the migrate or similar.

postgres.log
2022-02-25 06:35:51.125 UTC [13404] LOG:  starting PostgreSQL 13.5 (Debian 13.5-0+deb11u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit 2022-02-25 06:35:51.126 UTC [13404] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432 2022-02-25 06:35:51.127 UTC [13404] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2022-02-25 06:35:51.133 UTC [13405] LOG:  database system was shut down at 2022-02-25 06:35:33 UTC 2022-02-25 06:35:51.144 UTC [13404] LOG:  database system is ready to accept connections 2022-02-25 06:36:27.704 UTC [13521] dspace@dspace FATAL:  database "dspace" does not exist 2022-02-25 06:36:27.812 UTC [13522] dspace@dspace FATAL:  database "dspace" does not exist 2022-02-25 06:44:35.925 UTC [13571] postgres@dspace ERROR:  extension "pgcrypto" already exists 2022-02-25 06:44:35.925 UTC [13571] postgres@dspace STATEMENT:  CREATE EXTENSION pgcrypto SCHEMA extensions; 2022-02-25 06:53:30.601 UTC [13800] dspace@dspace LOG:  could not receive data from client: Connection reset by peer 2022-02-25 06:53:30.603 UTC [13799] dspace@dspace LOG:  could not receive data from client: Connection reset by peer 2022-02-25 06:54:54.490 UTC [13840] dspace@dspace LOG:  could not receive data from client: Connection reset by peer 2022-02-25 06:54:54.490 UTC [13839] dspace@dspace LOG:  could not receive data from client: Connection reset by peer 2022-02-25 07:12:44.711 UTC [16508] dspace@dspace LOG:  could not receive data from client: Connection reset by peer 2022-02-25 07:12:44.713 UTC [16507] dspace@dspace LOG:  could not receive data from client: Connection reset by peer

The dspace.log as zip.
dspace.zip
Tried everything again, including a mvn package and a fresh_install. Cleaned all log files before I started again. Still the same result.

Just to make sure did not change to backend 7.2 will try this on monday.

@WolfgangT71 : Your dspace.log shows a lot of ERROR lines that say DSpace cannot connect to your Solr instance. For example:
2022-02-25 06:54:44,089 ERROR unknown unknown org.dspace.discovery.SolrSearchCore @ Error while initializing solr server
org.apache.solr.client.solrj.SolrServerException: Server refused connection at: http://localhost:8983/solr/search

DSpace requires Solr to be functional, otherwise you may see very odd behavior.

ok, solr went down, when reinstalling the configsets, needed some permission corrections. But that was not the problem. could try to give ownership to tomcat instead of solr. But solr is now reachable from the web. Problem with create-administrator persists. Will update to 7.2. And drop database again. Will report back later.

7.2 also not working, is it working already with Postgres 13.5?

What are tested postgres versions, for the main branch of 7.2?

So tried now to install postgres 12.10 and still not working.
Solr is up and running.
This came by fresh_install
test_database:      [java] 2022-02-27 23:28:12,419 WARN  org.dspace.servicemanager.DSpaceServiceManager @ Unable to locate bean by name or id=database. Will try to look up bean by type next.      [java] org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'database' available      [java] 	at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:808) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]      [java] 	at org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1279) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]      [java] 	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:297) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]      [java] 	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:207) ~[spring-beans-5.2.5.RELEASE.jar:5.2.5.RELEASE]      [java] 	at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1114) ~[spring-context-5.2.5.RELEASE.jar:5.2.5.RELEASE]      [java] 	at org.dspace.servicemanager.DSpaceServiceManager.getServiceByName(DSpaceServiceManager.java:426) [dspace-services-7.2.jar:7.2]      [java] 	at org.dspace.scripts.ScriptServiceImpl.getScriptConfiguration(ScriptServiceImpl.java:33) [dspace-api-7.2.jar:7.2]      [java] 	at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) [dspace-api-7.2.jar:7.2]      [java] 	at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98) [dspace-api-7.2.jar:7.2]      [java]       [java] Attempting to connect to database      [java] Connected successfully!      [java]       [java] Database Type: postgres      [java] Database URL: jdbc:postgresql://localhost:5432/dspace      [java] Database Schema: public      [java] Database Username: dspace      [java] Database Software: PostgreSQL version 12.10 (Debian 12.10-1.pgdg110+1)      [java] Database Driver: PostgreSQL JDBC Driver version 42.2.25      [java] PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)      [java] FlywayDB Version: 6.5.7      [java] 2022-02-27 23:28:13,087 WARN  org.dspace.services.sessions.StatelessRequestServiceImpl @ Request interceptor (org.dspace.services.events.SystemEventService$EventRequestInterceptor@5ebefaeb) failed to execute on end (request-303-1646004492448): null

postgresql.log
2022-02-27 23:18:22.807 UTC [52306] LOG:  starting PostgreSQL 12.10 (Debian 12.10-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit 2022-02-27 23:18:22.807 UTC [52306] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432 2022-02-27 23:18:22.809 UTC [52306] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2022-02-27 23:18:22.858 UTC [52307] LOG:  database system was shut down at 2022-02-27 23:18:22 UTC 2022-02-27 23:18:22.877 UTC [52306] LOG:  database system is ready to accept connections 2022-02-27 23:28:13.132 UTC [53220] dspace@dspace LOG:  could not receive data from client: Connection reset by peer 2022-02-27 23:28:13.133 UTC [53219] dspace@dspace LOG:  could not receive data from client: Connection reset by peer 2022-02-27 23:30:13.057 UTC [53264] dspace@dspace LOG:  could not receive data from client: Connection reset by peer 2022-02-27 23:30:13.057 UTC [53263] dspace@dspace LOG:  could not receive data from client: Connection reset by peer

dspace.log
dspace.zip

I can reach it from outside. But not from localhost.

http://dspace.umiz.at:8983/solr/#/search/core-overview
Can reach it like this, but only as my ip Addresses are given free to reach it.

If I start
http://localhost:8983/solr/search/select)
I get when saved:
{   "responseHeader":{     "status":0,     "QTime":3,     "params":{}},   "response":{"numFound":0,"start":0,"numFoundExact":true,"docs":[]   }}

Newest log file, no solr errors in it.
dspace.zip

But still not working

Just to check, I tried installing postgresql 14 with contrib, than the solr errors are reappearing again.
But also had the errors with postgresql 13.
Problem might be that in my system only 13 and 14 have contrib, v 12 does not have a matching contrib to install.

I currently do all of my DSpace development and testing with PostgreSQL v13.5.
The WARNing "Unable to locate bean by name or id=database. Will try to look up bean by type next." is expected in this context.
The connection test appears to succeed, and seems to be giving reasonable values for the connection parameters.
The WARNing "Request interceptor (org.dspace.services.events.SystemEventService$EventRequestInterceptor@5ebefaeb) failed to execute on end (request-303-1646004492448): null " is one that I always see when installing.  I've not spent the time to find out where this interceptor is or why it is not executing, because it seems not to be a problem.
I don't see any relevant messages in the latest attached dspace.log.  You may have to step through the create-administrator code with a debugger to identify the problem.  (We should be logging something -- this is a second problem.)

@WolfgangT71 : Like @mwoodiupui noted, I don't see any obvious issues based on the logs you've provided.  What you want to be looking for are any log lines that are of an ERROR or FATAL status...especially when you attempt to run the command that isn't working for you.  Make sure to check ALL the relevant logs (DSpace, Tomcat, Postgres, Solr, etc)...as it's possible the issue could be logged in any of those areas.
I'd highly recommend reviewing our Troubleshooting guide if you need help finding error messages in logs:
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)
Also, please keep in mind that normally we do NOT use GitHub Issues for support questions. Instead, support is available through one of the support options at https://wiki.lyrasis.org/display/DSPACE/Support  For technical support, we recommend using (and searching) our Tech Support mailing list (https://groups.google.com/d/forum/dspace-tech) -- as that ensures that others can help out if they've hit a similar issue.  It's also a good place to search if you discover an odd error message, in case someone else has already found a way to solve that problem.
As we are not able to reproduce this issue, I'm going to close this ticket as "cannot reproduce".  If you need further help, use one of our Support options listed above.  But, please first try to find more information on the underlying error (as sending us logs to comb through makes it harder to help, as we all provide support in our volunteer time).  If we later find that there's an actual bug in the codebase, we can always reopen this ticket as needed.


Chainweaver in Browser, Testnet Account

Chainweaver download links are difficult to find, and most tutorials already focus on the browser version of the software.
I have rewritten the tutorial to take this into account, and link to the download link as an option.
Added 3 more steps describing how to add the account that received the KDA faucet to Chainweaver.

Thank you for your contribution. We will have a look at it asap.


SteemJS streamOperations is returning a error code 301 for the ws connection.

Expected behavior
steem.api.streamOperations(function (err, operations) { ...}
normally returns all streaming operations.
Actual behavior
It is currently returning the following error:
WebSocket connection to 'wss://steemit.com/wspa' failed: Error during WebSocket handshake: Unexpected response code: 301
How to reproduce
run the example Stream.html from the release, or any product using the same stream.api like (https://autosteem.learnthis.ca)
The error code occurs immediately.  I've tried with the latest 0.4.7 in releases as well.

It seem that the websocket on Steemit just moved. Please try using this ond instead: wss://steemd.steemit.com

I'm currently experiencing this issue


Fix spelling in hooks error message

I was writing some tests for a hook that throws inside of a selector and I ran into this little suggestion via my code spell checker:

So here we are! 😅

Thanks!

(well now my test is gonna break haha)
Thanks for the quick feedback


Plugins and Application root

Bevy has something called plugins which go something like this...
var app = new Application();
app.AddPlugin(MyPlugin);
app.Run();

public void MyPlugin(Application app)
{
    app.AddSystem(...);
}

What's their purpose?

@genaray plugins allow people to add systems and other plugins to the world.

This seems trivial to add using extension methods and a couple of interfaces, I don't think that this needs to be part of the core library.

ok


Add error screen for collections with configurations unsupported by the UI

Description
This adds a UI screen for when a collection response returned from the server contains valid configuration rules that cannot be displayed in the UI. Although these collections cannot be viewed or edited with the UI controls, their results can still be viewed and they can be attached to other collections.
This should occur rarely (or not at all) since the server checks most of these situations on create/edit, but this is a more user-friendly fallback instead of an error.
Follow ups

Work with UX and/or docs team on better wording for the specific error messages.
If possible, remove the "Edit" and "Clone" options from the header dropdown.

Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Navigate to a collection page with rules that are unsupported by the UI. Note that this can only be accomplished currently by creating the collection via the API, and only by creating a collection with rules for two different fields for the same entity type. (e.g. A single collection with a rule for "Namespace" and "Namespace Label".) The collection page will display the following UI. Collection results will still be able to be displayed.

The  "More info" section can expand to give details information on why the collection cannot be displayed. (Better error info is TBD.)

This collection can still be attached to other collections without error:

Viewing the collection in a modal will still display the error screen:

Current dependencies on/for this PR:

master

PR #3881   👈

This comment was auto-generated by Graphite.

/retest


[misc]: nextjs 15 metadata opengraph card image returns invalid content type

I understand that this issue may be closed if it should be filed in another category

[X] I understand

My issue
working on a dynamic web app using nextjs 15, in it i have decided to use the metadata function by nextjs to bump up the seo and in it opengraph and twitter card images. here is the sample code:
 openGraph: {     type: 'xxx',     url: 'xxx',     title: 'xxx',     description:       'xxx',     images: [       {         url: 'https://utfs.io/f/NQ1UkAeyXUbIyGzw9wCFCp1Fm627bgXMD4x3c8K9zjZqvLrl',         width: 1200,         height: 630,       },       {         url: 'https://utfs.io/f/NQ1UkAeyXUbIaxO68p167jviNgO80Zen4UQR2Yytc5Fw1fdl',         width: 600,         height: 315,       },     ],   },   twitter: {     card: 'xxx',     creator: 'xxx',     title: 'xxx',     description:       'xxx',     images: [       'https://utfs.io/f/NQ1UkAeyXUbIyGzw9wCFCp1Fm627bgXMD4x3c8K9zjZqvLrl',       'https://utfs.io/f/NQ1UkAeyXUbIaxO68p167jviNgO80Zen4UQR2Yytc5Fw1fdl',     ],   },
unfortunately, all the metadata is visible on both twitter and sites that use opengraph except fro the images.
on using Facebook Debugger  i am told that

it used to work up until recently around 12th November 2024 when uploadthing.com kinda went down for a few hours and when it got back, this stopped working.
Please help.

content type seems fine on that url?

uploadthing.com kinda went down for a few hours and when it got back, this stopped working.

I am not aware of any such outage, what makes you say this?

This file: https://utfs.io/f/NQ1UkAeyXUbNjlp9UeyXUb7StWz0vPDscg1LOToVwhxaQY - is not in our DB which means either it never existed or it was deleted more than a week ago
That's why it cannot be used as OG cause the URL returns a 404 not found page:

Closing as I don't see the issue here from our end, existing files are properly displayed as opengrah, and non-existing ones correctly 404s. If you believe otherwise feel free to open a new issue with more details


Previous issue closed too soon

Hello there,
Sorry to bother you again but my previous issue has not, in my eyes, been solved.
Could you look into it please?
Thanks ❤

Sorry, I do not have time to do support.


A few small changes to make project more visible

Please add the word 'functional' somewhere in the description, as well as a tag to make it easier to find on github. :)

@hengestone Added functional to project description, the latest release v0.12.3 is tagged.


some questions

Oh，i awite this project very much!
Can u teach me vuejs? I'm watching your project for long days, and i do not understand how can i use vuejs in my own project to better my project!
: )

However, we may not apply Vue.js to our project.


Removes SIGSTKFLT when cross-compiling to MIPS.

This is the only failing error when cross compiling to Tessel, which is a MIPS-based architecture.
Apparently libc does not have SIGSTKFLT (Term Stack fault on coprocessor) on this system, and indeed it does not have a coprocessor.
This commit should preserve the semantics for all other architectures. Potentially this can be inverted in the future if more platforms are added to only whitelist ARM, x86, x86_64, but I thought this conditional would suffice.

@fiveop Looks like this condition is not possible on MIPS as an architecture, so this change seems to make sense.  https://www.linux-mips.org/archives/linux-mips/2006-05/msg00345.html

I wish there was a better way to manage this (and there might be through macro magic), but I'm good with this change today in order to fix mips @homu r+
I still need to revisit getting the CI tests for MIPS to pass.  Until then, I would not say we officially support MIPS.  I would like to, of course.

:pushpin: Commit 1f2d896 has been approved by posborne

:zap: Test exempted - status

Thanks for finding the reference for this @posborne. If I can help with fixing the MIPS CI, lmk what I should look at.

If I can help with fixing the MIPS CI, lmk what I should look at.

Sure, that task is basically getting  CI passing.  The infrastructure built on top of docker is already present and you can run CI for mips by doing the following (also read https://github.com/nix-rust/nix/tree/master/ci):
 $ DOCKER_IMAGE=posborne/rust-cross:mips \
      RUST_VERSION=1.7.0 \
      RUST_TARGET=mips-unknown-linux-gnu ci/run-docker.sh


Hard to put a secret into a file

What are you trying to do?
I'm trying to put a secret into a file, but it's very hard because there's no function what makes it easier.
Why is this important to you?
No response
How are you currently working around this?
No response

@karak1974 Can you explain more of what you want to do?

Where does the secret come from? How generated?
Why do you want to store it in a file?
Where would the file be? On client (e.g. laptop, ci server) or file in a container in Dagger?
Is the file ephemeral (use and throw away) or will it be persisted (e.g. on your laptop, encrypted in a git repo)?
Would you store the secret decrypted or encrypted somehow?
Could you store the secret in a more ephemeral place like an environment variable?

Here are secrets docs: https://docs.dagger.io/1204/secrets/

related to #4366

This is related to 0.3 and with CUE. We will close this one since it is unrelated to the new version


MPW Design Description

@mithro
Design description for each MPW shuttle designs updated to resolve #32

As I mentioned previously, a person who views this repository shouldn't care about which MPW a design ran on.

@mithro currently, we have ~90 designs for four shuttles, if we keep this avg for mpw-6 we will add 20+ more and so on for each new shuttle. If we keep the current organization we will soon have over 100 subfolders under designs (even more under scripts) and a README with well over 1k lines. Do you think the current organization is ok?
I was thinking about changing the organization, either by creating mpw-X/design and mpw-X/scripts folders on the root of the repo or a subfolder under the existing folders design/mpw-X, scripts/mpw-X and have the README for each folder/shuttle -- however this organization might be opposed to your statement:

a person who views this repository shouldn't care about which MPW a design ran on.

@mithro currently, we have ~90 designs for four shuttles, if we keep this avg for mpw-6 we will add 20+ more and so on for each new shuttle. If we keep the current organization we will soon have over 100 subfolders under designs (even more under scripts) and a README with well over 1k lines. Do you think the current organization is ok?
I was thinking about changing the organization, either by creating mpw-X/design and mpw-X/scripts folders on the root of the repo or a subfolder under the existing folders design/mpw-X, scripts/mpw-X and have the README for each folder/shuttle -- however this organization might be opposed to your statement:

a person who views this repository shouldn't care about which MPW a design ran on.

@vvbandeira
If you're planning to split designs/mpw-x, then current description can be re-used easily.

Which MPW run these designs happened to be submitted on should not be relevant, hence I'm against using that information in any way to organize them.

@mithro
Updated design description in alphabetical order with commit c37ff10
@vvbandeira  FYI

@mithro
Please review and we can close this PR.

All the CI tests are failing?


Split ZDNS into a library and CLI tool

This PR exposes a new Resolver object so other go code can interact directly with ZDNS. /cli creates 1k worker threads, each with their own Resolver to resolve large sets of domains efficiently.
I'll add documentation of the new structure but want to get this PR merged since it's holding anything else up.

@zmap/zdns-maintainers This is ready for review but I would like to wait until we either merge or discard https://github.com/zmap/zdns/pull/370 before merging this.

@phillip-stephens just wanted to flag that I think this is in your camp at the moment as tests are currently failing :(

Let me actually run a linter against this. My next step after this is merged is setting up a linter CI, and that'll avoid 2 huge PR's 😄


Theme installation issue

Hello, it's my first time installing a theme for Ghost and I have some trouble doing it. I am stuck with my page showing up like this and I am unable to fix it, so here I am asking for your help. Thanks!

I think that all is ok, just you need to setup the cover image and other stuff.
Check the documentation. Also I just release a new version, so be sure that you have the last theme version (download again from releases section and replace the files).


Module not found: Can't resolve 'material-ui/CircularProgress'

It looks like the material-ui-next folks are considering flattening this particular component from the /Progress folder (where it is in my latest installed version) to the root.  The material-ui-image component is looking for it in the root of material-ui and it doesn't seem to be there in the 1.0 (37) version.

Thanks for reporting this issue, it was fixed in v1.0.0-pre.6, see #14


Sources for System.Configuration.Install

@terrajobst this is an assembly that we missed before, and was requested in dotnet/runtime#29643.

I'm just going to merge. It's already open by virtue of this PR.


Updated line-ids for DB Regio Nordost/Nord, HANS, ODEG, NEB, AKN, etc.

again new line-id for DB Regio Nordost/Nord, HANS, ODEG, NEB, AKN, etc.

At least for me, now both RB 23 operated by DB Regio Nordost are displayed with the same blue color, although the VBB RB 23 should have an orange color.

They have the same color, because they can not be distinguished anymore. Both are operated by db-regio-ag-nordost and have the same line id rb-22.
I haven't checked, but the same should apply for RE 4, RE 7 and RB 24 as this name is used for two different routes each by DB Regio Nordost.


AttributeError: 'NoneType' object has no attribute 'expandtabs'

Rasa Core version:
0.12.0a4
Python version:
Python 2.7.15
Operating system (windows, osx, ...):
Ubuntu (Docker)
Issue:
I have a custom button for Facebook Messenger. However, when trying to train my dialogue model interactively, it seems to break when these buttons are uttered.
Here's the button snippet, I use to render products on Messenger:
class ActionSearchItems(Action, ShoppingActions):
    def name(self):
        # define the name of the action which can then be included in training stories
        return "action_search_items"

    def run(self, dispatcher, tracker, domain):
        products = ShoppingActions.search_products(client, items, max_products=3)
        elements = [
            {
                "title": product["name"],
                "subtitle": "Product",  # workaround for cmdline button interpretation
                "image_url": product["imageUrl"]["primary"],
                "buttons": [
                    {
                        "type": "postback",
                        "title": "+ " + product["name"],
                        "payload": '/user.selected_products{"products": ["' + str(product['id']) + '"]}',
                    },
                ]
            } for product in products
        ]

        dispatcher.utter_custom_message(*elements)

However, when running this action in the interactive training mode, I get this error:
? The bot wants to run 'action_search_items', correct?  Yes
2018-11-11 13:03:27 ERROR    rasa_core.training.interactive  - An exception occurred while recording messages.
Traceback (most recent call last):
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 1078, in record_messages
    finetune, sender_ids, plot_file)
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 728, in _predict_till_next_listen
    _print_history(sender_id, endpoint)
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 394, in _print_history
    table = _chat_history_table(evts)
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 477, in _chat_history_table
    wrapped = wrap(format_bot_output(evt), bot_width(table))
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 417, in wrap
    replace_whitespace=False))
  File "/opt/conda/envs/env/lib/python2.7/textwrap.py", line 354, in wrap
    return w.wrap(text)
  File "/opt/conda/envs/env/lib/python2.7/textwrap.py", line 325, in wrap
    text = self._munge_whitespace(text)
  File "/opt/conda/envs/env/lib/python2.7/textwrap.py", line 154, in _munge_whitespace
    text = text.expandtabs()
AttributeError: 'NoneType' object has no attribute 'expandtabs'
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/opt/conda/envs/env/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/opt/conda/envs/env/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 1078, in record_messages
    finetune, sender_ids, plot_file)
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 728, in _predict_till_next_listen
    _print_history(sender_id, endpoint)
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 394, in _print_history
    table = _chat_history_table(evts)
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 477, in _chat_history_table
    wrapped = wrap(format_bot_output(evt), bot_width(table))
  File "/opt/conda/envs/env/lib/python2.7/site-packages/rasa_core/training/interactive.py", line 417, in wrap
    replace_whitespace=False))
  File "/opt/conda/envs/env/lib/python2.7/textwrap.py", line 354, in wrap
    return w.wrap(text)
  File "/opt/conda/envs/env/lib/python2.7/textwrap.py", line 325, in wrap
    text = self._munge_whitespace(text)
  File "/opt/conda/envs/env/lib/python2.7/textwrap.py", line 154, in _munge_whitespace
    text = text.expandtabs()
AttributeError: 'NoneType' object has no attribute 'expandtabs'

Thanks for raising this issue, @EPedrotti  will get back to you about it soon.

Not sure if that info helps, but what I find interesting is that when running core in debug mode, the buttons are just rendered as a dict, which works great.

I think I just accidentally found the key issue. It is the button_to_string function in channel.py:
def button_to_string(button, idx=0):
    """Create a string representation of a button."""
    return "{idx}: {title} ({val})".format(
            idx=idx + 1, title=button['title'], val=button['payload'])

When formatting the string, it causes an error for buttons that don't have a title and / or payload. Can we replace this with something more generic? Maybe just:
def button_to_string(button, idx=0):
    """Create a string representation of a button."""
    return "{idx}: {button}".format(
            idx=idx + 1, button=json.dumps(button))

That would only require the button to be json serializable, which I think would be necessary anyway for most scenarios.

Created a PR for this.

I found a few more related issues affecting output of (custom) buttons / elements in interactive mode. Will include them in PR as well.


Docker image no longer accessible

Looks like the docker image is gone:
Unable to find image 'ghcr.io/chevere/xrdebug:latest' locally
docker: Error response from daemon: Head "https://ghcr.io/v2/chevere/xrdebug/manifests/latest": denied.

https://github.com/xrdebug/xrdebug/pkgs/container/xrdebug


Run all tests on travis

Setup travis and create a test profile with the right config so we can run the vmq_diversity  database tests.

Ready for review.

LGTM!

That was fast! ;)


Improve comments in heartbeats.py

Mostly very minor changes to make the comments more consistent and easier to follow.

@hofaflo do you know what's up with the ImportError: numpy.core.multiarray failed to import?

Not sure what the reason is exactly, but I've found out the following things:
The wheel is built using the most recent version of numpy on each Python version (1.21 for 3.7, 1.22 for 3.8/3.9). For testing, numba is installed, which will support NumPy 1.21 only on its next release, so NumPy is downgraded to 1.20.x. The message RuntimeError: module compiled against API version 0xf but this version of numpy is 0xe is probably there because of some incompatible change in the NumPy C-API from 1.21 to 1.22. Limiting the NumPy version used for building the wheels in pyproject.toml to something below 1.22 (e.g. 'numpy<=1.21.5') fixes the issue for Python 3.8 on Windows.

Limiting the NumPy version used for building the wheels in pyproject.toml to something below 1.22 (e.g. 'numpy<=1.21.5') fixes the issue for Python 3.8 on Windows.

Do you want to push this as a hotfix until Numba properly supports the latest Numpy?

The wheels on conda and PyPI were built with NumPy 1.21, so we don't need a hotfix release, but for the upcoming minor release it would make sense, yes!

OK - can you push the required changes? Then we should merge this hotfix before any other PRs, because otherwise we don't have any tests.

Done, thanks @cbrnr!


♻ Refactor logic module into package

Refactor logic module into package in preparation for adding issues logic.

please review :)

Codecov Report

Merging #16 (25eeaf6) into main (600f9ca) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #16   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         9    +3
  Lines          368       375    +7
  Branches        61        61
=========================================
+ Hits           368       375    +7

Impacted Files
Coverage Δ

src/logic/__init__.py
100.00% <100.00%> (ø)

src/logic/base.py
100.00% <100.00%> (ø)

src/logic/models.py
100.00% <100.00%> (ø)

src/logic/prs.py
100.00% <100.00%> (ø)

Continue to review full report in Codecov by Sentry.

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


Keras does not verify supports_masking

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): OS X Mojave
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): "pip install"
TensorFlow version (use command below): v2.0.0-rc2-26-g64c3d382ca 2.0.0
Python version: 3.7.4
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the current behavior
I add an Embedding layer with mask_zero=True. Then I add another layer, either Flatten or GlobalAvgPool1D or GlobalMaxPool1D.
Of these, only GlobalAvgPool1D supports masking.
But when I compile and fit the model, no error is raised. (I believe in the past, prior to TF 2.0, an error would be raised.)
Describe the expected behavior
An error should be raised when using a layer that doesn't support masking on top of a layer that performs masking.
Code to reproduce the issue
Code for repro: https://github.com/asadovsky/nn/blob/master/text_classification.py
When setting "arch" to "max_pool" or "flatten", the train_and_evaluate_model(hp) function should raise an error. But instead, no error is raised.

Issue replicating for TF-2.0, kindly find the gist of colab.Thanks!

Could reproduce the issue, i.e., No error is being raised  when  "arch" is set to "max_pool" or "flatten", with Tensorflow Version 2.0. However, in 1.14, the error,
TypeError: Layer global_max_pooling1d does not support masking, but was passed an input_mask: Tensor("embedding/NotEqual:0", shape=(?, 4), dtype=bool), is being raised.
Here is the Gist. Thanks!

This is still true for TF 2.1 Notably the following example
import numpy as np
import tensorflow as tf

m = tf.keras.Sequential([
    tf.keras.layers.Masking(.0),
    tf.keras.layers.GlobalMaxPool1D(),
])
print(m(np.array([[[0.]]], np.float32))._keras_mask)

produces None on both TF 2.0 and TF 2.1.
Therefore, the model silently ignores the mask! Therefore, if it would be used in training, silently the training would be performed on all elements instead of on the non-masked only.

Also, as mentioned in #28143, TF 2.0.0-alpha0 was raising and error.

@omalleyt12 do you remember if we implicitly swallow it?

Reading through the code, we did make a change to implicitly mark output mask to be None when support_masking=False, whereas we previously errors out. The commit is here.
I'm not sure what's the reasoning behind it. Re-assigning to author of that commit.

A gentle bump after two months of inactivity.

@asadovsky
I ran the code on tf-nightly and do not face any error, please refer to this gist and please confirm if we may move this issue to closed status

@saduf2019 Not raising an error is actually the problem -- GlobalMaxPool1D does not support masking, so when getting masked input it used to (I am sure it did so with TF 2.0.0-alpha0) raise an exception. With the current behaviour, you are not warned when you construct an invalid model.
So the issue is still unchanged from when it was reported.

Was able to reproduce this issue in TF 2.6.0-dev20210527 ,please find the gist here..Thanks !

I could reproduce the issue with TF 2.6 .Please, find the gist here.Thanks!

Hi There,
This is a stale issue. As you are using an older version of tensorflow, we are checking to see if you still need help on this issue. Please test the issue with the latest TensorFlow (TF2.7 and tf-nightly). If the issue still persists with the newer versions of TF, please feel free to open it in keras-team/keras repository by providing details about the issue and a standalone code to reproduce the issue. Thanks!
Please note that Keras development has moved to a separate Keras-team/keras repository to focus entirely on only Keras. Thanks!


compatibility char against keycodes

I'll create a new one, i've to stash commits 5fe1e8a and 975e7f7


Add Tailwind CSS

Add Tailwind CSS
To close this issue the following must be done:

[ ] Install Tailwind CSS

Install tailwindcss and its peer dependencies via npm, and then run the init command to generate both tailwind.config.js and postcss.config.js.

[ ] Configure your template paths

Add the paths to all of your template files in your tailwind.config.js file.

[ ]  Add the Tailwind directives to your CSS

Add the @tailwind directives for each of Tailwind’s layers to your ./styles/globals.css file.

Relevant documentation

Tailwind Website
Nextjs Tailwind guide

Happy hacking 😎✨

Add Tailwind CSS
To close this issue the following must be done:

[ ] Install Tailwind CSS

Install tailwindcss and its peer dependencies via npm, and then run the init command to generate both tailwind.config.js and postcss.config.js.

[ ] Configure your template paths

Add the paths to all of your template files in your tailwind.config.js file.

[ ]  Add the Tailwind directives to your CSS

Add the @tailwind directives for each of Tailwind’s layers to your ./styles/globals.css file.

Relevant documentation

Tailwind Website
Nextjs Tailwind guide

Happy hacking 😎✨


Doesn't work if the source is not in src/**/*.rs

cargo-mutants currently assumes that src/**/*.rs will find all the source files in a tree, which is typical but not necessarily true for Rust source trees. https://github.com/Nukesor/pueue is one example where it is not true.
Perhaps a better approach here is to look at the output of cargo metadata to find out where the source is? Or, possibly to look at the commands that are run during a build in the source tree...
https://github.com/sourcefrog/cargo-mutants/blob/687590c4ac231fccdb8814f7af170f1164ab246e/src/source.rs#L95-L122

It seems like this is in cargo metadata but it will need some filtering to distinguish the crate we actually want to test from all its dependencies or from other crates in the same workspace.
For instance in cargo-mutants today it's at .packages[11].targets[0].src_path.
How do we know which package? The package dict has a manifest_path at .packages[11].manifest_path that shows it's in this directory...

Fixed in 0.2.6


chokidar watch fails

environment:
os: ubuntu 13.10
iojs: v1.8.1
chokidar:v1.0.1

erros
[2015-05-09 21:42:22.923] [ERROR] console -  Caught exception: SYSTEM_ERROR: watch ENOSPC
    at exports._errnoException (util.js:749:11)
    at FSWatcher.start (fs.js:1228:11)
    at Object.fs.watch (fs.js:1254:11)
    at createFsWatchInstance (/home/xxx/node_modules/chokidar/lib/nodefs-handler.js:37:15)
    at setFsWatchListener (/home/xxx/node_modules/chokidar/lib/nodefs-handler.js:80:19)
    at EventEmitter.NodeFsHandler._watchWithNodeFs (/home/xxx/node_modules/chokidar/lib/nodefs-handler.js:228:14)
    at EventEmitter.NodeFsHandler._handleDir (/home/xxx/node_modules/chokidar/lib/nodefs-handler.js:403:23)
    at EventEmitter.<anonymous> (/home/xxx/node_modules/chokidar/lib/nodefs-handler.js:450:19)
    at EventEmitter.<anonymous> (/home/xxx/node_modules/chokidar/lib/nodefs-handler.js:455:16)
    at FSReqWrap.oncomplete (fs.js:78:15)

ENOSPC means that there is no space on the drive. Is that the case?

it is not possible of that case!
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       144G   50G   88G  37% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            1.5G  4.0K  1.5G   1% /dev
tmpfs           295M  1.2M  293M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            1.5G   17M  1.5G   2% /run/shm
none            100M   44K  100M   1% /run/user

maybe it is the memory space issue.

weird, same problem here, restart helped

@jhartma
i close the sublime or remove some project  and it works.
may be there are some many files need to watch when sublime open a lot files.
ENOSPC can also mean you're running into one of the system limits:

$ sysctl -a | grep ^fs.inotify
fs.inotify.max_queued_events = 16384
fs.inotify.max_user_instances = 128
fs.inotify.max_user_watches = 8192

I have same problems due to system limitation. I would like only watch directory and I wonder why chokidar add watch on every file in directory ? So if I put more than max_user_watches application crash with ENOSPC. I could do workaround. But I would like to know if it is possible to watch only directory ?

why chokidar add watch on every file in directory

because that's the only way to reliably detect all the changes

if it is possible to watch only directory

Not with chokidar. If you only want a watcher at the directory level only, use fs.watch directly.

So fix is to always try to use relative paths for globs. For example __dirname, cwd or just prepending the glob with ./, e.g. ./dir/*.{js,css,html}.

why chokidar add watch on every file in directory

because that's the only way to reliably detect all the changes

Hi @es128, are you sure watching individual files is needed on Linux? If so, can you share the issues you've come across?
My experience with file watching on Linux, Mac & Windows is that Linux is the only OS with a completely reliable file watching sub-system, and doesn't need a helping hand over and above the fact that it doesn't support recursive directory watches, so that you have to add and remove shallow directory watches on the fly as directories come into and go out of existence.
The only real downside to Linux's file watching that I've run into is that you can easily run out of watch handles, and so watching files rather than directories (which will only exacerbate this problem) would definitely be a good one to avoid if at all possible.

You will miss change events if you watch only the directory and not the files (depending on how the file was modified). If you only care about files being created, deleted, or moved, then yes, directory-level watchers should suffice. But chokidar does not provide an option for this.

Hi @es128, are you sure that's the case for Linux too, or is it a design of lowest common denominator?


Updates Quickstart Guide Links for v0.2.0 Release

Updates the Quickstart guide links for the v0.2.0 release.
Signed-off-by: danehans<EMAIL_ADDRESS>

Note: I will submit a PR after cutting the release to change the links back to latest.

Closing due to https://github.com/envoyproxy/gateway/pull/631.

The Quickstart guide is the only user/dev doc that references release artifacts:
$ grep -ri "https://github.com/envoyproxy/gateway/releases/download/latest" docs/user docs/dev

Codecov Report

Merging #630 (61c45b8) into main (ac3b50f) will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #630      +/-   ##
==========================================
+ Coverage   62.15%   62.24%   +0.08%
==========================================
  Files          47       47
  Lines        5742     5742
==========================================
+ Hits         3569     3574       +5
+ Misses       1944     1940       -4
+ Partials      229      228       -1

Impacted Files
Coverage Δ

internal/provider/kubernetes/gateway.go
51.59% <0.00%> (+0.21%)
:arrow_up:

internal/provider/kubernetes/gatewayclass.go
75.36% <0.00%> (+2.89%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Downsample all stimuli

Must incorporate downsampling of audio and re-encoding to lossless encoder for video into clip preparation. Because it takes so long, we'll want to do this on the HPC using an ffmpeg Singularity image.
Base command:
ffmpeg -i S01E01R02_highres.mp4 -codec:v libx264 -crf 0 -preset fast -ar 44100 S01E01R02.mp4

The Singularity image and associated script appear to be working except for merges, which are failing because files are missing. I will need to fix that. Also, I'm not sure why, but the lossless encoded videos (even with the veryslow option) are absolutely enormous. Like 2-5 GB from 100-200 MB original videos.

Merging now works. Still huge files.


is this possible to get camera 3d pose (objectron)

hi.
i was looking through the api but could not find a reference.
i was looking on demo of objectron and there is one image where you show camera trace (Fig 3)
https://google.github.io/mediapipe/solutions/objectron.html
is this possible to get access in real time to camera position and rotation (relative to some specific objec or landmark of course).
is this possible to have access to each point in point cloud?
my primary goal is to get 3d pose of camera. secondary is to get pose of multiple cameras but I don't think that would be option for MP.
Thanks.

Hi @gb2111, Have you tried building any of the platforms and didn't you found it recognizing as Fig3. Which platform are you referring? Thanks!

@sgowroji I build python samples and they work very well.
My point is to get position of camera, not the object. Is that possible?

To get an accurate camera pose on device, you'll need to use ARCore camera API.


Document Whether the AMX tile registers are Caller Saved (volatile) or Callee-Saved (non-volatile)

The current version of the x64 Calling Convention does not mention the new AMX Technology Tile Registers as either Callee Saved or Caller Saved. It should be documented whether or not they are considered volatile.
Note: The Sys-V x86_64 ABI (https://ccs.neu.edu/home/ntuck/courses/2021/01/cs3650/asm/x86-64-sysv-abi.pdf) declares the registers Caller saved (volatile). That may be something to consider in making the decision.

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

ID: a87b11e0-0214-175b-0926-0f8a4653e444
Version Independent ID: 43e8bf4a-9a0d-ea28-d432-ead828604d5e
Content: x64 calling convention
Content Source: docs/build/x64-calling-convention.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@chorman0773
As far as I can tell, the TMM registers are in a category labeled "don't track", which (since it doesn't explicitly say callee saved) I'd assume effectively also means volatile/caller saved. I will check with the developers and follow up.


BulkInsert - add managed identity authentication

Closes #47. 2.0.0 change. Microsoft.Sql -namespace declared and used instead of System.Data.SqlClient as per instructions.

Summary by CodeRabbit

New Features

Transitioned database connectivity to use Microsoft.Data.SqlClient, enhancing performance and compatibility with SQL Server.
Updated connection strings in tests to include TrustServerCertificate=True, improving SSL certificate handling.

Bug Fixes

Adjustments made in testing methods to ensure compatibility with the new SQL client library.

Chores

Updated project dependencies to replace System.Data.SqlClient with Microsoft.Data.SqlClient version 5.2.1.

Since MicrosoftSQL has some packages that should be updated, they could probably be done under this PR as well. 🤔


Kieu

Continue to update the language conversion from English to Vietnamese on the homepage, login, register

Continue to update the language conversion from English to Vietnamese on the homepage, login, register


Yavin Demo App Test are not passing

Describe the bug
We were trying to run test on a Yavin app but see tests were failing.
To Reproduce

git clone git@github.com:yavin-dev/app.git
cd app
./gradlew build

Expected behavior
All tests should pass
Screenshots
StaticAssetServingTest > graphiql_landing_page_test() PASSED

StaticAssetServingTest > ui_route_test() FAILED
    java.lang.NullPointerException at StaticAssetServingTest.kt:48

StaticAssetServingTest > api_landing_page_test() PASSED

StaticAssetServingTest > swagger_landing_page_test() PASSED

StaticAssetServingTest > landing_page_test() FAILED
    java.lang.NullPointerException at StaticAssetServingTest.kt:25

RoleTest > createDateTest() PASSED

RoleTest > roleEndpointTest() PASSED

DashboardTest > dashboard() PASSED

DashboardTest > wrongUser() PASSED

DashboardTest > permissions() PASSED

DashboardTest > dashboardWithWidgets() PASSED

DashboardTest > globalFilters() PASSED

DashboardWidgetTest > dashboardWidget() PASSED

DashboardWidgetTest > widgetSetAuthor() PASSED

DashboardWidgetTest > widgetUserPermission() PASSED

DemoDataSourceTest > simple_netflix_table_test() PASSED

BasicTest > basic_server_hello() PASSED

AsyncQueryTest > testAsyncQueryPermissions() PASSED

UserTest > userEndpointTest() PASSED

UserTest > createDateTest() PASSED

UserTest > userPermissions() PASSED

UserTest > reverseRelationships() PASSED

UserTest > favoriteReports() PASSED

UserTest > roles() PASSED

UserTest > editingDashboards() PASSED

UserTest > securityTest() PASSED

UserTest > favoriteDashboards() PASSED

CorsFilterTest > it can return cors headers() PASSED

CorsFilterTest > it rejects bad request methods() PASSED

ReportTest > userPermissions() PASSED

ReportTest > report() PASSED

ReportTest > wrongUser() PASSED

ReportTest > differentAuthorPermissions() PASSED

ReportTest > createDate() PASSED

ReportTest > testHaving() PASSED

ReportTest > reportSort() PASSED

RequestV2Test > dashboardsWithRequestV2() PASSED

RequestV2Test > reportWithRequestV2() PASSED

RequestV2Test > testHaving() PASSED

ServerGeneratedConfigTest > server_generated_config() PASSED

40 tests completed, 2 failed

> Task :ws:test FAILED

FAILURE: Build failed with an exception.

Desktop (please complete the following information):

OS: Mac
Version: yavin-dev/app master branch

Additional context
N/A

I have Java 11 as well
javac -version
javac <IP_ADDRESS>

Hmm, it sounds like it's not building the ui subproject and copying the output over correctly. These are the files that it should build and copy over
# in the root 'app' dir
$ ls ui/build/resources/main/META-INF/resources/ui/
assets     fonts      img        index.html robots.txt testem.js  tests

You could also try running ./gradlew build -p ui directly to see if any errors occurred during the build

Thank you @kevinhinterlong for investigating! I'll definitely try it later today
(Sorry for the very late reply. :) )


custom attribute guide - updated screen shot

Update screen shots to NR1
https://newrelic.atlassian.net/browse/DEVEX-1123

@markweitzel  there seems to be a merge conflict with this PR, you can see that by clicking on resolve conflicts button.


setup multiple nodes cluster for kubeshare performance testing

per paper, the workloads are resnet50 and tf-serving.

The current implementation of Kubeshare can not support multiple nodes cluster.


Integer values are not parsed correctly

I'm using the raw lexer (no provided mongodb or other integrations).
Let's look at this example:
from odata_query.grammar import ODataLexer, ODataParser
lexer = ODataLexer()
parser = ODataParser()
odata_filter = parser.parse(lexer.tokenize("foo eq 15"))

I would expect that odata_filter contains a numerical value for foo, instead I get:
Compare(comparator=Eq(), left=Identifier(name='foo'), right=Integer(val='15'))

Hey @keul ,
I think your example might be missing something as I don't see what you mean with SomethingElse.
The parser will always output an AST, and it's up to the ORM integration or a custom transormer to turn that into a usable query. So the Compare node you see is exactly what I'd expect for that query.

Really sorry @OliverHofkens, opened the issue while rushing (SomethingElse was foo).
My question was about doing this:
>>> odata_filter.right
Integer(val='15')
>>> odata_filter.right.val
'15'

There's not an (easy) way to obtain the Python value expected from this token (so the 15 integer value and not the '15' str value).
I can obviously cast it myself by looking at the token type (Integer in this case) but I'm wondering if there's a more straightforward way.

Sure, I see the point!
Adding a new property getter with converted values would be great for a end-user point of view IMHO.

I just released v0.5 which includes this change!
Literal nodes now have a py_val property, which is the closest Python equivalent of the OData type.
I refactored the existing Transformers to use this new property as well.
Note that release 0.5 also includes full typing support, so keep that in mind if you use Mypy and upgrade.
Thanks for suggesting this!


Error when running mxnet with openmp disabled

With USE_OPENMP and USE_OPENCV disabled,  I got errors when running "python train_mnist.py.
Traceback (most recent call last):
File "train_mnist.py", line 1, in
import find_mxnet
File "/home/yifeng/mxnet/example/image-classification/find_mxnet.py", line 2, in
import mxnet as mx
File "/home/yifeng/mxnet/python/mxnet/init.py", line 7, in
from .base import MXNetError
File "/home/yifeng/mxnet/python/mxnet/base.py", line 43, in
_LIB = _load_lib()
File "/home/yifeng/mxnet/python/mxnet/base.py", line 35, in _load_lib
lib = ctypes.cdll.LoadLibrary(lib_path[0])
File "/usr/lib64/python2.7/ctypes/init.py", line 438, in LoadLibrary
return self._dlltype(name)
File "/usr/lib64/python2.7/ctypes/init.py", line 360, in init
self._handle = _dlopen(self._name, mode)
OSError: /home/yifeng/mxnet/python/mxnet/../../lib/libmxnet.so: undefined symbol: omp_get_thread_num
Any ideas?

It can be fixed by removing flags in dmlc-core/make/dmlc.mk line 14 and 15


upgrade: enable one api endpoint to do the whole initialization

this will be consumed by crowbarctl during the upgrade

Is it easy possible to squash the "fix" commits?

Can we move the helper functions to a separate file? It's in the meantime hard to review the stuff.

Is it easy possible to squash the "fix" commits?

not really, the first one anyways is not fixing anything that was introduced with this PR

Can we move the helper functions to a separate file? It's in the meantime hard to review the stuff.

yeah agree, slowly it gets a bit big for one file, but lets do that in a follow up please. if I move it now it doesn't make it easier to review anyways.

+1

So how does it change the api? Should PR to mkcloud and/or crowbarctl follow?

So how does it change the api? Should PR to mkcloud and/or crowbarctl follow?

26d2655ea1caff3c8881d4c7adea17fbc063cf4a affects it, but as gating passed, it should be good
and there is already the adaption for crowbarctl https://github.com/crowbar/crowbar-client/pull/105 which will consume this new endpoints

+1


Get selected item from json ?

How to get selected item using (itemSelected) callback ?
eg : the data is {"name": "Indonesia", "currency":"IDR"}
how to get the "IDR" when event triggered ?
so i still want to showing "Indonesia" on input text but i need "IDR" as input value.
Thank you! 👍

Still no answer, have you solved it ?

Here is the solution:
Add this to the page.html
<ion-auto-complete [dataProvider]="completeTestService" (itemSelected)="getVal($event)"></ion-auto-complete>
In the page.ts use this:
getVal($event){     console.log($event);   }
It will return the entire selected object.

Thanks but, did you mean entire selected object ?
what i mean is to get the value="" on option, not the entire text
I already use getVal($event) it just give me option text not the option value

@zeroseed each entry is actually the object associated with the option within the implemented service.
That means, that there is no a "value" attribute, but any property associated with the options is reflected and is accessible.

thank you so much @zaiderikat


Add extra validations to the stream frame decoder

This PR validates that the sum of Offset and  Length fields in the STREAM frame will not:

Overwrap a uint64_t
Exceed 2^62-1, as stated in the spec (end of section 19.8)

The sum is computed and used in apply_stream_frame() as max_stream_data.

After sleeping on it, QUICLY_MAX_STREAM_OFFSET_SIZE might be a bit misleading. I took it from this sentence:

The largest offset delivered on a stream - the sum of the offset and data length - cannot exceed 2^62-1, as it is not possible to provide flow control credit for that data.

Thank you for the PR.
I'm going to mark this PR as pending, because it is under debate if this error check should be done in the frame decoder, and if FRAME_ENCODING_ERROR is the correct code to be sent here. See https://github.com/quicwg/base-drafts/pull/3042.

Closing this PR, as QUIC WG has reached consensus that the case can be handled by the flow control logic, returning FLOW_CONTROL_ERROR.


Translations do not work on the first render of Client component when used in Layout

What version of this package are you using?
2.6.1
What operating system, Node.js, and npm version?
latest
I have created a code sandbox
link
just go there and type /test to the end of url of the app and hit Enter
as a temporary solution I am using this workaround:
const label = globalThis.__NEXT_TRANSLATE__ ? t(href) : fallbackImportedJSON[href];
because NEXT_TRANSLATE is missing on the first render
I tried to look at the code, but could not find a solution.
Are you willing to submit a pull request to fix this bug?
yes

Thanks to report it @bluelakee02. Looks weird, is rendering the children before the provider.
Plugin code:
https://github.com/aralroca/next-translate-plugin/blob/3d6a5044a65769013401fb021883304611842b55/src/templateAppDir.ts#L129
Logs:

This templateRCCPage is only executed on client pages (RCCPage = React Client Component Page), but it's not the case because your layout is RSCPage.

Any update on this one @aralroca? It would be really helpful if we can create a test suite for this case.

I suggested a solution here https://github.com/aralroca/next-translate/issues/1173#issuecomment-2305051765


Implemented TryFrom<&[u8]> for Key

The existing Key::from method, which creates a key from a &[u8], panics when the key isn't long enough. This PR moves this logic into an impl of TryFrom that returns a Result instead of panicking. The existing Key::from now just unwraps the TryFrom impl, so its behavior is unchanged.
This allows better handling an improperly created key, as well as creating a Key without having Key in scope, e.g. when using another crate that requires a Key but doesn't reexport cookie.

This is great, thanks for the contribution!
This is technically a breaking change, albeit a minor one, so perhaps we should wait for a major release. In any case, I'll merge this now; feel free to opine on the breakage considerations!

annotations mine. Since TryFrom is a std trait and it's parameterized by &[u8] (an std type), users couldn't create a conflicting implementation

This isn't quite the issue here. Consider the following:
struct Foo;

// implemented in `cookie`
impl std::convert::TryFrom<&[u8]> for Foo {
    type Error = ();

    fn try_from(_val: &[u8]) -> Result<Foo, ()> {
        println!("TryFrom");
        Ok(Foo)
    }
}

// in external crate
pub trait MyTrait<T>: Sized {
    type Error;

    fn try_from(value: T) -> Result<Self, Self::Error>;
}

// in external crate
impl MyTrait<&[u8]> for Foo {
    type Error = ();

    fn try_from(_val: &[u8]) -> Result<Foo, ()> {
        println!("MyTrait");
        Ok(Foo)
    }
}

// in external crate
fn main() {
    use std::convert::TryFrom;

    Foo::try_from(&[][..]); // ERROR: multiple applicable items in scope
}

Ahh, makes sense. I didn't consider that case. Thanks for taking the time!


Animation removed from webp

As per https://github.com/lovell/sharp/issues/518 and https://github.com/libvips/libvips/issues/823 sharp should be able to handle animated webps.
I am not very fluent in sharp nor JS in general, so there may be something I am doing wrong. If that is the case please enlighten me :)
Also question on the side, why can't I use fileStream.pipe(sharp().foFile(destPath)) (results in TypeError: dest.on is not a function). If this is out of scope that's ok as well.
Using sharp 0.28.0
What are the steps to reproduce?
File used for testing: https://files.catbox.moe/lap1sg.webp
File saved by sharp: https://files.catbox.moe/3okmbm.webp
const fileStream = ...  // FileStream of mentioned animated webp
const destPath = ...  // string of destination path

const chunks = []
fileStream.on('data', (chunk) => {
	chunks.push(chunk)
})
.on('end', () => {
	  const buffer = Buffer.concat(chunks);
	  // fs.writeFile(destPath, buffer, () => {});  // results in working animated webp at destPath
	  sharp(buffer).toFile(destPath)	// Removes metadata by default
		  .catch(abortWithError);
});

What is the expected behaviour?
Metadata removed and animation untouched
Running inside WSL 2.0
❯ npx envinfo --binaries --system
npx: installed 1 in 0.811s

  System:
    OS: Linux 5.4 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
    Memory: 4.19 GB / 7.74 GB
    Container: Yes
    Shell: 3.1.0 - /usr/bin/fish
  Binaries:
    Node: 14.15.3 - ~/.nvm/versions/node/v14.15.3/bin/node
    Yarn: 1.22.10 - ~/.nvm/versions/node/v14.15.3/bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v14.15.3/bin/npm

Hi, you can specify that you want all frames, rather than the default first frame, by using:
- sharp(buffer).toFile(destPath)
+ sharp(buffer, { animated: true }).toFile(destPath)

https://sharp.pixelplumbing.com/api-constructor#parameters

ahh darn, I looked at the documentation about webp and toFile not at the sharp constructor itself... 🤦
Thank you!

I've added an animated WebP example to the webp() docs via commit https://github.com/lovell/sharp/commit/08a25a0c8fb4dfaa5bddd7d0f4f0eea55cce2f65


New Device: Qingping Air Monitor Lite

Hello, please add support for this device.
Thank you
https://home.miot-spec.com/spec/cgllc.airm.cgdn1

Hi,
the device uses wifi, right? And doesn't it already support homekit out of the box?

Support is now added in version 1.0.0!


Login issue - MCZ Halo Air Up!

Stove: HALO AIR 8 UP! M1
When I try to log in, I also get a "unexpected error” message.
I'm supposed to use S/N and MAC as username/password, right?

Hi @k3ruakk, I believe this integration is not suitable for your stove.
It will only work for those using the black mobile app. Called 'Maestro MCZ'.


Jetty 9.4 changed async error handling

The current tests for EventSource don't work with Jetty 9.4. Jetty's breaking commit: https://github.com/eclipse/jetty.project/commit/dd4a72ce76acb012d4dadd5253217ec94783b4c9
Our tree: https://github.com/ringo/ringojs/tree/jetty-9.4
If Jetty 9.4 arrives right in time before Ringo's 1.0 RC, I would keep this on the 1.0 milestone. Otherwise this issue will be re-scheduled for RingoJS 1.1.

I think the fixed Jetty until 9.4.1 and so I close this issue. All our tests work as expected now.


Appstudio update test-component-pac-wmgt

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-wmgt-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
16 seconds
clone-repository

✅ Succeeded
31 seconds
build-container

✅ Succeeded
15 seconds
deprecated-base-image-check

✅ Succeeded
16 seconds
inspect-image

✅ Succeeded
37 seconds
clamav-scan

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
9 seconds
sbom-json-check

✅ Succeeded
17 seconds
optional-label-check

✅ Succeeded
17 seconds
label-check

✅ Succeeded
5 seconds
show-sbom

✅ Succeeded
6 seconds
show-summary


libtcmu: handle error when netlink family group is not found

genl_ctrl_resolve_grp returns a negative error code[1] when failed to
look up the family object. This patch handles the negative error code.
[1] http://www.infradead.org/~tgr/libnl/doc/api/group__genl__ctrl.html

Numeric group identifier or a negative error code.

Huh. That is a weird. I wonder what happened. Did we just forget to handle the ret value or did we do it on purpose due to some issue in the netlink code.
Going to assume we just forgot to handle ret.
Thanks.


panic 'Matrix index out of bounds.' in check_homogeneous_invariants (impl TCategory for TAffine)

The following code:
let local_transform : Affine3<f32> = try_convert(Matrix4::<f32>::identity()).unwrap();

results in a panic 'Matrix index out of bounds.' in check_homogeneous_invariants: src/geometry/transform.rs, line 104
fn check_homogeneous_invariants<N, D, S>(mat: &SquareMatrix<N, D, S>) -> bool
        where N: Scalar + Field + ApproxEq,
              D: DimName,
              S: Storage<N, D, D>,
              N::Epsilon: Copy {
        mat.is_invertible()                   &&
        mat[(D::dim(), D::dim())] == N::one() &&
        (0 .. D::dim()).all(|i| mat[(D::dim(), i)].is_zero())
    }

Shouldn't D::dim() be D::dim()-1 ?

Thank you for reporting this. I issued a PR adding a little regression test for now. I do not think, that this had been tested anywhere before.


Test the new introduced routes

I realized we forgot to test the auth of the new fetch & delete documents route.
I also noticed that we forgot to test the delete-batch route introduced a long time ago; thus, I added it to the list of routes to test.

Since this doesn't impact the code/features but makes us more confident in how the routes work, I would like to merge this in the release-v1.2 branch. If we have to fix a bug and make a patch release later, I'll be way more confident with these tests in the release.

FYI the commit of this PR was also in https://github.com/meilisearch/meilisearch/pull/3759/commits, that I bors merged

Oooh my bad, well I guess we can close this one then


PrestoAsyncServlet (user  password)

how to add user param,password param when i run query?

Sorry for replying so late.
If you use presto with LDAP, you may change yanagishima.properties.
But I'm not sure your environment.
Anyway, please follow issue template.


test for CI, will upstream soon if it works

This can't work because the oc cluster up change isn't in yet...


feature: add dragonfly as a http proxy for pulling image

pull image always stucks in grpc stream transport, do not merge now.
https://github.com/containerd/containerd/issues/2060
this is related to https://github.com/alibaba/pouch/issues/103.

LGTM
Could we add a document for users how to get started with pouch and dragonfly? @Ace-Tang 😄


fix exist()

add back quot to variable exist_result
add rstrip to tagui_output to remove tailing \n

Hi @xw0810 thanks for raising this PR! There might be some conflict on your PC. This Python rpa package uses a forked version of TagUI with a different syntax. Your PR is actually changing the package to use the latest syntax from TagUI. This won't work, because the forked version is optimised to work with this Python package.
To fix the issue on your PC, you can try doing print(r.tagui_location()). Inside, there should be a tagui or .tagui folder depending on which OS you are using. Delete that tagui or .tagui folder away (or move elsewhere as a backup).
Then run import rpa as r and r.init(). The package will pull the correct TagUI engine accordingly to run.


Scaling should be dynamic

Scaling should not be handled manually by changing resolution constants #114
It should be dynamically calculated from the retrieving the window size

Current options

Use of Camera https://api.arcade.academy/en/latest/api/camera.html
Implement logic in on_resize() https://api.arcade.academy/en/latest/api/window.html#arcade-view

Literature:
https://github.com/pythonarcade/arcade/commit/c4e8a4794a926df2a862d09c9f72b5068d9b1f65


Add UnitTests project. Add xUnit. Add tests for CacheSettings.

Sorry I probably should have used a branch on my fork.
I am new to the Fork and Pull pattern :)
Thanks for your patience!
Just wanted to write some simple tests for one class to make sure we are on the same page with tests.

I didn't forgot you, I'm just quite busy atm, review and merge will come soon.
Thanks for your patience.


[TEST] Fix KyuubiOperationWithEngineSecuritySuite and related issues

Why are the changes needed?

Currently, the KyuubiOperationWithEngineSecuritySuite is not valid, because

InternalSecurityAccessor is a singleton, only the first initialized one takes effect, which means if we change the testing orders, some tests may fail.
discoveryClient.startSecretNode calls PersistentNode#start underlying, which is async, we should call waitForInitialCreate to ensure it is created before running the test. Base on my analysis, it may take 30s for waiting. (mtime-ctime)[zk: <IP_ADDRESS>:55408(CONNECTED) 2] get /SECRET
_ENGINE_SECRET_
cZxid = 0x5
ctime = Wed Jul 19 23:01:57 CST 2023
mZxid = 0x7
mtime = Wed Jul 19 23:02:17 CST 2023
pZxid = 0x5
cversion = 0
dataVersion = 1
aclVersion = 0
ephemeralOwner = 0x0
dataLength = 15
numChildren = 0

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

Codecov Report

Merging #5072 (69cce29) into master (acb3362) will not change coverage.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master   #5072   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         564     564
  Lines       31293   31297    +4
  Branches     4096    4097    +1
======================================
- Misses      31293   31297    +4

Impacted Files
Coverage Δ

...vice/authentication/InternalSecurityAccessor.scala
0.00% <0.00%> (ø)

...ha/client/zookeeper/ZookeeperDiscoveryClient.scala
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks, merged to master/1.7


Add get stat functions

This'd be really useful for me, as I'm trying to integrate Steam Stats with Acheivments

Yes, I need it too. I would like to open more PRs but idk if @Noxime is still working on it.


Web UI Hanging

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
Often (more often than not), the web UI hangs on initial load for me.
As you can see in the screenshot below, the websocket is open and data is flying in for monitors, so the browser is definitely connected to the server and there doesn't seem to be any noticeable issues with server connectivity.
Issue reproduces on Edge for Mac (114.0.1823.43), Firefox for Mac (112.0.1) and Safari for Mac (Version 16.5 (186<IP_ADDRESS>.4)).
When it DOES work, it's often very slow to initially load (10+ seconds before you see anything happening as monitors load).
I can also confirm that some push monitors experience latency/timeouts when calling UptimeKuma.
System: Proxmox LXC

8 Cores (2X E5-2680 v3)
RAM: 8GB
Disk: 3-way ZFS Mirror on Dell Enterprise SAS SSDs

Average CPU via htop shows fairly straightfoward, nothing too exciting:

👟 Reproduction steps
N/A really, just open the web page and observe.
👀 Expected behavior
Page loads as normal
😓 Actual Behavior
Page hangs and shows:

🐻 Uptime-Kuma Version
version :  "1.21.3"
💻 Operating System and Arch
Debian 11 x64 via https://tteck.github.io/Proxmox/
🌐 Browser
Microsoft Edge Version 114.0.1823.43 (Official build) (arm64)
🐋 Docker Version
N/A - LXC
🟩 NodeJS Version
9.5.1
📝 Relevant log output
I don't see anything interesting in the logs output. Let me know what I can provide to assist.

How many monitors do you have? What is their type?
10s seems quite long

I am experiencing the same behavior. On initial load it seems very slow, but on subsequent loads it seems much faster. Running 96 monitors (each checking every minute). My database size is 2.3 GB.

I'm having the same issue with 216 monitors. Sometimes they randomly display, but then when drilling down they disappear!
I cannot see any errors in the logs.
Running as a container on Docker/Unraid.  Version: 1.22.1
DB size: 1.15GB
Has anyone managed to find a solution?

I'm having the same issue. When I log in with a new browser, I only see the WEB UI, no data.
When I check with developer tools, I am only receiving data on the socket.
When i restart via "pm2 restart uptime-kuma" command, i see the data.
However, when I connect with a different browser, I don't see the data again.
monitoring : 716 monitors running
Database size : 1.4gb+
OS : Windows 2012 R2
CPU : Xeon 2.9
Memory : 16GB
Keep Log  data : 7 days
uptime kuma version : 1.22.1
node.js version : 18.16.1

Please retest with latest version 1.23

Note that this could be caused by #3515 which is not merged yet.

could be caused

I doubt that it is, given the reported mounitor-count and db-size:

Running 96 monitors [...] My database size is 2.3 GB

@kevin-dunas and @ChrisLStark 's comments are likely not related to this issue and are likely fixed by the PR you linked.
This might be solved by the call to optimise introduced in https://github.com/louislam/uptime-kuma/pull/3380 and released in 1.23
=> @Saibamen 's comment if @SlothCroissant can retest if this is a problem in 1.23 is valid
This might also be solved by https://github.com/louislam/uptime-kuma/pull/3595 or https://github.com/louislam/uptime-kuma/pull/2750.

I have the same issue.
Running under Proxmox, LXC Debian 12, docker container inside.
Version 1.23.11
DB size: 51.5 MB, keeping only 1 day of history as lowering it seems to improve somehow this issue. At least that was my impression. Might be false.
83 monitors.

Read: with the lowered retentionvyoubare still having problems or not?

@CommanderStorm if I understood your question correctly (not sure because of the typos) you are asking if I still have issues with lowered retention. I still do, but seems to happen less often.
Normally this is working OK and after few days it the response period is lengthening until becoming really long and I just reboot the machine then. This "few days" is usually about a week.

Why isn't this project utilizing Node worker threads? It's common for the UI to freeze when the thread is blocked by monitor processing, in addition to sqlite3.

Which monitors are you using?
Monitor processing should not be a significant amount of time as all monitors are async and await => allow switching to another part of the codebase.
The usual answer: We just are currently not, no good reason why.
=> benchmark it to prove that there is a improvement and contribute a fix ^^

Currently, we are monitoring 82 services, including ping, HTTP, DNS, MySQL, MariaDB, MongoDB, PostgreSQL, and others. It is taking more than 60s to load. I recently experimented with adding worker_threads, which significantly enhanced our performance. Could I contribute further to this area?

Yes, sounds obviously interesting. (Duuh..)
Problem is that migrating to the new, way more performant data shema of v2 is not currently done.
=> directly migrating the experiments data (I am assuming you have a high amont of retention configured) won't be possible.
I think if you configure a few hundreds/thousands of monitor @ 20s (see https://pypi.org/project/uptime-kuma-api/) ping and set up a local mock server to ping against you can create a good testcase/"benchmark" for this.
Be aware that some monitors have different scaling requirements.
For example ping is supprisingly CPU intensive => this is an example where I think worker threads might be especially interesting.
Also monitor the impact on RAM (I think that might be the downside of this approach) ^^

Uptime Kuma is designed to be usable in a container with 256MB of memory. Since worker threads is basically a separate node.js instance with its own v8 heap, every thread will take up precious memory and interfere with the memory management of v8 (#3039). Of course there could be a dynamic scaling algorithm based on the available memory, but a lot more engineering effort is needed.
Also, in my limited testing v2 running with an external database has not experienced any performance issues, which suggests to me that the current bottleneck is still on SQlite.

I have been benchmarking why it is taking too many time to load and I found the Monitor.toJSON function. It’s very slow because it fetches lots of data recursively

I meet the issue, too.
And my monitoring items are 240.
I found a way to resolve that temporarily.

Restart the service.
Try to open the dashboard. If failed, go to step 1.
Select ALL items, and pause them.
Try to open the dashboard.
Resume ALL the items.
The dashboard resumes normal.

Hope this can help you.

I#m experiencing the same on latest 1.x release in docker. I couldn't rly find a solution in this thread. The tip in the end here only seems to be for v 2.x because i don't have the settings folder in my docker drive.
Any new infos on this?
Only running 15 item tho

/settings/monitor-history is a url

Oh my bad 🙈 bad thing is I can't use anything anymore. Web UI IS completly frozen and useless. Even monitoring push messegaes are effected now. Getting some "is up again" but never got the "went down" :/

@UllenBullen
No, you can't currently deactivate the history. The problem with maintenance you are describing is likely unrelated to the history.

@olli991
In that case, you will need to go into the sqlite console and manually delete items.
First ensure that the system is offline, then run

VACCUM
DELETE FROM heartbeats WHERE 1=1 (adjust the where clause to your needs)
VACCUM

A vacuum alone could solve your problem, you will have to check this.

We are experiencing the same problem.

Running Version: 1.23.15 in a docker container
Monitoring 1198 devices, mostly ping
Monitoring history is set to 7 days
The database is 905.6MB
Heartbeat Interval is set to 120 seconds
Packet Size is 56

When accessing the web interface, it reloads at least 3 times before being able to do anything.

Monitoring 1198 devices

That is far beyond our capabilities in v1. V2 does improve upon this (see #4500 for mitigations in the mean time).
Likely the issue needs https://github.com/louislam/uptime-kuma/pull/5025 too, but I have not have time for a proper re-review of said PR

I'm probably in the same boat.
I have about 50 monitors running. Monitoring is reliable, notifications are coming in.
However, the web UI regularly crashes after a little longer uptime (haha!). Then the entries/monitors are not updated, or are missing, or the whole app is not loaded.
Browser Reload does not help, Server Restart does (mostly).
The log is unremarkable. Only http monitors, I keep history for 100 days, my database is around 800 MB.

Could another table/index could be added which nullifies the need to have the code scan through the entire DB recursively?

We have released V2.0.0-beta1 with lots of performance fixes.
I am going to close this issue to keep possible V2 and V1 performance issues in different threads

You are right, we probably should have added a > [!TIP] to the related issues.
I have updated https://github.com/louislam/uptime-kuma/issues/4500 with this tip:

[!TIP]
If you are affected by the performance limits mentoned above in v1, you need to reduce the amount of data you store.
The core problem is that Uptime Kuma in v1 has to do a table scan of the entire heartbeat table for some operations.
The solution boils down to having a lower amount of data => making Uptime Kuma less worried about reading those gigabytes of data.:

reduce the retention and execute a manual cleanup under /settings/monitor-history
Increase the time between checks
pause or reduce the amount of monitors
delete the specific history of less essential monitors (to "lower" their retention below the configured maximum)


Modify Grammar and RCG pre-build scripts

We have determined the time it takes to use Maven to test for the existence of a jar file is longer than simply doing the build of them.  So both pre-build scripts should

remove the maven test for jar
start with test for repo existence
a. if it exists, pull the latest main branch
b. if it does not, create the directory and pull
do the build.

@hammyau I just realized with the above procedures, if I hard-code a pull of main, one can't do development on the workbench using other branches for grammar and RC-apps.  What if we just did a "pull" without switching branches?  Then one can make RC and grammar have the right branches? (but having local changes would be problem...that won't work)
Do we just use the automated script to pull main then?

Add a command line parameter to define the branch name.

OK, so additional thinking in this space, based upon our discussion:

Build.sh will be maintained as a simple build script to build all the components across all repos (grammar, RC-apps)

It will be modified to accept (but not require) a branch name, which will be used across all repos (default will be main)

A new buildwb.sh will be placed inside the "Prebuild" directory, which can be used to build just the workbench

This script and grammar.sh and rcg.sh (renamed rc-apps.sh) will all accept (but not require) a branch name
default branch name will be main
They will test for an environment variable to be used for the source repo url
They will test for the existence of the local repo directory, creating it if it does not exist
If it exists, they will simply switch to the given branch
Pull to get the most current remote branch
They will build the components

This will mean that these scripts are not useful for local develop as the local repo status would be overwritten by the pull.
But they can be used to create any components needed for development which are not updated from remote.

Determined to externalize all git branches from the GitHub build scripts.  If branches exist, the build scripts will not not update them.  If they do not exists, they will be cloned, and the default (i.e., main) branch will be used in the build.
Although the Grammar Script could be consolidated under the RC-app repo (and then the resulting components are in place for the Workbench build which follows), The DB2 Jar imports are done differently for the RC Apps and for the workbench, so those remain separate.

Close with #126


Create ShellSort.java

This is a java program for sorting an array using Shell Sort algorithm.
Issue Id you have worked upon -
Kindly write your answer here
Briefly explain your program logic -
Kindly write your answer here
Screenshots(Attach 2 screenshots of your own input and output) -
Attach here

Checklist:
Eg - If your code follow the below guidelines. Kindly change [] to [x]
All the conditions should be fulfilled for considering your code for merging -

[] I have mentioned the question as comment in my solution file.

[] My code follows the guidelines of this project.

[] I have performed a self-review of my own code.

[] I have commented my code.

[] My code gives the correct output.

[] I confirm that I have not copied the code from anywhere. In case its found that I have copied even after successful merge then I can be banned from the repository and hacktoberfest.

[] I affirm that I strictly follow contributing guidelines and code of conduct.

@ravneetsinghgaba,
Kindly create an issue first and then PR. And follow the PR template and contribution guidelines.
I am not closing this PR since this was your first time. You may refer CONTRIBUTING.md(present in the repository) and create an issue(iff program has not been done in repositories probable folders).
If above given lines follow, then kindly create an issue now and claim it. I will assign it to you.