iNelsForHass is not working on HA version 2023.5

Hi Jirka,
your integration of INELS isn't loaded properly after Home Assistant update to 2023.5 version.
I can prove that everything works flawlessly under HA 2023.4.

Hi Adam,
I already made fix for this issue early this morning.
Try it and give me a feedback, please.
Kind regards
JH
Dne pá 5. 5. 2023 14:31 uživatel Adam Košík @.***>
napsal:

Hi Jirka,
your integration of INELS isn't loaded properly after Home Assistant
update to 2023.5 version.
I can prove that everything works flawlessly under HA 2023.4.
[image: image]
https://user-images.githubusercontent.com/75278121/236458069-05877e30-32d0-45d8-a33f-bbc437d1a11b.jpeg
—
Reply to this email directly, view it on GitHub
https://github.com/JH-Soft-Technology/InelsForHass/issues/9, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6ZWNPW2GPJVFN4QCXDQ5LXETXLLANCNFSM6AAAAAAXXBYBSA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Yeah, after fix update everything works like a charm.
Great work Jitka.
Thank you.


Add hooks imports

Very nice extension. Just started using it but it seems very functional 👍
I would really like to have imports when using hookW (and probably the others but I haven't used them yet.)
import 'package:flutter/material.dart';
import 'package:flutter_hooks/flutter_hooks.dart';

Hi @Hauglid, Thanks for opening this issue and I apologies for being too late to respond to this matter.
Actually, it a very good idea I mean why not, I'll start adding them and once I finish it..  I'll let you know here, I'm gonna let this one open until I release a version with the enhancements you mentioned above.
Again, Thanks for making things awesome mate!

Hi @Hauglid,
Flutter hooks imports have been added in v0.0.5, you can update the extensions and start using it.


MPI-ESM1-2-HAM-tasmax.yaml because cannot parse parameters file as JSON list

Looks like the parameter file is screwy, from running in workflow https://argo.cildc6.org/workflows/default/e2e-tasmax-jobs-kz947.
Argo throws the message:
withParam value could not be parsed as a JSON list: [ { "target": "historical", "variable_id": "tasmax", "historical": { "activity_id": "CMIP", "experiment_id": "historical", "table_id": "day", "variable_id": "tasmax", "source_id": "MPI-ESM1-2-HAM", "institution_id": "HAMMOZ-Consortium", "member_id": "r1i1p1f1", "grid_label": "gn", "version": "20190627" }, "ssp": { "activity_id": "ScenarioMIP", "experiment_id": "ssp370", "table_id": "day", "variable_id": "tasmax", "source_id": "MPI-ESM1-2-HAM", "institution_id": "DKRZ", "member_id": "r1i1p1f1", "grid_label": "gn", "version": "20190628" } }, { "target": "ssp", "variable_id": "tasmax", "historical": { "activity_id": "CMIP", "experiment_id": "historical", "table_id": "day", "variable_id": "tasmax", "source_id": "MPI-ESM1-2-HAM", "institution_id": "HAMMOZ-Consortium", "member_id": "r1i1p1f1", "grid_label": "gn", "version": "20190627" }, "ssp": { "activity_id": "ScenarioMIP", "experiment_id": "ssp370", "table_id": "day", "variable_id": "tasmax", "source_id": "MPI-ESM1-2-HAM", "institution_id": "DKRZ", "member_id": "r1i1p1f1", "grid_label": "gn", "version": "20190628" } }, ]: invalid character ']' looking for beginning of value

I got this. I think it's a simple formatting error. I'll get a PR up ASAP.


Add 1.9.2/2.0/2.1 to travis test matrix.

It's not clear if there was a reason to exclude these rubies... either way, I thought it was worth a try to see if we wanted to add them to the matrix.
I assume since we support 1.8.7 in travis, we probably should be testing 1.9.2.

@kbrock please review, thanks!


[Bug]: The slide bar in the about page is entirely black and unreadable. [GSSoC'23]

What happened?
I found a BUG 🐞
In the about page of the website, when you open the slide bar. The slide bar is entirely black and unreadable.
Add screenshots

What browsers are you seeing the problem on?
Chrome
Code of Conduct

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

@1Shubham7 this issue is duplicate and has been assigned to someone else, if he fails to do it Then you will be assigned

But I solved it locally.

I just had to push. Now what should  I do? wait ?

Please do let me know what to do?


Custom config?

I was looking at this package to replace a custom solution. Are you planning on creating a default config to show people how to create mappings?

I guess it does make sense to add the default config for demo. I'll add it tomorrow.

@matchish I got this package working nicely on one of my projects! Thank you! The zero downtime is nice as well!

Thank you too) I've add default config to config branch. It passing all tests but I'm not ready to merge it to master right now.

It's not a problem for me. I just thought it would be nice for others that don't know elastic search.


Quick Question

First of all thank you so much for this! Have you tested this lately?

I have, and it works great. It stops you from getting banned by vacs automated server from what i understand, and from practise. But be warned you CAN still get overwatch banned, so don't be blantant, and dont hack with your main account.

Very cool.Thanks!

testing it more than half year and it works great


question about KCV 4.2.4

1-its just me or KCV 4.2.4 load very slow?
i tessed my net on IE its seem having no problem,
but inside KCV its takes allmost like 10~15min to fully load.
that not include the loading each battle/tab takes 10sec longer than normal.
2-is there any plugins that 4.2.4 can show the droplist and construction log? like ver3.8.2r557
or i missed something since its in JAP language, plz do teach me about it.

I have no idea why it is slow for you.
You can switch it to English. There is a logger plug-in bundled with KCV.
You can use 3.8.2r562 from gakada.

(Also before reporting issues with slow loading etc. please test with Grabacr's original build first.)

allright, thx for advice, did 3.8.2r562 from gakada can use for the new april issue?
last time i using  ver3.8.2r557 but no update and no information about my fleet open up due to new API

oh yea, any quick link for gakada work? that gona be a big help

Have you tried, you know, his repository? I mean, it's probably impossible to find but still.

was looking for gakada works till now..
for now..hahaha.... i try to find em in serchbar but nothing comeout..lol that y.
btw, thx for the help Yuu


error: responsive grid community

Description
the grid with the apps in the community section is breaking. I left a recording of the screen down:

http://upload-gifs.s3-sa-east-1.amazonaws.com/da13a556-35da-4bfb-8c3d-c6bd23233538_before-rn-website.gif


Add SKOS properties   CR 10-16

Description of the change: (free-text)
For all of the subject, place, people, organization and object objects within ninjs, we should add the SKOS relationships:
https://www.w3.org/TR/skos-primer/#secrel
broader (which I already asked for in http://dev.iptc.org/ninjs-CR-10-11-More-subject-properties)
narrower
related
And we shouldd add the "Concept Mapping" properties from SKOS:
https://www.w3.org/TR/skos-primer/#secmapping
exactmatch
closematch
broadmatch
narrowmatch
relatedmatch
I guess that, in keeping with the spirit of SKOS we should make these properties arrays of URIs.

JAYSON:
Hmmm this seems like overkill to me, but then we do not use SKOS properties :) It will be interesting to see other's responses to this one


autocorrect: init at 2.6.2

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@JulienMalka I fixed it
thanks

@candyc1oud why are you closing this ?

@candyc1oud why are you closing this ?

@JulienMalka Sorry, you haven't replied to me for so long that I thought you didn't care about this PR

@JulienMalka Sorry, you haven't replied to me for so long that I thought you didn't care about this PR

@candyc1oud it is not for me to care or not care about this PR, we are a whole team of people that give some of their time to review all PRs on Nixpkgs (there is a lot of them) and to try to bring all of them in a mergable state if possible. Sometimes this process is long we often are only doing this on our free time. You have to be patient. If you feel that your PR is good to be merged, you can ping a reviewer or you can try to post it on the discourse, there is a subject "PR ready for review".

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1867


Added missing include of  for std::accumulate

On gcc6.2 std::accumulate is not found due to a missing include. This commit fixes this.

Thanks for correction!


Add the text "my changes" to article.

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi @ezioda004, I think you forgot to mark this PR invalid.


require pathname in simplecov-lcov.rb instead of spec_helper.rb

We should require 'pathname' where Pathname is actually used to avoid errors like:
Formatter SimpleCov::Formatter::LcovFormatter failed with NameError: uninitialized constant Class::Pathname (simplecov-lcov-0.4.0/lib/simplecov-lcov.rb:41:in `single_report_path')

Coverage decreased (-50.0%) to 50.0% when pulling ae122c91921ee042f551f2596cddfe302a9c81b8 on chilicheech:pathname into 7dd122a891415e9da29ec8fc07ed566142bcc54e on fortissimo1997:master.

Coverage remained the same at 100.0% when pulling dbb2db357cb7ef26fb60f364416e5bb65731c56f on chilicheech:pathname into 7dd122a891415e9da29ec8fc07ed566142bcc54e on fortissimo1997:master.

:+1:


Add AccessibilitySnapshotColorBlindness to package

Hey Nick 👋
Leaving this as draft, as it's entirely up to you whether you think this is valuable within the scope of this project.
While maybe (for some) not as helpful as the core VoiceOver capability this project offers, colour blindness simulation can still be an important part of some team's accessibility reviews. This is where my project was born from.
Having now validated the capability, I wanted to see what you thought about making this an optional component of this project. Users would have to explicitly opt-in to include this subspec/target in their project, but having accessibility snapshots of all forms under a single umbrella seems like a good vision to have.
Let me know what you think, and as always feel free to decline if you'd rather keep them separate!

I think this functionality is a great addition! But I would actually add this to the existing modules, rather than as a separate subspec. While most of the framework focuses on VoiceOver (as well as covering most of Switch Control), there's already prior art for supporting other features like Invert Colors.
The best approach here is probably to add the filter logic to the core subspec and then create interfaces for using it in tests in the subspecs for the two snapshotting engines.

@Sherlouk Are you still interested in working on this one? I can take over the PR if you don't have time right now.

Thanks Nick, I unfortunately do not have much time at the moment to move forward with this.

@Sherlouk After thinking about it for a while, I think for now we should keep the projects separate. Do you want to add it to the extensions list in the README though?

No worries! It's already on the main SnapshotTesting README, and doesn't depend on this project (though are related in theme) - it's probably fine as it is for now 🙂


[Feature] fix registration preview style on narrow window [OSF-6464]

Purpose
If the window is narrow when looking at a preview of a registration, the formatting is strange.

Changes

switch from col-md to col-xs

Side effects
None
Ticket
https://openscience.atlassian.net/browse/OSF-6464

Looks good. 🎉 🐧 🎉


Restore missing Tutorial file

#72

Is this off the main file or the branch?

It's the one off the branch.


Spot has a max windows size

Describe the bug
Window will not resize larger than a max fixed size
To Reproduce
Steps to reproduce the behavior:

open app
use a 3440x1440 screen with 100% resolution scale and drag the windows to fill larger portion of the screen. Or optionally use a tiling window manager and notice gaps in spots location.

Expected behavior
window would not resize itself
Screencast from 2022-11-20 18-35-27.webm
might be related to #424

Hi! this is indeed very strange. Couple things you can try:

does it happen on a smaller screen with the same setup?
are you able to test different environments? x11 vs wayland/another DE?

I'm using kinda the same setup. Spot installed via spot-client-git from AUR on Artix Linux, running Sway and launching Spot directly in Wayland. On my 3440x1440p monitor with 1x scaling, I'm not having above mentioned issue, Spot behaves as expected.

Closing this due to conflicting reports. Feel free to open again if the problem persists in the newest version.


Item vertical scroll interferes with carousel horizontal scroll (Android only)

Is this a bug report, a feature request, or a question?
This is a bug report
Summary: I have a carousel where each item is a card that has a title and a WebView. On Android, when attempting to scroll the web page loaded in the webview, the gesture handler of the Carousel gets fired first most of the time. On iOS, everything works fine.
Have you followed the required steps before opening a bug report?

[x] I have read the guidelines regarding bug report.
[x] I have reviewed the documentation in its entirety, including the dedicated documentations :books:.
[x] I have searched for existing issues and made sure that the problem hasn't already been reported.
[x] I am using the latest plugin version.
[x] I am following the issue template closely in order to produce a useful bug report.

Have you made sure that it wasn't a React Native bug?
Yes, it is not an issue with React Native - the iOS build works as expected.
Is the bug specific to iOS or Android? Or can it be reproduced on both platforms?
Android only.
Is the bug reproductible in a production environment (not a debug one)?
Yes
Environment
Environment:
React: 16.11.0
React native: 0.62.0
react-native-snap-carousel: 4.0.0-beta.5
Target Platform:
Android (10.0)
iOS (13)
Expected Behavior
On Android, the user should be able to scroll the web page (vertically) without triggering a carousel horizontal scroll.
Actual Behavior
On Android, most attempts to scroll the web page (vertically) will trigger a carousel horizontal scroll
Here are gifs showing the issue. The iOS build works as expected, but for Android it's virtually impossible to scroll a webpage vertically without triggering the horizontal Carousel scroll.
iOS

Android

Reproducible Demo
https://github.com/dudeinthemirror/carousel-example
Steps to Reproduce
iOS

Initialize, build and run iOS (yarn, yarn start, pod install, yarn ios)
Cards with title and webview will load in the Carousel
Scroll up and down in a webpage
Observe that everything works as expected (no interference between the vertical and horizontal scroll)

Android

Initialize, build and run Android (yarn, yarn start, pod install, yarn android)
Cards with title and webview will load in the Carousel
Scroll up and down in a webpage
Observe that it's virtually impossible to scroll a webpage vertically without triggering the Carousel horizontal scroll

Thank you for your time!

hey @dudeinthemirror I'm also struggling with this issue. Did you figure out any workarounds?

hey @goleary, not yet. I posted on SO as well, nothing so far. Let me know if you figure out something, thanks 🍻

Thanks for following up @dudeinthemirror. Someone on my team rigged something to spit scroll events from the webview into the react native application that will conditionally disable swiping on the carousel...sadly it doesn't work very well and slows the app down so I was hoping you'd found a better solution.
I'll let you know if we get it to work better or come up with a better solution.

appreciate it @goleary !

hey @dudeinthemirror I ended up switching to another package to get around this limitation:
https://github.com/callstack/react-native-viewpager
Here's a snack I made where you can play with it: https://snack.expo.io/@goleary/2d70d1
Looks like it doesn't work on the web, but it works in Android & iOS (which is all we need).
Hope it's helpful!

hey @dudeinthemirror I ended up switching to another package to get around this limitation:
https://github.com/callstack/react-native-viewpager
Here's a snack I made where you can play with it: https://snack.expo.io/@goleary/2d70d1
Looks like it doesn't work on the web, but it works in Android & iOS (which is all we need).
Hope it's helpful!

hey @goleary thanks for following up on this! This looks like a viable solution and the fact that it's published under the @react-native-community namespace is reassuring ;) I'll make the switch in our project as well.

hey @goleary thanks for following up on this! This looks like a viable solution and the fact that it's published under the @react-native-community namespace is reassuring ;) I'll make the switch in our project as well.

@dudeinthemirror
The viewpager works a million times better on Android. But it has one annoying issue on iOS. The webview doesn't load when off screen (unlike with this package), so when you swipe from one to the next it's blank for a bit.
I've got a PR out that I hope will fix this, but it could be a bit before it makes it into that package.
Just thought I'd let you know in case it affects your decision to move over or not.

@dudeinthemirror
The viewpager works a million times better on Android. But it has one annoying issue on iOS. The webview doesn't load when off screen (unlike with this package), so when you swipe from one to the next it's blank for a bit.
I've got a PR out that I hope will fix this, but it could be a bit before it makes it into that package.
Just thought I'd let you know in case it affects your decision to move over or not.

Any solutions for this?

neither of the issues have been fixed in either repo...so I use the snap carousel on ios & the view pager on android 😬

But how to create asnap carousel type carousel with first and last item visible using pager view.

ahh I have no idea. I use full screen webviews with both.

@vikrantnegi from what I've tried so far, if you use viewpager you can't have it show previews (i.e. part of the previous page (left) and part of the next page (right)). The Ux is sub-par IMO.

@dudeinthemirror You are right, there is no support for showing previews in react native pager.

Sorry, please allow me to advertise for my open source library! ~
I think this library react-native-reanimated-carousel will solve your problem. It is a high performance and very simple component, complete with React-Native reanimated 2

any workarounds ?


Calling Actions.key() not reload the components Scene

Version
Tell us which versions you are using:

react-native-router-flux v4.0.1 (v3 is not supported)
react-native v0.55.4

Expected behaviour
Refresh of the components of Scene when it is called with:
Actions.key();
Actual behaviour
I update from react-native-router-flux 4.0.0.beta27 where the default behaviour was that when i called Actions.key() the components of the Scene were reloaded, but now it doesn't happen.
Probably i miss something new, some parameter ?

Do you have a sample code? I have no idea about what might be happening here.

I made an example code to show you what i mean go here: https://github.com/pierol/rnrf-example it's an EXPO example try to open it in a ios simulator. Make login inside the app with these credentials: pierol and pw: giulia09. You have to swtch the version of react-native-router-flux from 4.0.0.beta.27 and 4.0.1 to see the two different behaviours. There is a console log in the DayList componenetWillMount method this component is part of the first Scene. After the Login is successfully i will make an Actions.choorHour() call to return to the first Scene, the one with the Daylist component. Only using 4.0.0.beta.27 will reload the component DayList when i return to the main scene from the Login form.

Thank you for providing the example - I'll investigate further later tonight.

The main point to be aware here is that RNRF had a major library upgrade (react-navigation) during the v4.0.0-beta.x releases. So beta.31was the last version using<EMAIL_ADDRESS>After that RNRF started to use<EMAIL_ADDRESS>that deprecated some stuff, and removed others - but also added lots of new things/fixes.

In general i think that it's not the right behaviour do not refresh the components of a scene when you focus on it. The component could have in its componentWiilMount a fetch like in the example i made. Another solution could be to set in the  an atttribute that specify if refresh or not, but it should refresh as default behaviour.

That would not be a refresh - refreshing automatically a component would make sense if params were going to change - if they do not change, you will not get any reason the trigger render again. If they change, you will need to inform that, in that case, I believe it's more flexible and less problematic to allow users works with it in the ways that might be the best for them. Do you know what I mean?

Yes i understand what you mean :

I believe it's more flexible and less problematic to allow users works with it in the ways that might be the best for them.

Thats's right it could be a attribute in the Scene tag like :
<Scene .... refreshOnFocus={true} ... />

This might get easier to fix with the proposal work that I am going to do in #3240.

@pierol Now that I got deeper in that code a bit more - I believe you can get done using onEnter={Actions.refresh}. This will trigger a refresh every time the Scene get focused.
Other thing you might try too is to have a call with params: Actions.key(params). Reopen the ticket if those solutions does not work. Also, there is an opened PR that have a few fixes and samples that show this.

Sorry but with onEnter={Action.refresh}  in the example code i made it doesn't work.

Sorry i didn't update the react-native-router-flux to the version 4.0.4, now it works with onEnter={Actions.refresh}, thank you for the support


feat(doc-generation): generate api.json

generates this in doc/api.json

Nice!
Me:

So what'd you do today Jeroen?

Jeroen:

Oh you know, just crushed it.

Me:

Again?!?!

It would be sad if a great library like aurelia-validation would be missing from the new docs :+1:


Change bot in order to add coins correlated to those in LunarCrush

Some free services like this or this offer the possibility to know coins that have a behavior extremely similar or are the opposite of other coins.
I believe that we could scale profits if we had the option to add these positively correlated or negatively correlated coins to the existent 10 altrank/galaxyscore coins.
Is it possible to have another helper/script that looks for these correlated coins in these services above-mentioned and that can automatically update the bot?

Can you give an example?


use MS_MOVE to change / to the roots

Signed-off-by: Lai Jiangshan<EMAIL_ADDRESS>

ref: https://github.com/opencontainers/runc/blob/55aabc142c005cd732614e1af985902814a1f704/libcontainer/rootfs_linux.go#L608-L616

lgtm

updated for read/write file command


Exposing the current time directly from the player

PLEASE FILL THIS OUT IF YOU CONTRIBUTE!
What kind of change does this PR introduce? (check one with "x")

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

What is the current behavior? (You can also link to an open issue here)
To access the currentTime you need to subscribe yourself to the video.timeupdate event and to update the current time from an external source you need to handle it manually as well
What is the new behavior?
The contribution creates a ngModel like binding called time which you can read to get the current time in seconds or write to, to update the player current time
Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

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

I tslinted the code, but other than that it seems to be okay.
These changes will be available in the next release.  Thank you for the contribution.

Thank you for integrating the PR so quickly!


Support WMS wrapDateLine parameter

Please support the WMS wrapDateLine parameter such that data at the 180th/International Date Line is seamless not disjointed.  We have a potential fix but lack Python expertise.

wrapDateLine is an OpenLayer option. For issues at the anti-meridian see #187


[sival] hash_kat test in crypto testplan

Description
The crypto testplan for sival points to the //sw/device/tests/crypto/cryptotest:hash_kat target which no longer exists.
This test seems to have been split into a separate test for each kind of hash. If this is the case, the testplan needs to be updated.

cc @milesdai, I think https://github.com/lowRISC/opentitan/pull/25256 takes care of the last instance, it just needs to be cherry-picked to earlgrey_1.0.0 now.

#25333 performs the cherry-pick


Pgai

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: github-actions[bot]:x: guruh46You have signed the CLA already but the status is still pending? Let us recheck it.

Hey, I think you mixed up repositories. Next.js is not related to pgai in any way.

I'm sorry sir I made a mistake, what about 3a606ef apakah bisa digunakan?


Pass in browsers options to pixrem

This PR will enable pixrem to use cssnext's own browsers option instead of requiring one of his own.
Addresses #263 and #174

Nice. I will make some really minor syntax changes, but looks good. Thanks for your contribution!

@MoOx Glad to contribute! Thanks.

PR was incorrect and some (crucial) tests were missing, see f550d4be1bf437ef33bdf910ed11caf45940687a and 47dd159f3aa088105c770382efdfb55de242bec3.
Will cut a release tomorrow morning.


Release 0.3.1-incubating

Let me merge it first to make the 0.3.1 available on the website, reviewers could leave comments and I will address them in the follow-up PRs


Add support for grant_types

Thanks for this @dancrumb! Could you run gofmt on this? Then this PR is good to merge ;)


Web page connection - 302 error code

After the success install, I'm connect on the web service : http://myLocalIP:8091
But, my client notify me than the page is not redirected correctly.
In the backend, I have this message :
  z2m:Store settings.json not found +0ms
  z2m:Store scenes.json not found +109ms
  z2m:App Application path:/usr/src/app +0ms
  z2m:Gateway Gateway needs both MQTT and Zwave Configuration to work +0ms
  z2m:App Listening on port 8091 +0ms
  z2m:App Error: Not Found
  z2m:App     at /snapshot/Zwave2Mqtt/app.js:0:0
  z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
  z2m:App     at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
  z2m:App     at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
  z2m:App     at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12)
  z2m:App     at next (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:275:10)
  z2m:App     at cors (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:188:7)
  z2m:App     at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:224:17
  z2m:App     at originCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:214:15)
  z2m:App     at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:219:13
  z2m:App     at optionsCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:199:9)
  z2m:App     at corsMiddleware (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:204:7)
  z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
  z2m:App     at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
  z2m:App     at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
  z2m:App     at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12) +9s
GET / 302 163.416 ms - 46
  z2m:App Error: Not Found
  z2m:App     at /snapshot/Zwave2Mqtt/app.js:0:0
  z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
...
...
...
  z2m:App Error: Not Found
  z2m:App     at /snapshot/Zwave2Mqtt/app.js:0:0
  z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
  z2m:App     at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
  z2m:App     at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
  z2m:App     at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12)
  z2m:App     at next (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:275:10)
  z2m:App     at cors (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:188:7)
  z2m:App     at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:224:17
  z2m:App     at originCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:214:15)
  z2m:App     at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:219:13
  z2m:App     at optionsCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:199:9)
  z2m:App     at corsMiddleware (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:204:7)
  z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
  z2m:App     at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
  z2m:App     at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
  z2m:App     at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12) +64ms
GET / 302 39.646 ms - 46

To inform, I use one Raspberry pi 0w with raspbian-strech. I have try your dockers images, the classic install and build my own docker image (with arm32v6/alpine).
Thanks a lot for your help !

I need to investigate, tomorrow I will do some checks. So just to know did you tried also to build the project yourself (by cloning git repo and running npm build) or did you just pulled the precompiled image from dockerhub?
thanks for the feedback.
Daniel

On 16 Apr 2019, at 18:40, Benjamin<EMAIL_ADDRESS>wrote:
After the success install, I'm connect on the web service : http://myLocalIP:8091
But, my client notify me than the page is not redirected correctly.
In the backend, I have this message :
z2m:Store settings.json not found +0ms
z2m:Store scenes.json not found +109ms
z2m:App Application path:/usr/src/app +0ms
z2m:Gateway Gateway needs both MQTT and Zwave Configuration to work +0ms
z2m:App Listening on port 8091 +0ms
z2m:App Error: Not Found
z2m:App     at /snapshot/Zwave2Mqtt/app.js:0:0
z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
z2m:App     at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
z2m:App     at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
z2m:App     at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12)
z2m:App     at next (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:275:10)
z2m:App     at cors (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:188:7)
z2m:App     at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:224:17
z2m:App     at originCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:214:15)
z2m:App     at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:219:13
z2m:App     at optionsCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:199:9)
z2m:App     at corsMiddleware (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:204:7)
z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
z2m:App     at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
z2m:App     at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
z2m:App     at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12) +9s
GET / 302 163.416 ms - 46
z2m:App Error: Not Found
z2m:App     at /snapshot/Zwave2Mqtt/app.js:0:0
z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
...
...
...
z2m:App Error: Not Found
z2m:App     at /snapshot/Zwave2Mqtt/app.js:0:0
z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
z2m:App     at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
z2m:App     at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
z2m:App     at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12)
z2m:App     at next (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:275:10)
z2m:App     at cors (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:188:7)
z2m:App     at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:224:17
z2m:App     at originCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:214:15)
z2m:App     at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:219:13
z2m:App     at optionsCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:199:9)
z2m:App     at corsMiddleware (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:204:7)
z2m:App     at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
z2m:App     at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
z2m:App     at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
z2m:App     at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12) +64ms
GET / 302 39.646 ms - 46
To inform, I use one Raspberry pi 0w with raspbian-strech. I have try your dockers images, the classic install and build my own docker image (with arm32v6/alpine).
Thanks a lot for your help !
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, thanks for your help.
I have try your all docker image form docker-hub without success. So I have try with your repo to build the app (npm install). And to finish, clone your Zwave2mqtt-docker and build from this source.
All installs went well but none worked properly on my Rpi0w.
Thanks,
Benjamin

I have just successfully installed it on my Rpi 3 Model B+ following the "manual" install:
# Install Openzwave
wget "https://github.com/ekarak/openzwave-debs-raspbian/raw/master/v1.4.79/openzwave_1.4.79.gfaea7dd_armhf.deb"
wget "https://github.com/ekarak/openzwave-debs-raspbian/raw/master/v1.4.79/libopenzwave1.3_1.4.79.gfaea7dd_armhf.deb"
wget "https://github.com/ekarak/openzwave-debs-raspbian/raw/master/v1.4.79/libopenzwave1.3-dev_1.4.79.gfaea7dd_armhf.deb"
sudo dpkg -i *openzwave*.deb
export LD_LIBRARY_PATH=/usr/local/lib
sudo sed -i '$a LD_LIBRARY_PATH=/usr/local/lib' /etc/environment
sudo ldconfig

# Clone and build app
git clone https://github.com/robertsLando/Zwave2Mqtt.git
cd Zwave2Mqtt
npm install
npm run build

# Start app
npm start

I have also tried with docker and it works:
pi@raspberrypi:~ $ sudo docker run --rm -it -p 8091:8091 --device=/dev/ttyACM0 --mount source=zwave2mqtt,target=/usr/src/app robertslando/zwave2mqtt:arm32v7-latest
Unable to find image 'robertslando/zwave2mqtt:arm32v7-latest' locally
arm32v7-latest: Pulling from robertslando/zwave2mqtt
d8d287cbc574: Pull complete
74af0ebc085c: Pull complete
6e873d5f914a: Pull complete
a2075eca02a7: Pull complete
b409dfb16e6e: Pull complete
58aa07503bf7: Pull complete
Digest: sha256:2175669ef69d5ede28b0a0a20799b78feae6b05bbd6bf79cb666edefe91b56bd
Status: Downloaded newer image for robertslando/zwave2mqtt:arm32v7-latest
  z2m:Store settings.json not found +0ms
  z2m:Store scenes.json not found +10ms
  z2m:App Application path:/usr/src/app +0ms
  z2m:Gateway Gateway needs both MQTT and Zwave Configuration to work +0ms
  z2m:App Listening on port 8091 +0ms
GET / 200 21.211 ms - 1432
GET /static/js/manifest.2ae2e69a05c33dfc65f8.js 200 12.001 ms - 857
GET /static/css/app.6767e8280089a963b7ff2532eaea9424.css 200 12.656 ms - 210253
GET /static/js/app.dd547788f2afe0892d2a.js 200 10.006 ms - 49171
GET /static/js/vendor.bdbd6d4fd3cc9baa1adb.js 200 13.290 ms - 812044
GET /static/logo.png 200 7.817 ms - 10014
  z2m:App New connection xlmDmozEgQJ7b3hbAAAA +4s
GET /static/favicons/favicon-32x32.png 200 7.778 ms - 1831

I don't have a Pi0w to test this but if it doesn't work using docker it must work by compiling the library yourself (first method I show you there, maybe you would need to compile openzwave yourself too)
Let me know

I have also add a commit to better handle logs of 404 Not Found errors. Anyway you receive 302 because I redirect by default all 404 to /. I think you forgot to run the command npm run build and it doesn't find any index.html file in /dist folder

I have remove the volume and the image, repull the image, recreate the volume and it work !
Thanks for your help !!
See you,
Benjamin.


Reticulum compatability?

Two questions

Could I use my Reticulum Identity: https://github.com/markqvist/Reticulum/discussions/155#discussioncomment-4186004 to append to Hypercore logs?

Could I use https://reticulum.network/ as a transport for Hypercore?

HC supports ed25519 keys atm so depends on that. The transport stream can be any binary stream.

ed25519 is supported so it looks like it would be compatible


[ic-card] Accessibility issue for expandable cards

Summary of the bug
When running accessibility tests in Cypress for expandable cards, there's an error to do with the aria-controls value we've set.
It can also be replicated running accessibility checks against our site.
📸 Screenshots or code

🧐 Expected behaviour
It should pass accessibility checks so that we can add in Cypress tests for a11y.

Consider accessibility guidance update if required.


Use Java 1.6+ MimeTypesFiletypeMap for SimpleStorageResource content type derivation

Type: Feature
Is your feature request related to a problem? Please describe.
We would like to be able to take advantage of this library's WritableResource creation by just using a s3:// URL. Unfortunately there's not quite enough flexibility in determining the content type. The code in SimpleStorageNameUtils makes a call to URLConnection#guessContentTypeFromName() which is difficult to extend.
As a result, we have to manually create and upload using AmazonS3 (or TransferManager).
As of Java 1.6, there is a facility called MimeTypesFiletypeMap which is similar but somewhat easier to customize. Any META-INF/mime.types file in your app classpath can augment the default types, and provide a mapping from file extension to content type.
This proposal is to augment (if not replace) the URLConnection call to make it easier to use user-defined mappings.
Describe the solution you'd like
Something like:
static String getContentTypeFromLocation(String location) {
    String objectName = getObjectNameFromLocation(location);
    if (StringUtils.hasLength(objectName)) {
      String contentType = FileTypeMap.getDefaultFileTypeMap().getContentType(objectName);
      if (contentType == null) {
        contentType = URLConnection.guessContentTypeFromName(objectName);
      }

      return contentType;
    }
    return null;
}

Additional context
The FileTypeMap is in javax.activation API, which does seem to be included as a dependency for this project.
Assuming you agree with the general premise, I'd be happy to put together a PR for this.

Thanks @chrisrhut for suggestion and apologies for late reply. I like this idea if especially if we make it in a backward compatible way - so that we don't break existing users - and also if we make using javax.activation API optional. Checking for class presence can be done with Spring ClassUtils.isPresent(..). You have green light for preparing a PR 👍

Hi @maciejwalkowiak, thanks for the reply and no worries on the delay!
Unfortunately the default behavior changes in a non-extensible way: the javax.activation.MimeTypesFiletypeMap falls back to application/octet-stream - rather than null - if there's no match, and there's no way to modify this behavior.
My suspicion is that ultimately this would be fine, since any store such as s3 would just use default handling if null is passed as the type and application/octet-stream is as generic as it gets.
However, the fact that this immediately failed the unit tests gives me pause. What do you think, should we 86 this idea?

In 3.0 we will still rely on guessContentTypeFromName but will give an option to provide custom implementation of content type resolver. This is because we still need to support Java 8+, and there was quite a bit of mess with javax.activation that I don't think i want to solve now.
Anyways, you won't be limited anymore to the content type resolution provided by the framework and i think this is a good middleground.


[question] result of the experiments shows too high variation

Hello, @seolhokim  again.
I hope you have good week.
I have another question, if you don't mind.
My question consists of 3 questions, MAIN QUESTION 1, SUB QUESTION 1 and 2.
I ran multiple 'main.py' of your code. That is simulation for hopper around 1000 times run.
My question is that actor_loss, critic_loss, score all vary. (suffered from variation)
I learn that result of reinforcement learning is variant. But i didn't expect this variant.
(MAIN QUESTION 1)Is it normal?
(제가 main.py 를 여러번 돌려 보았습니다. hopper를 1000번씩 돌려보는 seolhokim님의 기본 setting대로 입니다.
제 질문은 actor_loss, critic_loss, score의 분포가 너무 다양하다는 것입니다.
저는 현재 DRL 뉴비인데, 공부한 바로는 DRL 결과의 분포는 일반적인 supervised learning에 비해 분포가 심할 수 있다고 배웠습니다.
그러나 이렇게 심할 줄은 몰랐습니다. 이게 정상인가요? 아니면 제가 뭔가를 놓쳐서 잘못된 결과를 받은 건가요?)
(참고)
I didn't fix random_seed
(SUB QUESTION 1) Do i have to fix random_seed?
(SUB QUESTION 2 )Do i have to run 1000000 times like ppo original paper?

This picture shows results of multiple runs of 'main.py'. I set the 'smoothing' as 0.999. You see that all the last score of multiple runs end up in different value. High value of score is 2091 and lowest value of score is 985. And last score of critic loss also vary. The highest value of critic loss is 2.175 and the lowest value of critic loss is 0.3734.
(위 사진은 main.py를 여러번 돌린 결과를 tensorboard로 표현한 것입니다. 명확한 표현을 위해서 'smoothing'은 0.999로 세팅했습니다. 보시면 각 score value가 1000번째(마지막) run에 다양한 값으로 나타나 있습니다. 가장 큰 값은 2091인데, 가장 작은 값은 985입니다. critic loss 또한 사정은 같으며, 가장 큰 값은 2.175이고, 가장 작은 값은 0.3734입니다. )

Hi, If you look at some papers, the authors try experiments several times and show mean and std. It is a natural phenomenon. (Not always) Don't pay too much attention to the loss value now. Soon, you will have the opportunity to understand loss and do debugging and research.
Many papers mention performance in relation to the amount of frames actually interacting with. This PPO implementation trains 2048 frames in 1 epoch(You can find it in config.ini file)

@seolhokim
Thanks for the comment.
Okay. I will run several times and derive mean and std from them.
And I will read more papers for better understanding.
And Yes. I do notice the 2048 frames (in config.ini file). I believe that 'frame' means 'trajectory length'. Right?

Right. one frame is equal to one interaction with environment.

Thank you, @seolhokim .

Good evening, @seolhokim .
After reading some paper as you instructed, I have related and detailed question about this issue.
Please see the Fig3 and Fig4 on these picture.

On each description on the pictures, A2C author said that y-axis is averaged over three best cases. And TRPO author said that y-axis is averaged over five runs.
So, is this what we mean, right?
But my question is that how can this be fair? only five? only three even the best ones?
Even with the five runs, If i choose different five combination, then I will have different figure.
So What i mean is that five or three is too small population.
Is this RL's custom?
말씀해주신데로, 몇가지 논문을 찾아본 후, 관련 질문이 있어 글 남깁니다.
사진에 나와 있는 figure 설명란에 보면, A2C 저자들은 y-axis가 3가지 best case를 average 했다고 하며, TRPO 저자는 5개 시도를 평균냈다고 합니다.
말씀해 주신 mean과 average가 이걸 뜻하는 것인가요?
하지만 제 의문은 이게 충분히 fair 할 수 있나요? 고작 5개 또는 3개, 그것도 best one만 cherrypicking해서요?
그리고 5개 시도를 평균 낸다고 해도, 만약 제가 다른 5개를 택한다면 그래프가 다르게 나올 것 같습니다.
제 말씀은 5개나 3개는 너무 작은 모집단이 아닌가 해서요.
이게 Reinforcement learning 논문들의 custom인가요?
(말투가 따지는 듯 하다면 죄송합니다 ㅠ 자세히 여쭙느라고 이렇게 문장을 표현하였습니다.)

I recommend to read this paper. Deep Reinforcement Learning at the Edge of the Statistical Precipice
You will recognize how many computation(time) is needed to test some algorithms in DMC or atari.

Thank you @seolhokim  for the recommendation.
Have a good night.


Deprecation warning due to invalid escape sequences in Python 3.8

find . -iname '*.py'  | xargs -P 4 -I{} python3.8 -Wall -m py_compile {}

./tests/test_pygrok.py:89: DeprecationWarning: invalid escape sequence \[
  pat = '%{HOSTNAME:host} %{IP:client_ip} %{NUMBER:delay}s - \[%{DATA:time_stamp}\]' \
./pygrok/pygrok.py:85: DeprecationWarning: invalid escape sequence \w
  if re.search('%{\w+(:\w+)?}', py_regex_pattern) is None:

Looks like that line is missing the leading r to make it a literal. All of these other lines already have the r:
https://github.com/garyelephant/pygrok/blob/de9e3f92f5a52f0fc101aaa0f694f52aee6afba8/pygrok/pygrok.py#L70
https://github.com/garyelephant/pygrok/blob/de9e3f92f5a52f0fc101aaa0f694f52aee6afba8/pygrok/pygrok.py#L76
https://github.com/garyelephant/pygrok/blob/de9e3f92f5a52f0fc101aaa0f694f52aee6afba8/pygrok/pygrok.py#L81
It's an easy fix


Document flags for CLI running of spotDL

Problem
Document the flags that have been added recently
e.g. --ffmpeg-path, --output-format etc.
Solution
As per the problem

Also need to update help message spotdl -h (line 50 in /spotdl/__main__.py)

#1293


Add discount category to main page

The client wanted to add website advertisements to the main page. The addition of website advertisement images has already been implemented, and there is no need to add a discount category.


Wrench does not interact with Glass Casings

Unable to pick up glass casings with Create "Wrench" tool shift-right click.
Behavior inconsistent with other casing blocks in Create.
Mod version: 0.1.2e
Minecraft version: 1.19.2
Forge version: 43.2.3
If this is an intentional choice, a config setting option to enable the behavior would be preferred.

Has been fixed 👍


Fix parameter block binding for Vulkan

Fixes #307
This ends up being a major overhaul over how type layout computation is structured and exposed.
The big problems all arise around cases where both the "container" for a parameter block or CB, and the "element" type both use the same kind of resource.
E.g., if you define a CB with a texture in it, then in Vulkan both the CB and the texture use the same kind of resource, and so if you query the CB's resource usage it will just tell you it uses two descriptor-table slots, but nothing more than that.
Similar confusion still arises in the HLSL case, when a CB with a texture in it reports its parameter category as "mixed" so that a user might query for a category they didn't mean to. There were also cases in the existing code where a parameter block might expose both a register-space usage and another concrete resource type, which isn't right.
The most important changes here are:

A ParameterGroupTypeLayout now has a more refined internal structure, consisting of:

A containerTypeLayout, which represents the resource usage of the buffer/block itself (e.g., if a constant buffer had to be allocated)
An elementVarLayout which stores the offsets that need to be applied to get from the VarLayout for an instance of this parameter-group type to the offsets of its elements. The TypeLayout for this variable layout should be the "raw" type of the block/CB element.
The offsetElementTypeLayout (formerly just elementTypeLayout) which represents the element type, but in the case of a struct element type, will have fields offset similar to the elementVarLayout. This is what all the old code used to use, so we need to keep it for compatibility.

When doing reflection on a ParameterGroupTypeLayout, we now only report the resource usage of the containerTypeLayout. This is technically a potentially breaking change in the public API, but I don't think Falcor will mind, since they actually want something closer to this behavior.

Add a new public API for querying the element variable layout of a parameter block of constant buffer. This could be used by savvy applications to fold the handling of CB element offsetting into some notion of a "reflection path." This would be required for applications that want to handle CBs or parameter blocks where the element type is not a struct type.

Remove old logic for applying an offset when creating a type layout for constant buffer element, and instead perform offsetting more uniformly later, by constructing the offsetElementTypeLayout from the rawElementTypeLayout. This is useful both because we want to keep both (the "raw" type layout becomes the type layout of the elementVarLayout), and also because we can decide later whether we even want to allocate a CB register for a buffer, based on whether it actually contains any uniform data.

Fix cases where we might end up with a parameter block type reporting both that it uses a whole register space (and thus should not expose the resource usage of the container/element type) and a constant-buffer register/slot. The latter should be hidden inside the regsiter space.

Clean up the spReflectionParameter_GetBinding{Index,Space} functions to just route to spReflectionVariableLayout_Get{Offset,Space}, using the "default" category of the parameter

Try to make the GetSpace query take into account cases where a variable also has an explicit RegisterSpace allocation.

This probably still needs some cleanup, since ideally we'd just move things into the space field on the ReosurceInfo and have an invariant that a variable either has a RegisterSpace allocation, or it has other resource infos, but never both...

Add some ad-hoc logic so that if the user queries for a binding index/space using a parameter category that doesn't actually apply (e.g., they query for a D3D t register when using Vulkan), we can optionally remap it to the resource type they "probably" meant. This is a mess of Do What I Mean code, but it is also what our users want right now.

Fix various bits of emit logic so that if a parameter block has a register space/set allocated to it, we properly output that as part of the binding information for it.

This is another thing that might be cleaned up if we rationale the way that things get split during legalization.

Add a GLSL case for emitting a parameter block variable as a cbuffer.

I need to check this in without an up-front review because of time pressure to fix Falcor issues.


req.next in request.js

In this line the call to req.next throws
TypeError: req.next is not a function
    at done (/app/node_modules/express/lib/response.js:961:25)
    at /app/node_modules/hbs/lib/hbs.js:73:9
    at tryToString (fs.js:456:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:443:12)

if the view not found.
Handlebars is used as view engine.
Application is deployed to Heroku. At localhost this issue is not reproduced.
AFAIK, this is internal api

Hi @Gebon that's weird. The req.next method is something Express defines and uses internally in a variety of locations. We define it for every request at https://github.com/expressjs/express/blob/c087a45b9cc3eb69c777e260ee880758b6e03a40/lib/middleware/init.js#L33 . I can take a look into what is happen, but need something I can reproduce so I can debug. Can you provide the following?

The exact version of this module
The exact version of Node.js
The exact versions of all other modules needs to reproduce.
Full, complete source code we can copy and paste into a file and run.
Full, complete instructions on how to reproduce. Please leave nothing implied, as everything you just leave to implied makes it that much more unlikely for us to reproduce.

I'm finally found out what was happened. I have a middleware with code similar to
if (smth) next();
next(new Error('description'));

When smth is true, next called twice. When I changed it to
if (smth) return next();
next(new Error('description'));

all worked fine.


Create tests for ride-hailing/MissionParams using jest.

first-timers-only
This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.
Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.
Find more first-timers-only issues from DAV Foundation here.
Thank you for your help :heart:
What is this project?
DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.
As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.
dav-js
This SDK enabled integrating any client side JS and NodeJS code with the DAV Network.
How you can help
The Issue
Create tests for ride-hailing/MissionParams using jest.
You need to create tests to check that the serialize and deserialize methods work as expected.
Please use the test file for class NeedParams as a basis for your new code.

Function serialize in class MissionParams must return a JSON object that contains all properties defined in the MissionParams instance.

Function deserialize in class MissionParams receives a JSON string and must initialize all the properties of the MissionParams instance with the values in the JSON string.

missionParams.desrialize(missionParams.serialize()) == missionParams must therefore always be true.
NOTE: Some names are changed between protocol string representation of instance properties:

location is internally represented as { lat , lon } but serialized as { latitude , longitude }
Private properties are internally prefixed with _ but serialized without the prefix. i.e. _protocol becomes protocol

Contributing to dav-js

[ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
[ ] Comment in this issue that you would like to do it.
[ ] Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
[ ] Code Code Code
[ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
[ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help
We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

I would like to do it :)

Thanks @akshait
Go ahead 👍


Enum number return type is not type safe

TypeScript Version:  3.8.0-dev.20200211

Search Terms:
Enum return type, enum strictly typing, enum type safety
Code
enum Hello{
  world
}

const sayHello = ():Hello => {
  return 2;
};
console.log(sayHello()); // 2

Expected behavior:
An exception/error that 2 is not one of the enum option
and that i should use the enum and not just a number value. Which in the programming world
is commonly known as Magic number
Actual behavior:
returns 2
Playground Link:
https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=8&pc=30#code/KYOwrgtgBAEsA28D2BvAsAKClA7kgTvACZQC8UAjJgL6aYDGSIAzgC5TMCGAnnIkmSgAKAJQAuPsjIA+KOixR8wVmHwgoAJgDcNHRkYsk8YADpkAcyFdeCZKJFaoAeieagA
Hackish workaround:
enum Hello{
  world = "1",
}

const sayHello = ():Hello => {
  return "2"; // <-- will give an error
};
console.log(sayHello()); // 2

But typescript should make our code more typesafe and give enums the power it should have in first place.

Number enums are not really enums at all. It's "by design", even if many people don't agree.

Enum numbers are by design meant to be not actually enums and string enums are by design actual enums?
I would just expect number enums to act the same as string enums
Hope you can help me out, it's giving different type restrictions depending on if the Enum is a number or string.
If many people feel the same then it's good to discuss about it
I think you would agree with me that the restrictions for string enums should also be reflected with number / default enums and will help the developer gain a more strictly typed environment

I don't like it, either. It is what it is, though.
But, yes, number and string enums have different behavior. Also, if you look at the JS emit for number and string enums, you'll see that they're different.
It's worth noting that JS has no actual enum type. It's a TS concept. Just like namespace.


Clean up scan_partitioner

Removed scan_partitioner sequential f3 implementation (obsolete)
Refactored parallel algorithms that used above implementation ("remove" and "unique") to use util::partitioner instead
Marginal performance improvement (if any)

Can one of the admins verify this patch?

retest

@Pansysk75 The tests.unit.modules.algorithms.container_algorithms.sort_range and tests.unit.modules.algorithms.container_algorithms.stable_sort_range tests started to fail after those changes (see: https://cdash.cscs.ch/viewTest.php?onlyfailed&buildid=40459). Could you please have a look?

@Pansysk75 The tests.unit.modules.algorithms.container_algorithms.sort_range and tests.unit.modules.algorithms.container_algorithms.stable_sort_range tests started to fail after those changes (see: https://cdash.cscs.ch/viewTest.php?onlyfailed&buildid=40459). Could you please have a look?

Just noticed your comment, I'll have a look

bors merge


Any example of IfElsePipeline(condition, agent1, agent2)?

Can I get an example of IfElsePipeline(condition, agent1, agent2)? I think there's no related guide in official docs.

You can refer to the test_if_else_pipeline of tests/pipeline_test.py for simple examples.
In simple terms, the condition function is a lambda function whose input is the pipeline input Msg, and whose output is True or False. When the output is True, the if_body_operators will be executed, and when the output is False, the else_body_operators will be executed.

Thanks! my problem is solved.


TPV nuclear pore nuclear basket

Has is_a "membrane protein complex".
I don't think that is correct is it?

Based on the definition, nuclear pore nuclear basket is part of the nuclear pore complex, which is itself a protein complex that crosses the nuclear membrane (see https://en.wikipedia.org/wiki/Nuclear_pore), so I would think that the is_a assertion is correct.

Ah OK, but nuclear pore doesn't have "membrane protein complex" it has "membrane bounded organelle"?

Checking again, you were right. The NPC does not actually cross the membrane, but instead crosses the envelope. The figure at https://en.wikipedia.org/wiki/Nuclear_pore#/media/File:NuclearPore_crop.png shows that the membrane actually folds on each side of the NPC, which never crosses it.
I removed the wrong axioms for the subpart of the NPC. Thanks for the report!


Make different types of jokes

Create at least 2 new commands which use APIs to make jokes. The categories of the jokes should be different. For example knock knock jokes and puns

Alright, please make sure the APIs do not require authentication keys


Broken Checkstyle (Commit 0e19e)

This commit violated checkstyle. It should fall under the ConstantName checkstlye module, but since it is not final it expects the first character to be lowercase  (Name 'INJECTION_TARGETS_PER_GETTER_METHOD' must match pattern '^[a-z][a-zA-Z0-9]*$'.)
Broken line in commit

There's an additional violation for line length here

There's an unused import here


Fix deprecated location for default_store

Putting default_store in the [DEFAULT] section has been deprecated since Juno.  We verified this was causing failures in starting the glance service.  Moved to the correct location.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

:+1:

Looks good to me. I'll let @paulczar decide if he wants this on the WIP.

Looks good. Thanks for doing this.

Wondering why we're showing 8 commits here instead of just the 1. We rebased didn't we?

A rebase (non-interactive) just plays your changes on top of the branch you're rebasing on. If you want to reduce the commits you need to rebase interactively (-i) and squash/fixup some commits.


Feature/prl 5230

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] the enable_keep_helm label has been added, if the helm release should be persisted after a successful build

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

closing the PR, as  new PR (1298) is already created


eq-json-descriptions Add descriptions

Add descriptions to json schemas as appropriate to aid documentation, re-use and development
What is the context of this PR?
Added descriptions to the schemas under data/schema to aid explanation. Also added descriptions to test_unit_patterns.json and test_big_list_naughty_strings.json to align them with other test schemas
New pull request on new branch to remove extraneous commit.
How to review
No tests as such, as no functionality has changed, just check that the descriptions are sensible. I have checked that the descriptions don't leak when the schemas are rendered

Squashed and ready


Picture of the wireless module?

Do you by any chance have a picture of the wireless module?
This is the picture of the PCB of Ambientica Advanced+:

From the PCB I can deduce that it uses either RS422 or RS485 as communication between devices (so possibly modbus?)

Well no worries, I'm just wondering whether Wireless module is also "connectable" via the RS422/RS485 (the black/blue/red connector + upside down chip labelled 65176B). This might possibly  give better control of the device (read status, etc).
Also, 6 unpopulated pins just below the msp430 seems to be also routed to the UART pins of the MSP430, but I have yet to power up the device and observe the traffic from there. (I did the bottom/front stackup already in GIMP, but haven't yet had time to trace out the connections...)

Managed to do some tracing:

Really cool, can you also identify the chip on the right of ESP32?

Sure


Feature/cwl dag hints

Docker hints are now working for cwl. I just use the same code as with requirements. I don't reuse the function for docker requirements in case they have some differences in the future.
Fixes this issue https://github.com/ga4gh/dockstore/issues/1136
Relevant with https://github.com/ga4gh/dockstore/issues/1284

Coverage decreased (-31.3%) to 35.077% when pulling e6da8a04c93bb43b3afe3ffc6bff404d4d9877f7 on feature/cwl-dag-hints into 43630808d894107c2adbb4854082e8c5d09d1555 on develop.

Coverage decreased (-31.3%) to 35.077% when pulling e6da8a04c93bb43b3afe3ffc6bff404d4d9877f7 on feature/cwl-dag-hints into 43630808d894107c2adbb4854082e8c5d09d1555 on develop.

Just a comment on this. It seems that for some reason we thought the format for docker requirements was

DockerRequirement
dockerPull: ...

I checked the docs as far back as draft 3 and I can't find this, so I don't know if it is actually valid. Anyways the way it should be is

class: DockerRequirement
dockerPull: ...
The class field is required, as there are multiple types of hints and requirements.


Please make a release of the current version

The latest version (0.0.2) has a different directory structure than the one in master/main branch:
include/
    hash_grow/
    hash_nogrow/
    parlay/

versus:
include/
    parlay_hash/
    parlay/
    ...

I am creating a Conan (package manager) recipe for Parlay Hash and I would like to use the latest directory structure.
Thanks

Not sure what you mean by the latest version?   We did a major reorganization of the directory structure and the implementation that was added a couple weeks ago to the main branch.    Now there is only one implementation, which is in "include/parlay_hash" (which allows for growing).   There are no longer separate hash_grow and hash_nogrow implementations since we found the growable version was effectively just as fast as the no_grow version.  The new implementation is also faster by about 25%.
Sorry if this conflicted with your work on a Conan recipe.

Not sure what you mean by the latest version? We did a major reorganization of the directory structure and the implementation that was added a couple weeks ago to the main branch. Now there is only one implementation, which is in "include/parlay_hash" (which allows for growing). There are no longer separate hash_grow and hash_nogrow implementations since we found the growable version was effectively just as fast as the no_grow version. The new implementation is also faster by about 25%.
Sorry if this conflicted with your work on a Conan recipe.

@gblelloch
Thank you for your prompt response and for the update on the reorganization of the directory structure in the main branch. I understand that the new implementation combines the features of the previous versions and is more efficient, which is great news.
I wanted to clarify that there's no issue at all regarding the changes impacting the Conan recipe I'm working on. The flexibility of package management with Conan allows for easy adaptation to such changes.
However, for Conan to effectively manage the Parlay Hash package, it requires the ability to download code from specific tags or releases on GitHub. Currently, the latest release (0.0.2) still contains the old directory structure. My request is, could you please create a new release on GitHub that reflects the latest directory structure and implementation?
Having a release that corresponds with the current main branch's structure is crucial for maintaining consistency. Once a new release is available, I can ensure that the first Conan package for Parlay Hash aligns with your latest and most efficient implementation. This will also prevent any compatibility issues for users who rely on the Conan repository when the new version is released.
I appreciate your consideration of this request and look forward to the continued success of the Parlay Hash project.

OK, thanks for the clarification.    Done.


Fortiswitch port stats

@bluecmd or @secustor

@Jurka007 can you rebase and fix the check errors?


Adding support for Apache HTTP Async Client

Supports from first official version 4.0 released at October 2013. Since this API is much more likely to be used for async calls, I decided not to support the async API of the old client.
Currently not supporting the pipelining API, not sure how commonly it is used, we can add that later.
Includes a new post-type-matching API based on implementation version (without loading the class, only reading the manifest file), to ease support of specific class versions.

Codecov Report

Merging #558 into master will decrease coverage by 3.11%.
The diff coverage is 24.33%.

@@             Coverage Diff              @@
##             master     #558      +/-   ##
============================================
- Coverage     65.25%   62.13%   -3.12%
  Complexity       68       68
============================================
  Files           180      185       +5
  Lines          7209     6994     -215
  Branches        863      810      -53
============================================
- Hits           4704     4346     -358
- Misses         2251     2375     +124
- Partials        254      273      +19

Impacted Files
Coverage Δ
Complexity Δ

...lastic/apm/agent/http/client/HttpClientHelper.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...sticsearchRestClientInstrumentationHelperImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...nt/httpclient/ApacheHttpAsyncClientHelperImpl.java
0% <0%> (ø)
0 <0> (?)

...nt/httpclient/HttpAsyncRequestProducerWrapper.java
0% <0%> (ø)
0 <0> (?)

...ic/apm/agent/httpclient/FutureCallbackWrapper.java
0% <0%> (ø)
0 <0> (?)

...astic/apm/agent/bci/ElasticApmInstrumentation.java
75% <100%> (+2.27%)
0 <0> (ø)
:arrow_down:

...va/co/elastic/apm/agent/impl/transaction/Span.java
61.64% <25%> (-2.13%)
0 <0> (ø)

...tpclient/ApacheHttpAsyncClientInstrumentation.java
34.28% <34.28%> (ø)
0 <0> (?)

.../ApacheHttpAsyncClientRedirectInstrumentation.java
46.15% <46.15%> (ø)
0 <0> (?)

...java/co/elastic/apm/agent/bci/ElasticApmAgent.java
75.15% <50%> (-0.47%)
0 <0> (ø)

... and 12 more

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 6482904...db09e24. Read the comment docs.

Research and implementation rationale summary:
The current approach instruments the main HttpAsyncClient#execute API overload, which captures all other API invocations as their implementation go through it. This is where the span is created and started. In addition, the HttpAsyncRequestProducer and FutureCallback arguments are wrapped.
Cons:

legacy async API (HttpAsyncRequester) is not supported. The old API was very complicated to use as it required starting the reactor and its thread and specify many configurations. The Apache HttpAsyncClient 4.0 API was introduced already at October 2013 to simplify all this, so we don't assume there is a lot of usage in the legacy API.
relies on HttpAsyncRequestProducer#close for ending the span and recycling the wrapper- a risk for wrapper/span leak and failure to delegate if reused. As far as my tests shown- we can rely on it
wrapping of HttpAsyncRequestProducer means that we will need to watch out for this interface changes, although it looks consistent for a long time now
we rely on the response code set as attribute in the HttpContext when the FutureCallback is invoked, but this is not part of the API, so this may change. In addition, we don't have a guarantee that the context is not already stripped from attributes. Looks like something we can rely on at least in most cases. Worst case is not so bad (no or wrong response code)

Other approaches considered:

Instrumentation of HttpAsyncClientExchangeHandler which we can think of as the reactor implementation. Main advantage of this option is that we don't need to wrap.
Cons:

The API does not include

asfd

Summary of research and implementation rationale:
Current solution:
Instrumenting the main HttpAsyncClient#execute API, which is invoked by the implementation of all other APIs. This is where a span is created and started. In addition, the HttpAsyncRequestProducer and FutureCallback arguments are wrapped. The way to connect the response to the callback is through the HttpContext which is where the client sets the response object as an attribute.
Limitations/risks:

The legacy HttpAsyncRequester API is not supported. This API was very complicated to use and was replaced by the HttpAsyncClient to greatly simplify usage already at October 2013, so we assume it is not commonly used.
Wrapped HttpAsyncRequestProducer means we need to watch out to future changes of the API, but it seems very consistent so far
We rely on HttpAsyncRequestProducer#close to end the span and recycle the wrapper. If not invoked, we may get span/wrapper leak or even wrong delegations if reused after closed. Tests didn't find any problem
Getting the response code from the HttpContext is not part of the API, so no guarantee about it, especially when invoked in the callback where it may be stripped from attributes already. Tests didn't find any problem.
The pipelining API is not supported at this stage. We can add support for it if demand rises.

Other solutions considered:

Instrumenting implementations of HttpAsyncClientExchangeHandler so that we don't need to wrap and we can support the legacy async API.
Cons:

we must rely on the context in order to relate a response to a request, but this is not part of the API and requires specific instrumentation of all implementations to locate the context.
no indication whether a response is the final one or can be redirected.

Registering HttpRequestInterceptor and HttpResponseInterceptor.
Cons:

registering during build time mean we only support startup and not agent attach. Otherwise, we need to add implementation-specific instrumentation to add interceptors to the list- probably not very resistant to client changes.
we don't know when the final response is called in case of redirects, so we don't know when to finish the span.


XSD validation XML path

I saw a previous issue regarding getting the line number of the error when doing XSD validation. Since that doesn't seem to be possible, is there a way we can get the XML path of element with the error? That will help with troubleshooting XML errors.

Does the original libxml2 (xmllint or the like) provide this information?
If yes, can you please provide a test case where we can see it in action?
If libxml2 doesn't give it to you, then most likely (take this with a grain of salt, as I haven't really delved into the gory details of libxml2 recently) the answer is no, we can't. I'm willing to be convinced otherwise, though.

Does the original libxml2 (xmllint or the like) provide this information?
If yes, can you please provide a test case where we can see it in action?
If libxml2 doesn't give it to you, then most likely (take this with a grain of salt, as I haven't really delved into the gory details of libxml2 recently) the answer is no, we can't. I'm willing to be convinced otherwise, though.


Can send to channel after leaving in mattermost

Steps to reproduce:

Be in mattermost channel.
Connect to matterircd, autojoin mattermost channel.
In mattermost UI, leave channel.

Expected behaviour:

IRC client no longer receives messages from channel.
Sending to channel from IRC is not possible.
IRC client leaves channel.

Observed behaviour:

:heavy_check_mark: IRC client no longer receives messages from channel.
:x: Sending to channel from IRC is still possible.
:x: IRC client does not leave channel.

NB: After rejoining the channel in mattermost, the IRC client is forced to quit, and receives an error that the (public) channel cannot be joined because it is +i.

NB: this also works for secret channels, and also works after getting kicked.

NB: when being readded to a secret channel in IRC after being kicked, IRC client does not leave the channel.

Note that disallowing users from sending to a channel they are not in should be fixed in mattermost-server (see linked issue); but fixing IRC join/leave behaviour should be fixed here.

Fixed in master, thanks for reporting.


Misc. test app improvements

During my snow day I came across some issues in the UWP test app that blocked me from getting stuff done efficiently:

My laptop runs in high DPI and I didn't want to switch to regular DPI just to run JSON serialization tests, so I added a Run Anyway button to the DPI warning
It's really painful to manually inspect JSON diffs where everything is on one line. I introduced a formatting routine for the purposes of diffing to make it easier to see the differences.

I should note that I did this yesterday without any internet access. There's probably a better way to deal with the UICommand used in the MessageDialog.
Also, @RebeccaAnne or @khouzam, any ideas on making the content dialog hosting the diffview wider? I've tried a bunch of things, but figure I'm missing something simple. :)

In case it's not clear what we get from this change:


Having multiple error on dashboard-next upon installation of npm

What I'm trying to achieve
npm i
Steps to reproduce the problem

rm -rf node_modules/
npm i

What I expected to happen
clean installation
Screenshots
`
ERROR in /home/app/multivendor/saleor/static/dashboard-next/auth/components/LoginPage/LoginPage.tsx
ERROR in /home/app/multivendor/saleor/static/dashboard-next/auth/components/LoginPage/LoginPage.tsx(123,9):
TS2741: Property 'loading' is missing in type '{ email: string; password: string; rememberMe: boolean; }' but required in type 'FormData'.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts(1,1):
TS6133: 'Money' is declared but its value is never read.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts(6,32):
TS2709: Cannot use namespace 'Money' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts(6,48):
TS2709: Cannot use namespace 'Money' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts(6,58):
TS2709: Cannot use namespace 'Money' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts(12,37):
TS2709: Cannot use namespace 'Money' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts(12,53):
TS2709: Cannot use namespace 'Money' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/Money/index.ts(12,63):
TS2709: Cannot use namespace 'Money' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/MoneyRange/MoneyRange.tsx
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/MoneyRange/MoneyRange.tsx(5,1):
TS6133: 'IMoney' is declared but its value is never read.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/MoneyRange/MoneyRange.tsx
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/MoneyRange/MoneyRange.tsx(8,10):
TS2709: Cannot use namespace 'IMoney' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/MoneyRange/MoneyRange.tsx
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/MoneyRange/MoneyRange.tsx(9,8):
TS2709: Cannot use namespace 'IMoney' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/MoneyRange/MoneyRange.tsx
ERROR in /home/app/multivendor/saleor/static/dashboard-next/components/MoneyRange/MoneyRange.tsx(12,29):
TS2709: Cannot use namespace 'IMoney' as a type.
ERROR in /home/app/multivendor/saleor/static/dashboard-next/siteSettings/components/SiteSettingsPage/SiteSettingsPage.tsx
ERROR in /home/app/multivendor/saleor/static/dashboard-next/siteSettings/components/SiteSettingsPage/SiteSettingsPage.tsx(67,55):
TS2345: Argument of type '{ code: string; country: string; }' is not assignable to parameter of type 'SiteSettings_shop_companyAddress_country'.
Property '__typename' is missing in type '{ code: string; country: string; }' but required in type 'SiteSettings_shop_companyAddress_country'.
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js??ref--6-1!node_modules/postcss-loader/lib/index.js??ref--6-2!node_modules/sass-loader/dist/cjs.js??ref--6-3!saleor/static/dashboard/scss/dashboard.scss:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js??ref--6-1!./node_modules/postcss-loader/lib??ref--6-2!./node_modules/sass-loader/dist/cjs.js??ref--6-3!./saleor/static/dashboard/scss/dashboard.scss 676 KiB {0} [built]
[13] ./saleor/static/dashboard/images/chevron-right.svg 96 bytes {0} [built]
+ 12 hidden modules
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js??ref--6-1!node_modules/postcss-loader/lib/index.js??ref--6-2!node_modules/sass-loader/dist/cjs.js??ref--6-3!saleor/static/dashboard/scss/document.scss:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js??ref--6-1!./node_modules/postcss-loader/lib??ref--6-2!./node_modules/sass-loader/dist/cjs.js??ref--6-3!./saleor/static/dashboard/scss/document.scss 7.31 KiB {0} [built]
+ 1 hidden module
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js??ref--6-1!node_modules/postcss-loader/lib/index.js??ref--6-2!node_modules/sass-loader/dist/cjs.js??ref--6-3!saleor/static/scss/storefront.scss:
Entrypoint mini-css-extract-plugin = *
[0] ./node_modules/css-loader/dist/cjs.js??ref--6-1!./node_modules/postcss-loader/lib??ref--6-2!./node_modules/sass-loader/dist/cjs.js??ref--6-3!./saleor/static/scss/storefront.scss 737 KiB {0} [built]
[3] ./saleor/static/images/arrow-select.svg 95 bytes {0} [built]
[4] ./saleor/static/fonts/Lato-Light.woff2 95 bytes {0} [built]
[5] ./saleor/static/fonts/Lato-Light.woff 94 bytes {0} [built]
[6] ./saleor/static/fonts/Lato-Light.ttf 93 bytes {0} [built]
[7] ./saleor/static/fonts/Lato-Regular.woff2 97 bytes {0} [built]
[8] ./saleor/static/fonts/Lato-Regular.woff 96 bytes {0} [built]
[9] ./saleor/static/fonts/Lato-Regular.ttf 95 bytes {0} [built]
[10] ./saleor/static/fonts/Lato-Bold.woff2 94 bytes {0} [built]
[11] ./saleor/static/fonts/Lato-Bold.woff 93 bytes {0} [built]
[12] ./saleor/static/fonts/Lato-Bold.ttf 92 bytes {0} [built]
[13] ./saleor/static/images/block1.jpg 89 bytes {0} [built]
[14] ./saleor/static/images/block2.jpg 89 bytes {0} [built]
[15] ./saleor/static/images/block3.jpg 89 bytes {0} [built]
+ 2 hidden modules
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>build-assets: webpack -p
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build-assets script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-11-13T04_09_16_317Z-debug.log`
System information
npm 6.12.0
node v12.13.0

Hi @paulon-zervoulakus Can you precise what version of Saleor you use?
FYI: Starting from v2.9, the dashboard has been moved to a separate repository.

Hi @paulon-zervoulakus Can you precise what version of Saleor you use?
FYI: Starting from v2.9, the dashboard has been moved to a separate repository.

I believe it was 2.8.0 base on the changelog

Changelog

All notable, unreleased changes to this project will be documented in this file. For the released changes, please visit the Releases page.
[Unreleased]

Fix product type taxes select - #4453 by @benekex2
Fix form reloading - #4467 by @dominik-zeglen
Fix time zone based tests - #4468 by @fowczarek
Move Django Debug Toolbar requirement to the "dev" one (also downgrade it 2.0 -> 1.11, see PR) - #4454 by @derenio

2.8.0
Core

Avatax backend support - #4310 by @korycins
Add ability to store used payment sources in gateways (first implemented in Braintree) - #4195 by @salwator
Add ability to specify a minimal quantity of checkout items for a voucher - #4427 by @fowczarek
Change the type of start and end date fields from Date to DateTime - #4293 by @fowczarek
Revert the custom dynamic middlewares - #4452 by @NyanKiyoshi

Dashboard 2.0

any updates regarding this?

Dashboard lives in the separate repository saleor-dashboard. You can build it from master for the latest development version or using Github tags for a release version: https://github.com/mirumee/saleor-dashboard/releases/.
Please check again if you can build it after a clean clone and npm install. Please open an issue in the dashboard's repository if there are still problems with the installation.


Better error for target release mismatch

Right now if there's a target release mismatch, the error
doesn't show the info to find the offending bug. This does that
./elliott --assembly=rc.4 --group=openshift-4.12 attach-cve-flaws --advisory 104601 --noop

/lgtm