com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnectionListener onFailure MqttException (0) - java.net.SocketTimeoutException: connect timed out

mvn exec:java -pl aws-iot-device-sdk-java-samples -Dexec.mainClass="com.amazonaws.services.iot.client.sample.pubSub.PublishSubscribeSample" -Dexec.args="-clientEndpoint a3b3bee1v25lqs.iot.us-west-2.amazonaws.com -clientId sdk-java -certificateFile ../caokun.cert.pem -privateKeyFile ../caokun.private.key"
[INFO] Scanning for projects...
[INFO] Inspecting build with total of 1 modules...
[INFO] Installing Nexus Staging features:
[INFO]   ... total of 1 executions of maven-deploy-plugin replaced with nexus-staging-maven-plugin
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building aws-iot-device-sdk-java-samples 1.1.0
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- exec-maven-plugin:1.5.0:java (default-cli) @ aws-iot-device-sdk-java-samples ---
Dec 19, 2016 8:07:25 PM com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnectionListener onFailure
WARNING: Connect request failure
MqttException (0) - java.net.SocketTimeoutException: connect timed out
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:664)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:86)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:650)
... 1 more
Dec 19, 2016 8:07:25 PM com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFO: Connection temporarily lost
Dec 19, 2016 8:07:25 PM com.amazonaws.services.iot.client.core.AbstractAwsIotClient onConnectionFailure
INFO: Client connection lost: sdk-java
Dec 19, 2016 8:07:28 PM com.amazonaws.services.iot.client.core.AwsIotConnection$1 run
INFO: Connection is being retried
Dec 19, 2016 8:08:28 PM com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnectionListener onFailure
WARNING: Connect request failure
MqttException (0) - java.net.SocketTimeoutException: connect timed out
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:664)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:86)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:650)
... 1 more
Dec 19, 2016 8:08:28 PM com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFO: Connection temporarily lost
Dec 19, 2016 8:08:28 PM com.amazonaws.services.iot.client.core.AbstractAwsIotClient onConnectionFailure
INFO: Client connection lost: sdk-java
Dec 19, 2016 8:08:34 PM com.amazonaws.services.iot.client.core.AwsIotConnection$1 run
INFO: Connection is being retried
Dec 19, 2016 8:09:34 PM com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnectionListener onFailure
WARNING: Connect request failure
MqttException (0) - java.net.SocketTimeoutException: connect timed out
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:664)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:86)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:650)
... 1 more
Dec 19, 2016 8:09:34 PM com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFO: Connection temporarily lost
Dec 19, 2016 8:09:34 PM com.amazonaws.services.iot.client.core.AbstractAwsIotClient onConnectionFailure
INFO: Client connection lost: sdk-java
Dec 19, 2016 8:09:46 PM com.amazonaws.services.iot.client.core.AwsIotConnection$1 run
INFO: Connection is being retried
Dec 19, 2016 8:10:48 PM com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnectionListener onFailure
WARNING: Connect request failure
MqttException (0) - java.net.SocketTimeoutException: connect timed out
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:664)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:86)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:650)
... 1 more
Dec 19, 2016 8:10:48 PM com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFO: Connection temporarily lost
Dec 19, 2016 8:10:48 PM com.amazonaws.services.iot.client.core.AbstractAwsIotClient onConnectionFailure
INFO: Client connection lost: sdk-java
Dec 19, 2016 8:11:12 PM com.amazonaws.services.iot.client.core.AwsIotConnection$1 run
INFO: Connection is being retried
Dec 19, 2016 8:12:12 PM com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnectionListener onFailure
WARNING: Connect request failure
MqttException (0) - java.net.SocketTimeoutException: connect timed out
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:664)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:86)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:650)
... 1 more
Dec 19, 2016 8:12:12 PM com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFO: Connection temporarily lost
Dec 19, 2016 8:12:12 PM com.amazonaws.services.iot.client.core.AbstractAwsIotClient onConnectionFailure
INFO: Client connection lost: sdk-java
Dec 19, 2016 8:12:42 PM com.amazonaws.services.iot.client.core.AwsIotConnection$1 run
INFO: Connection is being retried
Dec 19, 2016 8:13:42 PM com.amazonaws.services.iot.client.mqtt.AwsIotMqttConnectionListener onFailure
WARNING: Connect request failure
MqttException (0) - java.net.SocketTimeoutException: connect timed out
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:664)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:70)
at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:86)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:650)
... 1 more
Dec 19, 2016 8:13:42 PM com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFO: Connection temporarily lost
Dec 19, 2016 8:13:42 PM com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFO: Connection retry cancelled or exceeded maximum retries
[WARNING]
Dec 19, 2016 8:13:42 PM com.amazonaws.services.iot.client.core.AbstractAwsIotClient onConnectionClosed
INFO: Client connection closed: sdk-java
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:294)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.amazonaws.services.iot.client.AWSIotException
at com.amazonaws.services.iot.client.core.AwsIotCompletion.get(AwsIotCompletion.java:213)
at com.amazonaws.services.iot.client.core.AbstractAwsIotClient.connect(AbstractAwsIotClient.java:112)
at com.amazonaws.services.iot.client.AWSIotMqttClient.connect(AWSIotMqttClient.java:501)
at com.amazonaws.services.iot.client.core.AbstractAwsIotClient.connect(AbstractAwsIotClient.java:93)
at com.amazonaws.services.iot.client.AWSIotMqttClient.connect(AWSIotMqttClient.java:463)
at com.amazonaws.services.iot.client.sample.pubSub.PublishSubscribeSample.main(PublishSubscribeSample.java:137)
... 6 more
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:21 min
[INFO] Finished at: 2016-12-19T20:13:42+08:00
[INFO] Final Memory: 17M/193M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.5.0:java (default-cli) on project aws-iot-device-sdk-java-samples: An exception occured while executing the Java class. null: InvocationTargetException: AWSIotException -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

in my AWS IoT consol,there is also a notification:
Dec 19, 2016 8:11:29 PM +0800
Mqtt connection lost. Reconnect. Error code: 7. AMQJS0007E Socket error:undefined.
Anyone can help me ?
thanks a  lot

Hi @kuncao ,
Thank you very much for using AWS IoT Java SDK!
From the error message you listed, I am assuming you are using the SDK client and IoT Console client at the same time. Can you confirm on the client ids you are using to connect these two clients to AWS IoT? Connecting with the same client id in different MQTT connections is not allowed. The next connection will kick out the first connection.
Thanks,
Liusu

@liuszeng
Thanks you for Help
java-sdk
mvn parameter
Dexec.args="-clientEndpoint a3b3bee1v25lqs.iot.us-west-2.amazonaws.com -clientId sdk-java -certificateFile ../caokun.cert.pem -privateKeyFile ../caokun.private.key"
how to check the clientid in IoT Console?

@liuszeng
When stop  trying  connect with java sdk.
In IoT Console.
when run test ,the following message appear:
Connecting to Device Gateway......
Mqtt connection lost. Reconnect.
this message will occur many times

@liuszeng
http://docs.aws.amazon.com/iot/latest/developerguide/diagnosing-connectivity-issues.html
from above url,it seem to need "Add the AWS IoT CA certificate to your client’s trust store."
Is this done automatically or need to add by manul?
thanks

Hello @kuncao,
It seems like you are seeing two issues. The first is using the Java SDK, the second is an error received from the AWS IoT Console.
For the first, it looks like you are receiving a socket timeout. Can you confirm you are able to connect to your endpoint outside of using the Java SDK? This can be done by trying to telnet to the endpoint, port 8883: telnet <ENDPOINT> 8883 where your endpoint is of the form telnet abcdef.iot.us-east-1.amazonaws.com. Note, your region in the previous example may differ.
Another test can be done using OpenSSL's TLS client: openssl s_client -connect <customer endpoint>:8883 -tls1_2 -CAfile <path to Root CA cert> -cert <Path to device cert> -key <Path to device private key>.
For the second, when does this error appear? Does it appear on first connect? Are you able to consistently connect and then receive this error after a certain amount of time? Is an action required (such as switching pages) required to see the error?
Thank you again for reaching out to us regarding your issues and for using AWS IoT.
John

@johnrotach
Thanks johnrotach.
mvn exec:java -pl aws-iot-device-sdk-java-samples -Dexec.mainClass="com.amazonaws.services.iot.client.sample.pubSub.PublishSubscribeSample" -Dexec.args="-clientEndpoint a3b3bee1v25lqs.iot.us-west-2.amazonaws.com -clientId sdk-java -certificateFile ../caokun.cert.pem -privateKeyFile ../caokun.private.key"
so
szv1000082894:~ # telnet  a3b3bee1v25lqs.iot.us-west-2.amazonaws.com 8883
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection timed out
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection timed out
Trying <IP_ADDRESS>...

@liuszeng
when run test ,MQTT client can not connect the device gateway
for information security reason,I can't upload the file to the issue.
I have send the email to<EMAIL_ADDRESS>Please check your email.
You can also share the doc with  johnrotach.
thanks all.

szv1000082894:/home/awskey # openssl s_client -connect a3b3bee1v25lqs.iot.us-west-2.amazonaws.com:443 -servername a3b3bee1v25lqs.iot.us-west-2.amazonaws.com -showcerts | openssl x509 -text -noout
connect: Connection timed out
connect:errno=110
unable to load certificate
4972:error:0906D06C:PEM routines:PEM_read_bio:no start line:pem_lib.c:650:Expecting: TRUSTED CERTIFICATE

my endpoint seem to be ok
Custom endpoint
This is your custom endpoint that allows you to connect to AWS IoT. Each of your Things has a REST API available at this endpoint. This is also an important property to insert when using an MQTT client or the AWS IoT Device SDK.
Status
ACTIVE
Your endpoint is provisioned and ready to use. You can now start to publish and subscribe to topics.
Endpoint
a3b3bee1v25lqs.iot.us-west-2.amazonaws.com

Hello @kuncao,
From the above output, it looks like you are unable to connect to the endpoint. In contrast, when I run this same command I receive this:
$> openssl s_client -connect a3b3bee1v25lqs.iot.us-west-2.amazonaws.com:443 -CAfile /path/to/my/rootCA.pem -cert /path/to/my/cert.pem -key /path/to/my/key.pem
CONNECTED(00000003)
depth=2 C = US, O = "VeriSign, Inc.", OU = VeriSign Trust Network, OU = "(c) 2006 VeriSign, Inc. - For authorized use only", CN = VeriSign Class 3 Public Primary Certification Authority - G5
verify return:1
depth=1 C = US, O = Symantec Corporation, OU = Symantec Trust Network, CN = Symantec Class 3 Secure Server CA - G4
verify return:1
depth=0 C = US, ST = Washington, L = Seattle, O = "Amazon.com, Inc.", CN = *.iot.us-west-2.amazonaws.com
verify return:1
---
Certificate chain
 0 s:/C=US/ST=Washington/L=Seattle/O=Amazon.com, Inc./CN=*.iot.us-west-2.amazonaws.com
   i:/C=US/O=Symantec Corporation/OU=Symantec Trust Network/CN=Symantec Class 3 Secure Server CA - G4
 1 s:/C=US/O=Symantec Corporation/OU=Symantec Trust Network/CN=Symantec Class 3 Secure Server CA - G4
   i:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=(c) 2006 VeriSign, Inc. - For authorized use only/CN=VeriSign Class 3 Public Primary Certification Authority - G5
---
Server certificate
-----BEGIN CERTIFICATE-----
...
<cert removed for brevity>
...
-----END CERTIFICATE-----
subject=/C=US/ST=Washington/L=Seattle/O=Amazon.com, Inc./CN=*.iot.us-west-2.amazonaws.com
issuer=/C=US/O=Symantec Corporation/OU=Symantec Trust Network/CN=Symantec Class 3 Secure Server CA - G4
---
No client certificate CA names sent
Peer signing digest: SHA512
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3390 bytes and written 434 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---

Notice the CONNECTED statement in my output.
A connection timeout usually points to a networking issue and not an issue with certificates or the AWS IoT service.
What do you receive if you paste the endpoint URL (https://a3b3bee1v25lqs.iot.us-west-2.amazonaws.com) into a web browser or attempt to do a request with curl curl https://a3b3bee1v25lqs.iot.us-west-2.amazonaws.com? You should receive a Missing Authentication Token error rather than a connection timeout.
John

@johnrotach
When I paste the endpoint URL (https://a3b3bee1v25lqs.iot.us-west-2.amazonaws.com) into a web browser
I recieve  the following output
{"message":"Missing Authentication Token","traceId":"87579c24-deba-7ac5-abcc-2b752987de8d"}
can you help to paste the  output of the command
telnet a3b3bee1v25lqs.iot.us-west-2.amazonaws.com 8883
thanks a lot

Sure. I see:
$> telnet a3b3bee1v25lqs.iot.us-west-2.amazonaws.com 8883
Trying <IP_ADDRESS>...
Connected to dualstack.iotmoonraker-u-elb-1w8qnw1336zq-1186348092.us-west-2.elb.amazonaws.com.
Escape character is '^]'.
^]
telnet> close
Connection closed.
$>

What do you receive?

szv1000082894:~ # telnet a3b3bee1v25lqs.iot.us-west-2.amazonaws.com 8883
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection timed out
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection timed out
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection timed out
Trying 2620:108:700f::3694:ec5e...
telnet: connect to address 2620:108:700f::3694:ec5e: Network is unreachable
Trying 2620:108:700f::3423:5490...
telnet: connect to address 2620:108:700f::3423:5490: Network is unreachable
Trying 2620:108:700f::23a0:2f9f...
telnet: connect to address 2620:108:700f::23a0:2f9f: Network is unreachable

This could be a port blocking issue with port 8883 on your network. Do you receive the same error if you attempt the telnet command on port 443?
e.g. telnet a3b3bee1v25lqs.iot.us-west-2.amazonaws.com 443

szv1000082894:~ # telnet a3b3bee1v25lqs.iot.us-west-2.amazonaws.com 443
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection timed out
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection timed out
Trying <IP_ADDRESS>...
telnet: connect to address <IP_ADDRESS>: Connection timed out
Trying 2620:108:700f::3423:5490...
telnet: connect to address 2620:108:700f::3423:5490: Network is unreachable
Trying 2620:108:700f::3694:ec5e...
telnet: connect to address 2620:108:700f::3694:ec5e: Network is unreachable
Trying 2620:108:700f::23a0:2f9f...
telnet: connect to address 2620:108:700f::23a0:2f9f: Network is unreachable

https://a3b3bee1v25lqs.iot.us-west-2.amazonaws.com

telnet a3b3bee1v25lqs.iot.us-west-2.amazonaws.com 8883

Hi @kuncao,
The Missing Authentication Token message is expected. A request to that endpoint needs to be authenticated using AWS Signature V4. This is typically handled for you automatically when using the AWS CLI or an AWS SDK but not on a raw curl request such as this. The point of this test was to see if you could successfully make a TCP connection (which you did since you received this message back from AWS).
Given this error (and the lack of a connection in the other cases) It appears that you can successfully establish a connection from your personal computer but not from your server. It appears all network traffic is not making it to that endpoint, regardless of the protocol. This may be a network issue from China. Are you able to access any other AWS services from your server?
John

@johnrotach @liuszeng
Merry Christmas

@johnrotach
Are you able to access any other AWS services from your server?
At current , not try.
But  I put a small file in my s3 bucket with my chrome browser.

Hi,
i am following the tutorial https://github.com/aws/aws-iot-device-sdk-java/blob/master/README.md to connect from Java to IoT through MQTT over WebSocket. I am using the simple main:
	AWSIotMqttClient client = new AWSIotMqttClient(clientEndpoint, clientId, awsAccessKeyId, awsSecretAccessKey);
		client.connect();

But i get error:
WARNING: Connect request failure
MqttException (0) - java.io.IOException: WebSocket Response header: Incorrect connection header
....
I am using my AWS credential. My user is also admin and i have policy for full access to IoT:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "iot:",
"Resource": ""
}
]
}
can you pls help?
thanks lot.

Any updates on this? I have the same problem.
See stacktrace below:
Unable to connect to server (32103) - java.net.ConnectException: Connection timed out: connect (local port 57998 to addr ess 0:0:0:0:0:0:0:0, remote port 8883 to address <IP_ADDRESS> (ec2-35-166-74-244.us-west-2.compute.amazonaws.com))         at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:90)         at org.eclipse.paho.client.mqttv3.internal.SSLNetworkModule.start(SSLNetworkModule.java:92)         at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:676)         at java.lang.Thread.run(Thread.java:805) Caused by: java.net.ConnectException: Connection timed out: connect (local port 57998 to address 0:0:0:0:0:0:0:0, remote  port 8883 to address <IP_ADDRESS> (ec2-35-166-74-244.us-west-2.compute.amazonaws.com))         at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)         at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:86)         at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)         at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)         at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:173)         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)         at java.net.Socket.connect(Socket.java:899)         at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)         at org.eclipse.paho.client.mqttv3.internal.TCPNetworkModule.start(TCPNetworkModule.java:81)         ... 3 more

sorry for late update
my colleague  oversea can telnet  telnet a3b3bee1v25lqs.iot.us-west-2.amazonaws.com 8883
but I can not telnet in China.
May be this is forbidden in China


Add docs on AcroForms with recursive field structure

Split of from #497  by @typhoon71
Now that the AcroForm howto is merged, I suppose I can consider some other cases.
I waited after the PR got merged because it was becaming difficult for me to keep focused.
AcroForms with recursive fields structure. I did prepare the code to process those, but I'd like to talk a bit on how to format the output, which in some cases can be... funny. Would it be better to discuss it here or to prepare a howto + PR and then discuss on that?

I'll work on this after #497 is done.

It seems I won't be able to work on this in the foreseeable future, stuff happened.
One thing I could do is post the code I prepared, which was working (but is not commented).

It seems I won't be able to work on this in the foreseeable future, stuff happened.
One thing I could do is post the code I prepared, which was working (but is not commented).

Finally found some time!
As promised, I'm posting the code that I planned to use for the docs on recursive AcroForms.
As is , it extracts interactive recursive forms into nested lists of tuples (name, value) and pretty prints the result.

from pdfminer.pdfparser import PDFParser
from pdfminer.pdfdocument import PDFDocument
from pdfminer.pdftypes import resolve1
from pdfminer.psparser import PSLiteral, PSKeyword
from pdfminer.utils import decode_text

import pprint  # only to pretty print output, not needed to decode forms

def decode_value(value):
    if isinstance(value, (PSLiteral, PSKeyword)):
        value = value.name
    if isinstance(value, bytes):
        value = decode_text(value)
    return value

def get_field(field):

    name = field.get('T')
    if name is not None:
        name = decode_text(name)

    forms = field.get('Kids')
    if forms:
        values = [get_field(resolve1(form)) for form in forms]
        return name, values

    values = field.get('V')
    values = resolve1(values)

    if isinstance(values, list):
        values = [decode_value(v) for v in values]
    else:
        values = decode_value(values)

    return name, values

fp = r'FR_Y-1520151231_f.pdf'  # https://www.ffiec.gov/npw/FinancialReport/FRY15Reports

parser = PDFParser(open(fp, 'rb'))
doc = PDFDocument(parser)
res = resolve1(doc.catalog)

if 'AcroForm' in res:
    data = [get_field(field=resolve1(f)) for f in resolve1(res['AcroForm'])['Fields']]

    print()

    pp = pprint.PrettyPrinter(indent=1, width=160)
    pp.pprint(data)

The output still needs to be converted to dict {key: value}, as there are some special cases to consider before converting the nested pairs; the forms can have some "funny" cases, ie: [(None, None), (None, None), (None, None)]
This snippet works, but it's not commented (which was the reason I started working on it), but I'm pretty sure it's easy enough to complete it if willing, it's not much different from my previous work.
And it decodes the pdf samples fine (as you can see this sample uses one of them).
Hope it can be of help.


368 pdf storage

Codecov Report

Merging #2414 (cd14fc9) into development (8b1d51d) will decrease coverage by 29.28%.
The diff coverage is n/a.

:exclamation: Current head cd14fc9 differs from pull request most recent head 8c6e954. Consider uploading reports for the commit 8c6e954 to get more accurate results

@@               Coverage Diff                @@
##           development    #2414       +/-   ##
================================================
- Coverage        87.64%   58.35%   -29.29%
================================================
  Files             1807     1289      -518
  Lines            62583    33052    -29531
================================================
- Hits             54853    19289    -35564
- Misses            7730    13763     +6033

Impacted Files
Coverage Δ

spec/support/concerns/random_token_methods.rb
2.63% <0.00%> (-97.37%)
:arrow_down:

spec/support/concerns/request/api.rb
11.11% <0.00%> (-88.89%)
:arrow_down:

app/models/identifier/global/issn.rb
14.28% <0.00%> (-85.72%)
:arrow_down:

app/models/identifier/global/isbn.rb
8.33% <0.00%> (-85.42%)
:arrow_down:

lib/dwca/generator.rb
20.00% <0.00%> (-80.00%)
:arrow_down:

app/models/protonym/becomes.rb
16.43% <0.00%> (-79.46%)
:arrow_down:

app/models/identifier/global/uri.rb
21.42% <0.00%> (-78.58%)
:arrow_down:

lib/catalog/description_from_observation_matrix.rb
13.22% <0.00%> (-78.10%)
:arrow_down:

app/models/identifier/global/orcid.rb
22.22% <0.00%> (-77.78%)
:arrow_down:

app/controllers/concerns/token_authentication.rb
22.58% <0.00%> (-77.42%)
:arrow_down:

... and 1070 more

Continue to review full report at Codecov.

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


feat: adding sonatype central support

Description
This PR adds support for the new Sonatype Central publishing api, documented here and here. To use, ensure that your environment variables contain the appropriate credentials and add the following to your library build.sbt:
import xerial.sbt.Sonatype.sonatypeCentralHost

ThisBuild / sonatypeCredentialHost := sonatypeCentralHost

New Dependencies
Adding these was necessary, since the airframe client does not support multipart uploads. Perhaps it is possible to custom-wire the airframe client so that it does this, but I was not successful in an initial try. There is, in any case, no airframe documentation about multipart uploads, nor could I find any support in the code base. The following dependencies made implementation very easy. I have added the "effect-free" versions, since the current sbt-sonatype codebase does not use any effects, though use of effects would make certain things like resource management easier.
"com.softwaremill.sttp.client4" %% "core" % "<version>",
"com.softwaremill.sttp.client4" %% "circe" % v"<version>",
"com.softwaremill.sttp.client4" %% "slf4j-backend" % "<version>",

New SBT Keys
Users can customize Sonatype Central deployment names like so:
sonatypeCentralDeploymentName := DeploymentName.fromRawString("<custom-deployment-name>")

Additional Notes

This initial version hard-codes the bundle upload to a "user-managed" deployment - i.e. after the bundle is uploaded and verified, users will need to manually press "publish" in order for it to be published to Maven Central. This functionality is ideal for a release candidate version of sbt-sonatype, as it gives users the ability to verify that everything is working before publishing. A final version can either hard-code the deployment to "automatic" or introduce a new sbt key so that users can specify this themselves (preferred).

Sonatype Central currently does not support publishing snapshots. The documentation says that an uploaded (but not published) deployment can be tested in production by referring to the deployment id, but I have not verified this.

I deployed a library to Sonatype Central using these new changes and it worked with no issues.

@xerial , before finalizing and adding tests, could I get an overall thumbs-up on this implementation? Would like to make sure that there's nothing controversial here, otherwise time spent on testing could be wasted effort.

Formatting issues are fixed - all workflows should now succeed. If there are no issues with the overall approach, I'll add some tests and finalize.

@Andrapyre First of all, thanks for preparing this PR. It gives us a head start. I also could learn a lot about the new Sonatype API.
Major and unknowns:

Can we merge two similar keys, sonatypeCentralDeploymentName (how this will be used in the new API?), sonatypeSessionName? sonatypeSessionName is used for creating a unique session in the legacy style, so that we can resume the release process even after network failures.

Or make it just a sonatypeDeploymentName (String). I believe there is no need to expose the internal DeploymentName model class to users, and central will eventually be the default repository, we can remove Central from the key name.

It depends on the plan of Sonatype for migrating legacy API users to the new one, but if the process can be totally different, instead of merging sonatypeBundleRelease, it would be better to create new separate commands like sonatypeRelease (for automatic deployment) and sonatypeUpload (for user-managerd deployment), so that sonatypeBundleRelease can call sonatypeRelease internally and the user can choose what they need.

Good

Creating SonatypeCentralClient extracting some common code look good.

Minor, but can be painful for me in the long run.
Note: You don't need to tackle the items mentioned here, as I will be able to manage them.

Coding style differences, especially using Either for error handling. I understand the benefit but I've also observed it's been confusing people who are relatively new to Scala's ecosystem.
　- Please note that I've been maintaining this plugin for almost 10 years. While using sttp is acceptable, introducing circe might not be the best choice, especially considering that the main creator has left the Scala world. If you require a JSON parser, I recommend using airframe-codec, which is already used within airframe-http for parsing JSON responses.
If airframe-http supports multi-part upload, we can use the same retry mechanism without introducing sttp, circle, Either, which is beneficial in the long run. I'll think about supporting multi-part upload in airframe-http.

After receiving your responses, I can suggest further adjustments to the PR, or I can make these changes myself to save your time, depending on your preference.

@xerial , thanks for the quick response. Several points:

The deployment name is purely cosmetic in Sonatype Central, so that the user can meaningfully distinguish in the ui between different deployments. Multiple deployments can even have the same name and if no name is provided then they will automatically be assigned the filename (in this case bundle.zip as the deployment name. To avoid the scenario where the user logs in and sees 100 "bundle.zip" deployments with no way to figure what is what, I've set the deployment name to "<org_name>.<artifact_id>-", but left it open to users to customize, hence why the class is exposed. Each deployment comes with a deployment id and that would probably be the equivalent of the session name (though I don't know, since I haven't worked with the old api). In any case, this implementation gives the deployment id its own class and it is not exposed to the user to customize, since it's generated by Sonatype Central.

Downstream plugins (such as typelevel sonatype and sbt-ci-release) use the sonatypeBundleRelease command. To give users the freedom to specify whether they want their deployment to be managed or automatic without needing to make downsteam changes, I would introduce a new key, `isSonatypeReleaseAutomatic" and have sonatypeBundleRelease pass the value down accordingly, while keeping the rest of the functionality as is in this PR.

I will make a best effort attempt to migrate to airframe codec. It should be pretty easy. If it gets time-consuming or I run into larger issues, I will leave as-is or pick a different framework, if you prefer (jsoniter-scala is very fast/the fastest and well maintained - I've had a very good experience with it in other projects). I agree in general that fewer dependencies are better and would have preferred to introduce none with this feature.

I appreciate that Scala can be difficult to read and work with, especially for new beginners. In my experience though, that generally applies to use of effects - I haven't seen anyone complain about simple types like Either or Option. Are you referring to my utils package with the leftMap implementation? I can add a few comments so that it's clear what those are practically doing. Otherwise, I find using Either to wrap exceptions far less messy than putting try/catch everywhere and would prefer not to change it if possible.

Let me know your thoughts. I'll proceed in any case with revising the json parsing away from circe.

@Andrapyre The internal implementation can be changed later, so merging this first works. You need to address only two points addressed as major here https://github.com/xerial/sbt-sonatype/pull/474#issuecomment-1967331705

sonatypeDeploymentName : String.  // Do not use DeploymentName object here for setting this value
sonatypeBundleRelease

Call sonatypeRelease (automated release at Central) internally
sonatypeUpload (for manual release)

I'm against changing the behavior of sonatypeBundleRelease with an option (e.g., isSonatypeReleaseAutomatic ) because the command is supposed to complete all of the deployment steps at once. These command names and behavior will be difficult to change once the users start depending on the behavior.

Understood - I'll make said changes and revert.

Alright. Several changes here:

The sonatypeDeploymentName setting is now a String type.
I migrated to zio-json which has a similar structure to circe and has better support/maintenance long-term. I didn't see airframe codec or jsoniter-scala easily decoding the deployment stage enum we have, something that is very simple with both circe and zio-json.
Two new commands - sonatypeCentralRelease (automatic) and sonatypeCentralUpload (user-managed) sonatypeBundleRelease calls the same function as sonatypeCentralRelease if the credential host is Sonatype Central.

I will add some tests (mainly for the Sonatype Central client) and then request a final review.

Apologies for the delay. I'll be looking into this next week. And with Sonatype's recent announcement about account migration, it looks like I'll also need to get my repositories set up there.

All good - I had a delay myself due to other commitments taking priority. I did manage to test automatic deployments today, as well as a cross-versioned deployment to Sonatype Central, and everything worked as expected. I will forego tests for now for the sake of immediately merging this. The other client doesn't have testing as is and it seems that sttp might be ripped out in the near future and then all tests would need to be rewritten anyway. On that subject, if the plan is to keep sttp, I'm happy to add tests in a follow-up PR.
I still need to add some documentation and push all changes.

Documentation is added. Happy to receive a review now.

@xerial , I have moved all of the basic client operations into a client library here, where I will maintain and test it long term. I also updated some of the retry logic to immediately fail when it encounters user errors (e.g. the user specified wrong credentials, so we shouldn't retry for the next 30 minutes, etc.).
Could we get a 4.0.0-RC1 out in the next few days, so that the community can test this? Main question mark for me is how very large, cross-built projects with a lot of modules will be affected and whether we need to build out any extra support for such projects. With Sonatype Central, users can only upload one large bundle. It looks like the legacy oss environment supported parallel processing of some kind vis-a-vis this comment here? The same functionality isn't available in Central. Not sure about the potential breakage there.

@xerial Are there any blockers before this can be merged and an RC can be published? It would be amazing to be able to use sbt-sonatype with Sonatype Central.
BTW, thanks for maintaining this library :heart:

@KacperFKorban , @xerial expressed concerns offline that there was too much overlap between legacy and newer functionality, when many of the features are quite different or mean totally different things. For instance, there are no staging repos, host names, snapshot repos, or profiles, etc. in the new publishing api. Nevertheless, working the new central portal api into this plugin requires us to set values for all or most of these, which makes the code harder to reason about and could lead to potential bugs down the road.
When I implemented this for mill the team requested that this functionality be kept in a completely separate lib, though I also initially integrated it into their existing sonatype publishing lib. I've decided to take a similar route here and put this into a separate plugin, which I will maintain here. I'm having some issues deploying it - https://github.com/lumidion/sbt-sonatype-central/issues/1. When these are resolved, I will deploy the plugin, close this pull request, and request that the corresponding issue be closed as well.

Hi folks. As I don't have much time to review or fix it, I'll ship it now and fix it (or review it) later.

Released 3.11.0 https://github.com/xerial/sbt-sonatype/releases/tag/v3.11.0


AttributeError: 'VCRRequestsHTTPSConnectionfixtures/cassettes/test_' object has no attribute 'ssl_context' in with urllib3/python 2.7.12

This is working for urllib3 1.16 but failed for 1.17
vcrpy version: 1.10.0 and 1.10.2
self = <vcr.patch.VCRRequestsHTTPSConnectionfixtures/cassettes/test_dowload_wavefile object at 0x104375d90>
key_file = None, cert_file = None, cert_reqs = None, ca_certs = None
assert_hostname = None, assert_fingerprint = None, ca_cert_dir = None

    def set_cert(self, key_file=None, cert_file=None,
                 cert_reqs=None, ca_certs=None,
                 assert_hostname=None, assert_fingerprint=None,
                 ca_cert_dir=None):
        """
            This method should only be called once, before the connection is used.
            """
        # If cert_reqs is not provided, we can try to guess. If the user gave
        # us a cert database, we assume they want to use it: otherwise, if
        # they gave us an SSL Context object we should use whatever is set for
        # it.
        if cert_reqs is None:
            if ca_certs or ca_cert_dir:
                cert_reqs = 'CERT_REQUIRED'
>           elif self.ssl_context is not None:
E           AttributeError: 'VCRRequestsHTTPSConnectionfixtures/cassettes/test_' object has no attribute 'ssl_context'

@number5 sorry this got dropped for the last 2.5 years.
If you'd still like to put this in, could you rebase with master and add a test case that capture this?
Thanks.

Sorry to ask again but could you rebase against the latest master when you get the chance. Looks like Travis was run against an environment configuration that doesn't match tox

the tests looks good


MPI_Get_version not implemented

Original issue: https://charm.cs.illinois.edu/redmine/issues/284

IMB_MPT1 makes a call to this function, then ignores the result.  I commented that out as a workaround, but we should support this function.

Original date: 2013-10-25 21:19:09

Done! Tested with tiny C and f90 codes.

Original date: 2013-10-29 16:22:26

d:\cygwin\home\gengbin\autobuild\multicore\charm\multicore-win32\tmp\libs\ck-libs\ampi\ampi.c(5466) : error C4716: 'AMPI_Get_version' : must return a value

Return success, please, like the spec says.

Original date: 2013-10-29 20:27:52

Fixed the return value. Why don't we utilize MPI_SUCCESS and just return 0 instead?


Automated Package Upgrade

:tada: This PR is included in version 2.2.293 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add Egress description more clearly

Egress value is emit per minute per Streaming Endpoint services. It's not all of total Streaming Endpoint services.

@dahatake : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Update FAQ and Landpage

Fixes #2729
Also fixes #2787

We should also update the text about Print Friendly mode:
https://www.reddit.com/r/homebrewery/comments/14v4cil/printfriendly_help/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=2

@5e-Cleric I have rewritten the section you were asking about.
I also noticed that none of my other comments were applied. Did you have any specific reason not to accept those suggestions?

I did accept those changes in my local branch, just didnt commit them, will do so right now

I did accept those changes in my local branch, just didnt commit them, will do so right now

Gotcha. Just FYI, you can automatically commit a change straight from GitHub by clicking this button:

Three commits for the same thing seemed excessive anyway.
github still marks this as still waiting to fix the review lol

Merging now. Thanks @5e-Cleric !


Example for the kudu extension is needed

How do we programmatically add a restriction to the  <sitename>.scm.azurewebsite.net  tab?   If feels even more important to restrict that site than the main site.

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

ID: d90bbf62-44f9-30a6-d6ea-bbf776f6efc5
Version Independent ID: b3961eac-6c70-b345-f48c-e4c0ec67059c
Content: Restrict client IPs - Azure App Service
Content Source: articles/app-service/app-service-ip-restrictions.md
Service: app-service-web
GitHub Login: @ccompy
Microsoft Alias: ccompy

Hi @jfayatkim, thanks for the feedback! We are currently investigating and will update you shortly.

@jfayatkim The process is the same except the JSON snippet will look like the below example.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
"scmIpSecurityRestrictions": [
          {
            "ipAddress": "<IP_ADDRESS>/24",
            "action": "Allow",
            "tag": "Default",
            "priority": 300,
            "name": "No",
            "description": "Okay"
          }
        ],


Disable Variable Substitution

Is there any way to disable Variable substitution? (that is, to only do file transform)

@dotkiddo -- Gideon, thanks for your feedback; we appreciate it. To make sure we have all the information needed to triage your issue, please let us know which topic you’re referencing, or provide more context around your general task.


Err(Other(ClientImport("Runtime Ethereum block not found, rejecting!")))

Version: 0.9.12-3
OS: Ubuntu 20.04
I have run my new validator and in status I get errors (Err(Other(ClientImport("Runtime Ethereum block not found, rejecting!")))
Steps:

Login to server
pulls latest release tag (0.9.12-3) and sets it as var - LATEST_RELEASE=curl --silent "https://api.github.com/repos/digitalnativeinc/standard-substrate/releases/latest" | grep '"tag_name":' | sed -E 's/.*"([^"]+)".*/\1/'
downloads binary based on latest tag set - wget -O opportunity-standalone https://github.com/digitalnativeinc/standard-substrate/releases/download/$LATEST_RELEASE/opportunity-standalone-linux-x86_64
chmod +x ./opportunity-standalone
mv opportunity-standalone /usr/local/bin
touch /etc/systemd/system/opportunity-standalone.service
paste content into the file

copy everything line 12-28 inclusive
cat > /etc/systemd/system/opportunity-standalone.service << EOF
[Unit]
Description=Standard Validator
[Service]
ExecStart=/usr/local/bin/opportunity-standalone
--base-path
--chain opportunity
--port 30333
--name
--validator
Restart=always
RestartSec=120
[Install]
WantedBy=multi-user.target
EOF
8.systemctl daemon-reload
9. systemctl enable opportunity-standalone
10. systemctl start opportunity-standalone
11. systemctl status opportunity-standalone
Results:
Errors in console:
Dec 24 22:41:07 Standard opportunity-standalone[5435]: 2021-12-24 22:41:07 💤 Idle (0 peers), best: #0 (0x0250…4bce), finalized #0 (0x0250…4bce), ⬇ 5.4kiB/s ⬆ 6.1kiB/s
Dec 24 22:41:12 Standard opportunity-standalone[5435]: 2021-12-24 22:41:12 💤 Idle (0 peers), best: #0 (0x0250…4bce), finalized #0 (0x0250…4bce), ⬇ 0.5kiB/s ⬆ 0.9kiB/s
Dec 24 22:41:13 Standard opportunity-standalone[5435]: 2021-12-24 22:41:13 💔 Error importing block 0x22ac8aa3bd4844da1a0d1b5dca6e98f00ebea5080153686d0ef7be2b74dc228d: Err(Other(ClientImport("Runtime Ethereum block not found, rejecting!")))
Dec 24 22:41:13 Standard opportunity-standalone[5435]: 2021-12-24 22:41:13 💔 Error importing block 0x22ac8aa3bd4844da1a0d1b5dca6e98f00ebea5080153686d0ef7be2b74dc228d: Err(Other(ClientImport("Runtime Ethereum block not found, rejecting!")))

I have the same error with version 0.9.12-3.

@kamiloski88 @koburzasty This has been fixed in the latest release - 0.9.12-4, try purging/deleting the local database and syncing it, should be all working. Thanks! Once confirmed will close it.

@firke Yesterday I downloaded the source and compiled it - it worked.
Today, after returning home, I will check the new release.

Fixed with version 0.9.12-4


Add link to source on each part title

CALL FUNCTION 'RS_TOOL_ACCESS'
    EXPORTING
      operation           = 'SHOW'
      object_name         = i_object_name
      object_type         = i_object_type
    EXCEPTIONS
      not_executed        = 1
      invalid_object_type = 2
      OTHERS              = 3.```

Implemented in #36


Compiler error messages report wrong file path on Windows

Brief Issue Summary
Compiler error messages link to wrong file paths when the workspace path includes upper case characters under Windows. When I select a compiler error from the Problems view, an already opened file is opened a second time but with a lower-case path. This completely messes up the respective file when the source code is reformated as vscode supposedly does not assume a single file to be opened twice.
Expected:
Casing of the workspace path should be preserved by CMake Tools. So error messages will show the path with the correct case.
Apparent Behavior:
The workspace path is converted to lower case when CMake is called.
The issue can be reproduced by the following steps
On Windows:

Copy a cmake project to a path containing upper case letters
Introduce a compiler error to a source file in the project
Ensure the respective source file is still open
Compile with CMAKE: Build
Click on the error message in the Problems view
The file is opened a second time in VSCode.

CMake Tools Log
When the project is in the path: "C:\Code/UpperCaseIssue" cmake is called with a lower case path:
[vscode] Executing command: cmake --build c:/code/uppercaseissue/build --target all --config Debug -- -j 6

Platform and Versions

Operating System: Windows
VSCode Version: 1.20.1
CMake Tools Extension Version: 0.10.4
Compiler/Toolchain: Visual C++ 2015

Other Notes/Information
I guess the case should not be normalized, even on Windows operating systems (normalizePath in util.ts).

If you are building with VC++ 2015, the compiler is the culprit here.  I believe that most (if not all) VS projects turn on the /FC switch which results in full paths in the build output, but they are all lower-cased in the output.  Normally this shouldn't be a problem because the Windows file system is case insensitive, but VS Code treats these paths as unique.
So while some of the blame can be put on the compiler, this is actually a VS Code issue.  Issue https://github.com/microsoft/vscode/issues/12448 is where most of the discussion on this is happening.  I recommend you upvote that issue.


@xstate/test .getShortestPathPlans() doesn't run all event cases

Description

I've been experimenting with @xstate/test and trying to use it to test events that should be run with multiple cases.
Expected Result

Whether I use .getShortestPathPlans() or .getSimplePathPlans() all of the cases for each event would be taken into account.
Actual Result

If I use .getSimplePathPlans() all the event cases are used, as expected. If I use .getShortestPathPlans() only the first case is ever used.
Reproduction
https://codesandbox.io/s/blissful-wind-f75ux

Repro + Output
Repro Code
const { Machine: createMachine } = require("xstate");
const { createModel } = require("@xstate/test");

const machine = createMachine({
  id: "menu",
  initial: "booting",
  states: {
    booting: {
      on: {
        EVENT: "ready"
      }
    },

    ready: {}
  }
});

const model = createModel(machine).withEvents({
  EVENT: {
    exec: (test, ev) => console.log(ev),
    cases: [{ id: "one" }, { id: "two" }, { id: "three" }]
  }
});

const execute = async plans =>
  plans.forEach(plan => {
    plan.paths.forEach(async path => {
      await path.test({ ctx: "foo" });
    });
  });

(async function() {
  console.log("getSimplePathPlans()");
  await execute(model.getSimplePathPlans());

  console.log(".getShortestPathPlans()");
  await execute(model.getShortestPathPlans());
})();

Repro Output
getSimplePathPlans()
> Object {type: "EVENT", id: "one"}
> Object {type: "EVENT", id: "two"}
> Object {type: "EVENT", id: "three"}

.getShortestPathPlans()
> Object {type: "EVENT", id: "one"}

Additional context

<EMAIL_ADDRESS><EMAIL_ADDRESS>

As discussed on Gitter - this is as expected, because the events need to result in different states, and the reproduction always results in the same state, regardless of the event cases.


Generate Flutter Assets Paths Automatically

Maybe with: https://plugins.jetbrains.com/plugin/15427-flutterassetsgenerator
Edit: We won't use the above as it is a jetbrains only pluging, we should go with the one from the comment below: https://github.com/FlutterGen/flutter_gen

This one is a better approach as it works universally and not only for Jetbrains: https://github.com/FlutterGen/flutter_gen

Closed by: #1030


@electron-forge/maker-flatpak error after project setup

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Forge Version:

6.0.0-beta.51

Electron Version:

9.0.0

Operating System:

Ubuntu 20.04 x64

Last Known Working Electron Forge version:

Expected Behavior
maker-flatpak should successfully build the flatpak
Actual Behavior
maker-flatpak process fails with the following error:
An unhandled error has occurred inside Forge: An error occured while making for target: flatpak flatpak-builder failed with status code 1 Error: flatpak-builder failed with status code 1     at ChildProcess.<anonymous> (/home/denn-s/VSCodeProjects/my-app/node_modules/@malept/flatpak-bundler/index.js:68:16)     at ChildProcess.emit (events.js:315:20)     at ChildProcess.EventEmitter.emit (domain.js:485:12)     at maybeClose (internal/child_process.js:1051:16)     at Socket.<anonymous> (internal/child_process.js:442:11)     at Socket.emit (events.js:315:20)     at Socket.EventEmitter.emit (domain.js:485:12)     at Pipe.<anonymous> (net.js:670:12) error Command failed with exit code 1.
To Reproduce

yarn create electron-app my-app
yarn add --dev @electron-forge/maker-flatpak
add maker-flatpak to package.json as described in the forge config section of the docs:
{ "name": "@electron-forge/maker-flatpak", "config": {   "options": {     "categories": ["Video"],     "mimeType": ["video/h264"]   } } }
yarn make

Additional Information
I figured out a way to make @electron-forge/maker-flatpak work again. My research for a solution guided me towards the following result:

set up flatpak as described in the official flatpak electron example
change the maker config options:
{ "name": "@electron-forge/maker-flatpak", "config": {   "options": {     "base": "io.atom.electron.BaseApp",     "base-version": "stable"    }  } }

If this is desired I could create a pull request in order to extend the documentation for maker-flatpak so that new users could set up a working flatpak configuration.

I've updated the documentation to reflect the relatively new external dependency: https://github.com/MarshallOfSound/electron-forge-docs/commit/2aa0f59668d630e4100ac82129de53e154c63d06

Adding eu-string via elfutils doesn't fix this problem. Tested on Arch and Ubuntu 18.04.

Also having this issue, although the error shows slightly different lines:
Error: flatpak failed with status code 1
    at ChildProcess.<anonymous> (/home/sfr/Documents/repositories/test/node_modules/@malept/flatpak-bundler/index.js:71:16)
    at ChildProcess.emit (node:events:376:20)
    at ChildProcess.EventEmitter.emit (node:domain:470:12)
    at maybeClose (node:internal/child_process:1063:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:376:20)
    at Socket.EventEmitter.emit (node:domain:470:12)
    at Pipe.<anonymous> (node:net:666:12)

Also having this issue, although the error shows slightly different lines:
Error: flatpak failed with status code 1
    at ChildProcess.<anonymous> (/home/sfr/Documents/repositories/test/node_modules/@malept/flatpak-bundler/index.js:71:16)
    at ChildProcess.emit (node:events:376:20)
    at ChildProcess.EventEmitter.emit (node:domain:470:12)
    at maybeClose (node:internal/child_process:1063:16)
    at Socket.<anonymous> (node:internal/child_process:449:11)
    at Socket.emit (node:events:376:20)
    at Socket.EventEmitter.emit (node:domain:470:12)
    at Pipe.<anonymous> (node:net:666:12)

Still having this issue on Arch, eu-strip is in my path.


karma won't launch any browser ENOENT

I'm runnning

Windows 7 x64
node.js 0.10.3
karma 0.8.4

I've set all my *_BIN ENV variables,
`echo %CHROME_BIN%
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe"``
I've checked the paths are correct and I can launch the browsers by launching %CHROME_BIN% myself.
However, karma wont launch any browser.
ERROR [karma]: { [Error: spawn ENOENT] code: 'ENOENT', errno: 'ENOENT', syscall:  'spawn' } Error: spawn ENOENT     at errnoException (child_process.js:977:11)     at Process.ChildProcess._handle.onexit (child_process.js:768:34)
It happens with every browser. I've been checking the other issues but it seemed that they all were fixed by setting the ENV variables, but not in my case.
I've also tried launching karma from a cmd shell with administrative rights (just in case) but had no luck either.

I resolved this issue by simply running 'npm rebuild'
I got same issue when I have updated my npm, but after rebuild it worked fine.
Hope this will help someone!

@harshadbankar worked for me, thanks.


Implement support for zmscore

PR adds support for ZMSCORE (available since redis-py 4.0.0) and associated Hypothesis-based tests.

Please also revert changes to poetry.lock

@cunla All requested changes have been applied, I believe the PR should be ready for another (or final) review round 🙂

Tests fail on py3.7 (see checks).

@cunla I saw it, just didn't have time in the day to get to it yesterday. I'll get it fixed up and re-pushed shortly.

@cunla I saw it, just didn't have time in the day to get to it yesterday. I'll get it fixed up and re-pushed shortly.
EDIT: @cunla Fixed, pushed. 😁

@the-wondersmith
Still failing.. checkout the workflow logs

@cunla Completely forgot I had act installed. I'll run the workflows locally till they pass and let you know.

For the tests with redis-py < 4 - use the decorator to skip your tests:
@testtools.run_test_if_redispy_ver('above', '4.2.0')

@cunla Knew I missed something when I stripped out hypothesis from the tests. Drat! 😅
Fixed and pushed.

Please squash and merge


Feature request: TLE support

Very nice library!
It would be awesome to see TLE support in this library so it can be used for tracking satellites.
Currently rust-gpredict can be used for that, however it relies on C libgpredict. It would be better to use rust native library.

Thanks!
And yes, extracting TLE data and applying SGP4/SDP4 models to it does sound like a great feature to add. I'll look forward to implementing it in pure Rust!


How Presenter is injected?

I could not find any module with @Provides returning a presenter. However, on UserDetailsFragment, the UserDetailsPresenter is injected. Can anyone explain to me how this works?
Thank you.

See: https://github.com/android10/Android-CleanArchitecture/issues/108#issuecomment-180989041


Programs:test script is failing on 'main' branch

I'm using Linux Mint 21.1.
I have cloned the repo, was able to run pnpm run programs:build
But when running pnpm run programs:test I get:
Besides some other type errors.
error[E0282]: type annotations needed for `Box<_>`
  --> /home/st/.cargo/registry/src/index.crates.io-6f17d22bba15001f/time-0.3.34/src/format_description/parse/mod.rs:83:9
   |
83 |     let items = format_items
   |         ^^^^^
...
86 |     Ok(items.into())
   |              ---- type must be known at this point
   |
   = note: this is an inference error on crate `time` caused by an API change in Rust 1.80.0; update `time` to version `>=0.3.35` by calling `cargo update`

Any pointers?

When I run cargo update in the programs/lighthouse dir, I get this:
error: failed to select a version for the requirement `bytemuck = "=1.14.3"`
candidate versions found which didn't match: 1.21.0, 1.20.0, 1.19.0, ...
location searched: crates.io index
required by package `lighthouse-program v2.0.0 (/media/st/Rígido/perion/lighthouse/programs/lighthouse)`
if you are looking for the prerelease package it needs to be specified explicitly
    bytemuck = { version = "1.2.0-alpha.1" }

I tried to edit Cargo.toml, added patches as below:
[dependencies]
...
bytemuck = "1.14.3"
...

[patch.crates-io]
solana_rbpf = { git = "https://github.com/solana-labs/rbpf", tag = "v0.8.0" }
spl-pod = { git = "https://github.com/solana-labs/solana-program-library", rev = "950efde" }
spl-transfer-hook-interface = { git = "https://github.com/solana-labs/solana-program-library", rev = "950efde" }
spl-type-length-value = { git = "https://github.com/solana-labs/solana-program-library", rev = "2883813" }

Then Cargo update will run ok.
But Cargo build will fail (same for programs:test), with a bunch of errors like:
error[E0277]: the trait bound `T: spl_discriminator::discriminator::SplDiscriminate` is not satisfied
   --> /home/st/.cargo/registry/src/index.crates.io-6f17d22bba15001f/spl-tlv-account-resolution-0.5.1/src/state.rs:286:45
    |
286 |         let bytes = state.get_first_bytes::<T>()?;
    |                           ---------------   ^ the trait `spl_discriminator::discriminator::SplDiscriminate` is not implemented for `T`
    |                           |
    |                           required by a bound introduced by this call
    |
note: required by a bound in `get_first_bytes`
   --> /home/st/.cargo/git/checkouts/solana-program-library-dad8d98b86bb61bf/950efde/libraries/type-length-value/src/state.rs:252:27
    |
252 |     fn get_first_bytes<V: SplDiscriminate>(&self) -> Result<&[u8], ProgramError> {
    |                           ^^^^^^^^^^^^^^^ required by this bound in `TlvState::get_first_bytes`
help: consider further restricting this bound
    |
276 |     pub async fn add_to_instruction<T: SplDiscriminate + spl_discriminator::discriminator::SplDiscriminate, F, Fut>(
    |                                                        +++++++++++++++++++++++++++++++++++++++++++++++++++

error[E0277]: the trait bound `T: spl_discriminator::discriminator::SplDiscriminate` is not satisfied
   --> /home/st/.cargo/registry/src/index.crates.io-6f17d22bba15001f/spl-tlv-account-resolution-0.5.1/src/state.rs:177:40
    |
177 |         let (bytes, _) = state.alloc::<T>(tlv_size, false)?;
    |                                -----   ^ the trait `spl_discriminator::discriminator::SplDiscriminate` is not implemented for `T`
    |                                |
    |                                required by a bound introduced by this call
    |
note: required by a bound in `TlvStateMut::<'data>::alloc`


Update README.md with latest release

@jaredsburrows  all set

@digitalbuddha Thanks!
So you are able to push locally but not with gradle?
I see this is version 0.1.0, https://mvnrepository.com/artifact/com.github.brianPlummer/tinydancer/0.1.0. In gradle it is set to 1.0.0-SNAPSHOT: https://github.com/friendlyrobotnyc/TinyDancer/blob/master/build.gradle#L39.

I think @brianPlummer pushed manually using a local gradle.properties. We tried to redo the keys and no bueno.  I need to learn more about the process or just grab someone else that know what they are doing.

@digitalbuddha Alright. You could PM me the pass, I could tinker with it and then you can change the password after. Let me know if I can help.

@digitalbuddha Oh, I just meant you can message me on hangouts or email<EMAIL_ADDRESS>


feat: predictable preview deployment aliases via pr id

I'm deploying multiple Next.js applications from a monorepo. These are being fused together by rewrites to appear like one application as described here. I would like to be able to preview the whole setup, therefore I need stable and predictable preview aliases for all deployed applications. This probably could be achieved with the current approach of using the branch names, but seems like quite a hassle due to the trimming of long branch names. Also the branch name is currently not being made available explicitly in the build step to utilise it to generate the required rewrites.
In order to achieve this I would like to propose these two changes:
Provide the Azure DevOps PR ID as a env var to the build via the --build-env flag for  the vercel deploy command.
Offer an alternative matching way to generate the deployment alias URLs.
Currently they are generated from project and branch name (simplified: ${projectName}-${branchName}.vercel.app). Some parts might be trimmed if 63 chars in total are being exceeded. This would be quite a bit of logic to generate the rewrite urls in the Next config. Also the branch name isn't currently available at build time afaik (could be easily provided via --build-env as well – might be a nice to have addition).
Therefore I suggest the following alternative: ${projectName}-${pullRequestId}.vercel.app.
In the Next config you can then easily generate rewrites for the corresponding application:
{
  source: '/zone-a/:path*/',
  destination: `https://zone-a-app-${process.env.devopsPullRequestId}.vercel.app/:path*/`,
}

This obviously might be a breaking change for existing setups, therefore I suggest to provide this as opt-in only.
Unfortunately I'm not able to test and verify my changes easily. Therefore I tried to keep the change's footprint as small as possible.

I came to the realization, that this approach might be to opinionated.
Instead I'll prepare a PR adding (some of) the env vars which are usually available during a build when using a standard git integration.
The required alias can be created in the DevOps pipeline by adding your own step after the deployment task and using it's output.


[FLINK-4639] [table] Make Calcite features more pluggable

Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[x] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[x] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

This PR adds some means to modify Calcites behavior within the Table/SQL API. It introduces a CalciteConfig which is available through tEnv.getConfig().getCalciteConfig(). It allows to append/replace a rule set, append/replace SQL operators and replace the SQL parser so far.

PR looks good to me, except for some methods of the added CalciteConfig. Will fix these issues and merge the PR.

Merging


Rename tutorials to examples, how-tos to tutorials

Overview
Rename the docs pages "tutorials" to "examples", and "how-tos" to "tutorials". This also fixes broken navigation on the how-tos page.
Connected to https://github.com/pilosa/www/pull/189
Pull request checklist

[ ] I have read the contributing guide.
[ ] I have agreed to the Contributor License Agreement.
[ ] I have updated the documentation.
[ ] I have resolved any merge conflicts.
[ ] I have included tests that cover my changes.
[ ] All new and existing tests pass.

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.

Sorry, I didn't think about how much this would screw up the diff. Readable diff here for posterity:
$ git diff
diff --git a/docs/examples.md b/docs/examples.md
index d304dc8..bf5e76f 100644
--- a/docs/examples.md
+++ b/docs/examples.md
@@ -1,5 +1,5 @@
 +++
-title = "Tutorials"
+title = "Examples"
 weight = 4
 nav = [
     "Transportation",
@@ -7,7 +7,7 @@ nav = [
 ]
 +++

-## Tutorials
+## Examples

 ### Transportation

diff --git a/docs/getting-started.md b/docs/getting-started.md
index 84c5fd0..1bd2fae 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -155,4 +155,4 @@ curl localhost:10101/index/repository/query \

 ### What's Next?

-You can jump to [Data Model](../data-model/) for an in-depth look at Pilosa's data model, or [Query Language](../query-language/) for more details about **PQL**, the query language of Pilosa. Check out the [Tutorials](../tutorials/) for example implementations of real world use cases for Pilosa. Ready to get going in your favorite language? Have a peek at our small but expanding set of official [Client Libraries](../client-libraries/).
+You can jump to [Data Model](../data-model/) for an in-depth look at Pilosa's data model, or [Query Language](../query-language/) for more details about **PQL**, the query language of Pilosa. Check out the [Examples](../examples/) page for example implementations of real world use cases for Pilosa. Ready to get going in your favorite language? Have a peek at our small but expanding set of official [Client Libraries](../client-libraries/).
diff --git a/docs/tutorials.md b/docs/tutorials.md
index 7809b70..4c2cdd7 100644
--- a/docs/tutorials.md
+++ b/docs/tutorials.md
@@ -1,14 +1,14 @@
 +++
-title = "How Tos"
+title = "Tutorials"
 weight = 4
 nav = [
-    "how-to-setup-a-secure-pilosa-cluster"
+    "How To Setup a Secure Cluster",
 ]
 +++

-## How Tos
+## Tutorials

-### How To Setup a Secure Pilosa Cluster
+### How To Setup a Secure Cluster

 #### Introduction


WIP - Tasks in action chain inherit notify from chain

Besides the things I have mentioned, this approach looks good to me.


Installing a package without specific version

When installing a package without a version the @types package is installed to the latest version available.
The problem with it is when the package already has built in types the @types package is installed even though there is no need.
I suggest, after installing a package, check the version of the installed package and then if the @types package is available for this version, install it, otherwise you can assume the package already have built in types and then you can skip the installment of the @types package.

Here is another suggestion
Maybe after installing a package the tool will check if the package has types from its package.json file, using the types or typings field.


Release v2.0.7?

Am I missing something or should there be a v2.0.7 release?  I see version 2.0.7 on the SuperMarket (https://supermarket.chef.io/cookbooks/rundeck) but no version that matches in GitHub.
Master is very close but there are differences (installation of slack plugin, variable data bag name).

https://github.com/Webtrends/rundeck/releases/tag/v2.0.7


Support multiple config matches for a single tenant/product

What does this PR do?

Fixes #45
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How should this be tested?

[x] Start the jackson service. Add multiple IdP configs for same tenant/product. Login using jackson-demo. The browser will show an IdP selection page from jackson service. Select and click proceed to resume the flow.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code and corrected any misspellings
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@niwsa Should update docs to add the new config for IdP discovery path


Add 'set' operators

It would be nice to be able to more in 'set' than set a whole field value:
field=~/pattern/replacement/ ?
field.subfield.subfield=bar ; when field value is a JSON blob, set by jsonpath spec
This is especially useful for svcinst

Roadmap ideas for the interface belong in noms-command, I think.


Webpack Deprication Notice Removed

Detail-
http://stackoverflow.com/questions/42076879/fallbackloader-option-has-been-deprecated-replace-with-fallback

Thank you! This warning kept bugging me just didn't have the time 🎈


visual studio code show error

[js] Exported external package typings file '.../node_modules/json2csv/index.d.ts' is not a module. Please contact the package author to update the package definition.

Feel free to submit a PR, I don't use TS.

Using declare module seems to be deprecated: https://github.com/Microsoft/TypeScript/issues/2839
I changed the typescript definition to the following:
declare namespace json2csv {
  interface CSVCallback {
    (error: Error, csv: string): void;
  }

  export function json2csv(options: any, callback: CSVCallback): string;
}

export = json2csv.json2csv;

I will prepare a pull request and try to validate if this the current state of the are type definition format.

In which version will this fix be available?

It is now released as 3.4.1

@knownasilya thanks :)

Has anyone been able to use this with TS? Would be great to add a section in the docs for ts for a minimal example.

Feel free to pioneer this, and I'll review your PR.

I found a stopgap,but not using this repo, atm I'm snowed under with work


Add train logs for asreader_who_did_what experiment

Hmm, I would probably put this in a condensed form somehow on a new page under doc/, instead of committing the actual log file.  I might put it here: http://deep-qa.readthedocs.io/en/latest/models/about_models.html, though I'm not sure yet.

yeah, i'm not too sure where or how to present it as well --- we can leave this open until we think of a good solution.

I'd probably add a section under About Models  listing all of the models we can reproduce, including references to papers, links to the experiment json file / scala code to run the experiment, the result we got, and the running time (including on what machine).  My only question is whether to have this in the About Models page, or somewhere else (e.g., one section like this under each type of model).

still unsure where this should go...

i cant think of a centralized place to put these things, so i'm going to close this for now; the files will remain on my branch / these results are documented so I don't think we're losing much.

Maybe you could add a section to this page that lists some of the more popular models that we have implemented (with links to the docs for the actual implementation), and gives results from training those models with our code.


Ceeid system userId module docs

🏷 Type of documentation

[ ] new bid adapter
[ ] update bid adapter
[ ] new feature
[x] text edit only (wording, typos)
[ ] bugfix (code examples)
[ ] new examples

📋 Checklist

[ ] Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself
[ ] For new adapters check submitting your adapter docs

@decemberWP - please fix conflicts?


DynamicRepo - NextVersion.txt file when no /target branch arg

When testing the new dynamic repo functionality (thanks for the new feature by the way!), I noticed that the NextVersion.txt file in my repo was not being honoured and therefore my attempts to bump the version number using that file were not working.
To replicate,

Add a NextVersion.txt file to the target repo and set a bumped version number
Execute GitVersion.exe using the -url -u and -p args which will invoke the new dynamic repo functionality in GitVersion.

Note that the version number GitVersion outputs won't be bumped as per the text file.
I believe if you also pass in an -targetbranch arg to GitVersion then it works but that's an assumption from reading the code not any actual testing.

Let's explain how this works. You have a repository with a default branch. If you follow GitFlow, you probably have set the default branch to develop. If you haven't, you are probably on master. From now on, I will call the default branch default.
When you clone a dynamic repository, it checks the default branch (you can change that in the server settings, for example in GitHub). If you have pushed NextVersion.txt to the develop branch, but your default branch is master, it cannot find NextVersion.txt thus it will be ignored.
Please make sure that the NextVersion.txt is also available on the default branch of your repository. Otherwise it will only work when you specify the branch on which you committed the NextVersion.txt file.

@GeertvanHorrik  my default branch is master. It has a NextVersion.txt file. So I can't see anything wrong there.
If no one else can replicate this I will happily assume user error.
However the code you showed me here https://github.com/ParticularLabs/GitVersion/blob/ca002ed570b03f2f3a610523ab79adf34848fdc1/GitVersionExe/GitPreparer.cs#L105 seemed to only do the checkout of nextversion.txt if there was a targetbranch arg present.

No, if you read the code correctly, it does this:

Get repository (default branch) (note that this code should already have the latest head)
If target specified, try to get the new head (will be null if nothing specified)
If we have a new head, switch to it (will not be executed if null)
Check out the file if it exists (always)

Can you write a failing unit test? Then I am willing to look into this.

Hmm, I am always willing to accept my own fallibility. But, I'm reading this:
            if (!string.IsNullOrWhiteSpace(arguments.TargetBranch))
            {
                    ... shortened for brevity...

                    repository.CheckoutFilesIfExist("NextVersion.txt");
             }

Irrespective of what I am reading, the issue was raised off the back of actually running GitVersion.exe locally - but I appreciate your caution - no one likes to have there time wasted.
There doesn't appear to be any existing test coverage for this otherwise you could just point to the existing test and tell me to run it - nevermind - I will have a go at creating one.
In order to carry out the unit test, i'll need the ability to commit a NextVersion.txt file to the local repo used for the unit test. I'll have to get familiar with libgit2sharp before I can do that - I'll work on that as soon as I can. If anyone knows of an existing function in the code base that commits a file to a Repo - i would be greatful if they could point me to that.
Cheers

You are right, I missed the argument check at the top. I think it can be removed, let me double check.

Thanks Henk - glad we are on the same page :)
I still think a test for regression purposes would still be handy as the NextVersion.txt file is a pretty important feature of GitVersion - but if you don't have time for that I can look into that as it will give me an excuse to get more familiar with the repo as well as libgit2sharp!

btw. I do recommend to always pass in the branch name since you should never assume the default branch name of a repository. But will fix this anyway.

GitPreparerTests.WorksCorrectlyWithRemoteRepository is the test covering this.
We have a bunch of extension methods on the fixture.Repository.
As for NextVersion.txt this is being completely replaced by GitVersionConfig.yaml. So Whatever you do for NextVersion.txt please add support for GitVersionConfig.yaml at the same time.  v3 is dropping NextVersion.txt and only using the config file

@JakeGinnivan  - yep I found that test and those extension methods. I couldn't see anything that  commits an actual file - but leave that to me, I only briefly looked at this stage. Thanks for letting me know about the yaml file I wasn't aware of that!

The first fix is easy:
var targetBranch = arguments.TargetBranch;
if (string.IsNullOrWhiteSpace(targetBranch))
{
    targetBranch = repository.Head.Name;
}

Will look into GetVersionConfig.yaml support after that.

@dazinator wondering if you had time to create a wiki page for the dynamic repositories feature in general.
I think it would be handy to include tips on how to get the currently building branch names from different CI environments.

@JakeGinnivan - nope I have not yet created a wiki page for this feature, but I'll happily give that a shot!
I have been looking at the existing page here: https://github.com/ParticularLabs/GitVersion/wiki/Command-Line-Tool which does already describe these arguments, but I don't think there is anywhere that explains this particular feature in detail, and how, for example, it enables CI's to work that don't automatically checkout the repo - for example Team City builds that are set to "checkout on agent".
Are you thinking having some documentation page per CI system would be the way to go because I like that idea.

I was thinking have a Dynamic Respositories wiki page. We can link it from the command line args page and also the FAQ.
The info per CI system would be more how to get the branch name to pass to the argument so GitVersion calculates for the correct branch (otherwise it will always calculate master version even if building something else).

@JakeGinnivan - Ah Ok I Get ya.
I have created a wiki page here: https://github.com/ParticularLabs/GitVersion/wiki/Feature:-Dynamically-Obtained-Repository feel free to have a read and edit however you like.
I get the impression I may not understand the full implications of this feature just because my Git skills are weak. For example would it be common to have an scenario where you are building your repo - but you want the version number to be calculated from another repo or another branch? Because if that scenario is common in the Git world, then I can see how this feature might also enable that - I didn't want to speculate on this so the wiki page doesn't mention anything like this at present.

I think the /b should nearly be made mandatory, one may never rely on the default branch.

For example would it be common to have an scenario where you are building your repo - but you want the version number to be calculated from another repo or another branch?

I don't think this would be common. This is mainly for build servers who do not check out a proper git repo.
Good work on the wiki page. I think we should say to always specify /b with note about the fallback.
Also should say something like ' in TeamCity the current branch can be accessed with the %system.current_vcs_branch% (or whatever the variable actually is)
Nice work
Sent from my Windows Phone

From<EMAIL_ADDRESS>Sent: ý18/ý01/ý2015 16:22
To<EMAIL_ADDRESS>Cc: Jake<EMAIL_ADDRESS>Subject: Re: [GitVersion] DynamicRepo - NextVersion.txt file when no /target branch arg (#351)
@JakeGinnivanhttps://github.com/JakeGinnivan - Ah Ok I Get ya.
I have created a wiki page here: https://github.com/ParticularLabs/GitVersion/wiki/Feature:-Dynamically-Obtained-Repository feel free to have a read and edit however you like.
I get the impression I may not understand the full implications of this feature just because my Git skills are weak. For example would it be common to have an scenario where you are building your repo - but you want the version number to be calculated from another repo or another branch? Because if that scenario is common in the Git world, then I can see how this feature might also enable that - I didn't want to speculate on this so the wiki page doesn't mention anything like this at present.
—
Reply to this email directly or view it on GitHubhttps://github.com/ParticularLabs/GitVersion/issues/351#issuecomment-70414351.

Ok - I have made those changes that you both suggested. Feel free to make any further tweaks.

Going to close this.
See #367 for the enforcing the branch


Maven/Integration-test of security-sample-managed (VaadinSession issue)

Hi , I try to do an integration test of the security-sample-managed but I have a problem when it is executed by maven. I have no problem with JUnit in eclipse.
stackTrace.txt
loginIT.zip (pom.xml, loginIT.java)

You could start by making sure that the classpath in Eclipse does not contain anything that's not in the Maven classpath or vice versa.

java.lang.AssertionError: null - you have to disable jvm assertions when running tests with maven
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <configuration>
        <enableAssertions>false</enableAssertions>
    </configuration>
</plugin>

Thanks for the help. It works.


⚠ Bofrost.at has degraded performance

In d0d9dd3, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1608 ms

Resolved: Bofrost.at performance has improved in 34dbef7 after 6 minutes.


Integrate camel enhancements in quarkus-artemis 3

We added some additional camel support in #121. Due to the fact that quarkus 3 makes the switch from JavaEE to JakartaEE, and camel 4 makes the switch from JavaEE to JakartaEE, we need to wait to port this changes into quarkus-artemis 3 until camel-quarkus 3, based on camel 4, is released.

quarkus-camel is available in quarkus version 3.0.0.Beta1. Thus, the ticket is unblocked

I would like to work on this :)

Blocked by: https://github.com/apache/camel-quarkus/issues/4725 , but there is already a PR in progress to solve it


nav-buttons don't show unless moved inside ion-view

I've had a right button in the nav bar, specific to each state, using ion-nav-buttons.
<ion-nav-buttons side="right">
    <button class="button button-icon icon ion-gear-b" ng-click="popover.show($event)"></button>
</ion-nav-buttons>
<ion-view title="Plot">
  <ion-content class="has-header">
    <!-- stuff-->
  </ion-content>
</ion-view>

Switching to release 14 broke that functionality, and the workaround was to move the ion-nav-buttons inside the ion-view.
<ion-view title="Plot 2">
  <ion-nav-buttons side="right">
      <button class="button button-icon icon ion-gear-b" ng-click="popover.show($event)"></button>
  </ion-nav-buttons>

  <ion-content class="has-header">
    <!-- stuff -->
  </ion-content>

</ion-view>

Is this even an issue, or was this change in requirements intended?  Will my workaround continue to work?  I browsed the change/deprecate/broken logs and didn't see anything directly referencing this.  I also checked the current issues, and didn't see anybody saying the same thing.  Am I missing something?
Plunker showing broken and workaround
Ionic is an awesome project!  Kudos to the team.

Greetings, @CatabeeScienceAndDesign!
We are now requiring all issues to be submitted through our custom issue form so that we have all of the information necessary to fix them as quickly as possible.
Your progress on this issue has been saved at the following url:
link to Ionic issue form
This issue will be closed if not resubmitted through the form. Please fill out the rest of the form so that we may assist you.
Thank you for allowing me to assist you.

The docs for ion-nav-buttons (http://ionicframework.com/docs/api/directive/ionNavButtons/) state that they should always be inside an ion-view. Is there a reason that you want to declare them outside of an ion-view?

Ah.  I was originally using it inside a [ion-nav-bar] (http://ionicframework.com/docs/api/directive/ionNavBar/) which does NOT have to be in the ion-view, so I had not noticed that requirement.  For some reason, in the previous version of Ionic I was able to use them outside the ion-view but upgrading brought in enforcement of that requirement.  Thanks!


Update NLLB documentation to reflect current behavior

Doc request
Substitute mentions of tokenizer.lang_code_to_id from NLLB documentation.
Additional context
huggingface/transformers#29834 removed lang_code_to_id from NLLBTokenizer and NLLBTokenizerFast but the documentation on the website still makes use of it:
https://github.com/huggingface/transformers/blob/52585019a17f6033df64e6ad4222d22a1f993c61/docs/source/en/model_doc/nllb.md?plain=1#L104
https://github.com/huggingface/transformers/blob/52585019a17f6033df64e6ad4222d22a1f993c61/docs/source/en/model_doc/nllb.md?plain=1#L129
https://github.com/huggingface/transformers/blob/52585019a17f6033df64e6ad4222d22a1f993c61/docs/source/en/model_doc/nllb.md?plain=1#L178

Hi, can you open this issue on the transformers repo instead?


support internlm-xcomposer2d5-7b

Motivation
support internlm-xcomposer2d5-7b
related issues https://github.com/InternLM/lmdeploy/issues/1920

[x] base model & image inputs
[x] Write & Webpage model (since turbomind doesn't support slora, only one model can be deployed at a time)
[x] quantization
[x] document
[ ] video input

Currently, the hf model can't be used with transformers api due to https://github.com/InternLM/InternLM-XComposer/issues/354


Add --syslog-prefix (-Z) option

Good day,
When we enable --syslog in multiple instances of dnsscrypt-proxy, it wouldn't be easy to track specific messages about particular targets written in a syslog file since we only have PID's to distinguish each instance.  But if we have this feature we can customize the messages to become something like this:
May 18 09:55:14 local dnscrypt-proxy[6349]: [<IP_ADDRESS>:443] Server key fingerprint is ...
May 18 09:55:14 local dnscrypt-proxy[6349]: [<IP_ADDRESS>:443] Proxying from 127.0.x.x:5053 to <IP_ADDRESS>:443
May 18 09:55:15 local dnscrypt-proxy[6350]: [<IP_ADDRESS>:443] Starting dnscrypt-proxy 1.6.1
May 18 09:55:15 local dnscrypt-proxy[6350]: [<IP_ADDRESS>:443] Generating a new session key pair
May 18 09:55:15 local dnscrypt-proxy[6350]: [<IP_ADDRESS>:443] Done
May 18 09:55:15 local dnscrypt-proxy[6350]: [<IP_ADDRESS>:443] Server certificate #808464433 received
May 18 09:55:15 local dnscrypt-proxy[6350]: [<IP_ADDRESS>:443] This certificate is valid
May 18 09:55:15 local dnscrypt-proxy[6350]: [<IP_ADDRESS>:443] Chosen certificate #808464433 is valid from

So it would be nice if it gets added.

Merged, thanks!


Fix to allow custom images

If a requested image has a slash, use it as is (since a regisistry was specified)
Otherwise, use the rancher prefixed image names (allows current ui to not break)
For #104

The new machine image type now covers this functionality.

@LLParse Thank you!


fix(project): upgrade vulnerable dependency

Signed-off-by: Bracken Dawson<EMAIL_ADDRESS>PR summary
jsonwebtoken was found to be vulnerable.
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[x] Yes
[ ] No

Other information

:tada: This PR is included in version 0.0.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


publish<EMAIL_ADDRESS>

Requested by: @bruno-garcia
Merge target: (default)
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[ ] symbol-collector
[ ] upm
[ ] github
[ ] registry

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

Please don't approve until we check with @bitsandfoxes if we'll go ahead or change the Screenshot options


Bug: Can't clear user profile fields

Introduced in #482-- if I try to unset my address or mobile number, I can't. We had a user change their mobile number to someone else's to avoid receiving texts.
Related: if someone does clear out their mobile number, should we unset their sms_status?

The changes introduced in #482 were to avoid clearing out user's password. Per suggestions in that PR and https://www.pivotaltracker.com/story/show/150597370, the ideal fix is to split out a separate change password form that requires current password in order to change.


Fix Swagger Office Queue Spec

Description
This supports #1597 load testing.
The swagger spec for the office queue is incorrect and strict interpretation of it by the Yelp Bravado python library throws unrecoverable errors. In particular:

Customer Deadline is dead code and is never filled in despite being a required field
Either PPM Status or HHG Status can be empty but both are required fields.
GBL number is required despite the fact that it doesn't exist until after a GBL is generated so it usually shows up as empty for new moves
Move Date is required despite most of the e2e test data not having that data at all and the queue still loads without it.

Reviewer Notes
Apparently this was never caught before because React-Table is loading the data outside of a swagger api request. Per this discussion.
Should we modify the react-table integration to use our swagger endpoint?  Drift like this between the swagger spec and our API calls is concerning.
Setup
Run the app and go to the queues page, you should not see any issues.
Code Review Verification Steps

[x] Request review from a member of a different team.
[x] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for removing customer deadline

🚢


feature request: continue press ctrl+shift+i to select line up

currently when press ctrl+i several times vscode will select line below.
what about press ctrl+shift+i to select line up
analysis: ctrl+i bind to expandLineSelection, this command will select current line and move cursor to the first column of next line,
we can implement a comand expandLineSelectionUp that select current line and move cursor to the previous line.

Already requested: https://github.com/Microsoft/vscode/issues/1262

Thank you @Bill-Stewart, let's track in #1262


polygon-pattern-file with remote URL doesn't work

This code:
polygon-pattern-file:url("http://freeseamlesstextures.com/images/4-old-brick-background-thb.jpg");
(following the onboard documentation)
gave:
file could not be found: '/Users/stevebennett/vicroads-purple.tm2/http://freeseamlesstextures.com/images/4-old-brick-background-thb.jpg' in style 'water' in PolygonPatternSymbolizer
Using a local file worked fine.
0.2.5 on OS X Mavericks.

This is an oversight in the documentation. CartoCSS itself does not support loading web resources - in TileMill this was handled by the millstone module, but we aren't using that in Mapbox Studio and all resources should be local. I've updated the online documentation in bc5eeac0d1e45595c203d13798d3d9fdccfee972 - did you see a web URL reference anywhere else?

Ah, that makes sense. If I run into something similar elsewhere I'll let you know.
Any plans to include Millstone or a successor? I found it pretty convenient in Tilemill.

Any plans to include Millstone or a successor? I found it pretty convenient in Tilemill.

No plans - all assets that you want to include in the style need to be in the style project folder.