text:
Update python packages to their latest available

Update packages to their latest available
I skipped updating typedload to 2.18 because I hit an issue while testing. Will take a look at when I have more time.

Tested the sdp-operator deployment on my local cluster

Putting back into as draft. May have a found an issue while testing.

repo: appgate/sdp-operator


text:
Improve folding ranges if editor only supports line folding

If the folding range doesn't end at the end of the last line, exclude that line from the folding range since the end line gets folded away. This means if we reported end.line, we would eg. fold away the } that matches a {, which looks surprising.
If the folding range does end at the end of the line we are in cases that don't have a closing indicator (like comments), so we can fold the last line as well.

@swift-ci Please test

source: gharchive/pull-request

repo: apple/sourcekit-lsp

license_type: permissive

license_source: github-api


text:
build: use export targets for XCTest

This adjusts the build to use the CMake config and export targets to
ensure that things are rebuilt when appropriate.  This also reduces the
use of custom variables.

Please test with following PRs:
apple/swift-corelibs-xctest#290
apple/swift#28232
@swift-ci please test

Please test with following PRs:
apple/swift-corelibs-xctest#290
@swift-ci please test

repo: apple/swift-corelibs-foundation


text:
[Parseable output] Use FileType's description for the file type.

FileType.description provides the "external" name for each file type,
which is used for parsable output and output file maps, among other
things. Fix the description for serialized diagnostics files... so now
diagnostics show up properly in Xcode.

@swift-ci please test

repo: apple/swift-driver

license_source: bigquery


text:
[Basic] Introduce a FS method for creating directories.

This also fixes a problem with the prior use of the LLVM APIs, which don't
properly delegate to the umask to set the permissions.

@swift-ci please smoke test

repo: apple/swift-llbuild


text:
When parsing the DBGSourcePathRemapping plist entries

When parsing the DBGSourcePathRemapping plist entries
in a dSYM, and it's a version 2 DBGSourcePathRemapping,
in addition to the build/source paths specified, add
build/source paths with the last two filename components
removed.  This more generic remapping can sometimes
help lldb to find the correct source file in complex
projects.
rdar://problem/33973545
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@311622 91177308-0d34-0410-b5e6-96231b3b80d8
(cherry picked from commit 31696925e66879752f1f32cdff3f9f19bccda278)
(cherry picked from commit bdc50e2821f13e5e740c8b9670fa9d0e997d2c06)

@swift-ci please test

@jasonmolenda Jason, are you going to merge this one?

@swift-ci please test

@jasonmolenda this seems to be dead, can we close it?

Feel free to reopen this if you plan to work on it again.

authors: dcci jasonmolenda

repo: apple/swift-lldb


text:
Include source in StreamLogHandler output

Include source in StreamLogHandler output.
Motivation:
When using the same Logger across an application in combination with the default StreamLogHandler, it may be difficult to differentiate between logs produced by different modules. ServiceLifecycle works around this by prepending the log message with [Lifecycle], which is what I'd like to do StreamLogHandler by default, leveraging the source log parameter.
Modifications:
StreamLogHandler will include the source in brackets right before the log message when writing a log.
Result:
Logs from different modules are easily differentiable when produced using the same Logger instance.

I added this PR as a starting point for a discussion around whether we should be including the source parameter in log output produced by StreamLogHandler. CC @ktoso, @weissi

I am personally happy with this PR, so good to go from my side :).
Said that, we kinda intentionally made StreamLogHandler "not good" because we want people to use real logging backends instead of relying on this "toy implementation". But given that we probably shouldn't omit too much information, I'd say let's take adding "source".

@swift-server-bot test this please

@swift-server-bot add to allowlist

Said that, we kinda intentionally made StreamLogHandler "not good" because we want people to use real logging backends instead of relying on this "toy implementation".
@weissi

Good point! Although one could also argument that having it as a reference point for "better" implementations would also be beneficial, so including it could motivate other impls to do the same.

authors: slashmo weissi

repo: apple/swift-log


text:
-cross-module-optimization Causes Compiler Crash

This occurs on both Ubuntu 18.04 and macOS 11.1. The below output is from Ubuntu.
This occurs on both Swift for Tensorflow 0.12 and Swift dev trunk 2020-12-23. The below output is from Swift dev trunk 2020-12-23.
$ which swift
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift
$ swift --version
Swift version 5.3-dev (LLVM bcee1b98f3b26c5, Swift dbcf7fe1bf76226)
Target: x86_64-unknown-linux-gnu
$ git log
commit 62bf5083df970e67c886210fa5b857eacf044b7c (HEAD -> main, tag: 2.10.2, origin/main, origin/HEAD)
Author: Cory Benfield <lukasa@apple.com>
Date:   Wed Dec 16 09:34:00 2020 +0000

    Update BoringSSL to df75139becd7355e117c9860452265b898b49376. (#261)
$ rm -rf .build
$ swift build -c release -Xswiftc -cross-module-optimization
Fetching https://github.com/apple/swift-nio.git from cache                                                                    Cloning https://github.com/apple/swift-nio.git                                                                                Resolving https://github.com/apple/swift-nio.git at 2.25.1                                                                    /home/xander/dev/swift-nio-ssl/Sources/NIOSSL/SSLPrivateKey.swift:54:44: warning: using 'class' keyword for protocol inheritance is deprecated; use 'AnyObject' instead                                                                                internal protocol CallbackManagerProtocol: class {                                                                                ^~~~~                                                                                AnyObject                                                                          <unknown>:0: error: fatal error encountered while reading from module 'NIOSSL'; please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the project
<unknown>:0: note: module 'NIOSSL' full misc version is '5.3(5.3)/Swift version 5.3-dev (LLVM bcee1b98f3b26c5, Swift dbcf7fe1b
f76226)'

*** DESERIALIZATION FAILURE (please include this section in any bug report) ***
module 'CNIOBoringSSL' was not loaded
Please submit a bug report (https://swift.org/contributing/#reporting-bugs) and include the project and the crash backtrace.
Stack dump:
0.      Program arguments: /home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend -frontend -
c /home/xander/dev/swift-nio-ssl/Sources/NIOTLSServer/main.swift -emit-module-path /home/xander/dev/swift-nio-ssl/.build/x86_6
4-unknown-linux-gnu/release/NIOTLSServer.build/NIOTLSServer.swiftmodule -emit-module-doc-path /home/xander/dev/swift-nio-ssl/.
build/x86_64-unknown-linux-gnu/release/NIOTLSServer.build/NIOTLSServer.swiftdoc -emit-module-source-info-path /home/xander/dev
/swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/NIOTLSServer.build/NIOTLSServer.swiftsourceinfo -emit-dependencies-path
 /home/xander/dev/swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/NIOTLSServer.build/NIOTLSServer.d -target x86_64-unkno
wn-linux-gnu -disable-objc-interop -I /home/xander/dev/swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release -I /home/xander/d
ev/swift-nio-ssl/.build/checkouts/swift-nio/Sources/CNIOSHA1/include -I /home/xander/dev/swift-nio-ssl/.build/checkouts/swift-
nio/Sources/CNIOAtomics/include -I /home/xander/dev/swift-nio-ssl/.build/checkouts/swift-nio/Sources/CNIOWindows/include -I /h
ome/xander/dev/swift-nio-ssl/.build/checkouts/swift-nio/Sources/CNIODarwin/include -I /home/xander/dev/swift-nio-ssl/.build/ch
eckouts/swift-nio/Sources/CNIOLinux/include -I /home/xander/dev/swift-nio-ssl/Sources/CNIOBoringSSLShims/include -I /home/xand
er/dev/swift-nio-ssl/Sources/CNIOBoringSSL/include -color-diagnostics -g -module-cache-path /home/xander/dev/swift-nio-ssl/.bu
ild/x86_64-unknown-linux-gnu/release/ModuleCache -swift-version 5 -O -D SWIFT_PACKAGE -Xcc -fmodule-map-file=/home/xander/dev/
swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/CNIOSHA1.build/module.modulemap -Xcc -fmodule-map-file=/home/xander/dev/
swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/CNIOAtomics.build/module.modulemap -Xcc -fmodule-map-file=/home/xander/d
ev/swift-nio-ssl/.build/checkouts/swift-nio/Sources/CNIOWindows/include/module.modulemap -Xcc -fmodule-map-file=/home/xander/d
ev/swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/CNIODarwin.build/module.modulemap -Xcc -fmodule-map-file=/home/xander
/dev/swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/CNIOLinux.build/module.modulemap -Xcc -fmodule-map-file=/home/xande
r/dev/swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/CNIOBoringSSLShims.build/module.modulemap -Xcc -fmodule-map-file=/
home/xander/dev/swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/CNIOBoringSSL.build/module.modulemap -module-name NIOTLS
Server -cross-module-optimization -num-threads 8 -o /home/xander/dev/swift-nio-ssl/.build/x86_64-unknown-linux-gnu/release/NIO
TLSServer.build/main.swift.o
1.      Swift version 5.3-dev (LLVM bcee1b98f3b26c5, Swift dbcf7fe1bf76226)
2.      While evaluating request ExecuteSILPipelineRequest(Run pipelines { PrepareOptimizationPasses, EarlyModulePasses, HighL
evel,Function+EarlyLoopOpt, HighLevel,Module+StackPromote, Serialize, MidLevel,Function, ClosureSpecialize, LowLevel,Function,
 LateLoopOpt, SIL Debug Info Generator } on SIL for NIOTLSServer.NIOTLSServer)
3.      While running pass #453 SILModuleTransform "PerformanceSILLinker".
4.      While deserializing SIL function "$s6NIOSSL13NIOSSLContextCfd"
5.      While deserializing SIL function "CNIOBoringSSL_SSL_CTX_free"
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x5731ea4]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x572f93e]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x573208c]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12980)[0x7f395e6fa980]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f395cf9cfb7]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f395cf9e921]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x106a549]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x11552f1]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x1155630]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x112870c]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x1127d05]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x112e8e6]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x1129ac1]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x113f32c]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x10f72ad]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x11fde4a]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x132e481]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x132e853]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x132e62f]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x11fdf04]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xc5437e]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xaeac5f]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xaed3c1]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xae7a28]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xae79db]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xb04d2a]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xaf2924]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xae7bf5]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0xaf51bf]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x69fc2d]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x51817d]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x517bbc]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x50b492]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x49c033]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f395cf7fbf7]
/home/xander/swift-DEVELOPMENT-SNAPSHOT-2020-12-23-a-ubuntu18.04/usr/bin/swift-frontend[0x49bb4a]

It is specifically the -Xswiftc -cross-module-optimization that causes the compiler crash. -c release alone does not trigger it.
Perhaps I should file a report at bugs.swift.org?

Yup, compiler crashes are Swift bugs and should be filed upstream.

SR-14006

source: gharchive/issue

authors: Lukasa xanderdunn

repo: apple/swift-nio-ssl


text:
NIOClientTCPBoostrap.connect() crashes when the host argument is empty

Expected behavior
When calling .connect() with an invalid hostname, I expect it to throw an error that can be caught with try...catch.
Actual behavior
Calling .connect(host: "", ...) crashes with an EXC_BAD_INSTRUCTION.
Steps to reproduce

Checkout swift-nio-examples
Call .connect() with an empty host argument, e.g. modify swift-nio-examples/UniversalBootstrapDemo/ExampleHTTPLibrary.swift:67 to:
.connect(host: "", port: useTLS ? 443 : 80)
Run

Backtrace:
(lldb) bt
* thread #2, queue = 'nio.transportservices.eventloop.taskqueue', stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
  * frame #0: 0x00007fff699d8401 libswiftNetwork.dylib`function signature specialization <Arg[1] = Owned To Guaranteed> of Network.NWConnection.init(to: Network.NWEndpoint, using: Network.NWParameters) -> Network.NWConnection + 417
    frame #1: 0x00007fff699b1d50 libswiftNetwork.dylib`Network.NWConnection.__allocating_init(to: Network.NWEndpoint, using: Network.NWParameters) -> Network.NWConnection + 48
    frame #2: 0x00000001004ccdd5 UniversalBootstrapDemo`NIOTSConnectionChannel.beginActivating0(target=<unavailable>, promise=<unavailable>, self=<unavailable>) at NIOTSConnectionChannel.swift:513:26
    frame #3: 0x00000001004d0159 UniversalBootstrapDemo`protocol witness for StateManagedChannel.beginActivating0(to:promise:) in conformance NIOTSConnectionChannel at <compiler-generated>:0
    frame #4: 0x00000001004efc0a UniversalBootstrapDemo`StateManagedChannel.activateWithType(type=<unavailable>, endpoint=<unavailable>, promise=<unavailable>, self=<unavailable>) at StateManagedChannel.swift:271:14
    frame #5: 0x00000001004efe32 UniversalBootstrapDemo`StateManagedChannel.connect0(endpoint=<unavailable>, promise=<unavailable>, self=<unavailable>) at StateManagedChannel.swift:182:14
    frame #6: 0x00000001004cfe4f UniversalBootstrapDemo`NIOTSConnectionChannel.triggerUserOutboundEvent0(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at NIOTSConnectionChannel.swift:660:18
    frame #7: 0x00000001004d0329 UniversalBootstrapDemo`protocol witness for ChannelCore.triggerUserOutboundEvent0(_:promise:) in conformance NIOTSConnectionChannel at <compiler-generated>:0
    frame #8: 0x00000001002e6ac9 UniversalBootstrapDemo`HeadChannelHandler.triggerUserOutboundEvent(context=<unavailable>, event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:978:38
    frame #9: 0x00000001002e6bb9 UniversalBootstrapDemo`protocol witness for _ChannelOutboundHandler.triggerUserOutboundEvent(context:event:promise:) in conformance HeadChannelHandler at <compiler-generated>:0
    frame #10: 0x00000001002e3e10 UniversalBootstrapDemo`ChannelHandlerContext.invokeTriggerUserOutboundEvent(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:1470:29
    frame #11: 0x00000001002e944f UniversalBootstrapDemo`ChannelHandlerContext.triggerUserOutboundEvent(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:1289:26
    frame #12: 0x00000001002d02b1 UniversalBootstrapDemo`_ChannelOutboundHandler.triggerUserOutboundEvent(context=<unavailable>, event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelHandler.swift:265:17
    frame #13: 0x00000001004347ad UniversalBootstrapDemo`protocol witness for _ChannelOutboundHandler.triggerUserOutboundEvent(context:event:promise:) in conformance HTTPRequestEncoder at <compiler-generated>:0
    frame #14: 0x00000001002e3e10 UniversalBootstrapDemo`ChannelHandlerContext.invokeTriggerUserOutboundEvent(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:1470:29
    frame #15: 0x00000001002e944f UniversalBootstrapDemo`ChannelHandlerContext.triggerUserOutboundEvent(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:1289:26
    frame #16: 0x00000001002d02b1 UniversalBootstrapDemo`_ChannelOutboundHandler.triggerUserOutboundEvent(context=<unavailable>, event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelHandler.swift:265:17
    frame #17: 0x00000001003065cd UniversalBootstrapDemo`protocol witness for _ChannelOutboundHandler.triggerUserOutboundEvent(context:event:promise:) in conformance <> ByteToMessageHandler<A> at <compiler-generated>:0
    frame #18: 0x00000001002e3e10 UniversalBootstrapDemo`ChannelHandlerContext.invokeTriggerUserOutboundEvent(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:1470:29
    frame #19: 0x00000001002e3ea8 UniversalBootstrapDemo`ChannelHandlerContext.invokeTriggerUserOutboundEvent(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:1472:24
    frame #20: 0x00000001002e283f UniversalBootstrapDemo`ChannelPipeline.triggerUserOutboundEvent0(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:797:30
    frame #21: 0x00000001002e2653 UniversalBootstrapDemo`ChannelPipeline.triggerUserOutboundEvent(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at ChannelPipeline.swift:717:13
    frame #22: 0x00000001002ce65a UniversalBootstrapDemo`Channel.triggerUserOutboundEvent(event=<unavailable>, promise=<unavailable>, self=<unavailable>) at Channel.swift:221:18
    frame #23: 0x00000001004caaa7 UniversalBootstrapDemo`protocol witness for ChannelOutboundInvoker.triggerUserOutboundEvent(_:promise:) in conformance NIOTSConnectionChannel at <compiler-generated>:0
    frame #24: 0x00000001004c1ec5 UniversalBootstrapDemo`closure #1 in NIOTSConnectionBootstrap.connect(channel=<unavailable>, promise=<unavailable>, endpoint=<unavailable>) at NIOTSConnectionBootstrap.swift:193:21
    frame #25: 0x00000001004c2ad8 UniversalBootstrapDemo`closure #3 in closure #2 in NIOTSConnectionBootstrap.connect(conn=<unavailable>, connectAction=<unavailable>, self=<unavailable>) at NIOTSConnectionBootstrap.swift:214:17
    frame #26: 0x000000010029c23c UniversalBootstrapDemo`thunk for @escaping @callee_guaranteed () -> (@owned EventLoopFuture<()>) at <compiler-generated>:0
    frame #27: 0x00000001003375b2 UniversalBootstrapDemo`closure #1 in EventLoopFuture.flatMap<Value>(self=<unavailable>, callback=<unavailable>, next=<unavailable>) at EventLoopFuture.swift:470:31
    frame #28: 0x0000000100337e63 UniversalBootstrapDemo`EventLoopFuture._addCallback(callback=<unavailable>, self=<unavailable>) at EventLoopFuture.swift:663:16
    frame #29: 0x0000000100337fad UniversalBootstrapDemo`EventLoopFuture._whenComplete(callback=<unavailable>, self=<unavailable>) at EventLoopFuture.swift:670:18
    frame #30: 0x000000010033722b UniversalBootstrapDemo`EventLoopFuture.flatMap<Value>(file=<unavailable>, line=<unavailable>, callback=<unavailable>, self=<unavailable>) at EventLoopFuture.swift:467:14
    frame #31: 0x00000001004c252b UniversalBootstrapDemo`closure #2 in NIOTSConnectionBootstrap.connect(channelOptions=<unavailable>, conn=<unavailable>, initializer=<unavailable>, connectAction=<unavailable>, self=<unavailable>) at NIOTSConnectionBootstrap.swift:212:15
    frame #32: 0x00000001004c3ba7 UniversalBootstrapDemo`partial apply for closure #2 in NIOTSConnectionBootstrap.connect(_:) at <compiler-generated>:0
    frame #33: 0x00000001003279b3 UniversalBootstrapDemo`thunk for @escaping @callee_guaranteed () -> (@owned EventLoopFuture<A1>, @error @owned Error) at <compiler-generated>:0
    frame #34: 0x000000010032f5d6 UniversalBootstrapDemo`partial apply for thunk for @escaping @callee_guaranteed () -> (@owned EventLoopFuture<A1>, @error @owned Error) at <compiler-generated>:0
    frame #35: 0x0000000100327696 UniversalBootstrapDemo`closure #1 in EventLoop.submit<Self>(promise=<unavailable>, task=<unavailable>) at EventLoop.swift:488:37
    frame #36: 0x000000010032a1e0 UniversalBootstrapDemo`thunk for @escaping @callee_guaranteed () -> () at <compiler-generated>:0
    frame #37: 0x00007fff69d052b9 libdispatch.dylib`_dispatch_block_async_invoke2 + 83
    frame #38: 0x00007fff69cf9658 libdispatch.dylib`_dispatch_client_callout + 8
    frame #39: 0x00007fff69cfec44 libdispatch.dylib`_dispatch_lane_serial_drain + 597
    frame #40: 0x00007fff69cff609 libdispatch.dylib`_dispatch_lane_invoke + 414
    frame #41: 0x00007fff69cfeaf6 libdispatch.dylib`_dispatch_lane_serial_drain + 263
    frame #42: 0x00007fff69cff609 libdispatch.dylib`_dispatch_lane_invoke + 414
    frame #43: 0x00007fff69d08c09 libdispatch.dylib`_dispatch_workloop_worker_thread + 596
    frame #44: 0x00007fff69f53a3d libsystem_pthread.dylib`_pthread_wqthread + 290
    frame #45: 0x00007fff69f52b77 libsystem_pthread.dylib`start_wqthread + 15

If possible, minimal yet complete reproducer code (or URL to code)
[anything to help us reproducing the issue]
SwiftNIO version/commit hash
2.20.2
Swift & OS version (output of swift --version && uname -a)
Apple Swift version 5.2.4 (swiftlang-1103.0.32.9 clang-1103.0.32.53) Target: x86_64-apple-darwin19.6.0 Darwin MiniII.lan 19.6.0 Darwin Kernel Version 19.6.0: Sun Jul  5 00:43:10 PDT 2020; root:xnu-6153.141.1~9/RELEASE_X86_64 x86_64

This is actually a Network.framework issue. You can reproduce this crash with no NIO code at all:
import Foundation
import Dispatch
import Network

let endpoint = NWEndpoint.hostPort(host: "", port: 80)
let connection = NWConnection(to: endpoint, using: .tcp)
connection.stateUpdateHandler = { state in
    print(state)
}

let q = DispatchQueue(label: "connectionQueue")
connection.start(queue: q)
dispatchMain()

As it's an easy-enough-to-detect issue we can work around it, which we will do, but I also recommend filing a FeedbackAssistant report with the above code if you can verify the crash.

See apple/swift-nio-transport-services#103.

Oh, indeed, your code sample crashes as well. I filed a report through FeedbackAssistant: FB8347519.

Resolved in the new release of swift-nio-transport-services.

authors: Lukasa lanurmi

repo: apple/swift-nio


text:
Dependencies Unavailable to Plugins

Description
Adding local target dependencies or external dependencies to my plugin doesn't result in an error when declared in the package manifest. However, importing these dependencies in the plugin code makes SwiftPM complain that it can't find these modules.
Expected behavior
I'd expect to declare dependencies and be able to actually import them.
Actual behavior
An error is emitted when importing a module that was declared as a dependency in the plugin code. This is the case for both build tools and command tools.
Steps to reproduce

Create a TestPackage directory, cd into it, and run swift package init.
Add the following target in the package manifest: .plugin(name: "MyPlugin", capability: .buildTool(), dependencies: [.target(name: "TestPackage")]),

Create a Plugins/MyPlugin/Plugin.swift containing:import TestPackage
import PackagePlugin

@main
struct Plugin: BuildToolPlugin {
    func createBuildCommands(context: PackagePlugin.PluginContext, target: PackagePlugin.Target) async throws -> [PackagePlugin.Command] {
        []
    }
}

Swift Package Manager version/commit hash
Swift Package Manager - Swift 5.7.0
Swift & OS version (output of swift --version && uname -a)
swift-driver version: 1.55.1 Apple Swift version 5.7 (swiftlang-5.7.0.113.202 clang-1400.0.16.2)
Target: arm64-apple-macosx13.0
Darwin Filip-MacBook-Air.local 22.0.0 Darwin Kernel Version 22.0.0: Tue May 24 20:30:32 PDT 2022; root:xnu-8792.0.50.111.3~5/RELEASE_ARM64_T8103 arm64

@abertelrud are missing validation here?

Yes, I think so.  This isn't currently supported and thus there should be up-front validation.  In the long run we should make it work, but that will require some build system changes (we either have to be able to do parts of the build before plugins run, or interleave running plugins are part of the build).

authors: abertelrud filip-sakel tomerd

repo: apple/swift-package-manager


text:
Warning 'Hashable.hashValue' is deprecated on Swift 4.0

macOS 10.14.4
Xcode 10.2.1 Build version 10E1001
Swift 4.0
1.1.2 (but looks like the same issue will be reproducible on the latest 1.5.0 version too)
'Hashable.hashValue' is deprecated as a protocol requirement; conform type 'My_Object' to 'Hashable' by implementing 'hash(into:)' instead

When compiling my project I receive many warnings:
'Hashable.hashValue' is deprecated as a protocol requirement; conform type 'My_Object' to 'Hashable' by implementing 'hash(into:)' instead

So my question - is there are any reasons to use the old hashValue function on Swift 4.0? Because I've changed #if swift(>=4.2) to #if swift(>=4.0) for example in the Message.swift class (and some other classes) and all works correctly and Xcode warnings was gone. So why not to fix it in future versions? If you agree with that - I will send PR. Thank you for your response!

Os there a reason you are using Swift 4 instead of 4.2 or 5?  If you move your Swift language version up the issue should go away.
That warning also sound like it might be mistake/bug on the compiler side.  https://github.com/apple/swift-evolution/blob/master/proposals/0206-hashable-enhancements.md says the changes went into Swift 4.2.  It may that since your are using the 5.0 toolchain in 4.0 mode, it is providing a false signal; but if you used a real 4.0 toolchain, it wouldn't know about the hashing changes.

Great, @thomasvl thank you for explanation!
P.S. There are many local dependencies that was written on Swift 4 so we are still using it..

P.S. There are many local dependencies that was written on Swift 4 so we are still using it..

Since the 4.x range, you should be able to mix language versions, i.e. - one dependency can be compiled with 4, but you can compile with 4.2 or 5 just fine.  https://docs.swift.org/swift-book/GuidedTour/Compatibility.html

Yep, we should check this
Thank you!

repo: apple/swift-protobuf


text:
Remove recover methods from the parser

Instead of sticking unexpected tokens into errorTokens of a CodeBlock, we should be putting them into the tree as unexpected nodes, where they can be diagnosed. These unexpected nodes are typically created by Parser.expect calls.

@swift-ci Please test

https://github.com/apple/swift/pull/60847
@swift-ci Please test

@swift-ci Please test

repo: apple/swift-syntax


text:
[4.0] migrator: handle qualified replacement for member reference expression. rdar://32845918

Previously, we only handle dot syntax call expression for qualified
replacement, i.e. changing from A.a to B.b. This patch teaches the tool
to handle the migration of member reference expression tool.

@swift-ci please test

repo: apple/swift


text:
Fixes two compile time problems which came up with the DoubleWidth benchmark

Remove an assertion from the Projection constructor to avoid bad corner-case compile times.

Cache the substituted types in the TypeSubstCloner.

Both changes give a 5x compile time improvement (for an assert compiler). But the compile time is still bad: ~3.5 min
rdar://problem/36887449

@swift-ci smoke test and merge


text:
[Serialization] Mark decls that can never be cross-referenced

This allows us to filter them out in cases that would otherwise be ambiguous. The particular prompting situation looks a lot like the test case: a protocol, plus a forward-declared class with the same name. (Normally we ignore forward-declared classes, but SourceKit's module interface generation feature makes dummy ClassDecls for them instead.)
SR-4851, plus possibly other SourceKit crashes in ModuleFile::readConformance.

@swift-ci Please test

@swift-ci Please test source compatibility

That was the idea, yeah. If you'd prefer a bit I can switch to that, but since most decls won't have it I didn't want to claim the space forever.


text:
Make sure the code completion takes both private imports and testable

imports into account separately.

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 2ac6cda9a77843022c67d5c6d323e216256d3deb

Build failed
Swift Test OS X Platform
Git Sha - 2ac6cda9a77843022c67d5c6d323e216256d3deb

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 2ac6cda9a77843022c67d5c6d323e216256d3deb

Build failed
Swift Test OS X Platform
Git Sha - 2ac6cda9a77843022c67d5c6d323e216256d3deb

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - ca686325e2a16636792de8bdb86f01b4f2f6bba2

Build failed
Swift Test OS X Platform
Git Sha - ca686325e2a16636792de8bdb86f01b4f2f6bba2

@swift-ci Please smoke test

authors: aschwaighofer swift-ci


text:
uniquely allocate AutoDiffParameterIndices and AutoDiffAssociatedFunctionIdentifier

Resolves https://bugs.swift.org/browse/SR-9428.

@swift-ci please test tensorflow

@rxwei, I have deleted isMethodFlag from the indices.
@swift-ci please test tensorflow

@swift-ci please test tensorflow

Additional comments (which need not be addressed in the short term):

It seems that this data structure can also be used for SIL for consistency and efficiency, especially when it no longer carries the isMethod flag.
Since we need to represent result selection in SIL functions using the same bit vector representation, would it make sense to rename this to AutoDiffIndexSet or AutoDiffIndexSelection?

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow linux gpu

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow linux

authors: marcrasi rxwei


text:
Need to specify compilers when building lldb

Simple tweak to build script so clang-cl is specified when building lldb on windows

The problem is that using clang-cl actually makes debugging lldb much harder.  Please add a note to that effect, and use the value clang-cl rather than the absolute path to clang-cl.

Ah I see, I assumed it was just a missing line in the code. It is probably fine to leave as in then, feel free to decline this pull request since I don't know the details of what you mean by "makes debugging lldb harder"

The debug info generated by clang is not as robust as the one built by Visual a studio, so you lose some of the expression evaluation and local variable information.  The PDB support in clang is improving but getting everything stable is the first goal (a small reduction in debugging after that won’t matter as much since you can try to find regressions and have the history to help you narrow down the changes).
I’m not opposed to the change, just think that it might be a good idea to explicitly call that out.

Looks like the documentation on master now has -DCMAKE_C_COMPILER=clang-cl, so I think that supersedes this PR, hence closing. Please feel free to re-open if closing this was a mistake!

authors: Phylliida compnerd varungandhi-apple


text:
Fix a case where vDSP is missing a cast

Also update availability information to use macOS instead of OSX, reorder CMakeLists.txt alphabetically, and rename ContiguousCollection.swift to AccelerateBuffer.swift.
Fixes rdar://problem/50076962

@swift-ci please smoke test


text:
EscapeAnalysis: handle SILUndef values

fixes a crash
rdar://problem/50279857

@swift-ci smoke test and merge

@compnerd I think this is the fix for what you were saying on the lldb bots.

authors: eeckstein gottesmm


text:
Change two instances where we are using strcmp to use == as a follow …

…up to #26158.

@swift-ci smoke test

@swift-ci smoke test and merge

@swift-ci smoke test and merge

@swift-ci smoke test and merge

@swift-ci smoke test and merge

Seems that #26158 might have affected the Windows builds (https://ci-external.swift.org/job/oss-swift-windows-x86_64/709/). I'm going to check if this fixes them or we need something else.
/cc @compnerd
@swift-ci please test Windows platform

@drodriguez I think the problem is that MSVC is being MSVC and doing stupid things around constexpr. The getPrefixed thing can just remove the constexpr.

authors: drodriguez gottesmm


text:
[Parse] Cleanup libSyntax type parsing

Using Parsed*SyntaxBuilder interface and SyntaxParserResult unnecessarily complicates Parser code. Use SyntaxParsingContext based node creation instead.
No behavior change.

@swift-ci Please smoke test

@swift-ci Please smoke test Windows


text:
Update CHANGELOG.md: "Swift Next" -> "Swift 5.4"

https://forums.swift.org/t/swift-5-4-release-process/41936

@swift-ci Please smoke test


text:
[Concurrency] Make Job/AsyncTask minimally compatible with dispatch object layout

Create a TargetDispatchClassMetadata for Swift metadata that also has a dispatch-compatible vtable. Dispatch leaves room for ObjC class metadata so the two regions don't overlap. (The vtable currently consists of a single dummy entry; this will be filled out later.)
Rearrange the Job and AsyncTask hierarchy so that AsyncTask inherits only from Job, which in turn inherits from HeapObject. This gives all Job instances a dispatch-compatible isa field. It also gives them a refcount word, which is wasted on instances that aren't AsyncTask instances. Maybe we can find some use for that space in the future.
rdar://75227953

Just double checking, this won't impact any of the later fragments of the AsyncTask right?

@ktoso Shouldn't affect anything like that. AsyncTask still has the same layout as before, it's just achieved without multiple inheritance now.

Thanks for clarifying Mike :)

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - bd62fdb2db235a8c5c68f326b3eed5a233275a4a

@swift-ci please test linux platform

@swift-ci please test windows platform

Build failed
Swift Test Linux Platform
Git Sha - bd62fdb2db235a8c5c68f326b3eed5a233275a4a

@swift-ci please test linux platform

Build failed
Swift Test Linux Platform
Git Sha - bd62fdb2db235a8c5c68f326b3eed5a233275a4a

@swift-ci please clean test linux platform

authors: ktoso mikeash swift-ci


text:
Cleaned up comments, variable names, and string messages.

What's in this pull request?
A cleanup of comments, variable names, and string messages in stdlib/public/core/Algorithm.swift.
Some of these changes are opinion based, others aim at improving consistency, and a few curate erroneous information.

@natecook1000 @amartini51 Could you review, please?

@natecook1000 Thanks for the feedback. I fixed the changes accordingly :)

@CodaFi So I changed "construct" to "initialize", as I thought it would fit the Swift terminology (of writing "initializers" instead of "constructors"). But if "create" is the standard, as @rintaro points out, it'll make most sense to call it that.

@marcusrossel Could you give this one last rebase?

@CodaFi This may sound stupid, but I'm quite inexperienced with git and can't figure out how to rebase for the life of me.
I tried cloning the repository to my computer -> switching to my branch -> adding a remote -> fetching from apple/swift -> rebasing. This process never ended up working though.
Would it be ok if I closed this PR? and added all of the changes in a single commit in a new PR?

@marcusrossel That's probably the best route forward, as there have recently been documentation changes for some of these symbols. Please take a look and see where your changes still apply in a new branch. Thanks again for your interest in contributing!

@natecook1000 I see. Where are these changes documented?

You should see them in Algorithms.swift when you update to the latest.

authors: CodaFi gribozavr marcusrossel natecook1000


text:
CrossModuleOptimization: don't serialize functions referencing imported C functions/variables

Imported C functions and variables are not necessarily public in their modules.
rdar://100874714

@swift-ci smoke test


text:
[Observation] Refine the macro implementation for Observable

This alters the macro emission for @Observable to:
better handle initialization
produce sensible diagnostics when inferred types are used for properties
produce sensible diagnostics when actors are marked as @Observable
better names for member variables and types to avoid conflicting with users of @Observable

@swift-ci please test

@swift-ci please test


text:
[Requirement Machine] Implement same-element requirements.

SE-0393 supports same-element requirements. From the proposal:

A same-type requirement where one side is a type parameter pack and the other type is a scalar type that does not capture any type parameter packs is interpreted as constraining each element of the replacement type pack to the same scalar type:
func variadic<each S: Sequence, T>(_: repeat each S) where repeat (each S).Element == T {}

This is called a same-element requirement.

We represent pack elements in the requirement machine through a new singleton PackElement symbol, written [element]. Same-element requirements are mapped to re-write rules that prefix type parameter pack terms with the [element] symbol.
For example, given a protocol P with an associated type A, the generic signature <each T, U> where repeat each T: P, repeat (each T).A == U maps to the following re-write system:
Rewrite system: {
- [P].[P] => [P]
- [P].A => [P:A]
- [P].[P:A] => [P:A]
- [P:A].[shape] => [shape]
- τ_0_1.[shape] => [shape]
- each τ_0_0.[P] => each τ_0_0
- [element].each τ_0_0.A => τ_0_1
- each τ_0_0.A => each τ_0_0.[P:A]
- [element].each τ_0_0.[P:A] => τ_0_1
- [element].each τ_0_0.[shape] => [shape]
}

The implementation is gated behind -enable-experimental-feature SameElementRequirements because the minimal conformance computation doesn't yet support same-element requirements. The current rewrite rules also do not support deriving pack element conformance from a scalar type parameter conformance through same-element requirements. For example, the generic signature <each T, U> where U: P, repeat each T == U maps to the following rewrite system:
Rewrite system: {
- [P].[P] => [P]
- [P].A => [P:A]
- [P].[P:A] => [P:A]
- [P:A].[shape] => [shape]
- τ_0_1.[shape] => [shape]
- τ_0_1.[P] => τ_0_1
- [element].each τ_0_0 => τ_0_1
- τ_0_1.A => τ_0_1.[P:A]
}

The conformance rule τ_0_1.[P] => τ_0_1 and the same-element rule [element].each τ_0_0 => τ_0_1  do not provide a rewrite path to the pack conformance rule each τ_0_0.[P] => each τ_0_0. One possible solution is to use element symbols for all property rules, which would also allow the minimal conformance support to fallout naturally. However, this approach poses a problem for same-type-pack requirements. If we use [element] symbols for same-type-pack requirements, e.g. [element].each τ_0_0 => [element].each τ_0_1, then this rule no longer implies a same-shape rule each τ_0_0.[shape] => each τ_0_1.[shape]. Stripping the [element] symbols from same-type-pack rewrite rules creates a different set of problems for conformances, because the pack conformance rules contain [element] symbols, which would prohibit applying associated type rewrite rules to non-element pack terms. I'm still exploring strategies for resolving these issues, hence the experimental flag!

@swift-ci please smoke test

@swift-ci please smoke test

This is subsumed by https://github.com/apple/swift/pull/70227


text:
Improve API docs to provide more general background

Hi guys,
As some developers go straight to the API docs - there should be some general information and examples there.
We do have this concept for some of the modles, but can definitely improve others: IC, AC.
We should at least add a link in every model's main API page to the relevant page in the user guide.
Also - in some cases, we do have model description - but it's under the model's create() method, and not in the model's main page. Maybe it should be in both?

Merging this with documentation redesign https://github.com/apple/turicreate/issues/546

authors: afranklin igiloh

repo: apple/turicreate


text:
[Bug]: Insert query fails in mysql crud pages

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Insert query fails in mysql crud pages

Steps To Reproduce

Generate a My sql crud page
Now click on insert button
Add  data in the input fields
click on submit button
There is not action performed and the queries fails

Public Sample App
No response
Version
release

This doesn’t seem to be related to frontend hence unassigning myself.

@Nikhil-Nandagopal have we made updates in the CRUD page template? I'm seeing the JSON form widget is used in the update and insert form. This is causing the issues as queries are updating the fields partially or failing completely. Can we please revert that change for now as backend will also need some change in how the replacement logic is handled in the queries.

Reverted the changes so this should be working when it's deployed in 30 mins

the issue is resolved now

authors: Nikhil-Nandagopal RakshaKShetty Rishabh-Rathod abhvsn

repo: appsmithorg/appsmith


text:
[Bug]: On forking an app with the mongo we get an error, and are unable to fork

On forking an app with the above connection string URI set to Yes, we get an error, and are unable to fork with this setting. [Workaround, with the use connection string set to no, and all details entered, we can proceed with forking]

Originally posted by @btsgh in https://github.com/appsmithorg/appsmith/issues/24660#issuecomment-1598338428

This issue has been resolved with the the 24683 fix.


text:
[Bug]: Statbox widget has inconsistent min heights

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When dragging and dropping a statbox widget, the min-height for auto height is set to 14 rows. For Container widgets the default min height is 9 rows.
When switching the value of the height property from Fixed to Auto Height -- for the statbox widget -- the min-height is reset to 9 rows.
Due to the above reasons:

When we delete the bottom few widgets in a freshly dropped statbox widget, the statbox widget's height doesn't go below 14 rows, leaving a lot of white space at the bottom of the widget
However, if we toggle the height property of the statbox widget, the widget now properly collapses to a minimum of 9 rows.

This inconsistent behaviour is unexpected.
The reason this logic was intentionally put in to the Statbox widget, is due to the way Auto Height works.
When we first drop a statbox widget.

Widget is rendered
Widget triggers an auto height update
Widget changes height based on the auto height computations

The three steps above causes a "flicker" when we first drop the widget, as the widget height changes. To mitigate this, we added a default min-height of 14 rows to the statbox widget.
Steps To Reproduce

Drop a fresh statbox widget
Delete 2 or 3 of the bottom most widgets in the statbox widget
Notice that the height doesn't change
Toggle the "height" property of the statbox widget to "Fixed", then back to "Auto Height"
The statbox widget collapses appropriately to get rid of the white space at the bottom.

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud and Self hosted - 1.9.44

Hello, I'm interested in contributing to Appsmith and would like to work on fixing this bug. Could I take this issue?

Hi @LuisVicenteCorreia!
As this effect was intentional (as mentioned in the issue description) I'm afraid that this issue needs a product exploration in the team to resolve and will not be open for external contribution.
If you haven't contributed to Appsmith earlier, I would encourage you to take a look at some of the issues with the label: "good first issue".

@LuisVicenteCorreia
To consistently replicate the flicker issue we need to try dropping the statbox widget in different viewport editors. When the viewport width changes the "auto height" feature adapts the contents of the statbox widget and causes it to re-render with a different height.
Any value that we use that is larger than 9 will have this issue.
Thanks for sharing the fix for the original issue. We'll review it.

authors: LuisVicenteCorreia riodeuno


text:
Fix button variant control in the property pane

I would like to work on this issue please assign it to me

@KelvinOm Can you please provide some info on how to recreate this issue?

@sans-byte Thank you for your willingness to contribute. I'm sorry, but we're talking about components that are used under  feature flag. Fixing this issue may not be as easy as it seems. Could you please look at Good First Issue list and choose something there?

authors: KelvinOm sans-byte


text:
Fix focus retention of tabs while switching between IDEs

When you switch between IDEs, the old IDE loses the focus retention of tabs. For example, you're on app editor and on page 2, with 6 queries/apis open (tabs). Now, you switch to home screen and open a package editor, and then back to the app editor, the opened page as well as its open tabs are no longer retained.
This also happens when you simply move from editor to homepage and back to editor. Another scenario this happens is on page refresh. And yet another one, if you try to connect and authorize a Google spreadsheet as a datasource, once you are back on the app editor after authorisation is complete, the opened tabs are no longer retained (open bug #31590)
This needs to be fixed by maybe using local storage or you can explore other solutions.
Also, handle the state that maintains which tabs are open so that when user switches between say data and editor tabs in the sidebar, the open entities should remain open. The focus retention across IDEs will be handled in another task.

Hey team! Please add your planning poker estimate with Zenhub @alex-golovanov @ankitakinger

authors: ankitakinger hetunandu


text:
[Bug]: The empty space is clickable when the user edits the App name or the organisation name

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
It is observed that form the homepage when the user tries to edit the application name or the organization name by clicking on the pencil icon and after editing the name when the user clicks on the empty space(where the pencil icon was displayed initially) the changes gets saved.
Expected result:
Clicking on pencil icon should show save icon and cancel icon so that user may click on save icon to make the changes or cancel icon to un-save changes
Actual result:
Currently empty space is displayed and which is clickable

Steps To Reproduce
1.Launch appmsith app in release or prod environment
2.From the homepage click on the three dots from any existing app or the organization name
3.click on the pencil icon
4.Edit the name and click on the empty space - where the pencil icon was displayed initially and observe
Environment
Production
Version
Cloud

Hi @YogeshJayaseelan, @Nikhil-Nandagopal, @riteshkew
I would like to work on this issue, I am planning to add tick icon for save and cross icon for cancel. Is it fine or do you give any suggestions or refer any icons or buttons i could use in place of save and cancel.

@Sai6347 This does not seem like an icon issue but more of how the \div containing the icon was defined.

@Sai6347 This does not seem like an icon issue but more of how the \div containing the icon was defined. Please go ahead if you are planning to look into this issue. Do reference the PR to this issue for better tracking.

@riteshkew ok thanks for confirmation, i will work on it.

Hi @riteshkew, can you please review this PR or assign someone to review it.

authors: Sai6347 YogeshJayaseelan riteshkew


text:
fix: Widget pane not closing when switching from canvas

Description
Fixed issue in widget pane, was not closing when navigate to Datasource page via omnibar.
Fixes #9194
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Tested navigation from omnibar
Tested navigation from run query in property pane.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/9194-widget-pane-switching-issue

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
55.07 (0.01)
36.57 (0.01)
34.52 (0.01)
55.58 (0.01)

:green_circle:
app/client/src/pages/Editor/WidgetsEditor/CanvasContainer.tsx
96.77 (0.77)
66.67 (0)
100 (0)
96.77 (0.77)

:green_circle:
app/client/src/utils/WorkerUtil.ts
89.76 (0.78)
72.55 (1.96)
100 (0)
93.33 (0.95)

/ok-to-test sha=0653410

/ok-to-test sha=0653410

/ok-to-test sha=0653410

/ok-to-test sha=0653410


text:
fix: Fixed test MongoDB datasource shows ok even if there is no database matching the name in the 'Default Database Name' input

Description
Test MongoDB datasource shows ok even if there is no database matching the name in the 'Default Database Name' input.
Fixes #11214
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Test case MongoPluginTest.testDatasourceFailWithInvalidDefaultDatabaseName()  is added
Tested manually

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=161ec76


text:
fix: Fix cancel issue and form value state persistence

This PR fixes two things

The cancel button not showing the dialog after a change has been made.
The fields in the datasource form retaining values changed by the user without the user saving those changes.

Fixes #25333

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] Jest
[x] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/build-deploy-preview skip-tests=true

/ok-to-test

/ok-to-test

/build-deploy-preview skip-tests=true

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


text:
chore: move orientation and label position to content tab"

Fixes #29428

Summary by CodeRabbit

New Features

Introduced new configuration options for widget orientation and label position, allowing users to customize their widgets to be either horizontal or vertical and to position labels on the left or right.

Refactor

Simplified the property pane configurations by removing unused style configurations, streamlining the setup for users.

Chores

Cleaned up widget configuration code for Checkbox Group, Radio Group, and Switch Group widgets to enhance maintainability and user experience.

/build-deploy-preview

Yes! Definitely for checkbox / radio buttons. For switches convention is a bit less defined, but keeping it same as others helps when building an app, I think.

/build-deploy-preview

@ichik @KelvinOm Change the default of label position as right for all three of them.

@ichik @KelvinOm Changed the default value of label position as right for all three of them. 👍

We have to change this for switch and checkbox as well.

Yes

authors: KelvinOm ichik jsartisan


text:
chore: Hide hidden columns from table in preview mode

PR fixes following issue(s)
Fixes https://github.com/appsmithorg/appsmith/issues/15639
Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test tags="@tag.Table"

@sbalaji1192 we don't need tests here?

@somangshu We are not adding any functionality. Updated a condition with an existing variable.


text:
Moving markers without redrawing whole map

Is there a way to change marker position? We would like to show user's current position and update it regularly. I noticed current location is on the roadmap, I just wonder if there is some workaround. My another idea was to make the location dot a separate widget on top of the map and update its location with MapController. Any ideas?

Also, marker grouping would be nice, and I think more control over the markers would solve this too.

You can do this just by changing the marker locations passed to the widget in a setState().  No need to use the controller for this, since the MarkerLayer widget is stateless.

@maral Did that work for you?

awesome 😎

authors: johnpryan maral


text:
Class based source readers?

Currently, there is a single general Reader class with various methods for different sources.
I wonder if a series of specific classes for different filetypes be better e.g. Reader23andMe, ReaderAncestry, etc. Still keeping the single Reader class overall, but delegating a lot of the details to the specific classes for implementation.
By grouping everything for a particular format together it makes it easier to read, and to add extra sources. Also it would allow subclasses (e.g. for Global Screening Array based sources) to abstract functionality more easily.

Thanks @afaulconbridge, this is a great idea. Since several read functions use the same parser, I wonder if the top level Reader class should implement the parser functions?

authors: afaulconbridge apriha

repo: apriha/snps


text:
Auto commenting on issues and self assign

I'll create a workflow for auto commenting on issues and self assigning the issue to the contributor if he or she wants to contribute to the issue.
This will give updates to the user and will give him green flag to start working on the issue.
This will be very helpful for the project manager too.

please assign this issue to me under gssoc

Actually I don' want this Self assigning workflow in my repo.
But you can instead make a Github action greeting which will show/pop up whenever the contributor will open an issue or PR

Yesh sorry about that
and the level label?

license: MIT


text:
Fix warnings from Link component

React didn't like the way this component was mutating this.props.

Thank you again @chadoh

authors: apzentral chadoh

license: mit


text:
feat: add nikolaydubina/go-cover-treemap

nikolaydubina/go-cover-treemap: 🎄 Go code coverage to SVG treemap

Thank you!

v4.21.0 is out 🎉
https://github.com/aquaproj/aqua-registry/releases/tag/v4.21.0

authors: iwata suzuki-shunsuke

repo: aquaproj/aqua-registry


text:
Revert "Support for KE helm install 5.3"

This commit shouldn't be part of 5.0 as the changes made are specific to 5.3. Some branching error the commit ended up in 5.0 branch.
Also, this PR contains
When Kube-Enforcer is unavailable users are facing issues in creating application workloads in k8s cluster. So adding an explicit ignore policy for webhooks on request failure.
Also, updated README.md to adjust the path on certificate generation.
@kenmccann @niso120b
This reverts commit 3dee91ec4b45d84682dc528c3f15d8bff754f760.

Talked to Vinee,
This PR was tested
Has low risk and as no impact on documentation.

repo: aquasecurity/aqua-helm


text:
adding attribute ogit/access-control

This initial discussion of this attribute was for it to be ogit/public meaning
public read-only access to the node. However on creating this pull-request I
realised that abstracting this into an ACL value would provide applications more
flexibility than a binary public/not public.
I did struggle with the node name, access-control-list seemed execessively
verbose, acl seemed like too much of a contraction/intialism, and access
seemed too vague.

I have made the changes as requested, however the documentation for how to name objects in OGIT is out of date (https://github.com/arago/OGIT/blob/master/SGO/format/README.md) - it requires the first character of an attribute to be lowercased (as with pretty much all existing attributes - they are almost exclusively in lowerCamelCase).

The guidelines are reworked at the moment. Sorry for the confusion.

Sorry for the confusion. Attributes begin with lower case. The new guidelines are here.
https://github.com/arago/OGIT/blob/master/SGO/format/README.md
"7. Guidelines of OGIT ontology" at the main page of github page.

authors: plarem thechriswalker

repo: arago/OGIT


text:
Memory leak at Web UI

My Environment

ArangoDB Version: 3.6.5
Storage Engine: RocksDB
Deployment Mode:  Single Server
Deployment Strategy:  ArangoDB Starter in Docker
Configuration:
Infrastructure:
Operating System: Container in docker
Total RAM in your machine:   16
Disks in use:  SSD
Used Package:

Steps to reproduce

Open Web ui
Leave the tab open for a few days

Problem:

Expected result:
I think it should use less memory

Hi,
the problem originates with the graphs on the main page.
If you i.e. open the query tab and press f5 it stops.

I understand, that if I reload page, problem'll dissapear :)
I only wanted to designate the problem

authors: aunikitin dothebart

repo: arangodb/arangodb


text:
Question,How to use  search with languages Polish and Ukrainian

Have a. question, in support languages, cant found Polish and Ukrainian - how I can add it -  or how to search using full-text search for these languages.
Thanks

Hi,
Please refer to this ticket about adding stemmers etc.

closing as solved duplicate

authors: dothebart menesty


text:
On kubernetes cluster 2 of the 5 DBServers does not start

My Environment

ArangoDB Version:        3.8.1
Storage Engine:             RocksDB
Deployment Mode:       Cluster
Deployment Strategy:   Kubernetes
Configuration:               5 nodes
Infrastructure:               own
Operating System:        Ubuntu 20.04 nodes on rancher kubernetes cluster
Total RAM in your machine:        52 GB on cluster - 0.9% usage for arangodb
Disks in use:        669 GB on cluster - very low usage for now for arangodb
Used Package:              Ubuntu .deb

Component, Query & Data
Affected feature: Cluster nodes on Kubernetes
Dataset: No problem with the dataset, DB is working fine with 3 active nodes.
Size of your Dataset on disk: very low usage
Replication Factor & Number of Shards (Cluster only):

Steps to reproduce
I don't know exactly the reason but I suspect that may be due to sudden electrical power off on the physical servers.
Problem:
Two DBServers are not starting and keep trying forever.
The pods are giving an error that may indicate some corrupted database data (maybe).

Expected result:
To be able to reset nodes, or remove them to be able to grow the number of dbservers again.
It should be great to be able to do it from the arangodb web interface, however, any information about another way of doing it will help me for now.

the ENGINE file is supposed to contain rocksdb - as you can see in the errormessage.
So one could try whether setting the content in this file is enough, or whether one needs to re-create the node and sync it in from the replicas.
If you use dynamic PVCS you should be able to delete the respective ones, and let the operator re-create them.
Which PVCS do you use in first place?

Thank you for the answer. Yes, this other repository seems more accurate for this issue. I will create it.
For the PVC I'm using Longhorn as StorageClass. The filesystem is ext4 on Kubernetes nodes.
I've tried deleting the PVCs and corresponding DBServer PODs (cluster-prmr), now I have 1 node issue instead of 2.
The problem now is for one PVC when I delete it, it is automatically created again so the node planning keeps halting, I can not abort the operation on the web interface. The DBServer POD is not created anymore, only de PVC is recreated.

the re-launched node is now catching up, getting shards back most probably, this may take a while until its green again. FS is good.

authors: dothebart frcuutn


text:
Horizontal scaling with number of databases

Hi, I'm reviewing Arangodb for a multi-tenant application. The official docs mentions that splitting by db is good for this use case but does not go into details on how it would scale.
How well does multiple databases on a single arango cluster scale horizontally? (thousands/ tens of thousands databases)
There's a older question on stackoverflow https://stackoverflow.com/questions/31392534/maximum-number-of-databases-in-arangodb that mentions some overhead but it's not clear to me if it would be per server or if it's shared evenly across the cluster (is a node that does not manage leader or replica for any collection shard  in a db does not need to store or open any threads/files related to that db).
Thanks

Hi,
Databases have collections that manage them. This is one of the overheads mentioned in that article.
These collections are split into shards which are randomly distributed across your DB-Server nodes of the cluster.
Also your multi-tennancy will bring a set of collections that each of your databases will have.
Especially in the cluster the MMFiles-Storage engine doesn't scale well on that, you should use Rocksdb.
Generally you should benchmark whether your servers can bear with the load pattern you want to apply.

Hi @cleaton,
Does the answer from dothebart clarify your queries on the horizontal scaling of databases?
Best,

authors: cleaton dothebart vinaypyati


text:
ArangoDB Starter --ownAddress ignores port argument

My Environment

ArangoDB Version:        3.3.19
Storage Engine:              MMFiles
Deployment Mode:        Cluster
Deployment Strategy:    ArangoDB Starter
Configuration:               3 virtual servers
Infrastructure:               own
Operating System:        CentOS 7
Used Package:              SUSE or RedHat .rpm

Steps to reproduce

arangodb --ownAddress localhost:4000

Problem:
arangodb binds to localhost:8528 as the following snippet from the output shows:
2018-11-07T10:43:30-05:00 |INFO| Starting arangodb version 0.13.7, build bdac926 component=arangodb
2018-11-07T10:43:30-05:00 |INFO| Relaunching service with id '176d3806' on localhost:4000:8528... component=arangodb
...
Expected result:
arangodb should bind to localhost:4000 as explained in https://docs.arangodb.com/3.3/Manual/Deployment/ArangoDBStarter.html#automatic-native-clusters

Hi @bgaechter,
Thanks for opening an issue. Unfortunately, the starter option --ownAddress that you are using to start the cluster is currently obsolete. Please use the latest option --starter.address and --starter.port to specify the address and port respectively.
arangodb --starter.address localhost --starter.port 4000

Please have a look to latest options by using arangodb --help. For more info you can refer to the latest documentation.
Thanks!

Hi @bgaechter
Just sending a followup, to check if you had the chance to read above Vinay's message? Did you try to use --starter.address instead ?
Please provide a feedback
Thanks

Hi @OmarAyo
Yes, I used --starter.address together with --starter.port and it works but it doesn't solve my problem. I need the coordinator to be available on that specific port while setting the port for the arangoDB starter only changes the port for the initial setup of the cluster. It would be nice to be able to do these kind of things with the helper.
However, I am running arangod with some parameters for now, which works for me.

Closing this as outdated with the availability of ArangoDB 3.7.

authors: OmarAyo bgaechter dothebart vinaypyati


text:
Feature/better rocksdb settings and metrics

Scope & Purpose
This PR makes some changes to the default settings we use with RocksDB, as well as adds some new options to allow greater tunability. The overall goal is to help users manage the memory usage of RocksDB a bit better. Some parameters were also added specifically with preventing write stalls in mind. For instance, there are new hidden options which allow to control the number of writer buffers on a per column family basis. This can make a great deal of sense, as it is common for the document family to use much more space and require more buffers than the vpack index family, for instance.

[ ] :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)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket number:
[ ] Design document:

Testing & Verification
(Please pick either of the following options)

[ ] This change is a trivial rework / code cleanup without any test coverage.
[x] The behavior in this PR was manually tested
[ ] This change is already covered by existing tests, such as (please describe tests).
[ ] This PR adds tests that were used to verify all changes:

[ ] Added new C++ Unit tests
[ ] Added new integration tests (e.g. in shell_server / shell_server_aql)
[ ] Added new resilience tests (only if the feature is impacted by failovers)

[ ] There are tests in an external testing repository:
[ ] I ensured this code runs with ASan / TSan or other static verification tools

Link to Jenkins PR run: https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13183/
Documentation

All new features should be accompanied by corresponding documentation.
Bugs and features should furthermore be documented in the CHANGELOG so that
support, end users, and other developers have a concise overview.

[ ] Added entry to Release Notes
[ ] Added a new section in the Manual
[ ] Added a new section in the HTTP API
[ ] Added Swagger examples for the HTTP API
[ ] Updated license information in LICENSES-OTHER-COMPONENTS.md for 3rd party libraries

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

https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13185/

https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13200/

https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13225/

https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13230/

https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/13233/


text:
BTS-1075: unify behavior of DOCUMENT() function with empty keys

Scope & Purpose
Backport of https://github.com/arangodb/arangodb/pull/17566/
Fixes https://arangodb.atlassian.net/browse/BTS-1075
BTS-1075: unify behavior of DOCUMENT() function with empty keys

[x] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[x] integration tests
[ ] resilience tests

[x] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[x] Backport for 3.10: this PR
[ ] Backport for 3.9: -
[ ] Backport for 3.8: -

Related Information

[ ] Docs PR:
[ ] Enterprise PR:
[x] GitHub issue / Jira ticket: https://arangodb.atlassian.net/browse/BTS-1075
[ ] Design document:

LGTM

authors: jsteemann markuspf


text:
FE 242, FE-244: bugfix - add support for cache fields, fix index name undefined

Scope & Purpose
adds support for fields -> cache , primarySort -> cache, and primaryKeySort options

[x] :hankey: Bugfix

Checklist

[x] Tests

[x] Manually tested

[x] :book: CHANGELOG entry made

Related Information
(Please reference tickets / specification / other PRs etc)

[x] GitHub issue / Jira ticket: https://arangodb.atlassian.net/browse/FE-242, https://arangodb.atlassian.net/jira/software/c/projects/FE/issues/FE-244

[x] https://jenkins01.arangodb.biz/job/arangodb-ANY-jslint/28546/


text:
fixes some graph data parsing issues, if format was not like it was e…

…xpected
e.g. non unique edge elements, which causes problems inside sigmajs library.

Jenkins
http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/1729/

authors: hkernbach mchacki


text:
Sometimes ETIMEDOUT when connecting to ArangoDB

I'm running a single ArangoDB (no cluster atm) in a Kubernetes cluster and everything works fine, but sometimes I'm having trouble connecting to my ArangoDB. I've a very simple application that looks like:
const arango = require('arangojs')

async function test () {
  const db = new arango.Database({
    url: 'http://<some-ip-addr>:8529',
    databaseName: 'somedb',
    auth: {
      username: 'root',
      password: 'mypassword'
    }
  })

  const col = db.collection('test')
  console.log('Exists:', await col.exists())
}

test()

When I start the application, I'm often getting the following error message:
(node:29612) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT <some-ip-addr>:8529
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:29612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:29612) [DEP0018] DeprecationWarning: Unhandled promise rejectio
ns are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:29612) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT <some-ip-addr>:8529
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
(node:29612) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

When I use try/catch around "await col.exists()" I'm getting the following error:
Error: connect ETIMEDOUT <some-ip-addr>:8529
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
  errno: -4039,
  code: 'ETIMEDOUT',
  syscall: 'connect',
  address: '<some-ip-addr>',
  port: 8529,
  request: <ref *1> ClientRequest {
    _events: [Object: null prototype] {
      response: [Function],
      timeout: [Function (anonymous)],
      error: [Function (anonymous)]
    },
    _eventsCount: 3,
    _maxListeners: undefined,
    outputData: [],
    outputSize: 0,
    writable: true,
    destroyed: false,
    _last: true,
    chunkedEncoding: false,
    shouldKeepAlive: true,
    _defaultKeepAlive: true,
    useChunkedEncodingByDefault: false,
    sendDate: false,
    _removedConnection: false,
    _removedContLen: false,
    _removedTE: false,
    _contentLength: 0,
    _hasBody: true,
    _trailer: '',
    finished: true,
    _headerSent: true,
    socket: Socket {
      connecting: false,
      _hadError: true,
      _parent: null,
      _host: null,
      _readableState: [ReadableState],
      _events: [Object: null prototype],
      _eventsCount: 8,
      _maxListeners: undefined,
      _writableState: [WritableState],
      allowHalfOpen: false,
      _sockname: null,
      _pendingData: 'GET /_db/_system/_api/collection/test HTTP/1.1\r\n' +
        'authorization: Basic <removed :-)>\r\n' +
        'content-type: text/plain\r\n' +
        'x-arango-version: 30400\r\n' +
        'Host: <some-ip-addr>:8529\r\n' +
        'Connection: keep-alive\r\n' +
        '\r\n',
      _pendingEncoding: 'latin1',
      server: null,
      _server: null,
      parser: null,
      _httpMessage: [Circular *1],
      [Symbol(async_id_symbol)]: 10,
      [Symbol(kHandle)]: null,
      [Symbol(kSetNoDelay)]: false,
      [Symbol(lastWriteQueueSize)]: 0,
      [Symbol(timeout)]: null,
      [Symbol(kBuffer)]: null,
      [Symbol(kBufferCb)]: null,
      [Symbol(kBufferGen)]: null,
      [Symbol(kCapture)]: false,
      [Symbol(kBytesRead)]: 0,
      [Symbol(kBytesWritten)]: 0
    },
    _header: 'GET /_db/_system/_api/collection/test HTTP/1.1\r\n' +
      'authorization: Basic <removed :-)>\r\n' +
      'content-type: text/plain\r\n' +
      'x-arango-version: 30400\r\n' +
      'Host: <some-ip-addr>:8529\r\n' +
      'Connection: keep-alive\r\n' +
      '\r\n',
    _keepAliveTimeout: 0,
    _onPendingData: [Function: noopPendingOutput],
    agent: Agent {
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      defaultPort: 80,
      protocol: 'http:',
      options: [Object],
      requests: {},
      sockets: [Object],
      freeSockets: {},
      keepAliveMsecs: 1000,
      keepAlive: true,
      maxSockets: 3,
      maxFreeSockets: 256,
      scheduling: 'fifo',
      maxTotalSockets: Infinity,
      totalSocketCount: 1,
      [Symbol(kCapture)]: false
    },
    socketPath: undefined,
    method: 'GET',
    maxHeaderSize: undefined,
    insecureHTTPParser: undefined,
    path: '/_db/_system/_api/collection/test',
    _ended: false,
    res: null,
    aborted: false,
    timeoutCb: null,
    upgradeOrConnect: false,
    parser: null,
    maxHeadersCount: null,
    reusedSocket: false,
    host: '<some-ip-addr>',
    protocol: 'http:',
    [Symbol(kCapture)]: false,
    [Symbol(kNeedDrain)]: false,
    [Symbol(corked)]: 0,
    [Symbol(kOutHeaders)]: [Object: null prototype] {
      authorization: [Array],
      'content-type': [Array],
      'x-arango-version': [Array],
      host: [Array]
    }
  }
}

When I start the application 5 times, I'm getting this error on 3 or 4 starts. On 1 or 2 starts it works. But I'm connected to the web-interface using Firefox without any problems. I'm running a single instance of ArangoDB 3.7.3, using arangojs 7.1.1 (previously tried with arangojs 7.2.0) using Node.js 14.14.0.
Any suggestions?

I finally figured out that it was a problem on my side that interrupted the connection because of a while-loop.

I finally figured out that it was a problem on my side that interrupted the connection because of a while-loop.

repo: arangodb/arangojs


text:
Typescript definition file

Dear guys,
After deleting arangojs and reinstalling it via npm, I figured out that the typescript definition file is not part of it. I would like to suggest that the arangojs.d.ts file is added to the the npm respository and the package.json. It is also possible to transfer the file into the lib folder (for better consistency rename it to index.d.ts in this case) and prepend the lib folder to all corresponding paths within the package.json accordingly, e.g. typings: "lib/index.d.ts".

Thanks for the fix. Leaving the file in place and adding it to the whitelist seems like the best option.

Good :) And do you plan to release a new version for npm?
When i am trying to pull the master repo via npm (arangodb/arangojs) I only get those files that are referenced within the files array. There is no way to run npm install properly then as all needed files are missing. That's why I am asking for an updated npm version, so I can pull the built files right away.

authors: daffunn pluma


text:
Feature: Table redesign

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Changed hover effect, added search bar in 2 pages and added button as per requirement.

Why was this change needed? (You can also link to an open issue here)
Fixes: #1286

Other information:

Hey @ManishMadan2882 the required changes are made can you please check it out.
Feel free to ask for more changes if required :)

Hey @AkashJana18 how is it going?

@dartpain working on it PR will updated soon

Hey @ManishMadan2882  I have made the required changes

Can you specify the kind of app crash on creating new key?
Also can guide me regarding resolving conflict. Like do i need to keep the skeleton reloader or remove it?

Hi @AkashJana18

The app crashes on creating new api key
The error is logged in the console
Uncaught TypeError: Cannot read properties of undefined (reading 'toLowerCase')  at APIKeys.tsx:93:20
We need to keep every change in the main branch including the skeleton.
Thanks.

Hey @ManishMadan2882 conflicts have been resolved.
Can you please check if the apikey error is resolved or not.
Thank you.

Hey @AkashJana18
Do you mind testing these changes before pushing or is there any issue you are facing during set up on your system?
Fails with npm run dev
[plugin:vite:react-babel] /home/manish/Documents/contributors/akash jana/DocsGPT/frontend/src/settings/APIKeys.tsx: Unexpected token, expected "," (57:6)
  60 |       });
/home/manish/Documents/contributors/akash jana/DocsGPT/frontend/src/settings/APIKeys.tsx:57:6
55 |            );
56 |          }
57 |        })
   |        ^
58 |        .catch((error) => {
59 |          console.error(error);

@ManishMadan2882 how do i revert the changes made while resolving conflict. I think i made error while resolving conflict if you can revert the change in APIkeys.tsx i can fix it.
i resolved conflict from github itself (not from vscode).

Follow this


text:
反馈：Nuxt3使用ArcoIcon编译后运行报错

[ ] I'm sure this does not appear in the issue list of the repository

基本信息

依赖包名 及 版本: @arco-design/web-vue@2.37.1
框架版本: NUXT：3.0.0-rc.8
浏览器版本: chrome105.0.0.0
复现地址: https://stackblitz.com/edit/nuxt-starter-e3nbgk?file=plugins/arco-icon.ts

额外补充
【arco-icon.ts】代码：
import ArcoVueIcon from '@arco-design/web-vue/es/icon';
import { Icon } from '@arco-design/web-vue';
const IconFont = Icon.addFromIconFontCn({ src: '//at.alicdn.com/t/font_3375775_9892igkxfb.js' });
export default defineNuxtPlugin((nuxtApp) => {
nuxtApp.vueApp.use(ArcoVueIcon);
nuxtApp.vueApp.component('icon-font', IconFont);
});
复现步骤
【在线复现异常】
1、打开 #1524 中回复的 demo
2、执行进行编译
3、编译成功后运行 ，能成功启动服务
4、打开网站控制台就会疯狂报错，无法正常访问：
[request error] [unhander] [500] 无法找到模块 'D：\网站开发\nuxt3_arco_cms.output\server\node_modules@arco-design\web-vue\es\icon.js' 从 D 导入：\网站开发\nuxt3_arco_cms.output\server\chunks\server.mjsnpm run buildnode .output/server/index.mjs

@kustone 看报错信息是导入解析存在问题，「无法找到模块 'D：\网站开发\nuxt3_arco_cms.output\server\node_modules@arco-design\web-vue\es\icon.js'」组件库不存在 @arco-design\web-vue\es\icon.js 文件，这里对应的应该是 @arco-design\web-vue\es\icon\index.js，可以检查下打包工具的相关配置

@kustone 看报错信息是导入解析存在问题，「无法找到模块 'D：\网站开发\nuxt3_arco_cms.output\server\node_modules@arco-design\web-vue\es\icon.js'」组件库不存在 @arco-design\web-vue\es\icon.js 文件，这里对应的应该是 @arco-design\web-vue\es\icon\index.js，可以检查下打包工具的相关配置

好的，我尝试一下，非常感谢您的回复和解答。

authors: flsion kustone

repo: arco-design/arco-design-vue


text:
下拉菜单 Dropdown只要使用了a-dsubmenu多级菜单，打包时就报错

[ ] I'm sure this does not appear in the issue list of the repository

基本信息

依赖包名 及 版本: @arco-design/web-vue@2.41.1
框架版本: Vue3
浏览器版本: chrome108.0.0.0

额外补充
错误信息：
[vite]: Rollup failed to resolve import "D:/www/data_pool/node_modules/@arco-design/web-vue/es/dsubmenu/style/css.js" from "src/views/data-center/metrics-database/components/content-chart-metrics/chart-series-source-box.vue?vue&type=script&setup=true&lang.ts".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external
error during build:
Error: [vite]: Rollup failed to resolve import "D:/www/data_pool/node_modules/@arco-design/web-vue/es/dsubmenu/style/css.js" from "src/views/data-center/metrics-database/components/content-chart-metrics/chart-series-source-box.vue?vue&type=script&setup=true&lang.ts".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external
at onRollupWarning (file:///D:/www/data_pool/node_modules/vite/dist/node/chunks/dep-4da11a5e.js:45916:19)
at onwarn (file:///D:/www/data_pool/node_modules/vite/dist/node/chunks/dep-4da11a5e.js:45714:13)
at Object.onwarn (file:///D:/www/data_pool/node_modules/rollup/dist/es/shared/rollup.js:23263:13)
at ModuleLoader.handleResolveId (file:///D:/www/data_pool/node_modules/rollup/dist/es/shared/rollup.js:22158:26)
at file:///D:/www/data_pool/node_modules/rollup/dist/es/shared/rollup.js:22119:26
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

看了一下，好像没有/node_modules/@arco-design/web-vue/es/dsubmenu这个文件夹

是不是用了 vite-plugin-style-import 这个插件，这个插件在 vite^4.0.0 上会有点问题

vite-plugin-style-import

是用了vite-plugin-style-import插件，因为用的Arco Design Pro，里面自带这个插件。
有什么办法解决这个报错吗？
我目前是手动创建了dsubmenu这个文件夹，然后把dropdown文件夹里面的style文件夹复制过去，能打包，不确定有没有问题

@Chanzhaoyu
是用了vite-plugin-style-import插件，因为用的Arco Design Pro，里面自带这个插件。
有什么办法解决这个报错吗？
我目前是手动创建了dsubmenu这个文件夹，然后把dropdown文件夹里面的style文件夹复制过去，能打包，不确定有没有问题

@zhonghuaifang
dsubmenu 这个是子组件，没有单独的文件夹样式。这个插件不维护了，你尝试下用 按需加载（模板）替换掉它吧。

@zhonghuaifang dsubmenu 这个是子组件，没有单独的文件夹样式。这个插件不维护了，你尝试下用 按需加载（模板）替换掉它吧。

或者你把 vite 等插件降级下，arco design pro 最近有更新，就是降级了 vite

@Chanzhaoyu 我试试，谢谢

记录：
问题：升级到最新版的arco design pro还是一样打包报错
解决过程：找到/config/plugin/arcoResolver.ts文件中的说明“虽然Pro项目中是全量引入组件，但此插件会默认使用。”（unplugin-vue-components 按需引入插件）
解决方法：/config/plugin/styleImport.ts文件中，在ignoreList数组中加入dsubmenu

谢谢 已成功解决 year-picker 和 dsubmenu 打包问题

authors: Chanzhaoyu Tingfenghhh zhonghuaifang


text:
upload 组件，当上传数量超过limit的时候，希望能加个字段，让用户来决定按钮是否显示

拖拽上传的区域框隐藏后感觉不大美观。

@zhubenjie Get

authors: Flsion zhubenjie


text:
在布局容器里，table组件没有数据且页面出现左右滚动条的时候，显示的空提示可以左右滚动，如果不在布局容器里，则空提示不会跟着左右滚动

[ ] I'm sure this does not appear in the issue list of the repository

基本信息

依赖包名 及 版本: @arco-design/web-react@2.37.2
框架版本: 18.0.0
浏览器版本: chrome103.0.0.0
复现地址: https://codesandbox.io/s/determined-diffie-6s6346?file=/src/App.tsx

复现步骤
调整浏览器窗口大小，可以看到滚动条的时候，左右滚动则可看到空提示也跟着滚动了

无法复现

无法复现

空提示的宽度大于表格的宽度40px，但窗口的大小变化后就能恢复到正常的状态了，只有第一次显示的时候会那样

刚刚打开的时候是好的，刷新下页面的时候就能重现了

authors: PengJiyuan leietal

repo: arco-design/arco-design


text:
PE-6629: get native address

This PR adds the getNativeAddress utility functoin on a TurboDataItemSigner and exposes the signer via the Turbo class

:tada: This PR is included in version 1.12.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.12.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: dtfiedler fedellen

repo: ardriveapp/turbo-sdk


text:
Remove "EMUcanT4"

Companion to https://github.com/arduino/library-registry/pull/2314

Done in https://github.com/arduino/library-registry/pull/2314#issuecomment-1377562352

repo: arduino/library-registry


text:
[2.x] [Forms] List of blocks : counter without Dropdown looks broken

List of blocks : counter without Dropdown looks broken
When listing blocks into Forms :
When no dropdwon are around the counter number, the item is misaligned with the label.
Steps to reproduce
Latest version.
Create a list of blocks that are not re-orderable.
Expected result
Counter should be aligned with text
Actual result
Counter is misaligned (see image)
Versions
Twill version 2.11.0

Hey @mrdoinel this is a regression, I will look into a bugfix tomorrow and make a new release.

I have checked this briefly, but I cannot immediately reproduce the issue.
Did you run php artisan twill:update after the composer update?
If that does not help, can you share how you are implementing the block editor field?

I updated the content of the issue so this is more precise : the issue is happening with Repeater items.

authors: haringsrob mrdoinel


text:
Updating the Navbar

I'm proposing an update to the navbar design to enhance its aesthetics and usability. This update will include improvements in color scheme, typography, layout, and responsiveness.

@arghadipmanna101 Can u plz assign this issue to me!!

sure. you have been assigned. go ahead and do you best.

Please , assign this  issue to me

Hello @arghadipmanna101 sir
I would like to work on this issue as a contributor to the GSSOC. please assign this to me!
I have relevant skills that definitely help to enhance the website.

Hello @arghadipmanna101 sir I would like to work on this issue as a contributor to the GSSOC. please assign this to me! I have relevant skills that definitely help to enhance the website.

which update you want to do? please explain

Hello @arghadipmanna101 sir, I would like to improve the header, nav bar including the hover effect and also the time for transition of it, and make the header more interactive and smooth.
would you assign it to me under GSSoC ?

@arghadipmanna101 I have already worked on a similar kind of clone.  I can fix the issue . Kindly assign this issue to me

@arghadipmanna101 Can u plz assign this issue to me!!


text:
Improve contrast

Improve contrast in some parts of UI for better accessibility.
1. Borders
before

after

2. Collapsible

3. Help
This one, I'm not sure about. I made the headings purple because I felt the help menu looked like a wall of text, but it's kind of awkward.

Looks good but I will have to make sure it works properly with custom themes once I have access to my Windows machine. Also, make sure the code is properly formatted.

I will add back the fix for this when I have time, but how did you get a custom theme?? 😯

https://github.com/rbxrootx/Roblox-Studio-CustomTheme-Patcher

Made some additional changes
Help widget
I don't like colored headers so made the wiki link use a branded color. Also it's fine that this page looks like a wall of text since users are meant to use argon.wiki anyway.

Settings collapsible
I don't think we need to introduce a new color here. I reused a more subtle one that we already have and added some logic to it.
https://github.com/user-attachments/assets/d6d20d06-4134-4dd2-b44b-e44a9389f3ba
Border contrast
Here I only changed how it's implemented. Hardcoding color values is not a good idea.

authors: DervexDev pinehappi

repo: argon-rbx/argon-roblox


text:
Support for new HTTP/2 provider API

Apple announced a new provider API for APNs based on HTTP/2 at WWDC 2015. Currently, there is no written documentation, but it should be available in the coming weeks.
See this video starting at 20:50 for an introduction to the new API: https://developer.apple.com/videos/wwdc/2015/?id=720
Also see the slides starting at page 98: http://devstreaming.apple.com/videos/wwdc/2015/720xwbi9nl/720/720_whats_new_in_notifications.pdf?dl=1

Thanks for opening this Florian, I hadn't got to that video yet. I will definitely be adding support for HTTP/2 and hopefully it should simplify a lot of the module.
―A

On 16 Jun 2015, at 15:02, Florian notifications@github.com wrote:
Apple announced a new provider API for APNs based on HTTP/2 at WWDC 2015. Currently, there is no written documentation, but it should be available in the coming weeks.
See this video starting at 20:50 for an introduction to the new API: https://developer.apple.com/videos/wwdc/2015/?id=720
―
Reply to this email directly or view it on GitHub.

Starting work on this in #278

If I'm not mistaken, Apple is yet to make the new HTTP/2 based API public?

Correct, but there is enough information in the WWDC session for me to make a start and adjust it as new information becomes available

I believe the Feedback API has been removed and now a HTTP/2 push is used instead? Has this been implemented in the http2 branch yet? Or do we continue using the old method for now?

That's correct. With the new HTTP/2 API there is no separate feedback service. If you send a notification to a disabled device, you will get an appropriate HTTP response in return.
I don't think the new HTTP/2 API is available yet.

@florianreinhart  Got it, just wanted to confirm. Thanks.

The http2 branch is completely broken at the moment as I have ripped out all the old protocol code. I am using it to experiment with how I will build the http2 support going forward but as @florianreinhart says the protocol isn't live yet so I won't be able to do much until then.
―A

On 9 Jul 2015, at 10:43, Nikhil Nigade notifications@github.com wrote:
@florianreinhart Got it, just wanted to confirm. Thanks.
―
Reply to this email directly or view it on GitHub.

Hi @argon, Apple just made the docs public.
Doc: https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/APNsProviderAPI.html#//apple_ref/doc/uid/TP40008194-CH101-SW1

Any schedule when this will be released?

Not yet. I'll do what I can but this is a personal project in my spare time so I can't make any promises about timescale

On 18 Dec 2015, at 10:51, Stavros Schizas notifications@github.com wrote:
Any schedule when this will be released?
—
Reply to this email directly or view it on GitHub.

@argon You've already done some work on the http2 branch. If you could tell how the certificates come into play (the only bit I have never managed to figure out), I could probably take a shot at this and if all is good, send a PR.

The basics of certificate handling should already be in place. I should warn you though that I will be actively developing the HTTP/2 support, I simply can't provide an ETA
—A

On 18 Dec 2015, at 13:26, Nikhil Nigade notifications@github.com wrote:
@argon You've already done some work on the http2 branch. If you could tell how the certificates come into play (the only bit I have never managed to figure out), I could probably take a shot at this and if all is good, send a PR.
—
Reply to this email directly or view it on GitHub.

@argon I see. Well then, I'll lend a helping hand where ever I can. Thank you.

Will the API to use this node module be any different for the http2 version?

There will be at least a few breaking changes as the feedback service will now need to be integrated in the Connection instead of being separate. I will probably deprecate some old API so it may be a 2.0 I haven't decided yet. Any necessary changes should be very minor though. What are your thoughts on this?

On 23 Dec 2015, at 02:09, Noah Andrews notifications@github.com wrote:
Will the API to use this node module be any different for the http2 version?
—
Reply to this email directly or view it on GitHub https://github.com/argon/node-apn/issues/277#issuecomment-166784066.

The first thing that comes to my mind is utilizing EventEmitters.
That way, something like this should be possible and convenient:
service.on("feedback", (evt) => { ... })

service.on("delivered", (evt) => { ... })

service.on("error" (evt) => { ... })

// and so on

Absolutely, that is similar to how the current version works within the limitations of the APNS protocol. The HTTP/2 protocol is has much better responses so event emitters will be more useful.

On 23 Dec 2015, at 11:36, Nikhil Nigade notifications@github.com wrote:
The first thing that comes to my mind is utilizing EventEmitters.
That way, something like this should be possible and convenient:
service.on("feedback", (evt) => { ... })
service.on("delivered", (evt) => { ... })
service.on("error" (evt) => { ... })
// and so on
—
Reply to this email directly or view it on GitHub https://github.com/argon/node-apn/issues/277#issuecomment-166869803.

+💯

FYI:
The HTTP/2 APNs provider API is now up-and running.
Documentation can be found here:
https://developer.apple.com/library/mac/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/APNsProviderAPI.html#//apple_ref/doc/uid/TP40008194-CH101-SW1
Any ETA as to when we can expect a first version that supports it? :)

@jorisvervuurt That link had already been posted, and just six days ago @argon said he couldn't provide an ETA.

How things going on http2.0 APN?

+1 any updates on this?

This will probably take a while. It's turning out to be a complete rewrite. See https://github.com/argon/node-apn/pull/278.

I am actively working on this. I hope to have something functional soon, with further improvements as fast as I can.

@ekristen are you sure it's not possible to use a newly issued certificate with the current protocol?

@ekristen I just created a new certificate in the developer portal. It was able to send a notification via the sandbox service with the current version of node-apn (1.7.5)

@ekristen @argon I can confirm the new certs work for both Sandbox and Production with the current source from the master branch.

How far along are you with implementing the HTTP/2 API? I'm really interested in this :)

I have the basics working now but it's not ready for production. Still need to add multi connection support and better error handling.

Right, well, I'll be needing a module like this pretty soon for some production code, so if I can be of assistance in any way, let me know :)

+1

+1

Great work, @argon. It seems you are working alone on this, and everyone is waiting eagerly. Thanks for doing this! But please let us know if there is anything we can do to help! Can the work be split into smaller well-contained tasks, that can be assigned, and we can submit pull requests and review each others code?

@sveinhal The foundation of the new code is nearly in place. There is much to do but the basics work now. I will be creating new issues for remaining tasks so we can work from there. I hope to make further progress this weekend.

I am also waiting, Thanks for doing this!

I'm waiting for new release too

@argon I appreciate your work. Have you a clue when HTTP/2 version will be released.

Keep up the good work 👍

Any update on this one?

Thanks for working on!

Released as v2.0.0

great, thanks :)

Thank you for this big work you did

You nailed it @argon 👍

authors: NasserAlmanji NoahAndrews airs0urce argon dezinezync ekristen florianreinhart goldenice henry42 jorisvervuurt ms88privat n3trino pratiknaik sveinhal uronly14me

repo: argon/node-apn