BUG- .is_up_to_date raises error when never written before

Description
The <DataNode>.is_up_to_date method breaks when the Data Node has never been written.
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "c:\Users\jacta\.conda\envs\bar-cutting\lib\site-packages\taipy\core\data\data_node.py", line 528, in is_up_to_date
    and ancestor_node.last_edit_date > self.last_edit_date
TypeError: '>' not supported between instances of 'datetime.datetime' and 'NoneType'

How to reproduce
from taipy.config import Config
import taipy as tp

Config.configure_job_executions(mode="standalone")

# Normal function used by Taipy
def double(nb):
    return nb * 2

# Configuration of Data Nodes
input_cfg = Config.configure_data_node(id="somedata", default_data=21)
output_cfg = Config.configure_data_node(id="result")

# Configuration of tasks
first_task_cfg = Config.configure_task(id="double",
                                       function=double,
                                       input=input_cfg,
                                       output=output_cfg)

# Configuration of scenario
scenario_cfg = Config.configure_scenario(id="my_scenario",
                                         task_configs=[first_task_cfg],
                                         name="my_scenario")

if __name__=="__main__":
    tp.Core().run()
    scenario_1 = tp.create_scenario(scenario_cfg)

    print(scenario_1.result.is_up_to_date)

Expected behavior
We should not get an error; the result should be False if the Data Node is invalid.
Possible solution:
Change the is_up_to_date function in taipy/core/data/data_node.py, line 510:
@property
def is_up_to_date(self) -> bool:
    """Indicate if this data node is up-to-date.

    Returns:
        False if a preceding data node has been updated before the selected data node
        or the selected data is invalid.

        True otherwise.
    """

    if self.is_valid:
        from ..scenario.scenario import Scenario
        from ..taipy import get_parents

        parent_scenarios: Set[Scenario] = get_parents(self)["scenario"]  # type: ignore
        for parent_scenario in parent_scenarios:
            for ancestor_node in nx.ancestors(parent_scenario._build_dag(), self):
                if (
                    isinstance(ancestor_node, DataNode)
                    and ancestor_node.last_edit_date
                    and ancestor_node.last_edit_date > self.last_edit_date
                ):
                    return False
    return False

Runtime environment

Taipy: 3.1.1

Acceptance Criteria

[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] #1200

This should target both develop and 3.1 branches.

Hey, @jrobinAV, I'm not really familiar with python, but may I give this issue a try?
So, like we've to change return self.is_valid to return False in data_node.py, right?

More than just that. You have to replace the whole function with the one written above @yaten2302 Is that right? @jrobinAV

@yaten2302 Thank you for helping us on this issue.
Today's code for the method is_up_to_date does not work. The problem is that the code assumes the last_edit_date is populated, meaning the data node has already been written at least once. This is not always true.
The code that @FlorianJacta proposed in the description should solve the issue.
So, the main objective of this issue is to:

Exhibit the problem in a unit test
Replace the whole method with what has been proposed
Ensure the new code fixes the exhibited problem
Ensure all the possible use cases are tested

Hey @jrobinAV, thanks for assigning this issue to me 👍
@FlorianJacta I've replaced the whole function data_node.py with the one written above.
But, I've a doubt, do we've to create a separate branch or we can work directly on the default branch i.e. develop? Also, could you please guide that how to create tests, as I'm not familiar with that?

Description
The <DataNode>.is_up_to_date method breaks when the Data Node has never been written.
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "c:\Users\jacta\.conda\envs\bar-cutting\lib\site-packages\taipy\core\data\data_node.py", line 528, in is_up_to_date
    and ancestor_node.last_edit_date > self.last_edit_date
TypeError: '>' not supported between instances of 'datetime.datetime' and 'NoneType'

How to reproduce
from taipy.config import Config
import taipy as tp

Config.configure_job_executions(mode="standalone")

# Normal function used by Taipy
def double(nb):
    return nb * 2

# Configuration of Data Nodes
input_cfg = Config.configure_data_node(id="somedata", default_data=21)
output_cfg = Config.configure_data_node(id="result")

# Configuration of tasks
first_task_cfg = Config.configure_task(id="double",
                                       function=double,
                                       input=input_cfg,
                                       output=output_cfg)

# Configuration of scenario
scenario_cfg = Config.configure_scenario(id="my_scenario",
                                         task_configs=[first_task_cfg],
                                         name="my_scenario")

if __name__=="__main__":
    tp.Core().run()
    scenario_1 = tp.create_scenario(scenario_cfg)

    print(scenario_1.result.is_up_to_date)

Expected behavior We should not get an error; the result should be False if the Data Node is invalid.
Possible solution:
Change the is_up_to_date function in taipy/core/data/data_node.py, line 510:
@property
def is_up_to_date(self) -> bool:
    """Indicate if this data node is up-to-date.

    Returns:
        False if a preceding data node has been updated before the selected data node
        or the selected data is invalid.

        True otherwise.
    """

    if self.is_valid:
        from ..scenario.scenario import Scenario
        from ..taipy import get_parents

        parent_scenarios: Set[Scenario] = get_parents(self)["scenario"]  # type: ignore
        for parent_scenario in parent_scenarios:
            for ancestor_node in nx.ancestors(parent_scenario._build_dag(), self):
                if (
                    isinstance(ancestor_node, DataNode)
                    and ancestor_node.last_edit_date
                    and ancestor_node.last_edit_date > self.last_edit_date
                ):
                    return False
    return False

Runtime environment

Taipy: 3.1.1

Acceptance Criteria

[ ]  Ensure new code is unit tested, and check code coverage is at least 90%
[ ]  #1200

Also, when I was trying to reproduce this issue, it's showing this error in the installation of taipy on running command - pip install taipy

Try to create an entirely new Python environement

Hey @FlorianJacta, I've created a draft PR, could you please review it and let me know if any changes are required.
PR link

Thank you, the R&D will look into it!


[Pre go live activity] Authentication for Authors & author training

Setup authors roles in config.xlsx.
schedule Author training and create authoring guide

added technical user<EMAIL_ADDRESS>


Use case idea: alternative to github1s.com

https://github1s.com makes it very easy to browse and read code on GitHub with VS Code, and boots in seconds.
It would be cool to have something similar that would open JupyterLite instead. If the repo on GitHub contains notebooks, they could then be executed and interacted with easily.
Opening this issue so we can keep that in mind when implementing different ways of retrieving and sharing content, and also when thinking about deployments and publishing stories.

Of course Binder already does that too.
But the difference here would be that it would take seconds to boot instead of minutes.

Whatever the nuts and bolts of the deployment mechanism are, I feel like
keeping the scope of this repo to "build and test the building blocks"
makes the most sense... But unlocking federated extensions, and leaving the
right hooks open on the stuff here, is going to go really far to enabling
these behaviors.
A quick path to a read-remote-only-edit locally experience, is an nbconvert
exporter that could be gotten into nbviewer... It's already solved the
"download the notebook" part, even if the cache busting is kinda... busted
right now.
The original, lost prototype of the jyve stuff was actually built on
dat/beaker, and I'd love to spin back through the distributed stuff now
that it's had a few years to mature. Having the app be editable from within
itself was kinda magic... Though I'm more bullish on the protocol than the
browser.
What actually brought me here was a discussion with @yuvipanda, who's been
cooking on the deployment ideas for dinner time. Even a fully interactive
"waiting room" skin for binder would be kinda magical... And could even
offer to switch to the live kernel when ready.


[Improvement]: Add Shopify New Paid Order to Slack Channel Message template

Connector Name
connectors/samples (Connector Samples/Templates)
Suggested improvement
Currently there are only no Choreo samples which use the Shopify trigger.
To cater that requirement we need to implement an integration scenario which uses the above trigger.
A sample which sends a Slack channel notification upon a new paid order on Shopify seems to be a valid integration scenario.
Related issues
No response

Closing as this seems to be related to choreo samples, which is not valid anymore


IntoParams, multiple usage.

Hello, how to use IntoParams more than once? (I am new to Rust)

error[E0252]: the name `ParamsType` is defined multiple times
  --> src/repo/authentic_repo.rs:30:10
   |
24 | #[derive(IntoParams, Message)]
   |          ---------- previous import of the type `ParamsType` here
...
30 | #[derive(IntoParams, Message)]
   |          ^^^^^^^^^^
   |          |
   |          `ParamsType` reimported here
   |          help: remove unnecessary import

24 | #[derive(IntoParams, Message)]
   |          ---------- previous import of the type `HashMap` here
...
30 | #[derive(IntoParams, Message)]
   |          ^^^^^^^^^^ `HashMap` reimported here

Apparently this is a bug. I will fix. Please, isolate your structs with submodules for now.
Example:
pub mod mod1 {
 use rsfbclient::{prelude::*, FbError};
 pub struct UserExists...
}

pub mod mod2 {
 use rsfbclient::{prelude::*, FbError};
 pub struct PasswordCorrect...
}

Thank you :)

0.19.0 released, please check the new version

@fernandobatels, Thank you! It doesn't complain anymore, but I have a question, https://crates.io/crates/r2d2_firebird has not been updated?

https://crates.io/crates/r2d2_firebird has not been updated?

This crate is not building anymore with recents rust versions. I will check this tonight.


[FEATURE] Add ROC approach in benchmark testing and reporting

Is your feature request related to a problem?
Existing approach for kNN performance benchmarking does not give results in form of ROC. This format is de-facto standard in the industry, for example ann-benchamrk project publishes ROC curves for their results - https://github.com/erikbern/ann-benchmarks.
Currently for kNN there are two benchmarking tools, customized extensions for OpenSearch Benchmark tool and custom scripts that are specific for kNN.
What solution would you like?
At least one of existent benchmark tools in kNN need to be able to run and provide results in form of ROC curve or in a form that is ready to be plotted as ROC curve.
As a bare minimum we need an ability to configure and run indexing and query tests with several different algorithm parameters (m and efConstruction) and collect aggregated results (latencies, recall, throughput etc.).

@martin-gaievski what does ROC stand for?

Ah okay, I think what that would look like is some kind of wrapper tool around one of our benchmarking tools (preferabaly OSB functionality).
Alternatively, we can run with ann-benchmarks or bigann-benchmarks code for comparison purposes.


[wts] Fix wts gap for Canvas

There're still 4 tests gaps between wts and normal tests, it's
due to the following reasons:

In wts, 2d.scaled-manual.png is treated as test

In tests.xml, canvasgradient_addColorStop_INDEX_SIZE_ERR.html is
treated as one test, but there're 4 sub tests inside in fact.

Impacted tests(approved): new 0, update 110, delete 1
Unit test platform: WTS
Unit test result summary: pass 850, fail 20, block 0

In wts, 2d.scaled-manual.png is treated as test

This shall be a bug of WTS. @yugang @BruceDai

Merge as-is.


Linux Exploitation Tools

Added a new search and dataset for: Suspicious Linux Discovery Commands
This search has an updated logic that has a lookup of suspicious bash commands and covers previously added detections for these tools  (AutoSUID, LinEnum, LinPeas, Linux Exploit Suggesters)
Will create a new atomic and PR for Mimipenguin specifically if needed

Updated the description and added a new search ! Removed atomic searches and combined them into one!


[TRANSLATION]

Language the issue is about
Romanian
Details about request
Are you providing translations to a new language, or updating a current one?
New translation language.
Translations
Either provide any relevant translations below or attach the messages.yml file
messages.zip
Discord name
Provide if you want to get a special rank on the discord server
areanydd

Thanks for your contribution, this new translation will be added in the next update.


Add Canary test requirement to the PR template

Description
From now on we should include the link to the PR in Canary tests repo for each newly added tool. I am adding a reminder about it to the PR template.
Related issue: https://github.com/actions/virtual-environments-internal/issues/840
Check list

[X] Related issue / work item is attached
[N\A] Tests are written (if applicable)
[N\A] Documentation is updated (if applicable)
[N\A] Changes are tested and related VM images are successfully generated

Closing after internal discussion


releasing a spyglass while holding a bow causes the bow to shoot

https://user-images.githubusercontent.com/13991048/184518712-fb5c3a6f-5c4a-4bad-be78-88db4ef3c0a2.mov

Fix reverted because it (indirectly) caused other issues with splash potions not working properly in fast paced combat. Will need to investigate that before putting this fix back in.


[Question] Use multiple border routing interfaces with ot-br-agent

Hi
Situation:
We have a yocto Linux board that can be connected to the "user" network through Ethernet or WiFi (STA mode).
The two interfaces are not bridged.
We need to run ot-br-posix with the two interfaces as we want it to work with the two interfaces.
Currently otbr-agent is started with -B eth0 and we would like to make it working also with mlan0 but currently I don't know how to do it.
When I read the specifications (thread 1.3) it seems possible to use multiple link interfaces but I am really confused, i don't know if we need the BBR feature for this or not.
My research:
In otbr-agent the -B argument is backbone-ifname or Backbone interface
When we look where this is used:
    , mNcp(mInterfaceName.c_str(), aRadioUrls, mBackboneInterfaceName.c_str(), /* aDryRun */ false, aEnableAutoAttach)
#if OTBR_ENABLE_BACKBONE_ROUTER
    , mBackboneAgent(mNcp, aInterfaceName, aBackboneInterfaceName)
#endif

Currently, (in my config) OTBR_ENABLE_BACKBONE_ROUTER is disabled by the cmake-option OTBR_BACKBONE_ROUTER=OFF, so the parameter is only used here:
Ncp::ControllerOpenthread()
 -> otSysInit()
  -> platformInit()
   -> ot::Posix::InfraNetif::Get().Init(aPlatformConfig->mBackboneInterfaceName);

NOTES:

The backbone term is confusing as it can be used when BBR is OFF.
In my case with OTBR_BACKBONE_ROUTER=OFF, the parameter Backbone interface is used to configure an ICMP6 socket that is bind to the specified interface.

Questions:

Can you confirm that what i am looking for is Adjacent Infrastructure Link ?
If yes, how to set an Adjacent Infrastructure Link in otbr-agent ?
If not, is it possible to use multiple interfaces with otbr-agent ? How ?
Also, can someone explain what the Backbone Router (BBR) feature really provides more than classic border routing (BR) ?

As I understand from the specs, this is when we want to communicate with multiple thread networks using a backbone infrastructure link (a classic network (ethernet/wifi/vpn/...) ?)

Can you confirm that what i am looking for is Adjacent Infrastructure Link ?
Yes, the Backbone interface specified by -B eth0 is the Adjacent Infrastructure Link. It's a legacy name.

If you just looking for a feature "run otbr-agent with the first available interface in set('wlan0', 'eth0')", you can do this with otbr-agent options: -B wlan0 -B eth0
If you want otbr-agent to run on both interface at the same, it's not currently supported by neither openthread nor the Thread spec. The spec doesn't support it as well, because the on-link prefixes for the AILs are identical (i.e. derived from the extended pan id) but it doesn't work when Wi-Fi and Ethernet have the same on-link prefixes but not bridged.

Thanks for the response.
So finally we monitor the WiFi connection events using wpa_cli, then depending on WiFi status we start/restart otbr-agent on the correct interface (mlan0 or eth0)
We considere the WiFi interface as priority interface.
Later we should see how to do it better, for exemple using bridge or bounding.
I close the issue as this is answered.


Rename gruntwork-cli to gocommons

Good idea! Accepted suggestion, and then ran go mod tidy 83d076f. Sorry for the toil, but can I get another approval? Thanks!

Thanks for review, Merging now!


rename forall/exists to all/any in sorted_set

Both forall/exists and all/any make sense to me, but all/any are shorter. So in this PR, the forall/exists in sorted_set will be renamed to align with other collections.

Another candidate: every/some

Pull Request Test Coverage Report for Build 1847
Details

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.105%

Totals

Change from base Build 1846:
0.0%

Covered Lines:
2917

Relevant Lines:
3510

💛  - Coveralls


Section C.6.1.1. FCO_CPC_EXT.1 - Asterisk at the end of the sentence?

Section C.6.1.1. FCO_CPC_EXT.1 Component Registration Channel Definition
Asterick at the end of sentence: “FCO_CPC_EXT.1.3 The TSF shall enable a Security Administrator to disable communications between any pair of TOE components.*

Fixed in editorial-v3_0-typos


Adds the RubyAlternate command

This PR suggests an implementation for the :RubyAlternate (and add a docs file).
The strategy is:

If the current file path patern is xpto/dir1/dir2/../file_test.rb

tries to open app/dir1/dir2/../file.rb
or lib/dir1/dir2/../file.rb

If the current file path patern  xpto/dir1/dir2/../file_spec.rb

tries to open app/dir1/dir2/../file.rb
or lib/dir1/dir2/../file.rb

If the current file path patern  xpto/dir1/dir2/../file.rb

tries to open test/dir1/dir2/../file_test.rb
or spec/dir1/dir2/../file_spec.rb

There's a TODO in the util.lua that limits this functionality to Unix-based OS (or systems that uses / as a separator for the filesystem paths). Any idea about a better workaround? I linked in the comment the snippet from Plenary that sorts that out, but it looks like a non-public function/variable.
https://user-images.githubusercontent.com/4732915/125647542-cc36b800-13d5-454c-be7b-2dae8ad708f1.mp4

Thank you for the amazing contribution


(PUP-6602) Add test for pcore loader precedence

This commit adds an acceptance test to ensure that generated pcore
resource code is loaded over the ruby code that was used to create
it when using custom resource types.
[skip-ci]

CLA signed by all contributors.


Dataset processing issues

Excuse me, I noticed that your code was running very slowly. How should I preprocess the dataset to generate LQ images

I also meet this question. Do you know how to do it?


GH-38883: [Docs] Replace "have" with "indicate" in the "Struct validity" section of the docs

Rationale for this change
This documentation section says:
...a child array might have a null in its validity bitmap...
But an array can't have a null in its validity bitmap. It can only indicate a null with a bit equal to 0 in its validity bitmap.

What changes are included in this PR?
Rewording

Are these changes tested?
Renders normally

Are there any user-facing changes?
Changes documentation only.

Closes: #38883

@github-actions crossbow submit preview-docs

Is it intentional that you change the text instead of example validities?

I've made this PR for training purposes, as I'm new to this. It's useful but it's not connected with the issue GH-38883.
Please see my second PR https://github.com/apache/arrow/pull/38898, which deals with GH-38883.

Ah, I see.


Transparent change

Using transparent values like rgba(0, 0, 0, 0) or rgba(255, 255, 255, 0) means that the change will not be visible because the color is completely transparent.

Using transparent values like rgba(0, 0, 0, 0) or rgba(255, 255, 255, 0) means that the change will not be visible because the color is completely transparent.


[scaffolder] Config declaration update from existing class

Check if config declaration is capable of adding new getters if the original config file was updated (only for added new fields)

Closing for the future revise of scaffolder.


pay HUSD purchases to costake contract

As per requirements, when people buy HYPHA with HUSD, it goes in the cosale contract.

Gerardo approved


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter terminal for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ioBroker.terminal
   -

ERRORS:

[ ] :heavy_exclamation_mark: [E021] "licenses" in package.json are deprecated. Please remove and use "license": "NAME" field.
[ ] :heavy_exclamation_mark: [E029] Node.js 16 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '0.10' } }" at package.json.
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 2.6.8 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E035] No devDependency declared for @iobroker/testing. Please add "@iobroker/testing":"4.1.3" to devDependencies at package.json
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E106] "common.titleLang" must not have ioBroker in the name. It is clear, for what this adapter was created. Now: {"en":"ioBroker simple terminal","de":"ioBroker einfaches Terminal","ru":"простой терминал ioBroker","pt":"terminal simples ioBroker","nl":"ioBroker eenvoudige terminal","fr":"Terminal simple ioBroker","it":"terminale semplice ioBroker","es":"Terminal simple de ioBroker","pl":"Prosty terminal ioBroker","zh-cn":"ioBroker 简单终端"}
[ ] :heavy_exclamation_mark: [E114] Admin support not specified. Please add "common.adminUI.config = json|materialize<|html|none"
[ ] :heavy_exclamation_mark: [E150] No "common.connectionType" found in io-package.json
[ ] :heavy_exclamation_mark: [E152] No "common.dataSource" found in io-package.json
[ ] :heavy_exclamation_mark: [E162] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/ioBroker/ioBroker.terminal", press the settings button beside the about title and add some topics.

WARNINGS:

[ ] :eyes: [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W113] Adapter should support compact mode
[ ] :eyes: [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W172] "common.localLink" in io-package.json is deprecated. Please define object "common.localLinks": { "_default": "..." }
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W519] Consider adding plugin "@alcalzone/release-script-plugin-manual-review".
[ ] :eyes: [W522] Please consider migrating to admin 5 UI (jsonConfig).
[ ] :eyes: [W853] .npmignore found - consider using package.json object "files" instead.

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence

This issue has been replaced by new isse #76
This issue can be closed.
your
ioBroker Check and Service Bot


add missing re-export and typedef for UpgradableGuard

Sorry, missed this in the main pull request.

Nice catch!


Add travis/CI support for package:observable

https://travis-ci.org/dart-lang/observable
Go forth and add .travis.yaml n' such


[PROPOSAL] - Load order - Environment specific vs Global

So, this is the deal. In my Rails app, I have 3 environments (development, staging, production) with the following configuration:

environment
env file

** global **
.env

development
.env.development

staging
.env.staging

production
.env.production

Two of them (development and staging) share the same value for a specific environment variable:
FOO="bar"

The third (production) is using a different value:
FOO="baz"

As of today, I need to write the same variable in all three 'environment specific' files with the relative values, because they don't override the global .env file.
It wouldn't be better if the 'environment specific' file can be used first, and fallback to the global .env file, if needed?
With that, I can simply declare FOO="bar" in the .env and override the value in the .env.production file.

Was searching for already opened issue about this matter. But what I was expecting was to find a filled bug, not a proposal, since reading this part of the docs https://github.com/bkeepers/dotenv#what-other-env-files-can-i-use I understand that, e.g., .env.local should already override the .env.
Am i missing something?
I have a similar scenario where .env is the "template" committed in repo and .env.local is intended as the override, but instead I've to delete empty keys in .env since they are overrided.
Using dotenv-rails 2.7.5

!notstale


null for boolean field

Is already possible to set a boolean field to null by default? I see it as false by default, but it is already giving me information that user went for false. And it is not true!!! I don't know any other database that would disallow developers of null/unset value.

This was an early decision and an intended behavior. The reasoning for this is explained in https://github.com/pocketbase/pocketbase/issues/122#issuecomment-1186466209.
For now there are no plans to add option for supporting null for the bool fields but there are plans in the future to allow custom fields, which eventually will enable users to define their own fields and constraints.

Managing custom fields creates extra work for developers and it is not nice solution as this straightforward one. Sqlite has nullable data types, so why not making all of them here too?

Because it is easier to work with the fields when you know that they always have a value.
From the linked comment above:

This would also simplify the conditional checks pointed by Lex-2008 and in general it will be easier to integrate with languages that has sound null safety (eg. Dart).


Docs:fix_command_typo

Type of change

Documentation

Description

Checklist

[ ] Update documentation

Can one of the admins verify this patch?


missing man page ????

attempting a man sleep

@lbdyck can you retry with latest man? I get:
man sleep


Is there any way to change website appsettings during custom deployment script?

I'm about to make changes in Website AppSettings within deployment scenario.
Noticed I don't have admin rights to change the registry.
Added my variable to $ENV: but it's not available from portal and exist only in a current session.

You cannot affect the Azure App Settings during deployment. It's something that needs to be done using the Azure API, which you can't call from inside the sandbox.
The closest thing you can do is drop an XDT transform to add some environment variables. Sample here. They still won't show up in the Portal/API, but they will be effective at runtime.

@davidebbo Please fix me if I wrong.
There is no point to use https://github.com/projectkudu/kudu/wiki/REST-API#settings this?
Because I can't modify Azure App Settings using Kudu REST API?
When I make changes in /api/settings they are exists only on this page, but unavailable from portal, /Env and ARM, etc.

@mskutin You are correct; this API will not help. It is only used as an alternate way to set Kudu settings, but it does not have the same effect as general settings.


Question: traffic split support?

Hi!
I am looking at possibility of using cilium directly without more expensive mesh. Cilium covers transparent encryption using IPSec/Wireguard and enforce network policies very well, however another aspect I am interested in is traffic splitting.
Mesh like Istio (traffic management) and Consul (service splitter) both support percentage based traffic splitting.
Curious if cilium supports traffic split right now or would that be something to consider in near future/at all?

cc @jrajahalme

We are currently working on L7 LB features. The first case we'll target is vanilla k8s Ingress (so no % splitting), but will target this use case soon after.

Thanks @jrajahalme! Since this is more of a question and sounds like will see the feature coming out soon, going to close the issue here but keeping an eye on the releases 😄


Update retcodes to handle new cases

Description
This pull request is a continuation of #1612. The purpose of this pull request is to cover more cases for which tasks does not run successfully and Luigi exit code is 0.
More specifically, the following two cases are covered:

Tasks are not run because task-limit is reached counts as scheduling_error
Return code can be set for cases in which tasks fail or are left pending for unknown_reason

Motivation and Context
This relates to #1660.
Have you tested this? If so, how?
I have included unit tests.

Cool! I did a quick glance. One question quickly rose for me. Should we really convey that "unknown-->bad"? I think of unknown like literally unknown. Sometimes it's out of resources (not bad) and sometimes that task is disabled or still have a timeout for it's FAILED state (maybe bad, but the worker that previously failed has already sent error emails and stuff).
What I'm saying is that this is a really good patch, because it allows for luigi users to react exactly the way the want based on return codes. But I propose that (1) we don't use :( as I don't consider it bad. Maybe we make things confusing, but perhaps we could introduce :D for indicating that the root task is done, and unknown stays as :).

But I propose that (1) we don't use :( as I don't consider it bad.

I changed :( with :| for the unknown_reason case, would that be good enough in your opinion?

What about :¿? I make that to indicate my confusion.

Name it "pending_for_unknown_reason" maybe? That's what it is. And that hopefully also shows how it is worse than "pending". After all we're using ":|" for still_pending_ext ("pending_for_known_reason"). A situation where uncertainty is added is not better.

Sure, let's call it pending for unknown reason. Actually, I oversaw perhaps the most common "reason", that is when you let two separate workers (typically on 2 separate computers) run the same task, but one isn't allowed to run it because the other one has already finished running it.
Actually, even better name would probably be "not_run_for_unknown_reason". If we call it "pending_for_unknown_reason", users might think that it's state according to the central scheduler also is pending, that's usually not the case.

Actually, I oversaw perhaps the most common "reason", that is when you let two separate workers (typically on 2 separate computers) run the same task, but one isn't allowed to run it because the other one has already finished running it.

Shouldn't this case be covered in the run_by_other_worker set?

Shouldn't this case be covered in the run_by_other_worker set?

Sometimes but not always. The summary-printing worker will only know that somebody else ran it if it was RUNNING and that worker asked for work at that time. It could be the case that the other worker was fast and the tasks where DONE already when the summary-printing worker asks for work.

I have one more proposal for this.
Tasks in this set did not enter the run() phase and there is a certain number of reasons causing this; such reasons have been listed in the various comments of this pull request. In such a context, I think unknown_reason might be misleading since we are not dealing with an unexpected/unknown error. Nevertheless, the set is too broad to better define the specific motivation for which the task didn't run.
What if we simply call the set not_run, and we list the possible causes in the docs. I believe this name fits the other sets' names in terms of descriptive granularity (i.e. completed, already_run, not_run, failed,... ). I would agree on using 25  as error code.
Regarding the info logs and execution summary, did not run might be not enough. We might just mention the most probable causes for it.

@fabriziodemaria Your proposal sounds good to me in it's entirety. I like it.
Did you consider to have the info logs say wasn't permitted to run as I suggested before? I think it conveys that the worker did actually ask for work but was denied.

Denial can also occur passively/accidentally, as in the case when connection failure causes task purge, or in the case of an eventual scheduler bug. The "wasn't permitted" presents some controlledness flair when it may not be the case.
But I agree that the pattern how worker gets work out is something users often are confused about. The description of the probable cases can include the phrasing "wasn't permitted to run [by scheduler [because X or Y or Z]]".

\o/ Looks good.

I squashed this as there were to many implementation-detail commits. Hopefully the reworded commit is clearer and more direct to the point of what changed. Good job! :)


Redesign from @sschoger <3

I assume this one is waiting for Tailwind.css, makes the most sense to me.

❤

Closing temporarily because @nolveraa is going to be updating and expanding on these designs.


Add dependency lists for various tools

Relying on system installed tools is getting pretty annoying as the number of tools that lint-review support grows. To curb the reliance on system libraries, it would be best to use each language's packaging system to install non-global libraries.

For node use npm
For PHP use composer
For ruby use bundler but not RVM/rbenv.
Python is already taken care of.

I think it would also be useful to have a simpler install workflow that is as simple as make install.

I'm pretty sure most of this is done already.


[🐞] Partytown Shopify Integration Failed to execute 'postMessage' on 'Worker'

Describe the bug
hi!
I have been through the guide to set up partytown on a shopify 2.0 store but am now facing an error that I'm not quite sure how to handle.
I have created the proxy app on shopify and have set up the worker on cloudflare.
However, when I check the console I see the following error:

Any idea what the issue is?
Reproduction
NA
Steps to reproduce
Following this guide:
https://github.com/edlaver/cloudflare-worker-partytown-shopify-app-proxy/tree/main
Browser Info
Chrome
Additional Information
No response

It's a duplicate of #610


Allow op.yaml instead of just op.yml

currently only op.yml files are accepted input op file names.
request:
allow file to be named op.yaml

@zachpuck what if theres both op.yml and op.yaml in the same directory?

Maybe error saying invalid because both are found?

Doable but i'm wondering if it's better being strict like we are now and only allowing .yml so we don't have such a possibility. I could go either way... what's driving your need/want for this?

I am finding issues when on-boarding users to opctl they immediately make files as .yaml naturally and find it confusing to use .yml. thats the main driver for me.

The currently official extension is .yaml (https://yaml.org/faq.html) as pointed out in the SO answer above, the accepted answer of which also poignantly points out that that should be considered the standard -- so at the very least, there's an argument to support both. It sounds like there's a "small" group of people who use .yml, which frankly, surprises me as in my many years of using YAML, I've never used the 8.3 extension. Nevertheless, if the YAML org says the official extension is .yaml, then that should be considered a standard, which imho, should be followed.
It's not a big deal, really. If I have the time, I can write the code and submit a PR.


Use URL-encoded username for keyring if no URL-encoded password

Summary

Currently, the middleware will not check keyring or netrc if there is any URL-encoded credentials.  pip will check keyring and netrc if there is no URL-encoded password, and use the URL-encoded username for keyring.  This updates the middleware to match pip functionality in this way.
See issue:

#2563

Test Plan

See included unit tests
Note:  Introduced cfg-branching functionality to get_keyring_subprocess_auth in order to bypass subprocess calls in unit tests.

Flaky tests? Only change in my branch was a comment and failing tests are in unrelated parts of the codebase.
Unable to rerun failed checks on my end, btw.

I think GitHub has been having issues today.

This is on my to-do list, it's been slow because of all the cfg changes for testing — we've generally avoided doing something like this so far. Without an in-depth review, I'd say some sort of pluggable Provider interface is preferable.

@BakerNet Thanks for the PR. I can confirm that this resolved the direct issue. If I try to install a package it will now call keyring with the correct username allowing me to get a token as expected. However, it seems to hit a code path where this still fails when downloading transitive dependencies.

This is on my to-do list, it's been slow because of all the cfg changes for testing — we've generally avoided doing something like this so far. Without an in-depth review, I'd say some sort of pluggable Provider interface is preferable.

I have an idea to propose:
We could make the keyring check function a method on the KeyringProvider enum, and add a clap-skipped enum variant for test suite.
So instead of using cfg(test) we would match self
#[derive(Debug, Default, Clone, Copy, PartialEq, Eq)]
#[cfg_attr(feature = "clap", derive(clap::ValueEnum))]
pub enum KeyringProvider {
    /// Will not use keyring for authentication
    #[default]
    Disabled,
    /// Will use keyring CLI command for authentication
    Subprocess,
    // /// Not yet implemented
    // Auto,
    // /// Not implemented yet.  Maybe use <https://docs.rs/keyring/latest/keyring/> for this?
    // Import,
    #[cfg_attr(feature = "clap", clap(skip))]
    TestStub,
}

in method:
let output = match self {
    Self::Subprocess => match Command::new("keyring")
        ... ,
    Self::Disabled => Ok(None),
    Self::TestStub => Ok(Some("mypassword".to_string())),
}

@jenshnielsen would you mind testing this again to check if my fix works on your end when you have time?

I'm tackling this in a more comprehensive overhaul over in https://github.com/astral-sh/uv/pull/2976 if you're interested in looking at it.

Thanks for taking the time to put up a pull request, this was really helpful for understanding the desired behavior. I'm closing in favor of https://github.com/astral-sh/uv/pull/2976 which makes some other changes.


Update pipeline to run verify

Moves the checkstyle check from validate to verify stage
updates corresponding github action pipeline to run verify

Move checkstyle config google_checks.xml from root to src/main/resources/META-INF/

/lgtm


⚠ Bofrost.de has degraded performance

In 884c9c3, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2158 ms

Resolved: Bofrost.de performance has improved in 31fe6c1 after 11 minutes.


Fix #8 - Core classes can now be replaced

Currently you cannot replace core classes as documented in the user guide under Replacing Core Classes. This fix loads core classes from APPPATH first so you can replace them. This also matches the logic in CI 1.7.x:
Common.php line 110
// If the requested class does not exist in the application/libraries
// folder we'll load the native class from the system/libraries folder.
...
    if (file_exists(APPPATH.'libraries/'.$class.EXT))
    {
        require(APPPATH.'libraries/'.$class.EXT);
        $is_subclass = FALSE;
    }
    else
    {
        require(BASEPATH.'libraries/'.$class.EXT);
        $is_subclass = FALSE;
    }
...

This should be included in version 2.1.0.


Minor Server Changes

The following changes are made:

With @vesche's implementation of my multi client, the ClientConnection is no longer threaded and doesn't need to inherit from threading.Thread anymore and has been changed accordingly
Sends kill command to client before closing connection

Hey sorry, can you git pull and recommit? I was doing a major overhaul on the crypto, but I won't be making any more major changes until maybe later tonight.

Man this is quite a merge conflict, but can do.

Done. There's an extra exciting feature, the ability to drop into an interactive shell on the target.
Known Issues:
Doesn't support relative paths (ie: cd ..)

May want to adjust this PR to be to a certain commit instead of a branch...
Just added "Client periodic connection attempt"
In the client, the time between connection attempts can be adjusted. Clients will continually check for a connection, even after server is closed with "quit". To fully terminate a client, the server must send "kill".

Hey @reznok , I might look at doing a cherry-pick on some of these commits. I like the client retry on the server, and had it in the back of my mind to implement something like that. I'm not sure if the best way to implement it is to create the two loops like that inside the client...
Also, I like the addition to the server to gracefully kill all the clients on server exit.
I do really want to add an interactive shell, but I'm pretty sure there's a way to actually directly send an interactive /bin/bash or cmd.exe (based on platform) across the socket. I don't think it needs to be as involved as your implementation, but I'll look more into this.
I think I can do something like this for this PR...  Moving forward you probably should do PR from a different branch so I can merge and then cherry-pick from a seperate branch. Thanks for the collaboration!

A better implementation than the two loops would probably be a simple state machine for connected/not connected. I'll change to doing PRs for specific commits (pretty sure that's doable) instead of the entire branch, as this ended up getting messy fast.

@reznok i tested ur fork, client does not reconnect if server is disconnected and then reconnected.


IntelliSense does not working

class Class:

def __init__(self, path):

    self._path = path
    string = open(self._path, 'r'). #HERE

When I try to type read() intelliSense says no completions.
However, I know open() function returns file object, which has read() function. I want to see all supported function after typing a dot.
PyCharm shows me recommanded function list, but PTVS does not support.
I want to know this is casual things in PTVS or only happening to me.
My current Python Enviroment is Anaconda 4.3.0 (Python 3.5.3)
How can I fix it?

We've already fixed the specific case of open for our upcoming update (not the one that released today - the next one), but in short the problem is that you don't really know what open is going to return. In our fix, we guess one of two likely types, which should cover most use cases.
To work around it right now, your best option is to assign the result of open to a variable and force it to a certain type using an assert statement. For example:
f = open(self._path, 'r')
import io
assert isinstance(f, io.TextIOWrapper)

f = open(self._path, 'rb')
import io
assert isinstance(f, io.BufferedIOBase)

Note that your code will now fail if the variable is not the expected type, and that the code for Python 2 would be different from this, but until you can get the update where we embed this knowledge into our code it is the best you can do.

Thanks, I look forward next release version.


Information on browser support in README

It would be good to have some info on supported browsers or — and maybe that is more relevant — unsupported browsers.
Given the use of DOMContentLoaded and addEventListener, I'm guessing IE8 is not supported. Has this been tried in IE9? Android browser 4.x?

Indeed, I’ll add some info.

Tested Android 4.1, Android 4.4 and Internet Explorer 9: works fine.

Added info to README.md. Closing. :)


Move prims functions

Codecov Report
Attention: Patch coverage is 80.00000% with 35 lines in your changes are missing coverage. Please review.

Project coverage is 77.94%. Comparing base (6440a00) to head (82cfee2).

Files
Patch %
Lines

...l_experiment/torch_interpreter/_prims_functions.py
79.87%
33 Missing :warning:

...al_experiment/torch_interpreter/_aten_functions.py
0.00%
1 Missing :warning:

...tal_experiment/torch_interpreter/aten_functions.py
90.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #82      +/-   ##
==========================================
+ Coverage   77.91%   77.94%   +0.03%
==========================================
  Files          67       68       +1
  Lines        7303     7337      +34
==========================================
+ Hits         5690     5719      +29
- Misses       1613     1618       +5

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


torch version

which torch version do you use?
I use torch 1.5, but i got some error below  when i try to run  convert.py.
RuntimeError: version_ <= kMaxSupportedFileFormatVersion INTERNAL ASSERT FAILED at
../caffe2/serialize/inline_container.cc:132, please report a bug to PyTorch. Attempted to read a PyTorch file with version 5, but the maximum supported version for reading is 2. Your PyTorch installation may be too old.
w

Hi,
we’re actually using torch 1.6, and the models were compiled with TorchScript which might not be backward compatible. Maybe you can update the package first and try again. Let us know if the issue still persists.
On the other hand, requirements.txt will soon be added.

Thx，torch==1.6 can work。


remove extra margin below checkbox

Details
Remove the extra margin below the checkbox in BankAccountStep, AddDebitCardPage and TermsStep page
Fixed Issues
$ #7838
Tests

[x] Verify that no errors appear in the JS console

PR Review Checklist

Contributor (PR Author) Checklist

[x] I verified the PR has a small number of commits behind main
[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[ ] I clearly indicated the environment tests should be run in (Staging vs Production)

[ ] I wrote testing steps that cover success & fail scenarios (if applicable)
[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests & veryfy they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors related to changes in this PR
[x] I followed proper code patterns (see Reviewing the code)

[ ] I added comments when the code was not self explanatory
[ ] I put all copy / text shown in the product in all src/languages/* files (if applicable)
[ ] I followed proper naming convention for platform-specific files (if applicable)
[x] I followed style guidelines (in Styling.md) for all style edits I made
[x] I followed the JSDocs style guidelines (in STYLE.md)

[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I corroborated the UI performance was not affected (the performance is the same than main branch)
[ ] If I created a new component I verified that a similar component doesn't exist in the codebase

PR Reviewer Checklist

[ ] I verified the PR has a small number of commits behind main
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the testing environment is mentioned in the test steps

[ ] I verified testing steps cover success & fail scenarios (if applicable)
[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] I verified there are no console errors related to changes in this PR
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified comments were added when the code was not self explanatory
[ ] I verified any copy / text shown in the product was added in all src/languages/* files (if applicable)
[ ] I verified proper naming convention for platform-specific files was followed (if applicable)
[ ] I verified style guidelines were followed
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components are not impacted by changes in this PR (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[ ] I verified the UI performance was not affected (the performance is the same than main branch)
[ ] If a new component is created I verified that a similar component doesn't exist in the codebase

QA Steps
For Add a debit card page:

Navigate to Settings > Payments
Tap Add a payment method
Select Debit card
Press Save button without checking the terms checkbox
Observe the right margin between the checkbox and the error message

For Connect bank account page:

Navigate to Settings > Workspace > Connect bank account
Tap Connect manually
Press Save & continue button without checking the terms checkbox
Observe the right margin between the checkbox and the error message

For Terms and fees page:

Navigate to /settings/payments/enable-payments url
Press Enable payments button without checking the terms checkboxes
Observe the right margin between the checkbox and the error message

[x] Verify that no errors appear in the JS console

Screenshots
Web

Mobile Web

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @luacmartins in version: 1.1.42-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @chiragsalian in version: 1.1.42-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[Run Bin Scripts]: Add commands in './node_modules/.bin' to subprocess path

This should allow glicky to execute package scripts like those created by create-react-app

Fixes #15

I changed my path variable to pATh and confirmed that it works

Yeah, my bad! 😅, I've accepted the changes

Just tested on my machine it's working, nice stuff @neutrino2211 !


drivers: serial: Initial support for the UARTE peripheral on the nRF52.

This patch implements a driver for the UARTE peripheral that is present
in the Nordic nRF52832.
Signed-off-by: Bertold Van den Bergh<EMAIL_ADDRESS>

@BertoldVdb-byteflies sorry for the huge delay on this. @anangl and @jarz-nordic are now looking into this, we hope to propose something very soon

@jarz-nordic can you comment on whether support for this is coming or should we merge this PR if @BertoldVdb-byteflies addresses the outstanding review comments?

Created issue: https://github.com/zephyrproject-rtos/zephyr/issues/8371 to track UARTE progress.

@BertoldVdb-byteflies do you have plans to follow-up on this PR? Otherwise @jarz-nordic has plans to add support for UARTE in the near future

Hi,
It seems this code will not compile in non interrupt mode.
Second, I am not sure if it is the best idea to call interrupt callback handler from function uart_nrf5e_irq_tx_enable. Instead of calling callback you can force tx interrupt by sending 0 bytes length frame.

@jarz-nordic this PR has not been updated for a while, so it needs a rebase. The question is whether you want to use this PR if the author is willing to update it.

Closing this as I assume PR #8640 will end up adding support for UARTE


Wildcard matching in subscriptions doesn't really work

In some cases it works, but in many cases with wildcards it will fail.

This will become a problem for the MQTT client function being released.


Support non-cardinal labels (a.k.a. metric baggage, non-dimensional labels)

Proposal
Management of cardinality is a constant issue in Prometheus.
Since prometheus has decided never to support non-string metric values, users routinely attempt to associate non-numeric data with a specific time-series by (ab)using time-series labels. This results in difficult-to-analyse disjoint time-series, unexpected cardinality explosions, excessive memory consumption, etc.
I propose that Prometheus define a way to mark a given label as non-cardinal, such that

The label name and value will be stored in the tsdb; but
The label will be not be included in tsdb indexes for the metric;
Only the cardinal labels will be considered for determining metric time-series uniqueness, the label and value are ignored are not considered to define new dimensions of a metric;
The label will not be included when querying Prometheus to enumerate distinct time-series via the REST APIs;
The labels will be included in payloads when fetching values for a time-series

Relational database "covering indexes" provide a long-standing precedent for this functionality; see e.g. postgres's INCLUDE (y) clause for CREATE INDEX.
For backwards-compatibility with existing tools, this should probably be implemented by defining a well-known label prefix, much like prom does for the virtual labels it exposes in recording rules, remote write label rewrite rules, etc.
Use case: side-band message on health checks
Extremely common case. You have a health check endpoint with an associated message. You want to be able to see the message in your metrics platform, which uses Prometheus and the Prometheus metrics format.
E.g. the series
t=15 health[svc=foo,message="healthy"]                        0
t=16 health[svc=foo,message="warning: something is wrong"]    1
t=17 health[svc=foo,message="error: service on fire"]         2

The user typically expects this to mean one time-series "health[svc=foo]" with a metric-value and a side-band payload or baggage value "message". But Prometheus and tools actually see
t=15 health[svc=foo,message="healthy"]                        0

t=15 health[svc=foo,message="healthy"]                        [NO DATA FOR TIMESERIES]
t=16 health[svc=foo,message="warning: something is wrong"]    1

t=15 health[svc=foo,message="healthy"]                        [NO DATA FOR TIMESERIES]
t=16 health[svc=foo,message="warning: something is wrong"]    [NO DATA FOR TIMESERIES]
t=17 health[svc=foo,message="error: service on fire"]         2

If the message varies a lot, including identifiers or timestamps, etc, this can cause a cardinality explosion, massive memory consumption etc.
Tools that query for health metrics will be confused unless specifically configured to ignore the message label.
With my proposal, we would instead use something like:
t=15 health[svc=foo,__include_message="healthy"]                        0
t=16 health[svc=foo,__include_message="warning: something is wrong"]    1
t=17 health[svc=foo,__include_message="error: service on fire"]         2

Prom and TSDB would store these as in the timeseries health[svc=foo] *ignoring the value of __include_message for the purpose of identifying timeseries uniqueness in a scrape, indexing, etc, limiting memory use and search costs.
Use case: string payloads
While Prometheus is designed to only carry numeric metrics, the reality is that not everything can be represented as a single float64.
It's common for users to abuse labels to try to create string-valued "metrics" to propagate desired information for access via Prometheus federation, Prometheus-consuming tools like Grafana, etc. For example:

An application status field is a series of well-defined strings and user doesn't want to hardcode a string-to-int enumeration in their metrics endpoint then maintain a matching int-to-string mapping in their metrics dashboards/consumers etc (there are hacks that carry the mapping in the metric description, but, ick);
Attempts to bypass high-numbers-of-labels cardinality issues by using labels with json blobs or key/value pair strings
... you name it, you've probably seen it in the wild

A common antipattern is using a label to carry the real data, with a dummy unused value, e.g.
my_service_readiness=[readiness="starting"] 0
my_service_readiness=[readiness="initializing buttons"] 0
my_service_readiness=[readiness="loading whatsits"] 0
my_service_readiness=[readiness="rounding cubes"] 0
my_service_readiness=[readiness="adding k to every word"] 0
my_service_readiness=[readiness="ready I hope"] 0

This is again a pain to work with in common tooling and causes storage and memory issues in prom.
Since prom won't support string-valued metrics, being able to tell prom that these are non-cardinal labels would be a huge help for such use cases.
Alternative spelling
In the above I used a label prefix __include_ to mean "include, but do not index", akin to postgres's INCLUDE (cols) for covering indexes.
An alternative spelling would be a separate comma-separated list of metrics keys to treat as non-cardinal (or possibly a negated set for "only treat these labels as cardinal, everything else is non-cardinal"). This might be friendlier to tooling, since it would not impose constraints on metrics naming.
E.g.

t=15 health[svc=foo,__non_cardinal="message",message="healthy"]                        0
t=16 health[svc=foo,__non_cardinal="message",message="warning: something is wrong"]    1
t=17 health[svc=foo,__non_cardinal="message",message="error: service on fire"]         2

Not a use case: top-N sampling
Prometheus struggles with use cases where the number of distinct values for a label are very high but only the top-N for some value are of interest.
Consider monitoring of some table health metric for a relational database system. Users may have 1 table or 100,000 tables. You are not interested in all tables. But a single "max(x)" for the worst value for the health metric across all tables is generally inadequate and unhelpful. What you want is to capture and forward some top-N set of health metrics for a subset of tables.
Prometheus presently struggles with this because each time entries enter or leave the top-N set between scrapes that adds new cardinal values. If there is a lot of churn the usual performance and memory problems arise.
This is true whether the application metrics endpoint generates top-N style metrics with a varying set of labels or whether the whole dataset is scraped then reduced with recording rules before forwarding to a federated endpoint etc.
Non-cardinal labels won't help here, because you want to keep track of distinct values for different table names. You just want Prometheus to gracefully handle these sparse time-series that come and go over time.
There doesn't seem to be a good way to do this in Prometheus; there would need to be a way to efficiently represent "top-N" buckets for a metric with associated labels in TSDB directly.
So I'm explicitly excluding this use case from the non-cardinal labels proposal.

Hello from the bug scrub!
This is certainly a bigger effort to tackle. It is pretty much one of the use cases discussed in the whole metadata effort currently ongoing. See https://docs.google.com/document/d/1epBslSSwRO2do4armx40fruStJy_PS6thROnPeDifz8/edit#heading=h.5sybau7waq2q for a recent design doc draft. @aknuds1 @codesome maybe you could verify that the use case in this issues is included in your considerations? And respectively, @ringerc , feel free to comment on the design doc if you don't see your use case modeled.
In any case, due to the scope of this, we eventually want a proper proposal in https://github.com/prometheus/proposals  .
As these aspects will be tracked in the above mentioned design doc draft and later in the "proper" design doc in the proposals repo, we are closing this issue.

The pick-the-newest-sample conflict-resolution logic proposed in https://github.com/prometheus/prometheus/pull/14495 would partially solve the issue described here, if it was possible to extract it for use outside the proposed info() function.
Consider the example in in this issue's description. If we had some function latest_by(series, "key_labels") that returned the datapoint and full set of associated labels for the series with the newest datapoint in series when grouped by comma-separated label list key_labels, then consuming enumeration metrics would look like this:
latest_by(health, "svc")

and for the input given in this issue's description would produce the desired output at each of the time points by:

finding all series satisfying {__name__="health"}
grouping by cardinal label(s) svc
for each group, finding the series with the newest datapoint timestamp and returning that series


Comment when file is generally modified/added/deleted

...and not changes to specific lines. See update to README.md for exact description of how this works (proposal in https://github.com/haya14busa/reviewdog/issues/92#issuecomment-299137785).
Prerequisite(s):

[ ] That https://github.com/haya14busa/errorformat/pull/19 is accepted.

This fixes #92.

Thank you for the p-r, but i'm sorry as I said in the comment https://github.com/haya14busa/reviewdog/issues/92#issuecomment-301386137
I don't like the idea to use magic number to control comments.


Fixed unsafe conversion to underscore string

strcpy() always adds null-terminator at the end.
The original code allocated one byte less than what is needed, so it was overwriting something. Could've been important or not :)
Found this while debugging #248, but I don't know if it fixes it or not. In my local tests on ubuntu I was not able to reproduce the behavior described in #248. But if it's memory related, then it's bound to behave differently on x86 + linux. Worth checking if it helped.

Ok, I think this is enough improvements for now. The only thing left would be to call the new cleanup() method somewhere. In current implementation it will only be called in destructor, but since this is a static object that would be... never?
Shouldn't the mDNS.end() be called in MDNSComponent::on_shutdown() (in mdns_libretiny.cpp)? That would call cleanup right about when it should be, right? Currently it isn't called at all if I'm not mistaken.

That's the problem in embedded/IoT programming - these devices most often run as long as they're given power. There's no shutdown, no close button. ESPHome probably never actually calls the shutdown method under normal circumstances, because why would it?
The point is, with the current Arduino API, there's only so much you can improve. I'd say it's okay the way it is and that there's no need to worry about this.

I work in embedded for some time now and I've seen this "we won't need a shutdown" approach many times. And in many cases we eventually did need it :), only by then it was very hard to achieve due to many decisions like not doing proper deregistration or deallocations, using static objects and singletons.
And the reasons for needing this in embedded is one: to prevent a full reboot, which usually comes with a price of having to re-initialize and re-register everything, while the only thing you wanted was to reinitialize one small component.
The fact that esphome component does have a shutdown method means they are thinking about having this, so I would say it's worth to be prepared :)

Right, but that's a topic for another PR anyway :slightly_smiling_face:


Sitemap isn't working anymore

Probably due to the switch to incremental build.
https://github.com/iamvishnusankar/next-sitemap/issues/31#issuecomment-685724672
While the sitemap would be nice, I don't think it's that important, I've only added it, cause it was easy.

We can probably generate it separately with some script and just serve a static file. In the worst case it will be outdated before the next deployment happens.


[Fuzzing] fuzz testing support

using go-fuzz for fuzz testing of go-coap
How to run:
	go test -fuzz=FuzzDecode -fuzztime=10s $(PWD)/udp/coder/
	go test -fuzz=FuzzDecode -fuzztime=10s $(PWD)/tcp/coder/
	go test -fuzz=FuzzUnmarshalJSON -fuzztime=10s $(PWD)/message/codes/
	go test -fuzz=FuzzUnmarshal -fuzztime=10s $(PWD)/message/

Hello @0x34d , thank you for the contribution!
I would like to add all of the new test cases to CI testing job. The command in our GH workflow
go test -v -race ./... -coverpkg=./... -covermode=atomic -coverprofile=./coverage.txt

invokes them, but only with the preddefined seeds. It seems that running them all in a single command is not supported for now (if I read https://github.com/golang/go/issues/46312 correctly, but copying that script that invokes them all should work)

Hello @0x34d , thank you for the contribution!
I would like to add all of the new test cases to CI testing job. The command in our GH workflow
go test -v -race ./... -coverpkg=./... -covermode=atomic -coverprofile=./coverage.txt

invokes them, but only with the preddefined seeds. It seems that running them all in a single command is not supported for now (if I read golang/go#46312 correctly, but copying that script that invokes them all should work)

I have a better options.

If this project is accepted by the oss-fuzz team, then cifuzz is a better option.

If they don't, then ClusterFuzzLite is a really good option.

I have a better options.

If this project is accepted by the oss-fuzz team, then cifuzz is a better option.
If they don't, then ClusterFuzzLite is a really good option.

Thank you for the suggestions! I'm gonna apply to OSS-Fuzz and see what happens.

Well, i already did this, wait for my pr on oss-fuzz.

1- compile_native_go_fuzzer $(pwd)/message/. FuzzUnmarshal fuzz_unmarshal Could not find the function: func FuzzUnmarshal(f *testing.F)

I'm looking at the compile_native_go_fuzzer script. It happens because of this line:
if [ $(grep -r "func $function" $fuzzer_filename | grep "testing.F" | wc -l) -eq 1 ]

when I run it locally:
...
$ grep -r "func $function" $fuzzer_filename | grep "testing.F"

/home/danielius/go/src/github.com/plgd-dev/go-coap/message/options_test.go:func FuzzUnmarshal(f *testing.F) {
/home/danielius/go/src/github.com/plgd-dev/go-coap/message/codes/codes_test.go:func FuzzUnmarshalJSON(f *testing.F) {

Recursive grep and FuzzUnmarshal is prefix of FuzzUnmarshalJSON so it always finds both.

1- compile_native_go_fuzzer $(pwd)/message/. FuzzUnmarshal fuzz_unmarshal Could not find the function: func FuzzUnmarshal(f *testing.F)

I'm looking at the compile_native_go_fuzzer script. It happens because of this line:
if [ $(grep -r "func $function" $fuzzer_filename | grep "testing.F" | wc -l) -eq 1 ]

when I run it locally:
...
$ grep -r "func $function" $fuzzer_filename | grep "testing.F"

/home/danielius/go/src/github.com/plgd-dev/go-coap/message/options_test.go:func FuzzUnmarshal(f *testing.F) {
/home/danielius/go/src/github.com/plgd-dev/go-coap/message/codes/codes_test.go:func FuzzUnmarshalJSON(f *testing.F) {

Recursive grep and FuzzUnmarshal is prefix of FuzzUnmarshalJSON so it always finds both.

Fix:
perl -i -pe 'BEGIN{undef $/;} s/func Benchmark.*?\(b \*testing\.B\).*?\{.*?\n\}//smg' $(pwd)/udp/coder/coder_test.go
perl -i -pe 'BEGIN{undef $/;} s/func Benchmark.*?\(b \*testing\.B\).*?\{.*?\n\}//smg' $(pwd)/tcp/coder/coder_test.go
perl -i -pe 'BEGIN{undef $/;} s/func Benchmark.*?\(b \*testing\.B\).*?\{.*?\n\}//smg' $(pwd)/message/options_test.go
sed -i 's/FuzzUnmarshal/FuzzUnmarshalData/g' $(pwd)/message/options_test.go

I'm working on a new PR for go-coap to remove this regex code.
Here's my PR on oss-fuzz :) https://github.com/google/oss-fuzz/pull/10746/files


run config rows with invalid input should be user error

https://keboola.slack.com/archives/C02CGK5CL/p1549639567042800
run body: {"config":"358642681","row":{"id":"463615221"},"component":"keboola.ex-aws-s3","mode":"run"}
result:
{"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"failed to parse [params.row]"}],"type":"mapper_parsing_exception","reason":"failed to parse [params.row]","caused_by":{"type":"illegal_argument_exception","reason":"unknown property [id]"}},"status":400}

nemělo by to být spíš na syrup?
https://connection.keboola.com/admin/utils/logs?file=2019/02/08/16/2019-02-08-16-25-25-5c5d9f6587ddd-exception
https://connection.keboola.com/admin/utils/logs?file=2019/02/08/16/2019-02-08-16-25-25-5c5d9f65a2298-log

ok prehodil som to do syrupu https://github.com/keboola/syrup/issues/133


Sointu server for use with webassembly music

Related to https://github.com/petersalomonsen/javascriptmusic/pull/94

I am going to close this, maybe that motivates to finishing it :) I'll be happy to reopen then


Fix case where the user info are added dispite empty

Check failing test here , https://github.com/guzzle/guzzle/pull/2327

This is not according to rfc 3986

Applications should not render as clear text any data
after the first colon (":") character found within a userinfo
subcomponent unless the data after the colon is the empty string
(indicating no password)

I am not sure if I follow. At the moment if I do something like this:
        $uri = (new Uri('http://example.org/path'))->withUserInfo('', '');
        echo (string)$uri;

It will output<EMAIL_ADDRESS>Is this correct?

<EMAIL_ADDRESS>is a valid URI and browsers do accept it as well. It's basic auth with empty username and no password. There is not much use to it but it's valid.
Why not call withUserInfo('', null)? That would be the right thing to do as the default for password is null which means, no password.

Thank you.. I did not knew about this. I pushed a fixed to Guzzle client at the PR I mentioned above..

@Tobion this still seems to be a regression to me (as mentioned in #290), but I'm inclined to leave it as is if there is no real case where this can cause problems (except in the breaking tests).


Added HTTP 307

Added HTTP status code 307 TEMPORARY REDIRECT to RedirectionInterceptor.kt
https://httpstatuses.com/307

Hello, are there any concerns about the PR?

I don't. Thank you so much for this ✨ !!!


process is not defined when using a package that depends on it (in client)

Read me!
I fully understand that from several other issues mentioned here:
https://github.com/remix-run/remix/issues/1186, https://github.com/remix-run/history/issues/821, https://github.com/remix-run/remix/issues/2927
We should not be using process.env in the client. However, this issue is not concerning that. It's concerning the fact that other packages might be using it.
Wanted to start a discussion on this.
What version of Remix are you using?
1.8.2
Steps to Reproduce

install remix indie stack
install @paperxyz/react-client-sdk
use package import { PaperSDKProvider, LoginWithPaper } from "@paperxyz/react-client-sdk";
npm run dev
bug occurs

Expected Behavior
I expect us to be able to pull in this package @paperxyz/react-client-sdk
Actual Behavior
Uncaught ReferenceError: process is not defined
    at<EMAIL_ADDRESS>(index.js:5:1534)

This is because the client dependency @paperxyz/react-client-sdk has references to process.env in its source code. I can monkey patch this by directly going into the outputted index.js file from @paperxyz and setting the following
// inside<EMAIL_ADDRESS>
var process = {
  env: {}
};

Is there any way I can globally inject this fake variable into remix's client environment? I anticipate that other packages that utilize a reference to process.env in its source code will break with remix.

"@playwright/test": "1.29.0" (devDependencies) also cause the same error.
Remix packages version is 1.9.0.
index.js:17 Uncaught ReferenceError: process is not defined
    at<EMAIL_ADDRESS>(index.js:17:28)
    at __require2 (chunk-CUPSZOF3.js:18:50)
    at ../../node_modules/.pnpm/@playwright+test<EMAIL_ADDRESS>(index.js:26:49)
    at __require2 (chunk-CUPSZOF3.js:18:50)
    at ../../node_modules/.pnpm/@playwright+test<EMAIL_ADDRESS>(index.js:17:13)
    at __require2 (chunk-CUPSZOF3.js:18:50)
    at index.mjs:16:24


lint-staged not checking frontend tests folder

oh maybe lint-staged is not checking __test__?
npm run lint explicitly checks __test__:
"lint": "eslint src __tests__ & npm run type-check",
Slack Message

@dsadgat also setting this as P0 to prep for the spatial work!


"Cannot access '_A' before initialization" when using static properties and a static initializer

Describe the bug
When using both a static initializer block and static properties in a typescript class A, the compiled result produces an error:  Uncaught ReferenceError: Cannot access '_A' before initialization.
This is the class in question:
export class A {
  static MAP = new Map();

  static {
    Object.defineProperty(this.prototype, 'foo', { value: 123 });
  }
}

And vite compiles this to:
const _A = class {
  static {
    Object.defineProperty(_A.prototype, "foo", { value: 123 });
  }
};
export let A = _A;
A.MAP = /* @__PURE__ */ new Map();

Now this may very well be an upstream problem, but I wasn't able to figure out where it is caused. It seems that esbuild (with what little I understand of it) will produce correct results, either by compiling the static initializer into an IIFE (target es2020) or by keeping both constructs as they are (target esnext).
Maybe someone here can point me into the right direction? Maybe there's even a way to get this to work without having to wait for upstream fixes to land?
Reproduction
https://stackblitz.com/edit/vitejs-vite-xghabj?file=a.ts
Steps to reproduce
No response
System Info
System:
    OS: macOS 12.6.5
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 28.48 MB / 32.00 GB
    Shell: 5.2.15 - /usr/local/bin/bash
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
  Browsers:
    Chrome: 114.0.5735.106
    Chrome Canary: 116.0.5828.0
    Firefox: 108.0.2
    Firefox Developer Edition: 110.0
    Safari: 16.4.1
  npmPackages:
    vite: ^4.2.0 => 4.3.9

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

There seems to be a commit that already adressed this in esbuild (which was released in v0.18.2): https://github.com/evanw/esbuild/commit/c12cc901349759b8ce88012a1c13312e3a61e12d
When I force vite to use the 0.18.2 version of esbuild (instead of 0.17.19) (via {"overrides": {"esbuild": "0.18.2"}} in my package.json), the class compiles as it should.


JS Typed Arrays: Missing page title

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/typedarrays/
This is WCAG 2.4.2 https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-title.html

Also https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/familysearch/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/userselect/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/setimmediatesorting/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/analyzeperformance/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/chess/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/picture/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/coloringbook/

This one could be better as it is all one word and probably reads badly https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/twilioortc/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/math/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/@supports/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/eme/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/mandelbrot/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/webaudiotuner/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/microphone/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/css3filters/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/blobbuilder/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/photocapture/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/compatinspector/

https://developer.microsoft.com/en-us/microsoft-edge/testdrive/demos/audiomixer/


Broken links in README

Both links under the Contributing section lead to 404s

I know, I've not created those pages yet.


[vk] Access to this video has been restricted by the community's managers

Hi,
any solution te get video "restricted by the community's..." ?
using  yt_dlp-2022.9.1
python 3.9
Thanks.

This is not YT-DLP.

https://github.com/yt-dlp/yt-dlp/issues/new/choose


documentation on how to "paginate" results

I have put "paginate" in quotes because I am not referring to the paginate found in a offset/query based "page x of y" scheme, but as a "page" or chunk of rows in a infinite scrolling scheme.
The best I can tell from studying this library and the postings in the "use the index" site, the cursors are identified by the primary key of the row, and that I would still need to use limit in combination with those PKs to chunk the results.
With this in mind, I am not sure how to go about this properly with the Point/Space APIs in this library given a dynamic query.

On the first keyset paginated request for some records, the client would need to be given the following bits of info in the response:

The records in the current "page"
The cursor to get the previous "page"
The cursor to get the next "page"

In order to get the first item above, I could do a seek per the docs:
  Post.visible.seek([:id, :desc])

I could add a limit to change the behavior of the resulting after to infer the cursor for the next "page":
  Post.limit(10).visible.seek([:id, :desc])

However, I actually would have to fetch limit +1 for thespace.last to point to the cursor for the next "page".
I am already feeling like I am misunderstanding something. :)

On subsequent requests (e.g. now I have a cursor-- say id 42), I could use:
   Post.find(42).seek([:id, :desc])

Now I have a Point with a before and after. The before I won't use since this is an infinite scroller and the data is already on the client (otherwise I'd have to do additional calculation to get the before "page"'s start position).  The after once again would include all records, not just the next chunk, so calculating the cursor for the next "page" would involve similar limit +1 logic from above.

Now I definitely feel like I'm not using this library correctly!
If you could be so kind to provide some assistance, I would be willing to write some documentation on the wiki.

Not documentation but I went looking for examples where others are using it.
This project uses order_query.
https://github.com/MidnightRiders/MemberPortal/blob/03f72f47a650eb609d9b1c8e595ae3ad546ab581/app/views/matches/show.html.haml
In case that project disappears, this is the view that renders the next/previous links:
.row
  .small-4.medium-3.large-2.columns
    - if @order_point.previous(false)
      = link_to @order_point.previous(false), class: "button small expand primary-bg #{@order_point.previous(false).home_team.abbrv.downcase}" do
        = icon 'arrow-left'
        = @order_point.previous(false).home_team.abbrv
        v
        = @order_point.previous(false).away_team.abbrv
        = @order_point.previous(false).kickoff.strftime('%_m.%-d')
  .small-4.medium-6.large-8.columns.text-center
    = link_to matches_path(date: @match.kickoff.to_date), class: 'button small' do
      = icon 'calendar fa-fw'
      Back
  .small-4.medium-3.large-2.columns.right
    - if @order_point.next(false)
      = link_to @order_point.next(false), class: "button small expand primary-bg #{@order_point.next(false).home_team.abbrv.downcase}" do
        = @order_point.next(false).home_team.abbrv
        v
        = @order_point.next(false).away_team.abbrv
        = @order_point.next(false).kickoff.strftime('%_m.%-d')
        = icon 'arrow-right'

The controller sets up the @order_point object by doing @order_point = @match.order_selected(Match.all_seasons)
And the Match model has this code:
  order_query :order_selected,
              %i(kickoff asc),
              %i(location asc)

I have not pulled that project and attempted to run it. I've only sorted through to see how order_query was being used.

Hi, any additional documentation underway? If not, I'd be willing to contribute. My sense is that the usage explanation for the 'order_query' method could be a little clearer, and the examples might to well to use the limit method to make clear how the gem expects you to us AR to receive chunks.

Sorry about not being very clear in the readme, I'm not sure how to improve it. Nothing is underway currently. Please go ahead and send a PR.

@glebm Took a shot at clarifying the documentation on points where I got a little confused. And added a point about using limit. Let me know what you think!

Hi everyone, thanks for the various explanations, and thanks @niborg for the PR to expand the documentation. I'm getting a clearer idea of how this library can be used.


0456## - 132 Pattern

Description of the Problem
You may copy that from LeetCode
Code
Code

Link To The LeetCode Problem
LeetCode

Hi, can I be assigned for this issue?


Code snippet to plot radar points onto camera?

Hi,
Do we have any snippet of code to transform radar points onto camera FOV using some transformation matirx? Kindly help

Hi,
RadarScenes was meant as a "radar only" data set. The images from the documentary camera are just a reference for the developers, when they look at the data. It was never planned to fuse camera and radar data with the provided data set.
So there is no transformation matrix to project the radar point cloud into the camera image. This is anyway a hard task since there is no elevation information from the radar sensors available.


add exploitation subsection

The data management plan is part of the 'dissemination'. Is that on purpose? I would have taken, to have the 3 'official' D&E&C together. For example:

dissemination
exploitation
communication
data management plan

A pleasure to read.


Hide configuration of access roles apart from notebook level

The access roles settings don't actually do anything so we can remove them from the form sections, just leave the high level roles panel.

In fact there is no support for access control at all so at the moment all of this can be removed and we can re-add it when we add support in the main app.

Also, there is no support for form level annotation and uncertainty settings, so remove them as well.


Update docker images build section in README.md

Description
Update outdated build images section.
Affected Dependencies
n/a
How has this been tested?
Executing command locally
Checklist

[ ] I have followed the Contribution Guidelines and Code of Conduct
[ ] I have commented my code following the OpenMined Styleguide
[ ] I have labeled this PR with the relevant Type labels
[ ] My changes are covered by tests

Hi @vvmnnvk. I would wait to merge until Ionesio finishes with the reorganization


Changing peer keys doesn't work in wireguard-client unless make destroy

Once you install traefik with a wireguard-client container, if the peer keys change and you enter the new keys in traefik's config  and run make reinstall, the wireguard-client container launches wg with the old keys. you have to traefik/make destroy first.

It appears that it should always recreate the config from .env vars:
https://github.com/EnigmaCurry/d.rymcg.tech/blob/c15bd53163c3ffdff1d8a7cd7cada87b3a695e8a/traefik/docker-compose.yaml#L204-L221
https://github.com/EnigmaCurry/d.rymcg.tech/blob/c15bd53163c3ffdff1d8a7cd7cada87b3a695e8a/traefik/wireguard-client-config/setup.sh#L8
Can you reproduce it?

Yes, I can reproduce it. Here are the steps:

install traefik/wg as server on "sentry" droplet, install traefik/wg as client on local VM, confirm they can handshake
make destroy the sentry
make install the sentry - it now has new wg keys
make config the VM - config it with the new keys
make install or mae reinstall the VM
VM and sentry can no longer handshake, and wg on the VM shows the previous key next to "Peer" (not the new key)

ah, I see this in the logs now:
# docker compose -f docker-compose.yaml --env-file=.env_delorean-traefik-public_default --project-name=traefik logs -f -t wireguard-client-config
wireguard-client-config-1  | 2024-07-02T00:41:28.646565121Z rm: cannot remove '/config/coredns/Corefile': Permission denied
wireguard-client-config-1  | 2024-07-02T00:41:28.646885993Z rm: cannot remove '/config/templates/server.conf': Permission denied
wireguard-client-config-1  | 2024-07-02T00:41:28.646912353Z rm: cannot remove '/config/templates/peer.conf': Permission denied
wireguard-client-config-1  | 2024-07-02T00:41:28.647626922Z rm: cannot remove '/config/wg_confs/wg0.conf': Permission denied
wireguard-client-config-1  | 2024-07-02T00:42:24.005893395Z rm: cannot remove '/config/coredns/Corefile': Permission denied
wireguard-client-config-1  | 2024-07-02T00:42:24.005927059Z rm: cannot remove '/config/templates/server.conf': Permission denied
wireguard-client-config-1  | 2024-07-02T00:42:24.005952682Z rm: cannot remove '/config/templates/peer.conf': Permission denied
wireguard-client-config-1  | 2024-07-02T00:42:24.005978896Z rm: cannot remove '/config/wg_confs/wg0.conf': Permission denied

Thanks, I found the permission error due to unnecessary capabilities drop. I fixed it in a42aa19 as part of #237 .


CameraFrames: Access denied exeception with hololens

The app was build and deployed into HoloLens successfully, and the HoloLens has been activated into research mode. The app instantiated and found two MediaFrameSourceGroup, one is Sensor Streaming, the other MN34150. The MN34150 group worked, but Sensor Streaming never. The _mediaCapture.InitializeAsync(settings) for "Sensor Streaming" failed always with "Access Denied Exception". Actually, I only need the "Sensor Streaming" for Depth Image. Does anyone know the reason???

I've asked the feature team to investigate.

What version of Windows are you testing on? The feature team says that this is a known issue in the platform on Windows 10 version 1803. Please upgrade to Insider build 17743 or higher. If you still experience the problem, you can file an issue with Developer Support.

Visit http://aka.ms/storesupport and sign-in with your Microsoft account
Under the “App Development” section choose "Windows 10 universal app development", then choose the appropriate problem type and category to get engaged through a formal support channel.

Hi,
The answer is not correct. I am testing the uwp sample in hololens directly, which has been upgrated to OS RS4. The "access denied" issue was resulted from the wrong runtime linked to the CameraFrame C# project caused by wrong project configuration. Just modify the file CameraFrames.csproj by changing the value in the line 2 Project ToolsVersion="14.0" to "15.0", then the sample works! We have to edit the xml file, because this feature is not configurable over GUI.
Please leave the topic open, since more people would meet the same problem. I even have futher problem with this ToolVersion configuration. Since I am delevoping hololens App with unity, the project code exported by unity has all the ToolVersion = "14.0", thus results in the "access denied" problem again. Manually change the project configuration results in other symbol conflicts to the dlls that are pre-compiled by unity.
best regards

Sorry, my mistake. The exception was resulted from the missing
<rescap:Capability Name="perceptionSensorsExperimental" />
in the Package.appxmanifest.
Adding this property did solve the problem, not the ToolVersion.
best regards


C++ Style Comments Conflicts with C90 Standard

Attempting to compile with -std=c90 to check the claim that the codebase is compatible with the C90 standard results is many errors around C++ style (\\) comments.
I more than happy to fix these by replacing with C90 comments (\**\) or would you consider bumping up the C standard to C99 to support the C++ style?

I'd vote for just bumping to C99. I'll update the docs as such.
Strange though that gcc 2.9 (1998) on an old LynxOS/PowerPC does not barf on it (we still use that on some machines at the SMA). Perhaps, it already using the C99 standard? (I just assumed it was C90 given its age).

I think C99 is a good idea - it's the current JPL coding standards target. IIRC old GCC silently supports these comment styles and only complains when you explicitly supply the standard with -std

Updated docs to C99 at ffc8e40


Define how fitter node can tell if an analysis is possible

For example: dimension of a fit
generally: what type of data does a Fit even accept to work correctly?
Idea: have a function per analysis that checks for validity?
Eventually:
How should plottr behave when data is not valid?
For example: if we have 2d data, but 1d fit: should we automatically 'batch' fit? (not most urgent)

For data with multiple dependent variables, how should the fitter know which one to fit?
Should I add a dropdown data selection widget in fitter? or just attach the name of data to be fitted as a metadata in dataDict?


Moonscraper Chart Editor v<IP_ADDRESS> Windows 64 Installer blocked by Windows defender as severe threat Trojan virus

Upon uploading the file to VirusTotal, Windows Defender did not flag the file as malicious, so this is no longer an issue.


change automatic_masking script rembg model

I'm testing the automatic_masking script and rembg with different models
https://github.com/agisoft-llc/metashape-scripts/blob/master/src/automatic_masking.py
In the rembg code this command changes the model
rembg i -m isnet-general-use path/to/input.png path/to/output.png
Is it possible to change the model used the isnet-general-use ?

Hi, Henry.
Now, you can change name of used AI-model in this line: https://github.com/agisoft-llc/metashape-scripts/blob/50f0fbcc131154ace48b97bc33638851990c90a7/src/automatic_masking.py#L35
Why are you interested in isnet-general-use model? Is it better then unet in your case?

Hi, yes from testing the models, isnet-general-use produced better results for our data.
Thankyou for making that addition to the script to choose the model.
 So mask interpretation is binary. In case of cameras alignment we just want to mask out background pixels - to get rid of keypoints on background.
Also, this script generates masks without alpha-matting because in such way rembg works much faster.
Feel free to re-open this issue if needed.


Swiping not working

Hi, I downloaded the demo project to test it, but I don't seem to be able to swipe left or right. The only way to do so is by touching the buttons "Swipe left" and "Swipe right", not by dragging it. Any help with that?
Thank you!

I just updated the demo app. Could you try out the latest version and see if it works? Also, are you running the demo app on device or simulator? What are the version numbers for Xcode, iOS SDK and device's OS?

Hey there
It is working on the current version! thank you!
I'm running the demo app in the simulator, Xcode 6, iOS 7.1 and iPhone 5s.

Thanks!


Request Parameter 'Text'

I can't use the Array[String] type in the Text parameter?
When I try to do this, I get the error 400.
I have read your documentation. It says only String type.
I want to send multiple strings in one request. I could, of course, come up with some kind of separator in this case and pray that Deepl doesn't translate or remove it during processing...

Use \n pls

As a lines separator?
My texts can already use \n for a line break as it is....