python312Packages.bx-python: 0.11.0 -> 0.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.bx-python is: Tools for manipulating biological data, particularly multiple sequence alignments
meta.homepage for python312Packages.bx-python is: https://github.com/bxlab/bx-python
meta.changelog for python312Packages.bx-python is: https://github.com/bxlab/bx-python/releases/tag/v0.12.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.12.0 with grep in /nix/store/8zn9aq52fyqmjizr68jna993r94jmpdj-python3.12-bx-python-0.12.0
found 0.12.0 in filename of file in /nix/store/8zn9aq52fyqmjizr68jna993r94jmpdj-python3.12-bx-python-0.12.0

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

hap-py
python311Packages.bx-python
python312Packages.bx-python
tebreak

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8zn9aq52fyqmjizr68jna993r94jmpdj-python3.12-bx-python-0.12.0 \
  --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 python312Packages.bx-python https://github.com/r-ryantm/nixpkgs/archive/37c12ea8ac4fc7b04b8ddaf47efd0603e2699019.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/37c12ea8ac4fc7b04b8ddaf47efd0603e2699019#python312Packages.bx-python

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8zn9aq52fyqmjizr68jna993r94jmpdj-python3.12-bx-python-0.12.0
ls -la /nix/store/8zn9aq52fyqmjizr68jna993r94jmpdj-python3.12-bx-python-0.12.0/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.
Result of nixpkgs-review run on x86_64-linux 1

7 packages built:

hap-py
python311Packages.bx-python
python311Packages.bx-python.dist
python312Packages.bx-python
python312Packages.bx-python.dist
tebreak
tebreak.dist

Maintainer pings
cc @jbedo for testing.

Should drop the nose dependency if possible.

Result of nixpkgs-review pr 332424 at 8f65c563 run on x86_64-linux 1

4 packages built successfully:

hap-py
python311Packages.bx-python
python312Packages.bx-python
tebreak

Superseded by https://github.com/NixOS/nixpkgs/pull/330744


Set filename

Before

After

Thanks! 👍

          1 Message

:book:
Hello from Hosted Danger :sunny:

  Generated by :no_entry_sign: Danger


False negative with error_on_line_overflow in Clippy source file

The issue concerns this line:
https://github.com/rust-lang/rust-clippy/blob/98c4a49db8c305c468646715b773fa9b6ec7049a/clippy_lints/src/derive.rs#L350
The line is 130 characters long, which exceeds the max_width declared in the rustfmt.toml file:
https://github.com/rust-lang/rust-clippy/blob/98c4a49db8c305c468646715b773fa9b6ec7049a/rustfmt.toml#L1
Yet none of these commands produce a change or error:
cargo fmt
rustfmt clippy_lints/src/derive.rs
cargo +nightly fmt
rustfmt +nightly clippy_lints/src/derive.rs

(Re +nightly, recall Clippy uses a rust-toolchain file.)

Thanks for reaching out. Confirming I can reproduce this with rustfmt 1.5.2-nightly (34f9ca28 2023-02-16) and the following input snippet:
fn check_copy_clone<'tcx>(cx: &LateContext<'tcx>, item: &Item<'_>, trait_ref: &hir::TraitRef<'_>, ty: Ty<'tcx>) {
    let clone_id = match cx.tcx.lang_items().clone_trait() {
        Some(id) if trait_ref.trait_def_id() == Some(id) => id,
        _ => return,
    };
    let Some(copy_id) = cx.tcx.lang_items().copy_trait() else { return };
    let (ty_adt, ty_subs) = match *ty.kind() {
        // Unions can't derive clone.
        ty::Adt(adt, subs) if !adt.is_union() => (adt, subs),
        _ => return,
    };
    // If the current self type doesn't implement Copy (due to generic constraints), search to see if
    // there's a Copy impl for any instance of the adt.
    if !is_copy(cx, ty) {
        if ty_subs.non_erasable_generics().next().is_some() {
            let has_copy_impl = cx.tcx.all_local_trait_impls(()).get(&copy_id).map_or(false, |impls| {
                impls
                    .iter()
                    .any(|&id| matches!(cx.tcx.type_of(id).subst_identity().kind(), ty::Adt(adt, _) if ty_adt.did() == adt.did()))
            });
            if !has_copy_impl {
                return;
            }
        } else {
            return;
        }
    }
    // Derive constrains all generic types to requiring Clone. Check if any type is not constrained for
    // this impl.
    if ty_subs.types().any(|ty| !implements_trait(cx, ty, clone_id, &[])) {
        return;
    }
    // `#[repr(packed)]` structs with type/const parameters can't derive `Clone`.
    // https://github.com/rust-lang/rust-clippy/issues/10188
    if ty_adt.repr().packed()
        && ty_subs
            .iter()
            .any(|arg| matches!(arg.unpack(), GenericArgKind::Type(_) | GenericArgKind::Const(_)))
    {
        return;
    }

    span_lint_and_note(
        cx,
        EXPL_IMPL_CLONE_ON_COPY,
        item.span,
        "you are implementing `Clone` explicitly on a `Copy` type",
        Some(item.span),
        "consider deriving `Clone` or removing `Copy`",
    );
}

What's interesting is that with max_width=100 and error_on_line_overflow=true  errors are emitted:
error[internal]: line formatted, but exceeded maximum width (maximum: 100 (see `max_width` option), found: 102)
  --> <stdin>:21:21:101
   |
21 |             let has_copy_impl = cx.tcx.all_local_trait_impls(()).get(&copy_id).map_or(false, |impls| {
   |                                                                                ^^
   |

error[internal]: line formatted, but exceeded maximum width (maximum: 100 (see `max_width` option), found: 130)
  --> <stdin>:24:24:101
   |
24 |                     .any(|&id| matches!(cx.tcx.type_of(id).subst_identity().kind(), ty::Adt(adt, _) if ty_adt.did() == adt.did()))
   |                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |

warning: rustfmt has failed to format. See previous 2 errors.

I did some digging and I've figured out why we're not emitting a max_width error when max_width=120 is set, and I also figured out why we emit an error when max_width=100 is set.
The short answer is we're failing to emit an error because rustfmt doesn't currently support formatting matches! macros when they have match guard's (#5547).
Failing to format the macro leads to rustfmt adding the macro to the skipped_range list in return_macro_parse_failure_fallback:
https://github.com/rust-lang/rustfmt/blob/34f9ca28f2f4ae3ac462c6dcd862b513e107e459/src/macros.rs#L138-L141
which is behavior that was added by PR #3768.
Then when rustfmt gets to the point where it determines if it should emit a max_width error it decides to ignore it since it thinks the macro call was skipped via the #[rustfmt::skip] attribute instead of a macro formatting failure.
https://github.com/rust-lang/rustfmt/blob/34f9ca28f2f4ae3ac462c6dcd862b513e107e459/src/formatting.rs#L551-L560
It would seem that PR #3768 extended the use case for skipped_range, however the doc comment makes it clear that it was only intended to be used for #[rustfmt::skip] annotations:
https://github.com/rust-lang/rustfmt/blob/34f9ca28f2f4ae3ac462c6dcd862b513e107e459/src/visitor.rs#L83-L85

So why do we emit an error message when max_width=100?
It turns out that when we add the matches! macro to skip_ranges back in return_macro_parse_failure_fallback we add the lines range of the macro from the source file, not the line range after formatting.
In both the max_width=120 and max_width=100 case we push (19, 19) into the skipped range list (assuming you run rustfmt directly on the input snippet from my previous comment), but after formatting with max_width=100 rustfmt has less room to work with on each line so some lines that could be written on a single line with max_width=120 now get formatted over multiple lines.
This offsets the matches! line to line 24, and when rustfmt checks if line 24 was skipped it finds that it was not and decides to emits the error message.

Wow. That you put so much work into this in such a short period of time is, frankly, awe inspiriing, Thanks tremendously, @ytmimi!

@smoelius thanks for the kind words 😁 It definitely helps that I knew where to start looking.
Now that we understand the underlying issue we can try to come up with a solution. It may be as simple as removing the lines in return_macro_parse_failure_fallback, but more work will be needed to understand how removing those lines affect macro formatting failures. We may have to come up with a completely different solution. Unfortunately I don't have the bandwidth to do a deep dive into this right now, but I'm happy to help anyone who wants to take this on.

It turns out that when we add the matches! macro to skip_ranges back in return_macro_parse_failure_fallback we add the line range of the macro from the source file, not the line range after formatting.

It may be as simple as removing the lines in return_macro_parse_failure_fallback...

I would have expected you to say: changing that code to insert the line range after formatting.
Is that not desired? Could you briefly explain why?

I would have expected you to say: changing that code to insert the line range after formatting.
Is that not desired? Could you briefly explain why?

@smoelius Just to be clear I was suggesting we try to remove these lines of code altogether:
https://github.com/rust-lang/rustfmt/blob/34f9ca28f2f4ae3ac462c6dcd862b513e107e459/src/macros.rs#L138-L141
The false positive that you've pointed out in this issue is directly caused by rustfmt inserting line ranges into the skip_range list, so we definitely can't solve this issue by adjusting the line range we insert into skip_ranges. Additionally, I don't think we have enough information at the time of calling retrun_macro_parse_failure_fallback to determine how the lines from the input map to lines in the output.

Thank you, @ytmimi. Your explanation makes sense to me.

I'd like to request that we hold off on changing rustfmt behavior for the moment as I haven't had the bandwidth to process this thread yet.
Salient tl;dr, however, is that rustfmt intentionally handles macros differently and it's correct/intentional/desirable behavior that rustfmt does not error in cases where an unformattable macro exceeds width boundaries

@calebcartwright if the current behavior is correct, then we've got a separate issue to deal with that I highlight in the second half of https://github.com/rust-lang/rustfmt/issues/5700#issuecomment-1447586217 where I answer the question So why do we emit an error message when max_width=100?.


Add option to skip downloading PAA root certificates

This is especially useful during development.

I restart the server often in my dev environment, so I'd like to have the option to skip (as I know they are recent enough).

I restart the server often in my dev environment, so I'd like to have the option to skip (as I know they are recent enough, and it slows down startup time of the Matter Server, which is annoying during testing). This allows me to just add --skip-paa-certificate-fetch to the VS Code task run configuration.

Yeah, I get the point, but maybe we can enhance this even further by storing the last fetch timestamp in our persistent storage and if its fresher than, let's say 24 hours, we skip downloading the certs. That way its even more convenient.

Yeah, I get the point, but maybe we can enhance this even further by storing the last fetch timestamp in our persistent storage and if its fresher than, let's say 24 hours, we skip downloading the certs. That way its even more convenient.

Good idea, also for production!
But we could still have this flag, IMHO :sweat_smile:

But we could still have this flag, IMHO 😅

Let's not do that. It will end up by default in our VS Code configs and then we get issues one day when we try to commission a brand new device and then realize only after 3 hours we have this flag set haha. I'd rather quickly implement that freshness check. Then its solved for both usecases.

Yeah I guess this is philosophical. I kinda like to have arguments and to be under full control over what my server is doing. :man_shrugging:
But I can live with it either way.


Plugin Dev Ref giving 404

The plugin development ref, as linked to on the wiki/blog is giving a 404
URL is http://projects.skurfer.com/QuicksilverPlug-inReference.mdown
Linked to on the following pages:
https://qsapp.com/wiki/Developer_Information
http://blog.qsapp.com/post/47769690224/developing-plugins-for-quicksilver
@skurfer

I know. Had to move to a new VM and I took the chance to switch to Nginx. Haven’t gotten the thing working yet, but I will over the break. Thanks!

Back in business. Had to give up on Nginx (for now). :cry:


New maintainer(s) needed

Hi everyone,
Unfortunately I find myself without free time to improve upon the code base left by @Nick-Lucas while also moving towards different approaches and technologies (I'm primarily focusing on R).
Therefore, I cannot continue to actively maintain the project and I'm looking for anyone interested to take over. Let me know if you're interested and we can go through the handover of the project, incl. the nuget repo.
cc: @rohitjha @MarkusKgit @anovik @prasadtelkikar @akritikos @Nick-Lucas

Hi @gkampolis, I am interested in helping maintain the repo and improve the code base.

Hi,
I would like to help with code contributions, reviews etc. but I don't have the time for full ownership.
Greetings,
Markus

Hi,
I can also help with code contributions but I don't have enough time right now to maintain the repo.
Best regards,
Anna.

Hi @rohitjha, glad to see you're interested.
As you can see in the previous thread here the process involves 3 elements:

I'll see if I can transfer the repo directly to you. If not, I'll give you admin rights (and then you can transfer it on your own).
You'll need to set up a free AppVeyor account if you don't have one already (and create an AppVeyor project for the repo)
You'll need to ceate a nuget account, if you don't have one already, so I can transfer the ownership to you

The instructions for building the project are already present in appveyor.yaml and you should be able to get it going from the get go, by applying your own AppVeyor id key. The propagation to nuget is fairly simple, after you're happy with the state of the project for a new release, you simply need to increase the version prefix in the csproj and commit, triggering a new build by AppVeyor, which will "see" the new version and send that to nuget. Of course, you can move to a more sophisticated way of doing things using git tags, but I have no idea how to do this.
Let me know when you want to initiate all this. :)

@rohitjha I've tried to transfer ownership to you but I get the error message that "rohitjha/UnitConversion already exists."
Can you rename your fork or simply rename your local folder (to keep a backup of your work so far) so I can continue with the transfer?

@gkampolis I've renamed my fork to UnitConversionOld so you should be able to transfer now. Also, I've created a free AppVeyor account and a NuGet account (username rohitjha).

@rohitjha are you still interested in taking up the project?

I am interested in taking up this project

@gkampolis @rohitjha , lot of people are interested to take up this project, still no one started actual work on it.
My question to you is, when we are going to start working on this project?
what is next plan?

Sorry for the delay everyone, I never heard back from @rohitjha (almost a month ago) and then my own outside commitments kicked in.
@atulmish Many thanks for your interest, I'm very grateful you're willing to step in. I'll try transferring the repo to you directly, later on tonight. For this to succeed, you must not have already a repo with the same name or even a fork of this one (see previous attempt with @rohitjha above).
If you already have work you'd like to commit, you can either create a pull request that I'll accept  (and then you should delete your repo), or save your work locally (and then delete your repo) and commit afterwards.
@prasadtelkikar Apart from @rohitjha and @atulmish, everyone else said that they're willing to contribute but not take over the project. So not a lot of people but just two, with the first one going silent 1.5 months ago and @atulmish kindly expressing his interest 6 days ago. If you wanted to take over, I would have gladly transferred the repo to you, had you indicated that you were available and willing.

@gkampolis , I am ready to take ownership of this repo, as I have no experience in open source maintenance so I did not raise my hands for the same.
If no one is taking this role, then I am ready to take this challenge. Just need your help and guidance for the same

Hi @gkampolis ,
I am glad to hear back from you. I have theb plan
Phase 0:
Takeover
Resolve open issues.
Phase I: New types of converters
Power Converter
Atmospheres Converter
Energy Converter
Temperature Converter
Phase II: Developer Experience and Usabily Enhancements
Extension
Fluent Interface
Async Support
Phase II: Plugable third parties
Currency Converter (Plug in third party provider)
More to come

I am happy to confirm that I have accepted the transfer.
@gkampolis we would also need the ownership of AppVeyor and Nuget.

@atulmish I've sent you the relevant request over at nuget. That should pretty much be everything I think.
You'll need to link the gthub repo to an AppVeyor project which will update the nuget deployment once you manually change the version of the package. See previous comments on this thread and let me know if anything is amiss.
:)

The ownership transfer is complete so I am closing this issue.


flutter attach should wait if the requested fuchsia mod is not currently running

This matches the experience of iOS and Android, and allows developers to run attach before starting up a mod.

cc @keertip


Remove amplitude

Description
Removes Amplitude analytics from the project:

Deleted Amplitude-related code and imports
Removed amplitude_pull_types.sh script
Adjusted components (10+ files affected)

Risk
None, no one is using amplitude and amplitude -> customer.io integration was disabled.
Deploy Plan
Deploy front

✂ Can we also remove the env variables?

good point & sure !


action.Set() does not return NSButton to callback function

In Objective-C NSControl's action property is set to a method that has an argument that is usually called sender. In this callback  function the sender variable should point to the control that triggered the action to take place (just like in Objective-C). So if a NSButton triggered the action sender should be set to that NSButton. In this example program the variable sender is used to get the button's title that triggered the action:
package main

import (
	"fmt"
	"github.com/progrium/macdriver/helper/action"
	"github.com/progrium/macdriver/macos/appkit"
	"github.com/progrium/macdriver/objc"
)

func main() {
	app := appkit.Application_SharedApplication()
	app.SetActivationPolicy(appkit.ApplicationActivationPolicyRegular)
	app.ActivateIgnoringOtherApps(true)
	w := appkit.NewWindowWithSize(200, 200)
	w.SetTitle("Test Layout")

	// Button code
	button := appkit.NewButtonWithTitle("The Super Button")
	action.Set(button, doButton)
	w.ContentView().AddSubview(button)

	w.MakeKeyAndOrderFront(nil)
	w.Center()
	app.Run()
}

// The action method for button
func doButton(sender objc.IObject) {
	button := sender.(appkit.Button)
	fmt.Println("button's title:", button.Title())
}

What should happens is that in the doButton() method should be able to print the title of the button.
What actually happens is a panic:
panic: interface conversion: objc.IObject is objc.Object, not appkit.Button

goroutine 1 [running]:
main.doButton({0x1002fe588?, 0x13671f750?})
	/Users/user/desktop/test/main.go:29 +0xb0
github.com/progrium/macdriver/helper/action.callAction(0x14000028560?, 0x100179268?)
	/Users/user/Documents/golang/MacDriver/MacDriver-git/macdriver/helper/action/action_handler.go:54 +0x64
github.com/progrium/macdriver/objc/ffi._Cfunc_ffi_call0(0x1400007e600, 0x1c1c9c39c, 0x1003dc930, 0x14000013810)
	_cgo_gotypes.go:150 +0x30
github.com/progrium/macdriver/objc/ffi.Call.func1(0x1400007e600?, 0x200000001?, 0x1cd2f52f8?, {0x14000013810?, 0x200000000?, 0x1400007e600?})
	/Users/user/Documents/golang/MacDriver/MacDriver-git/macdriver/objc/ffi/ffi.go:76 +0x6c
github.com/progrium/macdriver/objc/ffi.Call(0x1400007e600, 0x14000013820?, 0x1003dc930, {0x14000013810, 0x2, 0x2})
	/Users/user/Documents/golang/MacDriver/MacDriver-git/macdriver/objc/ffi/ffi.go:76 +0x30
github.com/progrium/macdriver/objc.CallMethod[...]({0x1002fd6f8, 0x136705a80}, {0x209142be0}, {0x0, 0x0, 0x100282ae0})
	/Users/user/Documents/golang/MacDriver/MacDriver-git/macdriver/objc/class.go:279 +0x4e0
github.com/progrium/macdriver/macos/appkit.Application.Run({{{0x1002fe610?}}})
	/Users/user/Documents/golang/MacDriver/MacDriver-git/macdriver/macos/appkit/application.gen.go:178 +0x54
main.main()
	/Users/user/desktop/test/main.go:24 +0xe0
exit status 2

Instead of:
func doButton(sender objc.IObject) {
	button := sender.(appkit.Button)
	fmt.Println("button's title:", button.Title())
}

try:
func doButton(sender objc.Object) {
	button := appkit.MakeButton(sender.Ptr())
	fmt.Println("button's title:", button.Title())
}

It does not work.
This is the error:
./main.go:19:21: cannot use doButton (value of type func(sender objc.Object)) as action.Handler value in argument to action.Set

This is what I came up with as a fix:
---
 helper/action/action_handler.go | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/helper/action/action_handler.go b/helper/action/action_handler.go
index 9bbca78..16fe3dc 100644
--- a/helper/action/action_handler.go
+++ b/helper/action/action_handler.go
@@ -39,8 +39,11 @@ func Wrap(handler Handler) (target Target, selector objc.Selector) {
 }

 // Set set action for an ojbc instance, if it has target and setAction method.
-func Set(instance CanSet, handler Handler) {
-	target, selector := Wrap(handler)
+func Set(instance CanSet, callbackFunc Handler) {
+	callbackWrapper := func(sender objc.IObject) {
+		callbackFunc(instance)
+	}
+	target, selector := Wrap(callbackWrapper)
 	defer target.Release()
 	objc.SetAssociatedObject(instance, objc.AssociationKey("target"), target, objc.ASSOCIATION_RETAIN)
 	instance.SetTarget(target)
--
2.36.1

This change makes the example program work correctly.

How it works is it creates another function that calls the callback function with the control "instance" as an argument.

I can see that, but this makes assumptions about what Apple is passing as the sender. It works in this case, but it is not correct. Even if it were fine, this patch doesn't remove the code it totally bypasses. I'm about to push a different fix.

Pull and try my suggestion.
This was the change: https://github.com/progrium/macdriver/commit/8a4a2f7078550b417d4ab1da3df3ebc1fd3b9619

I can see that, but this makes assumptions about what Apple is passing as the sender. It works in this case, but it is not correct. Even if it were fine, this patch doesn't remove the code it totally bypasses. I'm about to push a different fix.

Yes I assume the variable sender will be a subclass of NSControl. Do you have a situation where this is not true?
Is action.Set() only suppose to be used with NSControl subclasses?

Pull and try my suggestion.
This was the change: 8a4a2f7

This change does make your doButton() function work now, but I don't think this is the best way to fix the problem.
Your doButton() function relies on a lot of DarwinKit code that is pretty new and undocumented. My doButton() function uses Go's type assertions which are fully documented and well known to the public. I believe using my patch would be easier for the public to use.

Dude.
You can see it works with anything that implements CanSet, which is a pattern elsewhere in Apple's APIs, like I was saying a while back. If you were to assume the sender is the argument, that would break Apple APIs and make this system behave inconsistent with how the underlying system is documented. Here are the docs on this pattern, which states the sender is usually but not always the instance:
https://developer.apple.com/library/archive/documentation/General/Conceptual/CocoaEncyclopedia/Target-Action/Target-Action.html
Yes, my way is undocumented right now, but that is the way that works correctly and it will be documented as such. It can be improved (for example appkit.ButtonFrom(sender)) but that is a different conversation. You can't type assert a value that is not already that type and Go types don't always carry across the FFI boundary, and it especially won't work if the sender is not that instance.
Also, a little humility when facing a system you don't fully understand goes a long way when trying to persuade people of your viewpoint.


Add add-on release tasks

Add (opinionated) tasks to help with the release of the add-on:

CreateGitHubRelease, a task that creates a GitHub release.
PrepareAddOnNextDevIter, prepares the next development iteration of
the add-on. Updates the changelog (with Unreleased section) and bumps
the version of the add-on.
PrepareAddOnRelease, prepares the release of the add-on. Replaces
the Unreleased section of the changelog with the version, release date,
and link to the release.

Split ConvertChangelogToChanges into two tasks to support the above
use case:

ExtractLatestChangesFromChangelog, extracts the changes from the
latest release, by keeping the changes in markdown they can be directly
used in the GitHub release.
ConvertMarkdownToHtml, converts markdown into HTML to be included
in the add-on manifest (as before).

The tasks CreateGitHubRelease and PrepareAddOnNextDevIter are exactly the same as the ones in the zap-extensions repo, the task PrepareAddOnRelease was tweaked to add a newline after the release link (so that PrepareAddOnNextDevIter does not introduce changes by adding the newline).

Addressed.


Plenv plugin

Initial creation of a simple plugin for plenv. See https://github.com/tokuhirom/plenv for details on plenv.

Thanks! I've added a couple of comments - can you please take a look?

I've updated the plugin as suggested. I'll close this pull request and open a new one.


HBASE-28663 Graceful shutdown of CanaryTool timeouts (branch-2)

HBASE-28663
clean cherry-pick of https://github.com/apache/hbase/pull/5991 followed by replacing a RegionInfo with a new HRegionInfo(RegionInfo) for a test method which expects the HRegionInfo.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 47s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m 24s
branch-2 passed

+1 :green_heart:
compile
2m 52s
branch-2 passed

+1 :green_heart:
checkstyle
0m 37s
branch-2 passed

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 31s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  1s
the patch passed

+1 :green_heart:
compile
2m 52s
the patch passed

+1 :green_heart:
javac
2m 52s
the patch passed

+1 :green_heart:
checkstyle
0m 36s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
10m  9s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
spotless
0m 43s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 37s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

31m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5992

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 9a9eb00022ca 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / e865c852c0

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
78 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 46s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

-1 :x:
mvninstall
1m 26s
root in branch-2 failed.

+1 :green_heart:
compile
0m 38s
branch-2 passed

+1 :green_heart:
shadedjars
5m 13s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 19s
the patch passed

+1 :green_heart:
compile
0m 40s
the patch passed

+1 :green_heart:
javac
0m 40s
the patch passed

+1 :green_heart:
shadedjars
5m 17s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
213m  6s
hbase-server in the patch passed.

234m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5992

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 08ccc8a8417e 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / e865c852c0

Default Java
Temurin-1.8.0_352-b08

mvninstall
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/artifact/yetus-jdk8-hadoop2-check/output/branch-mvninstall-root.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/testReport/

Max. process+thread count
4259 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  1s
branch-2 passed

+1 :green_heart:
compile
0m 50s
branch-2 passed

+1 :green_heart:
shadedjars
5m 25s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 28s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 47s
the patch passed

+1 :green_heart:
compile
0m 51s
the patch passed

+1 :green_heart:
javac
0m 51s
the patch passed

+1 :green_heart:
shadedjars
5m 23s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 25s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
227m 14s
hbase-server in the patch passed.

251m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5992

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9a8148d78332 5.4.0-174-generic #193-Ubuntu SMP Thu Mar 7 14:29:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / e865c852c0

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/testReport/

Max. process+thread count
4451 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5992/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

this was "merged" by commits https://github.com/apache/hbase/commit/32125e9c9f4132a9688d4137181dec073792a0e0 and https://github.com/apache/hbase/commit/353675e500cb2b8cd823cbc6c437d7d3d9a24135


If running the bot from a ubuntu server, is it then possible to send items to a certain account by ssh?

Title

Uhhh... nope.


Fixed failing docker build

I've fixed the issue with the failing docker build. Looks like two && where missing from one of the RUN commands.
Fixes #480

Thanks mate!


[WIP] Server shared resolutions

Fixes #

@typescript-bot user test tsserver
@typescript-bot test tsserver top256

@DanielRosenwasser this is not yet done.. infact i am pushing a commit at a time so i can run all incremental tests to verify each change is ok..

document’s readability and level statistics by selecting the Home tab, choosing Editor, and then going to Document stats1. You can also view document statistics by clicking the File tab in the Ribbon, selecting Info, and then looking under Properties2. Is this what you

@typescript-bot user test tsserver
@typescript-bot test tsserver top256


serOpen() serFlags?

Hello, please give advice on serFlags for the serial port, I haven't found anything in documentation, only that it should be set to null. But that If I want to set 8E1, how to do this?

As the doc states, these flags are (currently) undefined and must be set to zero.  There are no plans to make any enhancements in this area.
if you are using baud rates < 38K, you can use the bbserial apis which allow more control over the frame.


是否考虑 用template 来向LLM 提问？

在使用extension时候，对LLM的提问基本上是固定下来的，比如
解释代码
优化代码
现在的prompt 太简单，是不是可以考虑使用instructive prompt with an example，在7b model里没有什么特别的效果。
但可能对更大的model会有很好的效果。
另外，如果在fine tune的时候也使用同一个template，这可能将对LLM的一致性有很大的提高。

 You will provide the best possible answer with the code example, you also MUST provide reference url link to proof where you get the answer from.
User: use python sum up 43 to 2933
Llama: Python code example using for loop and range function to add all numbers in between given two numbers is :
numbers = [i for i in range(43, 2933)]
print(sum(numbers))
Answer:
The above answer is not possible as it's an exhaustive list of numbers that cannot be provided without proper context or reference url link. The question should have been more specific and focused on providing only one number at a time so the correct solution can be easily found based on this information. | Code Example:
def addallnumbers():
total = 0
# Using For Loop
for num in range(43, 2933):
    total += num

return total

Calling Function
result = addallnumbers()
print("Sum of Numbers Between 43 & 2933:", result)
Reference URL Link: https://www.mathsisfun.com/algebra/addition-sequence.html |

From the example above, it's clear that using a structured template allows us to customize the response with specific details, enhancing the quality of the output from the language model.


automatically link type names found in the doc comments

It would be a great enhancement to automatically link any API type names that are found in the doc comments. Adding a markdown link works, but it doesn't render properly in godoc, so if we can add the link in the generator we can have best of both worlds.

I can't think of a clean way of linking from parts of godoc comments without over-engineering.
Such a smart detection might also be susceptible to issues like:

generic type names such as Service could be linked unintentionally from all over the place

type A is in multiple pkgs (i.e. multiple apiversions) but we can't easily figure out which one to link to.

If we can live without, that'd be preferable. If you definitely want to do it, probably should be opt-in with an explicit syntax that doesn't break godoc too much.

Yeh, I think you are right; this is more problematic the more you think about it.
I poked at this using strings.Replacer which kinda works because all the types are in a single package (so the Name.Name field is unique). However, replacer does string replacements not word replacements, which is sometimes what you want. ListenerReasonDegradedRoutes gets the Listener part linked to the Listener type, which is totally unwanted, but Listeners also gets its Listener part linked, which could be what you want, but you'd want the whole word to be the link, not just the Listener prefix. There's a few variations of this.
If we switch to something like bufio.Scanwords we would have to deal with preserving the whitespace, which will be complicated. Still would need to have heuristics to get variants like "Listeners" and Gateway(s)" to all link to the same target.
There's no package context from renderComments which would result in the "easily figure out which one to link to" problem you point out above.
Here's a super-naive implementation:
diff --git main.go main.go
index 95193b8..6c7bb71 100644
--- main.go
+++ main.go
@@ -338,14 +338,25 @@ func isLocalType(t *types.Type, typePkgMap map[*types.Type]*apiPackage) bool {
        return ok
 }

-func renderComments(s []string, markdown bool) string {
+func renderComments(s []string, typePkgMap map[*types.Type]*apiPackage, markdown bool) string {
        s = filterCommentTags(s)
        doc := strings.Join(s, "\n")

        if markdown {
+               var replacements []string
+
+               for t := range typePkgMap {
+                       if lnk, err := linkForType(t, generatorConfig{}, typePkgMap); err == nil {
+                               klog.Infof("type %q, link %q", t.Name.Name, lnk)
+                               replacements = append(replacements, t.Name.Name, fmt.Sprintf("[%s](%s)", t.Name.Name, lnk))
+                       }
+               }
+
+               r := strings.NewReplacer(replacements...)
+
                // TODO(ahmetb): when a comment includes stuff like "http://<service>"
                // we treat this as a HTML tag with markdown renderer below. solve this.
-               return string(blackfriday.Run([]byte(doc)))
+               return string(blackfriday.Run([]byte(r.Replace(doc))))
        }
        return nl2br(doc)
 }
@@ -649,7 +660,7 @@ func render(w io.Writer, pkgs []*apiPackage, config generatorConfig) error {
                "typeIdentifier":     func(t *types.Type) string { return typeIdentifier(t) },
                "typeDisplayName":    func(t *types.Type) string { return typeDisplayName(t, config, typePkgMap) },
                "visibleTypes":       func(t []*types.Type) []*types.Type { return visibleTypes(t, config) },
-               "renderComments":     func(s []string) string { return renderComments(s, !config.MarkdownDisabled) },
+               "renderComments":     func(s []string) string { return renderComments(s, typePkgMap, !config.MarkdownDisabled) },
                "packageDisplayName": func(p *apiPackage) string { return p.identifier() },
                "apiGroup":           func(t *types.Type) string { return apiGroupForType(t, typePkgMap) },
                "packageAnchorID": func(p *apiPackage) string {


Bug: YAML Title Alias does not escape commas

Describe the Bug
If an h1 contains commas, the generated aliases array entry is not correctly escaped.
Obsidian expects an array for the aliases field; thus, any entry without quotes that contains commas is interpreted as multiple entries. Unfortunately, headers with commas are not enquoted, resulting in multiple aliases instead of one.
How to Reproduce
The following example shows the problem:
---
aliases: [Consistent, Durable, and Safe Memory Management for Byte-addressable Non Volatile Main Memory]
---

# Consistent, Durable, and Safe Memory Management for Byte-addressable Non Volatile Main Memory

Lorem Ipsum...

Obsidian parses this as multiple aliases:

Consistent
Durable
and Safe Memory Management for Byte-addressable Non Volatile Main Memory

This can be seen for example in the open document dialog.

Expected Behavior
If a title contains commas, it should be enquoted, exactly like if it contains : and their like.
---
aliases: ["Consistent, Durable, and Safe Memory Management for Byte-addressable Non Volatile Main Memory"]
---

# Consistent, Durable, and Safe Memory Management for Byte-addressable Non Volatile Main Memory

Lorem Ipsum...

The alias is now correct:

Device

[x] Desktop
[x] Mobile

I just found out that it works correctly with multi-line arrays. Just single-line and single string break.

Thanks for reporting this. I will see about fixing this. It seems that I just need to go ahead and escape that value if it is for either of those two types.

Ok thanks!
The multi line workaround is sufficient at the moment, but a single line would be more condense. So I appreciate your work :)

I believe I have a fix for this issue. It was much simpler than I thought it would be. However it may not fix existing bad data, so that may need to be dealt with manually.

This should be fixed on master and in the next release. Please let us know if that is not the case.


Driver

Init compute driver for OpenStack and upgrade network driver
Init OPS compute driver (Init base driver follow proposal):

create
show
list
delete
shutdown
start
reboot
resize
add_nic
delete_nic
list_nic

Upgrade network driver

allocate_public_ip

Coverage decreased (-2.4%) to 78.488% when pulling 9eb420920415962b4090acd48a3e280d1179f4d2 on driver into e49442e398245513100cb16930d1480f44483b68 on master.

Coverage decreased (-1.9%) to 79.018% when pulling aeeffee6e4c5e990559ac8a4e2ed55a4ef2fd871 on driver into e49442e398245513100cb16930d1480f44483b68 on master.

Coverage decreased (-0.6%) to 80.318% when pulling cacea31501ec6efe1cd221f9e47be9a7371b5b17 on driver into e49442e398245513100cb16930d1480f44483b68 on master.

Coverage increased (+0.6%) to 81.503% when pulling e7c6c1d33b69e6f67e1701fe8e96a2aa8d5a1fbc on driver into e49442e398245513100cb16930d1480f44483b68 on master.

Coverage increased (+0.6%) to 81.475% when pulling 51f0bc5de949b6688255cdb6d8338640120a8fe8 on driver into e49442e398245513100cb16930d1480f44483b68 on master.

@hieulq : Others code review have been fixed by this: https://github.com/cloudcomputinghust/CAL/commit/51f0bc5de949b6688255cdb6d8338640120a8fe8

@daikk115 ping?

Coverage decreased (-1.03%) to 79.857% when pulling cdc7a95408ea43df26e10356a7cb58c01e8a6cc2 on driver into e49442e398245513100cb16930d1480f44483b68 on master.

@hieulq : Coverage decreased by we don't have test for calplus/conf/opts.py
I wonder how to skip coverage on calplus/conf/opts.py or write a testcase for it.
I have try to find something like that but I still didn't get it.


dnsendpoint: not-yet-scraped: no error, no requeue

Second attempt to reduce thrashing on controller startup with lots of
clusters.
Since the scraper posts an event causing the DNSZone to be enqueued,
there's no need for this path to requeue (immediately, or ever). And
since we're just waiting for the scrape, it's not really an error
condition.
HIVE-1855

/assign @abutcher

/test e2e

/lgtm

/hold
Going to unfreeze, want to have a look at the CI results before this lands.

/test e2e
cmon now

/test e2e

Going to do this completely differently, on top of #1766.


Add support for spec annotations

It would be good to add the possibility of annotating the definitions with pre/post-conditions and even proof annotations.
This issue should be done after https://github.com/AeneasVerif/charon/issues/63

After https://github.com/AeneasVerif/charon/pull/105, an annotation like
#[postcondition(*x == y)]
fn foo(&mut x, y) { ... }

will show up as a string "postcondition(*x == y)" in the function attributes. Should charon do more than that?


Bug in followComponent when adding a background image

Current bug behaviour
Shake occurs when adding followComponent to camera and having background image using Box2d. This jitter disappears when that background image is removed, so there could be some relationship between component movement, camera tracking to it, background image, and rendering or memory.

Expected behaviour
...
Steps to reproduce

move a SpriteComponent in Box2d,
follow it with the camera with followComponent,
add an image or background parallax

More information
Sometimes I have been able to observe it in the example of FollowComponent with the camera in the example of the documentation

Forge2DGame's dimensions were different than the window. Putting it all relative to the size of the window partially solved it. Since the bug may be related to the performance of my own computer or to other causes that are not related to the flame engine, I think it is best to close this issue, and in case it becomes more clear later on, reopen it.
Happy New Year and great work for this great tool that is Flame Engine !!!


Delegate IO to faked File instead of IO in Pathname

Addresses #220 by incorporating @jirutka's fix with minor changes and unit tests.

See ticket #220 .  Thanks for the patches!

@marxarelli Thanks! :smile_cat:

No problem! Thanks for the original fix and the speedy patch release.


Clear Cache

Hay there will it be possible to add clear cache method
Thanks

I think we can add this method. But how it should works in details. I assume after calling Clear() we should end up with no entries in cache. Questions we need to answer

Are we going to call OnRemove callback for every element in cache
Are we going to create new (small) shard queues or just use existing one

In my opinion clear should just delete all entries in maps by creating new map (GC will do the rest) and reset indexes in queue (tail, head, rightMargin, count). OnRemove should NOT be called.
@btesanovic @wendigo What do you think?

@janisz: onRemove does not make any sense I guess (if you need keys - use iterator before clear()). I agree with you on creating new map and reseting indexes

I'll try to come up with an implementation

Solved @btesanovic. Let me know if it works for you!

Hey @wendigo  , thanks so much for fast response, this is perfect !!


Add Maaslandcollege Domain

I've added the Maaslandcollege domain to be able to use the Educational License of the JetBrains IDE's.

@NielsKrijnen First stage of verification passed, official domain is maaslandcollege.nl as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@NielsKrijnen Thank you for your patience while waiting for a review and processing your request. Pull request merged.


DT-2347 - support multiselect in combobox

Description & motivation 💭

Add functionality to the <Combobox /> component to support multiselect

Screenshots (if applicable) 📸
https://github.com/user-attachments/assets/7deac79d-68b4-4361-a7ab-94bb97f8cfcb
https://github.com/user-attachments/assets/c56cce77-6cb8-4957-a0e1-b632094db98f
Design Considerations 🎨
Testing 🧪
How was this tested 👻

[ ] Manual testing
[ ] E2E tests added
[ ] Unit tests added

Steps for others to test: 🚶🏽♂🚶🏽♀
Checklists
Draft Checklist
Merge Checklist
Issue(s) closed
Docs
Any docs updates needed?

Might want some padding with no leadingIcon

Probably don't want the placeholder when selected

Probably don't want the placeholder when selected

I think we still do, but maybe the n options selected text should go in a badge? I think hiding the placeholder is weird cause then it doesn't really come across as an input you can filter.

Ohh I like that


Fix product implementation

Thanks to @charlydagos for catching this. I’m really sorry for having introduced this bug.

@cocreature 😃 😃 😃 😃 😃

Didn't catch this either. Good thing I waited.


Climate setting form validation errors

ie. name can't be more than 60 chars long, shouldn't be able to advance through the form unless the section is filled out

Merged with https://github.com/seamapi/react/issues/483


igluctl: add check metadata-path check for static generate command

On lint and static push we're checking that schema filepath conforms schema metadata, otherwise marking it as invalid. But static generate prints
File [/Users/chuwy/com.acme/./sql/com.acme/entity_action/1-0-0/1-0-2.sql] was written successfully!
File [/Users/chuwy/com.acme/./sql/com.acme/entity_action/1-0-0/1-0-3.sql] was written successfully!
File [/Users/chuwy/com.acme/./sql/com.acme/entity_action/1-0-0/1-0-2.sql] was not modified
File [/Users/chuwy/com.acme/./sql/com.acme/entity_action/1-0-0/1-0-3.sql] was not modified

Which is confusing since 1-0-2 weren't exist before.

Migrated to https://github.com/snowplow-incubator/igluctl/issues/43


Support for parachain runtime upgrades

Right now, at a first glance, I can see that the proposal hash is computed considering the call system > setCode(code), which works fine for relay chains and solo chains.
When working with parachains, the call is usually parachainSystem > enactAuthorizedUpgrade(code), which means that using SRTool results in a different proposal hash. Is there any plans to support this, perhaps with a feature flag or something?

Yeah but I see that the srtool Docker image uses the build script on startup, which apparently does not show this info. So the image needs to be tweaked or overridden in the CI to show the info we need. That is probably not scope of this issue in this repo tho 😁

Yes, srtool it out of topic here so I will close this issue.
FYI srtool does show the parachain_authorize_upgrade_hash as text of json depending on the flags you pass. I see its readme is a little outdated though and does not show it currently.
As an example, here is a (very) recent output of a srtool run (slightly truncated to keep it readable, and I added markers to help you spot the locations):
{
  "gen": "srtool v0.9.21",
  "src": "git",
  "version": "0.9.26",
  "commit": "da37ab2942d04157d096bc579bd5c7d50d8a2389",
  "tag": "v0.9.26-rc2",
  "branch": "HEAD",
  "rustc": "rustc 1.62.0 (a8314ef7d 2022-06-27)",
  "pkg": "polkadot-runtime",
  "tmsp": "2022-07-07T08:05:36Z",
  "size": "1255846",
  "prop": "0xbdb4beafad4beec8871d2815a3ca508dac3ebd2d3176aa36f79e39a4dd549797",
  "ipfs": "QmYJ2CkLYhwcguiBPvtKWTELGpZkU2VZPyfpurVBqkRLSx",
  "sha256": "0xc34cf3b2cf9f3875a2aa336849780b72464d2c874c4179eeb945e28fb14ea7f9",
  "wasm": "runtime/polkadot/target/srtool/release/wbuild/polkadot-runtime/polkadot_runtime.compact.compressed.wasm",
  "info": {
    "generator": {
      "name": "srtool",
      "version": "0.9.21"
    },
    "src": "git",
    "version": "0.9.26",
    "git": {
      "commit": "da37ab2942d04157d096bc579bd5c7d50d8a2389",
      "tag": "",
      "branch": "HEAD"
    },
    "rustc": "rustc 1.62.0 (a8314ef7d 2022-06-27)",
    "pkg": "polkadot-runtime",
    "profile": "release"
  },
  "context": {
    "package": "polkadot-runtime",
    "runtime_dir": "runtime/polkadot",
    "docker": {
      "image": "paritytech/srtool",
      "tag": "1.62.0"
    },
    "profile": "release"
  },
  "runtimes": {
    "compact": {
      "tmsp": "2022-07-07T08:03:15Z",
      "size": "6433406",
      "prop": "0xe42cbd7c6328666f0e13cada6f4d1f25f6bb5a0d76c6b6f9ed9479ecff27a2ba",
      "blake2_256": "0x3f97b2b51bacacd4104fa84aca60ed4a07b32c1e81185a126533a29492871110",
      "ipfs": "Qmema86oxydLnWtoZxBa3YZ2sCBQCfXAMm2gzNj2nDdPjk",
      "sha256": "0x498dc3b0ad678ea44aa9b0e3d3432d7c8af2e0aad4b5351ec139a8e331ff2578",
      "wasm": "runtime/polkadot/target/srtool/release/wbuild/polkadot-runtime/polkadot_runtime.compact.wasm",
      "subwasm": {
        "size": 6433406,
        "compression": {
          "size_compressed": 6433406,
          "size_decompressed": 6433406,
          "compressed": false
        },
        "reserved_meta": [
          109,
          101,
          116,
          97
        ],
        "reserved_meta_valid": true,
        "metadata_version": 14,
        "core_version": {
          "specName": "polkadot",
          "implName": "parity-polkadot",
          "authoringVersion": 0,
          "specVersion": 9260,
          "implVersion": 0,
          "apis": [... ],
          "transactionVersion": 13
        },
        "proposal_hash": "0xe42cbd7c6328666f0e13cada6f4d1f25f6bb5a0d76c6b6f9ed9479ecff27a2ba",

        **************************************************
        "parachain_authorize_upgrade_hash": "0x5bf55a45b12132487cfaeed7b772c0ff18bac151e1b011868846d4570d68cded",
        **************************************************

        "ipfs_hash": "Qmema86oxydLnWtoZxBa3YZ2sCBQCfXAMm2gzNj2nDdPjk",
        "blake2_256": "0x3f97b2b51bacacd4104fa84aca60ed4a07b32c1e81185a126533a29492871110"
      }
    },
    "compressed": {
      "tmsp": "2022-07-07T07:57:10Z",
      "size": "1255846",
      "prop": "0xbdb4beafad4beec8871d2815a3ca508dac3ebd2d3176aa36f79e39a4dd549797",
      "blake2_256": "0x083bd39c531f977569c30cdb5973613d68a78dd7a241795feb817df2414504ef",
      "ipfs": "QmYJ2CkLYhwcguiBPvtKWTELGpZkU2VZPyfpurVBqkRLSx",
      "sha256": "0xc34cf3b2cf9f3875a2aa336849780b72464d2c874c4179eeb945e28fb14ea7f9",
      "wasm": "runtime/polkadot/target/srtool/release/wbuild/polkadot-runtime/polkadot_runtime.compact.compressed.wasm",
      "subwasm": {
        "size": 1255846,
        "compression": {
          "size_compressed": 1255846,
          "size_decompressed": 6433406,
          "compressed": true
        },
        "reserved_meta": [
          109,
          101,
          116,
          97
        ],
        "reserved_meta_valid": true,
        "metadata_version": 14,
        "core_version": {
          "specName": "polkadot",
          "implName": "parity-polkadot",
          "authoringVersion": 0,
          "specVersion": 9260,
          "implVersion": 0,
          "apis": [...],
          "transactionVersion": 13
        },
        "proposal_hash": "0xbdb4beafad4beec8871d2815a3ca508dac3ebd2d3176aa36f79e39a4dd549797",

        **************************************************
        "parachain_authorize_upgrade_hash": "0x746c1694829420878211a8491ec77a28fe0d6bfd6c21b6d9acd375a3ad59d57a",
        **************************************************

        "ipfs_hash": "QmYJ2CkLYhwcguiBPvtKWTELGpZkU2VZPyfpurVBqkRLSx",
        "blake2_256": "0x083bd39c531f977569c30cdb5973613d68a78dd7a241795feb817df2414504ef"
      }
    }
  }
}


Size of favicon

Hello, I'm seeing that my favicon in chrome is 71KB and 256x256 pixels, I would expect it to be 2 or 3 Kb in size, am I wrong? thanks :)

.ico files were not minified at all.
This will be available with the rewrite in Icon Genie v2.


feat(lwc): add graphql map view component

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

Project coverage is 92.26%. Comparing base (be2da49) to head (3a1cdc4).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   91.84%   92.26%   +0.41%
==========================================
  Files          25       27       +2
  Lines         687      724      +37
  Branches       75       81       +6
==========================================
+ Hits          631      668      +37
+ Misses         56       54       -2
- Partials        0        2       +2

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


Imbalanced Dataset vs Cost Function

Hi,
@albahnsen  Do you have any thoughts on the relationship between the cost matrix and re-balancing the data? I notice that you do not rebalance in your final logistic regression model in your wonderful paper.
If I have a highly imbalanced dataset where:
<1% are Positive
99% are Negative
But the theoretical cost is:
30 if all are labelled positive
and 1 if all are labelled negative
What should I be adjusting to stop it predicting all Positive? The imbalance? The cost? THe iterations?
Thanks!
Edit: I've done some Cross Validation to check different C aand max_iter but it seems like the best savings score I can get it 0 (with the worst being -12).

Hi.
If you're assuming a constant cost between errors, it is the same doing a balancing of the input dataset than adjusting the threshold doing the cost.
However, if the costs are example-dependent, balancing the dataset does not give you optimal results.
Edit: I've done some Cross Validation to check different C and max_iter but it seems like the best savings score I can get it 0 (with the worst being -12).
That look quite suspicious.

Can I confirm the columns of the cost - matrix are?
false positives, false negatives, true positives and true negatives
When I print out the model history (view of the iterations), it suggests the cost per example for the best model is: $0.805161. However, when I manually get the savings score
cost, cost_base, savings_p = savings_score(y_vec, train_predictions, cost_mat)
The cost per example much higher at the cost per alert and the model predicts all fraud.

The cost-matrix and loss function appear fine so the problem is with the optimisation of the function.
Now the reason I suggested downsampling is because whereas you had 0.5% true fraud in your example, my example is more like 0.05% or worse. =( Therefore the optimisation tends to converse to predicting a single class. This is not ideal.


BigTiff

Just a note that the TIFF support here doesnt support BigTiff http://bigtiff.org/ . The tiff crate does support bigtiff for anyone interested in trying to support it
github.com/search?q=repo%3Aimage-rs%2Fimage-tiff%20bigtiff&type=code

Thanks for the note, investigating now.

Hello @jayvdb , I found this in the http://bigtiff.org/ page.

Please note this is not an official release of libtiff.  This version has been submitted for a future standard update.

Has bigtiff been merged into the libtiff mainline?

That page is very old.
It was added to libtiff v4.0.0 c.f. https://libtiff.gitlab.io/libtiff/specification/coverage-bigtiff.html , which I believe was 2011.
Oddly, it looks like BigTiff support was added to exiftool before that, in 2007.

The result of the investigation is that we can add support for bigtiff, but because imageinfo uses the i64 type to represent width and height, bigtiff uses the u64 type. Although this may cause potential problems for very large image files, in theory, images with width/height > INT64_MAX should not appear in reality.

@jayvdb Please check version 0.7.27. It should support bigtiff now.

Hello @jayvdb
Please let me know if it works or not.
Thanks!

The executable is saying "unrecognised image format"
There is a test image at https://github.com/Roughsketch/imagesize/pull/43 , and some in https://github.com/image-rs/image-tiff/tree/master/tests/images/bigtiff

oh ... hang on .. I didnt pull main

Ok, now I have the latest, yup it is working well.  Thank you!!


Spyder (Python 3.6) + Pandas 0.23 - Future Warning

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[x] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[x] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
'FutureWarning' generated in error - appears to be a bug. Fresh install of Spyder Python 3.6.5 via Anaconda, just two lines of code in a new console (below) begin to trigger error - after a multi-hour work session.  Thank you!
What steps reproduce the problem?

import pandas as pd
nov17_3mo = pd.date_range(end='2017-11-01', periods=3, freq='MS')

What is the expected output? What do you see instead?
Object is created as requested - but I get additional error:
C:\Users\pjacob\AppData\Local\Continuum\anaconda3\lib\site-packages\spyder\widgets\variableexplorer\utils.py:414: FutureWarning: 'summary' is deprecated and will be removed in a future version.
display = value.summary()
Once it starts, this error comes up after every line of code executed in the console, e.g., print(1+1)
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version: 3.2.8
Python version: 3.6.5
Qt version: 5.9.4
PyQt version: 5.9.2
Operating System name/version: Windows 10

Dependencies

PASTE DEPENDENCIES HERE

IPython >=4.0    :  6.4.0 (OK)
cython >=0.21    :  0.28.2 (OK)
jedi >=0.9.0     :  0.12.0 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
numpy >=1.7      :  1.14.3 (OK)
pandas >=0.13.1  :  0.23.0 (OK)
pycodestyle >=2.3:  2.4.0 (OK)
pyflakes >=0.6.0 :  1.6.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.8.4 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
rope >=0.9.4     :  0.10.7 (OK)
sphinx >=0.6.6   :  1.7.4 (OK)
sympy >=0.7.3    :  1.1.1 (OK)

Pandas has deprecated Index.summary() in favor of Index._summary() as per:
Issue: https://github.com/pandas-dev/pandas/issues/18217
PR: https://github.com/pandas-dev/pandas/pull/20028

Thank you, quite helpful - but note a couple of issues: (1) Once this warning occurs, ANY executed statement provokes the warning, for example: print(1+1).  Also, since the old Index.summary() is invoked by certain DateTimeIndex object references, the warning is triggered - and repeats continuously - without a direct invocation of Index.summary().

Yes clearly this needs to be fixed.
If you want you can test a possible workaround, try changing:
C:\Users\pjacob\AppData\Local\Continuum\anaconda3\lib\site-packages\spyder\widgets\variableexplorer\utils.py   line 414
from
display = value.summary()

to
display = value._summary()

and see if that fixes the problem. Then we will have a possible solution.

That fixes the problem for me.

I'm having the same problem.  Another workaround is to suppress the message with:
import warnings
warnings.simplefilter(action='ignore', category=FutureWarning)

Great, thanks very much for the help & focus on this.

@dalthviz, please help me to solve this one. Here
https://travis-ci.org/spyder-ide/spyder/jobs/395955090#L1512
you can find here all warning generated by the latest Pandas.
For each one please do the following:
try:
    display = value._summary()
except Exception:
    display = value.summary()

This is for summary, but you get the idea for the rest of them: the new method name must be called first and the old one second. This way we will guarantee compatibility with old Pandas versions and avoid these warnings.


Allow casks to opt-in to forcibly quit during brew upgrade

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
When performing brew upgrade, the quit stanka is skipped.
This FR is to add the ability for cask maintainers to opt-in to forcibly quit before upgrading their apps.
What is the motivation for the feature?
Based on feedback from @bevanjkay on https://github.com/Homebrew/homebrew-cask/pull/173061
In the instance of Gitify, users experience errors/exceptions when the application is upgraded in-place without exiting it first
How will the feature be relevant to at least 90% of Homebrew users?
to be discussed
What alternatives to the feature have been considered?
Adding custom preflight and postflight scripts to individual casks

Seems reasonable to me but defer to @Homebrew/cask folks.

This was a recent change, because apps such as Visual Studio Code should not be forcibly closed as it is likely to cause a loss of work.
Adding the ability to specify that the stanza should fire on upgrade makes sense to me, but the criteria for when this should apply could be difficult to determine. I would suggest that the loss of work is the item that matters most.

On uninstall we do run the quit and signal directives.

Here's the related PR: https://github.com/Homebrew/brew/pull/16507

Thanks @bevanjkay. Yeh, I think a new DSL/parameter is warranted here.

Can you think of an existing dsl that has a similar parameter I can use as a guide?

@bevanjkay depends_on I think is the best model here? It may be more complicated than you need, though. Feel free to hack something together and open a very early draft WIP PR and I'll help you from there 👍🏻


Improved panel

Thank you for your efforts.
Please add account traffic limit and usage time to the panel.
thank you

we're working on it.

now available on v1043.


Different structure under UL unordered list

When manually written html ul the output is wrong
Steps to reproduce the behavior:

In editor write any unordered list with li child tags
On the same level add image so the input looks like this

Pasting from Microsoft Word and Excel.

Custom table selection, merge and split.

Media embed, images upload.

Can use CodeMirror, KaTeX.

And.. many other features :)

And the output is:

Pasting from Microsoft Word and Excel.

Custom table selection, merge and split.

Media embed, images upload.

Can use CodeMirror, KaTeX.

And.. many other features :)

So the image tag is replaced with li and the image is not preset

Note:
tested on latest versions
"suneditor": "^2.41.3",
"suneditor-react": "^3.2.0",

The 2.42.0 version has been updated.
If this issue has not been resolved, please reopen this issue.
Thank you.


[BACKLOG-29981] - snowflake needs the catalog specified when collecti…

…ng metadata
It was found Teradata does not support catalogs.  There are possibly others.  So, moving methods into the DatabaseInterface so that each implementation can override as needed

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/database/Database.java
  core/src/main/java/org/pentaho/di/core/database/DatabaseInterface.java
  core/src/main/java/org/pentaho/di/core/database/DatabaseMetaInformation.java
  core/src/main/java/org/pentaho/di/core/database/SnowflakeHVDatabaseMeta.java
  core/src/test/java/org/pentaho/di/core/database/DatabaseTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.database.SnowflakeHVDatabaseMeta

Complexity Change: -0.1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.1% :small_red_triangle_down:
Method Change: -0.3% :small_red_triangle_down:

org.pentaho.di.core.logging.LoggingRegistry

Branch Change: -2.5% :small_red_triangle_down:
Complexity Change: -3.3% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:
Line Change: -1.3% :small_red_triangle_down:

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.uniquerows.UniqueRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.gpload.GPLoadMeta

Branch Change: -0.9% :small_red_triangle_down:
Complexity Change: -0.8% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/database/Database.java
  core/src/main/java/org/pentaho/di/core/database/DatabaseInterface.java
  core/src/main/java/org/pentaho/di/core/database/DatabaseMeta.java
  core/src/main/java/org/pentaho/di/core/database/DatabaseMetaInformation.java
  core/src/main/java/org/pentaho/di/core/database/SnowflakeHVDatabaseMeta.java
  core/src/test/java/org/pentaho/di/core/database/DatabaseTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.database.SnowflakeHVDatabaseMeta

Complexity Change: -0.1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.1% :small_red_triangle_down:
Method Change: -0.3% :small_red_triangle_down:

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -0.4% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.job.entries.evaluatetablecontent.JobEntryEvalTableContent

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Branch Change: -0.6% :small_red_triangle_down:
Complexity Change: -0.5% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:
Line Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -4.4% :small_red_triangle_down:
Complexity Change: -5.2% :small_red_triangle_down:

org.pentaho.di.trans.Trans

Branch Change: -0.1% :small_red_triangle_down:
Complexity Change: -0.1% :small_red_triangle_down:

org.pentaho.di.ui.repository.pur.repositoryexplorer.model.UIEERepositoryUser

Branch Change: -8.3% :small_red_triangle_down:
Complexity Change: -6.7% :small_red_triangle_down:
Instruction Change: -0.9% :small_red_triangle_down:
Line Change: -3.1% :small_red_triangle_down:

org.pentaho.di.ui.repository.pur.repositoryexplorer.model.UISecurityRole

Branch Change: -1.8% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.5% :small_red_triangle_down:


Add scroll bars to graph editor background

These will be a temporary addition until we come up with a better navigation solution.
Need to think about how the limits work. But I think initial assumption is the size of the graph editor background for the scroll bars is the size of the current workflow.

Refinement notes:

Let's try to make scrollbars not too eye-catching, like in the google docs
We could make scrollbar extend their range when "overscrolling" (so user could navigate an infinite canvas).

https://www.lucidchart.com/ seems to work reasonably well for the "overscrolling" problem.


hot_functions_from_file doesn't find functions created in a macro

I'm trying to hide some of the moving parts by creating the exported, no_mangle'd functions in a macro (exposed from a library) but when I attempt to use it in my reloadable lib, the hot_functions_from_file function doesn't find them.
// mod file1
#[macro_export]
macro_rules! make_exports {
  #[no_mangle]
  pub fn f() -> i32 { 42 }
}

// mod file2
make_exports!();

// main
mod hot_lib {
  hot_functions_from_file("file2/src/lib.rs");
}

fn main() {
  hot_lib::f(); // function not found in `hot_lib`
}

So one limitation of the approach used with the hot_module macro is that expansion of macros in the target file is not supported. This means we are looking literally for
#[no_mangle]
pub fn f() -> i32 { ... }

We ignore the function body but use the signature to generate proxy functions in the context of hot_lib.
Now depending on what you want there might still be ways around this.
manual signatures
One option is to directly specify the signatures in hot_lib itself:
Instead of doing
#[hot_lib_reloader::hot_module(dylib = "lib_crate")]
mod hot_lib {
  hot_functions_from_file!("file2/src/lib.rs");
}

you can do
#[hot_lib_reloader::hot_module(dylib = "lib_crate")]
mod hot_lib {
    #[hot_function]
    pub fn f() -> i32 {}
}

I.e. you have to make sure that the function signatures of the reloadable functions matches what is exported from the dynamic library.
ignore_no_mangle
I just pushed a change to master that allows for a syntax like
hot_functions_from_file!("lib/src/lib.rs", ignore_no_mangle = true);

This is experimental and not part of a release yet. I will remove it if it turns out not to be useful for your use case.
This will disable the #[no_mangle] restriction when reading files from lib.rs. Functions will still need to be pub and the lib still needs to export symbols representing those functions unmangled but you could have a different way of ensuring that, e.g. a build.rs script.
Also note that the file you target from hot_module does not necessarily need to be the place where the "real" functions are defined and/or exported. All we do is to read the signatures from that file. So if you have some way of generating this this would be another option.


jco doesn't support wasmbuilder.app composed components with string parameter and return values

This thread provides an example that should be easy to reproduce.  The component generated from wasmbuilder can be found here

Some additional context.  The repo linked in zulip has two components created using cargo-component.  One is called hello, and just exposes a function that prepends a greeting string to an input name.  This is imported by another component, big, which takes the greeting with the input name, and capitalizes all of the characters in the string, exporting this logic in a function called big_greet.  The component linked in this issue is the result of using wasmbuilder to try and compose the components.  The error message occurs when trying to use jco transpile on the result component.
panicked at 'not implemented', crates/js-component-bindgen/src/bindgen.rs:1029:49
(jsct transpile) RuntimeError: unreachable
    at __rust_start_panic (wasm://wasm/0122631e:wasm-function[3490]:0x1fdc92)
    at rust_panic (wasm://wasm/0122631e:wasm-function[3486]:0x1fdc3f)
    at _ZN3std9panicking20rust_panic_with_hook17h1e5f3993ce22fe2aE (wasm://wasm/0122631e:wasm-function[3485]:0x1fdc0f)
    at _ZN3std9panicking19begin_panic_handler28_$u7b$$u7b$closure$u7d$$u7d$17h757395b3caa1a881E (wasm://wasm/0122631e:wasm-function[3471]:0x1fcbd6)
    at _ZN3std10sys_common9backtrace26__rust_end_short_backtrace17h3e911ea98537fbdbE (wasm://wasm/0122631e:wasm-function[3470]:0x1fcb38)
    at rust_begin_unwind (wasm://wasm/0122631e:wasm-function[3480]:0x1fd866)
    at _ZN4core9panicking9panic_fmt17he9c46855d60d636eE (wasm://wasm/0122631e:wasm-function[3604]:0x206c27)
    at _ZN4core9panicking5panic17hf333278c14c20b5eE (wasm://wasm/0122631e:wasm-function[3610]:0x207190)
    at _ZN20js_component_bindgen7bindgen9JsBindgen11instantiate17hfe4cbb5545331156E (wasm://wasm/0122631e:wasm-function[101]:0xf8e0)
    at _ZN20js_component_bindgen9component8generate17h2fb6336405b47ca9E (wasm://wasm/0122631e:wasm-function[198]:0x280ae)

I believe this is resolved with the transcoding support.


Allow configuration of cape slot

I've noticed there is no way to disable placing the elytra within the capes slot. Even though this is a well liked feature I feel a way to configure it would be a good option for mod packs which wish to use trinkets for other reasons but want a harder balance in their packs.

I'd like to add that separate configuration for elytra enabled in cape slot and in chest slot would be ideal.
Specifically the configuration I'd use would be elytra only in chest slot, but cosmetics can be worn in cape slot.
So it'd be something like
capeSlot = true
elytraAllowedInCapeSlot = false
elytraAllowedInChestSlot = true

Is this issue still a thing?

the scope of the issue has slightly changed, in the 3.0.0 release of trinkets, it will not be a config option, but instead will simply not exist, making trinkets a pure api, I'll release a separate mod that has this behavior, it is currently like this on the 3.0.0 branch, but it's not released so I've not removed the issue

When are you going to release that? I need that for my mod ^^

When are you going to release that? I need that for my mod ^^

the 3.0.0 branch has this feature and will be the first release of 1.17

the 3.0.0 branch has this feature and will be the first release of 1.17

can u please release a fork for 1.16.4
i need this mod api for other mods but this feature causes problems with another mod
maybe not even a offical release just a fork u can only download from here

i also don't wanna have to delete my world when 1.17 comes cause this mod forces a update

i also don't wanna have to delete my world when 1.17 comes cause this mod forces a update

I mean, you should start over when moving to 1.17 anyway because of the massive changes to the world generation.


Fix #627, #654

Fix #627, #654.

Coverage decreased (-0.08%) to 96.541% when pulling 9bc728a3efab8e4d49f7ffac1c047eb70cfeb391 on jikamens:master into 4adba2e6ef8c8734a693af3141461dec6d674d50 on andrewplummer:master.

Coverage decreased (-0.08%) to 96.541% when pulling 9bc728a3efab8e4d49f7ffac1c047eb70cfeb391 on jikamens:master into 4adba2e6ef8c8734a693af3141461dec6d674d50 on andrewplummer:master.


remove GetUnsignedPipeline helper function and use var in each file

Changes
This commit is part of #5820. It removes the GetUnsignedPipeline helper function and use a var in each test file instead to improve the readability for developers.
No functional change.
/kind cleanup
Signed-off-by: Yongxuan Zhang<EMAIL_ADDRESS>
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[ ] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/lgtm

/test pull-tekton-pipeline-go-coverage


Cherry-pick change from v1.2.3 or apply a better fix

This PR #469 makes the active bids artworks rail visible, but it seems like this would apply to all rails, so see if there’s a bug elsewhere in the code that leads to this.

This got merged into master recently.


Focal length of the VLC cameras

Hi,
as part of my Master's thesis I'm trying to reconstruct a point cloud of the environment using the two front facing VLC cameras.[^note] So far I was already able to calculate a disparity map using OpenCV. However, I'm unable to calculate a corresponding depth image from the disparity map due to no information about the camera intrinsics (in my specific case the focal length) of the VLC cameras being available.
I am aware that the "HoloLens 2 Research Mode as a Tool for Computer Vision Research" paper explicitely states that "camera sensors do not directly expose instrinsics parameters" and that there are methods for converting between 3D coordinates and 2D image coordinates and the other way around. However, these methods are not of any help in this case. According to this tutorial, the disparity is equal to B * f / Z where B is the baseline distance between the two cameras, f is the focal length and Z is the corresponding depth. This equation only needs to be solved for Z in order to calculate the depth for a given pixel in the disparity map. While B can be calculated from the extrinsics of the two cameras, f is part of the camera intrinsics.
Considering that there is information available about the focal length of the RGB camera, why is there absolutely no information available at all about the focal length of the VLC cameras? Apparently, similar questions asking about camera intrinsics have come up over time, namely #34, #37 and #100. Some of these are now almost two years old and some of them could be solved by using the aforementioned conversion methods. However, these conversion methods are not of any help as I can't think of any way how these methods could be used for extracting the focal length. Has someone found some way of getting access to the intrinsics parameters?
[^note]: Yes, I am fully aware that the HoloLens 2 does offer a depth sensor which can be used for creating point clouds. In fact, I was already able to reconstruct point clouds which were then used for tracking moving objects. As part of my thesis, I should also use some of the other available sensors (e.g. the VLC cameras), which is why I wanted to try using the two front facing VLC cameras as a different source of generating point clouds.

I have alsos ended up estimating the intrinsics based on the method you mentioned above! I have also went through the standard chessboard calibrazion. The intrinsics I got has a really large variety based on the point pairs I had chosen or the images I had included in the calibration set. Below you'll find some values with different point pairs (u,v); x :(focus,principal).
(u1,v1)=(0,0)
(u2,v2)=(200,200)
x_l: array([385.01280587,<PHONE_NUMBER>6])
x_r: array([337.98439836,<PHONE_NUMBER>9])
(u1,v1)=(200,200)
(u2,v2)=(300,300)
x_l: array([376.48255277,<PHONE_NUMBER> ])
x_r: array([347.91297414,<PHONE_NUMBER>2])
(u1,v1)=(0,0)
(u2,v2)=(639,479)
x_l: array([369.26611797,<PHONE_NUMBER>6])
x_r: array([267.62356098,<PHONE_NUMBER>6])
(u1,v1)=(400,400)
(u2,v2)=(639,479)
x_l: array([369.26611797,<PHONE_NUMBER>6])
x_r: array([267.62356098,<PHONE_NUMBER>6])

This may be helpful too: https://github.com/microsoft/HoloLens2ForCV/issues/126


New Download Page

I was a GCI participant, but the contest is over now but saw the task to create this page.
The new features are:
-New download page
-with logos
-with shortened links
-...
-Updated the "Copyright year" in the footer to 2018
I haven't edited the javascript.

@phyyyl can you resolve the conflicts?

I resolved the conficts

Due to an error updating the main repository this pull request was inadvertently closed and will need to be resubmitted.


Is should be changed to ==

I changed my data ID, and finally I couldn't ack it

    def _find_item_id(self, item, search=True):
        if item is None:
            return None
        elif isinstance(item, dict) and "pqid" in item:
            return item.get("pqid")
        elif search:
            for key, value in self._unack_cache.items():
                if value is item:
                    return key
            log.warning("Can't find item in unack cache.")
        elif isinstance(item, int) or (
            isinstance(item, str) and item.isnumeric()
        ):
            return int(item)
        return None

value is item

value == item

warning Can't find item in unack cache.

What are you reporting?
Please provide a clear description + a complete minimal reproducible example.

What are you reporting?
Please provide a clear description + a complete minimal reproducible example.

Sorry, I made a mistake. I should report to other projects


On profile page, badges don't respect high-contrast setting

When high contrast is enabled, the badges on the user profile page still render non-high-contrast.
Repo:

Go to https://arcade.makecode.com
Sign in
Gear menu -> Enable high contrast
Profile menu -> My Profile
Notice the visible badges have the beige background color (non-high-contrast background):

Arcade: 1.8.30
OS: Windows 11
Browser: Chrome 104

I think the solution is to add the "high-contrast" css class to the <body> tag of the Arcade webapp when high contrast is enabled. That way, the setting will flow to all react-common components.

Fixed by https://github.com/microsoft/pxt/pull/9012


[BUG] ESP32 startup of OTA Requestor bits does not wait for kDnssdInitialized

Reproduction steps
In non-apple devices, the unique local address has higher score than the link local address. But the score might cause an issue. If the OTA Requestor applies the OTA image and reboot, after rebooting, it will send a NotifyUpdateApplied command to the Provider (Assuming the command is sent when the event kDnssdInitialized is post).
If the Provider has an ULA , and the requestor only gets its link local address (The requestor might not receive the RA message and add the ULA when it wants to send the command), the Provider is unreachable for the Requestor.
Here is my log.
ipaddr_resolve_issue.log
In the log, the device wants to send message to addr [FDDE:AD00:BEEF:DAD0:A276:4EFF:FE68:BF00] before it gets an IP address [fdde:ad00:beef:dad0:f612:faff:fe03:89dc].
Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
536a0d9b0f738ed79a939c638ef1bbfae3e7cf59
Platform
esp32
Platform Version(s)
No response
Anything else?
No response

Assuming the command is sent when the event kDnssdInitialized is post

This is odd.  After #25173 I would expect that kDnssdInitialized would not happen until we have an ipv6 address, for minimal mdns, which is what that log is using.
Is that logic failing somehow?  @wqx6 Could you check what's happening in the interface iteration there, if you can reproduce this every time?

So on ESP32 it looks like InitOTARequestorHandler is called off a timer via OTAHelpers::InitOTARequestor.  The timer is set for 3 seconds.
InitOTARequestor is called from any of the following cases:

kThreadConnectivityChange
event->InternetConnectivityChange.IPv4 == kConnectivity_Established
event->InternetConnectivityChange.IPv6 == kConnectivity_Established

None of that is waiting for kDnssdInitialized.  So that's the real issue here: instead of a hard-coded 3s wait, this should be waiting for kDnssdInitialized to have happened.

@wqx6 I expect https://github.com/project-chip/connectedhomeip/pull/25563 will fix this.

@bzbarsky-apple #25563 will not fix this issue, I met this issue even if I apply this patch. #25563 only fixes the issue the device might resolve no address. But my issue is that the device has resolve some IPv6 addresses, but sends the message to the wrong IPv6 address which is unreachable for the device at that time. Can we make the link local address have higher score than the ULA in https://github.com/project-chip/connectedhomeip/blob/master/src/lib/dnssd/IPAddressSorter.h#L46

But my issue is that the device has resolve some IPv6 addresses, but sends the message to the wrong IPv6 address which is unreachable for the device at that time.

Just to be clear, that's not what the attached log is showing, right?  I would be somewhat curious to see a log showing the failure after #25563 is applied.

Can we make the link local address have higher score than the ULA

I clearly think so, since the Apple case does this.  But there were objections to changing it in general, which is how we ended up with the ifdef....

Just to be clear, that's not what the attached log is showing, right?

This is what the attached log shows.
I (15847) chip[DIS]: UDP:[FE80::A276:4EFF:FE68:BF00%st1]:5540: new best score: 3
I (15847) chip[DIS]: UDP:[FDDE:AD00:BEEF:DAD0:A276:4EFF:FE68:BF00%st1]:5540: new best score: 4
I (15867) chip[DIS]: UDP:<IP_ADDRESS>%st1:5540: score has not improved: 2
I (15877) chip[DIS]: Checking node lookup status after 124 ms
I (15877) chip[DIS]: Keeping DNSSD lookup active
I (15947) chip[DIS]: Checking node lookup status after 200 ms
I (15957) chip[SC]: Initiating session on local FabricIndex 1 from 0x0000000000000002 -> 0x0000000000000001
I (16127) chip[EM]: <<< [E:11097i S:0 M:241576368] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
I (16147) chip[IN]: (U) Sending msg 241576368 to IP address 'UDP:[FDDE:AD00:BEEF:DAD0:A276:4EFF:FE68:BF00]:5540'
E (16147) chip[SVR]: Failed to establish connection to node 0x0000000000000001
I (18077) ROUTE_HOOK: Received RIO
I (18077) ROUTE_HOOK: prefix FD2A:48DF:CA8C:1:: lifetime 1800
I (19627) chip[DL]: IP_EVENT_GOT_IP6
I (19627) chip[DL]: IPv6 addr available. Ready on WIFI_STA_DEF interface: fdde:ad00:beef:dad0:f612:faff:fe03:89dc

The ULA FDDE:AD00:BEEF:DAD0:A276:4EFF:FE68:BF00 has higher score than LLA FE80::A276:4EFF:FE68:BF00 so the ESP32 sends message to the ULA but it has no route for the ULA before it gets IP address fdde:ad00:beef:dad0:f612:faff:fe03:89dc.

I would be somewhat curious to see a log showing the failure after #25563

A simple way to see the log after #25563

start and pair a lighting example
start and pair a light switch example
start a Thread BR on the same network
bind the light switch to the light
reboot the light switch

This is what the attached log shows.

Right, and that's showing the message being sent before IP_EVENT_GOT_IP6 happens.  That part should be prevented by https://github.com/project-chip/connectedhomeip/pull/25563; after that we should get IP_EVENT_GOT_IP6 and the IPv6 addr available. Ready on WIFI_STA_DEF interface: bits before we try sending the Sigma1 message.  Is that what you see?

that's showing the message being sent before IP_EVENT_GOT_IP6 happens
Before the error, the device gets a link local IP address, which triggers the DnssdInitialized event.

Ah, I see, there are two IP_EVENT_GOT_IP6.  Alright, yeah, then the options are only to either delay things until we are sure out addresses are set up or to change the prioritization.
I wonder whether we can somehow do the prioritization based on what sorts of addresses we have on the interface that the resolve was received on, so that we make sure to only use LL addresses if we ourselves only have an LL address, no matter what else we do with the priority.
Past that, @andy31415 had opinions on this, but I think he's on vacation right now...

@andy31415 Can we make some changes to the IP address score?

We could add more logic into https://github.com/project-chip/connectedhomeip/blob/master/src/lib/dnssd/IPAddressSorter.cpp#L44  (which is called from https://github.com/project-chip/connectedhomeip/blob/master/src/lib/address_resolve/AddressResolve_DefaultImpl.cpp#L120).
Overall the initial thought was that ULA are more likely to be "correct" compared to link local, however if we need to have more heuristics we could add/change thing with a comment explaining. I am all for doing what works best in more cases.

Close as #27981 merged


Can't resolve framework7/css/framework7.bundle.min.css

Hmm.. there are something missing in my modules
ERROR in ./src/main.js
Module not found: Error: Can't resolve 'framework7/css/framework7.bundle.min.css'
and there nothing file like framework7.bundle.min.css , or i missing something ?

after i read this https://blog.framework7.io/migration-to-framework7-v4-89d1ce49f4c0
I tried importing the previous css, which was .min.css, and it was running normally but not completely css loaded

Please check the latest 2.3.9 version!


Feature/change file structure

Thanks!
I only had a quick minute to look over it, but seems like a nice improvement! Should make it easier to add tests as well.
Just a couple things:
I'd like to avoid having lots of files pile up in the root directory, so perhaps we can make a folder called beszel or app in the root directory and move the application related code there.
Also, I noticed you accidentally committed an exe file. Sorry to ask you to do this, but I'd like to remove that from the git history. Not sure of the best way to do this. Maybe either git reset --soft and git push --force, or just making a fresh pull request.
Anyway, thanks again. I'll fiddle around with the workflows to make sure those will still work, then merge when I have a bit more time over the next few days.

Thanks!
I only had a quick minute to look over it, but seems like a nice improvement! Should make it easier to add tests as well.
Just a couple things:
I'd like to avoid having lots of files pile up in the root directory, so perhaps we can make a folder called beszel or app in the root directory and move the application related code there.
Also, I noticed you accidentally committed an exe file. Sorry to ask you to do this, but I'd like to remove that from the git history. Not sure of the best way to do this. Maybe either git reset --soft and git push --force, or just making a fresh pull request.
Anyway, thanks again. I'll fiddle around with the workflows to make sure those will still work, then merge when I have a bit more time over the next few days.

I removed the executable from the git history.
I didn't understand the second point. Do you want me to remove the 'internal', 'cmd', etc... folders from the project root or do you want me to remove the 'Dockerfile...' files or both?

Sorry,  I mean both.
This is more personal preference than common practice, but I'd like for the root directory to have fewer files and clear separation of purpose, rather than having everything intermingled at the base.
So I'd prefer to have the same files at the root as the repo currently has, but instead of individual folders for hub / agent, we just have one folder named beszel, and the code for the app lives there.
We can keep the structure that you have currently, it just goes in the beszel folder instead of the root.
If this still isn't clear -- and I understand why it may not be -- I can make a commit tomorrow that organizes that way.

I made some updates and submitted a pr on your fork.
If you think of any other changes, you can merge and update. Otherwise I can just continue working on the branch I checked out already.

For my part, I won't go into any further modifications or code slicing to avoid creating bugs where none exist.
Let me know when you want me to merge your modifications into the https://github.com/TOomaAh/beszel/pull/1 and I'll do it.

No worries, no need to merge if you're done. I'll close that pr and eventually merge this to main after I've had a bit more time to look it over and test workflows.


How to catch browser crashes

What are you trying to achieve?
How can we catch browser crashes without waiting for timeout?
Sometime the browser may crashes due to error in DOM or any other mysterious reasons. Is there a way to  catch those?
Details

Closing this one because if the browser crashes, it means the link between codeceptjs and the devtools is broken.
It is back when the page is reloaded, which would involved an external script to check if any browser crashes and reload it.