[VS Code] Could not connect to the server. Check that you are connected to the internet.

Logs : vs_codelogs.zip
Error:
Could not connect to the server. Check that you are connected to the internet.
Steps to Reproduce:

Trying to join or share a live share session

Version Data

extensionName
VSLS

extensionVersion
0.3.735

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.28.0

platformName
Linux

platformVersion
4.18.0-2-amd64

Other information
Debian Sid updated as of 20181010 13:26 CEST.
dpkg -l | grep libssl
ii  libssl-dev:amd64                                                 1.1.1-1                                 amd64        Secure Sockets Layer toolkit - development files
ii  libssl1.0.2:amd64                                                1.0.2o-1                                amd64        Secure Sockets Layer toolkit - shared libraries
ii  libssl1.1:amd64                                                  1.1.1-1                                 amd64        Secure Sockets Layer toolkit - shared libraries
norangshol@enceladus:~$ dpkg -l | grep libssl | dpkg -L $(get_cols 2 |  tr '\n' ' ')
/.
/usr
/usr/include
/usr/include/openssl
/usr/include/openssl/aes.h
/usr/include/openssl/asn1.h
/usr/include/openssl/asn1_mac.h
/usr/include/openssl/asn1err.h
/usr/include/openssl/asn1t.h
/usr/include/openssl/async.h
/usr/include/openssl/asyncerr.h
/usr/include/openssl/bio.h
/usr/include/openssl/bioerr.h
/usr/include/openssl/blowfish.h
/usr/include/openssl/bn.h
/usr/include/openssl/bnerr.h
/usr/include/openssl/buffer.h
/usr/include/openssl/buffererr.h
/usr/include/openssl/camellia.h
/usr/include/openssl/cast.h
/usr/include/openssl/cmac.h
/usr/include/openssl/cms.h
/usr/include/openssl/cmserr.h
/usr/include/openssl/comp.h
/usr/include/openssl/comperr.h
/usr/include/openssl/conf.h
/usr/include/openssl/conf_api.h
/usr/include/openssl/conferr.h
/usr/include/openssl/crypto.h
/usr/include/openssl/cryptoerr.h
/usr/include/openssl/ct.h
/usr/include/openssl/cterr.h
/usr/include/openssl/des.h
/usr/include/openssl/dh.h
/usr/include/openssl/dherr.h
/usr/include/openssl/dsa.h
/usr/include/openssl/dsaerr.h
/usr/include/openssl/dtls1.h
/usr/include/openssl/e_os2.h
/usr/include/openssl/ebcdic.h
/usr/include/openssl/ec.h
/usr/include/openssl/ecdh.h
/usr/include/openssl/ecdsa.h
/usr/include/openssl/ecerr.h
/usr/include/openssl/engine.h
/usr/include/openssl/engineerr.h
/usr/include/openssl/err.h
/usr/include/openssl/evp.h
/usr/include/openssl/evperr.h
/usr/include/openssl/hmac.h
/usr/include/openssl/idea.h
/usr/include/openssl/kdf.h
/usr/include/openssl/kdferr.h
/usr/include/openssl/lhash.h
/usr/include/openssl/md2.h
/usr/include/openssl/md4.h
/usr/include/openssl/md5.h
/usr/include/openssl/mdc2.h
/usr/include/openssl/modes.h
/usr/include/openssl/obj_mac.h
/usr/include/openssl/objects.h
/usr/include/openssl/objectserr.h
/usr/include/openssl/ocsp.h
/usr/include/openssl/ocsperr.h
/usr/include/openssl/opensslv.h
/usr/include/openssl/ossl_typ.h
/usr/include/openssl/pem.h
/usr/include/openssl/pem2.h
/usr/include/openssl/pemerr.h
/usr/include/openssl/pkcs12.h
/usr/include/openssl/pkcs12err.h
/usr/include/openssl/pkcs7.h
/usr/include/openssl/pkcs7err.h
/usr/include/openssl/rand.h
/usr/include/openssl/rand_drbg.h
/usr/include/openssl/randerr.h
/usr/include/openssl/rc2.h
/usr/include/openssl/rc4.h
/usr/include/openssl/rc5.h
/usr/include/openssl/ripemd.h
/usr/include/openssl/rsa.h
/usr/include/openssl/rsaerr.h
/usr/include/openssl/safestack.h
/usr/include/openssl/seed.h
/usr/include/openssl/sha.h
/usr/include/openssl/srp.h
/usr/include/openssl/srtp.h
/usr/include/openssl/ssl.h
/usr/include/openssl/ssl2.h
/usr/include/openssl/ssl3.h
/usr/include/openssl/sslerr.h
/usr/include/openssl/stack.h
/usr/include/openssl/store.h
/usr/include/openssl/storeerr.h
/usr/include/openssl/symhacks.h
/usr/include/openssl/tls1.h
/usr/include/openssl/ts.h
/usr/include/openssl/tserr.h
/usr/include/openssl/txt_db.h
/usr/include/openssl/ui.h
/usr/include/openssl/uierr.h
/usr/include/openssl/whrlpool.h
/usr/include/openssl/x509.h
/usr/include/openssl/x509_vfy.h
/usr/include/openssl/x509err.h
/usr/include/openssl/x509v3.h
/usr/include/openssl/x509v3err.h
/usr/include/x86_64-linux-gnu
/usr/include/x86_64-linux-gnu/openssl
/usr/include/x86_64-linux-gnu/openssl/opensslconf.h
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libcrypto.a
/usr/lib/x86_64-linux-gnu/libssl.a
/usr/lib/x86_64-linux-gnu/pkgconfig
/usr/lib/x86_64-linux-gnu/pkgconfig/libcrypto.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/libssl.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/openssl.pc
/usr/share
/usr/share/doc
/usr/share/doc/libssl-dev
/usr/share/doc/libssl-dev/changelog.Debian.gz
/usr/share/doc/libssl-dev/changelog.gz
/usr/share/doc/libssl-dev/copyright
/usr/lib/x86_64-linux-gnu/libcrypto.so
/usr/lib/x86_64-linux-gnu/libssl.so

/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2
/usr/lib/x86_64-linux-gnu/libssl.so.1.0.2
/usr/lib/x86_64-linux-gnu/openssl-1.0.2
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/lib4758cca.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libaep.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libatalla.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libcapi.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libchil.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libcswift.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libgmp.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libgost.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libnuron.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libpadlock.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libsureware.so
/usr/lib/x86_64-linux-gnu/openssl-1.0.2/engines/libubsec.so
/usr/share
/usr/share/doc
/usr/share/doc/libssl1.0.2
/usr/share/doc/libssl1.0.2/changelog.Debian.gz
/usr/share/doc/libssl1.0.2/changelog.gz
/usr/share/doc/libssl1.0.2/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libssl1.0.2

/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/engines-1.1
/usr/lib/x86_64-linux-gnu/engines-1.1/afalg.so
/usr/lib/x86_64-linux-gnu/engines-1.1/capi.so
/usr/lib/x86_64-linux-gnu/engines-1.1/padlock.so
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
/usr/lib/x86_64-linux-gnu/libssl.so.1.1
/usr/share
/usr/share/doc
/usr/share/doc/libssl1.1
/usr/share/doc/libssl1.1/NEWS.Debian.gz
/usr/share/doc/libssl1.1/changelog.Debian.gz
/usr/share/doc/libssl1.1/changelog.gz
/usr/share/doc/libssl1.1/copyright

Due to logs I suspect error:0E076071:configuration file routines:MODULE_RUN:unknown module name is telling us that libssl1.0.2 has removed some binary compability in libssl1.0* ?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768476;msg=152 comes to mind that SSL3 is removed, but this is a guess.

Internet connectivity is fine, just for the record. So the error message is quite misleading.

@norrs Thanks for reporting the issue. From the logs, it seems SSL connection could not be established.
@Priya91 can you take a look at this? This is similar to issue #1087

Hmm, we should provide a better error message here. @Chuxel Is this the one you were talking about in the standup?

I have the same problem on Fedora Linux
$ uname -a
Linux gauss 4.18.13-250.vanilla.knurd.1.fc28.x86_64 #1 SMP Wed Oct 10 07:25:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ dnf list installed | grep openssl
apr-util-openssl.x86_64                1.6.1-8.fc28                     @updates
compat-openssl10.x86_64                1:1.0.2o-1.fc28                  @fedora
openssl.x86_64                         1:1.1.0i-1.fc28                  @updates
openssl-debuginfo.x86_64               1:1.1.0h-3.fc27                  @updates-debuginfo
openssl-debugsource.x86_64             1:1.1.0h-3.fc27                  @updates-debuginfo
openssl-devel.x86_64                   1:1.1.0i-1.fc28                  @updates
openssl-libs.i686                      1:1.1.0i-1.fc28                  @updates
openssl-libs.x86_64                    1:1.1.0i-1.fc28                  @updates
openssl-libs-debuginfo.x86_64          1:1.1.0h-3.fc27                  @updates-debuginfo
openssl-pkcs11.i686                    0.4.8-2.fc28                     @updates
openssl-pkcs11.x86_64                  0.4.8-2.fc28                     @updates
rubygem-openssl.x86_64                 2.1.0-93.fc28                    @updates
xmlsec1-openssl.x86_64                 1.2.25-4.fc28                    @updates

Excerpt from vsls Agent.log:
[2018-10-10 20:09:51.374 Agent I] vsls-agent v0.3.788.8381 (pid: 6952)
[2018-10-10 20:09:51.381 Agent I] Reminder: You may only use this software with Visual Studio and Visual Studio Code, as described in the license (https://go.microsoft.com/fwlink/?linkid=872556).
[2018-10-10 20:09:51.381 Agent I] Start time: 10/10/18 8:09:51 PM
[2018-10-10 20:09:51.381 Agent I] Using VSLS service: https://insiders.liveshare.vsengsaas.visualstudio.com/
[2018-10-10 20:09:51.435 Agent I] VSLSAgent/0.3.788.8381 VSLS/2.2 PlatformName/Linux 4.18.13 PlatformVersion/<IP_ADDRESS>
[2018-10-10 20:09:51.436 Agent I]
[2018-10-10 20:09:51.442 Agent.Proxy I] Proxy settings from env variable: http_proxy was null and https_proxy was null
[2018-10-10 20:09:51.449 Agent I] (1001) Listening on pipe "903de871a5464e5ea662b5ce32025792"
[2018-10-10 20:09:51.519 Agent I] Accepted incoming pipe connection.
[2018-10-10 20:09:51.537 Agent I] RPC session #1 established.
[2018-10-10 20:09:51.788 Agent V] > #1 {Id=0 Name=version.exchangeVersions Arguments={}}
[2018-10-10 20:09:51.832 Agent V] < #1 {Id=0 Result={VersionString=0.3.788.8381 ProtocolVersionString=2.2 PlatformName=Linux 4.18.13 PlatformVersionString=<IP_ADDRESS>} HandlingTimes=[35]}
[2018-10-10 20:09:51.835 Telemetry V] > #1 {Id=1 Name=telemetry.initialize Arguments={}}
[2018-10-10 20:09:51.856 Telemetry V] < #1 {Id=1 Result={CanCollectPII=False} HandlingTimes=[20]}
[2018-10-10 20:09:51.886 Agent V] > #1 {Id=2 Name=version.exchangeSettings Arguments={}}
[2018-10-10 20:09:51.899 Agent V] < #1 {Id=2 Result=<null> HandlingTimes=[12]}
[2018-10-10 20:09:51.899 Agent.Rpc.Auth V] > #1 {Id=3 Name=auth.loginWithCachedToken Arguments={}}
[2018-10-10 20:09:51.919 Agent.Auth V] secret_password_lookup_sync((default), (default)) => 0
[2018-10-10 20:09:51.921 Agent.Rpc.Auth V] < #1 {Id=3 Result=<null> HandlingTimes=[21]}
[2018-10-10 20:09:52.236 Agent.Proxy W] Connecting to <https://insiders.liveshare.vsengsaas.visualstudio.com/c147640a> via proxy failed with exception System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, ExceptionDispatchInfo exception)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.PartialFrameCallback(AsyncProtocolRequest asyncRequest)
--- End of stack trace from previous location where exception was thrown ---
   at System.Net.Security.SslState.ThrowIfExceptional()
   at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
   at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult)
   at System.Net.Security.SslStream.<>c.<AuthenticateAsClientAsync>b__47_1(IAsyncResult iar)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.ConnectHelper.EstablishSslConnectionAsyncCore(Stream stream, SslClientAuthenticationOptions sslOptions, CancellationToken cancellationToken)
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at System.Net.Http.HttpConnectionPool.CreateConnectionAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at System.Net.Http.HttpConnectionPool.WaitForCreatedConnectionAsync(ValueTask`1 creationTask)
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage request, Boolean doRequestAuth, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
   at Microsoft.Cascade.Agent.DefaultWebProxy.ConnectToUriAsync(Uri targetUri, CancellationToken cancellationToken) in E:\A\_work\64\s\src\Agent\DefaultWebProxy.cs:line 81
[2018-10-10 20:09:54.222 Telemetry V] > #1 {Id=4 Name=telemetry.initialize Arguments={}}
[2018-10-10 20:09:54.222 Telemetry V] < #1 {Id=4 Result={CanCollectPII=False} HandlingTimes=[0]}
[2018-10-10 20:09:54.223 Agent.Rpc.Auth V] > #1 {Id=5 Name=auth.loginWithCachedToken Arguments={}}
[2018-10-10 20:09:54.225 Agent.Auth V] secret_password_lookup_sync((default), (default)) => 0
[2018-10-10 20:09:54.225 Agent.Rpc.Auth V] < #1 {Id=5 Result=<null> HandlingTimes=[1]}
[2018-10-10 20:09:54.226 Agent.Rpc.Auth V] > #1 {Id=6 Name=auth.getLoginUri Arguments={}}
[2018-10-10 20:09:54.227 Agent.Rpc.Auth V] < #1 {Id=6 Result={} HandlingTimes=[0]}
[2018-10-10 20:10:14.038 Telemetry V] > #1 {Id=7 Name=telemetry.initialize Arguments={}}
[2018-10-10 20:10:14.038 Telemetry V] < #1 {Id=7 Result={CanCollectPII=False} HandlingTimes=[0]}
[2018-10-10 20:10:14.039 Agent.Rpc.Auth V] > #1 {Id=8 Name=auth.loginWithCachedToken Arguments={}}
[2018-10-10 20:10:14.041 Agent.Auth V] secret_password_lookup_sync((default), (default)) => 0
[2018-10-10 20:10:14.041 Agent.Rpc.Auth V] < #1 {Id=8 Result=<null> HandlingTimes=[1]}
[2018-10-10 20:10:14.042 Agent.Rpc.Auth V] > #1 {Id=9 Name=auth.getLoginUri Arguments={}}
[2018-10-10 20:10:14.042 Agent.Rpc.Auth V] < #1 {Id=9 Result={} HandlingTimes=[0]}
[2018-10-10 20:10:47.848 Telemetry V] > #1 {Id=10 Name=telemetry.initialize Arguments={}}

Are both of you behind a proxy by chance?
@norrs, at least on Debian 9, libssl1.0.2 works fine from what I have seen.  Which exact distro is this? I can see it's Debian / apt based, but which one?
@thomasdarimont It does look like you are missing libssl1.0.x.  Which exact distro is this?  It looks like Fedora 28.
@nandiniYeltiwar @Priya91 The bug I know we have we were not properly detecting when libssl1.0.x was missing and triggering the dependency installer.  I know for a fact this happens on openSUSE Leap 15.  There's a telltale "info" (not error) message about no suitable version of libssl in the digostic logs along with a SIGABRT agent termination.  However, this particular issue didn't repro on base Fedora and Debian - but are theoretically possible on other downstream variations.  Off hand, neither of these look like that problem.

@Chuxel yes this is Fedora 28 and I'm not behind a proxy.
I have libssl on my machine:
/usr/lib/libssl.so.1.1
/usr/lib/libssl.so.1.1.0i
/usr/lib/libssl3.so

/usr/lib64/libssl.so
/usr/lib64/libssl.so.1.0.0
/usr/lib64/libssl.so.1.0.2
/usr/lib64/libssl.so.1.0.2o
/usr/lib64/libssl.so.1.1
/usr/lib64/libssl.so.1.1.0i
/usr/lib64/libssl.so.10
/usr/lib64/libssl3.so

Hmmm. Things work without issue in my Fedora 28 install.
@Priya91 @nandiniYeltiwar What version of .NET Core runtime does Live Share ship with right now.  This sounds like at least one of these issues could be this issue that supposedly shipped with 2.1.3:
https://github.com/dotnet/corefx/issues/30388
...or...
https://github.com/dotnet/corefx/issues/29942
One of the comments suggested running:
sudo update-ca-certificates  --fresh on Ubuntu to clean out potential bad certs.

@Chuxel : As mentioned under "Other information", my distro version of Debian is sid. https://www.debian.org/releases/sid/ - think of it as arch linux, rolling distro.
I've tried sudo update-ca-certificates --fresh without any luck already.
norangshol@enceladus:~$ openssl s_client -connect insiders.liveshare.vsengsaas.visualstudio.com -port 443
CONNECTED(00000005)
depth=2 C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root
verify return:1
depth=1 C = US, ST = Washington, L = Redmond, O = Microsoft Corporation, OU = Microsoft IT, CN = Microsoft IT TLS CA 2
verify return:1
depth=0 CN = *.liveshare.vsengsaas.visualstudio.com
verify return:1
---
Certificate chain
 0 s:CN = *.liveshare.vsengsaas.visualstudio.com
   i:C = US, ST = Washington, L = Redmond, O = Microsoft Corporation, OU = Microsoft IT, CN = Microsoft IT TLS CA 2
 1 s:C = US, ST = Washington, L = Redmond, O = Microsoft Corporation, OU = Microsoft IT, CN = Microsoft IT TLS CA 2
   i:C = IE, O = Baltimore, OU = CyberTrust, CN = Baltimore CyberTrust Root
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIG3jCCBMagAwIBAgITIAABI4SQlT/nKUujMgAAAAEjhDANBgkqhkiG9w0BAQsF
ADCBizELMAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcT
B1JlZG1vbmQxHjAcBgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjEVMBMGA1UE
CxMMTWljcm9zb2Z0IElUMR4wHAYDVQQDExVNaWNyb3NvZnQgSVQgVExTIENBIDIw
HhcNMTcxMTA4MjIxNDI1WhcNMTkxMTA4MjIxNDI1WjAxMS8wLQYDVQQDDCYqLmxp
dmVzaGFyZS52c2VuZ3NhYXMudmlzdWFsc3R1ZGlvLmNvbTCCASIwDQYJKoZIhvcN
AQEBBQADggEPADCCAQoCggEBAM1FaYiPXvmV5s3EVLh4vHx8BVMHNakrBVqY1dpW
kld9QlrO5tYXyPU4pXZT2x6EuC4BglwAU5nAZDPZ4Aexxe0+b2oZH8NkpQ8SSvQV
Fq4mmuNw0WrZehDhEq8AjGrziFMacQcTfIFnnpnHkM/WpIj8gXd8NvNUD9DBMY5A
DUGPARV0vk7p2bhnCikE9SNOOMl1PMhveXjagqQM1HQxrnEJqg6Xb1p+s5Qqhu9e
LiOxGpHF+04/6rWsgANYE7FKa0ExK+tTQFQKNQgIa1PVT1lLX79WZWde4P2OezuI
LdDXVeq1J9LHadW8b2UCd1zSodLFMQpQZVIu1yHmu3Rzh10CAwEAAaOCApIwggKO
MB0GA1UdDgQWBBTmyaoRW9lXQ7bbVeZl4ZiZ9O66uTALBgNVHQ8EBAMCBLAwHwYD
VR0jBBgwFoAUkZ47RGw9V5xCdyo010/RzEqXLNowgawGA1UdHwSBpDCBoTCBnqCB
m6CBmIZLaHR0cDovL21zY3JsLm1pY3Jvc29mdC5jb20vcGtpL21zY29ycC9jcmwv
TWljcm9zb2Z0JTIwSVQlMjBUTFMlMjBDQSUyMDIuY3JshklodHRwOi8vY3JsLm1p
Y3Jvc29mdC5jb20vcGtpL21zY29ycC9jcmwvTWljcm9zb2Z0JTIwSVQlMjBUTFMl
MjBDQSUyMDIuY3JsMIGFBggrBgEFBQcBAQR5MHcwUQYIKwYBBQUHMAKGRWh0dHA6
Ly93d3cubWljcm9zb2Z0LmNvbS9wa2kvbXNjb3JwL01pY3Jvc29mdCUyMElUJTIw
VExTJTIwQ0ElMjAyLmNydDAiBggrBgEFBQcwAYYWaHR0cDovL29jc3AubXNvY3Nw
LmNvbTA+BgkrBgEEAYI3FQcEMTAvBicrBgEEAYI3FQiH2oZ1g+7ZAYLJhRuBtZ5h
hfTrYIFdhNLfQoLnk3oCAWQCARYwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUF
BwMBME0GA1UdIARGMEQwQgYJKwYBBAGCNyoBMDUwMwYIKwYBBQUHAgEWJ2h0dHA6
Ly93d3cubWljcm9zb2Z0LmNvbS9wa2kvbXNjb3JwL2NwczAnBgkrBgEEAYI3FQoE
GjAYMAoGCCsGAQUFBwMCMAoGCCsGAQUFBwMBMDEGA1UdEQQqMCiCJioubGl2ZXNo
YXJlLnZzZW5nc2Fhcy52aXN1YWxzdHVkaW8uY29tMA0GCSqGSIb3DQEBCwUAA4IC
AQANt1cMH5fDx9iIWSjoAZkCAGqoGjuK2/GxAwDto45gevMegpVS7IOF+eT2hYk8
0RJcRtS+TN+Y2r3OAUZ9cFq7teBfl3R75ooBevBa56AjMKE1BWnoqbO0385JPWRi
sl2XUR9hHWqyeBkDXllR1pDibN68dQWCJgikIeHc2wgzt4DOqO9oHHSCKOnVTz0v
BIS/rsttV/V9OforYiiaBdxhL8CZrocCKpurtiQu5lcTFw0s72dn7SRFTHwr05ia
yhwIaJ+mxZc1OzZzT8nliOHrQMb/51Tmc4GFR73eA0JdXpURSC2AgcSItSCZSsuM
yJJs4M159tisMX+VTGr6aHvrsgLmyM0OsthnXGlXJvrf9SHxV5xfkXxnyxP2Ei7j
jxLBS2TnelrugkcjIOB7jYbFts00pENqAE2Ri5shVr9D9PeDdBfhciVTH5lUu1F5
iTi9JYvKV2RhgjT63Ki8p6CvWRB/DC5Tqq6A+7ZDGzEahEzkKEJJS6UmeD0M0dp+
aQ5m2IkRRnShy7H8fwqXkpjwT/oCEaqFBl1BP+UP4LvA+gl2LXEJsj2Lwy53PfIw
JPCuuqwmtV1dNfBqXKzTf9XlPXgAKRMRRbZvwb8mWO0spduSdD527Vo1U7VvNw6n
CJ1N7iC0WxlRokKhsI32naghz3TiFLdYso5Mnl3QPxdeXg==
-----END CERTIFICATE-----
subject=CN = *.liveshare.vsengsaas.visualstudio.com

issuer=C = US, ST = Washington, L = Redmond, O = Microsoft Corporation, OU = Microsoft IT, CN = Microsoft IT TLS CA 2

---
No client certificate CA names sent
Peer signing digest: SHA512
Peer signature type: RSA
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 3740 bytes and written 463 bytes
Verification: OK
---
New, TLSv1.2, Cipher is ECDHE-RSA-AES128-GCM-SHA256
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-AES128-GCM-SHA256
    Session-ID: 2A1572B0AE22E6657369AE611115FC4861131DC09869D87B1FCD20EE3DBB4CFC
    Session-ID-ctx:
    Master-Key: 5B680C2085D872B2AA3C4623DCD7D504327A632946F6693C8305F5C70A35099B1D2FCAFA202640679A757BCD51592A01
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: yes
---

DONE

So openssl s_client verifies it as well, but I'm unsure how this works with dotnet stuff as I've never played around with dotnet stuff before.
sudo update-ca-certificates --fresh >/tmp/logg 2>&1 && find /etc/ssl/certs/   >>/tmp/logg 2>&1

Clearing symlinks in /etc/ssl/certs...
done.
Updating certificates in /etc/ssl/certs...
133 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

Updating Mono key store
Linux Cert Store Sync - version <IP_ADDRESS>
Synchronize local certs with certs from local Linux trust store.
Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed.

I already trust 133, your new list has 133
Import process completed.
 How to verify mono key store?

Resolving as a duplicate of #1086.

@lostintangent : you have way more debugging information in this ticket..

Also you have a way too generic error message, this bug title probably should be renamed to point on the issue in regards of mono ssl key store.

Refering to another https://github.com/MicrosoftDocs/live-share/issues/1105#issuecomment-443468674 is just weird.


Model State should have values for greedy model binders as well.

Currently HeaderModelBinder and BodyModelBinder do not populate the model state by calling SetModelValue, for success cases. This means we cannot do a ajax post which uses the populated value.

Based on the tests that are disabled with this bug as the reason, problem is much more broad. All values bound from user input should have ModelState entries. This affects ByteArrayModelBinder, FormCollectionModelBinder, and FormFileModelBinder as well as the two mentioned in the original description (BodyModelBinder and HeaderModelBinder). So, "type-matching" as well as "greedy" binders.

c4fa402 and 715a0b6
further cleanup in a170a4e


[Launcher]: Replicate ZK Store to HDFS Store

Coverage increased (+0.4%) to 49.883% when pulling 3fb9609856b31c656060ff0fad4641517e64e28e on yqwang/launcher-dev into e2209be844ce40eb102ef25fb64ef681d7965f92 on master.


Add pad-pack and loop peel based transform dialect

Can we turn the transform dialect scripts here into tests? Basically run this using iree-opt --iree-transform-dialect-interpreter and make it a check test?
We should do that for all the scripts here, but let's start with this one.
Related: I have been playing around with this as well,

I have been looking at non divisible shapes. After working through it a bit , the pad bufferization is a mess. It generates a fill and copy and is unmanageable. So in my draft I moved back to pack at both levels.
I will send that out as a draft on top of this PR.

I added lit tests for transform dialect scripts.
I still want to keep matmul_fill_spec_pad_pack_peel.mlir in case we want to revisit it in the future.
I haven't pushed your transform dialect script, because I think it will need your hack codes in llvm-project? Probably add it when you have the upstream codes merged?


$${variable} escapes still highlight as interpolation

In nix $${...} escapes the interpolation and includes into string ${...} verbatim, rather than trying to evaluate the expression within the curly braces.
However (at least in nvim) this is highlit as the first $ being a string content and following ${...} as the regular interpolation.

I've just tried out tree-sitter-nix in conjunction with nvim-treesitter to decide whether to use it to replace vim-nix, but found that it did not provide highlighting for string interpolation (i.e. an expression like "something/${some.nix.here}" had the entire string still highlighted as a string literal.
Are dollar-curly expressions highlighted differently from you using this?
(I've only started trying nvim-treesitter today so it's possible I'm not configuring anything properly, so take this with a handful of salt.)

Ah, I wasn't aware of this; sure enough:
nix-repl> b = "b"

nix-repl> "a${b}c"
"abc"

nix-repl> "a$${b}c"
"a$${b}c"

nix-repl> "a$$${b}c"
"a$$bc"

nix-repl> ''a${b}c''
"abc"

nix-repl> ''a$${b}c''
"a$${b}c"

nix-repl> ''a$$${b}c''
"a$$bc"

I'll get to this a little later today. Should be an easy fix in scanner.c.
Thanks for bringing this to my attention!

@chuahou this is not exactly the right place for support, but yes, I do have useful highlighting with treesitter. My only guess is that you haven't set up treesitter correctly. It is not super trivial to do if you want to do so in Nix-land.

I see, these are the two parts I've messed up:

the \$[^\{\"\\] pattern in https://github.com/NixOS/nix/blob/1af3f63be53018ab764090acab36e7c5401609cd/src/libexpr/lexer.l#L161
the \$[^\{\'] pattern in https://github.com/NixOS/nix/blob/1af3f63be53018ab764090acab36e7c5401609cd/src/libexpr/lexer.l#L179

@nagisa Yeah, I know, I wasn't asking for support, sorry if it came off that way. I simply thought that string interpolation highlighting wasn't supported by tree-sitter-nix, and wanted to check (in the context of the issue) that the interpolation highlighting you talked about was indeed due to tree-sitter-nix.

@nagisa Should be fixed now. Let me know if you spot anything else!


Laravel 5.3 gatherRouteMiddlewares() change

In Laravel 5.3, gatherRouteMiddlewares() in the src/Illuminate/Routing/Router.php has been changed to gatherRouteMiddleware(), causing API to fail. This PR is addressing that. Here's commit history on Router.php:
https://github.com/laravel/framework/commit/ce0d33d602f65a64ff531744b7058763823cbb00#diff-66c4eb54eb5af7de5e493b416e13991dL653

Wouldn't this just break support for Laravel 5.1 and 5.2?

@crynobone oh damn. Let me correct this later today. I forgot to add a method_exists() check. Thanks.

PR #1152 has these changes, plus the missing method_exists check. Gonna close this one out since the other is a little more up-to-date. Thank you though @Dartanjan


Add example code in Swift

The functionality needs to be same as here: https://github.com/Plant-id/Plant-id-API/blob/master/python/sync_identification_example.py
To get free API key for testing fill in this form & mention this issue.
Feel free to ask questions.

@Krejdom
Added simple example in PR https://github.com/flowerchecker/Plant-id-API/pull/28

@Krejdom
Can we count this enhancement issue as resolved now?


Store formatting configuration from DidChangeConfiguration

In order to do document/selection formatting, the language server needs to grab all of the same configuration that the extension is using and store it for use. Right now, DidChangeConfiguration only stores analysis-related configuration, and needs to be extended.

Closing per #10.


Possible fragment bug introduced in v1.13.0

Describe the bug
As of v1.13.0 i'm getting GraphQL error: Unknown fragment "Me". Looks like if a fragment has the same name as a query the fragment is not included in the operation. If I rename Me to MeFoo it will add MeFoo to the operation.
To Reproduce
Steps to reproduce the behavior:

My GraphQL schema:

fragment Staff on Staff {
    id
    username
    name
}

fragment Me on Staff {
    settings
    permissions
}

query Me {
    staff {
        ...Staff
        ...Me
    }
}

My GraphQL operations:

query Me {
    staff {
        ...Staff
        ...Me
        __typename
    }
}

fragment Staff on Staff {
    id
    username
    name
    __typename
}

#
# <------ Missing 'Me' fragment.
#

My codegen.yml config file:

overwrite: true
schema:
  - "http://localhost.loc/graphql":
documents: "./src/app/**/*.graphql"
generates:
  src/generated/graphql.ts:
    plugins:
      - "typescript"
      - "typescript-operations"
      - "typescript-apollo-angular"

Expected behavior

Environment:

OS: Windows 10
@graphql-codegen/1.13.0:
NodeJS: v13.10.1

Additional context

I have the same problem

@xiaoyu-tamu @tuurbo thank you for reporting this.
Can you please share a reproduction in codesandbox / repo? I tried to add a failing tests, but couldn't reproduce the error you mentioned.

I have the same issue, although I'm using typescript-react-apollo instead of typescript-apollo-angular.
After updating the graphql-codegen packages to 1.13.0, it looked like this in my diffs:
 export const ExampleDocument = gql`
 query example {
   example {
     ...someFragment
   }
 }
-${someFragmentDoc}
 `;

(The fragment document is not included in the string anymore)
And it seems that when the client now performs this query, it uses the fragment inside the query with the spread operator, but doesn't send the fragment definition with it.

Same here, @rynti's explanation matches what i am getting too
Error:
'GraphQLError: Unknown fragment "Me".',
  '    at Object.FragmentSpread (/<path>/node_modules/graphql/validation/rules/KnownFragmentNames.js:29:29)',

Sounds strange, but for me it seems to be only happening on the MeFragment, all other queries are fine??
this is the diff after generating when on v1.13.0 ...
     ...Me
   }
 }
-    ${MeFragmentDoc}`;
+    `;

I found out how to reproduce this: The bug occurs when the fragment has the same name as the query.
I set up a project on codesandbox.io: https://codesandbox.io/s/objective-chandrasekhar-l9nso
I wasn't able to make the graphql generator work in the sandbox, so you have to download the project as a ZIP and run npm install & npm start yourself.
Here are the steps to reproduce the bug:

Download the sandbox as a ZIP from https://codesandbox.io/s/objective-chandrasekhar-l9nso (File -> Export to ZIP)
Run npm install (This installs graphql-codegen 1.13.0)
Run npm start (This generates the graphql TS file for the schema)
Check out the out/generated-graphql.ts file and you will notice that the notWorkingExample fragment is missing in the NotWorkingExampleDocument, however the workingExample fragment is included in the WorkingExampleDocument.
Inside the package.json, change the graphql-codegen dependency versions to 1.12.2
Run npm install again (This installs graphql-codegen 1.12.2)
Run npm start again (Again, this generates the TS file for the schema)
Notice how the generated-graphql.ts file now has the notWorkingExample fragment included in the NotWorkingExampleDocument.

@rynti we have a ready-to-use codesandbox template for the codegen, it could be found here: https://codesandbox.io/s/github/dotansimha/graphql-code-generator-issue-sandbox-template (and it's also part of the issue template)
I think I managed to find and fix the issue, see: https://github.com/dotansimha/graphql-code-generator/pull/3621
@tuurbo @rynti @xiaoyu-tamu can you please try the alpha version 1.13.1-alpha-6bbc3dae.9?

Can confirm that the issue doesn't occur anymore with version 1.13.1-alpha-6bbc3dae.9, thank you for the quick fix! 🎉👍

@dotansimha alpha version works for me. Thanks!

Fixed in v1.13.1 🎉

Unfortunately, this is still happening in 1.13.1. Could we reopen this issue, please? Happy to provide details if it would be useful.

Unfortunately, this is still happening in 1.13.1. Could we reopen this issue, please? Happy to provide details if it would be useful.

I've bumped typescript-operationsto 1.13.1, and this is likewise not working for me

@Waitak @jcardali You should bump all codegen packages together. They are linked together.
If it's still not working for you, please share a reproduction.


EAGLE-346: ClassNotFoundException thrown out when topology is executing

https://issues.apache.org/jira/browse/EAGLE-346

merged, please close


Fix typo where request.method is request.path

There is a similar problem in the docs.

Hi @hubt. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/ok-to-test
I have some deja vu somehow on this change, cc @douglas-reid

@hubt: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
c70b87b6924e50da921b1de4564a6b6e152941cc
link
@istio-testing bazel test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Should we close this ?

/test all

/test all

/test all

/test all

closing but reopen if I'm reading this wrong


!urban: multi-word definitions broken

Try !urban Tom Manderson and you get the definition for "Tom"

discussion from slack


chore: zeebe-operator to 0.0.33

chore: Promote zeebe-operator to version 0.0.33

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Audio comes out choppy

is there any way to improve the audio output?
USER:  Hello?
ASSISTANT: Hello there!
2024-08-20 19:17:38,156 - main - INFO - Time to first audio: 1.694
ASSISTANT: How can I assist you today?
Audio:
H-ow-ca-nai-a-ssi-st-yo-u-to-day?
(Using Zluda emulator and RX 6700XT GPU, had to downgrade torch to 2.3.0)

yup, it is choppy, even when i used H100 on runpod, the way I was able to resolve it a bit was by increasing the value of play_steps_s to 1.0, it should help.

I forgot to mention that can also help. It was also choppy on an H100? That's unexpected! Maybe the connection latency is a bit high there? We tested with a 4090 but it was in our network.

Yeah within the same network, will not have network latency and makes a huge difference.

I forgot to mention that can also help. It was also choppy on an H100? That's unexpected! Maybe the connection latency is a bit high there? We tested with a 4090 but it was in our network.

Same, I also tested on RTX4090 and the audio came out choppy. I have checked the GPU usage and it is under the max of the 4090 card.

yup, it is choppy, even when i used H100 on runpod, the way I was able to resolve it a bit was by increasing the value of play_steps_s to 1.0, it should help.

That did help to remove most choppiness, still some remains. I have not noticed much load on GPU, 6700XT does perfectly fine job.

@jasonngap1 , that's interesting, could you share more details of your setup? If I can figure out what might be happening, I could fix it :)

I think the issue could be because of the use of TCP. UDP/RTP streams would be ideal for audio streams.

yes exactly using tcp does cause latency issues, udp is a better option, using webrtc might be a solution.

I think the issue could be because of the use of TCP. UDP/RTP streams would be ideal for audio streams.
I am having the same issues running on a 36 core Xeon with an RTX 4090 and 256GB of system ram.

My system specs is similar to yours. Strange thing is that when I load in Windows the audio comes out fine. There were much hallucination in the STT transcription but that's another issue.

yeah there might also be a need to get a more robust VAD model, sometimes it even misses the first few spoken words, I also tried to change the parameters for VAD sensitivity, but didn't get much of a difference.

I changed the default speech_pad_ms to 500ms to try to get whisper to transcribe audio still even when the VAD fails.

Btw, here are some of my learnings to share:

Using TCP protocol for transmission of audio from server (on a remote) to client takes about 2 sec using MeloTTS.

I successfully switched to UDP and the results were amazing:

Less than 10ms for a 1-sec WAV file
About 10ms for a 4-5 sec WAV file
About 20ms for an 11-sec WAV file

Switching to a socket-based server using UDP could be a great approach to remove audio choppiness and reduce latency. However, packet transfer handling needs to be robust, as I experienced some noise while transferring a large WAV file. I think transferring very small chunks and stitching them up on the client side could be a great alternative to eliminate noise.

I didn't look at the socket code too much, is it TCP by default? can we change it to be UDP?

Typically with VoIP protocols we use RTP which is a UDP protocol, and the payload is usually 20ms of audio every 20ms.

Hey there, I am looking into improving the client-server connection set up. Indeed UDP seems like a more suitable option yet handling lost and out of order packets is not trivial. I am not finding any good RTP implementation to build upon for this (found this one, yet necessity to extract the RTP part from it). Do you have a good pointer here @joecryptotoo ?

@eustlb maybe just hook it up to FreeSWITCH with a custom FS module. Let FS handle the VoIP stuff. Then you would be able to route phone calls to/from the AI agent.

This module may work.
https://github.com/jambonz/freeswitch-modules/tree/main/mod_audio_fork

Here we go! https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Modules/mod_unimrcp_6586728/


[BUG] User not found when clicking on achievements

Dunno when this was introduced. Only happens within the UI. Functionality is fine.

https://github.com/loftwah/linkarooie/pull/76


Rework RBAC resources to work with sensu-go changes

Pull Request Checklist

Description

Refactor sensu_role
Add sensu_role_binding
Add sensu_cluster_role
Add sensu_cluster_role_binding
Related Issue

Fixes #1016
Motivation and Context

Sensu-go rewrote the RBAC resources and this PR is necessary to work with upstream changes.  Upstream change: https://github.com/sensu/sensu-go/pull/2338.  This pull request will not work until that PR is merged and released as RPM.  Also currently testing in Vagrant is broken until I get confirmation on subjects data structure since docs do not match sensu-go code.  The docs for RBAC changes are already published: https://docs.sensu.io/sensu-go/5.0/reference/rbac/
How Has This Been Tested?

In Vagrant sensu-backend box with binaries built from source with upstream pull request applied.

PR updated now that know how subjects should behave, just bug in docs, issue opened: https://github.com/sensu/sensu-docs/issues/922
Just waiting on RPMs and can test with beaker.  So far ad-hoc tests are looking good in Vagrant.

Added commit that removes sensu_extension since removed from upstream, this will fix #1019.  My hope is that when next set of RPMs are released the tests in this PR will begin passing.

Added commits:

Switch repos to stable (replaces #1020)
Fix package names to match those in stable repos
Manage backend state-dir which now seems to be necessary

Some tests may pass but still seeing issues in local executions of beaker tests.

Added commits:

Remove subdue_days from sensu_check, removed from sensu-go (https://github.com/sensu/sensu-go/pull/2377)
Remove when_days from sensu_filter, when removed from filters in sensu-go (https://github.com/sensu/sensu-go/pull/2385)
Handle sensuctl asset list returning null when no assets

Other commits added are to fix acceptance tests after running into issues with stable sensu-go packages.  Edited the original RBAC commit to fix issues hit during local testing.
The failing tests are because stable repos have no packages for Debian 8, Debian 9 and Ubuntu 14.04.


Replacement of hard-coded SQL query for issue #601

Dear django-helpdesk developers,
The error I was having was
ProgrammingError: (1146, "Table 'projectdev1.helpdesk_ticket' doesn't exist")
where projectdev1 is one of the databases that are being used by our project. This database is not used for storing django-helpdesk tables, instead it is in projectdev2. The cause of the issue appears to be that the router does not re-direct the hard-coded SQL queries to projectdev2 and so they try to reach helpdesk tables on projectdev1.
I removed the unused dash_tickets variable and its calculation (lines 165-168) and modified the case where it is used so that now it relies on model query APIs (lines 1106-1130). This solved the problem for our project. I hope it helps others as well.

Codecov Report

Merging #603 into master will decrease coverage by 0.26%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #603      +/-   ##
==========================================
- Coverage   62.58%   62.32%   -0.27%
==========================================
  Files          38       38
  Lines        3547     3541       -6
  Branches      557      556       -1
==========================================
- Hits         2220     2207      -13
- Misses       1174     1182       +8
+ Partials      153      152       -1

Impacted Files
Coverage Δ

helpdesk/views/staff.py
40.56% <100%> (-0.19%)
:arrow_down:

helpdesk/lib.py
65.3% <0%> (-6.13%)
:arrow_down:

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 fef0808...764c55e. Read the comment docs.


Set tenant MTU to 1500 for shift on stack

For enabling the communication between VMs and considering that the MTU for the tenant network that openshift-installer creates is 1442, the tenant VLAN should be set to 1500 so the geneve tunnel works as expected.
This change is making the tenant vlan MTU configurable and it is setting it to 1500 on the shift-on-stack-overrides.yml
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/ok-to-test

/approve
/lgtm


About and legal overlay | "activeTabLabel"

Prerequisites

[X] I have read the Contributing Guidelines.
[X] I have not leaked any internal/restricted information like screenshots, videos, code snippets, links etc.

What happened?
"activeTabLabel" seems not working as expected.
Attribute: active-tab-label
Wanted Tab 2 to be selected by default in the below given Code Snippet.
What type of frontend framework are you seeing the problem on?
Angular
Which version of iX do you use?
2.4.0
Code to produce this issue.
<ix-application>
<ix-application-header>

</ix-application-header>
<ix-menu #menu>
<ix-menu-about [activeTabLabel]="'Tab 2'" >
<ix-menu-about-item label="Tab 1">Content 1</ix-menu-about-item>
<ix-menu-about-item label="Tab 2">Content 2</ix-menu-about-item>
</ix-menu-about>
</ix-menu>
</ix-application>

Duplicate #1182


Contention between optional option and required parameter

The example I am using has three options followed by one required parameter.  The options could be used in any order.  One of the options is a String with arity="0..1".  This is an optional string.  When this option is used as the last of the options (with the option used but a value not specified) followed by the required String parameter, the value which should go to the REQUIRED parameter is going to the OPTIONAL option instead.  MissingParameterException is being thrown.  This is not expected behavior.  I would consider this a bug.  I can provide additional details if the scenario is unclear.  Thank you.

Hi, yes, this is how picocli currently handles options with an optional parameter.
The picocli parser is “greedy” when it handles optional parameters: it looks at the value following the option name, and if that value is likely to be a parameter (not another option or subcommand) then picocli will process the value as a parameter for that option.
(See also a similar discussion on https://github.com/remkop/picocli/issues/979.)
We could try to improve the logic for determining if a value is “likely to be a parameter”, but this is not straightforward. It requires looking forward at all remaining arguments to see if all required positional parameters (there may be more than one) will get a value. This means parsing all the way to the end before deciding on how to treat the value following an optional option: so we would need to implement a backtracking parser, and while this is on the TODO list, it may take a while before I can get to it.
Possible Solutions/Workarounds
One way to deal with this is to point out this ambiguity in the documentation of your application. End users can disambiguate the input by specifying either the -- end-of-options delimiter or another option between the optional option and the required parameter. It is after all quite possible that the end user intended the value to be a parameter for the option and actually did forget to specify the required positional parameter.
An alternative you could consider is removing the ambiguity from your application. For example, an optional option could be replaced by a boolean option plus an option that requires a parameter.

So, the optional option has three possibilities:

Not used (-x was not used)
Used without a value (-x)
Used with a value (-x value)

These are all valid for arity 0..1.
In throwing a MissingParameterException, your logic is throwing out #2 as a valid possibility.  To me, that translates as a bug because it goes against the specification.

I will update the documentation to clarify what picocli's behaviour is in this scenario. I don't think it is mentioned anywhere at the moment.

Until https://github.com/remkop/picocli/issues/980 is implemented, the best I can do is clarify the current behaviour.
I added section Options with an Optional Parameter to the user manual.

Closing this issue.
This is a known and (thanks to your feedback) documented drawback of defining commands that have both an option with an optional parameter and a positional parameter.
However, picocli now offers parser plugins for custom parameter processing.
The documentation for the IParameterPreprocessor plugin has an example showing a solution for this exact use case.
Hopefully that offers sufficient flexibility for people to build applications meeting their requirements.


tracker: 0.17 release

list of items to add to the new release since changing maintainer(s)
Required

[ ] nist data #195
[ ] nalgebra

[ ] update to ^0.32 will be chosen #187 #162
consistent multivariate API with nalgebra

[ ] MultivariateNormal #209
[ ] Dirichlet
[ ] MultivariateStudentT

[ ] changelog updates
[ ] fix erroneous docs

[ ] literal reference to incorrect versions

[ ] others TBD

Option

[ ] review CI, #207

[ ] clippy
[ ] rustc fail on warnings

[ ] feature for multivariate_nalgebra
[ ] others TBD

Note that while the NIST dataset is still in the repo, #214 at least removed it from the crates.io package. So the remaining part of the issue should not be a blocker for a new package version/release.
The CI changes don't need to be a version blocker either, they're almost exclusively non-functional changes (formatting, code style). On the other hand, they're relatively easy to fix.
I guess it would be nice to have a consistent nalgebra API, but IMHO, I'm not sure it's worth holding back a release for. This is subjective, but the current API is not broken or untenable and a new release could be productive for these API discussions because of renewed attention on the project. ATM, it's only a small amount of people participating in these API-related discussions.

More input from users would be beneficial for the discussion on API. Thanks for the suggestion, and I think I'll take it.


limit hare outputs cache

Overview / Motivation
we introduced hare.Hare which is basically the orchestrator that lets the whole system read hare results and the system tick to start one.
We want to keep track of last layers we've processed and before our map gets full, remove old output based how far it is from the present.
The Task
Limit the size of the map and before an output is collected check if we have enough space to insert the new output, otherwise remove oldest output.
Implementation Notes
there are some todos in hare.go that describe more about that task.
Contribution Guidelines
Important: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter dev channel

Introduce yourself on go-spacemesh dev chat channel - ask our team any question you may have about this task
Fork branch develop to your own repo and work in your repo
You must document all methods, enums and types with godoc comments
You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature
When ready for code review, submit a PR from your repo back to branch develop
Attach relevant issue to PR

this was already done in #418


Accompanist is crashing  java.lang.NoSuchMethodError: No static method rememberPagerState on Release

Describe the bug
Accompanist is crashing the minified proguard app in release version 0.20.0 using compose version 1.0.5.
To Reproduce
Steps to reproduce the behavior:

Import Accompanist
Create a minified r8/proguard release
Open the app
See error

Expected behavior
It Shouldn't crash.
Screenshots?
If applicable, add screenshots to help explain your problem.
Environment:

Android OS version: API 30
Device: Emulator
Accompanist version: 0.20.0

Additional context
StackTrace
Process: com.careem.acma.qa, PID: 5393
    java.lang.NoSuchMethodError: No static method rememberPagerState(IIFIZLe1/i;II)Ls51/g; in class Ls51/i; or its super classes (declaration of 's51.i' appears in /data/app/com.example.qa-EMuA8-jvfzLacCR6fzoRFA==/base.apk!classes4.dex)
        at kz0.b.a(:41)
        at kz0.b$e.a(Unknown Source:9)
        at kz0.b$e.invoke(Unknown Source:9)
        at e1.z0.g(:140)
        at e1.j.J0(:2158)
        at e1.j.g(:2404)
        at e1.j$h.invoke(:2585)
        at e1.j$h.invoke(:2571)
        at e1.o1.c(:234)
        at e1.n1.i(:1)
        at e1.j.i0(:2571)
        at e1.j.I0(:2547)
        at e1.o.b(:620)
        at e1.a1.W(:786)
        at e1.a1.D(:105)
        at e1.a1$j$a.a(:456)
        at e1.a1$j$a.invoke(:425)
        at androidx.compose.ui.platform.f0$c.doFrame(:34)
        at androidx.compose.ui.platform.d0.P1(:109)
        at androidx.compose.ui.platform.d0.J1(:41)
        at androidx.compose.ui.platform.d0$d.doFrame(:69)
        at android.view.Choreographer$CallbackRecord.run(Choreographer.java:964)
        at android.view.Choreographer.doCallbacks(Choreographer.java:790)
        at android.view.Choreographer.doFrame(Choreographer.java:721)
        at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:951)
        at android.os.Handler.handleCallback(Handler.java:883)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at android.os.Looper.loop(Looper.java:214)
        at android.app.ActivityThread.main(ActivityThread.java:7356)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)

According to release notes of the Accompanist you need to use 0.20.2 which is compatible with Compose 1.0.5.
Did you try to use 0.20.2?

Yes we tried it as well. :(

I'm getting the same crash. If you put the library in the recommended version (0.20.2) the error keeps happening. I'm using compose in version 1.0.5.

It would be nice if someone can share the project where it is reproducible (if you don't want to share it publicly you can send it to my email<EMAIL_ADDRESS>as I tried to use rememberPagerState with Compose 1.0.5 and Accompanist 0.20.2 in my sample project and it is not crashing in the release build.

It would be nice if someone can share the project where it is reproducible (if you don't want to share it publicly you can send it to my email<EMAIL_ADDRESS>as I tried to use rememberPagerState with Compose 1.0.5 and Accompanist 0.20.2 in my sample project and it is not crashing in the release build.

@andkulikov
I got confused with stacktrace. The stacktrace I was getting was related to another error, but it had the same exception:
E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.studiosol.dojo.compose, PID: 20098
    java.lang.NoSuchMethodError: No static method AnimatedContent(Landroidx/compose/animation/core/Transition;Landroidx/compose/ui/Modifier;Lkotlin/jvm/functions/Function1;Landroidx/compose/ui/Alignment;Lkotlin/jvm/functions/Function4;Landroidx/compose/runtime/Composer;II)V in class Landroidx/compose/animation/AnimatedContentKt; or its super classes (declaration of 'androidx.compose.animation.AnimatedContentKt' appears in /data/app/com.studiosol.dojo.compose-3MdDmITAsMaDnU7SsR3Ocw==/base.apk)
        at com.google.accompanist.navigation.animation.AnimatedNavHostKt.AnimatedNavHost(AnimatedNavHost.kt:242)
        at com.google.accompanist.navigation.animation.AnimatedNavHostKt.AnimatedNavHost(AnimatedNavHost.kt:91)
        at com.studiosol.dojo.compose.presentation.MainActivity$onCreate$1$1$1.invoke(MainActivity.kt:42)
        at com.studiosol.dojo.compose.presentation.MainActivity$onCreate$1$1$1.invoke(MainActivity.kt:40)
...

In this case I managed to solve this by putting compose in version 1.1.0-beta03 and accompanist in version 0.21.3-beta. Thanks!

@jibraniqbal-careem
@dmitrytavpeko
Your case should be similar to mine, I recommend checking all dependencies related to compose and accompanist and see if they are following the same version. In my case, as I said, I put all that needed compose in version 1.1.0-beta03 and in the case of accompanist in version 0.21.3-beta

I will close it for now. As mentioned already it could be some strange incompatibility between libraries


Feature request: latestMap

I would love a method to is almost like an .switchMap() but the big difference is that it should wait until the latest "project" Observable is completed before it starts the latest "project" Observable.
Why?
When you are working with an api that isn't cancelable and that specific function can only be executed once and have to wait until the callback is executed before you can executed that function/method again and only the lastest value is important.
A use case
When you have a player for instance and want to seek to a current time in playback. Doing multiple seeking at the same time is of course unnecessary and in my case also actually crashes the app (smart tv development). To write this code right now is very complicated. We tried to debounce the seek but this sometimes fails because of slow buffering.
// My desired code
currentTimeChanged$ // A stream that represent a progress bar
  .debounceTime(1000)
  // Should subscribe next latest project when idle.
  // Should not subscribe latest project until previous project is completed.
  .latestMap((currentTime) => {
    return Observable.create((observer) => {
      // player.setCurrentTime can only be executed while not "running"
      player.setCurrentTime(currentTime, () => observer.complete());
    });
  });

Have you looked at concatMap and exhaustMap?

@staltz yes,
concatMap will execute all currentTimeChanged$ in sequence and I'm only interested that the latest value is executed.
exhaustMap will execute seek but won't always execute the latest currentTime depending on timing issues.

It's like a combination between a exhaustMap and a switchMap is what I want.

with let and new pipe-able operator structure introduce in 5.5, we are recommding creating new operator as user-level one (/doc/operator-creation.md@master#publish-your-operator-as-a-separate-library) for now. Core team is discussing about processes of pick / removing core level operator as a separate topic.

@EloB from what I can tell, I think this is auditMap -- if so, you should be able to achieve something similar via source.auditTime(1000).exhaustMap((x) => asyncThing(x))

@trxcllnt I like the name auditMap. I think your example has some timing issues source.auditTime(1000).exhaustMap((x) => asyncThing(x)). If the exhaustMap gets a new emitted value while running asyncThing. Then that value gets lost. It's important that it always runs the last value.
Example: Drag and Drop = DnD
DnD progressbar emits values while dragging -> Seek and wait until finished -> Repeat the process if the DND changed while seek.

I'm not sure about the code above that I written but I really would like something that takes care of this in Rxjs core because the teardowns cannot be async...

This is basically audit. Closing this issue as stale. With pipeable operators users can easily create their own if they have a need.


PR#3350: Update interpolated-strings.md

Mock user PR on conceptual documents, see https://github.com/dotnet/docs/pull/3350/files

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/csharp/language-reference/keywords/interpolated-strings.md
:warning:Warning

Details

docs/csharp/language-reference/keywords/interpolated-strings.md

Line 53: [Warning] Invalid file link:(~/docs/csharp/language-reference/keywords/strings.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/csharp/language-reference/keywords/interpolated-strings.md
:warning:Warning

Details

docs/csharp/quick-starts/hello-world.yml
:warning:Warning

Details

docs/csharp/language-reference/keywords/interpolated-strings.md

Line 53: [Warning] Invalid file link:(~/docs/csharp/language-reference/keywords/strings.md).

docs/csharp/quick-starts/hello-world.yml

[Warning] 7 invalid cross reference(s) "<xref:System.String.Trim%2A>", "<xref:System.String.TrimStart%2A>", "<xref:System.String.TrimEnd%2A>", "<xref:System.String.Replace%2A>", "<xref:System.String.Contains%2A>", "<xref:System.String.StartsWith%2A>", "<xref:System.String.EndsWith%2A>".
[Warning] the value Tutorial is undefined for metadata pagetype

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[CI] Refactor triton-benchmarks.yml

The environment setup for softmax can be reused for GEMM.
Remove some unnecessary environment variables from running GEMM.

https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/10187746673

Can we keep SYCL_PROGRAM_COMPILE_OPTIONS to make XeTLA compile flag taking effect. This have huge performance impact on XeTLA kernel.

Can we keep SYCL_PROGRAM_COMPILE_OPTIONS to make XeTLA compile flag taking effect. This have huge performance impact on XeTLA kernel.

Of course, didn't know why it was there: https://github.com/intel/intel-xpu-backend-for-triton/pull/1753.


Add note about the Alby Hub and redirect users to the hub

nwc.getalby.com gets depreacted

@bumi updated banner style a bit, + whole banner is clickable

oh nice!


ci: add cachix to CI build

Proposed Changes

Add cachix to CI build.

Use ci.bootstrap to bootstrap some tools in the Nix CI container image.

Types of Changes
What types of changes does your code introduce? Put an x in the boxes that
apply

[ ] A bug fix (non-breaking change which fixes an issue).
[ ] A new feature (non-breaking change which adds functionality).
[ ] A breaking change (fix or feature that would cause existing
functionality to not work as expected).
[x] A non-productive update (documentation, tooling, etc. if none of the
other choices apply).

Checklist
Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you're unsure about any of them, don't hesitate to ask. We're here to
help! This is simply a reminder of what we are going to look for before merging
your code.

[x] I have read the
CONTRIBUTING
guidelines.
[x] I have added tests that prove my fix is effective or that my feature
works.
[x] I have added the necessary documentation (if appropriate).

Further Comments

@cmdoret : Still some issues:
https://github.com/cachix/cachix/issues/662


Dojo storage layout

Currently, the Dojo storage layout can be seen as serial. The fields of a model struct are stored in a consecutive order, with data being packed a bit level.
struct MyModel {
    a: u32,
    b: u32,
    c: felt252,
}

// Serialized:
[a, b, c]
// Packed
[packed(ab), packed(c)]

This layout (let's call it serial) has the benefit to be very compact, and can easily support the "one" felt storage model.
However, the downsides are:

Not resistant to upgrade (fields order, field removal), it's an append only model.
Dynamic types like arrays are forced to be "fixed", which induce other constraints.

On Starknet, the storage uses the selector of each field name to ensure each field starts at a different slot in the storage.
The proposal here is to add an other layout to the dojo database: hash.
By leveraging the hashing function, we could replicate how Starknet storage works, without compromising the composability of Dojo database.
#[dojo::model(layout: 'hash')]
struct MyModel {
    a: u32,
    b: ByteArray,
    c: Array<felt252>,
}

// Serialized:
[a, b, c]
// Packed, but each one is packed individually.
[packed(a), packed(b), packed(c)]

Doing so, we gain two major things:

Upgradeability resiliency (fields can be removed, re-ordered).
Dynamic types are now supported.
The downside of this approach is that we pay extra hashing for every single field, regardless of it's size.

The proposal here is to have both layout available in Dojo. The default layout would be switched to hash, to ensure a smooth experience with all dynamic types. And the user can then optimize the storage by switching to serial layout.
Implications:
This change will impact mostly dojo-core, dojo-lang and torii.

dojo-core: The world API will be updated to support those two layouts. In the case of hash layout, the selector of each fields will be passed to instruct in which order the fields must be gathered. And then packing layout is also something we can still support.
dojo-lang: The macro for get! and set! must now distinguish the model layout. Based on this, we can generate the appropriate implementation to retrieve the layout and values from the model data.
torii: When the hash layout is used, I'm not sure if Torii needs to be modified to support it as we already rely on serialization. However, the ByteArray (string) and Array<T> must be supported for indexation. We may start with only array of primitive types though.

To remind also the longer term vision, we also want to enable a user to update/retrieve only certain fields of a model. Both layout should support that.
Questions

Should we use hash layout by default?
Should we allow packing on / packing off (independently of the layout)?
Is this something missing in the Storage that you guys at higher level / client side feel we're missing?

Happy to have any feedback on that, to ensure we can provide to user a very smooth and configurable experience when it comes to storage and upgradeability.

I don't think i understand this:

Dynamic types are now supported.

But I think my question might be useful for clarification anyway.
Let's say we have an array of this type
#[dojo::model(layout: 'hash')]
struct SimpleModel {
    a: u32,
    b: u8
}
let arr: Array<SimpleModel> = [ (10,11), (20,21), (30, 31) ] //Simplified notation but u get the point

How is the arr stored using the hash layout?

Dynamic types inside the model, because we store the model in the database.
So it would rather be:
#[dojo::model(layout: 'hash')]
struct SimpleModel {
    a: u32,
    b: Array<u8>,
}

And in the storage with hash layout you will have:

selector("a") address (derived from model base address) -> [u32] (1 felt)
selector("b") address (derived from model base address) -> [size of array, elts...] (at least 1 felt, but can be more).

For the first iteration, we will not support that, only primitive types:
#[dojo::model(layout: 'hash')]
struct NestedModel {
    a: u32,
    b: Array<SimpleModel>,
}

+1 for hash being default since arrays / bytearrays would be a common primitives. But I wonder how important is it to still support serial layout? If developers are looking to optimize for cost they could implement their own pack/unpack on single fields within the model? Much like what @notV4l is doing for RYO

+1 for hash being default since arrays / bytearrays would be a common primitives. But I wonder how important is it to still support serial layout? If developers are looking to optimize for cost they could implement their own pack/unpack on single fields within the model? Much like what @notV4l is doing for RYO

Good point.
When with the serial layout you can:
#[dojo::model(layout: 'hash')]
struct MyData {
    hp: u8,
    potions: u8,
    ...
}

and this will be packed automatically by Dojo, which allows you to keep your game logic using the model naturally?
But as you mentioned, is it really an added value for Dojo to support that, we've to decide. :+1:

Iff you decide you want to support both layouts, wouldn't it be better to abstract the model serialization and de-serialization?
The benefit would be that a particular mechanic could be derived or custom implemented, much like serde.

Good point. But isn't then your model like:
struct MyOneFelt {
   f: felt252,
}

And you have to do the pack/unpack yourself + the access to the fields?

If this serde-like way is doable (I'm not familiar with dojo low-level to the sufficient extent) then you would only need pack/unpack. The model interface (fields) would remain the same.
It might be a two bladed sword thou, since when the implementation is written by someone else the burden of keeping the model upgradable is on the implementer. So added flexibility but also more room for errors.
I don't know if it makes sense but just a point to consider :)

I'm on it !

Reworked for 0.7.0 and new type support.


Add m1093782566 information to etc/default_data.json

Add m1093782566 information to etc/default_data.json for more exact data collections

Thank you for contributing to openstack/stackalytics!
openstack/stackalytics uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.

Thank you for contributing to openstack/stackalytics!
openstack/stackalytics uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


Douglas UPass renew failed

The following message is appearing inside the snack bar after trying to renew:
se.fishtank.css.selectors.scanner.ScannerException: Bad input!

The ID we use is wrong, but fixing this likely won't fix the issue since Douglas uses an ASP.NET form which doesn't work at the moment.


Add tailwindcss support

Hi all,
I wanted to know if you're interested in adding tailwindcss support.
I did a proof of concept in a draft PR #505. It is a rough copy of the sass/scss support. I wanted to reach out before I go to the trouble of testing it and fixing the issues.
Thanks,
Mark

Not a maintainer, but I'm psyched for this - very nice looking work @markcatley

I just made a pull request to the existing yew-tailwindcss example. It works fine as far as I can see. What benefit would explicit support provide?

This was already merged - issue could be closed?

✅


publishing Paste the Plan extension

@dzsquared looks good to me. Though I noticed that there doesn't seem to be a custom icon for the extension. This isn't a requirement, but I'd recommend using a custom icon as I think it looks better in the marketplace, IMO.

@kburtram  I absolutely agree about the icon being important!  I included a "Microsoft.VisualStudio.Services.Icons.Default" asset in the extension gallery file, and URL for the image is working.  I'll check it out a bit further

@dzsquared I'll push this as-is and see if the icon shows up.  Please just post another PR if there are follow-ups needed.

@dzsquared it looks good now that the initial extension metadata has been published.


meteor app cannot access server's local filesystem

Hi,
In my meteor app, I access a directory on the local system for data, in my case a bunch of images.
When I deploy the app with mupx (my machine is OSX 10.11.3, and server is Ubuntu 14.04), I can successfully deploy the app, but I get the following error in the logs:
[-] => Starting meteor app on port:80
[-] filePath for data is: /home/meh/test-data
[-] { [Error: ENOENT, readdir '/home/meh/test-data'] errno: 34, code: 'ENOENT', path: '/home/meh/test-data' }
My mup.json looks like this:
{
"servers": [
{
"host": "xxx.xx.xxx.xx",
"username": "meh",
"pem": "~/.ssh/auth-poc",
"env": {
"TEST_DATA": "/home/meh/test-data"
}
}
],
"setupMongo": true,
"appName": "auth-poc",
"app": "~/Development/meteor/auth-poc-stable/auth-poc",
"env": {
"PORT": 80,
"ROOT_URL": "http://xxx.xx.xxx.xx"
},
"deployCheckWaitTime": 15,
"enableUploadProgressBar": true
}
I'm not sure if it has something to do with the permissions of the docker container,
how the path is specified, or something else.

What you need when using mupx is to add a "volume" argument to the appropriate docker run command
https://github.com/arunoda/meteor-up/blob/mupx/templates/linux/start.sh
This would then mount the deploy targets files system into the docker container.
The mongodb files setup via 'setup' are preserved across repeated deployments this way.
It's likely this is easier with new features in the port of mupx to kadirahq. They have also added hooks which might be another way to get it mounted.

Thanks for your input.
I managed to solve it like you said by adding volume arguments for each directory I needed access to (in the start.sh file). Here I'm showing how I added one directory for the 'bearing-data'.
  docker run \
    -d \
    --restart=always \
    --publish=$PORT:80 \
    --volume=$BUNDLE_PATH:/bundle \
    --env-file=$ENV_FILE \
    --link=mongodb:mongodb \
    --hostname="$HOSTNAME-$APPNAME" \
    --env=MONGO_URL=mongodb://mongodb:27017/$APPNAME \
    --name=$APPNAME \
    -v /home/username/data:/bearing-data \
    meteorhacks/meteord:base

I added it on all three docker run commands in that file.
My method was this:

uninstall current version of mupx (if installed)

sudo npm uninstall mupx -g

clone the current mupx code to local machine

mkdir /custom-meteor-up
git clone -b mupx https://github.com/arunoda/meteor-up.git

edit the meteor-up/templates/linux/start.sh file to mount data directory in docker run command

add '-v /home/username/data:/bearing-data' to all 3 docker run commands
add '-v /home/username/test-data:/bearing-test-data' to all 3 docker run commands
add '-v /home/username/cfs:/cfs' to all 3 docker run commands

install customized mupx

cd custom-meteor-up
sudo npm install -g
sudo npm link


Add binder badge

This PR add a binder badge to the README and fixes a version in requirements.txt, since Multi-Template-Matching version 1.5.0 is not available via pip, but 1.5.1 is.
To test the binder functionality, you can run binder from this PR's branch on my fork:

BTW, the requirements in requirements.txt are not sufficient for the third tutorial.
@LauLauThom You might want to add a cell directly to the affected .ipynb notebook though:
!pip install gluoncv mxnet

Nice trick about Binder thanks ! also for noticing the package version !
For gluoncv, I will add the line indeed as it is not a requirement for MTM per se, just for this tutorial


Neuromancer seems to load slowly/ poorly when zoomed out in 3 panel mode

Using layer: graphene://https://minnie.microns-daf.com/proxy/minniev1_em
When in 3-panel mode and zoomed out, the loading appears slow (despite still downloading at a reasonable rate ~ 15 - 30 MB/sec) and pauses before the image resolves clearly.
For example:

We used to get around this by loading:
precomputed://gs://microns-seunglab/minnie_v4/alignment/fine/sergiy_multimodel_v1/vector_fixer30_faster_v01/image_stitch_multi_block_v1
but this layer no longer exists.
After conversing with Sven it appears a solution to this would be to create a layer with a single mip specified.

Minor correction from my side: the solution would be a to bring back the feature that restricts loading to a single mip.


v2.32.3 - Unable to start container when Syslog Standard destination set in ENV

The following error is seen on startup:
Jul 18 08:57:10 sc4s systemd[1]: Starting SC4S Container...
Jul 18 08:57:10 sc4s systemd[1]: Started SC4S Container.
Jul 18 08:57:11 sc4s docker[3772]: SC4S_ENV_CHECK_HEC: Splunk HEC connection test successful to index=main for sourcetype=sc4s:fallback...
Jul 18 08:57:11 sc4s docker[3772]: SC4S_ENV_CHECK_HEC: Splunk HEC connection test successful to index=prd_monitoring for sourcetype=sc4s:events...
Jul 18 08:57:12 sc4s docker[3772]: Traceback (most recent call last):
Jul 18 08:57:12 sc4s docker[3772]:   File "/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.py", line 76, in <module>
Jul 18 08:57:12 sc4s docker[3772]:     transport=transport,
Jul 18 08:57:12 sc4s docker[3772]: NameError: name 'transport' is not defined
Jul 18 08:57:12 sc4s docker[3772]: [2022-07-17T22:57:12.278952] confgen: Generator program returned with non-zero exit code; reference='/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.conf:3:1', context='root', block='dest_syslog', exec='/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.py', rc='256'
Jul 18 08:57:12 sc4s docker[3772]: Error parsing config, syntax error, unexpected LL_ERROR, expecting end of file in /etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.conf:3:1-3:12:
Jul 18 08:57:12 sc4s docker[3772]: Included from /etc/syslog-ng/syslog-ng.conf:49:1-49:1:
Jul 18 08:57:12 sc4s docker[3772]: 44      @include "conf.d/local/config/sources/*.conf"
Jul 18 08:57:12 sc4s docker[3772]: 45      @include "conf.d/local/config/sources/*/*.conf"
Jul 18 08:57:12 sc4s docker[3772]: 46
Jul 18 08:57:12 sc4s docker[3772]: 47      @include "conf.d/destinations/*.conf"
Jul 18 08:57:12 sc4s docker[3772]: 48      @include "conf.d/destinations/*/*.conf"
Jul 18 08:57:12 sc4s docker[3772]: 49---->
Jul 18 08:57:12 sc4s docker[3772]: 49----> ^
Jul 18 08:57:12 sc4s docker[3772]: 50      @include "conf.d/local/config/destinations/*.conf"
Jul 18 08:57:12 sc4s docker[3772]: 51      @include "conf.d/local/config/destinations/*/*.conf"
Jul 18 08:57:12 sc4s docker[3772]: 52
Jul 18 08:57:12 sc4s docker[3772]: 53      # Group 0 log paths run before all others for high level activity like null queue
Jul 18 08:57:12 sc4s docker[3772]: 54      @include "conf.d/log_paths/0/*/*.conf"
Jul 18 08:57:12 sc4s docker[3772]: syslog-ng documentation: https://www.syslog-ng.com/technical-documents/list/syslog-ng-open-source-edition
Jul 18 08:57:12 sc4s docker[3772]: contact: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Jul 18 08:57:13 sc4s docker[3772]: Traceback (most recent call last):
Jul 18 08:57:13 sc4s docker[3772]:   File "/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.py", line 76, in <module>
Jul 18 08:57:13 sc4s docker[3772]:     transport=transport,
Jul 18 08:57:13 sc4s docker[3772]: NameError: name 'transport' is not defined
Jul 18 08:57:13 sc4s docker[3772]: [2022-07-17T22:57:13.199104] confgen: Generator program returned with non-zero exit code; reference='/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.conf:3:1', context='root', block='dest_syslog', exec='/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.py', rc='256'
Jul 18 08:57:13 sc4s docker[3772]: Error parsing config, syntax error, unexpected LL_ERROR, expecting end of file in /etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.conf:3:1-3:12:
Jul 18 08:57:13 sc4s docker[3772]: Included from /etc/syslog-ng/syslog-ng.conf:49:1-49:1:
Jul 18 08:57:13 sc4s docker[3772]: 44      @include "conf.d/local/config/sources/*.conf"
Jul 18 08:57:13 sc4s docker[3772]: 45      @include "conf.d/local/config/sources/*/*.conf"
Jul 18 08:57:13 sc4s docker[3772]: 46
Jul 18 08:57:13 sc4s docker[3772]: 47      @include "conf.d/destinations/*.conf"
Jul 18 08:57:13 sc4s docker[3772]: 48      @include "conf.d/destinations/*/*.conf"
Jul 18 08:57:13 sc4s docker[3772]: 49---->
Jul 18 08:57:13 sc4s docker[3772]: 49----> ^
Jul 18 08:57:13 sc4s docker[3772]: 50      @include "conf.d/local/config/destinations/*.conf"
Jul 18 08:57:13 sc4s docker[3772]: 51      @include "conf.d/local/config/destinations/*/*.conf"
Jul 18 08:57:13 sc4s docker[3772]: 52
Jul 18 08:57:13 sc4s docker[3772]: 53      # Group 0 log paths run before all others for high level activity like null queue
Jul 18 08:57:13 sc4s docker[3772]: 54      @include "conf.d/log_paths/0/*/*.conf"
Jul 18 08:57:13 sc4s docker[3772]: syslog-ng documentation: https://www.syslog-ng.com/technical-documents/list/syslog-ng-open-source-edition
Jul 18 08:57:13 sc4s docker[3772]: contact: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Jul 18 08:57:13 sc4s docker[3772]: syslog-ng checking config
Jul 18 08:57:13 sc4s docker[3772]: sc4s version=2.32.3
Jul 18 08:57:14 sc4s docker[3772]: starting goss
Jul 18 08:57:15 sc4s docker[3772]: Traceback (most recent call last):
Jul 18 08:57:15 sc4s docker[3772]:   File "/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.py", line 76, in <module>
Jul 18 08:57:15 sc4s docker[3772]:     transport=transport,
Jul 18 08:57:15 sc4s docker[3772]: NameError: name 'transport' is not defined
Jul 18 08:57:15 sc4s docker[3772]: [2022-07-17T22:57:15.108213] confgen: Generator program returned with non-zero exit code; reference='/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.conf:3:1', context='root', block='dest_syslog', exec='/etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.py', rc='256'
Jul 18 08:57:15 sc4s docker[3772]: Error parsing config, syntax error, unexpected LL_ERROR, expecting end of file in /etc/syslog-ng/conf.d/destinations/dest_syslog/plugin.conf:3:1-3:12:
Jul 18 08:57:15 sc4s docker[3772]: Included from /etc/syslog-ng/syslog-ng.conf:49:1-49:1:
Jul 18 08:57:15 sc4s docker[3772]: 44      @include "conf.d/local/config/sources/*.conf"
Jul 18 08:57:15 sc4s docker[3772]: 45      @include "conf.d/local/config/sources/*/*.conf"
Jul 18 08:57:15 sc4s docker[3772]: 46
Jul 18 08:57:15 sc4s docker[3772]: 47      @include "conf.d/destinations/*.conf"
Jul 18 08:57:15 sc4s docker[3772]: 48      @include "conf.d/destinations/*/*.conf"
Jul 18 08:57:15 sc4s docker[3772]: 49---->
Jul 18 08:57:15 sc4s docker[3772]: 49----> ^
Jul 18 08:57:15 sc4s docker[3772]: 50      @include "conf.d/local/config/destinations/*.conf"
Jul 18 08:57:15 sc4s docker[3772]: 51      @include "conf.d/local/config/destinations/*/*.conf"
Jul 18 08:57:15 sc4s docker[3772]: 52
Jul 18 08:57:15 sc4s docker[3772]: 53      # Group 0 log paths run before all others for high level activity like null queue
Jul 18 08:57:15 sc4s docker[3772]: 54      @include "conf.d/log_paths/0/*/*.conf"
Jul 18 08:57:15 sc4s docker[3772]: syslog-ng documentation: https://www.syslog-ng.com/technical-documents/list/syslog-ng-open-source-edition
Jul 18 08:57:15 sc4s docker[3772]: contact: https://lists.balabit.hu/mailman/listinfo/syslog-ng
Jul 18 08:57:15 sc4s systemd[1]: sc4s.service: Main process exited, code=exited, status=1/FAILURE
Jul 18 08:57:15 sc4s systemd[1]: sc4s.service: Failed with result 'exit-code'.

Sample env_file config
# FIREEYE
SC4S_DEST_SYSLOG_PALANTIRFE_HOST=<IP_ADDRESS>
SC4S_DEST_SYSLOG_PALANTIRFE_PORT=514
SC4S_DEST_SYSLOG_PALANTIRFE_TRANSPORT=tls
SC4S_DEST_SYSLOG_PALANTIRFE_MODE=SELECT

v2.32.4 has the following error logs
Jul 18 19:52:42 sc4s systemd[1]: Starting SC4S Container...
Jul 18 19:52:42 sc4s systemd[1]: Started SC4S Container.
Jul 18 19:52:42 sc4s docker[23417]: SC4S_ENV_CHECK_HEC: Splunk HEC connection test successful to index=main for sourcetype=sc4s:fallback...
Jul 18 19:52:42 sc4s docker[23417]: SC4S_ENV_CHECK_HEC: Splunk HEC connection test successful to index=prd_monitoring for sourcetype=sc4s:events...
Jul 18 19:52:45 sc4s docker[23417]: syslog-ng checking config
Jul 18 19:52:45 sc4s docker[23417]: sc4s version=2.32.4
Jul 18 19:52:46 sc4s docker[23417]: starting goss
Jul 18 19:52:47 sc4s docker[23417]: starting syslog-ng
Jul 18 19:52:49 sc4s docker[23417]: [2022-07-18T09:52:49.105526] transport(tls) was specified, but tls() options missing;
Jul 18 19:52:49 sc4s docker[23417]: [2022-07-18T09:52:49.106157] Error initializing message pipeline; plugin_name='syslog', location='root generator dest_syslog:5:5'
Jul 18 19:52:49 sc4s docker[23417]: syslog-ng failed to start; exiting...
Jul 18 19:52:49 sc4s docker[23417]: Handling exit 1 and restarting
Jul 18 19:52:49 sc4s docker[23417]: starting syslog-ng
Jul 18 19:52:51 sc4s docker[23417]: [2022-07-18T09:52:51.033791] transport(tls) was specified, but tls() options missing;
Jul 18 19:52:51 sc4s docker[23417]: [2022-07-18T09:52:51.034498] Error initializing message pipeline; plugin_name='syslog', location='root generator dest_syslog:5:5'
Jul 18 19:52:51 sc4s docker[23417]: syslog-ng failed to start; exiting...
Jul 18 19:52:51 sc4s docker[23417]: Handling exit 1 and restarting
Jul 18 19:52:51 sc4s docker[23417]: starting syslog-ng
Jul 18 19:52:53 sc4s docker[23417]: [2022-07-18T09:52:53.245578] transport(tls) was specified, but tls() options missing;
Jul 18 19:52:53 sc4s docker[23417]: [2022-07-18T09:52:53.246153] Error initializing message pipeline; plugin_name='syslog', location='root generator dest_syslog:5:5'

Its not an error for using tls options, tls flags need to be set.

Please note this issue is not resolved.
We have made a PR which we believe will fix the issue. Please revirew and advise
#1755

Thanks @pwickham ,thank you so much contributing and yes it was overlooked in the implemented fix as i was not using tls as transport in my tests, i presumed we have edge cases sorted, let me do my testing and i will release fix today.

Fixed in version 2.32.5


PHP MySQLi extension support

Hello, maybe w2ui could support the mysqli extension, because the mysql extension has been deprecated since PHP 5.5. The mysqli or PDO extension should be used instead. The mysql extension has been removed since PHPNG(PHP 7) .
I am write a new one(w2db.php) to support the mysqli extension. :)
https://github.com/kn007/w2ui-w2db-mysqli.php
Thank you.

w2db.php is not part of this project. This is more just like an example how to do it. Plus it is not actually scope of this project. :)

Got it, Thank you.
Actually I created this issue just want to help people in need.

Sure, it sounds good. Thanks.

Got it, Thank you.
Actually I created this issue just want to help people in need.

HI, did you rewrite w2db.php to make use of PDO? I am facing the same problem now, and wonder if somebody has already done this.

Hi @kn007, did you rewrite w2db.php to make use of PDO? I am facing the same problem now, and wonder if somebody has already done this.


Missing add_special_tokens in biencoder?

Hi! Thank you for your great work!
To my understanding, BLINK uses special tokens to represent a mention position and entity title for both bi-encoder and cross-encoder.
In cross-encoder, your code actually sets special tokens to the tokenizer.
https://github.com/facebookresearch/BLINK/blob/main/blink/crossencoder/crossencoder.py#L82-L89
But in bi-encoder, add_special_tokens is not called which means special tokens are just processed as [UNK].
https://github.com/facebookresearch/BLINK/blob/main/blink/biencoder/biencoder.py#L82-L87
Do  you do this intentionally? If so, could you elaborate on that?

@jojonki: Yes, the special tokens are missing form biencoder tokenizer.


Update GDB runners to use new shim architecture

Please see https://github.com/c9/c9.ide.run.debug/pull/40 for context.
Updates all runners that use the GDB Debugger plugin to use the new shim design. The shim is called directly and is responsible for managing the gdbserver and gdb client processes. Since the shim communicates with the debugger plugin via a socket, debugport is not needed.
This also renames the C (GDB Debugging) runner to C (make) to make it more semantically consistent with C (simple).
Edited to add: the socket path and retry count and interval are specified in the runners. maxdepth is no longer necessary as it can be passed as parameter directly to the shim, but defaults to 50 and is therefore simply removed from the runners.
Important note: Once accepted, this PR should be deployed at the same time as https://github.com/c9/c9.ide.run.debug/pull/40 to ensure consistent access to the GDB debugger.

not sure why github didn't detect this as merged. the last commit of this pr is at
https://github.com/c9/c9.ide.run/commit/f4ccb6871a6edcaf21dc8796bbf9a8c747edba29


Support for spacing character to enable CAPS_UNDERSCORE, kebab-case, etc

Hi, great plugin! I thought about make this one myself but I never had the time so super nice that you've built it!
It would be nice if it would be possible to support spacing. I have no idea if it's possible to override the standard selection mechanism but these would all be interchangeable:
myVar
MyVar
my-var
MY_VAR
Camel-Kebab

Hi, thank you for your kind words.
I could be wrong, but I don't think the word selection hotkey behavior can be overridden. Most probably you would have to select with alt+mouse, which largely defeats the purpose of the extension.
Selection problems aside, I suppose those cases could be implemented. I won't be doing it any time soon, cause without easy selection I don't see much value in it. I might accept a PR though.

Hi bro, what combinations of keys you use?

Hi bro, what combinations of keys you use?

Me? cmd-d on mac

Me? cmd-d on mac

Me? cmd-d on mac

Thanks, man, in windows is Ctrl + D, the repo owner answer me, thank you same.

Me? cmd-d on mac

Thanks, man, in windows is Ctrl + D, the repo owner answer me, thank you same.


--verbose switch

Hi,
just a thing that came into my mind while playing today with autoname.
Describe the solution you'd like
add a switch, maybe --verbose, and output something like:
opened "window class"
closed "window class"
etc...
in case of dedup:
opened "window class1"
opened "window class2"
opened "window class1" -- duplicate
etc..
Additional context
would be easier to identify classes without hyprctl
thanks!

Thanks for the idea 💡

Can you give a try ? I did simple.

mate you are awesome.
it works, just a note:
when i open a window, it says all the opened windows: is it possible to see only the last one? or maybe --verbose 1 or --verbose 2 to switch between these modes?
and while playing with this noticed a problem, but i'll open a bug just to bother you :rofl:

It's possible but looks like a lot of code to do for just verbose. For sure I can do better but need to studies more than few seconds how to do this 😅

atm my QOL while setting autoname up, is surely better and faster :) so many many thanks!

I close this issue, I will try to make better later 😉


Update unit tests

Some unit tests for the protocol implementation and model were working a year ago when I started the 0.8.x upgrade.  They've since broken as files have gotten moved and interfaces changed slightly.  This needs to be fixed.

The protocol unit tests are working now. I've also added tests for the BalancedConsumer and pykafka's SimpleConsumer

Updated title to reflect that we have some tests, but need a boatload more before we can call this done/ready.

We've got some integration tests working now for the main components, so we can move this to the next milestone for now.

Let's just kill it. We've hit 80%, which I set as passing in coveralls.  We'll just need to make sure that new additions have tests so that the suite grows with the project.


Use $input-border-width for both .form-control and .btn borders

Fixes #18424.
Both widgets need to use the same border width because of input groups.
Thus, s/[$]btn-border-width/[$]input-border-width/g
I admit $input-border-width might stand to be renamed, but no great alternative name came to mind. Suggestions welcomed.
CC: @mdo

$input-btn-border-width?

Good enough for me. Renamed.


PageSize being ignored

When using the autogenerated list action, it seems the pageSize parameter is being ignored. I can replicate this both in the api gateway and using curl.
{service}/?pageSize=20 keeps returning 10 (the default). For comparison page does work, {service}/?page=2 returns the second page

Sorry, just realized this was due to a middleware bug!


Issue 47 - pyrenew_demo.qmd

Completed documentation for pyrenew demo

Thanks! And agreed - I'd have put a lot more description of each function into this if I had had more time.


create donboscosandona.txt

it is a secondary school

This database is for post-secondary (higher education) schools only. Closing.


Move CDAP to common-services and extend in stacks

This moves the CDAP service from resources/stacks/HDP/*/services/CDAP to resources/common-services/CDAP/${PACKAGE_VERSION} and now has a stacks directory that allows us to set specific changes for specific HDP versions... (for example, TEZ is introduced in HDP 2.1)

One question, otherwise LGTM.


add glm.ortho and related tests

resolves #4

... ps: the different math libraries produced different projections... which all seemed correct, but were still significantly different numerical values (which makes comparison and testing difficult).
As part of this change set I reworked tdl-fast's implementation and also how three.js's gets invoked -- such that now everything lines up better with observed GLM 0.9.6 / GLM 0.9.8 behavior (ie: regardless of back-end vendor lib, results should be consistent).


feat: attempt to parse gravatar url if thumbnail url is not provided

Task linked: CU-8695hvz92 Avatar is not displayed properly


Update the Rails test server port

Running the next command yarn cypress open --project ./spec starts up Cypress which seems to look for a server responding on port 5002 by default rather than the previously documented bin/rails server -e test -p 5017. This fix updates the documentation to get the Rails test server running on the port that Cypress expects it to be responding on, 5002.

Related to #49

I release a new version so that the default port and README.md on master matches


Syntax highlight JS parts

In the code snippet gif in the README, the syntax highlighting of HTML looks very nice. However, the ${title} seems to not be highlighted to note that title is a JS variable. Could the dynamic parts of the template literal be syntax highlighted as JS?

This issue was moved to mjbvz/vscode-lit-html#5


A submission by a full ELR sender gets a return json response from the API

User Story:
As a sender, I want to receive a response from the API when I submit a report, so I can know if the submission was successful.
Description/Use Case
A sender needs to receive a structured json response to their submission, including a report ID and other relevant data.
Risks/Impacts/Considerations

Following the existing json response structure may result in many empty fields
Creating a new response structure may result in downstream effects from existing senders that want to switch to full ELR

Dev Notes:

The response should have all/most populated fields as compared to a COVID Async response.
Only the async method of submission will be used for full ELR senders.
Need to generate response using existing structure and methods use to generated the COVID response.
If the structure of the response is not going to be matching the existing response structure, this needs to be discussed with the team

Acceptance Criteria

The reports/waters API returns a JSON response with a report ID if the report was accepted/validated.
The reports/waters API returns a JSON response without a report ID if the report was not accepted.
The reports/waters API JSON response has similar data to a COVID async response.
The reports/waters API returns a JSON response which must contain a submission ID.

All AC met accordingly.


Allow for "shellArgs" in Windows integrated terminal

VSCode Version: 1.6.1
OS Version: Windows 10

Steps to Reproduce:

Try to change terminal.integrated.shell.windows to pass additional parameters like variable expansion flag.
terminal fails with exit code 1

There is no current way to pass additional parameters to the Windows shell, it would be useful for configuration scripts and flags passed to the terminal, os other options passed to custom terminals.
In fact, the integrated terminal don't work with anything other than powershell and cmd.

Assign to @octref first as I saw https://github.com/Microsoft/vscode/pull/11982

the integrated terminal don't work with anything other than powershell and cmd.

What shell are you using?
CC @Tyriar

This is fixed for Windows and coming to stable soon in v1.7.


Compile errors [Swift 3.0]

Hi,
thanks for #17 but I'm still getting errors. See attached build log.
Could you please take a look?
Thanks a lot.
build.log.txt

Are you using the latest Swift beta version? The errors you are getting look like they would come from a pre-beta6 compiler

I do have Swift 3.0 Beta 5 on my Ubuntu VM, but I can't compile Swift from source code (low RAM). That Beta 6 compiler is necessary?

OK. I made fresh install of Ubuntu, Swift 3.0 PREVIEW 6 and I'm still getting errors. Could you please take a look? Thanks.
build.log.txt

Well, see #19. :)