fix(error-boundary): connect RenderFallbackProps.reset's args to onReset correctly

Connect RenderFallbackProps.reset's args to onReset correctly
If we want to pass any args to onReset's args when using RenderFallbackProps.reset, I think merging this Pull Request is required.
For easy understanding why I connect args, I left the code for reference (bvaughn/react-error-boundary).
If you merge this Pull Request, below implementation will be available like bvaughn/react-error-boundary
<ErrorBoundary
  renderFallback={({ reset }) => <button onClick={() => reset('something')}>reset all</button>}
  onReset={(...args) => {
    // args[0] will be 'something'
    console.log(args[0])
  }}
>
...
</ErrorBoundary>

Suggestion other way to solve this problem
I think removing this feature will be also good option. differently with bvaughn/react-error-boundary, I think passing args is not essential feature in ErrorBoundary and this feature can make difficulty to understand what is args, so, after discussing, I want to suggest Removing all args in ErrorBoundary. like @suspensive/react
I want to make ErrorBoundary as simply understand without passing args
thanks to @jinn2u, why I made this PR

PR Checklist

[x] I read and included theses actions below

I have read the Contributing Guide
I have written documents and tests, if needed.

Our response is slow due to our company’s holiday season, and every maintainer is at vacation right now. We will review this pull request by next week.

I guess this is quite a minor feature -- why not hold this until there are actual use cases? I understand this feature is good-to-have, but it is hard to type the props (we have to use unknown[]) and will make our codebase harder to maintain (because we have to support additional feature)

If you agree, can we close this pull request and open this again when we have an actual use case?

I guess this is quite a minor feature -- why not hold this until there are actual use cases? I understand this feature is good-to-have, but it is hard to type the props (we have to use unknown[]) and will make our codebase harder to maintain (because we have to support additional feature)

You mean, you want to remove this feature like my suggestion, right?

I think so too. So If you accept my suggestion: removing not essential feature(passing args: unknown[]), not like bvaughn/react-error-boundary. I will remove args type of reset with this feature. Could you decide it for me?

Yes, I think removing the feature would be nice.

Cool, I removed reset's args type in 01cb9d5 like @suspensive/react's ErrorBoundary's reset
Thanks to @jinn2u fixed it in @suspensive/react


Adding the POST JSON request and tests

Adding the POST JSON method with tests similar to the regular POST test.
This is related to issue #1

Closes #1


[in_app_purchase] Expose JSON serialization methods for the classes SKPaymentTransactionWrapper and PurchaseWrapper

Use case
The SKPaymentTransactionWrapper and PurchaseWrapper classes are already serializable via the json_serializable plugin, and the classes AppStorePurchaseDetails and GooglePlayPurchaseDetails have each a factory that expects their own transaction wrapper.
To be able to serialize those classes as JSON objects would be very helpful for persisting and transporting the information within the purchase stream.

Proposal
The classes already possesses a fromJson constructor factory that is already helpful, and they already have a private method generated by the json_serializable plugin into a .g dart file that contains  _$SKPaymentTransactionWrapperToJson and _$PurchaseWrapperToJson respectively, my proposal is to just expose those existing private methods as public in both classes:
// sk_payment_transaction_wrappers.dart
Map<String, dynamic> toJson() =>  _$SKPaymentTransactionWrapperToJson(this);

// purchase_wrapper.dart
Map<String, dynamic> toJson() =>  _$PurchaseWrapperToJson(this);

The potential issue we'll need to weigh here is that this would make the serialization itself part of the API surface, which could be an issue when changing method channel details.

Could you elaborate in more detail about the exact use case? Under what circumstances would you want a serialization whose format you don't control? Would you be passing this to other code that uses a different deserialization that's not part of the plugin? Persisting this on disk (which again has API compat issues)? Something else?

Of course.
Currently I work with the hydrated_bloc plugin that works with full serialized Map<String, dynamic> values.
I wish to accomplish a smooth serialization of a purchase details in order to store and retrieve locally on the device the objects that come out of the purchase stream. That layer of persistence is useful to obtain a full asynchronous cycle of validation and completion of the purchase with my backend server without losing consistency due to any error in the communication between the server and the device.

If you're persisting to disk and then reading it later, then you don't really just want the current functionality exposed, you want it exposed and for there to be an API guarantee of forward compatibility for all data it writes. That's significantly more impact on the maintainability of the API.

I see your point but the thing is that for my case I do not intent to store the PurchaseDetails serialized objects in any database for a long period of time. What I wish to accomplish is to create a cached snapshot of the last PurchaseDetails sent by the stream that can be finished via completePurchase some time later on and then delete them.
Although a full guarantee of compatibility would be appreciated it is not necessary for 99% of the cases, it would take the user to upgrade the app to a version that would break the API while having a pending purchase being processed.


ContainerLaunchException: Container startup failed

Hi,
I'm trying to start using TestContainers and got a Container startup failed exception.
I'm using windows 10 64 bit, docker version is 18.09.2, build 6247962, testcontainers version 1.11.1.
Code is pretty simple (and was taken from yours examples)
MySQLContainer mysql = (MySQLContainer) new MySQLContainer()
               .withConfigurationOverride("somepath/mysql_conf_override")
               .withLogConsumer(new Slf4jLogConsumer(logger));
 mysql.start();

When I tried to debug it I checked containers using "docker ps" command and there are several running containers (up to attempts counts). Also, I tried to connect manually to MySQL server using one of these containers and it was successful.
So,

container is created
mysql server is running
I'm able to execute 'Select 1' on it using DBeaver

but still got an exception :(
Do you have any idea what's going wrong?
Also I tried to start MSSQL container with the same results.
Here is a stacktrace
org.testcontainers.containers.ContainerLaunchException: Container startup failed
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:217)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:199)
	at TestContainersMySQL.doSimpleMySQLTest(TestContainersMySQL.java:20)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:567)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:305)
	at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:365)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:330)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:78)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:328)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:65)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:292)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:305)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:412)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:68)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exception
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:83)
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:210)
	... 27 more
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:277)
	at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:212)
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:76)
	... 28 more
Caused by: org.rnorth.ducttape.TimeoutException: Timeout waiting for result with exception
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:51)
	at org.testcontainers.containers.JdbcDatabaseContainer.waitUntilContainerStarted(JdbcDatabaseContainer.java:129)
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:259)
	... 30 more
Caused by: java.lang.RuntimeException: Could not get Driver
	at org.testcontainers.containers.JdbcDatabaseContainer.getJdbcDriverInstance(JdbcDatabaseContainer.java:165)
	at org.testcontainers.containers.JdbcDatabaseContainer.createConnection(JdbcDatabaseContainer.java:187)
	at org.testcontainers.containers.JdbcDatabaseContainer.lambda$waitUntilContainerStarted$0(JdbcDatabaseContainer.java:135)
	at org.rnorth.ducttape.unreliables.Unreliables.lambda$retryUntilSuccess$0(Unreliables.java:41)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:835)
Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:583)
	at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
	at java.base/java.lang.Class.forName0(Native Method)
	at java.base/java.lang.Class.forName(Class.java:332)
	at org.testcontainers.containers.JdbcDatabaseContainer.getJdbcDriverInstance(JdbcDatabaseContainer.java:163)
	... 7 more

Here is a log of container
Initializing database

2019-04-05T11:23:11.877456Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2019-04-05T11:23:11.879911Z 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html

2019-04-05T11:23:11.955762Z 0 [Warning] InnoDB: New log files created, LSN=45790

2019-04-05T11:23:12.062578Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.

2019-04-05T11:23:12.129738Z 0 [Warning] No existing UUID has been found, so we assume that this is the first time that this server has been started. Generating a new UUID: 328c1b31-5795-11e9-b4e7-0242ac110003.

2019-04-05T11:23:12.133406Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.

2019-04-05T11:23:12.134093Z 1 [Warning] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.

2019-04-05T11:23:13.553648Z 1 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:13.553694Z 1 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:13.553701Z 1 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:13.553711Z 1 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:13.553714Z 1 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:13.553719Z 1 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:13.553810Z 1 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:13.553815Z 1 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.

Database initialized

Initializing certificates

Generating a 2048 bit RSA private key

...........................+++

......................................+++

unable to write 'random state'

writing new private key to 'ca-key.pem'

-----

Generating a 2048 bit RSA private key

......................+++

.....................................................................................................................+++

unable to write 'random state'

writing new private key to 'server-key.pem'

-----

Generating a 2048 bit RSA private key

................................................+++

........................................................+++

unable to write 'random state'

writing new private key to 'client-key.pem'

-----

Certificates initialized

MySQL init process in progress...

2019-04-05T11:23:16.937179Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2019-04-05T11:23:16.938427Z 0 [Note] mysqld (mysqld 5.7.22) starting as process 90 ...

2019-04-05T11:23:16.940482Z 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html

2019-04-05T11:23:16.940529Z 0 [Note] InnoDB: PUNCH HOLE support available

2019-04-05T11:23:16.940537Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-04-05T11:23:16.940539Z 0 [Note] InnoDB: Uses event mutexes

2019-04-05T11:23:16.940541Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2019-04-05T11:23:16.940544Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3

2019-04-05T11:23:16.940546Z 0 [Note] InnoDB: Using Linux native AIO

2019-04-05T11:23:16.940697Z 0 [Note] InnoDB: Number of pools: 1

2019-04-05T11:23:16.940810Z 0 [Note] InnoDB: Using CPU crc32 instructions

2019-04-05T11:23:16.942222Z 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M

2019-04-05T11:23:16.943051Z 0 [Note] InnoDB: Completed initialization of buffer pool

2019-04-05T11:23:16.943642Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2019-04-05T11:23:16.954884Z 0 [Note] InnoDB: Highest supported file format is Barracuda.

2019-04-05T11:23:16.962328Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2019-04-05T11:23:16.962435Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2019-04-05T11:23:16.982276Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2019-04-05T11:23:16.983052Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.

2019-04-05T11:23:16.983094Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.

2019-04-05T11:23:16.983430Z 0 [Note] InnoDB: Waiting for purge to start

2019-04-05T11:23:17.033705Z 0 [Note] InnoDB: 5.7.22 started; log sequence number 2589163

2019-04-05T11:23:17.034091Z 0 [Note] Plugin 'FEDERATED' is disabled.

2019-04-05T11:23:17.037419Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.

2019-04-05T11:23:17.037562Z 0 [Warning] CA certificate ca.pem is self signed.

2019-04-05T11:23:17.037698Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2019-04-05T11:23:17.038398Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190405 11:23:17

2019-04-05T11:23:17.045742Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.

2019-04-05T11:23:17.046622Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:17.046671Z 0 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:17.046679Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:17.046691Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:17.046694Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:17.046700Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:17.047869Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:17.047917Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:17.052234Z 0 [Note] Event Scheduler: Loaded 0 events

2019-04-05T11:23:17.052574Z 0 [Note] mysqld: ready for connections.

Version: '5.7.22'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MySQL Community Server (GPL)

Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.

Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.

Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.

Warning: Unable to load '/usr/share/zoneinfo/zone1970.tab' as time zone. Skipping it.

2019-04-05T11:23:20.116176Z 4 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.116219Z 4 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.116227Z 4 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.116241Z 4 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.116245Z 4 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.116251Z 4 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.116490Z 4 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.116497Z 4 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.

mysql: [Warning] Using a password on the command line interface can be insecure.

mysql: [Warning] Using a password on the command line interface can be insecure.

mysql: [Warning] Using a password on the command line interface can be insecure.

mysql: [Warning] Using a password on the command line interface can be insecure.

2019-04-05T11:23:20.139752Z 8 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.139848Z 8 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.139882Z 8 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.139926Z 8 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.140107Z 8 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.140159Z 8 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.140639Z 8 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.140683Z 8 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:20.143422Z 0 [Note] Giving 0 client threads a chance to die gracefully

2019-04-05T11:23:20.143461Z 0 [Note] Shutting down slave threads

2019-04-05T11:23:20.143466Z 0 [Note] Forcefully disconnecting 0 remaining clients

2019-04-05T11:23:20.143470Z 0 [Note] Event Scheduler: Purging the queue. 0 events

2019-04-05T11:23:20.144052Z 0 [Note] Binlog end

2019-04-05T11:23:20.144424Z 0 [Note] Shutting down plugin 'ngram'

2019-04-05T11:23:20.144460Z 0 [Note] Shutting down plugin 'partition'

2019-04-05T11:23:20.144466Z 0 [Note] Shutting down plugin 'BLACKHOLE'

2019-04-05T11:23:20.144471Z 0 [Note] Shutting down plugin 'ARCHIVE'

2019-04-05T11:23:20.144475Z 0 [Note] Shutting down plugin 'PERFORMANCE_SCHEMA'

2019-04-05T11:23:20.144503Z 0 [Note] Shutting down plugin 'MRG_MYISAM'

2019-04-05T11:23:20.144508Z 0 [Note] Shutting down plugin 'MyISAM'

2019-04-05T11:23:20.144517Z 0 [Note] Shutting down plugin 'INNODB_SYS_VIRTUAL'

2019-04-05T11:23:20.144521Z 0 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'

2019-04-05T11:23:20.144526Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'

2019-04-05T11:23:20.144531Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'

2019-04-05T11:23:20.144534Z 0 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'

2019-04-05T11:23:20.144536Z 0 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'

2019-04-05T11:23:20.144537Z 0 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'

2019-04-05T11:23:20.144539Z 0 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'

2019-04-05T11:23:20.144540Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'

2019-04-05T11:23:20.144542Z 0 [Note] Shutting down plugin 'INNODB_SYS_TABLES'

2019-04-05T11:23:20.144543Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'

2019-04-05T11:23:20.144545Z 0 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'

2019-04-05T11:23:20.144546Z 0 [Note] Shutting down plugin 'INNODB_FT_CONFIG'

2019-04-05T11:23:20.144548Z 0 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'

2019-04-05T11:23:20.144549Z 0 [Note] Shutting down plugin 'INNODB_FT_DELETED'

2019-04-05T11:23:20.144551Z 0 [Note] Shutting down plugin 'INNODB_FT_DEFAULT_STOPWORD'

2019-04-05T11:23:20.144552Z 0 [Note] Shutting down plugin 'INNODB_METRICS'

2019-04-05T11:23:20.144554Z 0 [Note] Shutting down plugin 'INNODB_TEMP_TABLE_INFO'

2019-04-05T11:23:20.144555Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_POOL_STATS'

2019-04-05T11:23:20.144557Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE_LRU'

2019-04-05T11:23:20.144558Z 0 [Note] Shutting down plugin 'INNODB_BUFFER_PAGE'

2019-04-05T11:23:20.144560Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX_RESET'

2019-04-05T11:23:20.144561Z 0 [Note] Shutting down plugin 'INNODB_CMP_PER_INDEX'

2019-04-05T11:23:20.144563Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM_RESET'

2019-04-05T11:23:20.144564Z 0 [Note] Shutting down plugin 'INNODB_CMPMEM'

2019-04-05T11:23:20.144565Z 0 [Note] Shutting down plugin 'INNODB_CMP_RESET'

2019-04-05T11:23:20.144567Z 0 [Note] Shutting down plugin 'INNODB_CMP'

2019-04-05T11:23:20.144568Z 0 [Note] Shutting down plugin 'INNODB_LOCK_WAITS'

2019-04-05T11:23:20.144570Z 0 [Note] Shutting down plugin 'INNODB_LOCKS'

2019-04-05T11:23:20.144571Z 0 [Note] Shutting down plugin 'INNODB_TRX'

2019-04-05T11:23:20.144573Z 0 [Note] Shutting down plugin 'InnoDB'

2019-04-05T11:23:20.144615Z 0 [Note] InnoDB: FTS optimize thread exiting.

2019-04-05T11:23:20.145245Z 0 [Note] InnoDB: Starting shutdown...

2019-04-05T11:23:20.245559Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool

2019-04-05T11:23:20.246124Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 190405 11:23:20

2019-04-05T11:23:21.868845Z 0 [Note] InnoDB: Shutdown completed; log sequence number 12359588

2019-04-05T11:23:21.878353Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

2019-04-05T11:23:21.878461Z 0 [Note] Shutting down plugin 'MEMORY'

2019-04-05T11:23:21.878477Z 0 [Note] Shutting down plugin 'CSV'

2019-04-05T11:23:21.878486Z 0 [Note] Shutting down plugin 'sha256_password'

2019-04-05T11:23:21.878491Z 0 [Note] Shutting down plugin 'mysql_native_password'

2019-04-05T11:23:21.878735Z 0 [Note] Shutting down plugin 'binlog'

2019-04-05T11:23:21.883461Z 0 [Note] mysqld: Shutdown complete

MySQL init process done. Ready for start up.

2019-04-05T11:23:22.160486Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2019-04-05T11:23:22.161454Z 0 [Note] mysqld (mysqld 5.7.22) starting as process 1 ...

2019-04-05T11:23:22.163246Z 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html

2019-04-05T11:23:22.163319Z 0 [Note] InnoDB: PUNCH HOLE support available

2019-04-05T11:23:22.163326Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-04-05T11:23:22.163329Z 0 [Note] InnoDB: Uses event mutexes

2019-04-05T11:23:22.163331Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2019-04-05T11:23:22.163333Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3

2019-04-05T11:23:22.163334Z 0 [Note] InnoDB: Using Linux native AIO

2019-04-05T11:23:22.163475Z 0 [Note] InnoDB: Number of pools: 1

2019-04-05T11:23:22.163551Z 0 [Note] InnoDB: Using CPU crc32 instructions

2019-04-05T11:23:22.164599Z 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M

2019-04-05T11:23:22.165345Z 0 [Note] InnoDB: Completed initialization of buffer pool

2019-04-05T11:23:22.166094Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2019-04-05T11:23:22.177176Z 0 [Note] InnoDB: Highest supported file format is Barracuda.

2019-04-05T11:23:22.187290Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2019-04-05T11:23:22.187399Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2019-04-05T11:23:22.207808Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2019-04-05T11:23:22.208777Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.

2019-04-05T11:23:22.208819Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.

2019-04-05T11:23:22.209311Z 0 [Note] InnoDB: Waiting for purge to start

2019-04-05T11:23:22.259597Z 0 [Note] InnoDB: 5.7.22 started; log sequence number 12359588

2019-04-05T11:23:22.260008Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2019-04-05T11:23:22.260357Z 0 [Note] Plugin 'FEDERATED' is disabled.

2019-04-05T11:23:22.261538Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190405 11:23:22

2019-04-05T11:23:22.264017Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.

2019-04-05T11:23:22.264342Z 0 [Warning] CA certificate ca.pem is self signed.

2019-04-05T11:23:22.265823Z 0 [Note] Server hostname (bind-address): '*'; port: 3306

2019-04-05T11:23:22.265880Z 0 [Note] IPv6 is available.

2019-04-05T11:23:22.266648Z 0 [Note]   - '::' resolves to '::';

2019-04-05T11:23:22.266698Z 0 [Note] Server socket created on IP: '::'.

2019-04-05T11:23:22.271096Z 0 [Warning] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.

2019-04-05T11:23:22.272047Z 0 [Warning] 'user' entry 'root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:22.272093Z 0 [Warning] 'user' entry 'mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:22.272101Z 0 [Warning] 'user' entry 'mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:22.272122Z 0 [Warning] 'db' entry 'performance_schema mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:22.272126Z 0 [Warning] 'db' entry 'sys mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:22.272133Z 0 [Warning] 'proxies_priv' entry '@ root@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:22.273853Z 0 [Warning] 'tables_priv' entry 'user mysql.session@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:22.273911Z 0 [Warning] 'tables_priv' entry 'sys_config mysql.sys@localhost' ignored in --skip-name-resolve mode.

2019-04-05T11:23:22.277853Z 0 [Note] Event Scheduler: Loaded 0 events

2019-04-05T11:23:22.278087Z 0 [Note] mysqld: ready for connections.

Version: '5.7.22'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server (GPL)

ok, I wrapped container starting in try catch block and it's working (I mean still falling down with the same exception but at least I can use container). Created container has
mysql.isCreated() == true
mysql.isRunning() == true
mysql.isHealthy() falls with Null pointer exception because inspectContainerResponse.getState() return null.
any suggestions?

I have a similar problem with KafkaContainer.

@nagaeva-anastasia  hey, I am facing the same issue with my test... Did you get any updates or solutions for this issue? Thank you for your help!

@Novembera Hi! Unfortunately nope. I hope someone from testcontainers team will be able to help us.

@nagaeva-anastasia could you please share a reproducer?

@nagaeva-anastasia  After testing with DB examples from https://github.com/testcontainers/testcontainers-java/tree/master/modules/jdbc-test/src/test/java/org/testcontainers/junit  (MySQLContainer("mysql:5.5") and with created oracle-xe container) I have same Error in every try: container is created (line 237 this.containerIsCreated(this.containerId); in GenericContainer) but can not be started (catch (Exception var3), line 252) @bsideup

Here is log from my created (but not started) container:
ORACLE PASSWORD FOR SYS AND SYSTEM: 5fa16c205c198929
Specify a password to be used for database accounts. Oracle recommends that the password entered should be at least 8 characters in length, contain at least 1 uppercase character, 1 lower case character and 1 digit [0-9]. Note that the same password will be used for SYS, SYSTEM and PDBADMIN accounts:
Confirm the password:
Configuring Oracle Listener.
Listener configuration succeeded.
Configuring Oracle Database XE.
 For details check the logfiles at:
/opt/oracle/cfgtoollogs/dbca/XE.
Database Information:
Global Database Name:XE
System Identifier(SID):XE
Look at the log file "/opt/oracle/cfgtoollogs/dbca/XE/XE.log" for further details.
Connect to Oracle Database using one of the connect strings:
 Pluggable database: fb76f889deb1/XEPDB1

 Multitenant container database: fb76f889deb1

Use https://localhost:5500/em to access Oracle Enterprise Manager for Oracle Database XE
The Oracle base remains unchanged with value /opt/oracle
#########################
DATABASE IS READY TO USE!
#########################
The following output is now a tail of the alert.log:
2019-06-19T10:54:48.845841+00:00
XEPDB1(3):Resize operation completed for file# 10, old size 358400K, new size 368640K
2019-06-19T10:54:51.091125+00:00
XEPDB1(3):CREATE SMALLFILE TABLESPACE "USERS" LOGGING  DATAFILE  '/opt/oracle/oradata/XE/XEPDB1/users01.dbf' SIZE 5M REUSE AUTOEXTEND ON NEXT  1280K MAXSIZE UNLIMITED  EXTENT MANAGEMENT LOCAL  SEGMENT SPACE MANAGEMENT  AUTO
XEPDB1(3):Completed: CREATE SMALLFILE TABLESPACE "USERS" LOGGING  DATAFILE  '/opt/oracle/oradata/XE/XEPDB1/users01.dbf' SIZE 5M REUSE AUTOEXTEND ON NEXT  1280K MAXSIZE UNLIMITED  EXTENT MANAGEMENT LOCAL  SEGMENT SPACE MANAGEMENT  AUTO
XEPDB1(3):ALTER DATABASE DEFAULT TABLESPACE "USERS"
XEPDB1(3):Completed: ALTER DATABASE DEFAULT TABLESPACE "USERS"
2019-06-19T10:54:52.776178+00:00
ALTER PLUGGABLE DATABASE XEPDB1 SAVE STATE
Completed: ALTER PLUGGABLE DATABASE XEPDB1 SAVE STATE

@Novembera your issue seems to be different - it just fails to start. Please check Oracle module for the usage details, and raise a separate issue
@nagaeva-anastasia from the original stacktrace, I see the following line:

Caused by: java.lang.ClassNotFoundException: com.mysql.jdbc.Driver

Did you forget adding a MySQL driver?

@bsideup if you are talking about gradle dependencies
dependencies {
compile 'org.seleniumhq.selenium:selenium-java:3.141.59'
compile 'junit:junit:4.13-beta-2'
compile 'org.testcontainers:selenium:1.11.1'
compile 'org.testcontainers:mysql:1.11.1'
compile 'org.testcontainers:testcontainers:1.11.1'
compile 'mysql:mysql-connector-java:8.0.15'
compile 'log4j:log4j:1.2.17'
compile 'org.apache.logging.log4j:log4j-core:2.11.0'
compile 'org.apache.logging.log4j:log4j-api:2.11.0'
testCompile 'org.testcontainers:mssqlserver:1.11.1'
testCompile 'org.testcontainers:oracle-xe:1.11.1'
testCompile 'com.google.code.findbugs:jsr305:1.3.9'
}

Sorry for the mess. Right now I can't attach the link to the project with the reproducable issue.
I will come back a bit later.

BlueDi

i got same

I had the same problem. Try checking whether the port where the container(image) has to start is free


update readme

cleanup
adds helpful tips for common snags in our set up steps

Hey James, I created my own branch based off of yours, and then pushed mine to: "origin HEAD:jrogers/update_readme_setup". Hopefully that was the move!
I also need to figure out how to preview the formatting of it. I'm a little worried that it doesn't look very clear.

@zoeblairfriedman i just formatted it a bit more, but feel free to take it further if you want (i don't think you need to)
but previewing is possible right in vscodw

or you could've viewed our repo's homepage (shows readme by default) and switched to this branch
https://github.com/Nonprofit-Exchange-Hub/web-app/tree/jrogers/update_readme_setup
as for git workflow, i guess what you did worked fine but even simpler, you can just work right in my branch on your local and then push into my remote branch (fine as long as you're not deleting any of my commits because i'll always be able to see what you changed)

@jd2rogers2 Ah, yes. Thanks for that screenshot. I forgot about that feature in VSCode! Super helpful. Also I see how you've formatted the code sections now. This looks a lot better, thank you. Just going to make one slight header adjustment but I know Keith is on the rest of it!


INTERESTED AS TECHNICAL WRITER AT CURIOUS READER

Want to participate in curious reader as a technical writer as a part of gsod 2021?
Can you please provide me the contact?
My experience :

I am a software engineer at American Express
have written couple of blogs on Medium
Have served as a Technical content writer at Girlscript foundation
Have been a top contributor in Hackincodes and girlscript summer of code open source contribution programs
https://www.linkedin.com/in/shraddha-v-prasad/ - Linkedin
https://github.com/shraddhavp - Github
<EMAIL_ADDRESS>- Medium

I am really interested in this project can you please provide me the details ?

Hi @shraddhavp  ! Thanks for reaching out. If you could send an e-mail to<EMAIL_ADDRESS>with:

Your resume
Links to any portfolio pieces you have to showcase any technical writing you have written in the past
[Optional]: Links to any pieces of shareable code/software you may have written that you have also documented

Again thanks for your interest and we look forward to hearing from you.

Hello Sir,
By when can we expect the results sir ?
BY :
Shraddha Prasad
On Wed, 21 Apr 2021 at 00:28, burrage @.***> wrote:

Hi @shraddhavp https://github.com/shraddhavp ! Thanks for reaching out.
If you could send an e-mail to @.*** with:

Your resume
Links to any portfolio pieces you have to showcase any technical
writing you have written in the past
[Optional]: Links to any pieces of shareable code/software you may
have written that you have also documented

Again thanks for your interest and we look forward to hearing from you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/curiouslearning/CuriousReaderRCC/issues/4#issuecomment-823524817,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKFYWOQ3AOEIEQMJ44AGDULTJXFF5ANCNFSM43C75SVA
.

Hi @shraddhavp !
If you have been selected for an interview, you'll be hearing back via e-mail. Good luck!


SCP-2123: Add a nicer interface to the cost model for the ledger

This gives the ledger an interface that looks like a bag of named
integer parameters.
The implementation is ugly. I wanted this to work today, so I went with
something cheap and unpleasant: it would be nice to have something more
principled, but the current version does work.
We may want to revisit any number of these things. We can get rid of
some ugliness once we also use integetrs internally. But also stuff
like: the set of keys is derived from our current JSONification, which
isn't ideal, it should be highly stable. However, apparently it's okay
if we change the keys a bit before the testnet, so we can come back to
this.
Finally, I added some actual tests that the example scripts work, which
is helpful!

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages
[x] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

I'm going to aggressively merge this once CI passes, but I'd appreciate post-hoc reviews!


Code-related articles

Hi Liu Feng,
Thank you for sharing the code. I find your work very interesting. Is there a paper that provides more detailed description? Which paper should I cite when using your code?

Hello Adam,
Thanks for your interest in my recent work. We've been continuously revising and refining our work on ADFWI, and the latest version will be available within two months. This latest iteration will feature full waveform inversion of acoustic and elastic waves based on automatic differentiation. Additionally, we're in the process of preparing a related article, the preprint version of which will be released earlier.
Best regards


Student AD Test Accounts for Mobile SSO

Acquire student AD test accounts for ongoing development and testing of mobile SSO.
Notes:

For all intents and purposes these accounts will need to be indistinguishable from a regular student AD account. The account will need a valid PID, current class schedule (ongoing) and finals schedule which is returned during appropriate finals windows.
This request is for 5 student AD test accounts, with a mix of undergraduate and graduate students.

Let's move forward onboarding more students as alpha/beta testers.

Sounds good. Let's revisit this in the future if/when it becomes feasible.


Derive Vulkan bindings from D3D register syntax

Suppose a user writes code like:
SamplerState mySampler : register(s0, space2);

They might assume that when compiling for Vulkan, this will output as:
layout(binding=0, set=2)
sampler mySampler;

We already emit a warning in this case (see issue #505) to indicate to user that they should use [[vk::binding(0,2)]] if they want to specify the layout for Vulkan, but it appears the wording of that message isn't clear enough. Some users are under the impression that the compiler is warning them, but then using their register specifier anyway.
From a user perspective, the feature request would be that when compiling for Vulkan/GLSL:

If a parameter has a [[vk::binding(...)]], then use that.

Otherwise, if the parameter has a register binding, then attempt to use that instead.

This would need to work for both individual parameters and parameter blocks:
Texture2D t : register(t0, space3); // derive [[vk::binding(0,3)]]
ParameterBlock<X> pb : register(space4); // derive [[vk::binding(0,4)]]

There are some gotchas here that need to be thought through. The most obvious is when the simple derivation leads to overlapping bindings:
// This code is in error on Vulkan, but what should we report?
Texture2D t : register(t0, space2);
SamplerState s : register(s0, space2);

Diagnosing overlapping bindings here might be confusing to a user, since the register specifiers don't seem to overlap.
Another subtle issue is what to do when a parameter uses multiple resource kinds and thus needs multiple register specifiers:
struct MyStuff { Texture2D t; SamplerState s; };
MyStuff myStuff : register(t2) : register(s9);

In this case should we derive that myStuff gets a binding of 2 or of 9? It seems that in a case like that we should diagnose an error, but that requires detecting the situation and explaining it to the user in reasonable terms.
I suppose another case down that road is when a regsiter specifier is present, but has nothing to do with the reosurces a parameter consumes:
Texture2D t : register(s0);

That should probably produce an error when compiling for D3D, but when compiling for Vulkan we don't have the information handy to know that the s register class is disjoint from our parameter (we just know that our parameter consumes bindings).
It is probably correct that all these edge cases are relatively rare, so that the payoff from having the feature outweighs the cost.
The other thing to consider if we go down this road is whether to support anything like the command-line options for dxc that apply and offset/shift to each of the D3D register classes when computing bindings. Those would be an additive change over the base feature, so we can consider them down the line.

Language cleanup, low, q3

Fixed by #4338


Clicking the "covered" preset removes the option

For instance, if you create a foot path, type "covered" in the all tags section and then go to click the yes checkbox for the preset it will just close it. It also happens when you add covered along with yes to the all tags section and then try to cycle through the checkbox's options beyond no.

I don't think we can support letting the user enter partial data (key only) in the "all tags" section and then expecting a ui checkbox above to properly cycle through values.  That checkbox is going to remove the key because it is trying to assign both key and value together.
Anyway I'm going to close this, as it's a pretty minor issue.  I think advanced users can just enter the tags that they want.

OK. That makes sense. I thought maybe it was a bug or something.


Add FromScratch v1.0.1

[x] Checked there aren’t open pull requests for the same cask.
[x] Checked there aren’t closed issues where that cask was already refused.
[x] When naming the cask, followed the token reference.
[x] Commit message includes cask’s name.
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.

Added appcast and verification comment. Sadly the #{version} variable is not usable in that URL as the versions differ for the OSX artifact (v1.0.0 vs. 1.0.1).
@vitorgalvao PTAL again


support Xen virtual disk device (xvd) used by Amazon EC2

I tested this fix on my Amazon EC2 cluster and it worked.   I assume it would be same for any Xen VM cluster.  If it works in the CI, then I think we're good.
I would like in the future to see these regular expressions separated out into variables so that changes like this only need to be made in one place, but I went for the least risky change given all the activity here.  I may do a separate PR for this if you like that idea.

I'm finding this a bit overwhelming, some tests pass and some don't, but it's not clear what my change has to do with any of this.  Great that we have all these tests, but does purge-cluster.yml BEFORE my change pass all these tests?  Is there any way I can check this?   With some of the failures it's not even clear that the CI ran the test.  For example, the first failure is caused by a java exception at the top of the log file, which obviously did not even look at my code let alone try to run it.

These failures are normal:

luminous-ansible2.3-journal_collocation_auto
luminous-ansible2.3-journal_collocation_auto_dmcrypt
luminous-ansible2.3-lvm_osds
luminous-ansible2.3-purge_lvm_osds

jenkins test luminous-ansible2.3-bluestore_dmcrypt_journal

jenkins test luminous-ansible2.3-journal_collocation

@bengland2 yes, I think it'll be nice to put that regex in a variable, I think we can try that in this PR, if you don't mind :). Thanks!

I put vars in roles/ceph-osd/defaults/regex.html , is this where you would have put them?     I have to explicitly read them in, unfortunately.  Is there an easier way that reaches all the playbooks?

@bengland2 just put it in ceph-defaults/default/main.yml, all the roles will inherit from it.

However you might need to include it in the infrastructure playbooks not playing the ceph-defaults role.

This fails in luminous-ansible2.3-purge_cluster because of error below, which I do not think is my fault, but I do not fully understand how the CI runs.
TASK [define regex vars] *******************************************************
task path: /home/jenkins-build/build/workspace/ceph-ansible-prs-luminous-ansible2.3-purge_cluster/purge-cluster.yml:197
fatal: [osd0]: FAILED! => {
    "ansible_facts": {},
    "changed": false,
    "failed": true,
    "message": "Unable to find '../roles/ceph-osd/defaults/main.yml' in expected paths."
}
	to retry, use: --limit @/home/jenkins-build/build/workspace/ceph-ansible-prs-luminous-ansible2.3-purge_cluster/purge-cluster.retry

When I look at the log, it appears that files from ceph-ansible are getting pulled using statements like this:
statically included: /home/jenkins-build/build/workspace/ceph-ansible-prs-luminous-ansible2.3-purge_cluster/roles/ceph-defaults/tasks/facts.yml
statically included: /home/jenkins-build/build/workspace/ceph-ansible-prs-luminous-ansible2.3-purge_cluster/roles/ceph-defaults/tasks/check_socket.yml

I do not see roles/ceph-defaults/defaults/main.yml in this list.  Is this the list of files being pulled from git into the test area?  Where is the list of files maintained?  It is not in ceph-ansible git tree AFAICT.

Also, when I get this finally working, I can collapse the commit chain to 1 commit if this makes it easier to review and accept.

@bengland2 please rebase

I'm closing this particular PR, merging all the commits into 1 to make it easier to review and rebasing for a new PR.  THanks for the help.


Fix zone detection for cross-zone cnames

CNAMEs cannot co-exist with SOA records so responses with
a CNAME should be skipped.
The cross-zone-example.assets.sh. is currently hosted by
me (@fd) and will continue to exist for as long as the assets.sh
domain exists. (The assets.sh domain is used as a CDN and is unlikely
to go away.)
See #330

@xenolf 🏓  This patch has been running in our production environment for a while now. (it processed ±1000 domains with DNS hosted by various providers)

🎉


net: http: Provide destination address in http replies

net_app_ctx maintains multiple net contexts(net_ctx). But when http
api's wants to reply or send some data, its always choose the first
net_context in the array, which is not correct always.
net_app_get_net_pkt_with_dst() api will select proper context
based on destination address. So with the help of new api in
net_app, http can select proper context and send packets. To
achieve this, desination address is provided in http_recv_cb_t
and http_connect_cb_t callbacks. Also chaged relevant API's to
provide destination address in http message preparation methods.

Do you have a summary description for what changes existing applications must make in the meantime?

@rveerama1 This patch is semi confusing.  The change from net_app_get_net_pkt() -> net_app_get_net_pkt_with_dst() will make sure you select a context w/ the same family as dst, but it doesn't actually check any other information.  Is that the goal of the PR?  If so, why use sockaddr?  Would passing sa_family around as the parameter be clearer?

Do you have a summary description for what changes existing applications must make in the meantime?

I am working on changing samples and tests. But in mean time take a look
https://github.com/zephyrproject-rtos/zephyr/pull/5035/commits/1f838a5df52df0ce9d725c63b48a090ce5d77006#diff-780b2211d7789425a2584af4afc52b77 . This should give an overview of changes to application.

@rveerama1 This patch is semi confusing. The change from net_app_get_net_pkt() -> net_app_get_net_pkt_with_dst() will make sure you select a context w/ the same family as dst, but it doesn't actually check any other information. Is that the goal of the PR? If so, why use sockaddr? Would passing sa_family around as the parameter be clearer?

@mike-scott https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/lib/app/net_app.c#L966 and https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/lib/app/net_app.c#L656. In case of TCP select_server_ctx() calls get_server_ctx() should match dst address. But in case of UDP https://github.com/zephyrproject-rtos/zephyr/blob/master/subsys/net/lib/app/net_app.c#L665 you are assumption is right. Issue might exist in case UDP when net_app_ctx has multiple net_contexts and when selection proper context based on dst address may go wrong. I don't have any samples to verify. Have you tried anytime with net_app_ctx with multiple active net_contexts (in case of UDP) and send data over different contexts?

Issue might exist in case UDP when net_app_ctx has multiple net_contexts and when selection proper context based on dst address may go wrong. I don't have any samples to verify. Have you tried anytime with net_app_ctx with multiple active net_contexts (in case of UDP) and send data over different contexts?

Bit thorough looking at net_app.h only TCP in case of Server role has multiple net contexts. UDP shouldn't be having these kind of issue.

Codecov Report

Merging #6167 into master will decrease coverage by <.01%.
The diff coverage is 3.84%.

@@            Coverage Diff             @@
##           master    #6167      +/-   ##
==========================================
- Coverage   53.11%   53.11%   -0.01%
==========================================
  Files         414      414
  Lines       40260    40269       +9
  Branches     7759     7762       +3
==========================================
+ Hits        21384    21388       +4
- Misses      15709    15714       +5
  Partials     3167     3167

Impacted Files
Coverage Δ

subsys/net/lib/http/http.c
0% <0%> (ø)
:arrow_up:

subsys/net/lib/app/net_app.c
20.52% <7.14%> (+0.25%)
:arrow_up:

subsys/net/lib/app/server.c
27.27% <0%> (+2.02%)
:arrow_up:

Continue to review full report at Codecov.

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

Tests doesn't need any changes and samples are modified

@mbolivar Could you test with this patch and latest upstream if you can replicate the issue you were seeing earlier?

@mbolivar Could you test with this patch and latest upstream if you can replicate the issue you were seeing earlier?

@jukkar @rveerama1 this is helpful, but not a complete fix, for the issue we are seeing. With this patch, we no longer see usage faults, but our application is still broken by what looks like a spurious HTTP timeout.
I'm trying to make a smaller reproducer.

@rveerama1 please note that this patch re-adds a patch that was previously removed during the API cleanup: https://github.com/zephyrproject-rtos/zephyr/commit/e04a5412a12f6b18b8f142aa488f75f1f81aa93f
I've re-added that patch to my patches here: https://github.com/zephyrproject-rtos/zephyr/pull/6410
This will of course cause this PR to have a conflict.  Hopefully it can be fixed easily if my PR gets merged first?

Will need rebase when #6410 gets merged.

I will rebase.

#6410 is merged, if you want this to go into 1.11 please review ASAP

@carlescufi Rebased and uploaded.
@jukkar @mike-scott @mbolivar can you take a look please.

addressed @mike-scott comments. Uploaded new version.

I didn't test latest version of the patch. But code LGTM.

Not many changes in this patch, only dst addr provided as per your comment, that too it's a debug function.

Not many changes in this version, only dst addr provided as per your comment, that too it's a debug function.

Yep.  I don't think anything here will break us.  (I approved the PR).

@jukkar @tbursztyka I would need an additional review to merge this. @rveerama1 is this critical for 1.11?

@rveerama1 is this critical for 1.11?

Yes, if Zephyr is acting as a HTTP server with concurrent TCP connections and multiple active net_contexts, without this PR applications will fail to send data to right peer address.


#10 Location Sharing : Force user to enable at least one team before starting location sharing service

reverted


What is the website built in?

In what framework is the website built?
https://tailwindcss.com

Idk I think it's this one: https://tailwindcss.com/
Can't be too sure though.

Its built using Jigsaw primarily with a bit of Vue. It’s also arguably the worst codebase I’ve ever created so don’t expect to learn much from it 😅 Slowly working towards rebuilding the whole thing with Next.js and MDX.
https://github.com/tailwindcss/docs
On Aug 4, 2019, 5:07 PM -0400, Robert Dennis<EMAIL_ADDRESS>wrote:

Idk I think it's this one: https://tailwindcss.com/
Can't be too sure though.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey @adamwathan, I love what you did with tailwindcss, I'm trying to use it on my new project, with Next.js & eather emotion or styled-component. I wonder can you share your configuration.
I figure out mostly everything but bits about do I need purgecss, and babel-plugin-tailwind.
PS. Your screencasts are the best, small suggestions: make the screencasting link to more stand out, I missed it on my first stab with site.

4h later I figure it out.


Android Error : Failed to create h264 codec context

Describe the bug

I have built the binary .so files required for Android following the steps given in the readme.
I am using the .so files with the modified version of FreeRDP(an older version) android app for obvious reasons.
I have updated the LibFreeRDP.java with recent changes.
while the app runs successfully on Android version 11 and above (Checked versions Android 6, 11, 13), I notice it gives following error when I try connect to a remote desktop on Android 6.

GetProcAddress: could not find procedure AMediaCodec_setParameters: undefined symbol: AMediaCodec_setParameters Error resolving function AMediaCodec_setParameters f Failed to create h264 codec context
To Reproduce
Steps to reproduce the behavior:

Open the Connection Information
Enter connection details (IP address, username, password)
Disconnected, Reconnecting.
See error log
GetProcAddress: could not find procedure AMediaCodec_setParameters: undefined symbol: AMediaCodec_setParameters Error resolving function AMediaCodec_setParameters f Failed to create h264 codec context

Expected behavior
Should connect to remote desktop on Android 6 just like how it does for Android 11 and above.
Screenshots
If applicable, add screenshots to help explain your problem.
Application details

FreeRDP version 2.11.2 (Android)
Windows Server - Windows 10

Environment (please complete the following information):

OS: Android
Version/Distribution: Android 6
Architecture: ARM

Additional context
Application is based on older version of freeRDP android app, not sure which version it is based on.

I am using the .so files with the modified version of FreeRDP(an older version) android app for obvious reasons.
which reasons are these? (not that obvious ;))

GetProcAddress: could not find procedure AMediaCodec_setParameters: undefined symbol: AMediaCodec_setParameters Error resolving function AMediaCodec_setParameters f Failed to create h264 codec context
so you run on an outdated android version (below the minimum API for mediacodec it is compiled for) and expect the API of the newer one to be there? good luck with that assumption ;)

I´d add -DWITH_MEDIACODEC=OFF (disables hardware H264 support) and fixes your issue


Login fails

Thanks for developing this gem :heart:, I was using a scrapper for this purpose but when I was told about this library I thought it was much more practical. I also found the video of the Madrid.rb talk very interesting.
I've stumpled accross the following error - when running:
bankscrap transactions BBVA --credentials=user:<user> password:<password>

I'm getting the following error:
Traceback (most recent call last):
	19: from /home/amiedes/.rbenv/versions/2.6.5/bin/bankscrap:23:in `<main>'
	18: from /home/amiedes/.rbenv/versions/2.6.5/bin/bankscrap:23:in `load'
	17: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-2.1.1/bin/bankscrap:5:in `<top (required)>'
	16: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/thor-1.0.1/lib/thor/base.rb:485:in `start'
	15: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
	14: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
	13: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
	12: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-2.1.1/lib/bankscrap/cli.rb:78:in `transactions'
	11: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-2.1.1/lib/bankscrap/cli.rb:118:in `initialize_client_for'
	10: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-2.1.1/lib/bankscrap/cli.rb:118:in `new'
	 9: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-bbva-2.0.3/lib/bankscrap/bbva/bank.rb:20:in `initialize'
	 8: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-2.1.1/lib/bankscrap/bank.rb:29:in `initialize'
	 7: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-bbva-2.0.3/lib/bankscrap/bbva/bank.rb:140:in `login'
	 6: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-2.1.1/lib/bankscrap/bank.rb:77:in `with_headers'
	 5: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-bbva-2.0.3/lib/bankscrap/bbva/bank.rb:141:in `block in login'
	 4: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-2.1.1/lib/bankscrap/bank.rb:65:in `post'
	 3: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/mechanize-2.7.6/lib/mechanize.rb:511:in `post'
	 2: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/mechanize-2.7.6/lib/mechanize.rb:562:in `request_with_entity'
	 1: from /home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/bankscrap-bbva-2.0.3/lib/monkey_patch/mechanize.rb:32:in `fetch_with_retry'
/home/amiedes/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/mechanize-2.7.6/lib/mechanize/http/agent.rb:329:in `fetch': 500 => Net::HTTPInternalServerError for https://servicios.bbva.es/ENPP/enpp_mult_web_mobility_02/sessions/v1 -- unhandled response (Mechanize::ResponseCodeError)

The login procedure seems to be failing here. I tested this gem a few days ago and it was working OK.
I've tried to inspect the traffic with Charles Proxy but I haven't been able to configure the SSL proxy correctly for BBVA, I'm getting the following error:

But I've managed to configure it correctly for other hosts:

Other information

I'm inspecting the traffic from my phone, iPhone Xs

Questions

¿Can someone confirm if bankscrap bbva is also failing for them?
¿Can someone confirm if he/she is able to configure SSL proxying correctly?

Yes, it's failing for me as well.

Yes, sadly it's failing, I suspect they have changed something since @javiercr developed the last version of this adapter.
I'll try to take a look in the next weeks, but I don't know how easy it will be to fix this: If they changed completely how the login works, we will have to develop a new adapter. I will keep you posted.

Hi Raul! Have you had the chance to have a look at this?

Hi Raul! Have you had the chance to have a look at this?


Validate with button (noSubmit)

I want to validate a From with a button (no Submit) and the button should be disabled if is invalid
Would be great for Step Forms

Maybe just write a custom form submit handler. Then you'd be able to use a normal submit button, and unless you're on the last page of the step form, just handle it in javascript (I'm assuming that's what you're trying to do)


fix: add browser info for @web/test-runner reporter

Adds browser info from the @web/test-runner results into the outputted report. Included chrome since it seems to be different enough from chromium to warrant it.

Closer to closing out https://github.com/Brightspace/test-reporting-node/issues/59. Still need to see if I can get a better start time for individual tests.


SIGINT from docker is ignored

Read the title. These templates for issues are worse than most eulas.
My cli applications written with typer don't handle sigints sent by docker.

Can't reproduce, here it seems sigint causes a typer-based script to close just fine. You're probably not running it right in docker, or you have something else intercepting the signals.
Notably if you use COMMAND with certain images, they are not exec'd like you might expect, but there's some shell that wraps it and doesn't pass on the signals properly. To avoid it, always prefer the array version of ENTRYPOINT, and if you have some init script wrapper, remember to exec python3 (....) when you start your application at the end of it.

I'm using entrypoint myself and pointing it to the python script with the appropriate shebang, unless the official python containers from docker are doing something really weird then I don't think this is an environment issue
https://github.com/fakuivan/docker-syncthing-system/blob/13efffdfe168260669e1fa3dc6eafc67066708ce/Dockerfile

Ok, I can see that you have a 466 line script with a ton of libraries and some threading stuff, too. Usually when submitting a bug to an upstream project, it's a good idea to have a minimal piece of code that demonstrates the issue very clearly. What you have is a "haystack" where you are claiming the "needle" is typer, but I don't really think that's true, or at least it is not demonstrated here in any way.

I've had this happen in other private repos where I also use typer, and I know that typer has some handling code for sigint, so I thought I could get some help here. I've tried to isolate to isolate the issue and it seems to be related with docker compose. Even this times out at 10s when running docker compose down:
services:
  alpine-sh:
    image: alpine
    entrypoint: [ "sh", "-c", "while true; do sleep 10; done;" ]

Thanks for the help. I'm closing this, as it doesn't seem to be related.


Failed to install postgresql and redis

Hello!
I'm experimenting with laptop in a vagrant box. I have two failures, please see below:
vagrant@This-MacBook-Pro:~ % cat laptop.log

Updating Homebrew formulae ...
Already up-to-date.
Succeeded in tapping thoughtbot/formulae
Succeeded in tapping homebrew/services
Succeeded in installing ctags
Succeeded in installing git
Succeeded in installing openssl
Succeeded in installing rcm
Succeeded in installing reattach-to-user-namespace
Succeeded in installing the_silver_searcher
Succeeded in installing tmux
Succeeded in installing vim
Succeeded in installing zsh
Succeeded in installing heroku-toolbelt
Succeeded in installing parity
Succeeded in installing hub
Succeeded in installing imagemagick
Succeeded in installing qt
Succeeded in installing libyaml
Succeeded in installing node
Succeeded in installing rbenv
Succeeded in installing ruby-build
Could not find domain for
Error: Failure while executing: /bin/launchctl load -w /Users/vagrant/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
Failed in installing postgres
Could not find domain for
Error: Failure while executing: /bin/launchctl load -w /Users/vagrant/Library/LaunchAgents/homebrew.mxcl.redis.plist
Failed in installing redis

Success: 20 Fail: 2
failed

Also, please see my Vagrantfile below:
➜  osx cat Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure("2") do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "jhcook/osx-elcapitan-10.11"

  # private network setup
  # config.vm.network "private_network", type: "dhcp"
  config.vm.network :private_network, ip: "<IP_ADDRESS>"
  # enable NFS
  config.vm.synced_folder ".", "/vagrant", type: "nfs"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network "forwarded_port", guest: 80, host: 8080

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "<IP_ADDRESS>"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  # config.vm.synced_folder "../data", "/vagrant_data"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", inline: <<-SHELL
  #   apt-get update
  #   apt-get install -y apache2
  # SHELL
end

It seems different than #461, because it doesn't look like I'm having a problem with permissions but instead it has something to do with /bin/launchctl. Looking at #260 mentions:

The fix would probably be to check launchctl list to see if the service is already loaded before calling launchctl unload.

I'm not really sure what I should be looking for but this is the output from launchctl list
vagrant@This-MacBook-Pro:~ % launchctl list
PID	Status	Label
-	0	com.apple.trustd.agent
-	0	com.apple.mdworker.mail
424	0	com.apple.cfprefsd.xpc.agent
-	0	com.apple.spotlight.IndexAgent
-	0	com.apple.mdworker.bundles
-	0	com.apple.secinitd
-	0	com.apple.cvmsCompAgent3600_i386_1
-	0	com.apple.cvmsCompAgentLegacy_i386
1021	0	com.apple.tccd
-	0	com.apple.cvmsCompAgent3600_x86_64_1
-	0	com.apple.netauth.user.auth
-	0	com.apple.mbbackgrounduseragent
-	0	com.apple.cvmsCompAgent_x86_64
-	0	com.apple.pluginkit.pkd
-	0	com.apple.cvmsCompAgentLegacy_x86_64
-	0	com.apple.security.cloudkeychainproxy3
-	0	com.apple.metadata.mdflagwriter
-	0	com.apple.speech.speechsynthesisd
-	0	com.apple.mdworker.shared
-	0	com.apple.mdworker.isolation
-	0	com.apple.installandsetup.migrationhelper.user
-	0	com.apple.TrustEvaluationAgent
-	0	com.apple.FileSyncAgent.PHD
-	0	com.apple.mdworker.32bit
-	0	com.apple.secd
-	0	com.apple.cvmsCompAgent_x86_64_1
-	0	com.apple.cvmsCompAgent_i386_1
-	0	com.apple.cvmsCompAgentLegacy_i386_1
-	0	com.apple.cvmsCompAgent3600_i386
-	0	com.apple.mdworker.lsb
-	0	com.apple.storeinstallagent
-	0	com.apple.mdworker.single
-	0	com.apple.cvmsCompAgentLegacy_x86_64_1
-	0	com.apple.syncdefaultsd
-	0	com.apple.mdworker.sizing
-	0	com.apple.metadata.mdbulkimport
1278	0	com.apple.mdworker.shared.01000000-0000-0000-0000-000000000000
-	0	com.apple.cvmsCompAgent3600_x86_64
1365	0	com.apple.distnoted.xpc.agent
-	0	com.apple.cvmsCompAgent_i386

Also manually running launchctl confirms that there is something going on with the domain:
vagrant@This-MacBook-Pro:~ % launchctl load  /Users/vagrant/Library/LaunchAgents/homebrew.mxcl.postgresql.plist
Could not find domain for

Would love some help and guidance on how to sort these two out.
Also I'd like to keep discussing laptop and dotfiles on Upcase as I'm sure I'll have more questions, but it doesn't seem like there is an appropriate category. I was expecting to find a zsh, dotfiles or configuration management category but it doesn't look like it's there. What would you recommended?
Thanks for your help 😄

The solution was to get in through VirtualBox instead of only sshing in, see this stack overflow post for more details, looking forward to learning more about this project 👍  👍


heap-buffer overflow in str.c

A heap-buffer overflow occurs in the below program when provided with malformed input.


Fixing collagen synthesis

Description of the issue:
All reactions pertaining to collagen synthesis in v1.10 (MAR06983, MAR06984, MAR06985, MAR09553) are dead-end reactions. Adding an export reaction to remove 1,2-D-glucosyl-5-D-(galactosyloxy)-L-lysine-procollagen[c] enables the reactions to carry flux, except for MAR09553 which seems to be a duplicate of MAR06983. Furthermore, collagen synthesis also involves proline residues, which are not captured in the rxns in the current HUMAN-GEM.
Expected feature/value/output:
Collagen production and secretion is an important feature of cells such as fibroblast, and it can be an important sink of aminoacids in such cells. Since other extracellular matrix components like hyaluronate can be produced by the model, I believe that curating and improving this set of reactions can be of value to the community. I am creating this issue in case someone else has thought of this problem or if anyone has any ideas on how to address it. I will start by looking at how other GEMs deal with collagen synthesis.
I hereby confirm that I have:

[x] Checked that a similar issue does not exist already

@CadavidJoseL very nice input.
can you please look into if there is any transporter(s) that assist the secretion of 1,2-D-glucosyl-5-D-(galactosyloxy)-L-lysine-procollagen?

@Hao-Chalmers I'll have to look at this pathway in detail, it is more complicated than I thought. Procollagen seems to be exported in vesicles and it matures fully outside the cell. Glycosylation seems to be one of the final steps in the synthesis process, so for practical purposes maybe we consider 1,2-D-glucosyl-5-D-(galactosyloxy)-L-lysine-procollagen as the final collagen precursor to be exported. I am looking at fixing other gene associations in the HUMAN-GEM, and also at whether we can improve the collagen synthesis pathway in general, but I'll be a bit slow given my current time constraints.

More generally, I found this paper (with input from your group) that looks at incorporating protein export. Maybe this is an even better thing to integrate?

@CadavidJoseL did any idea crystallize?

@mihai-sysbio other than my previous comment, I haven't been able to spend too long on this since I am trying to get experiments to graduate this year. Terribly sorry about this. If we want to address collagen synthesis only, that might be simpler, but if we want to incorporate more secreted proteins, it's much longer. If you have an idea of how to approach the problem systematically, I am happy to help with parts of it!


cannot decompose class type have non-static data members

given we have a base msg structure , how to make it work
struct msg {
    int type;
};

struct person : public msg {
    std::string name;
    int age{};
};

auto [data, in, out] = zpp::bits::data_in_out(zpp::bits::size2b{});

   out(person{1009, "Person1", 25});
    person p;
    in(p);

error: cannot decompose class type 'person': both it and its base class 'msg' have non-static data members

Check this issue resolution - https://github.com/eyalz800/zpp_bits/issues/90
There is no way to automatically get into the base class, I might introduce a better way to handle this, but currently see if the issue above helps you workaround classes with base classes.

Check this issue resolution - #90
There is no way to automatically get into the base class, I might introduce a better way to handle this, but currently see if the issue above helps you workaround classes with base classes.

from what I understand from that solution , is that every driveed class has to have extra boilerplate to work , any other solution that can be done once in the base class ?

I don’t believe there is a generic solution to this issue, because there is no way to enumerate the base classes of a class, but even if there was a way - there is still the issue that structured binding will not work if you have a class with a base class and both have data members - and because structured binding is what we use to serialize the data members - we have no option but to require this boilerplate anyway. Does that make sense?

I don’t believe there is a generic solution to this issue, because there is no way to enumerate the base classes of a class, but even if there was a way - there is still the issue that structured binding will not work if you have a class with a base class and both have data members - and because structured binding is what we use to serialize the data members - we have no option but to require this boilerplate anyway. Does that make sense?

yeah it makes sense now , thanks for the clarification .
the idea was to force adding a Msg->type, so the buffer structure will always be 2 bytes for size , followed by 2 bytes for type , so when I receive the msg/packet, I can easily know which msg/packet it is , so I can deserialize it to the correct structure based on the second two bytes of the buffer.
something like:
const uint16_t packetId = *reinterpret_cast<uint16_t*>(buffer + 2);
switch (packetId)
{
  case 1009:{
    //this is person packet/msg
    person p;
    in(p);
    break;
  }
}

hopefully I made it clear enough .

You are describing exactly what std::variant does for you without the switch case, go ahead and try it!

See this test code -
https://github.com/eyalz800/zpp_bits/blob/main/test/src/test_variant.cpp

See this test code - https://github.com/eyalz800/zpp_bits/blob/main/test/src/test_variant.cpp

sure , thanks for the reference.


Styling (mostly)

Hey guys,
I have tuned the code a little while catching up with your progress here.
Please see if that, mostly styling, PR might be useful. (feel free to throw it away if you like, the purpose was to understand how that works and not to refactor it)
There are some commits that improve error handling and possible issues that may be cherry-picked if you'd like not to change the styling here.
Here is a more detailed list of changes:

improve error handling
improve logger definition
fix log-level case sensitivity
change default log level to 'info'
fix typos in user messages
simplify some variables and functions
upgrade dependencies
add dependabot integration
fix possible price conversion issue

P.S: I have not tested it, so be my guest. Hopefully, it won't break anything 😉

@anton-yurchenko I've added a PR with some potential changes to this here: https://github.com/anton-yurchenko/infracost/pull/1

Merged, thanks!


[BUG] Can't deploy RKE2 1.21.10+rke2r1 with JeOS

Describe the bug
When we deploy RKE2 1.21.10+rke2r1 on JeOS, we can't start the cluster. If we use crictl ps -a, there is no container.
To Reproduce

Setup Harvester cluster.
Run Rancher v2.6-head.
Import Harvester cluster to Rancher.
Import Image SLES15-SP3-JeOS.x86_64-15.3-OpenStack-Cloud-GM.qcow2 to Harvester.
Create 1-node RKE2 1.21.10+rke2r1 with JeOS on Harvester.
RKE2 cluster is stuck in Provisioning status.

Expected behavior
RKE2 can run.
Environment:

Harvester ISO version: master-da3f1778-head
Underlying Infrastructure: KVM

Additional context
We have a workaround for this issue. After running following commands, RKE2 can be installed and cluster will become Active.
zypper ar --priority=200 http://download.opensuse.org/distribution/leap/15.3/repo/oss repo-oss
zypper ref
zypper in apparmor-parser

Related issue: https://github.com/harvester/harvester/issues/1954

Duplicate with https://github.com/harvester/harvester/issues/1973. Close this one.


[FLINK-5979] Backwards compatibility for HeapKeyedStateBackend serialization format (1.2 -> 1.3)

This PR re-establishes the broken backwards compatibility in the serialization format of KeyedStateTable between Flink 1.2 and Flink 1.3.
It also implements a push-down of reduce, fold, aggregate, and merge to the StateTable implementations.
This PR sits on top of #3466 .

R @aljoscha

Thanks for the review, @aljoscha. I have addressed your comments. Merging this now.

Merged in ab014ef.


[Index] Introduce IndexSystem::foreachUnitTestSymbolReferencedByOutputPaths()

This is useful for retrieving all the unit test class/method occurrences that are referenced from a set of output file paths and their associated units.

@swift-ci Please test


Fixes book routes

This was a mix of merge conflict resolution and getting the addAuthors functionality to work. Ran into several conflicts when trying to add it, after resolving conflicts and before merging I found that some of the code for a few of the routes vanished. Also the books.sql file is nearly empty lol
Fixes

the add book route now requires the title and author fields to be filled out in the form and create the book and author entries one after the other, storing their returned IDs in variables, then inserts an entry into book_authors using the IDs

Problems with Fix

Currently there is no check if an author already exists in the table, so there will be duplicate entries for authors.
Because of this the book_authors table wont be as effecient, a book with the same author as another will have a different author.id in the book_authors table.

Also not merging this incase some of your work is missing from it. Not sure how or wtf happened but some of the routes rolled back.


Multi lines

Does this have support for multiple lines in the graph?

sure, you can find it in d3 document. It's not related to d3node


Added NOMINMAX to CMakeLists.txt

Added definition of NOMINMAX to cmake. This will avoid conflicts with windows macros when compiling for windows.

Code Changes
Documentation Changes

thanks, this same fix is already in another pr waiting to be merged though!


Increase Attachment Size

Currently, there is a limit for attachment sizes which is reported as too low for some users. We need to support attachment sizes of up to (at least) 100MB.
We need to change the way attachments are encrypted and perform most of the attachment-actions using streams and not im RAM anymore.
This needs to be synchronized with Ginlo for Android.

Fixed with 4.2.2 of Ginlo/Ginlo Business Release (Commit: https://github.com/cdskev/ginlo-ios/commit/768922534dcaa7d59c1f1fef7af7ea71eb9e5a7a)


Build doesn't work in docker rootless mode

Trying to make a build locally resulted in the following error:
+ docker run --rm -i -u 1000:1000 -v /home/phantom/FFmpeg-Builds/ffbuild:/ffbuild docker.pkg.github.com/btbn/ffmpeg-builds/win32-lgpl-shared:latest bash -s
+ cd /ffbuild
+ rm -rf ffmpeg prefix
+ git clone https://github.com/FFmpeg/FFmpeg.git ffmpeg
fatal: could not create work tree dir 'ffmpeg': Permission denied

Looks like the issue is that the commands inside the container are run with my own user id, when they should be run with user id 1. If I remove -u "$(id -u):$(id -g)" from build.sh, then the commands succeed. I'd send a pull request with this change, but I'm assuming there must be some significance to manually setting the user id in the script, otherwise the option wouldn't be there.

Without running it as the same user/group than the one that's invoking the command causes issues later in the script, because build-artifacts end up owned by root.
Packaging artifacts and deleting leftovers fails then without doing so as root as well.
Since this is designed to run on Github-Actions, where dockerd runs as root, this cannot be changed and in turn means a setup where docker-root is not real root isn't supported.
I also don't really see any way to check if the uid dockerd runs as is identical to the one of the current user, which is the check necessary to drop the User-Switch.

Please try again with latest changes.

Looks like it works now. Thank you very much for fixing.


function to Eliminate All Whitespace

What is needed:
Function to remove all whitespace characters from a string.
Where to Code:
Find the Contribution Station in textCleaning.js.
Contribution Steps:
1. Create a development branch out of this issue. (Visible on the right column of the issue)2. Code your function in that branch.3. Raise a Pull Request to merge that branch into the main branch.For more clarity, follow the visual guide in CONTRIBUTE.md.

Hi @swanandapps , Please allow me to work on this.

Added the PR for this function #30


'DataFlowAnalysis' object has no attribute 'op_LOAD_CLOSURE'

    self.dispatch(info, inst)
  File "numba/dataflow.py", line 80, in dispatch
    fn = getattr(self, fname)
AttributeError: 'DataFlowAnalysis' object has no attribute 'op_LOAD_CLOSURE'

Failed at object (analyzing bytecode)
'DataFlowAnalysis' object has no attribute 'op_LOAD_CLOSURE'

I got the above errors when I tried the following code:
`
@jit
def train_lasso(Data,y, thresh_ = 0.000001, eps =0.0000001,lambda_ls = 0.1):
Theta_0 = train_ls(Data, y, lambda_ls)
N, L = Data.shape
@jit
def get_z(theta_):
    z = np.sqrt(theta_*theta_ + eps)
    return z
@jit
def get_theta(z_):
    Z_diag = np.diag(z_/2)
    a = np.dot(Data.T, Data) +  lambda_ls * Z_diag
    b = np.dot(Data.T, y)
    theta = np.linalg.lstsq(a, b)[0]
    return theta
this_theta = Theta_0
while 1:
    tmp = this_theta
    this_z = get_z(this_theta)
    this_theta = get_theta(this_z)
    diff = this_theta - tmp
    print np.linalg.norm(diff,1)
    if np.linalg.norm(diff,1) < thresh_:
        break
return this_theta

`

Hi,
The code above wasn't pasted properly: some indentation is bogus.
In any case, the answer here is that closures are not supported by Numba: you cannot declare a function inside a JITted function.


sudo make install does not work

make: *** No rule to make target 'install'.  Stop.

OK, now it worked. I have had to go to cmake GUI and set some parameters like cuda SDK path manually: /usr/local/cuda-8.0/


Consider using ActivatorUtilities.CreateFactory in CompressionProviderFactory

ActivatorUtilities.CreateInstance is 30x slower than invoking factory delegate.

@pakrym just for perf?

Yes


Fixing README

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state "None”]
write issue no. here
https://github.com/dhairyagothi/50_days_50_web_project/issues/285
Email id used to regsiter for VSoc'24
<EMAIL_ADDRESS>Description
[Please include a brief description of the changes or features added]
I have updated the README such that it shows all the contributors
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Security enhancement
[ ] Other (specify): _______________

check in issue by entering [X] in boxes
Screenshots / Videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]

Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have followed the code style guidelines of this project.
[x] I have checked for any existing open issues that my pull request may address.
[x] I have ensured that my changes do not break any existing functionality.
[x] Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.
[x] I have read the resources for guidance listed below.
[x] I have followed security best practices in my code changes.

check in issue by entering [X] in boxes
Additional Context
[Include any additional information or context that might be helpful for reviewers.]
I have also updated .gitignore, to ignore .vscode folder
Contribution Guidelines
Thank you for considering contributing to our project! To ensure smooth collaboration and effective contribution management, please adhere to the following guidelines:
Issue Creation

Limit on Issues:

Each contributor is allowed to create a maximum of 4 issues per day. This helps us manage and address issues efficiently.

Contribution Levels

Basic Contributions:

This project is primarily focused on documentation. Most of the setup has been completed, so contributors will generally need to work on basic code tasks, such as writing tests.
For these tasks, issues will be assigned the Easy label.

Acknowledging Hard Work:

If a contributor puts in significant effort on a task, the issue will be upgraded to Medium. This is our way of recognizing and appreciating extra effort.

Feature Additions and Component Work:

Contributors working on new features or components using JSX/TSX will be assigned a level based on the complexity and quality of their work.
The more complex and valuable the contribution, the higher the level assigned.

Level Definitions

Easy:

Tasks are straightforward, such as fixing minor bugs, writing tests, or making simple documentation updates.

Medium:

Tasks require more effort, such as addressing complex bugs, improving existing features, or making substantial documentation improvements.

Hard:

Tasks are highly complex and involve significant new feature development, major refactoring, or extensive contributions to the project’s core components.

We look forward to your contributions and appreciate your effort in helping us improve the project!

resolve conflicts @deepesh611


Remove request dependency from core directory

request is an unnecessary dependency of the core package as it is only used in the /website directory as a required primary dependency.
Test Plan
request is only used in the /website directory. Searched entire package with regex.
/require\(('|")request+\('|"))/gi
All applicable local tests passed!

@hramos This change looks good to me -- website/package.json already lists request under its dependencies.

Sounds good to me. No need to manually import this as the dependency should already be present in our offline cache.

@facebook-github-bot shipit


Update parens.ts

Use the real parentheses characters instead of the shrinked ones

Sorry I didn't see this. I believe https://github.com/captbaritone/vscode-implicit-parentheses/pull/4 fixes this in a way that preserves the option of having a visual distinction for those tho prefer it.


Clarify download experience

Description
Downloading of files was implemented after feature request https://github.com/jiahaog/nativefier/issues/185 . It works, but nothing tells the user about the pending downloads or where files are downloaded:

We should at least notify when the download completes.
Location of downloaded files should be clear.
There could be some sort of visual progress indicator. Maybe not a full-fledged bottom bar like Chrome's as Nativefier aims at a chrome-less experience, so maybe just an overlay?

Specifications

Nativefier 7.1.0
OS: All

By the way, where are files downloaded? I created draw.io with Nativefier  and when I export something (for example, pdf, png) nothing seems to happen. I'm just a beginner with Nativefier actually.

By the way, where are files downloaded? I created draw.io with Nativefier and when I export something (for example, pdf, png) nothing seems to happen.

@bartier files are downloaded straight to your OS-defined Downloads folder. Typically, that would be:

Windows: C:\Users\bartier\Downloads
macOS/Linux: ~/Downloads

@ronjouch Thanks! Additionally, it would be nice if there was an option to change where the file downloaded will be saved (Downloads folder or always asks where to save).

Hey
I just found a way to enable "Save As" (not sure if this is already mentioned before).
Earlier, my web app was by default downloading the file straight to the download folder.
So basically, I just opened up the source files and edited the "main.js".
In main.js, I changed this   			if (!opts.saveAs) { 				item.setSavePath(filePath); 			} to this  			if (opts.saveAs) { 				item.setSavePath(filePath); 			} Removed the '!'
This worked absolutely fine, as now the "Save As" dialog box poped whenever there was a download event.
Specifications

Version of Nativefier (run $ nativefier --version): v7.3.1
Version of Node.js (run $ node --version): v4.5.0
OS: Mac
Architecture OSX Darwin

@sameerkumar18 In this case probably the entire if statement could be removed leaving just the dialog opening code:
item.setSavePath(filePath);
Basically it's just a way to force dialog box popup on each download request.

At least notify when the download completes is what i wanted.
I can not find item.setSavePath(filePath); in source code.
version: 7.4.0

+1 ... a way to at least change the download path would be great. It doesn't even have to be a flag, I'm willing to hardcode it manually if that's what it takes. I just want it on my desktop.


Add Dark Mode

Add option to switch between light and dark mode.

Hi, any ETA on this one? If implemented in next release, I'd buy you a cup of coffee/tea :-)
BTW, I am the one asking for it in the forums.

It's like very hard. Reskinning the whole IDE is not trivial.

The ETA for this is pretty much infinite without external help.

Actually, it might be more trivial than you think.  Being Qt Creator based, you should be able to just load a new style sheet when you launch it, which is just a command-line option. Here's one that's available: https://draculatheme.com/qtcreator/

Sorry, the current mode is dark mode. What you guys want is light mode.
A lot of the widgets are custom styled by me. They aren't done so through QtCreator. So, I'll have to add this option and then fix styling for one widget after another. This is probably 20+ hours of work.
As I have to focus on drivers like triple buffering for the camera I don't really have time.

If you want it done convince Arduino folks it needs to be done. Then I can get contracting hours for it.

Hmm, a pity, I believe there are as many who loves dark modes as who cannot stand them for different reasons. My reason are simple practical, not based on feelings. I can't use dark mode at all as I need to turn up the brightness too much which kills my eyes, latest when switching to another application.

No, I understand dark mode has issues. In particular, it's quite a challenge to use outside in sunlight.
Okay, so, this is easy to do... I can allow the editor style to change to a different mode. This will look uglyish, but, change 70% of the application to light mode.

No, I understand dark mode has issues. In particular, it's quite a challenge to use outside in sunlight.
Okay, so, this is easy to do... I can allow the editor style to change to a different mode. This will look uglyish, but, change 70% of the application to light mode.

Awesome! If needed, I'd be happy to test it when (not if :-) ) you have it ready and give feedback!

Any hope to have option of light mode in next IDE-version?

Nope, however, tabs, split view, and minimap in the scroll bar will come.
For light mode to happen I honestly need help.

Ok, unfortunately I don't have the knowledge or capacity to help myself. Am though willing to test when the time comes.

Now when you're upgrading Qt libraries, any chance of getting a light mode option?

Yeah, Qt 6.5 which will be updating to has this feature. So, it will be across the board.

Great news, at least for me!

This is fixed for version 4.0.0. Light mode will also land too. The whole IDE is themed now so it can be whatever color you like.


added cancel audio recordings

Recorded all possible beeps which can be set on a cancel delivery 1f command by using this command on the rileylink: https://github.com/ps2/rileylink_ios/blob/omnikit/OmniKit/MessageBlocks/CancelDeliveryCommand.swift#L36


juan additional routes

Added the routes for future budget, moneyflow and current month spending.
Trello card: https://trello.com/c/5ijJlqON/37-setup-routes-and-render-visuals

Run npm test from the local branch to see if that fixes failing check

I second @redpage001s comment for removing the test.


Response with ReadableStream + HTMLRewriter throws error

Reproduction repo: https://github.com/Mitch528/workerd-streams-repro
><EMAIL_ADDRESS>start
> workerd serve config.capnp --experimental

workerd/server/server.c++:1842: error: Uncaught exception: workerd/io/io-context.c++:1211: failed: remote.jsg.Error: The script will never generate a response.
stack: 102a7e3b4 102a7ebd4 102a7f3e0 10492a58c 10492d6b0

Fixed in #120

Thank you very much for the simple repro!

This issue has been fixed in main


Clear manager in the import loop (console command)

Calling $manager->clear() in the import loop to avoid memory problems.
Pull Request
Related issue
Fixes #350
What does this PR do?

Add a call of $manager->clear() in the import loop to avoir memory problems.

PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Can you fix CS?

bors merge

Thank you @johndodev


Create Packet.net storage device to quickly mount boxes

The amount of time it takes to download boxes from Vagrant Cloud is now upwards of an hour per box due to unknown reasons causing slowness.
The best way to address this problem will be to create a Packet storage device pre-populated with boxes and mount it when running CI jobs. This should speed up the overall CI job considerably.

Added in #288