Candidate Package: pytest-selenium

References

https://www.zenrows.com/blog/selenium-wire#request-response-objects
https://github.com/pytest-dev/pytest-selenium

Implemented with: 8c9f940ff1672b37fa774a7c42ed7420aec24ff5


motion regressors

Is there a way to tell lyman not to include motion regressors in the GLM?

No. Why would you want to do that?

I don't like them. Neither do some FSL people. From the feat manual: You may want to include the head motion parameters (as estimated by MCFLIRT motion correction in the Pre-stats processing) as confound EVs in your model. This can sometimes help remove the residual effects of motion that are still left in the data even after motion correction. This is not strongly recommended as there is still much to learn about residual motion effects; simply adding such confound EVs is quite a simplistic solution.
It's not that big of a deal though. It shouldn't make a huge difference one way or another...
Sent from my iPhone

On May 12, 2015, at 6:52 PM, Michael Waskom<EMAIL_ADDRESS>wrote:
No. Why would you want to do that?
—
Reply to this email directly or view it on GitHub.

That seems to be saying "this may not be the best way to do it, so don't do it at all", which seems like a strange perspective to have.

I dont really understand how they do what they’re supposed to.  Also I think they introduce colinearity in the model which can be problematic.

On May 12, 2015, at 7:38 PM, Michael Waskom<EMAIL_ADDRESS>wrote:
That seems to be saying "this may not be the best way to do it, so don't do it at all", which seems like a strange perspective to have.
—
Reply to this email directly or view it on GitHub https://github.com/mwaskom/lyman/issues/61#issuecomment-101486820.

IMO, if your motion is correlated with your task regressors, your'e screwed whether or not you include the motion regressors in the model.
In any case, if you don't want them, write your own scripts.


feat(dedicated-host): Update VPC service with API version 2020-12-15

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add ruby-2.3

Add Ruby 2.3 Dockerfiles and tests.

you need to add the new version to the Makefile

[test]

Yes, the SCL packages are not in CentOS yet. :)

eta?

(sorry wrong button)

ETA 1 week

k, let's re-test it then.

Ruby 2.3 packages are in CentOS testing repository only now, so those can be installed using:
yum install -y centos-release-scl-rh
yum-config-manager --enable centos-sclo-rh-testing

@pvalena you'll want to add this change:
https://github.com/openshift/s2i-ruby/pull/104

[test]

lgtm


やったことメモ

oh-my-zsh 周り
git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions
git clone --depth=1 https://github.com/romkatv/powerlevel10k.git ${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k

ツール
clippy
raycast

terraform
https://qiita.com/sugo/items/8b667e8b6bfe092e9d62


Treat 'pen' pointerType like 'mouse' in useHover hook

I made these changes in the github.dev editor, so apologies if any linter requirement might not be met.
I made these changes to the dist/floating-ui.react-dom-interactions.esm.js locally, tested them, and then copied the changes to the source file - so there's an exceedingly small chance there was a transcription error on my part - but I believe this code to be functional and ready to go.
@atomiks

Good catch @atomiks! I accidentally made that typo and "fixed it" but I must have hit Ctrl+Z once too often and undid it.

@atomiks I'm not sure if it would be undefined or an empty string. Do you still want me to stick undefined in there, or should we handle that as a separate issue if there's some uncertainty.

pointerTypeRef.current can be undefined, which is why we need it (if onPointerEnter/onPointerDown are never called). As for empty string, yeah I guess add that as well. I think it's better to fallback to showing the floating element than not showing it when it can't be determined. Hopefully all touch devices reliably send back touch though...

Alright now we have both undefined and '' in the array!

Hopefully all touch devices reliably send back touch though...

One can never be certain, but I think it's a safe assumption. I think it's much less likely for touch devices to have any weirdness  like my edge case involving pen vs mouse.


Dispatching and rate sensors fail to reflect OE intelligent smart charges

Describe the bug
The integration currently looks at the source to determine if the dispatch is a bump-charge (initiated by the user - peak rates) or a smart-charge (initiated by OE - off peak rates).
There seems to be a change in the data returned by OE and source is no longer defined. This is stopping the dispatch sensor from turning on and from the rate sensor changing dispatch periods to off peak.
Reproduction steps
Get pending dispatches from OE where the source is None.
Expected behaviour
Reached out to OE on clarification if this change is expected (None/Null equals a smart charge/off peak rate) or a bug.
Tariff Code
Intelligent tariffs
Integration Version
10.1.2
Home Assistant Version
2022.2.2
Fresh Install?
After upgrading
Home Assistant Logs
N/A
Confirmation

[X] I confirm that I cannot find my solution within the documentation
[X] I confirm that I cannot find my solution within the FAQ

This should be resolved in v10.1.3, as per recommendation from OE (https://forum.octopus.energy/t/pending-and-completed-octopus-intelligent-dispatches/8510/102?u=bottlecapdave)


TypeScript definitions

Is it possible to include typescript definitions?

I don't use typescript, but if someone submits a PR I'll gladly merge it.

@syabro should the definitions file perhaps be named index.d.ts? I don't use TypeScript regularly so I can't speak much to tooling for real TypeScript users, but Visual Studio Code isn't picking up the definitions with the current filename. When I rename it within node_modules (not a real solution, of course), it works.

@rainydio have no idea :) works for my IDEA, but of course you may add a PR with renaming I bet it will break anything

#29 should fix this. Closing.


Project Delta ESP.

Acknowledgement of preliminary instructions

[X] I have read and acknowledged the preliminary instructions.

What idea do you have?
Project delta made a new anti cheat that whenever ctrl+f8 is pressed (same as to activate ESP 1st stage) It starts to lag SO MUCH your FPS drops to 10 and you get kicked, and even if you dont its UNPLAYABLE so i suggest

I suggest making it so that there is an option to change the starting button to ctrl+f7 or alt+f7-f8 so it cant be detected

ehhhhhhh? 🤣

yeb, but how to change buttons? testing on other games and esp dont works there too for some reason

this is not a cheating tool bud


Add new theme and correct some document.

Details are in the commit history.
Tested under Chrome on Linux, Android Browser for Android 4.1 and Kindle Paperwhite 2.

Thanks for the contribution!

You are welcome. They are what I need meanwhile.


Compilation not working.

I am totally new to protobuf's. We are using Play Framework with Java. I have implemented everything specified in the docs.
Following are my settings in build.sbt:
PB.protobufSettings

PB.javaConversions in PB.protobufConfig := true

PB.runProtoc in PB.protobufConfig := { args =>
  com.github.os72.protocjar.Protoc.runProtoc("-v300" +: args.toArray)
}

Also added these two libraryDependencies inside build.sbt:
"io.grpc" % "grpc-all" % "0.9.0",
"com.trueaccord.scalapb" %% "scalapb-runtime-grpc" % "0.5.21"

And my plugins.sbt contains following lines:
addSbtPlugin("com.trueaccord.scalapb" % "sbt-scalapb" % "0.5.21")

libraryDependencies += "com.github.os72" % "protoc-jar" % "3.0.0-b2"

I am not getting any errors on running "activator clean compile". But it is also not running compilation of the .proto file in src/main/protobuf. Though a folder named "compiled_protobuf" is getting created at target/scala-2.11/src_managed/main/.
I don't understand what I am missing. I ultimately want to use gRPC.

Can you try "sbt clean compile"? I have never tried using ScalaPB with activator. If it doesn't work, can you share a github project that has this problem?

I checked on the net, activator runs sbt internally. Its same. But I will try sbt also.
Meanwhile can you please have a look at build.sbt and plugins.sbt

This link tells that activator is just a little fancy wrapper around sbt and there is no way to invoke sbt directly. I am still looking into any possible way to run sbt directly.

Maybe try activator shell and inside it clean and compile. For running sbt directly, just install SBT and run it from the project's home directory, nothing else is normally needed.

Tried activator shell and through SBT also now. No luck.

Are my .sbt files fine?

Was trying different things. Commenting the following line resulted in successful compilation:
lazy val root = (project in file(".")).enablePlugins(PlayJava)
But this is somehow very important. Any way to work around this?

maybe just
enablePlugins(PlayJava)

Another alternative is to switch to a multi-project build:
  lazy val protos = project
    .settings(
      PB.protobufSettings ++ Seq(
        // protoc in PB.protobufConfig := "/path/to/protoc",
        // Optionally read protos from parent directory, otherwise it's protos/src/main/protobuf
        // sourceDirectory in PB.protobufConfig := file("../some/path/to/proto")
     ))

The protobufs should go in "protos/src/main/protobuf" (you can customize, see comments above)
Then make the root project depend on it:
lazy val root = (project in file(".")).enablePlugins(PlayJava).dependsOn(protosProject)

I am trying this. Not working yet. But I will figure it out.
I will let you know. Thanks a lot.

Is it anyway possible to do this without updating sbt version. I am getting evicted warning.
From last 6 hours I am struggling with this problem only. :(

Finally, its working now. I ended up creating separate build.sbt file for protos folder inside root. Sbt is beyond my understanding. Thanks for the help.


Assertion failed:  'A listener must be provided'

This is very similar to https://github.com/phetsims/scenery/issues/1377, which also popped up from a new test I added, many sims will hit this when running the record-input-and-playback with ?fuzzBoard. For example
http://localhost:8080/phet-io-wrappers/input-record-and-playback/?sim=balloons-and-static-electricity&phetioDebug&fuzzBoard, if you instead hit the "unique ID" issue with dialog playback, please refresh, that will be covered by https://github.com/phetsims/phet-io/issues/1847.

@jessegreenberg, this fix feels like a bandaid, is there something in the PhET-iO context that is clearing eagerly, or not adding/setting when it should?
Let me know if you want to pair.

I'm unsure this has fixed it, I still see this in density:
density : phet-io-input-record-and-playback-fuzzBoard : unbuilt
https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/phet-io-wrappers/input-record-and-playback/?sim=density&phetioDebug&fuzzBoard&supportsInteractiveDescription=true&wrapperContinuousTest=%7B%22test%22%3A%5B%22density%22%2C%22phet-io-input-record-and-playback-fuzzBoard%22%2C%22unbuilt%22%5D%2C%22snapshotName%22%3A%22snapshot-1647283977083%22%2C%22timestamp%22%3A1647288367354%7D
Uncaught Error: Uncaught Error: Assertion failed: A listener must be provided
Error: Assertion failed: A listener must be provided
at window.assertions.assertFunction (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/assert/js/assert.js:25:13)
at PDOMPointer.removeInputListener (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/scenery/js/input/Pointer.js:163:15)
at clearIntent (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/scenery/js/input/Pointer.js:367:14)
at Object.blur (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/scenery/js/input/Pointer.js:362:24)
at Input.dispatchToListeners (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/scenery/js/input/Input.js:1747:23)
at Input.dispatchEvent (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/scenery/js/input/Input.js:1702:10)
at Input.dispatchPDOMEvent (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/scenery/js/input/Input.js:1045:12)
at Input.focusoutAction.PhetioAction.phetioPlayback (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/scenery/js/input/Input.js:635:14)
at PhetioAction.execute (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/tandem/js/PhetioAction.js:90:17)
at PhetioAction.implementation (https://bayes.colorado.edu/continuous-testing/ct-snapshots/1647283977083/chipper/dist/js/tandem/js/PhetioAction.js:145:18)
id: Bayes Chrome
Snapshot from 3/14/2022, 12:52:57 PM

Any thoughts about this @jessegreenberg?

The fix in https://github.com/phetsims/scenery/commit/b7aa4f9e849f4ee352154918c54a6ab3221515c3 works for mouse/touch in reserveForDrag but there is a similar bit in reserveForKeyboardDrag causing the most recent assertion. I added this patch for testing
Index: js/input/Pointer.ts
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/js/input/Pointer.ts b/js/input/Pointer.ts
--- a/js/input/Pointer.ts	(revision b042a44c8d06c9861d86544e3eb3d871bc22d060)
+++ b/js/input/Pointer.ts	(date<PHONE_NUMBER>216)
@@ -30,6 +30,7 @@
 import { IInputListener, scenery, SceneryEvent, Trail } from '../imports.js';
 import IAttachableInputListener from './IAttachableInputListener.js';

+let counter = 0;
 export class Intent extends EnumerationValue {
   // listener attached to the pointer will be used for dragging
   static DRAG = new Intent();
@@ -381,13 +382,17 @@
       this.addIntent( Intent.KEYBOARD_DRAG );

       const listener = {
-        keyup: ( event: SceneryEvent<KeyboardEvent> ) => clearIntent(),
+        keyup: ( event: SceneryEvent<KeyboardEvent> ) => clearIntent( event ),

         // clear on blur as well since focus may be lost before we receive a keyup event
-        blur: ( event: SceneryEvent<FocusEvent> ) => clearIntent()
+        blur: ( event: SceneryEvent<FocusEvent> ) => clearIntent( event ),
+
+        count: counter++
       };

-      const clearIntent = () => {
+      const clearIntent = ( event: SceneryEvent ) => {
+        console.log( event.type, listener.count, event.target );
+        assert && assert( listener === this._listenerForKeyboardDragReserve, 'listener has already been cleared or another set' );
         this.removeIntent( Intent.KEYBOARD_DRAG );
         this.removeInputListener( this._listenerForKeyboardDragReserve! );
         this._listenerForKeyboardDragReserve = null;

And last logs before the assertion are

It is the same Tab in both console statements and the same count, which indicates it is the same listener trying to get removed twice.
Is it possible that PhET-iO is playing back duplicate blur or up events on a devensive copy of listeners?

@zepumph and I worked on this for a while today. The issue is around the blur event being dispatched twice in the downstream sim. But we identified that the workaround in https://github.com/phetsims/scenery/commit/b7aa4f9e849f4ee352154918c54a6ab3221515c3 had no impact on this issue so I reverted it.

Ahh beat me to the explanation! Thanks.

Over in https://github.com/phetsims/phet-io/issues/1854, we decided that we were no longer going to support playbacks with input events, so we are not going to work on this issue anymore. Closing


1 input file(s) are in error

https://bazelbuild.slack.com/archives/CA31HN1T3/p1677239867192349

Please add the relevant information in the issue here instead of pointing out to slack.

Stale


estimated fees - faq

What would you like to be added:
It should be added on all labels using Estimated fees:

Why is this needed:

Acceptance Criteria: When user hovers over Estimated fee i, definition should display
Android:

[ ] Send > Send DFI > Continue > Hover over Estimated fee i

[ ] Send > Send dBTC > Continue > Hover over Estimated fee i

[ ] Send > Send dETH > Continue > Hover over Estimated fee i

[ ] Send > Send dUSDT > Continue > Hover over Estimated fee i

[ ] DEX > Add dBTC-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Add dETH-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Add dUSDT-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Remove dBTC-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Remove dETH-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Remove dUSDT-DFI > Continue > Hover over Estimated fee i

iOS:

[ ] Send > Send DFI > Continue > Hover over Estimated fee i

[ ] Send > Send dBTC > Continue > Hover over Estimated fee i

[ ] Send > Send dETH > Continue > Hover over Estimated fee i

[ ] Send > Send dUSDT > Continue > Hover over Estimated fee i

[ ] DEX > Add dBTC-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Add dETH-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Add dUSDT-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Remove dBTC-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Remove dETH-DFI > Continue > Hover over Estimated fee i

[ ] DEX > Remove dUSDT-DFI > Continue > Hover over Estimated fee i

@izzycsy It should be click, there's no hover state on mobile


Movies Anywhere

Vizio recently added the Movies Anywhere app to SmartCast, is this something that can be added? I am trying to select it as a source using HASS.
Thanks.

Can you send me the app config? Launch the app then check the state of the media player in HASS and paste that here. I can use that information to add in native support.
You can also define this as an additional config here: https://www.home-assistant.io/integrations/vizio/#apps

Unfortunately the reason I was checking if I could launch this through my HASS integration is that I believe it was geo-restricted to the US and I am in Canada - I do have a US MoviesAnywhere account though.
Basically when the app was first added to SmartCast I received a notification on the home page which automatically launched the app which let me sign into my account and verify my PIN. However once I changed out of the app it was not available on the launcher for me to select again.
There are other apps I have on my Harmony remote that I can launch directly even though they are not on my SmartCast home screen, so I believe that as it let me log in initially if I could launch it with other means I could still use it.
Hopefully someone else with the update can provide the info to add the app. If I ever figure out a way back in I will grab the info from the location you specified.
Thanks for the info.

Got it, I would pull this for you if I could but I don't have a vizio tv. I also downloaded the latest SmartCast APK to see if there's a reference to Movies Anywhere but no such luck.
Good luck finding it!

Well, I was able to make some progress here. Turns out the SmartCast app gets the latest app list from http://hometest.buddytv.netdna-cdn.com/appservice/vizio_apps_prod.json and http://hometest.buddytv.netdna-cdn.com/appservice/app_availability_prod.json. Using that I found the following config for Movies Anywhere:
{"NAME_SPACE": 2, "APP_ID": "38", "MESSAGE": null } you should be able to add this to your config in HA to support this app. I will look separately into querying this list in HA so you don't have to configure it manually

Wow, thanks for digging in to this further.
I don't have a vizio section on my configuration.yaml at the moment as it was auto-discovered (I'm using the HaSS OS VM image). Is there a way to add this somewhere else without duplicating the existing device?

Not sure if this should be a separate issue, but with this newfound power to check these other apps I've been tinkering.
If I try to launch "CBS All Access" by selecting the associated Input, all I get is a black screen with a spinning circle. However, when I defined the CBS All Access manually as an additional_config in my configuration.yaml, it launches properly.
Does this maybe have to do with the country flag in const.py? Everything else looks the same, this is how I added it for testing:
        - name: CBSAA           config:             APP_ID: 37             NAME_SPACE: 2             MESSAGE: null

I can't explain why adding the app manually works but using the predefined one doesn't. What I can say is that in the files that I linked above, the config for CBS all access is different from whats in const.py (NAME_SPACE is 3 instead of 2). I plan on updating HA to pull those files and to use those instead of my static list which should make this functionality more future proof.

@YEGrolo the latest release of Home Assistant (0.115) should automatically fetch the latest app list. I say should because I can't be confident that I found the defacto source for this information, but hopefully I did

Theres certainly a huge list of apps in the Input list now so something is working. One that I noticed isn't in there though is the app for Apple TV - this was just added within the last week or two to Smartcast.

well crap. There must be another source then because the sources I found above do not have that app listed. I guess I will take another look later

FWIW, yesterday my TV was giving me an error for a while that it couldn't reach Vizio. I'm not sure I understand the issues going on but if you are getting inconsistent results it might be worth waiting and seeing if they are having problems again or still.

I'm definitely checking the right file. @YEGrolo can you find the Apple TV app in the Apps section of the SmartCast mobile app? It's possible that it's available on your TV but the app hasn't been updated yet, in which case pyvizio wouldn't be able to get it

I think you're right. It's on the TV but not in the app yet - app last updated in the Play store September 3rd. Will keep an eye out for it to show up. Separately it might be cool if there was some sort of notification when a new app/input is detected in the files you found.

I think this would be an abuse of the notification system so I am going to decline that suggestion. Since 0.115 has been released, I think this can be closed so doing so accordingly. Please re-open if you disagree


Tracing miss span context with transfer manager or thread executor

Describe the feature
Current implementation of tracing creates a span context from opentelemetry::context::RuntimeContext::GetCurrent()
This is a thread_local stack of previous span context.
When getting an object through the transfer manager or with GetObjectCallable or GetObjectAsync the span will be created from another thread than the one doing the request.
There is no way to link or give the right parent to the span created in S3Client::GetObject.
Could you provide a way to propagate the right context like opentelemetry propagator is doing between client / server with http headers?
Use Case
I can't correlate smithy tracing span in S3Client GetObject with my code
Exemple:
             main thread                                                   thread executor
| Span A |(application)
   | Span B | (TransferManager::DownloadFile)
                 | Span D | (Proccess Data)                           | Span C | (GetObject)

Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[X] This feature might incur a breaking change

Thanks for using this sdk and taking the time to open this feature request. We do want to add support for this, but this is not a high priority currently. I will make sure to update here when we add support


Fixed the issue preventing part.Exited from firing when a part is destroyed while inside the zone.

Nice job Argus! Thanks for your contributions. I'm aiming to complete a few issues myself next week so will hopefully have these deployed to main along with those. 👍
In response to your other questions: you're more welcome to submit a PR right-away for minor/easy-to-review changes like these.
This resolves #53

No problem. I had an assignment in one of my classes to contribute to an open source project, and this popped into a head. Thank you for the opportunity, hopefully I can continue to contribute in the future!


Reordering Tabs using drag and drop

I'm trying to enable reordering on Tabs using react-beautiful-dnd, but I can't manage to get it to work. No error appears but got a weird behavior when I drag. Here's an example code:
<DragDropContext onDragEnd={onDragEnd}>
    <Droppable droppableId="tabs" direction="horizontal">
        {props =>
         <Tabs
            ref={props.innerRef} {...props.droppableProps}
            value={this.state.index}
            onChange={this.handleIndexChange}
            variant="scrollable"
            scrollButtons="auto">
            {
                tabs.map(({ id, label }, index) => {
                    <Draggable key={id} draggableId={id} index={index}>
                        {props =>
                            <Tab ref={props.innerRef} {...props.draggableProps} {...props.dragHandleProps} label={label}/>
                        }
                    </Draggable>
            }
            {props.placeholder}
        </Tabs>
        }
    </Droppable>
</DragDropContext>

Is it possible to implement tab reordering with or without react-beautiful-dnd?

For how-to questions please use StackOverflow instead of Github issues. There is a StackOverflow tag called "material-ui" that you can use to tag your questions.
This helps us keep issues for... issues. :smile: Thanks!
(If as a result you identify an issue with Material-UI, feel free to open an issue using the appropriate template.)


Consider adding offset and length methods to serde_json::Error

As it stands, serde_json::Error includes the line number and column number of the start of an item whose parsing resulted in a parse error. This is great, but doesn't interoperate well with other things (in my case, miette) which expect a byte offset and byte length of the offending error.
Use case: I'm trying to wire up serde_json with miette to get prettier / clearer error messages in test code which tries to deserialize a variety of JSON files with a specific, fairly complex, schema.
The line and column numbers, in combination with the original program text, can be resolved into the initial byte offset, though the length then would require tokenization of the specific token at that byte offset.
Would it be possible for serde_json::Error to instead expose Error::offset and Error::length methods (names subject to bikeshedding)?

Aha! It turns out miette has some functionality to do what I need already. This may still be worth considering anyway, but my immediate use cases is resolved.


Fix inline fields

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

This PR started with a fix for just the radio component (description below), but I've found more related things to fix regarding form field inline label alignment.
The inline() API of the radio button form component currently also sets the label to be inline. This is unexpected, as the dedicated inlineLabel() API should control this. This PR updates the radio component to support non-inline label with inline radios. Visually this may be regarded as a breaking change, but to me this is a bug since the current result is unexpected.
Before

After

I'm concerned as the inline() method for checkboxes does add them inline with the label, hence why it was like this before. I think this is too much of a breaking change tbh

I'm concerned as the inline() method for checkboxes does add them inline with the label, hence why it was like this before. I think this is too much of a breaking change tbh

For single checkboxes it makes sense as is, but checkbox lists (which are the checkbox counterpart of radios) don't have the inline() API.
I understand your concern regarding the change being breaking. Though we should add a temporary API to allow for the right behavior introduced by this PR, because the new behavior is in fact what it should have been all along (also check Tailwind UI for example: https://tailwindui.com/components/application-ui/forms/radio-groups#component-f77fa2476964716cd375c934954229ae).

Removed the BC by calling inlineLabel() from inline() conditionally. To revert that, you just to inline()->inlineLabel(false) which I think makes sense.

Yup, good workaround. Where do we document this change so we can remove it in v4, @danharrin?

I don't think we should remove it in v4 IMO, this behaviour is useful as it allows you to put a radio next to a checkbox/toggle without consuming extra height

Well, it should be enabled explicitly. Just making the radios inline shouldn't make the label inline. Using ->inline()->inlineLabel() should be used explicitly.


Natural analogue is mandatory but misses a star

In the monomer page, when adding a new RNA monomer, the natural analogue is mandatory but there is no red star next to title.

It is mandatory for RNA, and Peptide, but not for CHEM.

Difficult to find a better alternative solution since it is only mandatory in some circumstances. Close.

My mistake - it is mandatory, so a star needs to be in place.

Star now present. Close.


Module Metadata Framework

Create Metadata class. Acts as a service for all the metadata stored in and read from metadata.json
Create metadata.json. Contains all the metadata fed to modules at their creation, of which there's the module's name, version, description, and ReleaseState.
Create IDocumented. Ensures every module has fields that take fields from that module's corresponding ModuleMetadata entry in the json.
Create ReleaseState. A module's ReleaseState can be Canary (not in master, or not production ready), Beta (master, but whitelisted, preferably for testing), and Stable (fully public).
Add Metadata class to the service collection. So it, you know, does stuff.

Need changes


"Add to BitBar" button on getbitbar.com doesn't work if app not open

If the app isn't running, clicking "Add to BitBar":

Open the app
Does NOT popup the install box

It should

Open the app
Popup the install box as normal

Possible fix: http://stackoverflow.com/a/2080974


RFC 8445

According to the readme, aioice is based on RFC 5245. There is now RFC 8445 that obsoletes RFC 5245: https://datatracker.ietf.org/doc/html/rfc8445#section-21
I am not very familiar with the codebase of aioice or ICE in general, but I didn't see a mention of the new RFC anywhere and thought that it's something that needs to be tracked.

AFAICT the main change is that "aggressive" nomination is deprecated, and only "regular" nomination should be used. This would mean reworking some of aioice's code. A PR is most welcome!


Fix asset precompile for productization

Fixes 2 issues related to precompile assets for productization, and removes obsolete code.  Worked with @Fryguy

The "productization" directory was being added to the assets path too early. Needed to wait until all other paths get loaded.  Replaces #7030

Some of the images in the productization weren't being precompiled.  Needed to add them to the precompile list.

Wow, less is more. Does that rails hook run when we want? :clap:

@jrafanie yes, looks like that hook is what we needed.  Tested with and without productization and got correct files precompiled for both cases :smiley:

LGTM


formData object does not have methods

I wanted to use the formData in my React Native Application to send a file. The code to do this is really simple:
import FormData from 'form-data';

const uploadFile = ()=> {
    const form = new FormData();
    console.log('headers', form.getHeaders()) // Will throw TypeError: form.getHeaders is not a function
}

form.append works.
when I console.log(form) I get this:
FormData_parts: (8) [Array(2), Array(2), Array(2), Array(2), Array(2), Array(2), Array(2), Array(2)]__proto__: Object

Apparently Everything is saved under the _parts and as an Array.
when I console.log(FormData) I get this:
ƒ FormData() {
      _classCallCheck(this, FormData);

      this._parts = [];
    }

I get the same issue when I am trying to use other functions like form.getBoundary()
I have been stuck for 3 days now. I don't know where is the problem

This is not an issue! I found out it work this way.

@mohammedSlimani What did you do to get it to work? I am running into this issue today and have been for a while.

@rizowski  try to stringify the nested objects that you have inside your data form. For me it was a nested location object, once I did that it worked well!


pull request

HI, could you provide a description of what this fixes and why we might want it ? It looks like it is just a custom build that works for you or is there more to it than that ?


Updates the block-related types in the Byron era chain spec

This patch both updates block-related types and provides a few new classes for interfacing with the consensus layer.
Closes #238.

I folded everything to BlockHeader.

@nc6 , @edsko : it's been a while since anything happened here, but it'd be great if I could make progress with this one. The PR is blocked and I have no clue what the BHToSign type is.

@edsko, do you think this is OK now? The main thing is in [https://github.com/input-output-hk/fm-ledger-rules/pull/239/files#diff-21890a40677adda3a137e87a3b0758f5]
(Cardano.Spec.Consensus.Block).
Damian already approved this. If it looks OK to you, I'll remove Nicholas' request for changes as I've addressed them and he's been on a vacation, yet his request is blocking this PR from getting merged.

@mdimjasevic Feel free, don't hold back on my account, as I'm not really involved with the design of this on your side. We'll found out soon enough if it's now general enough when you start the integration work again.


Image should include everything that is needed to build

I like to use docker as by build tool, so I don't have to install anything. It also makes it super easy for other people to build your stuff.
Also, I'm NOT a fan of building inside the same container, that you will ship.
I'd therefore suggest that you include (or provide an alternative image) that includes Git (and whatever else is typically needed for a build).

Makes sense- I was installing git on top of this image but it should be included since Swift's package manager uses it.


Add Valid Analog Problem Solution

Problem Name: Valid Anagram
Description
Given two strings s and t, return true if t is an anagram of s, and false otherwise.
An Anagram is a word or phrase formed by rearranging the letters of a different word or phrase, typically using all the original letters exactly once.
Example 1:
Input: s = "anagram", t = "nagaram"
Output: true
Example 2:
Input: s = "rat", t = "car"
Output: false
Hey @Kumar-laxmi , I want to add the solution of valid anagram problem, so please asign it to me under SSOC'23

Assigned!
@shubhanshurav C, C++, Java & Python

@Kumar-laxmi Thanks for assigning me.


Workflows / CI: fixed & refactored

Fixed

Ruby 2.6 (see hotwired/turbo-rails/issues/681).

Changed

Moved Rails versions to CI matrix.
Both edge and outdated Ruby / Rails versions may fail.
Use the latest RubyGems.

LGTM!

I'm sorry, but another approval is needed due to suggested modifications made.


Password Label tailwind style loss on customizing change_form template

As described, the password field label will lose it's class when customizing change_form of User object, because nor the widget neither the template start with unfold.
I've customized the password field by overidding the PasswordInput widget class into UnfoldPasswordInput class without doing anything but pass.
The same style loss happens FilteredSelectMultiple class.
So what is the purpose for the original design for this check:?
https://github.com/unfoldadmin/django-unfold/blob/0501bbf45f3db9159f011097b767a93ed5a36fe7/src/unfold/fields.py#L178-L181
if not self.field.field.widget.class.name.startswith(
"Unfold"
) and not self.field.field.widget.template_name.startswith("unfold"):
return super().label_tag()

The reason for this condition is to ensure that proper styles are applied only when Unfold is used because you can have default admin running in parallel where we don't want to apply Unfold styles.

Appriciate your answer! Is there any better way to sustain the styles other than rewrite the widget class with Unfold title?

Unfortunately, I was not able to find an elegant way how to do it. I guess it would be possible to achieve such a solution but when I was looking at it, I would be required to override tons of business logic which I'm trying to avoid as much as possible.


Development

Before submitting a pull request, please make sure the following is done:
Fork the repository and create your branch from master.
Run npm in the repository root.
If you've fixed a bug or added code that should be tested, add tests!
Ensure the test suite passes (npm test). Also you can launch tests using "Extension Tests" vscode task.
Thanks!

Codecov Report

Merging #33 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   99.47%   99.47%
=======================================
  Files           8        8
  Lines         191      191
  Branches       22       22
=======================================
  Hits          190      190
  Misses          1        1

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 45ee766...8c54a6c. Read the comment docs.


flutter build web command only copy .html file.

I have external .js files used in my web project and when I build for release, they're never copied to the build folder.
My web folder:

My build/web folder:

I'm pretty sure it used to work before the merge of web in master. Am I missing something?
Flutter version: Flutter 1.13.3-pre.67

Hi @obshksw
can you please provide your updated  flutter doctor -v
and your flutter build --verbose?
Also, to better address the issue, would be helpful
if you could post  a minimal code sample
or the steps to reproduce the problem.
Thank you

Flutter (Channel master, v1.13.3-pre.83, on Microsoft Windows [Version 10.0.17763.914],
    locale en-US)
    • Flutter version 1.13.3-pre.83 at C:\dev\flutter\flutter
    • Framework revision 78db965642 (4 hours ago), 2019-12-19 11:23:01 +0100
    • Engine revision 0f90e6546b
    • Dart version 2.8.0 (build 2.8.0-dev.0.0 aa6709974d)

λ flutter build web --verbose
[  +22 ms] executing: [C:\dev\flutter\flutter\] git -c log.showSignature=false log -n 1
--pretty=format:%H
[  +72 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 78db9656424768d71b363f3365fa5637b3a3fa49
[        ] executing: [C:\dev\flutter\flutter\] git describe --match v*.*.* --first-parent --long--tags
[  +71 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.13.2-83-g78db96564
[   +6 ms] executing: [C:\dev\flutter\flutter\] git rev-parse --abbrev-ref --symbolic @{u}
[  +51 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] executing: [C:\dev\flutter\flutter\] git ls-remote --get-url origin
[  +49 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +86 ms] executing: [C:\dev\flutter\flutter\] git rev-parse --abbrev-ref HEAD
[  +53 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] master
[  +45 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[   +9 ms] Artifact Instance of 'MaterialFonts' is not required, skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required, skipping update.
[        ] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required, skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not required, skipping update.
[ +251 ms] Generating
c:\dev\SVI\live_app\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[ +111 ms] Generating
c:\dev\SVI\live_app\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +12 ms] Compiling lib\main.dart for the Web...
[   +8 ms] Initializing file store
[  +17 ms] Done initializing file store
[  +76 ms] Skipping target: web_entrypoint
[+1724 ms] Skipping target: dart2js
[  +78 ms] web_release_bundle: Starting due to {InvalidatedReason.outputMissing}
[ +133 ms] web_release_bundle: Complete
[+1778 ms] Persisting file store
[  +16 ms] Done persisting file store
[  +12 ms] Compiling lib\main.dart for the Web... (completed in 3.8s)
[   +3 ms] "flutter web" took 4,351ms.

And well there's no code or any particular steps except what's mentioned in the title... I just do flutter build web and it results in missing files in my build folder...

I took the time to test something else:

flutter create test_project
add a .js file to the web folder
flutter build web

Notice that the .js file is not copied to the build/web folder although the .html is.

/cc @jonahwilliams : Is it possible to add .js assets in pubspec?

@ferhatb
Yes it works that way but the problem is that they would be included for the native builds, which I don't want.
Unless there's a way to specifiy a platform for the assets in the pubspec?

This was done by https://github.com/flutter/flutter/pull/48316

Awesome, thank you! :)


FileManager directory creation doesn't call to subclasses

The file manager implementation needs to call the fileManager variable when calling other FileManager functions instead of using self in order to call down to an overriden subclass implementation if present. I accidentally used self instead of fileManager in one instance which resulted in subclasses experiencing different behavior with this swift implementation of FileManager. I'll followup with a future change to make this mistake harder to create by potentially renaming the internal functions to be different than the public API functions.

@swift-ci please test


Outdated page number

Hello!
There's a hardcoded page number reference that has become outdated:
https://github.com/riscv/riscv-isa-manual/blob/2f2f75dbc4160cb6cef22267bc133ca5aa6ac4c0/src/hypervisor.adoc?plain=1#L182
Current situation:

The line references "page 19" for a specific table.
The table is now actually on page 24.

I don't know if there is a way of dinamically linking pages based on a specific element (like a table) or if it is just better to remove the page reference since I believe this will keep getting outdated with  ISA manual revisions.

Hardcoded page numbers are a definite no-no.  If you see more of these, feel free to keep filing issues (or PRs to fix them).  In this case, the <<misabase>> link suffices, and we can just delete the page number.


Numpy reshaping added to rospc_to_o3dpc

open3d.utility.Vector3dVectory expects an input of shape (n, 3) http://www.open3d.org/docs/release/python_api/open3d.utility.Vector3dVector.html#open3d-utility-vector3dvector
Tested this locally and it works. Was giving a "bad callback" runtime error before the change.

Thank you for your contribution! I'll test it and update the PyPI soon.


Smoke test 1.2

Description
Adds a scripted smoke test for Data Prepper docker images
Issues Resolved
[List any issues this PR will resolve]
Check List

[x] New functionality includes testing.
[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

:exclamation: No coverage uploaded for pull request base (1.2@8a8a0dd). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 769c2ad differs from pull request most recent head fd04aee. Consider uploading reports for the commit fd04aee to get more accurate results

@@          Coverage Diff           @@
##             1.2     #702   +/-   ##
======================================
  Coverage       ?   91.49%
  Complexity     ?      586
======================================
  Files          ?       74
  Lines          ?     1788
  Branches       ?      148
======================================
  Hits           ?     1636
  Misses         ?      116
  Partials       ?       36

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 8a8a0dd...fd04aee. Read the comment docs.

Thanks for putting this together!
I tried running the script. Unfortunately, it kept reporting Waiting for Data Prepper to start.
The containers appeared to be running:
$ docker ps                                                                                [14:49:05]
CONTAINER ID   IMAGE                                   COMMAND                  CREATED         STATUS                          PORTS                                                                     NAMES
f3d476e2676d   smoke-tests_otel-span-exporter          "/bin/sh -c 'python3…"   5 minutes ago   Restarting (0) 54 seconds ago                                                                             smoke-tests_otel-span-exporter_1
360db2978df1   otel/opentelemetry-collector:0.40.0     "/otelcol --config=/…"   5 minutes ago   Up 5 minutes                    <IP_ADDRESS>:4317->4317/tcp, :::4317->4317/tcp, 55678-55679/tcp                smoke-tests_otel-collector_1
b012352c7593   opensearchproject/data-prepper:latest   "/bin/sh -c 'java $J…"   5 minutes ago   Up 5 minutes                    <IP_ADDRESS>:2021->2021/tcp, :::2021->2021/tcp                                 smoke-tests_data-prepper_1
539741e51931   opensearchproject/opensearch:1.0.0      "./opensearch-docker…"   5 minutes ago   Up 5 minutes                    9300/tcp, 9600/tcp, <IP_ADDRESS>:9200->9200/tcp, :::9200->9200/tcp, 9650/tcp   node-0.example.com
3b5b1f974174   alpine                                  "/bin/sh -c 'set -x;…"   5 minutes ago   Up 5 minutes                                                                                smoke-tests_http-log-generation_1

@dlvenable if all containers are up an running try these two curls:
curl -k -u 'admin:admin' 'https://localhost:9200/_cat/indices'
curl -k -H "Content-Type: application/json" -d '[{"log": "smoke test log "}]' 'http://localhost:2021/log/ingest'

These are use by the script to confirm the open search API and Data Prepper HTTP source are responding

@dlvenable updated to target main


Increase requested stories in dashboard

Feature Description
Currently only 10 stories are being requests when dashboard is requested. This means lots of waiting scrolling. The api allows for 100 items to be requested in a simple request. This should used to making scrolling smoother.
Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

the count per request was updated to 20 items this week. I'd opted for less than the max to prevent grabbing more data than we need at once. Am happy to adjust this further.
@o-fernandez thoughts?

^^ @o-fernandez friendly nudge on this just so we can keep the board clean.

For the record the max is 100. 20 is not much more than the existing 10. Why get the full amount? Or at least half, say 50?

My only hesitation to set it to the max is you're really never going to be looking at 100 stories at once, so why not grab them as we need them to avoid excess data. Happy to split the difference. Mostly just think either way this ticket is easy to solve and it'd be nice to get it off the board!

We load 100 items in the media library and there is very little chance a user will see all of them.  For example, I have a monitor that is portrait and 20 is not enough. I think it is better to overload data and have a little more data than you need than give some users a bad experience. From a WordPress stand point, the response time should be that different at all.

Ok, i will update to 100.

Thanks for this update, but I think this may have been a disservice (as @BrittanyIRL feared) because the full page load time is now taking long... I'm on a fast network and here are the stats from a full page load of the dashboard for our dashboard.
161 requests
50.9 MB transferred
58.6 MB resources
Finish: 5.44 s
DOMContentLoaded: 625 ms
Load: 661 ms
With cache enabled it's a little better at 4.3 seconds, but it still feels laggy.
There's probably opportunity to do code optimizations and refactoring to make this snappier and keep the 100 results, but I think we should start by reducing the number of results to see how the end to end looks and aim to get to a page load of p95 <3s (ideally <1s, but for this page I think aiming for <3s for now is fine).
Brittany, I'm sorry for the back and forth, but is it possible for you to test what the end-to-end page load time (on an adequate network) is if you set this to 24 results or 60 results?
I'm thinking we'd do one of those (24 or 60) so that way you get full rows of results for screens that display 2, 3, or 4 results across, so you don't get the odd last row that doesn't have incomplete results even if there are more stories.

No worries! I'll do some testing and get back to you. Moving this back to in progress.

@o-fernandez can you review the PR description from this update here and confirm that this update is ok for now?
Ultimately, this is a bandaid for some perf issues with loading the data and time to first paint.
https://github.com/google/web-stories-wp/pull/2789

Looks good! Given your findings, it seems that 24 is a reasonable load.

Tested in QA and this is way better, I'm at 1.89s. You can probs merge this and I'll do a UAT testing in master. :)

Awesome, thanks for jumping on this so fast - glad to get this merged!


newer packages are required for the async example to run

Thanks for the PR!
To better assist you, please select the type of PR you want to create.
Click the "Preview" tab above, and click on the link for the PR type:

:bug: Bug fix or new feature

Thanks!

Nothing wrong with bumping deps here, but I have to say I'm not sure why "newer packages are required to run".

Nothing wrong with bumping deps here, but I have to say I'm not sure why "newer packages are required to run".

the npm install was giving out some errors and stating some vulnerabilities and the app could not be started.

What specific "errors" were you seeing?

What specific "errors" were you seeing?

I just did a git checkout first and then npm i:
$ git co a6823aa8c452079abbe5c55aaef0203abbc435fc
$ npm i

><EMAIL_ADDRESS>install /Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.8/fse-v1.2.8-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v72 ABI, unknown) (falling back to source compile with node-gyp)
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
../fsevents.cc:43:32: error: no template named 'Handle' in namespace 'v8'
    static void Initialize(v8::Handle<v8::Object> exports);
                           ~~~~^
In file included from ../fsevents.cc:73:
../src/constants.cc:89:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagNone").ToLocalChecked(), Nan::New<v...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:90:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagMustScanSubDirs").ToLocalChecked()...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:91:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagUserDropped").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:92:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagKernelDropped").ToLocalChecked(), N...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:93:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagEventIdsWrapped").ToLocalChecked()...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:94:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagHistoryDone").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:95:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagRootChanged").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:96:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagMount").ToLocalChecked(), Nan::New<...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:97:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagUnmount").ToLocalChecked(), Nan::Ne...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:98:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemCreated").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:99:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemRemoved").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:100:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemInodeMetaMod").ToLocalChecked()...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:101:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemRenamed").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:102:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemModified").ToLocalChecked(), Na...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:103:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemFinderInfoMod").ToLocalChecked(...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:104:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemChangeOwner").ToLocalChecked()...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:105:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemXattrMod").ToLocalChecked(), Na...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:106:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsFile").ToLocalChecked(), Nan:...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:107:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsDir").ToLocalChecked(), Nan::...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:108:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsSymlink").ToLocalChecked(), N...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
../fsevents.cc:76:16: error: variable has incomplete type 'void'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
               ^
../fsevents.cc:76:31: error: no member named 'Handle' in namespace 'v8'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                          ~~~~^
../fsevents.cc:76:48: error: expected '(' for function-style cast or type construction
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                     ~~~~~~~~~~^
../fsevents.cc:76:50: error: use of undeclared identifier 'exports'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                                 ^
../fsevents.cc:76:58: error: expected ';' after top level declarator
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                                         ^
                                                         ;
20 warnings and 6 errors generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 18.7.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node" "--module_name=fse" "--module_path=/Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72"
gyp ERR! cwd /Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents
gyp ERR! node -v v12.14.0
gyp ERR! node-gyp -v v5.0.7
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node --module_name=fse --module_path=/Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64 --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
node-pre-gyp ERR! System Darwin 18.7.0
node-pre-gyp ERR! command "/usr/local/bin/node" "/Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents
node-pre-gyp ERR! node -v v12.14.0
node-pre-gyp ERR! node-pre-gyp -v v0.12.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node --module_name=fse --module_path=/Users/username/code/redux/examples/async/node_modules/chokidar/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64 --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)

><EMAIL_ADDRESS>install /Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.8/fse-v1.2.8-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v72 ABI, unknown) (falling back to source compile with node-gyp)
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
../fsevents.cc:43:32: error: no template named 'Handle' in namespace 'v8'
    static void Initialize(v8::Handle<v8::Object> exports);
                           ~~~~^
In file included from ../fsevents.cc:73:
../src/constants.cc:89:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagNone").ToLocalChecked(), Nan::New<v...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:90:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagMustScanSubDirs").ToLocalChecked()...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:91:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagUserDropped").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:92:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagKernelDropped").ToLocalChecked(), N...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:93:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagEventIdsWrapped").ToLocalChecked()...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:94:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagHistoryDone").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:95:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagRootChanged").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:96:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagMount").ToLocalChecked(), Nan::New<...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:97:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagUnmount").ToLocalChecked(), Nan::Ne...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:98:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemCreated").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:99:11: warning: 'Set' is deprecated: Use maybe version [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemRemoved").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:100:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemInodeMetaMod").ToLocalChecked()...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:101:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemRenamed").ToLocalChecked(), Nan...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:102:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemModified").ToLocalChecked(), Na...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:103:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemFinderInfoMod").ToLocalChecked(...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:104:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemChangeOwner").ToLocalChecked()...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:105:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemXattrMod").ToLocalChecked(), Na...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:106:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsFile").ToLocalChecked(), Nan:...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:107:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsDir").ToLocalChecked(), Nan::...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:108:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsSymlink").ToLocalChecked(), N...
          ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8.h:3402:3: note: 'Set' has been explicitly
      marked deprecated here
  V8_DEPRECATED("Use maybe version",
  ^
/Users/username/Library/Caches/node-gyp/12.14.0/include/node/v8config.h:311:29: note: expanded from macro
      'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
../fsevents.cc:76:16: error: variable has incomplete type 'void'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
               ^
../fsevents.cc:76:31: error: no member named 'Handle' in namespace 'v8'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                          ~~~~^
../fsevents.cc:76:48: error: expected '(' for function-style cast or type construction
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                     ~~~~~~~~~~^
../fsevents.cc:76:50: error: use of undeclared identifier 'exports'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                                 ^
../fsevents.cc:76:58: error: expected ';' after top level declarator
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                                         ^
                                                         ;
20 warnings and 6 errors generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 18.7.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node" "--module_name=fse" "--module_path=/Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72"
gyp ERR! cwd /Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents
gyp ERR! node -v v12.14.0
gyp ERR! node-gyp -v v5.0.7
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node --module_name=fse --module_path=/Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64 --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
node-pre-gyp ERR! System Darwin 18.7.0
node-pre-gyp ERR! command "/usr/local/bin/node" "/Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents
node-pre-gyp ERR! node -v v12.14.0
node-pre-gyp ERR! node-pre-gyp -v v0.12.0
node-pre-gyp ERR! not ok
Failed to execute '/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node --module_name=fse --module_path=/Users/username/code/redux/examples/async/node_modules/jest-haste-map/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64 --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: `node install`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/jest-haste-map/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: `node install`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

added 1403 packages from 760 contributors and audited 878640 packages in 29.708s
found 16310 vulnerabilities (3 moderate, 16306 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

Yeah, none of that has anything to do with Redux or React-Redux.  That looks like some OS-specific dependency isn't building right on your machine.
Again, not saying that updating the deps is bad.  Just that there was no actual real issue that had to do with the example package that needed to be solved.

Yeah, none of that has anything to do with Redux or React-Redux. That looks like some OS-specific dependency isn't building right on your machine.
Again, not saying that updating the deps is bad. Just that there was no actual real issue that had to do with the example package that needed to be solved.

is that right.  I then did npm update and then everything started working... not sure why the newer versions worked.


Menu: adding seperator between the list items

Environment

Package version(s):0.13.1

In itwin.bentley.con or plansight , a typical header dropdown has seperator(s)  in the menu:

I couldn't find any styling for it in ITwinUI.

iui-menu-divider is now available in 0.24.0 🎉


General: Improve Cheatsheet experience

Hi, I've been working on CheatSheets for Python and R. To present the work itself, I have used these tools:

google colab: to replicate the experiment in the cloud
streamlit: to interactively display the CheatSheets codes in pdf format
pdf: the classic way to display a CheatSheets

My job is looks like this:

Topic
PDF
Streamlit
Google Colab

dplyr

ggplot2

forcats

Note: The PDF format cheat sheets included here are authored by other contributors and have been used as sources of inspiration for the content presented.

I would like to see if this experience with CheatSheets can be done with a tool like Binder  or Posit Cloud (instead of Google Colab) and Shiny (instead of streamlit). I will be investigating to help with some of these points.

Note: Complete documentation about my work can be found at this link.

Thanks for sharing this. At this point we don't plan on an interactive experience for the cheatsheets however setting up the cheatsheets to open in Binder and/or Posit Cloud should be doable.


Add the first favicon

What?
This PR adds the simplest version of favicon.
We are using this package (https://github.com/expressjs/serve-favicon) that was extracted from express in the past.

This PR fixes https://github.com/ResultadosDigitais/matrix/issues/79


Refine trust system actions for staged ledger errors

PR #2372 invokes the trust system for staged ledger errors, in Transition_frontier.Breadcrumb.build.
As written, two errors have the Violated_protocol actions, the rest have Gossiped_invalid_transition.
These distinctions could be made finer, if needed.

Before merging, we added actions Sent_invalid_proof and Bad_signature.