profile
viewpoint

pyrtsa/poly 45

Solving the Expression Problem in C++11

pyrtsa/Frameless 1

The spiritual successor to Less Framework

pyrtsa/homebrew-dupes 1

System duplicate formulae for the Homebrew package manager

pyrtsa/nt2 1

The Numerical Template Toolbox - C++ Scientific Computing Made Easy

pyrtsa/alga 0

Algebraic graphs

pyrtsa/atom-language-idris 0

A Idris Mode for Atom.io

pyrtsa/atom-nix 0

Nix syntax highlighting for Atom

pyrtsa/CocoaPods 0

An Objective-C library dependency manager.

pyrtsa/CryptoSwift 0

Crypto related functions and helpers for Swift implemented in Swift programming language

pyrtsa/easyexif 0

Tiny ISO-compliant C++ EXIF parsing library, third-party dependency free.

fork pyrtsa/sswg

Swift Server Working Group (SSWG)

https://swift.org/server/

fork in a day

pull request commentapple/swift-algorithms

Add sliding windows algorithm

Any reason not to rename the function accordingly now, windows(ofCount:)slidingWindows(ofCount:)?

ollieatkinson

comment created time in 15 days

issue commentapple/swift-algorithms

Consider adding scan

I think scan can be taken as a name of art (also used by Combine framework), but this might be a good opportunity to consider the term reductions which is more noun-like, pairs up nicely with reduce, is also used elsewhere, and has been proposed and supported in the past for Swift.

The term scan is established e.g. in Haskell, but in Haskell what we call reduce is known by a different name too: it's a fold.

fwgreen

comment created time in 15 days

issue commentapple/swift-algorithms

Consider adding scan

+1 on the idea.

I'd rather see the latter function with the following signature, allowing for a different result type and aligning with Sequence.reduce(_:_:):

extension Sequence {
    func scan<Result>(_ initialResult: Result, _ nextPartialResult: (Result, Element) throws -> Result) rethrows -> [Result]
}

Also a lazy counterpart for both functions seems like a useful thing to include.

fwgreen

comment created time in 15 days

pull request commentapple/swift-algorithms

Add "partiallySorted(count:)" to Collection

I wonder if instead of the non-mutating partiallySorted, we in fact need just the function which only returns the sorted prefix of the partially sorted input. Wouldn't that lead to a more natural name?

extension Sequence {
     public func sortedPrefix(_ count: Int, by areInIncreasingOrder: (Element, Element) throws -> Bool) rethrows -> [Element]
 }

 extension Sequence where Element: Comparable {
     public func sortedPrefix(_ count: Int) -> [Element]
 }

Example:

let numbers = [7,1,6,2,8,3,9]
let smallestThree = numbers.sortedPrefix(3, <)
// [1, 2, 3]
rakaramos

comment created time in 17 days

issue commentapple/swift-algorithms

A `first` operator that returns the first non-nil transformed value

@ktoso I think you mixed up the type signatures? And if you did, isn't func collect<R>(_ transform: (Element) -> R?) -> [R] what we already know as compactMap(_:)?

Qata

comment created time in 17 days

issue commentapple/swift-algorithms

A `first` operator that returns the first non-nil transformed value

That would be a useful addition!

The current alternative could be code golfed down to this though:

let value = ["Hello", "10"].lazy.compactMap(Int.init).first
Qata

comment created time in 17 days

issue closedfastlane/fastlane

upload_to_app_store failing when uploading no screenshots

<!-- Thanks for helping fastlane! Before you submit your issue, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) -->

New Regression Checklist

Regression Information

<!-- Knowing the breaking versions and last working versions helps us track down the regression easier -->

  • Breaking version: [e.g. 2.156.0]
  • Last working version: [e.g. 2.149.1]

Regression Description

In our setup we never had any screenshots to upload by Fastlane and upload_to_app_store worked fine. Having today updated to the latest Fastlane, uploads to App Store started failing with this error:

Failed verification of all screenshots uploaded... 0 incomplete screenshot(s) still exist

This error is unexpected because we don't expect any screenshots to be uploaded so there's really nothing to verify about them either. (OTOH we never specified skip_screenshots.)

As a workaround, setting the environment variable DELIVER_SKIP_SCREENSHOTS=true made the upload pass.

The above error message was introduced by https://github.com/fastlane/fastlane/pull/16972, so I assume this to be a new regression in 2.156.0.

Complete output when running fastlane, including the stack trace and command used

<details> <pre> [13:55:26]: Will begin uploading snapshots for '3.2.1' on App Store Connect [13:55:26]: Starting with the upload of screenshots... [✔] Waiting for all the screenshots processed... [13:55:29]: Failed to upload all screenshots... Tries remaining: 4 [✔] Waiting for all the screenshots processed... [13:55:30]: Failed to upload all screenshots... Tries remaining: 3 [✔] Waiting for all the screenshots processed... [13:55:32]: Failed to upload all screenshots... Tries remaining: 2 [✔] Waiting for all the screenshots processed... [13:55:34]: Failed to upload all screenshots... Tries remaining: 1 [✔] Waiting for all the screenshots processed... ... [13:55:35]: Failed verification of all screenshots uploaded... 0 incomplete screenshot(s) still exist

+------+---------------------------------------------------------------+-------------+ | fastlane summary | +------+---------------------------------------------------------------+-------------+ | Step | Action | Time (in s) | +------+---------------------------------------------------------------+-------------+ | ... | 💥 | upload_to_app_store | 22 | +------+---------------------------------------------------------------+-------------+

[13:55:35]: fastlane finished with errors

[!] Failed verification of all screenshots uploaded... 0 incomplete screenshot(s) still exist</pre> </details>

Environment

Essentially we have skip_screenshots at its default value of false but no screenshots to upload by Fastlane when this error happens.

closed time in a month

pyrtsa

issue commentfastlane/fastlane

upload_to_app_store failing when uploading no screenshots

The fix works now. Thank you!

pyrtsa

comment created time in a month

issue commentfastlane/fastlane

upload_to_app_store failing when uploading no screenshots

Thank you! Will test it soon.

pyrtsa

comment created time in 3 months

issue openedfastlane/fastlane

upload_to_app_store failing when uploading no screenshots

<!-- Thanks for helping fastlane! Before you submit your issue, please make sure to check the following boxes by putting an x in the [ ] (don't: [x ], [ x], do: [x]) -->

New Regression Checklist

Regression Information

<!-- Knowing the breaking versions and last working versions helps us track down the regression easier -->

  • Breaking version: [e.g. 2.156.0]
  • Last working version: [e.g. 2.149.1]

Regression Description

In our setup we never had any screenshots to upload by Fastlane and upload_to_app_store worked fine. Having today updated to the latest Fastlane, uploads to App Store started failing with this error:

Failed verification of all screenshots uploaded... 0 incomplete screenshot(s) still exist

This error is unexpected because we don't expect any screenshots to be uploaded so there's really nothing to verify about them either. (OTOH we never specified skip_screenshots.)

As a workaround, setting the environment variable DELIVER_SKIP_SCREENSHOTS=true made the upload pass.

The above error message was introduced by https://github.com/fastlane/fastlane/pull/16972, so I assume this to be a new regression in 2.156.0.

Complete output when running fastlane, including the stack trace and command used

<details> <pre> [13:55:26]: Will begin uploading snapshots for '3.2.1' on App Store Connect [13:55:26]: Starting with the upload of screenshots... [✔] Waiting for all the screenshots processed... [13:55:29]: Failed to upload all screenshots... Tries remaining: 4 [✔] Waiting for all the screenshots processed... [13:55:30]: Failed to upload all screenshots... Tries remaining: 3 [✔] Waiting for all the screenshots processed... [13:55:32]: Failed to upload all screenshots... Tries remaining: 2 [✔] Waiting for all the screenshots processed... [13:55:34]: Failed to upload all screenshots... Tries remaining: 1 [✔] Waiting for all the screenshots processed... ... [13:55:35]: Failed verification of all screenshots uploaded... 0 incomplete screenshot(s) still exist

+------+---------------------------------------------------------------+-------------+ | fastlane summary | +------+---------------------------------------------------------------+-------------+ | Step | Action | Time (in s) | +------+---------------------------------------------------------------+-------------+ | ... | 💥 | upload_to_app_store | 22 | +------+---------------------------------------------------------------+-------------+

[13:55:35]: fastlane finished with errors

[!] Failed verification of all screenshots uploaded... 0 incomplete screenshot(s) still exist</pre> </details>

Environment

Essentially we have skip_screenshots at its default value of false but no screenshots to upload by Fastlane when this error happens.

created time in 3 months

more