plasma5: 5.21.3 -> 5.21.4

Motivation for this change
This has a fix badly needed for plasma wayland and key remapping.
Let's send it to staging as we have frameworks 5.80 waiting there.
Will build and run over the weekend for testing.
Cc: @NixOS/qt-kde
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 119598 at 2ef27e26 run on x86_64-linux 1

227 packages marked as broken and skipped:

libsForQt512.akonadi-calendar
libsForQt512.akonadi-import-wizard
libsForQt512.akonadi-search
libsForQt512.akonadiconsole
libsForQt512.akregator
libsForQt512.alkimia
libsForQt512.baloo-widgets
libsForQt512.bluedevil
libsForQt512.bomber
libsForQt512.bovo
...

258 packages skipped due to time constraints:

ajour
amarok (amarok-kf5)
calligra
carla
colord-kde
digikam
fly
grit
httpx
kdev-php
...

2 packages built successfully:

entt
nimmm

4 suggestions:

warning: missing-phase-hooks
checkPhase should probably contain runHook preCheck and runHook postCheck.
Near pkgs/servers/rippled/default.nix:156:3:
    |
156 |   checkPhase = ''
    |   ^

warning: unclear-gpl
gpl3 is a deprecated license, please check if project uses gpl3Plus or gpl3Only and change meta.license accordingly.
Near pkgs/applications/terminal-emulators/nimmm/default.nix:51:5:
   |
51 |     license = licenses.gpl3;
   |     ^

warning: missing-phase-hooks
buildPhase should probably contain runHook preBuild and runHook postBuild.
Near pkgs/applications/terminal-emulators/nimmm/default.nix:39:3:
   |
39 |   buildPhase = ''
   |   ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/terminal-emulators/nimmm/default.nix:44:3:
   |
44 |   installPhase = ''
   |   ^

I think you added a few commits by accident to this PR.

I think you added a few commits by accident to this PR.

I was targetting the wrong branch, thanks!

@ofborg eval

Works fine here.


ChroniquesGalactiques Version 4.4.0

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ ] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Corrected a bug in the ability rolls buttons on new sheets
Added support for a configurable list of skills

Character Sheet Info Roll20 Internal Use only.


google domains

wondering if a plugin for google domains and its DNS is needed ?

I would recommend using DNS challenge delegation for Google domains, since they don't have a sensible API. The duckdns plugins explicitly supports this:
https://github.com/caddy-dns/duckdns#challenge-delegation

Will be working on this shortly.

(... still waiting, I was reached out to by the Google Domains team about a possible API, but haven't heard back)

Google has finally announced their implementation of a (basic) API to manipulate DNS records, but only for the purposes of ACME challenges.
This has been implemented in caddy-dns/google-domains. We were fortunate enough to be able to test this integration before the launch.
I'm going to close this issue, since I think it was originally opened for the purpose of solving ACME challenges and getting certificates, which is now functional. And since they don't have a general DNS record manipulation API, we can't implement that anyway.

Sigh. Unsurprisingly, Google Domains is shutting down in a few months: https://newsroom.squarespace.com/blog/googledomains
What a trashfire of a product.


Add Support for Browser Web

Summary
With the current setup, we have to manually add the (very long) browser js tag to our root page (for example, in Vue3, the index.html page). If our app is also using capacitor, we now have to set a flag to determine whether or not to use the browser lib, or the capacitor/native package. This also adds more bloat to our apps.
Desired Behavior
Given that all the methods are already set up and integrated with the native SDKs, additional support to add the browser-based tracking would be ideal. This way we can use the same methods, and depending on the runtime (is IsPlatform), they get shipped to the right place.
Possible Solution
N/A
Additional context
Sentry, Bugsnag & Segment all support hybrid (web and native) approaches using a single interface, for capacitor projects.

@vanpyrzericj we already have our browser agent for this.


changed according to the pep8 standards

Merging this pull request. Need to test the branch after merge.


Audit log search is client side only

Needs to be server side.
Add new API endpoint which accepts filter elements:

Text String
Project ID
Environment IDs

And returns pageable results.

Adds a query param named search to search logs https://github.com/Flagsmith/flagsmith/pull/633

https://github.com/Flagsmith/flagsmith/pull/653 As of this, frontend for this will be live under the flag audit_api_search, the remote config value of this flag determines the page size


Updates on add-update-metadata

I add the parser "branch" that allows to provide the desired branch or tag from which the metafiles should be updated from and the necessary changes throughout the script.
I also included a check if the chosen branch/tag exists and made some changes to the 'report_script_version' function because it wasn't working.

Here are some remarks that were raised for the update-metadata script but also apply here:
You raised the point yourself that fetching everything from the remote (github) hits the API rate limit even though we are not yet doing many things. Hence, the implementation should pull the template repository with something like git pull --all and then update from the local copy to avoid rate limiting.
This has now been implemented. The requested branch/version tag will be downloaded if not already present in the a 'temp' folder of the project folder. The user has the option to keep those files (default is False) If the folder exists the files will be updated via git pull --all.
The code is not readily designed to run in batches, i.e. the call to update the workflow files should be encapsulated in a function that can be called on a workflow directory (plus some parameters if necessary).
The code was altered to make it more modular.
repeated calls to standard library functions such as subprocess.run should always be encapsulated in a separate function (see actually how this is done (e.g., see how this is done in the Snakemake template for calls to rsync or for writing log messages in the commons::pyutils.py module).
The subprocess.run functions have not yet been encapsulated in a separate function; however, the call is a one liner for most occurrences. Repeated parts like the "Yes/No" questions have been transitioned into a function
The code has not been reformatted with black; the changes are minor, though
That has been done
None of the functions actually has a docstring explaining what the function should do - it's really difficult to follow the logic of the code
A docstring has been added each function and also additional information regarding certain parts within functions have been added. Also the strings of returns have been removed and functions have been shortened where possible to make it hopefully easier to follow the logic of the code.
Some additional features were add, e.g. dry-run option is now implemented, metadata files are not downloaded separately but stored in a temp folder that will be deleted when the script finishes (or can be kept if the user selects this newly included option). Checks if the repo and or the branch/version tag are present have been implemented.

@svenwillger
I just did a test run and on the basis of the command line help, I have trouble understanding what the point of this temp folder is and why the metadata repository is checked out into a subfolder of the repository that is supposed to be updated? That is quite a no-go because you are altering the layout and content of a folder (= the repository to be updated) that is under version control by git. In the worst case, if the user misses that, they might add/commit all that into their repository, which would cause quite a hassle.
In other words, the clone/checkout location for the metadata repository should simply be next to the project repository (and if that already exists, just run a git pull --all in that location when the script is started).
I am also unsure what the messages are supposed to tell the user:
CITATION.md checking...
LICENSE checking...
.editorconfig checking...
pyproject.toml checking...
Update metadata files version in pyproject.toml? (y/n): y

Well, what did the check reveal? No update necessary? This probably cannot be because the version number in the pyproject.toml was updated if I followed the changes correctly, but I have no clue what was going on here.

@ptrebert
Since I was hitting the API rate limit when updating local workflows directly from the github repo I need the temp folder to have a local copy of the branch/version tag of interest to which the local metadata files should be compared to, but I totally agree that the location within the repo that is getting updated was very bad.
The clone/checkout location for the metadata repository is now next to the workflow/project repository (and if that already exists, a git pull --all will run in that location when the script is started).
To make it clearer I changed the variable name for this "temp" folder to metadata_dir and the previously called "metadata_dir" which referred to the location of the local location of the metadata files of the project/workflow folder is now called workflow_dir.
I also revised all screen messages so they clearly state now what is being done and what the outcome of those actions is.


CI test publishing

@swankjesse landing to test in CI on master.

Example failure report from master
https://github.com/square/okhttp/runs/3218289171


Auto commenting feature for new PR raised

This feature aims to address the problem of delayed and inconsistent communication following the raising of PRs. By automatically commenting on PRs as soon as they are raised, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.
Could you please assign me this issue under GSSOC'24.

This issue is already solved.
Try to contribute to different issues.


VB-3291-Move-Bristol-(BSI)-sessions-to-new-timetable

Bristol (BSI) have asked for a significant change to their timetable over Christmas. There are some existing bookings from the ‘old’ deactivated session templates that need to be moved to the appropriate new session templates.

LGTM


Chore/update deps

Summary by CodeRabbit

Documentation

Updated the badge URL in the README.md to reflect the current dependencies status from npm.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (149d466) 100.00% compared to head (fc32a88) 100.00%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main        #8   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           20        20
  Branches         4         4
=========================================
  Hits            20        20

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Talk/hall connections get really slow, blocking other traffic

Not 100% sure what's happening here, but I have observed the following:

Re-connecting to my parent's urbit-meta caused ~palfun to get into one-way connectivity with it. After rebooting both ships, all unsuccessful |his suddenly went through (from star to planet).
Booting a moon, it initially didn't seem to get connectivity to the planet's hall, and wasn't receiving |his from the planet either. Rebooting and forcing talk to reconnect eventually caused some amesing and a big chunk of messages making their way onto the moon.
Had to wait a long time (during which I also rebooted and reconnected again) for smaller chunks of more recent messages to come through. After those mostly completed, the |his finally came through as well.

This seems to me as if big prizes take a ton of time to go to the recipient and be processed, which blocks other communication in the same direction until that has finished (because packets need to stay in-order).
Maybe talk shouldn't ask for the entire history on-connect? Clients will likely want to load it in at some point though. Should we somehow cut up large prizes into smaller chunks?

Subset of #582.


e2e_dgpu: Remove dgpu folder

Remove e2e/dgpu folder for GA 1.0.0 clean up task in #14.
Content of this folder will be a part of e2e/inference
Signed-off-by: vbedida79<EMAIL_ADDRESS>

It looks good to me.


stdin is not tty causes container to exit

docker version: Docker version 1.6.2, build 7c8fca2
uname -a: Linux ip-xx-x-x-xxx 3.14.44-32.39.amzn1.x86_64 #1 SMP Thu Jun 11 20:33:38 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
We are starting a container and run task using aws ecs service, the image got pulled successfully according to the task definition but when the container trying to run the task it exited because of "stdin is not tty". We manually reproduced that error by running docker run {image_name} but didn't figure out a way to fix it. Here's the output:
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension GLX
stdin: is not a tty

We are using Xvfb to run tests and here are the related dependencies in our dockerfile
# install virtual display
RUN apt-get -qy install xvfb
RUN apt-get -qy install x11-xkb-utils
RUN apt-get -qy install xserver-xorg-core
RUN apt-get -qy install xfonts-100dpi xfonts-75dpi xfonts-scalable xfonts-cyrillic

Does anyone happen to know how to fix this? Thanks a lot.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

I believe you want the -t argument for docker run.
For example:
# docker run ubuntu tty
not a tty

# docker run -t ubuntu tty
/dev/console

thanks for your response, but the problem is we create the task by clicking the run task button on the task definition page of amazon ecs, so that we can't append options to the docker run command.

This sounds like an issue with AWS ECS. I would recommend opening a ticket with them.

Closing since this is specifically an issue with how ECS is shelling out to the docker CLI.


Revert "missing pinned version" change for 5.10

There's an unfortunate interaction here with the resolver precomputation / LocalPackageContainer which leads to us rejecting versions as "not available" if they don't happen to be the currently checked out version. We need a more hollistic change to resolve this issue which is out of scope for 5.9, so we'll revert this change here.
rdar://115303494
(cherry picked from commit 87d65e3da6a128b87f105f579caa58e509962617)

@swift-ci please test

stderr: error: 'validlayouts_singlemodule_library': Invalid manifest (compiled with: ["/Users/ec2-user/jenkins/workspace/swift-package-manager-PR-macos-smoke-test/branch-main/build/buildbot_incremental/toolchain-macosx-x86_64/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc", "-vfsoverlay", "/var/folders/7n/r31lzfjx6556jgc6vg55_cg80000gn/T/TemporaryDirectory.3kz842/vfs.yaml", "-L", "/Users/ec2-user/jenkins/workspace/swift-package-manager-PR-macos-smoke-test/branch-main/build/buildbot_incremental/swiftpm-macosx-x86_64/x86_64-apple-macosx/lib/swift/pm/ManifestAPI", "-lPackageDescription", "-Xlinker", "-rpath", "-Xlinker", "/Users/ec2-user/jenkins/workspace/swift-package-manager-PR-macos-smoke-test/branch-main/build/buildbot_incremental/swiftpm-macosx-x86_64/x86_64-apple-macosx/lib/swift/pm/ManifestAPI", "-target", "x86_64-apple-macosx12.0", "-sdk", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.1.sdk", "-F", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks", "-I", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib", "-L", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib", "-swift-version", "4.2", "-I", "/Users/ec2-user/jenkins/workspace/swift-package-manager-PR-macos-smoke-test/branch-main/build/buildbot_incremental/swiftpm-macosx-x86_64/x86_64-apple-macosx/lib/swift/pm/ManifestAPI", "-sdk", "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX13.1.sdk", "-package-description-version", "4.2.0", "-module-cache-path", "/Users/ec2-user/jenkins/workspace/swift-package-manager-PR-macos-smoke-test/branch-main/build/buildbot_incremental/swiftpm-macosx-x86_64/x86_64-apple-macosx/release", "/private/var/folders/7n/r31lzfjx6556jgc6vg55_cg80000gn/T/ValidLayouts_SingleModule_Library.qHAdt5/ValidLayouts_SingleModule_Library/Package.swift", "-Xfrontend", "-disable-implicit-concurrency-module-import", "-Xfrontend", "-disable-implicit-string-processing-module-import", "-o", "/var/folders/7n/r31lzfjx6556jgc6vg55_cg80000gn/T/TemporaryDirectory.wTS7Pb/validlayouts_singlemodule_library-manifest"])
<unknown>:0: error: cannot open file '/private/var/folders/7n/r31lzfjx6556jgc6vg55_cg80000gn/T/spm-tests-testInitPackageLibrary.BWg1TC/Foo/.build/x86_64-apple-macosx/debug/Foo.build/module.modulemap' (No such file or directory)
/private/var/folders/7n/r31lzfjx6556jgc6vg55_cg80000gn/T/ValidLayouts_SingleModule_Library.qHAdt5/ValidLayouts_SingleModule_Library/Package.swift:1:8: error: failed to build module 'Foundation'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.7.1 (swiftlang-<IP_ADDRESS>.4 clang-14<IP_ADDRESS>)', while this compiler is 'Apple Swift version 5.9-dev (LLVM 4ebee5bc182ee86, Swift 5b8553cbe76b51b)'). Please select a toolchain which matches the SDK.
import Foundation
       ^

the PR is into "main", did you mean to make into "5.10"?

the PR is into "main", did you mean to make into "5.10"?

Yes, good catch.

@swift-ci please test

FAIL: Swift(windows-x86_64) :: Driver/windows-link-job.swift (2265 of 9746)
******************** TEST 'Swift(windows-x86_64) :: Driver/windows-link-job.swift' FAILED ********************
Script:
--
: 'RUN: at line 1';   rm -rf "T:\1\tools\swift\test-windows-x86_64\Driver\Output\windows-link-job.swift.tmp/DISTINCTIVE-WINDOWS-PATH/usr/bin" && mkdir -p "T:\1\tools\swift\test-windows-x86_64\Driver\Output\windows-link-job.swift.tmp/DISTINCTIVE-WINDOWS-PATH/usr/bin"
: 'RUN: at line 2';   rm -rf "T:\1\tools\swift\test-windows-x86_64\Driver\Output\windows-link-job.swift.tmp/DISTINCTIVE-WINDOWS-PATH/usr/lib" && mkdir -p "T:\1\tools\swift\test-windows-x86_64\Driver\Output\windows-link-job.swift.tmp/DISTINCTIVE-WINDOWS-PATH/usr/lib"
: 'RUN: at line 3';   ln 't:\\1\\bin\\swift-frontend.exe' T:\1\tools\swift\test-windows-x86_64\Driver\Output\windows-link-job.swift.tmp/DISTINCTIVE-WINDOWS-PATH/usr/bin/swiftc || cp 't:\\1\\bin\\swift-frontend.exe' T:\1\tools\swift\test-windows-x86_64\Driver\Output\windows-link-job.swift.tmp/DISTINCTIVE-WINDOWS-PATH/usr/bin/swiftc
: 'RUN: at line 4';   env PATH= T:\1\tools\swift\test-windows-x86_64\Driver\Output\windows-link-job.swift.tmp/DISTINCTIVE-WINDOWS-PATH/usr/bin/swiftc -target x86_64-unknown-windows-msvc -### -module-name link -emit-library C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swift\test\Driver\windows-link-job.swift 2>&1 | "C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\python.exe" C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swift\utils\PathSanitizingFileCheck --allow-unused-prefixes --sanitize BUILD_DIR=T:/1/tools/swift --sanitize SOURCE_DIR=C:/Users/swift-ci/jenkins/workspace/swiftpm-PR-windows/swift --use-filecheck t:\1\bin\filecheck.exe --enable-windows-compatibility C:\Users\swift-ci\jenkins\workspace\swiftpm-PR-windows\swift\test\Driver\windows-link-job.swift
--
Exit Code: 1

Command Output (stdout):
--
$ ":" "RUN: at line 1"
$ "rm" "-rf" "T:\1\tools\swift\test-windows-x86_64\Driver\Output\windows-link-job.swift.tmp/DISTINCTIVE-WINDOWS-PATH/usr/bin"
# command stderr:
Error: 'rm' command failed, [WinError 32] The process cannot access the file because it is being used by another process.
error: command failed with exit status: 1

@swift-ci please test windows


Add amend2 for joinable generators

Possibly simplifies #81
This is likely more specifically for joinable data but could theoretically expand API up to Tuple22 if needed. Premise is that for building joinable dataset you build a Gen of tuple and then amend2 over that tuple. This is what I have been doing on my own already and this trims down the necessary work by a bit. Still not ideal but a slight improvement.

Definitely will document, writing it up. Probably it would be writing for everything from Tuple2 to Tuple22. Alternative is applying similar logic to a Gen[List[T]] instead, but not sure it's necessary yet.


Fixed ASSET tutorial mybinder, vectorized probability_matrix_analytical

Done
Each bullet point corresponds to a single commit that is easily revertable.

fixes #329
removed annoying short-lasting (according to the tutorial compute time) tranges from _pmat_neighbors
vectorized probability_matrix_analytical

Tests
"vectorized probability_matrix_analytical" commit has been tested like so
# Compute the probability matrix obtained from imat using the Poisson
# pdfs
pmat2 = scipy.stats.poisson.cdf(imat - 1, Mu)
pmat = np.zeros(imat.shape, dtype=np.float32)

for i in range(imat.shape[0]):
    if mpi_accelerated and i % size != rank:
        continue
    for j in range(imat.shape[1]):
        pmat[i, j] = scipy.stats.poisson.cdf(imat[i, j] - 1, Mu[i, j])

if mpi_accelerated:
    for i in range(imat.shape[0]):
        pmat[i] = comm.bcast(pmat[i], root=i % size)

if symmetric:
    # Substitute 0.5 to the elements along the main diagonal
    if self.verbose:
        print("substitute 0.5 to elements along the main diagonal...")
    np.fill_diagonal(pmat2, 0.5)
    np.fill_diagonal(pmat, 0.5)

from numpy.testing import assert_array_almost_equal
assert_array_almost_equal(pmat2, pmat)

Suggestion
asset.py takes >1000 lines of code. Consider splitting the functional into blocks as stated in the ASSET documentation. __init__.py could serve for backward compatibility.
asset/
├── __init__.py
├── asset.py
    ├── the ASSET class, auxiliary protected functions, needed in ASSET
└── post_exploration.py
    ├── synchronous_events_xxx functions

Waiting for

Cristiano's improvements for _jsf_uniform_orderstat_3d that alleviate checking for the _wrong_oder

Coverage increased (+0.002%) to 89.174% when pulling 8e273ae5c4076ed4e47304bd060903cf2497f315 on INM-6:fix/asset_leftovers into 1405966d56e859d0c22e8d486ad91a0477df235f on NeuralEnsemble:master.


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
a5e68b7 -> 5558284

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.10.19 -> v1.11.3

terraform-ibm-modules/common-pipeline-assets
action
patch
v1.17.0 -> v1.17.4

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.11.3
Compare Source
Bug Fixes

bug setting the pr dir (#617) (00131bb)

v1.11.2
Compare Source
Bug Fixes

lock into vpc-go-sdk v0.41.0 (#616) (ef9cacf)

v1.11.1
Compare Source
Bug Fixes

add logging (#615) (beb86f4)

v1.11.0
Compare Source
Features

addition of configurable base repo or branch for upgrade test (4fd1e34)

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.17.4
Compare Source
Bug Fixes

remove collab check - no longer required (#523) (be1c5de)

v1.17.3
Compare Source
Bug Fixes

Debug logging (#522) (0fe31b8)

v1.17.2
Compare Source
Bug Fixes

bug with trim (60c8a95)

v1.17.1
Compare Source
Bug Fixes

add debug and trim comment (#520) (e0bb379)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

/run pipeline

Going to close this PR so renovate will create a new one that it can manage since we fixed the bug that is causing https://github.com/terraform-ibm-modules/terraform-ibm-event-streams/pull/90#issuecomment-1712349531


Feature: Update Maintainers Guide

Type of feature
🍕 Feature
Current behavior
I think we could better support maintainers with a more developed guide.
Suggested solution
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[X] I agree to follow this project's Contribution Docs

What are some parts that need improvement @BekahHW?


No implementation found for method getCookies on channel webview_cookie_manager

webview_flutter: 3.0.0
Flutter 2.8.0 • channel stable • https://github.com/flutter/flutter.git
Framework • revision cf44000065 (2 weeks ago) • 2021-12-08 14:06:50 -0800
Engine • revision 40a99c5951
Tools • Dart 2.15.0
E/flutter (10616): [ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: MissingPluginException(No implementation found for method getCookies on channel webview_cookie_manager)
E/flutter (10616): #0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:165:7)
E/flutter (10616):
E/flutter (10616): #1      MethodChannel.invokeListMethod (package:flutter/src/services/platform_channel.dart:353:35)
E/flutter (10616):
E/flutter (10616): #2      JdcookiePage.build. (package:jd_cookie/pages/jdcookie/view.dart:61:42)
E/flutter (10616):

Problems with hot refresh and hot start


fix issue #1700 - [closed]

In GitLab by @sokril on Sep 20, 2018, 06:28
Merges weioperations -> dev

In GitLab by @wknet123 on Nov 13, 2019, 11:23
closed


Unable to Install in .Net Framework 4.5

Install-Package : Could not install package 'ACB.FCMPushNotifications 1.0.1'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.5', but
the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
At line:1 char:1

Install-Package ACB.FCMPushNotifications

  + CategoryInfo          : NotSpecified: (:) [Install-Package], InvalidOperationException
  + FullyQualifiedErrorId : NuGetCmdletUnhandledException,NuGet.PowerShell.Commands.InstallPackageCommand

Hi, this library is specifically targeting an "ASP.Net Core" application running on ".Net Core" (see difference between ".Net Framework" and ".Net Core")
I have no plans to add support for ".Net Framework" at this time, but I think you should be able to adapt a large portion of the code to work with your app, as the only parts that are really specific to Core are the configuration, and taking advantage of dependency injection out of the box.

Thanks. The problem was with nuget package manager. I tried in in new project and it worked.


Flaky-test: TransactionBufferCloseTest.deleteTopicCloseTransactionBufferTest

Search before asking

[X] I searched in the issues and found nothing similar.

Example failure
https://github.com/apache/pulsar/actions/runs/5401760645/jobs/9812478081?pr=20671#step:10:913
Exception stacktrace

  Error:  Tests run: 14, Failures: 1, Errors: 0, Skipped: 13, Time elapsed: 52.953 s <<< FAILURE! - in org.apache.pulsar.broker.transaction.buffer.TransactionBufferCloseTest
  Error:  org.apache.pulsar.broker.transaction.buffer.TransactionBufferCloseTest.deleteTopicCloseTransactionBufferTest[true](3)  Time elapsed: 10.058 s  <<< FAILURE!
  org.testng.internal.thread.ThreadTimeoutException: Method org.apache.pulsar.broker.transaction.buffer.TransactionBufferCloseTest.deleteTopicCloseTransactionBufferTest() didn't finish within the time-out 10000
  	at java.base@17.0.7/jdk.internal.misc.Unsafe.park(Native Method)
  	at java.base@17.0.7/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252)
  	at java.base@17.0.7/java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1866)
  	at java.base@17.0.7/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
  	at java.base@17.0.7/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
  	at java.base@17.0.7/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1939)
  	at java.base@17.0.7/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095)
  	at app//org.apache.pulsar.client.admin.internal.BaseResource.sync(BaseResource.java:342)
  	at app//org.apache.pulsar.client.admin.internal.TopicsImpl.deletePartitionedTopic(TopicsImpl.java:457)
  	at app//org.apache.pulsar.client.admin.Topics.deletePartitionedTopic(Topics.java:802)
  	at app//org.apache.pulsar.broker.transaction.buffer.TransactionBufferCloseTest.deleteTopic(TransactionBufferCloseTest.java:81)
  	at app//org.apache.pulsar.broker.transaction.buffer.TransactionBufferCloseTest.deleteTopicCloseTransactionBufferTest(TransactionBufferCloseTest.java:72)
  	at java.base@17.0.7/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  	at java.base@17.0.7/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
  	at java.base@17.0.7/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  	at java.base@17.0.7/java.lang.reflect.Method.invoke(Method.java:568)
  	at app//org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139)
  	at app//org.testng.internal.invokers.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:47)
  	at app//org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:76)
  	at app//org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11)
  	at java.base@17.0.7/java.util.concurrent.FutureTask.run(FutureTask.java:264)
  	at java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
  	at java.base@17.0.7/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
  	at java.base@17.0.7/java.lang.Thread.run(Thread.java:833)

Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@Test(timeOut = 10_000, dataProvider = "isPartition")
    public void deleteTopicCloseTransactionBufferTest(boolean isPartition) throws Exception {
        int partitionCount = isPartition ? 30 : 1;
        List<TopicName> topicNames = createAndLoadTopics(isPartition, partitionCount);
        String namespaceName = topicNames.get(0).getNamespace();
        checkSnapshotPublisherCount(namespaceName, 1);

        for (int i = 0; i < topicNames.size(); i++) {
            deleteTopic(isPartition, topicNames.get(i));
            // When delete all topics of the namespace, the publisher count should be 0.
            int expectCount = i == topicNames.size() - 1 ? 0 : 1;
            checkSnapshotPublisherCount(namespaceName, expectCount);
        }
    }

I think we can remove the timeout of the test. Because it creates and then deletes 60 topics if isPartition=true.

This is strange, I tested on my local env, and it only costs less than 2 seconds.

It seems that this method was blocked, I'm afraid the thread was stuck.
admin.topics().deletePartitionedTopic(topicName.getPartitionedTopicName(), true);

again: https://github.com/apache/pulsar/actions/runs/5536635370/jobs/10110676512?pr=20623#step:10:1201

@gaoran10 It looks like there's a resource leak somewhere. When the test times out there are 718  threads:
https://jstack.review/?https://gist.github.com/lhotari/a4276e94f10c8f62cc0fd3c1257624f6#tda_1_dump
Lots of threads with the same name, for example:
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800337ab3f8 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080000cab0d0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800336f0e18 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008001c456320 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008001c4453c8 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f5e314f0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f5e1e848 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800167b9f60 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f5e29468 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f5e35928 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f49f6c58 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f5e1a4c8 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f5e250f8 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803fd845250 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008003371cc80 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008003374c040 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800336fcc80 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080033743fd0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008002e436230 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800336f4cb8 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803fd839070 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008001c43b4b8 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800336ffdf0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803fd834ee0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008003375cf68 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f5e22758 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080033714c18 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803fd854f08 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008002e43f5d0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008001b7ada88 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800368373a0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080033748020 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800337109b0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800093d68d8 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080033752588 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080036824490 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080036840ae0 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080033718d10 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800093c1028 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x0000080000ca5d10 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000803f5e39718 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008001c4401f8 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x000008003370c850 ]
pulsar-backlog-quota-checker-OrderedScheduler-0-0awaiting notification on [ 0x00000800336f8d80 ]
/Cc @dave2wave @Technoboy-  Here yet another resource leak in tests.

thread leaks:
❯ grep -shEr "created [0-9][0-9]+ new threads" pulsar-broker
2023-07-13T06:18:12,115 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ReplicatorAdminTlsTest created 26 new threads
2023-07-13T06:09:10,589 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.TopicOwnerTest created 40 new threads
2023-07-13T06:18:27,708 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.BrokerBkEnsemblesTests created 32 new threads
2023-07-13T05:59:04,195 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.SimpleBrokerStartTest created 13 new threads
2023-07-13T06:02:54,883 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.extensions.scheduler.UnloadSchedulerTest created 10 new threads
2023-07-13T06:27:27,595 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.BacklogQuotaManagerTest created 17 new threads
2023-07-13T06:24:54,267 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.BrokerServiceTest created 37 new threads
2023-07-13T06:31:26,617 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ReplicatorSubscriptionTest created 23 new threads
2023-07-13T06:14:34,465 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ReplicatorTlsTest created 18 new threads
2023-07-13T06:34:40,969 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.transaction.buffer.TransactionStablePositionTest created 78 new threads
2023-07-13T06:32:03,632 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.BrokerBookieIsolationTest created 51 new threads
2023-07-13T06:00:16,670 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.impl.BundleSplitterTaskTest created 13 new threads
2023-07-13T06:07:32,859 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.PeerReplicatorTest created 24 new threads
2023-07-13T06:05:18,690 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.auth.AuthorizationTest created 12 new threads
2023-07-13T06:05:50,722 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.SimpleLoadManagerImplTest created 51 new threads
2023-07-13T06:04:49,333 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.MultiBrokerLeaderElectionTest created 89 new threads
2023-07-13T06:10:48,796 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.persistent.PersistentStickyKeyDispatcherMultipleConsumersTest created 11 new threads
2023-07-13T06:30:07,831 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ReplicatorTopicPoliciesTest created 22 new threads
2023-07-13T06:31:28,204 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.intercept.MangedLedgerInterceptorImplTest created 10 new threads
2023-07-13T06:20:06,450 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ClusterMigrationTest created 743 new threads
2023-07-13T06:20:30,680 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.schema.PartitionedTopicsSchemaTest created 16 new threads
2023-07-13T06:08:03,645 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ReplicatorRemoveClusterTest created 18 new threads
2023-07-13T06:06:43,539 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ReplicatorAdminTlsWithKeyStoreTest created 25 new threads
2023-07-13T06:27:39,557 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.MessageCumulativeAckTest created 62 new threads
2023-07-13T06:29:35,866 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ServerCnxTest created 849 new threads
2023-07-13T06:05:18,567 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.ModularLoadManagerImplTest created 47 new threads
2023-07-13T06:31:20,507 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.MaxMessageSizeTest created 23 new threads
2023-07-13T06:23:33,302 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.schema.SchemaServiceTest created 18 new threads
2023-07-13T06:34:47,454 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.transaction.pendingack.PendingAckInMemoryDeleteTest created 78 new threads
2023-07-13T06:17:41,339 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.OneWayReplicatorTest created 20 new threads
2023-07-13T06:05:49,956 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.SLAMonitoringTest created 31 new threads
2023-07-13T06:34:39,547 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.transaction.AuthenticatedTransactionProducerConsumerTest created 100 new threads
2023-07-13T05:59:13,933 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.LeaderElectionServiceTest created 13 new threads
2023-07-13T06:27:18,576 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.ReplicatorTest created 61 new threads
2023-07-13T06:00:53,494 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.MultiBrokerLeaderElectionExpirationTest created 81 new threads
2023-07-13T06:02:37,720 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.loadbalance.LoadBalancerTest created 92 new threads
2023-07-13T06:10:33,889 - WARN  - [main:ThreadLeakDetectorListener@60] - Summary: Tests in class org.apache.pulsar.broker.service.persistent.PersistentSubscriptionTest created 25 new threads

@lhotari Thanks for this discovery, I'll check the dump and try to fix this problem.

UPDATE: the thread leak detection does some false alarms since broker shutdown is asynchronous in tests because of performance reasons. For example, in ServerCnxTest,  svcConfig.setBrokerShutdownTimeoutMs(5000L); makes the shutdown wait for completion, but that makes the test very slow. /cc @gaoran10

Actually, setting svcConfig.setBrokerShutdownTimeoutMs(5000L); in ServerCnxTest didn't make the thread leak go away. There must be some other problem in shutdown sequence. I'll file another bug report for it.


fix a translation problem in index.md

This pull request is to fix a translation problem in index.md

Job d2l-zh/PR-750/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-750/


Moving OD wrapper to device

Without this fix, predict was failing on GPU. With this change, now we have successful dpv2 runs --
https://ml.azure.com/experiments/id/ab455878-3e59-4595-bd75-db321c20277d/runs/2bab199f-340f-4b50-94ed-359ee7ac08ef?wsid=/subscriptions/a75ae43f-9f72-4699-ba66-d3a173cfe082/resourceGroups/ilmatdpv2rg3/providers/Microsoft.MachineLearningServices/workspaces/ilmatdpv2ws3&tid=72f988bf-86f1-41af-91ab-2d7cd011db47#

Codecov Report

Merging #110 (c337d0b) into main (5908553) will decrease coverage by 35.45%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main     #110       +/-   ##
===========================================
- Coverage   72.68%   37.23%   -35.45%
===========================================
  Files          26       26
  Lines        1574     1579        +5
===========================================
- Hits         1144      588      -556
- Misses        430      991      +561

Flag
Coverage Δ

unittests
37.23% <0.00%> (-35.45%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

python/ml_wrappers/model/image_model_wrapper.py
36.58% <0.00%> (-55.87%)
:arrow_down:

... and 16 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix missing #!/usr/bin/env php and chmod +x for ./serve

Before
$ ./serve
-bash: ./serve: Permission denied
$ sudo ./serve
sudo: ./serve: command not found

After added
#!/usr/bin/env php

in the first line, and run chmod:
$ chmod +x ./serve

Got succeed
$ ./serve
CodeIgniter development server started on http://localhost:8080

While I'm not opposed to including a !# line in these - it would have to serve the most people. And the most common locations are either /usr/bin/php or /usr/local/bin/php, not the /usr/bin/env that you've included here. So, it still wouldn't help your case.
Run it as php serve and you're good to go.


Improve the log message - issue #1078

Signed-off-by: David Geng<EMAIL_ADDRESS>

@genggjh why does this PR include an update to the .gitignore file? Did you include that by accident?

@srderson because the membersrvc binary file which is used for my testing will be included into my path if i do not ignore it in the .gitignore.

If you want I can move the changes into a separate commit.

ah, ok. Makes sense. Thanks.

done, @srderson please help to review it again.

sorry, was not clear. You were correct. The .gitignore file should membersrvc/membersrvc. Can you please add it back to this PR?

never mind, see you created a second PR. That works also.

Yes, I think so 👍

LGTM. Thanks!


UNICEF 171: Remove no-script warning

@saeedmb8 please review
Ticket requires the removal of this warning. Since we do not have a lot of JavaScript support.


CodeWhisper: Implement allow revise-prs to revert a commit

CodeWhisper autogenerated PR. Reply to this PR to have CodeWhisper make revisions.
fix: #11
if the user says a commit was no good, revert it.

CodeWhisper commit information
Summary
Implemented the ability to revert commits in the revise-prs workflow. Added a new function to check if a commit needs to be reverted, and updated the revisePullRequest function to handle commit reversions when necessary.
Files we looked at

/Users/gregoryguterman/code/CodeWhisper/src/ai/pull-request-workflow.ts
/Users/gregoryguterman/code/CodeWhisper/src/ai/undo-task-changes.ts
/Users/gregoryguterman/code/CodeWhisper/src/utils/git-tools.ts
/Users/gregoryguterman/code/CodeWhisper/tests/unit/git-tools.test.ts

Potential Issues

The implementation assumes that the last comment on a PR accurately represents the user's intention to revert a commit.
There's no limit on how many commits can be reverted, which could potentially lead to unexpected behavior if multiple reverts are requested in succession.
The commit reversion is done automatically without additional user confirmation, which might not be ideal in all scenarios.

Next steps
You can reply to CodeWhisper with instructions such as:

"Revert the last commit"
"Fix the typo in line 10"
"Add a new function to the file"

hi

CodeWhisper commit information
Summary
Added functionality to revert the last commit in the revise-prs workflow if the user indicates it was not good. This includes a new function to check if a revert is needed, updates to the revisePullRequest function to handle the revert process, and necessary changes to the GitHubAPI class to support these operations.
Files we looked at

/Users/gregoryguterman/code/CodeWhisper/src/ai/pull-request-workflow.ts
/Users/gregoryguterman/code/CodeWhisper/src/ai/undo-task-changes.ts
/Users/gregoryguterman/code/CodeWhisper/src/github/github-api.ts
/Users/gregoryguterman/code/CodeWhisper/src/utils/git-tools.ts
/Users/gregoryguterman/code/CodeWhisper/tests/unit/git-tools.test.ts

Potential Issues

The implementation assumes that the last comment on a PR accurately represents the user's intention to revert a commit.
There's no limit on how many commits can be reverted, which could potentially lead to unexpected behavior if multiple reverts are requested in succession.
The commit reversion is done automatically without additional user confirmation, which might not be ideal in all scenarios.
The current implementation doesn't handle potential conflicts that might arise during the revert process.

Next steps
You can reply to CodeWhisper with instructions such as:

"Revert the last commit"
"Fix the typo in line 10"
"Add a new function to the file"

revert the last commit

CodeWhisper commit information
Summary
Reverted the last commit as requested.
Files we looked at
Potential Issues
undefined
Next steps
You can reply to CodeWhisper with instructions such as:

"Revert the last commit"
"Fix the typo in line 10"
"Add a new function to the file"

never mind, in   await git.revert(['HEAD']); the argument should just be a string, not a list

replace the word list check for a call to an ai to determine if a commit should be reverted

CodeWhisper commit information
Summary
Added functionality to revert the last commit in the revise-prs workflow if the user indicates it was not good. This includes updating the needsRevert function to use AI for determining if a revert is needed, modifying the revisePullRequest function to handle the revert process, and adding a new method to the GitHubAPI class to post custom comments.
Files we looked at

/Users/gregoryguterman/code/CodeWhisper/src/ai/pull-request-workflow.ts
/Users/gregoryguterman/code/CodeWhisper/src/ai/undo-task-changes.ts
/Users/gregoryguterman/code/CodeWhisper/src/github/github-api.ts
/Users/gregoryguterman/code/CodeWhisper/src/utils/git-tools.ts
/Users/gregoryguterman/code/CodeWhisper/tests/unit/git-tools.test.ts

Potential Issues

The AI-based determination of whether to revert might not always accurately interpret user intent.
There's no limit on how many commits can be reverted, which could potentially lead to unexpected behavior if multiple reverts are requested in succession.
The commit reversion is done automatically without additional user confirmation, which might not be ideal in all scenarios.
The current implementation doesn't handle potential conflicts that might arise during the revert process.

Next steps
You can reply to CodeWhisper with instructions such as:

"Revert the last commit"
"Fix the typo in line 10"
"Add a new function to the file"

good ai. doesn't do anything else.

 This includes adding a function to check if a revert is needed, modifying the revisePullRequest function to handle the revert process, and updating the GitHubAPI class to support pushing changes after a revert.
Files we looked at

/Users/gregoryguterman/code/CodeWhisper/src/github/github-api.ts
/Users/gregoryguterman/code/CodeWhisper/src/ai/apply-changes.ts
/Users/gregoryguterman/code/CodeWhisper/src/ai/pull-request-workflow.ts
/Users/gregoryguterman/code/CodeWhisper/src/ai/task-workflow.ts
/Users/gregoryguterman/code/CodeWhisper/src/ai/undo-task-changes.ts
/Users/gregoryguterman/code/CodeWhisper/src/utils/git-tools.ts
/Users/gregoryguterman/code/CodeWhisper/tests/unit/apply-changes.test.ts
/Users/gregoryguterman/code/CodeWhisper/tests/unit/git-tools.test.ts
/Users/gregoryguterman/code/CodeWhisper/tests/unit/github-api.test.ts
/Users/gregoryguterman/code/CodeWhisper/tests/unit/task-workflow.test.ts

Potential Issues

The AI's interpretation of user comments to determine if a revert is needed may not always be accurate.
If there are conflicts during the revert process, manual intervention may be required.
The revert process assumes that the last commit is always the one to be reverted, which may not always be the case in complex scenarios.

Next steps
You can reply to CodeWhisper with instructions such as:

"Revert the last commit"
"Fix the typo in line 10"
"Add a new function to the file"


timeToDismissNotification no longer avalible

No longer able to use present notification with time for display in version 1.9.1

Can you please fix this.

It is not a bug. Currently this is an static property of BSForegroundNotification:
usage:
BSForegroundNotification.timeToDismissNotification = 5
setup it once in your AppDelegate.

A great. Thank you.


DriverUpdate mode in Invoke-CMApplyDriverPackage.ps1 not working because of bug in Get-OSBuild function.

Script Invoke-CMApplyDriverPackage.ps1 version 4.1.1.
Bug: When using the script in 'DriverUpdate' mode the script will crash in the function Get-OSBuild and bail out.
Cause: Line number 965 contains "$OSVersion = 20H2" which is invalid. The value is not a valid integer but a string whereas all other values passed to $OSVersion in the Switch block are integers.
Solution:
All values passed to $OSVersion should be strings enclosed in quotes.
At the least line 965 should say "$OSVersion = '20H2'"

I can confirm that I had to do this as well. I should have checked on here first, but that was the fix in my case as well!

Thanks for spotting this mistake, it will be corrected in 4.1.2 that'll be released in the next couple of days.


User is stuck on initial loading screen

A few users have experienced an issue of having Pearl running normally and suddenly one day when trying to open the app, it was stuck on the initial loading screen. View logs from 2 users attached:
cli (2).log
cli (3).log
cli 2.log
part cli.log

cli (2).log is file write permission issue when writing pearl PID (process ID to kill) to operate.kill
cli (3).log looks like invalid json file causing cli to break
`cli 2.log doesn't have logs to determine error, but may be that next server did not start
part cli.log formatting is messed up, but seems like windows PID did not exist when attempting to kill and broke cli

cli (3).log


feat: multi-thread reads and batched writes

Write batching and read multi-threading improves throughput by 5-18x, depending on workload type.
Benchmark with:
denokv --sqlite-path denokv-test.sqlite serve --access-token public-token --num-workers 8 --atomic-write-batch-timeout-ms 50
deno run -A --unstable ./scripts/benchmark.ts --path http://<IP_ADDRESS>:4512 --read-concurrency 128 --write-concurrency 64 --size 10000 --consistency-check-interval 10

Before:
Inserted 10000 entries in 18661ms
NewRds:     1831/s, NewWrs:      472/s, NewCfs:        7/s,

After:
Inserted 10000 entries in 1317ms
NewRds:    34573/s, NewWrs:     2285/s, NewCfs:       38/s

Great improvements, nice work.


Update Get-PrintJob.md

made changes to the ID description as you cannot use wild card characters on Get-PrintJob -Id
Fixes https://github.com/MicrosoftDocs/windows-powershell-docs/issues/3583

@JohanFreelancer9  Please copy review

close > reopen


Add test for user order creation

This affect user recreation changing UIDs

Nice it fails, now the patch to fix it should make it pass

Reported by https://github.com/kairos-io/kairos/issues/1920 should also affect any other users using yip for user creation


Support debug configs (launch.json) for running tests.

(for #332)

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[x] Has a news entry file (remember to thank yourself!)
[x] Has sufficient logging.
[x] Has telemetry for enhancements.
[x] Unit tests & system/integration tests are added/updated
[x] Test plan is updated as appropriate
~[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed)~

FTR, support for launching the tests through the debugger UI (select the config in the pull-down, click on the green arrow) is getting sorted out in #4376.


Fix typo D365 EXTENSION MGMT -> D365 EXTENSION MGT

Source: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-get-started#controlling-user-access-to-developing-and-publishing-extensions

Thank you for your contribution! This is indeed a typo, and we'll get it updated on the backend for an upcoming doc refresh. We're having technical problems these days, so I cannot merge your pull request, unfortunately. Once our technical problems are fixed, we'll open for contributions again.
Thanks!


ehl_crb: portability.posix.common.posix_realtime failed.

Bug Description
The posix_realtime test in the /tests/posix/common test suite is failing due to assert:
Assertion failed at WEST_TOPDIR/zephyr/tests/posix/common/src/clock.c:75: test_posix_realtime: (rts.tv_nsec not equal to mts.tv_nsec)

This is observed in the other configurations of testcase.yml

portability.posix.common
portability.posix.common.newlib
portability.posix.common.tls
portability.posix.common.tls.newlib

To Reproduce
Steps to reproduce the behavior:

Example for a single configuration: west build -b ehl_crb -p auto tests/posix/common/
--DCONFIG_NEWLIB_LIBC=n
copy binary to USB/PXE boot media
boot
See error

Logs and console output
Booting Zephyr OS build zephyr-v2.5.0-1430-g911ba334a06a
...
START - test_posix_recursive_mutex
recrusive mutex lock is taken
PASS - test_posix_recursive_mutex in 0.4 seconds
START - test_posix_mqueue
PASS - test_posix_mqueue in 0.11 seconds
START - test_posix_realtime
POSIX clock set APIs
Assertion failed at WEST_TOPDIR/zephyr/tests/posix/common/src/clock.c:75: test_posix_realtime: (rts.tv_nsec not equal to mts.tv_nsec)
Nanoseconds not equal
FAIL - test_posix_realtime in 0.19 seconds
START - test_posix_timer
POSIX timer test
Timer fires every 0 secs and  100000000 nsecs
Time remaining to fire 0 secs and  899000000 nsecs
Handler Signal value :20 for 1 times
Handler Signal value :20 for 2 times
Handler Signal value :20 for 3 times
Handler Signal value :20 for 4 times
Handler Signal value :20 for 5 times
Handler Signal value :20 for 6 times
Handler Signal value :20 for 7 times
Handler Signal value :20 for 8 times
Handler Signal value :20 for 9 times
Handler Signal value :20 for 10 times
Handler Signal value :20 for 11 times
Handler Signal value :20 for 12 times
PASS - test_posix_timer in 2.112 seconds
Environment (please complete the following information):

OS: Fedora33
Toolchain: zephyr-sdk-0.12.3
Commit ID: 911ba334a06a

I can reproduce this, looking into root cause.
Also, the bug report describes uses west to reproduce, but wanted to check with @chen-png and @yerabolu if this is observed on the other configurations. When I run this with twister for tests/posix/common/, all (4) configurations fail on this test at this 911ba33. If confirmed, we'll update the bug description.

For consideration in debug, Spoorthy and I confirmed this is observed in the other configurations of testcase.yml

portability.posix.common
portability.posix.common.newlib
portability.posix.common.tls
portability.posix.common.tls.newlib

I'm curious when was the last time this was known to be passing? I can reproduce the issue back a couple weeks already 2134f9b7:
driver: clock: npcx: remove useless operands. I'll keep going and update here.

Got some feedback offline and bisecting may not yield success in this case. Suggested to move forward with debug without bisect point.

Printing out the values that fail the zassert_equal( ), we see there is an off by 1 in the index 2 from the left:
DEBUG   - DEVICE: START - test_posix_realtime
DEBUG   - DEVICE: POSIX clock set APIs
DEBUG   - DEVICE: DEBUG - jen - rts.tv_nsec 21800000 mts.tv_nsec 21700000
DEBUG   - DEVICE:
DEBUG   - DEVICE: Assertion failed at WEST_TOPDIR/zephyr/tests/posix/common/src/clock.c:76: test_posix_realtime: (rts.tv_nsec not equal to mts.tv_nsec)
DEBUG   - DEVICE: Nanoseconds not equal
DEBUG   - DEVICE: FAIL - test_posix_realtime in 0.24 seconds

Just saw a recently resolved issue that looks very similar to this issue, https://github.com/zephyrproject-rtos/zephyr/issues/25453. The solution was merged in patch #28516.
If I revert that change by moving the printk( ) after the k_usleep( ), then this issue with tests/posix/common on ehl_crb. Reverting that patch may not be the best solution here, so seeking other options.
@andyross @jhedberg  Is there a timing configuration we need to adjust for ehl_crb?

This is not observed on acrn_ehl_crb at this point in the code base. A different issue is seen but is easily resolved using the CONFIG_APIC_TIMER_IRQ=48, recently discovered while working on https://github.com/zephyrproject-rtos/zephyr/issues/33593 (merged).
Adding the same APIC timer irq for this native EHL configuration did not resolve the assert observed here.

Adding the same APIC timer irq for this native EHL configuration did not resolve the assert observed here.

ehl_crb uses HPET_TIMER. APIC_TIMER is not set on ehl_crb, that is one of the differences between acrn_ehl_crb and ehl_crb.

Hi @andyross ! Did you get a chance to look at this test case failing, fixed by moving the printk?

Just saw a recently resolved issue that looks very similar to this issue, #25453. The solution was merged in patch #28516.
If I revert that change by moving the printk( ) after the k_usleep( ), then this issue with tests/posix/common on ehl_crb. Reverting that patch may not be the best solution here, so seeking other options.

ping @andyross Can you please offer feedback or recommendation?

Would be interesting to try this with CONFIG_APIC_TSC_DEADLINE_TIMER=y to see if this is specific to the HPET driver or if it's something general.

With that, I get build error (ld) for HPET definitions. There must be a kconfig I need to adjust as well?

Does setting SMP=n or MP_NUM_CPUS=1 also address the problem?

Neither resolved the issue. Thanks for the suggestions!

This comment in the test is confusing to me. Why does the test_posix_realtime() tell us to remove the code if we are using posix? and this k_usleep(1) is a known workaround, so its suggested we follow the previous comment of removing the code?
void test_posix_realtime(void)
{
	/* Make sure the realtime and monotonic clocks start out the
	 * same.  This is not true on posix and where there is a
	 * realtime clock, so don't keep this code.
	 */

	int ret;
	struct timespec rts, mts;
	struct timeval tv;

	printk("POSIX clock set APIs\n");

	/* Minimal sleep to align us to the next tick interval. This
	 * helps with a case that 2 consecutive calls to clock_gettime()
	 * below return different values. Note that it's still a workaround,
	 * which may break, in which case follow the suggestion in the
	 * comment above.
	 */
	k_usleep(1);

It is not ideal - I know - but noticed this passes with a longer kusleep() (which is a workaround as-is). I extended the sleep by the difference between rts.tv_nsec and mts.tv_nsec  is 100000 (100 microseconds):
k_usleep(101);

Is it worth a PR for that? I don't feel like it will be acceptable.

FWIW: the k_usleep(1) is a tick alignment, not a workaround.  The idea is that timer behavior is only deterministic if you start the test at the beginning of an OS tick.  Otherwise there are inevitable timer aliasing bugs (think of them as "race conditions against the passage of real time" -- you can't take a lock to stop the universe).  So you have to ask the kernel "please sleep until the very next tick expires".  And the simplest way to do that is to request a sleep for the smallest unit of time expressible[1].
Playing with timeouts to make this pass makes me nervous, and implies there's something else going on.
[1] Actually there's a nanosecond API now, but nothing uses a MHz+ tick rate so this is shorter and simpler.

It looks like there is an issue with clock_gettime(CLOCK_MONOTONIC, &mts);? Perhaps only for this board?
The realtime clock is further tested later in the test sequence, including comparison of gettime API with the gettimeofday API which works as expected [1] with clock_gettime(CLOCK_REALTIME, &rts); with gettimeofday(&tv, NULL);.
As one would expect, at the breakpoint for this bug, when I use the gettimeofday API instead of check against mts, this passes (really just reconfirming comparison described above):
+++ b/tests/posix/common/src/clock.c
@@ -71,8 +71,10 @@ void test_posix_realtime(void)
        ret = clock_gettime(CLOCK_REALTIME, &rts);
        zassert_equal(ret, 0, "Fail to get realtime clock");

+       ret = gettimeofday(&tv, NULL);
+
        zassert_equal(rts.tv_sec, mts.tv_sec, "Seconds not equal");
-       zassert_equal(rts.tv_nsec, mts.tv_nsec, "Nanoseconds not equal");
+       zassert_equal(rts.tv_nsec,  tv.tv_usec * NSEC_PER_USEC, "Nanoseconds not equal");

[1] (see https://github.com/zephyrproject-rtos/zephyr/blob/1b129c50c2fdb4d7e8a270356dd5fba623deb1cc/tests/posix/common/src/clock.c#L142)

Oh, and I should note:
If there's desire to resolve this test failure in upstream Zephyr for the purposes of tracking or whatever, some workaround in order of my personal preference:

Use the APIC_TSC_DEADLINE_TIMER, which is not susceptible to this bug
Turn off TICKLESS_KERNEL and use a 100 Hz tick rate, which avoids the slow paths in the HPET hardware
Turn the tick rate way down, maybe to 2000 Hz or so, which is more fiddly but would probably work too

Hi @andyross - Thanks for noting workarounds. In our sync we considered just excluding ehl_crb for this test case, is that not feasible? Perhaps we cannot exclude for only test_posix_realtime().  This case fails for all configurations in the testcase.yml, how can we exclude the platform for just one test case inside the test suite?
Let's reopen since this will keep showing up. ehl_crb is not excluded and we do not have a workaround implemented so keep this open until resolved, please.

Could  you please enable TCC Mode in BIOS and verify again ? For enable TCC mode, please go to BIOS "Intel Advance menu" and then go to "Intel(R) Time Coordinated Computing" and then enable "TCC Mode" . This will optimize SOC fabric, memory, etc. for maximum performance for time sensitive application which have stringent real time requirment. Please note that this can impact platform power


Vitest browser mode tests always fail when using mixed-typed workspaces

Describe the bug
I have a monorepo and I am taking advantage of Vitest workspaces. One workspace uses browser mode and the other workspace does NOT use browser mode.
When I run tests from the project root, the normal tests run fine, but browser tests always fail. The browser test can be extremely simple like expect(true).toBeTruthy() and it still fails. However, if I run the tests from the individual workspaces instead of the project root, then the tests always execute and succeed.
This seems to be a regression of the change made from this issue: https://github.com/vitest-dev/vitest/issues/3363
Since then, I have upgraded to Vitest v0.32.0 and switched to using v8 as a coverage provider. Even If I switch back to c8, the bug still occurs. I should also note that running tests and collecting coverage or not collecting coverage makes no difference in the outcome.
Reproduction
https://stackblitz.com/edit/vitest-browser-mode-bug-2?file=package.json
System Info
- pnpm: v8.4.0
- vitest: ^0.32.0
- playwright: ^1.35.0
- pnpm workspaces
- vitest workspaces

  System:
    OS: macOS 11.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 2.85 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.14.2 - ~/.nvm/versions/node/v18.14.2/bin/node
    npm: 9.5.0 - ~/.nvm/versions/node/v18.14.2/bin/npm
  Browsers:
    Chrome: 114.0.5735.106
    Firefox: 111.0
    Safari: 14.1.2
  npmPackages:
    @vitest/browser: ^0.32.0 => 0.32.0
    @vitest/coverage-v8: ^0.32.0 => 0.32.0
    @vitest/utils: ^0.32.0 => 0.32.0
    vitest: ^0.32.0 => 0.32.0

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

@sheremet-va I hope you don't mind me tagging you in this issue. I assume you might be able to provide more insight as this seems related to https://github.com/vitest-dev/vitest/issues/3363.

@sheremet-va Is there anything I can do for this ticket?


Shape of points in a t3 scheme

quadpy.__version__   '0.16.6'
It's probably a silly question, but I'm having trouble understanding the shape of quadrature points for t3.
What does scheme.points return for a t3?
I would expect something with shape (3, 81) for the example below, but I'm apparently missing something.
For c1 and s2 the shape of points matches my expectation.
import quadpy

scheme = quadpy.t3.get_good_scheme(10)
print(scheme.points.shape)
# Out: (4, 81)

print(scheme.weights.shape)
# Out: (81,)

scheme = quadpy.c1.gauss_patterson(5)
print(scheme.points.shape)
#Out: (63,)

scheme = quadpy.s2.get_good_scheme(6)
print(scheme.points.shape)
#Out: (2, 12)

What does scheme.points return for a t3?

All simplex schemes return barycentric coordinates.


unable to sign in after deploying <gcloud app deploy app.yaml --project=>

Hello, I successfully deployed the app using google app engine and browse to https://.appspot.com . But i was unable to sign in on the web browser to upload the prepared dataset.
Error message : unexpected error occurred. please try again.
I appreciate any hints on where to check to fix the error.
Thanks,,

Do you see any error messages in the JavaScript console or in the AppEngine dashboard?


Make sure extract layout does not publish empty json

Changelog Description
This PR is to make sure extract layout does not publish empty json
Additional info
Please try testing when groupLoadAssets option enabled
Testing notes:

Create Layout
Extract Layout

the layout does not work because of other issue which is resolved by #104


wrong SAS token example

[Enter feedback here]
the blob SAS token should be updated - as the example is not working. it should be updated according to this URL -
https://docs.microsoft.com/en-us/azure/open-datasets/dataset-seattle-safety?tabs=pyspark
Azure storage access info
blob_account_name = "azureopendatastorage"
blob_container_name = "citydatacontainer"
blob_relative_path = "Safety/Release/city=Seattle"
blob_sas_token = r""

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 355fba0e-958e-f572-18c2-892c91d20b13
Version Independent ID: 7fe76247-c969-2068-2c3c-bf327fbbe39e
Content: Quickstart - Run a Spark job on Azure Databricks Workspace using Azure portal
Content Source: databricks/scenarios/quickstart-create-databricks-workspace-portal.md
Service: azure-databricks
GitHub Login: @mamccrea
Microsoft Alias: mamccrea

@yaronpri Thank you for sharing your valuable feedback. We are actively validating it. We will share updates soon.

@mamccrea / @leifbro Could you please validate feedback and update document as appropriate. Thank you.

Adding content owner @PeterCLu

Thanks for providing feedback that helps improve our documentation. This issue has been resolved and the outdated content has been removed. We are closing the issue.
#please-close

#please-close


fix: tap and andThen fallthrough function

fixes for example:
declare const foo: (x: number) => Effect.Effect<void>;
Effect.succeed(true).pipe(Effect.tap(foo)); // no error
Effect.succeed(true).pipe(Effect.tap(x => foo(x))); // error

Mmm what about Effects that are functions? Like the proxy ones from the new tag

Mmm what about Effects that are functions? Like the proxy ones from the new tag

What about them? It they match the supported function signature, then they’re golden. Otherwise they are I believe rightfully rejected.

I think if an arg is both a function and an effect we have to force () => because the impl will take a choice, either there is an isFunction or isEffect. Quite a conondrum...

I think if an arg is both a function and an effect we have to force () => because the impl will take a choice, either there is an isFunction or isEffect. Quite a conondrum...

I see, seems like a related topic, how is it affected by this change?

It's not affected but related, with the intro of effect.tag we can't
basically distinguish functions from effects, it is an issue for tacit
usage
On Fri, 8 Mar 2024, 18:25 Patrick Roza, @.***> wrote:

I think if an arg is both a function and an effect we have to force () =>
because the impl will take a choice, either there is an isFunction or
isEffect. Quite a conondrum...
I see, seems like a related topic, how is it affected by this change?
—
Reply to this email directly, view it on GitHub
https://github.com/Effect-TS/effect/pull/2264#issuecomment-1986107990,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFZAKCVBJRRXCBXUDLQTOKLYXHYADAVCNFSM6AAAAABEM66QGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWGEYDOOJZGA
.
You are receiving this because your review was requested.Message ID:
@.***>

It's not affected but related, with the intro of effect.tag we can't basically distinguish functions from effects, it is an issue for tacit usage

alright, would at least like to get the bug fix merged so that users stop getting bit by it.
In the meantime we can look into it.
From my gut feeling though; isn’t the proxy hiding the internals on access? On phone. Would need some test cases I guess

I think there are a few other places where we assume an Effect isn't a function, will need to hunt them down.

It's not affected but related, with the intro of effect.tag we can't basically distinguish functions from effects, it is an issue for tacit usage

I see now yes, that's certainly 'fun' :D

It's not affected but related, with the intro of effect.tag we can't basically distinguish functions from effects, it is an issue for tacit usage

How about https://github.com/Effect-TS/effect/pull/2266/files#diff-1eaca66f74be66210f25595750619630e4d14443b5ddaa1f2f8a265256432778R5292


Implement conversion from CPUParticles to GPUParticles (3D/2D)

This PR adds a conversion option from CPUParticles2D/CPUParticles3D -> GPUParticles2D/3D. Closes https://github.com/godotengine/godot-proposals/issues/2997.

Calinou was faster than me, LTGM! Thank you a lot!!

Thanks!


Avoid non-existent index error in empty description arrays.

First of all you ROCK for (making and) publishing this. I'm not sure where all keel_petfinder_api_get_pet_attribute is being used, but this at least allows it to pull in from our Shelter ID which has a bunch of empty descriptions.

Hi @MikeiLL - Good call on both of these! Thanks for the updates. Accepted, as soon as I get a chance to make updates to the version number.

Moved to new PR with a few updates: https://github.com/cferdinandi/harbor-wp-theme/pull/56


Release Google.Cloud.PubSub.V1 version 3.5.1

Changes in this release:
Bug fixes

Dispose channel on PublisherClient/SubscriberClient shutdown. Fixes #10304 (commit d38ab04)

Created release for Google.Cloud.PubSub.V1-3.5.1


Sync with upstream Markdown Extended syntax.

Adds support for new inline languages, some minor fixes and indentation
changes. New languages:

Jade
C-sharp
LiveScript
Lua
Swift
PHP
R
Rust
Scala
Postgres

@danielgtaylor is this addressing the issue with line code block (some code) you have mentioned or not ?

@danielgtaylor also note that we usually name branches like <your (nick) name>/<feature> eg. daniel/feature-sync

Thanks, I'll name my branch that way in the future. This does not address the inline code issue, just syncs with upstream so we keep a smaller diff between Markdown Extended and API Blueprint's syntax highlighting.


Logical Operators in story file?

Hey,
is it possible to write stories with operators like NOT. I want to write a story where action is executed if not a specific intent is given without writing for every intent except the wanted one the stories. I mean:

* NOT Intent_Wanted
    - utter_fallback

At this moment exclusion operator is not supported, as it is not clear how to train a model in this case

Yeah so you would have to handle it with adding an OR statement for all other intents

OR and AND will work like:
* Intent_Wanted OR * other_intent

It would be nice to have context based fallback such that based on prevoius intent or action like asking_for_location. If user gives then not required or requested intent than do fallback.
See:
https://forum.rasa.com/t/infer-intent-from-extracted-entity-context/1370

what do you mean AND? that doesn't exist. But or should look like this:
* Intent_Wanted OR other_intent

As for this context based fallback, you can write a story for that, if the user gives you any intent other than something you wanted, send a different reply. I think the post you linked is addressing something else

You can need this to do out of context fallbacks without writing exceptions for every intent. This is whta the link is about. But it would be nice to handle this in more rigourus way like here: https://github.com/mrbot-ai/rasa-addons#swap-intents

Some intents are hard to catch. For example when the user is asked to fill arbitrary data such as a date or a proper noun. The following rule swaps any intent caught after utter_when_do_you_want_a_wake_up_call with enter_data unless...

intent_substitutions:
  - after: utter_when_do_you_want_a_wake_up_call
    intent: enter_data
    unless: frustration|cancel|speak_to_human

Feel free to use this rasa-addons package, currently we're not going to add something like this to Rasa core. But when it comes to slot filling we'll be merging a new version of forms where the intent isn't payed attention to as much


Add v3 log format

add a writer to zerolog to create log messages in v3 format.
I implemented it as a different package, so it will be easier to move it out

Coverage increased (+1.1%) to 70.553% when pulling 64f02b14396e06bac621e9f7dac74fa2fb40a4e7 on add-v3-log-format into da35654a98b88eeeb65fe59ce858ccca49d25b43 on master.


Fuji fresh order page

@digijim please make this part of the fujifresh order page

match this part of the fujifresh info page

thoughts @afaiman and @digijim on using either the fujifresh logo and/or some photos of film on this page as well?

should we add link to "learn more about fujifresh here" and link to fujifresh info page?

I think the logo would be a good thing to add here. That and an image of film might be ok, too, but might be overkill. Defintiely should add a link to the info page.

OK GO-GO LOGO!

fuji logo
then "Order your favorite Fuji400H.
Available in 120 + 135 Pro Packs."
remove "#FUJIfresh 400H" from pro pack description

What do you think of this idea, @thisisveryimportant ?


issues-2: integrate hanzo menu to lux chat & fix origin menu issues

I updated several functions in luxfi/chat.

Integrate hanzo menu to chat one.
Change lux icon
Update menu label and link label colors.
Address chat input bar zindex issue

PTAL @zeekay


Document --downstream-http-proxy-enabled

The RPC proxy will proxy any unmatched RPC requests to a downstream execution client. By having the proxy it means that all RPC requests can go through web3signer with web3signer providing additional RPCs for eth_sendtransaction and eth_accounts (not part of this PR).
It is disabled by default behind a feature flag --downstream-http-proxy-enabled.
See: https://github.com/ConsenSys/web3signer/pull/775

This flag has been removed.


Restructure package sets

Pull a common localPackages out of the overlay and packages outputs, and
rebuild them.
This also adds the standard overlays output in addition to the deprecated
overlay output. It also adds a vim overlay for the Vim plugin and removes
darwin-security-hack from the overlays.

This is based on #85.
And here’s the CI results: https://garnix.io/commit/8f0211162ff9e06381d2da63c72590966421766a


Joindin 143 edit links

Requires the API changes to work

Can one of the admins verify this patch?

ok to test


Template calls

Generalization so that every template can be called from any template.
Tags and Layouts work like before, they were just special cases of the now more generic behavior.
This is still work in progress. Also, it needs to be seen if the IntelliJ plugin can be adjusted to support this.

Codecov Report

Merging #126 (48706fa) into master (78cc3d5) will decrease coverage by 0.23%.
The diff coverage is 79.36%.

@@             Coverage Diff              @@
##             master     #126      +/-   ##
============================================
- Coverage     92.41%   92.17%   -0.24%
- Complexity     1122     1123       +1
============================================
  Files            59       59
  Lines          2833     2823      -10
  Branches        449      461      +12
============================================
- Hits           2618     2602      -16
- Misses          113      117       +4
- Partials        102      104       +2

Impacted Files
Coverage Δ

.../html/policy/PreventOutputInTagsAndAttributes.java
100.00% <ø> (ø)

jte/src/main/java/gg/jte/compiler/LineInfo.java
94.44% <ø> (ø)

...te/compiler/TemplateParametersCompleteVisitor.java
96.55% <ø> (ø)

...ompiler/TemplateSingleControlStructureVisitor.java
97.50% <ø> (ø)

...te/src/main/java/gg/jte/compiler/TemplateType.java
100.00% <ø> (ø)

...runtime/src/main/java/gg/jte/runtime/Template.java
89.13% <50.00%> (-0.67%)
:arrow_down:

.../src/main/java/gg/jte/compiler/TemplateParser.java
89.77% <75.55%> (-0.72%)
:arrow_down:

...va/gg/jte/compiler/kotlin/KotlinCodeGenerator.java
97.33% <100.00%> (ø)

...e-runtime/src/main/java/gg/jte/TemplateEngine.java
95.79% <100.00%> (+0.75%)
:arrow_up:

...e/src/main/java/gg/jte/runtime/TemplateLoader.java
77.27% <100.00%> (-2.73%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 78cc3d5...48706fa. Read the comment docs.


fix: add check if runtime is null and change error message; add tests

#87

Replace NullPointerException with custom RuntimeException
Add tests for error message which will be generated
Add necessary dependencies for dynamic tests running

Missed this PR when I added a fix yesterday per #98 . Anyways, my fix went in a different direction - I am allowing unlinked CayenneTester to exist, just printing a bunch of warning.


[DO NOT MERGE] Add tracking to campaign page

Requires https://github.com/alphagov/collections/pull/952 to be merged in first

Replacing with https://github.com/alphagov/collections/pull/962 because this was proving to be difficult to rebase


v4 Modal backdrop is not removed on close

 is added when modal is on show, but it only turns to

 on hide while it's supposed to be removed.
This creates an issue where after closing a modal, nothing on the page can be clicked.

The demo has latest code, no issue there, perhaps you're using an incorrect markup?

@dkbnguyen well?

Sorry for the late reply. It was my bad, I commented out the bootstrap transitions scss module. It should be included in css file in order to run modal script.
Thank you for getting back quickly.


Parse Object/Array types

Was wrapped in a string before.

Please add reference to the appropriate Jira work item.  Also, make sure there is a separate, working test flow for Object columns, and another one for Array columns. How does the system behave if either the object or array are malformed? Will Snowflake allow us to create such a malformed entity?


Accumulated list of improvements to the guide

https://github.com/Plailect/Guide/wiki/Get-Started and https://github.com/Plailect/Guide/wiki/Part-1-(Homebrew) both contain a list of things to do separated by firmware. It's cognitively hard to find the appropriate section for a particular firmware though, so it should be grouped as a table, or at least as a proper list (via *). E.g.

9.0 - 9.8: blabla
9.9 - 10.5: blabla
....

Booting my EmuNAND took really long to get any (useful) visual feedback. It would be good to note somewhere that it may take up to two minutes, especially when the emunand has been formatted from the system settings (or via TinyFormat).
23:41 < neobrain> Plailect: the D9WIP version linked at https://github.com/Plailect/Guide/wiki/9.2.0-Update-(rxTools-2.5.2) doesn't work for me, https://github.com/d0k3/Decrypt9WIP/releases/tag/20160607 does
Part 4 could really benefit from grouping steps 17 to 25 into "Backup your NANDs" (such grouping should take place more oftenly anyway, but it's really annoying in that part)
01:27 < neobrain> Plailect: https://github.com/Plailect/Guide/wiki/NAND-Size should use MiB instead of MB, since apparently you are measing in units of 1024
part 4/step 35 lacks a note that the user needs to boot back into rednand (since tinyformat will have rebooted to sysnand after step 33 AFAICT) (note that this was incorrectly reported as part3/step 35 on IRC)
https://github.com/AuroraWright/arm9loaderhax/releases has two kinds of releases (noscreeninit vs screeninit), and it's not clear from the guide (part 5) which one to use. If it's explained at the top of the page, some sort of reference needs to be given from within the bullet list.
Part 5/Section 1/Step 14 talks about "the Uncart zip", but the link provided for uncart (https://github.com/AileSc/uncart/releases) at the top of the page does not provide any zip (anymore?), but just plain binaries
The end of Part 5/Section 1 is just annoying to read. Please merge those separate "Copy *.bin to ..." and "rename X to Y" bullet points into one point (because they constitute a single logical step). If people fail to do this properly, it will not cause any harm down the line and it's trivial to troubleshoot ("nothing happens when I press Y on boot" => fix your filenames)
In Part 5 / Section 5 / Step 8, no message relating to "starter.bin" was printed for me
Part 5 / section6 needs a note as to which program should be used and how to start it (EmuNAND9, holding Y on boot). Also, I think this is the first time in the guide that EmuNAND9 is used for NAND dumping (OTHelper was used before), so a little more handholding might be a good idea. A possibly better alternative might be to even replace prior use of OTHelper for NAND dumping with EmuNAND9 for consistency.

Oh wow nice work, the starter.bin thing is normal and the slow emunand booting is propbly because your sd card's speed is low. Besides that @Plailect can add it if he wants.

On Jun 21, 2016, at 6:53 AM, Tony Wasserka<EMAIL_ADDRESS>wrote:
https://github.com/Plailect/Guide/wiki/Get-Started and https://github.com/Plailect/Guide/wiki/Part-1-(Homebrew) both contain a list of things to do separated by firmware. It's cognitively hard to find the appropriate section for a particular firmware though, so it should be grouped as a table, or at least as a proper list (via *). E.g.
9.0 - 9.8: blabla
9.9 - 10.5: blabla
....
Booting my EmuNAND took really long to get any (useful) visual feedback. It would be good to note somewhere that it may take up to two minutes, especially when the emunand has been formatted from the system settings (or via TinyFormat).
23:41 < neobrain> Plailect: the D9WIP version linked at https://github.com/Plailect/Guide/wiki/9.2.0-Update-(rxTools-2.5.2) doesn't work for me, https://github.com/d0k3/Decrypt9WIP/releases/tag/20160607 does
Part 4 could really benefit from grouping steps 17 to 25 into "Backup your NANDs" (such grouping should take place more oftenly anyway, but it's really annoying in that part)
01:27 < neobrain> Plailect: https://github.com/Plailect/Guide/wiki/NAND-Size should use MiB instead of MB, since apparently you are measing in units of 1024
part 4/step 35 lacks a note that the user needs to boot back into rednand (since tinyformat will have rebooted to sysnand after step 33 AFAICT) (note that this was incorrectly reported as part3/step 35 on IRC)
https://github.com/AuroraWright/arm9loaderhax/releases has two kinds of releases (noscreeninit vs screeninit), and it's not clear from the guide (part 5) which one to use. If it's explained at the top of the page, some sort of reference needs to be given from within the bullet list.
Part 5/Section 1/Step 14 talks about "the Uncart zip", but the link provided for uncart (https://github.com/AileSc/uncart/releases) at the top of the page does not provide any zip (anymore?), but just plain binaries
The end of Part 5/Section 1 is just annoying to read. Please merge those separate "Copy *.bin to ..." and "rename X to Y" bullet points into one point (because they constitute a single logical step). If people fail to do this properly, it will not cause any harm down the line and it's trivial to troubleshoot ("nothing happens when I press Y on boot" => fix your filenames)
In Part 5 / Section 5 / Step 8, no message relating to "starter.bin" was printed for me
Part 5 / section6 needs a note as to which program should be used and how to start it (EmuNAND9, holding Y on boot). Also, I think this is the first time in the guide that EmuNAND9 is used for NAND dumping (OTHelper was used before), so a little more handholding might be a good idea. A possibly better alternative might be to even replace prior use of OTHelper for NAND dumping with EmuNAND9 for consistency.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

https://github.com/maorninja/Guide/wiki for (1st bullet point)
It does mention it (7th bullet point)
8. Its fine.
10. What?

I don't get what your trying to do? Also that's not even Plailects guide it's a fork of it and may be out of date.

On Jun 21, 2016, at 12:23 PM, maorninja<EMAIL_ADDRESS>wrote:
https://github.com/maorninja/Guide/wiki for (1st bullet point)
It does mention it (7th bullet point)
8. Its fine.
10. What?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

What I'm trying to is answer his questions. Also, I updated it so it's more then Plailect's guide.

@maorninja These aren't questions.

@neobrain sorry. I mean't your list.

These have all been implemented.