profile
viewpoint
Konrad `ktoso` Malawski ktoso We sell fruit. ¯\_(ツ)_/¯ I'm fine, thanks! Tokyo http://www.kto.so Serverside Swift & Dist. Systems @ ; ex-Akka core team | Reactive Streams TCK | Java Champion

apple/swift-evolution 11773

This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.

git-commit-id/git-commit-id-maven-plugin 1162

Maven plugin which includes build-time git repository information into an POJO / *.properties). Make your apps tell you which version exactly they were built from! Priceless in large distributed deployments... :-)

apple/swift-cluster-membership 145

Distributed Membership Protocol implementations in Swift

apple/swift-distributed-tracing 37

Instrumentation library for Swift server applications

drexin/akka-io-file 30

An asynchronous file handling module for Akka IO

DougGregor/swift-evolution 26

This maintains proposals for changes and user-visible enhancements to the Swift Programming Language.

apple/swift-distributed-tracing-baggage 10

Minimal context propagation container with Logging

fridek/Angry-Browsers 7

Box2Dweb based port of Angry Birds

pull request commentapple/swift

Enable RLE on OSSA

Build failed Swift Test OS X Platform Git Sha - 66ef200105a86e7890d0fcc2ecedb9b144b717f8

meg-gupta

comment created time in 14 minutes

PR closed EventStore/EventStore.Akka.Persistence

Update specs2-core to 4.10.5

Updates org.specs2:specs2-core from 4.10.0 to 4.10.5.

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

<details> <summary>Files still referring to the old version number</summary>

The following files still refer to the old version number (4.10.0). You might want to review and update them manually.

CHANGELOG.md

</details> <details> <summary>Ignore future updates</summary>

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.specs2", artifactId = "specs2-core" } ]

</details>

labels: test-library-update, semver-patch, old-version-remains

+1 -1

1 comment

1 changed file

scala-steward

pr closed time in 17 minutes

pull request commentEventStore/EventStore.Akka.Persistence

Update specs2-core to 4.10.5

Superseded by #65.

scala-steward

comment created time in 17 minutes

PR opened EventStore/EventStore.Akka.Persistence

Update specs2-core to 4.10.6

Updates org.specs2:specs2-core from 4.10.0 to 4.10.6.

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

<details> <summary>Files still referring to the old version number</summary>

The following files still refer to the old version number (4.10.0). You might want to review and update them manually.

CHANGELOG.md

</details> <details> <summary>Ignore future updates</summary>

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.specs2", artifactId = "specs2-core" } ]

</details>

labels: test-library-update, semver-patch, old-version-remains

+1 -1

0 comment

1 changed file

pr created time in 17 minutes

pull request commentapple/swift-corelibs-foundation

XMLParser fixes (SR-13546, SR-2301)

@swift-ci test

dhoepfl

comment created time in 23 minutes

push eventrsocket/rsocket-java

Oleh Dokuka

commit sha f2cfe20dba0fcd5a352ee14b6667239a1a6e75a9

adds example of enabling websocket frame aggregation Signed-off-by: Oleh Dokuka <shadowgun@i.ua>

view details

push time in 24 minutes

pull request commentapple/swift

Enable RLE on OSSA

@swift-ci test

meg-gupta

comment created time in 31 minutes

push eventreal-logic/aeron

mjpt777

commit sha 08ca6f0ac8047dad4328a245f1940550c8b8f98c

[Java] Javadoc.

view details

push time in 35 minutes

pull request commentreal-logic/aeron

[C++] Archive client shared library addition

We are currently using it to try archiving, as existing binary requires shared lib dlopen for integration with any 3rd party.

sshanks-kx

comment created time in 36 minutes

pull request commentapple/swift-corelibs-libdispatch

docs: fix simple typo, transiton -> transition

@swift-ci please test

timgates42

comment created time in an hour

pull request commentreal-logic/aeron

[C++] Archive client shared library addition

We have come to regret merging the previous support for creating a DLL. The implementation was partial and fills our build with so many warnings that important issues get missed. We are considering the removal of the DLL creation.

sshanks-kx

comment created time in an hour

CommitCommentEvent

issue commentreal-logic/aeron

QoS configuration option

We would be happy to consider a PR it it applies to both Java and C driver and comes with tests.

It should be configurable via system property, driver context, and URI param. We can discuss naming on a PR.

oktal

comment created time in an hour

Pull request review commentapple/swift-evolution

[Proposal Revision] Extend property wrappers to functions and closure parameters.

 func buy(  ## Detailed design -Property wrappers are essentially sugar wrapping a given declaration with compiler-synthesized code. This proposal retains this principle. Annotating a parameter declaration with a property-wrapper attribute allows the call-site to pass a wrapped value or a projected value, and the compiler will automatically initialize the backing wrapper to pass to the function. The function author can also use the property-wrapper syntax for accessing the backing wrapper and the projected value in the body of the function.+Property wrappers are essentially sugar wrapping a given declaration with compiler-synthesized code. Retaining this principle, a function can now be called with the wrapped and projected values. Namely, annotating a parameter declaration with a property-wrapper attribute changes the declaration’s type to the backing storage, and prompts the compiler to synthesize the wrapped and projected values. When the function is called the compiler will, also, insert a call to the appropriate property-wrapper initializer.

Ok, I see your point. Upon rereading the paragraph, I realize that expecting to hear about the current design (since it's in the section's name), I read about existing behavior, which is then paralleled to new behavior. I find this problematic because the reader will –– up to this point –– be unfamiliar with this new behavior. Thus, what do you think of simply moving the first two periods in the end?


Annotating a parameter declaration with a property-wrapper attribute allows the call-site to pass a wrapped value or a projected value, and the compiler will automatically initialize the backing wrapper to be passed to the function. The function author can also use the property-wrapper syntax for accessing the backing wrapper and the projected value within the body of the function. This behavior merely builds on property wrappers’ being sugar wrapping a given declaration with compiler-synthesized code.

filip-sakel

comment created time in an hour

push eventreal-logic/aeron

mjpt777

commit sha bbfeeed1297ecfe43e0b427ca779fb3a6cafd66e

[Java] Update documentation.

view details

push time in an hour

pull request commentapple/swift

[AST] #SR-13906 (Improvement) Error Messages

@swift-ci Please smoke test

aniketiq

comment created time in an hour

Pull request review commentakka/akka

Client-side mutual TLS bug.

    @ClassRule   public static AkkaJUnitActorSystemResource actorSystemResource =-    new AkkaJUnitActorSystemResource("JavaFutureTests", AkkaSpec.testConf());+      new AkkaJUnitActorSystemResource("JavaFutureTests", AkkaSpec.testConf());

Done! But I can't pass typesafe-cla-validator. I have done a commit which github doesn't consider to be linked to my account. How can I fix that?

TigranOhanyan

comment created time in 2 hours

CommitCommentEvent

PR opened open-telemetry/opentelemetry-specification

Update spec compliance for Swift

Changes

Update spec compliance for Swift

+5 -5

0 comment

1 changed file

pr created time in 2 hours

push eventakka/akka.io

Johan Andrén

commit sha 754f1eb8b40160ded320b8793eefba1822505832

Akka HTTP 10.2.3 release (#774) * Akka HTTP 10.2.3 release * Update blog/_posts/2021-01-18-akka-http-10.2.3-released.md Co-authored-by: Arnout Engelen <arnout@bzzt.net> Co-authored-by: Arnout Engelen <arnout@bzzt.net>

view details

push time in 2 hours

delete branch akka/akka.io

delete branch : akka-http-10.2.3

delete time in 2 hours

PR merged akka/akka.io

Akka HTTP 10.2.3 release
+67 -1

0 comment

2 changed files

johanandren

pr closed time in 2 hours

push eventreal-logic/aeron

mjpt777

commit sha 2e5f3b245e604b6317e3805c19c8a8a2bd72a3cf

[Java] Use timer check deadline rather than time of last check to do less work per check.

view details

push time in 2 hours

pull request commentakka/akka

Client-side mutual TLS bug.

Test FAILed.

TigranOhanyan

comment created time in 2 hours

Pull request review commentapple/swift-evolution

[Proposal Revision] Extend property wrappers to functions and closure parameters.

 func buy(  ## Detailed design -Property wrappers are essentially sugar wrapping a given declaration with compiler-synthesized code. This proposal retains this principle. Annotating a parameter declaration with a property-wrapper attribute allows the call-site to pass a wrapped value or a projected value, and the compiler will automatically initialize the backing wrapper to pass to the function. The function author can also use the property-wrapper syntax for accessing the backing wrapper and the projected value in the body of the function.+Property wrappers are essentially sugar wrapping a given declaration with compiler-synthesized code. Retaining this principle, a function can now be called with the wrapped and projected values. Namely, annotating a parameter declaration with a property-wrapper attribute changes the declaration’s type to the backing storage, and prompts the compiler to synthesize the wrapped and projected values. When the function is called the compiler will, also, insert a call to the appropriate property-wrapper initializer.

I think these changes have obscured the meaning/purpose of this paragraph.

Retaining this principle, a function can now be called with the wrapped and projected values

I don't think this makes sense without the context of "Annotating a parameter declaration with a property-wrapper attribute". Also, the fact that a function can be called with a wrapped value or a projected value of a property wrapper doesn't really follow from "retaining this principle"

annotating a parameter declaration with a property-wrapper attribute changes the declaration’s type to the backing storage

This isn't something we want to state unless we're explicitly talking about how the code is compiled. As far as the user is concerned, the function type does not take in the backing storage. That's why had worded the sentence to be about the call-site.

and prompts the compiler to synthesize the wrapped and projected values

The wrapped and projected values are not synthesized, they're provided by the user.

I'm not sure why this last sentence was removed:

The function author can also use the property-wrapper syntax for accessing the backing wrapper and the projected value in the body of the function

This is showcasing how the feature is useful for function authors because they now have property-wrapper syntax in the body of the function.

filip-sakel

comment created time in 2 hours

pull request commentakka/akka

Client-side mutual TLS bug.

At least one pull request committer is not linked to a user. See https://help.github.com/en/articles/why-are-my-commits-linked-to-the-wrong-user#commits-are-not-linked-to-any-user

TigranOhanyan

comment created time in 2 hours

issue openedakka/akka

Invalid incoming TLS handshake should abort, not close the connection

When the TLS stage receives an invalid handshake (e.g. a non-TLS connection), the stage is closed rather than failed, causing the connection to be completed normally (FIN) instead of aborted (RST).

It seems https://github.com/akka/akka/pull/18655 added this behavior for some messages, but didn't introduce failing on SSLExceptions during wrapping/unwrapping (perhaps to be conservative in the scope of the change?)

created time in 3 hours

pull request commentakka/akka

Client-side mutual TLS bug.

Test FAILed.

TigranOhanyan

comment created time in 3 hours

push eventapple/swift-evolution

Joe Groff

commit sha 753e81fad04f070a39df867f10ecab90fab84d49

begin review for SE-299

view details

push time in 3 hours

startedpawelkaczor/scalexpr

started time in 3 hours

more