Add TRON staking messages

Description
Fixes #599

Testing instructions

Types of changes

Checklist

[x] Prefix PR title with [WIP] if necessary.
[x] Add tests to cover changes as needed.
[x] Update documentation as needed.

if possible, can we add some tests?


Add masked MSE loss

I noticed that you mask the outputs of the decoder, so there was no need to apply any more 'masking code'. Just in the calculation of the MSE I added a counter of the non-padded elements, changed the loss reduction to 'sum' and then divided with the counter.
Signed-off-by: njellinas<EMAIL_ADDRESS>

Just tried, get error TypeError: forward() missing 1 required positional argument: 'output_lengths'

In which point did it output this error? I put an extra argument in the Tacotron2Loss forward function, but I give it as x[-1] which are the output_lengths from parse_batch.

Trace
`TypeError                                 Traceback (most recent call last)
 in ()
307 create_mels()
308 train(output_directory, log_directory, checkpoint_path,
--> 309       n_gpus, rank, group_name, hparams, log_directory2, checkpoint_path_vanilla)
1 frames
 in train(output_directory, log_directory, checkpoint_path, n_gpus, rank, group_name, hparams, log_directory2, checkpoint_path_vanilla)
244             y_pred = model(x)
245
--> 246             loss = criterion(y_pred, y)
247             if hparams.distributed_run:
248                 reduced_loss = reduce_tensor(loss.data, n_gpus).item()
/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py in call(self, *input, **kwargs)
491             result = self._slow_forward(*input, **kwargs)
492         else:
--> 493             result = self.forward(*input, **kwargs)
494         for hook in self._forward_hooks.values():
495             hook_result = hook(self, input, result)
TypeError: forward() missing 1 required positional argument: 'output_lengths'`

I guess you have a different codebase because this line 307 create_mels() does not exist in the master branch. And wherever there is a criterion function I have put the last argument.
Or should I pull from a different branch than master?

Yes, I have my own modification (minor) of this repo.
(and I'm not a contributor or something, just tried to use your loss function).
Maybe couz I use fp16 train.
Here is the code.
https://colab.research.google.com/drive/1tBOXMBNbAkS-zHDIvP3hfFEUNf-kGosd

Oh OK then that makes sense. Look at the changes in the diffs, and apply them to your code. You are missing the last argument at criterion which must be the Mel lengths.

Oh, sorry, somehow I missed what i copy-pasted train file and just pulled your changes to my repo.

@njellinas Does adding the masked MSE loss improve the model? For example, time to learn attention or lower validation loss?


Git ssh secrets

https://harness.slack.com/archives/C01F359BV6U/p1686310850936539

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Update repositories.txt

I have added the required tag 1.0.0. Please re-review my library.

I have added the required tag 1.0.0. Please re-review my library.

I have added the required tag 1.0.0. Please re-review my library.

@ArduinoBot please check it again.
@benax-rw note the second half of the instructions from the bot:

, mentioning @ArduinoBot in the comment.


Question + Suggestion: No User Group has been Added

Hi @nathanwoulfe
Umbraco v10.5.1 with Clip v10.0.2.
I haven't set any rules at all and it seems (as an Admin) - I am unable to add any nodes whatsoever until I set the rules. Is this intended?
Maybe As an Admin, there shouldn't be any restrictions? or maybe an option as a tick box to allow everything for specific role?

Er, that's not as intended - with nothing set, it should do nothing...
Won't be a big deal to fix.

Issue here was a big complicated one - I hadn't published the latest version... I've pushed 10.1.0 and 11.1.0, which has a fix for the issue you found, plus some other improvements (now works with elements, adds some caching and actually has unit tests!)

Thanks @nathanwoulfe I'll give it a try and let you know if I find anything else.

@TRexStark my bad - releases were sitting in DevOps awaiting deployment. Have hit the button on both 10.1 and 11.1, will be on Nuget shortly.


Not loading..! (wrong-type-argument symbolp 'unity)

Debugger entered--Lisp error: (wrong-type-argument symbolp 'unity)
symbol-name('unity)

It looks like the installation instructions had a syntax error. I pushed a fix to the readme.


Render PDFs to bitmaps?

It doesn't appear that gofpdf includes FPDF's ability to render a PDF file to a bitmap. Am I missing something in that regard? I'm looking for something to open a PDF file, grab the first page, and generate a PNG it (via image.png.Encode()).

I think the confusion is that FPDF is similar in name to the FPDFSDK from Foxit. Google has an open source version written in C++: https://pdfium.googlesource.com/pdfium

So maybe I'm barking up the wrong tree?

This project writes PDFs only. It is not capable of opening and processing PDF files that already exist. As far as I know, its parent project, FPDF, is not related to the Foxit PDF SDK (fpdfsdk) despite the name confusion.
I can't see gofpdf ever having the capability of opening PDFs and parsing them. However, the idea of generating an image as output rather than a PDF is intriguing and worth looking into.
Also, a Go wrapper (using cgo) of the pdfium library could be useful. Thanks for that link.

@jung-kurt Cool. After searching for a few days, I don't see anything native in Go that does what I need, so I'm going to end up using a web-based API from Datalogics. However, if you consider building a wrapper for PDFium, do let me know; I'm more than happy to contribute however I can.
Since we have an internal project that could use this functionality at work, I may be able to use some "20% time" to work on it.
Thanks again.

Many thanks!

I have not had time to work on embedding PDFium. However, if your objective is to generate images or PDFs from vector graphics, you may want to look into draw2d.


[8.x] Share data between chained job classes

The initial PR with the full explanation was closed here: https://github.com/laravel/framework/pull/33251
It was initially thought it was needed also for closures, but the main support was for the job classes only.

I think it's better to implement it as a separate package.


Glue integration issues

I was unable to load a casa-image into glue, which suggests we have some holes to fix in both spectral-cube and glue-astronomy:
In [1]: from spectral_cube import SpectralCube

In [2]: cd /orange/adamginsburg/ALMAIMF_Images/G327.29/B6/linecubes_12m/
/orange/adamginsburg/ALMA_IMF/2017.1.01355.L/RestructuredImagingResults/G327.29/B6/linecubes_12m

In [3]: cube = SpectralCube.read('G327.29_B6_spw1_12M_sio.image.pbcor', format='casa_image')
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]

In [4]: dc['g327sio'] = cube
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_37871/376271071.py in <module>
----> 1 dc['g327sio'] = cube

~/.local/lib/python3.9/site-packages/glue/core/data_collection.py in __setitem__(self, key, data)
    397         if not isinstance(data, Data):
    398
--> 399             handler, preferred = data_translator.get_handler_for(data)
    400
    401             data = handler.to_data(data)

~/.local/lib/python3.9/site-packages/glue/config.py in get_handler_for(self, data_or_class)
    564                                 "type Data to {0}".format(data_or_class.__name__))
    565             else:
--> 566                 raise TypeError("Could not find a class to translate objects of "
    567                                 "type {0} to Data".format(data_or_class.__class__.__name__))
    568         return handler, preferred

TypeError: Could not find a class to translate objects of type DaskVaryingResolutionSpectralCube to Data

In [5]: cube.to_glue(name='sio', glue_app=application)
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
/tmp/ipykernel_37871/1811065730.py in <module>
----> 1 cube.to_glue(name='sio', glue_app=application)

/blue/adamginsburg/adamginsburg/repos/spectral-cube/spectral_cube/spectral_cube.py in to_glue(self, name, glue_app, dataset, start_gui)
   2400                     return self._glue_app
   2401
-> 2402             glue_app.add_datasets(self._glue_app.data_collection, result)
   2403
   2404

/blue/adamginsburg/adamginsburg/repos/spectral-cube/spectral_cube/spectral_cube.py in __getattribute__(self, attrname)
   3925             return self._handle_beam_areas_wrapper(origfunc)
   3926         else:
-> 3927             return super(VRSC, self).__getattribute__(attrname)
   3928
   3929     @property

AttributeError: 'DaskVaryingResolutionSpectralCube' object has no attribute '_glue_app'

The problem is that DaskSpectralCubes are not instances of SpectralCubes; they should be, I think?

Why is this False?
from spectral_cube import SpectralCube
cube = SpectralCube.read('/orange/adamginsburg/ALMAIMF_Images/G327.29/B6/linecubes_12m/G327.29_B6_spw1_12M_sio.image.pbcor', format='casa_image')

I've got a fix in progress, but I don't think glue can handle VaryingResolution objects yet

https://github.com/glue-viz/glue-astronomy/pull/54


[connectors] Refactor a few Zendesk activities return values

Description

Turn simple boolean into objects to name the values.

Risk
Low
Deploy Plan

Deploy connectors

PMRR, I actually need this since I forgot to bump the workflow version in the last PR.

👍🏻


Rebase mainline branch to make .git directory smaller

Hey team,
Due to the previous inclusion of the python venv files removed in #2, we have a .git directory that's 175MB large. This is probably fine for most folks with a high speed connection but we could improve developer experience during the cloning/forking process by rewriting the history for the repo's first commit.
Rewriting history in git can be a big deal if we have many changes and contributors. However, if we believe this repository will be here for the long term, it feels like a good thing to do now while its contributor list is small.
From this repo:
du -h -d 1 ./.git/objects/pack
175M	./.git/objects/pack

Example of another fprime repo:
du -h -d 1 ./.git/objects/pack
  0B	./.git/objects/pack

Thoughts?

This change looks good to me! I went ahead and made you a repo admin so you can do what needs to be done.

Done! 🙃
du -h -d 1 ./.git/objects/pack
612K	./.git/objects/pack


fix(ui): Upgrade cross-spawn to 7.0.5

Description
Upgrades cross-spawn to 7.0.5 in 4.4
yarn list output before:

├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>   └─<EMAIL_ADDRESS>
yarn list output after:

└─<EMAIL_ADDRESS>
User-facing documentation

[ ] CHANGELOG is updated OR update is not needed
[ ] documentation PR is created and is linked above OR is not needed

Testing and quality

[ ] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag
[ ] CI results are inspected

Automated testing

[ ] added unit tests
[ ] added e2e tests
[ ] added regression tests
[ ] added compatibility tests
[ ] modified existing tests

How I validated my change
Verify CI run

/test gke-ui-e2e-tests

/test ocp-4-12-ui-e2e-tests

/test ocp-4-11-ui-e2e-tests

/test gke-ui-e2e-tests

/test ocp-4-11-ui-e2e-tests

/retest


Feature Request: Decorator for methods for local macro-generated methods

I have a trait in an existing crate of mine that I'm trying to convert to an async-trait, but am running into a problem with the order in which proc macros and macro_rules macros are run. My code currently generates some methods for the trait impl using macros, like such:
macro_rules! generate_foo {
    () => {
        fn foo() {}
    }
}

trait Foo {
    fn foo();
}

struct Bar;

impl Foo for Bar {
    generate_foo!();
}

When I change foo to async fn foo in the trait, I get an issue because the async_trait proc macro runs before the generate_foo macro is expanded, so I end up with generated code like this:
#![feature(prelude_import)]
#[prelude_import]
use std::prelude::v1::*;
#[macro_use]
extern crate std;
use async_trait::async_trait;

macro_rules! generate_foo { () => { async fn foo() { } } }

trait Foo {
    #[must_use]
    fn foo<'async_trait>()
    ->
        ::core::pin::Pin<Box<dyn ::core::future::Future<Output = ()> +
                             ::core::marker::Send + 'async_trait>>;
}

struct Bar;

impl Foo for Bar {
    async fn foo() { }
}

I understand why this is happening and don't consider it a bug that async_trait needs to, or even could, fix, but I was wondering if there could be an attribute to put on methods that could perform the code generation? I.e., I could do something like the following:
macro_rules! generate_foo {
    () => {
        #[async_trait::async_method]
        async fn foo() { }
    }
}

struct Bar;

impl Foo for Bar {
    generate_foo!();
}

I would be willing to work on this feature, but I figured I would check and see if this was something useful to others.

When I change foo to async fn foo in the trait, I get an issue because the async_trait proc macro runs before the generate_foo macro is expanded, so I end up with generated code like this:

I think the correct way to do this is to generate the body of the method, not the method (async-trait modifies the method signature, but not the body):
macro_rules! generate_foo_body {
    () => {
        // ...
    };
}

#[async_trait]
trait Foo {
    async fn foo();
}

struct Bar;

#[async_trait]
impl Foo for Bar {
    async fn foo() {
        generate_foo_body!();
    }
}

playground
(if the method has arguments)

async-trait modifies the method signature, but not the body

Ah, this isn't strictly correct because async-trait actually replaces self argument and Self keyword. However, self argument can be passed as an argument to the macro, and use of Self keyword is can be avoided.

@taiki-e thanks, I'll give that a try

Another remark, for those facing with a similar problem:
You can always try to write functions that return a future (for example, a BoxFuture) in the generate_foo part.

Using the macro to generate just the body of the method isn't always satisfying, especially if the method signature itself is long and fiddly.
The most flexible fix would be some way to signal, "expand all the macros in here before applying #[async_trait]".
Does anyone know of a workaround?

I would prefer not to build anything for this into this crate, but it would be reasonable for somebody else to explore a more fully-featured macro in a different crate which handles this situation.


Docker pull in scoring

The docker pull failure can happen during ingestion or scoring. It looks like when this happens during scoring, it is written to ingestion_std_err instead of the scoring logs.
See this competition: https://www.codabench.org/competitions/1299/
Submission ID: 28129

Let's keep track of it here: #1205


fix test case failed

Changes Unknown when pulling<PHONE_NUMBER>b7e861aac22ff6d9f34e1cb8f311be on ascrutae:zhangxin/fix/fix-testcase into ** on wu-sheng:feature/new-id**.


google site liberation token not work

please help me, today, google sites liebration token not work, if i click get token, error page in my browser. please help me. thank you

I fixed it by reopening the setting of google development console.
It works now.


Wire up Change Rune Address flow for rFOX

https://www.figma.com/design/REOouo0sAuOhoD597yZEGE/rFOX?node-id=1-250&t=rKiPIPofUI4duT4G-0

check string entered is valid rune address, show error state if invalid
validate new address is not the same as the old address
all functionality in flow works, tested against live arb contracts

Note, this issue encapsulates both the visual bits and the wire-up bits. Initial visual bits have been started in https://github.com/shapeshift/web/pull/6959, to be continued either in https://github.com/shapeshift/web/pull/6963 or in a separate @reallybeard PR.


Error message string formatting

Error message finds error on line of code, but puts the next line of code on the same line
found in latest master branch

Can no longer reproduce. Closing.


ISPN-6606 Fix attributes names in remote-persistence schema

https://issues.jboss.org/browse/ISPN-6606

Looks good. Pulling ...

Integrated. Thanks @pruivo !


Improve ockam identity delete with --output json to fail right away if no confirmation is provide as an argument

Current behavior
If you run ockam identity delete <IDENTITY_NAME> --output json without -y / --yes flag then it prompts the user and asks for confirmation whether they should delete it or not.
This behavior is normally desirable (in interactive mode /w a user) except that --output json implies that this is meant to be run in a scripted environment where user interaction is unavailable.
Here's an example of this.

Desired behavior
Instead, if you run the above command without -y / --yes flag then the command should produce an error and exit with a non zero exit code.
Please take a look at this file to get started.

We love helping new contributors! ❤
If you have questions or need help as you explore, please join us on Discord. If you're looking for other issues to contribute to, please checkout our good first issues.

This behavior is normally desirable (in interactive mode /w a user) except that --output json implies that this is meant to be run in a scripted environment where user interaction is unavailable.

This part is not entirely correct. User interaction is detected by other means, and I'm not 100% sold on the assumption that using --output json implies that we are on a non-tty env.
I'd close this issue and think a better approach for this.


Add resourceid and ipaddress to managed private endpoint properties

Data Plane API - Pull Request
Add readonly fields for resourceId and ipAddress to managed private endpoint properties. The Synapse Studio already takes a dependency on these properties. Currently they show up as blank in the UI. We need to populate these values to unblock customers.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[X] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/synapse/data-plane/Microsoft.Synapse/stable/2020-12-01/managedPrivateEndpoints.json
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

Hi Swagger team,
I realize that this is a breaking change. But these 2 properties were accidentally missed in the original code. The UI displays the properties without any values. We need to fix this problem retroactively. Can you make an exception?
Before fix:
[A picture containing text, screenshot, software, computer icon  Description automatically generated]
After fix:
@.***
Thanks
Dushyant
From: openapi-workflow-bot[bot] @.>
Sent: Sunday, April 30, 2023 6:34 PM
To: Azure/azure-rest-api-specs @.>
Cc: Dushyant Bansal @.>; Mention @.>
Subject: Re: [Azure/azure-rest-api-specs] Add resourceid and ipaddress to managed private endpoint properties (PR #23773)
NewApiVersionRequired reason:
A service's API is a contract with customers and is represented by using the api-version query parameter. Changes such as adding an optional property to a request/response or introducing a new operation is a change to the service's contract and therefore requires a new api-version value. This is critically important for documentation, client libraries, and customer support.
EXAMPLE: if a customer calls a service in the public cloud using api-version=2020-07-27, the new property or operation may exist but if they call the service in a government cloud, air-gapped cloud, or Azure Stack Hub cloud using the same api-version, the property or operation may not exist. Because there is no clear relationship between the service api-version and the new property/operation, customers can't trust the documentation and Azure customer have difficulty helping customers diagnose issues. In addition, each client library version documents the service version it supports. When an optional property or new operation is added to a service and its Swagger, new client libraries must be produced to expose this functionality to customers. Without updating the api-version, it is unclear to customers which version of a client library supports these new features.

Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-rest-api-specs/pull/23773#issuecomment-1529234311, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHXBYLLW7QWTSTBXJD6WHDTXD4HG7ANCNFSM6AAAAAAXRJM4QY.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Connection state not updating when account starts being used elsewhere.

I want to be able to gracefully handle when a user (me) starts using Spotify on a different device. However, when monitoring the connection state, I notice that it doesn't change when I start using Spotify, from say, my phone and my program stops working (although it doesn't throw any errors). Is this a bug or is monitoring the connection state not the proper way to detect account use on other devices?

You should be listening for when the PLAY_TOKEN_LOSTsession event occurs like mopidy-spotify does.

Ahh, gotcha. Thank you very much for your help!


Bug Fix: Autocreating Fixtures

The method operation_create (and operation_delete) tries to assign the local_method of the operation element being created. However, this attribute doesn't exist during initialization -- it is initialized through the method: keyword, but is accessed in the element instance through local_method because method already means something in Ruby.

@jhlee-mitre I think I know why - by default, the TestScriptRunnable sets the client to localhost at initialization time. So, load_fixtures and autocreate_ids are handled when client is set to localhost. However, this changes at run time.


Problem: No test to validate duplicate inputs

Solution: Update tests to include a case wherein the same an input has been used more than once in the same transaction

Codecov Report

Merging #2425 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2425      +/-   ##
==========================================
+ Coverage   88.43%   88.48%   +0.04%
==========================================
  Files          39       39
  Lines        2275     2275
==========================================
+ Hits         2012     2013       +1
+ Misses        263      262       -1


Example fails at flash stage

Following the example, using latest docker container, I get the failure below. Any tips on how to resolve?
ESP-IDF v5.0-dev-3202-ga2d5041492
root@aa10bc75605c:~# ./flash.sh program/build/emulation.bin
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.00309 s, 1.4 GB/s
stat: cannot statx './program/build/bootloader/bootloader.bin': No such file or directory
dd: invalid number: ''
stat: cannot statx './program/build/partition_table/partition-table.bin': No such file or directory
dd: invalid number: ''
stat: cannot statx 'program/build/emulation.bin': No such file or directory
dd: invalid number: ''
root@aa10bc75605c:~#

I will test today and get back to you

@patrickomatik did you forget building the program perhaps?


I found an error in the official document

Fixes #3126
Changes proposed in this pull request:
-There is an error in official document.
-The document link is https://shardingsphere.apache.org/document/current/en/manual/sharding-jdbc/usage/encrypt/#rule-configuration-based-on-spring-boot
-spring.shardingsphere.props.query.with.cipher.comlum=true should change to spring.shardingsphere.props.query.with.cipher.column=true

Pull Request Test Coverage Report for Build 456

9728 of 14768 (65.87%)  changed or added relevant lines in 852 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-8.3%) to 65.872%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-api/src/main/java/org/apache/shardingsphere/api/config/sharding/TableRuleConfiguration.java
6
7
85.71%

sharding-core/sharding-core-api/src/main/java/org/apache/shardingsphere/api/sharding/complex/ComplexKeysShardingValue.java
0
1
0.0%

sharding-core/sharding-core-api/src/main/java/org/apache/shardingsphere/api/sharding/hint/HintShardingValue.java
0
1
0.0%

sharding-core/sharding-core-api/src/main/java/org/apache/shardingsphere/api/sharding/standard/PreciseShardingValue.java
0
1
0.0%

sharding-core/sharding-core-api/src/main/java/org/apache/shardingsphere/api/sharding/standard/RangeShardingValue.java
0
1
0.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/spi/NewInstanceServiceLoader.java
18
19
94.74%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/spi/algorithm/TypeBasedSPIServiceLoader.java
14
15
93.33%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/spi/database/H2DatabaseType.java
3
4
75.0%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/spi/database/OracleDatabaseType.java
2
3
66.67%

sharding-core/sharding-core-common/src/main/java/org/apache/shardingsphere/core/spi/database/PostgreSQLDatabaseType.java
2
3
66.67%

Totals

Change from base Build 6250:
-8.3%

Covered Lines:
9728

Relevant Lines:
14768

💛  - Coveralls

Sorry, I can't merge this pr because I don't know what is your actual changes.

There is not code change.It is an error in in the official document.I don't know if i made it clear?

@HongJinFeng You're requesting pull to the master branch from the dev branch, changing to dev may help


forgot-password-page-design

when we put the mobile number it takes me to otp page but returns back to enter number again mostly it is an issue of validateOTP boolen state please check that again

the otp page is taking multiple values in one single box and the didn't receive text under it should be in centre , fix those issues as well

the otp page is taking multiple values in one single box and the didn't receive text under it should be in centre , fix those issues as well

Working on the logic and validation for the forgot-password-page


Develop

Coverage decreased (-0.3%) to 82.898% when pulling 68c0ef656bc0b864acf77582e4e3856c73b38a22 on develop into 547471d1e8b8f867ec939eddae31f158e0a5eafe on qa.


Feat: do we fancy a native Astro integration?

Hey folks!
Similar to the Express and Next.js packages, do we want to have a native Astro integration package as part of the officially provided packages from Trigger.dev?
See the following resources for more context:

The Astro integration package: https://github.com/lirantal/triggerdev-astro-integration
An example Astro project built with the above integration package: https://github.com/lirantal/trigger.dev-astro-example

Of course, that would be amazing! Here's everything I can think of at the moment that would be nice to do to get astro support in (this isn't to say you should do these, just that they should be done at some point):

[ ] Add astro adapter package to packages in the monorepo as @trigger.dev/astro
[ ] Add example Astro project to the examples repo: https://github.com/triggerdotdev/examples
[ ] Add a Quick start guide to the Trigger.dev/docs
[ ] Add support for astro in @trigger.dev/cli init

Sounds like a good list. I might just tackle them as one-by-one PRs to make it scoped and easier to review and iterate while working to land these in officially.

@ericallam I think you can remove the bullet-list you created as I copied it over to my opening comment body as a tasklist so it is easier to track.
On that note, see first PR introduced for the astro package.

@lirantal I detailed in a github discussion here all the steps it would take to "officially" support another framework for Trigger.dev, thought you might find it interesting for the Astro work.

Looks like this is now already shipped thanks to:

[x] https://github.com/triggerdotdev/trigger.dev/pull/354
[x] https://github.com/triggerdotdev/trigger.dev/issues/452

So I'd imagine we can close?

@lirantal yep this is done, thanks a lot 🤩


Entity with battery_alert_disabled: true still notifies

Hi,
Thanks for this great package. Gives great insights on all of my battery powered devices!
I added information of my car to Home Assistant which also has some battery info which is irrelevant to be notified about. So I looked up the battery_alert_disabled: true customization, but I still receive notifications on the notify.notify notifier.
Example of my customize.yaml:
sensor.last_trip_average_electric_consumption:
  battery_alert_disabled: 'true'

Thanks for your help!

Hi, I'm experiencing the same, using:
sensor.car_charging_time_left:
  battery_alert_disabled: 'true'

No matter what I try, the notifications keep coming. Why isn't this working in my case? Any help is appreciated :)

Have you also deleted the battery sensor that was made?

Hi @whoisdecoy. Thanks for your help.
I tried to set the delete input field and ran the automation to delete, but this crashed my HA with error:
2021-01-06 08:35:19 ERROR (MainThread) [homeassistant.components.automation.delete_battery_sensor] delete_battery_sensor: Error executing script. Invalid data for call_service at pos 1: MQTT topic name/filter must not be empty. for dictionary value @ data['topic']
2021-01-06 08:35:19 ERROR (MainThread) [homeassistant.components.automation.delete_battery_sensor] While executing automation automation.delete_battery_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 433, in async_trigger
    await self.action_script.async_run(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1010, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 245, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 253, in _async_step
    await getattr(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 460, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1405, in async_call
    processed_data = handler.schema(service_data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: MQTT topic name/filter must not be empty. for dictionary value @ data['topic']

Hi @whoisdecoy. Thanks for your help.
I tried to set the delete input field and ran the automation to delete, but this crashed my HA with error:
2021-01-06 08:35:19 ERROR (MainThread) [homeassistant.components.automation.delete_battery_sensor] delete_battery_sensor: Error executing script. Invalid data for call_service at pos 1: MQTT topic name/filter must not be empty. for dictionary value @ data['topic']
2021-01-06 08:35:19 ERROR (MainThread) [homeassistant.components.automation.delete_battery_sensor] While executing automation automation.delete_battery_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 433, in async_trigger
    await self.action_script.async_run(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1010, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 245, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 253, in _async_step
    await getattr(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 460, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1405, in async_call
    processed_data = handler.schema(service_data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 272, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.8/site-packages/voluptuous/schema_builder.py", line 432, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: MQTT topic name/filter must not be empty. for dictionary value @ data['topic']

Did you modify the package at all? Any of the automations? Do you have all the automations turned on?
You can manually delete the MQTT sensor that is created and add the customize code to stop creation of the sensor again.

Did you modify the package at all? Any of the automations? Do you have all the automations turned on?
You can manually delete the MQTT sensor that is created and add the customize code to stop creation of the sensor again.

No @whoisdecoy , I haven't changed the package. All automations are enabled.
How can I manually delete the MQTT sensor? I think I need to get it out of the group.battery_status entity, but can't find out how.
Thanks!

No @whoisdecoy , I haven't changed the package. All automations are enabled.
How can I manually delete the MQTT sensor? I think I need to get it out of the group.battery_status entity, but can't find out how.
Thanks!

@whoisdecoy I've looked into my MQTT. I see some topics related to batteries, but not the one which notifies while the attribute is set. That entity also misses the attribute delete_battery_sensor, which I do see on other entities. So I'm confused now, why does it notify when there is no MQTT sensor? I see the entity that notifies in the list group.battery_status.

@whoisdecoy I've looked into my MQTT. I see some topics related to batteries, but not the one which notifies while the attribute is set. That entity also misses the attribute delete_battery_sensor, which I do see on other entities. So I'm confused now, why does it notify when there is no MQTT sensor? I see the entity that notifies in the list group.battery_status.

Somehow I fixed the issue. I've tried su much, not sure what fixed it. But after reinstalling the package the entity customization was cleared. So I've added the fields again and since there were no notifications on these entities.

Somehow I fixed the issue. I've tried su much, not sure what fixed it. But after reinstalling the package the entity customization was cleared. So I've added the fields again and since there were no notifications on these entities.


This is not open source.

Much better alternative https://www.npmjs.com/package/exceljs


Updating Raspberry Pi 3 on unstable channel fails with assembler errors trying to compile the kernel (aarch64)

Describe the bug
Running nixos-rebuild switch --upgrade on rpi3 leads to compiling the kernel which fails. Here is the partial log:
$ nix-store --read-log /nix/store/4sg3mwn19561m86c568iknh3bfqcjp03-linux-5.4.drv
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/476gpxsc3h1v6qhfxf706n85llc6l5km-linux-5.4.tar.xz
source root is linux-5.4
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file linux-5.4/virt/lib/irqbypass.c
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
stripping FHS paths in `./certs/Makefile'...
...
make[1]: Leaving directory '/build/linux-5.4/build'
@nix { "action": "setPhase", "phase": "buildPhase" }
building
build flags: -j4 -l4 SHELL=/nix/store/bk9y5mzvj50snn0kr02k9fw6pffmz9z6-bash-4.4-p23/bin/bash O=\$\(buildRoot\) CC=/nix/store/nalgbdpjmhizap3sp1q3lqinisifld
l9-gcc-wrapper-8.3.0/bin/cc HOSTCC=/nix/store/nalgbdpjmhizap3sp1q3lqinisifldl9-gcc-wrapper-8.3.0/bin/cc ARCH=arm64 KBUILD_BUILD_VERSION=1-NixOS Image vmlin
ux modules KBUILD_BUILD_TIMESTAMP=Mon\ Nov\ 25\ 00:32:01\ UTC\ 2019
  GEN     Makefile
...
  CC [M]  crypto/aegis128-neon-inner.o
  CC      drivers/acpi/acpica/dsopcode.o
  CC      drivers/acpi/acpica/dspkginit.o
/build/ccWbaIVS.s: Assembler messages:
/build/ccWbaIVS.s:50: Error: selected processor does not support `aese v7.16b,v1.16b'
/build/ccWbaIVS.s:51: Error: selected processor does not support `aesmc v7.16b,v7.16b'
/build/ccWbaIVS.s:54: Error: selected processor does not support `aese v8.16b,v1.16b'
/build/ccWbaIVS.s:55: Error: selected processor does not support `aesmc v8.16b,v8.16b'
/build/ccWbaIVS.s:62: Error: selected processor does not support `aese v15.16b,v1.16b'
...
/build/ccWbaIVS.s:1663: Error: selected processor does not support `aesmc v0.16b,v0.16b'
make[2]: *** [../scripts/Makefile.build:266: crypto/aegis128-neon-inner.o] Error 1
make[1]: *** [/build/linux-5.4/Makefile:1652: crypto] Error 2
make[1]: *** Waiting for unfinished jobs....
....

To Reproduce
Steps to reproduce the behavior:

Rpi3 on unstable channel
nixos-rebuild switch --upgrade

Metadata
Please run nix run nixpkgs.nix-info -c nix-info -m and paste the result.

system: "aarch64-linux"
host os: Linux 5.2.9, NixOS, 19.09pre190687.3f4144c30a6 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
channels(root): "nixos-20.03pre203172.0ee0489d42e"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: linux
# a list of nixos modules affected by the problem
module:

https://github.com/NixOS/nixpkgs/commit/0e670a2e678ae8d23694d20848c558a3f17251f9 fixes the issue.


remove deprecated const EOL in AbstractHtmlElement

This repository has been closed and moved to laminas/laminas-view; a new issue has been opened at https://github.com/laminas/laminas-view/issues/14.

This repository has been moved to laminas/laminas-view. If you feel that this patch is still relevant, please re-open against that repository, and reference this issue. To re-open, we suggest the following workflow:

Squash all commits in your branch (git rebase -i origin/{branch})
Make a note of all changed files (`git diff --name-only origin/{branch}...HEAD
Run the laminas/laminas-migration tool on the code.
Clone laminas/laminas-view to another directory.
Copy the files from the second bullet point to the clone of laminas/laminas-view.
In your clone of laminas/laminas-view, commit the files, push to your fork, and open the new PR.
We will be providing tooling via laminas/laminas-migration soon to help  automate the process.


[5.1] Better "random" function

It's important Laravel is constantly audited for security. Thank you to @0xbb for making us aware that our random function is poor. Provided @taylorotwell is happy with this implementation, this can be backported to previous Laravel releases as he sees fit (happy now @JosephSilber :P).
Ping @ircmaxell. Please could you review this please? It's very important that this function is secure.

Replaces #9029 and #8991.

If it's really important, why not rely on a tested/proven library, like http://symfony.com/doc/current/components/security/secure_tools.html or https://github.com/ircmaxell/RandomLib ?

Yeah I'd rather have Laravel use Symfony's function too

Er, yeah, let's just Symfony's SecureRandom stuff.

Er, yeah, let's just Symfony's SecureRandom stuff.

Symfony doesn't do random strings like this though...

Symfony doesn't have this function, so what are we supposed to do?

Then let's use Anthony's RandomLib as barry suggested.

I'll prep another PR.

All in all I think its fine to just use Symfony's function (considering you're already binding to the FW).
You're generating strings of a specific character set, not multiple. And considering over-generation (2x length) isnt bad, but is also more performant than calling a generation for every single character without being any more secure, just do that.
In that the original algorithm in the code is fine (substr(strtr(base64_decode(...)))), just switch the initial buffer generation to use Symfony's and be done.

@ircmaxell Is there any chance you could send a PR to the 5.1 branch please as you'll probably do a better job than me? :)

@GrahamCampbell for a few reasons I can't. I can help review. But basically take the original and just port out the generation step...

Ok, thank you. I'll prep another PR, then let you know. :)

@ircmaxell I've had a chat with Taylor about this, and we've decided not to adopt symfony because it's no better than our implementation. We do, however keep an eye on it, and other implementations incase new security recommendations arise. We have, however, tweaked our implementation to ensure it's secure, and also, to make sure that we're actually guaranteed a string of the correct length.
    public static function random($length = 16)
    {
        if (function_exists('random_bytes')) {
            $bytes = random_bytes($length * 2);
        } elseif (function_exists('openssl_random_pseudo_bytes')) {
            $bytes = openssl_random_pseudo_bytes($length * 2, $strong);
            if ($bytes === false || $strong === false) {
                throw new RuntimeException('Unable to generate random string.');
            }
        } else {
            throw new RuntimeException('OpenSSL extension is required for PHP 5 users.');
        }

        $string = substr(str_replace(['/', '+', '='], '', base64_encode($bytes)), 0, $length);

        while (($len = strlen($string)) < $length) {
            $string .= static::random($length - $len);
        }

        return $string;
    }

How does that look now?

Well we mainly didn't use Symfony because it falls back to a more insecure algorithm whereas we prefer to always use OpenSSL and fail otherwise.

Yeh. :)

Isn't OpenSSL always available anyways because you require the openssl extension in composer?

Yes it should be. I don't think we used to require it via Composer.
On Wed, Jun 3, 2015 at 11:49 AM, Barry vd. Heuvel<EMAIL_ADDRESS>wrote:

Isn't OpenSSL always available anyways because you require the openssl
extension in composer?
—
Reply to this email directly or view it on GitHub
https://github.com/laravel/framework/pull/9031#issuecomment-108520531.

I don't think we used to require it via Composer.

laravel/framework requires it, but illuminate/support doesn't. That's why we've got that check. :)

Personally, since PHP does not have tail recursion, would rather see the entire function block be in a do/while rather than just recursion. That way you use a consistent stack space (granted, it's exceedingly unlikely to run once, yet-alone enough to stack overflow. But it's possible.

@ircmaxell Good point. Thank you. :)

@ircmaxell Ok, so our random functions now look like this:
    /**
     * Generate a more truly "random" alpha-numeric string.
     *
     * @param  int  $length
     * @return string
     *
     * @throws \RuntimeException
     */
    public static function random($length = 16)
    {
        $string = '';

        while (($len = strlen($string)) < $length) {
        	$size = $length - $len;
            $bytes = static::randomBytes($size * 2);
            $string .= substr(str_replace(['/', '+', '='], '', base64_encode($bytes)), 0, $size);
        }

        return $string;
    }

    /**
     * Generate a more truly "random" bytes.
     *
     * @param  int  $length
     * @return string
     *
     * @throws \RuntimeException
     */
    public static function randomBytes($length = 16)
    {
        if (function_exists('random_bytes')) {
            $bytes = random_bytes($length);
        } elseif (function_exists('openssl_random_pseudo_bytes')) {
            $bytes = openssl_random_pseudo_bytes($length, $strong);
            if ($bytes === false || $strong === false) {
                throw new RuntimeException('Unable to generate random string.');
            }
        } else {
            throw new RuntimeException('OpenSSL extension is required for PHP 5 users.');
        }

        return $bytes;
    }


significant slowdown calculating complements

[@jvasileff] Narrowing operations involving several cases can be quite slow. Using the test program:
import ceylon.ast.core {
    Node
}

Anything slowness1(String|Node node)
    =>  if (is String node) then null else null;
    //{ if (is String node) { return null; } else { return node; }

Anything slowness2(String|Node node)
    =>  if (is String node) then null else null;
    //{ if (is String node) { return null; } else { return node; }

Anything slowness3(String|Node node)
    =>  if (is String node) then null else null;
    //{ if (is String node) { return null; } else { return node; }

Anything slowness4(String|Node node)
    =>  if (is String node) then null else null;
    //{ if (is String node) { return null; } else { return node; }

void load(Node n) {}

abstract class Foo() {}

abstract class Enum() of
A | B | C | D | E | F | G | H | I | J |
K | L | M | N | O | P | Q | R | S | T {}

class A() extends Enum() {} class B() extends Enum() {}
class C() extends Enum() {} class D() extends Enum() {}
class E() extends Enum() {} class F() extends Enum() {}
class G() extends Enum() {} class H() extends Enum() {}
class I() extends Enum() {} class J() extends Enum() {}
class K() extends Enum() {} class L() extends Enum() {}
class M() extends Enum() {} class N() extends Enum() {}
class O() extends Enum() {} class P() extends Enum() {}
class Q() extends Enum() {} class R() extends Enum() {}
class S() extends Enum() {} class T() extends Enum() {}

I'm getting the following timings on my laptop:
slownessx(String|Node) (as shown above)
$ time ceylon compile-js --suppress-warning
Note: Created module simple/1.0.0

real	0m24.732s
user	0m32.355s
sys	0m0.610s

slownessx(String|Enum)
$ time ceylon compile-js --suppress-warning
Note: Created module simple/1.0.0

real	0m3.796s
user	0m9.294s
sys	0m0.295s

slownessx(String|Foo)
$ time ceylon compile-js --suppress-warning
Note: Created module simple/1.0.0

real	0m1.872s
user	0m4.039s
sys	0m0.232s

And with the slownessx functions commented out:
$ time ceylon compile-js --suppress-warning
Note: Created module simple/1.0.0

real	0m1.788s
user	0m3.924s
sys	0m0.226s

[Migrated from ceylon/ceylon-spec#1394]

This problem is substantially alleviated by https://github.com/ceylon/ceylon/commit/775eff799db59c7d565853eb6629bc49d8a58e3d (caching the union of cases for a Type).

Thanks Gavin. After some testing, it looks like 775eff7 (the "patch") solves the performance bug for moderate uses of Node.
I had previously changed some code (the "workaround") to help with this issue. Testing with and without the patch and workaround, the timings below are the number of seconds for the Eclipse editor to display or hide an error after making a one character change to an unrelated portion of the file:
| Patch | No Patch
--- | --- | ---
Workaround | < 2s | 8s
No Workaround | <4s | 25s

Now, what's very interesting, is that after saving all files, and after a full rebuild, positioning the cursor after "" in the code below
void f() {
    value s = "";
}

and pressing ctrl-space, there is a black-and-white-static-spinner-hang of exactly the same 2, 4, 8, and 25 second durations!

That's right, because invoking autocompletion forces a synchronous type check of the file. I wonder if that can be optimized away somehow...
Sent from my iPhone

On 30 Apr 2016, at 00:46, John Vasileff<EMAIL_ADDRESS>wrote:
Now, what's very interesting, is that after saving all files, and after a full rebuild, positioning the cursor after "" in the code below
void f() {
value s = "";
}
and pressing ctrl-space, there is a black-and-white-static-spinner-hang of exactly the same 2, 4, 8, and 25 second durations!
—
You are receiving this because you were assigned.
Reply to this email directly or view it on GitHub

@jvasileff could you do me a favor and try these two commits to see if either of them makes a difference to performance:

https://github.com/ceylon/ceylon/tree/possible_opt2
https://github.com/ceylon/ceylon/tree/possible_opt

Thanks!

@gavinking I'm not seeing a difference at all.
I tested the old master (pre-caching), and the two new branches after rolling back 775eff799
jvasileff@lynx:simple$ for x in 20160429 20160430-opt1 20160430-opt2; do time ~/Dropbox/Builds/ceylon-${x}/bin/ceylon compile-js ; done
Note: Created module simplebug/1.0.0

real	0m23.340s
user	0m26.277s
sys	0m0.243s
Note: Created module simplebug/1.0.0

real	0m23.425s
user	0m26.505s
sys	0m0.241s
Note: Created module simplebug/1.0.0

real	0m23.274s
user	0m26.342s
sys	0m0.231s
jvasileff@lynx:simple$

For reference, the following is with 775eff799
jvasileff@lynx:simple$ time ~/Dropbox/Builds/ceylon-20160429-cache-just-one/bin/ceylon compile-js
Note: Created module simplebug/1.0.0

real	0m7.689s
user	0m10.561s
sys	0m0.214s
jvasileff@lynx:simple$

OK, so they're useless. Fine. Then I can't see any other obvious way to optimize getUnionOfCases(). Perhaps if you run it through a profiler, you might turn up some hotspot that I have not thought of...

optimize getUnionOfCases()

This will be interesting to explore in my ceylon-ceylon-model project once I'm a bit further along.
BTW, it's completely subjective, but it seems that 775eff7 has really improved Eclipse responsiveness when working with large files that make heavy use of enumerated types that aren't as crazy as Node, even if the improvement doesn't show up in CLI compiles. I'm using a custom 1.2.2 build.

Excellent :-)

The patch below makes a massive difference compiling the code in the issue description.
diff --git a/model/src/com/redhat/ceylon/model/typechecker/model/UnionType.java b/model/src/com/redhat/ceylon/model/typechecker/model/UnionType.java
index 5cf2453..e976550 100644
--- a/model/src/com/redhat/ceylon/model/typechecker/model/UnionType.java
+++ b/model/src/com/redhat/ceylon/model/typechecker/model/UnionType.java
@@ -152,21 +152,12 @@ public class UnionType extends TypeDeclaration {
             return true;
         }
         else {
-            //this loop is intended as a performance
-            //optimization, but it doesn't actually
-            //seem to help at all really
-            /*for (Type ct: getCaseTypes()) {
+            for (Type ct: getCaseTypes()) {
                 if (!ct.getDeclaration().inherits(dec)) {
                     return false;
                 }
-            }*/
-            //have to resolve aliases here or the build of
-            //ceylon.ast is really slow / nonterminating
-            Type st =
-                    getType()
-                        .resolveAliases()
-                        .getSupertype(dec);
-            return st!=null && !st.isNothing();
+            }
+            return true;
         }
     }

Results:
jvasileff@orion:simple$ time ~/Dropbox/Builds/ceylon-20160503-master/bin/ceylon compile
Note: Created module simplebug/1.0.0

real	0m5.282s
user	0m8.011s
sys	0m0.194s
jvasileff@orion:simple$ time ~/Dropbox/Builds/ceylon-20160503-opt-union-inherits/bin/ceylon compile
Note: Created module simplebug/1.0.0

real	0m3.327s
user	0m5.901s
sys	0m0.192s
jvasileff@orion:simple$

For reference, here's a comparison without the previous cache optimization:
jvasileff@orion:simple$ time ~/Dropbox/Builds/ceylon-20160429/bin/ceylon compile
Note: Created module simplebug/1.0.0

real	0m16.433s
user	0m19.727s
sys	0m0.275s
jvasileff@orion:simple$ time ceylon compile
Note: Created module simplebug/1.0.0

real	0m7.960s
user	0m11.806s
sys	0m0.261s
jvasileff@orion:simple$

@jvasileff I'm very surprised to see that your proposed change doesn't seem to break anything. And I can't come up with any reason why it should have.
So I have pushed that change here https://github.com/ceylon/ceylon/commit/2b31ae21242ece49269bb57f2576605e30c2797f.

Ok, great. If there is a problem, hopefully I'll find it while working on the port.


Handle mask in TimeDistributed wrapper.

This PR aims to add proper support of mask in TimeDistributed wrapper layer. Several previous PRs have raised questions about this or have attempted to solve it, but I didn't find any perfect solution so far. I may not be able to have a perfect one either but am willing to improve it. The most frequent usage of such layers with masking support might be a hierarchical RNN on a sentence with words with characters, or a paragraph with sentences with words. (E.g., models like this).
Here are the main ideas/purposes of this pr:

For layers like TimeDistributed(Embedding(..., mask_zero=True)) or TimeDistributed(Masking(...)), the layer should call compute_mask() at each time step and stack them.
For layers like TimeDistributed(LSTM(...)), the input_mask should be split and fed into the LSTM layer at each time step. And if the output_shape changes (e.g., return_sequences=False in LSTM), the output_mask of the TimeDistributed layer should also change correspondingly.
The TimeDistributed layer should support, e.g., input_shape=(None, None). For example, the number of words in a sentence and the number of characters in a word can be different from sample to sample. Currently the TimeDistributed can only support one unspecified input dimension.

Here are some details of this PR to discuss, which might have better solutions:

K.int_shape() may not be available for some mask with Theano backend, especially when the inner layer is Embedding or Masking. This is because _keras_shape is not set in lots of operations in theano_backend if the tensor shape is not changed. I manually create the _keras_shape in compute_mask of these two layers.
When input_shape[0] is not None in TimeDistributed layer, we need to use K.rnn() to dynamically call the inner layer. Because K.rnn() can only take 1 tensor input but we need to feed both input and mask, I didn't do anything in this situation. Probably we can pass all mask as constants to K.rnn() but I was expecting better solutions.
If there's None from the output of K.int_shape, we need to replace it by the output from K.shape, so that reshape can be correctly called.

Thanks for the comments! I made some corresponding changes in the new commit.


Example has single volume, but multiple volumes field name.

It makes sense to deprecate volume in favor of volumes in the future.
Not sure what the motivation is for this change, but if the goal is to make all the examples consistent I'd recommend we go with volumes.

@keithchambers The example was incorrect, and I went with the simplest change to make it correct (volumes -> volume).

IIRC the reason for having volume was for simplifying the common case where tasks only needed a single volume. This is as opposed to say ports where 1. multiple of them is more common 2. the names are significant and are used for identifying the port


Merge develop into master to release

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

GitHub release
v1.0.1

Your semantic-release bot :package::rocket:


Move deprecation document to Eng hub site

https://dev.azure.com/azure-sdk/internal/_wiki/wikis/internal.wiki/192/Azure-SDK-deprecation-strategy

FYI @ladonnaq

@MrJustinB there was a reason we didn't migrate the deprecation doc when we did the mass migration from the wiki to Eng hub, but I don't remember what the reason was. Do you?

@mario-guerra I am often asked by service partner what the process/steps they need to take to deprecate their APIs and SDKs.  I think it would be very helpful to move the relevant information from this doc to engineering hub.

Okay, I can certainly do that. Where on eng hub do you think it makes the most sense to put it?
From: La Donna Quinn @.>
Sent: Tuesday, April 9, 2024 3:20 PM
To: Azure/azure-sdk-tools @.>
Cc: Mention @.>; Comment @.>; Assign @.***>
Subject: Re: [Azure/azure-sdk-tools] Move deprecation document to Eng hub site (Issue #7577)
@mario-guerrahttps://github.com/mario-guerra I am often asked by service partner what the process/steps they need to take to deprecate their APIs and SDKs. I think it would be very helpful to move the relevant information from this doc to engineering hub.

Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-tools/issues/7577#issuecomment-2045983839 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUNOJ7PNMJRKDF4TP3TRDTDY4REN5BFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2DEOBVGA2DKNBXGGSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJRG4YDKOJSGE4DNAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMBZG4YDOMBRHAZYFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI2DEOBVGA2DKNBXGGTXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@maririos Retirement should have its own section on engineering hub.  Can we add a top-level category for Retirement? Perhaps in between "Develop SDKs" and "Support".  If you agree, then @mario-guerra can add the section and start rewriting the docs. We can also cross-reference the links to Azure Docs (ARM, APEX program includes retirement, etc).

PR: https://dev.azure.com/azure-sdk/internal/_git/azure-sdk-docs-eng.ms/pullrequest/962

Docs live: https://eng.ms/docs/products/azure-developer-experience/develop/sdk-deprecation-guidelines

Old wiki doc updated to point to new place.


Chain filtering is leaking

Describe the bug
As there's no support for lists within dataset fields, I convert my lists to json-string format. However, the bug described is occurring even when the data format is 'string'.
These samples show that filtering behavior diverges from what's expected when chaining filterings.
On sample 2 the second filtering leads to "leaking" of data that should've been filtered on the first filtering into the results.
Steps to reproduce the bug
Sample 1:
import datasets
import json

items = [[1, 2], [3], [4]]
jsoned_items = map(json.dumps, [[1, 2], [3], [4]])
ds = datasets.Dataset.from_dict({'a': jsoned_items})
print(list(ds))
# > Prints: [{'a': '[1, 2]'}, {'a': '[3]'}, {'a': '[4]'}] as expected

filtered = ds

# get all lists that are shorter than 2
filtered = filtered.filter(lambda x: len(json.loads(x['a'])) < 2, load_from_cache_file=False)
print(list(filtered))
# > Prints: [{'a': '[3]'}, {'a': '[4]'}] as expected

# get all lists, which have a value bigger than 3 on its zero index
filtered = filtered.filter(lambda x: json.loads(x['a'])[0] > 3, load_from_cache_file=False)
print(list(filtered))
# > Should be: [{'a': [4]}]
# > Prints: [{'a': [3]}]

Sample 2:
import datasets
import json

items = [[1, 2], [3], [4]]
jsoned_items = map(json.dumps, [[1, 2], [3], [4]])
ds = datasets.Dataset.from_dict({'a': jsoned_items})
print(list(ds))
# > Prints: [{'a': '[1, 2]'}, {'a': '[3]'}, {'a': '[4]'}]

filtered = ds

# get all lists, which have a value bigger than 3 on its zero index
filtered = filtered.filter(lambda x: json.loads(x['a'])[0] > 3, load_from_cache_file=False)
print(list(filtered))
# > Prints: [{'a': '[4]'}] as expected

# get all lists that are shorter than 2
filtered = filtered.filter(lambda x: len(json.loads(x['a'])) < 2, load_from_cache_file=False)
print(list(filtered))
# > Prints: [{'a': '[1, 2]'}]
# > Should be: [{'a': '[4]'}] (remain intact)

Expected results
Expected and actual results are attached to the code snippets.
Actual results
Expected and actual results are attached to the code snippets.
Environment info

datasets version: 1.12.1
Platform: Windows-10-10.0.19042-SP0
Python version: 3.9.7
PyArrow version: 5.0.0

Update:
I wrote an even cleaner code snippet (without jsoning) that can expose leaking.
import datasets
import json

items = ['ab', 'c', 'df']

ds = datasets.Dataset.from_dict({'col': items})
print(list(ds))
# > Prints: [{'col': 'ab'}, {'col': 'c'}, {'col': 'df'}]

filtered = ds

# get all items that are starting with a character with ascii code bigger than 'a'
filtered = filtered.filter(lambda x: x['col'][0] > 'a', load_from_cache_file=False)
print(list(filtered))
# > Prints: [{'col': 'c'}, {'col': 'df'}] as expected

# get all items that are shorter than 2
filtered = filtered.filter(lambda x: len(x['col']) < 2, load_from_cache_file=False)
print(list(filtered))
# > Prints: [{'col': 'ab'}] -> this is a leaked item from the first filter
# > Should be: [{'col': 'c'}]

Thanks for reporting. I'm looking into it

I just pushed a fix ! We'll do a new release soon.
In the meantime feel free to install datasets from source to play with it

Thanks, I'm already using it from your branch!


Documentation improvements

I am new to using vue-maplibre-gl and maplibre-gl, I tried to refer to the documentation of this package to understand the structure and props of components, but unfortunately the documentation seems too empty, for example I wanted to add a base raster layer to override the base vector, but I did not find an example. Still, I managed to output the raster layer (but it is not clear yet how to remove the base vector). And it seems not obvious that MglRasterLayer should be placed inside MglRasterSource, since this is not described anywhere.
Let me know if all this is described somewhere, and I am not looking well

Hi,
I agree that the documentation on source and layers is quite poor. I'll try to improve it in the future.
There is one example with multiple source and layers here: https://indoorequal.github.io/vue-maplibre-gl/examples/playground.html


chore: Fix warning when building macOS version

This one annoyed me a lot and was easy to fix :-)

bors r+


Upgrade to viem/wagmi 2

Upgrading will help fix the below issue

noticing that we are using useContractWrite without usePrepareContractWrite whereas the docs recommend highluy using usePrepareContractWrite for wagmi 1.0

so we should we should use it or move to wagmi 2.0 where its no longer needed

Originally posted by @aaronmgdr in https://github.com/celo-org/staked-celo-web-app/issues/238#issuecomment-1953829376

done


Unclear whether the tool doesn't run on Sonoma, or I'm doing something wrong.

Hi,
installed the tool without any issues, gave it all the permissions it needed, but I struggle to follow the usage instructions.
If I type with my MacBook's inbuilt keyboard, and set the input source from the menu icon, this doesn't seem to affect the UserDefaults values. Am I doing something wrong? Does the "Usage Instructions" section need to be followed in a particular way?
P.S. I'm using an MX Keys, and I'm aware there are some issues with that, but already the ability to autoswitch when I'm using the inbuilt keyboard would be great for my use.
Thanks!

You could try the following procedure (adapted from yours, to be sure start autokbisw from the command line again and monitor the verbose output like you did before):
Opened textedit
typed random stuff on the inbuilt keyboard
switched the input language to italian
(new) typed random stuff on the inbuilt keyboard
typed random stuff on secondary keyboard
switched the language to English
(new) typed random stuff on secondary keyboard
That should absolutely work from my unterstanding.
If it doesn't (please paste the output from the command line here, a single keystroke is enough for switching keyboards), it may be a permissions issue. Did you try the following?

Re-grant the required privileges to the service by removing and re-adding the executable under System Preferences > Security & Privacy > Privacy > Input Monitoring. The path to add should either be /usr/local/bin/autokbisw (on Intel Macs) or /opt/homebrew/opt/autokbisw/bin/autokbisw (on Apple M1 Macs).

Hi @ohueter, I have followed the guide you provided (both for setup and for re-assigning permissions) and neither worked.
However, when I went to the command line to paste the output for you to look at, it exhibited a behaviour it never exhibited before.
As soon as I launch autobfsw with verbosity 2, the first keystroke I press on my inbuilt keyboard changes the input source to GB. From that moment on, no other keystroke changes it, not even if I manually revert it to Italian.
However, this behaviour is reproducible, because if I "exit" verbose mode, and I re-enter it, the first keystroke on my inbuilt keyboard will retriever the input source to GB.

Starting with useLocation: false - verbosity: 2
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
hreceived event from keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT] - 51 -<PHONE_NUMBER>
set input source to <TSMInputSource 0x600003b7b480> KB Layout: British (id=2) for keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT]
received event from keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT] - 51 -<PHONE_NUMBER>
received event from keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT] - 51 -<PHONE_NUMBER>
received event from keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT] - 51 -<PHONE_NUMBER>
received event from keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT] - 51 -<PHONE_NUMBER>
received event from keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT] - 51 -<PHONE_NUMBER>
received event from keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT] - 51 -<PHONE_NUMBER>
received event from keyboard Apple Internal Keyboard / Trackpad-[1452-835-Apple Inc.-FM7231300VENX0QAN+EBT] - 51 -<PHONE_NUMBER>
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
dreceived event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse
received event from keyboard MX Keys-[1133-45915-Logitech-5F82F70C668EE4A6] -<PHONE_NUMBER> -<PHONE_NUMBER>
ignoring event as device is a mouse

Hi Niccolo,
I'm sorry but it seems like you're affected from the MX keyboard issue. autokbisw has saved the GB layout for your internal keyboard and sets (restores) it when you start typing on it. It doesn't change when you start typing on your external keyboard because it is ignored due to the MX issue.
Unfortunately there's no easy workaround at the moment. If you're a little bit familiar with coding, you could remove the MX check from the source, compile the binary and use that version.

Hi @ohueter, thanks for the tip. I can confirm the system works with non logitech keyboards.
However, I cloned and built the version on branch 1.5, and it now works also on my Logitech wireless keyboard! Can I ask why we're not merging with main? Or at least creating an "untested" standalone for those with Logitech keyboards?
Thanks!

Happy you found a way to get autokbisw working for your setup! 🥳
Ignoring MX input devices is an intentional feature to solve a problem some users had with autokbisw. Changing it back would solve the problems of a different group of users, but re-introduce the problem the first user group had. The way to solve these issues for all users is layed out in the open issues tagged need help, please feel free to contribute!
Verbosity mode has no influence on the functionality of the program. I would assume that in your case it rather hints at persisting permissions issues with the service that Homebrew installed. You should make sure you're only running only one instance of the program with correct permissions for that exact executable. macOS hides the program path in System Settings, but this does make a difference. Maybe thats what causing this problem for you?

It absolutely is @ohueter, thanks for the reply.
I am now struggling to get the executable added to the background task. This happened automagically with brew service start autokbisw as it triggered all the privacy bells and whistles, and added the service to the background tasks.
If I launch the executable from terminal, I need to keep the terminal open for it to run, and it doesn't get added to the background tasks. Any documentation on that?

The service definition as plist should look something like that:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>Label</key>
    <string>autokbisw</string>
    <key>ProgramArguments</key>
    <array>
      <string>/path/to/autokbisw</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
    <key>KeepAlive</key>
    <true/>
  </dict>
</plist>

but I totally forgot how to add that to sysctl. You need to find out by yourself I'm sorry.

I don't know if this was said before, but for me the problem was, that I had Karabiner running, which proxies keyboard-input (as far as I understand), so the kernel sees input from the same keyboard, no matter the physical keyboard that is being used.


Define best practices for config content

Why:

as our internal standard
recommendation for cxflow users

The two principial options are:

include all constants in config
place default values in code, use config just for those constants that one wants to change from their default values
Hybrid solutions are possible.

Some advantages of including all in config
Even the longest configs will be << 200 lines and can be searched and structured. For novices we can write example configs and show the concepts.
Points:

clear message: it is one of the essential ideas behind cxflow - not changing code, only config
no need to read the code, distributed in different scripts
default values can cause a lot of pain in collaboration

Some advantages of placing defaults in code

easier start for cxflow novice

Me and Boris find the option with including all constants to config better.
@petrbel, @FloopCZ  please comment on this.

After giving it a second thought, I am for avoiding the defaults...
Explicit is better than implicit

Thanks for bringing this up. Regardless of the outcome, it should be reflected in our examples and docs...

I think some kind of a hybrid is the best solution. Datasets will probably suggest some default values for augmenters (probably disabled) etc and I don't think we need to specify enabled: false for every single augmenter.
Note that datasets will be usually used for a single data set, i.e. the same folder of images etc. Hence, it is almost superfluous (thanks @Teyras for this word) to specify the image shapes all over again.

Closing for inactivity.


speculos_test.go:251: get public key ERROR: Post "http://<IP_ADDRESS>:5001/apdu": EOF

Getting this error from CLI: https://github.com/spacemeshos/go-ledger-sdk/actions/runs/4453279188/jobs/7821677253. This works fine locally on macOS; tests on Linux run into #4.
Run go test -v -tags=speculos
=== RUN   TestSpeculos
    speculos_test.go:251: get public key ERROR: Post "http://<IP_ADDRESS>:5001/apdu": EOF
--- FAIL: TestSpeculos (0.00s)
FAIL
exit status 1
FAIL	github.com/spacemeshos/go-ledger-sdk	0.005s
Error: Process completed with exit code 1.

Fixed in #3


Mattermost Issue notification formatting broken

Gitea version (or commit ref): 1.10.0
Git version:
Operating system:
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
I integrated Gitea using a Webhook to Mattermost. When I create an issue in Gitea the following text gets posted on Mattermost:
[org/repo] Issue submitted by cornel

<https://host/org/test/pulls/1|#1 to do this>

The link can't be clicked as it's in text form.
Gitlab posts created issues as:
[[org/repo](https://host/org/repo)] Issue opened by Cornel (cornel)

which creates a link that can be clicked in Mattermost.
Screenshots

@cornelk Did you create a slack type webhook?

@lunny yes, it's a Slack typed Webhook.
Looking at the code of https://github.com/go-gitea/gitea/blob/a966a0298ea1a545c383541ca4e72c61de1ed59e/modules/webhook/slack.go I see that new commit posts get the repoLink/branchLink but getSlackIssuesPayload() does not make use of p.Repo.HTMLURL which will not allow any posted message in there to be clicked. I can fix it if wanted.

@cornelk could you send a PR?

The issue got reopened, so I post the remaining problem with the formatting here:

comment formatting is still broken


consolidate backup handler to 1 task instead of 2

Eliminate the need for 2 separate handler tasks to handle eos config backups.

Closes #166

Per discussion with @carlbuchmann updated to remove handler all together and consolidate config push with config backup tasks since the eos_config module supports this.

@ryanmerolle thanks for this PR!


Master

Changes / Comments
Updates on deviant character sheet and also made Geist sheet match the new colour scheme and background of the second edition
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
fixes on deviant sheet
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


Run CI on MacOS

Signed-off-by: mramotar<EMAIL_ADDRESS>Please see our contributing guidelines (contributing.md) primarily make sure to sign our cla as we cannot accept code externally without a signed cla
https://opensource.dropbox.com/cla/

Ios targets can not be built on linux_x64 machine


Wrong order when listing runtime versions availables

Description
I'm not entirely sure how the remote versions are fetched, but if there is any sorting done after, it's not quite entirely correct for some plugins.

This is something that's borked in asdf, at least in almost all plugins I use. I think it's hard to get it right because there too many schemes for versioning, but probably there is a web service that returns the versions correctly.

To Reproduce

Install go plugin
rtx ls-remote go

As a reference rtx ls-remote chezmoi does return the correct order while using a similar scheme.

Expected Behavior
rtx ls-remote go (or any plugin for that matter) should return the correct order for the versions.
rtx doctor Output
[x80486@uplink:~]$ rtx doctor
rtx version:
  1.32.2 linux-x64 (unknown 2023-07-06)

build:
  Target: x86_64-unknown-linux-gnu
  Features:
  Built: Thu, 06 Jul 2023 14:43:07 +0000
  Rust Version: rustc 1.70.0 (90c541806 2023-05-31) (built from a source tarball)
  Profile: release

shell:
  /bin/bash
  GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2020 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

  This is free software; you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

rtx environment variables:
  RTX_CONFIG_FILE=/home/x80486/.config/rtx/config.toml
  RTX_SHELL=bash

settings:
  {"always_keep_download": "false", "always_keep_install": "false", "asdf_compat": "false", "disable_default_shorthands": "false", "disable_tools": "[]", "experimental": "false", "jobs": "4", "legacy_version_file": "false", "legacy_version_file_disable_tools": "[]", "log_level": "INFO", "missing_runtime_behavior": "warn", "plugin_autoupdate_last_check_duration": "0", "raw": "false", "trusted_config_paths": "[]", "verbose": "false"}

config files:
  /home/x80486/.config/rtx/config.toml

plugins:
  bun             https://github.com/cometkim/asdf-bun.git#fd84edd
  chezmoi         https://github.com/joke/asdf-chezmoi.git#626e470
  deno            https://github.com/asdf-community/asdf-deno.git#87442fe
  go              https://github.com/rtx-plugins/rtx-golang.git#29068ac
  golangci-lint   https://github.com/hypnoglow/asdf-golangci-lint.git#a43c37c
  java            https://github.com/rtx-plugins/rtx-java.git#a8cbfc1
  node            (core)
  python          (core)
  terraform       https://github.com/asdf-community/asdf-hashicorp.git#c44c314

toolset:
  node@18, <EMAIL_ADDRESS><EMAIL_ADDRESS>java@temurin-17, <EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
No problems found

Can you be more specific? What's wrong with the order.

This is what I mean:
[x80486@uplink:~]$ rtx ls-remote chezmoi
0.0.1
...
1.8.9
1.8.10
1.8.11
2.0.0-rc1
2.0.0-rc2
2.0.0 <-- release on the correct position, after last release candidate
2.0.1
2.0.2

[x80486@uplink:~]$ rtx ls-remote go
1.2.2
1.3 <-- wrong order, should go after 1.3rc2
1.3beta1
1.3beta2
1.3rc1
1.3rc2
1.3.1
1.3.2
...
1.18.9
1.18.10
1.19 <-- wrong order, should go after last release candidate for 1.19
1.19beta1
1.19rc1
1.19rc2
1.19.1
1.19.2
...
1.19.10
1.19.11
1.20 <-- wrong order, should go after 1.20rc3
1.20rc1
1.20rc2
1.20rc3
1.20.1
1.20.2
1.20.3
1.20.4
1.20.5
1.20.6
1.21rc1
1.21rc2

this is not a problem in the core go plugin so I am going to close as resolved


How can I get object ID by object type?

Can I get the object ID by object type? Is there any realation?
Like the object ID "0xcf994611fd4c48e277ce3ffd4d4364c914af2c3cbb05f7bf6facd371de688630" ,  and the type is
0x1eabed72c53feb3805120a081dc15963c204dc8d091542592abaf7a35689b2fb::pool::Pool<0x5d4b302506645c37ff133b98c4b50a5ae14841659738d6d733d59d0d217a93bf::coin::COIN, 0x2::sui::SUI>

What are you using? Typescript/Rust/Python SDK?

Typescript SDK


Can this work when opening tmux in neovim (not vim in tmux)

I tried this plugin when opening tmux in neovim terminal buffer, but it seems it is not working.

Heho,
this cannot work, because tmux cli must know about nvim as child process.
Hosting tmux inside nvim means tmux is not aware of a running nvim.
Kind regards
Alexander


Replace import with invoke script (shortcuts?)

I played around with invoking the script but the parameters make it a little weird. Widget scripts usually load parameters from args.widgetParameter but invoking the script from a URL uses args.queryParameters. It still could be useful for passing in "DEBUG=1" or something similar but I think I'm going to pivot for now to just a "github" widget.
Here's how to open the scriptable script for context:
const uri = 'scriptable:///run/' + libraryInfo.name
Safari.open(uri)

The new direction will be a github script that keeps multiple scripts up to date. Invoking the scripts will be done in the scripts themselves so we don't need any weird async javascript stuff to load modules.