text:
Running rake android[test] fails

Finished in 30 secs

Error:
spec home, accessibility, and animation#test_0001_spec:
Timeout::Error: execution expired
/Library/Ruby/Gems/2.0.0/gems/appium_lib-3.0.2/lib/appium_lib/common/helper.rb:43:in sleep' /Library/Ruby/Gems/2.0.0/gems/appium_lib-3.0.2/lib/appium_lib/common/helper.rb:43:inrescue in block in wait'
/Library/Ruby/Gems/2.0.0/gems/appium_lib-3.0.2/lib/appium_lib/common/helper.rb:38:in block in wait' /Library/Ruby/Gems/2.0.0/gems/appium_lib-3.0.2/lib/appium_lib/common/helper.rb:36:inwait'
/Library/Ruby/Gems/2.0.0/gems/appium_lib-3.0.2/lib/appium_lib/driver.rb:161:in rescue in block (3 levels) in promote_singleton_appium_methods' /Library/Ruby/Gems/2.0.0/gems/appium_lib-3.0.2/lib/appium_lib/driver.rb:158:inblock (3 levels) in promote_singleton_appium_methods'
/usr/local/lib/node_modules/appium/appium/submodules/ApiDemos/tutorial/projects/ruby_android/appium/android/pages/home.rb:32:in assert' /usr/local/lib/node_modules/appium/appium/submodules/ApiDemos/tutorial/projects/ruby_android/appium/android/pages/home.rb:9:inaccessibility_click'
/usr/local/lib/node_modules/appium/appium/submodules/ApiDemos/tutorial/projects/ruby_android/appium/android/specs/test.rb:6:in `block (2 levels) in '

1 runs, 0 assertions, 0 failures, 1 errors, 0 skips
delete
Understand this is a failure to locate the element. This is built from the tutorial. What needs to be updated?

@jraczak Have a look at referenced PR that fixes Ruby tests.

Does bundle exec rake android[test] fail?

Yes, bundle exec rake android[test] will also fail.

fixed by https://github.com/appium/tutorial/issues/22

This works beautifully now. Thanks so much @JaniJegoroff for pushing this through so fast and @bootstraponline for the quick merge.

@jraczak Awesome, happy testing! :)

authors: JaniJegoroff bootstraponline jraczak

repo: appium/tutorial


text:
Error loading package from remote URI

Not sure if this is a bug, or if I missed a setting somewhere. I have a Pkl project that loads from a remote package, and pkl eval works fine. But when I do the equivalent thing from my Go code, I get this error:
error packaging template 'bucket.pkl': –– Pkl Error ––
Cannot import dependency because there is no project found.

If you meant to import a path that starts with `@`, prefix the path with `./` (e.g. `import "./@myPath").
If you meant to import a dependency, ensure that this file is within a directory that contains a PklProject module.

1 | amends "@cfn/template.pkl"
           ^^^^^^^^^^^^^^^^^^^
at bucket (file:///Users/ezbeard/Source/Cfn/try/try-guard/bucket.pkl)

The code that does this is here.
Options I'm using:
var EvaluatorOptionsFunc = func(opts *pkl.EvaluatorOptions) {
	pkl.WithDefaultAllowedResources(opts)
	pkl.WithOsEnv(opts)
	pkl.WithDefaultAllowedModules(opts)
	pkl.WithDefaultCacheDir(opts)
	opts.Logger = pkl.NoopLogger
	opts.OutputFormat = "yaml"
}

Also note that if I load local packages, the Go code works fine. It's only when I have a PklProject with a remote URI.

You need to construct an evaluator that understands your project, using NewProjectEvaluator.

In the same context, or maybe it is a different issue. I tried to the tool in the context of my company, but I think that with the lack of support for proxy settings, I'm not able to run it properly and fetch external packages. Do we have a plan to support Proxy Settings going forward already in the roadmap?

Although, yes, this is a very different issue, proxying is now supported (in 0.26.0), @francknouama.
Closing this, presuming it was addressed (please feel free to re-open if not-so, @ericzbeard)

source: gharchive/issue

authors: bioball ericzbeard francknouama holzensp

repo: apple/pkl-go

license_type: permissive

license_source: github-api


text:
build: clean up build and enable Windows

Setup the build for targeting Windows.  This cleans up the configuration
by unifying the behaviour for FreeBSD and other non-Darwin unices.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

source: gharchive/pull-request

repo: apple/swift-corelibs-foundation


text:
Don't use #import when #include will do

This changes a few #import statements to #include. This is because Clang's MSVC compatibility does not handle #import statements outside of of objc.
#import of type library is an unsupported Microsoft feature

@swift-ci please smoke test

@swift-ci Please test

@swift-ci please test

authors: kastiglione modocache


text:
Fix the layout calculation of generic tuple types.

Performing dynamic type resolution on a tuple type can actually change
the tuple's layout, so when computing the offsets of a tuple's
elements, we need to use the static (but archetype-bound) type instead
of the dynamic type.
This patch requires a matching commit in the Swift compiler.
rdar://problem/45462765

test with https://github.com/apple/swift/pull/20815
@swift-ci test

repo: apple/swift-lldb

license_source: bigquery


text:
[WIP] Implement SE-209 Swift Language Version API Update

This is the main implementation of the proposal. It adds a new runtime
and the proposed API changes.
rdar://problem/38721967 Provide support for Swift 4.2 in SwiftPM
https://bugs.swift.org/browse/SR-7464

@swift-ci please smoke test

repo: apple/swift-package-manager


text:
[5.6] Add module kind enum to the package plugin API

SwfitPM 5.6 nomination of #4098.
Although the different basic kinds of targets were expressed through types, the module kind (executable, test, or regular) for a source module target was not expressed in the API.  This adds that property.
rdar://86786080
(cherry picked from commit b7c299105592451cde264b3965aa41f0bbc3c3fc)

@swift-ci please test

@swift-ci please test

@swift-ci please test


text:
Fix testImportRestrictions

Landed two PRs at the same time which lead to the unexpected interaction of Foundation now showing up in the list of imported modules for tools-version 5.7 and earlier.

@swift-ci please smoke test


text:
Fix unhelpful -help message

Fixes #7218
Fix the unhelpful dialogue when invoking swift package -help
Motivation:
swift package -help is documented as a valid spelling. So it should work
Modifications:
Specifically detect -help in the argument
Result:
swift package -help prints the help message

I feel like we should be able to handle this on ArgumentParser level, thus requesting relevant reviewers

authors: AndrewHoos MaxDesiatov


text:
Exclude XCBuildSupport when building with CMake

XCBuildSupport is not available on non-Darwin platforms, especially Windows, where we have to have full CMake support at the moment. Maintaining XCBuildSupport in these unsupported configurations adds unnecessary overhead, especially in cases like https://github.com/apple/swift-package-manager/pull/7258, where we have to add new dependencies only when XCBuildSupport is available. We should exclude from CMake builds to reduce this maintenance overhead.

@swift-ci test

@swift-ci test windows

@swift-ci test windows

@swift-ci test windows

We should exclude from CMake builds to reduce this maintenance overhead.

Don't we bootstrap with CMake today? The toolchain builds are blocked because we end up hitting the error in Sources/swift-bootstrap/main.swift 😅.

authors: MaxDesiatov bnbarham


text:
[Utility] Add -help option to print usage

We now support -h, -help and --help to print usage.

https://bugs.swift.org/browse/SR-4121

@swift-ci please smoke test


text:
Introduce a SyntaxRawRewriter that is more performant than SyntaxRewriter

SyntaxRawRewriter is pretty much equivalent to SyntaxRewriter but the visit methods return raw syntax nodes, which makes SyntaxRawRewriter more performant than SyntaxRewriter.
The motivation for this is that BasicFormat needs to be written in terms of SyntaxRawRewriter to get it to an acceptable performance level.

@swift-ci Please test

Thinking about this again, I realized that this performance optimization isn’t actually necessary, https://github.com/apple/swift-syntax/pull/977 is sufficient to get acceptable performance.

repo: apple/swift-syntax


text:
Async/await: slow in certain combinations

Describe the bug
Without suspension happening,  asynchronous calls should be about as fast as synchronous calls. But this is not always the case.
Steps To Reproduce
Steps to reproduce the behavior:

Run the Swift package https://github.com/stefanspringer1/AsyncBenchmark.

Expected behavior
Without suspension happening,  asynchronous calls should be about as fast as synchronous calls.
What happens instead
But in certain circumstances, more precisely for the last three runs in the example, the factor is much higher, up to more than 6000. (In debug mode, only the last number is much higher than 1, it is 22).
Profile data
Attached:
profile.trace.zip
Program output (release):

--------------------------

100000 iterations
Evaluating: Execution...
Time for Execution: 0.0001037 seconds
Evaluating: AsyncExecution...
Time for AsyncExecution: 0.0001041 seconds
100000 iterations done
factor: 1.0040209
difference: 0.0000004

--------------------------

10000 iterations
Evaluating: Execution...
Time for Execution: 0.0000105 seconds
Evaluating: AsyncExecution...
Time for AsyncExecution: 0.0000105 seconds
10000 iterations done
factor: 0.9960952
difference: -0.0000000

--------------------------

1000 iterations
Evaluating: Execution...
Time for Execution: 0.0000011 seconds
Evaluating: AsyncExecution...
Time for AsyncExecution: 0.0000010 seconds
1000 iterations done
factor: 0.9603321
difference: -0.0000000

--------------------------

100 iterations
Evaluating: Execution...
Time for Execution: 0.0000001 seconds
Evaluating: AsyncExecution...
Time for AsyncExecution: 0.0000001 seconds
100 iterations done
factor: 0.6640000
difference: -0.0000000

--- directly in main 1 ---

100000 iterations
Evaluating: Execution...
Time for Execution: 0.0000516 seconds
Evaluating: AsyncExecution...
Time for AsyncExecution: 0.0119533 seconds
100000 iterations done
factor: 231.5407651
difference: 0.0119017

===== NON-ASYNC WORK =====

--------------------------

100000 iterations
Evaluating: Execution...
Time for Execution: 0.0000838 seconds
Evaluating: AsyncExecution...
Time for AsyncExecution: 0.0035407 seconds
100000 iterations done
factor: 42.2342486
difference: 0.0034568

--- directly in main 2 ---

100000 iterations
Evaluating: Execution...
Time for Execution: 0.0000419 seconds
Evaluating: AsyncExecution...
Time for AsyncExecution: 0.4371535 seconds
100000 iterations done
factor: 10429.0254312
difference: 0.4371115
Program ended with exit code: 0

Environment (please fill out the following information)

OS: macOS 12.5
Xcode Version/Tag/Branch: 13.4.1
Swift: 5.6.1

Additional context
Add any other context about the problem here.

Also See Forum topic https://forums.swift.org/t/async-await-slow-in-certain-combinations/59497/3.

repo: apple/swift


text:
Ubuntu 23.04 + Swift 5.8: Fails to compile bootstrap1 modules due to possible module map issues with CXX interop

Description
Ubuntu 23.04 + Swift 5.8: Fails to compile bootstrap1 modules due to possible module map issues with CXX interop
When compiling Swift from source with --bootstrapping=bootstrapping, compilation fails during generation of modules. Specifically on the Basic module.
Steps to reproduce

Download Ubuntu 23.04, which is currently in beta but also in feature freeze so its ABI stable at this point.
Install Swift dependencies as listed in the documentation
Construct a swift source root by running:
./swift/utils/update-checkout --clone --tag swift-5.8-RELEASE
Invoke the build-script as follows:

export SCCACHE_CACHE_SIZE="50G" && ./swift/utils/build-script -R --swift-install-components="autolink-driver;compiler;clang-resource-dir-symlink;stdlib;swift-remote-mirror;sdk-overlay;static-mirror-lib;toolchain-tools;license;sourcekit-inproc" --llvm-install-components="llvm-ar;llvm-cov;llvm-profdata;IndexStore;clang;clang-resource-headers;compiler-rt;clangd;lld;LTO;clang-features-file" --lldb --build-lld=1 --build-ninja=1 --llbuild=1 --libcxx=1 --swiftpm=1 --foundation=1 --libdispatch=1 --indexstore-db=1 --libicu=1 --install-swiftpm=1 --build-swift-static-stdlib --build-swift-static-sdk-overlay --install-llvm=1 --install-swift=1 --install-foundation --install-libdispatch --swiftdocc=1 -j=8 --sccache=1 --skip-test-linux=1 --skip-build-benchmarks --skip-early-swift-driver --skip-early-swiftsyntax --bootstrapping=bootstrapping --install-destdir=/home/jjones/swift-install

Expected behavior
Bootstrap compilation should succeed, however a failure occurs when swiftc is invoked and has to deal with cxx-interop.
Build Failure
[1216/1439][ 84%][321.279s] Building swift module Basic
FAILED: bootstrapping1/SwiftCompilerSources/Basic.o /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/swift-linux-x86_64/bootstrapping1/SwiftCompilerSources/Basic.o
cd /home/jjones/swift-source-root/swift/SwiftCompilerSources && /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/swift-linux-x86_64/bootstrapping0/bin/swiftc -c -o /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/swift-linux-x86_64/bootstrapping1/SwiftCompilerSources/Basic.o -I /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/swift-linux-x86_64/bootstrapping0/bin/../lib -I /usr/lib -target x86_64-unknown-linux-gnu -module-name Basic -emit-module -emit-module-path /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/swift-linux-x86_64/bootstrapping1/SwiftCompilerSources/Basic.swiftmodule -parse-as-library /home/jjones/swift-source-root/swift/SwiftCompilerSources/Sources/Basic/SourceLoc.swift /home/jjones/swift-source-root/swift/SwiftCompilerSources/Sources/Basic/Utils.swift -wmo -Xfrontend -validate-tbd-against-ir=none -Xfrontend -enable-experimental-cxx-interop -Xcc -UIBOutlet -Xcc -UIBAction -Xcc -UIBInspectable -Xfrontend -disable-implicit-string-processing-module-import -O -cross-module-optimization -Xcc -I -Xcc /home/jjones/swift-source-root/llvm-project/llvm/include -Xcc -I -Xcc /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/llvm-linux-x86_64/include -Xcc -I -Xcc /home/jjones/swift-source-root/llvm-project/clang/include -Xcc -I -Xcc /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/llvm-linux-x86_64/tools/clang/include -Xcc -I -Xcc /home/jjones/swift-source-root/swift/include -Xcc -I -Xcc /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/swift-linux-x86_64/SwiftCompilerSources/../include -I /home/jjones/swift-source-root/build/Ninja-ReleaseAssert/swift-linux-x86_64/bootstrapping1/SwiftCompilerSources
<unknown>:0: warning: unable to perform implicit import of "_Concurrency" module: no such module found
/home/jjones/swift-source-root/swift/include/swift/AST/ClangModuleLoader.h:19:10: note: while building module 'Clang_AST' imported from /home/jjones/swift-source-root/swift/include/swift/AST/ClangModuleLoader.h:19:
#include "clang/AST/DeclTemplate.h"
         ^
/home/jjones/swift-source-root/llvm-project/clang/include/clang/AST/APValue.h:16:10: note: while building module 'Clang_Basic' imported from /home/jjones/swift-source-root/llvm-project/clang/include/clang/AST/APValue.h:16:
#include "clang/Basic/LLVM.h"
         ^
/home/jjones/swift-source-root/llvm-project/clang/include/clang/Basic/Sanitizers.h:20:10: note: while building module 'LLVM_Transforms' imported from /home/jjones/swift-source-root/llvm-project/clang/include/clang/Basic/Sanitizers.h:20:
#include "llvm/Transforms/Instrumentation/AddressSanitizerOptions.h"
         ^
/home/jjones/swift-source-root/llvm-project/llvm/include/llvm/Transforms/AggressiveInstCombine/AggressiveInstCombine.h:20:10: note: while building module 'LLVM_intrinsic_gen' imported from /home/jjones/swift-source-root/llvm-project/llvm/include/llvm/Transforms/AggressiveInstCombine/AggressiveInstCombine.h:20:
#include "llvm/IR/PassManager.h"
         ^
<module-includes>:1:10: note: in file included from <module-includes>:1:
#include "IR/Argument.h"
         ^
/home/jjones/swift-source-root/llvm-project/llvm/include/llvm/IR/Argument.h:17:10: note: in file included from /home/jjones/swift-source-root/llvm-project/llvm/include/llvm/IR/Argument.h:17:
#include "llvm/IR/Attributes.h"
         ^
/home/jjones/swift-source-root/llvm-project/llvm/include/llvm/IR/Attributes.h:31:10: note: in file included from /home/jjones/swift-source-root/llvm-project/llvm/include/llvm/IR/Attributes.h:31:
#include <set>
         ^
/usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/set:60:10: note: in file included from /usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/set:60:
#include <bits/stl_tree.h>
         ^
/usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/bits/stl_tree.h:2008:5: error: missing '#include "gcc/x86_64-linux-gnu/12/../../../../include/c++/12/bits/stl_pair.h"'; 'pair' must be declared before it is used
    pair<typename _Rb_tree<_Key, _Val, _KeyOfValue,
    ^
/usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/bits/stl_pair.h:185:12: note: declaration here is not visible
    struct pair

Environment

Swift compiler: swift-5.8-RELEASE
OS: Ubuntu 23.04

The full build-log is attached.
swift_build_failure.txt

Looks similar to an issue occurring on a recent Fedora distribution as well:
https://www.spinics.net/lists/fedora-devel/msg310864.html

I see similar issues on Ubuntu 20.04, but can you first make sure that all package dependencies are installed? I know you listed it in your steps, but if you missed something, it may cause this.

@futurejones, I see you just released builds for Ubuntu 23.04, any idea how to fix these build issues we're seeing on Ubuntu?

Thanks @futurejones, maybe that's it, @jaredjones, as I'm building with one of the latest CMake releases, 3.26.1. I will try downgrading to what the linux CI is using and see if that makes a difference, you should try that too.

Looks like some folks upgrading to a Fedora rawhide are experiencing similar issues.
I bet this specifically only occurs on upgrade installs, not clean installs.
https://github.com/tachoknight/swift-lang-packaging-fedora/issues/2

Yep, that's it, the problem goes away after downgrading to CMake 3.19.6. I'll look into what flags recent CMake is adding that causes these build issues.

I can also confirm that downgrading cmake has resolved this issue.

Checked the failing command, it is identical between the two CMake versions. This implies some other build input is being generated differently based on the CMake version, will dig deeper.

Narrowed it down further: built LLVM with CMake 3.26.1 and then built the Swift compiler first with CMake 3.26.1, then wiped it and built with 3.19.6 and now could reproduce the problem with both, so it looks like the issue is in some LLVM file generated by CMake.
I think this may be what caused my similar problems on Android in #60272 too, will look into it more.

For what it's worth, I'm also seeing this packaging Swift 5.8 in NixOS. CMake 3.24.3 works, while 3.25.3 doesn't. (I'm not sure if it was already established this was a CMake >=3.25 issue. I wanted to narrow the range.)
I tried to diff the result of the configure step for LLVM between the two CMake versions, but nothing really stands out. (But I'm no expert.)

Thanks, @stephank, I suspect some modulemap is generated differently between the two CMake versions, but I've had to put investigating this CMake issue further on the back burner while dealing with more important things. I tried downgrading the CMake used for my Android build, but it made no difference there, so that is a different C++ Interop error.
@compnerd or @stevapple, have you guys seen this issue with recent CMake on Windows too?

It looks like the modulemap is completely missing, and build.ninje doesn't have any of the rules for it. So something about the way stdlib/public/Cxx/std/CMakeLists.txt is interpreted. I may have some more time to debug this tomorrow.
 #############################################
 # Utility command for libstdcxx-modulemap

-build stdlib/public/Cxx/std/libstdcxx-modulemap: phony stdlib/public/Cxx/std/CMakeFiles/libstdcxx-modulemap stdlib/public/Cxx/std/lib-swift-linux-x86_64-libstdcxx.h stdlib/public/Cxx/std/lib-swift-linux-x86_64-libstdcxx.modulemap
+build stdlib/public/Cxx/std/libstdcxx-modulemap: phony

Found a little time, and:
if(NOT ${sdk} IN_LIST SWIFT_LIBSTDCXX_PLATFORMS)  # current, doesn't work
if(NOT "${sdk}" IN_LIST SWIFT_LIBSTDCXX_PLATFORMS)  # works
if(NOT sdk IN_LIST SWIFT_LIBSTDCXX_PLATFORMS)  # works

But I'm unable to reproduce this in a small test setup, so something is fishy. Seems like it should be something specific to these checks, or it'd be far more widespread.

After sleeping on it, I realized this is simply because LINUX was probably defined somewhere, and because an expression accepts variable|string, how that expression is interpreted depends on what ${sdk} expands to and whether that value happens to match an existing variable name.
As it turns out, CMake defines LINUX=1 as of 3.25: https://github.com/Kitware/CMake/commit/62cd3904bf22fd75a2502af09ef67f8458ce06e1
So the current way we write these expressions is a little ambiguous. Quoting seems to help, and ensures CMake treats it as a string. I do believe we have more broken checks like this; will create a PR.

@jaredjones, would you reopen this and add the CMake version info to the title? Once @stephank submits a fix, he can close it.

See #65534

I'm also experienceing this problem when I tried to make a Swift 5.8 build for Arch Linux aarch64. (I'm using "GNU Make 3.81")

@compnerd FYI I also ran into this issue while building Swift on Exherbo using build-script
I can see there's an open PR for Swift 5.9, I'll try building the main branch then (which has been applied a fix).

authors: Kyle-Ye RemiBardon buttaface jaredjones stephank


text:
Adopt Codable on URLComponents

What's in this pull request?
Adopts Codable on URLComponents and adds relevant unit tests.
Updates the CodableTests infrastructure to more easily show failing tests.

@swift-ci Please test macOS

@swift-ci Please smoke test Linux


text:
Serialization: Fix crash when deserializing store_unowned SIL instruction [4.1]

Description: We would crash in deserialization when deserializing the store_unowned instruction.

Scope of the issue: Now that we preserve SIL when merging modules, there are more ways to trigger this in normal code, but in Swift 4.0 you could hit this by an @inline(__always) function that assigned to an unowned property.

Origination: Bug was present in the original implementation of "new" unowned properties that was added to Swift 3.0.

Risk: Very low, it's a trivial fix.

Tested: New test case added.

Radar: rdar://problem/35980211.

Reviewed by: @jckarter

@swift-ci Please test


text:
Fix SIL.rst

This change has not been applied to the swift-4.2-branch-04-30-2018, and it should.

@najacque can you force merge it, please?


text:
[IRGen] Fix a large-types corner case wherein we have a module without any signature modifications but with callee modifications

Assume we have a module with functions that keep their signatures as-is. And assume we have a method call callee for which we modified the return type to be indirect.
In that case we need to re-create the applies to said callee.
The large loadable types pass had a check that if we did not modify any function signatures, we can exit the module pass early to reduce compile time, that check breaks the situation described above.
This commit changes the early-exit check so that we can skip the rest of of the module pass if we did not change any function signatures AND we did not change any applies.
rdar://problem/40809999

@swift-ci Please smoke test and merge


text:
SR-8925: Require clang-3.9 on Ubuntu 14.04

Since commit 3469797d changed to build libdispatch for SourceKit with the
host compiler, we now require a clang with builtin __builtin_add_overflow.
Since Ubuntu 14 repositories have a clang that supports this update our
build instructions to use it.
Resolves SR-8925.

cc @jrose-apple

Seems reasonable, but possibly something we should have discussed first. cc @najacque, @shahmishal

@jrose-apple @compnerd I'm signing off for the weekend but if this is something that needs discussion then we should probably revert 3469797 to un-break the Ubuntu14 build.

@jrose-apple, I agree with it being nice to announce the minimum versions being updated early, however, 3.9 is over 2 years old at this point.  3.4 is pretty ancient (4+ years old!).  I suppose that we can switch the libdispatch build back to using the just built compiler if this isn't something we can accommodate.

@jrose-apple it looks like CI bots are now using Clang 7.0.0. Are you happy for me to merge this change?

It's a policy question more than a practical question, and someone other than me should decide that project. Maybe it's worth bringing up on the forums?

@kevints Did you ever wind up taking this to evolution?

I suppose it doesn't matter now that we don't support 14.04.  Going to merge at least so anybody trying to build on a legacy target doesn't run into the same bugs,

@swift-ci please smoke test and merge

authors: CodaFi compnerd jrose-apple kevints


text:
[CMake] Add dsymutil to list of unified build test deps

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test and merge

authors: compnerd davezarzycki


text:
[5.1 04/24][Diagnostics] Improve missing conformance diagnostics for opaque return

Description
New diagnostic framework can already identify contextual failures
related to opaque return types, RequirementFailure just needs
to get adjusted to identify correct affected declaration and provide
tailored diagnostic.
Reviewed By: @jckarter
Resolves: rdar://problem/49582531

@swift-ci please test

@swift-ci please test source compatibility

Looks like not all of the projects have been updated to support Swift 5 in source compatibility suite, failures are unrelated to my changes.


text:
Revert "[ClangImporter] Hash content for validation when using clang …

…modules"
This reverts commit c362e925af7ff948be704c55cb4406a05f5d13b7.
This might be causing hard to reproduce issues. Taking it out until
we have further investigation.
rdar://problem/57964637

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test


text:
[AutoDiff upstream] Add SIL differentiability witness serialization.

SIL differentiability witnesses are a new top-level SIL construct mapping
an "original" SIL function and derivative configuration to derivative SIL
functions.
This patch adds SILDifferentiabilityWitness serialization/deserialization.
Resolves TF-1136.

Todos:

TF-1137: upstream SILDifferentiabilityWitness verification.
TF-1138: upstream SILDifferentiabilityWitness SILGen from
@differentiable and @derivative attributes.
TF-20: robust mangling for SILDifferentiabilityWitness names.

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 6482b67f9caaff1dfa0a2ce04015f01025191de2

Build failed
Swift Test OS X Platform
Git Sha - 6482b67f9caaff1dfa0a2ce04015f01025191de2

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 6482b67f9caaff1dfa0a2ce04015f01025191de2

Build failed
Swift Test Linux Platform
Git Sha - 6482b67f9caaff1dfa0a2ce04015f01025191de2

CI failures seem unrelated, maybe they're fixed now.
@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - f6d99b004cc6df35215a26d909c9224d85f6365a

@swift-ci Please test macOS platform

I had to resolve a merge conflict, so tests must be run again.
@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - f6d99b004cc6df35215a26d909c9224d85f6365a

Build failed
Swift Test OS X Platform
Git Sha - f6d99b004cc6df35215a26d909c9224d85f6365a

authors: dan-zheng swift-ci


text:
test: loosen the overly-restrictive test

The types may be emitted in a different order.  Be more permissive about
ordering.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please smoke test

CC: @jckarter


text:
[TF] Change PythonKit deployment target to default.

Change PythonKit deployment target from macOS 10.13 to the default.
This is necessary to work around TF-1252 and should allow us to make
TensorFlow have a lower deployment target too.

I'm building a macOS toolchain with this patch now to verify if it can fix TF-1252. Let's wait for my verification before merging.
Triggering tests in the meantime.

@swift-ci Please test tensorflow

The goal of this patch is to lower the deployment target for TensorFlow. If I remove macOS 10.13 as the deployment target, the default actually becomes macOS 10.14:
tensorflow-swift-apis/Sources/TensorFlow/Core/PythonConversion.swift:17:10: error: compiling for macOS 10.13, but module 'PythonKit' has a minimum deployment target of macOS 10.14: /Users/swiftninjas/s4tf/swift/swift-nightly-install/Library/Developer/Toolchains/swift-tensorflow-DEVELOPMENT-2020-04-29-a.xctoolchain/usr/lib/swift/macosx/PythonKit.swiftmodule/x86_64.swiftmodule
  import PythonKit
         ^

I'll try explicitly setting the deployment target to macOS 10.10, to work around TF-1252.

@swift-ci Please test tensorflow

@swift-ci Please test tensorflow


text:
[CodeCompletion] Update member completion to handle ambiguous and invalid base expressions

This hooks up member completion to the new typeCheckForCodeCompletion API to generate completions from all solutions the constraint solver produces – including ones requiring fixes – rather than relying on a single solution being applied to the AST (if any). This lets us still produce member completion results when the base expression is ambiguous or invalid.
Whenever typeCheckExpression is called on an expression containing a code completion expression and a CompletionCallback has been set, each solution formed is passed to the callback so the type and decl of the base expression can be extracted along with any other info needed to generate member completions.

@swift-ci please test

@swift-ci Please Build Toolchain macOS Platform

/cc @hborla @DougGregor

macOS Toolchain
Download Toolchain
Git Sha - 491b691dbce23fe0896e835c4a36202b4bcf8935
Install command
tar -zxf  swift-PR-33749-669-osx.tar.gz --directory ~/

Build failed
Swift Test OS X Platform
Git Sha - 491b691dbce23fe0896e835c4a36202b4bcf8935

@swift-ci please test macOS platform

Toolchain https://ci.swift.org/job/swift-PR-toolchain-osx/677/artifact/branch-master/swift-PR-33749-677-osx.tar.gz

@swift-ci clean test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - d60116d11a7049a051b350b98057f05ebdda1727

Build failed
Swift Test OS X Platform
Git Sha - d60116d11a7049a051b350b98057f05ebdda1727

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 7a06792e5df8705f1a2005f0c0a04069ebb1c1ed

Build failed
Swift Test Linux Platform
Git Sha - 7a06792e5df8705f1a2005f0c0a04069ebb1c1ed

@swift-ci please test Linux

authors: nathawes rintaro swift-ci xedin


text:
C++ Interop: import namespaces redecls as separate extensions

Previously a namespace declaration was imported along with all of its redeclarations, and their members were added to a single Swift extension. This was problematic when a single namespace is declared in multiple modules – the extension belonged to only one of them.
For an example of this, try printing a module interface for std.string/std.iosfwd – it will be empty, even though the declarations from those modules are actually imported into Swift correctly.
This change makes sure that when we're importing different redeclarations of the same namespace, we're adding them as separate extensions to appropriate modules.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test Windows

@swift-ci please test Windows

@swift-ci please smoke test

Looks like macos is having an unrelated problem. Let's try again.
@swift-ci please smoke test macOS platform.

@swift-ci please smoke test macOS platform.

@swift-ci please smoke test

@swift-ci please test Windows

@swift-ci please smoke test macOS

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test Windows

@swift-ci please smoke test Linux

@swift-ci please smoke test Linux

Thanks for reviewing this @zoecarver!

@egorzhdan @zoecarver Is it possible this change causes ASAN failures?
ASAN test started failing in https://ci.swift.org/job/oss-swift-incremental-ASAN-RA-macos/5835/changes

@rintaro that would seem a bit odd to me. The test that's failing doesn't seem to touch namespaces whatsoever. That being said, this patch did touch the clang importer more generally, so it is possible that it broke that test.
Maybe we should put up a PR to revert this change and see if that fixes the bots? Side note: I'm almost done with a patch that would undo many of the more general clang importer changes and moves the namespace importing logic elsewhere, if this patch is the culprit, I suspect my change will fix it. So, if that is the case, let's revert the patch and I can submit something later that will probably not have the same issues.

For future readers, here's the Jenkins output (so that you don't have to dig through the huge text file)

******************** TEST 'Swift(macosx-x86_64) :: Interpreter/SDK/weak_objc_interop.swift' FAILED ********************
Script:
--
: 'RUN: at line 1';   rm -rf "/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp" && mkdir -p "/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp"
: 'RUN: at line 3';   cp /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift/test/Interpreter/SDK/weak_objc_interop.swift /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp/main.swift
: 'RUN: at line 4';   xcrun --toolchain default --sdk '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk' clang++ -target x86_64-apple-macosx10.9 -fmodules-cache-path='/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/swift-test-results/x86_64-apple-macosx10.9/clang-module-cache' -fno-objc-arc /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift/test/Interpreter/SDK/Inputs/ObjCWeak/ObjCWeak.m -c -o /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp/ObjCWeak.o
: 'RUN: at line 5';   xcrun --toolchain default --sdk '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.1.sdk' /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/bin/swiftc -target x86_64-apple-macosx10.9  -module-cache-path /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/swift-test-results/x86_64-apple-macosx10.9/clang-module-cache  -F '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks' -toolchain-stdlib-rpath -Xlinker -rpath -Xlinker '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks' -Xlinker -rpath -Xlinker /usr/lib/swift -Xlinker -headerpad_max_install_names  -swift-version 4  -Xfrontend -define-availability -Xfrontend 'SwiftStdlib 5.5:macOS 12.0, iOS 15.0, watchOS 8.0, tvOS 15.0'  -F '/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/lib' -Xlinker -rpath -Xlinker '/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/lib' /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp/main.swift -I /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift/test/Interpreter/SDK/Inputs/ObjCWeak/ -Xlinker /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp/ObjCWeak.o -o /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp/weak_objc_interop -Xfrontend -disable-access-control
: 'RUN: at line 6';   /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift/utils/swift-darwin-postprocess.py /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp/weak_objc_interop
: 'RUN: at line 7';   /usr/bin/env DYLD_LIBRARY_PATH='/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/lib/swift/macosx' LD_LIBRARY_PATH='/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/lib/swift/macosx:' SIMCTL_CHILD_DYLD_LIBRARY_PATH='/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/lib/swift/macosx'  /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64/test-macosx-x86_64/Interpreter/SDK/Output/weak_objc_interop.swift.tmp/weak_objc_interop 2>&1 | /Applications/Xcode.app/Contents/Developer/usr/bin/python3 /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift/utils/PathSanitizingFileCheck --sanitize BUILD_DIR=/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/swift-macosx-x86_64 --sanitize SOURCE_DIR=/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift --use-filecheck /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/buildbot_incremental_asan/llvm-macosx-x86_64/bin/FileCheck  /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift/test/Interpreter/SDK/weak_objc_interop.swift
--
Exit Code: 1
Command Output (stderr):
/Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift/test/Interpreter/SDK/weak_objc_interop.swift:28:16: error: CHECK-NEXT: expected string not found in input
// CHECK-NEXT: Gone
^
:4:1: note: scanning from here
AddressSanitizer:DEADLYSIGNAL
^
:8:39: note: possible intended match here
#0 0x7fff6e9c9840 in objc_loadWeakRetained+0xa2 (libobjc.A.dylib:x86_64h+0xd840)
^
Input file:
Check file: /Volumes/swift-ci/jenkins/workspace/oss-swift-incremental-ASAN-RA-macos/swift/test/Interpreter/SDK/weak_objc_interop.swift
-dump-input=help explains the following input dump.
Input was:
<<<<<<
1: before giving up strong reference:
2: Swift Object
3: after giving up strong reference:
4: AddressSanitizer:DEADLYSIGNAL
next:28'0     X~~~~~~~~~~~~~~~~~~~~~~~~~~~~ error: no match found
5: =================================================================
next:28'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6: ==1632==ERROR: AddressSanitizer: SEGV on unknown address 0x000013800020 (pc 0x7fff6e9c9840 bp 0x7ffeec461600 sp 0x7ffeec4615d0 T0)
next:28'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7: ==1632==The signal is caused by a READ memory access.
next:28'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
8:  #0 0x7fff6e9c9840 in objc_loadWeakRetained+0xa2 (libobjc.A.dylib:x86_64h+0xd840)
next:28'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next:28'1                                           ?                                           possible intended match
9:  #1 0x7fff6e9cb67b in objc_loadWeak+0xe (libobjc.A.dylib:x86_64h+0xf67b)
next:28'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10:  #2 0x1037a898c in tryWeakReferencing+0x1cc (weak_objc_interop:x86_64+0x10000a98c)
next:28'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11:  #3 0x1037a505e in main+0x5e (weak_objc_interop:x86_64+0x10000705e)
next:28'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
12:  #4 0x7fff6fb77cc8 in start+0x0 (libdyld.dylib:x86_64+0x1acc8)
next:28'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
13:
next:28'0     ~
.
.
.

--

I think https://github.com/apple/swift/commit/3372ab7a397960d8828749beba96fcebd60d0f05 is a more likely reason of the ASAN failure, since it touches ObjC closures & ManagedValues.
If the CI run proves me wrong, I'll be ready to investigate further.

Thank you for looking into this @egorzhdan ! I just put up another PR for testing https://github.com/apple/swift/commit/3372ab7a397960d8828749beba96fcebd60d0f05 revert.

Also started building with ASAN locally. Because if 3372ab7 is the reason, the failure is flaky, so we need to run the test multiple times.

Unfortunately, an ASAN PR test without any change https://ci.swift.org/job/swift-PR-macos-ASAN-test/229/console just passed Interpreter/SDK/weak_objc_interop.swift test 😢 So probably this test is indeed flaky. Hope I can reproduce the failure locally.

https://ci.swift.org/job/oss-swift-incremental-ASAN-RA-macos/
So the ASAN bot succeeded 2 times in a row. Now I think the failure was a transient. Sorry for the hassle!

Alright, thanks for the update @rintaro!

authors: egorzhdan rintaro zoecarver


text:
[WIP] Protocol conformance decoder

Add support for protocol conformance demangling.
rdar://46280860

Cool!


text:
SR 716: handle constant structs with padding

Handle padding in global structs.
Previously there was a mismatch between SIL's concept of a
struct (padding is implicit) and LLVM's (padding is explicit) in IRGen's
constant evaluator. The explicit padding fields need to be given a value
in the IR.

Resolves SR-716.

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 5aa6d8bc6b0d10dae9146cf37e900a09cc40abe3
Test requested by - @huonw

@huonw I noticed that @rjmccall made some comments about formatting. You should check out git-clang-format. It solves these issues really nicely. I can show you how to set it up on Monday if you want.

@swift-ci please test
I've updated the pull request, which should address the review. It restructures things in the vein of @rjmccall's suggestion of doing two passes over an array of llvm::Constant *, although the only way to get the stored properties that I can see result in some weirdness with the closure in emitConstantStruct.
It is also git-clang-format clean, so the formatting should be good now. (Thanks @gottesmm for pointing me to that script, I think I've got it setup in an appropriate way.)

@swift-ci please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 5aa6d8bc6b0d10dae9146cf37e900a09cc40abe3
Test requested by - @huonw

@huonw This looks great! One request from me would be to add an IRGen FileCheck test.

I... don't know what that test failure means. It doesn't seem to be in any code I touched, and running the validation tests locally (-T, right?) passes fine.

@swift-ci Please test
I added a IRGen test (test/IRGen/constant_struct_with_padding.sil), tell me if it looks reasonable please, @slavapestov.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test.
Updated.

@swift-ci Please test.
Updated.

@swift-ci Please test

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 9246b1ead46eb071b1cb91754f776ecca66d9185
Test requested by - @huonw

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 9246b1ead46eb071b1cb91754f776ecca66d9185
Test requested by - @huonw

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 642117b5511276c2da8ea64e36bac8ed30ff9572
Test requested by - @huonw

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 642117b5511276c2da8ea64e36bac8ed30ff9572
Test requested by - @huonw

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 642117b5511276c2da8ea64e36bac8ed30ff9572
Test requested by - @huonw

@moiseev, @phausler, know what's up with the macOS failure? Why would we lose the length property all of a sudden?
12:35:14 2016-10-03 12:34:08.112 swift[56714:13650955] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -length only defined for abstract class.  Define -[_TtCs19_NSContiguousString length]!'

@jrose-apple That failure does not make any sense to me. I verified that @objc for a property will be properly generated for an abstract object being passed. So something else must be at play here. I guess I can move it back into the standard lib instead of the overlay (but that seems sub-par)

Ah, you did land that change. I thought that hadn't happened yet. In that case the problem is that SwiftPM doesn't depend on Foundation, so the overlay is never loaded.

*sigh* I was thinking it made sense to move the fast-path operations, not length itself, but of course the fast-path operations are still useful even without the overlay. My bad.

I would have preferred for the string bridge to live in Foundation entirely. Perhaps we should consider making it only operate when Foundation is imported. That would be a breaking change but I think it would be highly desirable to not get spooky behavior differentials like this failure.
IMHO swiftpm should be importing Foundation if it is relying on the bridge.

(taking this to swift-dev to stop bothering @huonw)

Hang on, this really shouldn't be related to #5071 because that hasn't landed yet.

@jrose-apple are we getting build cruft interceding between builds somehow?

I sure hope not. I see a lot of "reset --hard" and "clean -f" in that build log. But even then I agree with you: the change to a property shouldn't make any difference.

@swift-ci Please test

authors: gottesmm huonw jrose-apple phausler slavapestov swift-ci


text:
[test] UnicodeScalarProperties: Disable when Unicode data files aren’t available

To reenable, the test needs to be configured to upload these files to the remote machine that executes the tests.
(cherry picked from commit ffab0c541f56cd7fd1a79b16a14a2627bb57b82d)

Explanation: This cherry picks a configuration change to a Standard Library test that resolves a CI blocker on the 5.7 branch by partially disabling a particular test that only supports running on the build host. It contains no code changes.

Scope: Stdlib tests

Issue: rdar://99716393

Risk: Minimal

Testing: Device/back deployment CI testing on main in https://github.com/apple/swift/pull/60713.

Reviewer: @Azoy

@swift-ci test


text:
[cxx-interop] Add base classes as opaque fields when lowering in IRGen.

Much of IRGen is built around fields (example: enum packing/unpacking). This is a simpler/less bug-prone way to do it. Fixes rdar://100093641 and rdar://100093806

@swift-ci please test.

Doesn't this also need a non-executable IRGen test? Otherwise LG.

authors: hyp zoecarver


text:
SwiftCompilerSources: force the -static flag

These libraries are built statically for static linking.  SPM currently does not support libraries, and this will ensure that we properly build the library target for consumption into the compiler.

@swift-ci please smoke test

@swift-ci please clean test Windows platform

@swift-ci please test Windows platform


text:
[embedded] Trim expected dependencies of Embedded Swift Concurrency after deployment target raise

Now that we have raised the deployment target on the Embedded Swift standard library for macOS (https://github.com/apple/swift/pull/72716), several dependencies are now gone from the Swift Concurrency runtime. Let's remove them from test/embedded/dependencies-concurrency.swift.

@swift-ci please test


text:
Changes padding for first five pooling layers TF OD

fixes #2616
Passes all unit tests after the change (python and cpp)

Oh and for cpp, the sixth pooling layer has an argument set_avgpoolexcludepadding = true, which might suggests that this layer is average pooling layer instead of max pooling layer:
https://github.com/apple/coremltools/blob/7f2b314f496072320e1088ad8c6f6f572063c454/coremltools/models/neural_network/builder.py#L1824
So maybe we want to use tf.nn.avg_pooling here instead @nickjong .

@jakesabathia2 Good catch. I will make changes to accommodate it.

repo: apple/turicreate


text:
Add support for grayscale PNG textures

appleseed reports "unsupported file format" when using gray scale png textures.
It doesn't affect textures used in OSL shaders (those are handled by OpenImageIO).
Reported by Pierre.

Has there been any progress toward support for grayscale textures?  I just realized this recently when I started using Substance Designer, and I realized all my grayscale maps have to converted before using them in appleseed.

Has there been any progress toward support for grayscale textures?

I don't think anyone is working on this now.

I just realized this recently when I started using Substance Designer, and I realized all my grayscale maps have to converted before using them in appleseed.

You can use the maketx program included with appleseed to convert your textures to linear, tiled, mipmapped EXR files.
I do not recommend using PNG for textures in any case. They are sRGB (the renderer expects linear) and do not support tiles or mipmaps (are not efficient to render).

I tried running maketx and maketiledexr on my grayscale PNGs, and I get errors with both.  I get the same unsupported file format error trying maketiledexr, and a "TIFFFileWrite failed" error when trying to run maketx on them.  Do I need to pass any specific options to maketx to get it to work?

maketiledexr is part of appleseed and uses the same code. It has the same problem with grayscale PNGs. We should probably get rid of it at some point.
I'm not sure about the TIFFWriteTile failed error. It does not happen on linux in my computer.
Try generating exr files, something like this:
maketx --colorconvert sRGB linear -d half input.png -o output.exr

That did the trick, thanks!

I think EXRs are better suited for textures instead of tiff.
You can store 16 bits floating point pixels and they usually compress better.
Some more useful maketx flags:
--constant-color-detect    Create 1-tile textures from constant color inputs
--monochrome-detect      Create 1-channel textures from monochrome input
--opaque-detect               Drop alpha channel that is always 1.0

The unfortunate truth is that we'll probably want to natively support grayscale PNG files, as well as really ill-suited texture formats such as BMP or JPEG. It's rather low priority, but eventually supporting these formats natively (and/or converting all textures automatically to OpenEXR) will make appleseed less cumbersome to use.

Discussion here: https://groups.google.com/forum/#!topic/appleseed-dev/01xronI1K5k

authors: dictoon est77 ohsnapitsjoel

repo: appleseedhq/appleseed

license: mit


text:
Update Readme with information about update

AS described

@VladSumtsov Good idea :+1:

repo: applicaster/react-native-svg

license: MIT


text:
Appodeal SDK Manager Window - don't open (v3.0.1)

Step 1: Environment

Computer OS: Windows
Unity Editor Version: 2020.3.38f1
Appodeal Unity Plugin Version: 3.0.1
Bug Repro Rate: 100%

Step 2: Describe the bug
Appodeal SDK Manager Window - is empty.
Step 3: How to reproduce
Try to open Appodeal SDK Manager from Menu Appodeal > Plugin Configuration
Step 4: Expected behavior
Appodeal SDK Manager open correctly
Step 5: Screenshots

Step 6: Additional context
This page on your FAQ - don't opened as expected

Hi, @Bonbeart!
This is not a bug but expected behavior (the same applies to #5). The 3.0.1 version of the Appodeal Unity Plugin hasn't yet been released. We cannot guarantee that everything works there. By design, the SDK manager doesn't show any dependencies for non-existing SDK/Plugin versions.
As for the FAQ article, it was hidden by my request. It was misleading users by suggesting to install the in-development version. You faced the unstable work of this version yourself(#4, #5).
The public release of v3.0.1 is planned for the nearest future. I'd recommend you wait for it or use the previous version for now.
Best Regards,

As for the FAQ article, it was hidden by my request

This article has not been removed from the FAQ, it is simply not accessible, which is even more misleading.

Thanks, I have forwarded this information to the team.

authors: Bonbeart DmitriiFeshchenko

repo: appodeal/appodeal-unity-plugin-upm


text:
[Bug]: Audio blob url shows undefined for audio recorder widget when trying to access

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When I record a new audio using the audio recorder widget, the blobURL shows empty when trying to bind in a query or other widgets.
Steps To Reproduce

Drag a new audio widget
Record and save the audio
Use {{.blobURL}} in a query or text widget to see that the value is shown as empty
Use {{}} to see the full parameters supported and see the blobURL parameter has value

Environment
Production
Version
Cloud

Autocompletion shows wrong hint. It should be blobURL instead of blobUrl .  Fixed here

authors: dilippitchika ohansFavour

repo: appsmithorg/appsmith


text:
[Task] maps widget tasks

While debugging maps infinite loading issue #1833, we found that the library is no longer maintained
https://github.com/tomchentw/react-google-maps/issues/1038
SubTasks

[ ] ~Find a stable alternative.~
[ ] Decide how to deal with widget interaction vs underlying map interaction.
[x] Ask about the create marker flow and fix/implement that.
[x] Switch over to functional component design.
[x] use useScript for loading the map.

We've decided not to replace the npm package for now.
We'll come back to this before upgrading to react 17.
I'll open another broader issue to discuss canvas vs widget interaction.


text:
[Bug] [Table Widget] Selected Row not getting reset when the table data changes

Description
If a table already has a row selected and if the data changes, the previous row index still shows selected. We should be clearing out selected row if table data has changed

@hetunandu Can you add the steps for this?

Steps to reproduce:

Run a query that only returns one row
Select the one row
Re-run the query with different input so that replaces the one data row content
The row remains selected so no way to select the new row and trigger any associated handlers

This is quite a common scenario for me so definitely looking forward to this being fixed, thx!

@hetunandu  this seems to be working on release. Please check the loom video
https://www.loom.com/share/233d17c7d01e43da8c5214cd8d1a8e67

I recorded this yesterday https://www.loom.com/share/5b0fe8fa59574e8080d9d6aa0ed04279

authors: Nikhil-Nandagopal hetunandu tazmaniax vicky-primathon


text:
[BUG]? is hidden on the bottom right corner because of Operator suggestions

Issue: ? is hidden on the bottom right corner because of Operator suggestions
Browser Details: Chrome Version 85.0.4183.102 (Official Build) (64-bit)
Device Details: macOS 10.15.6 (MacBook Pro)
Note: Tried on cloud.
Steps to replicate :

Hit https://app.appsmith.com/user/login
Sign up

Expected Result: With operator suggestions, ? on the bottom right should be visible.
Actual Result : With operator suggestions, ? is hidden.
Attachment: https://drive.google.com/drive/folders/1BiZCDCXlOM1fhU9gloNSzCTQtUEerg3f?usp=sharing

Thanks for reporting this. Try using loom chrome extension to record this so that it can be embedded in the issue itself.

@areyabhishek Apologies. Please find attached another screenshot which clearly displays the issue.

Closing this issue as it is no longer a problem

authors: Saket2 areyabhishek mohanarpit


text:
Preload tiles from an array of latlngs ?

I can see in the code there is a call to load an image/url depending on a point in the tilemap layer.
One thing I was wondering about, was the ability to preload a set of images, based on an array of latlongs, or an area (eg topleft, bottomright).
Reasoning is, I'm developing an app where offline is needed, and currently before I go ofline, I drag around a certain area to load the images into cache. Then the map works offline.
I'm unsure if this should be part of the core flutter_map though, as it feels like it could easily be abused (downloading too many tiles). Maybe there could be a delay added to be kind to the tileservers and a max tiles restriction ? I looked a the plugin lib, but didn't see how I could manage via that to access the tilelayer code.
Completely understand if it's not desirable.

Have you checked out the offline tile example? I suspect that will work for your use-case.

I think that a sortvof preliading and casching is a good think. So offline map are good molto for limited zone where tiles are very light under 100mb. So i m thinking somethink like:

caching leader tiles
preloading other tiles near visibile area for a smonth gestures

What about stsrt using cachednetwork plugin?

Am going to close this, although I still think it would be useful, especially using flutter_cache_manager, but it became too fiddly for me.
Just for info, I've gone with my own solution which lets me select an area via latlngs, download the tiles in advance (after deleting old set from a custom directory) using http.get & Io.File..writeAsBytesSync, and then if the app detects no data available, it changes fluttermap offline mode and uses a local urlTemplate, if there is data it uses a remote urlTemplate.

authors: gimox ibrierley johnpryan


text:
Add GenerateUnsplashImage to Ruby language

A sample Ruby Cloud function to generate a picture URL from Unsplash's API.

@rafaeelaudibert  please add screenshots of a successful execution from the Appwrite console along with the logs

@rafaeelaudibert closing this PR for now. Feel free to reopen it / create a new one when you're ready to start working on it once again

repo: appwrite/demos-for-functions


text:
🐛 Bug Report: Crash with Database Parsing

👟 Reproduction steps
I'm tying to use this SDK from a server to create the DB structure.  Here's a simple program to repro:
let client = Client()
            .setEndpoint(Constants.endpoint)
            .setProject(Constants.appWriteProjectId)
            .setKey(Constants.appWriteKey)

databases = Databases(client)
let databaseList = try await databases.list()

(Side note: 404 - page not found on the code of conduct link)
👍 Expected behavior
No crash :)
👎 Actual Behavior
AppwriteModels/Database.swift:53: Fatal error: Unexpectedly found nil while unwrapping an Optional value

🎲 Appwrite version
Different version (specify in environment)
💻 Operating system
Linux
🧱 Your Environment
Running AppWrite with docker on local
docker run -it --rm \
    --volume /var/run/docker.sock:/var/run/docker.sock \
    --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw \
    --entrypoint="install" \
    appwrite/appwrite:0.13.3

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

I had the wrong server version.

repo: appwrite/sdk-for-swift


text:
HSTS headers

@fancyremarker for you to review and merge. HSTS header.

Super, good catch.

Related: just discovered preload flag: https://hstspreload.appspot.com/
Not appropriate here but kind of neato.

authors: fancyremarker mixonic


text:
Frame busting and file drops in textareas

Takes two dashboard PRs and moves share-able bits here.

Frame buster, aptible/dashboard.aptible.com#552
Drag-n-drop .crt, bundled .crt, and .key files to create certificates, aptible/dashboard.aptible.com#543

Those both got a merge thumbs up, so I'll merge this on Travis' green light and then do another dashboard PR to set the cli version and implement these changes.

Thanks for this, great work!

authors: gib sandersonet

repo: aptible/ember-cli-aptible-shared


text:
[Feature Request]: add icon and change title

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The amazon clone is nice but there is no icon for the website, i would like to add it and change the title from 'Amazom' to 'Online shopping site in India' as it is the landing page of the website.
Use Case
This makes the website UI look professional .
Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I have starred the repository

@chaanakyaaM u are assigned

Kindly review the PR.


text:
feat(dockerfile): add a new check about "apk add --no-cache"

I'm trying to integrate Dockle into Trivy. This PR adds a new check defsec is currently missing.
https://github.com/goodwithtech/dockle/blob/master/CHECKPOINT.md#dkl-di-0004

@giorod3 @simar7 Would you review the PR?

repo: aquasecurity/defsec


text:
False Positive in KHV036

When the cluster returns 403 responses for unauthenticated requests, KHV036 shouldn't be triggered.
https://github.com/aquasecurity/kube-hunter/blob/7479aae9baed4bb137b4f8c80577ba978280ec60/kube_hunter/modules/discovery/kubelet.py#L63

kube-hunter producing incorrect result for KHV036 even though the authentication: anonymous: enabled is set to false in Kubelet configuration file. Please find the below screen shots for your reference.

Expected Result: If authentication: anonymous: enabled is set to false in Kubelet configuration file, the check should not be failed.
Actual Result: The check is being failed.

repo: aquasecurity/kube-hunter


text:
Add support for Response Policies

Would be great to be able to configure Response Policies with Terraform

This would be great feature

I have a large customer that wants to start using response policies to drive vulnerability management workflows and wants to uses Terraform exclusively to manage aqua configuration.
This feature would greatly accelerate their role out of aqua.

authors: MWilkin12 MorganTAtkins sigurdfalk

repo: aquasecurity/terraform-provider-aquasec


text:
Send webhook for deleted reports

Description
Before this PR, trivy-operator only sent webhooks for created/updated reports.
In this PR trivy-operator also sends webhooks for deleted reports.
To make sure the receiver of the webhook can distinguish between created/updated reports and deleted reports, the webhook has been modified so that it now contains 2 fields:

verb (can be "update" or "delete")
report (the actual trivy-operator report)

Related issues

Close #1058

Checklist

[x] I've read the guidelines for contributing to this repository.
[ ] I've added tests that prove my fix is effective or that my feature works.
[x] I've updated the documentation with the relevant information (if needed).
[ ] I've added usage information (if the PR introduces new options)
[ ] I've included a "before" and "after" example to the description (if the PR is a user interface change).

@bgoareguer thanks you for the PR update , I have added couple of suggestion and nit comment

@bgoareguer look good 🚀  thank you for the contribution,  last thing , do you mind updating the helm readme with new param

lgtm 🚀

authors: bgoareguer chen-keinan

repo: aquasecurity/trivy-operator


text:
A Comprehensive Analysis of Preprocessing for Word Representation Learning in Affective Tasks

一言でいうと
分散表現を学習する際、コーパスに対してかける前処理がどのような影響をもたらすのかを調査した研究。Negation(否定文を通常文に言い換える(not happy => sadなど))は様々なデータセットで効果があり、次いで品詞フィルタが効果有。StopWordとStemmingは逆に精度が落ちた。
論文リンク
https://www.aclweb.org/anthology/2020.acl-main.514/
著者/所属機関
Nastaran Babanejad, Ameeta Agrawal, Aijun An, Manos Papagelis

York University

投稿日付(yyyy/MM/dd)
ACL2020
概要
新規性・差分
手法
結果
コメント

解説スライド
https://speakerdeck.com/uchi_k/qian-chu-li-gadan-yu-mai-meip-miniyu-eruying-xiang-a-comprehensive-analysis-of-preprocessing-for-word-representation-learning-in-affective-tasks?slide=11

repo: arXivTimes/arXivTimes


text:
Feature: support shadow type match regex (#365)

create shadow tables in init.sql & sharding.sql
hide shadow tables for "show tables" command
impl shadow match hint rule (only select)
support shadow type match regex (only select)

Test Cases:
SELECT name FROM student WHERE uid = 1; //sharding
SELECT name FROM student WHERE name = 'lilei'; //fullscan
SELECT name FROM student WHERE uid = 1 and name = 'lilei'; //sharding
SELECT name FROM student WHERE uid = 1 or name = 'lilei'; //fullscan
/*A! shadow(shadow) */ SELECT name FROM student WHERE uid = 1; //sharding shadow tables
/*A! shadow(shadow) */ SELECT name FROM student WHERE name = 'lilei'; //fullscan shadow tables
/*A! shadow(shadow) */ SELECT name FROM student WHERE uid = 1 and name = 'lilei'; //sharding shadow tables
/*A! shadow(shadow) */ SELECT name FROM student WHERE uid = 1 or name = 'lilei'; //fullscan shadow tables
regex：only support eq & ne
SELECT name FROM student WHERE name = 'hanmeimei'; //fullscan shadow tables
SELECT name FROM student WHERE uid = 1 and name = 'hanmeimei'; //sharding shadow tables
SELECT name FROM student WHERE uid = 1 or name = 'hanmeimei'; //fullscan shadow tables
SELECT name FROM student WHERE NOT name = 'hanmeimei'; //fullscan

What this PR does:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

looks like need add create table script

see sharding.sql

pls add ut

add integration test for shadow tables

repo: arana-db/arana


text:
Environment variables define

How can we setup Environment  variables in foxx service apis? My use case is to create env variables and read in foxx service so that we dont have to change environment specific resources ?
my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[x] 3.3
[ ] self-compiled devel branch

Mode:

[x] Cluster
[x] Single-Server

@dothebart thanks for the reply , I am using ubuntu server where can we set systems evrironment for foxx services?

Hi, you would do so in the systemd unit file or the init script.

I have tried following steps but its not working for me -:
1.) sudo systemctl edit arangodb3.service
2.) Now updated arangodb3.service file with following values
[Unit]
Description=arango
[Service]
NODE_ENV="gg"
3.) sudo service arangodb restart
console.log to  process.env stills reads
{ "PATH" : "/bin:/usr/bin:/sbin:/usr/sbin", "LANG" : "en_US.UTF-8", "_SYSTEMCTL_SKIP_REDIRECT" : "true", "PWD" : "/", "GLIBCXX_FORCE_NEW" : "1", "ICU_DATA" : "///usr/share/arangodb3/" }

btw, its better style not to delete comments, but rather edit them how you overcame them so others have a resource to learn from.

ok sure , Actually above steps solved my problem , i was missing sudo systemctl daemon-reload
command
So steps are -:
1.) sudo systemctl edit arangodb3.service - Write your Env variables
2.) sudo systemctl daemon-reload
3.)  sudo service arangodb restart

repo: arangodb/arangodb


text:
Failed to update Foxx store from GitHub

My Environment

ArangoDB Version: 3.4.5
Storage Engine: RocksDB
Deployment Mode: Single Server
Deployment Strategy: ArangoDB Starter
Configuration:
Infrastructure: Openstack
Operating System: Ubuntu 16.04
Total RAM in your machine: 8GB
Disks in use: SSD
Used Package: TAR package

Component, Query & Data
Affected feature:
General operation, Foxx related
Steps to reproduce
Problem:
(Almost) daily I see the following warning in the logs:

Failed to update Foxx store from GitHub.

Why should the "Foxx store" be updated from GitHub and if so, then why is it failing?
I'm not using any Foxx applications myself, it's just a stock ArangoDB install with 2 databases
Expected result:
I see no reason why Foxx should be updated from GitHub, but if there is, then it shouldn't fail.

Hi @santo74

Why should the "Foxx store" be updated from GitHub

The Foxx store will fetch the apps directly from GitHub, this is how is designed

why is it failing?

Probably your instance is not connected to the internet or probably you have some network issue. The Foxx store will fetch for apps directly from GitHub even if you are not using any Foxx app
On the other hand, those messages can be ignored, if you are not using or willing to use any Foxx app taken from the Github store
Best,

@OmarAyo thanks for the clarification.
However, I think this shouldn't be on by default.
By default no Foxx apps are enabled, so there is no need to fetch from GitHub.
Security wise this isn't good practice in my opinion.
Btw, on that server I'm not blocking any outgoing connections for the moment.

Hi @santo74
I will forward your feedback internally, thanks for the feedback.
Regarding the root cause of those messages, if you are not blocking outgoing connections, then probably your firewall or proxy is disallowing access to GitHub.
Best,

I will forward your feedback internally, thanks for the feedback.

Thanks!

Regarding the root cause of those messages, if you are not blocking outgoing connections, then probably your firewall or proxy is disallowing access to GitHub.

I have no knowledge of GitHub being blocked/disallowed.
For my own projects I am using GitLab and I can fetch packages from there without any issues.

Fetching the service list from github seems to be broken in 3.4 and devel.

@dothebart thanks for investigating this further and confirming the issue.
When fixing this, would it be possible to make the fetching "optional", i.e. only fetch when Foxx apps are effectively in use (as I described earlier)?

@dothebart: I can retrieve the list of Foxx apps using 3.4 and devel just fine, and can even install them without problems.
I have been using a local ArangoDB installation and am not running it inside a specific container or such.
@santo74 : starting with ArangoDB 3.5, fetching the apps from the store can be turned off using a configuration option.

Fetching the service list from github seems to be broken in 3.4 and devel.

@dothebart is there more information available?

@dothebart: I can retrieve the list of Foxx apps using 3.4 and devel just fine, and can even install them without problems.
I have been using a local ArangoDB installation and am not running it inside a specific container or such.
@santo74 : starting with ArangoDB 3.5, fetching the apps from the store can be turned off using a configuration option.

@jsteemann that's great! Any chance it will be backported to 3.4?

@santo74: what I have been trying to say in my last message is that it worked for me out of the box.
I didn't fix anything, and it would be good if @dothebart could back his claims with some info about the environment he ran it in.

@jsteemann @dothebart's issue is not related to this ticket here.

@santo74: what I have been trying to say in my last message is that it worked for me out of the box.
I didn't fix anything, and it would be good if @dothebart could back his claims with some info about the environment he ran it in.

@jsteemann I know, but you said actually 2 things ;-)
So what I was trying to say is whether the possibility to turn off fetching the apps might be backported to 3.4?

@santo74 this is a new feature and it won't be backported.
Regarding the sole problem of this issue, I tried to download a similar file as arangodb desires from inside my arangodb docker container like this:
Find the container with arangod:
docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
73c5dc966862        arangodb:3.4.5      "/entrypoint.sh ar..."   14 seconds ago      Up 13 seconds       0.0.0.0:8529->8529/tcp   happy_borg

then execute an interactive shell in it, and use arangosh to try to download something from github:
docker exec -it 73c5dc966862 /bin/sh
/usr/bin/arangosh
 x=require('internal').download('https://raw.githubusercontent.com/arangodb-foxx/tableau-connector/v1.0.0/manifest.json')

This works for me like this:
{
  "headers" : {
    "source-age" : "0",
    "expires" : "Mon, 03 Jun 2019 12:06:04 GMT",
    "x-fastly-request-id" : "fdc6a0943ea261159fab77cd77a5bc4d7d143da5",
    "etag" : "\"be2919687748687f0703e68e44862dc5c82c3e46\"",
    "x-xss-protection" : "1; mode=block",
    "x-frame-options" : "deny",
    "content-type" : "text/plain; charset=utf-8",
    "connection" : "keep-alive",
    "x-geo-block-list" : "",
    "x-served-by" : "cache-hhn1531-HHN",
    "strict-transport-security" : "max-age=31536000",
    "content-length" : "383",
    "accept-ranges" : "bytes",
    "content-security-policy" : "default-src 'none'; style-src 'unsafe-inline'; sandbox",
    "x-content-type-options" : "nosniff",
    "date" : "Mon, 03 Jun 2019 12:01:04 GMT",
    "http/1.1" : "200 OK",
    "via" : "1.1 varnish",
    "x-github-request-id" : "3246:3591:546780:63A572:5CF50C00",
    "x-timer" : "S1559563265.866430,VS0,VE89",
    "cache-control" : "max-age=300",
    "x-cache" : "MISS",
    "x-cache-hits" : "0",
    "vary" : "Authorization,Accept-Encoding",
    "access-control-allow-origin" : "*"
  },
  "body" : "{\n  \"$schema\": \"http://json.schemastore.org/foxx-manifest\",\n  \"name\": \"tableau-connector\",\n  \"description\": \"Example Tableau Web Data Connector for ArangoDB.\",\n  \"version\": \"1.0.0\",\n  \"thumbnail\": \"tableau.png\",\n  \"engines\": {\n    \"arangodb\": \"^3.0.0\"\n  },...",
  "code" : 200,
  "message" : "OK"
}

Can you confirm that it does or does not work for you too?
You're naming openshift as environment, which is known to have stricter permissions than docker - this could be a reason.

@santo74 this is a new feature and it won't be backported.

Ok, fair enough.

Regarding the sole problem of this issue, I tried to download a similar file as arangodb desires from inside my arangodb docker container like this:
Find the container with arangod:
docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
73c5dc966862        arangodb:3.4.5      "/entrypoint.sh ar..."   14 seconds ago      Up 13 seconds       0.0.0.0:8529->8529/tcp   happy_borg

then execute an interactive shell in it, and use arangosh to try to download something from github:
docker exec -it 73c5dc966862 /bin/sh
/usr/bin/arangosh
 x=require('internal').download('https://raw.githubusercontent.com/arangodb-foxx/tableau-connector/v1.0.0/manifest.json')

This works for me like this:
{
  "headers" : {
    "source-age" : "0",
    "expires" : "Mon, 03 Jun 2019 12:06:04 GMT",
    "x-fastly-request-id" : "fdc6a0943ea261159fab77cd77a5bc4d7d143da5",
    "etag" : "\"be2919687748687f0703e68e44862dc5c82c3e46\"",
    "x-xss-protection" : "1; mode=block",
    "x-frame-options" : "deny",
    "content-type" : "text/plain; charset=utf-8",
    "connection" : "keep-alive",
    "x-geo-block-list" : "",
    "x-served-by" : "cache-hhn1531-HHN",
    "strict-transport-security" : "max-age=31536000",
    "content-length" : "383",
    "accept-ranges" : "bytes",
    "content-security-policy" : "default-src 'none'; style-src 'unsafe-inline'; sandbox",
    "x-content-type-options" : "nosniff",
    "date" : "Mon, 03 Jun 2019 12:01:04 GMT",
    "http/1.1" : "200 OK",
    "via" : "1.1 varnish",
    "x-github-request-id" : "3246:3591:546780:63A572:5CF50C00",
    "x-timer" : "S1559563265.866430,VS0,VE89",
    "cache-control" : "max-age=300",
    "x-cache" : "MISS",
    "x-cache-hits" : "0",
    "vary" : "Authorization,Accept-Encoding",
    "access-control-allow-origin" : "*"
  },
  "body" : "{\n  \"$schema\": \"http://json.schemastore.org/foxx-manifest\",\n  \"name\": \"tableau-connector\",\n  \"description\": \"Example Tableau Web Data Connector for ArangoDB.\",\n  \"version\": \"1.0.0\",\n  \"thumbnail\": \"tableau.png\",\n  \"engines\": {\n    \"arangodb\": \"^3.0.0\"\n  },...",
  "code" : 200,
  "message" : "OK"
}

Can you confirm that it does or does not work for you too?

I'm not using docker, so executed it directly from arangosh on the server and it worked fine.
Therefore I also rechecked the arangodb logs and noticed that the warning hasn't appeared anymore since I created this issue.
Can it be that the fetching is only performed during server startup?
Last week I restarted ArangoDB (or the host server it runs on) several times, but since I created this issue it wasn't restarted anymore.

You're naming openshift as environment, which is known to have stricter permissions than docker - this could be a reason.

No, the environment where ArangoDB runs is with a cloud provider whose infrastructure is based on OpenStack, which is not the same as OpenShift.

Ok, maybe at the time you were trying this github was having issues? (yes, that may also happen ;-) )

Yes that can happen indeed :-)
However, it happened at least 3 days in a row and I'm not aware of any recent "major" connectivity issues with GitHub.
I suggest that I monitor the logs for the next couple of days and if it doesn't happen again, I'll close the issue because in that case it can't be reproduced (anymore).

It appears to happen very randomly.
Right after my last comment it happened 2 times in 1 day, then everything was fine until yesterday.
I attached a screenshot to give an idea of the randomness.

@pluma can we add the details of the exception to this message?
  if (internal.isFoxxStoreDisabled()) {
    res.json([]);
  } else {
    try {
      store.update();
    } catch (e) {
      console.warn('Failed to update Foxx store from GitHub.');
    }
    res.json(store.availableJson());
  }
})
.summary('List of all Foxx services submitted to the Foxx store.')
.description(dd`
  This function contacts the fishbowl and reports which services are available for install.
`);

We could but I doubt the exception will be significantly more useful. We could log information about the response as that could indicate at least whether it failed because of an error response or because of network issues.

shouldn't this be an exception from the HTTP connection or its flow? so you could see whether arangod wasn't able to connect, or whether github itself errored out.

By default no Foxx apps are enabled, so there is no need to fetch from GitHub.

BTW: There are in fact two system services, /_admin/aardvark and _api/foxx.

@Simran-B True but the only thing that fetches from GitHub is the Foxx Store, which is only accessible via the Aardvark web interface. Note that if the Foxx Store is enabled, Aardvark will trigger a fetch as soon as you click on the Foxx services tab because the "install from store" view is the default.

FYI: The option in 3.5 is called --foxx.store and true by default.

Thanks for the follow-up guys!
Providing an indication of why the store update fails might be a good idea indeed.
It's also great to know the store can be disabled in 3.5, but that version isn't released yet and I probably won't be able to upgrade to 3.5 anytime soon after the release (for several reasons).
In production we're trying to skip any .0 and even .1 releases whenever possible.
Also, if I'm not mistaken "simple queries" will be removed in 3.5 but at the moment several of our services still rely on "simple queries". This means part of our code has to be rewritten in order to be able to upgrade to 3.5.

The Simple Queries API and interfaces are marked for deprecation, but will still be available until v4.0.0.

Disabling the Foxx store has been backported to the 3.4 branch by https://github.com/arangodb/arangodb/pull/9593.

Added options to make server more secure:

--foxx.api: set to false disables Foxx management API
--foxx.store: set to false disables Foxx UI

The new options will be available in 3.4.8.

@maxkernbach thanks for backporting this to 3.4!
I guess this issue can be closed now.

@santo74 Sure, we will close this issue once version 3.4.8 is released.

Closing this issue as fixed since version 3.4.8, which supports the following options, has been released:

--foxx.api: set to false disables Foxx management API
--foxx.store: set to false disables Foxx UI

Please find the latest version in the download section.

authors: OmarAyo Simran-B dothebart hkernbach jsteemann maxkernbach pluma santo74


text:
Bug fix/fix windows client installer

the client installer also needs to have all variables in order to install the javascript files into a proper location.

Fixes javascript.startup-directory client package KI: https://github.com/arangodb/release-qa/issues/183

authors: Simran-B dothebart


text:
fix disjoints in query snippet

add disjoint smart graph query snippet support

http://jenkins01:8080/view/PR/job/arangodb-matrix-pr/9679/

http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/9751/

http://jenkins01:8080/view/PR/job/arangodb-matrix-pr/9768/


text:
Cleanup/remove dead aql code

Removes dead and unused code in AQL.
This is preparation for Performance improvement, as this code delegates to the new API.
I want to keep both PRS separate to simplify review.

:+1: for code deletion!

Jenkins fully blue:
http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/11320/

authors: jsteemann mchacki


text:
don't make inline-subqueries optimizer rule pull out COLLECTs

Scope & Purpose
Don't apply optimizer rule inline-subqueries for subqueries that contain a COLLECT statement if the subquery itself is called from a FOR loop. Otherwise the COLLECT will be pulled out to caller level and be applied there, which may produce different results than when applied inside the subquery.

[ ] Bug-Fix for devel-branch (i.e. no need for backports?)
[x] Bug-Fix for a released version (did you remember to port this to all relevant release branches?)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)
[x] The behavior change can be verified via automatic tests

Related Information

[x] There is a JIRA Ticket number: https://arangodb.atlassian.net/browse/ES-664

Testing & Verification
This PR adds tests that were used to verify all changes:

[x] Added new integration tests (i.e. in shell_server / shell_server_aql)

http://172.16.10.101:8080/view/PR/job/arangodb-matrix-pr/11465/

Tests blue


text:
[CINFRA-118] Replicated Log JS Intergration

Scope & Purpose
Create a JS API that can be used to write functional tests and performance tests.

[ ] :hankey: Bugfix (requires CHANGELOG entry)
[x] :pizza: New feature (requires CHANGELOG entry, feature documentation and release notes)
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification
[ ] :book: CHANGELOG entry made

Backports:

[x] No backports required
[ ] Backports required for: (Please specify versions and link PRs)

https://jenkins.arangodb.biz/job/arangodb-matrix-pr/17441/


text:
3.4 #hacktoberfest

Please note that for legal reasons we require you to sign the
Contributor Agreement
before we can accept your pull requests.

Closed as useless and unrelated.


text:
Template String Processor for AQL (ES6/7)

Mirroring the request on arangodb it would be nice to have an method on a db instance db.aql that will process a template string into a parameterized query and run it, returning a promise.
This way, it will be very smooth writing interactions in JS with environments (babel/traceur) that support those features, and more so with async/await support.

Cool, :+1:

repo: arangodb/arangojs


text:
🛑 Test loibra.moo.com is down

In 7653024, Test loibra.moo.com (http://loibra.mooo.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Test loibra.moo.com is back up in 23b7aa1.

repo: aratan/Monitorizaci-n


text:
sharepoint_loader.py

pip install Office365-REST-Python-Client
run this one

Make sure that you also make relevant changes in the frontend such that users can sync their file/ folder.
Also changes in the remote_creator file and worker.py file too
Thank you!


text:
Feature: Round Corners

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix
Why was this change needed? (You can also link to an open issue here)
fixes #514
Other information:

@holopin-bot @SoumyadiptoPal  Just as rounded as we need it, thank you!

authors: SoumyadiptoPal dartpain


text:
pyflakes: removed unused import

Changes introduced with this PR
removed unused import dataclasses in plugin.py
Signed-off-by: Sandro Bonazzola sbonazzo@redhat.com

By contributing to this repository, I agree to the contribution guidelines.

yes. please keep this open, I'm checking integration with Jira.

repo: arcalot/arcaflow-plugin-sdk-python


text:
Create CEA's documentation website

Need of a website to show documentation for developers (read the docs kind). This should contain mainly information about the functions and workflow of the tool.
---- Store it in GitDocs.
---- The formula for showing scripts: (top-down and bottom-up). 2 callgraphs (one coarse, one in detail) followed by the description of every function using SphynX.

@JIMENOFONSECA for clarification: what is GitDocs?

@JIMENOFONSECA what is the status on this? I think you are creating the website, right? I have a task #386 for the RTD api documentation. See the issue for a preview of what it could end up looking like.

this issue is supposed to be #386. i think this is a duplicate then.... The CEA documentation website is intended to be in RTD or did i get it wrong?

i meant RTD when i said gitdocs, sorry...

You are right. Closing this as a duplicate.

authors: JIMENOFONSECA daren-thomas


text:
TextureUtil, GlConst and GLX are still SRG names

TextureUtil, GlConst and GLX are still SRG names. Only RenderSystem and GlStateManager are remapped to mojang/parchment names in the development environment.
Forge Extension.

Adding onto this add in ListTag would fail to remap mods from srg to named since there is a mapping with c add c c in the srg tiny

Should be fixed with my SrgMerger rewrite.

authors: BloCamLimb Juuxel shedaniel

repo: architectury/architectury-loom


text:
Does not work

Exception in setTimeout callback: TypeError: Cannot read property 'isotope' of undefined
at http://localhost:3000/packages/arcjet_radioactive.js?44a2a5fa53e45c6b4408cbdfb76105c637a5844a:285:31
at _.extend.withValue (http://localhost:3000/packages/meteor.js?9730f4ff059088b3f7f14c0672d155218a1802d4:971:17)
at http://localhost:3000/packages/meteor.js?9730f4ff059088b3f7f14c0672d155218a1802d4:428:45
at http://localhost:3000/packages/meteor.js?9730f4ff059088b3f7f14c0672d155218a1802d4:999:22

I will take a look.

Thanks :)

BTW, which version of Meteor are you using?

1.2.1

Cool.

So, I just took a look at my demo, it still works under 1.2.1. There's an isotope error early on, but it doesn't seem to affect the demo's functionality.
Have you taken a look at this?
https://github.com/arcjet/radioactive-demo
Also, are you using reactive-vars?

authors: cryptoquick nadeemja

repo: arcjet/radioactive


text:
日历插槽如何使用

日历插槽如何使用，使用下面代码无效果
<a-calendar
          v-model="calendarValue"
          mode="month"
          :modes="['month']"
          default-mode="month"
          @change="daySelectOnChange"
        >
          <template #default="{ date }">
            <div>{{ date }}日</div>
          </template>
</a-calendar>

@YJ-L-2017  你好，我这边 Demo 是没问题的。请确保版本 2.53.0 及以上。

非常感谢你的回复，使用 arco-cli生成的Arco Pro 简单项目，默认的@arco-design/web-vue 版本为2.45.0

你好，我升级之后依旧没有显示，

日历设置插槽之后，就无法使用触发change事件

日历插槽在年模式下是不起作用的吗

repo: arco-design/arco-design-vue


text:
make data/images path compliant with Linux/Macos etc.

on line 1698 the data path is configured for Windows, wiht back slashes. That wont' work on Macos/Linux etc.

Thank you for the contribution!
Will you fix any other backslashes or should I merge this as it is right now?

authors: arda-guler moshix


text:
Issue about PostProcessingAction

I am trying to use PostProcessingAction to filter queries created within the last year, but it doesn't seems to be working, I got the full queries, here is my code:
Query.PostProcessingAction(items => items.Where(e =>
{
    return e.CreatedTime != null && DateTime.TryParse(e.CreatedTime, out var parsedTime) ? parsedTime >= DateTime.Now.AddYears(-1) : false;
}));

I have done some tests, if I return false directly, I will get an empty list, which is expected:
Query.PostProcessingAction(items => items.Where(e =>{ return false; }));

But if I return e.CreatedTime == null, which always be false, I will get the full list:
Query.PostProcessingAction(items => items.Where(e =>{ return e.CreatedTime == null; }));

What is the problem? Am I using it incorrectly?

Hey @lumoslnt
I can not reproduce the issue. Here I created a full sample app. Please reproduce the issue in this sample.
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net8.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Ardalis.Specification.EntityFrameworkCore" Version="8.0.0" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="8.0.10" />
  </ItemGroup>

</Project>

using Ardalis.Specification;
using Ardalis.Specification.EntityFrameworkCore;
using Microsoft.EntityFrameworkCore;

await AppDbContext.SeedAsync();

using var context = new AppDbContext();
var repo = new Repository<Customer>(context);

var result = await repo.ListAsync(new CustomerSpec());

Console.WriteLine(result.Count);

public class CustomerSpec : Specification<Customer>
{
    public CustomerSpec()
    {
        Query.PostProcessingAction(item => item.Where(x => x.CreatedTime == null));
    }
}
public class Repository<T>(AppDbContext context) : RepositoryBase<T>(context) where T : class
{
}
public record Customer
{
    public int Id { get; set; }
    public DateTime? CreatedTime { get; set; }
}

public class AppDbContext : DbContext
{
    public DbSet<Customer> Customers { get; set; }
    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    {
        optionsBuilder.UseSqlServer("Server=(localdb)\\mssqllocaldb;Database=SpecIssue411Db;Trusted_Connection=True");
    }

    public static async Task SeedAsync()
    {
        using var context = new AppDbContext();
        await context.Database.EnsureDeletedAsync();
        await context.Database.EnsureCreatedAsync();
        var customer = new Customer { CreatedTime = DateTime.Now };
        context.Customers.Add(customer);
        await context.SaveChangesAsync();
    }
}

authors: fiseni lumoslnt

repo: ardalis/Specification


text:
No linux?

Is there some way to adapt it to run under linux?

Yes, you can. If you get an error you can share it here.

repo: ardamavi/Game-Bot


text:
Failed validation, i.e. additional field not present in schema, leads to duplicate responses, no context enhancements possible, introspection query and empty result..

Issue workflow progress

Progress of the issue based on the
Contributor Workflow

[x] 1. The issue provides a reproduction available on
Github,

Execution instructions are in the repo in the readme.

[ ] 2. A failing test has been provided
[ ] 3. A local solution has been provided
[ ] 4. A pull request is pending review

Describe the bug
We have created a mesh of different subgraphs. Now, if somebody sends a request with a non-existing field, i.e.
 query myQuery{ 	myQuery { 		items { 			id 			toast 		} 	} }
where toast does not exist in the schema, we face the following issues:
The query runs through the following plugin steps:

parse
validate (here we can see validation failed)
parse (now we have an introspection query for schema)
validate
execute (here we can see the result of the introspection query)

We are wondering why it is running through the second parse - validate cycle. From debugging we know in this case it sends an introspection query. Even if we tried disabling introspection, e.g. via envelop plugin, it still runs through this second phase.
Additionally, in executeDone we can only see the results of the introspection query, but not the original query's results.
The displayed result, then shows something like this:
 { 	"errors": [ 		{ 			"message": "Field \"toast\" is not defined by type \"myQuery_type\"." 		}, 		{ 			"message": "Field \"toast\" is not defined by type \"myQuery_type\"." 		} 	] }
So the result is duplicated.
To Reproduce Steps to reproduce the behavior:

Create a mesh with a query.
Execute a query with a non-existing field.

Expected behavior
We would have expected to see the validation result in execute phase, or even a context attribute, which we set in the validate phase, with which we would be able to skip execution. However, we can only see the introspection query here.
Environment:

OS: Windows 11
"@graphql-mesh/cli": "0.87.14",   "@graphql-mesh/graphql": "0.95.7",   "@graphql-mesh/http": "0.96.12",   "@graphql-mesh/transform-filter-schema": "0.95.7",   "@graphql-mesh/transform-rename": "0.95.8":
NodeJS: v18.18.0

Additional context
What we are trying to achieve is creating prometheus metrics with result status codes from all calls filtered by operationName, client, etc. therefore, we would also like to know who is potentially writing bad requests e.g. after a version upgrade.

Added repo for reproduction.

repo: ardatan/graphql-mesh


text:
[Library Manager] Please add SUSHI-EXP-BOARD-library

Hello.
I created a library to manage my board named SUSHI-EXP-BOARD (that assembled with ESP32).
Could you add this to a list of libraries?
url: https://github.com/Kei0208/SUSHI-IO-EXP
Thanks.

Hi @Kei0208. We have a new system for submitting libraries. The instructions are here:
https://github.com/arduino/library-registry#adding-a-library-to-library-manager
Please let me know if you have any questions.

repo: arduino/library-registry


text:
🛑 U3A Raspberry Pis is down

In 598992c, U3A Raspberry Pis (http://u3a.epizy.com/rpis) was down:

HTTP code: 0
Response time: 0 ms

Resolved: U3A Raspberry Pis is back up in 922d83b after 14 minutes.

repo: ardus-uk/upptime