fix/update blog policy

Signed-off-by: Chip Zoller<EMAIL_ADDRESS>Related issue
#1251
Proposed Changes
Fixes and updates the blog policy so it is correct along with corresponding Playground link.
Checklist

[x] I have read the contributing guidelines.
[x] I have inspected the website preview for accuracy.
[x] I have signed off my issue.

Links to be fixed in #1253

/cherry-pick release-1-12-0


Refactor Python debug options parsing

See ParseOptions in AD7Engine.cs for more info.

Worth going one step further and just switching all the options to JSON. We're going to have to have the functionality around anyway, so let's just use it and get out of the manual parsing business.

Unassigned, after investigating. I won't be able to finish this before heading off to vacation. This is open for anyone else to pickup meanwhile.


test(stdlib): skip failing window test due to new trigger optimization

Closes #
Briefly describe your proposed changes:
Skip failing end-to-end test due to https://github.com/influxdata/flux/issues/1067

[ ] Rebased/mergeable
[ ] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[ ] Sign CLA (if not already signed)

@jlapacik Why does table order effect the test case? I thought diff didn't care about table order.

@nathanielc as I mentioned in standup conversation, the test case is terminated by a group(), so the table ordering affects the row ordering of the single output table. That's why the test is failing.


Update sbt-tpolecat to 0.1.18

Updates io.github.davidgregory084:sbt-tpolecat from 0.1.11 to 0.1.18.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.github.davidgregory084", artifactId = "sbt-tpolecat" } ]

labels: sbt-plugin-update, semver-patch

Superseded by #124.


Auto-complete in Task Authoring

Extends PR #657

Fixes CSS issues
Fixes updating dynamic sources when file is removed or re-added.

lgtm


Faster hash [DNM]

Probably updating xxhasher is unnecessary? Particularly if it's just falling back to these intrinsics anyway. Needs perf testing.

High Level Overview of Change

Context of Change

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Tests (you added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation update
[ ] Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
[ ] Release

API Impact

[ ] Public API: New feature (new methods and/or new fields)
[ ] Public API: Breaking change (in general, breaking changes should only impact the next api_version)
[ ] libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
[ ] Peer protocol change (must be backward compatible or bump the peer protocol version)

Based on my perf testing I think the compiler already optimized this for us. Closing for now.


Multi tenancy

I understand that we the annotation argo-workflows/cluster-name I can bring some multi tenancy.
Is there a way to do this without using the annotation?
Additionally, how could I configure multiple Argo Workflow UI's?

annotations is the backstage way of introducing components.
Multiple workflows is not supported in the plugin as of now but PRs are welcome.


chore: add legal documentation

PR to add missing legal documentation according to TRG 7.01 and fix a typo in CONTRIBUTING.md.
DEPENDENCIES file is missing as there are none.

Thank you @pablosec


Update get-healthcare-apis-access-token-cli.md

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


[Question]: How do you disable the sitemap.xml file creation?

Also looked in the crawler documentation for keywords, but seems that it is not mentioned.

The purpose of this tool is to generate an sitemap, therefore you can't disable it. You could write the file to /tmp which would be deleted on machine restart.

Thanks !

Even better. :)


Potential 1.5.1 patch release

The following could be included in 1.5.1:

#4981 (plus a change in the Windows builders to test with C++17)
#4972
#4974
#4963
#4946
#4944

Maybe:

Algorithms ranges adaptations since 1.5.0
#4952

Thanks @hkaiser for updating the list! I think we should go with the minimum non-breaking changes. The parallel_executor change is not 100% compatible so I'd prefer to leave that for 1.6.0 (and some release candidates). This way we can get the patch release out quickly and not have to worry about what exactly could or should be included.

Thanks @hkaiser for updating the list! I think we should go with the minimum non-breaking changes. The parallel_executor change is not 100% compatible so I'd prefer to leave that for 1.6.0 (and some release candidates). This way we can get the patch release out quickly and not have to worry about what exactly could or should be included.

Fair point. I was not aware that the change is not fully backwards compatible. Let's not have it then.

Adding #4939, #4941, #4951, #4982

@aurianer @khuck mentioned that he would like to add a new APEX tag. Is that still possible?

So I already tag the release yesterday so that's actually not really possible as it notifies everyone who is watching the repo, also I believe our policy for patch releases (which fix only compilation/bug issues) is not to update the external libraries tags that's why I didn't ask, what do you think?
What does the tag include? In case it is really important I can still force push but I would like to avoid it since it notifies people a second time ^^'

So I already tagged the release yesterday so that's actually not really possible as it notifies everyone who is watching the repo, also I believe our policy for patch releases (which fix only compilation/bug issues) is not to update the external libraries tags that's why I didn't ask, what do you think?
What changes does the tag include? In case it is really important I can still force push but I would like to avoid it since it notifies people a second time ^^'

@khuck what do you say?

@aurianer @hkaiser It's not that critical.  At configuration time it can be overridden, so it doesn't have to go in to the release.

Okay then I'll announce the release once ci have passed, the update of the tag went well btw
@khuck In case you change your mind and you need it in, we can still do a 1.5.2 release :)


How to set a column a filter

Hi,
Is it possible to set a column with a filter like Excel?
Best, Paul

Unfortunately, this is not available in the current version. But you can search option as below:
https://bossanova.uk/jexcel/v3/examples/datatables


include_path required though it is listed optional

After the v2.3.0 release I'm getting an exception saying KeyError: 'include_path'
This errors goes away when adding that to the config file, however the readme list this as an optional value.  In the same release resolve_aws_alias also became required, but the docs were updated to reflect that.
Expected Behavior
To not get an exception if include_path is omitted from the config file.
Current Behavior
You get an exception if it is not included in the config file.
Traceback (most recent call last):
File "C:\Users\currentuser\AppData\Local\Programs\Python\Python38\Scripts\gimme-aws-creds.cmd", line 47, in
GimmeAWSCreds().run()
File "C:\Users\currentuser\AppData\Local\Programs\Python\Python38\lib\site-packages\gimme_aws_creds\main.py", line 466, in run
self._run()
File "C:\Users\currentuser\AppData\Local\Programs\Python\Python38\lib\site-packages\gimme_aws_creds\main.py", line 775, in _run
for data in self.iter_selected_aws_credentials():
File "C:\Users\currentuser\AppData\Local\Programs\Python\Python38\lib\site-packages\gimme_aws_creds\main.py", line 752, in iter_selected_aws_credentials
data = self.prepare_data(role, generate_credentials=True)
File "C:\Users\currentuser\AppData\Local\Programs\Python\Python38\lib\site-packages\gimme_aws_creds\main.py", line 704, in prepare_data
include_path = self.conf_dict['include_path']
KeyError: 'include_path'
Possible Solution
Update the readme to reflect it is no longer optional, or implement the default as outlined in the readme, which is set to no
Steps to Reproduce (for bugs)
Leave the value 'include_path' out of your config file.

Your Environment

v2.3.0
Python3.8
Windows 10

v2.3.1 is building with a fix for this.  Thanks!


Try to detect non-use of best practices

Hi all !
I'm not so new with Laravel but don't work with it so much so, I know it, I'm making conception errors and/or not following best practices like respect naming conventions. I pay a lot of attention to the quality of the code and the respect of the rules.
I've just installed a fresh Laravel site for fun and create two models

php artisan make:model Students
php artisan make:model Teacher

Students, plural form and Teacher, singular form.  I know that Models should be written using singular form. (https://github.com/alexeymezenin/laravel-best-practices#follow-laravel-naming-conventions)
So, does Larastan detect this violation?
composer require nunomaduro/larastan:^2.0 --dev
 ./vendor/bin/phpstan analyse

And this even at level 9:
includes:
    - ./vendor/nunomaduro/larastan/extension.neon
parameters:
    paths:
        - app/
    level: 9

Did you know if Larastan can be used too for such things i.e. notifying the developper he's not following best practices?
If not, did you know some tools for this usage?
Many thanks!

Hello Christophe! 👋🏻
Any software can do this.
I can think of 2: coding standards or static analysis.
Coding standards violation is closer to class naming.

At work, I'm using php-cs-fixer, phpcbf, phpcs, larastan and psalm.  Using rector too.  Yeah, I'm a fan of static analysis tools and how they are great to improve the codebase and increase skills of the developer.
My skills with Laravel (I mean writing code) can be improved and ... voilà, I'm trying to determine if tools exists for helping me (and people who don't write laravel code each day) to try to use best practices.
For the example I've given here above, no tools already detect this. Perhaps are there somewhere some magic I don't have discovered yet ;)

Please talk to Slevomat guys. They are deeply into this.

Thanks! Indeed, i've already see https://github.com/slevomat/coding-standard months ago; will read it once more.

(just for info, I think I've enabled all rules of  https://github.com/slevomat/coding-standard and none are helping here i.e. no notification about the user of the plural form in my Students model)

I've meant to really talk to them: please open an issue.

There are class name processing sniffs. E.g. the one that check interface name ending Interface.
It is very easy to copy it and make it check class names.

Have you heard of https://laravelshift.com/opinionated-laravel-way-shift ?

Never... Just take a look and create an account and... No, I can't use it.
That tool ask to clone my project but it's not possible. My projects are stored in our corporate GitLab instance and in no way it'll be allowed to push our code to their servers.

to clone my project

There are local shifts: https://laravelshift.com/docker


Add GHQ_LOOK env variable to a new shell executed by ghq look

I want to use the relpath of found local repository on a new shell executed by ghq look.
An example is as follows:
# .zshrc
if [ -n "$GHQ_LOOK" ]; then
    export PROMPT="[$GHQ_LOOK] $PROMPT"
fi

Reasonable. Thank you and sorry for such a late response!

Thank you for merge !!


Inconsistent markdown rendering in markdown preview and vscode extension explorer

VSCode Version: 1.24.1
OS Version: windows 10 1803

Steps to Reproduce:

Create an extension with a readme file containing *this should be cursive **this should be bold and cursive***
Publish the extension on the market place
Query for the extension in vscode's extension explorer

Description
The above markdown snippet is rendered as expected on github, vscode marketplace and vscode itself (using the markdown preview). However when you search for the extension in vscode's extension explorer the rendering of this snippet is broken.

Does this issue occur when all extensions are disabled?: yes
Example
For instance in the timing extension I wrote [...] *epoch time is the **source*** [...] in the readme.

Rendered on the marketplace:

Rendered with the extension explorer:

Rendered with the markdown preview:

It would be great if the rendering between vscode's markdown preview, extension explorer and vscode marketplace would be consistent.

The markdown engine we use for the extensions view is very fast/lightweight, but unfortunately not as compliant as the one bundled with the markdown extension. In this case, the engine we use views the three asterisks as syntactically ambiguous, and produces incorrect output.
I would recommend using the convention of underscores for italics when combining emphasis, which should render consistently everywhere. (i.e. _epoch time is the **source**_

Is there a way to check how the extension explorer's markdown engine renders the readme before I publish the extension to the vscode marketplace? I would like to avoid patches due to wrong markdown rendering.

This demo should show you how we will render it:
https://marked.js.org/demo/?text=When *the* *epoch time is the **source*** format of the conversion its unit is determined by its **digit count**%3A


Question: Current state

Hi!
I am the author of Wurfel Engine. I would like to add a Minecraft map import to the engine. I just want to read the Minecraft save files in order to get the block ids.
Is MCModify currently working for this task? Should I program my own software? Are there alternatives?
Kind regards,
Benedikt

I believe the chunk reading code should still work for current versions of Minecraft. The code is in the public domain so you can just copypaste the relevant parts into your project:
https://github.com/LB--/MCModify/blob/java/src/main/java/com/lb_stuff/mcmodify/minecraft/Region.java
https://github.com/LB--/MCModify/blob/java/src/main/java/com/lb_stuff/mcmodify/minecraft/FileRegion.java

Thank you for the links. I will let you know, if it worked.

There are a lot of errors, but I can read some chunks.

Is there a way to get one block just with x,y,z and the library does load the region and chunks automatically? Currently I have to specify the chunk, which I want to load.

I think the math for that is here: https://github.com/LB--/MCModify/blob/java/src/main/java/com/lb_stuff/mcmodify/location/LocChunkInDimension.java


Installation from alternative repository (test.pypi.org) fails due to missing pip option

I have uploaded a dummy package get_fourtytwo on testpypi. When I install it with pip directly, it works fine:
pip install --index-url https://test.pypi.org/simple/ get_fourtytwo
python -c "import get_fourtytwo"

I tried to install the package through poetry using this pyproject.toml:
[tool.poetry]
name = "foo"
version = "0.1.0"
description = ""
authors = ["konstin<EMAIL_ADDRESS>
[tool.poetry.dependencies]
python = "=3.6"
get_fourtytwo = "*"

[[tool.poetry.source]]
name = "testpypisimple"
url = "https://test.pypi.org/simple/"

poetry --version: Poetry 0.10.2
poetry install -vvv:
Updating dependencies
Resolving dependencies...
   1: fact: foo is 0.1.0
   1: derived: foo
   1: fact: foo depends on get_fourtytwo (*)
   1: selecting foo (0.1.0)
   1: derived: get_fourtytwo (*)
   1: selecting get-fourtytwo (1.6.0)
   1: Version solving took 0.043 seconds.
   1: Tried 1 solutions.

Package operations: 1 install, 0 updates, 0 removals

Writing lock file

  - Installing get-fourtytwo (1.6.0)

[VenvCommandError]
Command ['pip', 'install', '--no-deps', '-r', '/tmp/get-fourtytwo-1.6.0cvvv8zj_reqs.txt'] errored with the following output:
Collecting get-fourtytwo==1.6.0 (from -r /tmp/get-fourtytwo-1.6.0cvvv8zj_reqs.txt (line 1))
  Could not find a version that satisfies the requirement get-fourtytwo==1.6.0 (from -r /tmp/get-fourtytwo-1.6.0cvvv8zj_reqs.txt (line 1)) (from versions: )
No matching distribution found for get-fourtytwo==1.6.0 (from -r /tmp/get-fourtytwo-1.6.0cvvv8zj_reqs.txt (line 1))

Exception trace:
 /usr/local/lib/python3.6/dist-packages/cleo/application.py in run() at line 94
   status_code = self.do_run(input_, output_)
 /usr/local/lib/python3.6/dist-packages/poetry/console/application.py in do_run() at line 87
   return super(Application, self).do_run(i, o)
 /usr/local/lib/python3.6/dist-packages/cleo/application.py in do_run() at line 197
   status_code = command.run(input_, output_)
 /usr/local/lib/python3.6/dist-packages/poetry/console/commands/command.py in run() at line 72
   return super(BaseCommand, self).run(i, o)
 /usr/local/lib/python3.6/dist-packages/cleo/commands/base_command.py in run() at line 146
   status_code = self.execute(input_, output_)
 /usr/local/lib/python3.6/dist-packages/cleo/commands/command.py in execute() at line 107
   return self.handle()
 /usr/local/lib/python3.6/dist-packages/poetry/console/commands/install.py in handle() at line 50
   return installer.run()
 /usr/local/lib/python3.6/dist-packages/poetry/installation/installer.py in run() at line 75
   self._do_install(local_repo)
 /usr/local/lib/python3.6/dist-packages/poetry/installation/installer.py in _do_install() at line 254
   self._execute(op)
 /usr/local/lib/python3.6/dist-packages/poetry/installation/installer.py in _execute() at line 262
   getattr(self, "_execute_{}".format(method))(operation)
 /usr/local/lib/python3.6/dist-packages/poetry/installation/installer.py in _execute_install() at line 287
   self._installer.install(operation.package)
 /usr/local/lib/python3.6/dist-packages/poetry/installation/pip_installer.py in install() at line 37
   self.run(*args)
 /usr/local/lib/python3.6/dist-packages/poetry/installation/pip_installer.py in run() at line 62
   return self._venv.run("pip", *args, **kwargs)
 /usr/local/lib/python3.6/dist-packages/poetry/utils/venv.py in run() at line 274
   raise VenvCommandError(e)

install [--no-dev] [--dry-run] [-E|--extras EXTRAS] [--develop DEVELOP]

While the version and the sha256 in /tmp/get-fourtytwo-1.6.0cvvv8zj_reqs.txt are correct, it the installation fails because the index-url parameter is missing, i.e. pip install --no-deps --index-url https://test.pypi.org/simple/ -r get-fourtytwo-1.6.0cvvv8zj_reqs.txt works fine.
(Note that get_fourtytwo is a bdist_whl only available for cp3.6m on linux and testpypi gets cleaned sometimes, so you might to upload a different package to testpypi to reproduce)

Same problem here!
Seems that in order for the --index-url to be added to the pip command the package must have source_type set to "legacy" and a value for source_url (poetry/installation/pip_installer.py:20). It's not clear to me where those values have to be set.

This should be fixed in the latest release (0.10.3)

Indeed, thank you for the quick fix! (And, of course, for the overall great work)


Filtering Sentry.CrashErrors via Sentry.EventFilter

Will support for filtering these be something on the agenda?
We have handle_sasl_reports: true
together with:
      config :logger,
        backends: [:console, Sentry.LoggerBackend]

This gives us for example NoRouter errors from Phoenix in the form of Sentry.CrashErrors
I have been poking around in Sentry.LoggerBackend and it seems as the :crash_reason is available with for example the Phoenix.Router.NoRouteError. Adding it to the Sentry.CrashError struct would make it way nicer to filter on than looking up stuff in the general message string.

Thanks for opening an issue!
The Erlang logger has deprecated SASL as of OTP 21, so it's unlikely specific handling of SASL logs will be added.
If you're unable to disable SASL, one less than ideal option is to search for specific errors in the message along the lines of:
  def exclude_exception?(event, :logger) do
    if Regex.match?(~r/Phoenix\.Router\.NoRouteError/, event.message) do
      true
    else
      false
    end
  end

Since the structure of SASL metadata is different, Sentry.LoggerBackend wraps it in a Sentry.CrashError with a message from the original error.

Closing this issue for now 🙂


non-interactive way to bulk edit mirrors

hi
is there a way to edit mirror using command line optinos only?
i dont want to open up text editor and save
makes it hard to edit mirrors in bulk

this need to be redone https://github.com/etix/mirrorbits/blob/33000b73aba3b6fffc24d459017431f6f7f2af88/cli/commands.go#L552


[ENTVTX-146] add a workaround for CLOUD-2195

Shouldn't the .openshift.io/service.yaml file also be updated?

Thanks!


HTTP/403 returned when attempting to add child group as user with correct permissions

In GitLab by @jasonpagetas on Jul 12, 2024, 04:40
Cannot add child groups. Returns 403. have checked permissions and I should be able to complete this action

In GitLab by @jasonpagetas on Jul 12, 2024, 04:40
marked this issue as related to #74

unassigned @jon-nfc

mentioned in commit 9bece0a811826b5577ac214c38dad11bb8249e7f


attributeChangedCallback not being called

Now that I have things running, I noticed that attributeChangedCallback isn't being called. I have code like the following:
import 'document-register-element'

class MyEl extends HTMLElement {
    constructor() {
        super()
        console.log('my-el constructed')
    }

    connectedCallback() {
        console.log('my-el connected')
    }

    disconnectedCallback() {
        console.log('my-el disconnected')
    }

    attributeChangedCallback(attr, oldVal, newVal) {
        console.log('my-el attribute changed', attr)
    }
}

customElements.define('my-el', MyEl)

let myEl = document.createElement('my-el')

document.body.appendChild(myEl)

myEl.setAttribute('foo', 'bar')

myEl.remove()

Expected output:
my-el constructed
my-el connected
my-el attribute changed foo
my-el disconnected

Actual output:
my-el constructed
my-el connected
my-el disconnected

Have you tried queueing a macrotask (setTimeout()) to remove the element so the Mutation Observer (microtask) has time to fire?

@treshugart I haven't, but if I don't remove the element, f.e.
import 'document-register-element'

class MyEl extends HTMLElement {
    constructor() {
        super()
        console.log('my-el constructed')
    }

    connectedCallback() {
        console.log('my-el connected')
    }

    disconnectedCallback() {
        console.log('my-el disconnected')
    }

    attributeChangedCallback(attr, oldVal, newVal) {
        console.log('my-el attribute changed', attr)
    }
}

customElements.define('my-el', MyEl)

let myEl = document.createElement('my-el')

document.body.appendChild(myEl)

myEl.setAttribute('foo', 'bar')

//myEl.remove()

then the output is just
my-el constructed
my-el connected

Ah, I should have noticed this before. In v1 you need to define observedAttributes.

class MyEl extends HTMLElement {
  ...
  static observedAttributes = ['foo']
  // or
  static get observedAttributes() {
    return ['foo'];
  }
  ...
}

when in doubt, check the test file. You need to specify a list of attribtues through a static observedAttributes as tested in here:
https://github.com/WebReflection/document-register-element/blob/master/test/document-register-element.js#L117-L143

Moreover, check the super() caveat: https://github.com/WebReflection/document-register-element#v1-caveat

@WebReflection @treshugart There is only a single algorithm that uses observedAttributes in the spec, and that algorithm doesn't specify what happens when it is undefined, it only specifies what happens when it is "not undefined".
Section 2.6 also says

When any of [a custom element's] attributes are changed, appended, removed, or replaced, [the custom element's] attributeChangedCallback is run.

Did I miss something spec? Or are you guys just following what Chrome is implementing natively?
Personally, I'd like for  observedAttributes to be optional, then if it is undefined  attributeChangedCallback would fire for all attributes like in v0. Having this functionality would be opt-in.

Interesting. "Guys" (just me here, no plural) took Chrome as reference
indeed. For perfomance sake, I thought it was mandatory to specify a list
of attributes and I don't see any advantage in having a filter opt-in.
However, if that's what specs are saying, I might just drop the filter if
the list is missing or ...empty? What if the list is defined but empty?
Blacklisting everything?
On Tuesday, 13 September 2016, Joseph Orbegoso Pea<EMAIL_ADDRESS>wrote:

@WebReflection https://github.com/WebReflection @treshugart
https://github.com/treshugart There is only a single algorithm
https://w3c.github.io/webcomponents/spec/custom/#element-definition
that uses observedAttributes in the spec, and that algorithm doesn't
specify what happens when it is undefined, it only specifies what happens
when it is "not undefined".
Section 2.6
https://w3c.github.io/webcomponents/spec/custom/#custom-element-reactions
also says
When any of [a custom element's] attributes are changed, appended,
removed, or replaced, [the custom element's] attributeChangedCallback is
run.
Did I miss something spec? Or are you guys just following what Chrome is
implementing natively?
Personally, I'd like for observedAttributes to be optional, then if it is
undefined attributeChangedCallback would fire for all attributes like in
v0. Having this functionality would be opt-in.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/WebReflection/document-register-element/issues/76#issuecomment-246803173,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFO9eO-T6CIbl0nnx54-qclq4O01ejFks5qpv9agaJpZM4J7Rs0
.

If defined but empty, maybe attributeChangedCallback never gets called, if that's what you meant by "Blacklisting everything"?

I've followed the discussion and it turns out this poly is doing the right
thing already
On Saturday, 17 September 2016, Joseph Orbegoso Pea <
<EMAIL_ADDRESS>wrote:

If defined but empty, maybe attributeChangedCallback never gets called, if
that's what you meant by "Blacklisting everything"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/WebReflection/document-register-element/issues/76#issuecomment-247747912,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFO9TaIf90duBGXOFQ2RwPcbMIW77lHks5qq2j7gaJpZM4J7Rs0
.

It's almost moot, because to be backwards compatible with v0 (which doesn't
have observedAttributes) we still have to write the conditional checks for
all attributes.
On Sep 17, 2016 5:30 AM, "Andrea Giammarchi"<EMAIL_ADDRESS>wrote:

Closed #76
https://github.com/WebReflection/document-register-element/issues/76.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/WebReflection/document-register-element/issues/76#event-787107782,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASKzlux4xFZvNN21jc45gpxq_IDcNlyks5qpkhPgaJpZM4J7Rs0
.

if specs change please let me know, thanks.


[iOS] Integration Flutter Module | Swift - List widgets won't scroll on iOS

1- Create a simple Flutter app (module) with a single page including ListView or SingleChildScrollView. Append as many children as possible to make it scrollable.
2- Create a simple iOS native app, which has two controllers. Controller A has a button which initializes controller B. Controller B initializes and adds FlutterViewController into itself.
3- Run the app on the simulator using Xcode 13, IOS version 10 or later, Flutter 2.10.5

Hi @romaCaldeira, thanks for filing the issue.
Please provide a complete runnable minimal code sample, preferably in a repo, that we can run and investigate further.
Can you also check if you still experience this issue on flutter 3? If you do, please provide the updated flutter doctor -v as well.
Thank you

my app crashes

Hi @see, kindly file a new issue and provide the relevant information required to investigate this issue.
Your issue seems unrelated to this.


Does this library using out-of-band (OOB) requests?

I got an email from Google saying that my account used the OAUTH OOB approach sometime in the past. I experimented with a bunch of libraries before going with gmail_xoauth, so I don't know if gmail_xoauth uses OOB or not. Can you indicate whether 0.4.2 is compliant with Google's no OOB starting 3-Oct-2022?
https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html
Thanks,
Tom

This library does not handle the login/token process. So it has nothing to do with OOB.
Still, the readme suggests using oauth2.py, with uses the OOB approach: https://github.com/google/gmail-oauth2-tools/blob/master/python/oauth2.py#L130


fix for syntax measure

Type of changes

[ ] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[ ] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[ ] I accept that @willmcgugan may be pedantic in the code review.

Description
Please describe your changes here. If this fixes a bug, please link to the issue, if possible.

Codecov Report
Base: 98.64% // Head: 94.97% // Decreases project coverage by -3.67% :warning:

Coverage data is based on head (fe1ed53) compared to base (7d126c8).
Patch coverage: 90.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2558      +/-   ##
==========================================
- Coverage   98.64%   94.97%   -3.68%
==========================================
  Files          73       63      -10
  Lines        7840     6806    -1034
==========================================
- Hits         7734     6464    -1270
- Misses        106      342     +236

Flag
Coverage Δ

unittests
94.97% <90.00%> (-3.68%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

rich/ansi.py
100.00% <ø> (ø)

rich/filesize.py
100.00% <ø> (ø)

rich/json.py
100.00% <ø> (ø)

rich/text.py
99.48% <75.00%> (-0.52%)
:arrow_down:

rich/panel.py
98.29% <88.88%> (-1.71%)
:arrow_down:

rich/console.py
96.44% <100.00%> (-1.57%)
:arrow_down:

rich/markdown.py
100.00% <100.00%> (ø)

rich/pretty.py
98.98% <100.00%> (+<0.01%)
:arrow_up:

rich/style.py
99.75% <100.00%> (ø)

rich/syntax.py
99.38% <100.00%> (+<0.01%)
:arrow_up:

... and 14 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Feature Request]: Addition of JS scripts along with the HTML code for a particular component

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Allow users to add snippets of JS with their HTML code. This will include the following:

Updating the model to store the JS code on the database
Sanitizing this code to prevent harmful code and for security reasons
Updating the UI

Use Case
This will allow users to upload components like dropdowns and carousels, which usually require some form of JS to work.
Benefits
Allows the users to upload a broader range of components.
Add ScreenShots
No response
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

hey @Parth18Shah, any updates?

There are no updates at the moment; just going through various approaches so I can implement this issue.


Default selection colours are difficult to see. Seem to be black on dark-grey.

Default selection colours are difficult to see. Seem to be black on dark-grey.
e.g.

I am using zsh with oh-my-zsh with these plugins:
plugins=(zsh-syntax-highlighting zsh-autosuggestions bgnotify colored-man-pages last-working-dir rand-quote osx brew autojump git github npm atom)

(Note, you can also see the bug mentioned in issue 24/183 in the screenshot.)

Possibly related: https://github.com/zeit/hyperterm/issues/177

Should be closeable after merge of #272

Selection now takes its color from cursorColor and is more visible https://github.com/zeit/hyper/commit/600f815dffe6fd835dfef5e3fde568a09bd286db ✌


SyntaxError: Cannot use import statement outside a module

I am trying to import this into a NestJS project, within my jest tests. I get the following error:
Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /path/node_modules/mock-jwks/build/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import nock from 'nock';

I am using yarn 2 PnP

Version 1 currently is being flagged by DependaBot as one of the downstream dependencies have some security issues.
I'm currently going through the same issue described by OP, and your example did not help much.
Could you please elaborate?

You can only use version 2  if your project is a esmodule. To make your project an esmodule, I linked a guide. I cannot support you further on this since there is more than enough material on this out there. I linked a demo project that uses mock-jwks as a esmodule, which is only possible because the example project is a esmodule too. Esmodules are the future, so in general I would recommend upgrading.
I will address the security vulnerability in version 1 even though mock-jwks is supposed to be a development dependency of your project. If it (or its subdepedencies) have security issues, this should not affect your production code, so for me it is a kind of non-issue. But I will fix it anyhow.

Is https://github.com/levino/mock-jwks/issues/193 your issue @pliniodng ?

@pliniodng please try https://github.com/levino/mock-jwks/releases/tag/v1.0.10

Yes, that is the issue. Thanks for releasing a patch version.

FYI, I am still seeing this issue in our ESM project:
 Details:

    /Users/kgrundl/src/fhir-auth/node_modules/mock-jwks/build/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { createJWKS, createKeyPair, signJwt } from './tools.js';
                                                                                ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      1 | import { FastifyInstance } from 'fastify';
      2 | import { URLSearchParams } from 'url';
    > 3 | import createJWKSMock from "mock-jwks";

We ended up writing our own testOriginServer but thought I would mention that the issue is still there.

Thank you for reporting. Unfortunately it is impossible for me to debug as long as I do not have an example repo to reproduce the bug. There might be so many things that cause this error in a code base that I cannot see.
For your information: I test the usage of the library. I have no issues importing the code from npm. You might want to make a PR to the test repository which adds the new functionality which triggers your error. However my fist assumption is, that you have something misconfigured, please double check while comparing to that test repository.


Set navigation toggle button color to white

On small devices such as Android the nav toggle button is displayed but can't be seen because both masthead and bars icon are black.
To fix this, the bars icon color is set to white by changing the color to global_Color_light_100 in navToggle.

Deploy preview for koku ready!
Built with commit bd4e4638b2266375feb59846ff47ad4a18e7a3b0
https://deploy-preview-80--koku.netlify.com

Codecov Report

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

@@           Coverage Diff           @@
##           master      #80   +/-   ##
=======================================
  Coverage   85.72%   85.72%
=======================================
  Files          98       98
  Lines         918      918
  Branches       92       92
=======================================
  Hits          787      787
  Misses        122      122
  Partials        9        9

Impacted Files
Coverage Δ

src/components/masthead/masthead.styles.ts
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@dlabrecq sure.
It was mentioned here and shown there

I don't want to hold up the PR, so I'll approve. @dmiller9911 can comment later...

ping @dmiller9911


FDCAN issues

I happened to spot some (potential) issues in the FDCAN support

TXBCR TXBCF and TXBTO registers are bitmaps, not ordinals fdcan.rs#L1396
TXBRP register is a bitmap fdcan.rs#L1415
Tx buffer element ID_W is missing its top bit txbuffer_element.rs#L130 See RM0440 rev5 44.3.6
accept_all_into_fifo1() has the action for FIFO0 filter.rs#L40 filter.rs#L83

Related: Thoughts on a standalone fdCAN crate, like the bxCAN one?

Implementation suggestions: Would be nice to get the raw ID from ExtendedId and StandardId from outside the crate. Maybe make as_raw() public or some other way.
A nice way would be to have a crate to abstract this for every can implementation, so the ID types can be used in crates which should support any can implementation.

I happened to spot some (potential) issues in the FDCAN support
* `TXBCR` `TXBCF` and `TXBTO` registers are bitmaps, not ordinals [fdcan.rs#L1396](https://github.com/stm32-rs/stm32g4xx-hal/blob/master/src/fdcan.rs#L1396)

* `TXBRP` register is a bitmap [fdcan.rs#L1415](https://github.com/stm32-rs/stm32g4xx-hal/blob/master/src/fdcan.rs#L1415)

* Tx buffer element `ID_W` is missing its top bit [txbuffer_element.rs#L130](https://github.com/stm32-rs/stm32g4xx-hal/blob/master/src/fdcan/message_ram/txbuffer_element.rs#L130) See RM0440 rev5 44.3.6

* `accept_all_into_fifo1()` has the action for FIFO0 [filter.rs#L40](https://github.com/stm32-rs/stm32g4xx-hal/blob/master/src/fdcan/filter.rs#L40) [filter.rs#L83](https://github.com/stm32-rs/stm32g4xx-hal/blob/master/src/fdcan/filter.rs#L83)

Ooh, good points, nicely spotted!
I'll work on that tomorrow.

Related: Thoughts on a standalone fdCAN crate, like the bxCAN one?
I'm all for it; I needed the fdcan support, so I made it for the g4 as a stopgap measure, but please go ahead and copy this into a  stand-alone crate. I had that idea but this seemed like a good first stepping stone to me.

Implementation suggestions: Would be nice to get the raw ID from ExtendedId and StandardId from outside the crate. Maybe make as_raw() public or some other way.
I'll add this

A nice way would be to have a crate to abstract this for every can implementation, so the ID types can be used in crates which should support any can implementation.
That also sounds like a good idea to me!

For shared traits, there's already the new CAN traits that were recently merged into embedded-hal here, which came from the embedded-can crate with some slight modifications. Right now the latest embedded-hal version doesn't yet include the new CAN traits, but it should soon (perhaps even in a new 0.2 release); in any event it seems like using that trait for the ID types would be nice for cross compatibility.
Having a separate fdcan crate which could be shared between the various HALs sounds good too, please shout if you need any help creating a repo in stm32-rs.

please go ahead and copy this into a stand-alone crate

I've made a standalone crate here. It includes a svd2rust-style PAC that applies to the FDCAN register mappings for G0 G4 L5 and H7, although unfortunately the H7 (and MP1) registers are different enough from everything else that I decided to use feature flags to switch between them.
I would also support using either the embedded-can (probably the most practical at the moment) or embedded-hal traits.

I think it's better to leave the traits out of it, in the style of bxCAN and stm32-usbd.
Great work.


Documentation: pick one of cri-o / Docker for minikube GSG

We have instructions for both Docker and cri-o setup in the minikube GSG. This adds a lot of boilerplate to the GSGs that is not relevant for users that want to see how Cilium works. Pick one of these container runtimes and remove the other from the minikube GSG.

This has been fixed in latest master.


Tracks are now grouped in tiles, render time considerably improved (#57)

#57
for 0.2 release

Let's merge this, we'll see the last bug later.


Convert time from second to datetime64

Saving this so I don't forget it:
example of a current  loaded dataset:
<xarray.Dataset> Size: 63GB
Dimensions:       (time: 745, node: 3539584, plan: 1, nelem2: 6898577, ndp2: 3,
                   nelem3: 6898577, ndp3: 3)
Coordinates:
    x             (node) float32 14MB ...
    y             (node) float32 14MB ...
  * time          (time) float64 6kB 0.0 3.6e+03 7.2e+03 ... 2.675e+06 2.678e+06
    ikle2         (nelem2, ndp2) >i4 83MB ...
    ikle3         (nelem3, ndp3) >i4 83MB ...
Dimensions without coordinates: node, plan, nelem2, ndp2, nelem3, ndp3
Data variables:
    VELOCITY U    (time, node, plan) float64 21GB ...
    VELOCITY V    (time, node, plan) float64 21GB ...
    FREE SURFACE  (time, node, plan) float64 21GB ...
Attributes: (12/17)
    title:     TELEMAC 2D Model
    meshx:     [ 145.26067   -117.35177    -96.901276  ...  158.9151    -122....
    meshy:     [ 15.181208 -27.162487  69.59621  ...  84.81109  -27.315842  4...
    nelem2:    6898577
    nelem3:    6898577
    npoin2:    3539584
    ...        ...
    iparam:    (1, 0, 0, 0, 0, 0, 0, 186317, 0, 1)
    var_IDs:   ['U', 'V', 'S']
    varnames:  ['VELOCITY U', 'VELOCITY V', 'FREE SURFACE']
    varunits:  [b'M/S             ', b'M/S             ', b'M               ']
    date:      (2023, 7, 1, 0, 0, 0)
    type:      2D

time should be instead:
time      (time) datetime64[ns] 2013-01-01 ... 2013-12-31T23:57:30 (example)
It would also propagate back in ds.selafin.write() to assign
the seconds in the core file
and also the first datetime of the file

Ok. But I would rename "date" into "date_start" (or "starting_date"?) to avoid the confusion with the new datetime serie.


Add log search feature

This PR is a continuation of @ysm001's PR #1522 that is meant to resolve #1041.
This revision contains the following:

Resolves Uncaught TypeError issue https://github.com/docker/kitematic/pull/1522#issuecomment-200075306
Adds the ability for users to do case insensitive search.

Also, I did sign my commits but I am not sure why they were not generated in this PR. Am I missing something?

Can you merge master into this one?

Yep! I have just merged the changes.

Couple of UX things:

Can we make the 'search' box more visible? Maybe adding a top white border?
Add a find icon perhaps similar to atom's:

Finally, it would be really nice to have the Find + Find Next as part of the menu item, under edit - This will also allow the declaration of the shortcut keys and make them viewable to the user.

I was able to add Find to the menu but was unable to get it to actually register when I selected it in the menu. Can I replicate the selector functionality or do I need to create a click callback function?

Sorry for the delay in checking this - I'll take a look tomorrow and will provide some feedback.

I can't seem to come up with a good way to target the current container selected while in the menu - We may need to add some sort of place-holder to keep track of the currently selected container.

@ClemMakesApps WDYT about having a tracker for 'current' container detail shown and use that to allow the Find menu

@FrenchBen not sure what you mean by that. Also, I don't think I have the bandwidth to continue this MR 😞

I want this feature. I wanted create but many people tried it


prom_exporter using a python logger (configurable logLevel)

fixes https://github.com/DECSIS/docker-barman/issues/19
finally added this myself to better debug how many barman commands are spawned and where time is spend (this could be quite improved)..  as the current exporter execution can be slow (taking 10secs) if you have prometheus default scrape_interval=15s 🎱

@rsilva4 what do you think?
(ps: I tested the changes, they should not decrease stability in any way)


change code coverage to 2.0 branch

@nightlark can you change the code coverage to be reporting on the 2.0 branch.    We will have to update this again in a month when we move 2.0 to master and develop but since I am adding tests to the 2.0 branch for the next while.  It would be very useful to see the coverage reports on that branch.

Do you mean change the status button in the readme to be for the 2.0 branch? Code coverage builds are running for the 2.0 branch as part of the daily build, but the core test cases are timing out.

Mostly I just want to see the code coverage results on the HELICS 2.0 branch.  At some point we will move over the status button, but that wasn't my concern for the moment.  I just will be writing some more tests over the next month and I want to track the coverage changes that result, and those will be on the 2.0 branch.  So I want to make sure we are getting coverage results from that branch into the webpage.  If the failure in the core-test branch was the reason,  I will look more into the issue there.

Okay -- no output is the reason it is failing, but it could be that 10 minutes isn't enough to run all of the core tests on Travis; we can see if it passes on the daily build tonight.

it looks like with coverage the tests are taking about double  normal time, and if the core_tests times out that would be 4 minutes with just that one.    I should figure out what is wrong with that test occasionally failing.  I need to enable some more detailed output to see which test is stalling.

@nightlark  can you turn off the java and python builds for the coverage tests on the HELICS_2_0 branch?  They are not necessary for the code coverage purposes.  Actually come to think of it you can turn those off for the Valgrind, and Sanitizer runs as well.

The Java/Python tests aren't running on the coverage/valgrind/sanitizer builds. Do we want the interfaces to not get built at all for these tests? And do we still want the README to have links to the codecov badge for the HELICS_2_0 branch?

I don't think it is necessary to build the language interfaces since we build and test them for other tests.  For the README we plan to move the HELICS_2_0 to develop at the beta.2 release so it might not matter for long as the 2.0 branch will cease to exist in the near future.

now that the 2.0 branch has migrated to develop this issue is closed


Consolidated Docker CI workflows with proper dependencies

This modification will allow all the Docker images for Jitsi Meet to be built in one end to end pipeline, properly using the new build's base images for the dependent image builds within the branch/pr/tag. Also will run on a 'testing' branch with a separate tag. This will allow us to do the building/testing necessary for this PR which involves overhauling the base images completely since the existing builds still use the upstream base images and hosting the testing branch images will allow for testing the in an actual cluster without touching the release images.

hm, seems this may need some attention before merging:
buildx failed with: error: failed to solve: failed to solve with frontend dockerfile.v0: failed to create LLB definition: failed to parse stage name "ghcr.io/matrix-org/docker-jitsi-meet/base:17/merge": invalid reference format

Looks like the ${{ github.ref_name }} parameter isn't working as expected..

Looks like that did the trick :)

Agreed on both points and noted for later :)


Does it make any difference if the projects being tested/covered are built in DEBUG or RELEASE mode?

Does it matter if the projects which are getting tested against, if they are built using DEBUG or RELEASE configuration?
I know the test project isn't covered so I don't care what that is built against ... but the test project tests OTHER netstandard libraries / netcore apps ... which I'm wondering if I do care about the 'configuration' setting for those.

Yep the configuration changes the results because compiler could emit different IL so you can run you CI with both configuration(I advice to do that for testing reason) but you could see slightly different coverage result, check this old issue for instance https://github.com/tonerdo/coverlet/issues/389

For testing perspective it's very different usually related to performance always from emitting side and also because usually in debug/checked mode you run assertion and preprocessor use #define DEBUG or [Conditional("DEBUG")]  for istance diagnostics assertion https://github.com/dotnet/runtime/blob/4f9ae42d861fcb4be2fcd5d3d55d5f227d30e723/src/libraries/System.Private.CoreLib/src/System/Diagnostics/Debug.cs#L88
Semantics must remain the same.

Thanks heaps @MarcoRossignoli for the prompt reply 👍
I sorta don't understand what you are saying though 😊
Yes -> DEBUG creates different IL compared to RELEASE. Okay, that make sense .. but what should I be using for code coverage?
I had a read over #389 and it was a bit .. technical for me 😊
So even though there's different IL, should we be testing our projects that are compiled under DEBUG configuration for code coverage because there's less optimizations, etc?

DO testing DEBUG/RELEASE and check coverage report under DEBUG, btw if you've a simmetric CI where you simply pass $(configuration) as parameter won't be a problem you'll test/cover both config and it's ok. Debug report of coverage are usually more "precise" related to covered line because IL/pdb emitted by compiler is more "detailed".

For instance check coverlet CI https://github.com/tonerdo/coverlet/blob/master/eng/build.yml we build test and cover in both configuration...I'll check only debug one.

I mean usually debug it's enough, but suppose to have a bug where some code run only in debug mode and with that coverage percentage reach 90% but you'll find that in release mode drops under 80%...likely it's something to double check.

Oh wow! that's ... really interesting.
CI/CD Summary

Run all builds and tests in DEBUG and RELEASE configurations (leveraging the matrix ability for this!)
Only publish the RELEASE nugets.

But how is is the code coverage kicked off?
Checking the latest build (at the time of me posting this reply) at Azure Dev Ops shows this:
yml task:
- task: DotNetCoreCLI@2
  displayName: Test
  inputs:
    command: test
    arguments: -c $(BuildConfiguration) --no-build /p:CollectCoverage=true /p:CoverletOutputFormat=opencover /p:Include=[coverlet.*]* /p:Exclude=[coverlet.tests.remoteexecutor]*
    testRunTitle: $(Agent.JobName)

build log:
[command]C:\hostedtoolcache\windows\dotnet\dotnet.exe test --logger trx --results-directory d:\a\_temp -c Debug --no-build /p:CollectCoverage=true /p:CoverletOutputFormat=opencover /p:Include=[coverlet.*]* /p:Exclude=[coverlet.tests.remoteexecutor]*
Test run for d:\a\1\s\test\coverlet.core.tests\bin\Debug\netcoreapp2.2\coverlet.core.tests.dll(.NETCoreApp,Version=v2.2)

which suggests it's the MSBuild way? Where is the msbuild stuff defined/set? I also thought that the preferred way is to do this via the coverlet.collector nuget package, not msbuild? (I personally prefer dotnet tool's over msbuild )

Yes we use msbuild at the moment because we know that it doesn't affect by know issue, so you should use collectors if possible.

For us it's also a way to test engine, we use code just build and we inject it through msbuild targets, but it's only for internal use.

Okay, so if I use the coverlet.collector by referencing the nuget package in my test project, will that ignore that test project by default ?

Yep, you can follow our hello world sample https://github.com/tonerdo/coverlet/tree/master/Documentation/Examples/VSTest/HelloWorld with and without runsettings

Hi again @MarcoRossignoli - I'm back here trying to get this working once more.
TL;DR;
I'm not getting any summary of results, listed to the terminal.
 In it you have various OS flavours and are doing both DEBUG and RELEASE builds. Great.
In all of the TEST step, it produces a nice graphical result to the logging console out.
e.g.
Calculating coverage result...
  Generating report '/home/vsts/work/1/s/test/coverlet.core.tests/coverage.opencover.xml'

+------------------------------------+--------+--------+--------+
| Module                             | Line   | Branch | Method |
+------------------------------------+--------+--------+--------+
| coverlet.tests.projectsample.empty | 0%     | 100%   | 0%     |
+------------------------------------+--------+--------+--------+
| coverlet.msbuild.tasks             | 0%     | 0%     | 0%     |
+------------------------------------+--------+--------+--------+
| coverlet.core                      | 83.65% | 78.2%  | 84.07% |
+------------------------------------+--------+--------+--------+

+---------+--------+--------+--------+
|         | Line   | Branch | Method |
+---------+--------+--------+--------+
| Total   | 71.74% | 69.83% | 61.9%  |
+---------+--------+--------+--------+
| Average | 27.88% | 59.4%  | 28.02% |
+---------+--------+--------+--------+

I'm not getting this report into my logs. I'm using the "collector" solution (not msbuild, not global tool). Is that why?
e.g.
steps:
- task: DotNetCoreCLI@2
  displayName: 'Tests'
  inputs:
    command: test
    projects: '${{ parameters.solutionFile }}'
    arguments: -c $(BuildConfiguration) --no-build --collect:"XPlat Code Coverage"
    testRunTitle: $(Agent.JobName)

and each xunit test project includes the nuget package...
<ItemGroup>
  <PackageReference Include="coverlet.collector" Version="1.2.0">
    <PrivateAssets>all</PrivateAssets>
    <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
  </PackageReference>

  ...<skip>...

</ItemGroup>

When I look at the logs in AzureDevOps, I can see this at the top ...
/usr/bin/dotnet test /home/vsts/work/1/s/Foo.Search.sln --logger trx --results-directory /home/vsts/work/_temp -c Debug --no-build --collect:XPlat Code Coverage
so it looks for all the tests in the .sln and finds them and runs the discovered tests. Here's an example output:
Results File: /home/vsts/work/_temp/_fv-az175_2020-01-08_07_11_45.trx

Attachments:
  /home/vsts/work/_temp/58960cd6-99b6-47b1-8468-6df3845c9ed7/coverage.cobertura.xml
Test Run Successful.
Total tests: 52
     Passed: 52
 Total time: 26.6901 Seconds

So it looks like:

it created a tests results file (that .trx file)
some coverage file (that coverage.cobertura.xml file)

but noticed how it says: Attachments .. is that causing this to not print? This repo ReadMe.md says:

A summary of the results will also be displayed in the terminal.

which is not occurring :(
I also tried using change the format to opencover, but that errored all the time => wrong or bad switch. e.g. arguments: -c $(BuildConfiguration) --no-build --collect:"XPlat Code Coverage" --format:opencover  [there's no docs explaining what the syntax is]

Simply printing results to console is not supported for collectors for the moment.
Collectors are a totally different beast than .net tool and msbuild, we don't have complete control of workflow but we're injected inside the vstest engine.
BTW I'll open a new issue to understand if/how we can show reports on console like .net tools and msbuild.

Kewl thanks - much appreciated.
Q1: So even though there's no output to the terminal (reported separately in #681) it still creates the coverage xml file ... which means we could still use a 3rd party tool to help interegate the coverage results (e.g. codecov.io or ReportGenerator), right?
Q2: Secondly, in your azure pipelines for this repo, you so DEBUG and RELEASE. How do you only get coverage for DEBUG tests? It feels like each OS generates coverage for DEBUG and RELEASE mode? The scenario is that I wish to generate coverage for DEBUG only (as suggested by you, above) and then use a 3rd party to interigate the results.
Q3: Lastly, how do you specify the format using the coverage tool. The collector docs  say the only optional parameter is format but I can't figure out how to use that param properly, on the command line.

Q1: So even though there's no output to the terminal (reported separately in #681) it still creates the coverage xml file ... which means we could still use a 3rd party tool to help interegate the coverage results (e.g. codecov.io or ReportGenerator), right?

Yes

Q2: Secondly, in your azure pipelines for this repo, you so DEBUG and RELEASE. How do you only get coverage for DEBUG tests? It feels like each OS generates coverage for DEBUG and RELEASE mode? The scenario is that I wish to generate coverage for DEBUG only (as suggested by you, above) and then use a 3rd party to interigate the results.

If you want keep coverage for release but they are different because different IL is emitted by compiler.

Q3: Lastly, how do you specify the format using the coverage tool. The collector docs say the only optional parameter is format but I can't figure out how to use that param properly, on the command line.

You need to provide a runsetting file and inside format element include the list of formats https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/VSTestIntegration.md#advanced-options-supported-via-runsettings
Take a look to samples https://github.com/coverlet-coverage/coverlet/tree/master/Documentation/Examples/VSTest/HelloWorld
I apologize for late answer I lose this last comment and I don't know why :bow:
Feel free to close if solved!

No probs at all.
Since I got some answers and clues to this issue, a few months ago, I've started doing coverlet coverage for DEBUG builds. I'm also doing a "matrix" which does both DEBUG and RELEASE builds at the same time:

coverlet for DEBUG
create publish artifacts for RELEASE (aka pack)

to do this, i'm using a powershell script which does one or the other, based on the 'configuration' (D or R).
works great :)
cheers 👍

Glad to hear!feel free to ask if you're in trouble!

Glad to hear!feel free to ask if you're in trouble!

I have a problem.
When the --configuration parameter is Debug, the valid coverage.cobertura.xml file is always generated.
When the --configuration parameter is Release and the Passed value is 100%, an empty coverage.cobertura.xml file may be generated or the coverage.cobertura.xml file may not be generated.
A complete and valid coverage.cobertura.xml file is generated only if the Passed value is less than 100%.


Set the large_image via web

We can set any image to large_image:
https://stackoverflow.com/questions/64417184/how-does-pypresence-work-where-do-i-get-the-image-key
Maybe we can upload the images on GitHub and use it as a source of flags instead of modifying in discord developer portal.

Example of an image in GitHub:
https://raw.githubusercontent.com/ThiaudioTT/ThiaudioTT/main/img/reisen.jpg
It seems that it follows a pattern, probably we can use it.

Maybe we can use a JSON file on the github repo where the key would be the country and the value would be the link to the image?
I could be wrong, but I think we can request a raw version of files like JSON.
We could use a request.get on the JSON and get the link of the image from there

Quick update:
It is possible
https://stackoverflow.com/questions/60219180/importing-json-file-from-github-into-python-getting-error-jsondecodeerror-exp

Maybe we can use a JSON file on the github repo where the key would be the country and the value would be the link to the image?

That's a possible way of doing it, but I think that uploading the image on the web and setting it on the countries.py should be enough

That's a possible way of doing it, but I think that uploading the image on the web and setting it on the countries.py should be enough

Oh like a dictionary in countries.py instead of the repo? That would be an easier way to do it.

Oh like a dictionary in countries.py instead of the repo? That would be an easier way to do it.

Yes! It can be a hash table, currently we are doing using the match condition:
   match country:
      case "GER":
         country = "Germany"
         flag = "german_reich"
      case "ITA":
         country = "Italy"
         flag = "italy"
      case "JAP":
         country = "Japan"
         flag = "japan"
      case "EXAMPLE"
         country = "country example"
         flag = "https://sourceForCountryExample.jpg"

But I don't know if using hash table would be better:
country = countries[countryInput]
flag = country['flag']

There's several ways to do it, but I wanna go with the simplest and efficient one.

What if the dictionary had a tuple in it like this:
_dict = {
  GER : (Germany, german_reich),
  ITA : (Italy, italy)
}

# Accessing dict
country = _dict[countryInput][0]
flag = _dict[countryInput][1]

This would remove the switch statement completely

I made changes to my fork to show what it would look like, I would have made a pull request but I don't have the link to the assets so for now theres placeholders where the img link is supposed to be.

Nice, lgtm.

I don't have the link to the assets
For these countries already added, I don't think we need to set new ones

For others though:
https://hoi4.paradoxwikis.com/Countries
We can use the source on the wiki.

We can go that way:
Use that tuple and set the image not in github, but instead on imgurl (for cases where is fictional country) or hoi4 wiki ("built-in countries").

I think Hoi4 wiki is a nice start, I'm not sure how we'd add fictional countries without manually doing so.
I'm a little confused. On the wiki there are two tables listing all the countries, do we want to add the 2nd table too? Or just the 1st.

I'm not sure how we'd add fictional countries without manually doing so.

Fictional countries we need to add manually. These countries are mods, I'm saying this because we probably want to add in the future.

On the wiki there are two tables listing countries, do we want to add the 2nd table too? Or just the 1st.

You are talking about "releasable countries"? We need to add them too.
These releasable countries are countries that at the early of the game does not exist. As the game advances, these countries may appear.

Okay, working on it now. The only issue I am seeing is that some countries have more than one tag like Bulgaria and Italy.
I'm not sure what this looks like in-game or in the save file. So I'm not sure if this is something we should be worried about.
There are also some countries that have the tag D## such as Vojvodina and Dalmatia.
I'm unsure what to do about those countries either.
We could make a switch-case for these special cases but there's no way to differentiate countries with the same tag like Vojvodina and Dalmatia because of getCountry()'s parameters.

I'm not sure what this looks like in-game or in the save file. So I'm not sure if this is something we should be worried about.

I think the main script care about this part, the caller function needs to send the correct tag and deal with picking it and the getCountry only update the image and the flag based on it.
If you hover the mouse on the tag, it will say the country's name

I've never seen these additional tags personally and I could be wrong but I think that the main tag should be enough. Even the wiki apparently doesn't know about it.
If you have anymore doubts about it, see: https://forum.paradoxplaza.com/forum/threads/hoi4-resource-history-spreadsheet-updated-to-include-barbarossa-1-11-5.1509285/

There are also some countries that have the tag D## such as Vojvodina and Dalmatia.

Indeed, it seems that these tags are for civil war countries and I don't know how the game differentiates it, but this is a very special case, rarely someone play as one.
I think that we can just ignore for now and create an issue to investigate it.

Okay so update, I made a web scraper and automated the process of adding every country in the game.
https://github.com/Wolfmyths/hoi4-presence/commit/5be25827c848a13551a9bda63776423133da38ce
This adds up to 259 countries total. The hashmap was very much needed lmao.
As the commit description says, there are some countries that don't have a wiki page at all. The thumbnail images of those countries are probably too small to use. So I'm guessing we're going to use imgur for these?
The dictionary is really big so if you want to put it in a separate file or put it somewhere else in the script let me know.

As the commit description says, there are some countries that don't have a wiki page at all. The thumbnail images of those countries are probably too small to use. So I'm guessing we're going to use imgur for these?

Yes

The dictionary is really big so if you want to put it in a separate file or put it somewhere else in the script let me know.

Put in the end of the file. I think exporting to another file would be bad because python treat as a module. But you tell me, if putting in another file is better, go in this way.

Alright I was able to find even more flags on the wiki. Almost all countries have image links.
But some came out to be like in a super small resolution. And some flags I was just not able to find at all on imgur and the wiki.
The flags I found on imgur may also be different than the game's since the country's flag may have changed since WW2.

Put in the end of the file.

I forgot to put this in the commit description but I also moved the dictionary to the bottom of the script
https://github.com/Wolfmyths/hoi4-presence/commit/7ccf945015f7686a4f48b4a56bf25604cce8638f

But some came out to be like in a super small resolution. And some flags I was just not able to find at all on imgur and the wiki.

You can upload it on imgur or just use the image on wikipedia.

Closed: #27


Usage as background video

Hi @t-obi! Awesome project!
I'm interested in using it as a background video (with other content on a layer above it), like here is done for an image:

      Blah blah

So here the "Blah blah" is show on top of the image. Is this possible with your video component in some way?
Cheers!

Hey,
thanks for the kind words.
The second example is pretty much what you are describing: http://www.kloht.com/react-video-cover/#/background
The source is over here: https://github.com/t-obi/react-video-cover/blob/master/examples/BackgroundCoverExample.js
Basically it renders the video with fixed position to fill the page, with a negative z-index so that your content would be visible above it.
I think there might be different approaches to implement this, but yes it should definitely be possible. You can't pass any children at the moment though. Actually that might be a good idea to add - I'll think about it.

Thanks for the quick answer!
Maybe it can also be done without any changes, just using CSS, have a look at this: https://jsfiddle.net/cwells/7req2mdd/

That jsfiddle didn't use object-fit: cover, I have edited it slightly: https://jsfiddle.net/tkloht/y61s3vqk/3/
You can have that same effect with react-video-cover, check out this repo which is pretty much copy/paste from the jsfiddle and replaced the  with object-fit-cover: https://github.com/t-obi/background-video-example. The relevant code is in src/App.js, some styles in src/index.css. You can see the result over here: http://www.kloht.com/background-video-example/
hope that helps :)

Thanks a lot Tobias!


Missing "Remove characteristic"  functionality

We've switched recently from arduino framework BLE implementation to NimBLE and we really like the 400k it saves us!
But I am missing the possiblity to remove a characteristic from a service.
Is there a specific reason for not enabling those functions?

If you are asking about removing remote characteristics on the client that functionality was renamed.
https://github.com/h2zero/NimBLE-Arduino/blob/f970a1eac81c9f1bdfdb4d93038d8500b716ef20/src/NimBLERemoteService.h#L45

No I meant removing a characteristic from a NimBLEService

That server side functionality has not been brought up before and I did not see it in the original library so it wasn't ported to this.
It could be added in a similar manner as removeService, PR's are welcome 😃.

@Bascy I just opened a PR for this #264, if you'd like to test it I'd appreciate any feedback.


Schema support?

Thanks for implementing this! I've been meaning to move my Dendron vault over to Obsidian since development on Dendron was paused.
Are you planning on adding support for Dendron schemas? If not, would be happy to take a stab at it eventually.

Currently i do not have plan to add Dendron schema suppor. I do not use Dendron schema. I also do not know how Dendron schema work. I will be happy if you are willing to implement it.

I might take a stab at it!

@levirs565 I really appreciate you making this, it's been nice!
@nbbaier are you still working on this?

I never really started, I might eventually get at it but if you want to contribute go ahead!

I ended up using a different approach to organize instead, so I won't be working on it either.

What have you moved to, @YeungOnion?

I don't have a lot of notes, so I'm doing my best to "type" references and I'll see what structure appears. I don't have a great tool for visualization yet, but I figure I have some time.
I implement these as properties so it's a subpar workflow instead of some modification of the wiki syntax. Further, I found a tool, LogSeq, that allows me to reference smaller, non-header units of text ("blocks") and I've been liking that granularity without needing to create a header for that link target.


Issue #SB-2501 fix: Course-Text inside previous button has CSS issue

@harishgilimi - Please review this PR.

@harishgilimi - Yeah sure will do that

@lakhanmandloi Requested changes done, Please review the updated code


chore: add find_block_by_hash and more docs

The BlockProvider trait was used to fetch blocks from disk,
for payload building we also want to access pending blocks (from the tree)
This removes a lot of ambiguity by clarifying where implementors should provide blocks from, and adds a new type BlockSource that can be used to specify where blocks should be looked up from.

Codecov Report

Merging #2405 (f3b9dd0) into main (9fb66ff) will decrease coverage by 53.27%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2405       +/-   ##
===========================================
- Coverage   71.66%   18.40%   -53.27%
===========================================
  Files         486      486
  Lines       59696    59725       +29
===========================================
- Hits        42781    10990    -31791
- Misses      16915    48735    +31820

Flag
Coverage Δ

integration-tests
18.40% <0.00%> (-0.02%)
:arrow_down:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/storage/provider/src/lib.rs
0.00% <ø> (-100.00%)
:arrow_down:

crates/storage/provider/src/providers/database.rs
0.00% <0.00%> (-20.32%)
:arrow_down:

crates/storage/provider/src/providers/mod.rs
0.00% <0.00%> (ø)

crates/storage/provider/src/test_utils/mock.rs
7.55% <0.00%> (-13.91%)
:arrow_down:

crates/storage/provider/src/test_utils/noop.rs
30.40% <0.00%> (-6.84%)
:arrow_down:

crates/storage/provider/src/traits/block.rs
23.52% <0.00%> (-16.48%)
:arrow_down:

... and 330 files with indirect coverage changes


add ancestry to folders

we're working on getting to the point where we can cleanup ems folders, and in order to do so we'll need ancestry on folders and resource pools.
https://github.com/ManageIQ/manageiq-cross_repo-tests/pull/155

and this as well, please: @kbrock could I get a comment from you here about what I need to go here to get this moving forward?

and this as well, please: @kbrock could I get a comment from you here about what I need to go here to get this moving forward?


Warema Weather Station Plus

I'd like to add a feature request for the Warema Weather Station Plus. Basic support seems to be there, the device shows up in Home Assistant, however only the Illuminance entity is present, and the logs show a warning as the entity is reporting in 'klx' as opposed to 'lx' which is supported by HA. Here is the log information for the device:
2023-11-15 15:00:41.476 INFO (MainThread) [custom_components.homee] Found node Weather Station, with following Data: {'id': 10, 'name': 'Weather%20Station', 'profile': 3013, 'image': 'nodeicon_weatherstation', 'favorite': 0, 'order': 5, 'protocol': 23, 'routing': 0, 'state': 1, 'state_changed':<PHONE_NUMBER>, 'added':<PHONE_NUMBER>, 'history': 1, 'cube_type': 14, 'note': 'WAREMA%20Wetterstation%20Plus%20%281667338%29', 'services': 5, 'phonetic_name': '', 'owner': 2, 'security': 0, 'attributes': [{'id': 69, 'node_id': 10, 'instance': 0, 'minimum': 0, 'maximum': 1, 'current_value': 1.0, 'target_value': 1.0, 'last_value': 0.0, 'unit': '', 'step_value': 1.0, 'editable': 1, 'type': 385, 'state': 1, 'last_changed':<PHONE_NUMBER>, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': ''}, {'id': 70, 'node_id': 10, 'instance': 0, 'minimum': 0, 'maximum': 25, 'current_value': 2.0, 'target_value': 2.0, 'last_value': 2.5, 'unit': 'm%2Fs', 'step_value': 1.0, 'editable': 0, 'type': 146, 'state': 1, 'last_changed':<PHONE_NUMBER>, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': '', 'options': {'history': {'day': 1, 'week': 26, 'month': 6}}}, {'id': 71, 'node_id': 10, 'instance': 0, 'minimum': 1, 'maximum': 100, 'current_value': 7.0, 'target_value': 7.0, 'last_value': 8.0, 'unit': 'klx', 'step_value': 0.5, 'editable': 0, 'type': 11, 'state': 1, 'last_changed':<PHONE_NUMBER>, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': '', 'options': {'history': {'day': 1, 'week': 26, 'month': 6}}}, {'id': 72, 'node_id': 10, 'instance': 0, 'minimum': 0, 'maximum': 500, 'current_value': 500.0, 'target_value': 500.0, 'last_value': 500.0, 'unit': 'lx', 'step_value': 2.0, 'editable': 0, 'type': 301, 'state': 1, 'last_changed':<PHONE_NUMBER>, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': '', 'options': {'history': {'day': 1, 'week': 26, 'month': 6}}}, {'id': 73, 'node_id': 10, 'instance': 0, 'minimum': 0, 'maximum': 1, 'current_value': 0.0, 'target_value': 0.0, 'last_value': 0.0, 'unit': 'n%2Fa', 'step_value': 1.0, 'editable': 0, 'type': 101, 'state': 1, 'last_changed':<PHONE_NUMBER>, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': '', 'options': {'history': {'day': 35, 'week': 5, 'month': 1, 'stepped': True}}}, {'id': 74, 'node_id': 10, 'instance': 0, 'minimum': -20, 'maximum': 60, 'current_value': 5.5, 'target_value': 5.5, 'last_value': 5.5, 'unit': '%C2%B0C', 'step_value': 0.5, 'editable': 0, 'type': 5, 'state': 1, 'last_changed':<PHONE_NUMBER>, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': '', 'options': {'history': {'day': 1, 'week': 26, 'month': 6}}}, {'id': 75, 'node_id': 10, 'instance': 0, 'minimum': 0, 'maximum': 0, 'current_value': 0.0, 'target_value': 0.0, 'last_value': 0.0, 'unit': 'text', 'step_value': 1.0, 'editable': 0, 'type': 45, 'state': 1, 'last_changed':<PHONE_NUMBER>, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '3842110A', 'name': ''}, {'id': 76, 'node_id': 10, 'instance': 0, 'minimum': 0, 'maximum': 1, 'current_value': 0.0, 'target_value': 0.0, 'last_value': 0.0, 'unit': 'n%2Fa', 'step_value': 1.0, 'editable': 1, 'type': 170, 'state': 1, 'last_changed':<PHONE_NUMBER>, 'changed_by': 1, 'changed_by_id': 0, 'based_on': 1, 'data': '', 'name': ''}]}

Many thanks!

https://github.com/Taraman17/hass-homee/wiki/Warema-Weather-Station-Plus

I am now getting temperature too but nothing else.

Yes, thats correct.
I fixed the Temperature sensor in the last release and the rest of the weather station will be in the next one.

Great, thank you so much!

I added initial support for the values to the new beta release.

The Dawn sensor. It measures Lux from 0-500, but what does it show in Homee? What happens if Illuminance is over 500 lx?

All Warema light sensors have a separate Lux and a KLux sensor. So the Lux sensor will stop at 500 and then the KLux sensor will start picking up from 1KLux. This is useful for dusk automation as 1KLux is still very bright. This also needs implementing for the standalone Warema photo sensors, they currently only show the KLux sensor.

Thx.
So does the low level sensor show 500lx all the time when it is over?
And to drive dawn, you would check if the sensor is between 1 and 499 LX?
Can you post a log of the standalone sensor?

Hi Markus,
Yes the ‘dawn’ sensor stays at 500 Lux.
I would determine a custom threshold within the dawn range of 0-500 to trigger a dawn automation. 500Lux mint still be too bright, 0 is pitch black darkness.  I use 120lx atm. So this needs to be a second standard sensor entity the same way the KLux sensor works.
Here is a screenshot of how the sensor works in Homee:
https://capture.dropbox.com/l3eczEW6BmlUBoot￼
Click to view
capture.dropbox.com
I will post logs tonight, I also need to do this for my 15 Warema raffstores as only their sensors work right now, not the actual control entities (they show as unavailable in HA).
Thanks for your work, I am hoping this can eventually free me from the poorly supported black hole Homee has become and just use it as a WMS gateway.

On 11 Jan 2024, at 12:53, Markus Adrario @.***> wrote:
Thx.
So does the low level sensor show 500lx all the time when it is over?
And to drive dawn, you would check if the sensor is between 1 and 499 LX?
Can you post a log of the standalone sensor?
—
Reply to this email directly, view it on GitHub https://github.com/Taraman17/hass-homee/issues/32#issuecomment-1886992420, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH3AFDGU5M2GFPQNDJJSL4LYN7HFHAVCNFSM6AAAAAA7MRT54SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBWHE4TENBSGA.
You are receiving this because you commented.

Here is the standalone photosensor log. It looks like we actually need two lx sensors, a dawn sensor  that is capped at 500lx and the standard sensor that starts at 1000lx.
Logger: homeassistant.components.sensor
Source: components/sensor/init.py:714
Integration: Sensor (documentation, issues)
First occurred: 10:07:49 (1 occurrences)
Last logged: 10:07:49
Entity sensor.e_photosensor_1490047_illuminance (<class 'custom_components.homee.sensor.HomeeSensor'>) is using native unit of measurement 'klx' which is not a valid unit for the device class ('illuminance') it is using; expected one of ['lx']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/Taraman17/hass-homee/issues

On 11 Jan 2024, at 13:03, Holger Schueler @.***> wrote:
Hi Markus,
Yes the ‘dawn’ sensor stays at 500 Lux.
I would determine a custom threshold within the dawn range of 0-500 to trigger a dawn automation. 500Lux mint still be too bright, 0 is pitch black darkness.  I use 120lx atm. So this needs to be a second standard sensor entity the same way the KLux sensor works.
Here is a screenshot of how the sensor works in Homee:
https://capture.dropbox.com/l3eczEW6BmlUBoot
I will post logs tonight, I also need to do this for my 15 Warema raffstores as only their sensors work right now, not the actual control entities (they show as unavailable in HA).
Thanks for your work, I am hoping this can eventually free me from the poorly supported black hole Homee has become and just use it as a WMS gateway.

On 11 Jan 2024, at 12:53, Markus Adrario @.***> wrote:
Thx.
So does the low level sensor show 500lx all the time when it is over?
And to drive dawn, you would check if the sensor is between 1 and 499 LX?
Can you post a log of the standalone sensor?
—
Reply to this email directly, view it on GitHub https://github.com/Taraman17/hass-homee/issues/32#issuecomment-1886992420, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH3AFDGU5M2GFPQNDJJSL4LYN7HFHAVCNFSM6AAAAAA7MRT54SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBWHE4TENBSGA.
You are receiving this because you commented.

Hi,
Sorry I meant the log as described here:
https://github.com/Taraman17/hass-homee/blob/master/README.md#homee-device-not-working-correctly

Yes, I tried this, but there is nothing else to see then the error I provided:
￼

On 12 Jan 2024, at 13:15, Markus Adrario @.***> wrote:
Hi,
Sorry I meant the log as described here:
https://github.com/Taraman17/hass-homee/blob/master/README.md#homee-device-not-working-correctly
—
Reply to this email directly, view it on GitHub https://github.com/Taraman17/hass-homee/issues/32#issuecomment-1889025869, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH3AFDEFJQTCE7GO7G4ZXETYOESOTAVCNFSM6AAAAAA7MRT54SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBZGAZDKOBWHE.
You are receiving this because you commented.

Or is it 'everything'?
home-assistant_2024-01-12T13-06-31.179Z.log

I check next days when I'm home...

Thank you very much for your effort for adding the weather-station plus functionality! Great to have it within this integration.
But there is one catch... after the update my homee lights (dimmable) are unavailable.

Can you open a seperate issue for that and provide me with any log-entries from homee or pymee?

Or is it everything in 'full logs' once I filtered?
home-assistant_2024-01-12T13-06-31.179Z.log

It is in the full log - It'll take a few days until I#ll be able to look into it however.

Thank you very much.


Use SaveReason.EXPLICIT when saving files before executing build tasks (#104296)

This way, files are auto-formatted and code actions are run. Which is desirable,
as saving happens in direct response to an explicit user action, as opposed to
auto-saving after a delay, in which case we don't want to modify files.
Also, it's consistent with what happens when saving files before debugging, in
which case we also save using SaveReason.EXPLICIT.
This PR fixes #104296.

I think debug's behavior should be changed here, not tasks. I will wait and here what @isidorn has to say.

I can see both cases here.
It is an explicit gesture, however it is not an explicit gesture to save.
I think that tasks and debug should be consitent. I am not sure what is the correct SaveReason though.
Nobody complained thus far for debug behavior. But I am open for a change, especially if @alexr00 feels strongly about it.

I have gotten feedback in the past that format shouldn't happen in this case: https://github.com/microsoft/vscode/issues/96904
I do think this is more of an auto save than an explicit save.

Makes sense to me.

Oh, so then it wasn't an oversight, but a deliberate change (for building). I had missed that, sorry.
In that case it seems the only solution is to introduce a new option that lets users make this choice. Something like editor.formatOnBuild or task.formatBeforeRun?

I do not have a problem with having a setting that both debug and tasks read. Maybe "editor.formatOnAutomation" (to match "terminal.integrated.automationShell.*")  @isidorn, what are your thoughts?

I would not introduce a setting right now. I would leave this open so we see if more users request this and would be open to add it in the future.

@isidorn sounds good.
@stefanhaller thank you for the PR. However, since we want to go a different direction with this I will close the PR and summarize the discussion in the original issue.


Support arbitrary values

What:

allow users to specify their own structs to be stored as values in FASTER
allow users to provide their own RMW logic
provide out-of-the-box implementations of above for numeric types, strings, vecs, bools and chars
add stand-alone examples
update README
add my name to author's list

Why:

many obvious reasons why a user would want more than just u64s
some cases where RMW implementation obvious but generally user defining RMW logic makes things easier for us
examples and README help users
I did some authoring :)

Closes: #5

Nice work!
I've been meaning to add you as author, but was not sure which email to use. So, good that you added it :+1:

Thanks :) I was undecided whether to use my academic email or personal email but feel it's nice having public contributions under one email.


[Feature] File Locksimth on Win 11 right click menu

Description of the new feature / enhancement
Such as topic
Scenario when this would be used?
Such as topic
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/21719


Suggestion dropdown doesn't appear for documentation tokens while changing to another token on the "Inspect" tab

While trying to remap documentation tokens on the Inspect tab the dropdown with suggestions doesn't appear after I typed "{someTokeName..." https://postimg.cc/QBC7mRWs

Can you tell me more about how you reached that state? For me this works:

@six7 I reached this state just as I described. Inspect tab —> trying to remap documentation token —> don't see/get suggestion dropdown after I type symbol "{"

Are by chance none of your token sets marked as active?

@six7 nope, all three that I use are active always

@six7 here is video https://youtu.be/dcngtWjv-0E

Thank you for that video, that explains it! I'm guessing our logic that decides what tokens to show in the dropdown doesn't include tokenName or other related tokens yet.
Instead we should show all tokens when using that dropdown, same is probably true for all other Documentation tokens.


Set iLo Security to ignore all using Ansible

Hello,
is it possible to disable all iLo Security warnings using ilo_redfish or general_redfish collections ?
I havent found an example role/playbook.
Currently we deploy and setup our server iLo using Ansible but cant import server into Oneview with Security Alerts.
We have to manually go and disable/ignore all warnings on each server using iLo web GUI.

I am afraid you'll need to write your own role/playbook to ignore them. In pseudo code, it would be something like:
For each member in {{iloURI}}/redfish/v1/Managers/1/SecurityService/SecurityDashboard ; do
PATCH {{iloURI}}/redfish/v1/Managers/1/SecurityService/SecurityDashboard/{{member}} with payload: { "Ignore": true }
endfor

thanks for response.
For now, I disabled them all with ilorest tool but it would be great to have native ansible of doing it - if it's possible to consider this as a feature request for this ansible collection.


how to get data from response object

Hi guy I am using swagger for my project, The problem what i am facing "unable to get data from the response object"  Can some one help me to identified what i have done wrong below ?
var SwaggerExpress = require('swagger-express-mw');
var app = require('express')();

//this is done for schema validation
 var schemaValidator = require('./api/middlewares/schema_mw/schemaValidator');
 var validator = new schemaValidator();
 var SwaggerUi = require('swagger-tools/middleware/swagger-ui');
 module.exports = app; // for testing

 var config = {
     appRoot: __dirname // required config
 } ;

SwaggerExpress.create(config, function (err, swaggerExpress) {

  if (err) {
    throw err;
}

//install middleware to validate request object
app.use(validator.requestValidator.bind(validator));

app.use(SwaggerUi(swaggerExpress.runner.swagger));

  // install middleware
  swaggerExpress.register(app);

  var middleware = function(req, res , next){
        res.end = function(data , encoding) {
       console.log(data);
   }
   app.use(middleware);
}
    var port = process.env.PORT || 10010;
   app.listen(port);

  });

I think you are in the wrong repository. This one is about the Open API specification (formerly Swagger specification), your problem seems about some kind of tooling based on that spec – from the code I would guess the correct project/repository to ask would be https://github.com/apigee-127/swagger-express. Please open an issue there (assuming its documentation doesn't help).

@2007ay - yup, for tooling specific questions, please open the ticket on the respective project.


MiqAction#action_evm_event should raise MiqEvent instead of EmsEvent.

Usually EmsEvent is used for provider events and MiqEvent is used for MIQ events.
Alert can be set based on Datastores. But EmsEvent has fields for vm, host and ems_cluster but not for datastore.
https://bugzilla.redhat.com/show_bug.cgi?id=1306308

@gmcculloug @gtanzillo Please review.
If this approach is correct, other RSS feeds for Alert also need to be changed to be based on MiqEvent.
A DB migration may also be necessary to convert those EmsEvents for alert to MiqEvents.

@lfu This change definitely makes sense to me. Seems like it was misaligned on EmsEvent all of this time. Do you know if there are other places in the code where there's an expectation that events generated from this action are of type EmsEvent? Maybe timelines?

@miq-bot remove_label wip

@gtanzillo The code that expects these events generated from this action are of type EmsEvent are those .yml files under product/alerts/rss. They have been fixed to refer to MiqEvent.

@h-kataria Please help verify the changes for Timeline.

@gmcculloug UI changes look good, timelines in UI seem to be working fine.

@gmcculloug @gtanzillo please review

:+1: Looks good!


Query for api keys in the index endpoint returns them weighted

Related https://github.com/CartoDB/support/issues/1714
Now we return the api keys ordered by type and every type has a weight.
First we get the master one, then the default and finally the regular
ones

@javitonino done!

:rocket: