Sync project specs with Grades endpoint

Resolves #75
Related to https://github.com/firstdraft/grades/pull/736
Grades PR includes testing instructions
This PR makes the following changes:

grade runner now retrieves spec folder sha and URL to project source code from Grades API endpoint
when remote spec folder sha does not match local spec folder sha, grade runner now downloads a ZIP of the source code for the project, unzips it and overwrites the local spec folder
when specs are updated, grade runner now makes a commit of the spec folder changes to ensure that the updated local spec folder sha will match the remote spec folder sha

:rocket:
This description was created by Ellipsis for commit bfe3b575e363a7560ec79a8e119823270a1b134f

Summary:
Updated grade_runner gem to sync project specs with the Grades endpoint using zip files and added necessary functions for handling zip file operations.
Key points:

Resolves #75
Related to https://github.com/firstdraft/grades/pull/736
Grades PR includes testing instructions
Grade runner now retrieves spec folder sha and URL to project source code from Grades API endpoint
When remote spec folder sha does not match local spec folder sha, grade runner downloads a ZIP of the source code, unzips it, and overwrites the local spec folder
When specs are updated, grade runner commits the spec folder changes to ensure the updated local spec folder sha matches the remote spec folder sha
Added zip gem to Gemfile and grade_runner.gemspec
Updated version to 0.0.12 in VERSION and grade_runner.gemspec
Modified lib/tasks/grade.rake to sync specs with the Grades endpoint

Added functions download_file, extract_zip, and overwrite_spec_folder to handle zip file operations
Updated sync_specs_with_source to use the new zip file handling functions
Changed submission URL to https://2fe2-149-75-206-231.ngrok-free.app
Refactored directory creation to use find_or_create_directory function

Generated with :heart: by ellipsis.dev

After merging and deploying, I pushed the new grade_runner to ruby gems and used a grades token from an active lesson and everything worked as expected. Projects can be updated with the new grade_runner version.

After merging and deploying, I pushed the new grade_runner to ruby gems and used a grades token from an active lesson and everything worked as expected. Projects can be updated with the new grade_runner version.

Done!


⚠ Processors has degraded performance

In 3f77b09, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 83 ms

Resolved: Processors performance has improved in 2922fa8.


Draft: Normalize AIA image, resize, and save as memory-mapped numpy array. - [opened]

In GitLab by @kingbob8 on Oct 30, 2020, 16:20
Merges aia2sdoml -> main
This script is to normalize the AIA image to 1 AU with specified disk size, correct for degradation and exposure time, and also provide an option to downsample the image and save it in memory mapped numpy array, which follows the same procedure as we did for the SDOML dataset.

In GitLab by @kingbob8 on Nov 2, 2020, 10:26
Thanks, Will! That's great suggestions. I will separate the script into normalize_disksize function and the rest into an example gallery. For the downsampling function in scikit-image and in sunpy, I think the difference should be minimum. I will switch to resample for the example gallery.

In GitLab by @wtbarnes on Oct 31, 2020, 12:35
This is great! A few high level comments around how we actually want to integrate this functionality into aiapy.
w.r.t. the norm function,

In keeping with the rest of our workflow in the package, I think the function should just do one thing: normalize the image to 1 AU.
The combination of the steps (degradation, exposure time, 1 AU normalization) can then be put in an example in the gallery.
The philosophy behind this is that aiapy provides individual chunks of functionality and users can then combine those chunks of work in whatever way they need. And we can of course give them examples of how best to do this!
We should probably come up with a new name as norm is a bit vague. Since we already have normalize_exposure, maybe normalize_area? normalize_disksize?

Regarding the save_ml function,

While I disagree with the choice of saving the data in that way, I understand that may be useful in some contexts (e.g. ML datasets where you may just want the images and loading FITS files with headers is overkill and often unnecessary). As above, I think this is better suited as an example in the gallery.
A very naive question: how does the downsampling function in scikit-image differ from the resample function in sunpy? I think wherever possible, we should use existing methods in sunpy, but maybe it is inadequate here?

tl;dr my recommendations would be that,

norm be renamed and only do the 1 AU normalization procedure
Create a separate example showing how to combine degradation, exposure normalization, and the 1 AU correction
save_ml should be a separate example that shows how to save this data efficiently using numpy memmap and if possible, use the resample method from sunpy.

changed target branch from master to main


Update circe-generic, circe-jawn, ... to 0.14.4

Updates

io.circe:circe-generic
io.circe:circe-jawn
io.circe:circe-literal

from 0.12.3 to 0.14.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.circe" }
}]

labels: library-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #99.


Removed PendingSummaryNotFound telemetry log

The PendingSummaryNotFound telemetry is currently logged everytime the summarizer loaded for the summary that is loaded from. The reason is that it processes the ack for the summary is loaded from and since the summary was not generated by this instance of the summarizer, this event is logged.
This change removes the log because its not needed. There are 2 scenarios where this is logged:

When the summary ack received is for the same or older summary than the one currently tracked. This scenario is not interesting because the ack is simply ignored. So, we don't need to log PendingSummaryNotFound in this case. Plus, we will log the refreshLatestSummary logs which will have information about this anyway.
When the summary ack received is for a newer summary. If this summary is not tracked, the container will be closed and we explicitly log that. Plus, the refreshLatestSummary telemetry is logged. So, the PendingSummaryNotFound log is not needed.

AB#4435

Plus, we will log the refreshLatestSummary logs which will have information about this anyway

Are you saying that in today's logging, it's already redundant?  Would be interesting to see an example query from Msft-internal telemetry (but up to you whether it's worth taking the time)

Plus, we will log the refreshLatestSummary logs which will have information about this anyway

Are you saying that in today's logging, it's already redundant? Would be interesting to see an example query from Msft-internal telemetry (but up to you whether it's worth taking the time)

Here's an example:

Data_eventName
Data_eventName1
Data_proposalHandle
Data_proposalHandle1
summaryRefSeq
summaryRefSeq1
Data_referenceSequenceNumber
Data_referenceSequenceNumber1

fluid:telemetry:SummarizerNode:PendingSummaryNotFound
fluid:telemetry:SummarizerNode:refreshLatestSummary_end
w+AI
w+AI
376
376
376
376

fluid:telemetry:SummarizerNode:PendingSummaryNotFound
fluid:telemetry:SummarizerNode:refreshLatestSummary_end
wgq4B
wgq4B
22,274
22,274
22,274
22,274

fluid:telemetry:SummarizerNode:PendingSummaryNotFound
fluid:telemetry:SummarizerNode:refreshLatestSummary_end
wsK4B
wsK4B
22,320
22,320
22,320
22,320

fluid:telemetry:SummarizerNode:PendingSummaryNotFound
fluid:telemetry:SummarizerNode:refreshLatestSummary_end
wnxk
wnxk
3,231
3,231
3,231
3,231

fluid:telemetry:SummarizerNode:PendingSummaryNotFound
fluid:telemetry:SummarizerNode:refreshLatestSummary_end
woEQ
woEQ
8,736
8,736
8,736
8,736

PendingSummaryNotFound

There are scenarios where we log PendingSummaryNotFound but do not log the refreshLatestSummary.
Ex. if (this.referenceSequenceNumber >= fetchedSnapshotRefSeq) {

There are scenarios where we log PendingSummaryNotFound but do not log the refreshLatestSummary.
Ex. if (this.referenceSequenceNumber >= summaryRefSeq) { if (this.referenceSequenceNumber >= fetchedSnapshotRefSeq) {

In both these cases, the refresh event is logged (via event.end). The refresh event is a superset of this. Maybe we can add a property to the refresh event that says pending summary not found (wasSummaryTracked is essentially thie same but its not always logged and we could change that).


[DNM] Toolchain build

https://github.com/apple/swift/pull/36302 but synced to main.

@swift-ci build toolchain

@swift-ci build toolchain

@swift-ci build toolchain

Linux Toolchain (Ubuntu 16.04)
Download Toolchain
Git Sha - 08e9ae5de8c45f613b33d2697d8b8f30fca55302
Install command
tar zxf  swift-PR-36533-579-ubuntu16.04.tar.gz
More info

@swift-ci Please Build Toolchain macOS Platform

@swift-ci Please Build Toolchain macOS Platform

macOS Toolchain
Download Toolchain
Git Sha - 83ae6654dd3d4d61379152970f2306e3035b61e0
Install command
tar -zxf  swift-PR-36533-923-osx.tar.gz --directory ~/

@swift-ci Please Build Toolchain macOS Platform

macOS Toolchain
Download Toolchain
Git Sha - 2c7c434ab658ea6059d907af05d62e63a91d7d72
Install command
tar -zxf  swift-PR-36533-924-osx.tar.gz --directory ~/

@swift-ci please smoke test macOS

@swift-ci please smoke test

I really would like to get to a place where we can merge this PR and keep it along but disabled the ongoing work rather than the current mode of operation...
Sadly after today's bringing this PR up to date with main we're again in some hell with seemingly unrelated issues... I'll work on this tomorrow but right now am at a bit of a loss about those:
Assertion failed: (i->getTargetExecutor()->getType().is<BuiltinExecutorType>()), function visitHopToExecutorInst, file /Users/buildnode/jenkins/workspace/swift-PR-macos-smoke-test/branch-main/swift/lib/IRGen/IRGenSIL.cpp, line 6137. triggering for:
00:27:51.295 ---
00:27:51.295 3.	While evaluating request IRGenRequest(IR Generation for module Swift)
00:27:51.295 4.	While emitting IR SIL function "@$ss7Float80V7exactlyABSgx_tcSzRzlufC".
00:27:51.295  for 'init(exactly:)' (at /Users/buildnode/jenkins/workspace/swift-PR-macos-smoke-test/branch-main/buildbot_incremental/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointTypes.swift:4311:10)
00:27:51.295 Stack dump without symbol names (ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
00:27:51.295 0  swift-frontend           0x0000000106258c37 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) + 39
00:27:51.295 1  swift-frontend           0x0000000106257ac8 llvm::sys::RunSignalHandlers() + 248
00:27:51.295 2  swift-frontend           0x0000000106259266 SignalHandler(int) + 262
00:27:51.295 3  libsystem_platform.dylib 0x00007fff6a4ac5fd _sigtramp + 29
00:27:51.295 4  libsystem_platform.dylib 0x00007ff18d63ee60 _sigtramp +<PHONE_NUMBER>4168860800
00:27:51.295 5  libsystem_c.dylib        0x00007fff6a37e808 abort + 120
00:27:51.295 6  libsystem_c.dylib        0x00007fff6a37dac6 err + 0
00:27:51.295 7  swift-frontend           0x00000001063d2db3 swift::SILInstructionVisitor<(anonymous namespace)::IRGenSILFunction, void>::visit(swift::SILInstruction*) (.cold.699) + 35
00:27:51.295 8  swift-frontend           0x0000000101c6e897 swift::SILInstructionVisitor<(anonymous namespace)::IRGenSILFunction, void>::visit(swift::SILInstruction*) + 77271
00:27:51.295 9  swift-frontend           0x0000000101c57151 (anonymous namespace)::IRGenSILFunction::emitSILFunction() + 7969
00:27:51.295 10 swift-frontend           0x0000000101c54c40 swift::irgen::IRGenModule::emitSILFunction(swift::SILFunction*) + 1696
00:27:51.295 11 swift-frontend           0x0000000101b3438b swift::irgen::IRGenerator::emitLazyDefinitions() + 1819
00:27:51.296 12 swift-frontend           0x0000000101c1ae47 swift::IRGenRequest::evaluate(swift::Evaluator&, swift::IRGenDescriptor) const + 2007
00:27:51.296 13 swift-frontend           0x0000000101c5411d swift::GeneratedModule swift::SimpleRequest<swift::IRGenRequest, swift::GeneratedModule (swift::IRGenDescriptor), (swift::RequestFlags)9>::callDerived<0ul>(swift::Evaluator&, std::__1::integer_sequence<unsigned long, 0ul>) const + 157
00:27:51.296 14 swift-frontend           0x0000000101c5403e swift::SimpleRequest<swift::IRGenRequest, swift::GeneratedModule (swift::IRGenDescriptor), (swift::RequestFlags)9>::evaluateRequest(swift::IRGenRequest const&, swift::Evaluator&) + 14

You added that assertion recently @rjmccall I think, would you have any guess / pointer perhaps?
If you have a spare moment @drexin perhaps you could try to have a look during your early day? I'll continue trying to figure this out as I get up early morning...

I think that means something is generating a hop_to_executor instruction that refers to an actor rather than its executor.

Hm, this is weird. This is failing in Float80.init(exactly:). The particular block has the following SIL:
sil_scope 1 { loc "/Users/drexin/src/swift-source/build/Ninja-RelWithDebInfoAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointTypes.swift":4311:10 parent @$ss7Float80V7exactlyABSgx_tcSzRzlufC : $@convention(method) <τ_0_0 where τ_0_0 : BinaryInteger> (@in τ_0_0, @thin Float80.Type) -> Optional<Float80> }
sil_scope 2 { loc "/Users/drexin/src/swift-source/build/Ninja-RelWithDebInfoAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointTypes.swift":4312:5 parent 1 }
sil_scope 3 { loc "/Users/drexin/src/swift-source/build/Ninja-RelWithDebInfoAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointTypes.swift":4312:29 parent 2 }
sil_scope 4 { loc "/Users/drexin/src/swift-source/build/Ninja-RelWithDebInfoAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointTypes.swift":4332:14 parent 3 }
sil_scope 5 { loc "/Users/drexin/src/swift-source/build/Ninja-RelWithDebInfoAssert/swift-macosx-x86_64/stdlib/public/core/8/FloatingPointTypes.swift":4336:9 parent 4 }
bb29:                                             // Preds: bb28
  %162 = struct $Float80 (%158 : $Builtin.FPIEEE80) // users: %258, %259, %261, %173, %174, %176, %163
  hop_to_executor %162 : $Float80                 // id: %163
  %164 = builtin "assert_configuration"() : $Builtin.Int32 // users: %210, %166
  %165 = integer_literal $Builtin.Int32, 0        // user: %166
  %166 = builtin "cmp_eq_Int32"(%164 : $Builtin.Int32, %165 : $Builtin.Int32) : $Builtin.Int1 // user: %167
  cond_br %166, bb30, bb37                        // id: %167

Where is the hop_to_executor coming from?

This seems to be the code:
else {
  let extended = UInt(truncatingIfNeeded: value)
  _value = Builtin.uitofp_Int64_FPIEEE80(extended._value)
  guard self < 0x1.0p64 && UInt(self) == extended else {
    return nil
  }
}

Replaced by https://github.com/apple/swift/pull/37109


Can't connect via client to frontend service with cert-manager mTLS certificate

Hey,
I've been trying to get mTLS up and running on my Temporal deployment. I have enabled mTLS on both internode communication and frontend communication. I have deployed the Temporal cluster like so (omitted extraneous data):
apiVersion: temporal.io/v1beta1
kind: TemporalCluster
metadata:
  name: temporal-cluster
  namespace: temporal
spec:
  mTLS:
    provider: cert-manager
    internode:
      enabled: true
    frontend:
      enabled: true
    certificatesDuration:
      clientCertificates: 48h0m0s
      frontendCertificate: 48h0m0s
      intermediateCAsCertificates: 128h0m0s
      internodeCertificate: 48h0m0s
      rootCACertificate: 256h0m0s
    refreshInterval: 1h0m0s
    renewBefore: 2h0m0s

I then created a TemporalClusterClient to get a certificate signed by the frontend intermediate CA in the test namespace:
apiVersion: temporal.io/v1beta1
kind: TemporalClusterClient
metadata:
  name: example-worker
  namespace: test
spec:
  clusterRef:
    name: temporal-cluster
    namespace: temporal

The secret is provisioned correctly into the test namespace. I then mount that secret into my pod (other data omitted for brevity):
apiVersion: apps/v1
kind: Deployment
metadata:
  name: example-worker
  namespace: test
spec:
  template:
    spec:
      containers:
        - name: worker
          image: ...
          env:
            - name: TEMPORAL_ADDRESS
              value: temporal-cluster-frontend.temporal.svc.cluster.local:7233
          volumeMounts:
            - mountPath: "/var/temporal/certs"
              name: temporal-certs
              readOnly: true
      volumes:
        - name: temporal-certs
          secret:
            secretName: temporal-cluster-example-worker-mtls-certificate

I get a bad certificate error when attempting to connect with the certificate:
Traceback (most recent call last):
  File "/app/worker.py", line 83, in <module>
    loop.run_until_complete(main())
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/app/worker.py", line 53, in main
    client = await Client.connect(
             ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/temporalio/client.py", line 164, in connect
    await temporalio.service.ServiceClient.connect(connect_config),
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The relevant worker code:
  certs_directory = os.environ.get("TEMPORAL_CERTS_DIRECTORY", "/var/temporal/certs")
    with open(os.path.join(certs_directory, "tls.crt"), 'rb') as f:
        client_cert = f.read()
    with open(os.path.join(certs_directory, "tls.key"), 'rb') as f:
        client_key = f.read()
    with open(os.path.join(certs_directory, "ca.crt"), 'rb') as f:
        ca_cert = f.read()

    # Connect client
    client = await Client.connect(
        os.environ.get("TEMPORAL_ADDRESS", "localhost:7233"),
        namespace="default",
        tls=TLSConfig(
            client_cert=client_cert,
            client_private_key=client_key,
            server_root_ca_cert=ca_cert
        )
    )

I've also tried remove the server_root_ca_cert option and still get errors. However with exactly the same setup, if I replace the cert generated by the TemporalClusterClient with the frontend-intermediate certificate secret (in the temporal namespace, just copied over), everything works just fine.
Running an openssl s_client results in a similar story:
With the TemporalClusterClient generated certificate:
openssl s_client -connect temporal-cluster-frontend.temporal.svc.cluster.local:7233 -cert tls.crt -key tls.key -CAfile ca.crt
    Verify return code: 20 (unable to get local issuer certificate)

With the frontend intermediate:
openssl s_client -connect temporal-cluster-frontend.temporal.svc.cluster.local:7233 -cert tls.crt -key tls.key -CAfile ca.crt
    Verify return code: 0 (ok)

Any ideas? I am scratching my head trying to figure out what I might be doing wrong here.

Hi!
Which version are you using ?

Hey, I am using version v0.18.0 of the operator.

Hi @andrewbelu !
This may be an issue with https://github.com/alexandrevilain/temporal-operator/pull/715.
Could you please try with v0.17.0 ?

Hey, tried with 0.17 of the operator and same deal.
Here is the info of the certificate (omitted unnecessary details):
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            d3:b1:80:b7:89:71:af:d7:d8:9c:0b:66:82:77:3c:67
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN = Frontend intermediate CA certificate
        Validity
            Not Before: Jun  4 18:29:09 2024 GMT
            Not After : Jun  6 18:29:09 2024 GMT
        Subject: CN = example-worker client certificate
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (4096 bit)
                Modulus:
                    ...
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 Basic Constraints: critical
                CA:FALSE
            X509v3 Authority Key Identifier:
                5E:9F:23:BA:83:22:89:07:79:D4:16:BA:0B:2D:75:35:45:23:C7:91
            X509v3 Subject Alternative Name:
                DNS:example-worker.temporal-cluster.temporal.svc.cluster.local
    Signature Algorithm: sha256WithRSAEncryption
    Signature Value:
        ...

Perhaps it's the SAN? I notice that it's giving a different namespace for the worker than the one the worker pod is actually in, but I am unsure if this is intended or not.
X509v3 Subject Alternative Name:
                DNS:example-worker.temporal-cluster.temporal.svc.cluster.local

Hi @andrewbelu !
Sorry for the late reply, I'm trying to reproduce your issue, but it works well on my side.
Here are the steps I followed:
kubectl apply -f examples/cluster-mtls/00-namespace.yaml
kubectl apply -f examples/cluster-mtls/01-postgresql.yaml
kubectl apply -f examples/cluster-mtls/02-temporal-cluster.yaml
# waiting for the cluster to be up and running
kubectl apply -f examples/cluster-mtls/03-temporal-cluster-client.yaml
kubectl cert-manager inspect secret -n demo prod-my-worker-mtls-certificate # using cert-manager kubectl plugin
# exporting certificates
kubectl view-secret prod-my-worker-mtls-certificate -n demo tls.key > /tmp/tls.key
kubectl view-secret prod-my-worker-mtls-certificate -n demo tls.crt > /tmp/tls.crt
kubectl view-secret prod-my-worker-mtls-certificate -n demo ca.crt > /tmp/ca.crt
# exporting SERVER_NAME
export SERVER_NAME=$(kubectl get temporalclusterclient my-worker -o=template="{{.status.serverName}}")
# on another shell:
kubectl port-forward service/prod-frontend -n demo 7233:7233
# then same test:
openssl s_client -connect localhost:7233 -cert /tmp/tls.crt -key /tmp/tls.key -CAfile /tmp/ca.crt -servername $SERVER_NAME

Here is the result I get:
Connecting to ::1
CONNECTED(00000005)
depth=2 CN=Root CA certificate
verify return:1
depth=1 CN=Frontend intermediate CA certificate
verify return:1
depth=0 CN=Frontend Certificate
verify return:1
---
Certificate chain
 0 s:CN=Frontend Certificate
   i:CN=Frontend intermediate CA certificate
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Jun 13 14:20:27 2024 GMT; NotAfter: Jun 13 15:20:27 2024 GMT
 1 s:CN=Frontend intermediate CA certificate
   i:CN=Root CA certificate
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Jun 13 14:20:07 2024 GMT; NotAfter: Jun 13 15:50:07 2024 GMT
---
Server certificate
-----BEGIN CERTIFICATE-----
OMITED
-----END CERTIFICATE-----
subject=CN=Frontend Certificate
issuer=CN=Frontend intermediate CA certificate
---
Acceptable client certificate CA names
CN=Root CA certificate
Requested Signature Algorithms: RSA-PSS+SHA256:ECDSA+SHA256:Ed25519:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA384:ECDSA+SHA512:RSA+SHA1:ECDSA+SHA1
Shared Requested Signature Algorithms: RSA-PSS+SHA256:ECDSA+SHA256:Ed25519:RSA-PSS+SHA384:RSA-PSS+SHA512:RSA+SHA256:RSA+SHA384:RSA+SHA512:ECDSA+SHA384:ECDSA+SHA512
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 3652 bytes and written 2352 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_128_GCM_SHA256
Server public key is 4096 bit
This TLS version forbids renegotiation.
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)

Is there something I'm missing to reproduce your issue ?

I am troubleshooting a similar issue and figured I'd weigh in here so we can make progress on #746.  @andrewbelu, in your error I see error: InvalidCertificate(NotValidForName), which makes me think it's the server name.  Temporal's Go example for this also doesn't include the server name, so I was running into the same issue.  Once I added it, things started working for me:
temporalHostPort := os.Getenv("TEMPORAL_ADDRESS")
temporalNamespace := os.Getenv("TEMPORAL_NAMESPACE")
temporalTLSCert := os.Getenv("TEMPORAL_TLS_CERT")
temporalTLSKey := os.Getenv("TEMPORAL_TLS_KEY")
temporalTLSCACert := os.Getenv("TEMPORAL_TLS_CA_CERT")
temporalTLSServerName := os.Getenv("TEMPORAL_TLS_SERVER_NAME")

serverCAPool := x509.NewCertPool()
b, err := os.ReadFile(temporalTLSCACert)
if err != nil {
	log.Fatalln("Unable to read server CA certificate", err)
}
if !serverCAPool.AppendCertsFromPEM(b) {
	log.Fatalln("Unable to append server CA certificate to pool")
}

clientOptions := client.Options{
	HostPort:          temporalHostPort,
	ConnectionOptions: client.ConnectionOptions{
		TLS: &tls.Config{
			GetClientCertificate: func(info *tls.CertificateRequestInfo) (*tls.Certificate, error) {
				cert, err := tls.LoadX509KeyPair(temporalTLSCert, temporalTLSKey)
				if err != nil {
					return nil, err
				}
				return &cert, nil
			},
			RootCAs:    serverCAPool,
			ServerName: temporalTLSServerName,
		},
	},
	Namespace:         temporalNamespace,
}

c, err := client.Dial(clientOptions)
if err != nil {
	log.Fatalln("Unable to create client", err)
}
defer c.Close()

Looking at the Python docs, it looks like there's a domain property that could be set.  Does setting that fix your issue?
My issue is that once certificates expire, things don't seem to refresh, which I'll follow up in the relevant issue.


Reuse summary card as scan card

Screenshots:

Note that this is currently suffering from an overflow.

Thanks for your help on the project @slava-sh, have a nice time

Slava, thank you for all your contributions and support. Good luck in your next adventure, I'll take it from here :)

Please see #645


Disable Intel's edger8r from looking for GCC

This resurrects a patch we'd previously made and was lost when we pulled
upstream edger8r code from Intel. This patch should silence the warning
on Windows that the preprocessor was not found.

This change was resurrected from #1781.

Sorry @anitagov, I had no idea about this thing and should have looked further.

bors r+


feat(treeview): Added support for ts extension

Should I also update treeview.min.css?

Yes please run the build command and include the changed files. Thanks!


test(multicluster): add initial telemetry validation test

Adds initial telemetry tests to the multicluster scenarios.
This PR is the starting point for validation of multicluster telemetry. At this point in time, it simply attempts to validate that source_cluster and destination_cluster labels are available in the telemetry. It does not attempt to validate that they have any specific value or similar. These tests will hopefully be expanded upon in the 1.7 release cycle.
[ X ] Networking
[ X ] Policies and Telemetry
[ X ] Test and Release

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test all

@douglas-reid: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
872f83f2fd604f0663552cd9592d11443bb7e7a0
link
/test lint_istio

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.

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
872f83f2fd604f0663552cd9592d11443bb7e7a0
link
/test lint_istio

integ-local-tests_istio
872f83f2fd604f0663552cd9592d11443bb7e7a0
link
/test integ-local-tests_istio

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.

@douglas-reid: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
872f83f2fd604f0663552cd9592d11443bb7e7a0
link
/test lint_istio

integ-local-tests_istio
872f83f2fd604f0663552cd9592d11443bb7e7a0
link
/test integ-local-tests_istio

integ-multicluster-k8s-tests_istio
872f83f2fd604f0663552cd9592d11443bb7e7a0
link
/test integ-multicluster-k8s-tests_istio

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.

@howardjohn my current thinking is that if you want to do any advanced querying or the like, I think using prom makes sense (no reason to rewrite prom in a test). probably also makes sense if you are testing for something that involves wider validation, including validating prom functionality itself.
here, i just wanted to start simple and check labels at the source/destination without over-complicating the tests. once I get it working, and we start to improve these tests, maybe it will make sense to add some prom querying??

/test integ-multicluster-k8s-tests_istio

I have thought about it a bit before. One benefit is its more direct, without needing to go through scraping intervals, etc so its probably a bit quicker. We could also utilize the clear stats endpoint which would be useful for negative testing for example. Obvious downside is we aren't fully testing prometheus and re-implementing parts of prom. I think it makes sense here, especially since I don't think we have a prometheus config that works with all of these multi cluster scenarios (or do we? If we do we probably do want to use it as a means of testing it?)

I think it makes sense here, especially since I don't think we have a prometheus config that works with all of these multi cluster scenarios (or do we? If we do we probably do want to use it as a means of testing it?)

I don't think we have a good one, and tailoring one that makes easier cross-cluster validation will probably take some work.
We should probably work to add one and expand the existing reachability tests, etc., to check prom to confirm telemetry matches.

Direct scraping is fine for this test.
We do not need retest all stats testing that we do within a cluster. We are primarily testing that metadata exchange happens correctly. Stats plugin proper is not aware of clusters beyond how it affects labels.
@douglas-reid if we come across specific tests that require full Prometheus, we should add it. Until then this is great.
The types of tests I am thinking about are complex tests, say locality based load balancing test that verifies behaviour using stats. Those will need full prom.

Gentle ping for review here.


The project name is already in use when creating a new project

What happened:
I have user A with a project named dev.
If I try to create a new user B and a new project dev, I've got the error The project name is already in use.
What you expected to happen:
User B can create a project named dev.
How to reproduce it (as minimally and precisely as possible):

Log in as user A
Create project "dev"
Log in as user B
Create project "dev"

Anything else we need to know?:
Environment:

Operating system:
Browser and version:
Yorkie version (use yorkie version):
Yorkie JS SDK version:

@hackerwins @chacha912  Could I try this issue?

@jeonjonghyeok Of course. Thank you for your interest.

@jeonjonghyeok Of course. Thank you for your interest. It would be good to discuss some solutions before implementation.

@hackerwins I have now confirmed the changed message.
I've already worked on it, can I discuss it in PR? https://github.com/yorkie-team/yorkie/pull/406

This was fixed by https://github.com/yorkie-team/yorkie/pull/418.


basic italics patch

Basic italics patch. I've removed all of my kerning patch work from this so it's just the italics patch.
Nothing really new here, I just wanted to have an artifact as Hit By a Bus Security:tm:
I don't think this belongs in any official patches until people have run it enough to know it does not cause crashes 1/3 of the time.

just merging for one fewer PR. as promised in pr description, there's still more research involved.


Block size unexpected, causing file read throw I/O error

Alluxio Version:
2.7.2
Describe the bug
User fail to read multiple files consistently:

If using Alluxio command to list/copyToLocal/free, receiving below error:
[root@jssz-admpi-147 alluxio-2.7.2]# alluxio fs ls /379009661_nb2-1-74/ | grep 20205
833320       PERSISTED 08-16-2021 20:09:52:000 100% /379009661_nb2-1-74/020205.png
317       PERSISTED 08-16-2021 20:09:52:000   0% /379009661_nb2-1-74/020205.json
[root@jssz-admpi-147 alluxio-2.7.2]# alluxio fs copyToLocal /379009661_nb2-1-74/020205.png .
Block<PHONE_NUMBER>2512 is expected to be 833320 bytes, but only 0 bytes are available. Please ensure its metadata is consistent between Alluxio and UFS.
[root@jssz-admpi-147 alluxio-2.7.2]# alluxio fs free /379009661_nb2-1-74/020205.png
java.util.concurrent.TimeoutException: Timed out waiting for file to be freed. Another user may be loading it. options: WaitForOptions{interval=1000, timeout=10000} last value: false
The next time try copyToLocal, it succeed.
If we try get log from worker, didn't find anything related to "48551283392512" and "Error"
root@jssz-coeus-alluxio-01:~# k logs qa-frames-worker-4vwpr alluxio-worker | grep rror
root@jssz-coeus-alluxio-01:~# k logs qa-frames-worker-4vwpr alluxio-worker | grep<PHONE_NUMBER>2512
Both return nothing.
And user reported more files hitting this issue, using stat can see below information
[root@jssz-admpi-147 alluxio-2.7.2]# alluxio fs stat /248251145_nb2-1-64/023299.png
/248251145_nb2-1-64/023299.png is a file path.
URIStatus{info=FileInfo{fileId=10920591884287, name=023299.png, path=/248251145_nb2-1-64/023299.png, ufsPath=s3://cv_data/qichang/qa/frames/248251145_nb2-1-64/023299.png, length=1064509, blockSizeBytes=16777216, creationTimeMs=1649229190341, completed=true, folder=false, pinned=false, pinnedlocation=[], cacheable=true, persisted=true, blockIds=[10920575107072], inMemoryPercentage=0, lastModificationTimesMs=1629259544000, ttl=-1, lastAccessTimesMs=1649363203245, ttlAction=FREE, owner=root, group=root, mode=448, persistenceState=PERSISTED, mountPoint=false, replicationMax=1, replicationMin=0, fileBlockInfos=[FileBlockInfo{blockInfo=BlockInfo{id=10920575107072, length=1064509, locations=[BlockLocation{workerId=2768092020693031836, address=WorkerNetAddress{host=<IP_ADDRESS>, containerHost=, rpcPort=20200, dataPort=20200, webPort=20201, domainSocketPath=, tieredIdentity=TieredIdentity(node=<IP_ADDRESS>, rack=null)}, tierAlias=SSD, mediumType=SSD}]}, offset=0, ufsLocations=[]}], mountId=1, inAlluxioPercentage=100, ufsFingerprint=TYPE|FILE UFS|s3 OWNER|_ GROUP|_ MODE|448 CONTENT_HASH|a8c1246ad132fe54567ac7d961273a2b , acl=user::rwx,group::---,other::---, defaultAcl=}, cacheContext=null}
Containing the following blocks:
BlockInfo{id=10920575107072, length=1064509, locations=[BlockLocation{workerId=2768092020693031836, address=WorkerNetAddress{host=<IP_ADDRESS>, containerHost=, rpcPort=20200, dataPort=20200, webPort=20201, domainSocketPath=, tieredIdentity=TieredIdentity(node=<IP_ADDRESS>, rack=null)}, tierAlias=SSD, mediumType=SSD}]}

Occur
Block<PHONE_NUMBER>2512 is expected to be 833320 bytes, but only 0 bytes are available. Please ensure its metadata is consistent between Alluxio and UFS.

@beinan looks like a similar issue happens.
What could be the possible reasons that a block is broken?

have blocks left by the previous Alluxio cluster, didn't fully clean up when launching the new alluxio cluster, and have the same block id in the new cluster.
block itself broke after successfully written (unlikely?)

FYI @yuzhu

Occur
Block<PHONE_NUMBER>2512 is expected to be 833320 bytes, but only 0 bytes are available. Please ensure its metadata is consistent between Alluxio and UFS.

@beinan looks like a similar issue happens. What could be the possible reasons that a block is broken?

have blocks left by the previous Alluxio cluster, didn't fully clean up when launching the new alluxio cluster, and have the same block id in the new cluster.
block itself broke after successfully written (unlikely?)

Yes, @yuzhu and I have seen the same symptom when rolling back the journal.   As you said, there might be block files that have not been cleaned up. I'm still thinking to keep a last modified time in the metadata of each block will help alluxio kickout the staled or orphan blocks.

From @Nizifan, When cache is incorrect, can we delete the block and read from UFS to get the correct one

@beinan I discussed with @Nizifan  that
in Fluid with 0.7, worker is launch with statefulset, which means that the worker can be launched on random machine.
e.g. The kubernetes cluster has 7 nodes, we want 5 workers, the workers can be launched on one of the machine.
The worker may be randomly restarted and relaunch on other machines, but we want to reuse the local storage if any and if master has not been formatted.
e.g.
Master start on Node1
WorkerA starts on Node2
WorkerA write some blocks in Node2.
WorkerA stops.
after a while
WorkerB starts on Node2, workerB wants to reuse WorkerA's data.
In this case, we may not want to record the worker_format_time, only <cluster_id> or say master_format_time / master_clean_start_time is needed.


cells/klayout/pymacros/README: should document how to use pcells

Expected Behavior
https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/tree/main/cells/klayout/pymacros README should document how to generate gds using klayout and how to regenerate the tests in https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/tree/main/cells/klayout/pymacros/testing.
Actual Behavior
https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/tree/main/cells/klayout/pymacros assume developers/contributors are familiar with the process to generate pcells using klayout and update testcases gds.

@proppy and @mkkassem
Please check the usage in this document:
https://github.com/mabrains/globalfoundries-pdk-libs-gf180mcu_fd_pr/blob/main/cells/klayout/pymacros/README.md

@proppy About regression, please find more information here:
https://github.com/mabrains/globalfoundries-pdk-libs-gf180mcu_fd_pr/blob/main/cells/klayout/pymacros/testing/README.md

@mkkassem @atorkmabrains I think you can easily create a separate pull request for the pcell changes this way:
# clone upstream repo
git clone https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr
cd globalfoundries-pdk-libs-gf180mcu_fd_pr
# add your fork remote
git remote add mabrains git@github.com:mabrains/globalfoundries-pdk-libs-gf180mcu_fd_pr.git
git fetch mabrains
# create feature branch
git checkout -b improve-pcell-docs
# checkout (only) pcells changes
git checkout mabrains/main cells/klayout/pymacros
# create a new collapsed commit for (only) pcells changes
git commit -m 'cells/klayout/pymacros: improve documentation'
# push back to your fork
git push mabrains improve-pcell-docs
# create the pull request

[ ] @proppy I have discussed that with @mithro before. That can't be done. Primitive renaming is a lateral change that affects everything and if you take one part and leave the other parts of the PDK unchanged, it will break the PDK. And there is another issue, doing PR will not work as well as the amount of changes are massive. And github doesn't allow that. I have shown this to @mithro and @mkkassem. That's why I was asking you guys to get the primitives renaming PRs in first before we change anything.

I think that if you:

take the instruction in https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/issues/70#issuecomment-1311156971
force push to https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/pull/32 branches (https://github.com/mabrains/globalfoundries-pdk-libs-gf180mcu_fd_pr/tree/primitives_names_part1)
mark it as fixing this issue

That should be enough to provide a coherent set of change to review and merge (that include both naming change and appropriate documentation update to evaluate it).

@proppy I have all updates made in mabrains branch. I advise you to just replicate what you have here with what's in Mabrains.

@atorkmabrains so you'd prefer me to do the changes highlighted in https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/issues/70#issuecomment-1311156971 and https://github.com/google/globalfoundries-pdk-libs-gf180mcu_fd_pr/issues/70#issuecomment-1311302640 rather than giving it a go?

@proppy My advise is basically to replace what you have here with what's in Mabrains fork. And after that let review one by one. If there are any other changes required, we could handled them one by one. If you have doubts in my proposal, please go ahead and check the diff against what's in Mabrains. I'm not responsible of any issue if you didn't update to match Mabrains repo.

And after that let review one by one. If there are any other changes required, we could handle them one by one.

I'd prefer for us to work with the pull request as I suggested. I will go ahead and update them then.

@proppy Please do whatever you need at your end. But make sure that at the end that you match what I have on Mabrains side.
I believe you misunderstood me btw, what I'm saying is that you take what I have and push it to Google repo. Once that's done we could start adding PRs on Google side.
Please try to do that at your end.

@FaragElsayed2 We need to follow up on this in efabless version.


Recently uploaded is showing migrated items

The recently uploaded list is showing items that were uploaded in 2015.  I'm guessing it is using system date created instead of the date created field.

https://github.com/projecthydra/sufia/blob/master/app/controllers/concerns/sufia/homepage_controller_behavior.rb#L48-L50  Should be 'date_uploaded_dtsi'


Add new packages for networking support

I'm trying to work on a web browser and I was wandering if it is possible to add a new package into the snakewm like requests

I'm trying to work on a web browser and I was wandering if it is possible to add a new package into the snakewm like requests (https://pypi.org/project/requests/)

While I'm not entirely sure on Josh's view on new packages, extra Pip packages can be added to the snakeware bootable image relatively easily. (And if network support is planned, requests seems like an essential package to have)
ps: From the issue title, it feels like you're asking if snakeware works inside a web browser. You might want to change that to clarify it a little bit.

We can definitely add more packages, we're working on installing packages in a cross-platform way during the build process as we plan to target Raspberry Pi in addition to x86. That said, you'll probably want to hold off on implementing a full web browser until we get networking in place, but you could definitely get started on an HTML parser/renderer

Ok, was working on exactly that, trying to render simple html webpages.

@lmagoncalo see py browser engines

One possibility would be to use QtWebEngine via PySide2 (Qt for Python).
Qt can render into an SDL OpenGL context: https://forum.qt.io/topic/68383/qtquick-into-an-sdl2-window/4
PySide2 doesn't yet support cross-compiling for ARM, but it can actually built inside an ARM environment. (see https://bugreports.qt.io/browse/PYSIDE-802)

One possibility would be to use QtWebEngine via PySide2 (Qt for
Python).

QtWebEngine is WebKit (or Blink, not sure), yeah?
I'm not entirely sure if embedding an entire browser engine larger than
the OS itself would be a great idea, especially on lower-end computers.
Something like NetSurf would probably be better, assuming you don't
mind it taking over the entire framebuffer and running fullscreen.

Qt can render into an SDL OpenGL context:
https://forum.qt.io/topic/68383/qtquick-into-an-sdl2-window/4 PySide2

Currently, Snakeware doesn't use OpenGL, but rather draw directly into
the framebuffer.

doesn't yet support cross-compiling for ARM, but it can actually
built inside an ARM environment. (see
https://bugreports.qt.io/browse/PYSIDE-802)

Might be an issue for Raspberry Pi builds, as do you really want to
compile something big like Qt (and something even bigger, like WebKit)
in a Pi?


Fix the azure pipeline to use a non-deprecated Windows version

I'm currently seeing failures in #1039 due to a brownout of the win2016 azure image. This updates the pipeline to use windows 2019 (which requires updating the visual studio version).
See also https://github.com/actions/virtual-environments/issues/4312
I noticed that there is a possibility to test against x64 and x86, but wasn't sure how to enable this. Something that may be interesting for a future MR.

   Perhaps we have to clear them up as well.

E       Max relative difference: 2.1075528e-16
E        x: array([1.710838e+19, 8.347277e+18, 9.717432e+18, 5.238146e+18,
E              3.817785e+18, 1.656521e+19, 1.271839e+19, 4.426652e+18,
E              1.835957e+19, 1.335125e+19, 5.382931e+18, 1.341460e+19,...

E        y: array([7.819001e+18, 2.240689e+18, 1.198326e+19, 4.609387e+18,
E              7.140427e+18, 1.073009e+19, 1.269285e+19, 1.469904e+19,
E              1.186424e+17, 2.673267e+18, 5.310913e+17, 1.684725e+19,...

test\jpypetest\test_buffer.py:146: AssertionError

Fundamentally, I think this test is showing that there is a difference between Java's uint64 to float/double conversion and that of numpy. This is a bit of a surprise, but not entirely implausible.
Unfortunately this test is not changed/fixed by #1039.
In order to proceed, I think moving to assert_arrays_almost_equal makes sense, but perhaps @Thrameos has some other ideas?

Now I think there is a completely unrelated failure on Windows & Mac:
Collecting pyinstaller==4.0
  Downloading pyinstaller-4.0.tar.gz (3.5 MB)
     ---------------------------------------- 3.5/3.5 MB 27.7 MB/s eta 0:00:00
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'done'
  Preparing metadata (pyproject.toml): started
  Preparing metadata (pyproject.toml): finished with status 'error'
  error: subprocess-exited-with-error

  Preparing metadata (pyproject.toml) did not run successfully.
  exit code: 1

  [42 lines of output]
  Traceback (most recent call last):
    File "c:\hostedtoolcache\windows\python\3.8.10\x64\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 363, in <module>
      main()
    File "c:\hostedtoolcache\windows\python\3.8.10\x64\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 345, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File "c:\hostedtoolcache\windows\python\3.8.10\x64\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 164, in prepare_metadata_for_build_wheel
      return hook(metadata_directory, config_settings)
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-lc82mmak\overlay\Lib\site-packages\setuptools\build_meta.py", line 188, in prepare_metadata_for_build_wheel
      self.run_setup()
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-lc82mmak\overlay\Lib\site-packages\setuptools\build_meta.py", line 281, in run_setup
      super(_BuildMetaLegacyBackend,
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-lc82mmak\overlay\Lib\site-packages\setuptools\build_meta.py", line 174, in run_setup
      exec(compile(code, __file__, 'exec'), locals())
    File "setup.py", line 75, in <module>
      setup(
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-lc82mmak\overlay\Lib\site-packages\setuptools\__init__.py", line 87, in setup
      return distutils.core.setup(**attrs)
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-lc82mmak\overlay\Lib\site-packages\setuptools\_distutils\core.py", line 122, in setup
      dist.parse_config_files()
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-lc82mmak\overlay\Lib\site-packages\setuptools\dist.py", line 850, in parse_config_files
      setupcfg.parse_configuration(
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-lc82mmak\overlay\Lib\site-packages\setuptools\config\setupcfg.py", line 167, in parse_configuration
      meta.parse()
    File "C:\Users\VssAdministrator\AppData\Local\Temp\pip-build-env-lc82mmak\overlay\Lib\site-packages\setuptools\config\setupcfg.py", line 446, in parse

@pelson  I have fixed the azure pipeline so I am going to close this one for now.   I fixed the deprecation warnings in a different way.   The names for types were changed to use an underscore where there was a conflict.   Changing "np.bool" to "bool" would have caused a bunch of the tests to become redundant so I made it "np.bool_" which though still redundant (bool==np.bool_) it at least maintains the spirt of the test.   There is a function "np.allclose" which I could fix the remaining conversion tests with so we don't need to implement approximately equals ourselves.
Some of your changes look useful, but I don't have time to sort the good from the unnecessary currently.   Sorry for not getting to this quickly.

@pelson  I have fixed the azure pipeline so I am going to close this one for now.   I fixed the deprecation warnings in a different way.   The names for types were changed to use an underscore where there was a conflict.   Changing "np.bool" to "bool" would have caused a bunch of the tests to become redundant so I made it "np.bool_" which though still redundant (bool==np.bool_) it at least maintains the spirt of the test.   There is a function "np.allclose" which I could fix the remaining conversion tests with so we don't need to implement approximately equals ourselves.
Some of your changes look useful, but I don't have time to sort the good from the unnecessary currently.   Sorry for not getting to this quickly.

Thanks. Will pick up some of the good bits and propose them.


ACR base feature branch to create pipelines

Getting ACR into a feature branch before working on auth flow. Next step is to create a live tests pipeline.


Bug: ffmpeg needs to be updated to 5.1 (currently 4.3.6), causing errors

Describe the bug

When downloading YouTube videos that require merging fragment types 303 and 251 causes errors like this:
[download] Destination: xxxxx.f303.webm
[download] 100% of  134.09MiB in 00:00:52 at 2.56MiB/s
[download] Destination: xxxxx.f251.webm
[download] 100% of   12.85MiB in 00:00:00 at 15.43MiB/s
[Merger] Merging formats into "xxxxx.webm"
ERROR: Conversion failed!

This is an issue with the included old version of ffmpeg (https://github.com/yt-dlp/yt-dlp/issues/871). They says ffmpeg 5.1 fixes this VP9 bug.
Steps to reproduce

Run ArchiveBox on a page embedding a YouTube video with fragments 303 and 251 (seems like VP9 videos).
Media snapshot fails.

Screenshots or log output

[download] Destination: xxxxx.f303.webm
[download] 100% of  134.09MiB in 00:00:52 at 2.56MiB/s
[download] Destination: xxxxx.f251.webm
[download] 100% of   12.85MiB in 00:00:00 at 15.43MiB/s
[Merger] Merging formats into "xxxxx.webm"
ERROR: Conversion failed!


In DOM Effects, let array children contain anything

Currently they can't contain events or attribute objects, I think.
Another option: add a React-style ´fragment()´. I tried this briefly, using a DocumentFragment, but couldn’t get it to work immediately.

The DocumentFragment option doesn’t work because when a child doesn’t re-run, it still returns the same DocumentFragment, but that DocumentFragment is now empty, and its contents never make it back into it before it gets flushed to the document again.


Extra character at the end of the display in SerialDisplay.ino

While testing the SerialDisplay.ino example, after any string I would send to the display through the serial monitor, some extra character is added at the end (see picture attached right below).

By the way, if I upload the CustomCharacter.ino example beforehand, this extra character appears to be exactly the same one as the frownie character, if that can help. My guess is that this extra character comes from some memory space at a specific address of the Arduino card.
Can you help on how to remove this extra character from the LCD display?

Hello,
What is the microcontroller board you are using?

Hello.
The Arduino card is a Genuino 101 one.

Hello,
I will test this and get back to you.

Hello,
I have tested the same "SerialDisplay.ino example"  with my Arduino UNO board and it worked well. There was no extra character displayed.
Could you please share a photo of your hardware connection?
Thank you.


Flutter Expense_Project

Describe the project you want to add with tech stack
The Expense Manager Application, using Provider to manage state.
A Flutter sample app that shows a state management approach using the Provider package and shared preferences for saving data in mobile.
Assign this issue to me under GSSOC'23

@MohitGupta121 please assign me this issue


iOS Native: Replication works only once

Replication on iOS devices works only for some short period of time. This issue was previously reported to Dersim, but he told us that it might be related to inappropriate implementation of peer pool policy manager. We tried multiple solutions and after that, it still behaves the same, even using default one.
We also asked Enrico about that if he could investigate it further.

Most of the bugs causing replication to stop working have been fixed in https://github.com/thaliproject/thali-ios/commits/master-enrico-error-handling-tmp


Lock into landscape

Only for survey

➤ Ben Hylak commented:
Alex Tacescu is it possible to only lock in landscape for indicators and review? I think background questions are more usable in portrait..

➤ Ben Hylak commented:
Not lock for background questions


difference between this repo and the online demo

Could you please elaborate a bit on the differences between this repo and the online demo?
The official online demo seems to have better generation quality. The images I generated using this repo are also different from the ones generated by the online demo despite using the same seed, CFG, etc. This repo also does not have the "enhance non-face region" option. What could be the issue?

We will update soon to make them consistent.

We will update soon to make them consistent.

so many people are using your online demo and I must wait more than 20 mins. If you can make the local demo and online demo consistent, it will be nice since we can use our machine


return curried function in compose

I'm new to Ramda but this should solve #736.

We still need to decide whether before we take on how, I'm afraid.

ping

once #771 is in, i think it makes sense to do this as well

I will rebase as soon as #771 is in.

although #771 got whacked, i think we should go ahead with this, essentially returning curryN(max(fns), f) as we are doing elsewhere now,

I'm still nervous about this.  I agree that this should be the default behavior, but I really would like to find a way to offer a version of compose / pipe that don't do this in the case that the returned function has named optional parameters.

#985 is how converge works today. compose should have the same semantics IMO.

#985 is how converge works today. compose should have the same semantics IMO.

I think so too.
I rebased this.

We've switched from using four spaces for indentation to two spaces. Please adjust the indentation accordingly. :)

Also, we no longer update dist/ramda.js with each commit, so you should revert the changes to that file.

Yop, just saw that it will need more than just rebasing :smile: .

Now, it should be fin.

This looks good! It might be clearer to use an uncurried function in the test cases. As it stands one wonders whether R.compose(R.join(','), R.concat) evaluates to a curried function because R.concat is a curried function.

now the question is, do we need to have composeV (for variadic) with the old semantics to cover @CrossEye 's case?
otherwise, herd of :cow2:

I really hate having so many variants of this basic function.
But I think not offering that alternative does a big disservice to JS users who are used to working with functions with optional parameters, especially a final options argument.

Superseded by #1260


Does this project have future or not please answer?

Recommendation: Answered. Close issue.
Hi, I'm not affiliated with this repo or project, but I wanted to say that this is a very poor title for an issue. I agree with you, I enjoy Kiwi and want to see the new issues/security updates/etc., but please use proper titles and terminology when interacting with dev communities and dev projects, use search to make sure that no one else has already created an issue or discussion about this, etc. A much better title would be: "Is This App Still Being Maintained?" adding "please answer?" to your title doesn't get you any faster support. I'm replying just because I happen to be looking through the issues of Kiwi to find some information about something.
The maintainer replied, and stated that Kiwi is still in active development, and changes are expected to be released in the next several weeks. I made a comment here about why this takes time.


Add grab-points to climbing

This PR adds grab-point support to climbable objects.
https://github.com/GodotVR/godot-xr-tools/assets/1863707/25df6559-37bf-4dd5-b4fc-8327ba937f5b

tested, lgtm


Tweak expo-modules-core hack patch

Per expo recommendation in https://bluesky-builders.slack.com/archives/C05R8KJK1PC/p1723836730258259, tweaking the patch added in https://github.com/bluesky-social/social-app/pull/4942.

Test failure is okay, bug I still need to fix in that workflow when applying a patch update.


[Bug]: Can't start appsmith local

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Error: http://localhost/api/v1/tenants/current 404 status
Steps To Reproduce
I'm following this guide:
-https://github.com/appsmithorg/appsmith/blob/release/contributions/ServerSetup.md
and

https://github.com/appsmithorg/appsmith/blob/release/contributions/ClientSetup.md

When yarn start.  After sign up and sign in. I'm facing this error:
http://localhost/api/v1/tenants/current (404)

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Self Host

Can you please try this once with the release branch?


Option to add prefix to title

It would be nice to have a config option to add a prefix to the title.

title_prefix and title_postfix options are added in version 1.16.


feat: Add support for integration testing

Does not need to be merged until integration testing is finalized
Adds support for integration testing

Adds manifests used by integration testing
Adds removal_policy params to modules utilizing ecr.Repository. Default is to Retain which will not work in integration testing as resources need to be recreated each invocation.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

PR looks good. I have a question on the contents of the integ/addf, integ/idf yaml files. I will sync up offline.


fixed vim-mode autoCloseMath incompatibility

Fixed an issue with the builtin vim-mode, where while being in normal-mode and using '$' to jump to end-of-line, the plugin would wrongly insert a single '$' sign.
How to reproduce the bug in the unfixed version:

enable builtin 'Vim key bindings'
in normal-mode, press '$' to go to end-of-line

As an unexpected side effect, my editor also removed a lot of trailing whitespaces. If that is an issue, please tell me so I can correct it.

Hi! @wintermute-cell
Really thank you so much for the fix!
pardon me that I am not so familiar with Vim. I realize after merging, vscode reports that it cannot find "vim-mode-change".
Is there a specific package I need to install through npm?
thank you!

Hi! @wintermute-cell
I noticed a few issues.
As we set vimIsInsert default to "false", and used "&&"  at line 133 to check for vimIsInsert=true before applying autoCloseMath, this would mean that under the usual mode (vim key bindings turned off), the vimIsInsert variable is always false, and autoCloseMath will never be applied.
I suppose we may need to an another if clause to check whether vim key bindings is turned on before checking vimIsInsert. I haven't yet found a way to check if vim key bindings is on though.
also, I added a few lines at onunload to unload the registered code mirror for vim-mode-change.

@wintermute-cell
sorry, could you kindly open another new pull request for this? thanks


Graph of DetectNet on KITTI dataset not looks ok

Hi,
I followed the demo for DetectNet with the KITTI dataset (6373 images on train folder and 1108 on validation folder)
I set the model as shown in the tutorial but i got mAP, precision and recall 0(zero) for all the epoch.

Can you please help me understand what could be wrong
Thanks,
BTW: i set the prototxt for detectNet as given in the example

Could you include the legend? what is the mAP you get?

Hi,
The mAP was zero for all 30 epochs.
But than i just increase the Training epochs to 300 and now is seems ok.
Actually it worth mention in the docs that meaningful model only start after 100 epochs for this GoogleNet model of DetectNet.
Thanks.

I got the same problem. how can I change my train process ?  which parameter is wrong ?


Audio PR 5 - Audio Augmentations 1 [Spectrogram]

Contains support for Spectrogram

@swetha097 Please resolve merge conflicts and address PR comments


DNCENGMAC017 might have a bad provisioning profile

A customer reported that the DNCENGMAC017 machine might have a bad provisioning profile. I took it offline and will have a look at it.

All workitems have been failing on the machine for a while

The last helix log: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-92471-merge-c9965cd9637048d68c/iOS.Device.Aot.Test/1/console.52384849.log?helixlogtype=result

dbug: warning HE1902: The application 'net.dot.iOS.Device.Aot.Test' has been signed with a provisioning profile which does not include the device 'Dncengosx165'.

@ilyas1974 , we need to add this machine into the profile in the Apple developer account.  I talk to Premek - he is not able to do this.

We have a document https://dev.azure.com/dnceng/internal/_wiki/wikis/DNCEng Services Wiki/862/Apple-(iOS-tvOS)-signing-certificates?anchor=adding-new-apple-devices - but I believe, I'd need a help.


default password in config file

Fix for issue raised no #88

hi @tarun1992 ,
Thanks for the contribution! I just posted a comment about this one in the thread here:
https://github.com/nielsdejong/neodash/issues/88
I'm thinking to make this config.json field optional, for example:
dispatch(setConnectionProperties(config['standaloneProtocol'], config['standaloneHost'], config['standalonePort'], config['standaloneDatabase'], state.application.connection.username, config['standalonePassword'] ? config['standalonePassword'] : state.application.connection.password));

This way the application will pick up the hardcoded password if specified in config.json, otherwise it will default to state.application.connection.password (the latest in the application cache). What do you think?

Another thought: we should probably add the same thing for the username here, so that it's in sync.

That's a very good idea. I really like that.

Hi @tarun1992 ,
I've made some small changes to this one to pick up the standaloneUsername and standalonePassword fields only if they are specified in the config.json file.
The behaviour is now like this:

If standaloneUsername/standalonePassword are not specified (default behaviour), do the same thing as before. The connection modal is presented to the user with all fields prefilled except the username/password.
If standaloneUsername/standalonePassword are specified in config.json, pick these up, and automatically make the connection to the database + load the dashboard. The connection screen is skipped in its entirety.

Best,
Niels


Option to not close socket on server shutdown

Add option of not closing the socket of TcpListener when server is shutdown.
Use case: When socket has been sent to another process as part of seamless restart, socket must not be closed.

This is currently possible by creating custom AddrIncoming, but that requires duplicating most of server/tcp.rs - over 200 lines of duplicated code just to add custom drop - so that isn't a good solution.

This feature wouldn't be of any use without first having a unix listener which supports ancillary data - and as Rust doesn't have one, I'll just close this.


[Question] About *network.Session and connection pool

Hi @sijms! Firstly great thanks to you, I appreciate your work on this project.
My question is this: when I invoke DB methods(*sql.DB) by several goroutines at once I get this:
panic: runtime error: invalid memory address or nil pointer dereference
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x972e75]

goroutine 92 [running]:
github.com/sijms/go-ora/v2/network.(*Session).ResetBuffer(...)
        /workspace/vendor/github.com/sijms/go-ora/v2/network/session.go:157
github.com/sijms/go-ora/v2.(*defaultStmt).Close(0x0?)
        /workspace/vendor/github.com/sijms/go-ora/v2/command.go:1378 +0x35
panic({0xc9a700, 0x17cc560})
        /usr/local/go/src/runtime/panic.go:838 +0x207
github.com/sijms/go-ora/v2/network.(*Session).ResetBuffer(...)
        /workspace/vendor/github.com/sijms/go-ora/v2/network/session.go:157
github.com/sijms/go-ora/v2.(*RefCursor).Query(0xc00032a6e0)
        /workspace/vendor/github.com/sijms/go-ora/v2/ref_cursor.go:98 +0xff

This is happening when database/sql connection pool maxIdleCount < number of goroutines spawned.
It's ok and expected that not all goroutines gets their connection from pool. But panic here is a bit suprising.
Is this expected behaviour? Or am I miss something?
Thanks!
P.S. The DB methods I use does not share any common resources(refcursors) except *sql.DB itself.

would you test this code

Ок, I got it) Thanks @sijms! I'll close this issue.


What is the recommended way of testing workflow?

Hey @MaksimRT, It'd help to have more details on what you're trying to achieve, preferably with an example. I'm not sure if you're looking to test Workflow execution as an integration test, or to test a specific task type.
If it is integration testing a workflow, you can define workflow executions with fake data and run regression tests on your test cluster or a container.

Hi @kishorebanala! Thank you for reply!
Yes, I want to run an integration test.
I want to check that all steps (fork, join, if, switch and order of execution) is executed correctly based on input data.
I have to use the following API to do this:
GET /workflow/{workflowId}?includeTasks=true
Then I have to parse the result and check it.
Am I right?


flutter build ios default has changed to device. Should be simulator.

It looks like the default may have changed for the: flutter build ios command.
Following the instructions on https://flutter.io/developing-packages/#dart no longer works because:
flutter build ios doesn't build if you don't have a provision profile because the default seems to have changed to build for device. This used to work.
You must run flutter build ios --simulator to generate the project files for xcode properly.

Actually this just seems to be completely broken - the resulting .xcworkspace doesn't run.

/cc @xster

Seems like flutter build ios defaulted to a physical device build since it was created https://github.com/flutter/flutter/commit/3f9dcfe144a769597099755b17281d622aab8775.
https://flutter.io/developing-packages/#dart should definitely be edited to recommend flutter build ios --simulator or flutter build ios --no-codesign or something to avoid these issues.


Uninstall doesn't discuss restoring npm set prefix %NODIST_PREFIX%\bin

Is the correct uninstall procedure to npm config delete prefix?  If so, I can PR this into place.

Yes, I believe that step is missing from the uninstallation steps. It was preventing npm from working correctly after I stopped using nodist and went back to the official node install.

fixed by #84

@lksmth @marcelklehr
Even i uninstalled nodist ......... and unfortunately i missed that step npm config delete prefix
I installed nodejs  now everytime i run npm command it creates a blank 'nodist' directory and that command hangs thr !
How can i solve his ? I have removed all the nodist path and prefixes from env variables.

This is the error when i uninstall Nodist  and install Official Node

c:>npm
Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodist'
at Error (native)
Error: EPERM: operation not permitted, open 'c:\npm-debug.log.5ffe01514ef9d79ff24741e84d83ee33'
at Error (native)

Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodist'
at Error (native)

Error: EPERM: operation not permitted, open 'c:\npm-debug.log.7344b9c6b7a9541fb66fbce5426a4e4f'
at Error (native)

I dont even have Nodist .........or its directory, still its trying to access  nodist !
In official Node's npm home directory i have npmrc file , which says

PREFIX=[$APPDATA]/npm

Check the .npmrc file in your windows user home directory, e.g. C:\Users\your-name-here\.npmrc

Ohh !!  Thanks for the help ..!! Actually am new to node and npm !
I was still looking where that nodist path was coming from !!
Anyways thanks... :) help is appreciated

marcelklehr thank you!

I actually think nodist is good, but nvm is also a good choice; there is a new package available for Windows. I had this issue and saw that @robrich and @marcelklehr conclude on the same answer. Thanks to both of you. This worked for me!


Update mount creation to only use btrfs subvolume id

This is aimed at addressing the flaky btrfs tests. There appears to be a race between creating a subvolume and it showing up in the subvolume map. It is possible this is actually a race between creation and cleanup, but I have not discovered any place where this race occurs. If the flakiness still exists then we can rule out the not found errors. Either way, this change is valid as it avoids unnecessary metadata lookup.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@73ac66e). Click here to learn what that means.
The diff coverage is 83.33%.

@@            Coverage Diff            @@
##             master    #1371   +/-   ##
=========================================
  Coverage          ?   36.31%
=========================================
  Files             ?       23
  Lines             ?     2897
  Branches          ?        0
=========================================
  Hits              ?     1052
  Misses            ?     1608
  Partials          ?      237

Impacted Files
Coverage Δ

snapshot/btrfs/btrfs.go
51.01% <83.33%> (ø)

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 73ac66e...0e28f2c. Read the comment docs.

LGTM


bserver_remote: avoid infinite loop on a complete downgradeRef err

If the network is completely down, this loop will otherwise go forever
since no references will ever be marked as failed and removed.
Issue: KBFS-1236

lgtm


Fix file url placeholder

This placeholder is in the filed which user has to fill when creating new CSV dataset.
However the format of URL in the placeholder is incorrect.
If user enters URL in the form suggested by placeholder (file://home/...  <<-- just 2 slashes) he gets an error 'java.lang.RuntimeException: java.net.UnknownHostException:home'
The correct format is file:///home/... <<-- 3 slashes

+1

Merged on master. Thanks @jhrcek !


TypeError: unsupported operand type(s) for *: 'ZMQIOLoop' and 'float'

Problem description
I am trying to run the TestModel and I have found a TypeError when connecting to AirSim. It seems to me that it could come from the Tornado version, but actually I have tried with more than one version and the problem continues.
Problem details
Details of the problem are as follow:
When I run the script .\AD_Cookbook_Start_Airsim.ps1 landscape, everything runs perfectly in UE4 and AirSim but once I run the Jupyter Notebook (Step 2: "Test the model") as follows, it is when I find the error after the second cell (posted below):
model = load_model(MODEL_PATH)
client = CarClient()
client.confirmConnection()
client.enableApiControl(True)
car_controls = CarControls()
print('Connection established!')
Then I found the folowing error message:

TypeError                                 Traceback (most recent call last)
 in
1 model = load_model(MODEL_PATH)
2
----> 3 client = CarClient()
4 client.confirmConnection()
5 client.enableApiControl(True)
~\PycharmProjects\Cookbook\AutonomousDrivingCookbook-master\AutonomousDrivingCookbook-master\AirSimE2EDeepLearning\AirSimClient.py in init(self, ip)
504         if (ip == ""):
505             ip = "<IP_ADDRESS>"
--> 506         super(CarClient, self).init(ip, 42451)
507
508     def setCarControls(self, controls):
~\PycharmProjects\Cookbook\AutonomousDrivingCookbook-master\AutonomousDrivingCookbook-master\AirSimE2EDeepLearning\AirSimClient.py in init(self, ip, port)
148 class AirSimClientBase:
149     def init(self, ip, port):
--> 150         self.client = msgpackrpc.Client(msgpackrpc.Address(ip, port), timeout = 3600)
151
152     def ping(self):
~\Anaconda3\envs\Cookbook\lib\site-packages\msgpackrpc\client.py in init(self, address, timeout, loop, builder, reconnect_limit, pack_encoding, unpack_encoding)
13
14         if timeout:
---> 15             loop.attach_periodic_callback(self.step_timeout, 1000) # each 1s
16
17     @classmethod
~\Anaconda3\envs\Cookbook\lib\site-packages\msgpackrpc\loop.py in attach_periodic_callback(self, callback, callback_time)
37
38         self._periodic_callback = ioloop.PeriodicCallback(callback, callback_time, self._ioloop)
---> 39         self._periodic_callback.start()
40
41     def dettach_periodic_callback(self):
~\Anaconda3\envs\Cookbook\lib\site-packages\tornado\ioloop.py in start(self)
885         self._running = True
886         self._next_timeout = self.io_loop.time()
--> 887         self._schedule_next()
888
889     def stop(self) -> None:
~\Anaconda3\envs\Cookbook\lib\site-packages\tornado\ioloop.py in _schedule_next(self)
913     def _schedule_next(self) -> None:
914         if self._running:
--> 915             self._update_next(self.io_loop.time())
916             self._timeout = self.io_loop.add_timeout(self._next_timeout, self._run)
917
~\Anaconda3\envs\Cookbook\lib\site-packages\tornado\ioloop.py in _update_next(self, current_time)
920         if self.jitter:
921             # apply jitter fraction
--> 922             callback_time_sec *= 1 + (self.jitter * (random.random() - 0.5))
923         if self._next_timeout <= current_time:
924             # The period should be measured from the start of one call
TypeError: unsupported operand type(s) for *: 'ZMQIOLoop' and 'float'
Experiment/Environment details

Tutorial used: AirSimE2EDeepLearning
Environment used:  landscape (all my environment are running perfectly)
Versions of artifacts used:
-- Windows 10
-- Anaconda
-- Python 3.5
-- Tornado 6.0.2

Thanks a lot in advance.

@gonzaloaguilarjimenez may I ask how did you solve this issue?

Good afternoon,
Yes, I solved it and it worked perfectly.
Thanks for the response.
Best regards.
El mar., 3 sept. 2019 14:15, Omer S<EMAIL_ADDRESS>escribió:

@gonzaloaguilarjimenez https://github.com/gonzaloaguilarjimenez may I
ask how did you solve this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AutonomousDrivingCookbook/issues/106?email_source=notifications&email_token=AIP443SNPXN5YL4HO52H3U3QHZINBA5CNFSM4HJ73FS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5X7UBQ#issuecomment-527432198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIP443QEZIJMOCJGL62PPOLQHZINBANCNFSM4HJ73FSQ
.

@gonzaloaguilarjimenez would you mind sharing how you solved it?
Thanks!

downgrading torando worked for me. conda install tornado=4.5.3
https://github.com/jupyter/notebook/issues/3407#issue-303235000
Thanks anyways

Hello,
It was a problem with the anaconda version apparently.
I just uninstalled and reinstalled Anaconda and then it worked.
I do not remember the previous version, but if necessary I can check the current one.
Best regards.

Thank you
On Tue, Sep 3, 2019 at 3:36 PM gonzaloaguilarjimenez <
<EMAIL_ADDRESS>wrote:

Hello,
It was a problem with the anaconda version apparently.
I just uninstalled and reinstalled Anaconda and then it worked.
I do not remember the previous version, but if necessary I can check the
current one.
Best regards.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AutonomousDrivingCookbook/issues/106?email_source=notifications&email_token=AGZEDZ4XJXQK4T7AI4NIC6TQHZK4FA5CNFSM4HJ73FS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5YBJVQ#issuecomment-527439062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGZEDZZ4GBJCH6DLV4CP4BDQHZK4FANCNFSM4HJ73FSQ
.

I'm getting the same error. What version of anaconda ended up working?


[WIP] Continue development and upstream

from https://github.com/ros2-dotnet/ros2_dotnet/issues/49#issuecomment-1081846150:

Though I have to be honest, depending on when this will be finished (or at least
in a somewhat usable state compatible to the other APIs in https://github.com/ros2-dotnet/ros2_dotnet/pull/90) we can use this.
On the other hand if this isn't ready when we need the features in our internal
code I may not have a choice but implement this myself in order to avoid
delaying the development of our internal stuff/products.
[...]
In the case that I implement this for our internal products I would continue
sharing the code in the open and finding a way to contribute this back or
helping integrating your/other implementations into the main branch, including
updating our internal code afterwards to be on the main branch of this project
once actions are merged (with all the qualities described in my first post in
this issue).

Now we are at the state where we need action support next.
As described above we would like to contribute to the open and avoid doing a hard fork.
This PR is a grab bag of what is comming next on our development roadmap for this library.
I avoid to do multiple PRs that depend on each other for now, those will be done one the main branch moves forward. I will be using prefixes in the commit messages how those would be grouped to seperate PRs so this should be easyer later on.
Current roadmap:

[x] Fix some warnings (so other warnings don't get lost while developing).
[x] Use dotnet code style (so I don't constantly fight my habbits and editor configuration).
[x] Add support for GuardConditions.
[ ] Add support for SynchronizationContext to make async code easier.

Prototype working, see this Gist: https://gist.github.com/hoffmann-stefan/33a075a5ea36d2304967248ada75e895
Still needs work for including in rcldotnet, mainly defining the API and how it would interact with executers and callback groups.

[ ] Add support for action service and client. #49

[x] IDL message generation.
[x] Add basic action client
[x] Add basic action service
[ ] Testing.

[ ] Maybe more later on, but above is my current work package.

cc @esteve @ooeygui @shschaefer

Hello. What is the state of this development now?
Is it something we could try?

@pabloinigoblasco
This is work in progress, though we use this internally for our products as we need the features right now.
Should be fine to checkout and test and give feedback.
Though I may do some force-pushes here as I develop this further, and there might be breaking changes as well. But better then nothing if you need the features. Maybe use a copy of this branch that you can update independently of me pushing things here.
@esteve stated some days ago that he wants to look at my other PRs (that this is based on) and likely merge them to main: https://github.com/ros2-dotnet/ros2_dotnet/pull/90#issuecomment-1245449812

Closing this PR as all parts where now extracted into seperate PRs and only one PR is missing to be merged. So this PR dosn't provide any more use (for now it was the PR with all not merged changes integrated), but as only one is left to merge #108 can be used instead.
This is the list of all PRs that came out of this:

https://github.com/ros2-dotnet/ros2_dotnet/pull/99
https://github.com/ros2-dotnet/ros2_dotnet/pull/100
https://github.com/ros2-dotnet/ros2_dotnet/pull/103
https://github.com/ros2-dotnet/ros2_dotnet/pull/106
https://github.com/ros2-dotnet/ros2_dotnet/pull/107
https://github.com/ros2-dotnet/ros2_dotnet/pull/108


/en-US/docs/Learn/Server-side/Express_Nodejs/Displaying_data/Book_detail_page

Request type

[x] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[ ] Correction or update

Details

-// Display detail page for a specific book.
exports.book_detail = function(req, res, next) {
needs to be modified to
BookInstance.book_detail = function(req, res, next) {
since bookController.js already has a module.exports = BookInstance; right at the end of the file.

I think the original file has a exports but I had modified the same while trying to learn. This is not an issue.


Automated build for Docker

Automated build for architecture amd64 and arm

Is it still relevant after #7 @sahilph ?

@mappuji dont think so ...


Fix verify target

Problem: GNU Makefiles do not guarantee ordering when executing prerequisites.
The existing verify command relies on a series of commands being executed in
order.
Solution: Update the verify command to run in a predictable series of steps.

/lgtm

/retest

/lgtm


Dragging and resizing is not working on IE11

First thanks for the great library !
Currently dragging and resizing is not working in M$ IE11 (running on a Windows 7 VM). You can easily reproduce by trying to run the showcase demo in IE11 - https://strml.github.io/react-grid-layout/examples/0-showcase.html .
The problem seems to rely on react-draggable component and the way it detects if the device is a touch one. We found that by modifying draggable.js file (/node_modules/react-grid-layout/node_modules/react-draggable/lib/draggable.js) so that isTouchDevice is always false solve the problem.
So instead of having:
// @credits: http://stackoverflow.com/questions/4817029/whats-the-best-way-to-detect-a-touch-screen-device-using-javascript/4819886#4819886
/* Conditional to fix node server side rendering of component */
if (typeof window === 'undefined') {
    // Do Node Stuff
    var isTouchDevice = false;
} else {
    // Do Browser Stuff
    var isTouchDevice = 'ontouchstart' in window || // works on most browsers
      'onmsgesturechange' in window; // works on ie10 on ms surface
}

we do
var isTouchDevice = false;

the problem is fixed.
This seems to be a problem with touch detection in IE11 and probably must be fixed in react-draggable but just want to make sure people are aware of the problem and temporary solution. I will try to investigate the best solution and open an issue for react-draggable.

I wonder if this can be solved with React.initializeTouchEvents and not worry about checking for this sort of stuff.

That is a good point. Could you forward this on as a react-draggable issue?

@STRML do you know if the react-draggable issue was ever submitted?  I saw you submitted https://github.com/mzabriskie/react-draggable/pull/33 but I wasn't sure if that was supposed to fix the ie11 issue or something else.

This still seems to be a problem..?

Awesome! will check it out later today. Very appreciated.

Having some issues with the upgrade due to other changes in react-draggable. Working on it.

Hi @STRML, at the risk of being deeply annoying, I was wondering if you have a feel for how difficult it will be to solve the IE11 issue? RGL is really good - much better than any of the other Packery style offerings (including Packery itself).

@jgwconsulting I've definitely dropped the ball on this - work is about 80% done but I have to work out some compatibility bugs. My day job has taken up all of my time lately.
I want to use RGL in production (that's what I built this for) so the next release (0.11) is a priority. Hoping to bang it out within the next week.

I'm amazed you have time to create this as well as holding down a day job, sleeping and stuff like that :) Great news that you're nearly there. I'll swap out Packery for RGL in a heartbeat in a dashboard app I'm working on so you have my sincere gratitude!

Thanks - yeah, issue is that I've been between traveling and presentations as well - so life has been a whirlwind the last few months. My day job is bitmex.com so it's eventually going to make it into that app. I've definitely been slacking on this and I want it to hit production so it'll move forward shortly.

Yes, I saw your screenshot of Bitmex - that's a nice looking dashboard. It
must be an exciting area to work in too.
I work for part of Avid (they do video, audio, broadcast related stuff),
currently developing a dashboard to monitor all our various services and
Rabbit MQ based workflow. At the moment I'm using something called Golden
Layout for panels and Packery for widget layout within the panels (I do
write some of my own code, honestly!) but RGL is streets ahead.
Anyway, don't kill yourself getting it fixed!
On 27 Aug 2015 23:04, "Samuel Reed"<EMAIL_ADDRESS>wrote:

Thanks - yeah, issue is that I've been between traveling and presentations
as well - so life has been a whirlwind the last few months. My day job is
bitmex.com https://www.bitmex.com so it's eventually going to make it
into that app. I've definitely been slacking on this and I want it to hit
production so it'll move forward shortly.
—
Reply to this email directly or view it on GitHub
https://github.com/STRML/react-grid-layout/issues/29#issuecomment-135567959
.

@STRML @alanrubin I'd like to update you that the Modernizr test for detecting touchevents is updated to be this:
define(['Modernizr', 'prefixes', 'testStyles'], function(Modernizr, prefixes, testStyles) {
  // Chrome (desktop) used to lie about its support on this, but that has since been rectified: http://crbug.com/36415
  Modernizr.addTest('touchevents', function() {
    var bool;
    if (('ontouchstart' in window) || window.DocumentTouch && document instanceof DocumentTouch) {
      bool = true;
    } else {
      var query = ['@media (', prefixes.join('touch-enabled),('), 'heartz', ')', '{#modernizr{top:9px;position:absolute}}'].join('');
      testStyles(query, function(node) {
        bool = node.offsetTop === 9;
      });
    }
    return bool;
  });
});

Any updates on this? Tried building 0.9.2, but still no go in IE11 it seems.

@STRML d'you have a branch or work in progress fix for this that someone else could pick up and complete? You mentioned that it's 80% done, can we help with the extra 20% and get this working in IE?

This is fixed in 0.10.

awesome!


Heroku demo currently doesn't show the uploaded files correctly

It is just a minor thing since everything is working at my end. But the demo hosted on heroku doesn't show the uploaded files correctly.
I guess they are not uploaded anymore since they might get wiped if you redeloy the instance on heroku but the database still shows the upload entries.
https://meteor-files.herokuapp.com/kB6cioBNDCLsWepqs:

Hi @Aur0r
This is caused by "ephemeral filesystem", which is used by Heroku. Read SO thread and Heroku docs.
Basically it  means - Heroku has FS, but you can store files only during current session.
We are working on it. Further versions will store Files on Google Drive, examples will be published in docs section.
We are really missing Meteor's free hosting.

Hi @Aur0r thank you for contribution.
This issue is solved in v1.4.3
Read more about third-party storage


pull request: animated weather icons

and here we are again. animated weather icons in 8x8 px.
sadly i was not able to draw a good raspberry or a pimoroni pirate yet.
need some time to test some things but i don't have the old unicorn-hat set up.
i hope the code runs like on unicorn-hat-hd... but it should, i guess ;)
kind regards again from berlin
stephan

Is there any problem with the PR? Wondering because it is not merged yet.
Just tell me if I have to change something.
Kind regards from Berlin

No problem (at least not that I'm aware of!). I just haven't had a chance to test and merge it yet.

Merged, thank you! I moved it into the hat folder for examples, since it wont work on the pHAT, and also tidied up the README slightly. Otherwise, great effort squeezing them all into 8x8!

Hey Philip,
great... I just thought there might be a problem. thx for cleaning it up so
that it fits into the main project.
next week i will have some free days and i will make them even more perfect.
i also build a complete weather station with unicorn-hat, scroll-hat and
blinkt on a black-hat. nearly no soldering required.
might the be interesting too as an example? if yes i would put some more
effort in it to make it work for everyone.
check my repos, it is called UnicornWeather (
https://github.com/LoveBootCaptain/UnicornWeather).
it is a little messy at the moment, but hey... it works.
kind regards from berlin and thx for the merge
stephan
2017-07-18 16:24 GMT+02:00 Philip Howard<EMAIL_ADDRESS>
Merged, thank you! I moved it into the hat folder for examples, since it
wont work on the pHAT, and also tidied up the README slightly. Otherwise,
great effort squeezing them all into 8x8!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pimoroni/unicorn-hat/pull/100#issuecomment-316080284,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAt_mn-Yn95Ua-DtQILUu2K9PWZY6KURks5sPMATgaJpZM4OOORC
.


time elapsed on status bar not showing on version 1.6.0

Azure Data Studio Version: 1.6.0

Steps to Reproduce:
Run long query.
Status bar no longer shows time elapsed.

this was added here
Time elapsed status item #3006
I am sure this was working before the latest update to 1.6.0

@hedgehogface - I'm not able to repro this on either ADS 1.6.0 or the Insider builds. I'm going to close this now because of that - but if you can you provide the query you're running and copy the version info from Help -> About I'll see if there's something else going on.
Have you also tried uninstalling -> reinstalling? It's possible something wasn't updated correctly with the latest patch.


Document notifier tradeoffs

Capturing insights from this ElixirForum conversation and from an Oban support email.

Thanks for this @nathanl. I removed the differentiation from the list of notifiers because the detail is in each of the modules, but otherwise left the additions intact.


Added InternalEventFrom

This PR implements what has been suggested by @tom-sherman here and what I've initially prepared in the comment here.
This is still the subject for bike-shedding etc. I'm opening this as a draft to open a discussion about this. At the very least I'd like to add type tests for this before landing this.

We might still need this - but let's redo this PR when needed.


Move CMS fields config into beforeUpdateCMSFields to make changes eas…

Move CMS fields config into beforeUpdateCMSFields. Then we can make changes easily in extensions.
Eg: remove the Content field in extension.

I've restarted the build to see if #15 fixes this :)

Of course not, need to rebase first, duh.
This is safe, and if not I'll fix it.


Optional color is not rendered for text inside a paragraph tag

The HTML for the license renders optional text in blue color.  This is currently done by generating a div with a class name of optional-license-text.  The stylesheet specifies a blue color for this class.  Paragraphs included within this div use the default paragraph color rather blue.
I think this is a straightforward fix for the stylesheet (e.g. add paragraph and any other formatting elements).

@swinslow - If you could take a look at the stylesheet and provide any pointers.

Looking, for example, at the Condor-1.1 license, the bottom part ("For more information") is <optional>.
It should appear in blue, BUT... it actually contains <p> elements and the .page p color overrides the color of optional.
Why is the .page p needed, since we already have the .page one?

Thanks @zvr for the analysis!

Why is the .page p needed, since we already have the .page one?

Not sure - @jlovejoy do you know why we have these style edits?
I hacked the Condor-1.1 html on the website removing the .page p.  This fixed the issue.
I can remove this from the template and fix this permanently for the next revision of the license list.
A couple of questions:

Should we remove the other .page xx items where the color is the same as .page?
Should we move the inline style from the template to the .css file?

Based on a discussion with @swinslow and @jlovejoy , I'll try removing the .page p and .page th from the style embedded in the template.
We'll review on preview before committing the changes.

resolved with PR #58


Do not open SL/TP orders if the main buy or sell did not go through

Duplicate bug.
Fixed in https://github.com/Tim55667757/TKSBrokerAPI/issues/66


Option to use PrecomputedTextCompat

Android P introduced support for PrecomputedText which has been backported to provide a compat version.
This article explains its benefits. Primarily performance gain
Would absolutely love it if this can be incorporated since its such a text heavy library

same concern

I am open for pull requests to integrate this.


Add blog post from Hendrik & Co on remote development for Spyder 6

@hlouzada and @ccordoba12 will want to review the content first

Hendrik first person suggestions applied per @hlouzada 's permission ✔

I replaced the screenshots as requested and also optimized all of them to make them up to several times smaller by reducing unnecessary color depth

Make the requested and agreed final adjustments. Thanks @ccordoba12 (and @hlouzada , of course) for your feedback!


Replace IntelliJProvider.Default usages with values from config

Closes https://github.com/VirtusLab/ide-probe/issues/253

removed default values from scala code, if these values could be read from reference.conf
added one new optional key to the config: probe.intellij.version.format - so that core/driver/sources/src/main/scala/org/virtuslab/ideprobe/dependencies/IntelliJResolver.scala would be able to resolve the pattern to a .zip or .dmg file - depending on parsed configuration
removed core/driver/sources/src/main/scala/org/virtuslab/ideprobe/dependencies/IntelliJDmgResolver.scala file - as now users can use .dmg distributions by using mentioned probe.intellij.version.format config (no need to keep duplicated logic - let's try to make users use .conf file instead of direct calls to parts of our scala code where possible)
removed most of logic from core/driver/sources/src/main/scala/org/virtuslab/ideprobe/dependencies/IntelliJZipResolver.scala along with the file and moved the necessary def fromConfig(config: DependenciesConfig.IntelliJ): Seq[DependencyResolver[IntelliJVersion]] to the IntelliJResolver companion object.
changed default probe.driver.launch.command from empty Array ( [] ) to a one-element array: ["idea"] - which contains the basic command that is used anyway (changed to idea.sh in our scala code if needed). Such change makes it easier to understand for users, that under this config they can provide their own command that starts the process.
added fromReferenceConf method to object Config - to decrease boilerplate and keep it possible for users to use the "official" / "default" keywords in the probe.resolvers.intellij.repositories config
removed some replacements from IntelliJPatternResolver - the ones which were always resolved to the same value
updated unit tests accordingly

If tests will pass, I will undraft it :)

Let me keep this PR a draft until I will be sure about the https://github.com/VirtusLab/git-machete-intellij-plugin/blob/master/src/uiTest/resources/ideprobe.conf#L43 usage.

removed default values from scala code, if these values could be read from reference.conf

The point of this task IMo was to make IntelliJProvicer.Default initialize its value from the config, not to remove them at all.
Probe can be used both from config and from code and both should be convenient.

added one new optional key to the config: probe.intellij.version.format - so that core/driver/sources/src/main/scala/org/virtuslab/ideprobe/dependencies/IntelliJResolver.scala would be able to resolve the pattern to a .zip or .dmg file - depending on parsed configuration

To be closer to resolvers/patterns in jvm world, this should be named ext or extension.

removed core/driver/sources/src/main/scala/org/virtuslab/ideprobe/dependencies/IntelliJDmgResolver.scala file - as now users can use .dmg distributions by using mentioned probe.intellij.version.format config (no need to keep duplicated logic - let's try to make users use .conf file instead of direct calls to parts of our scala code where possible)

Not sure why. Let's allow users to choose if they prefer to use hocon or scala. I have the code that relies on that. I need to resolve dmg files in one place and zip files in another place, at the same time I am adding my own resolvers. Then I use resolvers api to fetch IntelliJ. Please don't drop this api.
override protected val dmgResolvers =
      Seq(OfficialIntelliJDmgResolver, OfficialNightlyIntelliJDmgResolver) ++
        localIntelliJRepository.map(new IntelliJDmgResolver(_))

removed some replacements from IntelliJPatternResolver - the ones which were always resolved to the same value

They are now resolved to the same value because it is IntelliJPatternResolver, but we could add support for android studio or pycharm and these patterns would still be useful.

Please do not drop scala code usecase, do not drop val Default from components (just build them form config) and default args for IdeProbeFixture.