text:
[API] WIP: Make Parameterized refine Differentiable

DO NOT MERGE

@swift-ci Please test tensorflow

Note: Using Tensor-typed parameters is blocked by conforming synthesized Parameters to TensorArrayProtocol for GPE.

Are there any blockers you're aware of in the case of dynamic compilation/no GPE? I'm getting a runtime segfault on this branch with -tf-dynamic-compilation for the following code (crash in __tf_to_host); will look into it:
struct Model: Parameterized, Differentiable {
  @TFParameter var w: Tensor<Float>
  func tangentVector(from cotangent: Parameters) -> Parameters {
    return cotangent
  }
}

let model = Model(w: Tensor<Float>(zeros: [5]))
let pb = pullback(at: model) { m in m.w }
print(pb(Tensor<Float>(zeros: [5])))

(although this works:)
let model = Model(w: Tensor<Float>(zeros: [5]))
let x = Tensor<Float>(zeros: [5])
let pb = pullback(at: model) { m in m.w + x }
print(pb(Tensor<Float>(zeros: [5])))

Looks like this was because I didn't rebuild the standard library.

@swift-ci please test tensorflow

@swift-ci please test tensorflow

@swift-ci please test tensorflow

authors: dan-zheng jekbradbury rxwei


text:
[upstream-update] update for SVN r266919

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

getSymbolName changed from ErrorOr to Expected.  Update the API accordingly.

CC @slavapestov

@swift-ci please test

@swift-ci Please test

@swift-ci please test

@swift-ci Please test

CC @rudkx

I already made this change and another one related to Expected<> in commit b044c4d74feb4fa232ed017451c9b06395ea5867.

source: gharchive/pull-request

authors: compnerd jrose-apple modocache rudkx

repo: apple/swift

license_type: permissive

license_source: github-api


text:
[5.1 06-12-2019] SILGen: Map dynamic self out of context when mangling reabstraction thunk symbols.

Fixes rdar://problem/51257789.

@swift-ci Please test

@swift-ci Please nominate


text:
[Clang importer] swift_newtype'd types are bridged when their underlying type is bridged

What's in this pull request?
This commit fixes a problem in the interaction between swift_wrapper/swift_newtype (SE-0033) and importing ObjC lightweight generics (SE-0057), where we would end up bringing in a bridged type in a position (i.e., a type argument to an imported ObjC generic type) where a class type is required.
Resolved bug number: (rdar://problem/26340353)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

…ing types are.
A swift_wrapper/swift_newtype'd type can wrap a bridged type. In such
cases, we need to report both the unbridged type (which is the
unbridged underlying type) and the bridged type (which is the
importer-created wrapper type). This fixes a problem where Objective-C
generic specializations would use the wrapper types on type parameters
with "AnyObject" constraints, which... doesn't work.
Fixes rdar://problem/26340353.

@swift-ci please test

I'm certain that wasn't me, but let's try again...

@swift-ci please test

@swift-ci please test

@swift-ci smoke test os x platform

authors: DougGregor tkremenek


text:
[stdlib] Provide migration hint for AnyTraversalIndex types

What's in this pull request?
This adds an @available attribute for AnyForwardIndex, AnyBidirectionalIndex, and AnyRandomAccessIndex that forwards to the new AnyIndex.
Resolved bug number: (SR-1597)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test and merge

CI failure is unrelated.


text:
StdlibUnittest: port to android x86, x86_64

Account for the x86 and x86_64 architectures when defining
RTLD_DEFAULT.

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

Resolves SR-NNNN.

@swift-ci please smoke test


text:
[NFC] Move some Type Checker Options into TypeCheckerOptions

Well, and a few other things

Remove TypeChecker::getLangOpts().  You can get it from the ASTContext.
Drop a few SaveAndRestores of type checker debug flags.  These were just being used to control the behavior of the ASTPrinter.  But the ASTPrinter doesn't dump types...
Clean up type checker option parsing a bit.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

⛵


text:
Allow initializing a wrapped property with a nonmutating setter

This is achieved in 3 steps:

CSApply detects assignments to property wrappers inside constructors, and produces an inout expr instead of a load, which it normally would because nonmutating setters take the self by-value. This is necessary becasue the assign_by_wrapper instruction expects an address type for its $1 operand.
SILGenLValue now emits the assign_by_wrapper pattern for such setters, ignoring the fact that they capture self by value. It also introduces an additional load instruction for the setter patrial_apply because the setter signature still expects a value and we now have an address (because of (1)).
DefiniteInitialization ignores specifically load instructions used to produce a self value for a setter referenced on assign_by_wrapper  because it will be deleted by lowering anyway.

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 27dcde950b7125fb2796212ea072fd922936d1f2

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - 27dcde950b7125fb2796212ea072fd922936d1f2

Build failed
Swift Test OS X Platform
Git Sha - 27dcde950b7125fb2796212ea072fd922936d1f2

Build failed
Swift Test OS X Platform
Git Sha - bce68e47cd98aff6e7afe529b478c6141763ad81

Build failed
Swift Test Linux Platform
Git Sha - bce68e47cd98aff6e7afe529b478c6141763ad81

The failures are caused by the fact that the change in SILGenLValue needs to do precisely the same kind of checking as done in CSApply. We must avoid rewriting such setters into assign_by_wrapper unless they are assignments to self in a constructor.

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - bce68e47cd98aff6e7afe529b478c6141763ad81

Build failed
Swift Test OS X Platform
Git Sha - bce68e47cd98aff6e7afe529b478c6141763ad81

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 4cdc3016e58e4b480437f9e6ac3f346e1e2afaa6

Build failed
Swift Test Linux Platform
Git Sha - 4cdc3016e58e4b480437f9e6ac3f346e1e2afaa6

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 4cdc3016e58e4b480437f9e6ac3f346e1e2afaa6

Build failed
Swift Test Linux Platform
Git Sha - 4cdc3016e58e4b480437f9e6ac3f346e1e2afaa6

You should add a SILGen test too (grep assign_by_wrapper test/SILGen/ to see where to add it)

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - 5f8ae56b287409d8e8c7acd32d374b7c106de4cd

Build failed
Swift Test OS X Platform
Git Sha - 5f8ae56b287409d8e8c7acd32d374b7c106de4cd

Huh.
@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - ea70b3848aa6bb717e6dc7c5e0a2b3911f92bae6

Build failed
Swift Test Linux Platform
Git Sha - ea70b3848aa6bb717e6dc7c5e0a2b3911f92bae6

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - ea70b3848aa6bb717e6dc7c5e0a2b3911f92bae6

Build failed
Swift Test OS X Platform
Git Sha - ea70b3848aa6bb717e6dc7c5e0a2b3911f92bae6

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - d89b731e1c667ba320e9c2b478d655f501c8b042

Build failed
Swift Test Linux Platform
Git Sha - d89b731e1c667ba320e9c2b478d655f501c8b042

Oops, merge conflict on a test.
@swift-ci test

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - d89b731e1c667ba320e9c2b478d655f501c8b042

Build failed
Swift Test OS X Platform
Git Sha - d89b731e1c667ba320e9c2b478d655f501c8b042

@swift-ci Please test OS X platform

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - cb5354b2ad8f36ab1b1bd226d4460d2ffca10cb2

Build failed
Swift Test Linux Platform
Git Sha - cb5354b2ad8f36ab1b1bd226d4460d2ffca10cb2

authors: artemcm slavapestov swift-ci


text:
[Frontend] Recover missing input file by dummy input buffer.

Recover missing input file by dummy input buffer as long as they are non-primary .swift files. Also, continue trying opening files even if any of primary files are missing so that the caller can know all files failed to open.
Fixes rdar://problem/33757793 where code completion failed if there's a missing input file.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please test Windows

@swift-ci Please test Windows


text:
Fix tab size for Emacs users.

For some reason .dir-locals.el was setting tab-width to 2.  That's a Really Bad Idea, because if somehow (as happened in my case) indent-tabs-mode was 't instead of nil like it should have been, Emacs will insert tabs instead of spaces, and it'll look like it's doing the right thing when it really isn't.

@swift-ci Please smoke test

@swift-ci Please smoke test Linux platform


text:
[Type Checker] Prevent Path Consistency algorithm from aborting too a…

What's in this pull request?
[Type Checker] Prevent Path Consistency algorithm from aborting too aggressively

Instead of failing shrinking when there are no solutions for current
sub-expression, let's restore overload domains for previously solved
sub-expressions and move on trying to solve next expression in the queue.

Resolved bug number: (SR-1794)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please clean test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please clean test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform
    Linux platform              | @swift-ci Please clean test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

…ggressively
Instead of failing shrinking when there are no solutions for current
sub-expression, let's restore overload domains for previously solved
sub-expressions and move on trying to solve next expression in the queue.

/cc @DougGregor @rudkx

@swift-ci Test and merge.

authors: rudkx xedin


text:
spelling: diagnostic

This fixes some misspellings in Swift lib/Localization, it is split per https://github.com/apple/swift/pull/42421#issuecomment-1101092698

@swift-ci Please smoke test and merge

authors: LucianoPAlmeida jsoref


text:
[CSClosure] NFC: Add a test-case for rdar://92757114

Used to produce a fallback type of expression ... diagnostic

@swift-ci please test

@swift-ci please test


text:
[5.7] Updating Swift tests to remove outdated tests and use more current calls

Changes now use CoreImage rather than Foundation, or make calls to implicitly import Foundation.

@swift-ci please test


text:
[stdlib] String.debugDescription: Fix quoting behavior

String.debugDescription currently fails to protect the opening or closing ” characters (or characters in a quoted scalar) from combining with the contents of the string itself:
let s = “\u{301}A\n\u{302}B\u{70F}”
print(s.debugDescription)
// ⟹ “́A\n̂B܏”  (characters: “́, A, \, n̂, B, ܏”)

This can make debug output difficult to read.
This change fixes this by force-quoting the problematic scalars in these cases:
let s = “\u{301}A\n\u{302}B\u{70F}”
print(s.debugDescription)
// ⟹ “\u{0301}A\n\u{0302}B\u{070F}”

Of course, Unicode scalars that don’t engage in such behavior are still allowed to pass through unchanged:
let s = “Cafe\u{301}”
print(s.debugDescription)
// ⟹ “Café”

Other types such as Substring, StaticString, String.UTF8View etc. implement CustomDebugStringConvertible by delegating to String, so this PR fixes our output for all of them.
rdar://103972032

@swift-ci test

D'oh, the test will only pass with #63046

@swift-ci test


text:
[Runtime] Ensure we always generate names for ObjC classes.

If something fails while trying to generate a name for an ObjC class, we fall back to a generated name based on the metadata pointer.  This ensures that we won't crash, and if the name turns up in the debugger or somewhere it should be obvious that something went wrong.
rdar://107718586

@swift-ci Please smoke test

@swift-ci Please smoke test


text:
[move-only] Ensure that copyable borrowing parameters of resilient type used by a function in the same module can be recognized by the checker

I found this while looking at problems around library evolution for noncopyable types. Specifically:
+public func borrowVal(_ x: borrowing CopyableStruct) {}

causes an error since we do not recognize the load_borrow here:
+sil [ossa] @testSimpleBorrowParameter : $@convention(thin) (@in_guaranteed CopyableStruct) -> () {
+bb0(%0 : @noImplicitCopy $*CopyableStruct):
+  %1 = load_borrow %0 : $*CopyableStruct                       // users: %7, %2
+  %2 = copyable_to_moveonlywrapper [guaranteed] %1 : $CopyableStruct // user: %3
+  %3 = copy_value %2 : $@moveOnly CopyableStruct               // user: %4
+  %4 = mark_must_check [no_consume_or_assign] %3 : $@moveOnly CopyableStruct // users: %6, %5
+  debug_value %4 : $@moveOnly CopyableStruct, let, name "x", argno 1 // id: %5
+  destroy_value %4 : $@moveOnly CopyableStruct                 // id: %6
+  end_borrow %1 : $CopyableStruct                              // id: %7
+  %8 = tuple ()                                   // user: %9
+  return %8 : $()                                 // id: %9
+}

rdar://112028837
(cherry picked from commit 87713349d43e297df13b7e3859c4677248fb4fc4)

@swift-ci test


text:
[Build] Enable building the early Swift Driver on linux with the prebuilt host toolchain

@bnbarham, let's see if this works on the linux CI now. This simply reverts most of your #68091, with the prebuilt Swift toolchain now installed on the linux CI.

@swift-ci please build toolchain

Alright, the only platform actually affected by this pull worked, linux. I checked the CI log and it's building and using the early swift driver just fine.
MacOS and Windows aren't affected by this pull: the former had a spurious build failure, while the latter's CI appears to be broken right now.
@bnbarham, ready for review and merge.

@swift-ci please build toolchain UBI9

@swift-ci please build toolchain CentOS 7

@swift-ci please build toolchain Ubuntu 22.04

@swift-ci please build toolchain Amazon Linux 2

@swift-ci please build toolchain Ubuntu 18.04

@swift-ci please test

Linux CI failed because the early swift driver tests are now being run, maybe for the first time on linux. @artemcm, you added those tests in #36377 a couple years ago, did you ever try them on linux? Natively on Android, I simply disable them with --skip-test-early-swift-driver.
Amazon Linux 2 toolchain build failed at source checkout, unrelated to this pull.

@swift-ci please build toolchain Amazon Linux 2

Natively on Android, I simply disable them with --skip-test-early-swift-driver.

I'd rather get to the bottom of the failures than just disable them 😅. That really just needs reproducing locally since the tests just all fail with exit code 1 though.

I'd rather get to the bottom of the failures than just disable them

Both this CI and my native Android toolchain build run the more extensive tests in the swift-driver repo later in the build, so I figured that's enough.

That really just needs reproducing locally since the tests just all fail with exit code 1 though.

Not all, if you scroll down, there are weird errors like this:
Command Output (stderr):
--
Swift version 5.11-dev (LLVM 1cd18baafcdabfd, Swift e002773d258ee29)
Target: x86_64-unknown-linux-gnu
Handled a.swift
Handled b.swift
Handled c.swift
Handled d.swift
Handled e.swift
Handled f.swift
Handled g.swift
error: autolink-extract command failed with exit code 1 (use -v to see invocation)
<unknown>:0: error: error opening input file 'a.o' (The file was not recognized as a valid object file
)

Most likely, it is just the various environment variables not being set right on linux. I figured it was something like that on Android and never looked into it.

Looked into those failing tests, it appears they are surfacing a genuine discrepancy between the legacy C++ Driver and the new swift-driver. I'm working on a fix.

@artemcm, how about a CI run with apple/swift-driver#1479, that should fix most of these tests.

https://github.com/apple/swift-driver/pull/1479
@swift-ci test

Rebased and added a fix for the single failing test, @bnbarham, need another CI run with the linked swift-driver pull.

https://github.com/apple/swift-driver/pull/1479
@swift-ci test

@bnbarham, ready for review and merge, after one last Windows CI run and merge of the linked swift-driver pull, that gets these early swift driver tests to work on linux.

Oh, this is great. Thank you @finagolfin

Thanks @finagolfin! I'll do one last toolchain build and then merge :)

https://github.com/apple/swift-driver/pull/1479
@swift-ci please build toolchain Ubuntu 22.04

authors: DougGregor artemcm bnbarham finagolfin


text:
Jenkins Job params

Hi.
Is it support parametrized jobs ?
How to pass jenkins job params ?

@appleboy are you interest on the feature to submit job params?
I have experiment to submit params in my fork successfully and would like to share it with your project, when your are interested.

@geopossachs Do you have your image upload to somewhere?
I'm interesting in your sharing.

Hallo @cool21540125,
only my master was published at docker hub
https://hub.docker.com/r/geopossachs/drone-jenkins
But you found only my code draft here.
https://github.com/geopossachs/drone-jenkins/tree/feature/job-paramter

@geopossachs Can you send the PR?

Yes, i will check my old code in the next days and will open an PR afterwards

@geopossachs THanks.

Hallo @cool21540125 ,
i have merged XSRF and params support together and now you can found it on docker hub
https://hub.docker.com/r/geopossachs/drone-jenkins/tags

Hallo @appleboy ,
i have open a MR for you. If it can be improved i'm open to hints.
https://github.com/appleboy/drone-jenkins/pull/27/files

source: gharchive/issue

authors: appleboy cool21540125 geopossachs xriser

repo: appleboy/drone-jenkins

license: MIT


text:
Sceneform example crashed after some time

I am using Sceneform example, I have placed some nodes on lat-long and start moving the camera around. After playing it for some time the camera gets heavy and finally crashed.
Android Studio: 3.1.1
Device: Samsung Galaxy S7
Android: 7.0 API level 24

What error did you get as it crashed?

I have tried to reproduce it but unable to reproduce the crash. But I am confirm that the camera is getting heavier with the passage of time.

authors: ArbabR johnwedgbury

repo: appoly/ARCore-Location


text:
Create scaffolding workflow for spinning up a cluster based on plan output.

Problem
We would like to spin up clusters quickly for testing various configurations.  While the Kismatic tool drastically simplifies cluster creation, manual intervention is required during the bring up process to finalize the plan file with various parameters such as IP address, CIDR ranges, and several other policy and configuration options.
Vagrant Scenario
Often, I spin up a small vagrant test cluster by running
kismatic install plan
After answering the node count and other questions, I create a matching Vagrant configuration of nodes.  The node IPs, and names (fqdn and short name for example, you could use the vagrant-dns plugin) need to be synchronized with the plan file.  Once additional options are set in the plan file (see enhancement #78 for a better way to capture this input) and the vagrant virtual machines have been brought up with vagrant up run
kismatic install validate
and then
 kismatic install apply
to deploy kubernetes.
Proposal
I propose we add an additional subcommand named scaffold.  This subcommand could accept a parameter identifying the target platform on which to scaffold (e.g. vagrant, aws, packet, etc.) the nodes necessary to implement the plan.  This target platform should be pluggable and adhere to a common API for specifying the node VM configurations for the cluster.
kismatic install scaffold should bring up the target platform.  This subcommand should honor the global parameter for specifying a plan file since it needs to both read and write it.  Since it would bring up the platform, would should provide the appropriate up, halt, and destroy subcommands to scaffold.
For example, if the target is

vagrant, a Vagrantfile should be produced (we will need to capture the desired CIDR for generating the nodes and optionally could consume a go template as a parameter for controlling certain aspects of the Vagrantfile)
aws, a CloudFormation script to bring up the nodes (the CLI should prompt the user for appropriate authentication credentials as well as region, availability zone, VPC, etc.).

Additionally, if scaffold specific parameters need to be saved (for halting, destroying, or bringing the cluster back up), those could be stored in the plan file as:
scaffold:
  vagrant:
    cidr: 192.168.50.0/24

A proposed order of operations is:
kismatic install plan
yielding the plan file.
kismatic scaffold up --target vagrant
This will bring up the Vagrant cluster.
kismatic install apply
will install the kismatic distribution on the new cluster.

I've actually been working on something like this, though in reverse.
What I have is a separate provision command, which operates against AWS (and soon Vagrant/Virtualbox and Rackspace) to create new machines using the same technique as our integration tests.
After creation, the provision command generates a plan and fills in the details of the newly created resources.
e.g.
provision aws --etcd=3 --master=2 --workers=4 --generatePlan
will spin up 7 machines using AWS credentials in the user's environment and output a basic plan file that may be edited after provision completes.

The order I specified allows for mapping a test cluster directly to a provided plan file and allows the planning step to work the same in all scenarios (instead of needing to provide switches).
This allows the scaffolding operation to be an optional step that can replace plan file prep that might be used during standard deployment.
The goal here would be to maintain well-understood workflow with pluggable steps.

https://github.com/apprenda/kismatic-provision
Please review. As it stands, this tool is intended to GENERATE a plan file, but it could also take input from a plan if this is desirable.

I recommend closing this issue and moving further enhancement requests for provisioning functions over to the new http://github.com/apprenda/kismatic repo.

authors: codymccain dasmb

repo: apprenda/kismatic

license_source: bigquery


text:
Support FreeBSD

Our other integrations have FreeBSD support, but it was not implemented when adding other platform support because there was no easy way to test it. This issue is about implementing it and testing it the hard way, with a FreeBSD VirtualBox.
To do

[ ] Add FreeBSD entry (or entries) to the build-triple-to-platform-tag map.

In this map, the key is the Rust-like build triple, as it appears on agent.py, while the platform tag is "simply" the output of some platform-dependent Python function in that platform, except for all the cases where it is not. 🙃 I tried looking for an existing example in PyPI's package list, filtering by the FreeBSD support category, but couldn't find one. You may need to boot a FreeBSD machine to figure out what the right value is.
If you can figure out if the "manylinux" spec somehow applies for FreeBSD, that would be neat, as it would allow us to specify which libc we depend on. I don't think it does, though.

[ ] Release a build with FreeBSD artifacts to TestPyPI.
[ ] Test with a FreeBSD virtual machine that pip install appsignal (with the --index-url bits to force installation from TestPyPI) installs the right version of the package. Make sure the agent boots.

Alternative todo list if the above is ETOOHARD:

[ ] Change the supported operating systems table in the docs to specify that Python does not support FreeBSD.

@tombruijn I'm not sure what platform.platform() is. The internet says that sysconfig.get_platform() is the replacement we should look at. In my local machine, these give slightly different results to platform.platform():
>>> import distutils; distutils.util.get_platform()
'macosx-12.6-x86_64'
>>> import sysconfig; sysconfig.get_platform()
'macosx-12.6-x86_64'
>>> import platform; platform.platform()
'macOS-12.6-x86_64-i386-64bit'

I'm also not sure about the current macOS versions specified. I cargo-culted them from somewhere. I don't think we need to specify them exhaustively, but it does seem that they matter somewhat.
Some old conversations online imply that the value provided by distutils.util.get_platform() is not useful for FreeBSD. That, combined with the fact that I've not been able to find any package for FreeBSD published on PyPI (not even numpy, which is probably the most popular Python package with a C extension) and that popular Python packages seem to be published as FreeBSD ports, makes me think that this might not be feasible. It might be that the best we can do is publish a link to a .whl somewhere for manual install.
Of course, I don't really know, because the documentation around all of this is incomplete and inaccurate and outdated. It's quite frustrating.

Before we ship anything, this issue is blocked on general FreeBSD support in https://github.com/appsignal/support/issues/118

authors: tombruijn unflxw

repo: appsignal/appsignal-python


text:
Enabling Rapier disables ability to place or move any nodes in Godot 4.3

Describe the bug
Add description here
To Reproduce
Steps to reproduce the behavior:

Run latest Godot stable on mac, 4.3, create a few Rigidbody2Ds in 2d, enable Rapier 2d in project settings.
Select an object, try to move it, most wont move or have weird buggy movement behavior when dragged with the mouse.

Most Rigidbody2D nodes cannot be moved in the editor, those that can 'move' with 'q' and dragging are buggy. There was a previous fix to 8.4 that was supposed to address this bug, but unfortunately the bug is still very much present, making Rapier basically unuseable in godot sadly.
Expected behavior
Nodes are able to be moved around in the editor per normal, the same as if GodotPhysics was selected.
Bug behavior for any 2d project if Rapier enabled.
Environment:

OS: Mac M1
Version
Godot Version 4.3
Type [e.g. simd single 2d]

I would love to be able to try out Rapier, I've been enabling it, reloading the project, disabling it, moving an object, reloading over and over to test it out, but this just isn't viable, would love to be able to actually use the engine.

Fixed in 0.8.5

awesome! working well, thank you!
https://github.com/user-attachments/assets/782a27df-d6ba-4a38-a18e-2515a04dfdde

authors: Ughuuu kyle-wendling

repo: appsinacup/godot-rapier-physics


text:
[Feature]: Ability to change the background color of the page

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
New option for setting the background color of the page should be added.
Why should this be worked on?
To change the background ui of the application for every page.

@dilippitchika @jsartisan seems like a fairly simple feature we can add for users

We are already doing this in app theming PR.

Talked to @jsartisan we don't have a way to do it at a page level only at an app level. Will co-ordinate with Liz and add this.

We would also like to be able change the background color of apps to something besides white! We need to make a dark themed app. Please implement this if possible!

repo: appsmithorg/appsmith


text:
[Feature]: Ability to suppress the Toast messages in specific known failure scenarios

Is there an existing issue for this?

[X] I have searched the existing issues

Summary

User wants ability to suppress the Application toast messages in certain scenarios where he knows there is going to be no data & do not expect toast error & data in those cases
User feels - this alert could be unnecessary in such places & hence wants to suppress it

Why should this be worked on?
https://app.intercom.com/a/apps/y10e7138/inbox/inbox/conversation/164629100095478#part_id=comment-164629100095478-14470174776

@Aishwarya-U-R the user should be able to do this by assigning an onError callback to the query

authors: Aishwarya-U-R Nikhil-Nandagopal


text:
[Bug]: Postgres | XML datatype - Unable to read/select values

Is there an existing issue for this?

[X] I have searched the existing issues

Description

Steps To Reproduce

Connect to a postgres ds
Create a table with xml datatype:
Insert values into it:

CREATE TABLE xmltest (xmldata XML);

INSERT INTO xmltest VALUES ('admin@testsite.commike@gmail.comSite is up. My site is working.');

INSERT INTO xmltest  VALUES ('<?xml version="1.0"?>  <Email>
                <to>admin@testsite.com</to>
                <from>mike@gmail.com</from>
                <subject>Site is up</subject>
                <message>My site is working.</message>
        </Email>');

Run a select query on the newly created table
Observe : Unable to read the values from the table with xml column & throws error as shown in above image
Expected : User should be able to read, perform all xml related functions on a XML datatype column

Public Sample App
No response
Version
Prod/Release v1.7.9

tested on 1 Jul 2024 - reproducible

@rohan-arthur i would like to work on this bug here i could not able to create a table column with XML datatype

i would like to work on this issue

authors: Aishwarya-U-R rohan-arthur skjameela


text:
[Task]: Arango plugin: change default db name to _system

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks

Currently when a new Arango DB plugin datasource is created the default db name is default. We should change it to _system since this is what the Arango documentation mentions as their default db name: https://www.arangodb.com/docs/stable/http/database-notes-on-databases.html#database-name

@sumitsum I'm interested to take up the issue. Could you pls assign this to me?

@reachtokish thanks for showing interest in this issue. I have assigned this issue to you. You need to make the change in this file. Happy coding :)

Sorry mistakenly clicked on unassign me link

Also raised https://github.com/appsmithorg/appsmith/pull/16198 - this PR. Kindly have a look.

authors: reachtokish sumitsum


text:
[Feature]: Added map details on each country

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
I need map details from Indonesian which contains regency in Indonesian.
Why should this be worked on?
To expand the features available in appsmith and to display demographics

@isal-evermos which widget are you using?

@Nikhil-Nandagopal "map chart"

authors: Nikhil-Nandagopal isal-evermos


text:
[Bug]: Path details of a URL cannot be added during app import configuration

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Previously, path details, like /posts could be added while reconfiguring datasources during app import. Save button would be enabled to proceed with this configuration
Now, only the domain information is accepted and save button is disabled if path details exist.
Post import, user can navigate to the datasources page and add in the path information to their saved API datasource
Steps To Reproduce

Export and import an app that has a saved API datasource
On the configuration modal, enter https://jsonplaceholder.typicode.com/posts and observe the save button is disabled
Remove path information and observe the save button gets enabled
Save the configuration and navigate to the datasource inside the application and edit the URL to contain path details and observe this is allowed.

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud

Since it is an issue on the Datasource configuration modal which comes up post the app import is successful, moving it to Integrations pod

https://github.com/appsmithorg/appsmith/assets/94514895/f362977a-f9d1-47f2-bdeb-56dbd0ebc666
not replicable anymore, maybe got fixed somewhere else

authors: ramsaptami riteshkew rohan-arthur


text:
[Task]: Document the Steps to setup Airtable locally

SubTasks

Document the steps to setup Airtable datasource locally
Log the issues faced and add Troubleshooting steps to resolve them.

https://www.notion.so/appsmith/Setting-up-Airtable-datasource-locally-a2d14005e6034d7fa71f153ede07d43e?pvs=4


text:
[Task]: Use standard naming convention strategy for index names in postgres

SubTasks

Go through existing indexes and add NULLS NOT DISTINCT
Renaming indexes as per this convention - https://stackoverflow.com/questions/4107915/postgresql-default-constraint-names/4108266#4108266

This is completed, closing this


text:
Replace Entity Item in Schema tables

[ ] Replace existing implementation with the EntityGroupedList component in ADS
[ ] Retain the test ids to not break any unit or integration tests
[ ] Replace both in Datasource tab in Bottom pane and View Data tab in Datasource editor

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


text:
[Feature] Support WSL2!

Summary
Appsmith currently doesn't support WSL2. This is prohibitive for the growing WSL community to use it and build on it/for it!
Motivation
My own self not being able to install Appsmith, since I'm on WSL.
Additional Context
WSL is Windows Subsystem for Linux, a newly launched capability to run Linux distributions natively inside Windows. WSL2 is the latest version of this feature and is now GA for all Windows 10 users. There is a growing community around WSL2.

@bharatkashyap thank you for the issue. We do indeed need to improve our WSL2 support. Unfortunately, no one on our team has windows right now so maintaining this has been a challenge.

authors: Nikhil-Nandagopal bharatkashyap


text:
fix: delete branch tests

Description
Adding jest and cypress tests for git delete branch feature
Fixes #13616
Type of change

Tests

How Has This Been Tested?
Attached tests.
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=318d59eb660c58a9358972c1d45a1b5c55ae8bca

Failing tests

Failing tests


text:
feat: Dynamic Menu Items - Table Widget

Description
This PR allows adding menu items from a Source for a Menu Button Column inside the Table Widget.
What we are able to do in #17652, we have extended that to the Menu Button inside the Table Widget in this PR.
Fixes #17955
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Manual
Jest

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 visibility and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[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
[ ] PR is being merged under a feature flag

QA activity:

[x] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

Test Plan for Dynamic Menu items in Menu Button Column inside Table widget:
https://github.com/appsmithorg/TestSmith/issues/2128

Tested this PR and LGTM

Tested Menu Button widget inside Table widget with both Dynamic & static source data
Tested with all Table properties to see behavior of Menu Button widget
Tested all style properties of Menu Button type and their Menu Items

/ok-to-test sha=cc566fb

/ok-to-test sha=da1f495

/perf-test sha=da1f495

authors: chandannkumar dhruvikn


text:
feat/Replace fusion charts with Echarts

Fixes #24426
Fixes #24263

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Add a TL;DR when description is extra long (helps content team)
Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change
Links to Notion, Figma or any other documents that might be relevant to the PR

PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

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

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/ok-to-test sha=f157c96

/build-deploy-preview env=release

/build-deploy-preview env=release

/ok-to-test sha=a214bec

@rajatagrawal Is the PR ready for review? I see a lot of commented code, console logs. Also please do fix the PR description

@ashit-rath
This PR isn't ready for review yet. It is still a work in progress. I think it got auto assigned to you because of code owners script. Apologies.

/ok-to-test sha=ed55c72

/ok-to-test sha=e0ce9ba

@rajatagrawal Is the PR ready for review? I see a lot of commented code, console logs. Also please do fix the PR description

@ashit-rath
This PR isn't ready for review yet. It is still a work in progress. I think it got auto assigned to you because of code owners script. Apologies.

Ahh okay, no worries

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

@Aishwarya-U-R can you please review the changes in the cypress folder ?

/build-deploy-preview env=release

/ok-to-test sha=fc9a9d9

@Aishwarya-U-R
I think I have to make some more significant changes to cypress tests. The cypress tests are not ready for review yet. Removing you from review for now. Thanks!

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/ok-to-test sha=b02c93a

/build-deploy-preview env=release

/ok-to-test sha=9ee9368

/build-deploy-preview env=release

/ok-to-test sha=409aa13

/build-deploy-preview env=release

/ok-to-test sha=09d31f7

/build-deploy-preview env=release

@rajatagrawal
Can we add in data to be seen on hover of the datapoints?
Empty states i.e, when no data is present are inconsistent.
Loom for the above two points: https://www.loom.com/share/b82963de494445a5afaffcfec9db1a3b?sid=e7e9e26f-8a86-4bff-bacb-bc4ffe26c758
Also, as discussed,
The line for pie charts needs to be removed.
Positioning of the legends to be made horizontal so there's no overlap over the graph.
Can we also change the More Details button's styling to be similar to the Connect Data button that we see on the table widget.

/ok-to-test sha=c7d9442

/build-deploy-preview env=release

@jsartisan can you please help review changes in ChartErrorComponent file ?

/build-deploy-preview env=release

/ok-to-test sha=3a32acb

Observations:

Data points are hard to read in multiple series data chart. As the datapoints are displayed above the bar. This is happening for only Bar_chart

Pie chart behaviour is not same as we have in prod today. Check the video for the difference in feature
https://www.loom.com/share/4c1d5195fe76459e8c57cedd8f904978

@rajatagrawal added some more callouts above

@rajatagrawal The error component code looks good. Just one question: Should the widget use the platform's component ( ADS Components ), or should it use wds components?
If the answer is "It should use wds components only", we will need to change the component later on once wds components are available to use.

/build-deploy-preview env=release

Tested and verified all the callouts and LGTM

Tested migration scenarios
Tested on modals and containers
Tested custom fusion charts as well
Tested error state functionalities

/ok-to-test sha=862bc41

/build-deploy-preview env=release

/ok-to-test sha=3763410

Tested this PR in new DP and it LGTM

authors: ashit-rath chandannkumar jsartisan laveena-en rajatagrawal tanvibhakta


text:
test: Cypress - progress widget cases

Added cases for:

Check Progress, Number of steps, Counterclockwise Show result elements disabled on infinite looping enablement
Check binding in Progress property
Check progress widget visibility based on visible state
Assert expected error texts

/ok-to-test

/ok-to-test

/ok-to-test


text:
chore: add action group component

Fixes #29425

Summary by CodeRabbit

New Features

Introduced a new Search functionality to the app, including a search bar in the Hero component and a Search component in the App component.

Style

Added styles for the search bar to enhance visual presentation.

/ok-to-test

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

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

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

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

authors: KelvinOm jsartisan


text:
Update useEffect dependency

Description
Update dependency
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

Please add some more info about why this change was needed

@hetunandu We were tracking props that didn't need to be tracked. It's a minor thing I noticed when fixing a merge conflict.

authors: akash-codemonk hetunandu ofpiyush


text:
scripts/install_hh_suite.sh: line 4: syntax error near unexpected token `&&'

scripts/install_hh_suite.sh
Cloning into '/tmp/hh-suite'...
remote: Enumerating objects: 9214, done.
remote: Counting objects: 100% (634/634), done.
remote: Compressing objects: 100% (183/183), done.
remote: Total 9214 (delta 448), reused 622 (delta 444), pack-reused 8580
Receiving objects: 100% (9214/9214), 23.79 MiB | 18.61 MiB/s, done.
Resolving deltas: 100% (6975/6975), done.
Note: switching to '47a835a6329e8041741160c1196bc82d718d56e0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
scripts/install_hh_suite.sh: line 4: syntax error near unexpected token &&' scripts/install_hh_suite.sh: line 4: && mkdir /tmp/hh-suite/build'

Fixed in a35c44f.

authors: gahdritz lucajovine

repo: aqlaboratory/openfold


text:
Documentation needed for Sample.create()

The documentation for Sample.create() is lacking
As a pydent developer, I would like to be able to take advantage of this method.

Is this better?
https://aquariumbio.github.io/pydent/generated/pydent.models.Sample.html#pydent.models.Sample.create
"Create" in this case is as in CRUD, which assumes the Sample has been created locally and the creation is in the Aquarium instance.
It's not really a user concept.

authors: bjkeller dvnstrcklnd

repo: aquariumbio/pydent


text:
CVE-2023-0286 found in operator related to alpine 3.16.2

latest operator scan show :

ghcr.io/aquasecurity/trivy-operator:e0ae5b9ead41962124c0e33b37b84afe693516a6-amd64 (alpine 3.16.2)
==================================================================================================
Total: 2 (HIGH: 2, CRITICAL: 0)

┌──────────────┬───────────────┬──────────┬───────────────────┬───────────────┬──────────────────────────────────────────────────────────────┐
│   Library    │ Vulnerability │ Severity │ Installed Version │ Fixed Version │                            Title                             │
├──────────────┼───────────────┼──────────┼───────────────────┼───────────────┼──────────────────────────────────────────────────────────────┤
│ libcrypto1.1 │ CVE-2023-0286 │ HIGH     │ 1.1.1q-r0         │ 1.1.1t-r0     │ [openssl: X.400 address type confusion in X.509 GeneralName] │
│              │               │          │                   │               │ https://avd.aquasec.com/nvd/cve-2023-0286                    │
├──────────────┤               │          │                   │               │                                                              │
│ libssl1.1    │               │          │                   │               │                                                              │
│              │               │          │                   │               │                                                              │
└──────────────┴───────────────┴──────────┴───────────────────┴───────────────┴──────────────────────────────────────────────────────────────┘

Same issue. Maybe need upgrade alpine version?

@drivebyer there is no official putting snapshot for now

authors: chen-keinan drivebyer

repo: aquasecurity/trivy-operator


text:
Update Plugin Artifacts Links for v0.163.9

Automated changes by create-pull-request GitHub action

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: aquasecurity/trivy-plugin-aqua


text:
Add back optional flow_id and flow_name arguments

Describe your changes and why you are making these changes
Mainly for backward compatibility. Using them shows Deprecated warning to end user.
Related issue number (if any)
ENG-3007
Loom demo (if any)
Checklist before requesting a review

[ ] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[ ] I have performed a self-review of my code.
[ ] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[ ] If this is a new feature, I have added unit tests and integration tests.
[ ] I have run the integration tests locally and they are passing.
[ ] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[ ] All features on the UI continue to work correctly.
[ ] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

Can you paste a screenshot as to what this deprecation warning looks like?

Can you paste a screenshot as to what this deprecation warning looks like?

repo: aqueducthq/aqueduct


text:
Remove pipreqsnb requirement from SDK

Following's Joey's suggestion to remove inference in OSS for now: https://linear.app/aqueducthq/issue/ENG-1191/remove-pipreqsnb-for-requirements-discovery

Other than comment @cw75 listed it looks good to me.

@kenxu95 So now, if the user manually provided a requirements.txt, we will try to install any package inside this file to the server. Otherwise, we don't attempt to infer or install anything. Is my understanding correct?

@cw75 the server will try to install whats in the zipped requirements.txt, yes. Otherwise, nothing happens.


text:
Safari: Aragon logo in header broken

This appears to now be fixed.

authors: izqui sohkai

repo: aragon/hack


text:
Translation key suggestion will be incorrect if the key is in snake_case

What version of this package are you using?
2.5.0
What operating system, Node.js, and npm version?
macOS 14.0 (Sonoma preview)
Node.JS v18.10.0
What happened?
If the translation key was in snake case, for example HELLO_WORLD

then the suggested translation key will be HELLO, which is incorrect

What did you expect to happen?
the suggested translation key showing HELLO_WORLD

Are you willing to submit a pull request to fix this bug?
I can try
possible fix is changing _${infer Num} to _${number}

Good catch. Thanks to report It! Feel free to PR!

authors: aralroca loukhin

repo: aralroca/next-translate


text:
Verbose

This PR resolves https://github.com/aramis-lab/AD-DL/issues/62.
The goal of this PR is to print messages with logging:

messages with level info / debug or less are directed to stdout,
other messages are directed to stderr.

Specific loggers are created depending on the function and formatted the message to also print the date + the name of the logger.

Once #65 will be merged, adapt the printed messages in classify with logging.
Also remove the folder test which will become obsolete.

Waiting for #71 to be merged to add verbose in transfer learning.

Hi @14thibea ,
This PR is still in draft mode... please let me know when it's ready for review !
(Maybe it should be unlinked from PR #71 which will be closed later, according to the roadmap).

Hello @14thibea! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file clinicadl/setup.py:

Line 12:9: E126 continuation line over-indented for hanging indent
Line 12:13: E251 unexpected spaces around keyword / parameter equals
Line 12:15: E251 unexpected spaces around keyword / parameter equals
Line 13:16: E251 unexpected spaces around keyword / parameter equals
Line 13:18: E251 unexpected spaces around keyword / parameter equals
Line 14:20: E251 unexpected spaces around keyword / parameter equals
Line 14:22: E251 unexpected spaces around keyword / parameter equals
Line 17:12: E251 unexpected spaces around keyword / parameter equals
Line 17:14: E251 unexpected spaces around keyword / parameter equals
Line 18:16: E251 unexpected spaces around keyword / parameter equals
Line 18:18: E251 unexpected spaces around keyword / parameter equals
Line 19:15: E251 unexpected spaces around keyword / parameter equals
Line 19:17: E251 unexpected spaces around keyword / parameter equals
Line 20:19: E251 unexpected spaces around keyword / parameter equals
Line 20:21: E251 unexpected spaces around keyword / parameter equals
Line 21:25: E251 unexpected spaces around keyword / parameter equals
Line 21:27: E251 unexpected spaces around keyword / parameter equals
Line 22:17: E251 unexpected spaces around keyword / parameter equals
Line 22:19: E251 unexpected spaces around keyword / parameter equals
Line 25:21: E251 unexpected spaces around keyword / parameter equals
Line 25:23: E251 unexpected spaces around keyword / parameter equals
Line 28:17: E123 closing bracket does not match indentation of opening bracket's line
Line 29:13: E123 closing bracket does not match indentation of opening bracket's line
Line 37:13: E123 closing bracket does not match indentation of opening bracket's line
Line 40:9: E123 closing bracket does not match indentation of opening bracket's line

repo: aramis-lab/AD-DL


text:
Multi-class classification

Provide a framework to perform multi-class classification as asked in https://groups.google.com/g/clinica-user/c/9LKl04t2wyY.

Addressed in #166

repo: aramis-lab/clinicadl


text:
Incorrect sorting with sort criteria partially covered by index

My Environment

ArangoDB Version:        3.4.8 & self-compiled devel branch
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Operating System:        Ubuntu 18.04
Total RAM in your machine:        16GB

Component, Query & Data
Affected feature:
AQL query using web interface
AQL query (if applicable):
FOR a in activities
    FILTER a.user_id == "31132147"
    SORT a.datetime DESC, a.order DESC, a._key DESC
    LIMIT 10
    RETURN KEEP(a, "_key", "name", "order", "datetime")

AQL explain (if applicable):
Query String (178 chars, cacheable: true):
 FOR a in activities
     FILTER a.user_id == "31132147"
     SORT a.datetime DESC, a.order DESC, a._key DESC
     LIMIT 10
     RETURN KEEP(a, "_key", "name", "order", "datetime")

Execution plan:
 Id   NodeType          Est.   Comment
  1   SingletonNode        1   * ROOT
 12   IndexNode          589     - FOR a IN activities   /* reverse skiplist index scan */
  6   CalculationNode    589       - LET #5 = a.`order`   /* attribute expression */   /* collections used: a : activities */
  7   CalculationNode    589       - LET #7 = a.`_key`   /* attribute expression */   /* collections used: a : activities */
  8   SortNode           589       - SORT #5 DESC, #7 DESC
  9   LimitNode           10       - LIMIT 0, 10
 10   CalculationNode     10       - LET #9 = KEEP(a, "_key", "name", "order", "datetime")   /* simple expression */   /* collections used: a : activities */
 11   ReturnNode          10       - RETURN #9

Indexes used:
 By   Type       Collection   Unique   Sparse   Selectivity   Fields                                 Ranges
 12   skiplist   activities   false    false        37.29 %   [ `user_id`, `datetime`, `_key` ]   (a.`user_id` == "31132147")

Functions used:
 Name   Deterministic   Cacheable   Uses V8
 KEEP   true            true        false

Optimization rules applied:
 Id   RuleName
  1   move-calculations-up
  2   move-filters-up
  3   move-calculations-up-2
  4   move-filters-up-2
  5   use-indexes
  6   remove-filter-covered-by-index
  7   use-index-for-sort
  8   remove-unnecessary-calculations-2

Problem:
The query optimizer recognizes correctly that the filter and the first sorting criterion are covered by the index on [user_id, datetime, _key], so it removes them. However, this still leaves the SORT node with the two remaining criteria and the query therefore produces a result that is not sorted correctly.
Expected result:
Result is sorted correctly
Workaround:
Create an index that covers all fields used for sorting.
Steps to reproduce

Create a collection activities
Insert these sample documents sample.json.gz
Create an index for [user_id, datetime, _key]
Run the query

I think the dataset does not match the query somehow.
The dataset does not include any user_id attributes for any of the documents.
However, I will make up some data on my own and try to reproduce.

Reproduced. Looking into it...

Right, sorry. I simply took the result of the query and forgot that it doesn't include a user_id.

The above PRs address this issue.
They are expected to land in

3.4.9: https://github.com/arangodb/arangodb/pull/10444
3.5.4: https://github.com/arangodb/arangodb/pull/10443
devel: https://github.com/arangodb/arangodb/pull/10442

authors: jsteemann mpoeter

repo: arangodb/arangodb


text:
don't return any in-progress indexes

Scope & Purpose
Don't consider in-progress indexes when determining the set of available indexes to be used for AQL queries. It seems that at least in the cluster such indexes could be shown and considered useful for supporting AQL queries.
Enterprise companion PR: https://github.com/arangodb/enterprise/pull/357

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

Testing & Verification
This change is already covered by existing tests, such as shell_server_aql.
Also added a new test for this.

http://jenkins.arangodb.biz:8080/job/arangodb-ANY-linux-matrix/583/

https://172.16.10.101/view/PR/job/arangodb-matrix-pr/7167/

Tests blue.


text:
bug-fix/internal-issue-#724

fix for issue 2 mentioned in https://arangodb.atlassian.net/browse/DEVSUP-596

superseded with #12055


text:
[3.7] Index Count Optimization Uniqueness

Scope & Purpose
Bugfix for https://github.com/arangodb/arangodb/issues/13675

[x] :hankey: Bugfix (requires CHANGELOG entry)
[x] :book: CHANGELOG entry made

Backports:

[x] Backports required for: to be decided

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

[x] GitHub issue / Jira ticket number: https://github.com/arangodb/arangodb/issues/13675

Testing & Verification

[x] The behavior in this PR was manually tested
[x] This change is already covered by existing tests, such as (please describe tests).
[x] This PR adds tests that were used to verify all changes:

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

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


text:
Bug fix 3.3/agency fix for last confirmed

Can we try this fix sooner? Since we are running clusters, it's really bad that it's in an unstable state.

Ditching this for new backport from devel

authors: dsonet kvahed


text:
ensure all system attributes are properly indexed by ArangoSearch view

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

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr/2533/

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


text:
🛑 Test loibra.moo.com is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Test loibra.moo.com is back up in eb138f5.

repo: aratan/Monitorizaci-n


text:
🛑 Test loibra.moo.com is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Test loibra.moo.com is back up in 5d04cb7.


text:
🛑 Test loibra.moo.com is down

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

HTTP code: 0
Response time: 0 ms

Resolved: Test loibra.moo.com is back up in f387c8b.


text:
🚀 Feature:  Link with download to source document

🔖 Feature description
Currently the Source info does not provide a link to the original document used to locate the answer.
🎤 Why is this feature needed ?
This allows the user to better understand where the answer has been build from give a chance  to verify and get more trust .
✌ How do you aim to achieve this?
If the document is uploaded it shall be stored and kept for linking as download below the answer.
🔄 Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?

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

Are you willing to submit PR?
None

Can you please assign this issue to me? I would like to work on it.

I would like to work on it.

Hmmm, I agree that its cool to allow users to download the document, but I think we will have to come back to this issue later as currently we need to plan where user will download it from in the UI. And if its practical to store original document.

authors: cforce dartpain manish7017


text:
Fix units and results for dhw storage

In Calc_ThermalLoads, the dhw return temperature in db and unit for mcpww is fixed, documentation for calc_dhw_heating_demand was added.

must this be added for the conference?

yes... otherwise some part of the results will not make sense.
but please wait until I finish testing Jimeno's new commit!

authors: daren-thomas shanshanhsieh

license: mit


text:
Content having '\n' not breaking to new line

Is this a bug report or a feature request?
Bug report

Have you read the guidelines regarding bug report?
Yes
Have you read the documentation in its entirety?
Yes
Have you made sure that your issue hasn't already been reported/solved?
Yes
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
Both the platforms
Is the bug reproductible in a production environment (not a debug one)?
Yes
Have you been able to reproduce the bug in the provided example?
No

Environment

React: 16.8.3
React native: 0.59.8
react-native-render-html: 4.1.2

Target Platform:
  Android (9.0)
  iOS (12.1)

Steps to Reproduce

(Write your steps here:)

HTML content with '\n' for new line break.
After rendering html content , '\n', is not getting break to new line.

Expected Behavior

To get the html content break to new line with '\n'.

Actual Behavior

The line is not breaking with '\n'.

Thanks

You can use
 for line break in HTML.

@lengieng ,
There are some limitations in providing
 for line break in HTML content. The line break is denoted by '\n' in HTML content.

@akhilsanker , what is the reason of using \n instead of
? \n is not a valid HTML tag. Therefore, it makes sense that the html parser won't pass it. Does your HTML content contain a code block which should be wrapped by
 tag?

I am closing this issue because, as commented, \n is not interpreted in html.

authors: akhilsanker jsamr lengieng

repo: archriss/react-native-render-html


text:
Jobs\MigrateDatabase fails using TenantDatabaseManagers\PostgreSQLSchemaManager::class

Bug description
Hello,
Jobs\MigrateDatabase fails using driver TenantDatabaseManagers\PostgreSQLSchemaManager::class
7 ERROR: no schema has been selected to create in at character 14 at /opt/eom/vendor/laravel/framework/src/Illuminate/Database/Connection.php:545)

If I migrate tenants table with artisan, it works. It only fails when on Events\TenantCreated jobs
I've tested tooo with the other pgsql driver TenantDatabaseManagers\PostgreSQLDatabaseManager::class
And I'm unable to create database.  Note that I'm using postgres user so, it should let me create anything!
a transaction block (SQL: CREATE DATABASE "tenant_e35341a4-4e84-4618-87d4-590726edb9b3" WITH TEMPLATE=template0)

[previous exception] [object] (PDOException(code: 25001): SQLSTATE[25001]:
Active sql transaction: 7 ERROR:  CREATE DATABASE cannot run inside
a transaction block at /opt/eom/vendor/laravel/framework/src/Illuminate/Database/Connection.php:545)
[stacktrace]

So, Ive come back to TenantDatabaseManagers\PostgreSQLSchemaManager driver as at least it let me create the database.
I've take a look to Jobs\MigrateDatabase code and I've seen. that exec  Artisan command.
So I've tried to exec the same command  on shell and it works well.
php artisan tenants:migrate --tenants=f74739bd-51c6-44eb-a2c9-da474b7c5147

I've dumped baseConfig from TenantDatabaseManagers\PostgreSQLSchemaManager driver when Jobs\MigrateDatabase is running. And It looks fine  as  search_path is set to the correct schema.
[2023-01-09 11:08:51] local.INFO: Array
(
    [driver] => pgsql
    [url] =>
    [host] => 127.0.0.1
    [port] => 5432
    [database] => eom
    [username] => postgres
    [password] => **********
    [charset] => utf8
    [prefix] =>
    [prefix_indexes] => 1
    [search_path] => tenant_1b38fc06-86eb-45fd-afea-14cc5558cbca
    [sslmode] => prefer
)

I don't think that is permissions issue as I'm using postgres user and moreover it works from console.
Any ideas? I can't progress  on my project due to this issue.
Thank you for the help
Regards
Steps to reproduce
Setup laravel tenancy using boilerplate and set tenant database driver to  TenantDatabaseManagers\PostgreSQLSchemaManager::class
You must enable  Jobs\MigrateDatabase into app/Providers/TenancyServiceProvider.php too
Expected behavior
Job should runs without error and migrate all tenants tables
Laravel version
9.19
stancl/tenancy version
3.6

@abrardev99 Try to reproduce this tomorrow (using boilerplate code as mentioned in the reproduction steps)

I've just do it, with just boilerplate and occur the same issue. It looks that the problem occurs when you create tenant using Nova4.

Nova doesn't let to create database but using schema it neither works.  Moreover, queued job, ran out of Nova, so it should works  isn't it?

I've just try back with schema  and queue job and nothing. Same error ...

Can you send me references , I've searched myself on issue tracker and discord server but I haven't been able to found anything

Working solution based on https://github.com/laravel/nova-issues/issues/180#issuecomment-433493057
class CreateTenant extends Action implements ShouldQueue
{
    use InteractsWithQueue;
    use Queueable;

    public $withoutActionEvents = true;

    public $confirmButtonText = 'Create Tenant';

    /**
     * @throws Throwable
     */
    public function handle(ActionFields $fields): void
    {
        DB::commit();

        $tenant = Tenant::create(['name' => $fields['name']]);
        $tenant->domains()->create(['domain' => $fields['domain']]);
    }

    public function fields(NovaRequest $request): array
    {
        return [
            Text::make('Project Name', 'name')
                ->rules(['required', 'string', 'max:30', 'unique:tenants,name'])
            ,
            Text::make('First Domain', 'domain')
                ->rules(['required', 'string', 'unique:domains,domain'])
            ,
        ];
    }
}

authors: abordage scramatte stancl

repo: archtechx/tenancy


text:
Domain tenant routes not scoped from console

Bug description
When using tenant-aware commands, routes generated are invalid as they are missing the domain component.
As a consequence of this, any generated notifications will also have invalid URLs and links.
A possible cause is that the tenant routes are loaded before identifying a tenant. The following iteration through TenantAwareCommand::getTenants() does not reload the routes and applies the domainless tenants across all tenants.
Steps to reproduce
<?php

namespace App\Console\Commands;

use Illuminate\Console\Command;
use Stancl\Tenancy\Concerns\HasATenantsOption;
use Stancl\Tenancy\Concerns\TenantAwareCommand;

class TestTenantCommand extends Command
{
    use TenantAwareCommand;
    use HasATenantsOption;

    /**
     * The name and signature of the console command.
     *
     * @var string
     */
    protected $signature = 'test-tenant-command';

    /**
     * The console command description.
     *
     * @var string
     */
    protected $description = 'Test tenant command';

    /**
     * Execute the console command.
     *
     * @return int
     */
    public function handle()
    {
		dd(route('insert-tenant-route-here'));

        return 0;
    }
}

Run the command:
`php artisan test-tenant-command`

### Expected behavior

The expected output is:
`https://tenant.central-domain.com`

Instead, the output will be:
`https://central-domain.com`

### Laravel version

10.23.1

### stancl/tenancy version

3.7.2

There seem to be problems posting


text:
Feature/update resource in central database

This PR introduces the possibility of creating a resource in the central database related to a resource from the tenant database only with synced attributes if this resource doesn't exist.
Solution
PR introduces the new config key, which is a boolean with a "false" default value.
Usage
Set the value of the following config key to "true" for enabling this possibility.
'created_only_with_synced_attributes' => true,

I recommend opening a feature request issue describing what you're trying to achieve first, before opening a PR. As I mentioned, we changed resource syncing a lot in v4.

authors: ovidiu-serafim stancl


text:
这个官网示例不太对

应该是数组

@tanhh326 感谢反馈，这里的文档有错误，应该是 icon: ()=>VNode

repo: arco-design/arco-design-vue


text:
当前页面关闭，a-date-picker，icon等元素一直存在已分离的被js引用的元素里不释放，这是什么原因？

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

Basic Info

Package Name And Version: @arco-design/web-vue@2.56.3
Browser: chrome130.0.0.0
Reproduction Link: https://github.com/KaiChow/arco-design-issue

找到其他的问题了

是有问题


text:
InputNumber支持点击＋－号时的回调

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

Basic Info
What are the similar cases of this feature
onChange
What problem does this feature solve?
支持点击按钮的时候可以根据步长自动将值修正为符合条件的值

onchange 的时候直接修正为符合格式的值，并且通过 value 设置给 inputnumber 就行？

场景需要支持输入非步长的值，在加减等快捷操作中可以纠正非步长的值

2.61.0 为 onChange 提供了第二个参数来标记组件值改变的原因，点击 "+/-" 按钮分别对应 increase 和 decrease。

authors: MisterLuffy rookiell yinkaihui

repo: arco-design/arco-design


text:
Undefined symbols for architecture armv7

ios debug可以用,打包ipa报错
ld: warning: ignoring file /Users/ieducc/develop/cloud/flutter_cloud/ios/Pods/ScanKitFrameWork/scansdk-ios-tool-1.0.2.300/ScanKitFrameWork.framework/ScanKitFrameWork, missing required architecture armv7 in file
    /Users/ieducc/develop/cloud/flutter_cloud/ios/Pods/ScanKitFrameWork/scansdk-ios-tool-1.0.2.300/ScanKitFrameWork.framework/ScanKitFrameWork (2 slices)
    Undefined symbols for architecture armv7:
      "_OBJC_CLASS_$_HmsBitMap", referenced from:
          objc-class-ref in FLScanKitView.o
          objc-class-ref in FlutterScankitPlugin.o
      "_OBJC_CLASS_$_HmsDefaultScanViewController", referenced from:
          objc-class-ref in FlutterScankitPlugin.o
      "_OBJC_CLASS_$_HmsCustomScanViewController", referenced from:
          objc-class-ref in FLScanKitView.o
      "_OBJC_CLASS_$_HmsScanOptions", referenced from:
          objc-class-ref in FLScanKitView.o
          objc-class-ref in FlutterScankitPlugin.o
    ld: symbol(s) not found for architecture armv7
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    note: Using new build system
    note: Building targets in parallel
    note: Planning build
    note: Analyzing workspace
    note: Constructing build description
    note: Build preparation complete

在xcode12要怎样设置才能移除armv7支持

@git-boya
华为 scankit 是不开源的，以二进制形式分发。目前scankit framework中并不包含armv7架构的二进制，因此Flutter打包时不要添加armv7架构。
选择 Build Setting， 搜索 VALID_ARCHS，然后去掉 armv7 选项。注意：debug 和 release 都删掉

@git-boya
华为 scankit 是不开源的，以二进制形式分发。目前scankit framework中并不包含armv7架构的二进制，因此Flutter打包时不要添加armv7架构。
选择 Build Setting， 搜索 VALID_ARCHS，然后去掉 armv7 选项。注意：debug 和 release 都删掉

xcode12 没有VALID_ARCHS了
网上查是用Excluded Architectures设置,我这么设置还是编译不过去.ios不太会弄啊

选择 Build Setting， 搜索arm

感谢作者 问题解决了

谢谢作者 解决了

同楼上 报错

您好，我还是想问问怎么加armv7，我的project和targets都加了怎么打包还是报错？？（插件用的是1.2.3版本）

@weigoudan
我上面已经说了，华为这个库不支持armv7

改Architectures那项试试

改Architectures那项试试
谢了，就是这个，后面重新把工程里的pod有关的全删了再重新pod install才可以，有毒

我已经是按照图上的配置的，但是还是有异常呀，有人能救救我吗？

@xiejibiao 1. 只能用真机 2. 删除缓存,重新pod install 试一试

hi, did these solutions work for you?

yes

如果不能解决，可以考虑使用google mlkit库来替代，pub上有很多相关的插件

authors: EmreSURK MakenChan arcticfox1919 git-boya guicai666 peakandyuri weigoudan xiejibiao zkooo


text:
color fixes

Hi. I noticed a few color issues that I corrected. I don't have True Color, as I use rxvt-unicode, but I set my term colors (in ~/.Xresources) to the nord palette, and I also checked everything in gvim.
I love nord (switching from solarized and hybrid/hybrid-material), but I noticed that when I first loaded it, I got a lot of wonky colors (as a few others have mentioned).
I saw this (and this is in gvim, but I see the same thing in vim/nvim):

As you can see, the Folds and Comments are almost invisible, and when you search, the IncSearch looks awful as does the Search.
So, I added this to my vimrc:
highlight Folded cterm=italic,bold ctermbg=0 ctermfg=12 guibg=#3B4252 guifg=#81A1C1
highlight Comment ctermfg=12 guifg=#81A1C1
highlight Search ctermbg=3 ctermfg=0 guibg=#EBCB8B guifg=#3B4252
highlight IncSearch ctermbg=8 guibg=#4C566A

The results look like so:

You don't have to incorporate the italic,bold on Folded, but I like it. Moreover, these small highlights seem to make it look much better.
It's quite late; so, I haven't looked at the nord.vim colorscheme file, but if you'd like me to submit a pull request, let me know. If not, hopefully this can help make nord the best!
Thanks for this great palette!
~ dylnmc

Thanks for your report :+1:
The problem with the unreadable foreground on pending search highlights has already been reported in #32. Please subscribe there for updates.
Thanks for your proposal regarding the comments, but this change is absolutely against the design style guide of Nord.
The low contrast has been selected specifically to not disturb code flow and keep the focus of the developer on the code. Using a color like e.g. nord8 for it would completely mix the separation between the code and comments. nord8 is used for classes/types/interfaces/documentation tags and you would be unable to differ if it is part of the running code or just a comment.
It is totally fine that you not agree to all highlighting color assignments, everyone has different preferences.
If you'd like to stay with nord8 for comments just paste this snippet into your ~/.vimrc somewhere before you set the color scheme via colorscheme nord and than add your custom syntax highlighting rules you want to override for the Nord Vim theme:
augroup nord-overrides
  autocmd!
  autocmd ColorScheme nord highlight Folded cterm=italic,bold ctermbg=0 ctermfg=12 guibg=#3B4252 guifg=#81A1C1
  autocmd ColorScheme nord highlight Comment ctermfg=12 guifg=#81A1C1
  autocmd ColorScheme nord highlight Search ctermbg=3 ctermfg=0 guibg=#EBCB8B guifg=#3B4252
  autocmd ColorScheme nord highlight IncSearch ctermbg=8 guibg=#4C566A
augroup END

The overriden rules will only be applied for Nord and won't affect other themes.

Duplicate of #32

authors: arcticicestudio dylnmc

repo: arcticicestudio/nord-vim


text:
Including nullable/optional navigation property causes only non-nullable connected objects to be returned

This is a bit of a head scratcher. Using the following specification with includes:
    // Define the return
    ISpecificationBuilder<Entities.AuditTrail, ListSievedModel>
      select = Query.Select(
      x => new ListSievedModel
      {
          Id = x.Id,
          Created = x.Created,
          Modified = x.Modified,
          State = x.State,
          OperationType = x.OperationType,
          ForEntity = x.ForEntity,
          Username = x.Username,
          TrackingKey = x.TrackingKey,
          RelStateName = x.RelState.ShortName,
          RelOperationTypeName = x.RelOperationType.ShortName,
          RelForEntity = x.RelForEntity,
          RelForEntityTitle = (x.RelForEntity == null) ? string.Empty : x.RelForEntity.ToString(),
          RelForEntityType = (x.RelForEntity != null) ? x.RelForEntity.EntityType : string.Empty
      });

    // Add Includes
    Query.IgnoreAutoIncludes();
    Query.Include(s => s.RelState);
    Query.Include(s => s.RelOperationType);
    Query.Include(s => s.RelForEntity).AsSplitQuery();

Creates two different data sets when repository.CountAsync and repository.ListAsync are run. CountAsync returns all projected objects regardless of whether s.RelForEntity is null or not null. ListAsync only returns the not-null s.RelForEntity projections.
The result is as follows from a web api:
{
"pagedInfo": {
"pageNumber": 1,
"pageSize": 20,
"totalPages": 2,
"totalRecords": 24
},
"value": [
{
"id": "3739c90a-47b2-4836-808f-65a57e18db20",
"created": "0001-01-01T08:00:00Z",
"modified": "0001-01-01T08:00:00Z",
"state": 5,
"operationType": 2,
"forEntity": "014b8736-1749-49f7-8e78-cd8b42a8c3e9",
"username": "",
"trackingKey": "014b8736-1749-49f7-8e78-cd8b42a8c3e9",
"relStateName": "Enabled",
"relOperationTypeName": "Insert",
"relForEntityTitle": "Four score and 7 hyars on 7/26/2023 8:16:55 PM ",
"relForEntityType": "Vantedge.Portfolio.Domain.Entities.Comment"
},
{
"id": "9ebc8c10-67f3-4ffe-a08f-aa7a512ce35c",
"created": "0001-01-01T08:00:00Z",
"modified": "0001-01-01T08:00:00Z",
"state": 5,
"operationType": 2,
"forEntity": "1e921c37-127b-43d3-ae59-a60a2fafa4ff",
"username": "",
"trackingKey": "1e921c37-127b-43d3-ae59-a60a2fafa4ff",
"relStateName": "Enabled",
"relOperationTypeName": "Insert",
"relForEntityTitle": "This is a test on 7/26/2023 8:10:46 PM ",
"relForEntityType": "Vantedge.Portfolio.Domain.Entities.Comment"
},
{
"id": "e39ff253-4c45-4488-b831-ad45d54a79a4",
"created": "0001-01-01T08:00:00Z",
"modified": "0001-01-01T08:00:00Z",
"state": 5,
"operationType": 3,
"forEntity": "f8a41f37-f4ff-4404-ad31-15105a349ac6",
"username": "",
"trackingKey": "f8a41f37-f4ff-4404-ad31-15105a349ac6",
"relStateName": "Enabled",
"relOperationTypeName": "Update",
"relForEntityTitle": "TTTTTEEEEESSSSSST",
"relForEntityType": "Vantedge.Portfolio.Domain.Entities.Market"
},
{
"id": "f0bc4bee-2ea5-42c4-9d81-e95d6b5bab23",
"created": "0001-01-01T08:00:00Z",
"modified": "0001-01-01T08:00:00Z",
"state": 5,
"operationType": 2,
"forEntity": "f8a41f37-f4ff-4404-ad31-15105a349ac6",
"username": "",
"trackingKey": "f8a41f37-f4ff-4404-ad31-15105a349ac6",
"relStateName": "Enabled",
"relOperationTypeName": "Insert",
"relForEntityTitle": "TTTTTEEEEESSSSSST",
"relForEntityType": "Vantedge.Portfolio.Domain.Entities.Market"
},
{
"id": "99047ee3-6a11-4b8c-9502-fea8bb8fffa6",
"created": "0001-01-01T08:00:00Z",
"modified": "0001-01-01T08:00:00Z",
"state": 5,
"operationType": 2,
"forEntity": "dd02898a-72c6-456c-a972-5db9a327bcf5",
"username": "",
"trackingKey": "dd02898a-72c6-456c-a972-5db9a327bcf5",
"relStateName": "Enabled",
"relOperationTypeName": "Insert",
"relForEntityTitle": "Keep this on 7/26/2023 8:17:24 PM ",
"relForEntityType": "Vantedge.Portfolio.Domain.Entities.Comment"
}
],
"valueType": "System.Collections.Generic.List`1[[Vantedge.Portfolio.Api.Endpoints.AuditTrails.CommandsAndResults+PagedResult, Vantedge.Portfolio.Api, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]], System.Private.CoreLib, Version=7.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e",
"status": 0,
"isSuccess": true,
"successMessage": "",
"correlationId": "",
"errors": [],
"validationErrors": []
}
Notice "totalRecords": 24 which is resolved from CountAsync . The actual data is from ListAsync which uses the exact same specification. The missing results are the null s.RelForEntity projections.
Any help would be much appreciated.
Cheers.

Hey @jeffreymonroe
I don't see it in your example, but you have Take/Skip somewhere right? The CountAsync method in the built-in repository is a bit special, it doesn't include all evaluators. For instance, Take and Skip are omitted. Actually, all evaluators with IsCriteriaEvaluator false are omitted.
This was a community request and it makes the pagination code simpler. You don't have to create two specs, one without pagination, and another one with pagination. Instead, you can use the same specification for counting all records, and also getting the list of records per page. Let's assume this specification
public class CustomerSpec : Specification<Customer>
{
    public CustomerSpec()
    {
        Query.Where(x => x.Age > 20)
            .Skip(10)
            .Take(10);
    }
}

If you call CountAsync using this spec, you'll get all customers satisfying the criteria. And if you call ListAsync with the same spec, will return only the second 10 records.
Omitted evaluators:

PaginationEvaluator - Take/Skip
OrderEvaluator - OrderBy/ThenBy
IncludeEvaluator - Include/ThenInclude

Note: Not particularly related to this issue, but I want to mention the following. Whenever you use projection (the Select statement), EF ignores all your Include statements. The logic behind it is that you anyway not returning entities back, but some projections, so all explicit Includes are ignored. If there is navigation usage inside your Select statement, EF automatically will add the join statements in the generated query.

Hi @fiseni
Thanks for the thorough explanation. I thought this was the case and I do agree with using the same specification for CountAsync and ListAsync. I am using a modified version of Sieve (https://github.com/Biarity/Sieve) which can be utilized with Specification. The Skip/Take are handled in Sieve.
In regards to optional navigation properties, I continue to have issues when including an optional navigation property inside a projection. See below:
      // Projection
       ISpecificationBuilder<Entities.AuditTrail, ListSievedModel> select = Query.Select(
          x => new ListSievedModel
          {
              Id = x.Id,
              Created = x.Created,
              Modified = x.Modified,
              State = x.State,
              OperationType = x.OperationType,
              ForEntity = x.ForEntity,
              Username = x.Username,
              TrackingKey = x.TrackingKey,
              RelStateName = x.RelState.ShortName,
              RelOperationTypeName = x.RelOperationType.ShortName,
              // RelForEntity = (x.RelForEntity == null) ? null : x.RelForEntity
              //RelForEntityTitle = (x.RelForEntity == null) ? string.Empty : x.RelForEntity.ToString(),
              //RelForEntityType = (x.RelForEntity != null) ? x.RelForEntity.EntityType : string.Empty
          }); ;

        // Add Includes
        Query.IgnoreAutoIncludes();
        //Query.Include(s => s.RelState);
        //Query.Include(s => s.RelOperationType);
        //Query.Include(s => s.RelForEntity).AsSplitQuery();

        Query.AsNoTracking().ApplySieve(sieveProcessor, sieveModel);

This code will return all projections where s.RelForEntity is null or not null. When I uncomment RelForEntity = (x.RelForEntity == null) ? null : x.RelForEntity I only get projections where s.RelForEntity is not null.
I suspect this is not a Specification issue, but something more general in EF. I was hoping you would have some insight.
Cheers and thanks again.

After setting this aside and then reviewing, I was able to fix this issue. Indeed it had nothing to do with Specification and everything to do with the EF configuration for the two related objects. I had to set the navigational property as nullable then define the relationship as IsRequired(false).
Cheers and I will mark this as closed.

authors: fiseni jeffreymonroe

repo: ardalis/Specification


text:
Fix typo in StringCalculator instructions

I believe the sample input should include the new line character, because, as explained in step 4, it needs to be on a separate line.

I think so, too. Good catch!

authors: ardalis gsaslis

repo: ardalis/kata-catalog


text:
Improve library manager option docs

I think this is accurate from 30 seconds reading their docs, but please feel free to correct it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant peternewman

repo: arduino/arduino-lint-action


text:
ADBDEV-5265: psql: show proper row count in \x mode for zero-column output [backport]

psql: show proper row count in \x mode for zero-column output
Also, fix pager enable selection for such cases, and other cleanups for
zero-column output.

Allure report https://allure.adsw.io/launch/68027

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1229397

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1229398

cherry-picked commit message should contain link/hash of cherry-picked commit

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1234574

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1234575

authors: BenderArenadata KnightMurloc RekGRpth

repo: arenadata/gpdb


text:
State is not saved when client error

Quite often when a player disconnect, an client error is thrown which prevent the state from being saved here
  aiter(
    combineAsyncIterators(
      actions[Symbol.asyncIterator](),
      packets,
      ...blockchain.sources
    )
  )
    .map(transform_action)
    .reduce(
      (last_state, action) => {
        const state = reduce_state(last_state, action)
        events.emit('state', state)
        return state
      },
      { ...initial_state, ...player_state }
    )
    .then(save_state)
    .catch(error => {
      // TODO: what to do here if we can't save the client ?
      log.error(error, 'State error')
    })

how can we get the final state to call save_state in a .finally ?

I observed that too. The root issue for me is that the "actions" stream and the reduce body should never throw errors, currently I guess that this is an unwanted behavior from events.on (it listen to the error event) on the packets stream
We could also as a mitigation (for future errors) for that to catch the error and try to save the get_state value, however I'm not a big fan of adding this now because we might in the future store the whole state updates of the player

authors: DeltaEvo Sceat

repo: aresrpg/aresrpg


text:
[PasscodeLock]Add Language Select

[PasscodeLock]Add Language Select
I want to translate this plugin to Russian, Ukrainian and Belarusian.

So you're suggesting me to translate the plugin into different languages?

I suggest that the choice of localization be made in the settings. I will translate the plugin into these 3 languages.

Create a translations page on crowdin so that people can localize for their languages, I think for such a plugin it will not be superfluous.
Well, I think Danik wanted to convey this idea so that this plugin would be translated, So it seems to be clear who and what to poke, but for convenience it would not be superfluous to read in your own language

Translate here: https://crwd.in/betterdiscord-passcodelock


text:
Update footer of index.html

Please review it as I have fixed the issue with the Footer.
Related Issue
Issue no.- #825 and #985
Description
In Issue #825, the footer occupies a lot of space and is not aligned properly.
In #985, The content of the footer is overlapping and also cut from window
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Before:

After:

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:

There have some conflict issue check it once and then make a new PR ok.

@arghadipmanna101 I have resolved the conflict. please check it once again.

Work on the updated website. Link : - https://flipkart-clone-seven-azure.vercel.app/


text:
Adapt component colors to screen configuration

Is your feature request related to a problem? Please describe.
My high-contrast screen wasn´t able to show faded/transparent UI components properly.
Describe the solution you'd like
@keithCuniah told me this might be resolved with adaptive UI components.
Describe alternatives you've considered
Change the contrast of my screen.
Additional context
N.A.

@davidberenstein1957 could you please share a screenshot

repo: argilla-io/argilla


text:
create equally sized batches before/during rg.log

Is your feature request related to a problem? Please describe.
I just wanted to upload 35K records and logging is not as robust as I would like.
Describe the solution you'd like
Ideally, I would like to divide records based on the allowed batch size, while equally dividing the text lengths over these batches. IMO, this could already alleviate some of the problems relatively easily. And this might also help with assessing and analyzing payload limitations(each payload is roughly equal in this case).
Describe alternatives you've considered
N.A.
Additional context
N.A.

Note that, batches should be equally sized based on the number of bytes of the sum of the records per batch. This will help smoothen logging behaviour.


text:
[BUG-UI/UX] Keyboard shortcuts do not work in bulk mode for classification

Describe the bug
I am using a Classification dataset to annotate some texts and I am not able to use keyboard shortcuts.
To Reproduce
Steps to reproduce the behavior:

Bulk view
Select one or various observations.
Keyboard shortcut to classify in one of the labels do not select the label.

Expected behavior
I would like to be able to use keyboard shortcuts in bulk mode similar to the single mode annotation workflow.

Hi @pelayoarbues ! You probably need to hit tab after making the selection to reactivate the form and then you should be able to enter the shortcut. If this is still too cumbersome we can try to find a solution to this.
cc @damianpumar @Amelie-V

It's not cumbersome, but it is not intuitive unless clearly stated to the user.

authors: nataliaElv pelayoarbues


text:
chore: remove invalid unit test

Signed-off-by: John Pitman jpitman@redhat.com
What type of PR is this?
/kind chore
What does this PR do / why we need it:
As part of PR: https://github.com/argoproj-labs/argocd-operator/pull/647 I inadvertently committed an invalid unit test.  This PR is to remove that test.
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

How to test changes / Special notes to the reviewer:
Run REDIS_CONFIG_PATH="$PWD/build/redis" make test.  The tests should complete without errors.

Thanks!! that showed so many errors , i thought issue with my code

repo: argoproj-labs/argocd-operator