text:
How to get result from "expect" function

Guys hello.
Help me please understand how I can get a result (passed or failed) from "expect" function.
I have such example code:
describe("Regression tests", function() {

it("Test1", function() {
    expect("Implementation-Title").toContain("Title");
    if (expect("Implementation-Title").toContain("Title") == 'passed'){
        //Do some actions;
    }
    else{
        //Do some actions;
    }});

it("Test2", function() {
    expect(2).toEqual(2);
    if (expect(2).toEqual(2) == 'passed'){
        //Do some actions;
    }
    else{
        //Do some actions;
    }
});});

How I can get a result (passed or failed) for each "it" and then, depends on result, do some actions?
I need to validate exceptions and if it's present, I need to do some actions (for example send exception to TestRail).
Thanks for support

Expectations throw when they fail, so any code after an expectation that executes means all the previous expectations passed.
What's your real-world need for executing code conditionally when expectations fail?

This is my real code:
var Login = require('./../login/login.page.js');
var TopmenuPage = require('../menu/top-menu.page.js');
var TestRail = require("node-testrail");
var testrail = new TestRail("http://192.168.2.414/testrail", "user", "password");

describe('Login scenario: ', function () {
var loginPage;

beforeEach(function () {
    loginPage = new Login();
});

afterEach(function() {
    browser.manage().deleteAllCookies();
});

it('should successfully log in', function () {
    loginPage.login(browser.params.user,browser.params.password);
    expect(TopmenuPage.logoutButton.isPresent()).toBe(true);
    expect(TopmenuPage.welcome).toContain("Welcome " + browser.params.user);
    if ("failed"){
        testrail.addResult(16620, "5", "This test failed", "test", "", "", "", function(body) {
            console.log(body);});
    }
    else{
        testrail.addResult(16620, "1", "This test passed", "test", "", "", "", function(body) {
            console.log(body);});
    }
});

it('should fail to login user with wrong permissions', function () {
    loginPage.login('user2',browser.params.password);
    expect(loginPage.dangerAlert).toContain("Authentication Failed: User does not have required permissions");
    if ("failed"){
        testrail.addResult(16621, "5", "This test failed", "test", "", "", "", function(body) {
            console.log(body);});
    }
    else{
        testrail.addResult(16621, "1", "This test passed", "test", "", "", "", function(body) {
            console.log(body);});
    }
});

it('should fail to login user with wrong credentials', function () {
    loginPage.login('test_user','test_user');
    expect(loginPage.dangerAlert).toContain("Invalid credentials");
    if ("failed"){
        testrail.addResult(16622, "5", "This test failed", "test", "", "", "", function(body) {
            console.log(body);});
    }
    else{
        testrail.addResult(16622, "1", "This test passed", "test", "", "", "", function(body) {
            console.log(body);});
    }
});});

If test will failed, I send fail result to TestRail, and if test will passed, I send passed results to TestRail.
But I don't know how to get failed result from expect function?
For example looks like this:
result.status == "failed"

I'm not familiar with any test framework which allows you to get pass/fail results in this manner. It seems like you'd want a tighter mocha/testrail integration, but I'm not really sure what the best approach is.

Because expect throws an AssertionError when failed, you can use try ... catch statement:
try {
  expect(foo).toExist()
  console.log('passed')
} catch (e) {
  console.log('failed')
}

However, as @ljharb pointing out, there might be a better integration solution for TestRail.

Thank you. I'll try.

I was found a solution!
I use jasmine reporter it have function "result.status == "passed". Thank you for help!

authors: Alexml8456 ljharb wuct

repo: mjackson/expect


text:
TagHandler is broken when tag values contain ': ' sequences.

If I:
$ exiftool -Caption-Abstract="Bob: The worst human I know." sample.jpg

Then try to use exiftool-lib to extract Caption-Abstract, it breaks.
The problem is in TagHandler. This:
// Now, we are sure we can process line.
String[] pair = TAG_VALUE_PATTERN.split(line);
if (pair != null && pair.length == 2) {

Should be this:
// Now, we are sure we can process line.
String[] pair = TAG_VALUE_PATTERN.split(line, 2);
if (pair != null && pair.length == 2) {

According to the docs for split:

The limit parameter controls the number of times the pattern is applied and therefore affects the length of the resulting array. If the limit n is greater than zero then the pattern will be applied at most n - 1 times, the array's length will be no greater than n, and the array's last entry will contain all input beyond the last matched delimiter.

So we want split(line, 2), not split(line). Because in my example above you'd get pair.length == 3 and it would be silently skipped.
Also, it seems like a log.warn("Skipped: %s", line); would be justified in the else for that if.
Thanks, -Sam

Thanks for your feedback and your PR, new version will be available on maven central soon.

source: gharchive/issue

authors: mjeanroy sam

repo: mjeanroy/exiftool

license_type: permissive

license_source: bigquery


text:
Outlook Mail Client Text Visible only After Resize

I am having issue with outlook mail client text display.
By default the text in outlook is not getting displayed but after resizing the window to any size, the text becomes visible.
I have added images below for better understanding.
Screenshots
By default the text is not displayed :

But when window is resized to any size the text shows up

The email template is based on Confirmation Email Template
MJML Version
mjml --version
2.2.0
Email clients the bug is seen on:
Outlook Mail Client
I have attached the mjml file as a  text file
welcome.txt
Can someone point out how I can solve this issue.?
P.S I cannot ask the users to resize the window.
Thanks

Try wrapping the text with a span style and giving the text size an !important tag.

@lRlevolution I tried with adding display:block !important to all span elements above the text and the issue still exists.

Hi @Tanmayshetty, thanks for reporting. That's a weird behaviour indeed, we'll investigate to understand what happens.

Hey @Tanmayshetty, have you had a similar issue lately? I just tried with MJML v3.0.2 and there doesn't seem to have any issue on Outlook Mail so I'm closing.
Feel free to reopen if you see a similar issue happen!

authors: Tanmayshetty lRlevolution ngarnier

repo: mjmlio/mjml

license: MIT

license_source: github-api


text:
Episode and Season numbering

The Plex XML output orders Seasons and Episodes. Plex JS uses this ordering to name episodes in the Plex GUI.
Should be able to set
episode_obj.episode_number = X
episode_obj.season_number = X
in the Episode class.
Also would be nice to have a definite integer attribute for season number as well, could be handled in the same way.

Expect a pull request for this added functionality in the next few hours. Working on it now.

The major problem with implementing this is the modular way that the XML parsing is done. When an item is built it doesn't have any context of where it was in the XML that came from Plex.
To pass this info down to the Season/Episode objects will require passing down an 'index' parameter into the object.
OR
after an item has been built, if it is part of a list it's index can be added to the item as an 'index' attribute, which could then be read. The downside to this is that the object is already created, and the listItems function doesn't know what type of object it is. It's a bit ugly to put in a 'if type == season' conditional in the listItems function, but it's also very ugly to persist 'index' as a parameter way down to the leaf object constructors.

I've been thinking about this problem a bit as well. The Season objects used to include index and parentTitle attributes, but seems to have been removed sometime in the last few months.  not sure about the best way to solve it.
The problem with knowing where you came from is not ideal either because you may not always to the the a Season object through it's Show. You can go directly there if you wanted. Maybe we do a combination of both.  Pass in the index if we have it, make a second request to the Show (from the Season) if we request index and do not have it yet?

Pull Request #55 should solve this issue. Only added 5 lines I think. Was pretty easy to add and I think it's a fairly elegant solution.

commit 36b5d12a192ac0574c33b0849f1087b17f805c9b
Author: Michael Shepanski mjs7231@gmail.com
Date:   Thu May 19 23:42:06 2016 -0400
Add back missing index value from Show,Season,Episode; Make season numbers a bit easier to fetch


text:
Update setup.py

Fixes problems related with "ld: library not found for -lodbc" during the build phase. Considering you're compiling on OS X 10.9 or 10.10 and installed unixodbc with homebrew

Yep. I'm using 10.10 also and the compiler had some trouble without the extra_link_args

I'm not seeing that, but I am on the latest 10.10.4 beta and my Xcode is out of date.  I should grab the latest to match the beta.
What versions do you have?
The installation method of unixODBC could make a difference too.  I installed via Homebrew, I think, which may have put the libs somewhere Xcode would pick them up automatically?  I'll have to look into this.  How did you install unixODBC?

source: gharchive/pull-request

authors: diogommartins mkleehammer

repo: mkleehammer/pyodbc


text:
Table component

If single row in Table component, it does not show.

I mean when null both include_columns and execlude_columns

@meynot is it possible to paste your sample code here or you can mail to mike@bladewindui.com. I need to know exactly which attributes you are using so I can replicate the problem.

@meynot I managed to reproduce the error. Will be fixed in next update.

authors: meynot mkocansey

repo: mkocansey/bladewind


text:
Cannot ignore sensors

I feel like I have set the config file up correctly.
   {
        "platform": "Alarmdotcom",
        "name": "Security Panel",
        "username": "my login at Alarm.com",
        "password": "my password at Alarm.com",
        "armingModes": {
            "away": {
                "noEntryDelay": false,
                "silentArming": false
            },
            "night": {
                "noEntryDelay": false,
                "silentArming": false
            },
            "stay": {
                "noEntryDelay": false,
                "silentArming": false
            }
        },
        "ignoredDevices": [
            "95937424-1",
            "95937424-2",
            "95937424-3",
            "95937424-4",
            "95937424-5",
            "95937424-6",
            "95937424-7",
            "95937424-8",
            "95937424-9",
            "95937424-10",
            "95937424-12",
            "95937424-229",
            "95937424-5267",
            "95937424-5270",
            "95937424-5271"
        ],
        "logLevel": 4
    },

I can arm and disarm the panel etc... But I can't seem to hide all the sensors from Homekit. I have deleted cached accessories and rebooted but still can't ignore accessories. The log shows accessories are ignored but Homebridge is still responding to changes in sensor state. The sensors also still show in the Home app.
[2020-1-7 11:37:25] [Security Panel] Received 1 partitions(s) and 15 sensor(s) from Alarm.com
[2020-1-7 11:37:25] [Security Panel] Received 0 light(s) from Alarm.com
[2020-1-7 11:37:25] [Security Panel] Received 0 locks(s) from Alarm.com
[2020-1-7 11:37:25] [Security Panel] Removing partition1 (95937424-127) from HomeBridge.
[2020-1-7 11:37:25] [Security Panel] Adding partition partition1 (id=95937424-127, uuid=9175dbea-cf34-4f64-82aa-598248bdf25c)
[2020-1-7 11:37:26] [Security Panel] Updating partition partition1 (95937424-127), state=3, prev=null
[2020-1-7 11:37:26] [Security Panel] Updating partition partition1 (95937424-127), desiredState=3, prev=null
[2020-1-7 11:37:26] [Security Panel] Updating partition partition1 (95937424-127), statusFault=false, prev=null
[2020-1-7 11:37:26] [Security Panel] Added partition partition1 (95937424-127)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Dining Room Slider (95937424-4)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Front Door (95937424-7)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Garage Door (95937424-2)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Garage Door Exterior (95937424-3)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Main (95937424-9)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Main Room Slider (95937424-5)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Master (95937424-10)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Master Bedroom Slider (95937424-6)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Panel Camera (95937424-229)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Panel Glass Break (95937424-8)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Retha (95937424-5270)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Scott (95937424-5271)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Scott iPhone (95937424-5267)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Smoke Detector (95937424-12)
[2020-1-7 11:37:26] [Security Panel] Ignored sensor Translator (95937424-1)
[2020-1-7 11:47:19] [Security Panel] Updating sensor Main Room Slider (95937424-5), state=0, prev=1
[2020-1-7 11:48:21] [Security Panel] Updating sensor Main Room Slider (95937424-5), state=1, prev=0

Oops! Had to kill home bridge, THEN delete cache! My Bad!

repo: mkormendy/homebridge-node-alarm-dot-com


text:
To make it work with DS 6.2

Maybe this should be comment rather than an issue?
(Sorry for 1 more issue, but I hope it's useful)
To make the Dockefile work with DS 6.2, there are 3 important changes that are needed
Obviously, the first line should change from:
FROM nvcr.io/nvidia/deepstream:6.1-devel
to
FROM nvcr.io/nvidia/deepstream:6.2-devel
But there are 2 more things:

Add this line after line 7:
ENV CUDA_MODULE_LOADING=LAZY
That's new in 6.2 and I presume it will be ignored in 6.1 and before

Add this line between current line 15 and 16:
RUN bash /opt/nvidia/deepstream/deepstream/user_additional_install.sh
As that will install the extra libraries taht are no longer part of the default package since 6.2

Do you have a repo fork somewhere with code to get started? If so, I could take a look

Hi Joxis,
I'm afraid not. I was just doing some edits locally to make it work and understand how it works. But all the changes to 6.2 are mentioned in the first post. Just the additional libraries are the issue.
(Feel free to close the tickets if it's not worth it. I'll take no offense)

How to use this repository with the yolov5 model as well as the custom yolov5 model?

authors: Al-Hasib GerardNL Joxis


text:
Model saving is calling on git which causes an issue when the subprocess library is from the system

Describe the bug
When the subprocess library is called from the system installation of python, git invocation does not work, since there is no git repo for the system python installation.
To Reproduce
Steps to reproduce the behavior:

Start GaNDLF training
See the following error:

$ > cat ${error_log}
[SNIP!]
  File "/geode2/home/u070/patis/BigRed200/projects/gandlf_mine/GANDLF/compute/training_loop.py", line 290, in training_loop
    save_model(
  File "/geode2/home/u070/patis/BigRed200/projects/gandlf_mine/GANDLF/utils/modelio.py", line 159, in save_model
    subprocess.check_output(["git", "rev-parse", "HEAD"])
  File "/N/soft/sles15/deeplearning/Python-3.10.10/Lib/subprocess.py", line 421, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/N/soft/sles15/deeplearning/Python-3.10.10/Lib/subprocess.py", line 503, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/N/soft/sles15/deeplearning/Python-3.10.10/Lib/subprocess.py", line 971, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/N/soft/sles15/deeplearning/Python-3.10.10/Lib/subprocess.py", line 1847, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)

Expected behavior
The model saving should work.
Screenshots
N.A.
GaNDLF Version

0.0.17-dev
Desktop (please complete the following information):
N.A.
Additional context
This is seen for the IU BigRed cluster.

I have fixed this, and will put a PR soon.

repo: mlcommons/GaNDLF


text:
iOS build crashes in release mode

In release and profile modes XCode optimizes the app and removes "unused" symbols from native libs.
We dynamically load symbols from a statically linked library so all of our exported functions are "unused".
We have a workaround for this but we didn't add new backend API functions there.
We didn't catch this on iOS CI because the CI uses debug mode to test the app.
We should modify the CI to use profile mode.

We didn't catch this on iOS CI because the CI uses debug mode to test the app.
We should modify the CI to use profile mode.

I don't think we will be able to implement this on our current CI.
We test using iOS Simulator, and Flutter is only able to launch the app in debug mode in a Simulator.
After some experiments I was able to launch the app with --profile flag but it seems that the app was not recompiled, and it still launched in debug mode.
Launching the app in profile or release mode directly from XCode also doesn't work.
We may fix this by using a physical device, for example from Firebase but I don't think this should be done in this issue.
I think we should address this after we move our iOS CI to a cloud service.


text:
Implemented plugin macros (MLDB-1904)

Improvements to macros to allow plugins to include installed directories and binaries

It reads ok to me.

authors: jeremybarnes jraby

repo: mldbai/mldb


text:
Some questions about the code

Hi, thanks for your code! And i have some questions to confirm.
1. unmatched weight
elif args.bert == 'sci':
            self.text_decoder = BertLMHeadModel.from_pretrained('allenai/scibert_scivocab_uncased',config=decoder_config)

The error here is
RuntimeError: Error(s) in loading state_dict for BertLMHeadModel:
	size mismatch for bert.embeddings.word_embeddings.weight: copying a param with shape torch.Size([31090, 768]) from checkpoint, the shape in current model is torch.Size([31092, 768]).
	size mismatch for cls.predictions.bias: copying a param with shape torch.Size([31090]) from checkpoint, the shape in current model is torch.Size([31092]).
	size mismatch for cls.predictions.decoder.weight: copying a param with shape torch.Size([31090, 768]) from checkpoint, the shape in current model is torch.Size([31092, 768]).
	size mismatch for cls.predictions.decoder.bias: copying a param with shape torch.Size([31090]) from checkpoint, the shape in current model is torch.Size([31092]).
	You may consider adding `ignore_mismatched_sizes=True` in the model `from_pretrained` method.

only when i add 'ignore_mismatched_sizes=True', it works.
2. the self.args.task
in knowledge.py
if self.args.task == 'pretrain' or self.args.task == 'retrieval':

but there is no task in the args
3. GPU number
the --n_gpu=1 ,and error here is
RuntimeError: Default process group has not been initialized, please make sure to call init_process_group.

I don't know if it is a mistake in the code. I hope you can help me confirm it. Thanks in advance~

Hi, sorry for the inconvenience. We have noticed these issues and will update the code soon.

I meet the same question, and I want to know ,if the code support undistributed training?

@NorthTree22 Hi, it does support. I will update the code soon.

@NorthTree22 👋Hey!  I have met you in other repositories related to report generation. Could you please leave your email address so that we can exchange some relevant content. 😆

@NorthTree22 👋Hey! I have met you in other repositories related to report generation. Could you please leave your email address so that we can exchange some relevant content. 😆

@Eldo-rado Ok, that would be great. You can contact me at 2874338756@qq.com

@NorthTree22 Hi, it does support. I will update the code soon.

Thank you very much. Look forward to your update.

I meet the same question

I meet the same question

how to solve the problem 'unmatched weight'? Only 'ignore_mismatched_sizes=True'?

how to solve it?
if self.args.task == 'pretrain' or self.args.task == 'retrieval':?

how to solve it? if self.args.task == 'pretrain' or self.args.task == 'retrieval':?

Please do not try my solutions 😂, as they are just simple attempts and are not succeed in running the code.
Please wait for an update from the author.

My email is 337940719@qq.com. I have solve the problems you can contact me~ 😊

My email is 337940719@qq.com. I have solve the problems you can contact me~ 😊

@Junyiliu0 Hi, did you solve the following problem? Can you share your solution?
if self.args.task == 'pretrain' or self.args.task == 'retrieval':?

I also want to know
how to solve it?
if self.args.task == 'pretrain' or self.args.task == 'retrieval':?

I meet the same question

how to solve it? if self.args.task == 'pretrain' or self.args.task == 'retrieval':?

I also encountered this problem, how did you solve it

My email is 337940719@qq.com. I have solve the problems you can contact me~ 😊

@Junyiliu0 Hi, did you solve the following problem? Can you share your solution? if self.args.task == 'pretrain' or self.args.task == 'retrieval':?

I also encountered this problem, how did you solve it


text:
feat: add sections data layer

What Issue does this PR resolve? (Link to GitHub Issue, approved features and bugs will be given priority)

Consolidates all section data handling into a centralized module
Automatically migrate data from versions 1.4.1-2.0.1 to the current format, in a robust and fully type-safe manner
Make imports fault-tolerant

sections that can be successfully converted to new format are added
sections that fail on convert are skipped and user is notified

Allow export buttons to directly access storage rather than needing to pass down state to them
Fixes bug where clicking on import buttons was unresponsive

Please provide a video demo below, or a screenshot and description of the change.
Should be pretty much the same visually.
Tag reviewers for the PR below.

note: i'd like for this PR to be rebased, to preserve the commits in develop - will make it easier to bisect later if the changes introduce any unexpected changes.

repo: mlool/workday-calendar-extension


text:
Ending Early error due to queries_issued in server scenario

In server scenario, there's an error looks weird as below,
"pid": 319114, "tid": 140443789978112, "ts": 955579ns : POWER_BEGIN: "mode" : Performance, "time" : 08-28-2019 22:00:01.671
"pid": 319114, "tid": 140443789978112, "ts": 488381497ns : Ending naturally: Minimum query count and test duration met.
"pid": 319114, "tid": 140443789978112, "ts": 488435298ns : POWER_END: "mode" : Performance, "time" : 08-28-2019 22:00:02.158
"pid": 319114, "tid": 140443789978112, "ts": 488436703ns : ERROR : Ending early: Ran out of generated queries to issue before the minimum query count and test duration were reached.
"pid": 319114, "tid": 140443789978112, "ts": 488436703ns : Please update the relevant expected latency or target qps in the TestSettings so they are more accurate.
The 2 bold msg seems conflict each other, the code in loadgen generatea the error is as following,
if (scenario != TestScenario::Offline && mode == TestMode::PerformanceOnly &&
queries_issued >= queries.size()) {
LogDetail([](AsyncDetail& detail) {
detail.Error(
"Ending early: Ran out of generated queries to issue before the "
"minimum query count and test duration were reached.");
detail(
"Please update the relevant expected latency or target qps in the "
"TestSettings so they are more accurate.");
});
}
Shall it be queries_issued > queries.size() ?

Shall it be queries_issued > queries.size() ?

Hi @xgu3. Thanks for pointing this issue out. We should definitely fix it.
The proposed fix isn't quite right since it will never evaluate to true (we won't issue more queries than we've generated). Instead, we should set a flag when exiting naturally and check for !exited_naturally.
Do you have cycles to put together a PR?

Yes, I’ll try it out.
Best Regards
Alex
The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.
From: Brian C. Anderson notifications@github.com
Sent: Thursday, September 5, 2019 8:17 AM
To: mlperf/inference inference@noreply.github.com
Cc: Gu, Alex alex.gu@intel.com; Mention mention@noreply.github.com
Subject: Re: [mlperf/inference] Ending Early error due to queries_issued in server scenario (#370)
Shall it be queries_issued > queries.size() ?
Hi @xgu3https://github.com/xgu3. Thanks for pointing this issue out. We should definitely fix it.
The proposed fix isn't quite right since it will never evaluate to true (we won't issue more queries than we've generated). Instead, we should set a flag when exiting naturally and check for !exited_naturally.
Do you have cycles to put together a PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mlperf/inference/issues/370?email_source=notifications&email_token=AGA24IOVV7KNWHHQZS3FJT3QIBFZLA5CNFSM4IRIUQPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD55NAAY#issuecomment-528142339, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGA24IPPVDWRCV73G4OR2I3QIBFZLANCNFSM4IRIUQPA.

I ended up fixing this as part of another fix since it was related: https://github.com/mlperf/inference/pull/398
@xgu3 : Can you verify that PR addresses the error you see as well?

@briandersn Just verified and the error is gone. Thank you very much!

Closing.

repo: mlperf/inference


text:
Updated flask default port to 5001

Fixed #199

The entire purpose of the --port argument is that a user can specify a custom port, so I encourage you to use that argument as designed.

repo: mmabrouk/chatgpt-wrapper


text:
tse

Summary

Context

test

repo: mmistakes/minimal-mistakes

license: mit


text:
Interactive list

In this PR the following was done:

Add interactivity to mark selected tasks completed
Add line striking to the selected task description
Add methods to enable element dragging and dropping effect

Thanks for taking your time to review my project.

repo: mmsesay/todo-list


text:
MRG: Clean up and unify _prepare_forward

This PR should not change any outputs, but internally it:

[x] Refactors _prepare_forward and _check_loose_forward to greatly simplify the logic they use, and deduplicate checks/flows across MNE and sparse solvers.
[x] Adds ordered argument to pick_channels and pick_channels_forward, which is something that I have often wanted. Eventually we can probably simplify a lot of our code using ordered=True, as there are a lot of places we do the same picking-with-order logic instead of picking-as-set logic.
[x] Fixes the CircleCI regression in master.
[x] Deprecates the old way of using compute_depth_prior in favor of a cleaner, Forward-based method.
[x] Adds an ignore for scanno in the inv round-trip test (should not matter, and I think our result is now possibly more correct because it resets scanno to match the number of entries in info)

These are important for #5881, and are hopefully the last steps we need (along with #5979) before having easy, unified, drop-in lead-field normalization across all solvers (!).
Ready for review/merge from my end @agramfort

This pull request introduces 1 alert when merging 4ee9f7cbb801d3126358bc34ed88d21afc8f99b0 into f7bb2ef4a40bf3bc3e20c82feba145e0e6e35aac - view on LGTM.com
new alerts:

1 for Redundant comparison

Comment posted by LGTM.com

Merged after chat with @agramfort

Thx @larsoner

authors: agramfort larsoner

repo: mne-tools/mne-python


text:
WIP: Pick the requested channel type early

So we don't have to worry about it during later processing steps!

Oh wow this went smoother than I had expected!

Just pick afterwards

CIs complain but diff looks good

Hopefully it works now.
Before ba14f2e:

After ba14f2e:

thx @hoechenberger !

authors: agramfort hoechenberger

repo: mne-tools/mne-study-template


text:
ENH, TESTS: Improved filename sanitization

This PR adds improved sanitization for filenames. Previously, we would only remove os.sep from filenames; however, this is not the only invalid character, and also it's OS-dependent. To ensure filenames are compatible with different operating systems, we have
to apply much stricter rules.
I have added a module pathtools.py that contains a sanitize_filename function, which removes all non-alphanumeric characters (except -, _, and .) from a filename. Having the sanitization done in a single place also allows for easy adjustment. For example, I personally would  prefer to replace invalid characters with _; but the current implementation was designed such that it would resemble the behavior of the existing code.
To test this module, I have also enabled pytest on our CI system.

@hoechenberger did you hit a bug to start addressing this issue?

@agramfort
+1 on general discussion
Regarding the specific question of filename sanitization – however we decide to do it, I think there should only be a central place where the sanitization method is specified. With the in-place string formatting in master (via str.replace(), one would have to change several (at least 3) different places if one decided to change the sanitization somehow (e.g., move from dropping invalid characters to replacing them with dashes)

Not to prematurely trigger the discussion, but I highly suggest doing a "literature survey" and looking at what other similar libraries do. E.g., Jupyter-book (or maybe sphinx gallery too?) has a similar flavor -- it provides a template book that can be modified by users. Maybe other cookiecutter/template projects in sklearn and MNE? What ideas can we borrow? What ideas don't work and are bad?

authors: agramfort hoechenberger jasmainak


text:
[Bug] 插件设置界面标题不会自动更新

进入设置界面，先点击BetterQQNT再点击登录设置，标题还是BetterQQNT。先点击其他插件设置，再点击登陆设置，也是如此。
不影响使用，但强迫症（

已知问题，随便点个插件的设置选项，再点击QQ的选项，再点回QQ选项即可触发

这个bug我觉得应该没人会触发（毕竟藏得还是有点深的，我就没管它了（

repo: mo-jinran/BetterQQNT


text:
与其他显示在任务栏的应用冲突

win11 22H2
在任务栏居左时，与TrafficMonitor的性能显示冲突

1.2.3版本会与TrafficMonitor的显示重叠，希望保持原来直接覆盖上层的显示方式

最新版本与TrafficMonitor重叠，之前的不会

TrafficMonitor我自己也在用，是个已知问题，会修的不要着急

想了想，感觉不是很好做。之前的窗口是不透明的只是放在任务栏上莫名其妙透明了所以能覆盖掉TrafficMonitor，现在窗口是真的透明了所以覆盖不掉TrafficMonitor。目前我的想法是把TrafficMonitor隐藏，或者留出一块空地给TrafficMonitor显示（自定义左右边距距离，而且还能解决其他这类软件的问题

自定义调节左右边距，支持负数

authors: PIut02 RingZc mo-jinran wangzipai

repo: mo-jinran/Taskbar-Lyrics


text:
🔒 New Unity Editor Releases

Each time a new UnityEditor is released, new comments are added by zapier.

Release 2021.1.25f1
Thu, 14 Oct 2021 23:57:59 +0200
https://unity3d.com/unity/whats-new/2021.1.25

/build-all

/build-all
2022.2.11f1
2023-03-15T02:33:37
https://unity.com/releases/editor/whats-new/2022.2.11

/build-all
2023.1.0b8
Thu, 16 Mar 2023 16:00:09 +0000
https://unity.com/releases/editor/beta/2023.1.0b8

/build-all
2023.2.0a6
Thu, 16 Mar 2023 16:12:18 +0000
https://unity.com/releases/editor/alpha/2023.2.0a6

/build-all
2023.2.0a6
2023-03-15T17:05:39
https://unity.com/releases/editor/alpha/2023.2.0a6

/build-all
2023.1.0b8
2023-03-15T15:20:07
https://unity.com/releases/editor/beta/2023.1.0b8

/build-all
2022.2.12f1
2023-03-22T19:38:11
https://unity.com/releases/editor/whats-new/2022.2.12

/build-all
2023.2.0a7
2023-03-22T21:21:49
https://unity.com/releases/editor/alpha/2023.2.0a7

/build-all
2023.2.0a7
Thu, 23 Mar 2023 06:09:01 +0000
https://unity.com/releases/editor/alpha/2023.2.0a7

/build-all
2023.1.0b9
2023-03-22T17:34:30
https://unity.com/releases/editor/beta/2023.1.0b9

/build-all
2023.1.0b9
Fri, 24 Mar 2023 06:09:01 +0000
https://unity.com/releases/editor/beta/2023.1.0b9

build-all
Release 2021.1.25f1
Thu, 14 Oct 2021 23:57:59 +0200
https://unity3d.com/unity/whats-new/2021.1.25

/build-all
2021.3.22f1
2023-03-29T20:44:06
https://unity.com/releases/editor/whats-new/2021.3.22

/build-all
2023.1.0b10
2023-03-29T19:31:31
https://unity.com/releases/editor/beta/2023.1.0b10

/build-all
2021.3.22f1
Fri, 31 Mar 2023 06:09:01 +0000
https://unity.com/releases/editor/whats-new/2021.3.22

/build-all
2023.1.0b10
Fri, 31 Mar 2023 06:09:01 +0000
https://unity.com/releases/editor/beta/2023.1.0b10

test

/build-all
2022.2.13f1
2023-03-31T14:48:28
https://unity.com/releases/editor/whats-new/2022.2.13

/build-all
2022.2.13f1
Sat, 01 Apr 2023 06:09:02 +0000
https://unity.com/releases/editor/whats-new/2022.2.13

/build-all
2022.2.14f1
2023-04-05T22:20:20
https://unity.com/releases/editor/whats-new/2022.2.14

/build-all
2020.3.47f1
2023-04-05T16:12:43
https://unity.com/releases/editor/whats-new/2020.3.47

/build-all
2023.2.0a9
2023-04-05T17:17:10
https://unity.com/releases/editor/alpha/2023.2.0a9

/build-all
2023.1.0b11
2023-04-04T21:58:08
https://unity.com/releases/editor/beta/2023.1.0b11

/build-all
2022.2.14f1
Fri, 07 Apr 2023 06:12:01 +0000
https://unity.com/releases/editor/whats-new/2022.2.14

/build-all
2020.3.47f1
Fri, 07 Apr 2023 06:12:01 +0000
https://unity.com/releases/editor/whats-new/2020.3.47

/build-all
2023.2.0a9
Fri, 07 Apr 2023 06:12:01 +0000
https://unity.com/releases/editor/alpha/2023.2.0a9

/build-all
2023.1.0b11
Fri, 07 Apr 2023 06:12:01 +0000
https://unity.com/releases/editor/beta/2023.1.0b11

/build-all
2022.2.15f1
2023-04-13T13:56:06
https://unity.com/releases/editor/whats-new/2022.2.15

/build-all
2023.2.0a10
2023-04-12T17:57:27
https://unity.com/releases/editor/alpha/2023.2.0a10

/build-all
2023.1.0b12
2023-04-12T16:58:27
https://unity.com/releases/editor/beta/2023.1.0b12

/build-all
2023.2.0a10
Fri, 14 Apr 2023 06:12:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a10

/build-all
2023.1.0b12
Fri, 14 Apr 2023 06:12:02 +0000
https://unity.com/releases/editor/beta/2023.1.0b12

/build-all
2021.3.23f1
Sat, 15 Apr 2023 06:12:02 +0000
https://unity.com/releases/editor/whats-new/2021.3.23

/build-all
2021.3.23f1
2023-04-14T03:05:53
https://unity.com/releases/editor/whats-new/2021.3.23

/build-all
2023.2.0a11
Thu, 20 Apr 2023 06:12:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a11

/build-all
2023.2.0a11
2023-04-19T23:11:25
https://unity.com/releases/editor/alpha/2023.2.0a11

/build-all
2022.2.16f1
2023-04-19T14:00:29
https://unity.com/releases/editor/whats-new/2022.2.16

/build-all
2023.1.0b13
2023-04-19T15:38:30
https://unity.com/releases/editor/beta/2023.1.0b13

/build-all
2022.2.16f1
Fri, 21 Apr 2023 06:12:01 +0000
https://unity.com/releases/editor/whats-new/2022.2.16

/build-all
2023.1.0b13
Fri, 21 Apr 2023 06:12:01 +0000
https://unity.com/releases/editor/beta/2023.1.0b13

/build-all
2023.1.0b14
2023-04-26T17:38:33
https://unity.com/releases/editor/beta/2023.1.0b14

/build-all
2023.2.0a12
2023-04-27T14:39:10
https://unity.com/releases/editor/alpha/2023.2.0a12

/build-all
2022.2.17f1
Fri, 28 Apr 2023 06:15:01 +0000
https://unity.com/releases/editor/whats-new/2022.2.17

/build-all
2021.3.24f1
Fri, 28 Apr 2023 06:15:01 +0000
https://unity.com/releases/editor/whats-new/2021.3.24

/build-all
2023.2.0a12
Fri, 28 Apr 2023 06:15:01 +0000
https://unity.com/releases/editor/alpha/2023.2.0a12

/build-all
2023.1.0b14
Fri, 28 Apr 2023 06:15:01 +0000
https://unity.com/releases/editor/beta/2023.1.0b14

/build-all
2021.3.24f1
2023-04-27T17:16:27
https://unity.com/releases/editor/whats-new/2021.3.24

/build-all
2023.2.0a13
2023-05-03T19:08:00
https://unity.com/releases/editor/alpha/2023.2.0a13

/build-all
2023.2.0a13
Fri, 05 May 2023 06:15:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a13

/build-all
2022.2.18f1
2023-05-04T14:54:59
https://unity.com/releases/editor/whats-new/2022.2.18

/build-all
2023.1.0b15
2023-05-04T15:09:21
https://unity.com/releases/editor/beta/2023.1.0b15

/build-all
2022.2.18f1
Sat, 06 May 2023 06:15:01 +0000
https://unity.com/releases/editor/whats-new/2022.2.18

/build-all
2023.1.0b15
Sat, 06 May 2023 06:15:01 +0000
https://unity.com/releases/editor/beta/2023.1.0b15

/build-all
2023.2.0a14
2023-05-10T19:50:11
https://unity.com/releases/editor/alpha/2023.2.0a14

/build-all
2023.2.0a14
Thu, 11 May 2023 06:15:01 +0000
https://unity.com/releases/editor/alpha/2023.2.0a14

/build-all
2021.3.25f1
Fri, 12 May 2023 06:18:02 +0000
https://unity.com/releases/editor/whats-new/2021.3.25

/build-all
2022.2.19f1
2023-05-11T12:02:51
https://unity.com/releases/editor/whats-new/2022.2.19

/build-all
2023.1.0b16
Fri, 12 May 2023 06:15:02 +0000
https://unity.com/releases/editor/beta/2023.1.0b16

/build-all
2023.1.0b16
2023-05-11T01:23:47
https://unity.com/releases/editor/beta/2023.1.0b16

/build-all
2022.2.19f1
Fri, 12 May 2023 06:18:02 +0000
https://unity.com/releases/editor/whats-new/2022.2.19

/build-all
2021.3.25f1
2023-05-11T13:55:39
https://unity.com/releases/editor/whats-new/2021.3.25

/build-all
2020.3.48f1
Thu, 18 May 2023 06:18:02 +0000
https://unity.com/releases/editor/whats-new/2020.3.48

/build-all
2023.2.0a15
2023-05-17T20:05:43
https://unity.com/releases/editor/alpha/2023.2.0a15

/build-all
2023.1.0b17
2023-05-17T16:32:57
https://unity.com/releases/editor/beta/2023.1.0b17

/build-all
2020.3.48f1
2023-05-17T17:23:52
https://unity.com/releases/editor/whats-new/2020.3.48

/build-all
2023.2.0a15
Thu, 18 May 2023 06:18:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a15

/build-all
2023.1.0b17
Thu, 18 May 2023 06:18:02 +0000
https://unity.com/releases/editor/beta/2023.1.0b17

/build-all
2022.2.20f1
2023-05-18T09:58:25
https://unity.com/releases/editor/whats-new/2022.2.20

/build-all
2022.2.20f1
Sat, 20 May 2023 06:18:02 +0000
https://unity.com/releases/editor/whats-new/2022.2.20

/build-all
2022.2.21f1
2023-05-24T11:15:23
https://unity.com/releases/editor/whats-new/2022.2.21

/build-all
2021.3.26f1
Fri, 26 May 2023 06:18:01 +0000
https://unity.com/releases/editor/whats-new/2021.3.26

/build-all
2023.2.0a16
2023-05-24T20:32:01
https://unity.com/releases/editor/alpha/2023.2.0a16

/build-all
2023.1.0b18
2023-05-24T14:12:55
https://unity.com/releases/editor/beta/2023.1.0b18

/build-all
2023.2.0a16
Fri, 26 May 2023 06:18:01 +0000
https://unity.com/releases/editor/alpha/2023.2.0a16

/build-all
2023.1.0b18
Fri, 26 May 2023 06:18:01 +0000
https://unity.com/releases/editor/beta/2023.1.0b18

/build-all
2022.3.0f1
Wed, 31 May 2023 14:41:05 +0000
https://unity.com/releases/editor/whats-new/2022.3.0

/build-all
2022.3.0f1
2023-05-30T10:40:13
https://unity.com/releases/editor/whats-new/2022.3.0

/build-all
2023.1.0b19
Thu, 01 Jun 2023 06:21:01 +0000
https://unity.com/releases/editor/beta/2023.1.0b19

/build-all
2023.1.0b19
2023-05-31T21:22:40
https://unity.com/releases/editor/beta/2023.1.0b19

/build-all
2023.2.0a17
2023-05-31T19:36:57
https://unity.com/releases/editor/alpha/2023.2.0a17

/build-all
2023.2.0a17
Fri, 02 Jun 2023 06:21:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a17

/build-all
2022.3.1f1
2023-06-07T11:44:18
https://unity.com/releases/editor/whats-new/2022.3.1

/build-all
2022.3.1f1
Thu, 08 Jun 2023 06:21:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.1

/build-all
2021.3.27f1
2023-06-07T16:35:21
https://unity.com/releases/editor/whats-new/2021.3.27

/build-all
2023.2.0a18
2023-06-07T15:05:43
https://unity.com/releases/editor/alpha/2023.2.0a18

/build-all
2023.1.0b20
2023-06-07T14:07:58
https://unity.com/releases/editor/beta/2023.1.0b20

/build-all
2023.2.0a18
Fri, 09 Jun 2023 06:21:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a18

/build-all
2023.1.0b20
Fri, 09 Jun 2023 06:21:02 +0000
https://unity.com/releases/editor/beta/2023.1.0b20

/build-all
2021.3.27f1
Fri, 09 Jun 2023 06:21:02 +0000
https://unity.com/releases/editor/whats-new/2021.3.27

/build-all
2022.3.2f1
2023-06-13T17:35:17
https://unity.com/releases/editor/whats-new/2022.3.2

/build-all
2023.1.0f1
2023-06-12T20:09:17
https://unity.com/releases/editor/whats-new/2023.1.0

/build-all
2022.3.2f1
Thu, 15 Jun 2023 06:21:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.2

/build-all
2023.2.0a19
2023-06-13T17:56:46
https://unity.com/releases/editor/alpha/2023.2.0a19

/build-all
2023.2.0a19
Fri, 16 Jun 2023 06:21:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a19

/build-all
2022.3.3f1
2023-06-21T15:21:19
https://unity.com/releases/editor/whats-new/2022.3.3

/build-all
2023.1.1f1
2023-06-21T14:44:26
https://unity.com/releases/editor/whats-new/2023.1.1

/build-all
2023.2.0a20
2023-06-21T19:58:23
https://unity.com/releases/editor/alpha/2023.2.0a20

/build-all
2022.3.3f1
Fri, 23 Jun 2023 06:24:02 +0000
https://unity.com/releases/editor/whats-new/2022.3.3

/build-all
2023.1.1f1
Fri, 23 Jun 2023 06:24:02 +0000
https://unity.com/releases/editor/whats-new/2023.1.1

/build-all
2023.2.0a20
Fri, 23 Jun 2023 06:24:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a20

/build-all
2023.1.2f1
2023-06-26T17:35:53
https://unity.com/releases/editor/whats-new/2023.1.2

/build-all
2022.3.4f1
2023-06-26T16:47:18
https://unity.com/releases/editor/whats-new/2022.3.4

/build-all
2023.1.2f1
Thu, 29 Jun 2023 06:24:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.2

/build-all
2022.3.4f1
Thu, 29 Jun 2023 06:24:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.4

/build-all
2023.1.3f1
2023-07-05T10:38:33
https://unity.com/releases/editor/whats-new/2023.1.3

/build-all
2021.3.28f1
Thu, 06 Jul 2023 06:24:01 +0000
https://unity.com/releases/editor/whats-new/2021.3.28

/build-all
2023.1.3f1
Thu, 06 Jul 2023 06:24:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.3

/build-all
2021.3.28f1
2023-07-04T19:41:02
https://unity.com/releases/editor/whats-new/2021.3.28

/build-all
2023.2.0a22
2023-07-10T10:49:24
https://unity.com/releases/editor/alpha/2023.2.0a22

/build-all
2023.2.0a22
Tue, 11 Jul 2023 06:24:02 +0000
https://unity.com/releases/editor/alpha/2023.2.0a22

/build-all
2023.1.4f1
2023-07-13T09:22:35
https://unity.com/releases/editor/whats-new/2023.1.4

/build-all
2023.1.4f1
Fri, 14 Jul 2023 06:24:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.4

/build-all
2022.3.5f1
Tue, 18 Jul 2023 06:03:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.5

/build-all
2022.3.5f1
2023-07-13T16:12:49
https://unity.com/releases/editor/whats-new/2022.3.5

/build-all
2023.1.5f1
2023-07-18T09:47:39
https://unity.com/releases/editor/whats-new/2023.1.5

/build-all
2023.1.5f1
Wed, 19 Jul 2023 06:27:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.5

/build-all
2023.2.0b1
Thu, 20 Jul 2023 14:39:12 +0000
https://unity.com/releases/editor/beta/2023.2.0b1

/build-all
2023.2.0b1
2023-07-19T17:48:18
https://unity.com/releases/editor/beta/2023.2.0b1

/build-all
2023.1.6f1
2023-07-25T14:07:19
https://unity.com/releases/editor/whats-new/2023.1.6

/build-all
2021.3.29f1
Thu, 27 Jul 2023 06:27:01 +0000
https://unity.com/releases/editor/whats-new/2021.3.29

/build-all
2021.3.29f1
2023-07-25T12:13:45
https://unity.com/releases/editor/whats-new/2021.3.29

/build-all
2023.2.0b2
2023-07-26T15:36:17
https://unity.com/releases/editor/beta/2023.2.0b2

/build-all
2023.2.0b2
Fri, 28 Jul 2023 06:27:02 +0000
https://unity.com/releases/editor/beta/2023.2.0b2

/build-all
2023.1.7f1
2023-08-01T11:52:30
https://unity.com/releases/editor/whats-new/2023.1.7

/build-all
2022.3.6f1
2023-07-31T18:44:28
https://unity.com/releases/editor/whats-new/2022.3.6

/build-all
2023.1.7f1
Thu, 03 Aug 2023 06:27:02 +0000
https://unity.com/releases/editor/whats-new/2023.1.7

/build-all
2022.3.6f1
Thu, 03 Aug 2023 06:27:02 +0000
https://unity.com/releases/editor/whats-new/2022.3.6

/build-all
2023.2.0b3
2023-08-01T21:20:07
https://unity.com/releases/editor/beta/2023.2.0b3

/build-all
2023.2.0b3
Fri, 04 Aug 2023 06:27:01 +0000
https://unity.com/releases/editor/beta/2023.2.0b3

/build-all
2023.1.8f1
2023-08-08T10:46:36
https://unity.com/releases/editor/whats-new/2023.1.8

/build-all
2022.3.7f1
Thu, 10 Aug 2023 06:27:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.7

/build-all
2023.1.8f1
Thu, 10 Aug 2023 06:27:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.8

/build-all
2022.3.7f1
2023-08-08T09:39:39
https://unity.com/releases/editor/whats-new/2022.3.7

/build-all
2023.2.0b4
Fri, 11 Aug 2023 06:30:02 +0000
https://unity.com/releases/editor/beta/2023.2.0b4

/build-all
2023.2.0b4
2023-08-10T16:28:52
https://unity.com/releases/editor/beta/2023.2.0b4

/build-all
2023.1.9f1
2023-08-15T08:51:07
https://unity.com/releases/editor/whats-new/2023.1.9

/build-all
2023.1.9f1
Thu, 17 Aug 2023 06:30:02 +0000
https://unity.com/releases/editor/whats-new/2023.1.9

/build-all
2023.2.0b5
2023-08-15T19:46:13
https://unity.com/releases/editor/beta/2023.2.0b5

/build-all
2023.2.0b5
Fri, 18 Aug 2023 06:30:01 +0000
https://unity.com/releases/editor/beta/2023.2.0b5

/build-all
2023.1.10f1
Fri, 25 Aug 2023 06:30:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.10

/build-all
2023.2.0b6
2023-08-23T16:37:08
https://unity.com/releases/editor/beta/2023.2.0b6

/build-all
2023.2.0b6
Fri, 25 Aug 2023 06:30:01 +0000
https://unity.com/releases/editor/beta/2023.2.0b6

/build-all
2023.1.10f1
2023-08-22T09:04:56
https://unity.com/releases/editor/whats-new/2023.1.10

/build-all
2022.3.8f1
Sat, 26 Aug 2023 06:30:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.8

/build-all
2022.3.8f1
2023-08-22T16:08:57
https://unity.com/releases/editor/whats-new/2022.3.8

/build-all
2023.1.11f1
Wed, 30 Aug 2023 06:30:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.11

/build-all
2021.3.30f1
2023-08-29T22:00:32
https://unity.com/releases/editor/whats-new/2021.3.30

/build-all
2023.2.0b7
2023-08-29T22:05:40
https://unity.com/releases/editor/beta/2023.2.0b7

/build-all
2023.1.11f1
2023-08-29T23:34:23
https://unity.com/releases/editor/whats-new/2023.1.11

/build-all
2021.3.30f1
Wed, 30 Aug 2023 06:30:01 +0000
https://unity.com/releases/editor/whats-new/2021.3.30

/build-all
2023.2.0b7
Wed, 30 Aug 2023 06:30:01 +0000
https://unity.com/releases/editor/beta/2023.2.0b7

/build-all
2023.3.0a3
2023-08-29T23:57:28
https://unity.com/releases/editor/alpha/2023.3.0a3

/build-all
2023.1.12f1
2023-09-05T13:19:07
https://unity.com/releases/editor/whats-new/2023.1.12

/build-all
2022.3.9f1
Fri, 08 Sep 2023 06:33:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.9

/build-all
2023.2.0b8
Fri, 08 Sep 2023 06:33:01 +0000
https://unity.com/releases/editor/beta/2023.2.0b8

/build-all
2023.3.0a4
Fri, 08 Sep 2023 06:33:01 +0000
https://unity.com/releases/editor/alpha/2023.3.0a4

/build-all
2023.1.12f1
Fri, 08 Sep 2023 06:33:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.12

/build-all
2023.2.0b8
2023-09-07T00:06:06
https://unity.com/releases/editor/beta/2023.2.0b8

/build-all
2023.3.0a4
2023-09-06T23:09:51
https://unity.com/releases/editor/alpha/2023.3.0a4

/build-all
2022.3.9f1
2023-09-05T11:20:42
https://unity.com/releases/editor/whats-new/2022.3.9

/build-all
2023.1.13f1
2023-09-12T16:45:26
https://unity.com/releases/editor/whats-new/2023.1.13

/build-all
2023.1.13f1
Thu, 14 Sep 2023 06:33:02 +0000
https://unity.com/releases/editor/whats-new/2023.1.13

/build-all
2023.3.0a5
Thu, 14 Sep 2023 06:33:02 +0000
https://unity.com/releases/editor/alpha/2023.3.0a5

/build-all
2023.2.0b9
2023-09-13T16:47:50
https://unity.com/releases/editor/beta/2023.2.0b9

/build-all
2023.2.0b9
Sat, 16 Sep 2023 06:33:02 +0000
https://unity.com/releases/editor/beta/2023.2.0b9

/build-all
2023.1.14f1
2023-09-19T13:45:02
https://unity.com/releases/editor/whats-new/2023.1.14

/build-all
2022.3.10f1
Thu, 21 Sep 2023 06:33:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.10

/build-all
2023.1.14f1
Thu, 21 Sep 2023 06:33:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.14

/build-all
2022.3.10f1
2023-09-19T11:09:17
https://unity.com/releases/editor/whats-new/2022.3.10

/build-all
2023.2.0b10
2023-09-21T00:25:39
https://unity.com/releases/editor/beta/2023.2.0b10

/build-all
2023.3.0a6
Fri, 22 Sep 2023 06:36:01 +0000
https://unity.com/releases/editor/alpha/2023.3.0a6

/build-all
2023.2.0b10
Fri, 22 Sep 2023 06:33:02 +0000
https://unity.com/releases/editor/beta/2023.2.0b10

/build-all
2023.3.0a6
2023-09-21T19:57:30
https://unity.com/releases/editor/alpha/2023.3.0a6

/build-all
2023.1.15f1
2023-09-26T13:26:57
https://unity.com/releases/editor/whats-new/2023.1.15

/build-all
2023.3.0a7
2023-09-20T23:32:03
https://unity.com/releases/editor/alpha/2023.3.0a7

/build-all
2023.3.0a7
Thu, 28 Sep 2023 06:33:02 +0000
https://unity.com/releases/editor/alpha/2023.3.0a7

/build-all
2023.1.15f1
Thu, 28 Sep 2023 06:36:02 +0000
https://unity.com/releases/editor/whats-new/2023.1.15

/build-all
2023.2.0b11
Tue, 03 Oct 2023 06:36:01 +0000
https://unity.com/releases/editor/beta/2023.2.0b11

/build-all
2023.2.0b11
2023-09-27T19:03:28
https://unity.com/releases/editor/beta/2023.2.0b11

/build-all
2023.1.16f1
2023-10-03T17:51:07
https://unity.com/releases/editor/whats-new/2023.1.16

/build-all
2021.3.31f1
Thu, 05 Oct 2023 06:36:02 +0000
https://unity.com/releases/editor/whats-new/2021.3.31

/build-all
2021.3.31f1
2023-10-03T15:50:59
https://unity.com/releases/editor/whats-new/2021.3.31

/build-all
2023.2.0b12
2023-10-05T05:35:01
https://unity.com/releases/editor/beta/2023.2.0b12

/build-all
2023.3.0a8
2023-10-05T04:37:32
https://unity.com/releases/editor/alpha/2023.3.0a8

/build-all
2023.2.0b12
Fri, 06 Oct 2023 06:36:02 +0000
https://unity.com/releases/editor/beta/2023.2.0b12

/build-all
2023.3.0a8
Fri, 06 Oct 2023 06:36:02 +0000
https://unity.com/releases/editor/alpha/2023.3.0a8

/build-all
2022.3.11f1
2023-10-10T15:27:45
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2022.3.11f1
Thu, 12 Oct 2023 06:36:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2023.2.0b13
2023-10-10T23:43:50
https://unity.com/releases/editor/beta/2023.2.0b13

/build-all
2023.2.0b13
Fri, 13 Oct 2023 06:36:01 +0000
https://unity.com/releases/editor/beta/2023.2.0b13

/build-all
2022.3.11f1
Fri, 13 Oct 2023 15:17:21 +0000
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2022.3.11f1
Tue, 17 Oct 2023 21:03:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2022.3.11f1
Thu, 19 Oct 2023 15:58:06 +0000
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2023.1.17f1
Thu, 19 Oct 2023 15:58:06 +0000
https://unity.com/releases/editor/whats-new/2023.1.17

/build-all
2023.3.0a10
2023-10-16T15:53:09
https://unity.com/releases/editor/alpha/2023.3.0a10

/build-all
2022.3.11f1
Thu, 19 Oct 2023 16:54:04 +0000
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2023.2.0b14
Thu, 19 Oct 2023 15:58:06 +0000
https://unity.com/releases/editor/beta/2023.2.0b14

/build-all
2023.3.0a10
Thu, 19 Oct 2023 15:58:06 +0000
https://unity.com/releases/editor/alpha/2023.3.0a10

/build-all
2022.3.11f1
Thu, 19 Oct 2023 17:22:05 +0000
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2022.3.11f1
Thu, 19 Oct 2023 17:42:03 +0000
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2023.1.17f1
2023-10-17T13:06:27
https://unity.com/releases/editor/whats-new/2023.1.17

/build-all
2023.1.18f1
Thu, 26 Oct 2023 06:39:01 +0000
https://unity.com/releases/editor/whats-new/2023.1.18

/build-all
2023.1.18f1
2023-10-24T16:38:46
https://unity.com/releases/editor/whats-new/2023.1.18

/build-all
2022.3.12f1
2023-10-26T14:00:14
https://unity.com/releases/editor/whats-new/2022.3.12

/build-all
2022.3.12f1
Fri, 27 Oct 2023 06:39:01 +0000
https://unity.com/releases/editor/whats-new/2022.3.12

/build-all
2023.3.0a11
Fri, 27 Oct 2023 06:39:01 +0000
https://unity.com/releases/editor/alpha/2023.3.0a11

/build-all
2023.2.0b15
Fri, 27 Oct 2023 06:39:01 +0000
https://unity.com/releases/editor/beta/2023.2.0b15

/build-all
2023.2.0b15
2023-10-26T19:42:17
https://unity.com/releases/editor/beta/2023.2.0b15

/build-all
2023.1.19f1
2023-10-31T14:12:27
https://unity.com/releases/editor/whats-new/2023.1.19

/build-all
2023.3.0a12
2023-10-31T20:54:47
https://unity.com/releases/editor/alpha/2023.3.0a12

/build-all
2023.1.19f1
Thu, 02 Nov 2023 06:39:02 +0000
https://unity.com/releases/editor/whats-new/2023.1.19

/build-all
2023.3.0a12
Thu, 02 Nov 2023 06:39:02 +0000
https://unity.com/releases/editor/alpha/2023.3.0a12

/build-all
2021.3.32f1
Fri, 03 Nov 2023 06:42:02 +0000
https://unity.com/releases/editor/whats-new/2021.3.32

/build-all
2023.2.0b16
Fri, 03 Nov 2023 06:39:02 +0000
https://unity.com/releases/editor/beta/2023.2.0b16

/build-all
2021.3.32f1
2023-11-01T15:47:25
https://unity.com/releases/editor/whats-new/2021.3.32

/build-all
2023.2.0b16
2023-11-01T07:07:29
https://unity.com/releases/editor/beta/2023.2.0b16

/build-all
2022.3.13f1
Wed, 08 Nov 2023 16:41:31 +0000
https://unity.com/releases/editor/whats-new/2022.3.13

/build-all
2021.3.32f1
Wed, 08 Nov 2023 16:41:31 +0000
https://unity.com/releases/editor/whats-new/2021.3.32

/build-all
2022.3.13f1
2023-11-07T17:33:11
https://unity.com/releases/editor/whats-new/2022.3.13

/build-all
2023.1.20f1
2023-11-09T11:37:53
https://unity.com/releases/editor/whats-new/2023.1.20

/build-all
2023.3.0a13
Fri, 10 Nov 2023 06:42:02 +0000
https://unity.com/releases/editor/alpha/2023.3.0a13

/build-all
2023.2.0b17
Fri, 10 Nov 2023 06:42:02 +0000
https://unity.com/releases/editor/beta/2023.2.0b17

/build-all
2023.3.0a13
2023-11-07T13:03:31
https://unity.com/releases/editor/alpha/2023.3.0a13

/build-all
2023.2.0b17
2023-11-07T01:15:49
https://unity.com/releases/editor/beta/2023.2.0b17

/build-all
2023.1.20f1
Fri, 10 Nov 2023 06:42:02 +0000
https://unity.com/releases/editor/whats-new/2023.1.20

/build-all
2022.3.11f1
Wed, 15 Nov 2023 17:31:49 +0000
https://unity.com/releases/editor/whats-new/2022.3.11

/build-all
2023.3.0a14
2023-11-14T21:47:34
https://unity.com/releases/editor/alpha/2023.3.0a14

/build-all
2023.3.0a14
Thu, 16 Nov 2023 06:42:02 +0000
https://unity.com/releases/editor/alpha/2023.3.0a14

/build-all
2023.2.0f1
2023-11-14T23:22:44
https://unity.com/releases/editor/whats-new/2023.2.0

/build-all
2023.2.0f1
Thu, 16 Nov 2023 13:48:04 +0000
https://unity.com/releases/editor/whats-new/2023.2.0

/build-all
2022.3.14f1
2023-11-21T20:07:15
https://unity.com/releases/editor/whats-new/2022.3.14

/build-all
2022.3.14f1
Thu, 23 Nov 2023 06:42:02 +0000
https://unity.com/releases/editor/whats-new/2022.3.14

/build-all
2023.2.1f1
2023-11-21T22:09:38
https://unity.com/releases/editor/whats-new/2023.2.1

/build-all
2023.3.0a15
2023-11-21T17:46:47
https://unity.com/releases/editor/alpha/2023.3.0a15

/build-all
2023.2.1f1
Fri, 24 Nov 2023 06:42:02 +0000
https://unity.com/releases/editor/whats-new/2023.2.1

/build-all
2021.3.33f1
Thu, 30 Nov 2023 06:45:02 +0000
https://unity.com/releases/editor/whats-new/2021.3.33

/build-all
2021.3.33f1
2023-11-28T15:21:35
https://unity.com/releases/editor/whats-new/2021.3.33

/build-all
2023.2.2f1
2023-11-28T20:28:30
https://unity.com/releases/editor/whats-new/2023.2.2

/build-all
2023.3.0a16
2023-11-28T18:53:03
https://unity.com/releases/editor/alpha/2023.3.0a16

/build-all
2023.3.0a16
Sat, 02 Dec 2023 06:45:02 +0000
https://unity.com/releases/editor/alpha/2023.3.0a16

/build-all
2022.3.14f1
Mon, 04 Dec 2023 18:06:53 +0000
https://unity.com/releases/editor/whats-new/2022.3.14

/build-all
2022.3.15f1
Thu, 07 Dec 2023 06:45:02 +0000
https://unity.com/releases/editor/whats-new/2022.3.15

/build-all
2022.3.15f1
2023-12-05T16:41:51
https://unity.com/releases/editor/whats-new/2022.3.15

/build-all
2023.2.3f1
Sat, 09 Dec 2023 06:45:01 +0000
https://unity.com/releases/editor/whats-new/2023.2.3

/build-all
2023.3.0a17
2023-12-05T20:29:50
https://unity.com/releases/editor/alpha/2023.3.0a17

/build-all
2023.2.3f1
2023-12-05T22:03:42
https://unity.com/releases/editor/whats-new/2023.2.3

/build-all
2023.3.0a17
Sat, 09 Dec 2023 06:45:01 +0000
https://unity.com/releases/editor/alpha/2023.3.0a17

/build-all
2023.3.0a18
2023-12-13T21:40:57
https://unity.com/releases/editor/alpha/2023.3.0a18

/build-all
2023.3.0a18
Thu, 14 Dec 2023 06:45:02 +0000
https://unity.com/releases/editor/alpha/2023.3.0a18

repo: mob-sakai/docker


text:
Output machine readable json on maestro test

As of now, the maestro test command will output human-readable values that show what's failing and what's not in a very clean and visual way, which is good for local testing. However, this output style isn't useful for CI, as it requires a machine-readable output, like a json, to register metrics, trigger alerts, etc.
I propose to add a --m and -machine parameter to maestro test that outputs a json at the end of the test run, of which can be used for whatever the developer desires.

What an absolute chad.
I prefer the output generated by Flutter with the machine parameter, like flutter test --machine.
Here's a sneak peek at what it outputs. Note that it outputs a minified json, I've formatted for readability, but note that it uploads one json per instruction/test, so it's not a valid JSON format:

Code sample
Code
{
 "protocolVersion": "0.1.1",
 "runnerVersion": "1.21.4",
 "pid": 52538,
 "type": "start",
 "time": 0
}
// ----------
{
 "suite": {
     "id": 0,
     "platform": "vm",
     "path": "[app_location]/test/test_2_test.dart"
 },
 "type": "suite",
 "time": 0
}
// ----------
{
 "test": {
     "id": 1,
     "name": "loading [app_location]/test/test_2_test.dart",
     "suiteID": 0,
     "groupIDs": [],
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "line": null,
     "column": null,
     "url": null
 },
 "type": "testStart",
 "time": 0
}
// ----------
{
 "suite": {
     "id": 2,
     "platform": "vm",
     "path": "[app_location]/test/test_1_test.dart"
 },
 "type": "suite",
 "time": 3
}
// ----------
{
 "test": {
     "id": 3,
     "name": "loading [app_location]/test/test_1_test.dart",
     "suiteID": 2,
     "groupIDs": [],
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "line": null,
     "column": null,
     "url": null
 },
 "type": "testStart",
 "time": 3
}
// ----------
{
 "count": 2,
 "time": 3,
 "type": "allSuites"
}[
 {
     "event": "test.startedProcess",
     "params": {
       "observatoryUri": null
     }
 }
][
 {
     "event": "test.startedProcess",
     "params": {
       "observatoryUri": null
     }
 }
]{
 "testID": 1,
 "result": "success",
 "skipped": false,
 "hidden": true,
 "type": "testDone",
 "time": 1869
}
// ----------
{
 "group": {
     "id": 4,
     "suiteID": 0,
     "parentID": null,
     "name": "",
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "testCount": 4,
     "line": null,
     "column": null,
     "url": null
 },
 "type": "group",
 "time": 1871
}
// ----------
{
 "test": {
     "id": 5,
     "name": "test A",
     "suiteID": 0,
     "groupIDs": [
       4
     ],
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "line": 4,
     "column": 3,
     "url": "file://[app_location]/test/test_2_test.dart"
 },
 "type": "testStart",
 "time": 1871
}
// ----------
{
 "testID": 3,
 "result": "success",
 "skipped": false,
 "hidden": true,
 "type": "testDone",
 "time": 1907
}
// ----------
{
 "group": {
     "id": 6,
     "suiteID": 2,
     "parentID": null,
     "name": "",
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "testCount": 1,
     "line": null,
     "column": null,
     "url": null
 },
 "type": "group",
 "time": 1908
}
// ----------
{
 "test": {
     "id": 7,
     "name": "test name",
     "suiteID": 2,
     "groupIDs": [
       6
     ],
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "line": 4,
     "column": 3,
     "url": "file://[app_location]/test/test_1_test.dart"
 },
 "type": "testStart",
 "time": 1908
}
// ----------
{
 "testID": 5,
 "error": "Expected: <false>\n  Actual: <true>\n",
 "stackTrace": "package:test_api                                    expect\npackage:flutter_test/src/widget_tester.dart 460:16  expect\ntest/test_2_test.dart 5:5                           main.<fn>\n",
 "isFailure": true,
 "type": "error",
 "time": 1938
}
// ----------
{
 "testID": 5,
 "result": "failure",
 "skipped": false,
 "hidden": false,
 "type": "testDone",
 "time": 1943
}
// ----------
{
 "test": {
     "id": 8,
     "name": "test B",
     "suiteID": 0,
     "groupIDs": [
       4
     ],
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "line": 7,
     "column": 3,
     "url": "file://[app_location]/test/test_2_test.dart"
 },
 "type": "testStart",
 "time": 1943
}
// ----------
{
 "testID": 7,
 "result": "success",
 "skipped": false,
 "hidden": false,
 "type": "testDone",
 "time": 1954
}
// ----------
{
 "testID": 8,
 "error": "Expected: <false>\n  Actual: <true>\n",
 "stackTrace": "package:test_api                                    expect\npackage:flutter_test/src/widget_tester.dart 460:16  expect\ntest/test_2_test.dart 8:5                           main.<fn>\n",
 "isFailure": true,
 "type": "error",
 "time": 1958
}
// ----------
{
 "testID": 8,
 "result": "failure",
 "skipped": false,
 "hidden": false,
 "type": "testDone",
 "time": 1958
}
// ----------
{
 "test": {
     "id": 9,
     "name": "test C",
     "suiteID": 0,
     "groupIDs": [
       4
     ],
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "line": 10,
     "column": 3,
     "url": "file://[app_location]/test/test_2_test.dart"
 },
 "type": "testStart",
 "time": 1958
}
// ----------
{
 "testID": 9,
 "error": "Expected: <false>\n  Actual: <true>\n",
 "stackTrace": "package:test_api                                    expect\npackage:flutter_test/src/widget_tester.dart 460:16  expect\ntest/test_2_test.dart 11:5                          main.<fn>\n",
 "isFailure": true,
 "type": "error",
 "time": 1969
}
// ----------
{
 "testID": 9,
 "result": "failure",
 "skipped": false,
 "hidden": false,
 "type": "testDone",
 "time": 1969
}
// ----------
{
 "test": {
     "id": 10,
     "name": "test D",
     "suiteID": 0,
     "groupIDs": [
       4
     ],
     "metadata": {
       "skip": false,
       "skipReason": null
     },
     "line": 13,
     "column": 3,
     "url": "file://[app_location]/test/test_2_test.dart"
 },
 "type": "testStart",
 "time": 1969
}
// ----------
{
 "testID": 10,
 "error": "Expected: <false>\n  Actual: <true>\n",
 "stackTrace": "package:test_api                                    expect\npackage:flutter_test/src/widget_tester.dart 460:16  expect\ntest/test_2_test.dart 14:5                          main.<fn>\n",
 "isFailure": true,
 "type": "error",
 "time": 1977
}
// ----------
{
 "testID": 10,
 "result": "failure",
 "skipped": false,
 "hidden": false,
 "type": "testDone",
 "time": 1977
}
// ----------
{
 "success": false,
 "type": "done",
 "time": 1989
}

Adding 2 cents to the flutter test command above, the output is compatible with a .log file, so here's a command to save the output to a file, so you can check it out: flutter test --machine > machine.log.
Here's what's inside the machine.log file:

Code sample
machine.log
{"protocolVersion":"0.1.1","runnerVersion":"1.21.4","pid":59582,"type":"start","time":0}
{"suite":{"id":0,"platform":"vm","path":"/Users/edgar/Repos/thinkific/mobile_app/test/test_2_test.dart"},"type":"suite","time":0}
{"test":{"id":1,"name":"loading /Users/edgar/Repos/thinkific/mobile_app/test/test_2_test.dart","suiteID":0,"groupIDs":[],"metadata":{"skip":false,"skipReason":null},"line":null,"column":null,"url":null},"type":"testStart","time":0}
{"suite":{"id":2,"platform":"vm","path":"/Users/edgar/Repos/thinkific/mobile_app/test/test_1_test.dart"},"type":"suite","time":3}
{"test":{"id":3,"name":"loading /Users/edgar/Repos/thinkific/mobile_app/test/test_1_test.dart","suiteID":2,"groupIDs":[],"metadata":{"skip":false,"skipReason":null},"line":null,"column":null,"url":null},"type":"testStart","time":3}
{"count":2,"time":3,"type":"allSuites"}

[{"event":"test.startedProcess","params":{"observatoryUri":null}}]

[{"event":"test.startedProcess","params":{"observatoryUri":null}}]
{"testID":1,"result":"success","skipped":false,"hidden":true,"type":"testDone","time":1969}
{"group":{"id":4,"suiteID":0,"parentID":null,"name":"","metadata":{"skip":false,"skipReason":null},"testCount":4,"line":null,"column":null,"url":null},"type":"group","time":1970}
{"test":{"id":5,"name":"test A","suiteID":0,"groupIDs":[4],"metadata":{"skip":false,"skipReason":null},"line":4,"column":3,"url":"file:///Users/edgar/Repos/thinkific/mobile_app/test/test_2_test.dart"},"type":"testStart","time":1971}
{"testID":3,"result":"success","skipped":false,"hidden":true,"type":"testDone","time":2055}
{"group":{"id":6,"suiteID":2,"parentID":null,"name":"","metadata":{"skip":false,"skipReason":null},"testCount":4,"line":null,"column":null,"url":null},"type":"group","time":2055}
{"test":{"id":7,"name":"test A","suiteID":2,"groupIDs":[6],"metadata":{"skip":false,"skipReason":null},"line":4,"column":3,"url":"file:///Users/edgar/Repos/thinkific/mobile_app/test/test_1_test.dart"},"type":"testStart","time":2055}
{"testID":5,"error":"Expected: <false>\n  Actual: <true>\n","stackTrace":"package:test_api                                    expect\npackage:flutter_test/src/widget_tester.dart 460:16  expect\ntest/test_2_test.dart 5:5                           main.<fn>\n","isFailure":true,"type":"error","time":2065}
{"testID":5,"result":"failure","skipped":false,"hidden":false,"type":"testDone","time":2069}
{"test":{"id":8,"name":"test B","suiteID":0,"groupIDs":[4],"metadata":{"skip":false,"skipReason":null},"line":7,"column":3,"url":"file:///Users/edgar/Repos/thinkific/mobile_app/test/test_2_test.dart"},"type":"testStart","time":2069}
{"testID":8,"error":"Expected: <false>\n  Actual: <true>\n","stackTrace":"package:test_api                                    expect\npackage:flutter_test/src/widget_tester.dart 460:16  expect\ntest/test_2_test.dart 8:5                           main.<fn>\n","isFailure":true,"type":"error","time":2082}
{"testID":8,"result":"failure","skipped":false,"hidden":false,"type":"testDone","time":2083}
{"test":{"id":9,"name":"test C","suiteID":0,"groupIDs":[4],"metadata":{"skip":false,"skipReason":null},"line":10,"column":3,"url":"file:///Users/edgar/Repos/thinkific/mobile_app/test/test_2_test.dart"},"type":"testStart","time":2083}
{"testID":9,"error":"Expected: <false>\n  Actual: <true>\n","stackTrace":"package:test_api                                    expect\npackage:flutter_test/src/widget_tester.dart 460:16  expect\ntest/test_2_test.dart 11:5                          main.<fn>\n","isFailure":true,"type":"error","time":2090}
{"testID":9,"result":"failure","skipped":false,"hidden":false,"type":"testDone","time":2090}
{"test":{"id":10,"name":"test D","suiteID":0,"groupIDs":[4],"metadata":{"skip":false,"skipReason":null},"line":13,"column":3,"url":"file:///Users/edgar/Repos/thinkific/mobile_app/test/test_2_test.dart"},"type":"testStart","time":2091}
{"testID":10,"error":"Expected: <false>\n  Actual: <true>\n","stackTrace":"package:test_api                                    expect\npackage:flutter_test/src/widget_tester.dart 460:16  expect\ntest/test_2_test.dart 14:5                          main.<fn>\n","isFailure":true,"type":"error","time":2097}
{"testID":10,"result":"failure","skipped":false,"hidden":false,"type":"testDone","time":2098}
{"testID":7,"result":"success","skipped":false,"hidden":false,"type":"testDone","time":2114}
{"test":{"id":11,"name":"test B","suiteID":2,"groupIDs":[6],"metadata":{"skip":false,"skipReason":null},"line":7,"column":3,"url":"file:///Users/edgar/Repos/thinkific/mobile_app/test/test_1_test.dart"},"type":"testStart","time":2114}
{"testID":11,"result":"success","skipped":false,"hidden":false,"type":"testDone","time":2120}
{"test":{"id":12,"name":"test C","suiteID":2,"groupIDs":[6],"metadata":{"skip":false,"skipReason":null},"line":10,"column":3,"url":"file:///Users/edgar/Repos/thinkific/mobile_app/test/test_1_test.dart"},"type":"testStart","time":2120}
{"testID":12,"result":"success","skipped":false,"hidden":false,"type":"testDone","time":2123}
{"test":{"id":13,"name":"test D","suiteID":2,"groupIDs":[6],"metadata":{"skip":false,"skipReason":null},"line":13,"column":3,"url":"file:///Users/edgar/Repos/thinkific/mobile_app/test/test_1_test.dart"},"type":"testStart","time":2123}
{"testID":13,"result":"success","skipped":false,"hidden":false,"type":"testDone","time":2125}
{"success":false,"type":"done","time":2136}

@dmitry-zaitsev can I help you with something in this issue? I can review the PR or maybe assist with some coding, if needed.

Hey @edgarlealbd we just recently added support for outputting junit-formatted xml output in this PR: https://github.com/mobile-dev-inc/maestro/pull/405
If you'd like to take a stab, you can check out the code changes above and add another --format option for flutter machine output

authors: Leland-Takamine edgarlealbd

repo: mobile-dev-inc/maestro


text:
Feat/introduce toml usage

Proposed Changes
After checking the build setup I identified some differences in versions of used dependencies.
Example:
File, Module, Plugin
build.gradle (maestro-android) -> "com.google.protobuf" version "0.8.18"
build.gradle (maestro-client) -> "com.google.protobuf" version "0.9.1"

To fix this issue I want to introduce version catalog (libs.versions.toml) so every dependencies + version is in one place. It is now easier to update & maintain all deps used in this repository.
Testing
Tested it by running ./gradlew test , installDist, using cli & maestro studio locally.
Issues Fixed
see above

TOML usage is a neat and welcome change! However, can we stick with Java 8 (or at least address it in a different PR)?

Java 11 branch in fork created. update-java-11-agp-7.4.1 depends on toml change so waiting until this is merged.

Thanks @nilsjr ! Everything works 👍

authors: dmitry-zaitsev nilsjr


text:
🛑 PizzaRiing Web is down

In be93310, PizzaRiing Web (https://pizzariing.uy) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PizzaRiing Web is back up in 2f10a49 after 16 minutes.

repo: mobilitysol/monitorweb


text:
🛑 RequetePizza Web is down

In 25cbceb, RequetePizza Web (https://requetepizza.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RequetePizza Web is back up in 455c1c6 after 15 minutes.


text:
🛑 Mobility Solutions Web is down

In 90e81ef, Mobility Solutions Web (https://mobilitysol.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mobility Solutions Web is back up in 4874245 after 9 minutes.


text:
🛑 Zulip Uruguay is down

In ff7ac94, Zulip Uruguay (https://zulip.mobilitysol.com:2443/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zulip Uruguay is back up in c05d5ca after 16 minutes.


text:
Example Code on Array Docs Gives a Warning

Link: https://mobily.github.io/ts-belt/api/array
node: v18.2.0
typescript: 4.7.3
tsserver: 0.11.1
tsconfig.json: i follow this https://mobily.github.io/ts-belt/docs/getting-started/config
I just tried the code from the array doc and it gives a warning like this:

the code runs fine, but the warning annoys me. So i removed the warning by handling the Option using match:
import { A, O, pipe } from "@mobily/ts-belt";

const arr = A.makeWithIndex(5, (i) => i); // if i changed this to [] without O.match, it will throws error
console.log(
  pipe(
    arr,
    A.tail,
    O.match( // initially i wanna use O.getWithDefault([]), but it also gives warning. O.getExn works but throws error if arr = [] :(
      (tail: readonly number[]) => tail,
      () => []
    ),
    A.take(2),
    A.map((val) => val * 2)
  )
);

question: is it some secret pipe behavior that handles Option or A.take type is not complete or the doc needs an update?
thank you

i just removed the Option handling and change A.tail to A.tailOrEmpty and the code runs fine and no warning. So, i propose that the docs should use A.tailOrEmpty because it returns Array<A> instead of Option<Array<A>>

@ahmaddynugroho thanks, good catch! 👀 (fixed)

authors: ahmaddynugroho mobily

repo: mobily/ts-belt


text:
2-bit quantization representation

In the blog, it says the quantized weight matrix should contain [-1,0,1,2], which can be decomposed to the sum of a binary and ternary matrix. But in the code, I think there is no such a treatment but represent the quantized 2-bit model with [0,1,2,3]. I'm not sure whether I didn't see the treatment. Thanks!

Yes, because at that time, there was no CUDA kernel doing that + in CUDA it doesn't make sense to do something like that, that would be more suitable for custom hardware, like FPGA. That's the same thing mentioned in the original 1.58bit paper: https://arxiv.org/abs/2402.17764 , the idea is that multiplications are expensive and you can turn binary/ternary matmul to only adding with some bitwise ops. But that is only applicable for custom hardware, in GPUs, mutliplications are fast and you are limited by the bandwidth instead. I have a GPU kernel doing this for ternary but it runs slower than multiplications because of the issue I have mentioned. Check out this work that did the implementation in FPGA: https://arxiv.org/pdf/2406.02528

Thank you so much! Really appreciate it!

BTW, do you think that [-2,-1,0,1] is better than [-1,0,1,2] shown in blog? Cause the former one can just be represented as int2 with sign bit. It can also be decomposed to binary + ternary.

By the way, I added support for 2-bit inference via BitBlas

authors: kaizizzzzzz mobicham

repo: mobiusml/hqq


text:
Fix URLs instances

Change static URL instances on rdfa document to mobivoc representation

You mean static http://schema.org/… URLs? (If so, please make the description above a bit more specific. And, of course, close the issue when it's done.)

authors: clange lavdim

repo: mobivoc/vocol


text:
Add Batches Details in Indicator Group Page

Add details about batches execution in the indicator group detailed page (similar to session info in the indicator page)

Done

repo: mobydq/mobydq


text:
Correctly identify and clean taken-over sessions

An issue was highlighted in which the subscriptions for a client which has undertaken a session takeover could be cleared erroneously in #173.
This behaviour was caused by the orphaned client unsubscribing from the client's topics after the new client had already inherited the subscriptions and begun reading.
Additionally, I identified a secondary, more significant issue in which an expiring orphaned client would delete the existing client from the server client map.
This PR attempts to resolve this issue through three mechanisms:

By adding a new isTakenOver atomic bit switch to the client which is set to 1 when the client session is inherited by a new client and the client is orphaned (the pointer to the client has been, or shortly will be overwritten in the server client map).
The s.unsubscribeClient logic has been adjusted to operate in two steps: first, the client subscriptions are moved from the client itself. Then, unsubscribe from the server topics index is only performed if the client has not been taken over.
When an actively connected client connection expires, it may only be deleted from the server clients map if the client has not been taken over (i.e. it is the active, operating client).

Pull Request Test Coverage Report for Build 4267624673

31 of 31 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 98.594%

Totals

Change from base Build 4247937237:
0.005%

Covered Lines:
5120

Relevant Lines:
5193

💛  - Coveralls

authors: coveralls mochi-co

repo: mochi-co/mqtt


text:
导出模型报错： forward() missing 1 required positional argument: 'x_mask'

python -m funasr.export.export_model --model-name /mnt/workspace/damo/speech_paraformer-large_asr_nat-zh-cn-16k-common-vocab8404-pytorch --export-dir ./export --type torch --quantize false
使用官方提供的docker环境
根据文档中的指令，导出本地模型报错，请问如何解决？
Traceback (most recent call last):
File "/opt/conda/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/opt/conda/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/opt/conda/lib/python3.7/site-packages/funasr/export/export_model.py", line 285, in
export_model.export(args.model_name)
File "/opt/conda/lib/python3.7/site-packages/funasr/export/export_model.py", line 221, in export
self._export(model, tag_name)
File "/opt/conda/lib/python3.7/site-packages/funasr/export/export_model.py", line 67, in _export
self._export_onnx(model, verbose, export_dir)
File "/opt/conda/lib/python3.7/site-packages/funasr/export/export_model.py", line 242, in _export_onnx
dynamic_axes=model.get_dynamic_axes()
File "/opt/conda/lib/python3.7/site-packages/torch/onnx/init.py", line 309, in export
export_modules_as_functions)
File "/opt/conda/lib/python3.7/site-packages/torch/onnx/utils.py", line 122, in export
custom_opsets=custom_opsets, export_modules_as_functions=export_modules_as_functions)
File "/opt/conda/lib/python3.7/site-packages/torch/onnx/utils.py", line 724, in _export
dynamic_axes=dynamic_axes)
File "/opt/conda/lib/python3.7/site-packages/torch/onnx/utils.py", line 499, in _model_to_graph
graph, params, torch_out, module = _create_jit_graph(model, args)
File "/opt/conda/lib/python3.7/site-packages/torch/onnx/utils.py", line 440, in _create_jit_graph
graph, torch_out = _trace_and_get_graph_from_model(model, args)
File "/opt/conda/lib/python3.7/site-packages/torch/onnx/utils.py", line 391, in _trace_and_get_graph_from_model
torch.jit._get_trace_graph(model, args, strict=False, _force_outplace=False, _return_inputs_states=True)
File "/opt/conda/lib/python3.7/site-packages/torch/jit/_trace.py", line 1166, in _get_trace_graph
outs = ONNXTracedModule(f, strict, _force_outplace, return_inputs, _return_inputs_states)(*args, **kwargs)
File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/opt/conda/lib/python3.7/site-packages/torch/jit/_trace.py", line 132, in forward
self._force_outplace,
File "/opt/conda/lib/python3.7/site-packages/torch/jit/_trace.py", line 118, in wrapper
outs.append(self.inner(*trace_inputs))
File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1098, in _slow_forward
result = self.forward(*input, **kwargs)
File "/opt/conda/lib/python3.7/site-packages/funasr/export/models/e2e_asr_paraformer.py", line 67, in forward
enc, enc_len = self.encoder(**batch)
File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1098, in _slow_forward
result = self.forward(*input, **kwargs)
File "/opt/conda/lib/python3.7/site-packages/funasr/export/models/encoder/conformer_encoder.py", line 69, in forward
xs_pad = self.embed(speech)
File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/opt/conda/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1098, in _slow_forward
result = self.forward(*input, **kwargs)
TypeError: forward() missing 1 required positional argument: 'x_mask'

我使用的是这个模型： damo/speech_paraformer_asr_nat-aishell1-pytorch

@langgz  please help to look at this problem

authors: wenmengzhou youngallien

repo: modelscope/modelscope


text:
🛑 Tautulli is down

In 9626316, Tautulli (https://tautulli.modem7.com/tautulli) was down:

HTTP code: 403
Response time: 104 ms

Resolved: Tautulli is back up in 75b428e.


text:
🛑 Wiki is down

In a7b5e73, Wiki (https://omegawiki.modem7.com) was down:

HTTP code: 523
Response time: 3345 ms

Resolved: Wiki is back up in a2977f3.


text:
Incorrect dtype when DataFrame is distributed

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

Windows 10

Modin version (modin.__version__):

0.7.2+85.gb9b791f.dirty

Python version:

Python 3.7.7

Code we can use to reproduce:

if __name__ == "__main__":
    import numpy as np
    import modin.pandas as pd

    s1 = pd.DataFrame(np.arange(1, 10000, dtype=np.float32), columns=["s1"])
    print(s1.dtypes['s1'])

Describe the problem

On Modin resulting dtype is float64 while on Pandas it is float32.
Source code / logs

Interesting, it appears that it does not happen when data is loaded with dtype kwarg.

There is a bug in DataFrame constructor:
https://github.com/modin-project/modin/blob/4c772ab5a97276709ae9e035ead5198caaa7f2bf/modin/pandas/dataframe.py#L113-L116
That list comprehension expression will return a python list with no dtype, with elements of data.
Let's say our data is np.ndarray with dtype=float32, after above expression, we will get a list of array elements, and then, when we would like to create pandas.DataFrame:
https://github.com/modin-project/modin/blob/4c772ab5a97276709ae9e035ead5198caaa7f2bf/modin/pandas/dataframe.py#L124-L127
Pandas will automatically detect the dtype as float64, because it has no information about original data type.

authors: dchigarev devin-petersohn gshimansky

repo: modin-project/modin


text:
FIX-#3151: Fix default size of Ray obj store memory

Signed-off-by: Alexey Prutskov alexey.prutskov@intel.com

What do these changes do?

[x] commit message follows format outlined here
[x] passes flake8 modin
[x] passes black --check modin
[x] signed commit with git commit -s
[x] Resolves #3151
[ ] tests added and passing
[ ] module layout described at docs/developer/architecture.rst is up-to-date

Restarting CI, please ping me when it's passing.

@devin-petersohn, notify, that all checks have passed

@devin-petersohn, just a friendly reminder

authors: devin-petersohn prutskov


text:
Specification of mf-manifest.json

Clear and concise description of the problem
For a build tool plugin which is implementing module federation (for e.g. rollup-plugin-module-federation), if it wants to generate the manifest file, what's the specification it should adhere to ?
The lack of specification for manifest protocol
Suggested solution
A specification for mf-manifest.json should be published so that all bundler plugins can adhere to that.
Or a utility module/function should be exposed via the SDK or runtime or appropriate package so that build tools can use that to generate and emit the file as part of the build process.
Alternative
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Yessss. I'm busy implementing federation into esbuild and the manifest is one remaining part. You can check my pr that open if you want to see my esbuild implementation.
Also can you dm me on twitter? I added a new api called create container which lets you dynamically create my container interfaces at runtime.

I just realized you're from intuit and AppFabric team. I think Zack C is working with you guys

Okay here is the spec:
INSTANCE_NAME = mfConfig.name
APP_IDENTIFIER = sanitized package.json name usually. eg comprehensive-demo-react18_app-01
ENV_TYPE= "local" when localhost otherwise something else, dont think theres any specific requirement
REMOTE_FILENAME = remoteEntry.js, without publicPath
REMOTE_PATH = path to remoteEntry, like /js/, without public path
REMOTE_TYPE = mfConfig.library.type. "global" if its var, assign, window, etc. "esm" if its esm output or output module.
types = would be the types info, which is TS type info.
pluginVersion = package.json.version of federation runtime
publicPath = "http://localhost:3001/" (abs url) | "auto"
PACKAGE = the package name. like "react"
REMOTE_CONTAINER = the @ syntax parsed from MF options. REMOTE_CONTAINER@http:///
REMOTE_CONTAINER_ALIAS = the key of the remote on mf options. for example {myApp: app2@http} REMOTE_CONTAINER_ALIAS is myApp, while container name is app2
CONSUMED_MODULE = what the user is importing from a remote. import(REMOTE_CONTAINER_ALIAS/CONSUMED_MODULE)
REMOTE_ENTRY = the entry url for the remote, can be either .js or .json manifest pointer.  REMOTE_CONTAINER@REMOTE_ENTRY
EXPOSED_MODULE = the name of an "exposes" without the './', for example SideNav
{
  "id": "INSTANCE_NAME",
  "name": "INSTANCE_NAME",
  "metaData": {
    "name": "INSTANCE_NAME",
    "type": "app",
    "buildInfo": {
      "buildVersion": "ENV_TYPE",
      "buildName": "APP_IDENTIFIER"
    },
    "remoteEntry": {
      "name": "REMOTE_FILENAME",
      "path": "REMOTE_PATH",
      "type": "REMOTE_TYPE"
    },
   "types": {
      "path": "",
      "name": "",
      "zip": "@mf-types.zip",
      "api": "@mf-types.d.ts"
    },
    "globalName": "INSTANCE_NAME",
    "pluginVersion": "0.1.9",
    "publicPath": PUBLICPATH
  },
  "shared": [
    {
      "id": "INSTANCE_NAME:PACKAGE",
      "name": "PACKAGE",
      "version": "18.2.0",
      "singleton": true,
      "requiredVersion": "^18.2.0",
      "assets": {
        "js": {
          "async": [], the dynamic imported chunks, non initial
          "sync": [
            "894.js", the chunks it needs
          ]
        },
        "css": {
          "async": [],
          "sync": []
        }
      }
    },
  ],
  "remotes": [
    {
      "federationContainerName": "REMOTE_CONTAINER",
      "moduleName": "CONSUMED_MODULE",
      "alias": "REMOTE_CONTAINER_ALIAS",
      "entry": REMOTE_ENTRY
    },
    {
      "federationContainerName": "app_02",
      "moduleName": "Dialog",
      "alias": "app_02",
      "entry": "http://localhost:3002/mf-manifest.json"
    },
    {
      "federationContainerName": "app_03",
      "moduleName": "Button",
      "alias": "app_03",
      "entry": "http://localhost:3003/mf-manifest.json"
    },
    {
      "federationContainerName": "app_04",
      "moduleName": "loadApp",
      "alias": "app_04",
      "entry": "http://localhost:3004/mf-manifest.json"
    },
    {
      "federationContainerName": "app_05",
      "moduleName": "components",
      "alias": "app_05",
      "entry": "http://localhost:3005/mf-manifest.json"
    }
  ],
  "exposes": [
    {
      "id": "INSTANCE_NAME:EXPOSED_MODULE",
      "name": "EXPOSED_MODULE",
      "assets": {
        "js": {
          "sync": [
            "__federation_expose_SideNav.js"
          ],
          "async": [
            "729.js",
            "569.js",
            "457.js",
            "710.js",
            "894.js",
            "210.js"
          ]
        },
        "css": {
          "sync": [],
          "async": []
        }
      },
      "path": "./SideNav"
    },
    {
      "id": "INSTANCE_NAME:Page",
      "name": "Page",
      "assets": {
        "js": {
          "sync": [
            "__federation_expose_Page.js"
          ],
          "async": [
            "729.js",
            "569.js",
            "457.js",
            "710.js",
            "894.js"
          ]
        },
        "css": {
          "sync": [],
          "async": []
        }
      },
      "path": "./Page"
    }
  ]
}

This is fantastic. Are all of these fields used by the federation runtime ? Is there a subset of the fields which are strictly required ?

I believe all fileds are used. some by options like preloadRemote, others are used for loadRemote etc. I dont think we pack any additional data in here other than whats directly needed for all features of the runtime to function

@ScriptedAlchemy If we are consuming multiple exposed modules from a remote, then each of those gets listed separately on the remotes array in the manifest. Why is that so ???

There can only be a single version of a remote that one consumer can use, right ??
When a container does this, there's no way for a bundler to unambiguously resolve this to different remotes.
import Button, { someThingElse } from 'project-b/button';
import Link, { someThingDifferent } from 'project-b/link';

Hence, why can't we simplify the remotes array to be:
"remotes": [
    {
      "federationContainerName": "http://localhost:8080/packages/examples/project-b/dist/rspack/esm/my-remote-entry.js",
      "moduleNames": ["button", "link"],
      "alias": "project-b",
      "entry": "*"
    },
],

I had a quick look at the esbuild implementation which also generates the manifest here
It only uses the module federation config provided by the user which doesn't have sufficient information about the "exposed" modules which are used from remotes.
For eg. in my case I have the following federation config:
remotes: {
    'project-b': 'https://localhost:8080/remoteEntry.js'
}

and I consume 2 exposed modules from the remote:
import Button, { someThingElse } from 'project-b/button';
import Link, { someThingDifferent } from 'project-b/link';

repo: module-federation/core


text:
Add as defaultProps types and tests

Fixes #223
Note: there is diff noise in the tests related to the changes we did in the core package for the comma-separated rules and ampersand in #245

@peduarte just tested against your use case in the original issue and realized you wanted the usage in jsx to reflect the changes you made in the defaultProps which isn't possible in typescript with the syntax you wrote.
if you need something similar then we'd need to make the default props a function call which then we could use to return a new component with the default props and their typing applied to them. (I think you showed me something like this previously in one of your discussions)
so for this to work we need:
const Text = styled("p", {});

const TextLink = styled(Text, {}).withProps({ as :'a'});

or:
const Text = styled("p", {});

const BaseTextLink = styled(Text, {});
const TextLink = BaseTextLink.withProps({as: 'a'})

in both of the examples above, we could use the withProps function to return a new component with its appropriate typing
other alternatives:
import {applyDefaultProps} from '@stitches/react'

const Text = styled("p", {});

const BaseTextLink = styled(Text, {});
const TextLink = applyDefaultProps(BaseTextLink, {as: 'a'})

or:
import {applyDefaultProps} from '@stitches/react'

const Text = styled("p", {});

const TextLink = styled(Text, {...styles}, {...defaultProps});

LGTM!

authors: hadihallak peduarte

repo: modulz/stitches


text:
Authentication without browser

It'd be nice to use this on a headless server where I cannot use a browser. Right now, my work around is to authenticate on my computer and then copy calendar-cli.json to the server, but that doesn't seem ideal...

Implemented --no-browser option in version 0.2.2.

authors: mogproject zowpowow

repo: mogproject/calendar-cli


text:
背景色の変更

背景色が272727固定になっているのでできれば背景の色変更できればなと。
説明文の方と色を合わせたいのですが、毎回検証→色変更は面倒なので)
（Greasy Forkの方にも誤って投稿してしまいました、ｽﾐﾏｾﾝ）

背景色は画面上部に表示したときにヘッダーと馴染むようにしていたのですが、確かに他の色と合わせたい場面もあるかと思います
背景色とかアクティブ色とかが変更できるように設定項目を追加しておきます


text:
allow the use of the back facing camera

Allow the user to use either the front or the back camera. This is useful when on a phone.

thanks to @gnargfu, add the ability to use the bake camera


text:
[bug] line seperator in conjunction with heading

it seems to be a kind of a follow up to #4... but definitively something weird is going on:
"heading2" (no matter if you use ## before or --- underneath) gets underlined... some phraser underline "heading1" and "heading2", but according to CommonMark no heading is underlined by default!
so either "heading1" and "heading2" should be underlined or none, which is IMHO the correct resp. better choice because you can still ad a line separator (---) if you want to.

This is an issue with the default style (from github) -> heading have an underline
Please select another css if you dont like that style.


text:
6-3 で負の数を渡した場合の出力がない

6-3 で add1() に負の数を渡して err != nil となった場合の出力がありません。
err を fmt.Printf() 等で出力するか、fmt.Errof() でラップした戻り値で更になにかするか、いずれかが意図であるように思われます。

ご指摘ありがとうございます。
fmt.Printf() に直しました。。。

authors: fkmhrk tyochiai


text:
Can't manage to push multiple requests

I have tried a variety of ways to send a list of 21 files in a push request.  But it seems that somewhere something is ending causing the server to crash
/home/alan/dev/node-http2/lib/protocol/stream.js:627
      throw new Error('Sending illegal frame (' + frame.type + ') in ' + this.state + ' state.');
      ^

Error: Sending illegal frame (DATA) in CLOSED state.
    at Stream.transition [as _transition] (/home/alan/dev/node-http2/lib/protocol/stream.js:627:13)
    at Stream._pushUpstream (/home/alan/dev/node-http2/lib/protocol/stream.js:230:8)
    at Stream._finishing (/home/alan/dev/node-http2/lib/protocol/stream.js:351:10)
    at emitNone (events.js:67:13)
    at Stream.emit (events.js:166:7)
    at finishMaybe (_stream_writable.js:468:14)
    at endWritable (_stream_writable.js:478:3)
    at Stream.Writable.end (_stream_writable.js:443:5)
    at OutgoingResponse._finish (/home/alan/dev/node-http2/lib/http.js:355:17)
    at emitNone (events.js:72:20)

I go through a process which gives me an array of objects with the push url and filename in each object.  My code is
        if(req.url === '/' || req.url === '/index.html') {
          if(res.push) {
            pushlist.forEach(item=> {
              var p = res.push(item.url)
              p.writeHead(200);
              fs.createReadStream(item.filename).pipe(p);
            })
          }
        }
        router(req,res,donewrapper);

the router(req,res,donewrapper); goes on to server index.html via serve-static.
without the push stuff, the server works perfectly - and single stepping through the initialisation of each of the file readstreams also seems to work.  It is only later when one of the streams end (see how OutgoingResponse._finish is at the bottom of the call stack) that this happens.
I don't know where to go next.

This looks like a duplicate of #107 (the stack is exactly the same). I suspect your client is sending a RST_STREAM for one or more of the pushes, for some reason or another.


text:
Possible bug in unix()

not sure if this is a bug or not, but Resharper doesn't like
function unix () {
    return Math.floor(+this / 1000);
}

Is ‘this/1000’ valid javascript?
Other methods seem to use this._offset

When this is coerced to a number by +this, it's equivalent to calling this.valueOf().  So any logic that needs to involve _offset or _d is already handled by the valueOf function.  The unix function just trims it from milliseconds to whole seconds.
The valueOf function is special in JavaScript, as it's overridden from the base Object prototype that all other objects are derived from.
https://github.com/moment/moment/blob/master/src/lib/moment/to-type.js
So yes, this is valid Javascript.

repo: moment/moment


text:
Beef up formatting tests to communicate moment(undefined, <your favorite format>).toISOString() won't work

Slightly related to #3180. On one hand...
var k = moment(undefined);
k.toISOString()  /// This returns ok.

On the other hand...
var k = moment(undefined, "YYYY-MM-DD");
k.toISOString()  /// This returns "invalid date".

It's unintuitive that moment(undefined) behaves as moment(), but moment(undefined, <your favorite format>) is really trying to format undefined and is failing. To help with this, let's add a test to make sure people understand this behavior.

We'll take this, sure.

Tracking in PR #3339


text:
Implement type checking to allow calendar to specify config first

Currently the API of moment().calendar() is specified as moment().calendar(moment-like, formats).
As pointed out in urish/angular2-moment#64, changing the formats is actually a much more common operation than changing the reference time.
It should be possible to use type checking to implement moment().calendar(formats) as an overload of this.
To accomplish this, ensure that exactly one parameter is specified, and that that one parameter has a type of object, and is NOT a moment. If that is done, it should be reasonable to assume it is a format specifier.

Found this issue report today and wrote up a fix, in the process of adding a few tests to the suite to cover my change.  Will put up my first ever PR shortly.

Hm looks like I might be late to the party if I am reading this right.

Closed in favor of #3666

authors: josephjaniga maggiepint


text:
feat: add logging implementation of experimental metrics middleware

This commit refactors the "Experimental Metrics CSV" middleware to
be an abstract class that is destination-agnostic. This will allow
us to provide implementations of it that write to other targets
besides CSV. Also included in this PR is an implementation that
writes the metrics to the logger, which is a slightly more scalable
destination for most of our users to consider enabling.

Looks good. My only comment is that if feels strange that the abstract class is in the impl directory instead of the concrete versions.

fair, maybe i'll try to think of a better name for that dir in a subsequent commit

repo: momentohq/client-sdk-javascript


text:
Manual download of hp.json file

Looking at
https://github.com/monarch-initiative/phenopacket2prompt/blob/52c7baa95874c9af35154a50b70a04c895197339/docs/setup.md?plain=1#L23-L25
it seems to suggest hp.json should be manually downloaded. However, it seems to me like
java -jar target/phenopacket2prompt.jar download
does exactly that + downloading hp-international.obo. @pnrobinson is this correct? If so, I can edit the documentation and make a PR

The download command does this! The documentation is currently completely out of date, sorry

Ok, I will edit it and make a PR

Fixed by https://github.com/monarch-initiative/phenopacket2prompt/pull/52

authors: leokim-l pnrobinson


text:
Add the ability to put color on the files in the Explorer

That’d be great if we could add color to the files in the files explorer as well (akin to what macOS does in the Finder with color tags).
I love this kind of thing and I’m definitely gonna use it, thank you for your work!

Thanks for the suggestion, I like the idea, it would definitely fit in a new extension.
I am happy that you like the extension :)

authors: mondersky morceaudebois

repo: mondersky/tabscolor-vscode


text:
Translations from weblate

Bulk of French translations from multiple contributors, but also translations for Turkish and Chinese

are we removing the @canonically-unique-host place holders from Moneropedia -> Locally-unique host also? (or the entire guide)

noticed an @démon under Documentation RPC on the dev guides page  https://deploy-preview-2178--barolo-time-757cf9.netlify.app/fr/resources/developer-guides/index.html

are we removing the @canonically-unique-host place holders from Moneropedia -> Locally-unique host also? (or the entire guide)

We can do it independently from this PR. It's better to not manually touch strings coming from Weblate

authors: Monero-Weblate erciccione plowsof

repo: monero-project/monero-site