text:
CVE-2007-4559 Patch

Patching CVE-2007-4559
Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.
If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

Hi @sphuber,
it looks like there was a similar PR on aiida-core repo, any insights? It looks like it was reverted on main hence my Q.

Yes, it was also opened on aiida-core and I reviewed it (https://github.com/aiidateam/aiida-core/pull/5681). Besides a syntax error for more recent Python versions I couldn't see anything directly malicious or incorrect. But then someone posted that they were malicious and it is true that I didn't review the actual code in high detail. To be sure, I therefore reverted the change. I am still not a 100% sure if this account is above-board or some kind of a malicious actor.

Well, the issue seems to be real:
https://github.com/python/cpython/issues/65308#issuecomment-1093650963
https://github.com/python/cpython/issues/97663

Yeah, I saw that as well, but that doesn't mean that the fix that is proposed is not malicious. I haven't had the time to go through the code diff in detail to see if it actually addresses the problem, which is not necessarily the case (even though at a first glance it looks plausible, it is not sending any data out or making dangerous sys calls, but it could still be malicious).

I think the code makes sure that the path inside a tar file does not go outside of the current folder.
The only suspicious thing for me was the GitHub account that does not seem to work: https://github.com/TrellixVulnTeam
The company seem to be real, though: https://www.trellix.com/

authors: TrellixVulnTeam danielhollas sphuber yakutovicha

repo: aiidalab/aiidalab


text:
和気あいAIの参加者一覧がSafariのときだけ変

どの機能に関する不具合ですか？

[x] それ以外

発生ページ

https://app.aipictors.com/events/wakiaiai
https://app.aipictors.com/events/wakiaiai2

どのような不具合が発生しましたか？
iPhoneのsafariで確認すると、参加者一覧のデザインが崩れている。

どのような操作をしましたか？
閲覧
どの端末で確認しましたか？

[x] iOS
[ ] Android

許せないですか？

[ ] 許せる
[x] 許せない

画像サイズを160にして修正できたのでクローズ

source: gharchive/issue

repo: aipictors/aipictors

license: MIT

license_type: permissive

license_source: github-api


text:
[Search Service(Java) setup] unable to start service

Gives the following exception during 'mvn spring-boot:run - To start the Java Service' step of the wiki.
Note: I already have the DB setup successfully.

Add your commit id here

[ ] spring boot is up and running.

Hi,
As mentioned earlier, there is an issue with th db. The permissions given to the db doesn't allow any modifications to the db which is preventing the spring boot to make a connection. As also from the errors this is evident. We are fixing it and will let you know.

@alakhsingh you can check the checkbox after fixing it (along with commit id), i will verify and close the issue. Take your time.

@KalaRaja Updated the steps in wiki. This issue was due to DB permissions.

After cloning everything from scratch, and following step by step, I ran into this error. Also, read this issue #44
_```
org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL "alter table public.search_details add column car_destination_price float8" via JDBC Statement
at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:67) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlString(AbstractSchemaMigrator.java:559) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlStrings(AbstractSchemaMigrator.java:580) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.migrateTable(AbstractSchemaMigrator.java:297) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.GroupedSchemaMigratorImpl.performTablesMigration(GroupedSchemaMigratorImpl.java:75) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.performMigration(AbstractSchemaMigrator.java:207) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration(AbstractSchemaMigrator.java:114) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:183) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:310) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:57) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:365) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:390) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:377) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.afterPropertiesSet(LocalContainerEntityManagerFactoryBean.java:341) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1804) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1741) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:576) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:498) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1083) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:853) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:316) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at com.start.envy.StarterEnvyApplication.main(StarterEnvyApplication.java:10) ~[classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_181]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_181]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_181]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_181]
at org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:558) ~[na:na]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]
Caused by: org.postgresql.util.PSQLException: ERROR: must be owner of relation search_details
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2440) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2183) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:308) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:293) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:270) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:266) ~[postgresql-42.2.5.jar:42.2.5]
at com.zaxxer.hikari.pool.ProxyStatement.execute(ProxyStatement.java:95) ~[HikariCP-3.2.0.jar:na]
at com.zaxxer.hikari.pool.HikariProxyStatement.execute(HikariProxyStatement.java) ~[HikariCP-3.2.0.jar:na]
at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:54) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
... 40 common frames omitted
2019-02-09 09:40:18.984  WARN 18600 --- [           main] o.h.t.s.i.ExceptionHandlerLoggedImpl     : GenerationTarget encountered exception accepting command : Error executing DDL "alter table public.search_details add column car_source_price float8" via JDBC Statement
org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL "alter table public.search_details add column car_source_price float8" via JDBC Statement
at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:67) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlString(AbstractSchemaMigrator.java:559) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.applySqlStrings(AbstractSchemaMigrator.java:580) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.migrateTable(AbstractSchemaMigrator.java:297) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.GroupedSchemaMigratorImpl.performTablesMigration(GroupedSchemaMigratorImpl.java:75) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.performMigration(AbstractSchemaMigrator.java:207) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.internal.AbstractSchemaMigrator.doMigration(AbstractSchemaMigrator.java:114) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:183) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:310) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939) [hibernate-core-5.3.7.Final.jar:5.3.7.Final]
at org.springframework.orm.jpa.vendor.SpringHibernateJpaPersistenceProvider.createContainerEntityManagerFactory(SpringHibernateJpaPersistenceProvider.java:57) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:365) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.buildNativeEntityManagerFactory(AbstractEntityManagerFactoryBean.java:390) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:377) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.afterPropertiesSet(LocalContainerEntityManagerFactoryBean.java:341) [spring-orm-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1804) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1741) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:576) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:498) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) [spring-beans-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1083) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:853) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:546) ~[spring-context-5.1.4.RELEASE.jar:5.1.4.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:142) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:775) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:316) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1260) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1248) ~[spring-boot-2.1.2.RELEASE.jar:2.1.2.RELEASE]
at com.start.envy.StarterEnvyApplication.main(StarterEnvyApplication.java:10) ~[classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_181]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_181]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_181]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_181]
at org.springframework.boot.maven.AbstractRunMojo$LaunchRunner.run(AbstractRunMojo.java:558) ~[na:na]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_181]
Caused by: org.postgresql.util.PSQLException: ERROR: must be owner of relation search_details
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2440) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2183) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:308) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:293) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:270) ~[postgresql-42.2.5.jar:42.2.5]
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:266) ~[postgresql-42.2.5.jar:42.2.5]
at com.zaxxer.hikari.pool.ProxyStatement.execute(ProxyStatement.java:95) ~[HikariCP-3.2.0.jar:na]
at com.zaxxer.hikari.pool.HikariProxyStatement.execute(HikariProxyStatement.java) ~[HikariCP-3.2.0.jar:na]
at org.hibernate.tool.schema.internal.exec.GenerationTargetToDatabase.accept(GenerationTargetToDatabase.java:54) ~[hibernate-core-5.3.7.Final.jar:5.3.7.Final]
... 40 common frames omitted

Can you please confirm if you executed commands one by one from intializer.sql and then used \i to run insert.sql?
If you do execute initializer.sql using \i then your db is not set up properly as when changing db psql might prompt you for your password.

authors: KalaRaja alakhsingh

repo: airavata-courses/Envy


text:
Couldn't find paper trail generator

Hey guys -
Using Rails 4.1, Ruby 2.1.4
I've entered gem 'paper_trail', '~> 3.0.6' into my Gemfile
I've bundled successfully, but when I bundle exec rails generate paper_trail:install I get:
Could not find generator paper_trail:install.
Seems like a very minute problem - am I missing something here?

Did you run bundle install first? And make sure the gem is not in a group on the Gemfile..

I've ran bundle install, and it's not in a group on the Gemfile. When I run bundle show, it does list the gem

Is it listed as a generator option when you run just bundle exec rails g?

It's not listed
On Wed, Jan 7, 2015 at 3:15 PM, Ben Atkins notifications@github.com wrote:

Is it listed as a generator option when you run just bundle exec rails g?
—
Reply to this email directly or view it on GitHub
https://github.com/airblade/paper_trail/issues/459#issuecomment-69110107
.

Hmmmm, I just tried with a fresh app of Rails 4.1.8 and it seemed to work for me so I'm not sure what the issue could be...

Strange. I've used Papertrail on other projects and this is the first time
I've had an issue with the generator
On Wed, Jan 7, 2015 at 3:19 PM, Ben Atkins notifications@github.com wrote:

Hmmmm, I just tried with a fresh app of Rails 4.1.8 and it seemed to work
for me so I'm not sure what the issue could be...
—
Reply to this email directly or view it on GitHub
https://github.com/airblade/paper_trail/issues/459#issuecomment-69110548
.

Are generators from other gems showing up in that list?

Yes, other gem generators are showing up
On Jan 8, 2015 7:48 AM, "Ben Atkins" notifications@github.com wrote:

Are generators from other gems showing up in that list?
—
Reply to this email directly or view it on GitHub
https://github.com/airblade/paper_trail/issues/459#issuecomment-69198122
.

Were you ever able to sort out what was going on here? Perhaps try upgrading Rails?

No I've been unable to figure it out..I decided to table it for now to do
something else.
On Wed, Jan 14, 2015 at 4:51 PM, Ben Atkins notifications@github.com
wrote:

Were you ever able to sort out what was going on here? Perhaps try
upgrading Rails?
—
Reply to this email directly or view it on GitHub
https://github.com/airblade/paper_trail/issues/459#issuecomment-70022287
.

You can always just copy the migration contents into a blank migration file if you really can't get it to work.
Sent from my iPhone

On Jan 14, 2015, at 8:05 PM, pkuruppu notifications@github.com wrote:
No I've been unable to figure it out..I decided to table it for now to do
something else.
On Wed, Jan 14, 2015 at 4:51 PM, Ben Atkins notifications@github.com
wrote:

Were you ever able to sort out what was going on here? Perhaps try
upgrading Rails?
—
Reply to this email directly or view it on GitHub
https://github.com/airblade/paper_trail/issues/459#issuecomment-70022287
.

—
Reply to this email directly or view it on GitHub.

This is happening for me too :(

If someone can provide a failing dummy app I can debug it more easily. I was unable to reproduce this, which makes it difficult to determine a cause.

For me it worked when sourcing the gem from Github master. It didn't work when using the rubygems version suggested in the readme.

@chrise86 - What version were you sourcing prior to sourcing from Github master?

is this a dup of #494?

I was experiencing the same issue in an app, after I switched to another version or ruby (using rvm) it magically appeared.
One curious thing was that, on the same environment I was having the problems, I was able to create a new rails app and the generator appeared.
This is the app in question in which I was experiencing the problems is this:
https://github.com/merlos/panatrans-api/tree/features/auditable
This is the last commit (before I solved the problem)
(https://github.com/merlos/panatrans-api/commit/95a62582bd5fffe7a6264a2a33f83cc18d36c020)
I guess that it may be related with any "base" gem or something like that. These are the steps I followed:
# generator not working

$ ruby --version
ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-darwin13.0]
$ rails --version
Rails 4.1.6

# Change to another ruby version

$ rvm ruby-2.1.2    # I had it already installed

$ ruby --version
$ ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]
$ rails --version
Could not find execjs-2.4.0 in any of the sources
Run `bundle install` to install missing gems.

# So, I had to udpate rails gems

$ bundle install
Fetching gem metadata from https://rubygems.org/.........
Using rake 10.4.2
Using i18n 0.7.0
Using json 1.8.2
Using minitest 5.5.1
Using thread_safe 0.3.4
Using tzinfo 1.2.2
Using activesupport 4.1.6
Using builder 3.2.2
Using erubis 2.7.0
Using actionview 4.1.6
Using rack 1.5.2
Using rack-test 0.6.3
Using actionpack 4.1.6
Using mime-types 2.4.3
Using mail 2.6.3
Using actionmailer 4.1.6
Using activemodel 4.1.6
Using arel 5.0.1.20140414130214
Using activerecord 4.1.6
Using acts_as_list 0.6.0
Using coffee-script-source 1.9.1
Installing execjs 2.4.0
Using coffee-script 2.3.0
Using thor 0.19.1
Using railties 4.1.6
Using coffee-rails 4.0.1
Installing git 1.2.9.1
Using haversine 0.3.0
Using hike 1.2.3
Using multi_json 1.10.1
Using jbuilder 2.2.8
Using jquery-rails 3.1.2
Using mini_portile 0.6.2
Using nokogiri 1.6.6.2
Installing paper_trail 4.0.0.beta2
Using pg 0.17.1
Using bundler 1.6.3
Using tilt 1.4.1
Using sprockets 2.12.3
Using sprockets-rails 2.2.4
Using rails 4.1.6
Using rails_serve_static_assets 0.0.2
Using rails_stdout_logging 0.0.3
Using rails_12factor 0.0.2
Using rdoc 4.2.0
Using sass 3.2.19
Using sass-rails 4.0.5
Using sdoc 0.4.1
Using spring 1.3.2
Using sqlite3 1.3.10
Using turbolinks 2.5.3
Installing uglifier 2.7.1
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.

# NOW IT APPEARS ! :-?

$ rails g
Usage: rails generate GENERATOR [args] [options]

General options:
  -h, [--help]     # Print generator's options and usage
  -p, [--pretend]  # Run but do not make any changes
  -f, [--force]    # Overwrite files that already exist
  -s, [--skip]     # Skip files that already exist
  -q, [--quiet]    # Suppress status output

Please choose a generator below.

Rails:
  assets
  controller
  generator
  helper
  integration_test
  jbuilder
  mailer
  migration
  model
  resource
  scaffold
  scaffold_controller
  task

Coffee:
  coffee:assets

Jquery:
  jquery:install

Js:
  js:assets

PaperTrail:
  paper_trail:install

TestUnit:
  test_unit:generator
  test_unit:plugin

Thanks!
Juan.

@merlos - Thanks for the detailed report. Just wanted to clarify though, what do you think is the culprit here then? Ruby 2.1.x?

I was unable to reproduce this.  I tried:
mkdir pt_issue_459 && cd pt_issue_459
echo "2.1.1" > .ruby_version
cat > Gemfile <<EOF
source 'https://rubygems.org'
gem "rails", "4.1.6"
gem "paper_trail", git: "git@github.com:airblade/paper_trail.git"
EOF
bundle
bundle exec rails new . --skip-gemfile --skip-spring
bundle exec rails g | grep paper_trail # paper_trail:install

Just guessing, but this may be a case of a poorly configured rvm or perhaps failing to use bundle exec.
@pkuruppu @merlos can you try the above and let us know what happens?

@jaredbeck It worked for me (I had to use https://github.com/airblade/paper_trail.git instead of git@github.com:airblade/paper_trail.git, something regarding permissions... ).
As I told in my previous comment, even before I solved the issue by setting a different ruby version I was able to create a new app with ruby 2.1.1 and the paper_trail generator appeared. It seemed to be a weird issue that affected only in the app I was working on. BTW I tried with/without bundle exec several times.
@batter My guess based on ignorance: some uncommon incompatibility with a particular version of a gem that was in my app.

Ok I'm tentatively ready to close this, just because I really don't have the faintest idea what could/would cause this and I don't know that there's anything we can do to "fix" it.  @jaredbeck - good point that, when in doubt, you should always run the commands with bundle exec just in case (even though rvm makes it possible to avoid it).

+1 to close it.

Just a note to this, I was having this problem on Ruby 2.1.6, changed to Ruby 2.0.0 and all works fine now.

Coming back to this I've been able to fix it for myself:
The problem was that after I bundled and ran the generator it returned the following message:

Could not find generator paper_trail:install.

After running 'gem list paper_trail' I saw it returned 2 versions.

paper_trail (4.0.0.rc1, 2.7.2)

Then I went to my Gemfile and set the version I wanted to use:

gem 'paper_trail', '4.0.0.rc1'

And it worked! ('bundle exec rails generator paper_trail:install')

create  db/migrate/20150602090759_create_versions.rb

Hope it helps anyone.

had the same issue after switching ruby version.  tried uninstalling and re-installing paper_trail gem a couple of times and finally got it to work.

Just to prove there are a million + 1 ways to mess things up, I experienced this same error.
The realized I'd added papertrail instead of ````paper_trail``` to my Gemfile.

In my case an error was nice enough to offer explanation how to fix itself - comment out: source 'https://rubygems.org' in Gemfile. Never had this error before. Thank you for the gem!

@lawso017 😆

Just to point out that I had the same issue using ruby-2.3.1. After I switched to ruby-2.2.4 everything worked as expected! :)
I thought it might be of help to somebody experiencing this.

For anyone wandering here from search engines, looks like this is an issue specifically with RVM only. On my linux dev machine, this worked as expected, however on my RVM using Ruby 2.3.1 I faced same issue as OP. You may just want to copy the migration file and commit it.

I have this issue as well in ruby 2.5.1 and rails 5.2

Had same issue with Ruby 2.5.0 and Rails 5.2.
Resolved issue with:
spring stop
Afterwards generate worked without problems. Hopes this would help to someone.

Had same issue with Ruby 2.5.0 and Rails 5.2.
Resolved issue with:
spring stop
Afterwards generate worked without problems. Hopes this would help to someone.

Thank you!

authors: Levia batter bombergio bugzpodder chrise86 dennisdevulder elkhan equivalentideas jaredbeck lawso017 merlos pkuruppu pwnious xgt001 zinosama

license: mit

license_source: bigquery


text:
Could not find table 'version_associations' when connecting to rails_admin

I'm in the process of adding paper_trail to my project, which already uses https://github.com/sferik/rails_admin.
I have only done this yet:
# Gemfile
gem 'paper_trail', '~> 4.0.0.beta'

bundle exec rails generate paper_trail:install --with-changes
rake db:migrate

But now when I'm connecting to http://localhost:3000/admin/?locale=en, I get the following error:
ActiveRecord::StatementInvalid at /
Could not find table 'version_associations'

Where does the need for this table version_associations come from, and why isn't it created in the migrations?

Stupid me, just read the manual!
bundle exec rails generate paper_trail:install --with-changes --with-associations


text:
Better support for AssistedInject factories

Using MvRx with Dagger becomes easier when we use AssistedInject.
This is how a usual setup looks like:
class MyViewModel(initialState: MyState): BaseViewModel(initialState) {
  ...

  @AssistedInject.Factory
  interface Factory {
    fun create(initialState: MyState): MyViewModel
  }

  companion object: MvRxViewModelFactory<MyViewModel, MyState> {
    ...

    override fun create(viewModelContext: ViewModelContext, state: HeadlinesState): MyViewModel? {
            val fragment = (viewModelContext as FragmentViewModelContext).viewModelFactory
            return viewModelFactory.create(state)
        }
  }
}

class MyFragment: BaseFragment() {
  ...
  @Inject lateinit var viewModelFactory: MyViewModel.Factory
  private val viewModel by fragmentViewModel()
}

We can make this better by creating a new fragmentViewModel delegate which accepts a view model producer:
  @Inject lateinit var factory: MyViewModel.Factory
  private val viewModel by fragmentViewModel { initialState ->
    factory.create(initialState)
  }

This way we will not need to access the fragment inside the companion object's MvRxViewModelFactory.

I have implemented this feature in one of my own library, and I think it looks a little neater than the alternative. Do you think MvRx could use this?

For the implementation of this, I was thinking of making the following changes:

A new overloaded version of by *viewModel delegates, which accept a view model producer lambda of the type: (S) -> VM where S is the state, and VM is the ViewModel.

A new get() method in MvRxViewModelProvider, which looks something like this:

fun <VM : BaseMvRxViewModel<S>, S: MvRxState> get(
  viewModelClass: Class<out VM>,
  stateClass: Class<out S>,
  viewModelContext: ViewModelContext,
  viewModelProducer: (S) -> VM, // New parameter
  key: String = viewModelClass.name,
  initialStateFactory: MvRxStateFactory<VM, S> = RealMvRxStateFactory(),
  stateRestorer: (S) -> S = {it}
): VM {
        val initialState = initialStateFactory.createInitialState(viewModelClass, stateClass, viewModelContext, stateRestorer)
        val factory = MvRxFactory { viewModelProducer(initialState) } // Bypass createViewModel method entirely
        return when (viewModelContext) {
            is ActivityViewModelContext -> ViewModelProviders.of(viewModelContext.activity, factory)
            is FragmentViewModelContext -> ViewModelProviders.of(viewModelContext.fragment, factory)
        }.get(key, viewModelClass)
    }

However, this causes an issue when trying to restore ViewModels, because the MvRxViewModelStore does not use the get() method of MvRxViewModelProvider to restore ViewModels. It instead uses the createViewModel method, which does not know anything about the viewModelProducer function.
To resolve this, maybe we can use Reflection to get a declared interfaces inside the ViewModel using an @AssistedInject annotated constructor, and look for a class annotated with the @AssistedInject.Factory. If such a class exists, then we know that the owner of this ViewModel must have a property of the type ThisViewModel.Factory which can be used to instantiate it.
This sounds flaky though, and we would need to add a dependency on AssistedInject to get access to those annotations.
I'm looking for alternatives to this, but any advice would be appreciated.

Closing this as this seems to be a bad design decision. The inconvenience of accessing the fragment class is a minor one, and does not warrant drastic changes in the library just to service one particular use case.

repo: airbnb/MvRx


text:
Use any instead of map

Save some CPU cycle by not doing a map first and then filtering.

@mwajeeh Can you rebase this to pick up the CI checks which we just re-enabled? LGTM to me if it goes green.

@gpeal I just did rebase and its still not picking it up. Am I missing something here?

It turns out that rebasing doesn't add the checks for whatever reason. LGTM though

source: gharchive/pull-request

authors: gpeal mwajeeh


text:
Fix weird border styling behavior for hover date (#378)

My solution for #378! I'm still noticing this weird curviness to the top-<left|right> border styles. I'm not sure how to solve that.
Let me know what you think. Thanks!

Coverage decreased (-1.4%) to 85.928% when pulling 4c8e7eb3f743d51b38040539049c00c42622c39f on ConAntonakos:fix-issue-378 into 091a34f101cbd7cdab4fedf537c43d253e5a79e5 on airbnb:master.

Sorry for taking so long to get to this! I think a problem is that in adding these modifiers (to be fair, this is largely due to the way we use modifiers right now), we're going to take a performance hit. It would be cool if it were possible to do this mostly in CSS. :/ I will investigate it a bit more.

No problem, @majapw! I think I agree with you regarding perf, though I haven't tested it thoroughly. I simply wanted to get this solution out at least since it was the first one that came to mind. I also agree about possibly changing this via styling only. Do you think it's possible with the current <table> <td> implementation? Do you think that might have to change? I'd be more than happy to rewrite the PR.

This still needs to be addressed, but because tables are hard I'm going to close it for now because I do not believe this is the correct solution.

No worries. Thanks for checking in. I'd be happy to update the PR once a better solution is figured out.

authors: ConAntonakos coveralls majapw

repo: airbnb/react-dates


text:
showsMyLocationButton not working

<MapView           style={styles.container}           showsUserLocation={true}           showsMyLocationButton={true}           onRegionChange={region => this.setState({ region })}           onRegionChangeComplete={region => this.setState({ region })}         />
"react": "16.0.0", "react-native": "0.50.0",
Show my location button still not appearing.

Did you solve this? Having the same problem.

I discovered on android device that when you rotate the phone, the button appears, but not in the initial state.

seeing the same here on iOS

you set Time out in componentWillMount.. and in
  <View style={{paddingTop: this.state.statusBarHeight }}>         <MapView            ............................         </MapView>         </View>..
because  showMyLocation init after map paint... => not appear

I also don't see the showsMyLocationButton on iOS:
        <MapView
           style={{flex:1}}
                  region={this.state.mapRegion}
                  showsUserLocation={true}
                  followUserLocation={true}
                  showsMyLocationButton={true}
                  onRegionChange={this.onRegionChange.bind(this)}>
        </MapView>

"expo": "^22.0.0",
"react": "16.0.0-beta.5",
"react-native": "0.49.3"

@richardstephenz  you setTimeOut and style map.. it will show...

Duplicate of #1315

Duplicate of #1033

authors: Germanaz0 Stophface alvelig aubreywahl radiKal07 richardstephenz vhuytdt

repo: airbnb/react-native-maps


text:
[tf][apps] un-commenting overwrite option in ssm param

to: @jacknagz
cc: @airbnb/streamalert-maintainers
size: small
resolves N/A
Background

Prior to v0.1.0 of Terraform, there was not support for overwriting an aws_ssm_parameter resource with a new value. We now use a newer version that supports this, so this is to enable config overwriting for apps.

Changes

Un-commenting the previously commented out overwrite = true property for the apps config stored in ssm.
This is necessary to update the config from the cli with new values (ie: when rate is changed).

Testing

Deployed a new rate with this change.

Coverage remained the same at 94.748% when pulling 549183e10690c985046a48807409f9ec2c78b0f5 on ryandeivert-tf-ssm-overwrite-fix into 10fc046d071722bbac8c4bf31a335af372d44a98 on master.

Coverage remained the same at 94.748% when pulling 549183e10690c985046a48807409f9ec2c78b0f5 on ryandeivert-tf-ssm-overwrite-fix into 10fc046d071722bbac8c4bf31a335af372d44a98 on master.

Coverage remained the same at 94.756% when pulling 622d4d19bbd049e1a8dccce1338c037e627380ad on ryandeivert-tf-ssm-overwrite-fix into 6e5a4dcebde9ac3ef18b691c30140fee0290cdd9 on master.

authors: coveralls ryandeivert

repo: airbnb/streamalert


text:
Pull most recent ruby gem version

It would be neat if as part of the deploy process we pulled the most recent airbrake gem version to display in docs that rely on it like:
https://airbrake.io/docs/ruby/upgrading-your-notifier/
Another option would be to perform a request for the most recent gem version when the page is loaded.

@mmcdaris now that we do not list a specific version in our docs, is this feature idea still relevant?
This is the update: https://github.com/airbrake/airbrake-docs/pull/401

Good point @thompiler, let's close it out!

authors: mmcdaris thompiler

repo: airbrake/airbrake-docs


text:
Filter out by default

string: Unsolicited response received on idle HTTP channel starting with HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nContent-Type: text/html\r\n\r\n
408 Request Time-out
\nYour browser didn't send a complete request in time.\n\n"; err=<nil>

Add filter that ignores errors with type string and message that stats with Unsolicited response received on idle HTTP channel starting with

repo: airbrake/gobrake


text:
feat: Add simple dashboard

Add simple dashboard

/help

/lgtm
/approve

repo: airconduct/go-probot


text:
getInputProps for checkbox returns defaultValue when it should use defaultChecked

Hey there, great package so far! This might be a lot to unpack, but I'll do my best to be clear.
Scenario: I am creating an "edit user" page where an admin can edit user details and change what permissions they have to the app. The create user flow worked flawlessly as far as I can tell, but in the edit flow I cannot get the checkbox list to properly hydrate those default states.
Here is the error that I'm getting from the browser:
Warning: ValidatedCheckbox contains an input of type checkbox with both value and defaultValue props. Input elements must be either controlled or uncontrolled (specify either the value prop, or the defaultValue prop, but not both). Decide between using a controlled or uncontrolled input element and remove one of these props. More info: https://reactjs.org/link/controlled-components

I have the following schema:
const schema = z.object({
  email: z.string().email(),
  passwords: z
    .object({
      password: z.string().min(6),
      passwordConfirmation: z.string(),
    })
    .refine((val) => val.password === val.passwordConfirmation, {
      path: ["passwordConfirmation"],
      message: "Passwords must match",
    }),
  firstName: z.string(),
  lastName: z.string(),
  isAdmin: zfd.checkbox().optional(),
  permissions: z
    .union([
      z.array(
        z.string().refine((val) => Object.values(UserPermission).includes(val as UserPermission), {
          path: ["permissions"],
          message: "Invalid permission",
        })
      ),
      z.string().refine((val) => Object.values(UserPermission).includes(val as UserPermission), {
        path: ["permissions"],
        message: "Invalid permission",
      }),
    ])
    .optional(),
});

and a form:
<ValidatedForm
  method="post"
  validator={validator}
  defaultValues={defaultValues}
>

    <ValidatedInput type="email" name="email" label="User email" readOnly disabled />
    <ValidatedInput type="text" name="firstName" label="First name" />
    <ValidatedInput type="text" name="lastName" label="Last name" />
    <ValidatedInput type="password" name="passwords.password" label="Password" />
    <ValidatedInput type="password" name="passwords.passwordConfirmation" label="Confirm password" />

    <ValidatedCheckbox
      className="sm:col-span-6"
      name="isAdmin"
      label="Admin user"
      value="on" // I had to add this because the library was adding a blank "value" prop otherwise, which broke it
      description="Admin users can update organization settings and manage users in addition to the following permissions"
      onChange={(checked) => setIsAdmin(checked)} // This is a bit of a hack to be able to disable the permissions list below
    />

    {permissions.map((permission) => (
      <ValidatedCheckbox
        key={permission.value}
        name="permissions"
        label={permission.label}
        value={permission.value}
        description={permission.description}
        id={`permission-${permission.value}`}
        disabled={isAdmin} // Is there a better way to get the current value of `isAdmin` other than tracking manually with useState?
      />
    ))}

    <SubmitButton submittingText="Saving...">Save</SubmitButton>

</ValidatedForm>

and finally the ValidatedCheckbox component:
const ValidatedCheckbox: React.FC<ValidatedCheckboxProps> = ({
  description,
  disabled,
  id,
  label,
  name,
  onChange,
  value,
}) => {
  const { error, getInputProps } = useField(name);

  const inputProps: any = getInputProps({
    id: id || name, // default to name if a specific id wasn't provided
    type: "checkbox",
    value, // this is for the user to optionally provide a custom value
    disabled,
  });

  // This function allows me to optionally track state changes of the checkbox in case I need to do other things
  // like show/hide/disable certain inputs based on the value of a checkbox
  const handleChange: ChangeEventHandler<HTMLInputElement> = (event) => {
    (inputProps as any).onChange(event.target.checked); // I noticed that the types recently screwed up and now I have to cast to `any`
    onChange?.(event.target.checked);
  };

  return (

        <input
          {...inputProps}
          onChange={handleChange}
        />

         {label}
        <p id={`${inputProps.id}-description`}> {description}

        {error ? (
          <p id={`${inputProps.id}-error`}> {error}

        ) : null}

  );
};

export default ValidatedCheckbox;

It seems that getInputProps should be using defaultChecked instead of defaultValue for checkboxes. Maybe the fix is as simple as that?
Indeed, if I add this guard to the ValidatedCheckbox component, I can get the default values to work as expected:
  if (inputProps.hasOwnProperty("defaultValue")) {
    if (Array.isArray(inputProps.defaultValue)) {
      inputProps.defaultChecked = inputProps.defaultValue.includes(value);
    } else if (typeof inputProps.defaultValue === "boolean") {
      inputProps.defaultChecked = inputProps.defaultValue;
    } else {
      inputProps.defaultChecked = inputProps.defaultValue === value;
    }
    delete inputProps.defaultValue;
  }

Hi! I agree that this is a little unintuitive.
For checkboxes, I think it's generally going to be a good idea to skip getInputProps entirely. There's a section in the docs here (Writing a checkbox component) where I suggest that.
I'll have to think a bit on what a library-level solution would be for making this more intuitive. I suppose we could tweak the props we use if type: 'checkbox' is passed into getInputProps, but I'm not sure how to account for both the individual checkbox case and the checkbox group case if we do that.
On another note, I think you can probably make the permissions check in your schema a little nicer if you use repeatableOfType.
permissions: zfd.repeatableOfType(z.nativeEnum(UserPermission))

I don't know if it related or not but the error comes from react and you going to get this error if you use like it says value and defaultValue, if you using value i think react is excepted to see onChange as well that signal to react its a control input

I don't know if it related or not but the error comes from react and you going to get this error if you use like it says value and defaultValue, if you using value i think react is excepted to see onChange as well that signal to react its a control input

It works fine if you use value with defaultChecked, but not value with defaultValue. See my solution at the end of the post, that seems to work well.

Hi! I agree that this is a little unintuitive.
For checkboxes, I think it's generally going to be a good idea to skip getInputProps entirely. There's a section in the docs here (Writing a checkbox component) where I suggest that.
I'll have to think a bit on what a library-level solution would be for making this more intuitive. I suppose we could tweak the props we use if type: 'checkbox' is passed into getInputProps, but I'm not sure how to account for both the individual checkbox case and the checkbox group case if we do that.
On another note, I think you can probably make the permissions check in your schema a little nicer if you use repeatableOfType.
permissions: zfd.repeatableOfType(z.nativeEnum(UserPermission))

Hey there! I must have missed that part of the docs where it says to build it myself, that would definitely make sense. I'll keep it the way I have it right now with this check:
  if (inputProps.hasOwnProperty("defaultValue")) {
    if (Array.isArray(inputProps.defaultValue)) {
      inputProps.defaultChecked = inputProps.defaultValue.includes(value);
    } else if (typeof inputProps.defaultValue === "boolean") {
      inputProps.defaultChecked = inputProps.defaultValue;
    } else {
      inputProps.defaultChecked = inputProps.defaultValue === value;
    }
    delete inputProps.defaultValue;
  }

This seems to handle the multiple and single values really well. There might be edge cases that I'm not considering here, but for me it's working out and gets rid of the error.
Thanks for that tip on using nativeEnum, definitely missed that when going over the zod docs.

I think that code to transform the default value just about covers it.
I'll add some extra handling for this situation similar to what formik does.

authors: AlonGvili airjp73 justinwaite


text:
Read text from multi line textbox

I run the parser and it's only read the first line of the textbox if the textboxt has more than one line.
And if the paragraph has more text style like this:
" Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux."
may be the color of the text, the font size too. I cant get all of this

Looks like there are a few questions here.  I'll get them separately. Here's the example I am using to Parse.

Multi-line Problem
Thanks, I hadn't realized this. The problem can be fixed in the paragraph parser
I naively just looked at the first element when extracting text, but after diseccting the actual Powerpoint Element, I see that each newline is a separate element of the array.
There is a raw element that is also a part of the PPTElement that actually has the parsed PPT XML that helps when debugging this uncaught stuff.

Might be smarter to iterate the array length and concatenate each element with a newline.
text: textElement["a:r"][0]["a:t"].toString() // problem is with the 0.

I'll see if I can push a new version soon or I'd encourage you to make a PR, now that you know the problem 😄
Preserving Color
I used red, and my color was preserved by the way. Colors are weird in Powerpoint, they can come from the theme or designs, try to explicitly assign one.
"textCharacterProperties": {
          "size": 1200, //ppt multipes fonts by 100 btw
          "fontAttributes": [
            0
          ],
          "font": "Helvetica", //this is the default, read the paragraph parser code, it'll teach you better
          "fillColor": "FF0000"
        }

In-line Bolding and Italics
I'm not sure how to handle the bolding and italics embedded in the text just yet, so that's probably not supported.
I'm still writing some docs, I haven't officially "published" this yet.  Not all elements are supported, you can see that list kind of here. Thanks for using this!

@tanphamanhh, should be fixed. Just published 1.0.6

I have an example PPTX that in one shape, it have more paragraphs. you can see the object model of pptx in here

I see in your PowerpointElement, in one shape it only have one paragraph

But, like the PPTX Object model image you see above, in one shape (PowerpointElement), it can have more than one paragraph.
Here is my pptx file's raw data:

That looks like a complex shape. At this point, I don't have plans to support that just yet. Feature requests can be tracked in Fider. I have added yours.
However, if this is something you really would like, I'd encourage you to make a PR to update the PPT Model and the parser to support paragraphs to return an array instead.

authors: rlingineni tanphamanhh

repo: airpptx/airppt-parser


text:
Create an endpoint for "Teams" to be viewed and updated

On control center, we need to create an endpoint for users.list to be able to:
1- Retrieve users.list
2- Add members to this users.list from Control Center UI.

Hey @M-Shorouk could you elaborate a bit more on this, please? What does it mean to create this endpoint "on the control" center and how does this relate to the existing users.list?

@chrismatix, sorry the ticket is not supper detailed.. still need discussion.
What i meant, we want to create "Teams" view on control center, that reads from user.lists as far as i understand.
Also we should allow the user to "ADD Member" to "Teams" through control center UI.

authors: M-Shorouk chrismatix

repo: airyhq/airy


text:
只是用pullup加载数据后上拉时候怎样才能整个页面都向上

Version 2.1.0-rc.47
<scroller ref="scroller"
                use-pullup
                scrollbar-y
                lock-x
                @on-pullup-loading="load"
                v-model="value" height="464px"
                v-show="hotelResult.list.length !== 0">

                  {{ item.saleTagName }}

{{item.productName}}

                    {{item.address}}

                  ￥{{item.minPrice}}起
                  ￥300

            <load-more v-show="value.pullupStatus === 'loading'" :tip="('正在加载')"></load-more>

 </scroller>

Expected behavior and actual behavior.
只是用pullup加载数据后，但是上拉时候只是scroller区域移动 整个页面都就停滞在scroller区域 要查看其他区域很难操作，
Steps to reproduce the problem

你误会了 scroller 组件的作用，它就是一个固定高度的容器内部可滚动。建议寻找其他非 VUX 组件来解决你的问题。

authors: ShineLam airyland

repo: airyland/vux


text:
设置路由切换loading无效

按照官网文档的写法写入 但是路由切换时loading不会触发 处于隐藏状态 看了下 好像是用vuex进行状态管理··不太懂那个 像知道是缺啥什么配置吗 另外 源码里面的vuex下面的store.js也照搬了··还是没效果

你应该先理解一下官网的demo为什么会触发loading效果，而不是单纯的去“抄”

按理说应该是isloading没有变化 一直是false···但是vuex的代码是跟作者一样的 我想知道遗漏了什么 除了app.vue和main.js以外

是要加载vuex-router-sync来进行同步处理吗··

建个可以重现的 repo。

检查了一下 router.beforeEach 里面的处理触发的 isloading成为false  但是router.afterEach里面的store.commit没有触发 打了console  有结果 说明执行了路由结束函数 但是store的函数没触发或者状态没有更新改变

是缺少什么类似更新状态的函数吗··

说反了··是router.beforeEach没触发 router.afterEach触发了

已经提交代码了··在我的仓库quesition

no package.json?
no build config?
no babel config?
Please add those files and reopen this issue.

恩 第一次弄github  不太熟练 这次上传完啦··

并不是无效，而是你并没有使用异步路由，切换时间短到 loading 不会显示出来。
setTimeout(() => {
    store.commit('updateLoadingStatus', {isLoading: false})
}, 1000)

乌龙了···非常感谢！


text:
如何用v-for循环为x-number的参数value赋值？

script全局引用
具体描述
本人用vux做电商页面，在购物车列表中用到了x-number表单组件，循环购物车商品数量列表给x-number参数value赋值失败（首先排除{{item.num}}不存在的可能）
页面代码
<div  v-for="(index,item) in checkList" >
    <group>
        <x-number :value={{item.num}} title="数量" :fillable=false  :min=1  :step=1  @on-change="changeNum" ></x-number>
    </group>
</div>

双花括号{{}} 并没有突出加黑显示 ，赋值失败

:value="item.num"

@airyland  这样写也不对，已经有试过
页面加载完后值为空，点击 ‘+‘ 号出现NAN类型
页面加载完成：

点击后：

你确定你的item.num是数字？

表字段是int类型的，抱歉之前回答的有点晚了

给个checkList的数据

checkList

你的num是字符串吧。

我知道了，虽然存的是int类型查出来的是string类型，需要把num先转为int类型在传参过去，谢谢你

authors: Van-jue airyland


text:
⚠ Turnos 24x7 has degraded performance

In da5fbb6, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1056 ms

Resolved: Turnos 24x7 performance has improved in 6449ffe.

repo: aisa-status/status-upptime-dev


text:
⚠ BCR Bot has degraded performance

In a458a2a, BCR Bot (https://bcr.alternativasinteligentes.com/BCRApi/web/chatbot) experienced degraded performance:

HTTP code: 200
Response time: 973 ms

Resolved: BCR Bot performance has improved in ed586df.


text:
Update README.md to clarify plugin/opensearch version sync

See NOTE: under Compatibility Matrix
As requested by @lukas-vlcek in  #197

@jeroenhabets Looking good. Maybe we can make it even more precise and point to plugins documentation here that also further explains the relation wrt to "sub"-patch plugin version, ie. all plugins 2.9.0.x will work only with OpenSearch 2.9.0.
Oh, and please provide DCO (--signoff), see https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/issues/78

Each commit must include a DCO which looks like this
Signed-off-by: Jane Smith jane.smith@email.com
You may type this line on your own when writing your commit messages. However, if your user.name and user.email are set in your git configs, you can use -s or --signoff to add the Signed-off-by line to the end of the commit message.

@lukas-vlcek I just commited an update including a Signed-off-by line.

@jeroenhabets The first commit is still missing the DCO. Maybe you can merge both commits into a single commit and have only this one commit signed?

Sorry @lukas-vlcek, then it's easier just to redo from start: https://github.com/aiven/prometheus-exporter-plugin-for-opensearch/pull/204

authors: jeroenhabets lukas-vlcek


text:
Customized knowledge base no kb_answers ERROR

I have a txt file which is my local knowledge base and now I want to use utils.process_document function to process my file. The database json file it generated is not the "QA" type. So when I add this tool into my config.json and run the run.py, it returns the following error:
AttributeError: 'KnowledgeBaseComponent' object has no attribute 'kb_answers'.
The code is here:
else:
  for hit in hits:
      matching_idx = hit["corpus_id"]
      if self.kb_chunks[matching_idx] in temp:
          pass
      else:
          knowledge = knowledge + f"{self.kb_answers[matching_idx]}\n\n"
          temp.append(self.kb_answers[matching_idx])
          if len(temp) == self.top_k:
              break
  print(hits[0]["score"])
  score = hits[0]["score"]
  if score < 0.5:
      return {"prompt": "No matching knowledge base"}
  else:
      print(knowledge)
      return {"prompt": "The relevant content is: " + knowledge + "\n"}

you could change kb.answers to kb.chunks, we will fix it soon.

@Jackie-shi you could check our latest codebase.

@callanwu I see, THX!

authors: Jackie-shi callanwu

repo: aiwaves-cn/agents


text:
unable to clone

C:\Users\Janek\Desktop\temp>git clone https://github.com/ajayrwarrier/Video-Chat/tree/video-chat-with-buttons
Cloning into 'video-chat-with-buttons'...
fatal: repository 'https://github.com/ajayrwarrier/Video-Chat/tree/video-chat-with-buttons/' not found
C:\Users\Janek\Desktop\temp>

That is weird. Is it working now?

authors: ajayrwarrier realjanek

repo: ajayrwarrier/Video-Chat


text:
✨App tile UI change

Category

Feature / Cosmetic

Overview

Because of file and commits conflict, it was decided it the better to redo the PR
Please refer to PR #1218

Issue Number

fixes #549 and fixes #834

Screenshot

Refer to PR #1218

@Tagaishi please check the modifications ive made. Are they okay for you ?

Just not liking the hovercard instead of the tooltip since the tooltip is used as an example of how it'll also look on over of the app itself.
Either both should be tooltips or both hovercards, but I don't really see a hovercard fitting as the hover object like tooltip does.

authors: Tagaishi ajnart

repo: ajnart/homarr


text:
1.0.0 is not in the Powershell Gallery

I see v 1.0 came out a while back but 0.2.1 is the current one listed on PowerShell Gallery
https://www.powershellgallery.com/packages/ArchitectureDecisionRecords

Oh, maybe I forgot to run the release when I tagged v1. I'll put that on my list.

Thought there aren't any functional changes from v0.2.1, so you aren't missing out on anything

I saw that. I'm doing some advocacy work on them and 0.2.1 vs 1.0.0 is just one less thing to deal with.
Thanks for looking into it.

Uploaded 1.0.0 to the gallery now.

authors: ajoberstar bigolewannabe

repo: ajoberstar/ArchitectureDecisionRecords


text:
Fix for PHP else indent for BDS/GNU/WS and Switch indentation

BDS/GNU/WS were not adding a newline character before else statements due to addNewLineIndent being commented out.

@mtpultz this PR is tested?

@akalongman the PR has been tested throughout the day, and doesn't cause any issues with regards to formatting, or throw any errors.

@akalongman what would you need to have this merged and become available to package control?

Few days :)

authors: akalongman mtpultz

repo: akalongman/sublimetext-codeformatter


text:
Deployment Failures Leading to Double Resource Consumption and Risk of Node Eviction Due to NodeHasDiskPressure

The Foundry encountered an issue where a node with 88Gi of available ephemeral disk space was experiencing NodeHasDiskPressure. This is evident from the events logged by the kubelet:
Events:
  Type     Reason                Age                  From     Message
  ----     ------                ----                 ----     -------
  Warning  FreeDiskSpaceFailed   2m1s                 kubelet  Failed to garbage collect required amount of images. Attempted to free 5118015897 bytes, but only found 80233010 bytes eligible to free.
  Normal   NodeHasDiskPressure   95s (x8 over 2d5h)   kubelet  Node prd-stk-tsr-dgx-41 status is now: NodeHasDiskPressure
  Warning  EvictionThresholdMet  45s (x30 over 2d5h)  kubelet  Attempting to reclaim ephemeral-storage

Correction:
The node isn't getting fully evicted but it is getting logged as in poor condition and evicting the pods there:
E[2023-10-30|19:01:03.614] node in poor condition                       cmp=provider client=kube node=prd-stk-tsr-dgx-41 condition=DiskPressure status=True

The issue was linked to a particular deployment, the contents of which can be found at this link. Due to continuous failures, Kubernetes kept trying to restart the deployment:
2lvnbm63bpumc76ei5993o9bhhc6hpibgrmhi2mc4k08q   comfy2-7dd5dcc9fc-64tb7   0/1     Error       0               5m18s
2lvnbm63bpumc76ei5993o9bhhc6hpibgrmhi2mc4k08q   comfy2-7dd5dcc9fc-vl64z   0/1     Pending     0               92s

To recreate the issue, a simple SDL was used:
...
command:
  - "sh"
  - "-c"
args:
  - 'sleep 10s; exit 1;'

profiles:
  compute:
    ssh:
      resources:
        cpu:
          units: 4
        memory:
          size: 8Gi
        storage:
          size: 53Gi

The available disk space reduced by twice the requested amount every 10 seconds, with the pod status alternating between Error and Pending. This indicated that Kubernetes was continually trying to restart the pod.
Upon checking the resource consumption before and after submitting the SDL, it was found that the CPU, memory, and storage were all being consumed at twice the rate requested by the deployment. Before the SDL submission, the resource status was:
$ date; provider_info.sh provider.hurricane.akash.pub
Mon Oct 30 07:36:10 PM CET 2023
type       cpu     gpu  ram                 ephemeral           persistent
used       46.5    1    147.09765625        625.09765625        550
pending    0       0    0                   0                   0
available  46.395  0    27.084184646606445  1183.6669998746365  613
node       46.395  0    27.084184646606445  1183.6669998746365  N/A

After the SDL submission:
$ date; provider_info.sh provider.hurricane.akash.pub
Mon Oct 30 07:36:44 PM CET 2023
type       cpu     gpu  ram                 ephemeral           persistent
used       46.5    1    147.09765625        625.09765625        550
pending    4       0    8                   53                  0
available  42.395  0    19.084184646606445  1130.6669998746365  613
node       42.395  0    19.084184646606445  1130.6669998746365  N/A

A few seconds later:
$ date; provider_info.sh provider.hurricane.akash.pub
Mon Oct 30 07:41:21 PM CET 2023
type       cpu     gpu  ram                 ephemeral           persistent
used       50.5    1    155.09765625        678.09765625        550
pending    0       0    0                   0                   0
available  42.395  0    19.084184646606445  1130.6669998746365  613
node       42.395  0    19.084184646606445  1130.6669998746365  N/A

When the deployment started to crash and redeploy:
$ kubectl -n $ns get pods
NAME                   READY   STATUS             RESTARTS      AGE
ssh-7bb5fcf55f-7bqxw   0/1     CrashLoopBackOff   3 (39s ago)   2m1s

This resulted in unexpected resource consumption, with the node having nearly double the resources than it was supposed to:
$ date; provider_info.sh provider.hurricane.akash.pub
Mon Oct 30 07:37:48 PM CET 2023
type       cpu     gpu  ram                 ephemeral           persistent
used       46.5    1    147.09765625        625.09765625        550
pending    4       0    8                   53                  0
available  38.395  0    11.084184646606445  1077.6669998746365  613
node       38.395  0    11.084184646606445  1077.6669998746365  N/A

Logs from Foundry:
Disk pressure flagged:
Normal   NodeHasDiskPressure    44s (x9 over 2d6h)   kubelet  Node prd-stk-tsr-dgx-41 status is now: NodeHasDiskPressure
  Warning  EvictionThresholdMet   11s (x32 over 2d6h)  kubelet  Attempting to reclaim ephemeral-storage

Events:
ingress-nginx                                   67s         Normal    Killing                 pod/ingress-nginx-controller-4wrzr                                    Stopping container controller
ingress-nginx                                   67s         Warning   Evicted                 pod/ingress-nginx-controller-4wrzr                                    The node was low on resource: ephemeral-storage. Threshold quantity: 15763389861, available: 15385288Ki. Container controller was using 468Ki, request is 0, has larger consumption of ephemeral-storage.
ingress-nginx                                   16s         Warning   ExceededGracePeriod     pod/ingress-nginx-controller-4wrzr                                    Container runtime did not kill the pod within specified grace period.
ingress-nginx                                   26s         Warning   Evicted                 pod/ingress-nginx-controller-4wrzr                                    The node was low on resource: ephemeral-storage. Threshold quantity: 15763389861, available: 12077328Ki. Container controller was using 132Ki, request is 0, has larger consumption of ephemeral-storage.

ubuntu@prd-stk-tsr-dgx-41:~$ sudo kubectl -n vk5gggln31994kc2e0s8thf4tkrca49un00m36ge4tvte get pods
NAME                     READY   STATUS    RESTARTS   AGE
comfy2-98b8ffcfb-7hj9r   1/1     Running   0          12m

ubuntu@prd-stk-tsr-dgx-41:~$ sudo kubectl -n vk5gggln31994kc2e0s8thf4tkrca49un00m36ge4tvte get pods
NAME                     READY   STATUS                   RESTARTS   AGE
comfy2-98b8ffcfb-7hj9r   0/1     ContainerStatusUnknown   1          14m
comfy2-98b8ffcfb-pkd7v   0/1     Pending                  0          4s
vk5gggln31994kc2e0s8thf4tkrca49un00m36ge4tvte   49s         Warning   Evicted                 pod/comfy2-98b8ffcfb-7hj9r                                            The node was low on resource: ephemeral-storage. Threshold quantity: 15763389861, available: 12484660Ki.
vk5gggln31994kc2e0s8thf4tkrca49un00m36ge4tvte   49s         Normal    Killing                 pod/comfy2-98b8ffcfb-7hj9r                                            Stopping container comfy2
vk5gggln31994kc2e0s8thf4tkrca49un00m36ge4tvte   39s         Warning   ExceededGracePeriod     pod/comfy2-98b8ffcfb-7hj9r                                            Container runtime did not kill the pod within specified grace period.

And provider goes offline too (since akash-provider pod gets evicted as well from that node).

I've tried the light image of mine with sleep 10; exit 1; and 50Gi storage requested; provider seem to be running fine.
@anilmurty pointed out this log line which would suggest that's the size of the image is causing the issue, which I'm now more inclined to believe is the main reason:
Failed to garbage collect required amount of images. Attempted to free 5118015897 bytes, but only found 80233010 bytes eligible to free.

as the image Foundry tried is enormous - 21.7GB:
$ docker images | grep zjuuu/comfyui
zjuuu/comfyui                                   0.6                     ce0a48d3f9c2   2 weeks ago     21.7GB

couldn't repro the node disk pressure with running zjuuu/comfyui:0.6 with sleep 10; exit 1;
however I could repro it when I used the default entrypoint of that image.
I guess it is doing something there that triggers the issue or so; gonna investigate deeper

The behavior is quite different, depending on whether the image was cached or being pulled.
Running image zjuuu/comfyui:0.6 with sleep 10; exit 1; today was pulling it again (seen from lease-events), knocking off the node after some time due to the disk pressure.
Re-running image zjuuu/comfyui:0.6 with sleep 10; exit 1; again, did not pull the image again (no Pulling image event in lease-events), the node was not knocked off.

Additionally, running image zjuuu/comfyui:0.6 with sleep infinity and then executing bash -x /entrypoint.sh (the standard entrypoint of that image) breaks the pod which then gets its lease terminated (likely when it reaches monitorMaxRetries which is about 4-5 minutes ).
The difference from the original behavior is that it supposed to restart that pod in sleep infinity mode (as per SDL) which is not happening.
It is possible that it spawns another replica/pod which gets indefinitely stuck in "Pending". This would be the case if the Foundry provider didn't implement the Force New ReplicaSet Workaround https://docs.akash.network/providers/akash-provider-troubleshooting/force-new-replicaset-workaround which would otherwise alleviate this situation. I'll ask them to verify/apply it today.
SDL - original with slight modifications, primarily:
    command:
      - "sh"
      - "-c"
    args:
      - 'sleep infinity; exit 1;'

lease-shell into the deployment:

fcb@ssh-7ffd9dd59c-59b5x:/$ bash -x /entrypoint.sh
...
+ wget -nv https://huggingface.co/stabilityai/stable-diffusion-xl-base-1.0/resolve/main/sd_xl_base_1.0.safetensors -P /comfyui/models/checkpoints
Error: lease shell failed: remote process exited with code 137

Exit code 137 error happens when a container or pod was terminated due to high memory usage.

After which:

lease-shell returns kube: lease not found;

lease-events returns no output;

blockchain PoV: market {order, bid, lease}, deployment = are all active & open;

when akash-provider reaches monitorMaxRetries it then closes the lease, client then gets Error: no active leases found  for dseq=13480440 as expected

[13480440-1-1]$ akash_shell bash
Detected provider for 13480440/1/1: akash17gqmzu0lnh2uclx9flm755arylrhgqy7udj3el
provider error messsage:
kube: lease not found

Error: remote server returned 400

[13480440-1-1]$ akash_status
Detected provider for 13480440/1/1: akash17gqmzu0lnh2uclx9flm755arylrhgqy7udj3el
provider error messsage:
kube: lease not found

$ provider_info.sh provider.akash.foundrystaking.com
type       cpu     gpu  ram                 ephemeral           persistent
used       6.5     1    35.5                50.5                0
pending    6       1    35                  50                  0                                           <<<<<< my deployment (`zjuuu/comfyui:0.6`)
available  638.35  53   4204.639930725098   4297.102982298471   0
node       95.125  8    753.6953830718994   790.7263174308464   N/A
node       89.625  6    719.1953601837158   741.2263174308464   N/A
node       95.425  8    503.05484199523926  791.2263174308464   N/A
node       94.85   8    502.97010040283203  791.2263174308464   N/A
node       73      7    468.37353897094727  38.08480133768171   N/A                 <<<<< pers.storage was 88Gi before the (`zjuuu/comfyui:0.6`) deployment; as well as 79 CPU, 8 GPU, 503Gi RAM
node       94.9    8    503.2803649902344   353.38659380655736  N/A
node       95.425  8    754.0703411102295   791.2263174308464   N/A

Before the deployment:
node       79      8    503.37353897094727  88.08480133768171   N/A

image was not cached, sleep infinity - disk pressure, pod evicted;

Running image zjuuu/comfyui:0.6 with sleep infinity; after few hours -- was pulling the image again (seen from lease-events), knocking off the deployment after some time due to the disk pressure. Provider eventually closed its lease as expected.
So the whole problem is the large image / low ephemeral storage space (nodefs, imagefs).
There are certain thresholds which can be tweaked around:
https://kubernetes.io/docs/concepts/scheduling-eviction/node-pressure-eviction/

The pods have been running well on that node; i.e. the node itself wasn't getting evicted but rather just the deployment itself.
The node was disappearing from the akash-provider report (8443/status) for short time while it was collecting the garbage.
I guess we are good then.
The pods have been running on prd-stk-tsr-dgx-41 through the entire time of this issue:
ubuntu@prd-stk-tsr-dgx-41:~$ sudo kubectl get pods -A -o wide | grep prd-stk-tsr-dgx-41
ingress-nginx                                   ingress-nginx-controller-rs88r                             1/1     Running     0          21h     10.233.84.232    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     calico-node-hwbjd                                          1/1     Running     0          7d21h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     coredns-5c469774b8-vz7z6                                   1/1     Running     0          7d21h   10.233.84.193    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     kube-apiserver-prd-stk-tsr-dgx-41                          1/1     Running     1          7d21h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     kube-controller-manager-prd-stk-tsr-dgx-41                 1/1     Running     2          7d21h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     kube-proxy-pxcm9                                           1/1     Running     0          6d19h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     kube-scheduler-prd-stk-tsr-dgx-41                          1/1     Running     1          7d21h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     nodelocaldns-5gwlp                                         1/1     Running     0          7d21h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
nvidia-device-plugin                            nvdp-nvidia-device-plugin-f457b                            1/1     Running     0          7d      10.233.84.199    prd-stk-tsr-dgx-41    <none>           <none>
prometheus                                      prometheus-prometheus-node-exporter-rkcpv                  1/1     Running     0          21h     10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>

It appears the provider is running chaperone utility which kills certain deployments.
Their file_types =  was set to ssh & sshd (I'm not sharing the entire config here for obvious reason).
And since I've been using the sshd-based one, it was getting killed:

logs from chaperone:

Oct 31 11:47:51 prd-stk-tsr-dgx-41 python3[1150795]: We found a process running with ssh match in pod ssh-548995d65d-clh4q
Oct 31 11:47:51 prd-stk-tsr-dgx-41 python3[1150795]: We found a process running with sshd match in pod ssh-548995d65d-clh4q
Oct 31 11:47:51 prd-stk-tsr-dgx-41 python3[1150795]: We found a process running with chm match in pod ssh-548995d65d-clh4q
Oct 31 11:47:51 prd-stk-tsr-dgx-41 python3[1150795]: Deleted namespace: 3ad5plmb0b7ivmob1dris8ikptv9ok2443kjo2oas6l5m

Going to re-test the 4th scenario.

image was not cached, sleep infinity - disk pressure, pod evicted;  (same as 4. except chaperone isn't killing the pod now)

The pod comfy2-58d5c7b44d-558f4 failed due to:
Message:             The node was low on resource: ephemeral-storage. Threshold quantity: 15763389861, available: 12139364Ki.

and the node prd-stk-tsr-dgx-41 had KubeletHasDiskPressure
Provider closed the lease.
FWIW: provider wasn't accessible initially because it was missing the haproxy rule to redirect 8443 (akash-provider) to the worker node it's been running at.

Logs
fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6   comfy2-58d5c7b44d-558f4                                    0/1     Error       0          20m
fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6   comfy2-58d5c7b44d-svl82                                    0/1     Pending     0          94s

ubuntu@prd-stk-tsr-dgx-41:~$ sudo kubectl get pods -A -o wide | grep prd-stk-tsr-dgx-41
fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6   comfy2-58d5c7b44d-558f4                                    0/1     Error       0          21m     10.233.84.239    prd-stk-tsr-dgx-41    <none>           <none>
ingress-nginx                                   ingress-nginx-controller-qcrn9                             0/1     Evicted     0          83s     <none>           prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     calico-node-hwbjd                                          1/1     Running     0          7d23h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     coredns-5c469774b8-vz7z6                                   1/1     Running     0          7d23h   10.233.84.193    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     kube-apiserver-prd-stk-tsr-dgx-41                          1/1     Running     1          7d23h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     kube-controller-manager-prd-stk-tsr-dgx-41                 1/1     Running     2          7d23h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     kube-proxy-sxkd7                                           1/1     Running     0          150m    10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     kube-scheduler-prd-stk-tsr-dgx-41                          1/1     Running     1          7d23h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
kube-system                                     nodelocaldns-5gwlp                                         1/1     Running     0          7d23h   10.40.160.141    prd-stk-tsr-dgx-41    <none>           <none>
nvidia-device-plugin                            nvdp-nvidia-device-plugin-f457b                            1/1     Running     0          7d2h    10.233.84.199    prd-stk-tsr-dgx-41    <none>           <none>
prometheus                                      prometheus-prometheus-node-exporter-5xlxh                  0/1     Evicted     0          80s     <none>           prd-stk-tsr-dgx-41    <none>           <none>

ubuntu@prd-stk-tsr-dgx-41:~$ sudo kubectl describe node prd-stk-tsr-dgx-41
Name:               prd-stk-tsr-dgx-41
Roles:              control-plane
Labels:             akash.network/capabilities.gpu.vendor.nvidia.model.v100=true
                    beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=prd-stk-tsr-dgx-41
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/control-plane=
                    node.kubernetes.io/exclude-from-external-load-balancers=
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: 10.40.160.141/24
                    projectcalico.org/IPv4VXLANTunnelAddr: 10.233.84.192
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Mon, 23 Oct 2023 15:28:48 -0400
Taints:             node.kubernetes.io/disk-pressure:NoSchedule
Unschedulable:      false
Lease:
  HolderIdentity:  prd-stk-tsr-dgx-41
  AcquireTime:     <unset>
  RenewTime:       Tue, 31 Oct 2023 15:13:05 -0400
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Mon, 23 Oct 2023 15:30:45 -0400   Mon, 23 Oct 2023 15:30:45 -0400   CalicoIsUp                   Calico is running on this node
  MemoryPressure       False   Tue, 31 Oct 2023 15:13:12 -0400   Mon, 23 Oct 2023 15:28:47 -0400   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         True    Tue, 31 Oct 2023 15:13:12 -0400   Tue, 31 Oct 2023 15:05:02 -0400   KubeletHasDiskPressure       kubelet has disk pressure
  PIDPressure          False   Tue, 31 Oct 2023 15:13:12 -0400   Mon, 23 Oct 2023 15:28:47 -0400   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Tue, 31 Oct 2023 15:13:12 -0400   Mon, 23 Oct 2023 15:32:02 -0400   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  10.40.160.141
  Hostname:    prd-stk-tsr-dgx-41
Capacity:
  cpu:                80
  ephemeral-storage:  102626232Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             528225832Ki
  nvidia.com/gpu:     8
  pods:               110
Allocatable:
  cpu:                80
  ephemeral-storage:  94580335255
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             528123432Ki
  nvidia.com/gpu:     8
  pods:               110
System Info:
  Machine ID:                 437e807e8fe84f478c670855995fba64
  System UUID:                81628b67-a46e-e811-ab21-d8c49769155b
  Boot ID:                    e6730582-abb0-4afd-bd01-2771350a1782
  Kernel Version:             5.15.0-84-generic
  OS Image:                   Ubuntu 22.04.3 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.7.5
  Kubelet Version:            v1.27.5
  Kube-Proxy Version:         v1.27.5
PodCIDR:                      10.233.64.0/24
PodCIDRs:                     10.233.64.0/24
Non-terminated Pods:          (8 in total)
  Namespace                   Name                                          CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                          ------------  ----------  ---------------  -------------  ---
  kube-system                 calico-node-hwbjd                             150m (0%)     300m (0%)   64M (0%)         500M (0%)      7d23h
  kube-system                 coredns-5c469774b8-vz7z6                      100m (0%)     0 (0%)      70Mi (0%)        300Mi (0%)     7d23h
  kube-system                 kube-apiserver-prd-stk-tsr-dgx-41             250m (0%)     0 (0%)      0 (0%)           0 (0%)         7d23h
  kube-system                 kube-controller-manager-prd-stk-tsr-dgx-41    200m (0%)     0 (0%)      0 (0%)           0 (0%)         7d23h
  kube-system                 kube-proxy-sxkd7                              0 (0%)        0 (0%)      0 (0%)           0 (0%)         150m
  kube-system                 kube-scheduler-prd-stk-tsr-dgx-41             100m (0%)     0 (0%)      0 (0%)           0 (0%)         7d23h
  kube-system                 nodelocaldns-5gwlp                            100m (0%)     0 (0%)      70Mi (0%)        200Mi (0%)     7d23h
  nvidia-device-plugin        nvdp-nvidia-device-plugin-f457b               0 (0%)        0 (0%)      0 (0%)           0 (0%)         7d2h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests        Limits
  --------           --------        ------
  cpu                900m (1%)       300m (0%)
  memory             210800640 (0%)  1024288k (0%)
  ephemeral-storage  0 (0%)          0 (0%)
  hugepages-1Gi      0 (0%)          0 (0%)
  hugepages-2Mi      0 (0%)          0 (0%)
  nvidia.com/gpu     0               0
Events:
  Type     Reason                 Age                    From     Message
  ----     ------                 ----                   ----     -------
  Normal   NodeHasNoDiskPressure  13m (x18 over 7d23h)   kubelet  Node prd-stk-tsr-dgx-41 status is now: NodeHasNoDiskPressure
  Normal   NodeHasDiskPressure    8m12s (x18 over 3d6h)  kubelet  Node prd-stk-tsr-dgx-41 status is now: NodeHasDiskPressure
  Warning  FreeDiskSpaceFailed    6m19s                  kubelet  Failed to garbage collect required amount of images. Attempted to free 9002490265 bytes, but only found 0 bytes eligible to free.
  Warning  EvictionThresholdMet   3m15s (x54 over 3d6h)  kubelet  Attempting to reclaim ephemeral-storage

ubuntu@prd-stk-tsr-dgx-41:~$ sudo kubectl -n fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6 describe pod comfy2-58d5c7b44d-558f4
Name:                comfy2-58d5c7b44d-558f4
Namespace:           fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6
Priority:            0
Runtime Class Name:  nvidia
Service Account:     default
Node:                prd-stk-tsr-dgx-41/10.40.160.141
Start Time:          Tue, 31 Oct 2023 14:50:53 -0400
Labels:              akash.network=true
                     akash.network/manifest-service=comfy2
                     akash.network/namespace=fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6
                     pod-template-hash=58d5c7b44d
Annotations:         cni.projectcalico.org/containerID: 43bef3f4ef7fbe33e7c178e973a1fa03d631232e4efa998dba09d63837e07369
                     cni.projectcalico.org/podIP:
                     cni.projectcalico.org/podIPs:
Status:              Failed
Reason:              Evicted
Message:             The node was low on resource: ephemeral-storage. Threshold quantity: 15763389861, available: 12139364Ki.
IP:                  10.233.84.239
IPs:
  IP:           10.233.84.239
Controlled By:  ReplicaSet/comfy2-58d5c7b44d
Containers:
  comfy2:
    Container ID:  containerd://9989c3a5b93e795a56f635d976a895ffd1b436831f39b2c3fa0a8ae51b387f1a
    Image:         zjuuu/comfyui:0.6
    Image ID:      docker.io/zjuuu/comfyui@sha256:7a6cf7c24e1c74b223b87fda62b47fa161a21333c072b49e02f09dd486626588
    Port:          8080/TCP
    Host Port:     0/TCP
    Command:
      sh
      -c
    Args:
      sleep infinity; exit 1;
    State:          Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Tue, 31 Oct 2023 14:57:01 -0400
      Finished:     Tue, 31 Oct 2023 15:09:58 -0400
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:                6
      ephemeral-storage:  53687091200
      memory:             37580963840
      nvidia.com/gpu:     1
    Requests:
      cpu:                6
      ephemeral-storage:  53687091200
      memory:             37580963840
      nvidia.com/gpu:     1
    Environment:
      ENABLE_MANAGER:                 true
      VAEURLS:
      MODELURLS:                      https://huggingface.co/stabilityai/stable-diffusion-xl-base-1.0/resolve/main/sd_xl_base_1.0.safetensors,https://huggingface.co/stabilityai/stable-diffusion-xl-refiner-1.0/resolve/main/sd_xl_refiner_1.0.safetensors
      UPSCALEURLS:
      COMMANDLINE_ARGS:               --listen --port 8080
      AKASH_GROUP_SEQUENCE:           1
      AKASH_DEPLOYMENT_SEQUENCE:      13485628
      AKASH_ORDER_SEQUENCE:           1
      AKASH_OWNER:                    akash1z6ql9vzhsumpvumj4zs8juv7l5u2zyr5yax2ys
      AKASH_PROVIDER:                 akash17gqmzu0lnh2uclx9flm755arylrhgqy7udj3el
      AKASH_CLUSTER_PUBLIC_HOSTNAME:  provider.akash.foundrystaking.com
    Mounts:                           <none>
Conditions:
  Type               Status
  DisruptionTarget   True
  Initialized        True
  Ready              False
  ContainersReady    False
  PodScheduled       True
Volumes:             <none>
QoS Class:           Guaranteed
Node-Selectors:      <none>
Tolerations:         node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                     node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason               Age    From               Message
  ----     ------               ----   ----               -------
  Normal   Scheduled            22m    default-scheduler  Successfully assigned fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6/comfy2-58d5c7b44d-558f4 to prd-stk-tsr-dgx-41
  Normal   Pulling              22m    kubelet            Pulling image "zjuuu/comfyui:0.6"
  Normal   Pulled               16m    kubelet            Successfully pulled image "zjuuu/comfyui:0.6" in 6m7.123648259s (6m7.12366841s including waiting)
  Normal   Created              16m    kubelet            Created container comfy2
  Normal   Started              16m    kubelet            Started container comfy2
  Warning  Evicted              4m3s   kubelet            The node was low on resource: ephemeral-storage. Threshold quantity: 15763389861, available: 12139364Ki.
  Normal   Killing              4m3s   kubelet            Stopping container comfy2
  Warning  ExceededGracePeriod  3m53s  kubelet            Container runtime did not kill the pod within specified grace period.

ubuntu@prd-stk-tsr-dgx-41:~$ sudo kubectl -n fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6 describe pod  comfy2-58d5c7b44d-svl82
Name:                comfy2-58d5c7b44d-svl82
Namespace:           fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6
Priority:            0
Runtime Class Name:  nvidia
Service Account:     default
Node:                <none>
Labels:              akash.network=true
                     akash.network/manifest-service=comfy2
                     akash.network/namespace=fns3s2v3eu25jps6bvr42de873t3iun1vngci22uf9ru6
                     pod-template-hash=58d5c7b44d
Annotations:         <none>
Status:              Pending
IP:
IPs:                 <none>
Controlled By:       ReplicaSet/comfy2-58d5c7b44d
Containers:
  comfy2:
    Image:      zjuuu/comfyui:0.6
    Port:       8080/TCP
    Host Port:  0/TCP
    Command:
      sh
      -c
    Args:
      sleep infinity; exit 1;
    Limits:
      cpu:                6
      ephemeral-storage:  53687091200
      memory:             37580963840
      nvidia.com/gpu:     1
    Requests:
      cpu:                6
      ephemeral-storage:  53687091200
      memory:             37580963840
      nvidia.com/gpu:     1
    Environment:
      ENABLE_MANAGER:                 true
      VAEURLS:
      MODELURLS:                      https://huggingface.co/stabilityai/stable-diffusion-xl-base-1.0/resolve/main/sd_xl_base_1.0.safetensors,https://huggingface.co/stabilityai/stable-diffusion-xl-refiner-1.0/resolve/main/sd_xl_refiner_1.0.safetensors
      UPSCALEURLS:
      COMMANDLINE_ARGS:               --listen --port 8080
      AKASH_GROUP_SEQUENCE:           1
      AKASH_DEPLOYMENT_SEQUENCE:      13485628
      AKASH_ORDER_SEQUENCE:           1
      AKASH_OWNER:                    akash1z6ql9vzhsumpvumj4zs8juv7l5u2zyr5yax2ys
      AKASH_PROVIDER:                 akash17gqmzu0lnh2uclx9flm755arylrhgqy7udj3el
      AKASH_CLUSTER_PUBLIC_HOSTNAME:  provider.akash.foundrystaking.com
    Mounts:                           <none>
Conditions:
  Type           Status
  PodScheduled   False
Volumes:         <none>
QoS Class:       Guaranteed
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age    From               Message
  ----     ------            ----   ----               -------
  Warning  FailedScheduling  3m48s  default-scheduler  0/8 nodes are available: 1 node(s) had untolerated taint {node.kubernetes.io/disk-pressure: }, 7 node(s) didn't match Pod's node affinity/selector. preemption: 0/8 nodes are available: 8 Preemption is not helpful for scheduling..

More logs
https://gist.githubusercontent.com/andy108369/20b536f8b41cc0521bcff59411c4b6af/raw/05f458c74ae83817b2b3d968a77f7abb2e87bc1a/logs.md

Looks like the provider increase the disk space, so the SDL can be retried there again.
$ provider_info.sh provider.akash.foundrystaking.com
type       cpu      gpu  ram                 ephemeral           persistent
used       10.5     1    39.5                54.5                0
pending    0        0    0                   0                   0
available  704.725  46   4742.572359085083   12225.30169552099   0
node       89.625   6    719.1953601837158   741.2263174308464   N/A
node       93.625   8    501.17984199523926  789.2263174308464   N/A
node       94.85    8    502.97010040283203  791.2263174308464   N/A
node       79       8    503.37351989746094  6384.962164035067   N/A
node       252.725  8    2012.5731716156006  3165.273985386826   N/A
node       94.9     8    503.2803649902344   353.38659380655736  N/A

repo: akash-network/support


text:
introduce dotenv, add header and footer

This PR contains

Files and folder restructure
Code revamp
Introduction to dotenv file
Introduction to composer

@akashvyavhare the PR was in the draft status and was not supposed to merge to the main branch.


text:
match_main_contract 调用报错

版本号
当前的 AKTools 版本为：0.0.86，AKShare 版本为：1.12.95

错误内容

设备 ：
调用 macos 和linux 的aktool 都会产生这个问题

现象  ：
只要调用 host:port/api/public/match_main_contract, 返回的内容都是null ， 查aktools 的log就会有error打印

4. match_main_contract

该接返回的是 str，不能通过 http 调用

那正确打开的方式应该是怎样呢？我希望通过java调用akshare

authors: albertandking lalalalalaqaq

repo: akfamily/aktools


text:
Continous scrolling stops

First and foremost, great plugin!
I am trying to achieve a continuous scrolling element like the one below
http://coolcarousels.frebsite.nl/c/23/
When i do this it starts to work with your plugin but then it stops. Here's what i mean:
https://codesandbox.io/s/1v5q7ox9oj
Any idea whats causing this and how I can fix it? Thanks

Make speed equal to autoplaySpeed and use cssEase='linear'.

it doesn't work for me, can you send me an example?

it doesn't work for me, can you send me an example?

Same here

authors: BadMachine jmelendev laveesingh xnog

repo: akiran/react-slick