text:
Improvements for Ecto

I was trying to migrate from bigint ids to TypeID
I came across a few problems because I need to have TypeID working during interim steps.

You can’t use TypeID as a standard, non primary-key field (this would fail to pick up the prefix)

schema "table" do
  field :uuid, TypeID, prefix: "user", type: :binary_id
end

You can’t set the foreign key type aside from using @foreign_key_type TypeID

belongs_to :model, Model, type: TypeID

This pull request addresses both usages
I didn’t see any Ecto tests, so I haven’t provided tests.

hi! thanks for taking the time to contribute. i'll need a moment to review this more thoroughly but i did have some immediate feedback for you:

2. You can’t set the foreign key type aside from using @foreign_key_type TypeID

you can do this using define_field: false on the belongs_to and defining the foreign key field manually. See https://github.com/sloanelybutsurely/typeid-elixir/issues/20#issuecomment-1635829743 for a more complete example.

authors: andrewtimberlake sloanelybutsurely

repo: sloanelybutsurely/typeid-elixir


text:
Add other properties to publish attestation

in the slides
in the attestation description
in the future work for implementation

Done.

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
[e2e]: generic workflow_dispatch branch1 default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/3258221576
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.branch1.default.slsa3.yml
Trigger: workflow_dispatch
Branch: branch1
Date: Sun Oct 16 04:36:08 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/branch1
Run: https://github.com/slsa-framework/example-package/actions/runs/3258221576
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.branch1.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.branch1.default.slsa3.yml
Trigger: workflow_dispatch
Branch: branch1
Date: Mon Oct 17 01:06:22 UTC 2022
Tests are passing now. Closing this issue.

repo: slsa-framework/slsa-github-generator


text:
Too sharp

This runs like if the super-responsive controls cheat were on
Needs lots of work
Im surprised that you alone are re-rewriting mario 64
wow

Thank you for checking it out and the feedback!
Ah, I think you are correct, I think I did the super responsive controls as a shortcut, to get movement working then forgot to go back to that.  I'll leave this issue open and close it after I fix that.
and thanks for the support! It's been a ton of work, but really satisfying.

You’re welcome, and i forgot to say this, but the game is actually shaping up and is starting to be a game, and now that i heard that this has intentions of online multiplayer, im even MORE excited about this project
Thank YOU.

This has been fixed. Let me know if the controls feel more like they are supposed to.

Yes they do! Thanks for fixing this. The game ALREADY feels complete. All thats left is more maps, doors, enemies, oh and also, the ground pound is, oh, its fixed too! Seems like the moveset is complete! Well imma close the issue now, goodbye

license: WTFPL


text:
Fix code scanning alert - Use of a broken or risky cryptographic algorithm

Tracking issue for:

[ ] https://github.com/smadi0x86/MalwareHolmes/security/code-scanning/4

This is not used for sensitive information, just common file hash algorithm used to identify unique files.

license: MIT


text:
Bug with code completion

Refact plugin version: 1.2.7-eap-c73abd0c
When i`m coding, it recommends autocompletion:

But when i click TAB button on keyboard, it writes more code, than he recommended before:

I don't know, it's bug of Refact or Plugin for Intellij.
IntelliJ IDEA 2023.2.2 (Ultimate Edition)
Build #IU-232.9921.47, built on September 13, 2023
Runtime version: 17.0.8+7-b1000.22 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 8192M
Cores: 16
Registry:
ide.experimental.ui=true
Kotlin: 232-1.9.0-IJ9921.47

Thanks for report! Strange...first screenshot is connected to request and render delay. ex. You wrote but request was long and you got this completion. Second is similar to first, but 2 requests mixed. These are bugs. Fixes will be in the next release.

Hi again! Check pls plugin "full line code completion"

It could be not our completion.

Up to this point, it was completely disabled (and even when it was enabled, I could not use it, since it apparently does not work with PHP).
Here IDEA probably has a limit on the length of the line (which is grayed out), which is why this “Bug” occurs.

We will release today-tomorrow new version(1.2.13). Try this one. I reworked completion a little bit, so hope it will fix this problem

Maybe everything is ok (i dont see this bug at this moment)

authors: pixkk reymondzzzz

repo: smallcloudai/refact-intellij


text:
Rework Kubernetes Service Discovery flaky tests

KubernetesServiceDiscoveryTest - fails most of the time on CI
KubernetesServiceDiscoveryCDITest - - fails most of the time on CI

Stack traces
KubernetesServiceDiscoveryTest
INFO: MockWebServer[54359] received request: POST /api/v1/namespaces/test/pods HTTP/1.1 and responded: HTTP/1.1 201 OK
[OkHttp https://localhost:47135/...] INFO io.fabric8.kubernetes.client.dsl.internal.AbstractWatchManager - Unknown Watch error received 2 times without progress, will reconnect if possible
java.util.concurrent.CompletionException: java.net.ConnectException: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:47135
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:347)
	at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1141)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
	at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
	at io.fabric8.kubernetes.client.okhttp.OkHttpWebSocketImpl$1.onFailure(OkHttpWebSocketImpl.java:90)
	at okhttp3.internal.ws.RealWebSocket.failWebSocket(RealWebSocket.java:571)
	at okhttp3.internal.ws.RealWebSocket$2.onFailure(RealWebSocket.java:221)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:211)
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.net.ConnectException: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:47135
	at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:249)
	at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:167)
	at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:258)
	at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135)
	at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114)
	at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:127)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:257)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:201)
	... 4 more
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:547)
	at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
	at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
	at java.base/java.net.Socket.connect(Socket.java:633)
	at okhttp3.internal.platform.Platform.connectSocket(Platform.java:129)
	at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:247)
	... 21 more
Sep 28, 2023 7:44:07 AM okhttp3.mockwebserver.MockWebServer$Http2SocketHandler onStream
INFO: MockWebServer[54359] received request: GET /api/v1/namespaces/test/endpoints?fieldSelector=metadata.name%3Dsvc HTTP/1.1 and responded: HTTP/1.1 200 OK protocol is h2
Sep 28, 2023 7:44:07 AM okhttp3.mockwebserver.MockWebServer$Http2SocketHandler onStream
INFO: MockWebServer[54359] received request: GET /api/v1/namespaces/test/pods/svc-109696231 HTTP/1.1 and responded: HTTP/1.1 200 OK protocol is h2
Sep 28, 2023 7:44:07 AM okhttp3.mockwebserver.MockWebServer$Http2SocketHandler onStream
INFO: MockWebServer[54359] received request: GET /api/v1/namespaces/test/pods/svc-109696232 HTTP/1.1 and responded: HTTP/1.1 200 OK protocol is h2
[OkHttp https://localhost:48653/...] INFO io.fabric8.kubernetes.client.dsl.internal.AbstractWatchManager - Unknown Watch error received 2 times without progress, will reconnect if possible
java.util.concurrent.CompletionException: java.net.ConnectException: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:48653
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:347)
	at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1141)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
	at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
	at io.fabric8.kubernetes.client.okhttp.OkHttpWebSocketImpl$1.onFailure(OkHttpWebSocketImpl.java:90)
	at okhttp3.internal.ws.RealWebSocket.failWebSocket(RealWebSocket.java:571)
	at okhttp3.internal.ws.RealWebSocket$2.onFailure(RealWebSocket.java:221)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:211)
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.net.ConnectException: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:48653
	at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:249)
	at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:167)
	at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:258)
	at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135)
	at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114)
	at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:127)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:257)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:201)
	... 4 more
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:547)
	at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
	at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
	at java.base/java.net.Socket.connect(Socket.java:633)
	at okhttp3.internal.platform.Platform.connectSocket(Platform.java:129)
	at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:247)
	... 21 more

KubernetesServiceDiscoveryCDITest
INFO: MockWebServer[44591] received request: POST /api/v1/namespaces/test/pods HTTP/1.1 and responded: HTTP/1.1 201 OK
[OkHttp https://localhost:37433/...] INFO io.fabric8.kubernetes.client.dsl.internal.AbstractWatchManager - Unknown Watch error received 2 times without progress, will reconnect if possible
java.util.concurrent.CompletionException: java.net.ConnectException: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:37433
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:347)
	at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1141)
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
	at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:2162)
	at io.fabric8.kubernetes.client.okhttp.OkHttpWebSocketImpl$1.onFailure(OkHttpWebSocketImpl.java:90)
	at okhttp3.internal.ws.RealWebSocket.failWebSocket(RealWebSocket.java:571)
	at okhttp3.internal.ws.RealWebSocket$2.onFailure(RealWebSocket.java:221)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:211)
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.net.ConnectException: Failed to connect to localhost/[0:0:0:0:0:0:0:1]:37433
	at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:249)
	at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:167)
	at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:258)
	at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:135)
	at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:114)
	at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:127)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:257)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:201)
	... 4 more
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.base/sun.nio.ch.NioSocketImpl.timedFinishConnect(NioSocketImpl.java:547)
	at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:602)
	at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
	at java.base/java.net.Socket.connect(Socket.java:633)
	at okhttp3.internal.platform.Platform.connectSocket(Platform.java:129)
	at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:247)
	... 21 more

Please reopen and assign to me, I'll try to take a look in my system.

Here a job failing https://github.com/smallrye/smallrye-stork/actions/runs/6624920840/job/17994852183

authors: aureamunoz cescoffier manusa

repo: smallrye/smallrye-stork


text:
Manual input and pressing TAB doesn't trigger changeDate

If you enter the date manually (type it) and press tab or escape, then the value of the field will be updated but this won't trigger changeDate,
quick fix would be to set changedDate by default to true

This fixed it manual inputs for me https://github.com/smalot/bootstrap-datetimepicker/issues/203

repo: smalot/bootstrap-datetimepicker

license_source: bigquery


text:
Dynamic Title "Come back"

The dynamic title is kinda disturbing and doesn't look good for a portfolio website. I meant that constant switching of "Come back" and "John Doe | Home"

I feel we can remove this as it was looking a bit unprofessional (personally) and only keep "John Doe | Home".
What say, admins?

Touche!
@varunwho You can remove it from all the pages. Assigned for 3 days

authors: smaranjitghose varunwho


text:
Add drawing options on editor page

While writing on the page suppose there is a need to draw a line or any shape somewhere then there should be an option to do so.
As a participant in GSSoC'21 I would like to contribute to this project.

While writing on the page suppose there is a need to draw a line or any shape somewhere then there should be an option to do so.
As a participant in GSSoC'21 I would like to contribute to this project.

Assigned for 4 days.

I'm the Participant of GSSOC'21. Please assign me this issue.I would love to work on this.

@rk05-lenavo you have 3 days for the initial PR

@smaranjitghose I made the drawing option. Please view it. If it seems okay to you  please issue me the PR.


text:
🛑 Dashboard is down

In d94ab3e, Dashboard (https://app.smart-moov.io) was down:

HTTP code: 502
Response time: 1114 ms

Resolved: Dashboard is back up in 6aa0ebd.

repo: smart-moov/upptime


text:
🛑 Dashboard is down

In 7d2736a, Dashboard (https://app.smart-moov.io) was down:

HTTP code: 502
Response time: 949 ms

Resolved: Dashboard is back up in b9ddd75 after 9 minutes.


text:
feat: comparison tool as icon on desktop

References https://smg-au.atlassian.net/browse/DM-3402
Motivation and context
Adds the comparison tool icon to the header as per design here: https://www.figma.com/design/JzvUE9wphKBMTAi0nYlLdY/AS24---Comparison-Tool?node-id=1475-119078&t=NoZMr8IcToL01MI6-0
This is only the first step. I'll add the icon on mobile separately as it requires a bigger restructoring of the header
You can see it in action here: https://talamcol-comparison-header-listings-web.branch.autoscout24.dev/

QA tested by Migmar ✅

source: gharchive/pull-request

repo: smg-automotive/components-pkg


text:
Initial release

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/67782
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 64d3f2783955e689de4c4715ffc45d358d841141
git push origin v0.1.0

authors: JuliaRegistrator smillerc


text:
Exception in streaming call not propagated to caller's scope

Describe the bug
An exception within a streaming sdk call is not being propagated to the caller's scope.
Regression Issue

[ ] Select this option if this issue appears to be a regression.

Expected behavior
A streaming sdk call made within a given scope should propagate its exceptions back to that scope. An exception handler provided at launch should be called if the exception is not otherwise handled.
Current behavior
Exceptions that occur within the stream that are not handled within the stream are not propagated to the calling scope's exception handler. Instead the app's top-level exception handler is receiving the following as an unhandled exception:
    FATAL EXCEPTION: DefaultDispatcher-worker-5
    Process: myprocess, PID: 14065
    okhttp3.internal.http2.StreamResetException: stream was reset: CANCEL
    at okhttp3.internal.http2.Http2Stream.checkOutNotClosed$okhttp(Http2Stream.kt:646)
    at okhttp3.internal.http2.Http2Stream$FramingSink.emitFrame(Http2Stream.kt:557)
    at okhttp3.internal.http2.Http2Stream$FramingSink.write(Http2Stream.kt:532)
    at okio.ForwardingSink.write(ForwardingSink.kt:29)
    at okhttp3.internal.connection.Exchange$RequestBodySink.write(Exchange.kt:223)
    at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.kt:256)
    at okio.RealBufferedSink.write(RealBufferedSink.kt:147)
    at aws.smithy.kotlin.runtime.http.engine.okhttp.InstrumentedSink.write(MetricsInterceptor.kt:51)
    at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.kt:256)
    at okio.RealBufferedSink.write(RealBufferedSink.kt:147)
    at okio.RealBufferedSink.emit(RealBufferedSink.kt:262)
    at aws.smithy.kotlin.runtime.io.AbstractBufferedSinkAdapter.emit(BufferedSinkAdapter.kt:90)
    at aws.smithy.kotlin.runtime.io.SdkByteReadChannelKt$readAll$2.invokeSuspend(SdkByteReadChannel.kt:114)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101)
    at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113)
    at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
    at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720)
    at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:707)
    Suppressed: okhttp3.internal.http2.StreamResetException: stream was reset: CANCEL
    at okhttp3.internal.http2.Http2Stream.checkOutNotClosed$okhttp(Http2Stream.kt:646)
    at okhttp3.internal.http2.Http2Stream$FramingSink.emitFrame(Http2Stream.kt:557)
    at okhttp3.internal.http2.Http2Stream$FramingSink.write(Http2Stream.kt:532)
    at okio.ForwardingSink.write(ForwardingSink.kt:29)
    at okhttp3.internal.connection.Exchange$RequestBodySink.write(Exchange.kt:223)
    at okio.RealBufferedSink.emitCompleteSegments(RealBufferedSink.kt:256)
    at okio.RealBufferedSink.write(RealBufferedSink.kt:147)
    at aws.smithy.kotlin.runtime.http.engine.okhttp.InstrumentedSink.write(MetricsInterceptor.kt:51)
    at okio.RealBufferedSink.close(RealBufferedSink.kt:280)
    at kotlin.io.CloseableKt.closeFinally(Closeable.kt:59)
    at aws.smithy.kotlin.runtime.http.engine.okhttp.StreamingRequestBody$doWriteTo$1.invokeSuspend(StreamingRequestBody.kt:64)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
    at kotlinx.coroutines.UndispatchedCoroutine.afterResume(CoroutineContext.kt:266)
    at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:100)
    at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46)
    ... 7 more
    Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [TelemetryContext(aws.smithy.kotlin.runtime.telemetry.DefaultTelemetryProvider@9fa78e0), LoggingContextElement({rpc=Transcribe Streaming.StartStreamTranscription, sdkInvocationId=563166c0-e5e1-4c22-bbb4-96f5faa14d9e}), aws.smithy.kotlin.runtime.telemetry.context.TelemetryContextElement@db9e799, CoroutineName(call-context:send-request-body), StandaloneCoroutine{Cancelling}@60e6a5e, Dispatchers.IO]

Steps to Reproduce
The streaming call is being started within a coroutine as follows:
        val myDispatcher = Executors
            .newSingleThreadExecutor(VoiceInteractionThreadFactory)
            .asCoroutineDispatcher()

        // supervisor is SupervisorJob()
        val myScope = CoroutineScope(myDispatcher + supervisor)

        awsTranscribeJob =
                myScope.launch(RecognitionServiceExceptionHandler) {
                    withContext(myDispatcher) {
                        try {
                            awsTranscribe?.start()
                        } catch (e: AwsTranscribeException) {
                            Timber.tag(RECOGNITION_LOGGING_TAG).e(e, "Error processing transcript from AWS Transcribe")
                            launch(Dispatchers.Main) {
                                givenCallback?.error(SpeechRecognizer.ERROR_SERVER)
                            }
                        } catch (e: IOException) {
                            Timber.tag(RECOGNITION_LOGGING_TAG).e(e, "IO error getting transcript")
                            launch(Dispatchers.Main) {
                                givenCallback?.error(SpeechRecognizer.ERROR_NETWORK)
                            }
                    }
                }
    }

suspend fun start(): String {
        enableHttp2FrameLogging()
        fullMessage = StringBuilder()

        client =
            TranscribeStreamingClient {
                logMode = LogMode.LogRequest + LogMode.LogResponse
                credentialsProvider = myCredentialsProvider
                region = "us-east-1"
                httpClient =
                    OkHttp4Engine {
                        enableHttp2FrameLogging()
                    }

                interceptors = mutableListOf(AwsLoggingInterceptor())
            }

        val req =
            StartStreamTranscriptionRequest {
                audioStream = audioStreamFlow
                mediaSampleRateHertz = 16000
                mediaEncoding = MediaEncoding.Flac
                languageCode = LanguageCode.DeDe
                languageModelName = "my-language-model-de-DE-v1.2"
                enablePartialResultsStabilization = false
                // partialResultsStability = PartialResultsStability.Low
            }

            client?.startStreamTranscription(req) { resp ->
                resp.transcriptResultStream
                    ?.collect { event ->
                        logger.debug("event received on transcriptResultStream")
                        when (event) {
                            is TranscriptResultStream.TranscriptEvent -> {
                                logger.debug("AwsTranscribe TranscriptEvent received")
                                event.value.transcript?.results?.forEach { result ->
                                    val transcript = result.alternatives?.firstOrNull()?.transcript
                                    if (result.isPartial) {
                                        speechRecognitionResultsListener
                                            ?.onPartialResult(
                                                transcript
                                                    ?: "",
                                            )
                                    } else {
                                        transcript?.let {
                                            fullMessage.append(it)
                                            speechRecognitionResultsListener?.onResults(fullMessage.toString())
                                            stop()
                                        }
                                    }
                                }
                            }
                            else -> error("unknown event $event")
                        }
                    }
            }
        return fullMessage.toString()
    }

Possible Solution
In aws.smithy.kotlin.runtime.http.engine.okhttp.StreamingRequestBody#doWriteTo
Perhaps the GlobalScope.launch is the issue?
    private fun doWriteTo(sink: BufferedSink) {
        val context = callContext + callContext.derivedName("send-request-body")
        if (isDuplex()) {
            // launch coroutine that writes to sink in the background
            GlobalScope.launch(context + Dispatchers.IO) {
                sink.use { transferBody(it) }
            }
        } else {
            // remove the current dispatcher (if it exists) and use the internal
            // runBlocking dispatcher that blocks the *current* thread
            val blockingContext = context.minusKey(CoroutineDispatcher)

            // Non-duplex (aka "normal") requests MUST write all of their request body
            // before this function returns. Requests are given a background thread to
            // do this work in, and it is safe and expected to block.
            // see: https://square.github.io/okhttp/4.x/okhttp/okhttp3/-request-body/is-duplex/
            runBlocking(blockingContext) {
                transferBody(sink)
            }
        }
    }

Context
No response
Smithy-Kotlin version
1.3.17
Platform (JVM/JS/Native)
JVM
Operating system and version
Android 13

I tried adding a .catch block to the stream processing:
                resp.transcriptResultStream
                    ?.catch { e ->
                        if (e !is Exception) throw e
                        logger.error("error in transcriptResultStream: ${e.message}")
                        speechRecognitionResultsListener?.onError(e)
                        stop()
                    }
                    ?.collect { event ->

but the result was that while this catch block was called, for instance when no audio was received by transcribe for 15 seconds, the StreamResetException was still unhandled.

I've been able to reproduce this and I'm working on a fix and additional testing within the SDK. I'll post an update here when I have a PR.

Circling back to this, I do believe that our use of GlobalScope is not optimal and should be changed. That being said, I do not believe that using a better scope will affect the issue of exceptions disappearing from child jobs.
I think the problem lies in using launch without any additional constructs which would wait on the result or propagate the exception. Without those, exceptions produced by child jobs won't block the current thread, they'll merely happen in the background and be handled by the default coroutine exception handler (which prints them to the console). I suggest using coroutineScope { } or join() to propagate the exception:
awsTranscribeJob =
    myScope.launch(RecognitionServiceExceptionHandler) {
        withContext(myDispatcher) {
            try {
                awsTranscribe?.start()
            } catch (e: AwsTranscribeException) {
                Timber.tag(RECOGNITION_LOGGING_TAG).e(e, "Error processing transcript from AWS Transcribe")
                launch(Dispatchers.Main) {
                    givenCallback?.error(SpeechRecognizer.ERROR_SERVER)
                }
            } catch (e: IOException) {
                Timber.tag(RECOGNITION_LOGGING_TAG).e(e, "IO error getting transcript")
                launch(Dispatchers.Main) {
                    givenCallback?.error(SpeechRecognizer.ERROR_NETWORK)
                }
            }
        }
    }.join()

Additionally, I believe the use of SupervisorJob here means child jobs' exceptions will not cause any error to happen outside of the scope, meaning they also will disappear. Your RecognitionServiceExceptionHandler may be able to see they've occurred and log messages but recovery will be impossible.
Lastly, I'm unclear what AwsTranscribeException is in the catch clause. The Kotlin Transcribe client will throw exceptions which inherit from TranscribeStreamingException for service-related errors, including BadRequestException which occurs when an audio stream has been idle too long.
I don't know enough about your surrounding code and desired state to be certain but I believe your invocation of this API can be simplified to remove the explicit scope and supervisor job, handle the correct base exception type, and eliminate the need for the uncaught exception handler:
val myDispatcher = Executors
    .newSingleThreadExecutor(VoiceInteractionThreadFactory)
    .asCoroutineDispatcher()

awsTranscribeJob = coroutineScope {
    withContext(myDispatcher) {
        try {
            awsTranscribe?.start()
        } catch (e: TranscribeStreamingException) {
            Timber.tag(RECOGNITION_LOGGING_TAG).e(e, "Error processing transcript from AWS Transcribe")
            launch(Dispatchers.Main) {
                givenCallback?.error(SpeechRecognizer.ERROR_SERVER)
            }
        } catch (e: IOException) {
            Timber.tag(RECOGNITION_LOGGING_TAG).e(e, "IO error getting transcript")
            launch(Dispatchers.Main) {
                givenCallback?.error(SpeechRecognizer.ERROR_NETWORK)
            }
        }
    }
}

This should enable exceptions to be caught and handled appropriately, including leaving the audio stream idle for too long.
Can you review and let me know if that resolves the exception propagation problem?

Thanks for the detailed feedback!
The reason why I am not using coroutine { } or join() is I am calling my start() method and thus triggering the transcribe client.startStreamTranscription from an Android RecognitionService#onStartListening
About the exception type, indeed that was a relic of something else I had tried, but the exception being caught in my exception handler (StreamResetException) is actually an IOException anyway.

The reason why I am not using coroutine { } or join() is I am calling my start() method and thus triggering the transcribe client.startStreamTranscription from an Android RecognitionService#onStartListening

I see. I'm not familiar with RecognitionService but I'm guessing you need to return quickly in onStartListening and then wrap up the Job somewhere else (maybe onStopListening). Are you using join() anywhere else to ensure the job is completing and throwing any relevant exception?

Thanks for the hints. Indeed, I found a way of passing the exception back to my RecognitionService:  by catching the exception in the response and then passing it back to the recognition service, where I can stop() the job that started the transcribe calls:
        client?.startStreamTranscription(req) { resp ->
                resp.transcriptResultStream
                    ?.catch { e ->
                        logger.error("error in transcriptResultStream: ${e.message}")
                        if (e !is Exception) throw e
                        speechRecognitionResultsListener?.onError(e)
                        stop()
                    }
                    ?.collect { event ->
                       logger.debug("event received on transcriptResultStream")
                    ......

`````

Great, I'm glad to hear that! I'm resolving this issue as not planned for now since there's no work to do. Please re-open if you have further questions.

authors: david-katz ianbotsf

repo: smithy-lang/smithy-kotlin


text:
Add declarative endpoints traits

Description of changes:
Add declarative endpoints traits
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Also un-resolved some previous comments that weren't fully taken care of.

authors: AndrewFossAWS kstich

repo: smithy-lang/smithy


text:
Execute as a script

Script execution made simple with SML/NJ
Submitted By: Dayanandan Natarajan
Supervisor: Joe Wells
School of Mathematical and Computer Sciences
Heriot-Watt University
Objective
Primary objective of this change is to give the programmers and developers the capability of running a SML program as a script. Programmers and developers can write a SML program and run the program like a script over the command prompt.
Files modified
smlnj/base/cm/main/cm-boot.sml
smlnj/base/system/smlnj/internal/boot-env-fn.sml
smlnj/base/compiler/TopLevel/interact/interact.sig
smlnj/base/compiler/TopLevel/interact/interact.sml
Change details

interact.sig & interact.sml

A new function (useScriptFile) is added to Backend.Interact structure, which takes the file name and its content as a stream and process the stream by passing it to EvalLoop.evalStream.
a)	New function declaration is added to interact.sig,
val useStream : TextIO.instream -> unit
val useScriptFile : string * TextIO.instream -> unit (* Addded by DAYA *)
val evalStream : TextIO.instream * Environment.environment -> Environment.environment

b)	New function definition is added to interact.sml,
    fun useScriptFile (fname, stream) = (

      (EvalLoop.evalStream (fname, stream))
        handle exn => (
          EvalLoop.uncaughtExnMessage exn
          )
      )

cm-boot.sml

The following changes were made in cm-boot.sml to recognise the new command line parameter passed from script.
a)	In function args, line added to recognise the new command-line parameter ‘--script’, and a new function ‘nextargscript’ is called to initiate the process of the file.
        fun args ([], _) = ()
          | args ("-a" :: _, _) = nextarg autoload'
          | args ("-m" :: _, _) = nextarg make'
          | args (["-H"], _) = (help NONE; quit ())
          | args ("-H" :: _ :: _, mk) = (help NONE; nextarg mk)
          | args (["-S"], _) = (showcur NONE; quit ())
          | args ("-S" :: _ :: _, mk) = (showcur NONE; nextarg mk)
          | args (["-E"], _) = (show_envvars NONE; quit ())
          | args ("-E" :: _ :: _, mk) = (show_envvars NONE; nextarg mk)
          | args ("--script" :: _, _) = (nextargscript ())  (* line added by DAYA *)
          | args ("@CMbuild" :: rest, _) = mlbuild rest
          | args (["@CMredump", heapfile], _) = redump_heap heapfile
          | args (f :: rest, mk) =
          (carg (String.substring (f, 0, 2)
             handle General.Subscript => "",
             f, mk, List.null rest);
           nextarg mk)

        and nextarg mk =
        let val l = SMLofNJ.getArgs ()
        in SMLofNJ.shiftArgs (); args (l, mk)
        end

        (* nextargscript added by DAYA *)
        and nextargscript () =
        let val l = SMLofNJ.getArgs ()
        in SMLofNJ.shiftArgs (); processFileScript (hd l); quit ()
        end

b)	In function init(), the new function (useScriptFile) is added as one of the parameter passed,
fun init (bootdir, de, er, useStream, useScriptFile, useFile, errorwrap, icm) = let
c)	In function procCmdLine (), new function processFileScript is added to process the script file, function will check for whether the file passed on is a script file starting with ‘#!’ thru another new function checkSharpbang, consumes the first line thru another new function eatuntilneline and pass the remaining content of the file to function useScriptFile.
          (* DAYA change starts here *)
            fun eatuntilnewline (instream : TextIO.instream): bool = let
                val c = TextIO.input1 instream
                in
                    case TextIO.lookahead instream of
                        SOME #"\n" => true
                        | SOME c => eatuntilnewline instream
                        | NONE => false
                end

            fun checkSharpbang (instream : TextIO.instream): bool = let
                val c = TextIO.input1 instream
                in
                    case c of
                        SOME #"#" => (
                            case TextIO.lookahead instream of
                                SOME #"!" => eatuntilnewline instream
                                | SOME c => false
                                | NONE => false
                                )
                        | SOME c => false
                        | NONE => false
                end

            fun processFileScript (fname) = let
                val stream = TextIO.openIn fname
                val isscript = checkSharpbang stream
                in
                    if (isscript) = false
                    then    ( Say.say [ "!* Script file doesn't start with #!. \n" ] )
                    else    ( useScriptFile (fname, stream) )
                end
            (* DAYA change ends here *)

boot-env-fn.sml

In functor BootEnvF, cminit function declaration is amended to include the newly added function useScriptFile.
functor BootEnvF (datatype envrequest = AUTOLOAD | BARE
          val architecture: string
          val cminit : string * DynamicEnv.env * envrequest
                   * (TextIO.instream -> unit)(* useStream *)
                   * (string * TextIO.instream -> unit) (* useScriptFile *)
                   * (string -> unit) (* useFile *)
                   * ((string -> unit) -> (string -> unit))
                                      (* errorwrap *)
                   * ({ manageImport:
                      Ast.dec * EnvRef.envref -> unit,
                    managePrint:
                      Symbol.symbol * EnvRef.envref -> unit,
                    getPending : unit -> Symbol.symbol list }
                  -> unit)
                   -> (unit -> unit) option
          val cmbmake: string * bool -> unit) :> BOOTENV = struct

Writing a script
The script should start with ‘#!’ in the first line followed by the environment location, command-line parameters ‘-Ssml’ and ‘—script’, a new line and then followed by the SML code or program.
Example script named ‘sample’,
--------------beginning of the script-------------
#!/usr/bin/env -Ssml –script
;(--SML--)
val () = print "Hello World\n";
--------------end of the script---------------------
Running a script
The script ‘sample’ can be executed from Linux terminal or command prompt as a regular OS script as below provided it is given execution permission,

$ ./sample

SML/NJ Version used
Our development and testing is based on Standard ML of New Jersey (32-bit) v110.99.3 on an Intel based macOS 10.13.16.
Test Details
Test Script #1
#!/usr/bin/env -Ssml --script
;(* SML code starts here *)
val x = "Hello World x\n";
val () = print x;
val y = "Hello World y\n";
val () = print y;
val z = "Hello World z\n";
val () = print z;
Test Result #1
$ ./sample
Standard ML of New Jersey (32-bit) v110.99.3 [built: Mon Apr 10 18:03:19 2023]
val x = "Hello World x\n" : string
Hello World x
val y = "Hello World y\n" : string
Hello World y
val z = "Hello World z\n" : string
Hello World z
$
Test Script #2 (sample script with forced error)
#!/usr/bin/env -Ssml --script
;(--SML--)
val x = "Hello World x\n";
val () = print x;
val y = "Hello World y\n";
val () == print y;
val z = "Hello World z\n";
val () = print z;
Test Result #2
$ ./sample
Standard ML of New Jersey (32-bit) v110.99.3 [built: Sat Apr 15 18:38:28 2023]
val x = "Hello World x\n" : string
Hello World x
val y = "Hello World y\n" : string
./exml07:7.18-8.4 Error: syntax error: deleting  SEMICOLON VAL
uncaught exception Compile [Compile: "syntax error"]
raised at: ../compiler/Parse/main/smlfile.sml:19.24-19.46
../compiler/TopLevel/interact/evalloop.sml:45.54
../compiler/TopLevel/interact/evalloop.sml:306.20-306.23

We need a fairly detailed description of what this does and how it works, and any new interfaces/signatures, and whether the top-level  pervasive environment is changed. When an SML program is invoked as a "script", is it loaded and run in the REPL?  Is the SML program that is run as a script an SML source file or is it a stand-alone program with an associated heap-image created by exportFn?

HI Dave, The pull request is still in draft, I will be adding all the details before I submit the request.

Ok, that’s what I expected, but I thought I’d give a potentially useful “prompt” about what we would like to see as documentation of the changes.
Also keep in mind that if and when it is merged into legacy, we are likely to also want to merge into the smlnj/smlnj (“development”, but really the continuing release) repository.
Also, I have been looking into the state of the compiler+CM “architecture”, which as become rather muddled.  So I am interested in whether your work will impinge on architectural issues.  We need to clarify the relation between CM and the interactive REPL, and investigate the idea of a “batch compilation” where stand-alone programs are built without using the REPL, its top-level environment, and exportFn.
Dave

On Apr 15, 2023, at 10:50 AM, dn2007hw @.***> wrote:
HI Dave, The pull request is still in draft, I will be adding all the details before I submit the request.
—
Reply to this email directly, view it on GitHub https://github.com/smlnj/legacy/pull/276#issuecomment-1509913128, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGXNPKOAH4KOM6R2YM4TO3XBLNW3ANCNFSM6AAAAAAW7RHZI4.
You are receiving this because you commented.

David MacQueen
@.***

Execute-as-a-script.txt

Thanks for that summary. This makes it fairly clear what you are doing.  I’m not sure how your “silenceCompiler” function works.
Dave

On Apr 15, 2023, at 10:58 AM, dn2007hw @.***> wrote:
Execute-as-a-script.txt https://github.com/smlnj/legacy/files/11240286/Execute-as-a-script.txt
—
Reply to this email directly, view it on GitHub https://github.com/smlnj/legacy/pull/276#issuecomment-1509915555, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGXNPILMHHTDWE2QRRIE73XBLOUPANCNFSM6AAAAAAW7RHZI4.
You are receiving this because you commented.

David MacQueen
@.***

silenceCompiler function is not part of this patch, I have removed the reference. It's part of next patch, I will be adding the details in that.

We should think about the name of the command-line option.  We currently do not use names like --script.  I would suggest @SMLscript (using the @SML prefix is a way to avoid colliding with options that the script might want to handle).
Also, the code can be tightened up a bit and should be made more robust.  For example, it might be more direct to process the first line of the script using TextIO.StreamIO.inputLine
(* if the first line of the input stream begins with "#!", then consume the line
 * and return `true`; otherwise return `false` and do not advance the input.
 *)
fun checkSharpbang inS = let
      val inS' = TextIO.getInstream inS
      in
        case TextIO.StreamIO.inputLine inS'
         of SOME(firstLn, inS'') =>
              if String.isPrefix "#!" firstLn
                then (TextIO.setInstream(inS, inS''); true)
                else false
          | _ => false
        (* end case *)
      end

This seems like a great feature to add, but I wanted to add my 2 cents about how to handle the shebang.
I think the best way to handle the "#!" is in the lexer: if the first 2 bytes of a file are "#!", then skip until the first "\n" like a line comment.
I think it's also important to not require a command-line flag.
On Linux, shebangs are only split into (executable, argument), and because sml could be installed in many different locations it would be good practice to use /usr/bin/env.
That doesn't leave any room for script arguments.
Tools such as nix-shell or languages like Rust (via cargo) support command-line options via comments.
#! /usr/bin/env cargo
//! ```cargo
//! [dependencies]
//! serde = "1.0.215"
//! ```
use serde::ser::{Serialize};

fn main () {
  println!("Hello from Rust!");
}

This could be integrated into SML/NJ by parsing the first comment in the file, and extracting arguments if the comment is of a certain form.
It could also allow for loading CM modules if executed as a script.
#! /usr/bin/env sml
(*#script -Cmlrisc.disable-jump-chain-elim $smlnj-lib.cm $pp-lib.cm *)

(* Executing this file runs `sml  -Cmlrisc.disable-jump-chain-elim '$smlnj-lib.cm' '$pp-lib.cm' <file.sml>`

val () = print "Hello from SML/NJ!\n"

Handling the shebang in the lexer also makes it possible to write SML files that act as both libraries and scripts.
For example, it would be possible to write:
#! /usr/bin/env sml

structure MyModule : sig
  val foo : unit -> unit
end = struct
  fun internal () = "Internal"

  fun foo () = print (internal ())

  fun test () =
    if internal () = "Internal" then () else raise Fail "Test failure"
  val () = if !SMLofNJ.isScript then test () else ()
end

Running the file would execute the script, but it could also be loaded like a normal file that defines a structure.

repo: smlnj/legacy


text:
Derive more anomalies, cluster, filter, bring to experts

Make "fakes and scores" gone through Kostya, so we can derive the number of outliers in the datasets.
Merge master to clustering or vice versa.
Derive new anomalies for all the fields.
Cluster them.
Filter somehow.
Present to Maria.

obsolete, totally

repo: snad-space/zwad


text:
Always finish job in dag

Resolves issue #118.

Thank you, I have tested the branch and it has indeed solved the issue for me.

Semi-related to tests failing.  I applied the patch described above and now am failing test_singularity_conda though it passes locally and should be unaffected by other changes and was passing a few days ago on this PR.  Any ideas?

Semi-related to tests failing. I applied the patch described above and now am failing test_singularity_conda though it passes locally and should be unaffected by other changes and was passing a few days ago on this PR. Any ideas?

I think this was likely a temporal server downtime.

authors: johanneskoester skitcattCRUKMI troycomi

repo: snakemake/snakemake


text:
docs: Update faq.rst / forcerun flag

Description
A very trivial doc fix, --forcerules is really --forcerun

Thanks!

authors: johanneskoester semenko


text:
Add_KFI

If you want to create a space follow this guide
https://docs.snapshot.page/guides/create-a-space

There is a conflict in your PR, can you resolve it?

authors: gokaiorg solproc

repo: snapshot-labs/snapshot-spaces


text:
[BUG] - Profile not loading on custom domain

Briefly describe the bug.
Snapshot profile or ens/lens resolver doesn't load on custom domains
How can we reproduce the bug?

Go to any custom domain, for example https://vote.kap.gg/#/
Connect a wallet with snapshot profile/ens/lens resolver
You will see an address like below

What is the expected behaviour?
It should display snapshot profile like on snapshot.org

Can you attach screenshots?
No response
Can you provide your device specific details below?
No response

Hey there , can i work on this ?

@wa0x6e this seems like an issue with stamp, this is just a guess as I don't see an error or CORS in the console.

@wa0x6e this seems like an issue with stamp, this is just a guess as I don't see an error or CORS in the console.

Will take a look

This is not an issue with stamp but with the UI itself, I found a fix will push it soon

repo: snapshot-labs/snapshot


text:
Snapview v1.1.0

Refactored Nodes and Properties;
Added main index file;

Hello @Vooord . This MR is too big and includes too many unrelated changes. Please split it.

Hello @Vooord . This MR is too big and includes too many unrelated changes. Please split it.

Hey, @denistakeda, I extracted github-actions into separate pr-3

I copied the changes to https://github.com/snapview/sunrise-dom/tree/v1.1

authors: Vooord denistakeda marc136

repo: snapview/sunrise-dom


text:
My reply to my own post seem to not get bridged (AP => AT)

My original post: https://social.atiusamy.com/notes/9t0gi01y9sto02ws
My reply to the original post:
https://social.atiusamy.com/notes/9t0gjayd9sto02wy
My post on bsky:
https://bsky.app/profile/AmyIsCoolz.social.atiusamy.com.ap.brid.gy/post/3krwiwcvmqek2
The post does not contain my own reply to my post-

Specifically, we were ending up with two variants of our PDS URL as delivery targets, both https://atproto.brid.gy (no trailing slash) and https://atproto.brid.gy/ (trailing slash), and creating post records for each of them independently. Not good. Finally reproduced it though, and it's an easy fix.
Btw @mackuba you'll probably find this one amusing. 😁 Surprisingly unrelated to what's in users' DID docs though!

Fix for this should be deployed in ~5m. Thanks again for reporting!

authors: AtiusAmy snarfed

repo: snarfed/bridgy-fed


text:
Route Calculator

Route Calculator
Notes
Checklist

[x] url and description in index file (see below)
[x] tested
[x] PR labeled with difficulty

Example
/*
https://www.codewars.com/kata/<some numbers>

Write function that meets these requirements...
 */

tests are passing locally
running on codewars returns the following error:

TSError: ⨯ Unable to compile TypeScript
solution.ts (4,53): Type expected. (1110)
solution.ts (22,20): Expression expected. (1109)
solution.ts (22,27): ':' expected. (1005)
solution.ts (26,38): Property 'groups' does not exist on type 'RegExpExecArray'. (2339)

typescript v. 2.4
javascript v. ES6

tests are passing locally
running on codewars returns the following error:

TSError: ⨯ Unable to compile TypeScript
solution.ts (7,68): Type expected. (1110)
solution.ts (45,61): Expression expected. (1109)
solution.ts (45,62): Identifier expected. (1003)
solution.ts (45,76): Expression expected. (1109)
solution.ts (45,80): ':' expected. (1005)
solution.ts (60,65): Expression expected. (1109)
solution.ts (60,69): ':' expected. (1005)
solution.ts (60,18): Initializer provides no value for this binding element and the binding element has no default value. (2525)
solution.ts (60,26): Initializer provides no value for this binding element and the binding element has no default value. (2525)

repo: snelling-a/codewars


text:
Style versionchanged and versionadded directives

See the Changed in version 2.0 at the top of this page: http://docs.ckan.org/en/latest/maintaining/authorization.html. That's versionchanged directive:
.. versionchanged:: 2.0
   Previous versions of CKAN used a different authorization system.

but in this theme it just looks like a normal paragraph.
It would be nice to style these so that they pop out, like notes, warnings etc do because these directives are very important.
Same comment for versionadded

This would be great. Is there any plan to style these directives ?

authors: seanh stof

license: mit


text:
TC201 false positives for generics that are not generic at runtime

There's a whole bunch of generics defined in third party stubs packages, that do not derive from typing.Generic and thus are not subscriptable at runtime. Currently this plugin will emit a TC201 if those annotations are properly forward-declared using a string literal to avoid a runtime exception.
The plugin will either need to inspect the class to make sure it derives from typing.Generic and have a separate whitelist for the builtins that provide a __class_getitem__ without inheriting from typing.Generic, such as dict and list or just do what some other plugins do and add a setting for a blacklist or whitelist of classes which should be considered generic only at type checking time.
Without any change this produces far too many false positives for packages with third party stubs for TC201 to be useful in a large existing code-base, since you will need to add hundreds of noqa: TC201 comments.

Would you mind adding some code examples?

Sure, let's take WTForms as an example, it has no builtin type stubs and thus requires types-WTForms.
It defines an UnboundField as temporary container which contains all the information to construct a specific Field class once you create an instance of a Form. For the purposes of type checking UnboundField is generic, so you know what kind of a Field it will create once bound, but at runtime UnboundField does not inherit from typing.Generic so you will get a TypeError if you try to subscript it:
from wtforms import Field
from wtforms.fields.core import UnboundField

foo: 'UnboundField[Field]'  # TC201
bar: UnboundField[Field]   # TypeError – 'type' object is not subscriptable

The plugin will either need to inspect the class to make sure it derives from typing.Generic and have a separate whitelist for the builtins that provide a class_getitem without inheriting from typing.Generic, such as dict and list

It's been a while since I've looked at Python AST, but I don't think it's possible to do this without loading the file from disk. That would add a significant runtime cost to each file checked. Very happy to be proven wrong though!

or just do what some other plugins do and add a setting for a blacklist or whitelist of classes which should be considered generic only at type checking time.

I guess adding a setting for allowed stringified types would be OK, but it does seem like a lot of work for a relatively small improvement - no offense. I'm not seeing this in my day to day, and since this is the first issue mentioning it I guess few people are affected in general?
That said, do you think it would be worth implementing despite this and/or do you think this type of false positive will become more prevalent? (I know there's some stuff happening with generics in Python 3.12, but have to admit I haven't looked at it properly yet)
Would be happy to accept a PR if you think it'd be worth the time investment. Otherwise, perhaps adding a few noqa's will do for now?

@sondrelg Yes, it will probably be pretty costly to determine this dynamically and it would involve parsing the source module's code, so a whitelist/blacklist would definitely be a more economical solution.
Maybe a better solution would be to favor false negatives over false positives, meaning that you won't emit a TC201 if the string literal contains square brackets. I would also be happy enough if it was a setting or if it were split into two separate error codes for the two level of strictness, so you can either favor false negatives or false positives, depending on your use-case.
Seeing as a false negative on TC201 is completely harmless, while a false positive actually incurs a runtime exception, I would definitely prefer to have false negatives.

That's a good point. Nudging people towards runtime exceptions seems bad :+1:
Thinking about it, I cannot think of a reason why allowing string literals with square brackets wouldn't be a sound enough solution. Can you? TC201 is really just a helper to help avoid mixing the two styles of forward-referenced types, but it's not really important to not mix - it's just nice in general.

@sondrelg Yeah, I agree. I will open a PR.
We can always make it more sophisticated in the future with a user-extensible whitelist of subscriptable types, if we wanted to decrease false negatives, although then you would probably want to take the python version into account for a sane default list and then you're treading into flake8-typing-imports territory.

authors: Daverball sondrelg


text:
Add simple tracker initialization taking only urlEndpoint

This allows us to:

Dodge introducing the tracker's builder pattern
Avoid explaining what an Emitter is
Dodge introducing the emitter's builder pattern

We can go even further, Crashlytics style, and just build the tracker from config properties.

Closing as the upcoming version 2.0 introduces configurations avoiding the use of builder pattern for separate components. They will be created autonomously by the tracker once it receives all the configurations needed.
See issue #558

authors: AlexBenny alexanderdean

repo: snowplow/snowplow-objc-tracker


text:
Release/0.9.6

Bump to snowflake driver to latest in hopes that it resolves customer issue with odd error message.
Also edited copyright to 2022.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

Coverage remained the same at 22.424% when pulling a7273fde412214971aedbce3004701f8738ca2b6 on bump-dependencies into 1f679ab9ce0e4c006b0da998bf706995ded1e3af on master.

Suggesting that @adatzer reviews this as she bumped the Snowflake driver last time so has some recent knowledge of this and will hopefully remember how it was tested it last time.

I'd suggest we bump the Github actions to use go 1.17 then.

Good point @adatzer .
I've bumped the go version to 1.17 for the project and the GH actions. I don't think our tests cover whether doing so has any impact on the other targets (eg. if we're using the BQ driver for 1.15) - since 1.15 is no longer supported I think there's some small possibility, however I don't believe there are any breaking changes in the releases so I think we should be ok.
If we think that needs specific attention I can go ahead and manually test before we push release.

Ty! Totally agree on the other dependencies - I gave it a shot to bump them all in one go, and hit some compiler errors. One of those that could be 5 minutes or 5 hours, so I decided to just bump snowflake and prioritise finding out if the driver update makes a difference to the prod issue.
That issue might turn out to require a follow-up bugfix release, in which case I can spend the time to bump the rest!

authors: colmsnowplow coveralls paulboocock snowplowcla

repo: snowplow/sql-runner


text:
🛑 Archives is down

In 479867a, Archives (https://archives.sochara.org) was down:

HTTP code: 502
Response time: 366 ms

Resolved: Archives is back up in d8410ab after .

repo: sochara-org/status


text:
EXC_BAD_ACCESS in ssl_lib.cc (OWT related)

After compiling socket.io-client-cpp (with the help of socket.io-client-cpp-ios-static) linking the libsioclient_tls.a file into my project was not enough, as Xcode was still complaining about undefined symbols (_SSL_ctrl, _SSL_CTX_ctrl and _CONF_modules_unload). So I also linked OpenSSL's libcrypto.a and libssl.a file which eventually allowed me to successfully compile my project.
But now I am stuck with a runtime error which occurs as soon as I try to make a connection using OWT.
EXC_BAD_ACCESS (code=257, address=0x3f3910043fd)
#1	0x0000000100f046c8 in ::SSL_CTX_new(const SSL_METHOD *) at /../../third_party/boringssl/src/ssl/ssl_lib.cc:605

error: memory read failed for 0x7391004200

I downloaded CS_WebRTC_Client_SDK_iOS.v5.0.zip which contains precompiled OWT and WebRTC framework. After I linked those into my project the undefined OpenSSL symbols disappeared and I was able to build my project without linking OpenSSL. Now everything seems to be working fine.


text:
Override MarshalJSON for 'Operation' in libovsdb

Related to https://github.com/socketplane/libovsdb/pull/54
Currently the 'Where' field in libovsdb 'Operation' struct is
taggged with 'json:omitempty'. Because of this, querying an
entire table using an empty 'Where' clause(RFC 7047 #5.2.2) is not possible.
This fix overrides the MarshalJSON function to allow empty
'Where' clause for 'select' operations.
Signed-off-by: Surya Tatapudi surya.tatapudi@hpe.com

@dave-tucker Could you please take a look

LGTM. @statapudi could you please squash your commits? Then I can merge. Thanks

@dave-tucker Done, thanks!

Thanks for the contribution @statapudi ⭐

authors: dave-tucker statapudi

repo: socketplane/libovsdb


text:
Wrapper#accept might be crashing in production.

https://github.com/socketry/io-endpoint/blob/e82badc71d9f2e7e51af727f4a2a27976d094396/lib/io/endpoint/wrapper.rb#L157
    1m     warn: Async::Task [oid=0xdfc] [ec=0xde8] [pid=56009] [2024-05-08 20:40:28 +1200]
               | Task may have ended with unhandled exception.
               |   OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 peeraddr=[::1]:50598 state=error: ssl/tls alert certificate unknown
               |   → /home/samuel/.rubies/ruby-3.3.1/lib/ruby/3.3.0/openssl/ssl.rb:527 in `accept'
               |     /home/samuel/.rubies/ruby-3.3.1/lib/ruby/3.3.0/openssl/ssl.rb:527 in `accept'
               |     /home/samuel/.gem/ruby/3.3.1/gems/io-endpoint-0.10.2/lib/io/endpoint/wrapper.rb:157 in `accept'
               |     /home/samuel/.gem/ruby/3.3.1/gems/io-endpoint-0.10.2/lib/io/endpoint/generic.rb:83 in `block in accept'
               |     /home/samuel/.gem/ruby/3.3.1/gems/io-endpoint-0.10.2/lib/io/endpoint/bound_endpoint.rb:65 in `block (2 levels) in bind'
               |     /home/samuel/.gem/ruby/3.3.1/gems/async-2.11.0/lib/async/task.rb:164 in `block in run'
               |     /home/samuel/.gem/ruby/3.3.1/gems/async-2.11.0/lib/async/task.rb:377 in `block in schedule'

Need to investigate whether SSLSocket#accept is performing additional TLS negotiation (is it causing latency in the accept loop?)
Need to figure out the best way to rescue errors to avoid killing the accept loop.

https://github.com/socketry/io-endpoint/pull/10

repo: socketry/io-endpoint


text:
Add kdf functionality

Libsodium has a module for kdf separately from pwhash using blake2b. For completeness it probably makes sense to bind to it. I've already forked to start work in including it, you can find the commit here.

See https://github.com/sodiumoxide/sodiumoxide/pull/351

Can this be closed since #351 has been merged?

Fixed in https://github.com/sodiumoxide/sodiumoxide/pull/351

authors: GallagherCommaJack kpp tasn

repo: sodiumoxide/sodiumoxide


text:
Device Names?

If I change the device name (Bezeichnung) in the adapter config I receive the errors:
wifilight.0 | | error | Known names are: HF-LPB100-ZJ200, HF-LPB100-ZJ002, HF-A11-ZJ002, Mi-Light, AK001-ZJ100
wifilight.0 | | error | config.device Kueche links is not a known device. Skipping this device!

So  it's not possible to give the devices speaking names?
Disclaimer: I'm very very new to ioBroker

You should not change the name. The name must be the name of the device. So, remove the entry of the device an search again.

This issue was moved to iobroker-community-adapters/ioBroker.wifilight-community#4


text:
Fixed manual install. Updated Readme instructions.

As the title says, I’ve fixed the manual install, and included instructions for adding SSKeychain as a framework for iOS 8 and above.

Needs a rebase

authors: nicolasgomollon soffes

repo: soffes/SSKeychain


text:
Can't implement setState

Question
Hi Guys, I have this function:
async function search() {
     try {
    const response = await places.nearbysearch({
      location: text, // LatLon delimited by ,
      radius: distance,  // Radius cannot be used if rankBy set to DISTANCE
      type: ['cafe','bakery','meal_delivery','meal_takeaway','restaurant'], // Undefined type will return all types
      // rankby: "distance" // See google docs for different possible values
    });

    const { status, results, next_page_token, html_attributions } = response;

    var index = Math.floor(Math.random() * response.results.length);
    console.log(response.results[index].name);

    restName = response.results[index].name;
    console.log(restName);

  } catch (error) {
    console.log(error);
  }

 }

it is within export default function App() {}
I have made a text compenent within view like this:
return (
    <View style={styles.container}>

    <View style={{minWidth: '100%', minHeight: '100%', backgroundColor: '#f0fbff', alignFit:'stretch', marginTop: 0, alignItems:'center', justifyContent:'space-evenly'}}>
    <Card style={{padding: 5, margin: 1}}>
      <Text style={{ fontWeight: 'bold', fontSize: 25,  }}>{restName}{"\n"}</Text>

even though restName updates( I made a button that runs the search() function on press), the text does not update, how would I implement set state with this or refresh the variabel.
In short, the actual variable changes but it doesn't display anything differently

I believe it is not an issue of the library itself and probably some issue with your code. It would be for sure easier if you made a small reproduction of the issue in a form of e.g. snack. I do not see any react-native-svg components here also. Would you be able to provide such reproduction?

authors: PradyMagal WoLewicki

repo: software-mansion/react-native-svg


text:
Need to smooth the animation for path Svg

Hi, i created a responsive rectangle path svg, and implement it in svgPath with animation, i am able to do the animation like my rectangle created perfectly but i am unable to do it smoothly, what should i do
here is my code
const [plateAnimate] = useState(new Animated.Value(0));
plateAnimate.setValue(DataStore.getState().general.currentSecMin.sec);
const withCheckPath = `
					M${Size.widthInP(50.1)} ${Size.heightInP(1.88)}
					H${Size.widthInP(88.1)}
					Q${Size.widthInP(94.3)} ${Size.heightInP(2.2)}
					${Size.widthInP(94.8)} ${Size.heightInP(5.7)}
					V${Size.heightInP(17.4)}
					Q${Size.widthInP(93.7)} ${Size.heightInP(20.6)}
					${Size.widthInP(88.2)} ${Size.heightInP(20.7)}
					H${Size.widthInP(12.8)}
					Q${Size.widthInP(7.2)} ${Size.heightInP(20.1)}
					${Size.widthInP(6.5)} ${Size.heightInP(17.5)}
					V${Size.heightInP(5.7)}
					Q${Size.widthInP(6.9)} ${Size.heightInP(2.5)}
					${Size.widthInP(13)} ${Size.heightInP(1.88)}
					 H${Size.widthInP(50)}
	`;

<AnimatedSvg height={Size.heightInP(22)} width={Size.widthInP(100)} style={{ right: 2.5 }}>
						<AnimatedPath
							d={withCheckPath}
							strokeWidth={2}
							fill="none"
							stroke={isDarkBlue ? "#2A9DFF" : "#B3D6FF"}
							strokeDasharray={867}
							strokeDashoffset={
								plateAnimate.interpolate({
									inputRange: [0, 59],
									outputRange: [0, -867],
									extrapolate: "clamp",

								})
							}
						/>
					</AnimatedSvg>

I hope you understad the code and i am asking the right place

Could you provide a repo with a simple reproduction of the issue and more descriptive comment of what you are trying to achieve exactly? It is hard to say anything without it.

Hello @jawwad22,
If you are still experiencing the issue, please feel free to open a new issue with a simple reproduction of the problem. Thank you.

authors: WoLewicki bohdanprog jawwad22


text:
[BUG]  get_block not working anymore

What happened
The method call  await client.get_block("latest") is not working anymore with FullNodeClient
{'l1_gas_price': {'price_in_fri': ['Missing data for required field.']}, 'l1_data_gas_price': ['Missing data for required field.'], 'l1_da_mode': ['Missing data for required field.']}
are missing
Stack trace
 in wait_gas_starknet
    block_data = await client.get_block("latest")
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\...\venv\Lib\site-packages\starknet_py\net\full_node_client.py", line 120, in get_block
    return cast(StarknetBlock, StarknetBlockSchema().load(res, unknown=EXCLUDE))
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\...\venv\Lib\site-packages\marshmallow\schema.py", line 722, in load
    return self._do_load(
           ^^^^^^^^^^^^^^
  File "C:\...\venv\Lib\site-packages\marshmallow\schema.py", line 909, in _do_load
    raise exc
marshmallow.exceptions.ValidationError: {'l1_gas_price': {'price_in_fri': ['Missing data for required field.']}, 'l1_data_gas_price': ['Missing data for required field.'], 'l1_da_mode': ['Missing data for required field.']}

Steps to reproduce

client = FullNodeClient(node_url=random.choice(RPC["starknet"]["rpc"]))
call client.get_block("latest")

SDK Version
0.21.0
Python version
3.11
What operating system are you using?
Windows
Is there an existing issue for this?

[x] I have searched the existing issues and verified no issue exits for this problem.

Hi @marcelkb
All the fields l1_gas_price, l1_data_gas_price, and l1_da_mode are required. It seems that the node you're currently using might be running an outdated RPC version. Please verify the RPC version of the node. If it is different from 0.7.0 or 0.7.1, you should update the node or switch to another one that supports these versions. If you still believe the problem lies with starknet.py, feel free to reopen the issue.

@ddoktorski
changing to  "https://starknet-mainnet.public.blastapi.io/rpc/v0_7"
and using the newest version of the lib fixes the problem.
thanks for your support

authors: ddoktorski marcelkb


text:
entfernte & lokale Fortbildung unterscheiden

Hallo! Die Originalfrage klang, als zielte sie auf Dienstreisen ab. Daher die hier vorgeschlagene Unterscheidung.

Danke!

authors: StephanJanosch katrinleinweber

repo: softwaresaved/international-survey


text:
Datenumbau Naturreservate neue auch ins Subthema "ch.SO.NutzungsplanungUeberlagernd"

Alle Naturreservate (erlassen mit Einzelschutz oder per Nutzungsplanung) werden zukünftig im Modell http://geo.so.ch/models/ARP/SO_ARP_Naturreservate_20200609.ili (Edit-Schema: arp_naturreservate) nachgeführt.
Neu werden die Naturreservate nur noch per Nutzungsplanungsverfahren erlassen.
Der GRTEL-Job "oereb_einzelschutz_naturreservat" muss deshalb angepasst werden. Die Naturreservate werden neu auch im Subthema "ch.SO.NutzungsplanungUeberlagernd" publiziert. Ob die Naturreservate unter weiteres Thema "ch.SO.Einzelschutz" oder als Subthema "ch.SO.NutzungsplanungUeberlagernd" im ÖREB-Kataster publiziert wird, hängt vom Attribut "reservat.einzelschutz" ab.
Das heisst der GRTEL-Job "oereb_einzelschutz_naturreservat" beinhaltet zukünftig den Datenumbau für das weitere Thema "ch.SO.Einzelschutz" und für das Subthema "ch.SO.NutzungsplanungUeberlagernd". Der GRETL-Job kann deshalb unbenannt werden in "oereb_naturreservat".
Ich glaube folgende Änderungen müssen im "insert_oereb_einzelschutz_naturreservat_tables.sql" vorgenommen werden. Aber bitte gut prüfen... Das mit Artcode und Liste weiss ich nicht... muss man das auch noch ergänzen.

        CASE
      WHEN reservat.einzelschutz IS TRUE
          THEN 'WeiteresThema'
        ELSE 'Nutzungsplanung'
  END AS thema,
  CASE
      WHEN reservat.einzelschutz IS TRUE
          THEN 'ch.SO.Einzelschutz'
        ELSE Null
  END AS weiteresthema,
  CASE
      WHEN reservat.einzelschutz IS TRUE
          THEN Null
        ELSE 'ch.SO.NutzungsplanungUeberlagernd'
  END AS subthema

......

Entfernen.. bei  WHERE (Zeile 55/56)
    AND         reservat.einzelschutz IS TRUE
GRETL-Job "oereb_nutzungsplanung" muss nicht angepasst werden die Typ "N522_Naturreservat_inkl_Geotope" wurde nie publiziert im ÖREB-Kataster.
Bitte koordinieren mit Anpassung im WMS. Bei nutzungsplanung_ueberlagernd_flaeche.qml muss eine Anpassung gemacht werden. Darstellung ist identisch zum Einzelschutz.
Wahrscheinlich
filter="artcode =  'naturschutzgebiete'"  label="Naturschutzgebiete"

@andreasneumann Der Gretl-Job lief in der Testumgebung durch, aus meiner Sicht fehlt nur noch das Symbol für artcode = '5220', thema = 'Nutzungsplanung', subthema = 'ch.SO.NutzungsplanungUeberlagernd'

@andreasneumann Kannst du das QML "nutzungsplanung_ueberlagernd_flaeche.qml" noch anpassen (siehe oben)
artcode = '5220', thema = 'Nutzungsplanung', subthema = 'ch.SO.NutzungsplanungUeberlagernd' Label='Naturschutzgebiete'

Wurde mit https://github.com/sogis/oereb-wms/commit/ab05b51c8804d80356d153ed24a91944e8934791 umgesetzt.
Mit https://github.com/sogis/oereb-wms/commit/e1721f88c4580b4e2f227d1588b07132f37657e7 wurde zudem das CI endlich nach Github migriert und der WMS damit in der Testumgebung ausgerollt.

authors: Luescher andreasneumann barpasen

repo: sogis/oereb-gretljobs


text:
spl-math: Add separate package to test instruction usage

Problem
We are using math approximations to have unsigned ints behave like floats, but we don't have a good way to share the math or test the instruction usage of different calculations.
Solution
Add an spl-math package to address both of those issues!  The types and approximations defined in it can be reused across programs, and we can eventually publish this crate with other spl utilities.
PreciseNumber is directly copied from token-swap, which needs a lot of work, but this is just about isolating the PreciseNumber instruction usage.  There's no need to read through the PreciseNumber code in this review, except for copy/paste issues.  Improvements can come in later work.
Ideas for improvement:

use the approach in lending of implementing traits like TryAdd and returning Result instead of Option
change PreciseNumber to a U192 internally, which cuts down instructions by 1/4
update swap to use the u64 sqrt approximation

Since the PreciseNumber implementation of square root is so instruction-heavy, using 350k instructions to get the root of u64::MAX (!!), this also adds a u64-only approximation which uses less than 10k instructions.  For ease of review, that change is all in 9ced577 -- let me know if you prefer to move that to a separate PR

I think we should scrap the general newtonian root calculations for now, they add extra bloat for square root because there's a multiplication by one and power to one that add extra instructions. Also, I think having a trait that can be applied to all unsigned integers would be best. There's a developer asking for u128 for example, and I think we could implement that more easily with a trait and/or macro

Using number generics in 8d8a8f8 and removed generic newtonian approximation.  You were right, we went down from roughly 8k instructions to 2k.  I also tested to see the difference in number of instructions between the generic implementation and the u64 implementation, and they're exactly the same -- compilers are smart!

Yay zero cost abstractions!

Looks great, do you mind adding an instruction count test for u128 as well?

I worked on a clever (read: overly-complicated) template-based approach for different instructions, but it was very messy with almost nothing to gain.  We can figure out a macro later on if needed.

authors: joncinque jstarry

repo: solana-labs/solana-program-library


text:
Governance: Voting workflow

Implemented instructions:

CastVote
RelinquishVote
FinalizeVote
CancelProposal

Design changes:

FinalizeVote instruction was added to support votes which can't be tipped automatically while voting. It allows to finalise Proposal vote after max_voting_time expires by manually transitioning  it to Succeeded or Defeated state.
Common scenario addressed by FinalizeVote is low community engagement. It allows to set vote_theshould_percentage below 50% and still have a meaningful vote.

I've found the name deserialise_account_ for functions deserialising and validating at the same time to be confusing. In order to avoid the confusion I changed them to getter style get_account_ to distinguish from deserialisation only.

There's still the questions about the math, and after that this will be good to :shipit:

authors: SebastianBor joncinque


text:
Add UUGAA token

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

Reopening per request https://github.com/solana-labs/token-list/issues/16607

repo: solana-labs/token-list


text:
Metatype fixes

https://github.com/solettaproject/soletta/issues/1713
https://github.com/solettaproject/soletta/issues/1677

lgtm. Just check the @note comments.

merged with the fixes.

authors: ceolin otaviobp

repo: solettaproject/soletta


text:
OpenLink changes relating to Solid logout and switching accounts

Related issues:
https://github.com/solid/oidc-auth-manager/issues/20
https://github.com/solid/node-solid-server/issues/675

Thanks @cblakeley!

(This PR is superceded by https://github.com/solid/oidc-op/pull/7). Leaving this open for the moment as a reminder, will close later.

@dmitrizagidulin As this PR was superceded by solid/oidc-op#7, can you now close it? Thanks.

@cblakeley no prob. closing.

authors: cblakeley dmitrizagidulin

repo: solid/oidc-auth-manager


text:
Demo does not work with firefox

While the demo app works fine with chromium, with firefox just nothing happens when I click on Log in.
In the console I find
[WDS] Disconnected!
solid-auth-client is listening to http://localhost:8081 so ignored a message received from http://localhost:8080.

It does work with Firefox, as this is what I test on, but perhaps we follow slightly different steps. Can you explain step by step what you are doing? Thanks.

Sorry,  probably the popup opened in the background. :flushed:
Works now.

Awesome 👍

repo: solid/solid-auth-client


text:
Playground in tutorial is not loading

Hi, it is been down for few days for me.
Repro steps:

Go to some tutorial page: https://www.solidjs.com/tutorial/stores_context
Look at the playground

Expected result:
Playground is loaded and functional
Actual result:
Playground window shows "Loading the playground..." text, console has one error:
The requested module 'https://cdn.skypack.dev/solid-js/web' does not provide an export named 'createComponent'

Not sure if this is correct repo to submit issue though... If it is not, please kindly redirect me to the correct one. Thanks!

Closing as fixed (Ryan published a new version that skypack accepted, and hopefully soon we'll publish a new version with jspm instead of skypack)

repo: solidjs/solid-playground


text:
Proposal: data with better type elimination from createResource

const [data] = createResource(...);

Currently, data returns an accessor that returns the current result of the resource. To check if it is still loading, we use data.loading and use data.error when checking for failures. This is great but not for Typescript.
https://github.com/solidjs/solid/blob/main/packages/solid/src/reactive/signal.ts#L216-L233
The accessor returns T | undefined but that is incorrect for 3 reasons:

Suspense should guarantee the type is exactly what is returned for data.
undefined is a valid value for a Promise to result into.
The presence of data.loading and data.error is not exclusive enough to perform type elimination.

There is a way to fix this but would introduce a breaking change:
interface Pending {
  status: 'pending';
  value?: undefined;
}
interface Success<T> {
  status: 'success';
  value: T;
}
interface Failure {
  status: 'failure';
  value: any;
}
type Result<T> = Success<T> | Failure | Pending;

// Either the bottom one or a proxy for Result<T>
type ResourceData<T> = () => Result<T>;

This way, the result is deterministic, exclusive and can be type-eliminated.
const result = data(); // Result<T>;
switch (result.status) {
  case 'pending': // Pending
    return null;
  case 'success': // Success<T>
    return
Success! {result.value}
;
  case 'failure': // Failure
    return
Something went wrong. {result.value.message}
;
}

I see. That's interesting. I guess with that API it doesn't even need to be a function accessor. It just has 2 getters. My instant hesitation was I liked the whole feels like a Signal thing.. with Suspense you rarely use the loading or error states.
We can't do that union trick the other way I guess. Like this won't fly?
interface Pending {
  loading: true;
  error: false;
  (): undefined;
}
interface Success<T> {
  loading: false;
  error: false;
  (): T;
}
interface Failure {
  loading: false;
  error: any;
  (): undefined;
}

I'm gathering not or you would have suggested it.
Hmm, it is breaking though which ties my hands I think for now.

I think that should work as well! Although I'm not sure if we can correctly eliminate the types (for instance, checking for data.error doesn't really eliminate into Failure. Is there a merit on adding a similar field to data.status? status helps brand the types.

Yeah this shows a lot of my misunderstanding of TS I was thinking keeping things in their own lanes would help typing instead of pushing the error through data. As I was saying loading and error were sort of secondary considerations. I don't want data to hold the error incase people aren't checking for it. I think status is probably fine addition and wouldn't be breaking.

I added a TypeScript playground link to demonstrate type eliminations with your idea (+ status). Seems to be behaving as expected.

Yeah we can do that I need to figure out which state is the source of truth.. status is probably derived like
{
  get status() {
     return error() ? "failure" : loading() ? "pending" : "success"
  }
}

Question of which strings we should use. Is it "success"? is it "failure"? Sometimes resources will start at "success" I guess. .
Is there a 4th state when it's never run and isn't triggered initially?

"pending" is set before the fetcher is run. "success" and "failure" corresponds to both when Promise resolves. I think "pending" is also enough for when the fetcher itself hasn't been evaluated yet.

Ok yeah because it is just boolean not true. And that's fine because status enough to type narrow ok. Yeah I am onboard for this then. Let's see if anyone has any thoughts. But I think we can get this out in the next minor version I guess.

After re-evaluating, I think there is a possible 4th state: "stale", a cross between "pending" and "success". It is loading: true while (): T.

I think this proposal is fine, though I'm not sure about "stale". Before moving forward with it, I think we should examine some realistic use-cases to see how well it works in practice. Switching on a string value using a real JS switch works well but I doubt this would be the way people actually end up using it. More likely I expect people to use JSX <Switch>+<Match>, <Show>, or ternaries. That being the case having to check against a string value ends up being pretty verbose.
function Comp() {
  const [data] = createResource(...);

  return (
    <Switch>
      <Match when={data.status === 'pending'}>

Loading...

      </Match>
      <Match when={data.status === 'failure'}>

{data.error}

      </Match>
      <Match when={true}>

{data()}

      </Match>
    </Switch>
  );
}

While not a reason to do nothing here, when using the control flow components, type narrowing doesn't really work anyways thought I'm hopeful we may be able to do more with TypeScript 4.4. Should probably try out the beta.

"stale" is yet optional, but the current behavior of createResource suggest that it will never be applied.
There's not much in 4.4 that can help us narrow types here. <Show> is the closest one I can think of since it also allows proper type elimination through render prop the last time I checked.

That works but it also changes the behavior. It basically keys it since data being passed through can change. Not just boolean. So type narrowing is just hard. Because our control flow isn't even keywords. Im not even sure LSP hacks make sense.

I looked at React query they have 4 states as well. "idle", "loading", "success", "error". They consider it idle whenever it is in a don't fetch state ie.. if the query is null in our case.  They don't have "stale" but also have a "isFetching". To be fair I use "loading" this way and it's up to the user whether they unmount it. But it appears React query only gives the "loading" status when there is no data available. I'm not sure there needs to be a no data check other than checking for data yourself.
It is interesting because changing the query in Solid doesn't wipe the resource value. We keep it around so I realize our proposed types aren't quite right. We can use "stale" for that I guess. But it also doesn't remove from the "success" state in a sense. So there is a question of whether we cater status for this initial load story because that is not how I've node the independent states.

Pending, Success and Failure are all states that I derived from the original Promise behavior.
We can consider Idle in SSR context however the values that it represents are completely similar (and behaves similarly) to that of Pending.
Meanwhile, Stale is completely derived from stale-while-revalidate strategy (give stale data while fetching new one). Not all data-fetching libraries have this behavior tho, and was completely opt-in by other libraries like React Query and Relay.

Here's a flowchart.

Pending is the initial state of a resource. It transitions to Success when resolving while Failure when it throws an error.
Success will transition back to Pending during a re-fetch. This is only applicable when the behavior is "network-only" (there's no cache).
Success will transition to Stale if the behavior is stale-while-revalidate.
Stale is similar to Pending except that there's a cached data from the previous Promise.
Stale will transition to Pending if the the resolution time is more of the stale age (this is a completely optional behavior). In React, this behavior is akin to a useDeferredValue/useTransition that takes more than 5 seconds to apply (based on the RAIL model).

Yeah I think it's interesting because React Query's is____ properties are like the current create resource but their status is closer to what is being proposed here. But if we include stale the success path of the switch like @rturnq  posted above includes both success and stale.  That's my only concern since it regresses from success which might not be obvious. React Query doesn't. But I do think you are right in that they are separate states.
useTransition handles stale pretty well. useDeferredValue allowing means to inverse the stale propagation. I do think with fine-grained we might be able to find a different way to handle this. Like tell the resource to only trigger on initial load etc.. I think useDeferredValue is super awkward way to detect stale state since we deal with containers rather than values. Our experiments only cemented that I don't think it's the best way but that's tertiary to what is being discussed here.
The main case for idle is fetching on demand. Like when the component loads you don't load it. But then on click load data. It isn't treated like loading since there is no intention perhaps of ever loading.

The main case for idle is fetching on demand. Like when the component loads you don't load it. But then on click load data. It isn't treated like loading since there is no intention perhaps of ever loading.

Is there an example case-scenario for this? I do think this works well for call-to-action fetches (e.g. POST) and not for data-derived UI. I may be wrong tho.

authors: LXSMNSYC rturnq ryansolid

repo: solidjs/solid


text:
add Bytes to ObjHashable

str is bytes in python2, and is the most common dict key, so it's necessary to support bytes as hashable when processing old data.

Maybe I should add some tests? Anyway this works for me.

Ok sure, I guess that's fine with me. Having some at least one test for this would be good; whatever you used to check if it works is probably good enough; if you're not sure whether to put a test in crate::test, crate::util::test, or crate::read::test, feel free to ask. Since this only changes something that used to be an error, I think a minor version bump should be fine, so please rebase onto master (because I merged #8) and then change the crate version to 0.4.2.
For proper Python 2 support, see #1 and https://github.com/landaire/py-marshal.

No problem, I have added one test for dict and one test for set.
Thanks for the reminder! Currently I only need to decode some basic types, no user defined classes, so this would be enough for me.

Done! https://crates.io/crates/py-marshal/0.4.2

authors: OmmyZhang sollyucko

repo: sollyucko/py-marshal


text:
[WIP] Add macOS support

This PR attempts to add support for macOS:

[x] goreleaser target
[x] attaching loopback device with hdiutil
[ ] mounting ext4 volumes via ext4fuse (in progress)

looks cool!

@yuval-k If only I could get that ext4 working on macOS 😂

authors: nfx yuval-k

repo: solo-io/packer-plugin-arm-image


text:
🛑 zakazbiletov.kz is down

In c8f9426, zakazbiletov.kz (https://zakazbiletov.kz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: zakazbiletov.kz is back up in 79c303a after 14 minutes.


text:
Fix 2-digit page pagination

Calling .next() or .prev() on 2-digit pages was not working. It was just a wrong regex.
Besides the fix, I expanded the pagination tests to also test the calls to .next() and .prev().
PS: I've never used fauxJax before, so not sure if the way I reset it for each test is the proper way.

Nice! Thank you @dcardosods  for opening this Pull-Request.
I'm taking a look at it now.
Quick questions to better understand your needs and get some feedbacks:

What kind of application are you developing using solvebio-js?
Are you using this package on the front-end or on the server side?
How did you find solvebio-js?

Thanks!

Can you please combine your 3 test suites 'Next page', 'Prev page' and '2-digit prev page' into one suite Test pagination?
You can change the faux-jax response in tests/init.js with 2-digits pages.
In your test suite I would test the following:

should have next function and prev function
should request 2-digit prev page
should request 2-digit next page

Also can you please chain your promises callbacks?
SolveBio.Dataset().all()
        .then(function(data) {
              return data.prev();
        })
        .then(function(dataPrev) {
              expect(dataPrev.url).toEqual('https://api.solvebio.com/v1/datasets?page=11');
              done();
        });

instead of
SolveBio.Dataset().all()
        .then(function(data) {
          data.prev()
            .then(function(dataPrev) {
              expect(dataPrev.url).toEqual('https://api.solvebio.com/v1/datasets?page=11');
              done();
            });
        });

@jercoh  I pushed the changes you asked.
To answer your questions...
I searched solvebio on github and found this repo. It seems to be not mentioned on the API docs, like the python and ruby packages are.
I'm using this package on the front-end, and our application is around variant data.

authors: dcardosods jercoh

repo: solvebio/solvebio-js


text:
Fix tests

Closes #410.

Tests are still failing

Thanks @phansys !

authors: VincentLanglet franmomu phansys

repo: sonata-project/EntityAuditBundle


text:
Once set, the URL in the options page cannot be updated

Once the URL has been initially set, it cannot be updated without uninstalling and installing the extension.  Feels like something around field validation. Found by a user and reproduced by me.

I am not seeing this in the latest repo version


text:
Azure 配置报错：DeploymentNotFound, message The API deployment for this resource does not exist.

想用one api 将opeai api转化为azure openai的格式，目前遇到的问题是，执行：docker run -d --restart always -p 3000:3000 -v /home/ubuntu/data/one-api:/data justsong/one-api。后，通过主机ip访问并在渠道页面添加了 azure 和openai的key 各一个，都是测试过可以使用的。 设置令牌之后，使用https://github.com/lss233/chatgpt-for-bot-docs ，无论将 http://主机ip;3000 设置为 api_endpoint还是 proxy。均无法使用，但直接使用渠道页面添加的openai api是可以使用的。请问该如何设置

应设置为 API Endpoint，你提到的这个项目貌似没什么热度，不排除项目本身的问题。
另外 One API 是把 Azure 的格式转换为 OpenAI 的格式，而不是反过来。

应设置为 API Endpoint，你提到的这个项目貌似没什么热度，不排除项目本身的问题。
另外 One API 是把 Azure 的格式转换为 OpenAI 的格式，而不是反过来。

是的，我需要的就是将Azure 的格式转换为 OpenAI 的格式，但是目前的情况是，我换了很多个github上面的项目， 都无法使用。
使用格式是：
api_endpoint = "http://主机ip:3000/"
api_key = "令牌中复制"
以这个格式放在很多的项目中都无法运行。
渠道中使用的是openai的api，点击测试，响应时间正常， 弹出页面反馈也正常
azure的api放在渠道中点击测试，响应时间正常， 但会显示
DeploymentNotFound, message The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again.
名称为 azure上的部署名， 默认api版本设置2023-03-15-preview
请问，是否存在设置上的错误，该如何检查？

设置上有问题，Azure 的部署名有要求的，设置界面有写。

弄好了。。原来是 api_endpoint = "http://主机ip:3000/v1"要在后面加一个v1

为防止其他人误解，我说明一下，这个是上面所提到的项目的格式要求，一般而言并不需要加 v1

authors: fangconquerord songquanpeng

repo: songquanpeng/one-api