SX [Bug] Individual Requests - Selection checkbox indeterminate state incomplete

Bug
Individual Requests - Selection checkbox indeterminate state incomplete

How does this bug manifest itself to the user?  What are the repro steps?


Configure dired-git-info variables

dgi-commit-message-format set to
%h  - Abbreviated commit hash
%cs - committer date, short format (YYYY-MM-DD)
%s  - subject
First two are fixed-width, which makes it look neater.
dgi-auto-hide-details-p set to nil, assuming a wide window.
I'm not sure if these are supposed to be inside use-package! after reading the previous commits to the file.
Screenshot:

Looks good to me. Thanks!


How to use WordPress custom page templates with router?

I need to have WordPress page templates.
If I put this anywhere in the theme folder, the drop down shows up in the UI, which is great.
<?php
/**
 * Template Name: Full Width Page
 *

Not sure if that file should just be in the route, or maybe in a directory like wp-templates, but it doesn't matter for now.
But how should I setup router.php to use this template? Seems like we should have something like path_from_template(), except the path could be anything, so it doesn't make a lot of sense.
Seems like we will need to use this function in some way.

@jrobson153 and I discussed this today, and how things like URL redirects cause issues in Vue. We do need to deal with pages that you shouldn't be able to get to, like individual slides in a slideshow page structure.
Perhaps we add a checkbox to the meta panel in WordPress that is "don't allow direct access to this page", and we just serve up the parent page's content... not sure.

Thinking about this the past couple days - I keep coming back to this solution:

I actually really like your idea of just looking for all pages with the page template meta set and setting up the routes automatically. It requires little config, and can be cached so it's not server intense.

This one seems perfect because it's super client-friendly and flexible - if we built a function that did this, we could theoretically build an entire WP site just by selecting template types from the drop-down menu. Even if that's not something we want to do, this'd create a super user-friendly front-end interface for selecting Vue components through WordPress, which is a big step toward seamlessly combining the two.
I'm going to spend a minute pulling together a proof-of-concept for that solution - I want to dig in and see where some of the limitations are.

Submitted PR implementing the above solution in #67

Added in 8843dfd!


Add domain hue.edu.vn

This domain is email of website https://thuathienhue.edu.vn

@tuannda Pull request merged. Thank you.


Context module not correctly implemented in Styleguide

Describe the bug
The default Styleguide title is replaced by '| Context Module'.
To Reproduce
Steps to reproduce the behavior:

Open the (acpaas-ui_angular Styleguide)[https://digipolisantwerp.github.io/acpaas-ui_angular/] in a tabbed browser.

Expected behavior
The title in the tab of the browser should be 'Acpaas UI | Angular Modules' and it should update to  'Acpaas UI | Context Module' when you open the 'Context' example in de sidebar.
Screenshots

OS (please complete the following information):
Device: MacBook Pro (Retina, 13-inch, Late 2013)
OS: macOS High Sierra (Version 10.14.1)
Browser: All browsers

Fixed in #170 (v3.0.0)


Simplify flake

This PR simplifies the flake down to the bare minimum. In this case, the apps block is unnecessary because nix run works with the default package output.
Feel free to reject if you wish 😄

Thanks !!!


Error msg: Variable 'rigInfo' originally saved as a VRRigInfo cannot be instantiated as an object and will be read in as a uint32.

rigInfo saved during behaviour as a conflicting 'object'


Automate run local network for integration

+ docker build --pull -t allorad -f ./Dockerfile.development .
DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
            Install the buildx component to build images with BuildKit:
            https://docs.docker.com/go/buildx/

unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /<REDACTED>/Dockerfile.development: no such file or directory

one strange thing is that the redacted path is one directory up (../) of the root of the entire workspace path

was able to get commit b2b1c087b1a02b8bdebb3443499275b6ce9c9839 to launch three validators


Fix tests for windows

#440

Thanks. For the final one, it is only failing in the cleanup (which can be safely ignored). I would remove the finally block and stop using try: for the body of the test.

(happy to push the test here, if you don't have the time)

Unfortunately, just a touch of lint: please run black fsspec


Documentation link in readme.md doesn't work

The documentation link to https://material-ui-pickers.firebaseapp.com/ in the main Readme.md file returns a 404

О_о

Can you please add a screen, share your browser, because for me it opens properly.

Ah it may be the network I am on then, as I connect through a proxy which may be blocking the link. It is impossible to tell which one is the issue. If it works ok for you I will try it on my homenetwork later.
Thanks for checking though :-)


Full screen dialog and back button on mobile

Having a full screen dialog really is a huge improvement for mobile.
But it really really needs to support the Back button. It's so counter intuitive for users when they hit the back button on their mobile and navigate them the actual page they were on.
Is it hard to add this because of the different routers used ?

It's outside of the scope of the library. You need to wire the open state with the URL.

@oliviertassinari ok thanks.
Will search for an example of how to do that online.

Anyone solve this? Cbf coding from scratch 😄

Any solution for this?

I'm a bit confused because the mUI docs for the Dialog example state that:

Touching outside of the dialog, or pressing Back, cancels the action and closes the dialog

But this does not appear to be the case?

@JulesAU Indeed I think this sentence is not correct.
I've made a demo that binds the open state with the location hash, like this, clicking the back button works as expected: https://codesandbox.io/s/material-demo-7zf07
@oliviertassinari do you think this could be added to the docs?

@ValentinH Thanks for sharing your demo. I believe this issue is enough as documentation.

`

[ ]  [#@@@@@#@](**### **_

`[url]([url]([url]([url](

url
))))`
_****)
`

I made a React hook useUrlHashState() based on @ValentinH 's answer.
import { SetStateAction, useEffect, useState } from 'react';

/**
 * use a boolean state that binds to a url hash
 * @param hash a string starts with '#'
 * @returns current state, and a function to update it
 */
export function useUrlHashState(
  hash: string
): [state: boolean, setState: React.Dispatch<SetStateAction<boolean>>] {
  const [state, setState] = useState<boolean>(window.location.hash === hash);

  useEffect(() => {
    const onHashChange = () => setState(window.location.hash === hash);
    window.addEventListener('hashchange', onHashChange);
    return () => window.removeEventListener('hashchange', onHashChange);
  }, [hash]);

  return [
    state,
    setStateAction => {
      if (
        (typeof setStateAction === 'boolean' && setStateAction) ||
        (typeof setStateAction === 'function' && setStateAction(state))
      ) {
        window.location.hash = hash;
      } else {
        window.history.back();
      }
    },
  ];
}

You can use MUI useTheme and useMediaQuery hooks to track screen size:

Make your own wrapper component with additional useEffect and callback to handle the history change
e.g.:
import React, { useCallback, useEffect } from 'react';
import ButtonBase from '@material-ui/core/ButtonBase';
import Dialog from '@material-ui/core/Dialog';

type Props = {
  open: boolean;
  onClose: () => void;
};

export const MyDialog: React.FC<Props> = ({ open, onClose, children }) => {
  useEffect(() => {
    if (!open) return;
    window.history.pushState('forward', '', '#dialog');
    window.addEventListener('popstate', onClose);

    return () => {
      window.removeEventListener('popstate', onClose);
    };
  }, [open, onClose]);

  const onCloseModal = useCallback(() => {
    onClose();
    window.history.pushState(
      'forward',
      '',
      window.location.pathname + window.location.search
    );
  }, [onClose]);

  return (
    <Dialog open={open} onClose={onCloseModal}>
      <ButtonBase onClick={onCloseModal}>X</ButtonBase>
      {children}
    </Dialog>
  );
};

Make your own wrapper component with additional useEffect and callback to handle the history change e.g.:
import React, { useCallback, useEffect } from 'react';
import ButtonBase from '@material-ui/core/ButtonBase';
import Dialog from '@material-ui/core/Dialog';

type Props = {
  open: boolean;
  onClose: () => void;
};

export const MyDialog: React.FC<Props> = ({ open, onClose, children }) => {
  useEffect(() => {
    if (!open) return;
    window.history.pushState('forward', '', '#dialog');
    window.addEventListener('popstate', onClose);

    return () => {
      window.removeEventListener('popstate', onClose);
    };
  }, [open, onClose]);

  const onCloseModal = useCallback(() => {
    onClose();
    window.history.pushState(
      'forward',
      '',
      window.location.pathname + window.location.search
    );
  }, [onClose]);

  return (
    <Dialog open={open} onClose={onCloseModal}>
      <ButtonBase onClick={onCloseModal}>X</ButtonBase>
      {children}
    </Dialog>
  );
};

This one is something, but the history is being saved actually. So if you open and close the dialog several times, then you will go through all this history when clicking browser back button. Also, I think you need to use onCloseModal function for popstate listener, not onClose.

 onClose();

what does onClose() function do here? Can someone post a complete example please


RTMClientv2 should respect rate limit

Reproducible in:
The Slack SDK version
slack-sdk==3.3.1
Python runtime version
Python 3.8.7
OS info
Linux 5.4.97-gentoo #1 SMP
Steps to reproduce:
Cause socket timeout during ssl negotiation.
Expected result:
Connection to fail but a reconnection attempt be performed without triggering the Slack rate limit.
Actual result:
Following numerous handshake timeout's, the RTMClientv2 reconnected to frequently within a short time frame.  This caused the Slack server to respond with a ratelimited error.
2021-02-14 18:19:49,579 ERROR    slack_sdk.rtm.v2          Failed to establish a connection (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81, error: _ssl.c:1108: The handshake operation timed out)
Traceback (most recent call last):
  File "/opt/errbot/lib/python3.8/site-packages/slack_sdk/socket_mode/builtin/connection.py", line 109, in connect
    sock.connect((hostname, port))
  File "/usr/lib/python3.8/ssl.py", line 1342, in connect
    self._real_connect(addr, False)
  File "/usr/lib/python3.8/ssl.py", line 1333, in _real_connect
    self.do_handshake()
  File "/usr/lib/python3.8/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
socket.timeout: _ssl.c:1108: The handshake operation timed out
2021-02-14 18:19:49,579 INFO     slack_sdk.rtm.v2          The connection has been closed (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:19:49,579 INFO     slack_sdk.rtm.v2          The connection has been closed (session id: b88f63ee-d644-45a8-bf18-be36c8673728)
2021-02-14 18:19:49,579 INFO     slack_sdk.rtm.v2          A new session has been established (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:19:49,579 INFO     slack_sdk.rtm.v2          Connected to a new endpoint...
2021-02-14 18:19:59,590 DEBUG    slack_sdk.rtm.v2          This connection is already closed. (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:19:59,590 INFO     slack_sdk.rtm.v2          The session seems to be already closed. Going to reconnect... (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:19:59,590 INFO     slack_sdk.rtm.v2          Connecting to a new endpoint...
2021-02-14 18:20:00,075 ERROR    slack_sdk.rtm.v2          Failed to retrieve WSS URL: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'ratelimited'}
2021-02-14 18:20:00,075 ERROR    slack_sdk.rtm.v2          Failed to check the current session or reconnect to the server (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81, error: SlackApiError, message: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'ratelimited'})
2021-02-14 18:20:10,092 DEBUG    slack_sdk.rtm.v2          This connection is already closed. (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:20:10,117 INFO     slack_sdk.rtm.v2          The session seems to be already closed. Going to reconnect... (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:20:10,121 INFO     slack_sdk.rtm.v2          Connecting to a new endpoint...
2021-02-14 18:20:10,339 ERROR    slack_sdk.rtm.v2          Failed to retrieve WSS URL: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'ratelimited'}
2021-02-14 18:20:10,339 ERROR    slack_sdk.rtm.v2          Failed to check the current session or reconnect to the server (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81, error: SlackApiError, message: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'ratelimited'})
2021-02-14 18:20:20,350 DEBUG    slack_sdk.rtm.v2          This connection is already closed. (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:20:20,350 INFO     slack_sdk.rtm.v2          The session seems to be already closed. Going to reconnect... (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:20:20,350 INFO     slack_sdk.rtm.v2          Connecting to a new endpoint...
2021-02-14 18:20:20,556 ERROR    slack_sdk.rtm.v2          Failed to retrieve WSS URL: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'ratelimited'}
2021-02-14 18:20:20,557 ERROR    slack_sdk.rtm.v2          Failed to check the current session or reconnect to the server (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81, error: SlackApiError, message: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'ratelimited'})
2021-02-14 18:20:30,567 DEBUG    slack_sdk.rtm.v2          This connection is already closed. (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:20:30,567 INFO     slack_sdk.rtm.v2          The session seems to be already closed. Going to reconnect... (session id: 18e8f520-5e64-443c-98ed-089ab1ef6f81)
2021-02-14 18:20:30,567 INFO     slack_sdk.rtm.v2          Connecting to a new endpoint...

Thanks again for reporting this. I will release a new version including the fix for this issue soon.

slack-sdk v3.4.0 is now available: https://pypi.org/project/slack-sdk/3.4.0/
Thanks for your feedback on this issue. Please let us know if you find any issues with the new version.


RuntimeError: Sizes of tensors must match except in dimension 1.

img_size=512, grid_size=(16,16)
x = torch.cat([x, skip], dim=1)
RuntimeError: Sizes of tensors must match except in dimension 1. Expected size 32 but got size 64 for tensor number 1 in the list.

i have same questions

Excuse me, Do you know the images processing. Can you share your code?

很奇怪，这个所以图像大小应该是多少呢？


Performance chart and History chart tweaks

Description:
Minor changes to improve edge-case handling in performance chart, modify sizing of both chart containers, modify color scheme in performance chart
Changes I Made:
PerfView.jsx – added container div around chart to improve chart re-sizing, fixed bug that caused mouseover highlighting to fail, modified color scheme
Chart.jsx – formatted for eslinter, removed margins, increased internal chart space and added a container div around chart to get correct parent size (to potentially be used for dynamic chart resizing later)
d3graph.css – added flexbox around performance chart, to allow for addition of other data later, renamed classes and containers for both charts to use similar syntax

Forgot to revert colors to those in current master

Oops, current colors were already in master. Carry on...


[Feature] Add additional objects to block Metadata

🚀 Feature

The block metadata should include a couple additional things:

[ ] Total supply of credits (add mints and subtract burns)
[ ] Cumulative proof target

Closed with #1461


Model Architecture, designs and decisions

Determining the models structure and relationships

Done

Great job, team!

organized the meetup to decide the database schema and finalize the database model structure


chore: update every tests to run mode

Updated every tests to use run mode.

I saw the PR title and thought you'd updated every operator in a single PR 😲😂


Transition from MSTest to xUnit for Unit Testing

Dumpify currently uses MSTest for unit testing. However, MSTest is basically an unmaintained unit testing framework. It aggregates with no actual value compared to more up-to-date and robust unit testing frameworks such as xUnit.
It'd be a strategic move that will provide long-term benefits for the project. And will ensure that it stays on top of best practices regarding to unit testing.

Our current testing capabilities are lacking to say the least. I was planning on investing in tests once this month's release is out, and the transition from MSTest to xUnit can be done as part of that effort


Bad code generation

Hello Guillaume (Adam),
On the page "HT_Download_Trial_SCANeR.md" I found a "bad code generation".
I think it might be due to the new system to add links.
Can you please check?
Thanks,
Sylvain

Bonjour Sylvain,
I made the correction on the website.
Should be fine now.
I think here is the cause:
When merging the "minor grammatical changes", there was a conflict.

On your side, there are text corrections, including in the first and last text lines
On the published side, I added the header and removed the "previous" and "next" links
I made these changes after Terry made a copy (fork) of the files
This resulted in this "merge resolution tags":

So to fix this

Removed all the "merge resolution tags"'
Kept only the "minor grammatical changes"
Kept (or restore) the header
Removed the "previous" and "next" links (if they reappear)

To avoid the issue next time

When Github notifies the merge conflict, decide to keep HEAD or [new commit] changes by editing the merge conflict file (it normally opens automatically)

It should not happen too often though. This is only due to me making changes over all files at once.

Also to avoid having more merge conflicts for Terry:

Discard the current copy : delete terry-avs/SCANeR-Quick-Starts
Make a copy again: fork from AVSimulation/SCANeR-Quick-Starts to terry-avs
Or when Terry gets access to AVSimulation:
Make the changes directly on AVSimulation/SCANeR-Quick-Starts
Use the "Published" branch for instant changes, or a new branch if it needs reviewing before publication.
Maybe clear for you but now it's written just in case ^^'

I let you close the issue if it's good

Thank you it's clear!


Update Chinese (Simplified) translation

I translated a part of the strings. I will add the missing translation later.

Amazing, thank you! Let us know when you are ready so we can approve the merge!

@gtn1024  Wait...Are you using Google Translate to finish this work? Seriously? Please stop this KPI grabbing behavior.

@gtn1024 Wait...Are you using Google Translate to finish this work? Seriously? Please stop this KPI grabbing behavior.

Well, while using Google Translate certainly makes things faster, I'd still advise to at least review and fix Google Translate results instead of simply running the text through it. We (the devs) have no way of assessing the quality of the translations, so I am glad that you guys do proofread each other's work and give healthy advice to each other on this. :)

@moriwang Alright, I must acknowledge that I did use use Google Translate for some sentence. I will not do it again.
@waydabber Thanks.

Hi@waydabber, I totally agree with @moriwang. It looks @gtn1024 finish all the work by translation tool. I do not think it is a good practice and I highly recommend to totally refuse this PR.
Because, for further improvements, we have to fix all the mistakes which is caused by the non-sense approach.
Please respect all the contributions from others, @gtn1024 . The first PR of Chinese localization is really not so important.

Uhh-ohh, I can't really judge on this case I am afraid, but I understand that an action must be taken, which will be the following:

Because of the controversy I'll close this PR.
I'd like to kindly ask any three of you to start a new PR when any of you (or somebody else) completed a full, valid translation (preferably not via an automated tool like Google Translate by itself).
Because of the questions, if this person will be @gtn1024 (who I am sure has the best of intentions even though it seems the implementation suffered a bit), I'll kindly ask a second opinion from @womeimingzi11 or @moriwang just to make sure that the quality is the expected one this time.
Please let the others know if somebody starts working on an alternate translation in the translation thread so we can avoid conflicts and working in vain. If there are multiple translations for the same language and all of them seem legit, I'll choose the one with the lower PR number.

I hope this is is a sensible and fair approach. I am sorry if I misjudged the situation, please let me know if anybody feels bad about this!
Thank you all very much for your contribution!

I feel so sorry for everybody. Thanks for your work! @moriwang @womeimingzi11 @waydabber

Uhh-ohh, I can't really judge on this case I am afraid, but I understand that an action must be taken, which will be the following:

Because of the controversy I'll close this PR.
I'd like to kindly ask any three of you to start a new PR when any of you (or somebody else) completed a full, valid translation (preferably not via an automated tool like Google Translate by itself).
Because of the questions, if this person will be @gtn1024 (who I am sure has the best of intentions even though it seems the implementation suffered a bit), I'll kindly ask a second opinion from @womeimingzi11 or @moriwang just to make sure that the quality is the expected one this time.
Please let the others know if somebody starts working on an alternate translation in the translation thread so we can avoid conflicts and working in vain. If there are multiple translations for the same language and all of them seem legit, I'll choose the one with the lower PR number.

I hope this is is a sensible and fair approach. I am sorry if I misjudged the situation, please let me know if anybody feels bad about this!
Thank you all very much for your contribution!

Good idea @waydabber, I totally agree with this plan. In fact,I didn't translate by myself, so there was no conflict. I just checked the PR list to find what's new here.
Can't wait for @gtn1024 's new contribution! Good luck!
BTW, I realized there may need some peer-review-like approaches in translation workflow. For some more detailed suggestions I'd like to post in discussion later.

Seems like #657 took some of my suggestion, maybe someone can continues work on the that.


Add proxy management

Twitter API has a limit:
500 requests / 10 minutes / 1 IP
With more IPs, higher limit can be achieved. Internal proxy management would be beneficial for this.
I suggest adding proxy config parameter to Rettiwt constructor. The config should be passed and applied in FetcherService request() method.

I'll be looking into it now.

Won't rotating the proxies with successive requests flag the Twitter account with suspicious activity?

Rettiwt constructor already takes apiKey as a parameter. Accounts can have proxies assigned to them. As long as proxy is kept consistent for each account, this is not going to be a problem.

So one apiKey must have one proxy?

Got it


test: fix check split bug in pd

cherry-pick #7841 to release-3.0

Signed-off-by: Liqi Geng<EMAIL_ADDRESS>What problem does this PR solve?
Problem Summary:
Fix check split bug in pd.
What is changed and how it works?
What's Changed:
It's possible that a left region has an old epoch so I remove the assert in check_split.

r1  => [0, 10)  r2 => [10, 20)
r1 merge to r2
r2 => [0, 20)
r2 split
r3 => [0, 10) r2 => [10, 20)
When r1 reports to PD again, the check_split will panic.

Move test_node_merge_write_data_to_source_region_after_merging test to failpoint test.
This is a mistake.
Related changes

Need to cherry-pick to the release branch

Check List
Tests

No code

Side effects
No.
Release note

No release note

/merge

/merge

/run-all-tests

/merge

/merge

/merge

/merge

/merge

/merge


1231

@laojiuh, you must sign our contributor license agreement before your changes are merged. Click here to sign the agreement. If you are a VMware employee, read this for further instruction.

@laojiuh, we have received your signed contributor license agreement. The review is usually completed within a week, but may take longer under certain circumstances. Another comment will be added to the pull request to notify you when the merge can proceed.

@laojiuh, VMware has rejected your signed contributor license agreement. The change has already been merged, but it will be backed out by the project maintainers if the agreement is not resigned in a timely manner. Click here to resign the agreement.


Added deletion of cache files and updated interface of iOS LlmTaskRunner and LlmInference

Moved caching logic to LlmTaskRunner
Added method to interface of LlmInference for deleting all caches.
Updated property types in LlmInference.Options
Added an extra check to see if provided modelPath is valid. As a result updated LlmInference and LlmTaskRunner inits to be throwing methods.
Updated access modifiers of some classes.

@mbrenon Our Google workspace is down. In case you need anything for the release, LMK here or how we can communicate.


Update chapter locations for Festus in portion

The chapter locations mentioned for Festus in the Full Chapter Analysis updates to the portion were incorrect. This corrects the page on biblequiz.com. The newsletter PDFs should also be updated going forward. I see they are PDFs so not sure how those get generated and uploaded to the repo.

@michsco @kevintgallo - FYI


Fix vendor lib issues, and clean up color threshold handling

This PR uses the WPILib Preferences API to keep threshold values persistent across robot reboots, while allowing the comp and practice bots to use their own settings.

Yay! Thank you very much!


Prevalence side panel filter headings don't change with localization change

@dptolle I don't think I can check this


Thoughts on new colours?

Feels strange now, but let's give it some time. I managed to get used to the black header and I now like it.

hahaha I knew I'd find an issue on this here :rofl:


add support for limits on TestCase.<setUp|tearDown(Class)?> methods

as a prefactoring, #11 was implemented for the django test runner integration

All in all looks good to me -


Add sequence to transaction builder

I would like to propose the new argument sequence to build transaction. With this feature, the signer client can self manage the sequence and send multiple transactions in a block without receiving unexpected sequence error.
A signer client currently can send only one transaction in a block since the blockchain will update account sequence after the transaction, so the sequence queried from the chain will be always wrong before the current transaction is included into a block. Therefore, I think self manage sequence is a solution for this case.
The detailed implementation is here: https://github.com/desmos-labs/cosmos-go-wallet/commit/e5ab3824cc32681a91b5b8b01bc26c9c32b0e4ce
In addition, I build a signer client for demo to achieve the multiple transactions in a block: https://github.com/dadamu/desmos-demo/blob/main/backend/service/client.go#L163
@RiccardoM, What do you think?   If you think it is worth to do, I can create a PR for it.

@dadamu Yes, this would be extremely useful for some cases! I think adding the ability to specify a sequence would be great!


jarek/8034: [spark] add an example with parquet files

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


update bundlr example url

you could potentially leave this as https://example.bundlr.network, and then leave a link to https://bundlr.network/status for the user to pick a bundlr node, but this is probably just adding confusion


Bug: $generateNodesFromDOM only generates plain text

Lexical version: 0.16.1
Steps To Reproduce

Run script provided.

Link to code example:

The current behavior
When running the script below, only paragraph text is outputted. Headings, lists and anything other than text is outputted when calling toJSON
import { createHeadlessEditor } from '@lexical/headless';
import { $generateNodesFromDOM, $generateHtmlFromNodes } from '@lexical/html';
import { $getRoot, $getSelection } from 'lexical';
import { JSDOM } from 'jsdom';
import type { SerializedEditorState } from 'lexical';

/**
 * Converts an HTML string to a Lexical editor state.
 *
 * @param {string} html - The HTML string to convert.
 * @returns {SerializedEditorState} The serialized editor state.
 */
export const htmlToLexical = (html: string): SerializedEditorState => {
	const editor = createHeadlessEditor({
		nodes: [],
		onError: (error) => { console.error(error); },
	});

	editor.update(
		() => {
			// In a headless environment you can use a package such as JSDom to parse the HTML string.
			const dom = new JSDOM(`<!DOCTYPE html><body>${html}</body>`);

			// Once you have the DOM instance it's easy to generate LexicalNodes.
			const nodes = $generateNodesFromDOM(editor, dom.window.document);

			// Select the root
			$getRoot().select();

			// Insert them at a selection.
			const selection = $getSelection();

			console.log("Generated nodes: ", nodes);

			if (selection) selection.insertNodes(nodes);
		},
		{ discrete: true },
	);

	return editor.getEditorState().toJSON();
};

I call it like so:
const scratch = () => {
    const html = htmlToLexical(
        '
Online English Lessons

Are you worried about making mistakes
',
    )
    console.log(JSON.stringify(html, null, 2))
}

Unfortunately, it doesn't generate headings and I'm not sure why?
"root": {
    "children": [
      {
        "children": [
          {
            "detail": 0,
            "format": 0,
            "mode": "normal",
            "style": "",
            "text": "Online English Lessons",
            "type": "text", // Should be heading?
            "version": 1
          }
        ],
        "direction": null,
        "format": "",
        "indent": 0,
        "type": "paragraph",
        "version": 1,
        "textFormat": 0
      },
    ],
    "direction": null,
    "format": "",
    "indent": 0,
    "type": "root",
    "version": 1
  }
}

The expected behavior
There should be a H2 within the children.
Impact of fix
N/A

You need to configure the editor with the nodes you expect to use. When you provide an empty nodes array in the configuration it will only be able to use TextNode, LineBreakNode, TabNode, and ParagraphNode.


UnauthorizedException not informative

Would it be bad to have its name present. These messages aren't useful while developing. I realise that may expose information, but I think I may want to do that anyway (I want 403 returned)
Prooph\ServiceBus\Plugin\Guard\UnauthorizedException: You are not authorized to access this resource

You want to show what? The class name or the event name?
Am 02.09.2016 06:20 schrieb "Bas Kamer"<EMAIL_ADDRESS>
Would it be bad to have its name present. These messages aren't useful
while developing. I realise that may expose information, but I think I may
want to do that anyway (I want 403 returned)
Prooph\ServiceBus\Plugin\Guard\UnauthorizedException: You are not authorized to access this resource
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prooph/service-bus/issues/136, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYEvNx_7rjxcapwZmHw_b9xF655sbIVks5qlxdxgaJpZM4Jy-4X
.

I would say name of the denied thing. Classnames of commands

Op 2 sep. 2016 om 01:21 heeft Sascha-Oliver Prolic<EMAIL_ADDRESS>het volgende geschreven:
You want to show what? The class name or the event name?
Am 02.09.2016 06:20 schrieb "Bas Kamer"<EMAIL_ADDRESS>
Would it be bad to have its name present. These messages aren't useful
while developing. I realise that may expose information, but I think I may
want to do that anyway (I want 403 returned)
Prooph\ServiceBus\Plugin\Guard\UnauthorizedException: You are not authorized to access this resource
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prooph/service-bus/issues/136, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYEvNx_7rjxcapwZmHw_b9xF655sbIVks5qlxdxgaJpZM4Jy-4X
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

A command does not need to be a classname, see: https://github.com/prooph/service-bus/blob/master/src/CommandBus.php#L62


Mediapipe Holistic js Does not start

Because I can't run mediapipe holistic js, will it fix the error?  I have a project, and I am extremely concerned about this, as nothing works for me.  Can somebody help me?

Como no puedo ejecutar js holístico de mediapipe, ¿solucionará el error? Tengo un proyecto y estoy muy preocupado por esto, ya que nada me funciona. ¿Puede alguien ayudarme?

@tyrmullen help me

@martincho0731 linked to #1600
you can try a prior version of holistic from npm, like version: 0.1.1607486640

@afogel
hi, i'm using cdn, i'm not using npm.  I am using the same example you have in the web demo.  What is happening ? https://codepen.io/mediapipe/pen/LYRRYEw

hi, could the problem be in the chrome browser?  Does anyone know what is happening?  I need a solution for this please

nope, the demo is broken cross browser rn.
To get it to work, the best situation I've found is to go through the minified version and figure out what you need in order to run it.
CDN does use npm.
Another option I'm currently exploring is setting up a backend service in python and pushing webcam images through a socket. There just isn't great support for the JS solution rn, to the best of my understanding.

It should be fixed now for Desktop Chrome with latest push.  Try https://mediapipe.dev/demo/holistic and see if it works.
(To make sure your browser isn't caching a stale version, you can open the JS Console, check the "Disable cache" box under the "Network" tab, and then leave the JS Console open while loading the page).

Amazing! Thank you so much @tyrmullen ~~

Debería arreglarse ahora para Desktop Chrome con el último empuje. Pruebe https://mediapipe.dev/demo/holistic y vea si funciona.
(Para asegurarse de que su navegador no almacena en caché una versión obsoleta, puede abrir JS Console, marcar la casilla "Deshabilitar caché" en la pestaña "Red" y luego dejar JS Console abierta mientras carga la página).

Debería arreglarse ahora para Desktop Chrome con el último empuje. Pruebe https://mediapipe.dev/demo/holistic y vea si funciona.
(Para asegurarse de que su navegador no almacena en caché una versión obsoleta, puede abrir JS Console, marcar la casilla "Deshabilitar caché" en la pestaña "Red" y luego dejar JS Console abierta mientras carga la página).

many thanks !!!  thank you so much

@tyrmullen Again, thank you for the fast update, it definitely helps a lot. To keep it stable, I'm instantiating the Holistic constructor variable, I'm now setting it to the current version:
Holistic({
	locateFile: (file) => {
		return `https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>	}
})

That should be fine, right?
One final question for rn: As I'm perusing through the console logs and I see that it's using a discrete graphics card when possible -- is there a way to simulate running it exclusively using CPU? I'm curious to see how mileage will vary based on a client's hardware.
Thanks again!

Hi @martincho0731 , Closing it as the issue resolved. Thanks !

@afogel To answer your last question: currently that decision is baked into the MediaPipe graph, but that would be an excellent option for us to add-- especially since that should also provide a workaround for issues like #1430.


Proposal: way to omit parameters that are optional

Based on discussion in the Slack, here's the proposal:
An [OmitValueAttribute] that can take an optional token value to test against.
Example syntax would be like GetFoo([OmitValue] Bar bar) or GetFoo([OmitValue] int? num) or GetFoo([OmitValue(-1)] int num);
In these cases, the value won't be added to the query string if it matches the default (null or supplied value).

RequestBuilderImplementation currently checks for null values and omits them. Perhaps this can be tabled for now then until there's a need to send a blank/null value.


Should be able to change font on specific "Odometer" call

I want to use Odometer with specific font when I instantiate the component on the screen.

Do changing font-family with CSS will work for you?


Adding deep fetch swagger support for getUnresolvedDependencies api

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Our service is currently not in GA. We are limited to only a couple of public regions now. As we are going towards GA we are trying to make sure that the new changes are run in public regions with the preview swagger. We are making sure in our service that none of our client breaks if they use the old parameters.

Rule
Message
Explanation

❌ 1041 - AddedPropertyInResponse
The new version has a new property 'summaryCollection' in response that was not found in the old version.New: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L1651:7 Old: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L1602:7
No existing users of the api wil be impacted. We have just enhanced the response of the current api to contain new information..

❌ 1043 - AddingOptionalParameter
The optional parameter 'dependencyLevel' was added in the new version.New: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L590:11
In service we have implemented in such a way that the api will continue to work with the older parameters. So none of our clients will break.

❌ 1043 - AddingOptionalParameter
The optional parameter '$orderby' was added in the new version.New: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L605:11
In service we have implemented in such a way that the api will continue to work with the older parameters. So none of our clients will break.

❌ 1043 - AddingOptionalParameter
The optional parameter '$filter' was added in the new version.New: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L615:11
In service we have implemented in such a way that the api will continue to work with the older parameters. So none of our clients will break.

Our service is currently not in GA. We are limited to only a couple of public regions now. As we are going towards GA we are trying to make sure that the new changes are run in public regions with the preview swagger. We are making sure in our service that none of our client breaks if they use the old parameters.

Rule
Message
Explanation

❌ 1041 - AddedPropertyInResponse
The new version has a new property 'summaryCollection' in response that was not found in the old version.New: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L1651:7 Old: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L1602:7
No existing users of the api wil be impacted. We have just enhanced the response of the current api to contain new information..

❌ 1043 - AddingOptionalParameter
The optional parameter 'dependencyLevel' was added in the new version.New: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L590:11
In service we have implemented in such a way that the api will continue to work with the older parameters. So none of our clients will break.

❌ 1043 - AddingOptionalParameter
The optional parameter '$orderby' was added in the new version.New: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L605:11
In service we have implemented in such a way that the api will continue to work with the older parameters. So none of our clients will break.

❌ 1043 - AddingOptionalParameter
The optional parameter '$filter' was added in the new version.New: Microsoft.Migrate/preview/2019-10-01-preview/resourcemovercollection.json#L615:11
In service we have implemented in such a way that the api will continue to work with the older parameters.


[java] Enable tests for telemetry logs by default in Java

Motivation

Changes

Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[ ] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[ ] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

Weblogs have no internal errors by default, so we can't pass this test. Closing.


Optional hashing when creating and querying

Currently gcstool create expects sha1 hashes in the input file, and gcstool query expects raw strings that it will hash with sha1. It would be good to make hashing optional in both cases, so I could create a set with raw inputs and query it with hashes. And a selectable hashing algorithm would be a plus.

It doesn't really care what the inputs are, so long as each line starts with 16 bytes of hex, but yeah, it does need to be made more flexible and that is on the todo list.
Mainly a matter of picking an appropriate right crate.  Thinking either crypto-hash or maybe crypto-hashes for a wider range of options (and more dependencies).

New global flag added:
OPTIONS:
    -H, --hash <hash>    Hash function [default: sha1]  [possible values: hex, sha1]

Will close this once it's a bit less limited.


fix logs path for creating model

The problem is wider. log folder is the folder you enter in catalyst configuration file:
args:
  expdir: "classify/baseline/"
  logdir: "log"

I used to choose the log name. You prefer logs.
To cope with it, we need to parse Catalyst's configuration file.
I have fixed this issue here:
https://github.com/catalyst-team/mlcomp/commit/5642ae56d415cf928303a572318ff3cb5cd02cb4
mlcomp==20.2.4a is released

Yes, it works now


Nan::SetterCallback has the wrong signature.

It's either wrong in the code:
https://github.com/nodejs/nan/blob/505803bbd83dbd43c06e179b78b690e52e17d317/nan_callbacks.h#L22
or in the docs (under Example):
https://github.com/nodejs/nan/blob/master/doc/methods.md#api_nan_setter
Going by the v8 docs on Accessors, it seems like it's wrong in the code, ie. third parameter should be const PropertyCallbackInfo<v8::Value>& instead of const PropertyCallbackInfo<void>&.

No, it is correct.
On October 4, 2015 12:56:40 AM GMT+02:00, 2Pacalypse-<EMAIL_ADDRESS>wrote:

It's either wrong in the code:
https://github.com/nodejs/nan/blob/505803bbd83dbd43c06e179b78b690e52e17d317/nan_callbacks.h#L22
or in the docs (under Example):
https://github.com/nodejs/nan/blob/master/doc/methods.md#api_nan_setter
Going by the v8 docs on
Accessors, it seems
like it's wrong in the code, ie. third parameter should be const PropertyCallbackInfo<v8::Value>& instead of const PropertyCallbackInfo<void>&.

Reply to this email directly or view it on GitHub:
https://github.com/nodejs/nan/issues/482

Is it wrong in the docs (under Example) then?

Ah, now I see what you mean (easier from a desktop browser). It's the example in the documentation that is wrong.

Thank you for confirming. Took me longer than I'd like to admit debugging before I noticed it either.
If you don't mind me asking, why exactly is void used there instead of v8::Value anyway?

Because a setter, as accessor, does not return a value. Named and indexed property interceptor setters, return a value, because the specification says so (probably). It is customary to return the value that was passed in, as this is how it works (automatically) in JavaScript.

Thanks, that makes sense.


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit a804ee8:
:clock10: Pending: waiting for processors (27 builds ahead of you)
:warning: Docs Build is busy, currently there are 27 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit a804ee8:
:clock10: Full build: the average full build time is 5 min(s) 8 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit a804ee8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-conceptual/testing.md
:warning:Warning
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)
Details

docs-ref-conceptual/testing.md

[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.
[Warning] Missing attribute: either ms.prod or ms.service is required. Use ms.prod for on-premise products, or ms.service for cloud services.
[Warning] Missing attribute: title.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Missing feature: tree loads

Although the TreeLoad class exists in the file loads.py, I am still unable to instantiate a tree load because it is still an abstract class (see below). Will the tree load feature be added soon? Thanks in advance.
TypeError: Can't instantiate abstract class TreeLoad with abstract method to_internal_datastructure

Should be fixed in version v1.1.0, you can now use DStabilityModel.add_load to add it to the loads.
You may also use the more manual way and add instances of PersistableTree to DStabilityModel.datastructure.loads[0].Trees

Thank you for the quick update! It works as expected now.


Add ability to add link to link

Not only messages can be controversial, but also links themselves can be controversial, so ability to add links to links is necessary.


Add documentation in codegen::Dimension

This patch simply adds some documentation to the codegen::Dimension
definitions with the result of me trying to understand what is going on
here, which might be useful to future readers of the code.

What I meant here is: I tried to understand what is going on, and the result (= what I understood) is written done in the documentation.  Agreed it could be more clear; will rephrase.


Shortcut function

This is mostly a question: would you consider adding shortcut functions to the library @Goldziher?
Background
I run into this pattern a lot. I have a mock like this:
mock = mocker.patch.object(my_object, 'my_method', AsyncMock(return_value=...))

and realize I can use pydantic-factories to provide the return data (yay 🎉 )
My issue is that the declaration needed to create a one-off model here is a little bit much for the scenarios where I just want valid data (I'm not testing inputs, I'm testing unrelated behavior, and just need valid filler). To make this work, I currently have to do this:
class MyMockModel(ModelFactory):
    __model__ = MyModel

mock_data = MyMockModel().build().dict()
mock = mocker.patch.object(my_object, 'my_method', AsyncMock(return_value=mock_data))

Suggestion
Could it make sense to provide a shortcut function for these cases, where we simply do something like this?
mock_data = default_factory(MyModel).build().dict()
mock = mocker.patch.object(my_object, 'my_method', AsyncMock(return_value=mock_data))

Haven't thought about the naming or implementation - wanted to hear your thoughts first 🙂 Happy to help implement this if it seems reasonable.

I'll start using something like this in my own project and see what it feels like:
T = TypeVar('T', bound=ModelFactory)

def default_factory(model: type[T]) -> ModelFactory[type[T]]:
    class ShortcutModel(ModelFactory):
        __model__ = model

    return ShortcutModel()

so there is already a method - which isn't documented in the readme at present, but is used internally and is meant for subclassing etc. Its- ModelFactory.create_factory().
It does exactly what you want and a bit more, the signature for this is:
def create_factory(cls, model: Type[BaseModel], base: Optional["ModelFactory"], **kwargs) -> Type["ModelFactory"]

model is a subclass of the pydantic BaseModel, base is an optional factory class to use as a base, other than ModelFactory which is the default, and the **kwargs you can pass are the class variables used by the factory (and any other property you like, since it will be set on the new class), see: https://github.com/Goldziher/pydantic-factories/blob/main/pydantic_factories/factory.py#L345
It would be cool if you could add a section regarding this in the documentation.

@sondrelg should i close this issue or do you intend to act on this?

I might re-open a PR after some more experimentation, but generally I'd say this has been less of an issue than I thought it might be 👍


MSID: 91010 Version: 2 DOI: 10.1101/2<IP_ADDRESS>3034

MSID: 91010
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>3034
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=91010
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>3034

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/91010v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>3034
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/91010/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Nicely spotted @rkcook312. I've uploaded a corrected package to s3://prod-elife-epp-meca/91010-v2-meca.zip. Should be loaded to EPP in a few hours.


Don't destroy lock before unlocking

It may happen that the GRPC_LB_POLICY_WEAK_UNREF triggers the destruction of the glb_policy, which hosts the mutex wrapped around the glb_rr_connectivity_changed function. In that case, the unlock operation will be referrencing freed memory.
This change saves a copy of the potentially disappearing policy to be unref'd outside the lock.

The changes/fix in this PR are now part of #8787. Closing.

That being said, if you'd rather have the fix on its own PR (which may be a good idea) let me know and I'll recreate it by splitting if off #8787.

Resurrecting this PR. This should be a change on its own.

Equivalent changes went in as part of #8787


FLEX-4126 ~ Consolidates OSLP 0.5.1 and 0.6.1 documentation.

Deprecates OSLP 0.5.1 after removing the protocol-adapter component.

All is well.

All is well.

All is well.


Access Denied error corrected for child processes

2018-05-10 10:01:31,502: INFO: proc(54): run_and_log_output: Output: quit:
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Parent Process 3796
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Creating dump for 3796
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Child Process 2052
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Creating dump for 2052
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Not able to create Dump for process 2052 [Error 5] Acceso denegado
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Child Process 884
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Creating dump for 884
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Not able to create Dump for process 884 [Error 5] Acceso denegado
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Child Process 500
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Creating dump for 500
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Not able to create Dump for process 500 [Error 5] Acceso denegado
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Child Process 2744
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Creating dump for 2744
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: Not able to create Dump for process 2744 [Error 5] Acceso denegado
2018-05-10 10:01:31,517: INFO: proc(54): run_and_log_output: Output: total elapsed time 0:00:02.077000

i was able to repro this bug locally and this PR fixes it and makes it more robust

@DrewScoggins @danmosemsft

LGTM


doc: show example of updating multiple values

This is #456 rebased and fixed

I took the commit message from #456, can change it if you want

No, it's fine :)


Use markdown files saved in git instead of wiki

Resolves #1.

@AntoineDao, thanks for this - it triggered us into moving things forward 😉
We've moved the delivered documents (WIP stuff will remain in wiki until in a more polished form) to /docs, and, furthermore, published a website from it using jekyll.
🙇


PeriodicBatchingSink Duplicates Messages on Failure

The current implementation uses Serilog's PeriodicBatchingSink. It is set up to receive a message batch, loop the collection, sending each message as a separate HTTP request (a Slack limitation, the API only allows one message).
This isn't a good use case for PeriodicBatchingSink, because if we have a batch of 10 messages, and HTTP request 9 out of 10 is throttled by Slack and fails, the batching sink will retry the entire batch. This will duplicate messages 1 - 8 until all requests for the batch succeed.
What the sink really needs to do is post one at a time, in a way Serilog can retry. Needs some investigation - maybe we can just set the batch size to 1?

We are using PeriodicBatchSink only to work with rate limits (https://api.slack.com/docs/rate-limits) - maybe its time to queue messages on our own (we just need to stick to 1msg/s rate limit) ?

Possibly, but the beauty of using PeriodicBatchingSink is that it handles all of the async/await + queueing for you. I am leaning towards just using a batch size of 1 so retry can't possibly duplicate messages, but it needs some testing :)

yeah, you are 100% right - what the heck I was thinking 🤔😉

Ha ha! Better to re-use :)
So looking at the code again ( https://github.com/serilog/serilog-sinks-periodicbatching/blob/dev/src/Serilog.Sinks.PeriodicBatching/Sinks/PeriodicBatching/PeriodicBatchingSink.cs#L53-L54 ) I think this will work... setting the batch size to 1 and the period to 1 second. No duplication on request errors and doesn't exceed Slack's limits.
Need to test it though, if a lot is being logged to Slack it's going to back up. My use case for this Sink is to log anything above a certain level. I doubt anyone will use it to log at the Verbose level to Slack, so volume-wise it might work out OK.
It's a bit of an abuse of the PeriodicBatchSink because there is no batch, but I am not sure if the regular Serilog Sink class does any retrying at all. Will check the docs when I get a moment!

So I was wondering - maybe its a https://github.com/serilog/serilog-sinks-periodicbatching issue (the way it tries to retry) ?

It's working as intended, if there is an exception thrown from the EmitBatch method Serilog will retry. It's useful when you are using it to submit a batch in one shot, which it is designed for, but won't work if you are making multiple requests in a tight loop: https://github.com/serilog/serilog/wiki/Reliability#asynchronousbatched-network-operations

Yeah, but they are retrying whole batch even though only one message failed. I'm good with previous solution though :)

It's designed to make only one HTTP request per batch though, not many 😄  So this is a little outside of the use case for the periodic batching sink, but I think we can make it work.


Add cities_light loading to docker installation instructions

Was trying to get a docker instance up and running, and followed the docker installation instructions.  However, mozillians requires you to update the superuser profile you create in order to start using the app.  To do this, you need the country/region/city data loaded in the DB or it won't allow the user to advance through.  This update to the document is an attempt to make it so that others don't get hung up on this.

Coverage decreased (-0.4%) to 89.39% when pulling 19b62fb76421bbcbceea38fa67e186fe2f4794db on claudijd:add_cities_loading into df1fe3b0e79cc1da2a4e81289e8558f0351df0c2 on mozilla:master.

Thanks for the PR @claudijd
r+ :rocket:


[nrfconnect] Added resolvable private address for BLE device

Problem
According to test event 1 test plan, CHIP device should use new address on each successfull or unsuccessfull commissioning
attempt.
Summary of Changes

Added configs enabling BT_PRIVACY
Added generating BLE resolvable private address instead of static one.

Fixes #5425 for nrfconnect

add label TE1 to this PR.

Why resolvable private address? Resolvable private addresses imply use of LE security and bonding to make sense of them. Why not use Static Random address like the spec specifies:

To ensure privacy, the BLE controller SHALL use LE Random Device Address. A commissionable CHIP device shall change its Advertising Address on every successful or unsuccessful commissioning attempt or on an announcement timeout (see Announcement Duration).

Why resolvable private address?

I felt like using private address is basically to hide device identity and prevent from tracking, so to ensure privacy. If it comes to the static random addresses I saw use cases describing it as rather good for assigning random address on boot, but not to change it at runtime multiple times. So basing on that and the fact that according to spec address should be random (it does not clearly say about private or static) I figured out that private will be more relevant.

NOTE: CP done but it was not clean (additional change on advertiser flags)


feat: support keepalive socket config

It can not test keepalive behavior in our existing test workflow, All options have been to pass on to openresty TCP  socket, So it seems there is not need to test it.


Update DRED document with links.

@ChuckM-Intel : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@stevewhims : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Update style of sign transaction buttons

Before:

After

I'm not a designer, but I still think that will be more intuitive than before.
closes #494

Hi @gbaranski, thanks for the contribution!
Could you share a bit about your use case, as well as the problem you're trying to solve?
Specifically, I'm not sure there's a clear hierarchy among these three actions. As I see it, it all depends on what you're using the lab for. But I'd love to understand your rationale here.
Thanks! :)

Hello, the problem is those buttons color, every is made as a primary, especially the most misleading is Sign with BIP Path, and not only i encountered this problem when I was clicking this button instead of submit transaction.
Also i did a mistake, those two buttons next to submit in my opinion should be outlined.
A layout should contain a single prominent button that makes it clear that other buttons have less importance in the hierarchy. This high-emphasis button commands the most attention.

Source: https://material.io/components/buttons
Thanks for response

Thanks! I understand your solution from a technical perspective, but what is the usability problem you're aiming to fix? Is it the fact that it's not obvious which buttons you should click on a happy path? Or is the problem that some clicks are optional, and that is not clear in the UI?

Also: what task were you trying to accomplish when you faced these issues?

@accordeiro That happens when I am signing transaction, and every time I press Sign with BIP Path i need to reload website, because it won't pass me with wrong Ledger Wallet input.
Actually, I think that submit buttons should always be with the highest emphasis. And yes, I think that may be also because some buttons are optional, like "View in XDR Viewer, Sign with BIP Path, Wrap with Fee bump" but in UI you see them as something most important.

Are there any updates about this PR?

Sorry for the late reply. I like your rationale, but I'm not sure about introducing a new button color. Maybe instead we could leave the "secondary" buttons as outlined buttons, the same way you did with the "Sign with BIP"? @vcarl @quietbits would love your thoughts here too.
As for the code: could you figure out the correct components / styles to update, so that we don't have to rely on !important overrides? This blog post explains well the rationale for avoiding them.

Closing this PR for no activity.


Generated report does not adhere to spec

After running the gitlab reporter there are not results shown; reason being the report does not adhere to the spec (https://github.com/codeclimate/platform/blob/master/spec/analyzers/SPEC.md#data-types).
Only part of the spec is filled in
Example result
[
    {
        "description": "x:183 - Unexpected indentation (20) (should be 16) (Rule: standard:indent)",
        "severity": "major",
        "location": {
            "path": "x",
            "lines": {
                "begin": 183
            }
        }
    }
]

Missing fields
type, check_name and categories.
Proposal
type should always be issue
categories can always be Style.
check_name could be the rule name that was violated (e.g. standard:indent)

Hi there,
The check_name field seems to be a (more or less) new requirement. type and categories do not need to be set for GitLab CLI (see GitLab CLI Custom Tools). I will also add those, as it still works if they are present. Thanks for the heads up.

Yes, that is added in the pull request as well.

No problem, I'm happy to help. Please let me know if it works once you've tried it.


⚠ Bofrost.at has degraded performance

In b0d6f5a, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1442 ms

Resolved: Bofrost.at performance has improved in 8b67f34.


[CORE] AQE cannot coalesce partitions when Exchange hash partitioning exists non-attribute expressions

Backend
CH (ClickHouse)
Bug description

A pre-project operator is added before the exchange operator when hash partitioning involves non-attribute expressions, which results in that AQE cannot coalesce shuffle partitions.
Spark version
None
Spark configurations
No response
System information
No response
Relevant logs
No response

@rui-mo mo @zzcclp Should we extend the substait pb to support expression in exchange operator?

@exmy Thanks for noticing this issue. Could you explain a bit how large this issue will affect the performance?

cc @PHILO-HE

@exmy Thanks for noticing this issue. Could you explain a bit how large this issue will affect the performance?

We've recently noticed that this issue will also prevent AQE's OptimizeSkewedJoin rule from being effective, and it has a significant impact on performance.
If OptimizeSkewedJoin disabled due to this issue:

If OptimizeSkewedJoin enabled:

@rui-mo

@exmy Thanks for the profiling. On which query can we reproduce the performance result? Does that mean we shouldn't add extra project before exchange?

@exmy Thanks for the profiling. On which query can we reproduce the performance result? Does that mean we shouldn't add extra project before exchange?

Sorry, this issue is specific to the CH backend. It's not present in the Velox backend.

Sorry, this issue is specific to the CH backend. It's not present in the Velox backend.

@exmy Thanks for your work. Velox backend also inserts a Project transformer before exchange if the hash keys are expressions. I assume similar issue also occurs for Velox backend, right?

@exmy Thanks for your work. Velox backend also inserts a Project transformer before exchange if the hash keys are expressions. I assume similar issue also occurs for Velox backend, right? cc @PHILO-HE

Velox backend doesn't has this issue. Because it adds pre-project to calculate hash value but doesn't change shuffle hash expressions in ShuffleExchange operator. I have tested it. @rui-mo

@exmy Thanks for checking!


Guide on creating a resource

@lwjohnst86 If you want to take this back, you are welcome to do so 👍


Snippets menu: differentiate between workspace and user snippets

In this example I have two snippet files called react: one is from my workspace and one is for my user (global). In the menu it's impossible to know which one is which. I would like to suggest adding a label to differentiate between workspace and user snippets.

Idea: when having two same names add details/description with the whole path

I've found that add whole path inside the description will make it longer and harder to read. We might also be able to add their types in, which would be more intuitive

and we can also add only the second item to the description in case of duplicate names, it can serve as a differentiator, and the code is relatively simple

This bug has been fixed in the latest release of VS Code Insiders!
@OliverJAsh, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version f1b09237cd400d92987cf7a9681995e8011ef54c of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!


Refactor StaticAnalyses on its own module

Codecov Report

Merging #258 (2466036) into main (521701b) will decrease coverage by 0.09%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #258      +/-   ##
==========================================
- Coverage   85.52%   85.43%   -0.09%
==========================================
  Files          40       40
  Lines        1333     1332       -1
==========================================
- Hits         1140     1138       -2
- Misses        193      194       +1

Impacted Files
Coverage Δ

src/ONSAS.jl
100.00% <ø> (ø)

src/StructuralAnalyses/StructuralAnalyses.jl
78.26% <ø> (-0.47%)
:arrow_down:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Notes on the unsafe keyword

https://github.com/brson/wasm-opt-rs/blob/aad563327f248190a17ad48de8e0a3f667b76597/notes.md#L721-L723
I think this is not the right mental model. The unsafe keyword means the programmer who is writing all those function signatures inside the extern block is on the hook for the unsafe responsibility of which ones to declare as fn vs unsafe fn according to their C++ semantics. In the extern block shown, the programmer has decided all these functions behave in a way that is safe to call from Rust. If there were no functions in the block that were made safe to call from Rust, the unsafe on the extern block would not be needed because there isn't anything the programmer is vouching for in that case.

I have reworded this.


Dvc yaml support - Autocomplete + Snippets

What's done:
Params suggestions and Vars
What's left:
Suggest folders and files
Maybe more snippets
Fix bugs

We also need to parse TOML and .py files for parameters

@wolmir can you please either close this or pull out the snippets so we can review and merge.


how to monitor the grpc request in springboot project

plugins can't package in apm-agent-attach way
https://www.elastic.co/guide/en/apm/agent/java/master/setup-attach-api.html

Hi,
I'm not sure to properly understand your request, can you elaborate a bit ?
We've added grpc recently, it should be available in our next release: https://github.com/elastic/apm-agent-java/pull/1019
Generally speaking, we prefer to discuss this kind of topic directly in our forum : discuss.elastic.co, as we try to keep github issues for actionable tasks. As a result this issue will very likely get closed.

ok, thanks for your answer


Support flashing from Windows

As learned from #60 (again)
Currently Windows users are somewhat "left out in the cold" and passing USB through VMs, etc is a mess.
We should create a Powershell or similar script so Windows users can flash a willow-dist.bin from the build process using esptool natively within Windows.

Hey - Using my normal account now....   Will we assume that the user has a willow-dist.bin on their local Window system to start?  This shoud be an easy script to create, happy to look at it.

That's what I'm thinking! Definitely bail if the file can't be found but other than that should be fairly straightforward?
In the main project (in the container) we could also start (with an explicit command) a tiny HTTP server or something and fetch willow-dist.bin from there whenever it's invoked. That way people are always flashing the last dist file if they do subsequent builds.

I like the HTTP server idea - makes sense, and then the user doesnt need to worry about copying it to the right location / etc...
I just wrote up a quick PS script that downloads Python 3.7 and installs it to c:\willow  (Thought it would be easier to put it here to keep track of things)
Then pip deploys esptools
The esptools flashes the firmware.
I need to test on a new Windows system though, my normal laptop has too many apps deployed and paths / etc ...  so I want to make sure it works on a different Windows system.
I can add the download of the firmware from the container - Is the thought that they would have the container running on their Windows system in Docker Desktop?   Im not sure if the current continer exposes 80 (guessing it doesnt yet?) - but if we do that, it woud be easy to add one line to the script to download the firmware to c:\willow
Last thing is the serial port - I can query and assum the first found port has the ESP on it  or just ask the user for the COMx port when they start the script.

Wow, thanks a lot! That was quick!
Can Docker Desktop on Windows run Linux containers? Sorry for the ignorance, I've been almost exclusively a Linux/Mac user for many years now. Given these issues, etc we will make sure to get some Windows installs going so we can support Windows ourselves.
I would think that the usual EXPOSE/-p args to Docker would work but there are all kinds of other issues that could be introduced with this approach.
COM port - almost forgot! I assume ACM devices are standard COM ports in Windows? If so, that's probably a safe assumption these days.

@ssurovich not sure if you saw the commit but we should be ready on the HTTP server side

Excellent... I didn't see that, been a busy Saturday  - I'll take a look tonight and add the download portion.  Should have it all done and fully tested tomorrow.

No worries! Just wanted to @ you to make sure you saw it so we can keep moving this forward.
Thanks again!

Absolutely- I appreciate the nudge, I would have missed it, no doubt.
I'm happy to help out - this has so much potential in my opinion.  I showed my wife the speed last night and she was impressed.  Of course her first question was about asking non HA intents, I told her it's just a start.  She wants me to integrate it with ChatGPT and have all voice prompts / information read back.  It's all there, just need some time....

Thanks! We're a little obsessed with speed (with quality, of course) so we appreciate that!
While ChatGPT integration is of course possible via any number of ways the Willow Inference Server supports self-hosted LLMs natively. It does 4 bit quantization of any LLaMa based model (currently) and I've personally had good experiences with Vicuna 13B. Total VRAM usage ends up around 18GB so all-in so higher end GPU for sure in terms of self-hosting.
We're still working out the flow but the idea is to support pipelining natively in WIS so:
Willow speech input -> STT -> LLM -> TTS -> Willow playback
With pipelining in WIS the only missing piece there is the Willow playback component but fundamentally it's easy enough. We're just very deliberate about things.
Regarding HA intents, given that Willow (either in local or WIS mode) is so capable we plan on creating a repo of HA intents that dramatically add to what HA supports natively.

That's awesome to hear - very exciting, brings me back to when I was writing my own home assistant long before HA or vendor solutions using Microsoft Kinects - the mics were great and the IR camera was good for occupancy detection.   With your work, I'm more excited than I was back then :)  I'm around for any testing or potential work, just beginning another book (Kubernetes) that will take a lot of time, but there's always time for the fun stuff in between that and my real paying job

Hah, I have a Kinect in my hardware pile as well!
We're happy to have you help out!

Wow, thanks a lot! That was quick!
Can Docker Desktop on Windows run Linux containers? Sorry for the ignorance, I've been almost exclusively a Linux/Mac user for many years now. Given these issues, etc we will make sure to get some Windows installs going so we can support Windows ourselves.
I would think that the usual EXPOSE/-p args to Docker would work but there are all kinds of other issues that could be introduced with this approach.
Sorry quick edit - worst case scenario we could leave it up to the user to get willow-dist.bin to their Windows machine somehow, possible with a command line argument to the PS script to skip HTTP?
COM port - almost forgot! I assume ACM devices are standard COM ports in Windows? If so, that's probably a safe assumption these days.

Yep - It can run Linux containers -great thing about Docker Desktop on Windows.
On Windows the COM will be different for most people, Mine was COM8 but thats because I flash a lot of ESP devices and some were in still in the registry as a port, so 8 was next.
I think we can take two ways - Ill get the final script running without HTTP download - just for people who may have a firmware.  Ill update it to a Docker support script for people who may want to build it on Windows and then just download the FW usinf HTTP.
I think the options would be good for people.

QQ - Did you want me to do a PR or did you want me to just send the Powershell script over with the short readme with the steps.  Im doing a final test now but it should have all checks to make it fairly easy for people to execute.   It will error out if the folder I need isnt created and it will also fail if willow-dist.bin isnt in that folder.  I cant verify the COM port right now, getting ports isnt too bad in Powershell, but verifying which one has the ESP attached is a bit tricky.  So right now, the need to manually supply the COM port (found by looking at device manager).

If you could do a PR with the Powershell script under misc/ that would be great! On any host platform getting the device port to flash is something that can be done programmatically but I'm always weary of cases like this where you're operating in unknown environments with any number of variables that can't possibly be accounted for. For the time being I'd like to stick with users having to explicitly define the flash/serial monitor port.
Speaking of device serial monitor - do you have a suggested terminal implementation? Last time I was on Windows Putty seemed like a fairly standard approach people used but it's been many years and I'm not sure if that's still viable/ideal. Ideally it could use the same approach we have today where define the port for flash and monitor once.

Cool - Ill do a PR today.   Ive tested the script a number of times and its working great.  I had a failure during one flash, it got to around 45% and timed out, but rerunning the script flashed it successfully.
Putty would be a good solution, I do still use that alot for both SSH and for a Serial Console.   Could add that to the script as we continue to add features to it?

I think it would be ok if we even fetch Putty like we do Python as long as we "install" in our own directory. I use install in quotes because from what I remember Putty is just a binary without installation. If Putty can take the already user-specified port (and our baud rate) as command line arguments that would be even better.

Yep, its a single binary, so I could download it to the c:\willow directory and using the COM port value the script asks for to flash, start a session with that COM port for the serial console.
The container side is a bit more work.  Nothing too difficult, but will take more time that just the flashing script.  I dont want to do the installation for Docker in a script, I would rather leave that to the user so we dont stomp on anything or upgrade something that could cause other issues.
I'll check out your utils.sh and look at the steps you're doing and just make that work in Windows with a script, adding a final step of copying the willow-dist.bin file into the c:\willow folder.

I think thats perfect - exposing the container on the web port is all we need (and of couse, a web sever with the just the willow-dist.bin FW).   Ill do a simple download using the port and that should be it - Nice and simple...

I hope Docker Desktop on Windows supports opening and exposing ports but it's so common I would have to imagine it does.
Note that like all variables defined at the top of utils they can be overridden via .env in the root dir but yes, the powershell script so match the current default of 10000.

I was debating some WSL steps, but I wanted to keep it simple for people that may not know about WSL / etc...  Its also one reason I wanted to create an easy flash in Powershell - easy for most Windows users.  At one point, I assume Willow will have a more generic firmware image available and we will be able to include it to allow most Windows users to just run the script and flash.

Do we have something ready I can test from my Windows box? I've been attempting with a docker image on Ubuntu but can't seem to get the docker image to start so a Windows port would be great. I am well versed in POSH. If it runs into any issues I can debug.

Correct me if I'm wrong. Within Ubuntu we are merging the software and our configuration settings onto a bin file? Once this is created esptools can flash?
I got the configuration menu to start, then I was away for a week. Now I can't find any evidence of an output.   :(
Love to try efforts of ssurovich

No, things have progressed. Since I know nothing of Ubuntu but by the power of Youtube I successfully completed the build.  Per the read.me instructions, I stopped at the PORT assignment assuming WLS2 is an issue. I'm running Ubuntu within my windows machine. What is the name of the flash bin file? Am I looking for willow-dist.bin? I searched and I don't have one.
Once I know I have the right .bin I'll try ESPtools of Windows first.

So if you want to get your file, inside the willow docker (run ./utils.sh docker from the directory you have willow cloned), then when inside the container you run ./utils.sh serve, it will make a small http server you can access anywhere on your network to download the distro bin:

Note mine is running on port 20000 as I am running this in the same docker network as my WIS instance and the default port 10000 conflicts with my installation. By default it would host on port 10000.  That then runs the willow docker container; you will notice your shell change to something like "root@ea3457bn#". At that point you are inside the willow docker container. Once inside there you would then run the ./utils.sh serve command. 😃

Gotcha! Went to http://[YOUR HOST IP]:10000 trying WSL & host IPv4 addresses without success. Suggestions?

It's possible WSL is blocking access to the port, I don't think by default it opens up the firewall. I had an issue with something like this before in the past and it was quite a pain to get around from what I recall :(

doesn't the WSL get its own IP?  on Ubuntu if you do a ip addr, what do you get?  (I haven't used wsl in a while)
You could try to connect the ip returned from that command

No silly questions for Ubuntu day two...
From IPCONFIG: result two addresses  one for my network and another for WSL adapter. both were tried...
Yes, 'Your host' was replaced with the actual IP

If I do ip addr, I assume I will have to exit the container and that will end the http server session?

Yeah, but you can just start it up again. Also gets a bit confusing because the container will have a docker address that would be bound to a bridge network, and that bridge in turn would be bound to the physical address of the docker host machine. So really, you'd need to know what the WSL host's IP address is I believe.

WSL keeps running in the background, as long as you don't stop it (from a prompt using wsl)
I can test something when i get home - my memory just isn't cooperating right now :)

I'm a little embarrassed, I wondered why on earth would anyone create a http server instead of a file output? So I searched for willow-dist.bin from windows and shockingly it was there.

Yeah, that also works 😆 the WSL filesystem is exposed to windows, so you can browse into it. Guess that is the simpler solution!

I'm a little embarrassed, I wondered why on earth would anyone create a http server instead of a file output? So I searched for willow-dist.bin from windows and shockingly it was there.

Excellent - so you found the image?

Yes!

With minor modifications (docker args) in utils.sh I built the firmware in Docker for windows. I got the firmware locally from the mounted willow directory. Then I successfully flashed the device via web flasher. If this is of interest, I can make a request later.

I just want to thank everybody who provided assistance so I could flash my first device especially since a flash tool is in the works. I was delayed by an unannounced 1300 mile road trip. I was eager to get back and try my bin file. Using procedure Flash successful, on to Home Assistant!

Closing as we now offer https://flash.heywillow.io/.


Detailed Setup for App Registration Endpoint Version 2

I followed the steps in the link below:
https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-protect-backend-with-aad
How to setup for the steps below? Please provide detailed steps.

If you use v2 endpoints, use the scope you created for the backend-app
in the Default scope field. Also, make sure to set the value for the
accessTokenAcceptedVersion property to 2 in your application manifest.
https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-protect-backend-with-aad#enable-oauth-20-user-authorization-in-the-developer-console

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 823eb96f-e5f1-0832-b175-0b31009be92f
Version Independent ID: 330085ae-dcf6-e930-86a8-0e4a60ab1314
Content: Protect API backend in API Management using OAuth 2.0 and Azure AD - Azure API Management
Content Source: articles/api-management/api-management-howto-protect-backend-with-aad.md
Service: api-management
GitHub Login: @miaojiang
Microsoft Alias: apimpm

@PingPongSet  Thanks for the question! We are investigating and will update you shortly.

@PingPongSet The Application Manifest is part of the App Registration in Azure AD and the doc linked covers the steps needed to configure it.

@PingPongSet Just following up here... Hope my previous comment clears things up.
Since there is no doc update required here, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Gauge Visual studio plugin executing scenario in alphabetically instead of scenario sequence.

Gauge VisualStudio Plugin running spec scenario alphabetically.
Expected behavior
When running specific spec from plugin then it should run spec in scenario order
Actual behavior
running scenario alphabetically.
Gauge version
Gauve - 0.9.1
Visual Studio Plugin version : 0.3 (Latest)

This issue was moved to getgauge/gauge-visualstudio#202


Error when scanning artifacts : Unable to validate information for artifact ID#336, Invalid artifact gear slot, Invalid artifact set name

Current Behavior
Hello,
When I scan my artifacts with Inventory Kamera, I am getting those errors: Unable to validate information for artifact ID#336, Invalid artifact gear slot, Invalid artifact set name.
And I get a 1ko JSON file in the export folder.
Thank you for your help
Expected Behavior
The scanner to correctly exports the data
Reproducing a Behavior
I opened Genshin Impact menu (Esc) after putting the game in 1600 900 resolution.
Then press on Scan Genshin
The image below represents the result that I got when I waited for the app to finish scanning

Device OS
Windows 10
Genshin Impact Version
3.7
Inventory Kamera Version
1.3.8
Screen resolution, screen mode, and UI scale
1600x900, window, I did not modified the UI scale (I do not know how to do it)
Additional notes and remarks
No response
Evidence
This is a part of the logs
Unable to validate information for artifact ID#333
Invalid artifact gear slot
Invalid artifact set name
Artifact ID: 333
Slot: fleurdelavie
Set:
Rarity: 5
Level: 12
Main Stat: hp_
Substat 1: hp_ + 5,3%
Substat 2: def + 19
Locked: True
Unable to validate information for artifact ID#334
Invalid artifact gear slot
Invalid artifact set name
Artifact ID: 334
Slot: fleurdelavie
Set:
Rarity: 5
Level: 12
Main Stat: hp_
Substat 1: atk + 16
Substat 2: atk_ + 15,2%
Locked: True
Unable to validate information for artifact ID#335
Invalid artifact set name
Artifact ID: 335
Slot: plume
Set:
Rarity: 5
Level: 12
Main Stat: atk
Substat 1: def_ + 10,9%
Locked: True
Unable to validate information for artifact ID#336
Invalid artifact gear slot
Invalid artifact set name
Artifact ID: 336
Slot: diadémedelogos
Set:
Rarity: 5
Level: 12
Main Stat:
Substat 2: def_ + 13,1%
Substat 3: atk_ + 8,7%
Substat 4: hp + 478
Locked: True
Unable to validate information for artifact ID#337
Invalid artifact gear slot
Invalid artifact set name
Artifact ID: 337
Slot: fleurdelavie
Set:
Rarity: 5
Level: 12
Main Stat: hp_
Substat 1: atk + 14
Substat 2: atk_ + 12,8%
Locked: True
Unable to validate information for artifact ID#338
Invalid artifact gear slot
Invalid artifact set name
Artifact ID: 338
Slot: sablesdutemps
Set:
Rarity: 5
Level: 12
Main Stat:
Substat 2: atk_ + 4,7%
Substat 4: hp + 717
Locked: True
Unable to validate information for artifact ID#339
Invalid artifact gear slot
Invalid artifact set name
Artifact ID: 339
Slot: diadémedelogos
Set:
Rarity: 5
Level: 12
Main Stat:
Substat 2: atk + 29
Substat 3: def + 37
Substat 4: def_ + 7,3%
Locked: True
Preflight Checklist

[X] I have checked for similar issues in the issue page, and I have not found any similar to mine.
[X] I am using the latest version of the scanner.
[ ] I tried setting the scanning delay to maximum, and it still doesn't work.
[ ] I have attached the video recording to the bug report.
[ ] I have attached the error log to the bug report.
[ ] I am available to later explains the issue.
[X] I have disabled all screen filtering software or plugins (i.e. HDR, Image Sharpening) while scanning.
[X] I use default in-game keybindings or have configured keybindings for the scanner.

The game must be in English


editor.formatOnSave set to True format badly "git merged files"

VS Code version
13.61.2
Extension version
v2021.10.1365161279
OS type
Linux
OS version
Container "FROM python:3.7"
Python distribution
Operating system
Python version
3.7.9
Language server
Pylance
Expected behaviour
Nothing shoud be formated on those git merge files. So vscode can handle these specific lines to provide features as accept... or compare...
accept current change | accept incoming change | accept both changes | compare changes
<<<<<<< HEAD
# current change
=======
# incoming change
>>>>>>> develop

Actual behaviour
But the <<<<<<< & ======= & >>>>>>> are formatted and vscode does no more recognize these lines...
<< << << < HEAD
# current change
== == == =
# incoming change
>>>>>> > develop

Steps to reproduce

Logs
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Currently in the extension we don't really filter formatting based on the contents of the file. This would be a new thing where we gate formatting on specific patterns. Hence turning this to a feature request.
Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

Thank you for submitting your feature request and everyone who considered it! Unfortunately this issue did not receive enough votes over the allotted time, and so we are closing the issue.


Fixed a spelling typo in background-runner.md

Thanks for the PR, but the plugins docs are fetched from the published plugin README.
The problem was in the plugin definitions, I've fixed it there and when merged and released will be fixed
https://github.com/ionic-team/capacitor-background-runner/pull/95


Use HandTracking and MultiHandTracking with files

Can i use this project without webcam? Input from files and output in files?

Yes, those desktop examples do support video-in-video-out workflow. You need to add --input_video_path and --otuput_video_path to the command. For example, to run multi hand tracking cpu demo with files, you need to do
GLOG_logtostderr=1 bazel-bin/mediapipe/examples/desktop/multi_hand_tracking/multi_hand_tracking_cpu --calculator_graph_config_file=mediapipe/graphs/hand_tracking/multi_hand_tracking_desktop_live.pbtxt --input_video_path=/path/to/input.mp4 --output_video_path=/path/to/ioutput.mp4