"Back-off restarting failed container"

A slightly different from #690.
Step to reproduce:

Setup dev-box, and prepare config, bootup k8s cluster.
Install PAI and start PAI services. Now everything is fine.
Stop PAI services and remove k8s cluster.
Change the bootup config(for example, change the master node of PAI), and install PAI.
Failed to start PAI services.

Kubectl logs:
root@k8s-eastus-head:/# kubectl logs -f  hadoop-data-node-ds Error from server (NotFound): pods "hadoop-data-node-ds" not found root@k8s-eastus-head:/# kubectl logs -f hadoop-data-node-ds-8cqgg 18/06/11 02:51:38 INFO datanode.DataNode: STARTUP_MSG: /************************************************************ STARTUP_MSG: Starting DataNode STARTUP_MSG:   host = localhost/<IP_ADDRESS> STARTUP_MSG:   args = [] STARTUP_MSG:   version = 2.7.2 STARTUP_MSG:   classpath = /usr/local/hadoop/etc/hadoop/:/usr/local/hadoop/share/hadoop/common/lib/jackson-xc-1.9.13.jar:/usr/local/hadoop/share/hadoop/common/lib/asm-3.2.jar:/usr/local/hadoop/share/hadoop/common/lib/hamcrest-core-1.3.jar:/usr/local/hadoop/share/hadoop/common/lib/api-asn1-api-1.0.0-M20.jar:/usr/local/hadoop/share/hadoop/common/lib/slf4j-api-1.7.10.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-configuration-1.6.jar:/usr/local/hadoop/share/hadoop/common/lib/guava-11.0.2.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-collections-3.2.2.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-httpclient-3.1.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-beanutils-1.7.0.jar:/usr/local/hadoop/share/hadoop/common/lib/snappy-java-<IP_ADDRESS>.jar:/usr/local/hadoop/share/hadoop/common/lib/jersey-server-1.9.jar:/usr/local/hadoop/share/hadoop/common/lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/common/lib/gson-2.2.4.jar:/usr/local/hadoop/share/hadoop/common/lib/servlet-api-2.5.jar:/usr/local/hadoop/share/hadoop/common/lib/jaxb-impl-2.2.3-1.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-beanutils-core-1.8.0.jar:/usr/local/hadoop/share/hadoop/common/lib/apacheds-kerberos-codec-2.0.0-M15.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-codec-1.4.jar:/usr/local/hadoop/share/hadoop/common/lib/jetty-6.1.26.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-io-2.4.jar:/usr/local/hadoop/share/hadoop/common/lib/stax-api-1.0-2.jar:/usr/local/hadoop/share/hadoop/common/lib/paranamer-2.3.jar:/usr/local/hadoop/share/hadoop/common/lib/jackson-jaxrs-1.9.13.jar:/usr/local/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar:/usr/local/hadoop/share/hadoop/common/lib/java-xmlbuilder-0.4.jar:/usr/local/hadoop/share/hadoop/common/lib/jaxb-api-2.2.2.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-logging-1.1.3.jar:/usr/local/hadoop/share/hadoop/common/lib/curator-client-2.7.1.jar:/usr/local/hadoop/share/hadoop/common/lib/apacheds-i18n-2.0.0-M15.jar:/usr/local/hadoop/share/hadoop/common/lib/mockito-all-1.8.5.jar:/usr/local/hadoop/share/hadoop/common/lib/jackson-core-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/common/lib/jersey-json-1.9.jar:/usr/local/hadoop/share/hadoop/common/lib/httpcore-4.2.5.jar:/usr/local/hadoop/share/hadoop/common/lib/jettison-1.1.jar:/usr/local/hadoop/share/hadoop/common/lib/jets3t-0.9.0.jar:/usr/local/hadoop/share/hadoop/common/lib/avro-1.7.4.jar:/usr/local/hadoop/share/hadoop/common/lib/jsr305-3.0.0.jar:/usr/local/hadoop/share/hadoop/common/lib/api-util-1.0.0-M20.jar:/usr/local/hadoop/share/hadoop/common/lib/httpclient-4.2.5.jar:/usr/local/hadoop/share/hadoop/common/lib/junit-4.11.jar:/usr/local/hadoop/share/hadoop/common/lib/htrace-core-3.1.0-incubating.jar:/usr/local/hadoop/share/hadoop/common/lib/jsp-api-2.1.jar:/usr/local/hadoop/share/hadoop/common/lib/jetty-util-6.1.26.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-compress-1.4.1.jar:/usr/local/hadoop/share/hadoop/common/lib/jersey-core-1.9.jar:/usr/local/hadoop/share/hadoop/common/lib/curator-recipes-2.7.1.jar:/usr/local/hadoop/share/hadoop/common/lib/hadoop-annotations-2.7.2.jar:/usr/local/hadoop/share/hadoop/common/lib/jsch-0.1.42.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-lang-2.6.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-digester-1.8.jar:/usr/local/hadoop/share/hadoop/common/lib/activation-1.1.jar:/usr/local/hadoop/share/hadoop/common/lib/zookeeper-3.4.6.jar:/usr/local/hadoop/share/hadoop/common/lib/protobuf-java-2.5.0.jar:/usr/local/hadoop/share/hadoop/common/lib/log4j-1.2.17.jar:/usr/local/hadoop/share/hadoop/common/lib/curator-framework-2.7.1.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-math3-3.1.1.jar:/usr/local/hadoop/share/hadoop/common/lib/netty-3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-net-3.1.jar:/usr/local/hadoop/share/hadoop/common/lib/hadoop-auth-2.7.2.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-cli-1.2.jar:/usr/local/hadoop/share/hadoop/common/lib/xz-1.0.jar:/usr/local/hadoop/share/hadoop/common/lib/xmlenc-0.52.jar:/usr/local/hadoop/share/hadoop/common/hadoop-common-2.7.2-tests.jar:/usr/local/hadoop/share/hadoop/common/hadoop-nfs-2.7.2.jar:/usr/local/hadoop/share/hadoop/common/hadoop-common-2.7.2.jar:/usr/local/hadoop/share/hadoop/hdfs:/usr/local/hadoop/share/hadoop/hdfs/lib/xml-apis-1.3.04.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/asm-3.2.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/guava-11.0.2.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jersey-server-1.9.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-daemon-1.0.13.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/servlet-api-2.5.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-codec-1.4.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/xercesImpl-2.9.1.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jetty-6.1.26.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-io-2.4.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-logging-1.1.3.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jackson-core-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jsr305-3.0.0.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/leveldbjni-all-1.8.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/htrace-core-3.1.0-incubating.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jetty-util-6.1.26.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jersey-core-1.9.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-lang-2.6.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/protobuf-java-2.5.0.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/log4j-1.2.17.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/netty-3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-cli-1.2.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/netty-all-4.0.23.Final.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/xmlenc-0.52.jar:/usr/local/hadoop/share/hadoop/hdfs/hadoop-hdfs-2.7.2-tests.jar:/usr/local/hadoop/share/hadoop/hdfs/hadoop-hdfs-2.7.2.jar:/usr/local/hadoop/share/hadoop/hdfs/hadoop-hdfs-nfs-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-guice-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jackson-xc-1.9.13.jar:/usr/local/hadoop/share/hadoop/yarn/lib/asm-3.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/guava-11.0.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-collections-3.2.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-server-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/yarn/lib/servlet-api-2.5.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jaxb-impl-2.2.3-1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-codec-1.4.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jetty-6.1.26.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-io-2.4.jar:/usr/local/hadoop/share/hadoop/yarn/lib/stax-api-1.0-2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jackson-jaxrs-1.9.13.jar:/usr/local/hadoop/share/hadoop/yarn/lib/javax.inject-1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/guice-3.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jaxb-api-2.2.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-client-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-logging-1.1.3.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jackson-core-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-json-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/aopalliance-1.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jettison-1.1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jsr305-3.0.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/leveldbjni-all-1.8.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jetty-util-6.1.26.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-compress-1.4.1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-core-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-lang-2.6.jar:/usr/local/hadoop/share/hadoop/yarn/lib/activation-1.1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/zookeeper-3.4.6.jar:/usr/local/hadoop/share/hadoop/yarn/lib/protobuf-java-2.5.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/log4j-1.2.17.jar:/usr/local/hadoop/share/hadoop/yarn/lib/netty-3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/yarn/lib/zookeeper-3.4.6-tests.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-cli-1.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/xz-1.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/guice-servlet-3.0.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-api-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-resourcemanager-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-applications-distributedshell-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-applicationhistoryservice-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-common-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-registry-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-web-proxy-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-sharedcachemanager-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-common-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-tests-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-applications-unmanaged-am-launcher-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-client-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jersey-guice-1.9.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/asm-3.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/hamcrest-core-1.3.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/snappy-java-<IP_ADDRESS>.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jersey-server-1.9.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/commons-io-2.4.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/paranamer-2.3.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/javax.inject-1.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/guice-3.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jackson-core-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/aopalliance-1.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/avro-1.7.4.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/leveldbjni-all-1.8.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/junit-4.11.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/commons-compress-1.4.1.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jersey-core-1.9.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/hadoop-annotations-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/protobuf-java-2.5.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/log4j-1.2.17.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/netty-3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/xz-1.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/guice-servlet-3.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-app-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-common-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-hs-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-hs-plugins-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.2-tests.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-shuffle-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-core-2.7.2.jar:/usr/local/hadoop/contrib/capacity-scheduler/*.jar STARTUP_MSG:   build = https://git-wip-us.apache.org/repos/asf/hadoop.git -r b165c4fe8a74265c792ce23f546c64604acf0e41; compiled by 'jenkins' on 2016-01-26T00:08Z STARTUP_MSG:   java = 1.8.0_162 ************************************************************/ 18/06/11 02:51:38 INFO datanode.DataNode: registered UNIX signal handlers for [TERM, HUP, INT] 18/06/11 02:51:38 INFO impl.MetricsConfig: loaded properties from hadoop-metrics2.properties 18/06/11 02:51:38 INFO impl.MetricsSystemImpl: Scheduled snapshot period at 10 second(s). 18/06/11 02:51:38 INFO impl.MetricsSystemImpl: DataNode metrics system started 18/06/11 02:51:38 INFO datanode.BlockScanner: Initialized block scanner with targetBytesPerSec 1048576 18/06/11 02:51:38 INFO datanode.DataNode: File descriptor passing is enabled. 18/06/11 02:51:38 INFO datanode.DataNode: Configured hostname is <IP_ADDRESS> 18/06/11 02:51:38 INFO datanode.DataNode: Starting DataNode with maxLockedMemory = 0 18/06/11 02:51:38 INFO datanode.DataNode: Opened streaming server at /<IP_ADDRESS>:50010 18/06/11 02:51:38 INFO datanode.DataNode: Balancing bandwith is 536870912 bytes/s 18/06/11 02:51:38 INFO datanode.DataNode: Number threads for balancing is 100 18/06/11 02:51:38 INFO datanode.DataNode: Balancing bandwith is 536870912 bytes/s 18/06/11 02:51:38 INFO datanode.DataNode: Number threads for balancing is 100 18/06/11 02:51:38 INFO datanode.DataNode: Listening on UNIX domain socket: /var/lib/hdfs/datanode_socket 18/06/11 02:51:39 INFO mortbay.log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog 18/06/11 02:51:39 INFO server.AuthenticationFilter: Unable to initialize FileSignerSecretProvider, falling back to use random secrets. 18/06/11 02:51:39 INFO http.HttpRequestLog: Http request log for http.requests.datanode is not defined 18/06/11 02:51:39 INFO http.HttpServer2: Added global filter 'safety' (class=org.apache.hadoop.http.HttpServer2$QuotingInputFilter) 18/06/11 02:51:39 INFO http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context datanode 18/06/11 02:51:39 INFO http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context static 18/06/11 02:51:39 INFO http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context logs 18/06/11 02:51:39 INFO http.HttpServer2: Jetty bound to port 45824 18/06/11 02:51:39 INFO mortbay.log: jetty-6.1.26 18/06/11 02:51:39 INFO mortbay.log: Started HttpServer2$SelectChannelConnectorWithSafeStartup@localhost:45824 18/06/11 02:51:39 INFO web.DatanodeHttpServer: Listening HTTP traffic on /<IP_ADDRESS>:50075 18/06/11 02:51:39 INFO datanode.DataNode: dnUserName = root 18/06/11 02:51:39 INFO datanode.DataNode: supergroup = supergroup 18/06/11 02:51:39 INFO ipc.CallQueueManager: Using callQueue class java.util.concurrent.LinkedBlockingQueue 18/06/11 02:51:39 INFO ipc.Server: Starting Socket Reader #1 for port 50020 18/06/11 02:51:39 INFO datanode.DataNode: Opened IPC server at /<IP_ADDRESS>:50020 18/06/11 02:51:39 INFO datanode.DataNode: Refresh request received for nameservices: null 18/06/11 02:51:39 INFO datanode.DataNode: Starting BPOfferServices for nameservices: <default> 18/06/11 02:51:39 INFO datanode.DataNode: Block pool <registering> (Datanode Uuid unassigned) service to /<IP_ADDRESS>:9000 starting to offer service 18/06/11 02:51:39 INFO ipc.Server: IPC Server Responder: starting 18/06/11 02:51:39 INFO ipc.Server: IPC Server listener on 50020: starting 18/06/11 02:51:39 INFO common.Storage: Lock on /var/lib/hdfs/data/in_use.lock acquired by nodename 10249@localhost 18/06/11 02:51:39 WARN common.Storage: java.io.IOException: Incompatible clusterIDs in /var/lib/hdfs/data: namenode clusterID = CID-ac91d691-a1c4-417e-a7de-5082f9b2f5aa; datanode clusterID = CID-57ca2ee4-d125-4166-b0c6-67e230ee53fb 18/06/11 02:51:39 FATAL datanode.DataNode: Initialization failed for Block pool <registering> (Datanode Uuid unassigned) service to /<IP_ADDRESS>:9000. Exiting. java.io.IOException: All specified directories are failed to load.         at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead(DataStorage.java:478)         at org.apache.hadoop.hdfs.server.datanode.DataNode.initStorage(DataNode.java:1358)         at org.apache.hadoop.hdfs.server.datanode.DataNode.initBlockPool(DataNode.java:1323)         at org.apache.hadoop.hdfs.server.datanode.BPOfferService.verifyAndSetNamespaceInfo(BPOfferService.java:317)         at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.connectToNNAndHandshake(BPServiceActor.java:223)         at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run(BPServiceActor.java:802)         at java.lang.Thread.run(Thread.java:748) 18/06/11 02:51:39 WARN datanode.DataNode: Ending block pool service for: Block pool <registering> (Datanode Uuid unassigned) service to /<IP_ADDRESS>:9000 18/06/11 02:51:39 INFO datanode.DataNode: Removed Block pool <registering> (Datanode Uuid unassigned) 18/06/11 02:51:41 WARN datanode.DataNode: Exiting Datanode 18/06/11 02:51:41 INFO util.ExitUtil: Exiting with status 0 18/06/11 02:51:41 INFO datanode.DataNode: SHUTDOWN_MSG: /************************************************************ SHUTDOWN_MSG: Shutting down DataNode at localhost/<IP_ADDRESS> ************************************************************/

Sometime encountered an other error:
"Readiness probe errored: rpc error: code = Unknown desc = container not running (93743f5c98733c4179c1c192a1a7ca4f8c976a8c41e81f34da2e6c3cdae2ce02)
Back-off restarting failed container"

Kubectl logs:
root@k8s-eastus-head:/# kubectl logs -f hadoop-data-node-ds-nfrg7
18/06/11 03:50:29 INFO datanode.DataNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting DataNode
STARTUP_MSG:   host = localhost/<IP_ADDRESS>
STARTUP_MSG:   args = []
STARTUP_MSG:   version = 2.7.2
STARTUP_MSG:   classpath = /usr/local/hadoop/etc/hadoop/:/usr/local/hadoop/share/hadoop/common/lib/jackson-xc-1.9.13.jar:/usr/local/hadoop/share/hadoop/common/lib/asm-3.2.jar:/usr/local/hadoop/share/hadoop/common/lib/hamcrest-core-1.3.jar:/usr/local/hadoop/share/hadoop/common/lib/api-asn1-api-1.0.0-M20.jar:/usr/local/hadoop/share/hadoop/common/lib/slf4j-api-1.7.10.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-configuration-1.6.jar:/usr/local/hadoop/share/hadoop/common/lib/guava-11.0.2.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-collections-3.2.2.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-httpclient-3.1.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-beanutils-1.7.0.jar:/usr/local/hadoop/share/hadoop/common/lib/snappy-java-<IP_ADDRESS>.jar:/usr/local/hadoop/share/hadoop/common/lib/jersey-server-1.9.jar:/usr/local/hadoop/share/hadoop/common/lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/common/lib/gson-2.2.4.jar:/usr/local/hadoop/share/hadoop/common/lib/servlet-api-2.5.jar:/usr/local/hadoop/share/hadoop/common/lib/jaxb-impl-2.2.3-1.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-beanutils-core-1.8.0.jar:/usr/local/hadoop/share/hadoop/common/lib/apacheds-kerberos-codec-2.0.0-M15.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-codec-1.4.jar:/usr/local/hadoop/share/hadoop/common/lib/jetty-6.1.26.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-io-2.4.jar:/usr/local/hadoop/share/hadoop/common/lib/stax-api-1.0-2.jar:/usr/local/hadoop/share/hadoop/common/lib/paranamer-2.3.jar:/usr/local/hadoop/share/hadoop/common/lib/jackson-jaxrs-1.9.13.jar:/usr/local/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar:/usr/local/hadoop/share/hadoop/common/lib/java-xmlbuilder-0.4.jar:/usr/local/hadoop/share/hadoop/common/lib/jaxb-api-2.2.2.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-logging-1.1.3.jar:/usr/local/hadoop/share/hadoop/common/lib/curator-client-2.7.1.jar:/usr/local/hadoop/share/hadoop/common/lib/apacheds-i18n-2.0.0-M15.jar:/usr/local/hadoop/share/hadoop/common/lib/mockito-all-1.8.5.jar:/usr/local/hadoop/share/hadoop/common/lib/jackson-core-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/common/lib/jersey-json-1.9.jar:/usr/local/hadoop/share/hadoop/common/lib/httpcore-4.2.5.jar:/usr/local/hadoop/share/hadoop/common/lib/jettison-1.1.jar:/usr/local/hadoop/share/hadoop/common/lib/jets3t-0.9.0.jar:/usr/local/hadoop/share/hadoop/common/lib/avro-1.7.4.jar:/usr/local/hadoop/share/hadoop/common/lib/jsr305-3.0.0.jar:/usr/local/hadoop/share/hadoop/common/lib/api-util-1.0.0-M20.jar:/usr/local/hadoop/share/hadoop/common/lib/httpclient-4.2.5.jar:/usr/local/hadoop/share/hadoop/common/lib/junit-4.11.jar:/usr/local/hadoop/share/hadoop/common/lib/htrace-core-3.1.0-incubating.jar:/usr/local/hadoop/share/hadoop/common/lib/jsp-api-2.1.jar:/usr/local/hadoop/share/hadoop/common/lib/jetty-util-6.1.26.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-compress-1.4.1.jar:/usr/local/hadoop/share/hadoop/common/lib/jersey-core-1.9.jar:/usr/local/hadoop/share/hadoop/common/lib/curator-recipes-2.7.1.jar:/usr/local/hadoop/share/hadoop/common/lib/hadoop-annotations-2.7.2.jar:/usr/local/hadoop/share/hadoop/common/lib/jsch-0.1.42.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-lang-2.6.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-digester-1.8.jar:/usr/local/hadoop/share/hadoop/common/lib/activation-1.1.jar:/usr/local/hadoop/share/hadoop/common/lib/zookeeper-3.4.6.jar:/usr/local/hadoop/share/hadoop/common/lib/protobuf-java-2.5.0.jar:/usr/local/hadoop/share/hadoop/common/lib/log4j-1.2.17.jar:/usr/local/hadoop/share/hadoop/common/lib/curator-framework-2.7.1.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-math3-3.1.1.jar:/usr/local/hadoop/share/hadoop/common/lib/netty-3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-net-3.1.jar:/usr/local/hadoop/share/hadoop/common/lib/hadoop-auth-2.7.2.jar:/usr/local/hadoop/share/hadoop/common/lib/commons-cli-1.2.jar:/usr/local/hadoop/share/hadoop/common/lib/xz-1.0.jar:/usr/local/hadoop/share/hadoop/common/lib/xmlenc-0.52.jar:/usr/local/hadoop/share/hadoop/common/hadoop-common-2.7.2-tests.jar:/usr/local/hadoop/share/hadoop/common/hadoop-nfs-2.7.2.jar:/usr/local/hadoop/share/hadoop/common/hadoop-common-2.7.2.jar:/usr/local/hadoop/share/hadoop/hdfs:/usr/local/hadoop/share/hadoop/hdfs/lib/xml-apis-1.3.04.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/asm-3.2.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/guava-11.0.2.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jersey-server-1.9.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-daemon-1.0.13.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/servlet-api-2.5.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-codec-1.4.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/xercesImpl-2.9.1.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jetty-6.1.26.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-io-2.4.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-logging-1.1.3.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jackson-core-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jsr305-3.0.0.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/leveldbjni-all-1.8.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/htrace-core-3.1.0-incubating.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jetty-util-6.1.26.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/jersey-core-1.9.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-lang-2.6.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/protobuf-java-2.5.0.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/log4j-1.2.17.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/netty-3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/commons-cli-1.2.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/netty-all-4.0.23.Final.jar:/usr/local/hadoop/share/hadoop/hdfs/lib/xmlenc-0.52.jar:/usr/local/hadoop/share/hadoop/hdfs/hadoop-hdfs-2.7.2-tests.jar:/usr/local/hadoop/share/hadoop/hdfs/hadoop-hdfs-2.7.2.jar:/usr/local/hadoop/share/hadoop/hdfs/hadoop-hdfs-nfs-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-guice-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jackson-xc-1.9.13.jar:/usr/local/hadoop/share/hadoop/yarn/lib/asm-3.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/guava-11.0.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-collections-3.2.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-server-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/yarn/lib/servlet-api-2.5.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jaxb-impl-2.2.3-1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-codec-1.4.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jetty-6.1.26.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-io-2.4.jar:/usr/local/hadoop/share/hadoop/yarn/lib/stax-api-1.0-2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jackson-jaxrs-1.9.13.jar:/usr/local/hadoop/share/hadoop/yarn/lib/javax.inject-1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/guice-3.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jaxb-api-2.2.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-client-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-logging-1.1.3.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jackson-core-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-json-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/aopalliance-1.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jettison-1.1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jsr305-3.0.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/leveldbjni-all-1.8.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jetty-util-6.1.26.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-compress-1.4.1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/jersey-core-1.9.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-lang-2.6.jar:/usr/local/hadoop/share/hadoop/yarn/lib/activation-1.1.jar:/usr/local/hadoop/share/hadoop/yarn/lib/zookeeper-3.4.6.jar:/usr/local/hadoop/share/hadoop/yarn/lib/protobuf-java-2.5.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/log4j-1.2.17.jar:/usr/local/hadoop/share/hadoop/yarn/lib/netty-3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/yarn/lib/zookeeper-3.4.6-tests.jar:/usr/local/hadoop/share/hadoop/yarn/lib/commons-cli-1.2.jar:/usr/local/hadoop/share/hadoop/yarn/lib/xz-1.0.jar:/usr/local/hadoop/share/hadoop/yarn/lib/guice-servlet-3.0.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-api-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-resourcemanager-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-applications-distributedshell-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-applicationhistoryservice-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-common-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-nodemanager-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-registry-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-web-proxy-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-sharedcachemanager-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-common-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-server-tests-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-applications-unmanaged-am-launcher-2.7.2.jar:/usr/local/hadoop/share/hadoop/yarn/hadoop-yarn-client-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jersey-guice-1.9.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/asm-3.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/hamcrest-core-1.3.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/snappy-java-<IP_ADDRESS>.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jersey-server-1.9.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jackson-mapper-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/commons-io-2.4.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/paranamer-2.3.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/javax.inject-1.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/guice-3.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jackson-core-asl-1.9.13.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/aopalliance-1.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/avro-1.7.4.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/leveldbjni-all-1.8.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/junit-4.11.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/commons-compress-1.4.1.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/jersey-core-1.9.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/hadoop-annotations-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/protobuf-java-2.5.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/log4j-1.2.17.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/netty-3.6.2.Final.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/xz-1.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/lib/guice-servlet-3.0.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-app-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-common-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-hs-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-hs-plugins-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.2-tests.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-shuffle-2.7.2.jar:/usr/local/hadoop/share/hadoop/mapreduce/hadoop-mapreduce-client-core-2.7.2.jar:/usr/local/hadoop/contrib/capacity-scheduler/*.jar
STARTUP_MSG:   build = https://git-wip-us.apache.org/repos/asf/hadoop.git -r b165c4fe8a74265c792ce23f546c64604acf0e41; compiled by 'jenkins' on 2016-01-26T00:08Z
STARTUP_MSG:   java = 1.8.0_162
/
18/06/11 03:50:29 INFO datanode.DataNode: registered UNIX signal handlers for [TERM, HUP, INT]
18/06/11 03:50:30 INFO impl.MetricsConfig: loaded properties from hadoop-metrics2.properties
18/06/11 03:50:30 INFO impl.MetricsSystemImpl: Scheduled snapshot period at 10 second(s).
18/06/11 03:50:30 INFO impl.MetricsSystemImpl: DataNode metrics system started
18/06/11 03:50:30 INFO datanode.BlockScanner: Initialized block scanner with targetBytesPerSec 1048576
18/06/11 03:50:30 INFO datanode.DataNode: File descriptor passing is enabled.
18/06/11 03:50:30 INFO datanode.DataNode: Configured hostname is <IP_ADDRESS>
18/06/11 03:50:30 INFO datanode.DataNode: Starting DataNode with maxLockedMemory = 0
18/06/11 03:50:30 INFO datanode.DataNode: Opened streaming server at /<IP_ADDRESS>:50010
18/06/11 03:50:30 INFO datanode.DataNode: Balancing bandwith is 536870912 bytes/s
18/06/11 03:50:30 INFO datanode.DataNode: Number threads for balancing is 100
18/06/11 03:50:30 INFO datanode.DataNode: Balancing bandwith is 536870912 bytes/s
18/06/11 03:50:30 INFO datanode.DataNode: Number threads for balancing is 100
18/06/11 03:50:30 INFO datanode.DataNode: Listening on UNIX domain socket: /var/lib/hdfs/datanode_socket
18/06/11 03:50:30 INFO mortbay.log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
18/06/11 03:50:30 INFO server.AuthenticationFilter: Unable to initialize FileSignerSecretProvider, falling back to use random secrets.
18/06/11 03:50:30 INFO http.HttpRequestLog: Http request log for http.requests.datanode is not defined
18/06/11 03:50:30 INFO http.HttpServer2: Added global filter 'safety' (class=org.apache.hadoop.http.HttpServer2$QuotingInputFilter)
18/06/11 03:50:30 INFO http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context datanode
18/06/11 03:50:30 INFO http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context static
18/06/11 03:50:30 INFO http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context logs
18/06/11 03:50:30 INFO http.HttpServer2: Jetty bound to port 42678
18/06/11 03:50:30 INFO mortbay.log: jetty-6.1.26
18/06/11 03:50:30 INFO mortbay.log: Started HttpServer2$SelectChannelConnectorWithSafeStartup@localhost:42678
18/06/11 03:50:30 INFO web.DatanodeHttpServer: Listening HTTP traffic on /<IP_ADDRESS>:50075
18/06/11 03:50:30 INFO datanode.DataNode: dnUserName = root
18/06/11 03:50:30 INFO datanode.DataNode: supergroup = supergroup
18/06/11 03:50:30 INFO ipc.CallQueueManager: Using callQueue class java.util.concurrent.LinkedBlockingQueue
18/06/11 03:50:30 INFO ipc.Server: Starting Socket Reader #1 for port 50020
18/06/11 03:50:30 INFO datanode.DataNode: Opened IPC server at /<IP_ADDRESS>:50020
18/06/11 03:50:30 INFO datanode.DataNode: Refresh request received for nameservices: null
18/06/11 03:50:30 INFO datanode.DataNode: Starting BPOfferServices for nameservices:
18/06/11 03:50:30 INFO datanode.DataNode: Block pool  (Datanode Uuid unassigned) service to /<IP_ADDRESS>:9000 starting to offer service
18/06/11 03:50:30 INFO ipc.Server: IPC Server Responder: starting
18/06/11 03:50:30 INFO ipc.Server: IPC Server listener on 50020: starting
18/06/11 03:50:30 INFO common.Storage: Lock on /var/lib/hdfs/data/in_use.lock acquired by nodename 665@localhost
18/06/11 03:50:30 WARN common.Storage: java.io.IOException: Incompatible clusterIDs in /var/lib/hdfs/data: namenode clusterID = CID-ac91d691-a1c4-417e-a7de-5082f9b2f5aa; datanode clusterID = CID-57ca2ee4-d125-4166-b0c6-67e230ee53fb
18/06/11 03:50:30 FATAL datanode.DataNode: Initialization failed for Block pool  (Datanode Uuid unassigned) service to /<IP_ADDRESS>:9000. Exiting.
java.io.IOException: All specified directories are failed to load.
at org.apache.hadoop.hdfs.server.datanode.DataStorage.recoverTransitionRead(DataStorage.java:478)
at org.apache.hadoop.hdfs.server.datanode.DataNode.initStorage(DataNode.java:1358)
at org.apache.hadoop.hdfs.server.datanode.DataNode.initBlockPool(DataNode.java:1323)
at org.apache.hadoop.hdfs.server.datanode.BPOfferService.verifyAndSetNamespaceInfo(BPOfferService.java:317)
at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.connectToNNAndHandshake(BPServiceActor.java:223)
at org.apache.hadoop.hdfs.server.datanode.BPServiceActor.run(BPServiceActor.java:802)
at java.lang.Thread.run(Thread.java:748)
18/06/11 03:50:30 WARN datanode.DataNode: Ending block pool service for: Block pool  (Datanode Uuid unassigned) service to /<IP_ADDRESS>:9000
18/06/11 03:50:31 INFO datanode.DataNode: Removed Block pool  (Datanode Uuid unassigned)
18/06/11 03:50:33 WARN datanode.DataNode: Exiting Datanode
18/06/11 03:50:33 INFO util.ExitUtil: Exiting with status 0
18/06/11 03:50:33 INFO datanode.DataNode: SHUTDOWN_MSG:
/
SHUTDOWN_MSG: Shutting down DataNode at localhost/<IP_ADDRESS>
************************************************************/

The cause:
Previously install left 'HDFS related' data on the nodes, need to clean it.

18/06/11 03:50:30 WARN common.Storage: java.io.IOException: Incompatible clusterIDs in /var/lib/hdfs/data: namenode clusterID = CID-ac91d691-a1c4-417e-a7de-5082f9b2f5aa; datanode clusterID = CID-57ca2ee4-d125-4166-b0c6-67e230ee53fb
18/06/11 03:50:30 FATAL datanode.DataNode: Initialization failed for Block pool (Datanode Uuid unassigned) service to /<IP_ADDRESS>:9000. Exiting.
java.io.IOException: All specified directories are failed to load.

Run the script below to clean the old install (Please using the previously config files).
./paictl.py service delete -p $CONFIG_PATH

Hi @hao1939 ,
Of course, this command will work. But if someone wanna delete hadoop data only. The following command will be better.
./paictl.py service delete -p $CONFIG_PATH -n hadoop-service

after you change the master node, the cluster id on the data node is not the same with that of the new master node. Since the new master node has initialized a new cluster and data node they are still using the old master's cluster id. That can make hdfs fails. Change the master is not supported if you don't clean the whole data.


Redesign Annotations Pane

A few small design changes were made to the annotations pane as well as the addition of the "underline" text modifier (whose functionality will need to be added soon).

The number was removed in the most recent design update.
There might've been another branch merged recently that affected the styles on this, so I'll have to double check.

Thanks for clarifying the design update, @wgranger 👍
OK, I've tested this across OSX+Chrome62/FF56/Safari11 and Win7+IE11 - it looks good across all browsers, save for one exception: OSX+Chrome62, when viewing a Previous Annotation.

OSX+Chrome62, when clicking on a Previous Annotation.

Zoom. Enhance.
The dropdown icon looks a bit off - like it was offset by just a little bit. And only for Chrome. Eh?
That said, I'm thinking that this PR is good to merge. The visual error is minor enough that it can be fixed in a later PR, and for the moment, we have other things to focus on.


Update the melior dependency to 0.17.0

Melior is the crate that allows us to use MLIR in rust, there is a new version 0.17.0 that changes a bit the api (mainly argument order on integer attributres), so its a bit more work than just changing the version on the toml file.

Can I work on this one @edg-l ?

Can I work on this one @edg-l ?

sure thing!


Make SchemaModel use class name, define own config

Addresses #760. Also addresses an unrelated issue:
import pandera as pa

class Foo(pa.SchemaModel):
    pass

class Bar(pa.SchemaModel):
    pass

Foo.Config.name = 'foo'
Bar.Config.name  # => 'foo'

I realize that setting name on Foo.Config outside the class definition is not the intended usage, but people still might do it if they are dynamically generating SchemaModels. Better to not be able to alter the global default config from a subclass.
NOTE: There are a few tests that need to be updated, I'll do that if @cosmicBboy you agree with this change.

this change looks good, go ahead and update the tests! re: the lint failures not sure what's going on, I can take a look at that

@cosmicBboy Thanks for fixing the tests and will be happy to see this get merged!


gcad.servce = gcad.service

gcad Linux service misses an "i":
gcad.servce = gcad.service

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

ID: 42e15326-3ca0-09ce-97de-9764698a12f7
Version Independent ID: cacf47f9-eac8-a21a-9b92-86fa71136286
Content: Overview of the Connected Machine agent - Azure Arc
Content Source: articles/azure-arc/servers/agent-overview.md
Service: azure-arc
Sub-service: azure-arc-servers
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@sbagmeijer Thanks for your comment! We will review and provide an update as appropriate.

@sbagmeijer I have verified and updated the document as required. The change should reflect soon in the document i.e., in less than 24 hours. Thanks again!


Deploy Server.go binary instead of HelloWorld

Right now the terraform script is deploying the helloworld binary instead of the server.go binary. This of course will need to be fixed before the website will be useful.

Sounds like this is fixed?

Fixed!


Is having inspector be a separate thing worth the maintenance burden?

When we added the ability to introspect interactors, we didn't want to provide a method for fetching matching elements on an interactor, something like this:
let elements = await Button("Foo").all();

Instead we opted to create an inspector API like this:
let elements = createInspector(Button, document.body).all();

I don't remember the exact use-case that we added this for. Is it even still relevant?
At any case, the infrastructure needed to support this feature is quite expensive. Our types are already very complicated, and this feature further complicates them. We should be asking ourselves if this overhead is worth it. If we want to have this feature available, maybe a simpler API with a smaller API surface would do the trick as well, and we wouldn't have to complicate our types. Just some thinking as I was working on simplifying the typing.

@wKich I think you worked on this, right? Do you remember why we added this? I have a vague memory that you were working on a playground for interactors and that this had something to do with it, but I don't really remember how that panned out?

I need the .all method to show in inspector all matched elements. I asked @cowboyd about it and we decided to don't include .all method as a part of interactors API. I think we did it because the interactors must match with only one element.

The use-case is that we want to have a dynamic and visual way to see what interactors are matching, and what the values of their filters / locators are just by presenting them to a document.
These tools are really key in helping you "grok" how an interaction library works by letting you compare alternatives with an instant feedback loop.
Examples from other tools:

testing-library https://testing-playground.com
cypress: https://docs.cypress.io/guides/core-concepts/test-runner#Selector-Playground

I guess my questions are: 1) What is expensive about it? 2) can we refactor internals to make it less so, and 3) can we accomplish the use-case with a completely separate mecahnism?

@cowboyd it is "expensive" in this sense of course figuratively, because we have a very high cognitive burden on our types. I wrote them, and when I've been away for a little while from this project, I barely understand them anymore 😅 The inspector API further complicates these types (for example by splitting Interactor into BaseInteractor and  ExistsAssertionsImplementation), and it would be great to streamline this and simplify it. So the question it, can we build an inspector API which does not complicate our types?

One thing that occurred to me as I was having a look at this https://github.com/folio-org/stripes-testing/pull/140/files was that there is a case where they want to make assertions against multiple elements, in this case "all actions are enabled", or run an action against a set of interactors as in "check all of the filters". Using a "higher order interactor"  may be the way to accomplish this. This would be similar to the .all() solution Dmitriy proposed earlier, except I think by modeling All as an interaction itself might solve some of the issues?
import { All } from '@interactors/html';

await All(Button('Submit')).is({ disabled: true }))
await All(FieldSet('Filters').find(Checkbox()).click();

//useful to inspector
let buttonElements = await All(Button()).elements();

I'm not sure how this would effect the typing although it seems doable since All<T> would just be T & AllAPI. Where AllAPI is any extra filters that we want to add like the elements filter above.
But zooming out a couple thousand feet, I think that the core functionality needed for the inspector is basically these functions:
interactor -> HTMLNodeList
This is needed to highlight the elements in the DOM that are matched by the class of interactor
HTMLElement -> Interactor[]
This is the reverse operation, where if you are hovering over an element, we want to be able to highlight all of the interactors that match it.

The reason why split Interactor and added BaseInteractor, because there is no way to use a different resolver than the default one unsafeSyncResolveUnique. So we can't use All interactor because we can't change the resolver from the outside.

I think #139 solves this sufficiently well


No email if issue closed by commit

Gogs version (or commit ref): <IP_ADDRESS>5
Git version: 2.11.1
Operating system: Windows
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[x] Yes (provide example URL)
[ ] No
[ ] Not relevant

Description
If an issue is closed by commit (e.g. fix #X) the user who opened the issue is not informed by email.

I was wondering about this too

Patch has pushed to fix this issue, please test on develop branch or https://try.gogs.io.

The patch works, I've closed an issue with a commit, and I've received the notification email.

Can confirm this too


Another PS7 Error? Could not load type 'System.Management.Automation.PSSnapIn' from assembly

Here we go again.
With reference to issue https://github.com/microsoft/navcontainerhelper/issues/3527, the same script is now failing when using BC v24.1 and BCCH 6.0.18. Building the container works fine, it fails when I'm using Invoce-ScriptInBcContainer, where I'm trying to Import-Module SQLPS.
Could not load type 'System.Management.Automation.PSSnapIn' from assembly 'System.Management.Automation, Version=<IP_ADDRESS>0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
Same scripts works fine for v23 and earlier.  I can also see the same error reported in issue https://github.com/microsoft/navcontainerhelper/issues/3541.
Based on the version (<IP_ADDRESS>0) I assume it has something to do with the PowerShell version?
So, let me start by asking once again. When should we be using PowerShell 5 vs 7?
When should we be specifying PWSH when invoking scripts in the container, and when not?

Let me start by answering once again then:-)
BC24 and above runs PS7 inside the container by default. All versions before BC24 runs PS5.1.
As you probably know by now, all cmdlets in BC24 and above are PS7 with a bridge between PS5.1 and PS7.
Yes - you can run everything in PS5.1 inside the container (still), but performance will be much slower than running PS7.
Therefore, I have changed most scripts in BcContainerHelper to be able to run in PS7 - for the places, where the script was unable to run PS7 - I have used -usePsSession:$false -usePwsh:$false when invoking the script.
If you have your own scripts, you will need to do the same (or run PS5.1 always by setting $bcContainerHelperConfig.usePwshForBc24 = $false) - this will make everything run PS5.1 and you can continue as before with degraded performance however.
I cannot do magic - SQLPS doesn't exist in PS7 - only the SqlServer module, and that isn't compatible. I have installed the SqlServer module in PS7 by default and added some aliases to get some common scripts to run.
 If you want to run PS7 for performance - you need to modify your scripts to make them run.
Sorry - but this is the best I can do.

I am always open for good ideas, which can make life easier for everybody - feel free to suggest stuff - but not to make me load SQLPS on PS7 - that cannot be done.

I am always open for good ideas, which can make life easier for everybody - feel free to suggest stuff - but not to make me load SQLPS on PS7 - that cannot be done.

It can be done. But you must use PowerShell remoting to accomplish that (Import-Module -UseWindowsPowerShell):
This is bad:
PS C:\Users\ernjus> Invoke-ScriptInBcContainer -containerName $ContainerName -scriptblock { Import-Module -Name SQLPS; Invoke-Sqlcmd -ServerInstance 'docker.softera.lt' -Query 'SELECT 1' -Username 'containeruser' -Password 'Password1.' }
Could not load type 'System.Management.Automation.PSSnapIn' from assembly 'System.Management.Automation, Version=<IP_ADDRESS>0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

Container Free Physical Memory: 13.3Gb
Disk C: Free 124Gb from 127Gb

Services in container bc123:
Exception: C:\Users\ernjus\OneDrive - Softera Baltic UAB\Documents\PowerShell\Modules\BcContainerHelper\6.0.18\ContainerHandling\Invoke-ScriptInNavContainer.ps1:301
Line |
 301 |                          throw $errorMessage
     |                          ~~~~~~~~~~~~~~~~~~~
     | Could not load type 'System.Management.Automation.PSSnapIn' from assembly 'System.Management.Automation, Version=<IP_ADDRESS>0, Culture=neutral,
     | PublicKeyToken=31bf3856ad364e35'.

This is ok:
PS C:\Users\ernjus> Invoke-ScriptInBcContainer -containerName $ContainerName -scriptblock { Import-Module -Name SQLPS -UseWindowsPowerShell; Invoke-Sqlcmd -
ServerInstance 'docker.softera.lt' -Query 'SELECT 1' -Username 'containeruser' -Password 'Password1.' }

RunspaceId                           Column1
----------                           -------
0b40cdc5-eb64-474c-b386-a40b131e43f6       1

The main downside is performance hit because then PowerShell needs a few seconds to create PowerShell 5 session and load the module there.

There is nothing forcing you to use Invoke-ScriptInBcContainer.
The benefit of that is that it works using docker exec or sessions and auto-loads modules.
If you know what you are doing - create a PSSession and use Invoke-Command instead.
I decided against the -useWindowsPowershell mostly because it sounds like a giant hack - but maybe it isn't.
Kind of like the bridge - any swapping back and forth between PS5 and PS7 must be slow - so I decided to face the issues - enable PS7 for BC24 and fix everything I encountered.
Problem for me was that it took most of 4-6 weeks.


Add configurability for unicode and skipping parsers

Unicode support greatly increases memory and latency and is not generally needed.
Compiling regex for unused parsers is just a waste of memory.

Both unicode support and device/os/user_agent parsers can now be configured via UserAgentParserBuilder.

I dug in a bit after this discussion about memory usage: https://github.com/rust-lang/regex/issues/1027#issuecomment-1625742621
I took at a look at other uaparser implementations and none of them are done with full unicode support. The uaparser-core test suite passes without it just fine. So I moved everything to use regex::bytes::Regex and make unicode a configuration option.
Additionally, we at Remind are only interested in OS for our use case. What we've been doing has been to take the core regex yaml file and deleting the Device and User Agent sections, but it would be nice to not have to curate that ourselves and instead just pass in flags to only parse and use the os parsers. So I added the ability to disable any of os, device, and user_agent parsers to save on memory.
Some performance numbers with these changes:
First, memory usage
➜  uap-rs git:(main) ✗ /usr/bin/time -l target/debug/examples/full_parser
Client { device: Device { family: "Mac", brand: Some("Apple"), model: Some("Mac") }, os: OS { family: "Mac OS X", major: Some("10"), minor: Some("15"), patch: Some("7"), patch_minor: None }, user_agent: UserAgent { family: "Chrome", major: Some("114"), minor: Some("0"), patch: Some("0") } }
        5.48 real         5.40 user         0.07 sys
           296796160  maximum resident set size
                   0  average shared memory size
                   0  average unshared data size
                   0  average unshared stack size
               18210  page reclaims
                  11  page faults
                   0  swaps
                   0  block input operations
                   0  block output operations
                   0  messages sent
                   0  messages received
                   0  signals received
                   0  voluntary context switches
                 101  involuntary context switches
<PHONE_NUMBER>2  instructions retired
<PHONE_NUMBER>1  cycles elapsed
           282281600  peak memory footprint
➜  uap-rs git:(main) ✗ /usr/bin/time -l target/debug/examples/no_unicode_parser
Client { device: Device { family: "Mac", brand: Some("Apple"), model: Some("Mac") }, os: OS { family: "Mac OS X", major: Some("10"), minor: Some("15"), patch: Some("7"), patch_minor: None }, user_agent: UserAgent { family: "Chrome", major: Some("114"), minor: Some("0"), patch: Some("0") } }
        1.01 real         0.99 user         0.01 sys
            63062016  maximum resident set size
                   0  average shared memory size
                   0  average unshared data size
                   0  average unshared stack size
                3949  page reclaims
                   6  page faults
                   0  swaps
                   0  block input operations
                   0  block output operations
                   0  messages sent
                   0  messages received
                   0  signals received
                   0  voluntary context switches
                  33  involuntary context switches
<PHONE_NUMBER>8  instructions retired
<PHONE_NUMBER>  cycles elapsed
            59262016  peak memory footprint
➜  uap-rs git:(main) ✗ /usr/bin/time -l target/debug/examples/os_only_no_unicode_parser
Client { device: Device { family: "Other", brand: None, model: None }, os: OS { family: "Mac OS X", major: Some("10"), minor: Some("15"), patch: Some("7"), patch_minor: None }, user_agent: UserAgent { family: "Other", major: None, minor: None, patch: None } }
        0.16 real         0.16 user         0.00 sys
            10469376  maximum resident set size
                   0  average shared memory size
                   0  average unshared data size
                   0  average unshared stack size
                 740  page reclaims
                   5  page faults
                   0  swaps
                   0  block input operations
                   0  block output operations
                   0  messages sent
                   0  messages received
                   0  signals received
                   0  voluntary context switches
                   9  involuntary context switches
<PHONE_NUMBER>  instructions retired
           497911781  cycles elapsed
             6668992  peak memory footprint

Disabling Unicode takes us from 300MB to 60MB, and only doing the OS parsers takes that all the way to 10MB.
Beyond memory, the cargo bench results are also nice to see:
parse_device            time:   [578.92 ms 581.72 ms 584.82 ms]
                        change: [-0.9028% +0.0193% +1.0401%] (p = 0.99 > 0.05)
                        No change in performance detected.
Found 7 outliers among 100 measurements (7.00%)
  4 (4.00%) high mild
  3 (3.00%) high severe

parse_device unicode disabled
                        time:   [496.35 ms 498.60 ms 500.98 ms]
                        change: [+0.0428% +1.2668% +2.4227%] (p = 0.05 > 0.05)
                        No change in performance detected.

parse_os                time:   [2.3230 ms 2.3356 ms 2.3488 ms]
                        change: [-2.9222% -1.7137% -0.4659%] (p = 0.01 < 0.05)
                        Change within noise threshold.
Found 8 outliers among 100 measurements (8.00%)
  7 (7.00%) high mild
  1 (1.00%) high severe

parse_os unicode disabled
                        time:   [2.3017 ms 2.3118 ms 2.3228 ms]
                        change: [-0.5476% +0.1792% +0.9374%] (p = 0.66 > 0.05)
                        No change in performance detected.
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high mild

parse_user_agent        time:   [174.95 ms 175.33 ms 175.73 ms]
                        change: [-1.2574% -0.5656% +0.1207%] (p = 0.10 > 0.05)
                        No change in performance detected.
Found 3 outliers among 100 measurements (3.00%)
  3 (3.00%) high mild

parse_user_agent unicode disabled
                        time:   [56.693 ms 56.998 ms 57.326 ms]
                        change: [-2.7180% -1.5820% -0.3546%] (p = 0.01 < 0.05)
                        Change within noise threshold.
Found 2 outliers among 100 measurements (2.00%)
  2 (2.00%) high mild

A huge speedup on the user_agent parsing (57ms vs 175ms), a moderate speedup on device parsing (498 vs 581), and not much change on OS.
I left the unicode support in as the default to make this a non-breaking change, but honestly it's just not needed and I'd recommend we rip it out and just make everything not support unicode.
Anyway, let me know what you think.

This example is a good example of how the new builder works and the configuration available https://github.com/davidarmstronglewis/uap-rs/pull/14/files#diff-f2849e4e13ac1633666e5ef659e790e06feb21fa5848bf7268b80e7e7de39a94

Hey @hamiltop, thank you for the lovely PR and for linking out to context around these changes. Solid change, my only feedback would be to hide the new UserAgentParserBuilder behind a builder method rather than exporting the type directly. In case you've moved on to something else I've pushed up this branch which does just that (and updates some Nix stuff; which you can ignore).
Once this is in I'll cut a new release. Thanks again ❤

Great. Updated from your branch and then fixed up a few tests to use the new syntax. Should be g2g here.


Preserve inspector focus when opening script from scene tree

Implements https://github.com/godotengine/godot-proposals/issues/247#issuecomment-561429796 (and also resolves https://github.com/godotengine/godot/issues/77791)
Opening a script by clicking on a script icon in the scene tree dock currently causes the script resource to grab the inspector's focus. This PR prevents this and leaves the inspector unchanged.
Inpector after opening script from scene tree dock:

Before PR

After PR

Thanks!


Mouse issues after clicking Paint or Build

When either of the buttons are pressed and I move over any other option they all get "clicked". Can't paint/build directly either because the mouse is apparently in a different state until I focus my 3D view and click.
Blender 2.78
Edit:
I can't click any options after focusing the 3D view until i hit escape.

Thanks for the report, will look into this.

Hi, not sure I can replicate this bug but there's a new update to Sprytile. There were some changes to handling the UI. Can you please check if it still occurs with 0.4.0? Thanks!

Here is a screen capture
It works a bit better now, the initial state of a button press only affects the adjacent buttons/options.
Once I click in my 3D view the first click doesn't actually build/draw anything. It's only on the second click.
I'm assuming the first click actually releases the button down state on the ui button. After clicking in 3d view, When I go back to the options you notice that it doesn't automatically select any of the buttons anymore when I hover over them.
fyi, 5 days ago I did a clean image reload of my pc. Blender is clean and so is your addon.
Perhaps it's bugged due to my mouse settings?
I can't actually remember what the default settings were though.

Thanks for this detailed bug report.

Do you have any other plugins installed? Your mouse settings look to be default, so that doesn't seem to be it.

Nothing of significance, pie menu and ogex exporter. But as I have mentioned when I tested it I had a clean install of blender. I might have enabled something on accident, but I honestly wouldn't what that be.
im on 2.78c

Downloaded 2.79 and the problem is gone. No idea what it could have been.

Thanks for trying it out with 2.79. Hope you have fun with using Sprytile :)

The problem is back. Using version 0.4.36


ServerVulnerabilityAssessmentClient Delete returns error object even if successful

Bug Report

import path of package in question, e.g. github.com/Azure/azure-sdk-for-go/services/preview/security/mgmt/v3.0/security
SDK version 31.1.0

Specify the exact commit if possible: 397140cd20ce375b8da0534436fb918389917264

output of go version go version go1.15.6 darwin/amd64

What happened?
When invoking Delete for a server vulnerability assessment the API an error object is returned since the backend API responds with 202.

What did you expect or want to happen?
Error object should be nil if the resource is successfully deleted.

How can we reproduce it?

Create virtual machine
Create server vulnerability assessment on that virtual machine
Wait for the server vulnerability assessment to be fully created (~1min)
Invoke the delete operation and inspect the error object that is returned

Anything we should know about your environment.

Discovered while adding support for server vulnerability assessment to terraform Pull Request on terraform

Hi @martenbohlin thanks for this issue!
This is a swagger bug - this API appears to be an async operation (otherwise it would not return 202 as response code), but it is not marked as long-running-operation in the swagger which results in an SDK with issues.
I have tagged this issue so that the corresponding service team will have a look and provide a fix for the swagger, then we can regenerate our SDK to fix this issue.

Hi @martenbohlin thanks for this issue!
This is a swagger bug - this API appears to be an async operation (otherwise it would not return 202 as response code), but it is not marked as long-running-operation in the swagger which results in an SDK with issues.
I have tagged this issue so that the corresponding service team will have a look and provide a fix for the swagger, then we can regenerate our SDK to fix this issue.

And also this issue has already been reported here: https://github.com/Azure/azure-rest-api-specs/issues/12308
Therefore close this issue in favor of the issue above.

And also this issue has already been reported here: https://github.com/Azure/azure-rest-api-specs/issues/12308
Therefore close this issue in favor of the issue above.


Add logs to StartSDL & StopSDL methods

Related:
APPLINK-14138
old pull request

@LuxoftAKutsan , changed logs

reviewed


x/pkgsite: mismatch between GetLatestMajorPathForV1Path and getLatestMajorVersion

What is the URL of the page with the issue?
https://pkg.go.dev/github.com/mediocregopher/radix
Screenshot

What did you do?

Visited https://pkg.go.dev/github.com/mediocregopher/radix and was redirected to https://pkg.go.dev/github.com/mediocregopher/radix/v4. This should redirect to https://pkg.go.dev/github.com/mediocregopher/radix/v3, since that is the highest tagged version.
This is due to a mismatch in the logic between GetLatestMajorPathForV1Path and getLatestMajorVersion. GetLatestMajorPathForV1Path looks for the highest major version, numerically. getLatestMajorVersion takes into account whether the module has tagged versions.

@julieqiu I would like to pick up this issue

@julieqiu I would like to pick up this issue

This has been fixed.


Add Executable Packing

https://github.com/dhondta/awesome-executable-packing
This provides a full bibliography, links to packers, unpackers and other related tools for executable formats (PE, ELF, ...). This aims to complement the Malware Analysis list.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Commented on https://github.com/sindresorhus/awesome/pull/2133
Commented on https://github.com/sindresorhus/awesome/pull/1966
unicorn

Please note that npx awesome-lint https://github.com/dhondta/awesome-executable-packing still gives 29 errors whose :

1 is related to an entry from the ToC ; I don't see what to fix...
27 are related to double links while the nested links are URL-encoded.
1 is about a list item description starting with an invalid case, but I don't see where.

The description is meta. See:

Includes a succinct description of the project/theme at the top of the readme. (Example)
- ✅ Mobile operating system for Apple phones and tablets.
- ✅ Prototyping interactive UI designs.
- ❌ Resources and tools for iOS development.
- ❌ Awesome Framer packages and tools.

Also, there's five different commits. You might want to combine them into one.

The description is meta. See:

Includes a succinct description of the project/theme at the top of the readme. (Example)

white_check_mark Mobile operating system for Apple phones and tablets.
white_check_mark Prototyping interactive UI designs.
x Resources and tools for iOS development.
x Awesome Framer packages and tools.

Also, there's five different commits. You might want to combine them into one.

Hi @catdevnull
Thank you for your review. What do you mean by "the description is meta" ? Is there anything to improve ?
For the five commits, they will be merged as a single one through the PR. This is not an issue.

Me explican porque así ya no estaré ok saludos

Thank you for your review. What do you mean by "the description is meta" ? Is there anything to improve ?

What I mean is that the guidelines suggest talking about the subject of the list instead of the list itself.

Thank you for your review. What do you mean by "the description is meta" ? Is there anything to improve ?

What I mean is that the guidelines suggest talking about the subject of the list instead of the list itself.

Hi @catdevnull
You're probably right but I included a description in the same format such as awesome-malware-analysis. I've seen many other awesome lists having such a format so far. I don't think it's that critical. How would you adapt it ?

I agree, I don't think it's that critical. I just thought it wasn't quite aligned with what the guidelines said.
I can't really define executable packing in one sentence; maybe something along the lines of:

Executable packing is the art(?) of the different methods of compressing, obfuscating and packing files into an executable file.

The list description in the list readme needs to be improved.

Many entries are missing a description.

Descriptions should not be title-case.

The list description in the list readme needs to be improved.

Sorry, but I don't see how to improve it. What do you think is unclear in what is currently described ?

Many entries are missing a description.

This is still work in progress ; I generate the README from a Zotero knowledge base and I'm progressively filling in entries.

Descriptions should not be title-case.

Which descriptions are you talking about ? If you mean the Bibliography section, it's normal as these are titles of the papers, books and other resources, which always have cased titles.

I agree, I don't think it's that critical. I just thought it wasn't quite aligned with what the guidelines said. I can't really define executable packing in one sentence; maybe something along the lines of:
…
Executable packing is the art(?) of the different methods of compressing, obfuscating and packing files into an executable file.

@catdevnull : FYI ; I added a definition of packing. Thank you for the suggestion.


Memory saving

To save memory usage, I change the dictionary structure to read only necessary part by separating part of speech from contents.

Coverage decreased (-0.4%) to 85.484% when pulling 1d044fa0cc383645e118377458119eaa058e7689 on develop into 1907ebee8fe1a347250f3a2679f7c30d4efcfb96 on master.


Use a local 'regs' pointer in executor dispatch loop

Current executor looks up register values through thr->valstack_bottom. If thr is not already in a register, this requires two pointer lookups. Adding regs to the executor stack frame ensures register base is always at most a single lookup because the stack pointer is not spilled.

This is not as easy to implement as #295 because the value stack base pointer is not stable - the value stack can be reallocated by many operations, in particular any DECREF may trigger a side effect which causes that.
One solution to this is to stash the address of the bytecode executor regs variable (which may need to be marked volatile) somewhere and then update it when resizing the value stack.
If this turns out too difficult, I'll postpone this to 1.4.

It is also important to avoid unintentional ancillary spilling--I saw a few comments already where the type of thing described here was foregone because it increased footprint...

Based on a quick test this might decrease footprint slightly - for every case where thr->valstack_bottom lookup requires a lookup of thr and then thr->valstack (instead of just looking up regs from stack) footprint decreases. There might be cases where looking up regs would push out something, but it's hard to imagine where that wouldn't have happened also when looking up thr->valstack_bottom through thr.
The performance improvement is not as clear because regs must be volatile and carefully managed so that it is always re-read from the stack frame if it may have changed (i.e. after any DECREF or any other side effects). Just naively using a volatile duk_tval *regs with no other changes decreases performance slightly. To get a performance increase, the idiom probably needs to be something like:
volatile duk_tval *regs_volatile;

case DUK_OP_ADD: {
    duk_tval *regs = regs_volatile;
    /* read registers using 'regs' which is not volatile */
    ...
    DECREF();
    regs = regs_volatile;  /* re-read if needed further */
    ...
}

The compiler will basically emit a load from the stack frame for 'regs' and keep it in a register, and then do whatever operations are necessary. This will work poorly if 'regs' then gets spilled during the operation; instead of just reloading regs_volatile the compiler will need to write regs out and load it back in later.
Anyway, I'm postponing this to 1.4 because this will need much more testing than the similar (but much easier) consts change.

The code footprint difference is -0.5kB for gcc -O2 build, but the quick test is missing value stack resize handling. The final difference would be less than that.

Using "volatile" should not be strictly necessary, ordinary aliasing rules should ensure correctness. In other words, the compiler can avoid re-reading the regs base pointer if no write could have changed it.

The impact of this is not clear so I'll drop this out of 1.5.0 release.


book-cd.yml uses a deprecated Node.js version

https://github.com/huggingface/candle/actions/runs/11342314214


[BUG] jest-expo prevents Node from reading global.gc correctly

Investigate what's up there in the jest-expo preset that prevents global.gc from being correctly populated by the --expose-gc flag. See: https://github.com/callstack/reassure/issues/174

Worthy of note: I am able to reproduce this error by simply adding jest-expo as a dependency and running yarn reassure; I don't need to require() in my jest.config.js and set it as a preset.

Resolved by #386. Support for jest-expo added in Reassure 0.9.0, which I've released yesterday.


remove std::cout

Issue revealed in CRAN submission.

Replaced these incorrect uses of std::cout with our _nimble_global_output stream.


Fix / update linux.scp action

Currently, linux.scp action is mostly useless if you want to download files from a remote server to a local one since it expects a dest_server argument.
We have a couple of ways to solve this:

Make scp action "desination agnostic" - instead of taking dest_server parameter, make it just take source and destination arguments. This way it works both ways (upload, download) since source and destination can either be a remote host with a path or just a path.
Rename existing scp action to scp_upload and add a new inverse scp_download action.

I like the idea of upload/download personally. This feels more like a generic action (get file, put file) that could switch backends if need be (FTP, FTPS, maybe CIFS/NFS), and would make actions more interchangeable. I see this as being some cases with ETL that we will have come up before long.

Resolved by #3335 #3463


Set CSS style of element

I'm trying to set a CSS property for a text component, but it doesn't appear to be working.
The documentation for Minified suggests the following should work, but it just sets the innerHTML for the component to "$overflowWrap"
clayConfig.getItemById('ConfigString').set('$overflowWrap','break-word');
I also tried the following, but it appears to just set the innerHTML to the Variable without including the surrounding .
clayConfig.getItemById('ConfigString').set('' + ConfigString + '');

configItem is not a Minifed list. The .set() method sets the value of the item. what you want is:
clayConfig.getItemById('ConfigString').$element.set('$overflowWrap','break-word');
Have a look at the docs here: https://github.com/pebble/clay#clayitem-object-config-


Can one get two-word suggestions?

Is it possible to get two-word completion? In first second third buffer content I would like to have first second as suggestion when I start typing first, and second third as suggestion when I start typing second.

I think what you really want here is something like https://github.com/hrsh7th/nvim-compe/issues/299, which I would also welcome.

@hrsh7th I was thinking whether locality bonus could be used here. I can imagine situation when, if enabled and perhaps with specific option set on top of it, it would take into consideration previous word in line, or last word of line above (if completion is for empty line), find one-before-this occurrence of that word and suggest word that followed with very high score.
What do you think? Is it feasible?


Don't override custom provider on update

Here's what I did
I updated the plugin through qgis.

Here's what I got
my custom providers are gone.

Here's what I was expecting
my custom providers to be preserved

Here's what I think could be improved
store custom providers in a different place or in a file that does not get overwritten.

also the api-key is lost each time

good point. it's the same file, config.yml. you got time for a PR? :wink:


Add Missing paths to MaxRetriesExceededError

One of the most cryptic errors in Falcor is the MaxRetriesExceededError. This error usually occurs when the server neglects to send back a value for a requested path. The ergonomics of this error could be improved significantly by simply including the set of missing paths that the model is unable to find in the error itself.
var error = new MaxRetriesExceededError(missingPaths);
console.log (error.missingPaths);

@sdesai

Fixed. https://github.com/Netflix/falcor/pull/874


feat/typescript support

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: pheew:x: gutenyeYou have signed the CLA already but the status is still pending? Let us recheck it.

Closed, no intention to create a PR


Fix package spec by using at symbol.

Tried to use the feature npm-package:1 but opening in container failed with:
Options       :
    PACKAGE="wrangler"
    VERSION="2.6.2"
===========================================================================
[2022-12-23T10:56:57.516Z] npm
[2022-12-23T10:56:57.516Z]  ERR! code EINVALIDTAGNAME
[2022-12-23T10:56:57.519Z] npm ERR! Invalid tag name "wrangler==2.6.2" of package "wrangler==2.6.2": Tags may not have any characters that encodeURIComponent encodes.
[2022-12-23T10:56:57.521Z]
npm ERR!

I could be doing something wrong but it seems npm install package-spec doesn't support the format PACKAGE==VERSION.
Quoting https://docs.npmjs.com/cli/v9/commands/npm-install#description

A package is:

a) a folder containing a program described by a [package.json](https://docs.npmjs.com/cli/v9/configuring-npm/package-json) file
b) a gzipped tarball containing (a)
c) a url that resolves to (b)
d) a <name>@<version> that is published on the [registry](https://docs.npmjs.com/cli/v9/using-npm/registry) (see registry) with (c)
e) a <name>@<tag> (see [npm dist-tag](https://docs.npmjs.com/cli/v9/commands/npm-dist-tag)) that points to (d)
f) a <name> that has a "latest" tag satisfying (e)
g) a <git remote url> that resolves to (a)

My proposal complies with bullet d)
Cheers

Thanks! Dont know how did I missed that


v1.0 launch

creating this so once im done with everything and its polished, i can launch it and merge it. i already moved master to pre-rewrite so thats out of the way.

jekdkfkidjfusjfkgoriweiwiid

ok, im gonna do this early


install pub (crypto ^2.1.2 and web_socket_channel 2.1.0)

Describe the bug
instalation failed
Because every version of sip_ua depends on crypto ^2.1.2 and web_socket_channel 2.1.0 depends on crypto ^3.0.0, sip_ua is incompatible with web_socket_channel 2.1.0.
To Reproduce
Steps to reproduce the behavior:
flutter pub add sip_ua
Expected behavior
Because every version of sip_ua depends on crypto ^2.1.2 and web_socket_channel 2.1.0 depends on crypto ^3.0.0, sip_ua is incompatible with web_socket_channel 2.1.0.
System Infomation()
Flutter SDK Version: 2.2.2
Target OS and Version:
Host OS and Version:

You could perhaps use web_socket_channel without a specified version e.g web_socket_channel:  which will use compatible version for your project

Hi there. I am a freelancer and I need assistance with this plugin.
I have been provided with the websocket uri, sipURI, password and sorts. And when I use it then there is no connection,
Could you perhaps show or at least tell me what I should expect in the debug output if it had connected or not


Sign Up page link "Sign Up with one of your existing third party accounts" that takes nowwhere

In the Sign Up page, "Sign Up with one of your existing third party accounts" is an <a> element, but it isn't underlined and doesn't link anywhere.

Video:
https://github.com/cppalliance/temp-site/assets/2286304/9eeb4194-a8e0-4749-b1ee-fb58d75b6dba
Dev Notes:

Both links on this page direct to the same page, which is the page the link is on.
But they direct to different divs -- the social signup div (which is the default, and why the first link doesn't look like a link when you first load the page) or the email signup div.
Each link is always present and always clickable, but they are only styled as links when the user is on the opposite option. So I see the email signup link when I also see the social signup content, and I see the social signup link when I see the email signup content.

Code snippet: https://github.com/cppalliance/temp-site/blob/develop/templates/account/signup.html#L24C9-L40C15
@anarthal I think this is intended behavior but @gregnewman can you confirm?

Resolved when Greg did away with the show/hide of the two login/signup pages


Remove non-existing solc argument

Without this change pyethereum will no longer work with solidity >= 0.4.21
Solidity issue: https://github.com/ethereum/solidity/issues/3695

@joeykrug ping. (Just because I saw that you merged the latest PRs)

Looks good, thanks!


[Feature Request] A Linux version

Linux support by this tool would be great.

Please read README from start to end before requesting such thing.

Good, anything else?

Short version: it's possible, but it would take an entire rewrite.

On Mar 11, 2018, at 11:37 AM, "M.Hanny Sabbagh"<EMAIL_ADDRESS>wrote:
Good, anything else?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

https://github.com/ValdikSS/GoodbyeDPI/blob/master/README.md#similar-projects
specially for u.

@r4sas Which redirects to another different project, which is completely unrelated to what am asking although I just used 10 words to easily describe my request.

linux wiki please

I cant even read the zagret readme file.
it is all in russian.
can it be translated or at least described by a russian guy, how can I use that application?
it is the same as this one and I just run and also add iptable rules?

@rezad1393 please dont post off topic messages.
For any issues with zapret go to https://github.com/bol-van/zapret/issues

it is the same as this one and I just run and also add iptable rules?

Yes. But GDPI uses WinDivert to create iptables-like rules on windows.

sorry.
I got sorta desperate.
did I get that right that you are trying to make this app for linux too? if so, where can I track that?

For Linux there's the other project, close to this one. I also can't read russian, but asking for info in a friendly manner may help.

@rezad1393 the top of the readme you're referring to mentions a file docs/readme.eng.txt

For Linux there's the other project, close to this one. I also can't read russian, but asking for info in a friendly manner may help.

Where is this project?

For Linux there's the other project, close to this one. I also can't read russian, but asking for info in a friendly manner may help.

Where is this project?

Here

Thank you!


Configure for travis + saucelabs

Changes Unknown when pulling ad79f46f1668106a6b5406aa2c2cc7962fe479fe on saucelabs into ** on master**.

Changes Unknown when pulling ad79f46f1668106a6b5406aa2c2cc7962fe479fe on saucelabs into ** on master**.


Version sorting

At recipe https://conan.io/center/recipes/emsdk
versions sorted not according to semver order

Hi @SavenkovIgor - Thanks for reporting it!
This is a known issue at the moment: https://github.com/conan-io/web/issues/37
We're working on that to solve it asap 😄


Footer UI can be improved.

Sure u can do it now

sir i have a bit experience in UI may I work on it ?

I would love to contribute on this issue ...plz assign this to me.

hey kindly assign it to me. i will surely resolve it.

@Sameer1408  @Paawan9700 @tanvideshmukh29  i am working on this issue you make look for others.

sir i have a bit experience in UI may I work on it ?

Sure

Assigined everyone please share the work among yourself and PR accordingly

Hey i am a UI designer and i can work on this.


Implement a CI/CD solution for indexing operator packages

Provide an automated way of indexing operator packages provided by third-party projects and adding/updating KUDO's community operator repository from this index.

This is implemented with https://github.com/kudobuilder/operators-index.


camera screen getting paused when user open camera while on call.

camera screen pauses when user's is on phone call. After the call ends, the camera view screen resumes to normal.

I will look into this

okay. thanks. Actually i find out the cause of this issue. Its because of the use of phone microphone. During call, the microphone get activated for call but the same if swift camera is opened, it also needs microphone usage for video recording. Because of this conflict, the camera screen gets paused,. Hopes this will help in finding solution.

Any updated on this by any chance?

@Awalz  @Jitenderios  @aurora14 Any updates?

@Awalz is there any option to toggle if the user is in a phone call to at least allow taking pictures?

this happen because of app goes in background mode and video recording is stop at that time and this didFailToRecordVideo delegate method was called and it was same for default camera
in default camera when app is goes in background mode than video recording was cancel so when app is goes in BG mode so cancel all recording code


Unable to boot Linux - userspace cannot write to console, no busybox shell

I'm building LiteX SoC with Rocket on a digilent nexys video board, which is listed as one of the supported platforms here:
./litex-boards/litex_boards/targets/digilent_nexys_video.py --sys-clk-freq 50e6 --with-ethernet --with-sdcard --cpu-type rocket --cpu-variant fulld --csr-json ./newdts.json --build
I have so far built linux with both the litex-rebase, and the master branches on the litex-hub/linux repository. My linux config requires the CONFIG_RISCV_SBI_V01=y option, otherwise it hangs as described here around the loop: module loaded debug message (long before starting init)
With the sbi_v01 option enabled, i manage to get it to boot until the following is seen:
[    0.093898] Run /init as init process
[    0.093923]   with arguments:
[    0.093953]     /init
[    0.093975]   with environment:
[    0.094006]     HOME=/
[    0.094030]     TERM=linux

When using the pre-built initramfs.cpio from the releases here.
I am sure that the init does actually start running, which i tested by creating a custom init executable that segfaults:
#include <stdlib.h>
#include <stdio.h>

#define ERROR(x) { int *tmp = (int*)x; *tmp = 0xDEADBEEF; }

int main() {
    printf("--------------------------- Hello, world!-------------------- \n");
    system("echo \"$$$$$$ HELLO WORLD FROM system()\" >/dev/kmsg");

    ERROR(0xffff0000ffff0000);
}

[    0.093893] Run /init as init process
[    0.093919]   with arguments:
[    0.093948]     /init
[    0.093970]   with environment:
[    0.094002]     HOME=/
[    0.094025]     TERM=linux
[    0.094406] init[1]: unhandled signal 11 code 0x1 at 0xffffff80ffff0000 in init[10000+62000]
[    0.094484] CPU: 0 PID: 1 Comm: init Not tainted 6.3.0-rc3-g640cc8df93a6 #55
[    0.094554] epc :<PHONE_NUMBER>010664 ra :<PHONE_NUMBER>01064a sp : 0000003fcacb7c10
[    0.094627]  gp :<PHONE_NUMBER>078bb8 tp :<PHONE_NUMBER>07e7e0 t0 :<PHONE_NUMBER>000002
[    0.094699]  t1 :<PHONE_NUMBER>009000 t2 : 000000006fffff41 s0 : 0000003fcacb7c30
[    0.094771]  s1 :<PHONE_NUMBER>000001 a0 :<PHONE_NUMBER>007f00 a1 : 0000003fcacb78d0
[    0.094843]  a2 :<PHONE_NUMBER>000000 a3 :<PHONE_NUMBER>000000 a4 : ffffffffdeadbeef
[    0.094915]  a5 : ffff0000ffff0000 a6 :<PHONE_NUMBER>074e98 a7 :<PHONE_NUMBER>000087
[    0.094987]  s2 : 0000003fcacb7dd8 s3 :<PHONE_NUMBER>000001 s4 : 0000003fcacb7de8
[    0.095059]  s5 :<PHONE_NUMBER>01062a s6 :<PHONE_NUMBER>000001 s7 :<PHONE_NUMBER>000001
[    0.095131]  s8 :<PHONE_NUMBER>000000 s9 :<PHONE_NUMBER>000000 s10:<PHONE_NUMBER>000000
[    0.095203]  s11:<PHONE_NUMBER>000000 t3 : 0000003f836b3000 t4 :<PHONE_NUMBER>000011
[    0.095275]  t5 :<PHONE_NUMBER>000000 t6 :<PHONE_NUMBER>072d80
[    0.095328] status:<PHONE_NUMBER>006020 badaddr: ffffff80ffff0000 cause:<PHONE_NUMBER>00000f
[    0.095412] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    0.095484] CPU: 0 PID: 1 Comm: init Not tainted 6.3.0-rc3-g640cc8df93a6 #55
[    0.095554] Call Trace:
[    0.095578] [<ffffffff800051b8>] dump_backtrace+0x1c/0x24
[    0.095632] [<ffffffff804c86bc>] show_stack+0x2c/0x38
[    0.095683] [<ffffffff804d0104>] dump_stack_lvl+0x3c/0x54
[    0.095736] [<ffffffff804d0130>] dump_stack+0x14/0x1c
[    0.095787] [<ffffffff804c87c4>] panic+0xfc/0x284
[    0.095834] [<ffffffff80010b4a>] do_exit+0x704/0x70a
[    0.095883] [<ffffffff80010cbe>] do_group_exit+0x24/0x6c
[    0.095936] [<ffffffff8001ba76>] get_signal+0x7e4/0x814
[    0.095988] [<ffffffff80004486>] do_work_pending+0xfa/0x422
[    0.096044] [<ffffffff800032c2>] resume_userspace_slow+0x8/0xa
[    0.096103] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

I have tried device trees from both the linux-on-litex-rocket repo, and by making my own using csr_json argument and then json2dts. I have attached the dts i'm currently using to the post.
I have also tried this flow with both linuxd + bbl with rv64imac, and fulld = bbl with rv64imafdc, observing the same issues.
I have additionally tried various permutations of the console= parameter passed to the kernel, but only console=liteuart0 seems to be working correctly, other options such as liteuart, sbi, or ttyLXU0 either result in warning: unable to open initial console errors, or a warning stating that the console argument is malformed during very early stages of the boot.
I have attached the full kernel log too. Thanks
log.txt
mydts.txt

On Wed, Mar 22, 2023 at 08:45:41AM -0700, Norbert Kremeris wrote:

I'm building LiteX SoC with Rocket on a digilent nexys video board, which is
listed as one of the supported platforms here.

If you're using the pre-built binaries for software, chances are that
MMIO registers placement has changed in more recent gateware builds.
If you're putting together your own software, make sure your
devicetree .dts matches the way your gateware was built (use
--csr-csv ./csr-csv to ensure that information is captured during
build).
HTH,
--Gabriel
PS. please be warned that cpu variant naming is about to be changed
pretty significantly, which will make the
"linux-on-litex-rocket/README.md" (even more) obsolete, and in need of
an update (next on my list, I promise :) )

Hi Gabriel! Sorry, i accidentally posted the issue without writing all the info and then frantically started editing it. Didn't expect such a quick reply!
Please take a look again at the updated info when you have the time. I am indeed using the generated (but slightly modified) dts.
I am using my own build of linux, bbl, and tried a custom build of busybox/initramfs.cpio as well as the prebuilt one.

Sounds like the issues I had with the irq of liteuart? Take a look at https://github.com/roryt12/qmtech_wukong_debian_on_litex_rocket . It hanged exactly at this point if I enable irq vs pooling?
Also try an alternative , ie the hvc0 driver, at my try with naxvriscv https://github.com/roryt12/qmtech_wukong_debian_on_litex_rocket seems to work fine (needs more options in kernel and in dts )

I haven't built anything using BBL in a very long time, having been discouraged from doing so by upstream who now favor
opensbi. The latter doesn't support emulating the FPU in M-mode, so it only works on boards that can accomodate at least one FPU-enabled Rocket core (85k ecp5, so no versa board; nexys* boards and better xilinx-equipped ones should still work).
I need to update the README to reflect this, but I'm also trying to get upstream LiteX to generate the full *.dts for a rocket-based system automatically, so I don't have to screw around with sample device tree files anymore :)
In the mean time, if you have a nexys_video, I'd like to propose that you try the following and let me know how it goes:
On the very latest upstream litex, add #define CONFIG_BIOS_NO_BOOT to the top of litex/soc/software/bios/main.c to inhibit it from automatically trying to boot from sdcard (you can still manually issue whatever boot command you want from the LiteX bios prompt). Then, build for the nexys_video:
litex-boards/litex_boards/targets/digilent_nexys_video.py --build \
    --cpu-type rocket --cpu-variant full --cpu-num-cores 2 --cpu-mem-width 2 --sys-clk-freq 50e6 \
    --with-ethernet --with-sdcard \
    --with-sata --sata-gen 1 --with-sata-pll-refclk \
    --csr-csv ./csr.csv

It's OK if you don't have a SATA adapter, but building it in anyway will make the MMIO registers line up properly with the DTS sample I'm about to link you to :)
Build the litex-rebase branch of the litex-hub kernel tree:
make clean
make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu-  litex_rocket_defconfig
make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j8

This gets you an arch/riscv/boot/Image kernel file.
Unpack nexys_video_binaries.zip. There will be a copy of Image already in there, pre-built. Feel free to use it or ignore it if you built your own. There's also a satatest4imafdc.dts sample in there. Compile it with:
dtc -O dtb satatest4imafdc.dts -o satatest4imafdc.dtb

Then build fw_jump.bin from source (or use the included one), like so:
make CROSS_COMPILE=riscv64-unknown-linux-gnu- PLATFORM=generic \
    FW_FDT_PATH=~/...path/to/.../satatest2imafdcbkph.dtb FW_JUMP_FDT_ADDR=0x82400000

Use the included initrd_bb (which should not be significantly different from previous sets of instructions).
Place the included boot.json, initrd_bb, Image, and fw_jump.bin into a tftp server directory (or on your FAT formatted sdcard), and issue the appropriate boot command (netboot or sdcardboot) from the LiteX bios.
LMK if this works for you (it does for me, and it's how things will be done from now on -- no more BBL).
All of this is also perfectly capable to boot e.g. Fedora (with an appropriately modified DTS and some doctoring of the official raw image to get it installed to the sdcard :) ).
LMK how it goes -- good luck!

note the edited --cpu-variant linux --cpu-num-cores 4 --cpu-mem-width 2 command line. If you go for full (now with [H]ypervisor support), there's only room for 2 such cores, and I gave you the wrong DTS for that :)

final edit: use --cpu-type rocket --cpu-variant full --cpu-num-cores 2 to get H support, and be able to use the enclosed binary opensbi blob (updated the source DTS to reflect the two larger h-capable full cores vs. the previous 4 lighter linux ones). The updated/edited commend containing build instructions is now correct and should reference the correct zip file.


feat: add icon component

icon component

Coverage decreased (-13.7%) to 56.104% when pulling 6138473d5057209aa674c07e7b70964e940efdf0 on NancyZhuJY:dev into 8134b4b597e4d00844836871c0be0eb1e7785d14 on ZhonganTechENG:dev.


Release 1.4

Is your enhancement related to a problem? Please describe
We should release 1.4.
Describe the solution you'd like
Do the 1.4 release and publish to the catalog.
Describe alternatives you've considered
No response
Additional context
No response

Complete.