IE (11), padding on child elements

I've noticed a weird discrepancy between IE (11) and other Browsers when you apply padding to elements that are child elements of a display:flex container.
I've documented it on my blog here:http://michaelgunner.co.uk/padding-flexbox-child-elements-causing-chaos-ie/
To summarise, if you set a flex-basis value and use flex-wrap:wrap, when you add padding to the elements in IE the layout totally screws up.
It's quite possible that being January, and also recovering from a bad cold/xmas/ny, I'm missing a beat somewhere and pulling a bit of a noob move - but I can't figure it out.
Code link: http://codepen.io/brightonmike/pen/KwNLpo
I'm aware I could remove the wrap property - but I want to my elements to wrap, not squeeze onto one line. Using width instead of basis fixes it too, but that reduces the flexibility of the code.

That is an interesting one and IE11 seems to have the same overall width for each item and padding on all sides as Chrome. In IE12 we made a lot of changes to match the latest spec which may have had some changes that didn't make it into IE11. Because of those changes IE12, FF and Chrome all render the same so going forward this won't be an issue. You've already stated the main work-around for this by setting a width. Can you give me your use case, I think in most flex situations this would be ok. The only ones that would be annoying is when you need to have X number of columns per row.

I've seen this before. It's in IE10 also.
I may be missing something else, but I believe the underlying issue is that in IE10/11, flex-basis and box-sizing:border-box; do not work like they do in FF/Webkit.
What seems to happen in IE is that the widths of flex children are sized according to the flex property, but then left/right padding and border are added to calculate the total layout width of the element, regardless of the box-sizing setting. Meanwhile, other browsers respect box-sizing:border-box; and calculate the final width including padding/border.
In other words, when sizing flex children, IE10/11 seem to forget that box-sizing:border-box; exists.
I've run into this myself and others have noted it on Stack Overflow both here and here.
There are a couple of workarounds:

if feasible, do not apply padding or border directly to a flex child. Allow the flex child to be a containing element to another element that will receive the padding or border. This is somewhat undesirable because avoiding this sort of extra markup is one the big benefits of box-sizing:border-box;.

depending on the nature of the layout, another option might be to apply an explicit width or (better, probably) max-width to the flex children. In IE10/11, max-width on the flex children will use box-sizing: border-box; where flex will not.
The drawback is that this will interfere with flex-grow. For example, if you set flex: 1 1 25%, flex children will be able to grow (flex-grow:1;) but their maximum width will be constrained by that max-width;
So, for the pen by @brightonmike you'd do:
div {
  flex:0 1 25%; /* Everyone: start at 25%, do not grow, you're allowed to shrink */
  padding:5em;
  max-width: 25%; /* No really IE10/11, do not grow bigger than 25% */
}

The width only works if you're using flex-direction:row. For column direction, it's not a fix, because the flex-basis applies to height not width. You could then use height instead I suppose, but that's starting to sound messy/hacky to me if you have a more complex layout that flicks between row and column layouts. The whole point I imagine of flex-basis, was to do away with height and be able to handle a minimum "length" regardless of axis. I'm still in my early days with flexbox though, so correct me if I'm mis-interpreting.
In my use case, I did need X number of columns.
Ultimately, the only workaround I was satisfied with was the first suggested by @leereamsnyder which is what I originally implemented. But, this does mean sticking in extra markup for every flex child that you need padding for.
Would it be fair to say at this point that this is a bug? I definitely think it's worth highlighting somewhere.

Yes it most definitely is a bug and was fixed in October. When the new build ships this should no longer be an issue.

Any idea when that might be, @gregwhitworth?

@NoahBuscher I unfortunately can't speak to when the product will ship. Sorry.

Thank you @gregwhitworth for clarifying and good news. Meanwhile, is it worth sticking a note about this somewhere on here just to make anyone aware of it until the fix ships out.

I added flexbug 7 for this via d365e3a79e9771a94106a7ba35caa4f144b6d1bf.

I confirm that this bug is still actual and that it can be worked around using max-width

@olivvv I'm not sure what you're saying. Are you implying the current workarounds aren't sufficient?

No the workaround is fine, but if I understood this thread right, a fix was supposed to be implemented at browser level. I still see the bug in IE11. tbh its in a VM, I ll check tomorrow on a real pc.

if I understood this thread right, a fix was supposed to be implemented at browser level

The fix is in the Edge browser, not in IE11.

Using pseudo-elements instead of padding worked for my use case, as pseudo-elements doesn't count as width a priori. I still have to test in detail.


Unable to hide the extensions window

I have the activity pane disabled. I've opened the extensions window, via CTRL+SHIFT+X. I'm now unable to close the extensions window.
Here's a screenshot of what it looks like ...

Version 1.11.0-insider
Commit bc9a7bb1f90557c271c39628b5a3cdd7dfbc750c
Date 2017-03-30T08:11:58.005Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0

@ryancole Try Ctrl+b

@Tekbr that does close the extensions window, but also closes the file explorer window.

I think you are asking for something that does not exist: views in the sidebar are not overlapping each other, so you cannot close them. You can either hide the sidebar or make another view active.
Can you rephrase your request, do you expect a tabs like behaviour in the side bar?

@bpasero I think you're correct. I was using ctrl+shift+b to bring up the extensions pane. I thought it was overlapping the file explorer pane, but, as you just informed me, it's not actually overlapping. So, with that info, I now understand what it's doing and how to use it. I can bring back the file explorer pane with ctrl+shift+e.


Add KeR-7 from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of nesd, to add KeR-7 to CKAN.
Please direct questions about this pull request to nesd.
Mod details:
name = /mod/2398/KeR-7
author = nesd
abstract = Set of some Soviet parts missing in Making History DLC
license = MIT
Homepage = https://forum.kerbalspaceprogram.com/index.php?/topic/182898-nesds-warehouse/
description =
This is a small mod that expand Making History DLC
and add some missing parts for R-7/Sputnik/Vostok/Soyuz rocket

Two engines based Soviet/Russian RD-0109 and RD-0124 for stock 1.875 size
both engines have tube support with fire shield, like their prototypes

Central fuel tank for second stage of R-7 rocket, that can hide decoupler on upper side
And small triangle steering wing for 1st stage boosters

Color schemes created to match parts from Restock mod,
so they can be slightly different than original KSP colors.
Also included patch to disable steering lag on Cub engine
to make rockets more stable in flight.

Asked about MH dep and syntax:
https://forum.kerbalspaceprogram.com/index.php?/topic/182898-nesds-warehouse-new-mod-ker-7/page/2/&tab=comments#comment-3769468


Add general UX enhancements to setup.md

Add a summary table at beginning that lists all required components, the amount of disk space they require, and maybe a time estimate.
It wouldn't hurt to show people how to verify the amount of free disk space they currently have.
Clarify that only the Dart SDK is needed (not full-on Dart), and it is INCLUDED.
Clarify that both Dart and Flutter need to be successfully added to your path (.bashrc) - and give a way to verify.

#7971

Regarding item #4: I never need to add Dart to the path to use Flutter.

Clarify that only the Dart SDK is needed (not full-on Dart)

Not sure what this means? Dart SDK is the full-on Dart.
But yeah, the user doesn't need to manually install Dart. We download it for them.

Regarding item 4: I never need to add Dart to my path to use Flutter.

@InMatrix do you ever run the formatter? Not sure if we put the Dart SDK bin's into your path...

Users think they need a standalone Dart installation, and they don't.
Often they go out and find Dart and install it :-(
Then when they have to specify the path for the plugin, they give their
standalone path.
On Tue, Feb 21, 2017 at 5:25 PM, Seth Ladd<EMAIL_ADDRESS>wrote:

Clarify that only the Dart SDK is needed (not full-on Dart)
Not sure what this means? Dart SDK is the full-on Dart.
But yeah, the user doesn't need to manually install Dart. We download it
for them.
Regarding item 4: I never need to add Dart to my path to use Flutter.
@InMatrix https://github.com/InMatrix do you ever run the formatter?
Not sure if we put the Dart SDK bin's into your path...
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/7864#issuecomment-281537947,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWYL553VT0XJHROAsFe1G6ryVnIzcw2Bks5re45tgaJpZM4L25Bm
.

Presumably https://github.com/flutter/flutter-intellij/issues/750 is the source of the confusion?  If so, the right fix is fixing the plugin rather than our docs? FYI @devoncarew

There is no need to configure the Dart part in the plugin. This happens automatically when you fill in the Flutter SDK path.

Users think they need a standalone Dart installation, and they don't.

Should we make it more clear in the instructions that they don't need to download a separate Dart?
(which, I want to confirm that all the Dart SDK bins from Flutter's Dart SDK are available to the Flutter developers, so they can run the formatter? We don't wrap dartfmt in the flutter command, so the user needs to run dartfmt directly. If they didn't install the Dart SDK separately, will they have dartfmt in their path from Flutter?)

I haven't used dartfmt from command line, and the Flutter installation script didn't put Dart SDK bin into my path.

Why can't they use flutter format?
$ flutter format
No files specified to be formatted.

To format all files in the current directory tree:
flutter format .

Format one or more dart files.

Usage: flutter format <one or more paths>
-h, --help    Print this usage information.

Wasn't sure if that existed. Now I know :) I also see https://flutter.io/formatting/
So, yeah, doesn't sound like anyone needs to install a separate Dart SDK.

Should https://github.com/flutter/flutter/issues/7971 be merged into this?


tsconfig outDir parameter failing

Since i updated the typescript compiler, my tsc wasn't working. I experimented and as soon as i remove outDir parameter from compiler options in tsconfig.config file, it is now working.
TypeScript Version:  2.0.3

Can you share more information. Please share a self contained test along with the expected output, and the actual output.

The issue is with --outDir option in the tsconfig file. When i removed the option, now its working fine. I didn't got down deeper. Please let me know if more info is needed.

The issue is with --outDir option in the tsconfig file

can you elaborate on how it is failing, what is the current output?

There is no output. Just that the javascript files are not getting generated from the ts files.

I have a similar problem on TypeScript 2.0.3.
I specified outDir parameter end with "../" but tsc command didn't generate any .js files.
When I run same command on TypeScript 1.8.10, .js files were generated successfully.
I tested on this gist files.

Thanks @tom-konda  for the repro. This looks like the same issue as https://github.com/Microsoft/TypeScript/issues/11621.
If you do not have exclude property set, it is implicitly set to ["node_modules", .., <outdir>]. since your outDir is a parent directory of your source directory, no files are included in the compilation.
to override this behavior specify empty exclude array.

I have also filed https://github.com/Microsoft/TypeScript/issues/11156 to track raising an error when no files are found to compile.


Feature request: helm search should take creation date into account (support commit based versioning)

When searching for chart you get the "latest" chart available. However, this only works if the chart version are strictly .
In our company we version them -. When doing so the helm search command does not list the latest chart available. Seems to be a bit random which chart get listed.
From some investigation of the index.yaml file of the repository, there is a field created that could be used for truly filtering out the latest built
helm search demo-chart --versions
CHART VERSION   APP VERSION     DESCRIPTION
helm-virtual/demo-chart        0.1.0-ceeabeb   0.1.0-ceeabeb   Demo Chart
helm-virtual/demo-chart        0.1.0-ac79f53   0.1.0-ac79f53   Demo Chart
helm-virtual/demo-chart        0.1.0-7232d1f   0.1.0-7232d1f   Demo Chart
helm-virtual/demo-chart        0.1.0-20f09ca   0.1.0-20f09ca   Demo Chart
In this listing 0.1.0-7232d1f is the latest built chart.
Actual output:
helm search demo-chart
CHART VERSION   APP VERSION     DESCRIPTION
helm-virtual/demo-chart        0.1.0-ceeabeb   0.1.0-ceeabeb   Demo Chart
Expected output:
helm search demo-chart
CHART VERSION   APP VERSION     DESCRIPTION
helm-virtual/demo-chart        0.1.0-7232d1f   0.1.0-7232d1f   Demo Chart

/remove-lifecycle stale

closing as inactive.


[TypeChecker/CodeCompletion] Re-introduce expression sanitization bef…

…ore solving
A call to SanitizeExpr has been incorrectly removed from
typeCheckForCodeCompletion by refactoring to use ASTNode.
It is still required because fallback calls could have partially
type-checked AST.
Resolves: https://github.com/apple/swift/issues/59315
Resolves: rdar://94619388

Guys can approve this?
@ahoppen @hborla


Retain authentication attached to URLs when making requests to the same host

Closes https://github.com/astral-sh/uv/issues/1860
In https://github.com/astral-sh/uv/pull/1816, we started using the URL attached to a response instead of the request URL for subsequent requests — this fixes various bugs but has the side-effect of dropping credentials from the URL. Here, we transfer credentials from the request URL to the response URL. We perform RFC compliant checks for safety.

Fyi I tested this against AWS CodeArtifact.


Associate  official TARA contract addresses with ABIs

We need to associate and keep a map of addres<-> ABIs to decode events from our contracts:

DPOS
Multisend
Multicall
Claim

What we have:

Logs of transactions in the indexer.

What we can do:

Get tx from indexer.
If there are logs, call another endpoint to decode them.
Get decoded events.

Event decode Endpoint

Send tx hash
Get tx logs from indexer
Checks if logs are available
Checks if internal
Calls registry for ABI otherwise
Decodes event

Plan:

Add ABIs to taraxa-go-client since we fetch dpos from there.
Relative benchmark: 1 tx with 2 events takes 0.008s to decode on the DPOS side.
Hardcode internal addresses to these ABIs.
Get tx with logs, decode internal if addresses are matching.
Implement a registry contract as a general solution that holds the address -> abi relations.
Fetch the registry contract for ABI for other addresses


Detecting @Entity change and update DB

Hello everybody,
if I change the structure of an Entity (column name, ...) in my  hibernate spring (not boot)  application, is Flyway able to detect it and generate the appropriate DDL for it and update the database or should I use hibernate hbm2ddl to generate the SQL script?
It will be nice if flyway oofers us a DdlExporter that we can use and avoid a self exporter implementation :)
thanks!

Duplicate of #648


READY : Extend InnerFrom & FromInner derive macro

Now can write:
#[ derive( FromInner, InnerFrom ) ]
pub struct Age{ age: u32 }

let a: u32 = Age::from( 18 ).into();

Not clear what was the task?


PyMySql support

Description

Support the pure-python PyMySql library, while maintaining support for mysql-connector-python. This fixes #1529.
Motivation and Context

The mysql-connector-python package depends on externally hosted files and so doesn't install from pypi (#1529). While a third-party replacement is available (mysql-connector-python-rf), a pure python replacement (PyMySql) is available and actively maintained. Both libraries use nearly the same API, so luigi can support both with minimal effort.
Testing

A unit test for the mysqldb module is at test/_mysqldb_test.py. This requires the database parameters to be set to valid values, so it is disabled by default. To run it, I created new tox environments depending on either pymysql>=0.7 or mysql-connector-python-rf >= 2.0.0. The tests pass with either library, using py27 and mysql 5.5.
Currently the environments are not included in tox.ini, but I could easily add them if desired.

@ziky90

All tests passed except the py35-cdh environment, which timed out. I find it very unlikely that my code changes are responsible for the test failure on only that one environment. Can someone restart travis?

@sbliven I think closing and reopening this pull request should trigger travis to rebuild.


Remove exclamation mark (!) from error messages

There are some error messages that end with an exclamation mark (An error occurred!). However, error messages in Go shouldn't end with a . or ! and have to start with a lowercase letter: an error occurred.
Those error messages should be corrected.
Note: As this is an extremely simple task, please only pick it if you want to learn how PRs work. If you're more advanced, take a look at some of the other Hacktoberfest issues.

i would like pick up this issue


What Firewall rules do I need for nginx-proxy?

I have a simple nginx-proxy setup: (where subdomain.example.com is replaced with my domain)
docker run -d -p 80:80 -v /var/run/docker.sock:/tmp/docker.sock:ro jwilder/nginx-proxy
docker run -e VIRTUAL_HOST=subdomain.example.com kdelfour/cloud9-docker

It works with no problem when I have my firewall off. When I have my firewall on, I get a 504 Gateway Time-out error from nginx. This means that I'm able to see nginx on port 80, but my firewall rules seem to be restricting container-to-container and/or Docker API traffic.
Before I delve into the subject of Docker firewall rules, I thought I would ask if anyone has been down this path before. What firewall rules (preferably iptables) do in need to allow nginx-proxy to work? Thanks.

Have not run into this myself.  Are you blocking the docker bridge or have ICC disabled?

ICC is a Docker setting, so that wouldn't change when I turn my firewall on or off. I have rules to forward between docker0 and eth0, but I may still be blocking traffic on the docker0 bridge.
I did some research, but didn't find anything that addressed my particular situation. If my situation isn't common, perhaps this is a question for Stackoverflow.  For the sake of completeness, though, I'll post the details of my setup. I I'm running Ubuntu 15.04 and Docker 1.7.1. These are my iptables rules (these break nginx-proxy):
# Based on tutorial from http://www.thegeekstuff.com/scripts/iptables-rules / http://www.thegeekstuff.com/2011/06/iptables-rules-examples/

# Delete existing rules
iptables -F

# Set default chain policies
iptables -P INPUT DROP
iptables -P FORWARD DROP
iptables -P OUTPUT DROP

# Allow loopback access
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT

# Allow inbound/outbound SSH
iptables -A INPUT -i eth0 -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --sport 22 -m state --state ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --sport 22 -m state --state ESTABLISHED -j ACCEPT

# Allow inbound/outbound HTTP
iptables -A INPUT -i eth0 -p tcp --dport 80 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --dport 80 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --sport 80 -m state --state ESTABLISHED -j ACCEPT

# Allow inbound/outbound HTTPS
iptables -A INPUT -i eth0 -p tcp --dport 443 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT
iptables -A OUTPUT -o eth0 -p tcp --dport 443 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --sport 443 -m state --state ESTABLISHED -j ACCEPT

# Ping from inside to outside
iptables -A OUTPUT -p icmp --icmp-type echo-request -j ACCEPT
iptables -A INPUT -p icmp --icmp-type echo-reply -j ACCEPT
# Ping from outside to inside
iptables -A INPUT -p icmp --icmp-type echo-request -j ACCEPT
iptables -A OUTPUT -p icmp --icmp-type echo-reply -j ACCEPT

# Allow outbound DNS
iptables -A OUTPUT -p udp -o eth0 --dport 53 -j ACCEPT
iptables -A INPUT -p udp -i eth0 --sport 53 -j ACCEPT

# Allow outbound NTP
iptables -A OUTPUT -p udp -o eth0 --dport 123 -j ACCEPT
iptables -A INPUT -p udp -i eth0 --sport 123 -j ACCEPT

# This bit is from https://blog.andyet.com/2014/09/11/docker-host-iptables-forwarding
# Docker Rules: Forward chain between docker0 and eth0.
iptables -A FORWARD -i docker0 -o eth0 -j ACCEPT
iptables -A FORWARD -i eth0 -o docker0 -j ACCEPT
ip6tables -A FORWARD -i docker0 -o eth0 -j ACCEPT
ip6tables -A FORWARD -i eth0 -o docker0 -j ACCEPT

iptables-save > /etc/network/iptables.rules

And, this is what I mean when I say "firewall off": (It works with these settings.)
iptables -F
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT

I posted a question on Stackoverflow and it turns out there was a problem with the FORWARD chain, which I fixed by adding:
iptables -A FORWARD -i docker0 -j ACCEPT
Beats me how no one else has had this problem, but whatever. It's fixed.


[DM-33153] Convert to kubernetes_asyncio

Use the asyncio Kubernetes library, and propagate the async
status through the storage and service layer.  Convert the watch
queue to asyncio.Queue accordingly.
This allows us to throw regular exceptions from the watch task,
since it's now a normal asyncio task, and gets rid of the custom
thread pool stuff we had to do to background the watch thread.

This one wasn't actually ready for review; it was marked as draft. But thank you for the review! The only additional change that I'll be making is to use the new Safir support.
The changes to use kubernetes_asyncio were in a separate commit from the large cleanups. Is that enough to allow review of the interesting bit and then skipping over the commits that are just mechanical, or would it be better to have entirely separate PRs?

Ah, I misunderstood because I got assigned this ticket to review in Jira.

Yeah, sorry, I should have clarified more in Jira that there were several stages of review for this. I'm never sure how to represent that.
It's fine to ask for multiple PRs! Honestly, I probably could have just self-merged the mechanical changes since there's no point in reviewing them. I'll do that in the future. Thank you for the feedback!


Add physical limits to compu methods

Add properties LinearCompuMethod.physical_lower_limit and LinearCompuMethod.physical_upper_limit.
Katrin Bauer<EMAIL_ADDRESS>on behalf of MBition GmbH.
Provider Information

Thanks. This looks good! if nobody objects, I'll merge this tomorrow...

sorry, I somehow forgot to merge this last week. Merging, thanks for the contribution!


how to get params from url?

like url：  http://localhost:8080/abc?id=123
how to get the  123
or should I get it from http.request directly ?

@freboat yes ，you should get it from http.request directly.


Remove dist folder

Hello,
I would recommend, to remove a dist folder, as it is not an editable code, and is autogenerated by builder.
I think that this should be considered as a mistake.
Best regards,
Maciej Błędkowski

Removed! Thanks.


Add support for building w/ Swift Package Manager

This does not add support for running swift test, unfortunately. The
test dependency stuff seems to not be fully flushed out in the current
build and AFAIK, there's no way to point to a specific branch, only a tag.
So we can't actually point to the proper version of SwiftCheck right now
anyway.

Looks like there are some Carthage references in the project file besides the ones I commented on... should those be purged?

@tonyd256 SPM doesn't use the project file at all, it's completely ignored. So those changed won't matter for SPM. That was me trying to get the project working correctly again on its own.

👍


.travis.yml: Update Elixir version to match mix.exs

I believe this is no longer necessary after #132.


Previous console work for GDB does not work with LLDB

Jackson made changes in LLDB to support -gdb-set new-console on in LLDB to
mimic the way we do console/terminal windows in Windows.
NOTE: the changes from the lldb side are also required
This also includes a change to ignore SIGHUP at the debugger level and
pass it to the debuggee. This happens when the console/terminal window is
closed.

@edumunoz @jacdavis @gregg-miskelly @chuckries

:ship:

:+1:


[BugFix] Fix mistake use old serialized name in PrivilegeCollection introduced by #17582

Signed-off-by: HangyuanLiu<EMAIL_ADDRESS>What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #17582
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_admit_test

[FE PR Coverage Check]
:heart_eyes: pass : 1 / 1 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/privilege/PrivilegeCollection.java
1
1
100.00%
[]


applies the new conventions for imaging tools agreed at BioHackEU23

xref https://github.com/elixir-europe/biohackathon-projects-2023/blob/main/16/conventions.md

FOR CONTRIBUTOR:

[x] - I have read the CONTRIBUTING.md document and this tool is appropriate for the tools-iuc repo.
[x] - License permits unrestricted use (educational + commercial)
[ ] - This PR adds a new tool or tool collection
[x] - This PR updates an existing tool or tool collection
[ ] - This PR does something else (explain below)

The new tool versions are not found by update-tool.py from the usegalaxy-eu/usegalaxy-eu-tools repo.
For example:
python scripts/update-tool.py --owner bgruening --name cp_cellprofiler4 imaging.yaml
INFO:root:Fetching updates for bgruening/cp_cellprofiler4

I guess this is due to the following error in the CI:

Unsuccessful tests found, inspect the 'All tool test results' artifact for details.

Errored Tests
❌ cp_mask_image (Test #1)
Execution Problem:
Input staging problem: History not found

Strangely the error was not reported by the PR CI.
I have no clue what "Input staging problem: History not found" means, any ideas? @bgruening

The new tool versions are not found by update-tool.py from the usegalaxy-eu/usegalaxy-eu-tools repo.
For example:
$ python scripts/update-tool.py --owner imgteam --name 2d_auto_threshold imaging.yaml
INFO:root:Fetching updates for imgteam/2d_auto_threshold

This is the error reported by CI:

Run peter-evans/create-or-update-comment@v2
with:
issue-number: 73
body: Attention: deployment skipped!
https://github.com/BMCV/galaxy-image-analysis/actions/runs/6746556561
env:
GALAXY_FORK: galaxyproject
GALAXY_BRANCH: release_23.0
MAX_CHUNKS: 4
MAX_FILE_SIZE: 1M
Error: Parameter token or opts.auth is required

Could this maybe be due the linting issues? @bgruening
The updates from https://github.com/bgruening/galaxytools/pull/1346 are also concerned, although it seems for a different reason (xref https://github.com/BMCV/galaxy-image-analysis/pull/71).

I uploaded manually and pushed ...

I uploaded manually and pushed ...

@bgruening Could it be that your comment was actually meant for https://github.com/bgruening/galaxytools/pull/1346? Because the new revisions of the tools from the bgruening/galaxytools repo are now there, but the revisions of the tools from this repo (GIA) are not :)

Upps, this can very well be. You had too many PRs in my tabs :)
Happy to merge your PR against the tools-install repo if you take it out ot Draft.

Upps, this can very well be. You had too many PRs in my tabs :)
Happy to merge your PR against the tools-install repo if you take it out ot Draft.

@bgruening My intention was to bundle the updates from this PR + https://github.com/bgruening/galaxytools/pull/1346 into a single PR for usegalaxy-eu, so that there will be fewer PRs for you to have a look at :)
That said, the updates from this PR are still not found (as described above). Any idea why that is?

I just assume that our CI here is not up to date and it does not deploy on linting errors. A thing we fixed on IUC already.
https://github.com/BMCV/galaxy-image-analysis/actions/runs/6746556561

Deployment still fails even after updating the CI (#78).
https://github.com/BMCV/galaxy-image-analysis/actions/runs/6810454241/job/18519017525
Did I miss something?
The only difference left between the pr.yaml of this repo and the IUC version, aside from repository names, is GALAXY_BRANCH: release_23.0, which is release_23.1 in IUC. Must this be incremented?


Update references for conformance

This renames all references and usages to the old crosstest repo so that they begin using the new connectrpc/conformance repository in the connectrpc organization.
Note this is not intended to merge (or build successfully) until the crosstest repo is officially moved.

Closing this because I'm going to split this up into PRs.


Enable explicit setting of protocol

var scriptSource = '//www.google-analytics.com/analytics.js'; (https://github.com/revolunet/angular-google-analytics/blob/master/src/angular-google-analytics.js#L396)
When the angular application is a native mobile application (e.g. by using cordova), the protocol will be file:// since its beeing executed inside a webview. I see no possibility to set the protocol explicitly to https://
This issue is kind of related with issue #31

Released to Bower. Pending release to NPM.


bug in Camera Controls

there's a bug in the extension "Camera Controls" where the bubble of the "say" and "think" block does not go outside the stage size, it stays clamped inside the stage even if "Remove Fencing" has been enabled in advanced

another example

I am consolidating all the camera controls issues into https://github.com/TurboWarp/extensions/issues/930


Edit machine-learning-walkthrough-5-publish-web-service.md

Edit complete.

Hi @ShawnJackson, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


H264 Video Playback

The problem is to play streaming h264 video coming over UDP, and send back data about the position of the head.
For h264 playback, FFmpeginteropX works well in classic 2D UWP. The problem is to simultaneously send back data about the position of the head. Is it possible to somehow display the standard Media Player in stereo kit, or maybe there are other options for how to integrate FFmpegInteropX and StereoKit? Perhaps you can recommend something else to solve this problem?
With respect,
Denis

Hey, thanks for bringing this up! This sounds like a remote rendering sort of use case, is that right?
What platform are your running on? If this is HoloLens, would something like Holographic Remoting (#255) work for you instead, or are you mostly interested in video decode (#243)?

Sorry, for taking so long for answer
Yes, I work with Hololens2
All I need is to play a live (raw h264 stream via UDP)  video on a 3d object. I learned how to do this in collaboration with Unity. To do this, I use FFmpeginterop as a MediaSource, and then run MediaPlayer in frame server mode. It works really well, I will definitely try to do the same with stereokit. I hope the performance with stereo kit will be higher.

Sorry, for taking so long for answer Yes, I work with Hololens2 All I need is to play a live (raw h264 stream via UDP) video on a 3d object. I learned how to do this in collaboration with Unity. To do this, I use FFmpeginterop as a MediaSource, and then run MediaPlayer in frame server mode. It works really well, I will definitely try to do the same with stereokit. I hope the performance with stereo kit will be higher.

Hi mosaviaDC!
Could you tell me how you did this Unity Integration?


Enforce GitHub issues in checkstyle configuration

Trying to change checkstyle.xml TodoComment doesn't seem to have any effect when running mvn validate -Pcheckstyle.
Also note that mvn checkstyle:check doesn't use that configuration.

Trying to change checkstyle.xml TodoComment

What's not working exactly, this works for me. By default checkstyle TodoComment matches only TODO case sensitive.

Also note that mvn checkstyle:check doesn't use that configuration.

This is by design, but the GitHub job uses validate with the proper profile, so it properly validate checkstyle. For speed locally you can use make checkstyle.


HADOOP-19065. Improve Protocol Buffers install instructions.

Description of PR
JIRA: https://issues.apache.org/jira/browse/HADOOP-19065

When downloading 'Protocol Buffers', there is no progress bar, Not very friendly for user.

The '-s' param is Silent mode, and if the network is blocked, without prompt, Not very friendly either.

Now, remove the -S -s param, Consistent with the install steps of CMake 3.19, concise and easy to understand.

reference: CMake 3.19

  CMake 3.19
  $ curl -L https://cmake.org/files/v3.19/cmake-3.19.0.tar.gz > cmake-3.19.0.tar.gz
  $ tar -zxvf cmake-3.19.0.tar.gz && cd cmake-3.19.0
  $ ./bootstrap
  $ make -j$(nproc)
  $ sudo make install

Additional:  Update all versions of protobuf to 3.21.12, We have started using protobuf 3.21 by HADOOP-19069.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 48s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
shadedclient
47m  8s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shadedclient
39m 18s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

92m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6526

Optional Tests
dupname asflicense codespell detsecrets

uname
Linux 0f6f6c4adbb3 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 88d2d8cb4a078db4fc8116b24cc3e4968f26ba70

Max. process+thread count
531 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

someone who knows curl better than me will need to review this

Hi @tasanuma  Can you help me review it? Thanks.
Thanks @steveloughran.

Although I'm not an expert in curl, I believe this change is fine as it aligns with the instruction for CMake. However, in the first place, protobuf 3.7.1 could be outdated. We have started using protobuf 3.21 by HADOOP-19069.

@huangzhaobo99 Thanks for updating it, but there are still many mentions of Protocol Buffers 3.7.1 in BUILDING.txt. If we want to update all them to version 3.21.12, we firstly need to update the Dockerfile and install-protobuf.sh to install protobuf 3.21.12, and we must make sure that Hadoop can still be built successfully.

@tasanuma Thanks for the reminder. I will complete it after.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 39s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ trunk Compile Tests _

+1 :green_heart:
shadedclient
41m 24s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shadedclient
34m 51s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

82m 39s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6526

Optional Tests
dupname asflicense codespell detsecrets

uname
Linux 4adb15f13af3 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f470b40885bbefc647bb019f6fce8d659898af94

Max. process+thread count
712 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/2/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@tasanuma Have completed, Whether or not need to modify the PR title?

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/3/console in case of problems.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/4/console in case of problems.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
52m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
hadolint
0m  0s

hadolint was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1 :x:
mvninstall
4m 31s
/branch-mvninstall-root.txt
root in trunk failed.

-1 :x:
mvnsite
0m  9s
/branch-mvnsite-root.txt
root in trunk failed.

-1 :x:
shadedclient
6m 10s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m 29s
/patch-mvninstall-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-1 :x:
mvnsite
0m 24s
/patch-mvnsite-root.txt
root in the patch failed.

+1 :green_heart:
shadedclient
1m 18s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 24s
/patch-unit-root.txt
root in the patch failed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

67m 14s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6526

Optional Tests
dupname asflicense codespell detsecrets hadolint shellcheck shelldocs mvnsite unit

uname
Linux 4f263dea2f4f 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b0f9f311af3deb8273bc60238af2b4d620fd7ce8

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/4/testReport/

Max. process+thread count
56 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/4/console

versions
git=2.9.5 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/5/console in case of problems.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
hadolint
0m  0s

hadolint was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

-1 :x:
mvninstall
0m 24s
/branch-mvninstall-root.txt
root in trunk failed.

-1 :x:
mvnsite
0m 24s
/branch-mvnsite-root.txt
root in trunk failed.

-1 :x:
shadedclient
2m 14s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m  9s
/patch-mvninstall-root.txt
root in the patch failed.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-1 :x:
mvnsite
0m 29s
/patch-mvnsite-root.txt
root in the patch failed.

-1 :x:
shadedclient
2m 50s

patch has errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
0m 24s
/patch-unit-root.txt
root in the patch failed.

+0 :ok:
asflicense
0m 25s

ASF License check generated no output?

11m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6526

Optional Tests
dupname asflicense codespell detsecrets hadolint shellcheck shelldocs mvnsite unit

uname
Linux e1a4968923ae 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 62390b2dec0d3fad3332d908168a09f8914969df

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/5/testReport/

Max. process+thread count
51 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/5/console

versions
git=2.9.5 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Pipeline failed, but the local env launched docker image was successfully built and compiled. cc @tasanuma

Install Docker and run this command:

./start-build-env.sh

trigger compile:

mvn package -Pdist -DskipTests -Dtar -Dmaven.javadoc.skip=true

[INFO] Apache Hadoop Cloud Storage ........................ SUCCESS [  3.984 s]
[INFO] Apache Hadoop Cloud Storage Project ................ SUCCESS [  0.016 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  16:56 min
[INFO] Finished at: 2024-02-22T02:39:26Z
[INFO] ------------------------------------------------------------------------
xxx@886b0e5bc37b:~/hadoop$

check docker env protobuf version:

protoc --version

libprotoc 3.21.12

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/6/console in case of problems.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
hadolint
0m  0s

hadolint was not available.

+0 :ok:
shellcheck
0m  0s

Shellcheck was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 53s

trunk passed

+1 :green_heart:
mvnsite
19m 31s

trunk passed

+1 :green_heart:
shadedclient
99m  9s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
30m 56s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
16m  3s

the patch passed

+1 :green_heart:
shadedclient
48m  1s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
16m 12s

root in the patch passed.

+1 :green_heart:
asflicense
1m  5s

The patch does not generate ASF License warnings.

200m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6526

Optional Tests
dupname asflicense codespell detsecrets hadolint shellcheck shelldocs mvnsite unit

uname
Linux ee637f0b52b8 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 62390b2dec0d3fad3332d908168a09f8914969df

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/6/testReport/

Max. process+thread count
560 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6526/6/console

versions
git=2.9.5 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@huangzhaobo99 Do you have any actual environment to use these dockerfiles? This involves many operating systems, and I am not sure whether it can really be executed normally.
cc: @tasanuma @steveloughran

@huangzhaobo99 Do you have any actual environment to use these dockerfiles? This involves many operating systems, and I am not sure whether it can really be executed normally.
cc: @tasanuma @steveloughran
@slfan1989 It has been verified, including manual installation.

@huangzhaobo99 Do you have any actual environment to use these dockerfiles? This involves many operating systems, and I am not sure whether it can really be executed normally.
cc: @tasanuma @steveloughran

@slfan1989 It has been verified, including manual installation.

Thanks for the feedback, this is good news.

@slfan1989 docker worked on the 3.3.6 release for me with macbook m1 for arm and AMD x86 on EC2 for x86 release. doing that in US-west-2 built pretty fast as that is where the maven central repo is


Pinecone1.0.x ~ Bun Integration

See issue here: https://github.com/pinecone-io/pinecone-ts-client/issues/141

Pinecone is working on it, with Bun related CI tests being added as well!
https://github.com/pinecone-io/pinecone-ts-client/pull/145


delete key should delete the object from the scene when it is highlighted

Behavior questions:

Should the delete key with an object selected remove any variables that aren't used anywhere else?
For now should you only be able to delete bodies in default mode, segments/points in sketch mode?

First attempt at this works for any entity that's defined "inline" but not if they're generated from a user-created function:
https://github.com/KittyCAD/modeling-app/assets/23481541/8c892360-0449-4833-9de5-970edf159e73
I think we need to map entities to code ranges differently so that entities generated from user-authored functions resolve to their top-level constant declaration, not the startSketchOn call within the function. I'll post a comment to discuss in there but since I recorded this in Slack anyway I'll leave it here too


[Bug]: Cart Sidebar -  cannot remove product or add more items

Expected Behavior
Products on Cart Sidebar element should behave as expected:

can be removed from Cart
can add more items
'save for later' button can be removed from this view I suppose (to be discussed)

Actual Behavior

Possible Solution
No response
Steps to reproduce
No response
What version of vendure integration are you using?
1.0.0.
What version of Node.js are you using?
16.13.2
What browser (and version) are you using?
Chrome Version 98.0.4758.80 (Official Build) (64-bit)
What operating system (and version) are you using?
Ubuntu
Relevant log output
No response
Code of Conduct

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

Hey, could you please check what is going on in the network/console tab of the browser? Also could you take a look at Vendure server to investigate whether the changes to the cart are actually happening on Vendure?

I ran into this issue as well. This integration transforms the bearer token that vendure sets for the guest user when they create an order into a cookie. The cookie has the "Secure" option so chrome won't set the cookie if you are not using https. Having the cookie set is required for any edits to the active order.

@Baroshem Vendure uses a session token for guest orders. My browser is what rejected the session cookie because it was marked as secure. This is no longer an issue for me as I am now serving my storefront with https in my test environment.
https://github.com/vuestorefront-community/vendure/blob/develop/packages/api-client/src/helpers/cookie.ts
This code marks the cookie as secure.

I see however, I am also using Chrome for development and serving the dev server locally on http, not https and it is working for some reason 🤔

@jacobfrantz1 Thanks for solving it, when I changed the cookie to secure:false it works. But it is strange that it works properly for @Baroshem without any change. Maybe there is some other difference in your configuration?

Maybe it has to do with the operating system. But I have seen @michaelbromley creating a demo store while working on Windows. Really really strange. Maybe as a workaround, we could add a condition here so that value of secure will be set to false in dev environment and true in prod?
Something like:
...
secure: process.env.production ? true : false

That's right, I use Windows 10 for all my development. Perhaps the issue has to do with the domain. Secure cookeis will only be set over HTTPS except when the domain is localhost - in some browsers. See here for more details: https://web.dev/when-to-use-local-https/#use-http:localhost-by-default

in my case if i increase the amount on an item in the cart, the item just vanishes.
The api returns: "GraphQL error: Die Bestellung beeinhaltet keine OrderLine mit der ID 40"
it means in english something like "The order does not contain OrderLine with ID 40"

@macrozone
Could you provide some reproduction repository?

@macrozone
Could you provide some reproduction repository?

nevermind, was a cookie error.
the cart is still very buggy though. E.g. after a checkout, the cart is still there, but you cant add any items, it throws an error
{"data":{"addItemToOrder":{"errorCode":"ORDER_MODIFICATION_ERROR","message":"Der Inhalt der Bestellung kann nur im Status \"AddingItems\" geändert werden","__typename":"OrderModificationError"}}}

@macrozone
Could you provide more details (ideally a reproduction repo)? I could try to reproduce it on my side. These issues are really strange because cart operations were there for about few months now, so these issues appear out of nowhere.

Once an Order is completed (by default this occurs when it transitions to the PaymentAuthorized or PaymentSettled states), it get set to active: false and should no longer be accessible via the activeOrder query in the Shop API.
So yes, it sounds like maybe an error is occurring at the payment stage. If you are able to isolate the steps which reproduce it, please open an issue on the Vendure repo.
Regarding error handling in VSF, pretty much all mutations in Vendure will return a union result containing either the expected object or an ErrorResult type.
The recommended way to handle this in the storefront is to select and check the __typename field when the response from the mutation is returned. If the __typename is not the expected type, e.g. 'Order' then we can assume an error ocurred and display some generic toast notification with the errorMessage.


grpc 0.15.2 errors when compiling with gcc-6.1.0 on recent MSYS2

gRPC seems not yet ready for gcc 6.1.0, or at least not in MSYS2 when compiled with the mingw64 compiler. I get several errors like
src/core/lib/iomgr/iomgr.c: In function 'grpc_iomgr_shutdown':
src/core/lib/iomgr/iomgr.c:100:17: error: unknown conversion type character 'l' in format [-Werror=format=]
                 "Waiting for %" PRIuPTR " iomgr objects to be destroyed",
                 ^~~~~~~~~~~~~~~
src/core/lib/iomgr/iomgr.c:100:17: error: too many arguments for format [-Werror=format-extra-args]
src/core/lib/iomgr/iomgr.c:118:32: error: unknown conversion type character 'l' in format [-Werror=format=]
             gpr_log(GPR_DEBUG, "Failed to free %" PRIuPTR
                                ^~~~~~~~~~~~~~~~~~
src/core/lib/iomgr/iomgr.c:118:32: error: too many arguments for format [-Werror=format-extra-args]
src/core/lib/iomgr/pollset_windows.c: In function 'grpc_pollset_shutdown':
src/core/lib/iomgr/pollset_windows.c:110:3: error: ignoring return value of 'grpc_pollset_kick', declared with attribute warn_unused_result [-Werror=unused-result]
   grpc_pollset_kick(pollset, GRPC_POLLSET_KICK_BROADCAST);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/core/lib/iomgr/pollset_windows.c: In function 'grpc_pollset_kick':
src/core/lib/iomgr/pollset_windows.c:232:7: error: ignoring return value of 'grpc_pollset_kick', declared with attribute warn_unused_result [-Werror=unused-result]
       grpc_pollset_kick(p, specific_worker);
       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1.exe: all warnings being treated as errors
make: *** [Makefile:2151: /tmp/mingw-w64-grpc/src/build-x86_64-w64-mingw32/objs/opt/src/core/lib/iomgr/pollset_windows.o] Error 1
==> ERROR: A failure occurred in build().
    Aborting...
Error making package mingw-w64-grpc, aborted.

Yay, new gcc...

:-) Its not really my preference either, but its just what's shipped with MSYS2 now...

I could fix this in MSYS2 by removing their default build define -D__USE_MINGW_ANSI_STDIO=1 from the PKGBUILD. Closing as fixed because there is a suitable workaround for MSYS2 / MinGW64.


Handle subnets in existing vnet

If vnet exists, then create a new subnet with required values provided from user. If vnet and subnet exists then accept resource id of subnet resource

Still need to addresses


Tried to fix linebuffer wraparound error when the depth of the buffer is not a power of 2

I've gotten the conv examples to run in the interpreter and compiled code simulator, but noticed that the linebuffer read and write indexes do not wrap around at the right place when the depth of the buffer is not a power of 2, so for example when the linebuffer in conv_3_1 has depth 10 it is indexed by a 4 bit address with a max value of 16, but the raddr, and waddr registers in linebuffermem just keep incrementing until they get to 15 and then reset since they are 4 bit numbers, causing the simulator to crash.
I have tried to fix this by updating the linebuffermem definition so that when depth is not a power of two the incremented value gets compared to the depth and set to 0 if the next value is equal to the depth.
I have also added LinebufferMem unit tests to /tests/simulator/interpreter.cpp for both the power of 2 and non-power of 2 cases.
@rdaly525 can you take a look and see if the changes to LinebuffereMem make sense?

@dillonhuff, looks like this failed on travis. Could you investigate?


support read-writeOnce

The code generated from the file STM32L063x.svd doesn't compile. Because the read-writeOnce access mode is not supported by svd2rust the DAC_SR register has no access methods:
# [ doc = "Digital-to-analog converter" ]
pub mod dac {
    // ..
    # [ doc = "status register" ]
    pub struct Sr {
        register: VolatileCell<u32>,
    }
    # [ doc = "status register" ]
    pub mod sr {
        impl super::Sr {}
    }
}

And you run into an unused field warning which becomes an error because of #![deny(warnings)].

I will contribute to this issue instead of making a new since I suspect these issues are the same.
When using svd2rust on NXP S32K144 svd file i get:
svd2rust -i ~/Nedlastinger/S32K144.svd | rustfmt | tee src/s32k144.rs
thread 'main' panicked at 'unknown access variant: writeonce',
/home/kjeka/.cargo/registry/src/github.com-1ecc6299db9ec823/svd-parser-0.5.1/src/lib.rs:286
note: Run with `RUST_BACKTRACE=1` for a backtrace.

and with RUST_BACKTRACE=1
RUST_BACKTRACE=1 svd2rust -i ~/Nedlastinger/S32K144.svd | rustfmt | tee src/s32k144.rs
thread 'main' panicked at 'unknown access variant: writeonce',
/home/kjeka/.cargo/registry/src/github.com-1ecc6299db9ec823/svd-parser-0.5.1/src/lib.rs:286
stack backtrace:
   0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace
             at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1: std::sys_common::backtrace::_print
             at /checkout/src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at /checkout/src/libstd/sys_common/backtrace.rs:60
             at /checkout/src/libstd/panicking.rs:355
   3: std::panicking::default_hook
             at /checkout/src/libstd/panicking.rs:371
   4: std::panicking::rust_panic_with_hook
             at /checkout/src/libstd/panicking.rs:549
   5: std::panicking::begin_panic
             at /checkout/src/libstd/panicking.rs:511
   6: std::panicking::begin_panic_fmt
             at /checkout/src/libstd/panicking.rs:495
   7: <core::option::Option<T>>::map
   8: <core::iter::FilterMap<I, F> as core::iter::iterator::Iterator>::next
   9: svd_parser::Device::parse
  10: svd_parser::parse
  11: svd2rust::main
  12: __rust_maybe_catch_panic
             at /checkout/src/libpanic_unwind/lib.rs:98
  13: std::rt::lang_start
             at /checkout/src/libstd/panicking.rs:433
             at /checkout/src/libstd/panic.rs:361
             at /checkout/src/libstd/rt.rs:56
  14: __libc_start_main
  15: _start

I will attach the file in case you would like to test for yourself.
S32K144.svd.zip

@kjetilkjeka Your error is not related, it comes from a miswritten svd file, the variant is called writeOnce, not writeonce. We could fix this in svd-parser, but I think we should strive to follow the SVD 1.0/1.1 schema as close as possible.
To fix your error and generate some code simply patch your svd to change all the writeonce into writeOnce.

@Emilgardis You are of course right. It worked when replacing writeonce with writeOnce, thanks.
And for what it's worth I do agree with your view on forcing the svd to be up to spec rather than accepting badly written svd files.

Implemented by #322.


As a contributor, I want an easy way to start developing medulla

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@AndrewBabbitt97 Is this issue complete by introducing Tye?


Add sub unit support to money object

Hey,
This pr should enable a get_amount_in_sub_unit method for money objects. The configuration is also set and it reflects here https://github.com/sebastianbergmann/money/blob/master/src/Currency.php.
Thanks

closing this, as i messed up the branch.


Metadata, Precision, Scale and Formulas in Calculate Fields

I 'm adapting my model to use EF7 , I need to upload the metadata of each entity and each field for different tasks that do not use EF directly, I managed to solve most through IEntityType interface and Sql Server extension, but there are three that I can not get.
They are: Precision, Scale in the numerical values and formulas for calculated fields.
There would be some way using EF to obtain these values. I know I can get them directly from the database but I would like to load them as I do with others.
Thank you.

@JuanIrigoyen EF metadata does not currently store precision or scale since these are never used in the EF code. Default or computed values can be accessed using metadata extensions, such as property.SqlServer().ComputedColumnSql where "property" is an IProperty from the model.

I think EF 7 should return precision & scale as it does with attributes like maxlenght as part of the metadata fields, this can be very useful for example to set the masks of some controls. Great work by the facility to access metadata compared to version 6, thank you very much for your reply

Max length is exposed in EF metadata if it is set when building the metadata, but it is not inferred into the metadata based on store type. For example, setting the store type to varchar(200) will not result in a max length in EF metadata of 200. Another way to think of this is that max length may be used as an input to type mapping, but the type mapping itself does not affect core metadata.
Given this, if metadata had precision and scale, then it would only be included in metadata if set when building the model. It would not be inferred from the store type. But EF does not do this, and so it is not needed in the model.
If you have additional metadata about your model that is not used by EF but which you wish to reference, then you can always store that metadata as annotations on the property, type, etc., and then refer to it later when doing things like creating masks.


Add CMake LINK_DEPENDS_NO_SHARED property as a parameter to the Facel…

The reason behind adding LINK_DEPENDS_NO_SHARED as a parameter:

LINK_DEPENDS_NO_SHARED can't be a global property. It might be set only for a specific target and since facelift CMake API changes the name of the target the most correct way of adding it is to add it as a parameter.
The second solution would be to set/unset CMAKE_LINK_DEPENDS_NO_SHARED every time facelift API is called in the client but IMHO it looks more hackish and less straightforward.

I do not understand why you say "The second solution would be to set/unset CMAKE_LINK_DEPENDS_NO_SHARED every time facelift API is called". CMAKE_LINK_DEPENDS_NO_SHARED can be set once for all. CMake will effectively apply it to the libraries of the correct type.

I do not understand why you say "The second solution would be to set/unset CMAKE_LINK_DEPENDS_NO_SHARED every time facelift API is called". CMAKE_LINK_DEPENDS_NO_SHARED can be set once for all. CMake will effectively apply it to the libraries of the correct type.

The problem is that I do not want to apply it to all targets (yes - it would be applied not only to libraries).

DO_NOT_RELINK_SHARED is meaningless and is inconsistent with CMake's LINK_DEPENDS_NO_SHARED. Keep CMake terminology.

Closing as outdated.


Standard mode usage (start, stop, pause, continue, restart)

System information

OS Platform and Distribution:  (e.g., Linux Ubuntu 16.04)
Apollo installed from: binary
Apollo version: 3.0

Steps to reproduce the issue:

switch on standard mode in dreamview
switch on Canbus, Gps, control, planning, routing, localization
"Start Auto" button  is inactive.

Why so?
How can I start, pause and stop current routing session?
How can I apply routing request after completed another one? (Now I have to restart planning module)

A1. Some modules don't start or there is some exceptions throwed , like perception or not ?
A2&A3.  There is no need to restart planning, When you are in auto mode ,you can send another routing.

Closed due to inactivity. If the problem persists, pls feel free to reopen it or create a new one and refer to it.


Update reward cards to play nicely with new transfer API default page size

The Chore
The default page wise for transfer API will change from 1000 to 50 because Edd doesn't have enough buckets to handle the data :-D
Tasks

[ ] check rewards page
[ ] check competitions page

Additional details / background info
Core 🎫  https://github.com/vegaprotocol/vega/issues/10685
Pagination bug 🎫  https://github.com/vegaprotocol/vega/issues/10837

https://vegaprotocol.slack.com/archives/C9E6XA8GK/p1709735484822469


Changed logo to something more relevant

resolves #56

Pull Request Test Coverage Report for Build 104

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.083%

Totals

Change from base Build 99:
0.0%

Covered Lines:
1672

Relevant Lines:
1920

💛  - Coveralls


How to start this script?

Can I do npm start?
Also is it possible to deploy it to firebase to make a forum website?

The library is not yet ready for third-party use, unfortunately; it has too many "unmentioned dependencies" on components from my main project environment. (you can see the list of things it needs provided to it in: https://github.com/Venryx/firebase-forum/blob/master/Source/Manager.ts)
The good news is that I am currently updating several of my libraries from using Redux to MobX, and in the process, I am also working to make them "well modulized", where the API is realistically usable in other projects. (for example, it won't require passing in functions from a specific router library, a specific place to store user data, etc.)
Sorry for the delay; I didn't expect random people to be finding the library just from searches, so did not prepare the library for use in other projects from the start.
When the library is ready for third-party use, I will update the readme with usage instructions. (thus closing this issue)

Hi, any progress?

Not really, no; it's not a high priority at the moment, due to the bare-bones nature of the library currently + more importantly, the fact that it is enmeshed with other libraries of mine right now.
Perhaps this could work as an alternative: https://github.com/hoppula/refire-forum


Bug - handling '|' char in filename

Description: | in a title is not properly replaced and throws an invalid character error during note filename creation.
Console output:
Uncaught (in promise) Error: File name cannot contain any of the following characters: * " \ / < > : | ?
    at we (app.js:1:244125)
    at t.checkPath (app.js:1:970824)
    at t.<anonymous> (app.js:1:972709)
    at app.js:1:235078
    at Object.next (app.js:1:235183)
    at app.js:1:234120
    at new Promise (<anonymous>)
    at m (app.js:1:233865)
    at t.create (app.js:1:972597)
    at ReadItLaterPlugin.eval (plugin:obsidian-read-it-later:6619:54)

How to reproduce: try to capture a youtube video containing a | char in the video title (example: https://www.youtube.com/watch?v=kPPq3dCe0Z0)
Tested on: plugin v 0.0.15 / Obsidian 0.15.9 on w11

Character "|" is striped from filename successfully. Problem is in the second double quote. Right now, normalizeFilename function stripes just first occurrence of character from list of illegal symbols. I'm working on fix.

Fixed in 0.0.16


GraphQL is not getting exposed on a different endpoint

I have tried using
graphql:
servlet:
mapping: /test
enabled: true
corsEnabled: true
GraphQL is not getting exposed on a different endpoint
I did not see any which way where /graphql van be exposed to some other point
Also /graphql is giving 400 bad request, it is only expecting query parameters
Only /graphiql is working which is a html page
How can we expose /graphql or any user defined url  as as endpoint with post body?

Wrong project again, you need to create the issue over here: https://github.com/graphql-java/graphql-spring-boot


Initial implementation for some basic 2D charts

Initial Implementation (with a lot of customizable properties) of:
*BarChart
*LineChart
*MultiBarChart
*MultiLineChart

Should I wait for?
PENDING: *StackedBarChart -> IN PROGRESS *CandleChart -> IN PROGRESS *Support for negative values -> IN PROGRESS *Support for Horitontal/Vertical modes in ALL charts -> IN PROGRESS *3D BarChart -> IN PROGRESS
Or review/merge this and the rest will be in another PR?

Go ahead , i already updated the description. That will go on a separate PR when its ready :D


Fix bug UI tags with long names

Hi @vincelwt I would like to work on this issue

Hi @Dhoni77,
We'd be glad if you could work on that. Let us know if you need any assistance setting up the project.

Hi @hughcrt would love to work on this. May I know how to reproduce this issue?

Hi @fitrahfm ,
You need to use tags with long names: https://llmonitor.com/docs/features/tags?lang=js
Let me know if you can't reproduce it


feat(core): make initialisation object of i18n configurable

SFO-126
Description
make initialisation object of i18n configurable
Fixes # (issue)
#56
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Performed a self-review of my own code
[ ] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

@vineet-suri there is an error in linting. Please fix it.


State "dysonairpurifier.0.xxx.Sleeptimer" has no existing object, this might lead to an error in future versions

hey
ich hab jetzt die 3.1.10 installiert und dazu mal alle Datenpunkte gelöscht.
jetzt wurden bei beiden Geräten erst gar nicht der sleeptimer angelegt.
beim humidify + cool bekomme ich im log die oben angeführte Fehlermeldung.
beim pure cool gibs keine fehlermeldung.
bei beiden fehlt der datenpunkt.
meine annahme: humidify + cool wird scheinbar abgefragt aber der datenpunkt wurde nicht angelegt, so erscheint mir der Inhalt der fehlermeldung
der pure cool wird gar nicht erst abgefragt, da es von ihm keine Fehlermeldung gibt.

Okay - dann schreib bitte mal ein debug-Log und poste das hier.
Dann sehen wir hoffentlich was los ist.

2024-05-14 20:52:51.196 - debug: dysonairpurifier.0 (6705) Redis Objects: Use Redis connection: <IP_ADDRESS>:9001
--
2024-05-14 20:52:51.258 - debug: dysonairpurifier.0 (6705) Objects client ready ... initialize now
2024-05-14 20:52:51.260 - debug: dysonairpurifier.0 (6705) Objects create System PubSub Client
2024-05-14 20:52:51.261 - debug: dysonairpurifier.0 (6705) Objects create User PubSub Client
2024-05-14 20:52:51.367 - debug: dysonairpurifier.0 (6705) Objects client initialize lua scripts
2024-05-14 20:52:51.376 - debug: dysonairpurifier.0 (6705) Objects connected to redis: <IP_ADDRESS>:9001
2024-05-14 20:52:51.441 - debug: dysonairpurifier.0 (6705) Redis States: Use Redis connection: <IP_ADDRESS>:9000
2024-05-14 20:52:51.504 - debug: dysonairpurifier.0 (6705) States create System PubSub Client
2024-05-14 20:52:51.506 - debug: dysonairpurifier.0 (6705) States create User PubSub Client
2024-05-14 20:52:51.780 - debug: dysonairpurifier.0 (6705) States connected to redis: <IP_ADDRESS>:9000
2024-05-14 20:52:51.880 - debug: dysonairpurifier.0 (6705) Plugin sentry Initialize Plugin (enabled=true)
2024-05-14 20:52:52.183 - info: dysonairpurifier.0 (6705) starting. Version 3.1.10 (non-npm: Grizzelbee/ioBroker.dysonairpurifier#0b4e707bfe64838a8ca0f2925b16f77e41583e35) in /opt/iobroker/node_modules/iobroker.dysonairpurifier, node: v20.13.1, js-controller: 5.0.19
2024-05-14 20:52:52.206 - info: dysonairpurifier.0 (6705) Querying devices from dyson API.
2024-05-14 20:52:52.802 - debug: dysonairpurifier.0 (6705) Data received from dyson API: {"Serial":"C4H-EU-NHA6440A","Name":"Dyson Pure Humidify+Cool","Version":"ECG2PF.<IP_ADDRESS>3","LocalCredentials":"x26K6jWOwJs39PyCJr8MiOqhIZ/QHgbasFLVqRlABteiWWMkx+hEqm39ZctcdReol2R9ubU0MNUZRKRNTPr+b6D8cZ9HSbnmgPY3IIpndCyq23N91/So7TUMcxDFq5rFx12KfLn2L9WfHc8LmFJZpIbIKP5v7MpE96USG23BARp9ljTAfGSreOw2sBsn/2uO","AutoUpdate":true,"NewVersionAvailable":false,"ProductType":"358","ConnectionType":"wss"}
2024-05-14 20:52:52.804 - debug: dysonairpurifier.0 (6705) Data received from dyson API: {"Serial":"VS8-EU-KGA0222B","Name":"Dyson Pure Cool","Version":"ECG2PF.<IP_ADDRESS>2","LocalCredentials":"0uRQB1HSEwSyQr67l9afpwwF/YyGBoNBleZJg1cPl8K4peSsoXxwzxv/72VL3xbYMu8XtYrvsXt6OwBGSNRAiKFr9R6GmHRuVWK7cJFRG0iSlMb48RfvdWFV/cMLKxfYVnxE6lbGY0PgfBVGVse04NcnM6BFwWkH9gv8MZHOVASjKfCjc8lyr0egrkkzqhTC","AutoUpdate":true,"NewVersionAvailable":false,"ProductType":"438","ConnectionType":"wss"}
2024-05-14 20:52:52.808 - debug: dysonairpurifier.0 (6705) Querying Host-Address of device: C4H-EU-NHA6440A
2024-05-14 20:52:52.820 - debug: dysonairpurifier.0 (6705) Got Host-Address-object [{"val":"<IP_ADDRESS>","ack":true,"ts":1715691749668,"q":0,"from":"system.adapter.dysonairpurifier.0","user":"system.user.admin","lc":1715691715081}] for device: C4H-EU-NHA6440A
2024-05-14 20:52:52.820 - debug: dysonairpurifier.0 (6705) Found valid Host-Address [<IP_ADDRESS>] for device: C4H-EU-NHA6440A
2024-05-14 20:52:52.821 - debug: dysonairpurifier.0 (6705) Looking for deprecated fields on device dysonairpurifier.0.C4H-EU-NHA6440A
2024-05-14 20:52:52.821 - debug: dysonairpurifier.0 (6705) Looking for deprecated field: dysonairpurifier.0.C4H-EU-NHA6440A.Sensor.PM10R
2024-05-14 20:52:52.822 - debug: dysonairpurifier.0 (6705) Looking for deprecated field: dysonairpurifier.0.C4H-EU-NHA6440A.Sensor.PM25R
2024-05-14 20:52:52.822 - debug: dysonairpurifier.0 (6705) Result of CreateOrUpdateDevice: [{"Serial":"C4H-EU-NHA6440A","Name":"Dyson Pure Humidify+Cool","Version":"ECG2PF.<IP_ADDRESS>3","LocalCredentials":"x26K6jWOwJs39PyCJr8MiOqhIZ/QHgbasFLVqRlABteiWWMkx+hEqm39ZctcdReol2R9ubU0MNUZRKRNTPr+b6D8cZ9HSbnmgPY3IIpndCyq23N91/So7TUMcxDFq5rFx12KfLn2L9WfHc8LmFJZpIbIKP5v7MpE96USG23BARp9ljTAfGSreOw2sBsn/2uO","AutoUpdate":true,"NewVersionAvailable":false,"ProductType":"358","ConnectionType":"wss","hostAddress":"<IP_ADDRESS>","mqttClient":null,"mqttPassword":"mkE2Ls/sEqtJZXVydu65gWULTCfBSLZ+XYGTTMIsixHClcvBaAjLO2Zel6bJYFGsLkVpyCuMtYE+v8R6vcLMjg==","updateIntervalHandle":null}]
2024-05-14 20:52:52.823 - debug: dysonairpurifier.0 (6705) Subscribing for state changes on datapoint: C4H-EU-NHA6440A.hostAddress
2024-05-14 20:52:52.824 - info: dysonairpurifier.0 (6705) Trying to connect to device [C4H-EU-NHA6440A] via MQTT on host address [<IP_ADDRESS>@undefined].
2024-05-14 20:52:52.883 - info: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT connection requested for [<IP_ADDRESS>@undefined].
2024-05-14 20:52:52.884 - debug: dysonairpurifier.0 (6705) Querying Host-Address of device: VS8-EU-KGA0222B
2024-05-14 20:52:52.904 - debug: dysonairpurifier.0 (6705) deprecated field: dysonairpurifier.0.C4H-EU-NHA6440A.Sensor.PM10R not found - nothing to do.
2024-05-14 20:52:52.905 - debug: dysonairpurifier.0 (6705) deprecated field: dysonairpurifier.0.C4H-EU-NHA6440A.Sensor.PM25R not found - nothing to do.
2024-05-14 20:52:52.915 - debug: dysonairpurifier.0 (6705) Got Host-Address-object [{"val":"<IP_ADDRESS>","ack":true,"ts":1715691749730,"q":0,"from":"system.adapter.dysonairpurifier.0","user":"system.user.admin","lc":1715691715081}] for device: VS8-EU-KGA0222B
2024-05-14 20:52:52.915 - debug: dysonairpurifier.0 (6705) Found valid Host-Address [<IP_ADDRESS>] for device: VS8-EU-KGA0222B
2024-05-14 20:52:52.915 - debug: dysonairpurifier.0 (6705) Looking for deprecated fields on device dysonairpurifier.0.VS8-EU-KGA0222B
2024-05-14 20:52:52.916 - debug: dysonairpurifier.0 (6705) Looking for deprecated field: dysonairpurifier.0.VS8-EU-KGA0222B.Sensor.PM10R
2024-05-14 20:52:52.916 - debug: dysonairpurifier.0 (6705) Looking for deprecated field: dysonairpurifier.0.VS8-EU-KGA0222B.Sensor.PM25R
2024-05-14 20:52:52.916 - debug: dysonairpurifier.0 (6705) Result of CreateOrUpdateDevice: [{"Serial":"VS8-EU-KGA0222B","Name":"Dyson Pure Cool","Version":"ECG2PF.<IP_ADDRESS>2","LocalCredentials":"0uRQB1HSEwSyQr67l9afpwwF/YyGBoNBleZJg1cPl8K4peSsoXxwzxv/72VL3xbYMu8XtYrvsXt6OwBGSNRAiKFr9R6GmHRuVWK7cJFRG0iSlMb48RfvdWFV/cMLKxfYVnxE6lbGY0PgfBVGVse04NcnM6BFwWkH9gv8MZHOVASjKfCjc8lyr0egrkkzqhTC","AutoUpdate":true,"NewVersionAvailable":false,"ProductType":"438","ConnectionType":"wss","hostAddress":"<IP_ADDRESS>","mqttClient":null,"mqttPassword":"Ork0FFeyLE4vu57QbOtiIy+QJ9tQz7R++sgjuRlJqFUJiT+AXs8AilDhpeJAcc0rHtV0FvJ6yyhIa5Uy8JKb1w==","updateIntervalHandle":null}]
2024-05-14 20:52:52.916 - debug: dysonairpurifier.0 (6705) Subscribing for state changes on datapoint: VS8-EU-KGA0222B.hostAddress
2024-05-14 20:52:52.917 - info: dysonairpurifier.0 (6705) Trying to connect to device [VS8-EU-KGA0222B] via MQTT on host address [<IP_ADDRESS>@undefined].
2024-05-14 20:52:52.919 - info: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT connection requested for [<IP_ADDRESS>@undefined].
2024-05-14 20:52:52.934 - debug: dysonairpurifier.0 (6705) deprecated field: dysonairpurifier.0.VS8-EU-KGA0222B.Sensor.PM10R not found - nothing to do.
2024-05-14 20:52:52.936 - debug: dysonairpurifier.0 (6705) deprecated field: dysonairpurifier.0.VS8-EU-KGA0222B.Sensor.PM25R not found - nothing to do.
2024-05-14 20:52:53.252 - info: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT connection established.
2024-05-14 20:52:53.256 - info: dysonairpurifier.0 (6705) Starting Polltimer with a 60 seconds interval.
2024-05-14 20:52:53.266 - debug: dysonairpurifier.0 (6705) Updating device [VS8-EU-KGA0222B] (polling API scheduled).
2024-05-14 20:52:53.419 - info: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT connection established.
2024-05-14 20:52:53.421 - info: dysonairpurifier.0 (6705) Starting Polltimer with a 60 seconds interval.
2024-05-14 20:52:53.431 - debug: dysonairpurifier.0 (6705) Updating device [C4H-EU-NHA6440A] (polling API scheduled).
2024-05-14 20:52:53.472 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-STATE
2024-05-14 20:52:53.478 - debug: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT message received: {"msg":"CURRENT-STATE","time":"2024-05-14T18:52:53.000Z","mode-reason":"PRC","state-reason":"MODE","rssi":"-45","channel":"44","fqhp":"104480","fghp":"74880","product-state":{"fpwr":"OFF","auto":"ON","oscs":"OFF","oson":"ON","nmod":"OFF","rhtm":"ON","fnst":"OFF","ercd":"11E1","wacd":"NONE","nmdv":"0004","fnsp":"AUTO","bril":"0002","corf":"ON","cflr":"0100","hflr":"0090","cflt":"CARF","hflt":"GHEP","sltm":"OFF","osal":"0088","osau":"0133","ancp":"CUST","fdir":"ON"},"scheduler":{"srsc":"0000000000000000","dstv":"0001","tzid":"0001"}}
2024-05-14 20:52:53.522 - debug: dysonairpurifier.0 (6705) MessageType: ENVIRONMENTAL-CURRENT-SENSOR-DATA
2024-05-14 20:52:53.526 - debug: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT message received: {"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2024-05-14T18:52:53.000Z","data":{"tact":"2952","hact":"0051","pm25":"0002","pm10":"0001","va10":"0003","noxl":"0009","p25r":"0002","p10r":"0002","sltm":"OFF"}}
2024-05-14 20:52:53.564 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-STATE
2024-05-14 20:52:53.570 - debug: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT message received: {"msg":"CURRENT-STATE","time":"2024-05-14T18:52:53.000Z","mode-reason":"LAPP","state-reason":"MODE","rssi":"-46","channel":"10","fqhp":"104912","fghp":"68048","product-state":{"fpwr":"ON","auto":"ON","oscs":"IDLE","oson":"ON","nmod":"OFF","rhtm":"ON","fnst":"OFF","ercd":"31U2","wacd":"NONE","nmdv":"0004","fnsp":"AUTO","bril":"0002","corf":"ON","cflr":"INV","hflr":"0087","cflt":"NONE","hflt":"GCOM","sltm":"OFF","osal":"0190","osau":"0190","ancp":"0090","hume":"HUMD","haut":"ON","humt":"0040","rect":"0045","msta":"OFF","clcr":"CLNO","cdrr":"0060","cltr":"0245","wath":"0675","psta":"OFF","fdir":"ON"},"scheduler":{"srsc":"0000000000000000","dstv":"0001","tzid":"0001"}}
2024-05-14 20:52:53.647 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-STATE
2024-05-14 20:52:53.651 - debug: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT message received: {"msg":"CURRENT-STATE","time":"2024-05-14T18:52:54.000Z","mode-reason":"PRC","state-reason":"MODE","rssi":"-45","channel":"44","fqhp":"104000","fghp":"74880","product-state":{"fpwr":"OFF","auto":"ON","oscs":"OFF","oson":"ON","nmod":"OFF","rhtm":"ON","fnst":"OFF","ercd":"11E1","wacd":"NONE","nmdv":"0004","fnsp":"AUTO","bril":"0002","corf":"ON","cflr":"0100","hflr":"0090","cflt":"CARF","hflt":"GHEP","sltm":"OFF","osal":"0088","osau":"0133","ancp":"CUST","fdir":"ON"},"scheduler":{"srsc":"0000000000000000","dstv":"0001","tzid":"0001"}}
2024-05-14 20:52:53.731 - debug: dysonairpurifier.0 (6705) MessageType: ENVIRONMENTAL-CURRENT-SENSOR-DATA
2024-05-14 20:52:53.758 - debug: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT message received: {"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2024-05-14T18:52:54.000Z","data":{"tact":"2952","hact":"0051","pm25":"0002","pm10":"0001","va10":"0003","noxl":"0009","p25r":"0002","p10r":"0002","sltm":"OFF"}}
2024-05-14 20:52:53.764 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-FAULTS
2024-05-14 20:52:53.775 - debug: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT message received: {"msg":"CURRENT-FAULTS","time":"2024-05-14T18:52:54.000Z","product-errors":{"amf1":"OK","amf2":"OK","amf3":"OK","amf4":"OK","amf5":"OK","amf6":"OK","amf7":"OK","amf8":"OK","com4":"OK","com1":"OK","ste1":"OK","iuh0":"OK","iup0":"OK","iuw0":"OK","iuh1":"OK","iuu1":"OK","iuc1":"OK","iuw1":"OK","iua1":"OK","iuh2":"OK","iuu2":"OK","iuc2":"OK","iuw2":"OK","iua2":"OK","iuh3":"OK","iuu3":"OK","iuc3":"OK","iuw3":"OK","iua3":"OK","ui01":"OK","ui02":"OK","ui03":"OK","uid1":"OK","uid2":"OK","fs01":"OK","fs02":"OK","fs03":"OK","fs04":"OK","fs05":"OK","fs06":"OK","fs07":"OK","fs08":"OK","fs09":"OK","fs0a":"OK","fs0b":"OK","fs0c":"OK","psu1":"OK","psu2":"OK","psu3":"OK","sen1":"OK","sen2":"OK","sen3":"OK","sen4":"OK","sen5":"OK","sen6":"OK","com5":"OK","com2":"OK"},"product-warnings":{"fltr":"OK"},"module-errors":{"szme":"OK","szmw":"OK","szps":"OK","szpe":"OK","szpw":"OK","szed":"OK","lspd":"OK","szpi":"OK","szpp":"OK","szhv":"OK","szbv":"OK","szav":"OK"},"module-warnings":{"srnk":"OK","stac":"OK","strs":"OK","srmi":"OK","srmu":"OK","nwcs":"OK","nwts":"OK","nwps":"OK","nwss":"OK"}}
2024-05-14 20:52:53.776 - debug: dysonairpurifier.0 (6705) MessageType: ENVIRONMENTAL-CURRENT-SENSOR-DATA
2024-05-14 20:52:53.803 - debug: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT message received: {"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2024-05-14T18:52:53.000Z","data":{"tact":"2941","hact":"0052","pm25":"0003","pm10":"0002","va10":"0007","noxl":"0003","p25r":"0004","p10r":"0004","sltm":"OFF"}}
2024-05-14 20:52:53.837 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-FAULTS
2024-05-14 20:52:53.851 - debug: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT message received: {"msg":"CURRENT-FAULTS","time":"2024-05-14T18:52:53.000Z","product-errors":{"amf1":"OK","amf2":"OK","amf3":"OK","amf4":"OK","amf5":"OK","amf6":"OK","amf7":"OK","amf8":"OK","amf9":"OK","com4":"OK","com1":"OK","iuh0":"OK","iup0":"OK","iuw0":"OK","iuh1":"OK","iuu1":"OK","iuc1":"OK","iuw1":"OK","iua1":"OK","iuh2":"OK","iuu2":"OK","iuc2":"OK","iuw2":"OK","iua2":"OK","iuh4":"OK","iuu4":"OK","iuc4":"OK","iuw4":"OK","iua4":"OK","ui01":"OK","ui02":"OK","ui03":"OK","uid1":"OK","uid2":"OK","fs01":"OK","fs02":"OK","fs03":"OK","fs04":"OK","fs05":"OK","fs06":"OK","fs07":"OK","fs08":"OK","fs09":"OK","fs0a":"OK","fs0b":"OK","fs0c":"OK","psu1":"OK","psu2":"OK","sen1":"OK","sen2":"OK","sen3":"OK","sen4":"OK","com5":"OK","com2":"OK","com9":"OK","coma":"OK","bosl":"OK","bosr":"OK","etws":"OK","wpmp":"OK","prot":"OK","uled":"OK"},"product-warnings":{"fltr":"OK","tnke":"OK","tnkp":"OK","cldu":"OK","etwd":"OK"},"module-errors":{"szme":"OK","szmw":"OK","szps":"OK","szpe":"OK","szpw":"OK","szed":"OK","lspd":"OK","szpi":"OK","szpp":"OK","szhv":"OK","szbv":"OK","szav":"OK"},"module-warnings":{"srnk":"OK","stac":"OK","strs":"OK","srmi":"OK","srmu":"OK","nwcs":"OK","nwts":"OK","nwps":"OK","nwss":"OK"}}
2024-05-14 20:52:53.941 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-STATE
2024-05-14 20:52:53.943 - debug: dysonairpurifier.0 (6705) MessageType: ENVIRONMENTAL-CURRENT-SENSOR-DATA
2024-05-14 20:52:53.949 - debug: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT message received: {"msg":"CURRENT-STATE","time":"2024-05-14T18:52:54.000Z","mode-reason":"LAPP","state-reason":"MODE","rssi":"-46","channel":"10","fqhp":"104576","fghp":"68048","product-state":{"fpwr":"ON","auto":"ON","oscs":"IDLE","oson":"ON","nmod":"OFF","rhtm":"ON","fnst":"OFF","ercd":"31U2","wacd":"NONE","nmdv":"0004","fnsp":"AUTO","bril":"0002","corf":"ON","cflr":"INV","hflr":"0087","cflt":"NONE","hflt":"GCOM","sltm":"OFF","osal":"0190","osau":"0190","ancp":"0090","hume":"HUMD","haut":"ON","humt":"0040","rect":"0045","msta":"OFF","clcr":"CLNO","cdrr":"0060","cltr":"0245","wath":"0675","psta":"OFF","fdir":"ON"},"scheduler":{"srsc":"0000000000000000","dstv":"0001","tzid":"0001"}}
2024-05-14 20:52:53.950 - debug: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT message received: {"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2024-05-14T18:52:54.000Z","data":{"tact":"2941","hact":"0052","pm25":"0003","pm10":"0002","va10":"0007","noxl":"0003","p25r":"0004","p10r":"0004","sltm":"OFF"}}
2024-05-14 20:53:53.348 - debug: dysonairpurifier.0 (6705) Updating device [VS8-EU-KGA0222B] (polling API scheduled).
2024-05-14 20:53:53.442 - debug: dysonairpurifier.0 (6705) Updating device [C4H-EU-NHA6440A] (polling API scheduled).
2024-05-14 20:53:53.460 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-STATE
2024-05-14 20:53:53.463 - debug: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT message received: {"msg":"CURRENT-STATE","time":"2024-05-14T18:53:53.000Z","mode-reason":"PRC","state-reason":"MODE","rssi":"-45","channel":"44","fqhp":"104472","fghp":"74880","product-state":{"fpwr":"OFF","auto":"ON","oscs":"OFF","oson":"ON","nmod":"OFF","rhtm":"ON","fnst":"OFF","ercd":"11E1","wacd":"NONE","nmdv":"0004","fnsp":"AUTO","bril":"0002","corf":"ON","cflr":"0100","hflr":"0090","cflt":"CARF","hflt":"GHEP","sltm":"OFF","osal":"0088","osau":"0133","ancp":"CUST","fdir":"ON"},"scheduler":{"srsc":"0000000000000000","dstv":"0001","tzid":"0001"}}
2024-05-14 20:53:53.511 - debug: dysonairpurifier.0 (6705) MessageType: ENVIRONMENTAL-CURRENT-SENSOR-DATA
2024-05-14 20:53:53.515 - debug: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT message received: {"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2024-05-14T18:53:53.000Z","data":{"tact":"2952","hact":"0051","pm25":"0002","pm10":"0001","va10":"0003","noxl":"0009","p25r":"0002","p10r":"0002","sltm":"OFF"}}
2024-05-14 20:53:53.561 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-FAULTS
2024-05-14 20:53:53.570 - debug: dysonairpurifier.0 (6705) VS8-EU-KGA0222B - MQTT message received: {"msg":"CURRENT-FAULTS","time":"2024-05-14T18:53:54.000Z","product-errors":{"amf1":"OK","amf2":"OK","amf3":"OK","amf4":"OK","amf5":"OK","amf6":"OK","amf7":"OK","amf8":"OK","com4":"OK","com1":"OK","ste1":"OK","iuh0":"OK","iup0":"OK","iuw0":"OK","iuh1":"OK","iuu1":"OK","iuc1":"OK","iuw1":"OK","iua1":"OK","iuh2":"OK","iuu2":"OK","iuc2":"OK","iuw2":"OK","iua2":"OK","iuh3":"OK","iuu3":"OK","iuc3":"OK","iuw3":"OK","iua3":"OK","ui01":"OK","ui02":"OK","ui03":"OK","uid1":"OK","uid2":"OK","fs01":"OK","fs02":"OK","fs03":"OK","fs04":"OK","fs05":"OK","fs06":"OK","fs07":"OK","fs08":"OK","fs09":"OK","fs0a":"OK","fs0b":"OK","fs0c":"OK","psu1":"OK","psu2":"OK","psu3":"OK","sen1":"OK","sen2":"OK","sen3":"OK","sen4":"OK","sen5":"OK","sen6":"OK","com5":"OK","com2":"OK"},"product-warnings":{"fltr":"OK"},"module-errors":{"szme":"OK","szmw":"OK","szps":"OK","szpe":"OK","szpw":"OK","szed":"OK","lspd":"OK","szpi":"OK","szpp":"OK","szhv":"OK","szbv":"OK","szav":"OK"},"module-warnings":{"srnk":"OK","stac":"OK","strs":"OK","srmi":"OK","srmu":"OK","nwcs":"OK","nwts":"OK","nwps":"OK","nwss":"OK"}}
2024-05-14 20:53:53.582 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-STATE
2024-05-14 20:53:53.587 - debug: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT message received: {"msg":"CURRENT-STATE","time":"2024-05-14T18:53:53.000Z","mode-reason":"LAPP","state-reason":"MODE","rssi":"-46","channel":"10","fqhp":"104568","fghp":"68048","product-state":{"fpwr":"ON","auto":"ON","oscs":"IDLE","oson":"ON","nmod":"OFF","rhtm":"ON","fnst":"OFF","ercd":"31U2","wacd":"NONE","nmdv":"0004","fnsp":"AUTO","bril":"0002","corf":"ON","cflr":"INV","hflr":"0087","cflt":"NONE","hflt":"GCOM","sltm":"OFF","osal":"0190","osau":"0190","ancp":"0090","hume":"HUMD","haut":"ON","humt":"0040","rect":"0045","msta":"OFF","clcr":"CLNO","cdrr":"0060","cltr":"0245","wath":"0675","psta":"OFF","fdir":"ON"},"scheduler":{"srsc":"0000000000000000","dstv":"0001","tzid":"0001"}}
2024-05-14 20:53:53.632 - debug: dysonairpurifier.0 (6705) MessageType: ENVIRONMENTAL-CURRENT-SENSOR-DATA
2024-05-14 20:53:53.634 - debug: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT message received: {"msg":"ENVIRONMENTAL-CURRENT-SENSOR-DATA","time":"2024-05-14T18:53:53.000Z","data":{"tact":"2941","hact":"0052","pm25":"0003","pm10":"0002","va10":"0007","noxl":"0003","p25r":"0004","p10r":"0004","sltm":"OFF"}}
2024-05-14 20:53:53.682 - debug: dysonairpurifier.0 (6705) MessageType: CURRENT-FAULTS
2024-05-14 20:53:53.691 - debug: dysonairpurifier.0 (6705) C4H-EU-NHA6440A - MQTT message received: {"msg":"CURRENT-FAULTS","time":"2024-05-14T18:53:53.000Z","product-errors":{"amf1":"OK","amf2":"OK","amf3":"OK","amf4":"OK","amf5":"OK","amf6":"OK","amf7":"OK","amf8":"OK","amf9":"OK","com4":"OK","com1":"OK","iuh0":"OK","iup0":"OK","iuw0":"OK","iuh1":"OK","iuu1":"OK","iuc1":"OK","iuw1":"OK","iua1":"OK","iuh2":"OK","iuu2":"OK","iuc2":"OK","iuw2":"OK","iua2":"OK","iuh4":"OK","iuu4":"OK","iuc4":"OK","iuw4":"OK","iua4":"OK","ui01":"OK","ui02":"OK","ui03":"OK","uid1":"OK","uid2":"OK","fs01":"OK","fs02":"OK","fs03":"OK","fs04":"OK","fs05":"OK","fs06":"OK","fs07":"OK","fs08":"OK","fs09":"OK","fs0a":"OK","fs0b":"OK","fs0c":"OK","psu1":"OK","psu2":"OK","sen1":"OK","sen2":"OK","sen3":"OK","sen4":"OK","com5":"OK","com2":"OK","com9":"OK","coma":"OK","bosl":"OK","bosr":"OK","etws":"OK","wpmp":"OK","prot":"OK","uled":"OK"},"product-warnings":{"fltr":"OK","tnke":"OK","tnkp":"OK","cldu":"OK","etwd":"OK"},"module-errors":{"szme":"OK","szmw":"OK","szps":"OK","szpe":"OK","szpw":"OK","szed":"OK","lspd":"OK","szpi":"OK","szpp":"OK","szhv":"OK","szbv":"OK","szav":"OK"},"module-warnings":{"srnk":"OK","stac":"OK","strs":"OK","srmi":"OK","srmu":"OK","nwcs":"OK","nwts":"OK","nwps":"OK","nwss":"OK"}}
2024-05-14 20:54:17.462 - debug: dysonairpurifier.0 (6705) MessageType: STATE-CHANGE
2024-05-14 20:54:17.464 - debug: dysonairpurifier.0 (6705) Values for [OscillationActive] are equal. No update required. Skipping.
2024-05-14 20:54:17.464 - debug: dysonairpurifier.0 (6705) Values for [FanStatus] are equal. No update required. Skipping.
2024-05-14 20:54:17.464 - debug: dysonairpurifier.0 (6705) Values for [LastErrorCode] are equal. No update required. Skipping.
2024-05-14 20:54:17.465 - debug: dysonairpurifier.0 (6705) Values for [LastWarningCode] are equal. No update required. Skipping.
2024-05-14 20:54:17.465 - debug: dysonairpurifier.0 (6705) Values for [Carbonfilter] are equal. No update required. Skipping.
2024-05-14 20:54:17.465 - debug: dysonairpurifier.0 (6705) Values for [HEPA-Filter] are equal. No update required. Skipping.
2024-05-14 20:54:17.466 - debug: dysonairpurifier.0 (6705) Values for [OscillationAngle] are equal. No update required. Skipping.
2024-05-14 20:54:17.468 - debug: dysonairpurifier.0 (6705) Values for [HumidificationState] are equal. No update required. Skipping.
2024-05-14 20:54:17.468 - debug: dysonairpurifier.0 (6705) Values for [DeepCleanCycle] are equal. No update required. Skipping.
2024-05-14 20:54:17.469 - debug: dysonairpurifier.0 (6705) Values for [WaterHardness] are equal. No update required.

Den  eigentlichenb Bug dieses Issues hier habe ich übrigens gefunden und behebe ihn gerade.

@krobipd Kannst Du bitte die Version hier von github testen?


Inline policies

Inline policy for config rules package is generated for security monkey user.  It would be cool if this were a customer managed policy instead.  One less thing to white list.

Thanks @andrewkrug do you have an example of that in other template? I'm not sure if I know what are you talking about.


Can we execute Ansible playbooks in kubeless function?

I had written kubeless function in python and that function calls ansible-playbook through the ansible-runner module. The function is getting deployed successfully, I am able to make function call. But when in function logs below error found:
The command was not found or was not executable: ansible-playbook.
Any support for ansible

Hi @JagrutiDharangutti,
The script ansible-playbook won't be included in the image running the function. If you want to add extra packages in the docker image, you can create your own (using the current kubeless one as base) and use it, replacing the target image in Kubeless configmap.

Can you give me an example, how to do that?

Unfortunately, there are no public examples of how to do that but you just need to use the python image that you can find here: https://github.com/kubeless/runtimes/blob/master/stable/python/python.jsonnet (like kubeless/python@sha256:efe867b7d1375e557d72487b068722211c4d8e08f9d0482f347c09046cc87872) and install any package on it.
Then you just need to edit the kubeless configmap (kubectl edit configmap -n kubeless kubeless-config) and replace the image with the one you built. Then restart the controller pod (kubectl delete pod -n kubeless -l kubeless=controller) to reload the changes.


Provide Tags

Hi! First of all: great Script - I love it!
But why don't you provide tags of your plugin? Using bower it would helpful to have version numbers.  It's best practice to have version numbers of your repo, done with the help of git tags.
Or am I getting something wrong?
Thank you.

:+1:

:+1:

:+1:

This is a must, because now with 4.0.0 released my website failed (4.0.0 has both js and css files, previously there was only js file) and I couldn't say bower to install the same version as there are no release tags for this repo!

+1
I have spent more or less 8 hours trying to figure out why notie worked on my fellow developer's machine, but not on mine. It turned out we had different versions downloaded, although bower said no new version was available. Please fix proper versioning for bower! (It's already correct for npm as far as i can tell.)

@jaredreich why did you close this? There are still no git tags to be found... Maybe you didn't push them?

If you're unsure on what needs to happen, let me know, I can help out.

I did add git tags with this release (3.1.0) but you're right it looks like they didn't push. I think it's because I pushed with the GitHub mac app rather than through CLI with --tags.
Working on this now, my apologies everyone for the inconvenience :(

Okay I've added tags for 2.1.0, 3.0.0, and 3.1.0 - hopefully this solves the issue. Please let me know if it's working with Bower now. Thanks!

Thanks, it's looking great now! npm and bower both report the same available versions.
(However, the version 4.0 mentioned above is not visible in either tool.)


Compatability

Does this work in Debian 10 Buster?  After running the python script in the terminal I get the "SyntaxError: invalid syntax". Any help is much appreciated.

This program only works in python3 try using it in python3!


Relational: Move ValueGenerationStrategy annotation to Relational.

Uncovered during Oracle sample provider work.

Closing old issue as this is no longer something we intend to implement.