Trouble working with Spark-CSV package (error: object databricks is not a member of package com)

Hey all,
Thanks for your work on spark-csv.
I'm working with Scala 2.11.6, and Spark 1.3.1 built from source via:
mvn -Pyarn -Phadoop-2.4 -Dscala-2.11 -DskipTests clean package
The error is encountered when running spark shell via:
spark-shell --packages com.databricks:spark-csv_2.11:1.0.3
The full trace of the commands:
MYCOMP:spark-1.3.1 mo.omer$ spark-shell --packages com.databricks:spark-csv_2.11:1.0.3
Ivy Default Cache set to: /Users/mo.omer/.ivy2/cache
The jars for the packages stored in: /Users/mo.omer/.ivy2/jars
:: loading settings :: url = jar:file:/Users/mo.omer/install/spark-1.3.1/assembly/target/scala-2.11/spark-assembly-1.3.1-hadoop2.4.0.jar!/org/apache/ivy/core/settings/ivysettings.xml
com.databricks#spark-csv_2.11 added as a dependency
:: resolving dependencies :: org.apache.spark#spark-submit-parent;1.0
        confs: [default]
        found com.databricks#spark-csv_2.11;1.0.3 in central
        found org.apache.commons#commons-csv;1.1 in central
:: resolution report :: resolve 134ms :: artifacts dl 10ms
        :: modules in use:
        com.databricks#spark-csv_2.11;1.0.3 from central in [default]
        org.apache.commons#commons-csv;1.1 from central in [default]
        ---------------------------------------------------------------------
        |                  |            modules            ||   artifacts   |
        |       conf       | number| search|dwnlded|evicted|| number|dwnlded|
        ---------------------------------------------------------------------
        |      default     |   2   |   0   |   0   |   0   ||   2   |   0   |
        ---------------------------------------------------------------------
:: retrieving :: org.apache.spark#spark-submit-parent
        confs: [default]
        0 artifacts copied, 2 already retrieved (0kB/5ms)
log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
15/04/22 12:55:46 INFO SecurityManager: Changing view acls to: mo.omer
15/04/22 12:55:46 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/22 12:55:46 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/22 12:55:46 INFO HttpServer: Starting HTTP Server
15/04/22 12:55:46 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/22 12:55:46 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:54264
15/04/22 12:55:46 INFO Utils: Successfully started service 'HTTP server' on port 54264.
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 1.3.1
      /_/

Using Scala version 2.11.2 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_67)
Type in expressions to have them evaluated.
Type :help for more information.
15/04/22 12:55:50 INFO Main: Spark class server started at http://<IP_ADDRESS>:54264
15/04/22 12:55:50 INFO SparkContext: Running Spark version 1.3.1
15/04/22 12:55:50 INFO SecurityManager: Changing view acls to: mo.omer
15/04/22 12:55:50 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/22 12:55:50 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/22 12:55:50 INFO Slf4jLogger: Slf4jLogger started
15/04/22 12:55:50 INFO Remoting: Starting remoting
15/04/22 12:55:50 INFO Remoting: Remoting started; listening on addresses :[akka.tcp://sparkDriver@mincbm-nmx3837:54265]
15/04/22 12:55:50 INFO Utils: Successfully started service 'sparkDriver' on port 54265.
15/04/22 12:55:50 INFO SparkEnv: Registering MapOutputTracker
15/04/22 12:55:50 INFO SparkEnv: Registering BlockManagerMaster
15/04/22 12:55:51 INFO DiskBlockManager: Created local directory at /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-c9480ffd-0b6e-4003-b98e-5beedd3dc609/blockmgr-af979d44-8772-4510-9ad2-dc028c809305
15/04/22 12:55:51 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
15/04/22 12:55:51 INFO HttpFileServer: HTTP File server directory is /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-c41f3e51-c62d-4e7b-beea-c65951890108/httpd-da0a7c96-a08a-4120-8727-a3e395591ecb
15/04/22 12:55:51 INFO HttpServer: Starting HTTP Server
15/04/22 12:55:51 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/22 12:55:51 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:54266
15/04/22 12:55:51 INFO Utils: Successfully started service 'HTTP file server' on port 54266.
15/04/22 12:55:51 INFO SparkEnv: Registering OutputCommitCoordinator
15/04/22 12:55:51 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/22 12:55:51 INFO AbstractConnector: Started SelectChannelConnector@<IP_ADDRESS>:4040
15/04/22 12:55:51 INFO Utils: Successfully started service 'SparkUI' on port 4040.
15/04/22 12:55:51 INFO SparkUI: Started SparkUI at http://mincbm-nmx3837:4040
15/04/22 12:55:51 INFO SparkContext: Added JAR file:/Users/mo.omer/.ivy2/jars/spark-csv_2.11.jar at http://<IP_ADDRESS>:54266/jars/spark-csv_2.11.jar with timestamp<PHONE_NUMBER>186
15/04/22 12:55:51 INFO SparkContext: Added JAR file:/Users/mo.omer/.ivy2/jars/commons-csv.jar at http://<IP_ADDRESS>:54266/jars/commons-csv.jar with timestamp<PHONE_NUMBER>187
15/04/22 12:55:51 INFO Executor: Starting executor ID <driver> on host localhost
15/04/22 12:55:51 INFO Executor: Using REPL class URI: http://<IP_ADDRESS>:54264
15/04/22 12:55:51 INFO AkkaUtils: Connecting to HeartbeatReceiver: akka.tcp://sparkDriver@mincbm-nmx3837:54265/user/HeartbeatReceiver
15/04/22 12:55:51 INFO NettyBlockTransferService: Server created on 54267
15/04/22 12:55:51 INFO BlockManagerMaster: Trying to register BlockManager
15/04/22 12:55:51 INFO BlockManagerMasterActor: Registering block manager localhost:54267 with 265.4 MB RAM, BlockManagerId(<driver>, localhost, 54267)
15/04/22 12:55:51 INFO BlockManagerMaster: Registered BlockManager
15/04/22 12:55:51 INFO Main: Created spark context..
Spark context available as sc.
15/04/22 12:55:51 INFO Main: Created sql context..
SQL context available as sqlContext.

scala> import com.databricks.spark.csv._
<console>:20: error: object databricks is not a member of package com
       import com.databricks.spark.csv._
                  ^
// ctrl-D
scala> 15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/metrics/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/stages/stage/kill,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/static,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/executors/threadDump/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/executors/threadDump,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/executors/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/executors,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/environment/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/environment,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/storage/rdd/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/storage/rdd,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/storage/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/storage,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/stages/pool/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/stages/pool,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/stages/stage/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/stages/stage,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/stages/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/stages,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/jobs/job/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/jobs/job,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/jobs/json,null}
15/04/22 12:59:17 INFO ContextHandler: stopped o.s.j.s.ServletContextHandler{/jobs,null}
15/04/22 12:59:17 INFO SparkUI: Stopped Spark web UI at http://mincbm-nmx3837:4040
15/04/22 12:59:17 INFO DAGScheduler: Stopping DAGScheduler
15/04/22 12:59:17 INFO MapOutputTrackerMasterActor: MapOutputTrackerActor stopped!
15/04/22 12:59:17 INFO MemoryStore: MemoryStore cleared
15/04/22 12:59:17 INFO BlockManager: BlockManager stopped
15/04/22 12:59:17 INFO BlockManagerMaster: BlockManagerMaster stopped
15/04/22 12:59:17 INFO SparkContext: Successfully stopped SparkContext
15/04/22 12:59:17 INFO OutputCommitCoordinator$OutputCommitCoordinatorActor: OutputCommitCoordinator stopped!
15/04/22 12:59:17 INFO RemoteActorRefProvider$RemotingTerminator: Shutting down remote daemon.
15/04/22 12:59:17 INFO RemoteActorRefProvider$RemotingTerminator: Remote daemon shut down; proceeding with flushing remote transports.

Not sure if I've done something wrong, or if the documentation is outdated, or...?

Hi @momer. Thanks for filing this. The issue seems to be with Spark on Yarn. Would you mind filing a JIRA for Spark: https://issues.apache.org/jira/browse/SPARK

Hi @momer , Could you please try spark-shell with --packages brkyvz:demo-scala-python:0.1.3 just to test whether this is a package related issue or Spark issue. I believe this is related to Yarn. If you fail at import com.brkyvz.spark.WordCounter then it is not package specific.
Thanks,
Burak

Yes, import com.brkyvz.spark.WordCounter failed as well :/
On Wed, Apr 22, 2015 at 6:45 PM, Burak Yavuz<EMAIL_ADDRESS>wrote:

Hi @momer https://github.com/momer , Could you please try spark-shell
with --packages brkyvz:demo-scala-python:0.1.3 just to test whether this
is a package related issue or Spark issue. I believe this is related to
Yarn. If you fail at import com.brkyvz.spark.WordCounter then it is not
package specific.
Thanks,
Burak
—
Reply to this email directly or view it on GitHub
https://github.com/databricks/spark-csv/issues/54#issuecomment-95368611.

Then it is probably a Spark with Yarn issue. Is there any way you can test this locally if possible? With Scala 2.11 just to make sure it is not a Scala 2.11 problem (I doubt it, but would be nice to double check)

Works in scala with
MINCBM-NMX3837:scalastuff mo.omer$ scala -cp ./demo-scala-python-0.1.3-s_2.10.jar
Welcome to Scala version 2.11.6 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_67).
Type in expressions to have them evaluated.
Type :help for more information.

scala> import com.brkyvz.spark.WordCounter
import com.brkyvz.spark.WordCounter

scala> :quit

However, spark-shell with --jars fails:
MINCBM-NMX3837:scalastuff mo.omer$ spark-shell --jars ./demo-scala-python-0.1.3-s_2.10.jar
log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
15/04/23 11:10:11 INFO SecurityManager: Changing view acls to: mo.omer
15/04/23 11:10:11 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/23 11:10:11 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/23 11:10:11 INFO HttpServer: Starting HTTP Server
15/04/23 11:10:11 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 11:10:11 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:50419
15/04/23 11:10:11 INFO Utils: Successfully started service 'HTTP server' on port 50419.
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 1.3.1
      /_/

Using Scala version 2.11.2 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_67)
Type in expressions to have them evaluated.
Type :help for more information.
15/04/23 11:10:15 INFO Main: Spark class server started at http://<IP_ADDRESS>:50419
15/04/23 11:10:15 INFO SparkContext: Running Spark version 1.3.1
15/04/23 11:10:16 INFO SecurityManager: Changing view acls to: mo.omer
15/04/23 11:10:16 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/23 11:10:16 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/23 11:10:16 INFO Slf4jLogger: Slf4jLogger started
15/04/23 11:10:16 INFO Remoting: Starting remoting
15/04/23 11:10:16 INFO Remoting: Remoting started; listening on addresses :[akka.tcp://sparkDriver@<IP_ADDRESS>:50420]
15/04/23 11:10:16 INFO Utils: Successfully started service 'sparkDriver' on port 50420.
15/04/23 11:10:16 INFO SparkEnv: Registering MapOutputTracker
15/04/23 11:10:16 INFO SparkEnv: Registering BlockManagerMaster
15/04/23 11:10:16 INFO DiskBlockManager: Created local directory at /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-84c31049-de58-4ffe-a0db-3d4e21cc1eb7/blockmgr-0a935446-4dd7-4f61-ba23-76864d48b1c4
15/04/23 11:10:16 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
15/04/23 11:10:16 INFO HttpFileServer: HTTP File server directory is /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-fd4c4317-940f-4e41-adb4-979be53de049/httpd-4ef0d987-0854-4519-be21-b2c120f88a01
15/04/23 11:10:16 INFO HttpServer: Starting HTTP Server
15/04/23 11:10:16 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 11:10:16 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:50421
15/04/23 11:10:16 INFO Utils: Successfully started service 'HTTP file server' on port 50421.
15/04/23 11:10:16 INFO SparkEnv: Registering OutputCommitCoordinator
15/04/23 11:10:16 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 11:10:16 INFO AbstractConnector: Started SelectChannelConnector@<IP_ADDRESS>:4040
15/04/23 11:10:16 INFO Utils: Successfully started service 'SparkUI' on port 4040.
15/04/23 11:10:16 INFO SparkUI: Started SparkUI at http://<IP_ADDRESS>:4040
15/04/23 11:10:16 INFO SparkContext: Added JAR file:/Users/mo.omer/install/scalastuff/./demo-scala-python-0.1.3-s_2.10.jar at http://<IP_ADDRESS>:50421/jars/demo-scala-python-0.1.3-s_2.10.jar with timestamp<PHONE_NUMBER>629
15/04/23 11:10:16 INFO Executor: Starting executor ID <driver> on host localhost
15/04/23 11:10:16 INFO Executor: Using REPL class URI: http://<IP_ADDRESS>:50419
15/04/23 11:10:16 INFO AkkaUtils: Connecting to HeartbeatReceiver: akka.tcp://sparkDriver@<IP_ADDRESS>:50420/user/HeartbeatReceiver
15/04/23 11:10:16 INFO NettyBlockTransferService: Server created on 50422
15/04/23 11:10:16 INFO BlockManagerMaster: Trying to register BlockManager
15/04/23 11:10:16 INFO BlockManagerMasterActor: Registering block manager localhost:50422 with 265.4 MB RAM, BlockManagerId(<driver>, localhost, 50422)
15/04/23 11:10:16 INFO BlockManagerMaster: Registered BlockManager
15/04/23 11:10:16 INFO Main: Created spark context..
Spark context available as sc.
15/04/23 11:10:17 INFO Main: Created sql context..
SQL context available as sqlContext.

scala> import com.brkyvz.spark.WordCounter
<console>:20: error: object brkyvz is not a member of package com
       import com.brkyvz.spark.WordCounter
                  ^

I assume that's what you meant by running it locally in the spark-shell, right?

If it's not even working with --jars then there might be a problem with your setup. As far as I'm aware, --jars works properly with Yarn.
Can you run locally like spark-shell --master local[*] --packages ...

No dice @brkyvz. I'm not sure what the problem with my setup could be - I've run my example apps fine on spark, and in the spark-shell.
An example app running:
MyComp:exampleApp mo.omer$ spark-submit --class "ExampleApp" --master local[4] target/scala-2.10/simple-project_2.10-1.0.jar
Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
15/04/23 13:16:43 INFO SparkContext: Running Spark version 1.3.1
15/04/23 13:16:44 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
15/04/23 13:16:44 INFO SecurityManager: Changing view acls to: mo.omer
15/04/23 13:16:44 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/23 13:16:44 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/23 13:16:44 INFO Slf4jLogger: Slf4jLogger started
15/04/23 13:16:44 INFO Remoting: Starting remoting
15/04/23 13:16:44 INFO Remoting: Remoting started; listening on addresses :[akka.tcp://sparkDriver@<IP_ADDRESS>:52492]
15/04/23 13:16:44 INFO Utils: Successfully started service 'sparkDriver' on port 52492.
15/04/23 13:16:44 INFO SparkEnv: Registering MapOutputTracker
15/04/23 13:16:44 INFO SparkEnv: Registering BlockManagerMaster
15/04/23 13:16:44 INFO DiskBlockManager: Created local directory at /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-c1e5677c-6117-44a2-add6-dc7fd210867a/blockmgr-b8112e25-47ae-4743-a74f-eac61d4aee8b
15/04/23 13:16:44 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
15/04/23 13:16:44 INFO HttpFileServer: HTTP File server directory is /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-da07b671-e5e8-45df-961d-d7185329b0f6/httpd-80964865-46b3-45e1-b191-9f2c92382ae6
15/04/23 13:16:44 INFO HttpServer: Starting HTTP Server
15/04/23 13:16:45 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 13:16:45 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:52493
15/04/23 13:16:45 INFO Utils: Successfully started service 'HTTP file server' on port 52493.
15/04/23 13:16:45 INFO SparkEnv: Registering OutputCommitCoordinator
15/04/23 13:16:45 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 13:16:45 INFO AbstractConnector: Started SelectChannelConnector@<IP_ADDRESS>:4040
15/04/23 13:16:45 INFO Utils: Successfully started service 'SparkUI' on port 4040.
15/04/23 13:16:45 INFO SparkUI: Started SparkUI at http://<IP_ADDRESS>:4040
15/04/23 13:16:45 INFO SparkContext: Added JAR file:/Users/mo.omer/projects/misc/spark/exampleApp/target/scala-2.10/simple-project_2.10-1.0.jar at http://<IP_ADDRESS>:52493/jars/simple-project_2.10-1.0.jar with timestamp<PHONE_NUMBER>135
15/04/23 13:16:45 INFO Executor: Starting executor ID <driver> on host localhost
15/04/23 13:16:45 INFO AkkaUtils: Connecting to HeartbeatReceiver: akka.tcp://sparkDriver@<IP_ADDRESS>:52492/user/HeartbeatReceiver
15/04/23 13:16:45 INFO NettyBlockTransferService: Server created on 52494
15/04/23 13:16:45 INFO BlockManagerMaster: Trying to register BlockManager
15/04/23 13:16:45 INFO BlockManagerMasterActor: Registering block manager localhost:52494 with 265.4 MB RAM, BlockManagerId(<driver>, localhost, 52494)
15/04/23 13:16:45 INFO BlockManagerMaster: Registered BlockManager
15/04/23 13:16:45 INFO MemoryStore: ensureFreeSpace(163705) called with curMem=0, maxMem=278302556
15/04/23 13:16:45 INFO MemoryStore: Block broadcast_0 stored as values in memory (estimated size 159.9 KB, free 265.3 MB)
15/04/23 13:16:45 INFO MemoryStore: ensureFreeSpace(22692) called with curMem=163705, maxMem=278302556
15/04/23 13:16:45 INFO MemoryStore: Block broadcast_0_piece0 stored as bytes in memory (estimated size 22.2 KB, free 265.2 MB)
15/04/23 13:16:45 INFO BlockManagerInfo: Added broadcast_0_piece0 in memory on localhost:52494 (size: 22.2 KB, free: 265.4 MB)
15/04/23 13:16:45 INFO BlockManagerMaster: Updated info of block broadcast_0_piece0
15/04/23 13:16:45 INFO SparkContext: Created broadcast 0 from textFile at ExampleApp.scala:20
15/04/23 13:16:45 INFO FileInputFormat: Total input paths to process : 1
15/04/23 13:16:45 INFO SparkContext: Starting job: reduce at ExampleApp.scala:29
15/04/23 13:16:45 INFO DAGScheduler: Registering RDD 3 (map at ExampleApp.scala:28)
15/04/23 13:16:45 INFO DAGScheduler: Got job 0 (reduce at ExampleApp.scala:29) with 1 output partitions (allowLocal=false)
15/04/23 13:16:45 INFO DAGScheduler: Final stage: Stage 1(reduce at ExampleApp.scala:29)
15/04/23 13:16:45 INFO DAGScheduler: Parents of final stage: List(Stage 0)
15/04/23 13:16:45 INFO DAGScheduler: Missing parents: List(Stage 0)
15/04/23 13:16:45 INFO DAGScheduler: Submitting Stage 0 (MapPartitionsRDD[3] at map at ExampleApp.scala:28), which has no missing parents
15/04/23 13:16:46 INFO MemoryStore: ensureFreeSpace(3472) called with curMem=186397, maxMem=278302556
15/04/23 13:16:46 INFO MemoryStore: Block broadcast_1 stored as values in memory (estimated size 3.4 KB, free 265.2 MB)
15/04/23 13:16:46 INFO MemoryStore: ensureFreeSpace(2560) called with curMem=189869, maxMem=278302556
15/04/23 13:16:46 INFO MemoryStore: Block broadcast_1_piece0 stored as bytes in memory (estimated size 2.5 KB, free 265.2 MB)
15/04/23 13:16:46 INFO BlockManagerInfo: Added broadcast_1_piece0 in memory on localhost:52494 (size: 2.5 KB, free: 265.4 MB)
15/04/23 13:16:46 INFO BlockManagerMaster: Updated info of block broadcast_1_piece0
15/04/23 13:16:46 INFO SparkContext: Created broadcast 1 from broadcast at DAGScheduler.scala:839
15/04/23 13:16:46 INFO DAGScheduler: Submitting 1 missing tasks from Stage 0 (MapPartitionsRDD[3] at map at ExampleApp.scala:28)
15/04/23 13:16:46 INFO TaskSchedulerImpl: Adding task set 0.0 with 1 tasks
15/04/23 13:16:46 INFO TaskSetManager: Starting task 0.0 in stage 0.0 (TID 0, localhost, ANY, 1404 bytes)
15/04/23 13:16:46 INFO Executor: Running task 0.0 in stage 0.0 (TID 0)
15/04/23 13:16:46 INFO Executor: Fetching http://<IP_ADDRESS>:52493/jars/simple-project_2.10-1.0.jar with timestamp<PHONE_NUMBER>135
15/04/23 13:16:46 INFO Utils: Fetching http://<IP_ADDRESS>:52493/jars/simple-project_2.10-1.0.jar to /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-393956c6-3b49-4214-963a-a220d603799a/userFiles-d3a567f7-a495-409e-aab4-bbdb37d16594/fetchFileTemp6043197432884401951.tmp
15/04/23 13:16:46 INFO Executor: Adding file:/var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-393956c6-3b49-4214-963a-a220d603799a/userFiles-d3a567f7-a495-409e-aab4-bbdb37d16594/simple-project_2.10-1.0.jar to class loader
15/04/23 13:16:46 INFO CacheManager: Partition rdd_1_0 not found, computing it
15/04/23 13:16:46 INFO HadoopRDD: Input split: hdfs://localhost:9000/user/mo.omer/dcm/NetworkClick_1057_03-29-2015.updated.log.gz:0+3340552
15/04/23 13:16:46 INFO deprecation: mapred.tip.id is deprecated. Instead, use mapreduce.task.id
15/04/23 13:16:46 INFO deprecation: mapred.task.id is deprecated. Instead, use mapreduce.task.attempt.id
15/04/23 13:16:46 INFO deprecation: mapred.task.is.map is deprecated. Instead, use mapreduce.task.ismap
15/04/23 13:16:46 INFO deprecation: mapred.task.partition is deprecated. Instead, use mapreduce.task.partition
15/04/23 13:16:46 INFO deprecation: mapred.job.id is deprecated. Instead, use mapreduce.job.id
15/04/23 13:16:46 INFO CodecPool: Got brand-new decompressor [.gz]
15/04/23 13:16:46 INFO MemoryStore: ensureFreeSpace(36045133) called with curMem=192429, maxMem=278302556
15/04/23 13:16:46 INFO MemoryStore: Block rdd_1_0 stored as values in memory (estimated size 34.4 MB, free 230.9 MB)
15/04/23 13:16:46 INFO BlockManagerInfo: Added rdd_1_0 in memory on localhost:52494 (size: 34.4 MB, free: 231.0 MB)
15/04/23 13:16:46 INFO BlockManagerMaster: Updated info of block rdd_1_0
15/04/23 13:16:47 INFO Executor: Finished task 0.0 in stage 0.0 (TID 0). 2491 bytes result sent to driver
15/04/23 13:16:47 INFO TaskSetManager: Finished task 0.0 in stage 0.0 (TID 0) in 1412 ms on localhost (1/1)
15/04/23 13:16:47 INFO TaskSchedulerImpl: Removed TaskSet 0.0, whose tasks have all completed, from pool
15/04/23 13:16:47 INFO DAGScheduler: Stage 0 (map at ExampleApp.scala:28) finished in 1.422 s
15/04/23 13:16:47 INFO DAGScheduler: looking for newly runnable stages
15/04/23 13:16:47 INFO DAGScheduler: running: Set()
15/04/23 13:16:47 INFO DAGScheduler: waiting: Set(Stage 1)
15/04/23 13:16:47 INFO DAGScheduler: failed: Set()
15/04/23 13:16:47 INFO DAGScheduler: Missing parents for Stage 1: List()
15/04/23 13:16:47 INFO DAGScheduler: Submitting Stage 1 (ShuffledRDD[4] at reduceByKey at ExampleApp.scala:28), which is now runnable
15/04/23 13:16:47 INFO MemoryStore: ensureFreeSpace(2024) called with curMem=36237562, maxMem=278302556
15/04/23 13:16:47 INFO MemoryStore: Block broadcast_2 stored as values in memory (estimated size 2024.0 B, free 230.8 MB)
15/04/23 13:16:47 INFO MemoryStore: ensureFreeSpace(1471) called with curMem=36239586, maxMem=278302556
15/04/23 13:16:47 INFO MemoryStore: Block broadcast_2_piece0 stored as bytes in memory (estimated size 1471.0 B, free 230.8 MB)
15/04/23 13:16:47 INFO BlockManagerInfo: Added broadcast_2_piece0 in memory on localhost:52494 (size: 1471.0 B, free: 231.0 MB)
15/04/23 13:16:47 INFO BlockManagerMaster: Updated info of block broadcast_2_piece0
15/04/23 13:16:47 INFO SparkContext: Created broadcast 2 from broadcast at DAGScheduler.scala:839
15/04/23 13:16:47 INFO DAGScheduler: Submitting 1 missing tasks from Stage 1 (ShuffledRDD[4] at reduceByKey at ExampleApp.scala:28)
15/04/23 13:16:47 INFO TaskSchedulerImpl: Adding task set 1.0 with 1 tasks
15/04/23 13:16:47 INFO TaskSetManager: Starting task 0.0 in stage 1.0 (TID 1, localhost, PROCESS_LOCAL, 1125 bytes)
15/04/23 13:16:47 INFO Executor: Running task 0.0 in stage 1.0 (TID 1)
15/04/23 13:16:47 INFO ShuffleBlockFetcherIterator: Getting 1 non-empty blocks out of 1 blocks
15/04/23 13:16:47 INFO ShuffleBlockFetcherIterator: Started 0 remote fetches in 2 ms
15/04/23 13:16:47 INFO Executor: Finished task 0.0 in stage 1.0 (TID 1). 1082 bytes result sent to driver
15/04/23 13:16:47 INFO TaskSetManager: Finished task 0.0 in stage 1.0 (TID 1) in 418 ms on localhost (1/1)
15/04/23 13:16:47 INFO DAGScheduler: Stage 1 (reduce at ExampleApp.scala:29) finished in 0.418 s
15/04/23 13:16:47 INFO TaskSchedulerImpl: Removed TaskSet 1.0, whose tasks have all completed, from pool
15/04/23 13:16:47 INFO DAGScheduler: Job 0 finished: reduce at ExampleApp.scala:29, took 1.925765 s
Most frequently occurring user in NetworkClick files: (AMsySZYUxM2cCs2_QKxaDKaroWH6,20)

And the local spark-shell --master attempt failing:
MINCBM-NMX3837:scalastuff mo.omer$ spark-shell --master local[*] --packages com.databricks:spark-csv_2.11:1.0.3
Ivy Default Cache set to: /Users/mo.omer/.ivy2/cache
The jars for the packages stored in: /Users/mo.omer/.ivy2/jars
:: loading settings :: url = jar:file:/Users/mo.omer/install/spark-1.3.1/assembly/target/scala-2.11/spark-assembly-1.3.1-hadoop2.4.0.jar!/org/apache/ivy/core/settings/ivysettings.xml
com.databricks#spark-csv_2.11 added as a dependency
:: resolving dependencies :: org.apache.spark#spark-submit-parent;1.0
        confs: [default]
        found com.databricks#spark-csv_2.11;1.0.3 in central
        found org.apache.commons#commons-csv;1.1 in central
:: resolution report :: resolve 143ms :: artifacts dl 7ms
        :: modules in use:
        com.databricks#spark-csv_2.11;1.0.3 from central in [default]
        org.apache.commons#commons-csv;1.1 from central in [default]
        ---------------------------------------------------------------------
        |                  |            modules            ||   artifacts   |
        |       conf       | number| search|dwnlded|evicted|| number|dwnlded|
        ---------------------------------------------------------------------
        |      default     |   2   |   0   |   0   |   0   ||   2   |   0   |
        ---------------------------------------------------------------------
:: retrieving :: org.apache.spark#spark-submit-parent
        confs: [default]
        0 artifacts copied, 2 already retrieved (0kB/6ms)
log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
15/04/23 13:05:44 INFO SecurityManager: Changing view acls to: mo.omer
15/04/23 13:05:44 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/23 13:05:44 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/23 13:05:44 INFO HttpServer: Starting HTTP Server
15/04/23 13:05:44 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 13:05:44 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:52307
15/04/23 13:05:44 INFO Utils: Successfully started service 'HTTP server' on port 52307.
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 1.3.1
      /_/

Using Scala version 2.11.2 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_67)
Type in expressions to have them evaluated.
Type :help for more information.
15/04/23 13:05:49 INFO Main: Spark class server started at http://<IP_ADDRESS>:52307
15/04/23 13:05:49 INFO SparkContext: Running Spark version 1.3.1
15/04/23 13:05:49 INFO SecurityManager: Changing view acls to: mo.omer
15/04/23 13:05:49 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/23 13:05:49 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/23 13:05:49 INFO Slf4jLogger: Slf4jLogger started
15/04/23 13:05:49 INFO Remoting: Starting remoting
15/04/23 13:05:50 INFO Remoting: Remoting started; listening on addresses :[akka.tcp://sparkDriver@<IP_ADDRESS>:52315]
15/04/23 13:05:50 INFO Utils: Successfully started service 'sparkDriver' on port 52315.
15/04/23 13:05:50 INFO SparkEnv: Registering MapOutputTracker
15/04/23 13:05:50 INFO SparkEnv: Registering BlockManagerMaster
15/04/23 13:05:50 INFO DiskBlockManager: Created local directory at /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-e8938bd8-a2bd-44fd-b994-86736a7b2aab/blockmgr-1a3a7c24-ac5a-448c-aa74-540fbc325c62
15/04/23 13:05:50 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
15/04/23 13:05:50 INFO HttpFileServer: HTTP File server directory is /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-c82a47e7-deb4-4abb-bce7-0e24d66099b1/httpd-7e1020c6-cd3b-484a-ae33-7216de5594b0
15/04/23 13:05:50 INFO HttpServer: Starting HTTP Server
15/04/23 13:05:50 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 13:05:50 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:52317
15/04/23 13:05:50 INFO Utils: Successfully started service 'HTTP file server' on port 52317.
15/04/23 13:05:50 INFO SparkEnv: Registering OutputCommitCoordinator
15/04/23 13:05:50 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 13:05:50 INFO AbstractConnector: Started SelectChannelConnector@<IP_ADDRESS>:4040
15/04/23 13:05:50 INFO Utils: Successfully started service 'SparkUI' on port 4040.
15/04/23 13:05:50 INFO SparkUI: Started SparkUI at http://<IP_ADDRESS>:4040
15/04/23 13:05:50 INFO SparkContext: Added JAR file:/Users/mo.omer/.ivy2/jars/spark-csv_2.11.jar at http://<IP_ADDRESS>:52317/jars/spark-csv_2.11.jar with timestamp<PHONE_NUMBER>593
15/04/23 13:05:50 INFO SparkContext: Added JAR file:/Users/mo.omer/.ivy2/jars/commons-csv.jar at http://<IP_ADDRESS>:52317/jars/commons-csv.jar with timestamp<PHONE_NUMBER>596
15/04/23 13:05:50 INFO Executor: Starting executor ID <driver> on host localhost
15/04/23 13:05:50 INFO Executor: Using REPL class URI: http://<IP_ADDRESS>:52307
15/04/23 13:05:50 INFO AkkaUtils: Connecting to HeartbeatReceiver: akka.tcp://sparkDriver@<IP_ADDRESS>:52315/user/HeartbeatReceiver
15/04/23 13:05:50 INFO NettyBlockTransferService: Server created on 52318
15/04/23 13:05:50 INFO BlockManagerMaster: Trying to register BlockManager
15/04/23 13:05:50 INFO BlockManagerMasterActor: Registering block manager localhost:52318 with 265.4 MB RAM, BlockManagerId(<driver>, localhost, 52318)
15/04/23 13:05:50 INFO BlockManagerMaster: Registered BlockManager
15/04/23 13:05:50 INFO Main: Created spark context..
Spark context available as sc.
15/04/23 13:05:51 INFO Main: Created sql context..
SQL context available as sqlContext.

scala> import com.databricks.spark.csv._
<console>:20: error: object databricks is not a member of package com
       import com.databricks.spark.csv._
                  ^

Update: I can import com.databricks.spark.csv._ if I download and build spark-csv with sbt package, and then add the scala 2.11 jar from the target folder onto my SPARK_CLASSPATH env variable, and then launch spark-shell a la:
MyComp:spark-csv mo.omer$ spark-shell --packages com.databricks:spark-csv_2.10:1.0.3
Ivy Default Cache set to: /Users/mo.omer/.ivy2/cache
The jars for the packages stored in: /Users/mo.omer/.ivy2/jars
:: loading settings :: url = jar:file:/Users/mo.omer/install/spark-1.3.1/assembly/target/scala-2.11/spark-assembly-1.3.1-hadoop2.4.0.jar!/org/apache/ivy/core/settings/ivysettings.xml
com.databricks#spark-csv_2.10 added as a dependency
:: resolving dependencies :: org.apache.spark#spark-submit-parent;1.0
        confs: [default]
        found com.databricks#spark-csv_2.10;1.0.3 in central
        found org.apache.commons#commons-csv;1.1 in list
:: resolution report :: resolve 137ms :: artifacts dl 6ms
        :: modules in use:
        com.databricks#spark-csv_2.10;1.0.3 from central in [default]
        org.apache.commons#commons-csv;1.1 from list in [default]
        ---------------------------------------------------------------------
        |                  |            modules            ||   artifacts   |
        |       conf       | number| search|dwnlded|evicted|| number|dwnlded|
        ---------------------------------------------------------------------
        |      default     |   2   |   0   |   0   |   0   ||   2   |   0   |
        ---------------------------------------------------------------------
:: retrieving :: org.apache.spark#spark-submit-parent
        confs: [default]
        0 artifacts copied, 2 already retrieved (0kB/5ms)
log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Using Spark's default log4j profile: org/apache/spark/log4j-defaults.properties
15/04/23 15:45:10 INFO SecurityManager: Changing view acls to: mo.omer
15/04/23 15:45:10 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/23 15:45:10 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/23 15:45:10 INFO HttpServer: Starting HTTP Server
15/04/23 15:45:10 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 15:45:10 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:53509
15/04/23 15:45:10 INFO Utils: Successfully started service 'HTTP server' on port 53509.
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 1.3.1
      /_/

Using Scala version 2.11.2 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_67)
Type in expressions to have them evaluated.
Type :help for more information.
15/04/23 15:45:14 INFO Main: Spark class server started at http://<IP_ADDRESS>:53509
15/04/23 15:45:14 INFO SparkContext: Running Spark version 1.3.1
15/04/23 15:45:14 WARN SparkConf:
SPARK_CLASSPATH was detected (set to ':/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/spark-csv/target/scala-2.11:/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/spark-csv/target/scala-2.11/spark-csv_2.11-1.0.3.jar').
This is deprecated in Spark 1.0+.

Please instead use:
 - ./spark-submit with --driver-class-path to augment the driver classpath
 - spark.executor.extraClassPath to augment the executor classpath

15/04/23 15:45:14 WARN SparkConf: Setting 'spark.executor.extraClassPath' to ':/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/spark-csv/target/scala-2.11:/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/spark-csv/target/scala-2.11/spark-csv_2.11-1.0.3.jar' as a work-around.
15/04/23 15:45:14 WARN SparkConf: Setting 'spark.driver.extraClassPath' to ':/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/spark-csv/target/scala-2.11:/Users/mo.omer/install/scalastuff/commons-csv-1.1/commons-csv-1.1.jar:/Users/mo.omer/install/scalastuff/spark-csv/target/scala-2.11/spark-csv_2.11-1.0.3.jar' as a work-around.
15/04/23 15:45:14 INFO SecurityManager: Changing view acls to: mo.omer
15/04/23 15:45:14 INFO SecurityManager: Changing modify acls to: mo.omer
15/04/23 15:45:14 INFO SecurityManager: SecurityManager: authentication disabled; ui acls disabled; users with view permissions: Set(mo.omer); users with modify permissions: Set(mo.omer)
15/04/23 15:45:14 INFO Slf4jLogger: Slf4jLogger started
15/04/23 15:45:14 INFO Remoting: Starting remoting
15/04/23 15:45:14 INFO Remoting: Remoting started; listening on addresses :[akka.tcp://sparkDriver@<IP_ADDRESS>:53510]
15/04/23 15:45:14 INFO Utils: Successfully started service 'sparkDriver' on port 53510.
15/04/23 15:45:14 INFO SparkEnv: Registering MapOutputTracker
15/04/23 15:45:14 INFO SparkEnv: Registering BlockManagerMaster
15/04/23 15:45:14 INFO DiskBlockManager: Created local directory at /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-b2510692-567f-4838-a04e-8a8bbfb8001b/blockmgr-6abf5fff-7c08-4afc-8da4-c1b82223d8b2
15/04/23 15:45:14 INFO MemoryStore: MemoryStore started with capacity 265.4 MB
15/04/23 15:45:14 INFO HttpFileServer: HTTP File server directory is /var/folders/xq/x0l63td56jzcvrn0mx2wgcvw0000gn/T/spark-dfa46938-8689-4ca0-ade0-bd1636cfca4b/httpd-4ddbbfe8-54d7-4723-a8ce-ca6d5e2308fa
15/04/23 15:45:14 INFO HttpServer: Starting HTTP Server
15/04/23 15:45:14 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 15:45:14 INFO AbstractConnector: Started SocketConnector@<IP_ADDRESS>:53511
15/04/23 15:45:14 INFO Utils: Successfully started service 'HTTP file server' on port 53511.
15/04/23 15:45:14 INFO SparkEnv: Registering OutputCommitCoordinator
15/04/23 15:45:14 INFO Server: jetty-8.y.z-SNAPSHOT
15/04/23 15:45:14 INFO AbstractConnector: Started SelectChannelConnector@<IP_ADDRESS>:4040
15/04/23 15:45:14 INFO Utils: Successfully started service 'SparkUI' on port 4040.
15/04/23 15:45:14 INFO SparkUI: Started SparkUI at http://<IP_ADDRESS>:4040
15/04/23 15:45:14 INFO SparkContext: Added JAR file:/Users/mo.omer/.ivy2/jars/spark-csv_2.10.jar at http://<IP_ADDRESS>:53511/jars/spark-csv_2.10.jar with timestamp<PHONE_NUMBER>739
15/04/23 15:45:14 INFO SparkContext: Added JAR file:/Users/mo.omer/.ivy2/jars/commons-csv.jar at http://<IP_ADDRESS>:53511/jars/commons-csv.jar with timestamp<PHONE_NUMBER>739
15/04/23 15:45:14 INFO Executor: Starting executor ID <driver> on host localhost
15/04/23 15:45:14 INFO Executor: Using REPL class URI: http://<IP_ADDRESS>:53509
15/04/23 15:45:14 INFO AkkaUtils: Connecting to HeartbeatReceiver: akka.tcp://sparkDriver@<IP_ADDRESS>:53510/user/HeartbeatReceiver
15/04/23 15:45:14 INFO NettyBlockTransferService: Server created on 53512
15/04/23 15:45:14 INFO BlockManagerMaster: Trying to register BlockManager
15/04/23 15:45:14 INFO BlockManagerMasterActor: Registering block manager localhost:53512 with 265.4 MB RAM, BlockManagerId(<driver>, localhost, 53512)
15/04/23 15:45:14 INFO BlockManagerMaster: Registered BlockManager
15/04/23 15:45:14 INFO Main: Created spark context..
Spark context available as sc.
15/04/23 15:45:15 INFO Main: Created sql context..
SQL context available as sqlContext.

scala> import com.databricks.spark.csv._
import com.databricks.spark.csv._

I'm having the same issue. I'm simply trying to import com.databricks.spark.csv.CsvContext but getting an error in spark-shell
log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Using Spark's repl log4j profile: org/apache/spark/log4j-defaults-repl.properties
To adjust logging level use sc.setLogLevel("INFO")
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /___/ .__/\_,_/_/ /_/\_\   version 1.5.0
      /_/

Using Scala version 2.10.4 (Java HotSpot(TM) 64-Bit Server VM, Java 1.7.0_79)
Type in expressions to have them evaluated.
Type :help for more information.
16/11/10 13:18:13 WARN MetricsSystem: Using default name DAGScheduler for source because spark.app.id is not set.
Spark context available as sc.
16/11/10 13:18:15 WARN Connection: BoneCP specified but not present in CLASSPATH (or one of dependencies)
16/11/10 13:18:15 WARN Connection: BoneCP specified but not present in CLASSPATH (or one of dependencies)
16/11/10 13:18:17 WARN ObjectStore: Version information not found in metastore. hive.metastore.schema.verification is not enabled so recording the schema version 1.2.0
16/11/10 13:18:18 WARN ObjectStore: Failed to get database default, returning NoSuchObjectException
16/11/10 13:18:19 WARN NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
16/11/10 13:18:19 WARN Connection: BoneCP specified but not present in CLASSPATH (or one of dependencies)
16/11/10 13:18:19 WARN Connection: BoneCP specified but not present in CLASSPATH (or one of dependencies)
SQL context available as sqlContext.

scala> import com.databricks.spark.csv.CsvContext
<console>:19: error: object databricks is not a member of package com
       import com.databricks.spark.csv.CsvContext
                  ^

scala>


Updated the STO roadmap for FY 25

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65c440b6f18c1f1a7fab7cca--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65c4442cb74af820bcd64595--harness-developer.netlify.app

@priteshchandaliya should not be too bad to fix. Can take a look on what's in source control (works) and re-modify?

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65c45366a3386929b9aa0460--harness-developer.netlify.app

LGTM!


Delete button bug

Jodit Version:  3.2.9
When there are empty lines pressing on delete button has strange behavior.
Firstly, it deletes one line but then returns it again.

Expected behavior:
delete button should remove next empty line.
Actual behavior:
delete button removes next empty line and returns it back.

Bug still exists. You can easily reproduce it on the main or playground page doesn't matter.

Make several empty lines - without (un)ordered list
Try to delete line with delete button


Updating Install-rpdp.sh. The changes were lost on the last merge

Added .local change to allow FQDNs for the hostname
re-done the changes from the earlier PR to copy the sound files and the remainder of the dependencies missing

@obsolescence please review and merge if appropriate


feat: add a version command

closes #127
Output for go build
./oasdiff version
oasdiff version: main

Output for docker build .
docker run oasdiff version
oasdiff version: v1.1.39-5-ga22039b

Output for goreleaser build --snapshot
./oasdiff version
oasdiff version: 1.1.39-SNAPSHOT-a22039b

Codecov Report

Merging #128 (a22039b) into main (a39d705) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #128   +/-   ##
=======================================
  Coverage   89.49%   89.49%
=======================================
  Files          70       70
  Lines        3949     3949
=======================================
  Hits         3534     3534
  Misses        298      298
  Partials      117      117

Flag
Coverage Δ

unittests
89.49% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Support expressions for line-dasharray

Currently the paint_factory only allows fixed arrays of numbers for line-dasharray and not expressions like ["get", "stroke-dasharray"]:
https://github.com/greensopinion/dart-vector-tile-renderer/blob/1d9f5f59bb67e221ecc4c3f1c8b464acc0da78ef/lib/src/themes/paint_factory.dart#L119-L126

feel free to send a PR!


Kbd autorepeat api fix

That looks ok for me, anyway I suspect that the change of behaviour might impact project that would like to migrate to 3.0. Perhaps it's the good timing to open a "migrate to 3.0" page in the WIKI or have a specific doc file in the repo ?

@hardening https://github.com/FreeRDP/FreeRDP/wiki/Migration-from-2.x-to-3.0
if you would be so kind to add your review we can merge ;)


Update submodule sitl_gazebo to latest Tue Dec 24 12:39:15 UTC 2019

- sitl_gazebo in PX4/Firmware (0e70578052d938ea87c70837a15185b99dbb2309): https://github.com/PX4/sitl_gazebo/commit/073da14f6e62d3b3c45e40eda556c0523f86d870
- sitl_gazebo current upstream: https://github.com/PX4/sitl_gazebo/commit/25ab469cb1d9b0ca303f64f0e5ab94d6563d852a
- Changes: https://github.com/PX4/sitl_gazebo/compare/073da14f6e62d3b3c45e40eda556c0523f86d870...25ab469cb1d9b0ca303f64f0e5ab94d6563d852a

25ab469 2019-12-24 Julian Oes - travis: reduce CI load, only build master branch
2b16eab 2019-12-24 Julian Oes - travis: update docker tags
7a0a462 2019-11-21 TSC21 - Travis: bump container tags to 2019-11-20
3d23283 2019-11-19 TSC21 - scripts: xacro.py: fix style for readable content
502b476 2019-11-18 TSC21 - Travis: MacOS stage: install Python 3 dependencies
88c3489 2019-11-18 TSC21 - scripts: format and clean
4b63700 2019-11-18 TSC21 - CMake: look for Python3
24e9902 2019-11-18 TSC21 - scripts: make usage of Python3 only
ad84d48 2019-12-19 bresch - Iris_base: update ADIS16448 gyro and accel noise density to with values from Kalibr

Broken waiting on python update.

@dagar Anychange that this will get merged?

@Jaeyoung-Lim this was brought in already


ReportType refactor

Refactor details pages to use common ReportType. This will help the details pages use common base components.

verified


Remove tailwind from package

We are using tailwind just to style the slash menu and a few other things. We could use custom SCSS there and get rid of tailwindCSS from the package.
enhancement _t

@goutham-subramanyam _a Could you please look into this?
cc: @amaldinesh7


orca (in R) does not save in /tmp relative to root

using
orca(p, "/tmp/plot.pdf")
the plot gets saved relative to the current folder ./tmp/plot.pdf and not in /tmp/plot.pdf (relative to root). Using the server it does properly save relative to root
server$export(p, "/tmp/plot.pdf")

also the command line program has the same bug:
orca-1.3.1.AppImage graph '{ "data": [{"y": [1,2,1]}] }' -o /tmp/fig.pdf --format pdf
The figure fig.pdf gets created in a subfolder tmp beneath the current folder, not the /tmp (under root). I think this is an important bug because many times temporary files must be created in the /tmp.


DOC: Update Google Web Store and Microsoft Store icons to latest - they are out of date

Updated via bb11321d98f422461ae00400d37370a0e5c04402


[CORE] Minor refactor WholeStageTransformContext

What changes were proposed in this pull request?
WholeStageTransformContext's intputAttr and outputAttr are unused.
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

Just note some code style test failure for CH backend. You can try to create a fix:
mvn spotless:apply -Pbackends-clickhouse -Pspark-3.2 -DskipTests -Pspark-ut
or
mvn spotless:apply -Pbackends-clickhouse -Pspark-3.3 -DskipTests -Pspark-ut

Just note some code style test failure for CH backend. You can try to create a fix: mvn spotless:apply -Pbackends-clickhouse -Pspark-3.2 -DskipTests -Pspark-ut or mvn spotless:apply -Pbackends-clickhouse -Pspark-3.3 -DskipTests -Pspark-ut

Thanks! will request for review when all CI passed.

Hi @PHILO-HE, this PR is ready for review.


move js to ecma to avoid jsx problems

Issue #3 is probably due to https://github.com/nvim-treesitter/nvim-treesitter/commit/69a55e86cebec679f26b0d1fda28bb0359d6dd64
Note also this previous commit https://github.com/nvim-treesitter/nvim-treesitter/commit/3b8c2ea492917fcb3c0e88ad6682dbd355cc0644 message:

create ecma base for use in js and ts which fixes jsx issues

Typescript injections should not import javascript, which pulls jsx, but ecma.
So I moved javascript injections to ecma, and I removed the typescript injections all together, since they already inherit from ecma.

Thank you so much! Can confirm that your solution works perfectly.
Was blind without syntax highlighting from the inline templates and styles but now no more!
Much appreciated!

If someone is still struggling with this error, I can confirm that @elgiano  solution works.
If you're using packer:
  use({ "elgiano/nvim-treesitter-angular", branch = "topic/jsx-fix" })

Thank you elgiano again!

Hi!
Thanks for fixing this!
Is there anything I need to do to get it working properly? I installed this branch... my inline templates are still not being highlighted. Any gotcha's I need to have set up with nvim-treesitter?
Thanks!

@kohane27, thanks for the reply!
I just figured out I had an issue with the html parser being compiled and installed correctly. I fixed that and now I have inline template highlighting working.
Thanks to you both!

@steelsojka could you merge this please?

Can confirm that this fix still works as expected

what needs to be done, to get this merged?


Maybe swizzle layoutSubviews, setNeedsLayout, and sizeThatFits: to avoid subclassing

Feedback I got from a fellow dev was that he's super hesitant to subclass UIView. I think I understand; I think I'd feel the same if I hadn't been a part of creating YOLayout.
Opening this issue to discuss the possibility of swizzling in the required layout methods and implementing layout as a category of UIView. Benefit of this is that it should work on UIControl, UIButton, UITableViewCell & UIView right out of the box.
I think we'd still keep YOView subclass around --the viewInit method itself is useful enough to merit this subclass. But we'd also provide the option of adding a YOLayout to an arbitrary UIView subclass.
What do you think?

Maybe the category would be something like this. In this method all the necessary swizzling would happen as well as the creation and storage of the YOLayout object.
@interface UIView (YOLayout)
- (void)yo_setLayoutBlock:(YOLayoutBlock)layoutBlock
@end

Cool thing about this, is that it should just work with UIControl, UIScrollView, etc

Closed by #53


chore: set up goreleaser and remove terraform inline build

Per: https://github.com/abcxyz/jvs/issues/129
Next steps:

Set up GPG
Set up release workflow to use goreleaser (initially without java release)
Set up cosign to sign images (requires a bit more discussion on key management)

cc: @sqin2019

I don't think we'd need both GPG and cosign, would we?


Feature/dock 1106/fix broken org logo images

Description
Currently, if the admin-specified org logo image is not loadable, in its place, the UI displays a broken image icon and/or the img tag's alt text, depending upon the browser.  This PR displays a default org logo image, instead of the broken image/alt text, using an entirely client-side mechanism.  An org with no admin-specified org logo image is rendered as before.
When a browser cannot successfully load an image, it fires an error event on the corresponding img tag:
https://developer.mozilla.org/en-US/docs/Web/API/Element/error_event
This PR adds an error event handler to each org logo img tag that passes the target img element to the underlying component's  orgLogoService.setDefault method, which sets the element's img.src to the default org logo url.  setDefault includes logic to set img.src no more than once, to avoid an infinite load loop if the default org logo is also not loadable.
I made the change in four places in the UI where the org logo appears:

organizations page
organization page
collection page
my organizations page

Did I miss anywhere?  Possibly.
I selected the default org logo, which is a modified version of this CC0 (public domain) svg:
https://www.svgrepo.com/svg/70462/organization
The goal for the default org logo was something generic that suggested the notion of an organization and was simple and non-descript enough to blend into the UI.  I think it meets those goals, but I'd recommend we engage our UI person regarding its suitability.  It is easy to change.
Issue
https://ucsc-cgl.atlassian.net/browse/DOCK-1106
dockstore/dockstore#3070
Screenshot

Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that your code compiles by running npm run build
[x] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[x] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[x] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[x] Do not use cookies, although this may change in the future
[x] Run npm audit and ensure you are not introducing new vulnerabilities
[x] Do due diligence on new 3rd party libraries, checking for CVEs
[x] Don't allow user-uploaded images to be served from the Dockstore domain

What if you did this instead as a component or directive? Then its usage could something like (my Angular component syntax is rusty, could be off):
<app-img-with-fallback [src] ="gravatarUrl$ | async" class="big-org-logo"
alt="organization logo"
fallbackImage="../../../../assets/images/dockstore/default-org-logo.svg">
</app-img-with-fallback>

You could also have a fallbackText attribute and use the same component for your collections feature. And maybe the fallbackImage is an enum instead of a path, like DEFAULT_ORG_LOGO.

Makes it reusable for non-org use cases, if ever have any
Makes it clear what the fallback is by looking at the HTML.
Mainly hides $event.target, which I think you should in Angular

If you think you could/should reuse the component for the collections, then it's probably worth the change; if not, then borderline.

Before wrapping the img in an Angular component, I would suggest the other ticket be completed, and we can refactor if desired.  The component solution is more complex and, in my experience, introduces annoying quirks/issues.  Not sure if it's worth it in this case.
Honestly, I probably would have implemented this with an attribute directive:
https://angular.io/guide/attribute-directives
ala
<img [src]="whatever.jpg" ... default-org-image>
or
<img [src]="whatever.jpg" ... default-src="ORG_LOGO">
or whatever.
But, the img[default] selector would add a bit of overhead to the templates, and given the spirit of the "no functions in templates" mandate, I thought that it might elicit non-positive reactions, so I did not.

But, the img[default] selector would add a bit of overhead to the templates, and given the spirit of the "no functions in templates" mandate, I thought that it might elicit non-positive reactions, so I did not.

Can you please elaborate on that? Where would the function in the template be coming from?

But, the img[default] selector would add a bit of overhead to the templates, and given the spirit of the "no functions in templates" mandate, I thought that it might elicit non-positive reactions, so I did not.

Can you please elaborate on that? Where would the function in the template be coming from?

No explicit function call, but computational overhead that's probably greater than that of calling very simple functions sparingly in templates.

This PR has changed significantly, see the updated description at top.


Some Scenarios running by line number are not executed

Describe the bug
Some Scenarios from the list with semicolon like cucumber feature_name.feature:NNN:MMM:KKK skipped to execute.
To Reproduce
It's really hard to say how to reproduce. Attached part of the log where skipped test cases are highlited.
Expected behavior
cucumber feature_name.feature:NNN:MMM:KKK should execute all Scenarios from the list with semicolon.
Context & Motivation
I use parallel_tests gem to execute in parallel threads (usually 8 threads). In parallel_cucumber i pass tags, and parallel_cucumber generates commands with features and line numbers with semicolon to execute. Last times we noticed that some tests cases were skipped to execute when started our regression in Jenkins. In last regression were skipped 25 test cases out of 763. Added more details (used --verbose option of parallel_cucumber) to the Jenkins log and found that those test cases were tagged in correct way, but somehow skipped to execute by cucumber. All skipped test cases are in 1 thread. Some of them Scenario Outline, some of them Scenario. All numbers point to the correct line, that contains Scenario: or Scenario Outline: keyword, not inside of Scenario.
Screenshots

Your Environment
Ruby 2.5.3
gem 'cucumber', '5.3.0'
gem 'parallel_tests', '3.6.0'
centOS7 / x86-64

Would you have some examples - a reproduction feature with command lines for example - to help us to reproduce?

Today I had another regression execution and got different set of skipped test cases. Could not find any dependency why exactly these test cases were skipped.
Initial command line to execute from Jenkins:
parallel_cucumber features/ --verbose -t cucumber -n $THREADS --group-by scenarios -o "--tags '$TAGS' -p parallel -p allure --retry 2 -p default"
where $THREAD=8, $TAGS=@regression and not @cert_only
It was converted to 8 commands, this is command that contains skipped test cases:
bundle exec cucumber --tags '@regression and not @cert_only' -p parallel -p allure --retry 2 -p default features/feature_files/oom_admin/account/admin_profile.feature:11:123 features/feature_files/oom_admin/account/billing.feature:81 features/feature_files/oom_admin/account/locations.feature:277 features/feature_files/oom_admin/account/porting.feature:220:50 features/feature_files/oom_admin/account/schedules.feature:143:27 features/feature_files/oom_admin/account_summary.feature:7 features/feature_files/oom_admin/header_footer.feature:5 features/feature_files/oom_admin/settings/device/base_station.feature:105 features/feature_files/oom_admin/settings/device/dp1_device.feature:95 features/feature_files/oom_admin/settings/device/ip_phones.feature:1075:1212:142:150:270:533:760 features/feature_files/oom_admin/settings/extensions/conference_server.feature:253:9 features/feature_files/oom_admin/settings/extensions/paging_groups.feature:48 features/feature_files/oom_admin/settings/extensions/ring_groups.feature:236:77 features/feature_files/oom_admin/settings/extensions/users.feature:139:302:475:622:800 features/feature_files/oom_admin/settings/extensions/virtual_fax.feature:147 features/feature_files/oom_admin/settings/extensions/virtual_receptionist.feature:166:392:619 features/feature_files/oom_admin/settings/managed_wifi.feature:87 features/feature_files/oom_admin/settings/phone_numbers/phone_numbers.feature:281:93 features/feature_files/oom_admin/settings/system/call_blocking.feature:105:194:234 features/feature_files/oom_admin/settings/system/general.feature:29 features/feature_files/oom_admin/settings/system/messaging.feature:12 features/feature_files/oom_admin/settings/system/music.feature:49 features/feature_files/oom_admin/settings/system/shared_speed_dial.feature:81 features/feature_files/oom_admin/store/accessories.feature:26 features/feature_files/oom_admin/store/office_pro.feature:232:362:49 features/feature_files/oom_admin/store/overview_page.feature:5 features/feature_files/oom_admin/store/phones.feature:36 features/feature_files/oom_admin/store/store.feature:110:146:265:298:306:337:73 features/feature_files/oom_admin/store/store_assign_and_pair_device.feature:131:41 features/feature_files/oom_csr/sales/sales.feature:238:5 features/feature_files/oom_end_user/account/user_profile.feature:40 features/feature_files/oom_end_user/dashboard/user_fax.feature:59 features/feature_files/oom_end_user/settings/user_call_handling.feature:66 features/feature_files/oom_end_user/settings/user_caller_id_preferences.feature:11 features/feature_files/oom_end_user/settings/user_voicemail_preferences.feature:103 features/feature_files/signupv3/signupv3_basic.feature:101:170:286:31:397:474:562:570:578:599:607:617:627:635:73 features/feature_files/signupv3/signupv3_nuarx.feature:75 features/feature_files/signupv3/signupv3_ooma.feature:216:57 features/feature_files/signupv3/signupv3_retailer.feature:103:125:19:191:268:27:296:405:50 features/feature_files/signupv3/signupv3_sfdc.feature:130:238:45 features/feature_files/signupv3/signupv3_wework_mobile.feature:50
cucumber.yml:
allure: --format AllureCucumber::CucumberFormatter --out=allure/results
parallel: --format message --out=reports/cucumber-messages<%=ENV['TEST_ENV_NUMBER']%>.ndjson
messages: --format message --out=reports/cucumber-messages.ndjson
html_report: -r features -b --format pretty --format html --out=reports/cucumber.html
json_report: --format json --out=reports/cucumber.json

I do not know how to reproduce this issue. It appears with random test cases in 1 thread (out of 8) only.
Is it possible to add some additional log info that may help to find a reason? Any other suggestions?

Did you see that we had an open issue that seems to be similar to yours?
Could you check your features to see if the specified line numbers match the "Scenario:" line or not?

Yes, I saw it. I checked all line numbers, they are correct and point to the Scenario or Scenario Outline.

If you execute yourself and several times the long command generated by parallel_cucumber, does it always fails the same or not?

When you say "skipped" @VladimirGumenny can you show us the output you see from Cucumber? Does it ignore the scenario completely, as though it had not been requested for execution / does not exist? Or does it appear in the results with a skipped status?

If you execute yourself and several times the long command generated by parallel_cucumber, does it always fails the same or not?

Executed 3 times exact that command from above: got correct result all 3 times.

When you say "skipped" @VladimirGumenny can you show us the output you see from Cucumber? Does it ignore the scenario completely, as though it had not been requested for execution / does not exist? Or does it appear in the results with a skipped status?

@mattwynne Sorry for unclear info. I meant that Scenario was completely ignored.
Attached log. As example in line #5 was requested accessories.feature:26.
This is Scenario Outline:
@regression @store_accessories
Feature: Store Accessories

  Background:
    Given I go to OOM Login page
    And I login to OOM as "admin" with "US" account using Resource Manager
    When I click on "Store" on the top level navigation menu
    And I click on "Accessories" on the inner level navigation menu

  @store_accessories1
  Scenario Outline: Verify that Accessories are filtered based on search bar input
    When I enter "<search_string>" into search field in Store Page
    Then I verify that "<expected_result>" devices are displayed in Store Page
    When I clear the Search field in Store Page
    Then I verify that all "Accessories" are displayed in Store Page
    When I logout from OOM
    Examples:
      | search_string | expected_result                                                                 |
 #Search by full device name
      | Base Station  | Base Station                                                                    |
 #Partial search by name
      | Yea           | Yealink EXP20,Yealink W60B,Yealink YHS33 Headset,Yealink Wi-Fi Dongle           |
      | in            | Ooma Linx,Yealink EXP20,Yealink W60B,Yealink Wi-Fi Dongle,Yealink YHS33 Headset |
 # Search by description (case not sensitive)
      | Yealink       | Yealink EXP20,Yealink W60B,Yealink YHS33 Headset,Yealink Wi-Fi Dongle           |
      | Wi-Fi         | Yealink Wi-Fi Dongle                                                            |
      | connect       | Ooma Connect 460,Connect 100 ft IX Cable                                        |
      | switch        | Netgear 8-port Switch                                                           |

It's easy to see that all others Examples were executed, but :26 ( | Wi-Fi | Yealink Wi-Fi Dongle |) was ignored.
log_532.log

If you execute yourself and several times the long command generated by parallel_cucumber, does it always fails the same or not?

Executed 3 times exact that command from above: got correct result all 3 times.

Ok, so it looks like it is more related to your environment, your tests, or parallel_test, than to cucumber itself.
Do you share any kind of state between tests that may leak from one thread to another one while executing in parallel?
How are resources - CPU and RAM mainly - on the machine which executes the tests?

Hmmm... interesting idea...
No, i do not share state or any other data between threads.
Test cases execute on the server in the docker with Selenoid:
# free -m
              total        used        free      shared  buff/cache   available
Mem:          15886        2629        7726         445        5530       12346
Swap:          8063        2026        6037
# cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 42
model name	: Intel Xeon E312xx (Sandy Bridge)

(8 cores at all)
I realized that 3 times may be not enough, since we have only 1 buggy thread from 8, will execute more times after today's regression execution.

@VladimirGumenny
I would like to close that issue as this seems not to be related to cucumber.
You executed the single cucumber command successfully, so cucumber is working well.
Still, I would like to continue helping you with your issue.
Where would you like to continue? I could suggest slack, or the cucumber community on smartbear, as suggested here: https://cucumber.io/docs/community/get-in-touch/#slack
Or would you prefer somewhere else?

@mattwynne @aurelien-reeves Whilst I've only just come back I would posit this is related to the issues with the regression we had where line numbers need to be exact.
I can't guarantee that's the issue. but it would be a good place to start

@aurelien-reeves
I am able to use any tool (just joined to Slack Cucumber Community workspace).
Use what works better for you.

I would suggest to start a thread on slack, in the #help or #help-cucumber-ruby channel

ok, started thread


Clarify many-to-one relationship for belongs_to

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


Add Watchers

Tasks
Consortium owners can add "watchers", people who can see the status and results of a pipeline run in a consortium, but who don't actually participate in the pipeline. Watchers must be approved by all consortium participants. If added before the consortium is created, all participants must be informed about who is watching. If the consortium owner wants invite a new watcher, they must be approved by all participants.
Participant = someone who participates in a pipeline run by contributing data to a pipeline

Still a need, adding priority


Ruby: Array splitting removes some elements

[:a, :b, c: []]

# press `gS`

[
  :a,
  :b
]

# `c: []` gone missing!
# expected:

[
  :a,
  :b,
  c: []
]

That's a good catch :). I'll be honest, I hadn't realized this is valid ruby syntax!
I've pushed a commit that should fix this. It's tricky, because it'll now add and remove brackets depending on argument bracket settings, so I hope it doesn't cause new issues for some people, but it should be working for you now, either way. Could you check it out?

This example seems to work for me at this time, so I'll go ahead and close this issue.


10.12.10 Studio Pro release notes

This PR can be merged after the date is updated.

@Robinfr , added, thanks!


Upgrading for React 18 with TypeScript

fixing React type definitionss -> Removal of implicit children
You can run:
npx types-react-codemod preset-18 ./src

thank you @Almusweb


Fix Concurrent Task Insertion in pendingCompletionTaskGroups

Fix Concurrent Task Insertion in pendingCompletionTaskGroups

Fixes #16727

Description
Fixed thread synchronisation issue in addDiscoveredTaskToPendingCompletionTaskGroups so the pendingCompletionTaskGroup is properly locked while initialising.

Fixed the bug ...
#16727
addDiscoveredTaskToPendingCompletionTaskGroups is not properly Thread Synchronized and updates to it are made on the basis of a stale copy of reads. When we submit supervisor config, there are cases  where instead of adding all tasks in same TaskGroup, it can create Multiple copies of TaskGroups. For ex, if A1,A2 are consuming from same partition and are in same group, then
ideal_behavior: pendingCompletionTaskGroup[P] = { TaskGroup{A1,A2}  }
behavior_seen: pendingCompletionTaskGroup[P] = { TaskGroup{A1}, TaskGroup{A2} }

This is because, while initialising a new TaskGroup, the threads rely on a stale copy of read and multiple threads executing simultaneously, adding tasks to pendingCompletionTaskGroup can create new task groups instead of being added to existing ones. This behaviour defeats the purpose of Task replication as these single task taskgroup if gets failed for some reason, than Overlord sees it as entire task group is failed, and kill actively reading tasks too, to resume ingestion from last published segment.
Renamed the class ...
Added a forbidden-apis entry ...

Release note

Key changed/added classes in this PR

MyFoo
OurBar
TheirBaz

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[x] added integration tests.
[x] been tested in a test Druid cluster.

I think the logic may be incorrect.
We should expect the following test (that I have written) to pass with the current logic and it does.
However, the changes in this patch cause a failure.

  @Test
  public void testAddDiscoveredTaskToPendingCompletionTaskGroupsSync()
  {
    EasyMock.expect(spec.isSuspended()).andReturn(false).anyTimes();
    EasyMock.expect(recordSupplier.getPartitionIds(STREAM)).andReturn(ImmutableSet.of(SHARD_ID)).anyTimes();
    EasyMock.expect(taskStorage.getActiveTasksByDatasource(DATASOURCE)).andReturn(ImmutableList.of()).anyTimes();
    EasyMock.expect(taskQueue.add(EasyMock.anyObject())).andReturn(true).anyTimes();

    replayAll();

    SeekableStreamSupervisor supervisor = new TestSeekableStreamSupervisor();
    Map<String, String> startingPartiions = new HashMap<>();
    startingPartiions.put("partition", "offset");

    Map<String, String> startingPartiions1 = new HashMap<>();
    startingPartiions.put("partition", "offset1");

    supervisor.addDiscoveredTaskToPendingCompletionTaskGroups(0, "task_1", startingPartiions);
    supervisor.addDiscoveredTaskToPendingCompletionTaskGroups(0, "task_2", startingPartiions);
    supervisor.addDiscoveredTaskToPendingCompletionTaskGroups(0, "task_3", startingPartiions);

    supervisor.addDiscoveredTaskToPendingCompletionTaskGroups(0, "task_7", startingPartiions1);
    supervisor.addDiscoveredTaskToPendingCompletionTaskGroups(0, "task_8", startingPartiions1);
    supervisor.addDiscoveredTaskToPendingCompletionTaskGroups(0, "task_9", startingPartiions1);

    CopyOnWriteArrayList<SeekableStreamSupervisor.TaskGroup> taskGroups = supervisor.getPendingCompletionTaskGroups(0);
    Assert.assertEquals(2, taskGroups.size());
    Assert.assertEquals(3, taskGroups.get(0).tasks.size());
    Assert.assertEquals(3, taskGroups.get(1).tasks.size());
  }

I think it is because you're handling the task group but not the start offsets as part of your logic.

It might be helpful if you can also add comments explaining what this method does and why concurrent insertion was previously failing and why changing the order of steps would help.

Hey @AmatyaAvadhanula , thanks for identifying this case which I missed.
I have improved the logic to handle this case.


Classes as well as Structs

Any chance this can work with classes as well as structs? If not, is it because the functionality isn't possible, or just needs a PR?

Unfortunately I haven't found a way to safely initialize classes. If someone has a solution I'd welcome a PR.

I was messing around with it, but it seemed every class needed to extend NSObject, with loads of @objc markers everywhere.
However, once you do that, you can reflect on everything using objective c methods, even method signatures, arguments, their types etc. Unfortunately, you're writing more objective-c than swift then ;)
Thought I'd share it anyway. Maybe in the future we'll get better reflection support in swift. Closing until that point, thanks!


Correct backtick escaping

Previously, the <code> block was being ended early by the backtick that should have been escaped. The proper way to escape backticks is to use more backticks: https://github.com/github/markup/issues/363

@david-mcgillicuddy-ovo : Thanks for your contribution! The author, @ash2017, has been notified to review your proposed change.

@david-mcgillicuddy-ovo - thanks for the catch... and the fix!


"Error: A retryable error occurred in the server."

following the guide, but the "hello" prompt returns:
"Error: A retryable error occurred in the server."
how this going?

I think the error might be coming from the Chrome AI model. Maybe try restarting Chrome Dev and see if that helps.


Lightning Model module , get_model_size method

🚀 Feature
A get_model_size method in model module which return model size in megabyte based on precision.
Motivation
Just thinking out loud..
Additional context
We can add this in mode summary too
# ------------
# model
# ------------
model = LitClassifier(args.hidden_dim, args.learning_rate)
>> print(model.size)
>> 104.14281 Mb with fp32.

That's a fun suggestion :)
I suppose a method is not suitable since this is just a information query and does not muatate the state of the model.

Property i mean :)


List of strings order must match AWS list of strings order (possibly alphabetical) when reconciling

What happened?
When trying to create an RDS instance in Crossplane, I noticed it was going through regular update cycles, meaning that the RDS instance was seldom in the available state. The reason for this ended up being that the list of strings in the enableCloudwatchLogsExports field were in a different order than what is reconciled against in the AWS list of strings.
How can we reproduce it?
I suspect this will occur for many resources where an argument takes a list of strings. However for this particular case, create an RDS instance with this field set to:
# this one caused RDS to go through regular update cycles
enableCloudwatchLogsExports:
              - upgrade
              - postgresql

You should notice that the RDS instance goes through regular update cycles.
Then set this field to:
# this one works as expected
enableCloudwatchLogsExports:
              - postgresql
              - upgrade

And note that the update cycles stop.
What environment did it happen in?
Crossplane version: 1.9.0
AWS Provider version: 0.29.0
Cloud provider or hardware configuration: AWS EKS
Kubernetes version (use kubectl version): v1.21.14-eks-18ef993
Kubernetes distribution (e.g. Tectonic, GKE, OpenShift): EKS

I should make a PR for this, https://github.com/sparebank1utvikling/provider-aws/commit/b2c3c7ccb46095e1bc2485fed681c3443082ab27
I wonder if we should remove CloudwatchLogsExportConfiguration at the same time


Moving the CSU, any impact on the Receipt No, Transaction No, Shift Id, etc needs to be highlighted

Moving the CSU between the regions will it impact the running numbers for the Receipt, Trans, Shift Id, etc. Is there a requirement to run the POS ReDeployment Checklist. Please advise else Customers might just move the CSU and expect the running numbers to continue as expected.
As it is a business risk, this should be highlighted to indicate it is automatically handled or this needs to be mitigated before by Partners/Customers.

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

ID: 083f5051-a328-f1e7-5d65-0f11fac5c304
Version Independent ID: 3d0ae350-6705-0009-fd1a-9fac44b4e83b
Content: Migrate channels to a different Commerce Scale Unit - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/deployment/Reassign-CSU.md
Service: dynamics-365-cross-app
Product: ****
Technology: ****
GitHub Login: @AamirAllaq
Microsoft Alias: aamiral

@AamirAllaq, please review. Thanks!


[15-wires] implement Maller's optimization

DO NOT MERGE: I only implemented this for 15-wires, not for 15-wires-plookup. To make tests work I deleted 15-wires-plookup. We are still figuring out how to deal with 15-wires-plookup.
In this PR I implement the Maller's optimization for 15-wires.
What is Maller's optimization? Or how does the protocol change? I documented it here: https://o1-labs.github.io/mina-book/crypto/plonk/maller_15.html
Some commits are also creating a o1-utils crate to deduplicate code and move extension to the arkwork types to their own crate (and avoid dependency issues).

rebased and addressed comments


Accessibility: expose element reference

Steps to reproduce
While using the puppeteer api page.accessibility.snapshot() the AXNode model leaves no trace of the DOM implementation. The underlying calls to CDP return nodeId (and backendDOMNodeId).
I suggest one or more of the following (will update if more ideas come in comments):

Give AXNode a new method 'asElement' which will create an ElementHandle from the stored nodeId or remoteObject reference.
Expose the nodeId or remoteObjectId on the AXNode (so it can be passed to other CDP calls).
Expose AXNode so CDP calls to Accessibility.getPartialAXTree can use this code to normalize the result the way snapshot() does.

Puppeteer version: 1.10+
Platform / OS version: any
URLs (if applicable):
Node.js version: latest

Please include code that reproduces the issue.
// ... open google.com
const tree = await this.page.accessibility.snapshot();
console.log(tree);

Yields:
{ role: 'WebArea',
  name: 'Google',
  children:
   [ { role: 'button', name: 'Dismiss' },
     { role: 'link', name: 'About' },
     { role: 'link', name: 'Store' },
     { role: 'link', name: 'Gmail' },
     { role: 'link', name: 'Images' },
     { role: 'button', name: 'Google apps' },
     { role: 'link', name: 'Sign in' },
     { role: 'combobox',
       name: 'Search',
       description: 'Search',
       focused: true,
       autocomplete: 'both' },
     { role: 'button', name: 'Search by voice' },
     { role: 'button',
       name: 'Google Search',
       description: 'Google Search' },
     { role: 'button',
       name: 'I\'m Feeling Lucky',
       description: 'I\'m Feeling Lucky' },
     { role: 'img', name: 'Google' },
     { role: 'link', name: 'Privacy' },
     { role: 'link', name: 'Terms' },
     { role: 'combobox', name: 'Settings', haspopup: 'menu' },
     { role: 'link', name: 'Advertising' },
     { role: 'link', name: 'Business' } ] }

But more useful would be:
{ role: 'WebArea',
  name: 'Google',
  nodeId: 1,
  children:
   [ { role: 'button', name: 'Dismiss', nodeId: 4 },
     { role: 'link', name: 'About', nodeId: 6 },
     { role: 'link', name: 'Store', nodeId: 7 },
     { role: 'link', name: 'Gmail', nodeId: 8 },
     { role: 'link', name: 'Images', nodeId: 11 },
     { role: 'button', name: 'Google apps', nodeId: 47 },
     { role: 'link', name: 'Sign in', nodeId: 48 },
 // ...
     { role: 'link', name: 'Business', nodeId: 129 } ] }

If approved, I feel I could make the needed changes to submit a PR.

I am also interested in this.

I suggest one or more of the following...

I think I can make this happen. Just need to understand the preference of the choices I outlined above (or have a better choice).

Both options 1 and 3 sound great to me

Sorry I should have been on top of this discussion sooner. Thanks for the interest everyone!
I definitely don't want to directly expose CDP's nodeIds. Instead the API should deal in ElementHandles.  And because of the way we make element handles, the api needs to expose a function that returns a promise to an ElementHandle. Otherwise we'd need to figure out how memory management would work, which would certainly be a breaking change.
Right now the AXNode is returned as a serilizable JSON object. This is done to make clear this this object is inert. It contains the state of the AXNode at the time of the snapshot. I feel a little bit weird adding a function to this object. But I don't see a better way.
What should that function be called? .node() is a bit strange, because the thing you are calling it on is also a "node". .DOMNode() is technically correct. .element() feels the most natural to me, and is consistent with ElementHandle in that we mislabel DOMNodes as elements 😄.
Not all Accessibility Nodes are directly associated with a DOM node, for example the popup menu of a <select> element. Should this return null, or the ElementHandle for its parent select? And sometimes AXNode's are associated with a DOMNode within the user agent shadow DOM. For example, the text inside a textarea in Chromium is implemented as a text node inside a div in the shadow dom of the textarea. Should these shadowy elements be exposed? Or null? Or their shadow host?

@JoelEinbinder Thanks for the good questions!
Trying to answer based on my own use case, I would love for AXNodes pointing to Shadow DOM subtrees to give me a reference to the element inside the subtree, even if it's a closed/native one. That would be my preference.
If that is too difficult to implement, and I would instead get a reference to the last author-inserted element, that would be okay by me in most cases though, and actually more convenient in a few. A couple of cases would be significantly more annoying, but I'm sure I could hardcode them, because there aren't many elements which are implemented with closed shadow trees in Blink as far as I know.
Regarding the name of the function, I'm not too concerned about this, and I think consistency with what you have today is a good way of narrowing this down, except if someone feels strongly about this.

asElement() was what I saw originally in other, similar areas of puppeteer but element() is fine. Personally, the native shadow implementation isn't helpful as I'm trying to map issues with accessibility back to their author implementation--WebComponents included (e.g., how another developer will see it in the devtools, not how the engine sees it). If that's something others want, please provide a second method for the "shadow host || element".
So, I'll make the same argument about the example of <select>: to a developer in devtools, the scrim of an opened <select> is abstracted away (and also invisible to the accessibility tab). That information is less helpful than the role and name exposed to AT.

asElement is actually our way to do casting. It does x instanceOf ElementHandle ? this : null.
@AutoSponge  I'm not sure what you mean about the scrim being hidden from the accessibility tab.

I'm talking about the MenuListPopup here, which doesn't correspond to any element in DOM, shadow or otherwise.
@FremyCompany The accessibility engine doesn't know the difference beteween user agent shadow nodes and just regular DOM nodes. So it would require more effort to filter them out. However I can't think of a case where they would be useful to web developers. Why would you want to see them?

Almost every DOM element has user agent shadow dom, besides really basic ones like div and span. It is just an implementation detail of Chromium though.

I feel a little bit weird adding a function to this object. But I don't see a better way.

@JoelEinbinder I prefer an option that injects an axNodeId to every AXNode and a separate method to resolve element handle from this ID:
const snapshot = await page.accessibility.snapshot({
  axNodeIds: true
});
const elementHandle = await page.accessibility.resolveElement(snapshot.axNodeId);

Alternatively, we can invest some effort and teach ElementHandle to work with backendNodeId internally instead of a remote object. This way the following will work without any memory concerns:
const snapshot = await page.accessibility.snapshot({
  elementHandles: true
});
const elementHandle = snapshot.elementHandle;

@JoelEinbinder Well, in my case I am trying to emulate a screenreader experience of some arbitrary web content, so being able to see internal controls of, say, a <video controls> element is rather useful. If you are not interested in those elements, it's not very difficult to walk up the tree until you find something in the light tree again, so I wouldn't worry about filtering them out.

@FremyCompany If you are trying to emulate a screen reader experience, why do you need the HTML element at all? Everything should be contained within the accessibility tree.

@JoelEinbinder Things are more complex than that :) For instance on Windows, there are APIs like UIA TextPattern which provides line-by-line text navigation and allows you to find out about the precise location of the screens of words (more generally any text range) which you cannot get from the accessibility tree but can get with things like getBoundingClientRect on Range etc... Also, many controls need to be interacted with, which means that you need to be able to ".click()" them etc which you cannot do from the AXNodes as far as I know.

All of those things are exposed through the real ax tree from chrome. It’s not exposed in puppeteer just because it takes some effort and I didn’t get around to it. I can probably add them if you have use for them. I definitely want to add clicking.
However if you are building a screen reader on top of puppeteer, why not instead use the platform accessibility apis?

@JoelEinbinder Long story, but having access to the full platform enables quickly experimenting and testing new things which would require extra-long coordination efforts across organizations otherwise, and either prove their value or iterate on them until a more concrete proposal can be made and analyzed regarding its cost/benefit; plus it is cross-platform which is great for sharing experimental results to people regardless of their platform.
Currently I have put that specific project on hold, because I am focusing on more fundamental research topics but the proof of concept I have built on top of puppeteer is very solid and I mid-term I intend to work on this again. I will say I was super impressed with the puppeteer project and API, and I say that having worked on browsers in the past, and having used all kinds of Selenium and Web Driver things including some internal-only ones at Microsoft :)

@JoelEinbinder Maybe I misspoke. An object like MenuListPopup is not targetable by a developer using devtools. Therefore, it's not an object I'd be interested in for my purposes. As @FremyCompany said, it may have importance for other applications. Maybe I can suggest a { pierce: true } option for this future method?

@FremyCompany It sounds like you are doing some experimental/prototype stuff. I'd recommend copying Accessibility.js into your project and modifying it yourself.
@AutoSponge can you give a bit more context about your use case? Would having elementHandle.accessibilitySnapshot be sufficient?

@JoelEinbinder I would consider doing that if that was required. Fwiw, your proposed elementHandle.accessibilitySnapshot would work really well for me (I would then navigate the dom as primary, then get the accessibility info on end nodes like input/video where the dom tree isn't providing the relevant info). If you do that,  elementHandle.accessiblitySnapshot should maybe have an optional parameter specifying not to return children nodes as an optimization, just the AXNode associated to the element.

@JoelEinbinder My case: I want to find (usually interactive) DOM nodes by accessible name for testing purposes. This simultaneously tests functionality and accessibility in a black box style. Short of a new method, queryByAXName, I need a way to correlate the AXTree and the DOM. this.nodeId = this._payload.nodeId is how I'm doing it using the CDP (in the AXNode constructor). But if a better, documented approach were available, I'd scrap my hack.

elementHandle.accessibilitySnapshot would be great for me too as I need an easy way to test that a certain element has focus.

@JoelEinbinder After seeing the new switch for "user agent shadow" in chrome devtools, it made me wonder if we can just use that as the flag for whether a node reference will be returned or not. Personally, I wouldn't need the user agent shadow nodes. Does that help work around some of the problems you mentioned before?

I need to interact (click, type, etc.) via the accessibility tree, so I need some kind of workaround… Sharing it here:
Workaround as of Puppeteer v5.0.0
Getting a raw accessibility tree from a Puppeteer page
const client = getClient(page)
const tree = await getAccessibilityTree(client)

/**
 * @param {import("puppeteer").Page} page
 */
function getClient(page) {
  return /** @type {import('puppeteer').CDPSession} */ (
    /** @type {any} */ (page)._client
  )
}

/**
 * @param {import("puppeteer").CDPSession} client
 */
async function getAccessibilityTree(client) {
  return /** @type {import("puppeteer/lib/esm/protocol").default.Accessibility.getFullAXTreeReturnValue} */ (await client.send(
    'Accessibility.getFullAXTree',
  ))
}

The result will contain nodes[*].backendDOMNodeId which allows resolving back to a DOM node.
Getting a DOM node given a backendDOMNodeId
const node = await resolveNodeFromBackendNodeId(page.mainFrame(), backendDOMNodeId)

/**
 * @param {import("puppeteer").Frame} frame
 * @param {number} backendNodeId
 */
async function resolveNodeFromBackendNodeId(frame, backendNodeId) {
  const ctx = await Promise.resolve(frame.executionContext())
  return /** @type {import('puppeteer').ElementHandle} */ (
    /** @type {any} */ (ctx)._adoptBackendNodeId(backendNodeId)
  )
}

The result will be an element handle that we can interact with.

What's the state of this issue? I'm looking for the same feature and can't really think of any better alternatives other than accessing the private APIs for now.
My use case is to query elements based on their accessibility properties. While aria query could do some of the jobs, but not all of them (currently aria query only support querying by name and role).
If it's up to me then I would probably try to keep it simple and just return null for those that are not associated with a DOM element, and just let the developers to handle the rest.

What's the state of this issue? I'm looking for the same feature and can't really think of any better alternatives other than accessing the private APIs for now.
My use case is to query elements based on their accessibility properties. While aria query could do some of the jobs, but not all of them (currently aria query only support querying by name and role).
If it's up to me then I would probably try to keep it simple and just return null for those that are not associated with a DOM element, and just let the developers to handle the rest.

I'd like to know where we are with this too. I would very much like the suggested elementHandle.accessibilitySnapshot. The documentation claims that page.accessibility.snapshot({ root: elementHandle }) should work, but as far as I can tell it simply doesn't, it just always returns null.


Update QUnit to the latest version

Recently, I've focused on a subject of Unit Tests and paid attention that UI5 uses very outdated version of QUnit: 2.3.2 from April 2017, while the latest version is 2.19.4 from January 2023, which is 6 years old version!
Even in a in brand new Learn to use TypeScript with UI5 [Tutorial] from UI5con 2023 we may observe version 2.3.2.
Is there is any reason why does UI5 stick with QUnit 2.3.2?
Are there any plans to upgrade QUnit to the latest version?

Is there is any reason why does UI5 stick with QUnit 2.3.2?

You know UI5 long enough to know the reason: compatibility: Unfortunately, the huge UI5 codebase inside SAP references the QUnit module from our sap/ui/thirdparty package. Upgrading one of the two modules inplace would cause regressions (e.g.. because newer versions also fail on uncaught promise rejections). As we have no process in place that triggers our internal consumers to handle these  issues, the existing modules are stuck at their current versions.
What we could do, but already decided against, is introducing additional qunit versions as new modules.
Instead, our strategy is to generally discourage consumers from using one of our QUnit versions. Consumers should rather pick their own version. This is for sure less convenient than reusing a version that UI5 already packages. But we see currently no better way to avoid the compatibility restrictions that come with our delivery.
It's unfortunate that the TypeScript tutorial and others don't reflect this yet, but I hope that one of the next updates will do so.

Is there is any reason why does UI5 stick with QUnit 2.3.2?

You know UI5 long enough to know the reason: compatibility […]. Upgrading one of the two modules inplace would cause regressions (e.g.. because newer versions also fail on uncaught promise rejections). As we have no process in place that triggers our internal consumers to handle these issues, the existing modules are stuck at their current versions.

Hi @codeworrior, maintainer of QUnit here.
If we implemented something in QUnit 2.x, like QUnit.config.ignoreUncaughtRejections that you can set to false in your test runner, would that unblock UI5 from upgrading?
I'm interested in exploring this and other needs so as to help you along. In particular, so that you have access to the TAP reporter (new in QUnit 2.16.0) that would potentially give you access to a wider range of Karma alternatives in the future. Including QTap, which is currently in development.
Feel free to reply below, or reach out at https://github.com/qunitjs/qunit/issues, or in our Matrix chat channel.


Version 1.1.0 Release Checklist

[ ] Test on Windows:

[ ] Ableton
[ ] FL Studio
[ ] Reaper
[ ] Studio One

[ ] Test on Mac:

[ ] Ableton
[ ] GarageBand
[ ] Logic (M1)
[ ]  FL Studio

[ ] Test on Linux:

[ ] Carla
[ ] Ardour

[ ] Test on iOS:

[x] AUM
[ ] GarageBand
[x] Standalone

[ ] Update CHANGELOG
[ ] Bump version number
[ ] Submit iOS build for review
[ ] Generate release builds/installers
[ ] Release iOS version
[ ] Tag GitHub Release
[ ] Update website
[ ] Postings:

[ ] KVR
[ ] AudioBus
[ ] Webpage (news)
[ ] Patreon

Hi, I'm playing with ChowKick.lv2 on Arch Linux with Reaper so I can test night builds, for now - ChowKick-Linux-x64-1.0.2.deb works fine in Arch

Awesome, thanks for helping with testing!


Neovim built-in statusline is shown when I change the window

The galaxyline is shown correctly when I open neovim for the first time:

But when I change to another window and come back to neovim, the built-in statusline is shown:

How can I fix it?
ENV:
Terminal: kitty
galaxyline: latest
nvim --version:
NVIM v0.5.0
Build type: Release
LuaJIT 2.0.5

I had airline installed on my previous setup and somehow it was still active. It was installed as a plugin for vim (/usr/share/vim/vimfiles/plugin) and after removing it manually, the issue does not occur anymore.


Revert "RocksDB: change compaction-guard-min-output-file-size to 1MB …

…(#14889) (#14908)"
This reverts commit 5fb42ddcbdea8b5e0c9041595a4238765354d826.

What is changed and how it works?

Issue Number: Close #15177
What's Changed:

updates the compaction-guard-min-output-file-size's default value from 1MB to 8MB.

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test

Side effects
Release note
Default value of compaction-guard-min-output-file-size is changed to 8MB

/merge