Speed up AttributesModified outdatedness rule

This speeds up AttributesModified by not repeating the same check in the case of items with multiple reps.
Example on nanoc.ws:
       Nanoc::Int::OutdatednessRules::AttributesModified#apply │   91    273   25.0%

Hit rate of 25% which isn’t too high, but it is useful.

Patch coverage check fails because of an unreachable code patch which deliberately raises an exception.


Focus change causes traceback

From<EMAIL_ADDRESS>on 2009-09-02T00:36:40Z
What steps will reproduce the problem?

Loose conection with volume that contains an active file
klick on the file in the editor.
Traceback produced What is the expected output? What do you see instead? IOexception should probably be caught.

the output:
>>> Traceback (most recent call last):

File "C:\Python26\lib\site-packages\spyderlib\plugins\editor.py", line 378,
in focus_changed
    self.refresh()

File "C:\Python26\lib\site-packages\spyderlib\plugins\editor.py", line 454,
in refresh
    self.__check_last_modified(index)

File "C:\Python26\lib\site-packages\spyderlib\plugins\editor.py", line 435,
in __check_last_modified
    self.reload(index)

File "C:\Python26\lib\site-packages\spyderlib\plugins\editor.py", line 517,
in reload
    txt, finfo.encoding = encoding.read(finfo.filename)
  File
"C:\Python26\lib\site-packages\spyderlib\encoding.py", line 169, in read

text, encoding = decode( file(filename, 'rb').read() )
IOError: [Errno 2]
No such file or directory: u'E:\henriksdal-3D-test.py' What version of the product are you using? On what operating system? python(x,y) 2.6.0 beta 3 on XP
Please provide any additional information below
. This is not a showstopper but it should be an easy fix. It is getting
harder and harder to find those little bugs but I am still trying. =)
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=21

From pierre.raybaut on 2009-09-03T14:09:58Z
fixed in v1.0.0beta6
Keep trying :)
Status: Fixed

From pierre.raybaut on 2009-09-02T05:46:52Z
Status: Accepted


Fix el7 package suffix

Fix el7 package suffix
Update icinga2 version

@vkhatri can you look at this?


UTC TimeZone instead of LA TimeZone?

Update to UTC TimeZone it is a universal timezone used in most games with an in-game clock, It is Easier to plan events around as everyone can convert UTC to their timezone more easily.

Pacific time is the timezone that was used in the original game


Quantbook.GetFundamental Accepts Multiple Selectors

Expected Behavior
Be able to request more than one fundamental property by GetFundamental call.
Actual Behavior
We can only request one property. If we want multiple properties we need to call this method multiple times and it's inefficient.
Potential Solution
N/A
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

Completed by https://github.com/QuantConnect/Lean/pull/5743


Add support for building ARM64, as well as proper project dependencies.

@manodasanW it appears I don't have permission to push to this branch; are you able to grant me permission, or do you want to pick up my changes separately somehow?


Deploy the 2.x Javadoc

Have to wait for central's search to index it before we can do this.

Done


chore(dialog): add generic param for config data

Adds a generic parameter to the MatDialogConfig that indicates the type of its data.
BREAKING CHANGE: Material now requires at least TypeScript 2.4.
Fixes #4398.

We may use 2.4, but I don't think we ever officially said that we require greater than that. Can you add a BREAKING CHANGE message for that?

Updated.

According to this comment, the core team recommends the use of<EMAIL_ADDRESS><2.4.0' for Angular 4x. Also, you get a warning in a CLI project if you try to use typescript greater than 2.4.


Avoid deep_copy or initializing

A lot of these are stylistic (allocate without initializing + deep copy instead of just initializing) so I am happy to disregard it if someone feels strongly about it. For me, this looks cleaner.

gpg: keyserver receive failed: Cannot assign requested address

gpg: keyserver receive failed: Cannot assign requested address

These happen occasionally.  Reviewer's judgement to ignore or re-run.


Substitute cosmwasm-template with cw-template on cosmwasm-plus branch

Misunderstood, this is not wanted


Support AnyScale

Thanks. My only concern is on dotenv. What is its purpose here?

It loads .env file at working directory, just make debug easier.

Can we keep things simple and unique by only loading configurations from environmental variables?

I strongly prefer to use OS environment variable. It can be saved in files too and can be reactivated via source. My motive is to follow the convention in major GenAI APIs that the keys are stored in OS environment variables.
Keeping one way is better than having multiple ways.

The huggingface inference now is supported in this PR, can you check it @forrestbao? Thank you so much.


feat: add options to disable or change selection debounce time

new settings

vscode-neovim.normalSelectionDebounceTime
vscode-neovim.mouseSelectionDebounceTime

Resolve: #1475

@xiyaowong out of curiosity, does disabling the mouse also disable cursor move on mouse click? I have a feeling that might still be nice to have even if selections don't enter visual mode.

I did a simple test at that time and didn’t find any issues.

To avoid the need for 2 options this could instead be a factor or multiple, like 1x/1.5x/2x/3x. Or from a user's perspective it could be a "dial" or slider, i.e. a range from 1 to 100. Which then would be converted by vscode-neovim to appropriate values internally. No need for users to tweak the exact millisecond values.

These two options are completely unrelated.

At present, I tend to solve the problem now and improve the document later.

There is now a limited range of values for these two options.

How are they unrelated? They both control the sync window between client/server. The fact that they control different internals is an implementation detail. When would a user adjust one of these values but not the other?

About normal selection: #1403, #1409
About mouse selection: #1475
The current values range and the candidates are both good. Most users don’t even need to change them, but if they do, they will naturally discover these configuration options. Like VSCode, it has a lot of hidden configurations.


Add missing doc.evaluate arguments for Firefox

Firefox complains about the two last arguments that were missing.
If that still causes issues later I'll suggest to switch to an alternative parsing method.
Let's see how it goes.
@evert

Interesting. We really need to get those unittests in place I suppose :/


Add camera functionality to web application

Adds another option to accept webcam input from user. While webcam is running, image upload is disabled until the user decides to take a picture

note my suggested updates in the camera branch

Continuing work on the upstream/camera branch


npm run build fails after the latest update

I'm using this package in a project and that runs autodeployment using travis to gh-pages branch, just recently after these updates the project fails to compile as shown below, what do I do to get things right? Add @material-ui/core as a dependency to the project? Any help would be appreciated. Thanks :smile:

Please read the changelog.
It was a major version bump because there were breaking changes, i.e. Material-UI was updated to version 1.0.0. If you're using an older version, don't update to v2.0.0 and you'll be fine. You should update to Material-UI 1.0.0 though, but that requires a bit of work.

@leMaik Okay thanks.


fix typo

Signed-off-by: xiekeyang<EMAIL_ADDRESS>

How is this a typo? markdown allows for intermixing html like this.

How is this a typo? markdown allows for intermixing html like this.
Seems it doesn't.
it shows on page as,   `application/vnd.oci.image.layer.tar+gzip`
We want like,  application/vnd.oci.image.layer.tar+gzip

On Sun, Sep 11, 2016 at 08:58:16PM -0700, Brandon Philips wrote:

How is this a typo? markdown allows for intermixing html like this.

There are some rules about inline Markdown inside HTML not being
supported.  I haven't dug up a refernce in the Markdown spec, but you
can see the backtics not being converted to code tags in master 1.
So +1 for b0edca4b (although a more specific commit summary would be
nice ;).

Update commit summary.

lgtm

LGTM


[💡 Feature]: DOC - How to build a core widget

Is your feature request related to a problem?
No problem, we have documentation of intergrating marquee with external VS Code Extensions, but no core widget documentation in terms of making our own.
Describe the solution you'd like.
Adds a section on the marquee docs on how to build a core widget -

Documentation for team and other devs that want to add to the core widgets of marquee.
A list of steps to create core widget / simplification of getting a core widget started.

Describe alternatives you've considered.
No response
Additional context
No response
Code of Conduct

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

@lorenzejay added a section to the CONTRIBUTING.md, please let me know if it all makes sense.

@lorenzejay added a section to the CONTRIBUTING.md, please let me know if it all makes sense.

Going to take a look.

added a bit more specifics on the structure but lmkwyt - https://github.com/stateful/vscode-marquee/pull/199

Thanks for the suggestions, merged!


copr: construct Column from ChunkedVec without copying

What problem does this PR solve?
Problem Summary:
We can now construct some types of Column directly from VectorValue (ChunkedVec) without overhead of copy.
What is changed and how it works?
Proposal: RFC: Using chunk format in coprocessor framework
Related Issue: #7724
What's Changed:

encode_chunk now requires ownership.
split from_vector_value of Column to from_vector_value and from_vector_value_slowpath.
Json and Bytes now supports direct copy construct
add tests for fast path conversion.

TODO

Fixed size types need to be refactored to use Vec<u8> inside. Therefore, we do not introduce fast path copy for them in this PR.

Check List
Tests

Unit test

PTAL, Thanks! @breeswish @TennyZhuang

/run-all-tests

I'll turn this PR into draft as more time is required to tackle the underlying issue.

/run-all-tests

 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.

 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.


after deleting a deployed solution the page needs to update automatically

Description
after deleting a deployed solution (from the VDC dashboard -> deployed solution page) the page not refreshed automatically to reflect the changes that just happened to the deployed solutions list. the changes show after the user refreshes the page manually.
Implementation
the page needs to update the list automatically after the solution deleted successfully, a good example is to replicate the behavior when the user deletes a VDC, the page refreshes automatically.

Close this issue as it is been verified before, update dashboard was needed to reflect the fix.


fix #989 - custom dns resolving

fix #989

bors r+

bors r+

This is blocked by #947 since this is now failing tests :(

superseded by #1011


Multiple images with different animation

I have 2 different images, I need the first image to move up and the other one to move down, is there a way I can assign a "move" object with all of its options to each image?

Hi @thegodliek,
Yes it's possible, I created a pen here
https://codepen.io/matteobruni/pen/MWymBxX
In short, you need this configuration:
shape: {
    type: "image",
    options: {
        image: [
            {
                src: "https://particles.matteobruni.it/images/fruits/apple.png",
                width: 32, // this width is used only for image ratio
                height: 32, // this height is used only for image ratio
                particles: { /* here you can specify all the particles options you want */
                    move: {
                        direction: "top"
                    }
                }
            },
            {
                src: "https://particles.matteobruni.it/images/fruits/avocado.png",
                width: 32, // this width is used only for image ratio
                height: 32, // this height is used only for image ratio
                particles: { /* here you can specify all the particles options you want */
                    move: {
                        direction: "bottom"
                    }
                }
            }
        ]
    }
}

Thank you for the response, it's what I was looking for, but in your example, the apple.png image is set to move to top, but some of them are moving down!
Is there anyway to fix that?

Yes I noticed that and I'm currently investigating

tsParticles v1.17.10 is coming out in few minutes with the bug fix

Thank you very much! The issue is now fixed.


No Icon font named '(null)'

When I run the example project included with the repository everything works fine, but when I try to use the library with my own projects, I keep getting No Icon font named '(null)'. I believe that it is an issue with how the font files are being loaded, but I can't be 100% sure on that.

Can you post the code you're trying to use? I think its an issue with how
its being declared.
Thanks,
Cory Smith
http://ca.linkedin.com/in/corysmith/
http:/twitter.com/smixx http://twitter.com/smixx
On Wed, Oct 21, 2015 at 8:11 AM, jneumann<EMAIL_ADDRESS>wrote:

When I run the example project included with the repository everything
works fine, but when I try to use the library with my own projects, I keep
getting No Icon font named '(null)'. I believe that it is an issue with how
the font files are being loaded, but I can't be 100% sure on that.
[image: screen shot 2015-10-21 at 9 00 30 am]
https://cloud.githubusercontent.com/assets/4145595/10639039/a2f48d76-77d3-11e5-865d-f01d3ff831a6.png
—
Reply to this email directly or view it on GitHub
https://github.com/corymsmith/react-native-icons/issues/122.

https://gist.github.com/jneumann/f9c483b9fccc4d9dd44e

You're missing:
iconName={'ion|ios-paper-outline'}
iconSize={32}
You can also specify the following if the icon is different when selected
vs. just being tinted a different color:
selectedIconName={'ion|ios-paper'}
Thanks,
Cory Smith
http://ca.linkedin.com/in/corysmith/
http:/twitter.com/smixx http://twitter.com/smixx
On Wed, Oct 21, 2015 at 9:21 AM, jneumann<EMAIL_ADDRESS>wrote:

https://gist.github.com/jneumann/f9c483b9fccc4d9dd44e
—
Reply to this email directly or view it on GitHub
https://github.com/corymsmith/react-native-icons/issues/122#issuecomment-149930190
.

@jneumann any luck?

That fixed it for me, thank you for your help!


⚠ Bofrost.de has degraded performance

In 7534b93, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1550 ms

Resolved: Bofrost.de performance has improved in 8eb143a.


[BUG] 'mask' not found when dataset type is "video_json"

https://github.com/alibaba/animate-anything/blob/d33431693eb4a76e854c5e6ef65cdea4598db448/utils/dataset.py#L616
example['mask'] ?

    if self.return_mask:
        mask = get_moved_area_mask(video.permute([0,2,3,1]).numpy())
        example['mask'] = mask

I modified the code like this, and the program runs successfully

Thanks. I have fixed it.


Skipping docker build for UI

I'm trying to run Hygieia via Docker-Compose on my mac.
I seem to have made it through the api portion of the install alright, but when I try to build the UI container mvn goes through its tasks, and seems to move along fine until it hits the docker build task
This leads me to believe that npm, bower and gulp do their thing, not seeing any errors there. So why is the docker build being skipped? I'm not getting any errors reported here either.
JohnDoes-MacBook-Pro:hygieia johndoe$ mvn clean package -pl UI docker:build
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building com.capitalone.dashboard:UI 2.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ UI ---
[INFO]
[INFO] >>> maven-pmd-plugin:3.5:check (default) > :pmd @ UI >>>
[INFO]
[INFO] --- maven-pmd-plugin:3.5:pmd (pmd) @ UI ---
[INFO]
[INFO] <<< maven-pmd-plugin:3.5:check (default) < :pmd @ UI <<<
[INFO]
[INFO] --- maven-pmd-plugin:3.5:check (default) @ UI ---
[INFO]
[INFO] --- frontend-maven-plugin:0.0.27:install-node-and-npm (install node and npm) @ UI ---
[INFO] Found proxies: []
[INFO] Node v5.4.1 is already installed.
[INFO] Found NPM version 2.14.15
[INFO]
[INFO] --- frontend-maven-plugin:0.0.27:npm (npm install) @ UI ---
[INFO] Found proxies: []
[INFO] Running 'npm install --color=false' in /Users/johndoe/somedir/hygieia/UI
[INFO]
[INFO] --- frontend-maven-plugin:0.0.27:bower (bower install) @ UI ---
[INFO] Found proxies: []
[INFO] Running 'bower install' in /Users/johndoe/somedir/hygieia/UI
[INFO]
[INFO] --- frontend-maven-plugin:0.0.27:gulp (gulp build) @ UI ---
[INFO] Running 'gulp.js build --no-color' in /Users/johndoe/somedir/hygieia/UI
[INFO] [11:41:45] Using gulpfile ~/somedir/hygieia/UI/gulpfile.js
[INFO] [11:41:45] Starting 'build'...
[INFO] [11:41:45] Starting 'clean'...
[INFO] [11:41:45] Finished 'clean' after 75 ms
[INFO] [11:41:45] Starting 'assets'...
[INFO] [11:41:45] Starting 'themes'...
[INFO] [11:41:45] Starting 'fonts'...
[INFO] [11:41:45] Starting 'js'...
[INFO] [11:41:45] Starting 'views'...
[INFO] [11:41:45] Starting 'test-data'...

[INFO] [11:41:52] gulp-inject 1 files into index.html.
[INFO] [11:41:52] gulp-inject 89 files into index.html.
[INFO] [11:41:52] Finished 'html' after 185 ms
[INFO] [11:41:52] Finished 'build' after 7.73 s
[INFO]
[INFO] --- docker-maven-plugin:0.3.3:build (default-cli) @ UI ---
[INFO] Skipping docker build
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 25.425 s
[INFO] Finished at: 2016-02-22T11:41:54-06:00
[INFO] Final Memory: 34M/333M
[INFO] ------------------------------------------------------------------------
JohnDoes-MacBook-Pro:hygieia johndoe$

I am taking a look at this...
On Feb 22, 2016, at 9:52 AM, Jeremy Plack <notifications<EMAIL_ADDRESS>wrote:
I'm trying to run Hygieia via Docker-Compose on my mac.
I seem to have made it through the api portion of the install alright, but when I try to build the UI container mvn goes through its tasks, and seems to move along fine until it hits the docker build task
This leads me to believe that npm, bower and gulp do their thing, not seeing any errors there. So why is the docker build being skipped? I'm not getting any errors reported here either.
JohnDoes-MacBook-Pro:hygieia johndoe$ mvn clean package -pl UI docker:build
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building com.capitalone.dashboard:UI 2.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ UI ---
[INFO]
[INFO] >>> maven-pmd-plugin:3.5:check (default) > :pmd @ UI >>>
[INFO]
[INFO] --- maven-pmd-plugin:3.5:pmd (pmd) @ UI ---
[INFO]
[INFO] <<< maven-pmd-plugin:3.5:check (default) < :pmd @ UI <<<
[INFO]
[INFO] --- maven-pmd-plugin:3.5:check (default) @ UI ---
[INFO]
[INFO] --- frontend-maven-plugin:0.0.27:install-node-and-npm (install node and npm) @ UI ---
[INFO] Found proxies: []
[INFO] Node v5.4.1 is already installed.
[INFO] Found NPM version 2.14.15
[INFO]
[INFO] --- frontend-maven-plugin:0.0.27:npm (npm install) @ UI ---
[INFO] Found proxies: []
[INFO] Running 'npm install --color=false' in /Users/johndoe/somedir/hygieia/UI
[INFO]
[INFO] --- frontend-maven-plugin:0.0.27:bower (bower install) @ UI ---
[INFO] Found proxies: []
[INFO] Running 'bower install' in /Users/johndoe/somedir/hygieia/UI
[INFO]
[INFO] --- frontend-maven-plugin:0.0.27:gulp (gulp build) @ UI ---
[INFO] Running 'gulp.js build --no-color' in /Users/johndoe/somedir/hygieia/UI
[INFO] [11:41:45] Using gulpfile ~/somedir/hygieia/UI/gulpfile.js
[INFO] [11:41:45] Starting 'build'...
[INFO] [11:41:45] Starting 'clean'...
[INFO] [11:41:45] Finished 'clean' after 75 ms
[INFO] [11:41:45] Starting 'assets'...
[INFO] [11:41:45] Starting 'themes'...
[INFO] [11:41:45] Starting 'fonts'...
[INFO] [11:41:45] Starting 'js'...
[INFO] [11:41:45] Starting 'views'...
[INFO] [11:41:45] Starting 'test-data'...

[INFO] [11:41:52] gulp-inject 1 files into index.html.
[INFO] [11:41:52] gulp-inject 89 files into index.html.
[INFO] [11:41:52] Finished 'html' after 185 ms
[INFO] [11:41:52] Finished 'build' after 7.73 s
[INFO]
[INFO] --- docker-maven-plugin:0.3.3:build (default-cli) @ UI ---
[INFO] Skipping docker build
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 25.425 s
[INFO] Finished at: 2016-02-22T11:41:54-06:00
[INFO] Final Memory: 34M/333M
[INFO] ------------------------------------------------------------------------
JohnDoes-MacBook-Pro:hygieia johndoe$
—
Reply to this email directly or view it on GitHubhttps://github.com/capitalone/Hygieia/issues/359.

@stlouisweb take a look at the commit I made on this ticket, if you pull that change it will fix your pom.xml

that was quick! I'm testing it out now. I'll let you know how it goes in a few.

it works, no more Skipping docker build

figured maybe leave this open until your change gets merged?

merged 4f20dca - (upstream/master, origin/master, origin/HEAD, master) Merge pull request #341 from jimzucker/eclipseCleanup

closed now with @jimzucker comment above.


vuid: set watchdog fd for better listen

This writes the current watchdog file descriptor to the watchdog.fd, then debugger could listen the watchdog feeding via:
$ WATCHDOG_PID=`getprop watchdog.pid`
$ WATCHDOG_FD=`getprop watchdog.fd`
$ strace -p ${WATCHDOG_PID} | grep "write(${WATCHDOG_FD}"

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added

This needs to cherry-picked to next and our v7.37.x branches if gets approved :)

Starts a complete CI on https://ci.rokid.com/view/Yodaos/job/rokid-ci-yodart-unit-tests/1397/.

Should 'state' or 'system' be prefixed to property names?

Should 'state' or 'system' be prefixed to property names?

I just keep consistent with this name above, we should apply the prefix to all in this file if this needs change.

@legendecas @FeelyChau Updated done, remove PID and add a state prefix to watchdog properties.


Map::first and Map::last methods

closes #35

Looks like the coverage check is not happy with doc-tests


STP Dashboard - Materialized statistics should count ingested infotons only

Statistic of materialized infotons gives the number of infotons which were materialized only without any count of successfully ingested infotons
The number of materialized infotons is less important because there is a need to know how much were actually ingested
We can do the following -
Change Materialized  to Ingested or
Add Ingested and failed count to the STP Dashoard

Let's get rid of the materialized stats and only keep ingested and failed values.

Implemented as attached


IntelliSense/Autocompletion is sometimes wrong

Describe the bug
In some situations, the autocompleted value is not replacing the already existing text correctly.
I assume, the hyphen in the name is the problem. And only, if the hyphen is already typed before the IntellySense kicks in.
To Reproduce
Steps to reproduce the behavior:

Enter setState('hm-rp'
With the cursor after the 'p' press CTRL+Space to activate IntelliSense
select hm-rpc and press '.' or tab
See error: setState('hm-hm-rpc'

Same for vis-hqwidgets or simple-api (start IntelliSense AFTER the hyphen was typed!).
Expected behavior
Expected behavior is setState('hm-rpc'
Screenshots

Version information (please complete the following information):

Extension version: v1.5.0
VS Code version: 1.92.1
ioBroker admin version: 7.0.22
ioBroker nodejs version: v18.20.4
ioBroker javascript adapter version: 8.7.6

I was able to reproduce the behaviour and I will try to fix it soon.


Add note to "Stream a Changefeed to Snowflake" tutorial

Add a bullet to the "Known Limitations Section" along the lines of:

Snowpipe works best with append-only workloads. Snowpipe lacks native ETL capabilities to perform updates to the data. You may need to do pre-processing of the data before uploading to Snowflake.

This is a limitation of Snowflake, and not CRDB. As a result, I'm going to leave it out of the Known Limitations proper page, and just added it to the Stream a Changefeed to Snowflake, as you suggest.


adding/fixing documentation and figures

@gwaybio This PR is ready for review!

@axiomcura @phicks22
This PR is adding more documentation to the NF1 project, specifically around the IC step.
I would like for feedback on the content and any issues within it (e.g. grammar, spelling, etc.).
No coding changed FYI

@gwaybio I have made changes to this PR using Erik's suggestions. Can you please review so we can merge? :smiley:

@gwaybio I will merge this now! Ty!


Missng parseFont typescript definition

I got an error from typescript when using parseFont with the font from importable-fonts, following the instruction from #32:
import figlet from "figlet";
import banner3 from "figlet/importable-fonts/Banner3";

figlet.parseFont("Banner3", banner3);

On the 4th line: Property 'parseFont' does not exist on type 'typeof figlet'.
More information:
os: Windows 10
node: 10.12.0
figlet: ^1.2.4
typescript: 3.5.2

This library was written in JavaScript. I’m not very familiar with TypeScript but I can add support if you know what needs to be done to resolve this.

I just realized the declaration file(index.d.ts) required by TypeScript is not included in figlet, instead it is found in @types/figlet (source: https://www.npmjs.com/package/@types/figlet) package which is updated one year ago. Perhaps this is the main reason the new parseFont method is not defined.
If the declaration file in @types/figlet is updated with the new method I think the problem will be solved :)

Sounds good, just put in an issue to get it updated. I @-ed you so you can follow it.


feat: Introduce flipt provider for dotnet

Flipt.io provider for dotnet
Initial version of flipt.io provider for dotnet.

Created a new provider for OpenFeature for flipt.io in .net

Related Issues
None
Notes

Handles most of openFeature datatypes

Follow-up Tasks

[x]  Pending unit tests for FliptProvider.cs class
[x]  Support .net 6.0, right now it only supports .net 8.0

@jeandreidc Great work! Thanks a lot. There's only 2 small things blocking my approval:

consider this comment regarding error evals
- can we build the rest client instead of committing it? If you look at the flagd provider, we generate some grpc sources as part of the build; you might be able to use similar patterns in your build steps
please add an entry for this package (and the equivalent test package) to the component_owners with yourself yourself (and potentially @markphelps ) as owners.

@beeme1mr @toddbaert is there anything else blocking this from merge?
Thanks again @jeandreidc !!

Approved, but there's an issue with the build. Feel free to ping me so I can retrigger CI once the issue has been addressed.

Yes, I thought the tests passed but apparently they hadn't started.

@jeandreidc sorry about that. Would you mind addressing the build issue in a separate pr? On the bright side, the ci should run automatically since it's no longer your first contribution 😀


Update create-a-basic-windows-10-app-in-cpp.md

\" doesn't work. " is the way to add double quote.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Thanks, I've fixed this now - the PR isn't taken as so much else changed on the page recently I didn't want to break anything. Your input is much appreciated!

\" appear several different places in the page. You may want to update those as well.


Step #5 is obsolete. There is no "OK" button on that page.

Please remove step #5 as there is no "OK" button on that page.

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

ID: e9ac0e5c-b8d2-09e8-2eeb-fa517e1d067b
Version Independent ID: a34c96e5-1726-c194-e57f-6ff54e033c6a
Content: Enable Azure Security Center for IoT service in IoT Hub Preview
Content Source: articles/asc-for-iot/quickstart-onboard-iot-hub.md
Service: ascforiot
GitHub Login: @mlottner
Microsoft Alias: mlottner

@wickste Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thanks for taking the time to provide us with valuable feedback. We've reviewed the page, found the UI updated, and modified the text with your suggestion.
Appreciate your contribution to ASC for IoT!

#please-close

Thanks!


Guidelines implementation: Construct Interface

[ ] Implement and apply rule awslint:resource-interface: All resource constructs should have a corresponding resource interface (IFoo)
[ ] Implement and apply rule awslint:ref-via-interface: All public APIs (props, methods, properties) should only use construct interfaces (IFoo)
[x] Implement and apply rule awslint:construct-interface-extends-iconstruct: IFoo must extend IConstruct (directly or indirectly)
[x] Implement and apply rule awslint:construct-base-is-private: FooBase should not be public (internal)
[ ] Implement and apply rule awslint:construct-inheritence: Restrict base classes to Resource,Construct,XxxBase to encourage composition over inheritence
[ ] Implement and apply rule awslint:config-explicit: All APIs not exposed on IFoo should have a @config annotation

Split into multiple tasks


Some question about sgd noise distribution

Hi. Formula(16) in paper note that sgd noise have Gaussian distribution like this:h(θ)~N (0, Σsgd(θ)).
Howerver.in "main.py" at line 128-130 shows like this:
parms.grad *= coeff_a
if args.modulation == 'OGM_GE':
    parms.grad += torch.zeros_like(parms.grad).normal_(0, parms.grad.std().item() + 1e-8)

after multiplying the coeff_a(or in paper is ku),the variance of parms.grad becomes ku* ku* Σsgd(θ) rather than Σsgd(θ).
So whether 'Σsgd(θ)' or 'ku* ku* Σsgd(θ)' is the right variance of noise distribution? Thanks for your reply!

Thanks for your question. If X~N(0, sigma), then kX~N(0,k^2sigma). Hence, the coeff_a is 'k', and the coefficient of 'Σsgd(θ)' is k^2.


TDI-38834:Azure Queue Name does not follow specification (even though it

appears to)
What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-38834
What is the new behavior?
Please check if the PR fulfills these requirements

[ ] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:

Pull request test result: success :star:


Create LICENSE

Thanks @hannesdelbeke , but I intentionally skipped the LICENSE file in order to constraint future additions to a single python module (the only file licensed on this repo).
Containing the project to a single file is a very important design decision to me, as I want to remove as many barrier of entry as possible for less technical people attempting to use quicklauncher, and adding anything going into a different direction needs further justification.


expand JSON test coverage

@briandealwis @loosebazooka also begin moving some utility code over from Eclipse

The PR say's it's expanding JSON test coverages but makes changes to a non-test class? Is there more going on here?

We needed MavenCoordinates for the tests, or did at one point. Now I'm not so sure. I expect there'll be some libraries for processing the metadata, though I'm still not sure which piece swill land here and which in the IDE repos.

If it's only being used for tests, can it be in the src/test/java directory instead?

reverted for now; it can come back later if needed

Pinging everyone. Are there any final blockers that prevent us from checking this in and moving forward with the rest of the google-cloud-java APIs?
We can easily add additional content later. Changing or removing existing fields should be done here if possible.
If not, it needs an approval.


no matching function for call to ‘nlohmann::basic_json<>::basic_json()’

Hi Team,
I am trying to convert json to managed object and in this regard, I am using the to_json and from_json functions provided by nlohmann/json.
When I write a sample program, I am able to see no issues with this APIs but when I integrate with the actual project, observing the below error when i call get_to with int as datatype.
no matching function for call to ‘nlohmann::basic_json<>::basic_json()’
CPP file (MTop.cpp)
void MTop::to_json(json& j, const MTop& mo)
{
    j = json{{"OClass", mOClass}};
}

void MTop::from_json(const json& j, MTop& mo)
{
    mo.mOClass = j.at("OClass").get_to< int >();   ---> This line is showing compilation error.
}

Headerfile (MTop.hpp)
#include <MObjectCls.h>
#include <nlohmann/json.hpp>
using json = nlohmann::json;

class MTop : public MObject
{
   public:

     virtual void to_json(json& j, const MTop& mo);

     virtual void from_json(const json& j, MTop& mo);

   private:

     MObjectCls mOClass;
};

Headerfile (MObjectCls.h)

class MObjectCls
{
   public:

   MObjectCls(int value);
};

Since there to_json and from_json are used by the object of this class only, these two functions are not maintained under any namespace.
if the from_json( ) logic is modified as below -
j.at("OClass").get_to(mo.mOClass);
MTop.cpp -->
error: no matching function for call to ‘nlohmann::basic_json<>::basic_json(<brace-enclosed initializer list>)’
error: no matching function for call to ‘nlohmann::basic_json<>::get_to(MObjectCls&) const’
../include/nlohmann/json.hpp:3017:28: error: no type named ‘type’ in ‘struct std::enable_if<false, int>’
../include/nlohmann/json.hpp:3030:25: error: no type named ‘type’ in ‘struct std::enable_if<false, int>’

Please guide me what could be the issue.
Note:  Since the header and cpp files are big, I have shared only the contents which are of focus here.

Deepak

The functions from_json and to_json must be defined in the same namespace as the type. They must not be member functions. Please try moving them out of MTop.

About "error: no matching function for call to ‘nlohmann::basic_json<>::get_to(MObjectCls&) const’"
You misused get_to. It should be either
int value = j.get<int>();

or
int value;
j.get_to( value );

First one in your case.

@nlohmann
Thanks for your response.
I have modified the files as below -
MTop.cpp
#include <nlohmann/json.hpp>
using json = nlohmann::json;
namespace MTop_ns
{
typedef enum
{
STATE_LOCKED = 0,
STATE_UNLOCKED = 1,
STATE_SHUTTINGDOWN = 2
} MAdminStateEnum;
NLOHMANN_JSON_SERIALIZE_ENUM ( MAdminStateEnum, {
    {STATE_LOCKED, "locked"},
    {STATE_UNLOCKED, "unlocked"},
    {STATE_SHUTTINGDOWN, "shutdown"},
});

struct MTop000
{
    int                         mOInstId;
    std::string                 mOInstName;
    MAdminStateEnum  mAdminState;
};

void to_json(json& j, const MTop000& mo)
{
    j = json{{"mOInstId", mo.mOInstId},
             {"mOInstName", mo.mOInstName},
            };
}

void from_json(const json& j, MTop000& mo)
{
    j.at("mOInstId").get_to(mo.mOInstId);
    j.at("mOInstName").get_to(mo.mOInstName);
}

}
MTop.hpp
#include <MObjectCls.h>
class MTop : public MObject
{
public:
private:
 MObjectCls mOClass;

};
Now, I don't see any compilation errors as the from_json and to_json are not part of the member functions.
I would be accessing this as below in other file -
MTop_ns::MTop000 mT = {"10, "mTopClass", STATE_LOCKED"};
json j = mT;
Since I have multiple managed objects, there will be many class files. If I had to write to_json/from_json for all those, then I need to do the same for all right ?
Is there any other way to do it ?

Deepak

Yes, you have to define it for every type. Maybe this article helps: https://json.nlohmann.me/features/arbitrary_types/#simplify-your-life-with-macros

@nlohmann
Thanks for the reference.
Looking into that, I made changes to my code and here is the change -
Headerfile (MTop.hpp)
#include <MObjectCls.h>
#include <nlohmann/json.hpp>
using json = nlohmann::json;
namespace MTop_ns
{
class MTop : public MObject
{
public:
NLOHMANN_DEFINE_TYPE_INTRUSIVE(MTop, moClass)

private:
 MObjectCls mOClass;

};
}
Headerfile (MObjectCls.h)
class MObjectCls
{
public:
MObjectCls( );
MObjectCls(int value);
virtual ~MObjectCls( );
};
WIth this, I am observing below errors -
MTop.h->
error: no match for ‘operator=’ (operand types are ‘nlohmann::basic_json<>::value_type’ {aka ‘nlohmann::basic_json<>’} and ‘const MibSccpInactivityTestTimer’)
../include/nlohmann/detail/macro_scope.hpp:268:81: error: no matching function for call to ‘nlohmann::basic_json<>::get_to(MibAdministrativeState&) const’
../include/nlohmann/json.hpp:3017:28: error: no type named ‘type’ in ‘struct std::enable_if<false, int>’
If I modify as below, then I don't see any error.
Headerfile (MTop.hpp)
#include <MObjectCls.h>
#include <nlohmann/json.hpp>
using json = nlohmann::json;
namespace MTop_ns
{
class MTop : public MObject
{
public:
NLOHMANN_DEFINE_TYPE_INTRUSIVE(MTop, moClass)

private:
 int mOClass;

};
}
This is a nested class where we need to access parameters from base class..
Should this macro be called inside all the inherited classes with the namespace ?

Deepak

Yes.

Yes.

@nlohmann
Thanks for your continuous support.
According to the document, we see that if the macro NLOHMANN_DEFINE_TYPE_INTRUSIVE is used, there is no need to define the macro within the namespace. Currently, I am following the same. Is this correct ?
NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE(name, member1, member2, ...) is to be defined inside of the namespace of the class/struct to create code for.
NLOHMANN_DEFINE_TYPE_INTRUSIVE(name, member1, member2, ...) is to be defined inside of the class/struct to create code for. This macro can also access private members.
#include <MObjectCls.h>
#include <nlohmann/json.hpp>
using json = nlohmann::json;
class MTop : public MObject
{
public:
NLOHMANN_DEFINE_TYPE_INTRUSIVE(MTop, moClass)

private:
 int mOClass;

};
MTop.h:  error: invalid use of non-static data member ‘MTop::mOClass’
../include/nlohmann/detail/macro_scope.hpp:276:130: error: ‘NLOHMANN_JSON_TO’ was not declared in this scope
Are these errors related with not using namespace ?

Deepak

@nlohmann
Thanks for your continuous support.
According to the document, we see that if the macro NLOHMANN_DEFINE_TYPE_INTRUSIVE is used, there is no need to define the macro within the namespace. Currently, I am following the same. Is this correct ?
NLOHMANN_DEFINE_TYPE_NON_INTRUSIVE(name, member1, member2, ...) is to be defined inside of the namespace of the class/struct to create code for.
NLOHMANN_DEFINE_TYPE_INTRUSIVE(name, member1, member2, ...) is to be defined inside of the class/struct to create code for. This macro can also access private members.
#include <MObjectCls.h>
#include <nlohmann/json.hpp>
using json = nlohmann::json;
class MTop : public MObject
{
public:
NLOHMANN_DEFINE_TYPE_INTRUSIVE(MTop, moClass)

private:
 int mOClass;

};
MTop.h:  error: invalid use of non-static data member ‘MTop::mOClass’
../include/nlohmann/detail/macro_scope.hpp:276:130: error: ‘NLOHMANN_JSON_TO’ was not declared in this scope
Are these errors related with not using namespace ?

Deepak

Looks like a typo. In NLOHMANN_DEFINE_TYPE_INTRUSIVE, you write moClass (lower-case o), but the member is called mOClass (upper-case O).

Looks like a typo. In NLOHMANN_DEFINE_TYPE_INTRUSIVE, you write moClass (lower-case o), but the member is called mOClass (upper-case O).

@nlohmann
My apology.  The code which was pasted had this typo error.
In the code what is being used, the variable passed is mOClass only.
NLOHMANN_DEFINE_TYPE_INTRUSIVE(MTop, mOClass)
Need your inputs on my below query -
According to the document, we see that if the macro NLOHMANN_DEFINE_TYPE_INTRUSIVE is used, there is no need to define the macro within the namespace. Currently, I am following the same. Is this correct ?

Deepak

@nlohmann
My apology.  The code which was pasted had this typo error.
In the code what is being used, the variable passed is mOClass only.
NLOHMANN_DEFINE_TYPE_INTRUSIVE(MTop, mOClass)
Need your inputs on my below query -
According to the document, we see that if the macro NLOHMANN_DEFINE_TYPE_INTRUSIVE is used, there is no need to define the macro within the namespace. Currently, I am following the same. Is this correct ?

Deepak

What compiler are you using?  Looks like there's a problem with the macro expansion.

What compiler are you using?  Looks like there's a problem with the macro expansion.

Can you try replacing that macro with this?
friend void to_json(nlohmann::json& nlohmann_json_j, const Type& nlohmann_json_t) {
    NLOHMANN_JSON_TO(mOClass)
}
friend void from_json(const nlohmann::json& nlohmann_json_j, Type& nlohmann_json_t) {
    NLOHMANN_JSON_FROM(mOClass)
}

If that doesn't work, then try this:
friend void to_json(nlohmann::json& nlohmann_json_j, const Type& nlohmann_json_t) {
    nlohmann_json_j["mOClass"] = nlohmann_json_t.mOClass;
}
friend void from_json(const nlohmann::json& nlohmann_json_j, Type& nlohmann_json_t) {
    nlohmann_json_j.at("mOClass").get_to(nlohmann_json_t.mOClass);
}

This will at least narrow down the failure.

Can you try replacing that macro with this?
friend void to_json(nlohmann::json& nlohmann_json_j, const Type& nlohmann_json_t) {
    NLOHMANN_JSON_TO(mOClass)
}
friend void from_json(const nlohmann::json& nlohmann_json_j, Type& nlohmann_json_t) {
    NLOHMANN_JSON_FROM(mOClass)
}

If that doesn't work, then try this:
friend void to_json(nlohmann::json& nlohmann_json_j, const Type& nlohmann_json_t) {
    nlohmann_json_j["mOClass"] = nlohmann_json_t.mOClass;
}
friend void from_json(const nlohmann::json& nlohmann_json_j, Type& nlohmann_json_t) {
    nlohmann_json_j.at("mOClass").get_to(nlohmann_json_t.mOClass);
}

This will at least narrow down the failure.

@gregmarr
Thanks for your inputs.
Will modify as suggested and check.

Deepak

@gregmarr
Thanks for your inputs.
Will modify as suggested and check.

Deepak

@gregmarr
Forgot to share the compiler details.
I am using WSL2 (running Ubuntu 20.4)
$ gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ uname -a
Linux IN-9KHT253 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

@gregmarr
Forgot to share the compiler details.
I am using WSL2 (running Ubuntu 20.4)
$ gcc --version
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ uname -a
Linux IN-9KHT253 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

@gregmarr
I tried your suggestion but end up getting different error
#include <MObjectCls.h>
#include <nlohmann/json.hpp>
using json = nlohmann::json;
class MTop : public MObject
{
public:
friend void to_json(nlohmann::json& nlohmann_json_j, const Type& nlohmann_json_t) {
           nlohmann_json_j["mOClass"] = nlohmann_json_t.mOClass;
}
friend void from_json(const nlohmann::json& nlohmann_json_j, Type& nlohmann_json_t) {
           nlohmann_json_j.at("mOClass").get_to(nlohmann_json_t.mOClass);
}

private:
 int mOClass;

};
Below error is observed -
error: ‘Type’ does not name a type
error: ‘Type’ has not been declared
mOClass is integer.  Its Unsigned integer. It should be supported by JSON API right ?

Deepak

@gregmarr
I tried your suggestion but end up getting different error
#include <MObjectCls.h>
#include <nlohmann/json.hpp>
using json = nlohmann::json;
class MTop : public MObject
{
public:
friend void to_json(nlohmann::json& nlohmann_json_j, const Type& nlohmann_json_t) {
           nlohmann_json_j["mOClass"] = nlohmann_json_t.mOClass;
}
friend void from_json(const nlohmann::json& nlohmann_json_j, Type& nlohmann_json_t) {
           nlohmann_json_j.at("mOClass").get_to(nlohmann_json_t.mOClass);
}

private:
 int mOClass;

};
Below error is observed -
error: ‘Type’ does not name a type
error: ‘Type’ has not been declared
mOClass is integer.  Its Unsigned integer. It should be supported by JSON API right ?

Deepak

Right, I forgot to mention to change Type to the type of mOClass.

Right, I forgot to mention to change Type to the type of mOClass.

@gregmarr
Thanks for the clarification.
This resolved the compilation error.. Hopefully, I should be able to integrate successfully.
Thanks for your support.

@gregmarr
Thanks for the clarification.
This resolved the compilation error.. Hopefully, I should be able to integrate successfully.
Thanks for your support.


Automatically chunk other in GroupBy binary ops.

[x] Closes #7683
[x] Tests added
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst

+      4.44±0.2ms       66.4±0.4ms    14.93  groupby.GroupByDask.time_binary_op_1d
+      9.03±0.2ms       44.3±0.6ms     4.91  groupby.GroupByDask.time_binary_op_2d

Well this was a big regression for the tiny benchmark problem. I still think it's a good idea given https://discourse.pangeo.io/t/xarray-unable-to-allocate-memory-how-to-size-up-problem/3233/1

Hmm yeah I agree that scalability seems more important. Also I missed that this PR doesn't have a whatsnew entry - we should probably add one to help flag the regression.


Add the spec file to podman

Taking the fedora spec file and adding it to the git repo
for copr
Signed-off-by: baude<EMAIL_ADDRESS>

bot, retest this please

@rh-atomic-bot r+

manually adding. homu is tied up and these files dont impact the podman code.


Hebrew traslation

related issue #535

Translations need to be done in poeditor https://poeditor.com/join/project/2oWfdaZQZj

For adding your language talk to @micheljung


Accept DOI as an entry point in the release/update form

We can do that with a lookup from the list end point (/dois)

@tloubrieu-jpl
Looks like the response for searching for a DOI by DOI or LIDVID are different in that the DOI response does not include the XML record field.
For example getting by LIDVID: http://localhost:8085/PDS_APIs/pds_doi_api/0.1/dois/100%3A%3A1.0
Returns this:
{
  "creation_date": "2021-01-11T00:00:00Z",
  "doi": "10.17189/29052",
  "lidvid": "100::1.0",
  "node": "eng",
  "record": "<?xml version='1.0' encoding='UTF-8'?>\n<records><record status=\"Reserved\" index=\"1\">\n    <id>29052</id>\n    <site_code>NASA-PDS</site_code>\n    <title>Laboratory Shocked Feldspars Collection #1</title>\n    <sponsoring_organization>National Aeronautics and Space Administration (NASA)</sponsoring_organization>\n    <accession_number>100::1.0</accession_number>\n    <doi>10.17189/29052</doi>\n    <publisher>NASA Planetary Data System</publisher>\n    <publication_date>2020-03-11</publication_date>\n    <site_url>N/A</site_url>\n    <product_type>Collection</product_type>\n    <product_type_specific>PDS4 Collection</product_type_specific>\n    <date_record_added>2021-01-11</date_record_added>\n    <date_record_updated>2021-01-11</date_record_updated>\n    <keywords>PDS; PDS4;</keywords>\n    <authors>\n      <author>\n        <first_name>J. R.</first_name>\n        <last_name>Johnson</last_name>\n        <affiliations/>\n      </author>\n    </authors>\n    <contributors>\n      <contributor>\n        <full_name>Planetary Data System: Engineering Node</full_name>\n        <contributor_type>DataCurator</contributor_type>\n        <affiliations/>\n      </contributor>\n    </contributors>\n    <related_identifiers/>\n  </record>\n</records>\n",
  "status": "Reserved",
  "submitter"<EMAIL_ADDRESS>  "update_date": "2021-01-11T00:00:00Z"
}

But when getting by DOI: http://localhost:8085/PDS_APIs/pds_doi_api/0.1/dois?doi=10.17189%2F29052
Returns this:
[
  {
    "doi": "10.17189/29052",
    "lidvid": "100::1.0",
    "node": "eng",
    "status": "Reserved",
    "submitter"<EMAIL_ADDRESS>    "update_date": "2021-01-11T09:52:33.656643+08:00"
  }
]

This doesn't include the record. Will this be added later?

Hi @eddiesarevalo
The reason why it is different is that when you do a search (2nd case), you get a summary of the record with only a few field. When you get the full document (1rst case), you get all the fields, and especially the xml record.
So if you need the full record from the doi, you need to do 2 requests: 1) search/lookup to get the lidvid 2) get the full document from the lidvid
Does that make sense ? if not we can discuss with @collinss-jpl to update that, but I think that should be ok for now.

@tloubrieu-jpl That is what I was thinking as well, I just wanted to make sure that you are ok with making two calls instead of one. I'll use this method.


GUID generation for dynamic fragments (#320)

Add information on GUID generation based on terminal#10374 and improve wording to make the importance of a profile GUID clearer.
Additionally, I removed some trailing whitespace.
I believe that the section "How to determine the GUID of an existing profile" is still incomplete, though.
@DHowett provided instructions for how to generate a GUID for an existing dynamic fragment that was provided along with Git for Windows and presumably installed into %ProgramData%\Microsoft\Windows Terminal\Fragments\Git\git-bash.json:

import uuid

# CALCULATE NAMESPACE BASED ON FRAGMENT FOLDER NAME
u = uuid.uuid5(uuid.UUID("{f65ddb7e-706b-4499-8a50-40313caf510a}"), "Git".encode("UTF-16LE").decode("ASCII"))

# CALCULATE FINAL BASED ON NAMESPACE
uuid.uuid5(u, "Git Bash".encode("UTF-16LE").decode("ASCII"))

# For Git/Git Bash: UUID('2ece5bfe-50ed-5f3a-ab87-5cd4baafed2b')

Note the UUID f65ddb7e-706b-4499-8a50-40313caf510a in there – I have no idea where this particular UUID comes from (the Windows Terminal namespace G/UUID is 2BDE4A90-D05F-401C-9492-E40884EAD1D8). Using that one instead will result in a different GUID for Git Bash as profile name.

Docs Build status updates of commit 747c79f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/json-fragment-extensions.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Right, so that GUID comes from here:
https://github.com/microsoft/terminal/blob/a766798fb829a9e6f91706e919b71feabcb9b35e/src/cascadia/TerminalSettingsModel/Profile.h#L72

AH, and the guid 2BDE4A90-D05F-401C-9492-E40884EAD1D8 is for profiles that were generated by Windows Terminal itself. This is to disambiguate profiles we create (visual studio, powershell 7, ...) from profiles created by plugins or fragments so they can never accidentally collide. :smile:

Docs Build status updates of commit 526e8da:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/json-fragment-extensions.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@cinnamon-msft, @DHowett thank you for your feedback. I updated the pull request based on your comments and added a few additional sentences explaining the different namespace GUIDs. Please let me know if there's anything else you'd like changed.
Based on that feedback I also took the liberty of exchanging the "Ubuntu" GUID – I am wondering whether it'd be better to use "Git Bash" example verbatim, though? The "Ubuntu" example is probably derived from the WSL-autogenerated profile?

The "Ubuntu" example is probably derived from the WSL-autogenerated profile?

AH! You're totally right. Yes, using the Git Bash example would be perfect.

Docs Build status updates of commit a0212a5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/json-fragment-extensions.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

The "Ubuntu" example is probably derived from the WSL-autogenerated profile?

AH! You're totally right. Yes, using the Git Bash example would be perfect.

I updated the pull request based on that. If there are any other changes you'd like me to make, please let me know.


Revert one timer after the first

I'm sorry to fire an issue for a problem that maybe it is only due to me not understanding how xidlehook operates, if it's not a real issue you can classify as a documentation request.
I'm using xidlehook to lock my screen (it's not the only use of course, but probably the main one as you know), and until now I was using really the same example written in the README.
Now I would like to try dim the screen after locking, waiting another while, and I added a timer. But as for the first time I want the restore the brightness of the screen if an activity is detected, so I replicated the first timer in the example, namely:
  `# Dim the screen after 60 seconds, undim if user becomes active` \
  --timer 60 \
    'xrandr --output "$PRIMARY_DISPLAY" --brightness .1' \
    'xrandr --output "$PRIMARY_DISPLAY" --brightness 1' \

The problem is that when he tries to restore brightness seems to step back at the beginning, retrying also to lock the screen, that is already locked.
How can I avoid this? Is it possible to put the xidlehook 'position' after the second timer (the locking one) instead of restarting from the beginning?

Could you post your entire xidlehook script?  Yeah, unfortunately I'm not sure how I'd solve this. Is there a good way to detect if a thing is locked? Maybe some lockers could be supported by having it rely on the blocking of each lockscreen (like slock doesn't return until you've unlocked it)...
I guess you could already use xidlehook-client to disable the first few timers as your locker script, and re-enable them after your lock command has returned. Like
  `# Undim & lock after 10 more seconds` \
  --timer $TIME_LOCK \
    'xrandr --output "$PRIMARY_DISPLAY" --brightness 1; ./my-locker.sh' \
    '' \

where my-locker.sh is something like the following:
xidlehook-client control --timer 0 1 --action disable

eval $LOCKER  # assuming the locker doesn't return until it's unlocked

xidlehook-client control --timer 0 1 --action enable

First of all thank you very much for your support!
Second: before considering which implementation is the best let's just be sure about the problem. My desired behavior is:

it dims after $TIME_DIM seconds, but if I am active again it restores full luminosity
then it locks after $TIME_LOCK seconds and restores full luminosity
(up to this step everything it's working great)
the new one: then it dims again the screen if I'm still idle, but if I am active again it restores luminosity, but still being locked
independently of what has happened before, after passing $TIME_SUSPEND seconds more from the last interaction it will suspend

Consider that if I unlock I would like everything to be reset and start again from the beginning.
This is what I would like to obtain, and it's almost what I already have (thanks to your xidlehook), but the problem it's when I try to revert the second dimming action, and it is trying to dim again.
Instead if I would do as you suggest everything probably will work as before (depending on locker capabilities) but disabling the timer it would not dim again nor suspend this time, and in order to do this I would need to launch a second instance of xidlehook.

Instead if I would do as you suggest everything probably will work as before (depending on locker capabilities) but disabling the timer it would not dim again nor suspend this time, and in order to do this I would need to launch a second instance of xidlehook.

It should, the idea was to disable the 2 first timers (dim + lock) and only run dim + suspend until you unlock

Ok sorry, now I've understood the role of --timer option, my bad.
Still the main issue was the dependency on locker behaviour, and this prevents me to adopt the proposed solution (thanks the same for your effort!).

Oh, so there's nothing xidlehook could do regardless, I think? You might need to check the docs for whatever your $LOCKER is set to, and try to hook it up to re-enable things after unlocking there

Ok, thank you very much. I will search a little bit more. I will close this issue, but we can still reopen if ever someone will find something interesting.


Create data integrity test checking the synapse information

Online at WormAtlas is the NeuronConnect.xls spreadsheet (sec 2.1).  Let's create a unit test that compares the connectivity within PyOpenWorm to what is in that spreadsheet.  We are modifying the import function to draw directly from this spreadsheet; so it should match.  Nonetheless, this will guarantee there have been no modeling issues or retrieval issues with this connectivity pattern.

Closed by #89 !! :)


Export to 3D Model

Does there exist a feature to export a generated mesh to an stl or obj model?
I have used your excellent library to make visualizations for my math courses.
I was hoping to make some 3D models of platonic solids and curved surfaces on a 3D printer. Although, there are existing models on the internet, I was hoping to add labels to the faces, which would be quite tedious in modeling software. I wrote a Rust program that calculates the vertices and embosses a number into each face.
The shape that I'm turning into a triangle mesh.

Do you have a suggestion for how I could go about exporting a mesh file from an object in three-d? I'm not much of a programmer, so any and all help would be greatly appreciated.
Thank you so much

Thanks for the kind words 🙏  Exporting 3D models was actually one of the ideas for three-d-asset, but unfortunately, it's not supported yet (see https://github.com/asny/three-d-asset/issues/43). However, the if you only need vertices, normals and indices, it should be fairly simple to export using for example stl_io.


Client ntlm auth

patch for #2084 to allow a NTCredentials instance to be used for proxy auth. I've also updated the doco, however my ServiceUnavailableRetryStrategy is somewhat unreliable at my work, sometimes it works, sometimes it doesnt

Coverage increased (+0.04%) to 84.972% when pulling 58cab888b15e5ffe2fcf7230d53681317f50f933 on stringy05:client_ntlm_auth into 591af0ef8cd71d7d428cfb6cfc1d476e326bb28f on dropwizard:master.

Coverage increased (+0.04%) to 84.972% when pulling 14507d538769936e4706ae94a02600e33b2360d3 on stringy05:client_ntlm_auth into 591af0ef8cd71d7d428cfb6cfc1d476e326bb28f on dropwizard:master.

Thank you for an awesome pull request 🎉
Something that isn't obvious to me is how ServiceUnavailableRetryStrategy is related to NTLM authentication. If not required, it may be prudent to break that into another PR so those changes can be more easily digested and reviewed.

It's not directly related so I will put it into a second PR. Basically I
was trying to use the Retry Strategy to inject a NTLM token when a 407 is
received from the Proxy. I'd added it to the docs, however took it out as
It works but is pretty unreliable
On 28 June 2017 at 23:11, Nick Babcock<EMAIL_ADDRESS>wrote:

Thank you for an awesome pull request 🎉
Something that isn't obvious to me is how ServiceUnavailableRetryStrategy
is related to NTLM authentication. If not required, it may be prudent to
break that into another PR so those changes can be more easily digested and
reviewed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dropwizard/dropwizard/pull/2091#issuecomment-311655352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGqxwHDecRI8KPdW9-Ll2uhPbND2U7Wcks5sIlENgaJpZM4OHdDx
.

Coverage increased (+0.03%) to 84.96% when pulling 0923c2f70e100585d8a4c154b7ed23c08609c47e on stringy05:client_ntlm_auth into 591af0ef8cd71d7d428cfb6cfc1d476e326bb28f on dropwizard:master.

Coverage increased (+0.03%) to 84.96% when pulling 0923c2f70e100585d8a4c154b7ed23c08609c47e on stringy05:client_ntlm_auth into 591af0ef8cd71d7d428cfb6cfc1d476e326bb28f on dropwizard:master.

Looks good to me! Thank you very much for this contribution!


importer

hola!
how are you?
how can i use a custom scss importer  (like with webpack or simpla node-sass)?

Hi @patrikx3, what do you mean about custom scss importer?

ciao! i fixed, thanks. have a nice day!

you too!


Immer 6.0.1 with IE 11

🐛 Bug Report
We've upgraded the Immer version from 5.3.6 to 6.0.1. As a result, the app stopped being visible (it doesn't load) on IE 11, even though we've added enableES5() in the root file. It worked fine before the upgrade.
The error that we can see in the console is:
 SCRIPT5022: [Immer] minified error nr 19: ES5. Find the full error at: https://bit.ly/38PiBHb
The root js file:
import 'react-app-polyfill/ie11'; // This must be the first line
import 'react-app-polyfill/stable';
import TagManager from 'react-gtm-module';
import { enableES5 } from 'immer';
import React from 'react';
import ReactDOM from 'react-dom';

import App from './App';

import './index.scss';

if (process.env.REACT_APP_GTM) {
  TagManager.initialize({
    gtmId: process.env.REACT_APP_GTM,
  });
}

enableES5();

ReactDOM.render(<App />, document.getElementById('root'));

Other than this root, we only use immer to import produce in reducers.
Environment
Our package.json
{
  "private": true,
  "license": "UNLICENSED",
  "name": "____",
  "scripts": {
    "start": "react-scripts start",
    "start:devserver": "node ./devServer/index.js",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "test:ci": "react-scripts test --ci --maxWorkers=2 --coverage --reporters=default --reporters=jest-junit",
    "test:coverage": "react-scripts test --coverage --watchAll",
    "eject": "react-scripts eject",
    "lint": "eslint 'src/**/*.{ts,tsx}'",
    "lint:fix": "npm run lint -- --fix",
    "storybook": "start-storybook -p 9009 -s public",
    "build-storybook": "build-storybook -c .storybook -o storybook"
  },
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged",
      "pre-push": "CI=true react-scripts test --changedSince=master"
    }
  },
  "jest": {
    "collectCoverageFrom": [
      "**/*.{ts,tsx}",
      "!**/*.d.ts",
      "!**/*.stories.tsx",
      "!src/serviceWorker.tsx",
      "!**/__fixtures__/**",
      "!**/node_modules/**",
      "!src/shared/utils/test/**",
      "!src/Order/types/**",
      "!src/Quotes/types/**"
    ]
  },
  "lint-staged": {
    "src/**/*.{ts,tsx}": [
      "npm run lint:fix"
    ]
  },
  "proxy": "http://localhost:4000",
  "engines": {
    "node": "^12.13.0",
    "npm": ">=6.12.0"
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "ie 11",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },
  "dependencies": {
    "@callstack/async-storage": "^2.0.3",
    "amazon-cognito-identity-js": "^3.2.5",
    "axios": "^0.19.2",
    "babel-polyfill": "^6.26.0",
    "bootstrap": "^4.4.1",
    "classnames": "^2.2.6",
    "file-saver": "^2.0.2",
    "history": "^4.10.1",
    **"immer": "^6.0.1",**
    "moment": "^2.24.0",
    "moment-timezone": "^0.5.28",
    "postcode": "^2.0.0",
    "rc-progress": "^2.5.2",
    "react": "^16.13.0",
    "react-app-polyfill": "^1.0.6",
    "react-datepicker": "^2.15.0",
    "react-dom": "^16.13.0",
    "react-gtm-module": "^2.0.8",
    "react-redux": "^7.2.0",
    "react-router": "^5.1.2",
    "react-router-dom": "^5.1.2",
    "react-select": "^3.1.0",
    "react-slick": "^0.25.2",
    "react-table": "^7.0.0-rc.15",
    "react-tooltip": "^4.1.2",
    "redux": "^4.0.5",
    "redux-devtools-extension": "^2.13.8",
    "redux-saga": "^1.1.3",
    "styled-components": "^5.0.1"
  },
  "devDependencies": {
    "@sambego/storybook-state": "^2.0.1",
    "@storybook/addon-actions": "^5.3.14",
    "@storybook/addon-knobs": "^5.3.14",
    "@storybook/addon-links": "^5.3.14",
    "@storybook/addons": "^5.3.14",
    "@storybook/preset-create-react-app": "^2.0.0",
    "@storybook/react": "^5.3.14",
    "@testing-library/react": "9.4.0",
    "@types/classnames": "^2.2.10",
    "@types/enzyme": "^3.10.5",
    "@types/enzyme-adapter-react-16": "^1.0.6",
    "@types/file-saver": "^2.0.1",
<EMAIL_ADDRESS>"0.0.40",
    "@types/jest": "^25.1.4",
    "@types/moment-timezone": "^0.5.12",
    "@types/react": "^16.9.23",
    "@types/react-datepicker": "^2.11.0",
    "@types/react-dom": "^16.9.5",
    "@types/react-gtm-module": "^2.0.0",
    "@types/react-redux": "^7.1.7",
    "@types/react-router-dom": "^5.1.2",
    "@types/react-select": "^3.0.10",
    "@types/react-slick": "^0.23.4",
    "@types/react-table": "^7.0.4",
    "@types/react-tooltip": "^3.11.0",
    "@types/storybook-react-router": "^1.0.1",
    "@types/styled-components": "^5.0.1",
    "@typescript-eslint/eslint-plugin": "^2.23.0",
    "@typescript-eslint/parser": "^2.23.0",
    "awesome-typescript-loader": "^5.2.1",
    "enzyme": "^3.11.0",
    "enzyme-adapter-react-16": "^1.15.2",
    "eslint": "^6.8.0",
    "eslint-config-prettier": "^6.10.1",
    "eslint-plugin-prettier": "^3.1.2",
    "eslint-plugin-react": "^7.19.0",
    "eslint-plugin-react-hooks": "^2.5.0",
    "husky": "^4.2.3",
    "jest-junit": "10.0.0",
    "jest-styled-components": "^7.0.0",
    "lint-staged": "^10.0.8",
    "node-sass": "^4.13.1",
    "prettier": "^1.19.1",
    "react-scripts": "3.4.0",
    "redux-saga-test-plan": "^4.0.0-rc.3",
    "storybook-react-router": "^1.0.8",
    "typescript": "^3.8.3",
    "webpack": "4.41.5"
  }
}

Please only file bug reports against the latest Immer version
Note that enableES5() should be called before doing any logic, so I'd make
sure to do it before initializing that tag manager, and ideally directly
after those ie11 polyfills
On Wed, May 20, 2020 at 11:11 AM Justyna Jurkowska (Zygmunt) <
<EMAIL_ADDRESS>wrote:

🐛 Bug Report
We've upgraded the Immer version from 5.3.6 to 6.0.1. As a result, the
app stopped being visible (it doesn't load) on IE 11, even though we've
added enableES5() in the root file. It worked fine before the upgrade.
The error that we can see in the console is:
SCRIPT5022: [Immer] minified error nr 19: ES5. Find the full error at:
https://bit.ly/38PiBHb
The root js file:
import 'react-app-polyfill/ie11'; // This must be the first line
import 'react-app-polyfill/stable';
import TagManager from 'react-gtm-module';
import { enableES5 } from 'immer';
import React from 'react';
import ReactDOM from 'react-dom';
import App from './App';
import './index.scss';
if (process.env.REACT_APP_GTM) {
TagManager.initialize({
gtmId: process.env.REACT_APP_GTM,

});
}
enableES5();
ReactDOM.render(, document.getElementById('root'));
Other than this root, we only use immer to import produce in reducers.
Environment
Our package.json
{
"private": true,
"license": "UNLICENSED",
"name": "sse",
"scripts": {
"start": "react-scripts start",

"start:devserver": "node ./devServer/index.js",

"build": "react-scripts build",

"test": "react-scripts test",

"test:ci": "react-scripts test --ci --maxWorkers=2 --coverage --reporters=default --reporters=jest-junit",

"test:coverage": "react-scripts test --coverage --watchAll",

"eject": "react-scripts eject",

"lint": "eslint 'src/**/*.{ts,tsx}'",

"lint:fix": "npm run lint -- --fix",

"storybook": "start-storybook -p 9009 -s public",

"build-storybook": "build-storybook -c .storybook -o storybook"

},
"husky": {
"hooks": {

  "pre-commit": "lint-staged",

  "pre-push": "CI=true react-scripts test --changedSince=master"

}

},
"jest": {
"collectCoverageFrom": [

  "**/*.{ts,tsx}",

  "!**/*.d.ts",

  "!**/*.stories.tsx",

  "!src/serviceWorker.tsx",

  "!**/__fixtures__/**",

  "!**/node_modules/**",

  "!src/shared/utils/test/**",

  "!src/Order/types/**",

  "!src/Quotes/types/**"

]

},
"lint-staged": {
"src/**/*.{ts,tsx}": [

  "npm run lint:fix"

]

},
"proxy": "http://localhost:4000",
"engines": {
"node": "^12.13.0",

"npm": ">=6.12.0"

},
"browserslist": {
"production": [

  ">0.2%",

  "not dead",

  "ie 11",

  "not op_mini all"

],

"development": [

  "last 1 chrome version",

  "last 1 firefox version",

  "last 1 safari version"

]

},
"dependencies": {
"@callstack/async-storage": "^2.0.3",

"amazon-cognito-identity-js": "^3.2.5",

"axios": "^0.19.2",

"babel-polyfill": "^6.26.0",

"bootstrap": "^4.4.1",

"classnames": "^2.2.6",

"file-saver": "^2.0.2",

"history": "^4.10.1",

**"immer": "^6.0.1",**

"moment": "^2.24.0",

"moment-timezone": "^0.5.28",

"postcode": "^2.0.0",

"rc-progress": "^2.5.2",

"react": "^16.13.0",

"react-app-polyfill": "^1.0.6",

"react-datepicker": "^2.15.0",

"react-dom": "^16.13.0",

"react-gtm-module": "^2.0.8",

"react-redux": "^7.2.0",

"react-router": "^5.1.2",

"react-router-dom": "^5.1.2",

"react-select": "^3.1.0",

"react-slick": "^0.25.2",

"react-table": "^7.0.0-rc.15",

"react-tooltip": "^4.1.2",

"redux": "^4.0.5",

"redux-devtools-extension": "^2.13.8",

"redux-saga": "^1.1.3",

"styled-components": "^5.0.1"

},
"devDependencies": {
"@sambego/storybook-state": "^2.0.1",

"@storybook/addon-actions": "^5.3.14",

"@storybook/addon-knobs": "^5.3.14",

"@storybook/addon-links": "^5.3.14",

"@storybook/addons": "^5.3.14",

"@storybook/preset-create-react-app": "^2.0.0",

"@storybook/react": "^5.3.14",

"@testing-library/react": "9.4.0",

"@types/classnames": "^2.2.10",

"@types/enzyme": "^3.10.5",

"@types/enzyme-adapter-react-16": "^1.0.6",

"@types/file-saver": "^2.0.1",

<EMAIL_ADDRESS>"0.0.40",

"@types/jest": "^25.1.4",

"@types/moment-timezone": "^0.5.12",

"@types/react": "^16.9.23",

"@types/react-datepicker": "^2.11.0",

"@types/react-dom": "^16.9.5",

"@types/react-gtm-module": "^2.0.0",

"@types/react-redux": "^7.1.7",

"@types/react-router-dom": "^5.1.2",

"@types/react-select": "^3.0.10",

"@types/react-slick": "^0.23.4",

"@types/react-table": "^7.0.4",

"@types/react-tooltip": "^3.11.0",

"@types/storybook-react-router": "^1.0.1",

"@types/styled-components": "^5.0.1",

"@typescript-eslint/eslint-plugin": "^2.23.0",

"@typescript-eslint/parser": "^2.23.0",

"awesome-typescript-loader": "^5.2.1",

"enzyme": "^3.11.0",

"enzyme-adapter-react-16": "^1.15.2",

"eslint": "^6.8.0",

"eslint-config-prettier": "^6.10.1",

"eslint-plugin-prettier": "^3.1.2",

"eslint-plugin-react": "^7.19.0",

"eslint-plugin-react-hooks": "^2.5.0",

"husky": "^4.2.3",

"jest-junit": "10.0.0",

"jest-styled-components": "^7.0.0",

"lint-staged": "^10.0.8",

"node-sass": "^4.13.1",

"prettier": "^1.19.1",

"react-scripts": "3.4.0",

"redux-saga-test-plan": "^4.0.0-rc.3",

"storybook-react-router": "^1.0.8",

"typescript": "^3.8.3",

"webpack": "4.41.5"

}
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/immerjs/immer/issues/601, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBCVGTQR6SP3SC4YUUTRSOUF3ANCNFSM4NFZMWPQ
.

Note that error 19 indicates that you are using a feature (like patches or maps) without enabling it. Please check https://immerjs.github.io/immer/docs/installation for details

@mweststrate , thanks for responding! I've tried enableAllPlugins already, with the same result. However, I'll try to combine it with reordering in the file.

@mweststrate , I've updated immer to 6.0.5., I've also made the changes you've recommended, I'm still seeing the same error.
Anything I should be looking into? Is there anything maybe related to babel that you'd suggest checking?
import 'react-app-polyfill/ie11'; // This must be the first line
import 'react-app-polyfill/stable';
import { enableAllPlugins } from 'immer';
/* eslint-disable import/first */
enableAllPlugins();

import TagManager from 'react-gtm-module';
import React from 'react';
import ReactDOM from 'react-dom';

import App from './App';

import './index.scss';

if (process.env.REACT_APP_GTM) {
  TagManager.initialize({
    gtmId: process.env.REACT_APP_GTM,
  });
}

ReactDOM.render(<App />, document.getElementById('root'));

Would you mind retrying with 6.0.6? it should give a clearer error message.

Never mind, that won't help with your case. I think you need a reproduction, it looks like immer is still being used before that enable plugins call is made, or you have multiple immers in your project (yarn why immer might help with that). For more help you might need to strip the project and make a minimal thing that can be checked.

@mweststrate, thank you for your answer. Indeed, we do have a few dependencies that are using immer(immer@1.10.0).

Ok, best analyse the stack traces to see if the throwing immer is the one
you enable ES5 for. Not much we can do from this side without small repro.
It might be that enableES5 needs to be called by one of the dependencies
that you are trying to use, if they are bundling their own version.
On Thu, 21 May 2020, 16:04 Justyna Jurkowska (Zygmunt), <
<EMAIL_ADDRESS>wrote:

@mweststrate https://github.com/mweststrate, thank you for your answer.
Indeed, we do have a few dependencies that are using immer(immer@1.10.0).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/immerjs/immer/issues/601#issuecomment-632136683, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBCWEBLE272LSWO6UNDRSU7GVANCNFSM4NFZMWPQ
.

I am also having this issue - on version 6.0.5

@katiawheeler  Please only report issues against the latest version (there has been some IE fixes lately).
If the issue still exists on the latest version, please do provide actionable information. Otherwise just a thumbs up on the issue will do.

@Kotauror How did you fix it? I have the exact same issue, getting the plugin error in IE11 even though I've installed all plugins. I also have react-dev-utils depending on<EMAIL_ADDRESS>which is not inlucded in the final bundle actually (it's a @storybook/react dependency)

@Kotauror How did you fix it? I have the exact same issue, getting the plugin error in IE11 even though I've installed all plugins. I also have react-dev-utils depending on<EMAIL_ADDRESS>which is not inlucded in the final bundle actually (it's a @storybook/react dependency)

I'm sorry to disappoint you, but the fix we went with for now was to freeze immer on v. 5.3.6, where it works fine, as solving this got deprioritized. Once it's back on our radar, I'll come back to the issue and hopefully will be able to have a more positive update.

@Kotauror Thanks for the heads up, I actually just fixed it randomly with bunch of different changes. One was that I imported and called enableES5 directly where I used produce. Apparently doing it in the entry Webpack file didn't quite worked (although it used to before). I also did a chore update to all my dependencies and excluded storybook from babel-loader webpack config.

IE 11 should work on the last version. If it doesn't, please report fresh issues with new details on the latest immer version. Otherwise it is unclear if we are dealing with old problems or not. Locking the conversation now, as comments on old issues are inactionable.


Handle reboot failures

Currently reboot() return bool indicating if reboot happened or not.
However this value is ignored by execute (https://github.com/teemtee/tmt/blob/main/tmt/steps/execute/internal.py#L262)
IMO we should raise exception instead and handle correctly (stop execution) if reboot fails to happen (e.g. fail to boot, reboot ignored etc)

To reproduce reboot ,  we can use provision connect,
e.g.
(tmt) huanli@FOO:plans$ cat reboot.fmf
summary: Basic smoke test
execute:
    how: tmt
    script: uname -a
(tmt) huanli@FOO:plans$
(tmt) huanli@FOO:plans$ tmt run -a provision --how=connect --guest=kvm-01-guest01 reboot
/var/tmp/tmt/run-001

/plans/reboot
    discover
        how: shell
        summary: 1 test selected
    provision
        how: connect
        guest: kvm-01-guest01.lab.eng.brq2.redhat.com
        user: root
        key: not provided
        summary: 1 guest provisioned
    prepare
        summary: 0 preparations applied
    execute
        how: tmt
        summary: 1 test executed
    report
        how: display
        summary: 1 test passed
    finish
        reboot: Rebooting guest
        reboot: Reboot finished
        summary: 1 task completed

total: 1 test passed

(tmt) huanli@FOO:plans$ cat /var/tmp/tmt/run-001/log.txt
...<snip>...
14:21:19         Execute command 'reboot' on guest 'kvm-01-guest01'.
14:21:19         Run command 'ssh -oForwardX11=no -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oIdentitiesOnly=yes -iNone -S/run/user/1001/tmt/tmpfutsubjj root@kvm-01-guest01 export TMT_PLAN_DATA=/var/tmp/tmt/run-005/plans/reboot/data; reboot'.
#^^^^^^^^^^^^^^^^^^^^^^^^ reboot is done via ssh

@lukaszachy, I failed to trigger off the code path ExecuteInternal._handle_reboot() via tmt run -a provision --how=... reboot, would you please let me know how can I make tmt run trigger off the related code path?

https://github.com/teemtee/tmt/blob/main/tmt/steps/execute/internal.py#L214 187	    def _handle_reboot(self, test, guest):
 188	        """
 189	        Reboot the guest if the test requested it.
 190
 191	        Check for presence of a file signalling reboot request
 192	        and orchestrate the reboot if it was requested. Also increment
 193	        REBOOTCOUNT variable, reset it to 0 if no reboot was requested
 194	        (going forward to the next test). Return whether reboot was done.
 195	        """
 196	        if self._will_reboot(test):
 ...
 212	            os.remove(reboot_request_path)
 213	            guest.push(test_data)
 214	            try:
 215	                guest.reboot(command=reboot_command, timeout=timeout)
 216	            except tmt.utils.RunError:
 217	                self.fail(
 218	                    f"Failed to reboot guest using the "
 219	                    f"custom command '{reboot_command}'.")
 220	                raise
 221	            except tmt.utils.ProvisionError:
 222	                self.warn(
 223	                    "Guest does not support soft reboot, "
 224	                    "trying hard reboot.")
 225	                guest.reboot(hard=True, timeout=timeout)
 226	            return True
 227	        return False

@idorax Execute 'tmt-reboot' within the test. Inspiration in any test which uses this command.

Isn't this solved by #1487 ? I just didn't realize that there is a duplicate

Well, @lukaszachy and @FrNecas, can I just close this issue now?

I'd say @FrNecas should make his PR fix this issue as well. (if it really fixes it ;)

Thanks @lukaszachy, I updated the assignee to @FrNecas just now.

Fixed in #1487


feat(rxjs): move rxjs/create into rxjs

Moves all Observable creation functions under the rxjs namespace.
BREAKING CHANGE: rxjs/create items are now exported from rxjs
Based on several other discussions we've had, rxjs/create was a little less ergonomic than we'd have liked. Also with the move to using the EMPTY constant, it seemed to make more sense.

Coverage remained the same at 97.506% when pulling 4b654abb03dde1c27374981ff3fda3122397092f on benlesh:create-to-rxjs into a24146f1ad09acd62ea92ee0f8d983d5ab5cf835 on ReactiveX:master.


Fix github tests (#2287)

Description
Fix GitHub tests
Related Issues
#2287
Checklist

[x] Pre-commit hook is installed to do formatting checks before committing code...etc
[ ] Tests included
[ ] Build pass
[ ] Documentation
[x] Code format and docstrings

Codecov Report

Merging #2290 (261c6b7) into development (814c5d8) will decrease coverage by 0.19%.
The diff coverage is 88.88%.

@@               Coverage Diff               @@
##           development    #2290      +/-   ##
===============================================
- Coverage        32.88%   32.68%   -0.20%
===============================================
  Files              136      137       +1
  Lines            13366    13392      +26
===============================================
- Hits              4395     4377      -18
- Misses            8971     9015      +44

Impacted Files
Coverage Δ

jumpscale/clients/github/helper.py
71.42% <71.42%> (ø)

jumpscale/clients/github/github.py
90.00% <100.00%> (+1.90%)
:arrow_up:

jumpscale/clients/github/repo.py
33.11% <100.00%> (+0.87%)
:arrow_up:

jumpscale/packages/admin/services/diskcheck.py
61.53% <0.00%> (-23.08%)
:arrow_down:

jumpscale/packages/admin/services/stellar.py
37.03% <0.00%> (-18.52%)
:arrow_down:

jumpscale/clients/stellar/__init__.py
30.76% <0.00%> (-12.31%)
:arrow_down:

jumpscale/tools/servicemanager/servicemanager.py
62.88% <0.00%> (-11.35%)
:arrow_down:

jumpscale/packages/admin/actors/wallet.py
21.25% <0.00%> (-10.00%)
:arrow_down:

jumpscale/entry_points/threebot.py
33.53% <0.00%> (-3.00%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3f7b91c...261c6b7. Read the comment docs.

Codecov Report

Merging #2290 (261c6b7) into development (814c5d8) will decrease coverage by 0.19%.
The diff coverage is 88.88%.

@@               Coverage Diff               @@
##           development    #2290      +/-   ##
===============================================
- Coverage        32.88%   32.68%   -0.20%
===============================================
  Files              136      137       +1
  Lines            13366    13392      +26
===============================================
- Hits              4395     4377      -18
- Misses            8971     9015      +44

Impacted Files
Coverage Δ

jumpscale/clients/github/helper.py
71.42% <71.42%> (ø)

jumpscale/clients/github/github.py
90.00% <100.00%> (+1.90%)
:arrow_up:

jumpscale/clients/github/repo.py
33.11% <100.00%> (+0.87%)
:arrow_up:

jumpscale/packages/admin/services/diskcheck.py
61.53% <0.00%> (-23.08%)
:arrow_down:

jumpscale/packages/admin/services/stellar.py
37.03% <0.00%> (-18.52%)
:arrow_down:

jumpscale/clients/stellar/__init__.py
30.76% <0.00%> (-12.31%)
:arrow_down:

jumpscale/tools/servicemanager/servicemanager.py
62.88% <0.00%> (-11.35%)
:arrow_down:

jumpscale/packages/admin/actors/wallet.py
21.25% <0.00%> (-10.00%)
:arrow_down:

jumpscale/entry_points/threebot.py
33.53% <0.00%> (-3.00%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3f7b91c...261c6b7. Read the comment docs.


add known issue for operator

reference #476

Codecov Report

Merging #503 (0aaab36) into master (9878248) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #503   +/-   ##
=======================================
  Coverage   56.70%   56.70%
=======================================
  Files          30       30
  Lines        2028     2028
=======================================
  Hits         1150     1150
  Misses        807      807
  Partials       71       71

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9878248...0aaab36. Read the comment docs.


send event: RequestGuildMember returns opcode 9 Invalid Session

Using the RequestGuildMembers Send Event without the following conditions results in an opcode 9 payload (Invalid Session).

As per Discord, the user must specify one of field query or user_ids.
As per Discord, when query is specified, limit must also be specified.

This payload prompts the bot to reconnect to the Gateway,

This issue could be solved by adding a help message to the RequestGuildMembers.SendEvent method that prompts the user of an incorrect configuration. However, the send event is likely called at a high frequency, the highest of any send event.
Placing an unnecessary if-statement at the start of a high-frequency code path is not recommended. So instead, this issue will serve as documentation for any potential issues regarding an incorrect RequestGuildMembers event configuration resulting in an opcode 9 (Invalid Session).


Agrim/chore: thai original version

Changes:

...

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

not required


[All Hosts] (devx) update VS2019 version mentions in intellisense art…

…icle

Docs Build status updates of commit 6462a75:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/get-javascript-intellisense-in-visual-studio.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Error [ERR_REQUIRE_ESM] in 3.0 beta versions and 2.0 beta 7 fails on require('performance-now')

In a Remix app, I can't use React Charts any more :-(
If I try the 3.0 beta the build fails with:
Error [ERR_REQUIRE_ESM]: require() of ES Module /node_modules/d3-time-format/src/index.js from /node_modules/react-charts/lib/utils/buildAxis.linear.js not supported.
[1] Instead change the require of index.js in /node_modules/react-charts/lib/utils/buildAxis.linear.js to a dynamic import() which is available in all CommonJS modules.

While if I try the 2.0 beta-7 the build fails with:
1] ✘ [ERROR] Could not resolve "performance-now"
[1]
[1]     node_modules/react-charts/dist/react-charts.development.js:853:20:
[1]       853 │   var now = require('performance-now'),
[1]           ╵                     ~~~~~~~~~~~~~~~~~

Can anyone suggest a workaround? I'm loath to use another charting library, I like React Charts.

Reproduction here: https://github.com/fergusmeiklejohn/rc-esm-bug-demo
npm i
npm run dev
navigate to locahost:3000
error logs in server console

the fix is adding serverDependenciesToBundle: ["react-charts", "d3-time-format"], to remix.config.js
See this in the Remix docs: https://remix.run/docs/en/v1/pages/gotchas#importing-esm-packages


Can't find Blood Sense

I haven't been able to get the Blood Sense option to show up, and I can't find it as a feat either. What do I do? I'm currently using V11 for 5e

The last version compatible with V11 is 1.14.3. Blood Sense was added in 2.3.0.


Fast Path is available for non ER Direct circuits as well

Pls strike the line saying ER direct is a requirement.

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

ID: dc3df950-cbe6-9514-8768-1614312ab0c3
Version Independent ID: a40c4a7f-2c61-4fa4-fafe-1eaa67e794fe
Content: ExpressRoute: Link a VNet to a circuit: Azure PowerShell
Content Source: articles/expressroute/expressroute-howto-linkvnet-arm.md
Service: expressroute
GitHub Login: @ganesr
Microsoft Alias: ganesr

@jknightly Thanks for the feedback! I have removed the incorrect requirement that Fast Path requires ER Direct, and the docs should reflect the change within 24 hours.
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.


Skip tests on Appveyor due to PSReadline issue

PR Summary
Enter-PSHostProcess tests fail on AppVeyor due to PSReadline issue. This change skips the tests on AppVeyor.
Expected 3948, but got @(<empty>, 'Oops, something went wrong.  Please report this bug with the details below.', 'Report on GitHub: https://github.com/lzybkr/PSReadLine/issues/new', '-----------------------------------------------------------------------', 'Last 0 Keys:', '```', <empty>, '```', <empty>, 'Exception:').

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[x] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

Something is not right; CI's are failing for this change.


VS code makes some syntax error, when we manually save the changes

Description:
$title
Steps to reproduce:

Write a ballerina program in which it has @tainted annotation.

Before saving the file

Then manually save the file

Affected Versions:
SLP4-SNAPSHOT
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):
Area/LanguageServer
Suggested Assignees (optional):

@suganyasuven This is an issue with the formatting as I observed. Can you check whether you have enabled formating on save option in your settings.json? If so, either you can disable the formating on save option or, enable auto save option. If this is the issue let's address this as a formatter issue.

@nadeeshaan I am not getting this issue now. It works fine.


Map SNS notification message as object in SqsListener

Type: Feature
Is your feature request related to a problem? Please describe.
Is there a way to automatically map SNS notification messages in @SqsListener? If the SQS queue is subscribed to a topic, the listener for the queue would process the SNS Notification. How can we automatically map the SNS Notification body as an object in the Sqs Listener?
Describe the solution you'd like
Ideally we can use the @NotificationSubject and @NotificationMessage in the method for the SqsListener. Is this possible?
  @SqsListener(value = QUEUE_NAME)
  public void consumeMessage(
      @NotificationSubject String subject,
      @NotificationMessage SomeObject messageAsObject) {
    log.info(subject);
    log.info(messageAsObject)
  }

@lenlaurito did you tried with this attribute => https://docs.aws.amazon.com/sns/latest/dg/sns-large-payload-raw-message-delivery.html
more explanation here: https://github.com/awspring/spring-cloud-aws/issues/886

@dbouclier Yes, we are also doing mapping of the "Message" in the SNS notification to an object-- similar to your comment. We're looking for an easier way of doing this if possible. Like having the "Message" mapped to an object automatically.
In previous versions of spring cloud (2.x), we were able to achieve this using @NotificationMessage annotation. But it doesn't seem to be working with spring cloud 3?

it's working actually, I was able to automatically de-serialize object in my @SqsListener, like that:
@SqsListener(queueNames = "some_queue.fifo")
    public void onEvent(final Message<MyCustomeType> event) {
      .....
    }

OR

@SqsListener(queueNames = "some_queue.fifo")
    public void onEvent(final MyCustomeType event) {
      .....
    }

but in the subscription you have to enable "RawMessageDelivery" attribute

@dbouclier We'd still like to be able to access the other fields of the notification though, like the subject.

Hi @lenlaurito and @dbouclier.
SCAWS 3.0 SQS integration doesn't provide any particular integration with SNS OOTB.
You should be able to have the raw message as a POJO and work your way through it with all available information in the original message using RawMessageDelivery as mentioned.
But I think it'd be helpful to provide the functionality similar to 2.0.
Would you be willing to write a PR for it?
Thanks.

Having the same issue with trying to upgrade.  I believe previous version of argument resolvers had a NotificationMessageArgumentResolver, where as the current version does not.

For the current version, what's the recommended way to customize the message converter to add the NotificationMessageHandlerMethodArgumentResolver and NotificationMessageHandlerMethodArgumentResolver, but still keep all the other defaults?

Hi @dapriett, you can use a SqsListenerConfigurer to manage the converters.
We're looking for a PR to add these resolvers, if you'd like to write one I'd be happy to review it.
Thanks.

I was able to get @NotficationMessage to work locally by adding the missing classes to my project and adding it to the registrar.
@tomazfernandes i don't mind opening up a PR to add these, I was able to copy these files over with no changes(I don't think). So let me know if there is something I am missing, otherwise I can create a PR

Hi @msosa, sure, sounds good, if you can please open a PR.
It'd be great if you could add an integration test and / or a Sample using this, though that's optional and won't block the PR.
Thanks.

Is there any progress on this ticket? We use this library, and SNS->SQS pipes, and want to update to SpringBoot 3. We are waiting for this issue to be fixed so that we can do the update without having to update our entire infrastructure to deliver raw messages.

Is there any progress on this ticket? We use this library, and SNS->SQS pipes, and want to update to SpringBoot 3. We are waiting for this issue to be fixed so that we can do the update without having to update our entire infrastructure to deliver raw messages.

We should be able to take a look into that soon - in the meantime, there's a workaround by creating a NotificationMessageArgumentResolver just like the PR opened for this issue.
Would that work for you?

We have 20+ projects currently using this, so rolling our own changes is not exactly something we would like to do. Particularly when the library change is in the pipeline. Hopefully it won't be too long before the library fix is in place :)

We now support @SnsMeesage for single message and batch listeners.
I'll close this issue, but if there's anything else we can reopen it.

@tomazfernandes
Thank you for the update. We've seen the SnsNotificationMessage annotation that can be used to get the Message payload and map it to an object.
Is there also a way for us to get the other details, like the sns notification subject in the the queue listeners? In older versions, we were able to use NotificationSubject annotation in the listeners for this.


Refactor DurableTaskRegistry, move bulk of methods to extensions

This PR refactors the DurableTaskRegistry to have the core implementation be the minimal required functionality. Then all of the other functionalities are moved to extension methods. The reason I like this approach is it forces a code "funnel", where we can force consistency in behavior by having a minimal API surface on the core type, and then all extension methods must go through this API surface.

I'm not opposed to this change, but I'll admit I don't understand what the benefit is. In my experience, extension methods are confusing because 1) they can't be unit tested directly (doesn't apply here since this is a sealed class) and 2) it makes searching through the code harder. You mentioned the ability to ensure all methods funnel into a few core ones, but why is it beneficial to create self-imposed restrictions like this?

That is fair. Would you rather these remain as instance methods?

That would be my preference, mainly as a means of prioritizing code simplicity.

Done - they are now instance methods.


[BUG] Mouse/Touch events in ssh terminal are broken

Bug description
On iPad the mouse and touch events in ssh terminal are broken.

no touch/click event
no scroll dragging
no double click/touch
no drop down menu
no drag & drop
This would affect all programs using mouse events. For example Midnight Commander is unusable.
External touchpads are also useless. Apple Pencil is not working either.
Also holding the touch or the pen would not allow drag scroll, because the context menu is opened instead.

Screenshots

Steps to reproduce
TOUCH BUG

Touch a menu or a file in MC
No response
Expected: the element touched should be opened/selected.

DRAG BUG

Drag to scroll a list of files in a MC panel or a text in a text editor.
The context menu is being opened instead.
Expected: the file list or the text in the text editor should scroll when dragged up or down.

@Emasoft I have a known issue about mouse events on WebSSH, iOS and macOS
I will improve its support

Thanks! This is very important! 🫶🏻🫡👍