Version 2 not installable/published correctly

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[ ] This issue affects my Ory Network project.
[x] I have joined the Ory Community Slack.
[X] I am signed up to the Ory Security Patch Newsletter.

Describe the bug
Version 2 of this package is not installable, as it's not published according to go's requirements (https://go.dev/blog/v2-go-modules).

...major version of a module must have a different module path than the previous version. Starting with v2, the major version must appear at the end of the module path (declared in the module statement in the go.mod file).

I think the fix will be as simple as updating the module in https://github.com/ory/hydra-client-go/blob/f558e85344c8c9ee053662f40f42fecc85dc3488/go.mod#L1 to github.com/ory/hydra-client-go/v2
Reproducing the bug
<EMAIL_ADDRESS>❯ go get -u<EMAIL_ADDRESS>go get<EMAIL_ADDRESS>invalid version: module contains a go.mod file, so module path must match major version ("github.com/ory/hydra-client-go/v2")
↩ 1 (ERROR)
<EMAIL_ADDRESS>❯ go get -u github.com/ory/hydra-client-go/v2
go get: module github.com/ory/hydra-client-go@upgrade found (v1.11.8), but does not contain package github.com/ory/hydra-client-go/v2
↩ 1 (ERROR)

Relevant log output
No response
Relevant configuration
No response
Version
Upgrading from v1.11.8 to v2.0.1
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
Kubernetes
Additional Context
No response

Same issue here

FYI, a workaround is to install by SHA, instead of by version. You can grab the sha associated with the release
e.g.
go get -u github.com/ory/hydra-client-go@76cf2d374d54a15b27ea0d7f9570069ceed30abc

results in a diff of
-       github.com/ory/hydra-client-go v1.11.8
+       github.com/ory/hydra-client-go v1.11.9-0.20221027120355-76cf2d374d54

(the version being 1.11.9 is expected, as go's basically saying it's the next greatest release, I think)

ack

https://github.com/ory/sdk/pull/225

This doesn't appear fixed? Both project go.mod files still are missing v2 suffixes. https://github.com/ory/hydra-client-go/blob/f558e85344c8c9ee053662f40f42fecc85dc3488/go.mod#L1, https://github.com/ory/sdk/blob/5711942bbd989c6b6d82ec27a00bd63ebbe19649/clients/hydra/go/go.mod#L1?

We still need to release a new version of ory hydra

I believe they did not communicate it. Their documentation still gives the wrong string that gives 1.18.
If you want to install the latest version, I figured out in the code they changed the package's name to the following: github.com/ory/hydra-client-go/v2.
go get github.com/ory/hydra-client-go/v2

That is correct!


feat(server): Add Handler per-connection hooks

I'm adding a feature to my webserver:  whenever the thread pool is getting too busy (say 4 out of 8 threads are occupied, possibly idly with keep-alive requests), we force Connection close on subsequent requests until the thread pool isn't so busy anymore.
To do this, I need hooks into the beginning and end of the connection loop.  The Handler handle function is per-request, not per-connection.
A very simple addition, but please consider the function names, comments, etc., as I have no preference for these.

This seems like an acceptable situation while async support is worked out. Thanks!

Go-go async support! That's gonna be awesome.  Thanks


BREAD Reorder

Version information

Laravel: v6.3
Voyager: v1.3
PHP: 7.2
Database: MySQL

Description of problem

I need reorder any BREAD with childs. Now we have button #order, but i need reorder elements with childs! In Backpack we can do it. We just need to add parent_id, lft, rgt and depth columns in our table and we got REORDER with childs.
I have big problems now, coz my lovely Voyager do not have REORDER with CHILDS REORDER.
I have 400 page in my website. I just want to have 400 rows in my table and have parent_it, lft, rgt, depth fields. And simple functionality as Backpack with Reorder any level!

This is NOT menu reorder with childs we need. Resource (database table with rows) reorder with childs need.
I dont' want any feature, but i need this! Is most grate feature what we need! We need to get tree of all resources in our BREAD - just 4 fields (parent_id, lft, rgt, depth).
Please guys make me happy! Please! I love Voyager. But I have biggest minus with it.

Extend order view
@extends('voyager::bread.order')

@section('javascript')
    <script>
        $('document').ready(function () {
            $('.dd').nestable({
                maxDepth: 3
            });
        });
    </script>
@stop

Then you'll need to extend VoyagerBaseController order method for the saving part.
Have fun!

Extend order view
@extends('voyager::bread.order')

@section('javascript')
    @parent

    <script>
        $('document').ready(function () {
            $('.dd').nestable('destroy');
            $('.dd').nestable({
                maxDepth: 3
            });
        });
    </script>
@stop

Then you'll need to extend VoyagerBaseController order method for the saving part.
Have fun!
Edit: forgot @parent and use destroy.

Thank you for small start. ; ) Okay, I am working on it now.
Voyager need to have reorder with childrens in any BREAD object.
I will let you know how it will be ready...

All is ready. I’ll check for various bugs, prepare a pull request and send it for approval.

All is ready.
Sent pull request here:
https://github.com/the-control-group/voyager/pull/4671


[ECS] Delete old tasksets before QuickSync except PRIMARY

What this PR does / why we need it:
If old deployments remain, the new deployment will sometimes fail.
So this PR removes old deployments before the new deployment.
Which issue(s) this PR fixes:
Workaround for #4692
Does this PR introduce a user-facing change?:

How are users affected by this change:
Is this breaking change:
How to migrate (if breaking change):

This is closed because this is just a workaround in hurry, and I'll fix it in another PR.


Trouble when debugging build of ObjC package: error: no such module 'PackageDescription'

Description
I am trying to better understand how SPM builds an ObjC package and would like to debug the SPM source code while doing so.
I've followed the CONTRIBUTING.md guide to get set up for local development. I've created a simple ObjC Swift package and am trying to use my local, cloned copy of SPM to build it.
While I can build a simple Swift project just fine, I can't get a ObjC package to build.
Expected behavior
I expected the ObjC package to build when pointing to it (as a launch argument in the scheme definition) while running the swift-build scheme.
Actual behavior
I get the following error in the console:
Invalid manifest
/Users/nickcooke/Developer/ObjcPackage/Package.swift:4:8: error: no such module 'PackageDescription'

Note that the ObjC package builds fine when running swift build in it's directory.
Steps to reproduce

Create a simple ObjC package using Swift Package manager.
My project's Package.swift looks like:

Navigate to your local copy of Swift Package Manager and open the Package.swift in Xcode.
Select the swift-build scheme
Edit the scheme to pass the following argument on launch:

--package-path /path/to/ObjcPackage

Run the scheme.

I'm getting the follow error in the console.
Invalid manifest
/Users/nickcooke/Developer/ObjcPackage/Package.swift:4:8: error: no such module 'PackageDescription'
import PackageDescription
       ^

Swift Package Manager version/commit hash
5275f3789028f4faee7ccaa8012129ef678a1402
Tip of main from July ~21
Swift & OS version (output of swift --version && uname -a)
swift-driver version: 1.60 Apple Swift version 5.7 (swiftlang-<IP_ADDRESS>.1 clang-14<IP_ADDRESS>)
Target: x86_64-apple-macosx12.0

Did you previously build the "SwiftPM-Package" scheme?

Thanks for looking @neonichu. I don't recall but am not 100% sure. Should I build it?

Yah, you basically always have to build that scheme first, because it builds the PackageDescription library.

Thanks @neonichu! That worked 🎉
Do you have an explanation as for why I was able to successfully build a Swift-only package without first building the SwiftPM-Package scheme?

Also, what do you think about me adding a note here to clarify that one should build the SwiftPM-Package scheme before  running other schemes?

We cache the results of manifest evaluation, so it could be that we considered the cached results as valid and didn't end up needing the PackageDescription library.
Adding a note about this sounds good to me, thanks.

Gotcha, thanks!


chore(deps): bump from

Update zeebe-io/zeebe-operate-helm from 0.0.24 to 0.0.26
Command run was jx step create pr chart --name zeebe-operate --version 0.0.26 --repo https://github.com/zeebe-io/zeebe-full-helm.git

Update zeebe-io/zeebe-cluster-helm from 0.0.128 to 0.0.141
Command run was jx step create pr chart --name zeebe-cluster --version 0.0.141 --repo https://github.com/zeebe-io/zeebe-full-helm.git

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign salaboy
You can assign the PR to them by writing /assign @salaboy in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: salaboy:x: jenkins-x-botjenkins-x-bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[FLINK-21290][table-planner] Support project push down for window TVF.

What is the purpose of the change
This pull request aims to support project push down for window TVF.
Brief change log

Introduce ProjectWindowTableFunctionTransposeRule
Update xml and .out of effected test case.

Verifying this change

Existed UT

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@godfreyhe Thanks for review, I've updated, please have a look.

@flinkbot run azure

@flinkbot run travis

@flinkbot run azure

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=22300&view=results

@flinkbot run azure


[Bug]: There are spaces before and after the names and parameters of MySQL functions and stored procedure formats

ODC version
odc431
OB version

What happened?

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?
Format function after creation
Anything else we need to know?
No response

fixed in dev-4.3.1

The problem still exists

Fixed In Commit fd338ebd8596f86f9e58ca2a98f817d6702d9a4a
------
xiaokang
Mon Jul 8 10:32:45 2024 +0800

pass


Updates to labs 3 and 4

Lab/Demo: 3 and 4
Fixes #3 .
Changes proposed in this pull request:
Lab 3: changed text and code to match the new sample database which contains product data now (instead of address data)
Lab 4:
-add instructions regarding security/sql user and pass
-add instructions regarding installing the Microsoft.Synapse

@Mihai-Ac
Please take a look at the feedback for the provider registration changes.


Native support for arm64 iOS Simulator

Steps to Reproduce
There is a scrolling problem with Isar and the M1 iOS simulator. As soon as Isar is activated, scrolling no longer works as usual. Every gesture scrolls way too much. It was possible to switch the simulator to Rosetta, but unfortunately this no longer works on the latest Mac Monterey version (12.6).
More information for the scrolling bug  on StackOverflow.
As far as I can see, the problem is that you are excluding the Arm64 architecture in the isar_flutter_libs.podspec.
'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'i386 arm64',

Details

Platform: iPhone Simulators on MacBook M1 with MacOS 12.6
Flutter version:  3.3.0
Isar version: 3.0.0

[x] I searched for similar issues already
[x] I filled the details section with the exact device model and version
[x] I am able to provide a reproducible example

Our current workaround is to to use a real device for debugging or temporary disable isar.

@DFelten Thanks. Nice catch by the way! I was scratching my head.
FYI. I'll try modifying the podspec (temporarily) and see how it goes.

@DFelten I was able to compile the library for the arm64 Simulator and use it as a workaround. It works, but you can't pack both arm64 iOS and arm64 simulator together for distribution. 🥲

libisar.a.zip
You can try dropping this into your pubcache as a workaround and modify podspec, but don't ship it with the app.

3.0.1 ships arm64 simulator binaries


moveit_visual_tools: 3.0.4-1 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository moveit_visual_tools to 3.0.4-1:

upstream repository: https://github.com/davetcoleman/moveit_visual_tools.git
release repository: https://github.com/davetcoleman/moveit_visual_tools-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.20
previous version for package: 3.0.4-0

moveit_visual_tools
* Removed stray debug output
* Improved debugging output for the hideRobot() feature and virtual_joints
* Contributors: Dave Coleman

Ready to merge


small correction in ref-based tutorial

'condition' should be in lower case as stated in next paragraph

Thanks @polkhe


load dummy image to avoid duplicate request getting sent on lazy load

Images are loading twice as part of lazy load, this PR will avoid the duplicate by having a dummy image src attribute and then replacing it with the loaded image src

@dinbror This issue is still happening. Images are getting loaded twice which naturally affects performance.

Any updates?


sayPlayer Wrong Parameters

Am I stupid?
I am providing an integer for the player and a message as a string and the answer I get is "Wrong parameter type(s)!"
Am I doing something wrong?

Mmh, something must be wrong with you code :/ This snippet validates the parameter types:
if (!is_int($player) || !is_string($message)) {
       throw new \Exception('Wrong parameter type(s)!');
}

If you are 100% sure, that your types are correct, you can work around by sending the command "manually":
$arc->command("Say $player $message")

I have just double checked my types...
The player ID is even intval()'ed before and the message is a string.
I am sending the command over a JSON api, so I'll have to look into that again.

Anyway, it works with the manual say command


Redact passwords in .yml files

We need to redact passwords some of the various password that appear in the yml files.

Do we have a list?  As you are aware, the passwords aren't necessarily in the open - they can be part of the URL.  Are you OK with requiring users who want this functionality to pass in some sort of formatted input file specifying what they want scrubbed?

#39 can possibly get merged into this issue.
I really think we should redact the credentials for the user instead of making them pass in a sanitized file. But maybe we should have a flag that disables this feature if needed.
I can work with dev to come up with a list of credentials that are known to exist in the various config files. The ones in a URL should be easy to spot with a regex (I think).

Done, in 2.0.6

Discovered that cloud.azure.storage.my_account.account and cloud.azure.storage.my_account.key is not redacted in the elasticsearch.yml collection, so worth adding to the list of already redacted credentials here.
This is only used if the user has the Azure plugin installed on their cluster.

Not sure if any of these should also be redacted?
xpack.notification.slack.account.heartbeats.url
xpack.notification.slack.account.healthmonitors.url
xpack.notification.slack.account.security.url


Fixed file links

File links (Such as links to hosted PDFs) are currently broken cause the router thinks that it is a content page, not a hosted file.

Fixed in 3822b28bbd98be583095a77ec9510716c65662a1


Invalid JSON in options error when omitting the options input entirely

When calling the deployer GitHub action without setting any values for the options input, the following error message appears: Invalid JSON in options
It doesn't break the deployment, however an error message in a successful deployment log feels weird :) And with no actual problems occurring, I was wondering if the error detection is slightly off.
I'm not familiar with the try-catch logic yet, so I cannot provide and improvement as a PR at this time.
Relevant code snippet:
https://github.com/deployphp/action/blob/06aeb295d6432970d615c5551e3d941e50349c46/index.js#L116-L126
Readme section:
https://github.com/deployphp/action/blob/06aeb295d6432970d615c5551e3d941e50349c46/README.md?plain=1#L26-L29

any update on this

duplicate of #72


Idea grammar changes

Purpose
This PR updates plugin grammar for the latest syntax changes.
Fixes #14003.
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[x] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Closing in favor of #14820


Is it Windows compatible?

OS: Windows 10
Node version (node -v): v6.6.0
phantomjs: 1.9.6

I'm just trying to run a simple script and I get

error: Could not spawn [/usr/local/share/phantomjs/bin/phantomjs] executable. Pl                                                                             ease make sure phantomjs is installed correctly.
error:  Error: spawn /usr/local/share/phantomjs/bin/phantomjs ENOENT
at exports._errnoException (util.js:1036:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "D:\AppData\Roa                                                                             ming\npm\node_modules\npm\bin\npm-cli.js" "run" "start"

Although phantomjs is on my PATH, it is not installed in /usr/local/share which would be a directory I would install phantomjs to if I was running *nix.
What am I doing wrong?

Please make sure phantomjs is installed correctly

This error happens when phantomjs can't be installed. So either make sure you can install phnatomjs from source or install latest version of it so that this module doesn't need it.

I don't have Windows computer, but let me know what you find.

I'm not sure what changed, I'm not getting this same error. If anyone comes across this issue, just uninstall and install via a different method (npm install prebuilt, build it, or download the binary).

Interesting. I am trying to use yarn so maybe this will be fixed.

Interesting. I am trying to use yarn so maybe this will be fixed.

I have Windows 10. Just ran across this today, and using yarn add phantom fixed it. Thanks.


Implement sock_accept and basic networking

Together with https://github.com/rust-lang/rust/pull/93158 this enables basic networking in rust.
See https://github.com/bytecodealliance/wasmtime/issues/3730 for the tracking issue.
With the addition of sock_accept() in wasi-0.11.0, wasmtime can now implement basic networking for pre-opened sockets.
For Windows AsHandle was replaced with AsRawHandleOrSocket to cope with the duality of Handles and Sockets.
For Unix a wasi_cap_std_sync::net::Socket enum was created to handle the {Tcp,Unix}{Listener,Stream} more efficiently in
WasiCtxBuilder::preopened_socket().
The addition of that many WasiFile implementors was mainly necessary, because of the difference in the num_ready_bytes() function.
A known issue is Windows now busy polling on sockets, because except for stdin, nothing is querying the status of windows handles/sockets.
Another know issue on Windows, is that there is no crate providing support for fcntl(fd, F_GETFL, 0) for sockets, so WasiFile::get_fdflags() always returns 0.
Todo

[ ] Test cases

@haraldh Is this still a draft?

@npmccallum now it's ready for a review :)

Changed one more thing:
             async fn get_fdflags(&self) -> Result<FdFlags, Error> {
-                Err(Error::badf())
+                let fdflags = self.0.as_filelike().get_fd_flags()?;
+                Ok(from_sysif_fdflags(fdflags))
             }

All right.. rust-lang PR merged :partying_face:

@sunfishcode Is this ready for merge?

Yes, looks good to me!


making scripts generic enough so that playbooks can be run on baremetal or other IaaS platform

Good idea, do you have an idea how do you like to use/apply the stuff to an external cluster? And which components (e.g. letsencrypt)
I can imagine to do something like:
# cluster.yaml contains all informations from your cluster (auth, url, dns provider credentials,..)
./ansible/externalcluster/install_letsencrypt.yaml -e cluster.yaml

No feedback, closed.


feat: Track GitHub tags with access_token

Don't think this is really needed. Don't know of any cases where versions only have a tag, and not a release

Don't think this is really needed. Don't know of any cases where versions only have a tag, and not a release


SVG and logoPunchoutBackground(true)

logoPunchoutBackground(true) has no effect on SVG files.

<?php
use Endroid\QrCode\Builder\Builder;
use Endroid\QrCode\Encoding\Encoding;
use Endroid\QrCode\Writer\PngWriter;
use Endroid\QrCode\Writer\SvgWriter;

foreach (['png', 'svg'] as $extension) {
    $generalBuilder = Builder::create();

    if ($extension === 'png') {
        $generalBuilder->writer(new PngWriter());
    } else {
        $generalBuilder->writer(new SvgWriter());
    }

    $generalBuilder->writerOptions([])
        ->data('https://github.com/Bacon/BaconQrCode')
        ->encoding(new Encoding('UTF-8'))
        ->size(320)
        ->margin(10)
        ->logoPath('logo.png')
        ->logoResizeToWidth(100)
        ->logoPunchoutBackground(true);
    }

    $generalBuilder->build()->saveToFile('qrcode.' . $extension);
}

Tested with 5.1.0

Confirmed with v6.0.0


Crash Report

Hi minecraft crashed and gave me this error by designating the OTG as a probable cause, I hope it can be useful to fix the problem:
crash-2019-06-30_21.59.18-server.txt

Hey @IGieckI, thanks for reporting this. Same as #279 .


Add pkg_test.go files for every package

Unless a _test.go file is present in a package, go toolchain will not consider that package for the purposes of coverage metrics. This is a regression and will be fixed in go1.22 but until then we need these files in each package to keep the coverage report honest.
There is an expected drop in code coverage with this PR. However the newer numbers will be a lot more accurate going forward.

/ok-to-test

/test e2e-ncn-1-calico-k8s-v.1.27-api-upgrade


Traffic Stats - Store status codes by host

Traffic Stats should store status codes by host.  Ideally this would be by host and deliveryservice so that you could find status codes for a DS per cache.  Traffic Monitor seems to have all the data necessary, just need to get Traffic Stats to gather, parse, and write to Influxdb.

Moved to Apache JIRA.


Second version of switching things to cloud build.

Ref #29 #35
cc @duggelz
This version is a lot simpler but it builds the interpreter each time and takes about 35 minutes to run.

+1, I like this as a good first step.
The next thing we can do is have the interpreter builder upload to GCS, generate a signature, and use that to determine if it needs to rebuilt.

+1

Is this a real error or just a symptom of a timeout?
Fetched 165 MB in 35s (4593 kB/s)
E: Failed to fetch http://httpredir.debian.org/debian/pool/main/b/blas/libblas-common_1.2.20110419-10_amd64.deb  Error reading from server. Remote end closed connection [IP: <IP_ADDRESS> 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
The command '/bin/sh -c /scripts/install-apt-packages.sh' returned a non-zero code: 123
make: *** [build] Error 123

Fetched 165 MB in 35s (4593 kB/s)
�[91mE: Failed to fetch http://httpredir.debian.org/debian/pool/main/b/blas/libblas-common_1.2.20110419-10_amd64.deb Error reading from server. Remote end closed connection [IP: <IP_ADDRESS> 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
�[0mThe command '/bin/sh -c /scripts/install-apt-packages.sh' returned a non-zero code: 123
make: *** [build] Error 123

That looks like some kind of timeout. I saw that (although a different package) yesterday at least once. The httpredir server seems to be less stable than our old gce_debian_mirror, but that is getting turned down at some point.

I would generally just ignore travis for now. Manually verify or use jenkins.

Should I merge this?

Let me finish my release first, then yes.
On Wednesday, November 2, 2016, dlorenc<EMAIL_ADDRESS>wrote:

Should I merge this?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/python-runtime/pull/36#issuecomment-258021127,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAlIUjArha3vodIEHjpAXMrkvFudYC9Wks5q6RDcgaJpZM4Ki1xK
.

Merging now...


Cloud Run recipe handler first draft

A first draft of a GCP Cloud Run recipe handler will evolve here. For now, I've just committed the official cloud run python quickstart (as a working baseline & reference for where I started).

Note: The quickstart worked out of the box, with the exception that we cannot run unauthenticated services, for the now-classic reason: organization policy dictates that any user invoker must have a @columbia.edu email address. That's okay, we do want this service to be authenticated (because it's purpose is to start Dataflow jobs). And we can give non-Columbia developers service accounts as needed.

Some details, expanding on what was covered at yesterday's Coordination meeting:

Cloud Run supports custom containers whereas Cloud Functions do not. So we definitely want Cloud Run.
To accept parameters, Cloud Run requires we run a web service. (The Cloud Run Jobs offering doesn't support param-passing.) As demonstrated in this SO post, the web service layer can be very lightweight, making Cloud Run feel almost like "just a function."
Re: per-job environment customization, I agree with @rabernat's proposal that the appropriate level of complexity for us at the moment is to pull a pre-built base image, and pip-install custom dependencies onto the base. This is contrasted with building an entirely new image as I did here. The tradeoff (as observed by @alxmrs) is that each Dataflow worker also needs to run the pip-installs, which will come at a (very small, for most things) start-up time cost, and also a small risk of client/worker version mismatches (which can be mitigated with version pinning and the --no-deps flag).
Because we expect that any given Cloud Run call may alter its own environment with some dynamic pip-installs, we will presumably want to deploy the service with the --concurrency=1 option, so that each call gets its own container instance.

Per chat yesterday afternoon, @yuvipanda agrees that this service would be well-accommodated by the composable Spawner approach he's proposed (which I've started implementing in https://github.com/pangeo-forge/pangeo-forge-orchestrator/pull/197).
In practice, this would mean the production Pangeo Forge Cloud instance could spawn recipe handling processes using a GCPCloudRunSpawner.run() method, which would make an (authenticated) call into the service deployed from this repository. This GCPCloudRunSpawner will receive an HTTP response from Cloud Run, and will need to parse that response into a generic result object. This allows orchestrator to interpret recipe child process results uniformly, regardless of whether they were produced by a GCPCloudRunSpawner, LocalSubprocessSpawner (which can be used for development and testing), etc. In pseudocode:
@dataclass
class RecipeCalledProcessResult:
    json_logs: str
    exit_code: int

class Spawner(ABC):
    @abstractmethod
    def run(
        cmd: List[str],
        pip_install: Optional[List[str]] = None,
    ) -> RecipeCalledProcessResult:
        """Spawn a new process and run a command in it.
        :param cmd: The command to run. Most commonly a call to `pangeo-forge-runner`.
        :param pip_install: If given, these dependencies will be installed via pip before running the cmd.

        :return: The result of the called process, parsed as a ``RecipeCalledProcessResult`` instance.
        """
        pass

class GCPCloudRunSpawner(Spawner):
     ...

☝ This last bit is really reference for https://github.com/pangeo-forge/pangeo-forge-orchestrator/pull/197, but somehow thinking about it here brought it into clearer focus, so just dropping it here for now.
Ok, enough "thinking"! This is making sense now, so I'll actually make some commits to rough out the idea now.

Notes to self re: next steps:

Add some server logging. These calls trigger long-running processes and it's a long wait to figure out where they might be / are hanging.
As used in orchestrator, FastAPI background tasks are probably appropriate, so we can get the response back in a timely manner.


Move to 3.0 Preview 6 SDK

Looks like migrating to the new SDK broke parts of our build.

This is the pain induced by moving so late :(.

Tagging to see this.

From email, it seems like we need a newer version of VS. I've switched to using the VS preview queues. We'll see whether the tests feel better after this.

Okay that didn't seem to work. We'll apply the workaround instead.

:up::date: to add dotnet/cli#11378 workaround (NuGet versions in current use do not honour PrivateAssets="All" in @(FrameworkReference) items). Local builds are now clean.

Thanks. Code check failure looks like flakiness. Not sure about the site extension error though. I'll re-run it and see if it's flakiness or something is really broken.

Well it seems like the SDK actually broke SiteExtensions build. Investigating.

Thanks @JunTaoLuo❕

Thanks very much @JunTaoLuo❕

@JunTaoLuo do you approve this PR now?

I want to see the build succeed first though.

Me too 😈

It's at the artifact publishing step now so I think it's good to merge. I'll do some additional verification of the built site extensions tomorrow.


Support for IR (Infrared) transmitters and receivers

IR

Send raw data string via Protobuf

User would paste the raw code into a new wippersnapper component

Raw code(s) may be write data or configuration data.
Possibly add a way on the fronted of saving N number of IR codes.

Applications:

IR-controlled appliances

ACs, heaters, fans

Accessibility projects

https://learn.adafruit.com/building-the-assistive-technology-ultimate-remote

https://www.adafruit.com/product/5639


Running development with https flag returns http urls from helper methods

Environment

Operating System: Darwin
Node Version:     v20.10.0
Nuxt Version:     3.9.1
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
Can't use stackblitz/sandbox as these handle https automatically, instead...

Pull and start with yarn dev (or nuxt dev --https): https://github.com/zacwebb/nuxt-https-repro
Hit the endpoint https://localhost:3000/api/https-test
Observe that helper: "http", whereas it should be https
vs when building for production it's correctly https: https://nuxt-https-repro.onrender.com/api/https-test

Describe the bug
When starting nuxt with the --https flag in development, the h3 getRequestProtocol method should return https rather than http.
This can lead to some issues for packages that use getRequestURL (which calls getRequestProtocol) returning http urls when they should be returning https (see my original issue for context: https://github.com/Hebilicious/authjs-nuxt/issues/151)
Couldn't quite track down whether this was an issue with h3, nitro, or nuxt specifically but since getRequestProtocol simply checks the value of (event.node.req.connection as any).encrypted, I'm assuming it's an issue with Nuxt's implementation of https with nitro when in dev mode.
This isn't an issue in the production build (even locally)
Additional context
No response
Logs
No response

Can you please verify with nuxt dev --no-fork? If it works, it is probably same issue as https://github.com/nuxt/cli/issues/324

Can you please verify with nuxt dev --no-fork? If it works, it is probably same issue as nuxt/cli#324

No luck unfortunately, nuxt dev --no-fork --https results in http from getRequestProtocol still

Have you switched to nuxt nightly channel as well?

Awesome thanks for confirming. Let's track it from https://github.com/nuxt/cli/issues/324 then!


Noticed an error while running tests more than once

Adding -p to the mkdir command makes it so the error is no longer an issue.
What I was seeing:
...
ok 127 Prints nodenv version when nodenv is installed
mkdir: /tmp/tmp-spacefish/node_modules: File exists
ok 127 Prints nothing when using the "system" version of node with nvm
...

This fixes issue #115. 😊

:tada: This PR is included in version 2.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


HDR meta information to AVC from HEVC

@JeromeMartinez Hi, do you have a chance to look at this?

Sorry I didn't see that you pushed a modified version (no GitHub notification in that case :-( ).
Thanks!

Thanks


Failed to build the docs

Describe the bug
I cannot build the docs
To Reproduce
Running the command according to build the docs section results in failure.
$ make html
sphinx-build -b html -d _build/doctrees   . _build/html
Running Sphinx v4.3.2

Extension error:
Could not import extension sphinxcontrib.mermaid (exception: cannot import name 'ENOENT' from 'sphinx.util.osutil' (/Users/tui/Library/Caches/pypoetry/virtualenvs/django-generate-series-Vs9BvJIc-py3.9/lib/python3.9/site-packages/sphinx/util/osutil.py))
make: *** [html] Error 2

Expected behavior
No error should occur and HTML docs should be generated.
Version:

python: 3.9.0
django-generate-series: 0.4.5

Additional context
The bug comes from sphinxcontrib-mermaid version 0.6.x not adapting to sphinx version 4.0.0 API changes.
Solutions

Workaround according to https://github.com/mgaitan/sphinxcontrib-mermaid/issues/72#issuecomment-835822975
Update sphinxcontrib-mermaid version to 0.7.0

Not sure how I missed this before, but fixed in latest version. Thank you for the report.


Notifying a service from a custom resource

Version:
Chef Development Kit Version: 0.10.0
chef-client version: 12.5.1
berks version: 4.0.1
kitchen version: 1.4.2
Environment:
OS X El Capitan
Scenario:
Notifying a service from a custom resource
Steps to Reproduce:
I've defined a custom resource (resources/quicktest.rb):
property :name, kind_of: String, name_attribute: true

# Chef 0.10.10 or greater
default_action :disable

action :disable do

  # verify the resource is in the collection
  test_serivce = resources(service: 'test')
  Chef::Log.fatal("test_serivce:  #{test_serivce}")

  execute "foo" do
    command "bar"
    notifies :nothing, 'service[test]', :delayed
  end
end

and am calling it from a recipe, where I define the service (recipes/quicktest.rb):
service 'test' do
  service_name 'test'
  supports [:start, :restart, :reload, :status]
  action [:nothing]
end

schoolspring_quicktest 'foobar' do
  action :disable
end

My kitchen file(s) look like this:
---
driver:
  name: docker
  socket: tcp://<IP_ADDRESS>:2375
provisioner:
  name: chef_zero

platforms:
  - name: ubuntu-12.04

suites:
  - name: qt
    run_list:
      - recipe[schoolspring::quicktest]
    attributes:

Expected Result:
The service[test] is found and notified
Actual Result:
When I run it via test kitchen, I'm getting the following error:
       Recipe: schoolspring::quicktest
         * service[test] action nothing (skipped due to action :nothing)
       * schoolspring_quicktest[foobar] action disable[2016-01-14T20:52:22+00:00] FATAL: test_serivce:  service[test]

           ================================================================================
           Error executing action `disable` on resource 'schoolspring_quicktest[foobar]'
           ================================================================================

           Chef::Exceptions::ResourceNotFound
           ----------------------------------
           resource execute[foo] is configured to notify resource service[test] with action nothing, but service[test] cannot be found in the resource collection. execute[foo] is defined in /tmp/kitchen/cache/cookbooks/schoolspring/resources/quicktest.rb:47:in `block in class_from_file'

           Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/schoolspring/recipes/quicktest.rb

             8: schoolspring_quicktest 'foobar' do
             9:   action :disable
            10: end

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/schoolspring/recipes/quicktest.rb:8:in `from_file'

           schoolspring_quicktest("foobar") do
             action [:disable]
             retries 0
             retry_delay 2
             default_guard_interpreter :default
             declared_type :schoolspring_quicktest
             cookbook_name "schoolspring"
         recipe_name "quicktest"
           end

This is expected behavior. The 12.5 custom resource syntax uses use_inline_resources internally and so has the same behavior. It creates an internal run context with an isolated resource collection. If you want to design code like this, Poise's notifying_block helper allows it.


error: The "header" component has been registered but not used (vue/no-unused-components) at

Version
3.9.2
Reproduction link
https://github.com/ajeethhacki
Environment info
npm -v  6.10.1,  node -v  v10.14.2, vue --version  3.9.2

Steps to reproduce
create new project  in the hellow world page add two component and then run it the above i told error will occur
What is expected?

What is actually happening?
The "header" component has been registered but not used (vue/no-unused-components)

As required, please add a reproduction.


Possibility to reduce framerate?

Hello,
I investigate on the pre-heating-time of the HoloLens2, so I need to run the StreamRecorderApp for about 90 minutes, only activating the Long Throw Depth Sensor. Unfortunately I noticed that the App runs very instable when using it for 10 or 15 minutes. After hitting the "Stop"-Button, the App takes several minutes to reload and it does not always give reliable results. Sometimes the app just crashes down without saving the recordings.
I suspect that this happens because of the high framerate (5fps in release-mode), so the app collects a big amount of data in that period of time.. Is there any possibility to reduce the framerate to make longer investigations possible (eg. 1 fps or still fewer)?

The API does not allow for controlling the sensor frame rates. You can try to modify the app recording loops to drop frames or use sleeps to slow down the capture rate.

Yes, one way to reduce the framerate inside the app could be to modify the IsNewTimestamp function in
RMCameraReader into a function that checks if the difference in timestamps is greater than a given threshold.
In general, the StreamRecorder app offers a demo about capture capabilities, but for specific used it should be customized and optimized. For instances, hand tracking data is saved in main memory and just dumped to disk only at the end of each capture sequence. This might be problematic for very long captures.

Hi @fehmerli,
in case you are still interested, i modified the IsNewTimestamp function to enforce a minimal difference of minDelta (in Hundreds of Nanoseconds) between frames. Maybe it is useful to you:
https://github.com/cgsaxner/HoloLens2-Unity-ResearchModeStreamer/blob/6e3d2ef3c6eec6fa875df70cc37d1ecce8a1f3fb/HL2RmStreamUnityPlugin/ResearchModeFrameProcessor.cpp#L175


I tap/click a photo to zoom it in, but the app makes me go through all the button help first

Open a product screen.
Click the main photo, expecting the photo to be zoomed in.
Get a description of the first button.
Click elsewhere.
Get a description of the second button.
…
?. Get a zoomed-in photo.

I don't know — it stopped happening? Or maybe it was a different place.

Afaik it "expires" after 3/4 times. I have to check.

Normally, this is the 1st time onboarding, and it does every single button available, so 7 times.


Small fixes

Coverage remained the same at 100.0% when pulling fcff2c686a0a73ba78bcc0237bb5d2012b00f59d on paescuj:small-fixes into d03232186f2b198f974b1c7a5186e13eac1154d3 on open-cli-tools:main.


lnrpc: add optional labels to on chain transactions

This PR adds optional user provided labels to sends initiated via lnrpc/lncli, as described in #2597.
As is, other subsystems that use the same wallet endpoints simply send empty labels. A potential followup for this PR would be to set generic labels for lnd-published txns.
This PR depends on btcsuite/btcwallet#696, so it has a temporary commit which updates version to point to my fork to btcwalet which has the changes merged.
Tests TBD, just a POC to make sure the btcwallet PR has the necessary changes.

We may want to brainstorm on the labels a bit more (mostly sweeps)

Sweep labels are pretty challenging because we combine multiple outputs in a single sweep. I was originally thinking that we could label exactly what a sweep is for, but that would require having labels by tx input, which I think is beyond the scope of this field.

having that discussion be a blocker on this PR doesn't seem necessary

For the time being I could remove the sweep label and leave the others in (or the api label at the very least, since I think that's nice to include with the rpc changes) so that we can brainstorm?  Def agree that we don't want to start writing labels now which we may want to change later, so happy to pull out any labels we aren't certain of into a follow up.

I think you forgot to push @carlaKC 😛

For the time being I could remove the sweep label and leave the others in (or the api label at the very least, since I think that's nice to include with the rpc changes) so that we can brainstorm?

Maybe let's just aim for the API and user send labels for now? For open channel, we could extend it with PSBT if it was opened through that flow, for close channel, we could extend it with whether the close was initiated by the user or not, etc. I'm not sure how useful these extensions would be though.

I think you forgot to push @carlaKC 😛

🤦♀ many prs named label right now, pushed the wrong one.

Maybe let's just aim for the API and user send labels for now?
I'm not sure how useful these extensions would be though.

No harm in taking more time to think about them, will go ahead with just the External label for now.

we really want tx-input labels

Should be addressed by #4157, not quite per tx input labels, but gives us a list of eech on chain resolution per channel which can then be matched with th e output form GetTransactions

is the plan to do a follow up with the subsystem labels or do it all in one go? either way is fine by me

@wpaulino pointed out that we might want to think more carefully about the labels we use for other sybsystems, so I'll add other labels in a follow up.  Some labels like JusticeTx probably won't change much, but no harm in thinking about them all a bit more.

Can be rebased now that the dependent PR has been merged.

@carlaKC looks good, just needs a rebase!

@carlaKC looks good, just needs a rebase!

Rebased ⚾
Actions failures unrelated, but looking into a fix.


Charba and Internet Explorer (11)

Hi *!
I have to support aged browsers :( !
Now I have the problem, that IE 11 doesn't show our GWT webpage ... when I disable all the Charba stuff, UI is shown!
I've found this (old) help: https://github.com/pepstock-org/Charba/issues/29
Adding polyfill, or corejs.js ... doesn't solve my problems! The webpage is still not shown correctly.
Is there still a way to support Charba / Charts in IE11 or at least load page :)
I use the Charba tables in Ui:Binder and I think this is the problem when the page is loaded, the source will create error and won't show up!
Any solutions? Or just handle the IE stuff in source (just inject charba and add Tables to DOM when !IE)
Thank you,
Martin

@MartinSchwarzbauer Unfortunately Charba dropped the support of IE11 from version 4.0 because the support has been dropped by CHART.jS in version 3 as well. For some capabilities, polyfill can be helpful but not for CHART.JS. I think it could be better to remove polyfill doc part because could be misleading.

Ok thank you very much for your answer!

@MartinSchwarzbauer apologize... :(


feat: initial Spectral integration

Initial integration of Spectral into the IBM Validator.
Changes:

Spectral is now ran as part of the validator execution. Any results found through spectral are then merged with the results found through the IBM Validator.
A default Spectral ruleset .defaultsForSpectral.json was created and includes all the Spectral rules for Swagger/OAS3 that are recommended by default, and don't overlap with any of the Validator's rules. Any future rules can be easily added from this file.
Added logic for Spectral to use a .spectral.json file if it's found in the cwd to give users the ability to specify their own custom Spectral ruleset.
Added several unit tests to ensure none of the enabled Spectral rules overlap with our validator's rules.
Fixed minor typo in an existing rule: securitySchemas -> securitySchemes

Given that the results from Spectral are just "fed in" to the validator, and the current validator logic handles the logic from there, I did not find any issues running any of the validator's cmd line options with this new integration.

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

I realized that I missed updating the code to also include Spectral in api invocations of the validator. I'll submit some changes soon to make sure that's accounted for.

@mkistler @dpopp07 this is ready for re-review

@mkistler I just pushed a commit to change the default ruleset to yml, and allow for custom ruleset files to be either yml or json.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update Cargo.toml minor fix for repository

I am building the Rust Digger to catch similar "low hanging fruits" improvements. There is a page that will list your crates as you upload more. I hope this will be useful.


Let markewaite adopt scp plugin to deprecate it

Let markewaite adopt scp plugin to deprecate it
The scp plugin was last released 13 years ago.  The last commit with any code change was almost 10 years ago.
There are two open security vulnerabilities.  The plain text credentials storage security vulnerability was published over 5 years ago.  The CSRF security vulnerability was published 18 months ago.
The last successful build on ci.jenkins.io was over 3 years ago.  The plugin does not build currently.
The scp command is available on all the operating systems that Jenkins supports.  Unix variants include scp with the OpenSSH commands.  Windows includes scp with their port of OpenSSH.
The installation counts of the plugin have decreased over the last 12 months.  Let's deprecate it as one more indicator for users that they should switch to more portable ways of performing scp.  Deprecation does not prevent users from installing it, but gives them another reason to consider removing the plugin from their installation.
Any one of those concerns would not be enough to justify deprecation of the plugin, but considering them all together, I think the plugin should be deprecated.
Link to GitHub repository
https://github.com/jenkinsci/scp-plugin/tree/master
When modifying release permission
If you are modifying the release permission of your plugin or component, fill out the following checklist:

### Release permission checklist (for submitters)
- [x] The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to [accounts.jenkins.io](https://accounts.jenkins.io/).
- [x] All users added have logged in to [Artifactory](https://repo.jenkins-ci.org/) and [Jira](https://issues.jenkins.io/) once.

### Reviewer checklist
- [ ] Check that the `$pluginId Developers` team has `Admin` permissions while granting the access.
- [ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
- [ ] If security contacts are changed (this includes add/remove), ping the security officer (currently `@Wadeck`) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it.

@gounthar and I skipped this plugin while working through the Java 21 upgrades, because it does not build on the primary branch and has not been updated in many years.
I encountered it again while checking the top 250 most popular plugins with Artifactory configuration changes:

https://github.com/jenkins-infra/helpdesk/issues/3842

Deprecating the plugin does not remove it from distribution, but it makes it clear that no one is maintaining it.  Deprecation persuades some users to remove it from their systems.

Is it necessary to adopt the plugin in order to deprecate it? I thought the only action item was to file an update-center2 PR with the deprecation, but I could be wrong.

The deprecating a plugin documentation says

Set a deprecated label for the plugin that will be visible on plugins.jenkins.io and in the Jenkins plugin manager. This can be done in two ways:

Put a deprecated topic in the plugin’s GitHub repository. If you have multiple plugins inside a single repository, it will apply to all of them. This is the preferred approach.

Add a deprecated label to the plugin entry in the Update Center’s label-definitions.properties file. Choose this approach if the GitHub repository contains multiple plugins and only some of the plugins in the repository are to be deprecated.

Update the plugin’s documentation to explain the reason of the deprecation.

Since the preferred path is to assign a topic on the repository, adopting the plugin seemed like the easiest way to do that.

Interesting, that documentation seems suspect to me because applying the topic doesn't allow one to add a URL linking to the cause. I think it makes more sense to do this in update-center2 where a URL can be provided explaining the cause of the deprecation. Examples:

https://github.com/jenkins-infra/update-center2/pull/735
https://github.com/jenkins-infra/update-center2/pull/729
https://github.com/jenkins-infra/update-center2/pull/719

Approved anyway, given your proposed README changes, it's good to reflect the deprecation state in the README too.


[Request - Product] :leaves: Fairphone :repeat:

:grey_question:  Full and short name of product

Long name: [Fairphone | The phone that cares for people and planet](https://www.fairphone.com/en/)
Full name: Fairphone
Short name: fairphone

:hourglass_flowing_sand:  Does this product have LTS versions?

No.

What are the intervals between each LTS version?**

Many years.
:link:  What is the website for the product and for its version information?

Official website
Wikipedia

:bookmark: Related content

https://github.com/simple-icons/simple-icons/issues/8262
Fairphone and Open Source
Open Source in Environmental Sustainability
:octocat: open-source-in-environmental-sustainability

Additional context

:point_right: Just dropped a dedicated PR :

https://github.com/endoflife-date/endoflife.date/pull/2339

I'll make some social enginering around that :100:

:memo: https://dev.to/adriens/fairphone-on-endoflifedate-g01 :gift:


atproto-goat: 0-unstable-2024-10-08 -> 0-unstable-2024-10-29

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for atproto-goat is: Go AT protocol CLI tool
meta.homepage for atproto-goat is: https://github.com/bluesky-social/indigo/blob/main/cmd/goat/README.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0-unstable-2024-10-29 with grep in /nix/store/f9myyqjk0s75s4n7szi3h5ja5nlmvfm4-atproto-goat-0-unstable-2024-10-29
found 0-unstable-2024-10-29 in filename of file in /nix/store/f9myyqjk0s75s4n7szi3h5ja5nlmvfm4-atproto-goat-0-unstable-2024-10-29

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

atproto-goat

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f9myyqjk0s75s4n7szi3h5ja5nlmvfm4-atproto-goat-0-unstable-2024-10-29 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A atproto-goat https://github.com/r-ryantm/nixpkgs/archive/cbf90379d11f7f535fda6c7a8f6c442cf3dd1418.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cbf90379d11f7f535fda6c7a8f6c442cf3dd1418#atproto-goat

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/f9myyqjk0s75s4n7szi3h5ja5nlmvfm4-atproto-goat-0-unstable-2024-10-29
ls -la /nix/store/f9myyqjk0s75s4n7szi3h5ja5nlmvfm4-atproto-goat-0-unstable-2024-10-29/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

atproto-goat

Maintainer pings
cc @pyrox0 for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Is there a suggested order to explore docs/notebooks/? Perhaps not...

https://github.com/vitessce/vitessce-python/blob/master/docs/widget_examples.rst determines the listing order for the notebooks in the generated documentation... but if there's a definite order a new user should look at these, should that be captured in the README.md? Or maybe the filenames could be numbered, so a jupyter user could just go down the list?
Somewhat related: How does the Jupyter user download the prerequisite data? #76

I think the numbering of the files is a good idea


Exponential Search in Java

🚀 Feature
Exponential Search algorithm injava
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
Exponential search is also known as doubling or galloping search. This mechanism is used to find the range where the search key may present.
Pitch
It uses the binary search technique to find the exact location of the search key. The searching process becomes faster.

@shraddhavp Please assign me this issue. I am a participant in DWOC.

May I go ahead with cpp for DWOC ?
@shraddhavp

yes @Sarthak-9  go ahead in cpp and @sakshikhachane  go ahead in java

yes @Sarthak-9  go ahead in cpp and @sakshikhachane  go ahead in java

@shraddhavp Please add the levels for this issue else it won't get counted.

@shraddhavp Please add the levels for this issue else it won't get counted.

@shraddhavp Please add a level label to this issue and PR as it isn't getting counted on the leaderboard.

@shraddhavp Please add a level label to this issue and PR as it isn't getting counted on the leaderboard.


Generalize Task.sequence for arbitrary collections

Task.sequence takes Seq[Task[A]] and gives back Task[List[A]], which might not be desirable in all cases.
Generalizing it as def sequence[A, M[X] <: TraversableOnce[X]: CanBuildFrom](xs: M[Task[A]]): Task[M[A]] would be helpful, as well as adding traverse: M[A] => (A => Task[B]) => Task[M[A]] in the same way.

I don't dislike the idea. I'm generally fearful of CanBuildFrom, but it's indeed useful.
But if we do this, then gather and gatherUnordered and zipList also need it, for consistency.

You're right. Then should be keep zipList, although it doesn't always produce a list? I'd suggest just dropping it IMHO, because it's just an alias and the word 'zip' is sometimes confusing.

Yes, we can still drop it.

@guersam also Coeval.sequence :-)

Note - I think zipList should not ne removed after all. And signature should stay the same. This is for consistency with Observable (I remembered the reason for why it's there :-))

I mean, on Observablr the zip operation is not like map2 or mapBoth. And zipList makes sense for Observable, whereas sequence and gather do not.

Ok, then how about making Task.zipList receive a vararg as the same as Observable.zipList?
Rewriting gatherUnordered using mutable builder brings a lock which might not be desirable. It seems fine to keep it unchanged by itself, but it causes signature inconsistency between gather and gatherUnordered. We need to choose between more flexible gather and consistency between similar functions. What do you prefer?

I agree.
I did some benchmarks lately and using Atomic is cool, but combining Atomic with persistent data-structures (like Vector) destroys performance as Vector is terrible - it's non-blocking, sure, but the performance loss isn't worth it. Just work with synchronize and make the signatures similar.

As the order doesn't matter, how about replacing Vector with List? Prepending to a list is significantly faster than appending to a vector. Then we can convert the final list to the desired container using CanBuildFrom or not.
In this case, it would be better to find another way to determine the end of computation not relying on .length, which takes O(n) on lists.

@guersam sorry for the late response, I'm caught up with other things and have high latency these days.
I do not want us to use another chunk of O(n) memory at the end, just to convert to a desired type. So we have two choices:

we synchronize on the CanBuildFrom builder
we use a List and return it just as it is - which means that results will happen mostly in reverse order, with non-deterministic variations of course - but given that this is gatherUnordered we are talking about, I think that's totally fine

Frankly, I'd go with number 2. This is because people would use gatherUnordered for performance reasons. And we could keep the Atomic which is cool for the non-blocking behavior. But then I'd do a benchmark to validate the assumption that number 2 is better or at least on par with number 1, because the last benchmark I did left me with a sour taste about using persistent vectors in atomic refs. In the benchmarks subproject you already have the setup and it's easy to try it out.

Btw - if you want to work on this, don't wait for me to approve - like do something, submit a PR and then we can also talk on the PR. When you've got time of course.

@guersam - I want to release this as part of release 2.0. Do you have time to work on it?

I've modified the code itself, but additional tests and docs are not done yet. Will open a PR soon with current changes to discuss remains.

should this be close?

Oh, it wasn't automatically closed... thanks for pointing it out.

@guersam @hepin1989 yes, it's deployed in 2.0.0, thanks.


two or more classes in one file | running in flipped order is working

executing this will throw error: error: can't find main(String[]) method in class: egzamin.GenericClass
/run java
package egzamin;

class GenericClass<T> {

     private final T pole;

     public GenericClass(T pole) {
          this.pole = pole;
     }

     public Class getMyType() {
         return this.pole.getClass();
     }
}

public class Main {
    public static void main(String [] args){
       GenericClass<Main> ala = new GenericClass<>(new Main());
       System.out.println(ala.getMyType());
    }
}

but executing in rotated order is working
/run java
package egzamin;

public class Main {
    public static void main(String [] args){
       GenericClass<Main> ala = new GenericClass<>(new Main());
       System.out.println(ala.getMyType());
    }
}

class GenericClass<T> {

     private final T pole;

     public GenericClass(T pole) {
          this.pole = pole;
     }

     public Class getMyType() {
         return this.pole.getClass();
     }
}

I think that bot is searching first class and executing its main, I think it should first search main class if not found then it should search main function in first found class.

This isn't the bot's fault, it's Java being Java. We simply can't know which class contains the main function, so we find the first class and run it.

https://github.com/engineer-man/piston/blob/c0b218f47791117867feb4e5bb53eef6a4e67e9e/packages/java/15.0.2/run#L7
We simply call java, so we can't fix this ourselves.


[core] Normalize the API

Reduce degree of freedom of the API with the color property. That's a tradeoff between correctness and verbosity.
People should be able to recover from that breaking change quite easily as react is going to throw warnings.
Transform all the classes to be camelCase (consistency)
Use @owencm trick with double RAF to fix an animation issue with Chrome v59
Fix animation with the older browsers like iOS 8.
Add new tests to the Chip.

I'm on board with the changes in principal, and gave it a quick scan.  Too many changed files to review it thoroughly! 😆


Fix custom ratelimit

Purpose
Fixes https://github.com/wso2/apk/issues/1109
Fixes https://github.com/wso2/apk/issues/1116 -
fixes the sample.
Also, added the org-level check and implementation in the gateway
Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

Codecov Report
Patch coverage has no change and project coverage change: -7.35 :warning:

Comparison is base (efa3770) 34.09% compared to head (b1f8990) 26.75%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1117      +/-   ##
==========================================
- Coverage   34.09%   26.75%   -7.35%
==========================================
  Files         352       49     -303
  Lines       39048     8810   -30238
  Branches    12196        0   -12196
==========================================
- Hits        13314     2357   -10957
+ Misses      25494     6333   -19161
+ Partials      240      120     -120

Flag
Coverage Δ

adapter
26.75% <ø> (-0.04%)
:arrow_down:

admin-domain-service
?

backoffice-domain-service
?

devportal-domain-service
?

idp-domain-service
?

router
?

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 305 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


pacmod_game_control: 2.2.0-0 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository pacmod_game_control to 2.2.0-0:

upstream repository: https://github.com/astuff/pacmod_game_control.git
release repository: https://github.com/astuff/pacmod_game_control-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.6
previous version for package: 2.1.0-1

pacmod_game_control
* Merge pull request #44 <https://github.com/astuff/pacmod_game_control/issues/44> from astuff/feat/lexus_braking_curve
* 0.625 and 6.25 are not the same value
* Added cubic braking curve
* Merge pull request #43 <https://github.com/astuff/pacmod_game_control/issues/43> from astuff/feat/multiple_button_enable
* Press start AND select to enable
* Merge pull request #42 <https://github.com/astuff/pacmod_game_control/issues/42> from astuff/fix/resume_control_after_estop
* Changing pacmod_enable flag after return form e-stop
* Contributors: Joshua Whitley, Kyle Rector, Sam Rustan, Zach Oakes

(waiting on sync https://discourse.ros.org/t/preparing-for-melodic-sync-2018-09-04/5919)


My container disappeared?

I don't know what happened, just for whatever reason I clicked and dragged on a backpack in my character sheet, and it plus all the items in it disappeared entirely.  I was able to recreate it with another container, and it seemed like it had something to do with dragging the backpack onto the Container bar? I can't recreate it consistently though, but we checked every character sheet and those bags didn't go anywhere.

Try updating your system install. There was an issue (#12638) a month ago concerning this.


DivideByZeroException in bark_load_model when calling ggml_time_us()

When calling bark_load_model from the C# BarkSharp wrapper, a System.DivideByZeroException is thrown at the line int64_t t_load_start_us = ggml_time_us();. This seems to indicate that the ggml_time_us() function is attempting to divide by zero, likely because the timer_freq variable has not been properly initialized.
Inserting a call to ggml_time_init() at the beginning of bark_load_model to initialize the timer leads to a StackOverflowException during the allocation of memory with ggml_allocr_new_from_buffer. This suggests a potential issue with memory management or initialization within the GGML library.
Reproduction Steps:

Build the Bark library: Ensure that the Bark library (including GGML) is built successfully.
Create a C# project: Create a C# project that uses the BarkSharp wrapper to interact with the Bark library.
Load the Bark model: Attempt to load the Bark model using the BarkContext class constructor, providing the path to the model file.

Example Code (Relevant C# snippets):
// BarkContext.cs
public BarkContext(string modelPath, BarkContextParams parameters, uint seed)
{
    var modelPathPtr = Marshal.StringToHGlobalAnsi(modelPath);
    _context = LoadModel(modelPathPtr , parameters, seed); // This call eventually leads to the exception
    // ...
}

// NativeMethods.cs
[DllImport(NativeLibraryManager.LibraryName, EntryPoint = "bark_load_model", CallingConvention = CallingConvention.Cdecl, CharSet = CharSet.Unicode)]
public static extern IntPtr LoadModel(IntPtr modelPath, BarkContextParams parameters, uint seed);

Relevant C++ Code (bark.cpp):
struct bark_context* bark_load_model(const char* model_path, struct bark_context_params params, uint32_t seed) {
    int64_t t_load_start_us = ggml_time_us(); // Exception occurs here

    struct bark_context* bctx = new bark_context();

    bctx->text_model = bark_model();
    std::string model_path_str(model_path);
    if (!bark_load_model_from_file(model_path_str, bctx, params.verbosity)) {
        fprintf(stderr, "%s: failed to load model weights from '%s'\n", __func__, model_path);
        return nullptr;
    }

    bctx->rng = std::mt19937(seed);
    bctx->params = params;
    bctx->stats.t_load_us = ggml_time_us() - t_load_start_us;

    return bctx;
}

Relevant C++ Code (ggml.c):
int64_t ggml_time_us(void) {
    LARGE_INTEGER t;
    QueryPerformanceCounter(&t);
    return ((t.QuadPart - timer_start) * 1000000) / timer_freq; // Potential division by zero
}

void ggml_time_init(void) {
    LARGE_INTEGER frequency;
    QueryPerformanceFrequency(&frequency);
    timer_freq = frequency.QuadPart;
    QueryPerformanceCounter(&timer_start);
}

Expected Behavior:
The bark_load_model function should load the model successfully without throwing any exceptions. The ggml_time_us() function should return a valid timestamp.
Actual Behavior:
A System.DivideByZeroException is thrown when calling ggml_time_us(). Attempting to fix this by calling ggml_time_init() at the beginning of bark_load_model results in a StackOverflowException during memory allocation.
Possible Causes:

Missing timer initialization: The timer_freq variable in ggml_time_us() might not be initialized properly before it is used, leading to the division by zero error.
Circular dependency or recursive call: The StackOverflowException when calling ggml_time_init() might indicate a circular dependency or a recursive function call that exceeds the stack limit.
Memory allocation issues: There might be problems with memory allocation or initialization within GGML, leading to the stack overflow during the creation of the allocator.

I had exactly the same error when using the dll in a python binding. The stack overflow problem is not due to too many calls to ggml_time_init, but instead the calling stack of bark_load_model or generate_audio can easily exceed the 1MB stack size limit on Windows.
My fix to the problem is to manually increase the stack size limit before making calls to dll APIs
something like
threading.stack_size(16*1024*1024)  # set stack size to 16MB

# then spawn a new thread and make calls to ctypes to the dll APIs

Thanks for your assistance, @vinovo The library is now operating and the StackOverflowException has been addressed. The only left issue is that C#'s default stack size of 1MB is fixed and cannot be changed on the Main Thread I am currently using background threads workaround for now. I am using llama.cpp and stable-diffusion.cpp both in the main thread without requiring a stack size change, though I suppose this could be connected to the out-of-date ggml.
@PABannier My apologies, I missed the ggml_time_init(); call in the main C++ example when I was porting it to C# and after encountering StackOverflowException I thought it was wrong workaround.  It would be great to align the ggml dependency with the upstream version this may fix the stack related issues.  Also, since bark_load_model serves as the library's entry point, could we consider moving the ggml_time_init(); call into it? This would prevent users from needing to interact directly with the low-level ggml code and make the library more user-friendly. It would streamline the process by initializing ggml timing within bark_load_model instead of requiring it in higher-level functions like Main();.
And since this issue got addressed, I am going to close it.

@LSXAxeller Thanks for the update and closing the issue!
I agree we can move the ggml_time_init() call into the bark_load_model function. I let you open a PR for that.
Regarding syncing with ggml upstream, I'm in the process of doing so. I'm almost done adapting the Encodec.cpp codebase with the latest ggml version, which bark.cpp relies on. I should be done in a few days.

Sorry for my late response, I opened PR #203 to call ggml_time_init() before int64_t t_load_start_us = ggml_time_us(); in bark_load_model(const char* model_path, struct bark_context_params params, uint32_t seed) function


compression_ratio_bug

Describe the bug
Conversion from config.compression_ratio to the number of columns is wrong
To Reproduce
Running example_CMS with a compression ratio of 1.6 should give a latent space with 15 columns, but actually gives 14
Additional context
This is caused by machine precision in calculating int(24//1.6)

Instead of floor division (a//b), propose we use ceil division (ceil(a/b)
Pull Request - https://github.com/baler-collaboration/baler/pull/263


change level from avg to high for dedicated-admin service trigger

@wanghaoran1988 has +1 on #4005


Code for flash messages

Add jinja code in the layout file to address flash messages that the controller function send along with the templates

Done...has been discussed with @ChiragSaxena5437 .


ISPN-7728 Run stress tests serially

https://issues.jboss.org/browse/ISPN-7728
https://issues.jboss.org/browse/ISPN-7730

Pushed to master


Does not render in Internet Explorer 11

Hello there,
Is there some particular reason why Material Dashboard React does not render in Internet Explorer 11 and just gives info that JavaScript needs to be enabled - even if IT IS enabled?
Thank you,
Pawel

Hello @pskorupinski ,
Thank you for your interest in using our product.
As of moment i am on a small vacation (this week until Saturday) when i'll get home, i'll see if on my PC - Windows - IE 11 the dashboard works. Meanwhile i will ask a friend to take a look at this and maybe he will be able to help you.
Best,
Manu

Hi @EINazare - some update on this?
I have noticed that https://demos.creative-tim.com/material-dashboard-pro-react/#/dashboard loads in IE but https://demos.creative-tim.com/material-dashboard-react/#/dashboard does not.
I have my project based on material-dashboard-pro-react but the behaviour is the same as of non-pro version (does not render). Any idea?


feat(connectCurrentRefinements): add a root label (PART 1)

Summary

The reason why you'd want a key like this is if you e.g. want to rename a single key or transform all keys to be upper case, without actually changing which attribute will be changed.
Result

A new root key label, this will always be identical to the attribute, and will be the thing which will be displayed.

We need to update the documentation.


Fix ownership of files in work

Files in data are just fine, but the temporary files in work belong to root – which is quite annoying. Maybe I need to specify these as proper (dynamic) output files, for Nextflow's fixOwnership to properly work? Alternatively, delete unneeded files and oly keep (and specify as output) essential output files?

https://www.nextflow.io/docs/latest/process.html#multiple-output-files
https://docs.oracle.com/javase/tutorial/essential/io/fileOps.html#glob

Huge PITA, but it's fixed. I no longer use the checkm-genome BioContainer, but a slightly modified version: https://hub.docker.com/r/abremges/checkm-genome/


Release 0.8.2

Released via https://github.com/r2dbc/r2dbc-spi/commit/d01166ab9a6ead3f628adb84bb968ea322086055.


[SQL][Minor] fix java doc for DataFrame.agg

Jenkins, test this please.

Can one of the admins verify this patch?

Jenkins, test this please.

Jenkins, test this please.

Merged build triggered.

Merged build started.

Test build #31260 has started for   PR 5712 at commit be23064.

Test build #31260 has finished for   PR 5712 at commit be23064.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/31260/
Test PASSed.

Thanks. Merging in master.


yo [generator-name] --help does not list subgenerators for a specific generator

Hi,
I have read that : yo --helpgive the list of subgenerators, It's working for me.
But I want the subgenerator for a specific generator not all the generators installed.
Something like yo my-generator --help.
Did I missed something ?
PS: Great job ;)

That is already a thing. What generator is it not working for?

It's on a custom generator, have you a link to the documentation to implement this in my custom generator ?

See http://yeoman.io/authoring/index.html

When i do
yo --help
I see all the subgenerators availables:
  angular
    common
    constant
    controller
    decorator
    directive
    factory
    filter
    main
    provider
    route
    service
    value
    view
  karma

Then I try for a specific generator :
 yo angular --help
And I have this result :
Usage:
  yo angular:app [options] [<appname>]

Options:
  -h,   --help                # Print generator's options and usage                   Default: false
        --app-suffix          # Allow a custom suffix to be added to the module name  Default: false
        --appPath             # Allow to choose where to write the files              Default: false
        --coffee              # Generate CoffeeScript instead of JavaScript           Default: false
        --angular:common      # Angular:common to be invoked                          Default:
        --angular:main        # Angular:main to be invoked                            Default:
        --angular:controller  # Angular:controller to be invoked                      Default:

Arguments:
  appname  # Type: String  Required: false

        --angular:common      # Angular:common to be invoked                          Default:
        --angular:main        # Angular:main to be invoked                            Default:
        --angular:controller  # Angular:controller to be invoked                      Default:

You have that list. The others aren't there because the generator needs to be updated

@eddiemonge I just installed a fresh version of generator-angular and I'm seeing the same issue. I checked the repo to find that all of the sub-generators are listed in the package.json under files, so I'm not understanding why only common, main and controller are showing when I run yo angular --help.
You say the generator needs to be updated. What, exactly, in the generator needs to be updated?


Implement JOIN ... USING query

Fixes #730

To implement JOIN ... USING, I added a new type argument to JoinBuilder, C extends string, representing the column names which are common to both tables being joined.
I see that JoinBuilder is also used for the MERGE query. Consequently this PR allows for a MERGE syntax which is not valid in Postgres and probably not valid on any DBMS:
// merge into person using pet using (id)
db.mergeInto('person').using('pet', (join) => join.using(['id']))

There are a couple ways to solve that (if maintainers here think it's worth solving):

Create a SelectJoinBuilder which extends JoinBuilder and adds the using function. Use SelectJoinBuilder for SELECT queries and use JoinBuilder for MERGE queries
MERGE queries could assign C = never as the type param to JoinBuilder

To implement JOIN ... USING, I added a new type argument to JoinBuilder, C extends string, representing the column names which are common to both tables being joined.

Sounds like it's not crucial and could've been placed on the method/s. We're usually quite conservative when it comes to adding more generic parameters to existing builders. There has to be a good reason..

I see that JoinBuilder is also used for the MERGE query. Consequently this PR allows for a MERGE syntax which is not valid in Postgres and probably not valid on any DBMS:
// merge into person using pet using (id)
db.mergeInto('person').using('pet', (join) => join.using(['id']))

There are a couple ways to solve that (if maintainers here think it's worth solving):

Create a SelectJoinBuilder which extends JoinBuilder and adds the using function. Use SelectJoinBuilder for SELECT queries and use JoinBuilder for MERGE queries
MERGE queries could assign C = never as the type param to JoinBuilder

That's fine for now, not worth the extra builder/s IMHO.

@dwickern Hope you have time to finish the pull request and insure that it gets merged. Since it is a very nice feature and very nice work.


NOTICE: Upcoming style change -- no more AoTs

When https://github.com/toml-lang/toml/pull/904 goes into a TOML spec release I plan to tweak Tomli-W's formatting by reverting the changes that make it write "arrays of tables", starting with PR https://github.com/hukkin/tomli-w/pull/15. Instead I plan to write "multi line inline tables" when there is a table within an array.
This should:

simplify the code
reduce inspection of input data, increasing performance
result in style that is easier to understand
avoid non-uniform input reported here https://github.com/hukkin/tomli-w/issues/35#issuecomment-1115917928

Note to self: Consider https://github.com/hukkin/tomli-w/issues/25 for both arrays and inline tables together with this change.


Push JSON STIX to opentaxii server

Can anyone point me to an example of how to push a JSON STIX object to an opentaxii server, for example by using the cabby client or by another method?

Cabby's default examples should work just fine. OpenTAXII is content agnostic, so you should be fine. Please post what you have tried so far and what the errors were.

@arcsector that examples link no longer works, i've looked at the cabby github and see no examples. Do you have any other suggestions?

@lcia-projects try this link: https://cabby.readthedocs.io/en/latest/user.html#using-cabby-as-a-command-line-tool


Consistently handle due time for III day loans to avoid duedate earlier outdate error

[Moved from https://github.com/FOLIO-FSE/service_tools/issues/15)
Sierra and Millennium don't export due times.
item_barcode	out_date	due_date	renewal_count	status	patron_barcode	next_item_status
789	2019-02-22 10:53:00	2019-02-22	0	n	1234

Parsing the dates as datetime typically translates that to 00:00:00, which for 1-day-loans results in a duedate earlier than outdate error.
item_barcode	out_date	due_date	renewal_count	status	patron_barcode	next_item_status
789	2019-02-22 10:53:00	2019-02-22 00:00:00	0	n	1234

Should we be setting all due times to 23:59:59PM (for III and other libraries that don't provide one) to avoid this?

@branchedelac  could you check https://github.com/FOLIO-FSE/folio_migration_tools/commit/fcd8fad745d3d37e242f6b9282e3ab48eac9cde5#diff-6276fd63df8b1563f60b13aa05727af12188396505613c9a8a953311dcd34728 to see if the test covers your use case?

Actually it does not. I am adding a new test case.

Now this case is covered as well


Error on install

Describe the bug
I run >composer require binarytorch/larecipe and all is fine
Then when I run >php artisan larecipe:install I get the following error:
Publishing assets and congigurations.. 🍪
Copied Directory [\vendor\binarytorch\larecipe\publishable\assets] To [\public\vendor\binarytorch\larecipe\assets]
Copied File [\vendor\binarytorch\larecipe\publishable\config\larecipe.php] To [\config\larecipe.php]
Copied Directory [\vendor\binarytorch\larecipe\resources\views\partials] To [\resources\views\vendor\larecipe\partials]
Publishing complete.
Setup initial documentations structure under .. 🍪
ErrorException
implode(): Invalid arguments passed
at C:\pmms\vendor\binarytorch\larecipe\src\Commands\GenerateDocumentationCommand.php:52
48|     public function handle()
49|     {
50|         $publishedVersions = config('larecipe.versions.published');
51|

52|         $this->info('Reading all docs versions, found: '.implode(',', $publishedVersions));
53|         foreach ($publishedVersions as $version) {
54|             $versionDirectory = config('larecipe.docs.path').'/'.$version;
55|
56|             $this->line('');

1   C:\pmms\vendor\binarytorch\larecipe\src\Commands\GenerateDocumentationCommand.php:52
implode(",")
2   C:\pmms\vendor\laravel\framework\src\Illuminate\Container\BoundMethod.php:33
BinaryTorch\LaRecipe\Commands\GenerateDocumentationCommand::handle()

Getting this also. Any fix or workaround?

For me, i had to run a php artisan config:cache
When debugging, i found that the GenerateDocumentationCommand was returning null for the
$publishedVersions = config('larecipe.versions.published');
When testing with other config files, arrays were returned. Working for me now, so might need to be tested further.

Thank you, Stephenstack. That did it. I had seen the same thing, that the published versions was returning null. Clearing and rebuilding the config cache fixed it for me too.


IconPicker does not work in ListViewCommandSet

Category
[ ] Enhancement
[x ] Bug
[ ] Question
Version
Please specify what version of the library you are using: [ 3.10.0 ]
Here are the dependencies from the package.json:
"dependencies": {
    "@microsoft/decorators": "1.13.1",
<EMAIL_ADDRESS>"^0.10.47",
    "@microsoft/sp-application-base": "1.13.1",
    "@microsoft/sp-core-library": "1.13.1",
    "@microsoft/sp-dialog": "1.13.1",
    "@microsoft/sp-listview-extensibility": "1.13.1",
    "@pnp/common": "^2.11.0",
    "@pnp/logging": "^2.11.0",
    "@pnp/odata": "^2.11.0",
    "@pnp/sp": "^2.11.0",
    "@pnp/spfx-controls-react": "3.10.0",
    "node-sass": "^4.14.0",
    "office-ui-fabric-react": "^7.180.3"
  }

Expected / Desired Behavior / Question
The IconPicker should open up when clicking the Button of the CommandSet.
Observed Behavior
From my console output I can see that the render method of my component with the IconPicker gets called, but the dialog does not come up.

Steps to Reproduce
Create a  SPFx Extension of type ListViewCommandSet
Create code for OnExcecute like this:
  @override
  public onExecute(event: IListViewCommandSetExecuteEventParameters): void {
    if(event.itemId === CommandNames.AssignSvg) {
      const selectedRow: RowAccessor = event.selectedRows[0];
      const id: string = selectedRow.getValueByName('ID');
      const div = document.createElement('div');

      console.log("Open CContainer.");
      const element: React.ReactElement<IPickerDialogContentProps> = React.createElement(
        CContainer,
        {
          listItemID: Number(id),
          message: "Icon auswählen",
          save: this._save
        }
      );
      ReactDOM.render(element, div);
    }
    else {
      throw new Error(`Unknown command ${event.itemId}`);
    }
  }

Add a class to hold an IconPicker:
import * as React from "react";
import IPickerDialogContentProps from "./IPickerDialogContentProps";
import { IconPicker } from '@pnp/spfx-controls-react/lib/IconPicker';

export default class CContainer extends React.Component<IPickerDialogContentProps, {}> {
    constructor(props: IPickerDialogContentProps) {
      super(props);
    }

    public render(): React.ReactElement<IPickerDialogContentProps> {
     console.log("render entring in CContainer.");
    return (<IconPicker
	renderOption="dialog"
	onSave={(value) => { this.props.save(value, this.props.listItemID); }}
	buttonLabel={ this.props.message }>
     </IconPicker>);
    }
  }

My props interface looks like this:
export default interface IPickerDialogContentProps {
    message: string;
    listItemID: number;
    save: (iconName: string, listItemID: number) => void;
  }

If I add a Panel instead of the IconPicker, my code is working:
public render(): React.ReactElement<IPickerDialogContentProps> {
      console.log("render entring in CContainer.");
      return ( <Panel isOpen={true}>

This is a custom panel with your own content

        <TextField value="Hello World" label="Item title" placeholder="Choose the new title" />
        <DialogFooter>
            <DefaultButton text="Cancel" />
            <PrimaryButton text="Save" />
        </DialogFooter>
    </Panel>);
    }

Please note: The IconPicker is calling initializeIcons(), but this method has been already called by the AllItems.aspx of my list (as far as I know). The console warning: Redefining what an icon is may have unintended consequences.
So it looks like the IconPicker cannot be used in a CommandSet, because of a bug.

Nobody?

Hi @EA12,
The "problem" with this control is that the icons list relies on a ready-to-use button and nothing else and there's no prop to handle the panel / dialog display.
Even if this could be an improvment idea (to have a new prop to display the icons list without a button), below a workaround that could fit your specific need for a Listview Command Set, using React ref.
Pay attention that the example is using an "any" ref, in order to trigger a private onClick event of the control. But this is not a recommanded approach (maybe you found another workaround, it's been almost a year).

ListViewCommandSet.ts

// ...
public onExecute(event: IListViewCommandSetExecuteEventParameters): void {
    console.log(event);
    switch (event.itemId) {
      case 'COMMAND_1':
        this._renderDialogContainer(true);
        break;
      default:
        throw new Error('Unknown command');
    }
  }

private _renderDialogContainer(isDialogDisplayed: boolean): void {
    const element: React.ReactElement<unknown> = React.createElement(
      IconPickerDialog,
      {
        context: this.context,
        displayDialog: isDialogDisplayed,
        closeDialog: this._closeDialogContainer
      }
    );

    ReactDom.render(element, this.dialogContainer);
  }

  private _closeDialogContainer = (): void => {
    this._renderDialogContainer(false);
  }

IconPickerDialog.tsx

import * as React from 'react';
import { IconPicker } from '@pnp/spfx-controls-react/lib/controls/iconPicker/IconPicker';

export interface IIconPickerDialogProps {
    displayDialog: boolean;
    closeDialog: () => void;
}

export default class IconPickerDialog extends React.Component<IIconPickerDialogProps, {}> {

    // eslint-disable-next-line @typescript-eslint/no-explicit-any
    private myRef: any;

    constructor(props: IIconPickerDialogProps) {
        super(props);

        this.myRef = React.createRef();
    }

    public componentDidMount(): void {
        this.myRef.current.iconPickerOnClick();
    }

    public componentDidUpdate(prevProps: Readonly<IIconPickerDialogProps>, prevState: Readonly<{}>, snapshot?: any): void {
        if (prevProps.displayDialog !== this.props.displayDialog && this.props.displayDialog) {
            this.myRef.current.iconPickerOnClick();
        }
    }

    public render(): React.ReactElement<IIconPickerDialogProps> {
        return (
            <IconPicker
                ref={this.myRef}
                renderOption='dialog'
                onCancel={() => this.props.closeDialog()}
                onSave={(iconName: string) => { console.log(iconName); this.props.closeDialog() }} />
        );
    }
}

Hope that it helps.

@EA12 is this still an issue?

@michaelmaillot & @joelfmrodrigues
You can close the issue. As I couldn't find a solution, we redesigned the whole thing and there was no need anymore to assign an icon. - Thanks for your effort.


divmod

Division and Modulus Function (divmod)
The divmod function is being implemented by @HoldW.

A lot of your learning will be individually directed, with guidance. Taking a look at the #12 will give an overview of how you want to approach this.

Writing the code is one step of open source contribution
You have to make sure that your code is well documentation. See Google Style Python Docstring

Once you have ensured that your code is documentation, we can continue.


Edit Sessions tree view no longer populates when running Show Edit Sessions

git bisect points to 5ab18068041a148195b124a0ec03aa1e0a273d24, cc @alexr00

The AbstractTreeView, which is what Edit Sessions is using, is used mainly for extension provided trees. I fixed a race that can happen with extension provided trees that requires that the tree dataProvider be set before the visible event fire. It looks like internal users of AbstractTreeView like to set the dataProvider when the visible event fires, meaning that they now never set a dataProvider. I will look at another fix.

Fixed by https://github.com/microsoft/vscode/pull/166029


ParseError: PowerManagement-ManagementDomain.ps1:163 Missing closing '}' in statement block or type definition

Code of Conduct

[X] I have read and agree to the Code of Conduct.
[X] Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
[X] Do not leave "+1" or other comments that do not add relevant information or questions.
[ ] If you are interested in working on this issue or have submitted a pull request, please leave a comment.

VMware Cloud Foundation
5.1.1
PowerShell Version
Windows Powershell 7.4
PowerCLI Version
<IP_ADDRESS>45081
Module Version
<IP_ADDRESS>0
PowerVCF Version
<IP_ADDRESS>0
Guest Operating System
Windows Server 2019
Environment Details
vanilla holodeck 5.1.1 deployment
Description
Running the PowerManagement-ManagementDomain.psi script results in a PowerShell ParserError
Lines 461 and 747 contain { and are duplicate lines causing brackets to mismatch
Lines 741 and 744 also appear to be unnecessary duplicate lines
Error or Debug Output
https://gist.github.com/goodnowm/2f3f143fef8ef186633e7077846a2f11
Expected Behavior
Shutdown the management domain
Actual Behavior
PowerShell ParserError
Steps to Reproduce
Using step 6 from the Usage documentation results in a PowerShell ParserError
Log Fragments and Files
No response
Screenshots

References
No response

I came across the same issue as well and was able to overcome by adding a closing bracket on Line 165 as so:
Write-PowerManagementLogMessage -Type INFO -Message "Attempting to connect to VMware Cloud Foundation to gather system details."}
and then I inserted below on line 166 and 167 :
	Catch { 			}
After the above changes I was able to progress.