Serialize time decimals using invariant culture (always use period as decimal separator)

Fixes #34 time bug where current culture is taken into account when serializing time decimals. Jenkins expects time decimals to use a period as decimal separator.

@thj-dk  Thanks, this is pretty much what I expected. Were you able to do any direct testing with this branch to confirm this fixes the issue?

@Siphonophora Yes. I tested the produced package from my branch using a local nuget repository. Using both cultures da-DK and nb-NO.
You can see the  different results here: https://gist.github.com/thj-dk/4596679994b0176b6c1ba4ef4534f388

@Siphonophora any chance of getting this fix merged and released? It's a bit of a deal breaker for us if we should use this lib or not.

@thj-dk Yeah, I've been thinking about whether there is an easy way to produce a test that would fail without this. I think that the JunitXmlValidator would probably raise an error if it was handed the version with commas instead of decimals.
That test would probably need to just call the serializer, directly, so we could control the thread culture, as it doesn't look easy to do that with the full acceptance test where we spin up an external process. If you want to give this a look, let me know. Otherwise I will.
I should have time to add the CLI flag over the weekend. In terms of release, what we would do is produce a pre-release package as these changes get merged down and ask you to verify the solution in your environment before moving to nuget.

@Siphonophora I can give the test a shot, but I cannot promise when. I'm a bit busy at the moment unfortunately.

@thj-dk Understood if you don't have much time. If you can only spend a little time I would rather ask you to spend it on #38 and I can do this.

@Siphonophora any chance on getting a new version released with this PR?

@thj-dk Yes, I will get that sorted this weekend. I have been thinking that because #39 doesn't look like a comprehensive solution to #34 that I will go ahead and remove that for now. This issue is a clear permanent fix and I'm happy to remove it. Let me know what you think, but I expect it will still be a while until #34 is fully sorted. If you have more feedback on that, it would be helpful.

@codito Can you cut a release? The only real change here is the bugfix from @thj-dk

@thj-dk Yes, I will get that sorted this weekend. I have been thinking that because #39 doesn't look like a comprehensive solution to #34 that I will go ahead and remove that for now. This issue is a clear permanent fix and I'm happy to remove it. Let me know what you think, but I expect it will still be a while until #34 is fully sorted. If you have more feedback on that, it would be helpful.

Thanks man. Regarding #34, i'm very busy at the moment, so I haven't got much time. We've currently sorted the problem using a custom powershell script that modifies the outputted xml to our needs. That'll do for now.

@codito Can you cut a release? The only real change here is the bugfix from @thj-dk

Done, v3.0.98 should be on nuget in a few minutes.

Thank's guys. Verified with success!


Winget doesn't remove old version of "double commander" when install new version

Brief description of your issue
When updating "double commander", winget won't remove the old version but install new ones directly.

Steps to reproduce

Install "double commander".
Wait for new release
Install again.

Expected behavior
Old version should be removed before installing the new ones.
Actual behavior
When updating "double commander", winget won't remove the old version but install new ones directly.

Environment
Windows: Windows.Desktop v10.0.19045.4291
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0

This should be moved to the winget-pkgs repo. The manifest may need a different UpgradeBehavior, such as uninstallPrevious.


data-role="table" : I need some explanations

Look at example:
https://codepen.io/TorakikiSan/pen/jKRpKo
Need some explanations.

Is it possible to define the width of the column? (style="width 3%;" for example)

Check the behavior of data-table-search-title against data-pagination-prev-title. The first works as I thought, while the second does not. Where am I wrong?

Ty!

Use attribute data-size for th
The question is not clear


chore: Release v1.9.32

/build-deploy-preview

/build-deploy-preview

/build-deploy-preview skip-tests=true

/ok-to-test


chore(deps): update dependency rollup to v4.26.0

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

rollup (source)
4.25.0 -> 4.26.0

Release Notes

rollup/rollup (rollup)
v4.26.0
Compare Source
2024-11-13
Features

Allow to avoid await bundle.close() via explicit resource management in TypeScript (#5721)

Pull Requests

#5721: feat: support using for RollupBuild (@shulaoda)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by Renovate Bot.

🛠 Docs Preview Building...

Configuration
{
  "repoOverrides": {
    "apollographql/apollo-ios-dev@main": {
      "remote": {
        "owner": "apollographql",
        "repo": "apollo-ios-dev",
        "branch": "renovate/rollup-4.x"
      }
    }
  }
}

aaf79ee7f1e84be01755b964c8a6ac1feefa1f70


Part 10,  hp_display.gd

I got through part 10, but noticed that my HP display had stopped working. It looks like you made some changes to hp_display.gd that aren't referenced in the actual tutorial. Once I made the change, it worked.
$ diff part_9/src/GUI/hp_display.gd part_10/src/GUI/hp_display.gd
8c8,9
< 	await ready
---
> 	if not is_inside_tree():
> 		await ready

Thank you for mentioning this, I will update the tutorial soon!

I just uploaded a version of part 10 that includes a mention of this.


Can't use whereHas in query filter

When I attempt to use the $query->whereHas method in a query filter, I get an exception:
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'has' in 'where clause' (SQL: SELECT

COUNT(id) AS aggregate FROM (select `scores`.* from `scores` where `scores`.`deleted_at` is null and

`has` = person and `deleted_at` is null group by `scores`.`id`) AS agg)

Here is my code:
    'query_filter'   => function ($query) {
        return $query->whereHas('person', function($q) {
                     return $q->where('special_number', '>', '0');
            })->whereNull('deleted_at');
    },

It appears that something is trying to parse whereHas like it would with where<property>, treating the word "has" as a property on the model.
I've temporarily worked around this by doing "join" statements to filter what I want manually.

@ssfinney screw wherehases :)


Update aws_accounts.json

Added Canada 🇨🇦  region for Cloudtrail and Redshift
Added Ohio 🇺🇸 region for Cloudtrail, Redshift and Access Logs
Changed Redshift and Access Logs URLs to https 🔒

Coverage decreased (-0.3%) to 51.515% when pulling b6c90d4521ab05dfe263bcca351be37cbdf5039d on markofu:develop into 265ac92dae427bc6ed6981c7dcf228eae1ffb5b0 on Netflix:develop.


Fix broken links to Restore and Save Actions in README.md

Fix broken links to Restore and Save Actions in README.md

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] 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 change)
[x] Documentation (add or update README or docs)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

please merge this!!

I find these two links works on both

https://github.com/actions/cache?tab=readme-ov-file and
https://github.com/actions/cache/blob/main/README.md

@knkarthik Could you point out in which case they are broken?

@muzimuzhi Oh, that's weird. https://github.com/actions/cache?tab=readme-ov-file#cache-action wasn't working for me.  I will close this PR then 🤷♂ .

@knkarthik Which browser are you using? Maybe the behavior is browser specific.
The markdown snippet
https://github.com/actions/cache/blob/704facf57e6136b1bc63b828d79edcd491f0ee84/README.md?plain=1#L5-L7
is parsed to HTML

Two other actions are available in addition to the primary cache action:

Restore action

Save action

where /actions/cache/blob/main/restore/README.md and /actions/cache/blob/main/base/README.md are both valid relative URLs, see for example MDN doc for  element.

@muzimuzhi Oh, that's weird. https://github.com/actions/cache?tab=readme-ov-file#cache-action wasn't working for me. I will close this PR then 🤷♂ .

I swear I had the same issue a few days ago and now it works just fine even though the README hasn't been touched. I don't get it 😆


Add pre-commit hook to remove cursors.

This PR adds a pre-commit hook specifically for *NIX systems to remove the cursor byte from all files under src/.
The reason why I chose python is because it is assumed that most *NIX systems already come with it pre-installed.

It does not rely on a Python dependency if the contributor doesn't want to use the actual hook. This is totally optional. I mean you need to install the hook after all with the appropriate hook.


skip and skip-glob are not enforced when using settings-path

Hi,
Version used: 4.3.15, not tested on other versions.
Setup:
$ tree -a
.
├── conf
│   └── .isort.cfg
├── file_glob_skip.py
└── file_to_be_skipped.py

1 directory, 3 files
$ cat conf/.isort.cfg
[isort]
skip =
    file_to_be_skipped.py
skip_glob =
    *glob_skip*
$ cat file_glob_skip.py
import os

print("Hello World")

import sys
$ cat file_to_be_skipped.py
import os

print("Hello World")

import sys

Files are not skipped when using --settings-path=conf/.isort.cfg:
$ isort --check-only --settings-path=conf/.isort.cfg
ERROR: /home/romain/Area51/isort_skip_bug/file_glob_skip.py Imports are incorrectly sorted.
ERROR: /home/romain/Area51/isort_skip_bug/file_to_be_skipped.py Imports are incorrectly sorted.

But works when using CLI options:
$ isort --check-only --skip file_to_be_skipped.py --skip-glob '*glob_skip*'
Skipped 2 files

The problem seems to have two causes:

check_skip is always set to False [1] which make SortImports not even trying any of the skip options [2] while the class use True as default for that argument [3]
Options defined in a settings-path file are not used [4] by iter_source_code() [5], the config dict will only contain options a local .isort.cfg and CLI options.

[1] https://github.com/timothycrosley/isort/blob/4.3.15/isort/main.py#L320
[2] https://github.com/timothycrosley/isort/blob/4.3.15/isort/isort.py#L98
[3] https://github.com/timothycrosley/isort/blob/4.3.15/isort/isort.py#L51
[4] https://github.com/timothycrosley/isort/blob/4.3.15/isort/main.py#L348-L349
[5] https://github.com/timothycrosley/isort/blob/4.3.15/isort/main.py#L353
A bisect give me 91ae94e477d066f133a889d13f3bd25363785258 as first bad commit.

Thanks for providing such a great detailed bug report for this issue!
This should be fixed in the just released 4.3.16 hotfix:

Thank you for the fix and the release!


Try to fix tests

close #11

Codecov Report
Patch and project coverage have no change.

Comparison is base (b4724ed) 87.37% compared to head (5f2e99b) 87.37%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage   87.37%   87.37%
=======================================
  Files           6        6
  Lines         198      198
=======================================
  Hits          173      173
  Misses         25       25

Flag
Coverage Δ

Linux
87.37% <ø> (ø)

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

Impacted Files
Coverage Δ

include/myproject/binary_exponentiation.h
100.00% <ø> (ø)

include/myproject/factorial.h
100.00% <ø> (ø)

include/myproject/fibonacci.h
100.00% <ø> (ø)

include/myproject/macros.h
56.00% <ø> (ø)

include/myproject/myproject_asserts.h
0.00% <ø> (ø)

include/myproject/undirected_graph.h
96.61% <ø> (ø)

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


missing Match Against for Full Text search

Hello heminei,
I am using your class. Very well crafted and no issues so far. Currently I need to peform a Full Text search, using standard PDO logic. Not sure if I can already do it, but MATCH AGAINST would be a good solution for your class:
SELECT MATCH (title) AGAINST ('$search' IN NATURAL LANGUAGE MODE) AS score
Besides this, I had to check your class to get_last_insert_id and get_query_with_parameters (debug). Maybe something for your docs ;)
Your piece of art (your class) works like a charme and very easy to understand. With most other classes I had trouble due to namespaces and dependencies.
Cheers

Hello,
Please check the new version and the new demo file: https://github.com/heminei/php-query-builder/blob/master/demo/fulltext-search.php

Hello Martin,
awesome support. Thank you so much for implementing my “request”.
It’s a top notch class, easy to implement and understand.
PS: I would link the full text search demo to the README.md @github, just to show visitors a complete list of features of this great extension.
Take care in these times. The light will shine bright very soon. 5:5
Birger
@.***
Von: Martin Bratvanov @.>
Gesendet: Dienstag, 6. Juni 2023 16:06
An: heminei/php-query-builder @.>
Cc: AppBuilder1984 @.>; Author @.>
Betreff: Re: [heminei/php-query-builder] missing Match Against for Full Text search (Issue #4)
Hello,
Please check the new version and the new demo file: https://github.com/heminei/php-query-builder/blob/master/demo/fulltext-search.php
—
Reply to this email directly, view it on GitHubhttps://github.com/heminei/php-query-builder/issues/4#issuecomment-1578833713, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5W3PPQ626DW4VI6SSLOY7LXJ42KXANCNFSM6AAAAAAYQMZFSM.
You are receiving this because you authored the thread.Message ID: @.***>


Svg text on azure functions

I'm building a small watermarking microservice on azure functions. I can't seem to get any svg text to render. I guess there is no fonts installed at all on the host os.
I have been trying to inline a font with base64, the svg works in the browser, but does not seem to use the font when running through sharp.
Example svg:
<svg height="40" width="220" xmlns="http://www.w3.org/2000/svg" version="1.1">
        <defs>
            <style>
            @font-face {
                font-family: 'zzz';
                font-style: 'normal';
                src: url("data:application/font-woff;charset=utf-8;base64,d09GRgABAAAAAGbMABIAAAAAuWgAAQAA.....") format('woff');
              }
              </style>
        </defs>
        <style><![CDATA[svg text{stroke:none}]]></style>
        <text x="20" y="30" font-size="35" fill="#fff" font-family="'zzz'" font-style="regular">test text</text>
</svg>

Please see https://gitlab.gnome.org/GNOME/librsvg/issues/153

any ideas as to how this could be accomplished through alternate means? doesnt have to be a specific font, just need to be able to actually output text.

Generic font families such as "serif" and "sans" might be OK.
librsvg uses fontconfig, which can be controlled via environment variables and config files - see https://www.freedesktop.org/software/fontconfig/fontconfig-user.html

neither serif nor sans worked. in the end, i could not get this to work.
I had to create a docker image and go that route instead. with docker, i could do a apt-get install fonts-roboto for example, and then the font would be in the system.
downside is, you can't use the consumption plan when using docker, instead you will have an app servie 24/7, so in the end it costs as much as hosting it as a regular website.

Perhaps you could ask at https://github.com/Azure/azure-functions-host about adding some basic fonts to the Azure Functions runtime environment.

I had the same problem with Edge Lambda. Solution was to package the fonts with the Lambda and then set the envvar programmatically (because Edge Lambdas cannot have envvars) process.env['FONTCONFIG_PATH'] = './fonts';.

I faced an issue where text was being rendered as empty boxes on a template in my Node.js application hosted as an Azure Web App. Here's how I fixed it:

I discovered that Azure uses a Dockerized environment to host Node.js applications. The issue occurred because fontconfig, a Linux-based tool that manages font discovery and rendering, was missing from the configuration.

I used SSH to access my Azure Web App and installed fontconfig. However, it was installed globally, and all the data was erased after every deployment. This happened because Azure Web Apps do not persist data stored outside their main directory. In my case, the persistent directory was /home.

To solve this, I created a file named install_fontconfig.sh in the /home directory, ensuring the file would persist after each deployment.

I added the following commands to the script to install fontconfig and the required fonts:

apt-get update

echo "Installing apt-utils"
apt-get install -y apt-utils

echo "Installing required fonts..."
apt-get install -y fontconfig fonts-roboto

echo "Font installation completed!"

In the entry point file of my Node.js application (index.js), which I used with nodemon (nodemon index.js), I added the following code:

const setupScriptPath = path.join(__dirname, '../../install_fontconfig.sh');

if (isUndefinedNullOrEmpty(process.env['SCRIPT_EXECUTED'])) {
  exec(`bash ${setupScriptPath}`, (error, stdout, stderr) => {
    if (error) {
      commonAnalytics.logEvent('BASH_ERROR', {
        message: error.message,
        path: setupScriptPath,
      });
      return;
    }
    if (stderr) {
      commonAnalytics.logEvent('BASH_WARNING', {
        message: stderr,
        path: setupScriptPath,
      });
    }

    commonAnalytics.logEvent('BASH_SUCCESS', {
      path: setupScriptPath,
      output: stdout,
    });

    process.env['SCRIPT_EXECUTED'] = 'true';
  });
}

With this setup, the script executed once when the application started, installing fontconfig in the persistent /home directory. After this, Sharp was able to correctly detect the fonts from the system and render the text as expected.
I believe the only thing you need for the script to work correctly is root permission, which I believe you will already have so it should work fine.


Fe: Spaces in description are messed up

the description I gave during the minting process is "om nom nom"

I think this should be fixed now.


xiasl: init at 1.1.67

Description of changes
Xiasl is a cross-platform DSDT & SSDT IDE.
Only Linux is supported by this derivation for now - additional patches to the build process and runtime executable searching are required for macOS. I recommend MaciASL on macOS for the time being.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ x Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 302104 run on x86_64-linux 1

1 package built:

xiasl


DO NOT MERGE YET: Adding SPARQL check to reference to obsolete classes

Fixes #13793

This seems to be taking too long

@dougli1sqrd - now we have an explicit verify command we don't need the perl hack as well?

Yeah that's right: https://github.com/geneontology/go-ontology/pull/14097/files#diff-22e910b7915a0c24f526851b8507813dR376
But looking at the pull request here, it looks like that merge never happened, or was re-written over?

ok, I rewrote obsolete-reference-violation.sparql to reduce its execution time as requested. Unfortunately, sometimes the order of the triple patterns in a query matters in Jena.


Correctly hydrating the server state in Pinia setup stores

Problem

We are almost done converting Vuex stores to Pinia (milestone). However, we are incorrectly re-initializing the store on the client side instead of reusing the server-side state, and this is causing a lot of errors.
Description

All of the stores are now converted to Pinia setup stores.
Final conversion surfaced a very important flaw in this conversion process. During the state hydration on the client, the Pinia store setup function is ran again as is. This means that instead of reusing the state passed from the server, we are re-creating the state with initial values. This causes numerous errors in the app logic.
For example, when you click on 'Load more' button on a server-rendered search page, the media fetch state page value is set to undefined, so we are re-fetching the same page that has already been fetched. Other bugs such as the audio search page with fewer than 20 results being unresponsive, and no change when you select an extension filter and decelect it, are also caused by the incorrect state on the client.
The solution I propose (and try out in the Provider store PR) is to add a custom function for initializing the state by setting it to the initial value on the server, and adding our own hydration solution on the client. Nuxt context is not injected inside the setup store setup function. However, it is available as part of the $nuxt property of the global window object.
const initialState = { searchType: ALL_MEDIA }

const initializeState = () => {
    // add `isClient` checks to make sure window is not undefined
    const serverState = window.$nuxt.context.pinia.state.search
    if (serverState) {
        // Making sure that the state is a simple object, not a proxy or a ref.
        return JSON.parse(JSON.stringify(serverState))
    } else {
        return initialState
    }
}

const searchStore = defineStore('search', () => {
    const state = reactive(initializeState())

    return { state }
})

This can only work if we can serialize and deserialize the state correctly. Here, the problem in the media store is with the current implementation of the fetchState, which is a composable that returns both simple properties, but also functions to change the fetchState. The functions cannot be stringified, and need to be filtered out when hydrating the state. We also cannot use a computed that would only return the inner simple FetchState object from this computed because Pinia treats computed refs as getters, and it only passes the state (i.e. the refs and reactives) from the server to client as part of the window.$nuxt.context value.
Instead, we can create the _fetchState as an inner composable that would handle state updates, and a fetchState ref that would be updated by a _fetchState watcher, and would be serialized by the server, and deserialized by the client to initialize client state correctly.
This conversion will be easier if the current large media store is split into separate stores: audio, image, allMedia, and singleMedia (for the image/audio detail pages), but that would make for a huge PR that would be difficult to review :(
Alternatives

Another to go back and refactor the stores to use options API. The options store uses a separate function for creating the store, and because of that does correctly handle hydration on the client side. It calls the state function on the server, but hydrates the server state values and makes them reactive on the client. There is even a special hydrate option that is only available for the options stores.
With this solution, we won't have to "fight the tool", and will be using the options it provides instead.
Additional context

The solution for store hydration is implemented in the Provider store PR: #1158.
I have also opened a discussion in the Pinia repository about the composition store state hydration, but it's still unanswered.
Implementation

[ ] 🙋 I would be interested in implementing this feature.

Another to go back and refactor the stores to use options API. The options store uses a separate function for creating the store, and because of that does correctly handle hydration on the client side. It calls the state function on the server, but hydrates the server state values and makes them reactive on the client. There is even a special hydrate option that is only available for the options stores.
With this solution, we won't have to "fight the tool", and will be using the options it provides instead.

I am personally very tempted by this solution, even though it means we'd have to do some significant refactoring and go back on our original decision.
Unfortunately the more we "fight the tool", as you said, the further we get away from the "standard/expected implementation" which, as we know, can be quite problematic with the Nuxt situation.
If other folks are strongly opposed to switching the store style (it makes me sad to think about but I really do think it would be the better option) then I like your approach with the initializeState function. It could be abstracted pretty easily as well if we just pass the store key and initial state as arguments to a generic initializeState function.
My concern, however, is that we'd still run into issues whenever we've defined individual state values as refs, instead of a single reactive state object.
On the other hand, it seems like the initializeState function could be implemented upstream as a helper. Like initializeSsrState or something in an additional ssr specific package. Did you happen to open a discussion or issue in Pinia about this by any chance?

I think there could be an abstraction that would initialize the state both when created using individual state reactive, and separate refs. The state object that we can get from window.$nuxt contains all of the data as an object, so we could simply iterate the keys/values, and create the state based on that. It would be better to standardize the state creation to use either single state OR a set of refs (I'd prefer state) should we select this approach.
Even though I feel really proud of myself for creating the initializeState solution, I do agree that using standard/expected implementation can save us a lot of headache in the future, and be much more maintainable.

I am going to go ahead and create issues to convert the stores. active-media store can stay a setup store because it does not use server state on the client.

[ ] nav store
[ ] search store
[ ] media store: split into media-results for individual mediaTypes, single-media for the media detail pages, and all-media for 'All Content' view.
[ ] related-media store
[ ] provider store


Cannot fund carrier accounts

I am unable to fund carrier accounts as we have in the past.   Is this available to the new API?
Thank you!

@FenceDad Can you share some more context around the issue you're having adding funds?  We may need to open you a ticket with our support team to dig in.

@AnneOReilly I think he means it is just not in the SDK. We turned on auto funding to get around it, but it is near the top of my list of endpoints to implement.

@brprigge, you are correct.  We can work around it by pushing to the API directly since it is a simple call.  Thank you for the quick response!


Message sending failure

The Company Communicator is failing to send a message to ~200k users (message status in the Company Communicator Author app attached).

Hi @manuel-faria,
Thank you for raising the query, can you please confirm on the version of the app used?


Issue

Info API down. Falling back to manual fetching...

package issue, try write to author of discord.py-self on github.

What do I use instead?

nothing, maybe fixed in new version. re-install packages from requirements.txt


Fix post install jobs golang path

This broke because of Golang 1.17 with the following error
package knative.dev/eventing-kafka/vendor/knative.dev/pkg/apiextensions/storageversion/cmd/migrate imports k8s.io/apiextensions-apiserver/pkg/client/clientset/clientset from implicitly required module; to add missing requirements, run:
	go get<EMAIL_ADDRESS>
This change is in-line with what we did to other repos.
Nightly is broken because of this.

/lgtm
/approve


Constant "Error fetching updates" notifications

Each time hyperterm fails to check for updates, it creates a system notification ("Error fetching updates"). It seems that hyperterm checks every 10-15 minutes or so, leading to the annoyance of many new system notifications.
In my case, it's likely due to the necessary ports being blocked at work, but there could be a number of other reasons why hyperterm might not be able to check for updates. Would it be better to have hyperterm fail silently when checking for updates?
Edit: Some sort of exponential backoff could be good for this, as well.

Or stop checking for updates after X failed attempts :)

I'm getting this as well. Looks like the autoupdater feed URL uses a .sh top-level domain. That is likely to be blocked in many work environments. Would it be possible to switch to a more common TLD?

Here's a screenshot of the error. If someone can direct me to the location of a log file, or something else that would help in debugging this, I'd be happy to help.

I'm also having this issue

I've got the same issue. It varies between "the request timed out," "the network connection was lost," and something like "could not locate bundle" (I didn't catch the exact message)

Getting a similar error...

@jcreamer898 That's the one I've got (or, rather, one of the three). Any idea what causes this @rauchg ? The developer console doesn't have any information besides a lot of repeated Cannot read property 'shell' of undefined errors

Possibly have them hosted on github (when signing works)?

This should be resolved shortly. We switched to a new builder mechanism that introduced a minor mismatch

Apologies 🙈

I have gotten a lot of different error messages. I think this screenshot includes them all. I received notifications for all of these (and more) within the past hour.

Looks like the latest release has resolved this, at least for me.

Me too

+1

Fixed


Correct a typo on the README file

Correct a typo and add an additional instruction to users using MacOS Sierra systems

Coverage increased (+0.02%) to 51.462% when pulling 2a73ffee3558a4b42d7720281895ffd209da0029 on bpineda:patch-1 into 991f3cac6c4ee4da4b4bc156bc86d9c9cd9eb87c on phpbrew:master.

Hey @bpineda,
Thanks for finding this as well!
I've already opened a PR resolving this for the English README as well as the Japanese README.
Additionally, there's a bit more to this particular correction: El Capitan is subject to this issue as well.

No problem, man. And now that you mention it, I could work on the README in Spanish.

It's conflicted.

Hi @bpineda any update of this PR? or I might have to close this PR.

Hello @bpineda , I'm closing this PR because every change in this PR has already been apllied to master through other PR or commits.  Thank you for your effort and concern any way.


meshConfig.accesLogFormat does not respect Yaml multiline parsing with Folded Style (no interior line breaks)

Bug Description
Consider the following log format configuration:
meshConfig:
  accessLogEncoding: TEXT
  accessLogFile: /dev/stdout
  accessLogFormat: >
    {
      "authority":"%REQ(:AUTHORITY)%",
      "bytes_received":"%BYTES_RECEIVED%",
      "bytes_sent":"%BYTES_SENT%",
      "connection_termination_details":"%CONNECTION_TERMINATION_DETAILS%",
      "downstream_local_address":"%DOWNSTREAM_LOCAL_ADDRESS%",
      "downstream_peer_cert_v_end":"%DOWNSTREAM_PEER_CERT_V_END%",
      "downstream_peer_cert_v_start":"%DOWNSTREAM_PEER_CERT_V_START%",
      "downstream_remote_address":"%DOWNSTREAM_REMOTE_ADDRESS%",
      "downstream_tls_cipher":"%DOWNSTREAM_TLS_CIPHER%",
      "downstream_tls_version":"%DOWNSTREAM_TLS_VERSION%",
      "duration":"%DURATION%",
      "hostname":"%HOSTNAME%",
      "istio_policy_status":"%DYNAMIC_METADATA(istio.mixer:status)%",
      "method":"%REQ(:METHOD)%",
      "path":"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%",
      "protocol":"%PROTOCOL%",
      "request_duration":"%REQUEST_DURATION%",
      "request_id":"%REQ(X-REQUEST-ID)%",
      "requested_server_name":"%REQUESTED_SERVER_NAME%",
      "response_code":"%RESPONSE_CODE%",
      "response_code_details":"%RESPONSE_CODE_DETAILS%",
      "response_duration":"%RESPONSE_DURATION%",
      "response_tx_duration":"%RESPONSE_TX_DURATION%",
      "response_flags":"%RESPONSE_FLAGS%",
      "route_name":"%ROUTE_NAME%",
      "start_time":"%START_TIME%",
      "trace_id":"%REQ(x-b3-traceid)%",
      "upstream_cluster":"%UPSTREAM_CLUSTER%",
      "upstream_host":"%UPSTREAM_HOST%",
      "upstream_local_address":"%UPSTREAM_LOCAL_ADDRESS%",
      "upstream_service_time":"%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%",
      "upstream_transport_failure_reason":"%UPSTREAM_TRANSPORT_FAILURE_REASON%",
      "user_agent":"%REQ(USER-AGENT)%",
      "x_forwarded_for":"%REQ(X-FORWARDED-FOR)%"
    }

According to the YAML specs (https://yaml.org/spec/1.2.2/#813-folded-style), this should result in interior line breaks being stripped out, so one has a valid and single line JSON for fluent-bit (or other logstashers) forwarding.
However, when this configuration is applied, the resulting YAML modifier > is replaced by |, causing new lines to be injected, breaking the log parsing.
meshConfig:
  accessLogEncoding: TEXT
  accessLogFile: /dev/stdout
  accessLogFormat: |
    {
      "authority":"%REQ(:AUTHORITY)%",
      "bytes_received":"%BYTES_RECEIVED%",
      "bytes_sent":"%BYTES_SENT%",
      "connection_termination_details":"%CONNECTION_TERMINATION_DETAILS%",
      "downstream_local_address":"%DOWNSTREAM_LOCAL_ADDRESS%",
      "downstream_peer_cert_v_end":"%DOWNSTREAM_PEER_CERT_V_END%",
      "downstream_peer_cert_v_start":"%DOWNSTREAM_PEER_CERT_V_START%",
      "downstream_remote_address":"%DOWNSTREAM_REMOTE_ADDRESS%",
      "downstream_tls_cipher":"%DOWNSTREAM_TLS_CIPHER%",
      "downstream_tls_version":"%DOWNSTREAM_TLS_VERSION%",
      "duration":"%DURATION%",
      "hostname":"%HOSTNAME%",
      "istio_policy_status":"%DYNAMIC_METADATA(istio.mixer:status)%",
      "method":"%REQ(:METHOD)%",
      "path":"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%",
      "protocol":"%PROTOCOL%",
      "request_duration":"%REQUEST_DURATION%",
      "request_id":"%REQ(X-REQUEST-ID)%",
      "requested_server_name":"%REQUESTED_SERVER_NAME%",
      "response_code":"%RESPONSE_CODE%",
      "response_code_details":"%RESPONSE_CODE_DETAILS%",
      "response_duration":"%RESPONSE_DURATION%",
      "response_tx_duration":"%RESPONSE_TX_DURATION%",
      "response_flags":"%RESPONSE_FLAGS%",
      "route_name":"%ROUTE_NAME%",
      "start_time":"%START_TIME%",
      "trace_id":"%REQ(x-b3-traceid)%",
      "upstream_cluster":"%UPSTREAM_CLUSTER%",
      "upstream_host":"%UPSTREAM_HOST%",
      "upstream_local_address":"%UPSTREAM_LOCAL_ADDRESS%",
      "upstream_service_time":"%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%",
      "upstream_transport_failure_reason":"%UPSTREAM_TRANSPORT_FAILURE_REASON%",
      "user_agent":"%REQ(USER-AGENT)%",
      "x_forwarded_for":"%REQ(X-FORWARDED-FOR)%"
    }

The work-around now is to collapse all of this into one line and use escape characters, but this is hard to read, maintain and error prone. Also, one needs to manually add a new line \n character at the end.
meshConfig:
  accessLogEncoding: TEXT
  accessLogFile: /dev/stdout
  accessLogFormat: "{ \"authority\":\"%REQ(:AUTHORITY)%\", \"bytes_received\":\"%BYTES_RECEIVED%\", \"bytes_sent\":\"%BYTES_SENT%\", \"connection_termination_details\":\"%CONNECTION_TERMINATION_DETAILS%\", \"downstream_local_address\":\"%DOWNSTREAM_LOCAL_ADDRESS%\", \"downstream_peer_cert_v_end\":\"%DOWNSTREAM_PEER_CERT_V_END%\", \"downstream_peer_cert_v_start\":\"%DOWNSTREAM_PEER_CERT_V_START%\", \"downstream_remote_address\":\"%DOWNSTREAM_REMOTE_ADDRESS%\", \"downstream_tls_cipher\":\"%DOWNSTREAM_TLS_CIPHER%\", \"downstream_tls_version\":\"%DOWNSTREAM_TLS_VERSION%\", \"duration\":\"%DURATION%\", \"hostname\":\"%HOSTNAME%\", \"istio_policy_status\":\"%DYNAMIC_METADATA(istio.mixer:status)%\", \"method\":\"%REQ(:METHOD)%\", \"path\":\"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%\", \"protocol\":\"%PROTOCOL%\", \"request_duration\":\"%REQUEST_DURATION%\", \"request_id\":\"%REQ(X-REQUEST-ID)%\", \"requested_server_name\":\"%REQUESTED_SERVER_NAME%\", \"response_code\":\"%RESPONSE_CODE%\", \"response_code_details\":\"%RESPONSE_CODE_DETAILS%\", \"response_duration\":\"%RESPONSE_DURATION%\", \"response_tx_duration\":\"%RESPONSE_TX_DURATION%\", \"response_flags\":\"%RESPONSE_FLAGS%\", \"route_name\":\"%ROUTE_NAME%\", \"start_time\":\"%START_TIME%\", \"trace_id\":\"%REQ(x-b3-traceid)%\", \"upstream_cluster\":\"%UPSTREAM_CLUSTER%\", \"upstream_host\":\"%UPSTREAM_HOST%\", \"upstream_local_address\":\"%UPSTREAM_LOCAL_ADDRESS%\", \"upstream_service_time\":\"%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%\", \"upstream_transport_failure_reason\":\"%UPSTREAM_TRANSPORT_FAILURE_REASON%\", \"user_agent\":\"%REQ(USER-AGENT)%\", \"x_forwarded_for\":\"%REQ(X-FORWARDED-FOR)%\" }\n"

Version
All

Additional Information
No response

However, when this configuration is applied, the resulting YAML modifier > is replaced by |, causing new lines to be injected, breaking the log parsing.

Any YAML modifications must be K8s doing this afaik.
IMO the fix here is to insert a newline if there isn't one present on Istiod side. Its never(?) relevant to not have a newline, and its annoying to have to add + easy to make mistakes. WDYT?

Hi @howardjohn , thanks for your response. I did a quick verification to see if K8s is able to handle this Yaml parsing nuance, and from the below result, I seem to believe it does.
# cat configmap-test.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: test-yaml
data:
  test1.properties: >
    here we should not
    see new lines being
    injected
  test2.properties: |
    here we should see
    new lines being
    injected

# kubectl apply -f configmap-test.yaml
configmap/test-yaml created

#  kubectl get cm test-yaml -o yaml
apiVersion: v1
data:
  test1.properties: |
    here we should not see new lines being injected
  test2.properties: |
    here we should see
    new lines being
    injected
kind: ConfigMap
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","data":{"test1.properties":"here we should not see new lines being injected\n","test2.properties":"here we should see\nnew lines being\ninjected\n"},"kind":"ConfigMap","metadata":{"annotations":{},"name":"test-yaml","namespace":"default"}}
  creationTimestamp: "2021-11-01T20:13:14Z"
  name: test-yaml
  namespace: default
  resourceVersion: "734501"
  uid: 2c43e118-a9c1-4061-8a51-d71734125671

Is it possible something goes wrong in the Yaml parsing in between the IstioOperator Object being applied and the Istio ConfigMap containing the result?

Is it possible something goes wrong in the Yaml parsing in between the IstioOperator Object being applied and the Istio ConfigMap containing the result?

Ah, that is plausible. Lots of marshalling an unmarshalling to get there..
What is the exact flow? Are you using the in cluster operator, istioctl install, etc?
Regardless of this i ithink we should still make the format code insert a newline. But we may need to do that and fix some other yaml thing in the operator

Hi John,
I use kubectl apply -f istiologconfig.yaml to apply my log configuration GitOps style.
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
metadata:
  name: istiologconfig
  namespace: istio-system
spec:
  meshConfig:
    accessLogEncoding: TEXT
    accessLogFile: /dev/stdout
    accessLogFormat: >
      my
      multiline
      stuff ..

As to the extra new line, this is indeed also an issue, but a separate one. Shall I create a dedicated issue, or is this report enough to cover both issues and trigger some yaml magic review?


Add ability to inject HttpClient instance

Add the ability to inject an HttpClient instance. This library is a no-go for my team without this capability.

Hi @goldsam, could you please provide some more information? This library is built using Flurl which provides a wrapper for HttpClient, and manages the HttpClient lifecycle, etc.
It would be a significant design change to move this project from Flurl to a standard HttpClient, so this issue is likely out of scope, unless Flurl has support to configure it with an existing HttpClient.

I understand. Why are you wrapping HttpClient this is the platform standard client. Preventing me from injecting my own instance flies in the face of well established conventions. Why did you choose to use an abstraction over an abstraction?

Hi @goldsam,
I see that you opened an issue on the Flurl project yesterday asking for some more information about the goals of Flurl. I see it has since been deleted, so hopefully you got a satisfactory answer.
As for why it is used in this project, as you can likely see this project was forked from an earlier project, and we took over maintenance of the fork in mid-2023, so I cannot really speak to why it was originally chosen, as Flurl has been a dependency for this project long before we started maintaining it.
With that said, as with many open-source projects we welcome contributions from the community, so, if you would like to be able to inject an existing HttpClient instance via the Factory interface you identified you are welcome to open a Pull Request. Please keep in mind when implementing this change should be backwards compatible with the existing implementation, i.e. it should be optional to inject an HttpClient and your change should not require users to manage their own HttpClient if they do not want to.
If you do open a PR please let me know so that it doesn't get missed,
Thanks.

I've found that it was easier to just NSwag to code generate a client from a generated Keycloak OpenAPI spec. This approach is easier to keep up to date and is considerably more flexible. Thanks though.


callback won't work and view doesn't close

I'm getting the error chromium: [INFO:CONSOLE(169)] "Scripts may close only the windows that were opened by them."

same here. have you found any solution?

same here! have you found any solution?

same here! have you found any solution?

I found the culprit.
Apple returns the redirect URL with one specific change.
The /handler was replacing into a /result which is it became false on the url.toString().contains(...) condition
Check my latest fork.


Improvements

First of all thank you for this great proof of concept and the video about the theme with shopware on youtube.
We are currently evaluating to switch to Shopware6 with our online Shops.
Internally we are mainly Laravel Developers and are working with the TALL (TailwindCSS, AlpineJS, Laravel, Laravel Livewire), so we would be thrilled if there is a tailwind Theme for Shopware 6. :)
We found a similar approach for magento2 with https://hyva.io/ which is very successful.
My question is: Will you expand the proof of concept here to a real theme? I think it has a lot of potential.
Currently we aren't that familar with the shopware 6 theming and will give it a try in the next weeks and maybe we can add a few components.
Best Regards
Christian

Hej Christian,
yes the approach is similar to hyva.io, but this here is open-source :wink:
The goal is to have a complete working theme. Every help is very welcome.
If you wanna check the current status you can build the theme from develop branch.
There is no deadline or roadmap. It is just a fun-/side-project.
The main work is to adapt most of the templates from bootstap to tailwindcss/alpine.js
At the moment the bootstap js is not removed this will be one of the lasts steps.
Greetings
Björn

Hi Björn,
thanks for your response. Sure first I will setup a dev shop for us and learn the first steps for theming with shopware 6.  But I will check it out. Thanks for your effort :)


pythonPackages.black: Move optional deps to passthru

Description of changes
All the optional dependencies for the black python package were moved to the passthru attribute set as recommended by the nixpkgs documentation in section <IP_ADDRESS>.2.
Advantages:
Users needing black without the extra features won't need to download/compile stuff they don't need.
black derivations would be compatible with more platforms since some of the optional dependencies (e.g. uvloop) have harsher restrictions on platforms than black does.
Disadvantages:
People expecting blackd to work will be surprised that they need to install the extra dependencies to get this working again.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Could you build the reverse dependencies to check they're not broken now due to missing deps?

Thanks!


Cannot see local/uncommited changes in Timeline anymore after March 30 2022 update

I have added one line into a python file and saved the file.
After saving a file, previously (prior to update in late March 2022?) Visual Studio Code created an "Uncommitted changes" item in the Timeline view (by default in the sidebar in the left). Clicking the item opened a view where the uncommitted changes could be compared. Currently such item is not created, but instead, a "File Saved" item is created which doesn't seem to show the changes properly.
(Looks like, in the current version of VSCode, a view similar to the previous "Uncommitted changes" can be still displayed with by navigating to Source Control and clicking the file in Source Control View, under the list of changed files.)
Image 1: The view previously opened after clicking "Uncommitted changes" item in the timeline.

However, this view cannot be displayed in the timeline anymore. Instead, a "File Saved" item is created in the Timeline (image 2) but clicking it does not reveal any changes (image 3):
Image 2: File Saved Pipeline

Image 3: Clicking the item opens a compare view. No changes highlighted.

I was expecting to see that one new line highlighted, similarly as in Image 1. Instead no changes are highlighted. However, the file name in the tab is yellow, so there are uncommitted changes.
Looking more into it, looks like clicking the "local changes" items in the timeline (such as File Saved and Undo/Redo) don't open a compare view that displays the changes done in that particular point, but compare the then version of the file with the current version of the file. So, I'm not sure if this is a bug or a feature, but it's not following the expected pattern in the timeline, where clicking a commit shows the changes introduced in that particular commit.
About VSCode:

Version: 1.66.0 (system setup)
Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5
Date: 2022-03-30T05:50:14.623Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22000

/assign @bpasero -@mjbvz

Intentional: https://github.com/microsoft/vscode/issues/145723


SSL is not working out of the box

Getting this error when I try to configure the update center to use SSL. I have changed the default update center in Jenkins to point to an internal update center. Any ideas?
Running Jenkins 2.5 on Ubuntu
javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
	at sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
	at sun.security.ssl.InputRecord.read(InputRecord.java:527)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
	at

How you exactly use it? If you want to use https, you need a frontend before juseppe - u can use nginx for this purposes

Thanks. I added Nginx and it seems to work now. Is this in the documentation anywhere?

This is standard approach to organize https on service without build-in support


Empty paragraphs messing up CSS numbering

Hello there! First of all thanks for making ContentTools -- it's pretty awesome.
I'm developing a personal project where I'd like my paragraphs to be numbered (I'm using CSS counters for that). Mostly everything works fine, except for an edge case where an empty paragraph is left when saving a document:
In editor view:

After saving:

I'm using the sample sandbox code and tried adding editor._emptyRegionsAllowed = false; to it. Here's how I'm initializing the editor:
window.onload = function() {
var FIXTURE_TOOLS, editor, req;
ContentTools.IMAGE_UPLOADER = cloudinaryImageUploader;
ContentTools.StylePalette.add([new ContentTools.Style('By-line', 'article__by-line', ['p']), new ContentTools.Style('Caption', 'article__caption', ['p']), new ContentTools.Style('Example', 'example', ['pre']), new ContentTools.Style('Example + Good', 'example--good', ['pre']), new ContentTools.Style('Example + Bad', 'example--bad', ['pre'])]);
editor = ContentTools.EditorApp.get();

editor.init('[data-editable], [data-fixture]', 'data-name');
editor._emptyRegionsAllowed = false;

Etc. Am I doing something wrong?
Thanks again!
Guilherme

Hi @guicapanema - that's an interesting one - could you send me a snapshot of the page HTML from the DOM/element inspector after the save when this glitch is visible.
Re. _emptyRegionsAllowed I don't believe setting this would help in this situation as it's to do with the whole region being empty not a single paragraph.

Hi @anthonyjb ! Thanks for answering and sorry for the delay.
This is what the HTML looks like:

    Conclusão

    Lorem ipsum dolor sit amet, consectetur adipiscing elit.

    Morbi aliquet leo sit amet nisl luctus facilisis sit amet sit amet eros.

And this is the result:

From what I see the problem is the empty
 tag is left in the DOM. It has the CSS's :before attached to it, which is what messes up the numbering. Not a huge deal, but should be an easy fix, right?

@guicapanema so you can remove that behaviour by changing the CSS of course however the default CSS uses an :after pseudo element for empty elements, see here: https://github.com/GetmeUK/ContentEdit/blob/master/src/styles/content-edit.scss#L164
So the before bit is confusing me a little bit.

Hi @anthonyjb . Actually, I didn't explain myself well. I added the :before element because I need paragraphs to be numbered, and that's where I'm putting my counters. In a normal situation (that is, with no empty  tags), that should work fine.
The main thing here is that I would like the editor to remove empty paragraphs before saving to the database. When I reported this, I was thinking no one would like empty s, but that was really shortsighted.
Perhaps adding an option?

@guicapanema ahh I see - misunderstood initially, this is definitely a bug, the editor should not be leaving those empty paragraphs in the DOM on save by default.

OK new release pushed resolving this issue (1.5.6)


fix or improve explanation for References and Semantics

closes #480
closes #481
closes #473
closes #479
added more invalid reference examples for all constraints effecting References
fix formatting

@j-blume: may you please also have a look at this PR? Thank you

@s-heppner Please check again whether it is ok now


Add "Ordinal" property

So, it would allow to export methods at desired ordinal.

seems dup of #8

seems dup of #8

Not duplicate.
#8 is to mimic ordinal counter to start from 1 instead of 0 (by default), and nothing more.
While this proposes to add a new property to DllExportAttribute class, which would allow to override the counter number.

initially it was a 'Ordinals should start from one (1), not zero (0)' with unclear description of what you trying to solve -_-
ok, suggestion to start from 1+ there, and to add as a common option here

you can check it with a2e9ba6


Implement Navbar Support

This PR implements the Navbar component and several required dependent components: <NavBar>, <NavItem>, <NavDropdown>, <NavDropdownItem>
This component requires JavaScript, so I implemented include_cdn_js(). I gave the inline version a shot, but it's remarkably difficult for JavaScript. I'm not yet familiar enough with trunk to let inline JavaScript sneak past it.

Wow...
First of all, thank you.  This is outstanding quality, even for open-source.
To be honest, I have since moved on from Yew to Svelte, as I got tired of the amount of boilerplate present in both React and Yew. I forgot to mark this repository as archived.
Although in line with open-source spirit, and seeing the work you put into this, I am happy you found the library useful, and wanted to contribute. Despite not using Yew anymore, I don't mind code-reviewing PRs. If you want to take over the project I also don't mind adding you as a Maintainer, or even transferring the project to your namespace. Just let me know if interested.
All 3 PR's look great, so will go ahead and merge. Thanks again!

To be honest, I have since moved on from Yew to Svelte, as I got tired of the amount of boilerplate present in both React and Yew. I forgot to mark this repository as archived.

What a coincidence - I'm moving from SvelteKit to Yew! 😆 I've become so fed up with using JavaScript and even TypeScript, though I know many enjoy them. I'm not yet sure that this will be a totally satisfying change for me as I do not yet have all of the components I'll need to rewrite my motivating project, but I am going to try.

First of all, thank you.  This is outstanding quality, even for open-source.

Thank you very much for your kind words.
If you were going to mark the repository as archived, I am happy to take it over. I intend to carry it a bit more forward to add several components I want to use; I am currently working on Modals. I think having more component libraries would help out Yew tremendously.
Completely taking over the repository appeals to me honestly, as I am a freelancer and it would be a useful feather in my cap for establishing my Rust credibility. If you were at all inclined to continue using this library I would answer otherwise.


docs: files directory update announcement

Looking for reviews. To merge at the same time as https://github.com/blue-build/template/pull/36#pullrequestreview-2185719665, rememeber to do an announcement on GitHub, Discord, and Mastodon.

Have to also update docs for modules to refer to files/ now.


Podman support?

Fedora, CentOS, and Red Hat Enterprise Linux have dropped Docker (Moby) and switched to Podman, which doesn't require a daemon. It does have API support (which is what we're using in cockpit-podman) We're specifically the new Podman 2.0 API, not the deprecated varlink API.
The new API has a podman-specific API and a Docker-compatible version.
Podman's API is documented at https://docs.podman.io/en/latest/_static/api.html and there's a simple overview @ https://www.redhat.com/sysadmin/podmans-new-rest-api

Additionally, Podman is used in SUSE distros (openSUSE Tumbleweed and Leap, and also SUSE Linux Enterprise). It's also made its way into Debian recently and should be in Ubuntu soon as well.

Supporting podman would be a very nice feature, but k3x does not interact with docker directly: all the heavy work is done by k3d. k3d is currently using the Docker API so, until k3d supports podman is some other way, this will not be possible. There is an open issue in the k3d repo about this though.

Cool, thanks!

https://k3d.io/v5.4.0/usage/advanced/podman/ suggests that this should be fairly easy to configure, but I cannot get it working as described with symlinks :( Any chance this issue can get a bump up in priority? :pray: :heart:


color field output

Hello
wordpress - 4.7
kirki - 2.3.7
I try to use kirki, but i have problem with color field. I can't get output for a element
My_theme_Kirki::add_field( 'my_config', array(
	'type'        => 'color',
	'settings'    => 'my_setting',
	'label'       => __( 'This is the label', 'My_theme' ),
	'section'     => 'my_section',
	'default'     => '#0088CC',
	'priority'    => 10,
	'alpha'       => true,
	'output' => array(
		array(
			'element' => 'a',
		),
	),
) );

`

Please take a look at the documentation for the output argument: https://aristath.github.io/kirki/docs/arguments/output.html
You should define a property in the array there.
colors can go as background-colors, border-colors, text-colors and a bunch of other things so you need to define what you want the control to do.
The typography control is a special case that doesn't require defining a property because it can only refer to text properties.


update release scripts for #195 bug fix

Updating release script to bring over feature #195 into release

Closing to use other release PR


Added the first edition of HDR wrapper

@Tharyn
Please try this :bow:
#147

Fantastic!
I'm very happy I found OpenCvSharp.

I download the branch and began some testing.
I found that this:
var cbd = CalibrateDebevec.Create();
ERROR: ArrayTypeMismatchException: Source array type cannot be assigned to destination array type.
(wrapper stelemref) object:stelemref (object,intptr,object)

Then I tried this from the samples:
var sr = SuperResolution.CreateBTVL1();
ERROR: ArrayTypeMismatchException: Source array type cannot be assigned to destination array type.
(wrapper stelemref) object:stelemref (object,intptr,object)

I then thought it might be that I am using OCS in Unity3D ran each of the samples in Visual Studio with no Unity in the process. Turns out something is wrong with them as well and it is not a Unity3D issue.
Check this out:
    // new BgSubtractorMOG();               ///      Breaks on Create()         Line 17: using (var mog = BackgroundSubtractorMOG.Create())
                // new BRISKSample();                   // WORKS
                // new ClaheSample();                   // WORKS
                // new ConnectedComponentsSample();     // WORKS
                // new DFT();                           // WORKS
                // new FaceDetection();                 // WORKS
                // new FASTSample();                    //       Breaks on  Cv2.FAST        Line 19: KeyPoint[] keypoints = Cv2.FAST(imgGray, 50, true);
                // new FlannSample();                   // WORKS
                // new FREAKSample();                   ///      Breaks on Create()         Line 22: FREAK freak = FREAK.Create();
                // new HistSample();                    ///      Runs, but Histogram is blank
                // new HOGSample();                     // WORKS
                // new HoughLinesSample();              // WORKS
                // new KAZESample();                    // WORKS
                // new MatOperations();                 // WORKS
                // new MatToBitmap();                   // WORKS
                // new MDS();                           // WORKS
                // new MSERSample();                    // WORKS
                // new NormalArrayOperations();         // WORKS
                 new PhotoMethods();                    // WORKS
                // new MergeSplitSample();              // WORKS
                // new MorphologySample();              // WORKS
                // new PixelAccess();                   // WORKS
                // new SeamlessClone();                 // WORKS
                // new SiftSurfSample();                ///      Breaks on Create()         Line 30: var sift = SIFT.Create();
                // new SolveEquation();                 // WORKS
                // new StarDetectorSample();            ///      Breaks on Create()         Line 17: StarDetector detector = StarDetector.Create(45);
                // new Stitching()                      // WORKS
                // new Subdiv2DSample();                // WORKS
                // new SuperResolutionSample();         ///      Breaks on Read()           Line 33: capture.Read(normalFrame);
                // new SVMSample();                     // WORKS
                // new VideoWriterSample();             ///      Breaks on Read()           Line 21: using (VideoWriter writer = new VideoWriter(OutVideoFile, -1, capture.Fps, dsize))
                //new VideoCaptureSample();             ///      Breaks on Read()           Line 16:   capture.Read(image); // same as cvQueryFrame

There is defiantly a pattern here. If we can get this sorted out I think I now have an understanding on how to start implementing the rest of the HDR functionality based on your example.
Again thank you for the attention and I'm happy to assist in any way that is useful.

I experimented with these errors for a few hours today. I know that the issue is in the arguments being sent to the native functions but can't seem to figure it out.
I'm not familiar enough with the wrapping of native functions to trouble shoot it :/

I'm starting to work on updating the samples. Th Read() breaks are from the 3.0 camera bug. I can fix those.
Not sure about the Create() breaks but I'll see if I can track it down.
The errors are consistent so I'm guessing its all the same stuff. I need to get them fixed before I can trouble shoot the HDR. I think something in the wrapper is broken.


corrected wording in command description

1. Why is this change necessary?
Wrong wording at command description
2. What does this change do, exactly?
Correct the wording
3. Describe each step to reproduce the issue or behaviour.
type bin/console
4. Please link to the relevant issues (if any).
5. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hey @buenosdiaz,
thanks for your contribution. :blue_heart: :tada:


TypeError: setInterval(...).unref is not a function

Environment details

OS: macOS 10.15
Node.js version: v10.16.3
npm version: 6.9.0
@google-cloud/firestore version: 2.4.0

Steps to reproduce
This problem occurs when running tests using Jest.
    TypeError: setInterval(...).unref is not a function

      at new SubchannelPool (node_modules/@grpc/grpc-js/build/src/subchannel-pool.js:55:36)
      at Object.<anonymous> (node_modules/@grpc/grpc-js/build/src/subchannel-pool.js:99:30)
      at Object.<anonymous> (node_modules/@grpc/grpc-js/build/src/channel.js:21:27)
      at Object.<anonymous> (node_modules/@grpc/grpc-js/build/src/index.js:22:19)
      at Object.<anonymous> (node_modules/google-gax/src/grpc.ts:36:1)
      at Object.<anonymous> (node_modules/google-gax/src/index.ts:32:1)
      at Object.<anonymous> (node_modules/@google-cloud/firestore/build/src/v1/firestore_client.js:16:13)
      at Object.<anonymous> (node_modules/@google-cloud/firestore/build/src/v1/index.js:15:25)
      at Function.get (node_modules/@google-cloud/firestore/build/src/index.js:1154:18)
      at ClientPool.Firestore._clientPool.pool_1.ClientPool [as clientFactory] (node_modules/@google-cloud/firestore/build/src/index.js:315:45)
      at ClientPool.acquire (node_modules/@google-cloud/firestore/build/src/pool.js:64:35)
      at ClientPool.run (node_modules/@google-cloud/firestore/build/src/pool.js:121:29)
      at Firestore.request (node_modules/@google-cloud/firestore/build/src/index.js:962:33)
      at WriteBatch.commit_ (node_modules/@google-cloud/firestore/build/src/write-batch.js:448:14)

Dependency
  "dependencies": {
  },
  "devDependencies": {
    "@firebase/testing": "^0.13.0",
    "@types/jest": "^24.0.18",
    "@types/node": "^12.7.4",
    "firebase-admin": "^8.6.0",
    "jest": "^24.8.0",
    "ts-jest": "^24.0.2",
    "tslint": "^5.19.0",
    "typescript": "^3.6.2"
  },
  "peerDependencies": {
    "firebase-admin": "^8.6.0"
  },
  "resolutions": {},
  "jest": {
    "transform": {
      "^.+\\.tsx?$": "ts-jest"
    },
    "testRegex": "(/__tests__/.*|(\\.|/)(test|spec))\\.(jsx?|tsx?)$",
    "moduleFileExtensions": [
      "ts",
      "tsx",
      "js",
      "jsx",
      "json",
      "node"
    ]
  }

import * as firebase from 'firebase-admin'

const secret = require("./secret.json")
firebase.initializeApp({
    credential: firebase.credential.cert(secret)
})

describe("Batch", () => {

	test("set test", async () => {
		const batch = firebase.firestore().batch()
		batch.set(firebase.firestore().collection("test").doc("doc"), {"a": "a"})
		await batch.commit()
	}, 10000)

})

Do test
jest

@1amageek I might be worth also logging an issue with Jest and referencing this issue,  setInterval(() => {}, 100).unref() is part of the Node.js runtime, and shouldn't be raising an exception.

@1amageek FYI take a look at this comment https://github.com/facebook/jest/issues/9033#issuecomment-541310639

The references issue suggests to use jest --env node to run the tests. If this does not work for you, please do let us know. In the meantime, I am closing this issue as it does not seem specific to this library. Please do let us know if there are any changes we need to make.


Postgres jsonb default is not quoted

Description
When creating a default for jsonb columns as an empty set '[]' it is not being generated with the quotes but simply square brackets [] causing a syntax error.
To Reproduce
Generate a changelog of a database with a jsonb column with default '[]'
Apply and update to an empty database.
Expected behavior
Column should be created with a default empty set.
Screenshots
Unexpected error running Liquibase: ERROR: syntax error at or near "["
Position: 442 [Failed SQL: (0) CREATE TABLE public.xyz (....JSONB DEFAULT [] NOT NULL...)

Additional context
Currently only ran into this error for jsonb columns.  Haven't tried it with json or text fields with a default value which would also need to be quoted.

Hi @jong82. Fellow PostgreSQL user here and I wanted to repro this. However...
If I have this changeset:
<changeSet id="3" author="aller">
    <addColumn tableName="department">
        <column name="extra" type="jsonb" defaultValue="[]"/>
    </addColumn>
</changeSet>
<changeSet id="4" author="aller">
    <createTable tableName="jsonb_test">
        <column name="extra" type="jsonb" defaultValue="[]"/>
    </createTable>
</changeSet>

it generates these SQL queries:
-- Changeset <snip>/db.changelog-master.xml::3::aller
ALTER TABLE public.department ADD extra JSONB DEFAULT '[]';

INSERT INTO public.databasechangelog <snip>;

-- Changeset <snip>/db.changelog-master.xml::4::aller
CREATE TABLE public.jsonb_test (extra JSONB DEFAULT '[]');

Which then applies successfully. Were you doing something different, or are you using an older version of LiquiBase maybe?
LiquiBase 3.8.8.

Hi @jong82 Does the option provided by @MaxAller work for you?

Seems like not actual anymore. Checked this with Liquibase 4.3.1. Used the same changeset as @MaxAller proposed. The table was generated with default empty sets: https://monosnap.com/file/diQZdxn4XZSh9XoejgAjXq2B7jigrz
After that I succesfully inserted a new row and updated existing row: https://monosnap.com/file/i0ErDtaXQht3lNadDyccim2Fk9w068

This is still happening in version Liquibase Community 4.6.2 by Liquibase

Hi @satbir121 Can you be a little more specific in your comment when you say this is still happening?
I just tried this with 4.6.2 , the same one as mentioned in maxaller's comment and it worked for me.
<changeSet id="4" author="aller">
    <createTable tableName="jsonb_test">
        <column name="extra" type="jsonb" defaultValue="[]"/>
    </createTable>
</changeSet>

Can you provide a test case that fails so that it can be fixed?

Using Liquibase version 4.28.0
Having the same issue with the same reproduction steps. I create a changelog for a PostgreSQL database schema and then attempt to update another database. The generated SQL does not have single quotes and I get the error:
liquibase.exception.DatabaseException: ERROR: syntax error at or near "["


BETA: Applied Accessibility: Improve Accessibility of Audio Content with the audio Element, not detecting closing  tag.

Applied Accessibility: Improve Accessibility of Audio Content with the audio Element

https://beta.freecodecamp.org/en/challenges/applied-accessibility/improve-accessibility-of-audio-content-with-the-audio-element
Issue Description

I tried to complete the task at hand. I believe it is done correctly, but it is saying that I still require a closing audio tag. You can see from the image below that I do have one in there and it is still not passing.
Browser Information

Note that this was performed in Chrome.

Browser Name, Version: Chrome, latest version
Operating System: Windows 10
Mobile, Desktop, or Tablet: Desktop

Your Code

Real Coding Ninjas

A sound clip of Zersiax's screen reader in action.

  <audio controls>
    <source src="https://s3.amazonaws.com/freecodecamp/screen-reader.mp3" type="audio/mpeg" />    </audio>

Screenshot

I also have this issue: receiving error message "cannot read property 'length' of null" and failing checks despite closing <audio> tag being in appropriate place.

Browser Information

Browser Name, Version: Vivaldi 1.13.1008.44
Operating System: Windows 10
Mobile, Desktop, or Tablet: Desktop

Isolated the error locally. I'll be opening a PR/fix later today.

(Real Coding Ninjas)Audio closing tag still not detected!!!!

SAME! It is not being detected.

Real Coding Ninjas

A sound clip of Zersiax's screen reader in action.

``

Real Coding Ninjas

A sound clip of Zersiax's screen reader in action.

``

`

Real Coding Ninjas

A sound clip of Zersiax's screen reader in action.

`

still not fixed

Ran into this same issue tonight. For everyone still having trouble, do not include an id attribute in your audio tag. It seemed to accept my answer after I removed the id attribute completely.
    <audio controls>
      <source src="https://s3.amazonaws.com/freecodecamp/screen-reader.mp3" type="audio/mpeg" />
    </audio>


Updated balance-of-with-max to add weight

Updated balance-of-with-max strategy to add an optional weight
Changes proposed in this pull request:

added weight as an option to multiply token total by
example weight set to 1

@ChaituVR as suggested I have updated this strategy to include weight rather than adding a new strategy. Thanks.


Show rough ETA text beside loading spinner

Description of new feature
Improve the communication re. query progress.

[x] Continue to use a spinner to indicate progress.  A progress bar is too much right now.
[ ] Add some text in the import progress dialog, something like:  "It will take a minute or so."

Motivation for new feature
Users say:  Is the app broken?  I've seen too many spinners before and they just go forever and the app doesn't work.  I don't trust the spinner.
Answer this for the user:  How long do I have to wait?

This is currently in the UI:

Closing


Add -important- to css class to maintain spacing

Add '!important' to '.manuscript-manager-template-columns' class to shift mmt columns down to prevent UI overlap.

related to https://www.pivotaltracker.com/story/show/86665314  [RW]

:+1: [RW]


Add conda to install instructions

Add Conda instructions as primary installation mechanism

Although the tests are failing, I'd be happy to merge this. @rhattersley - any reason to hold back while the (unrelated) tests are failing?

Looks like another natural earth data location issue! The data is missing off the github master source, however it is there under the v2.0 tag release.  We had a similar issue earlier last year when they changed the location of their data on their site.  This broke changed iris to use the updated location and fall-back to its github source if necessary, if I remember correctly.

I removed some markup and fixed line lengths
I rebased in passing in the hope that this was now suitable to merge

Thanks @marqh

Grrrr :angry: ... I forgot this had already been done in #1503. Merge conflicts ahoy!

I'll have a go at a merging 1.7.x onto master unless anyone else is keen.

Thanks @esc24, but it's OK ... I'm already wrestling with it. :expressionless:

Phew.

See #1520.


Avoid triggering long filename bug in Netatalk

Netatalk 2.2.x has a bug where after converting a long filename into the 31 chars max on HFS file systems, leads to a afpd crash everytime you subsequently move that file into a subfolder in the AFP share.
I want to introduce a workaround in the download_afp() method to shorten a long file name before it hits the Pi file system.

This should fix it https://github.com/akuker/RASCSI/pull/592

Reopening this to revert, since the underlying bug has been fixed in Netatalk.


Certificate expired: paolo_at_codesake_dot_com.pem

Trying to install the paolo_at_codesake_dot_com.pem, but it looks to be expired.
Removed the old certificate and added the new one, but that also seems expired.
$ gem cert --list
/CN=paolo/DC=codesake/DC=com

$ gem cert --remove ''
Removed '/CN=paolo/DC=codesake/DC=com'

$ gem cert --list

$ gem cert --add <(curl -Ls https://raw.githubusercontent.com/thesp0nge/dawn/master/certs/paolo_at_codesake_dot_com.pem)
Added '/CN=paolo/DC=codesake/DC=com'

$ gem install dawnscanner -P MediumSecurity
ERROR:  While executing gem ... (Gem::Security::Exception)
    certificate /CN=paolo/DC=codesake/DC=com not valid after 2015-01-27 17:25:01 UTC

Wow, this is huge.
I'll working on that.
Thanks
Paolo

Well, it's an easy fix, although I was a bit surprised that nobody reported it yet.
You probably already know this: Set reminders for certificate expiration dates, so you receive a notification to renew them before they expire.
I also wrote a small script that automatically finds certificates and checks the expiration dates for all the repositories and servers I manage.
Both saved me a lot of troubles of the years ;-)
Let me know if you need any help.

Since nobody reported me, it means... no one installed the gem since Jan 27 and no reports :-(
Thanks

New version 1.3.0 signed with the new key.
I close the issue, thanks again Gawin.

:+1:


sensor not created because of missing UUID and multiple sensor use

System Health details
System Information

version
core-2024.11.2

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.4

os_name
Linux

os_version
6.6.31-haos-raspi

arch
aarch64

timezone
Europe/Vienna

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

HACS Data
ok

GitHub API Calls Remaining
5000

Installed Version
2.0.1

Stage
running

Available Repositories
1461

Downloaded Repositories
38

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 13.2

update_channel
stable

supervisor_version
supervisor-2024.11.2

agent_version
1.6.0

docker_version
27.2.0

disk_total
116.8 GB

disk_used
40.7 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization

board
rpi4-64

supervisor_api
ok

version_api
ok

installed_addons
File editor (5.8.0), Terminal & SSH (9.15.0), AdGuard Home (5.1.5), Node-RED (18.1.1), Home Assistant Google Drive Backup (0.112.1), Studio Code Server (5.17.3), Mosquitto broker (6.4.1), OpenThread Border Router (2.12.0), Zigbee2MQTT (1.41.0-1), Zigbee2MQTT (1.41.0-1)

Dashboards

dashboards
7

resources
22

views
48

mode
storage

Recorder

oldest_recorder_run
8. November 2024 um 20:34

current_recorder_run
16. November 2024 um 21:34

estimated_db_size
12659.57 MiB

database_engine
sqlite

database_version
3.45.3

Checklist

[X] I have read the FAQ to see if there is a known solution to my problem.
[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
When adding a new sensor (existing sensor by a device) and you have added this sensor already in another powercalc-sensor, there is an entry created, but it fails to add additional sensors eg. for the use in an energymeter. so you get an configuration entry without additional sensors:

There is no hint for the error and the user is left in the dark what to do. it is stated in the logs:
2024-11-17 11:36:20.902 ERROR (MainThread) [custom_components.powercalc.sensor] sensor.energy_log_current_power_consumption_32306: **This entity has already configured a power sensor. When you want to configure it twice make sure to give it a unique_id**
solutions could be:

ask the user for an unique id
inform the user of a sensor already in use and
-- ask the user if the system should create one or the process should be aborted
-- generate a UUID automatically in the background
no info for the user, just generate a UUID in the background

i would definitly prefer an automatic generation one or the other way so the user does not have to deal with coding ...
Reproduction steps

set up a sensor with a power-sensor of an existing entity
try to set up another sensor with the same power-sensor of an existing entity

Debug logs
2024-11-17 11:36:20.902 ERROR (MainThread) [custom_components.powercalc.sensor] sensor.energy_log_current_power_consumption_32306: This entity has already configured a power sensor. When you want to configure it twice make sure to give it a unique_id
2024-11-17 11:36:49.564 ERROR (MainThread) [custom_components.powercalc.sensor] sensor.energy_log_current_power_consumption_32306_2: This entity has already configured a power sensor. When you want to configure it twice make sure to give it a unique_id

Diagnostics dump or YAML config
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2024.11.2",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.12.4",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Vienna",
"os_name": "Linux",
"os_version": "6.6.31-haos-raspi",
"supervisor": "2024.11.2",
"host_os": "Home Assistant OS 13.2",
"docker_version": "27.2.0",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"powercalc": {
"documentation": "https://docs.powercalc.nl",
"version": "v1.15.4",
"requirements": [
"numpy>=1.21.1"
]
},
"hacs": {
"documentation": "https://hacs.xyz/docs/configuration/start",
"version": "2.0.1",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"midea_dehumidifier_lan": {
"documentation": "https://github.com/nbogojevic/homeassistant-midea-air-appliances-lan/blob/main/README.md",
"version": "0.9.4",
"requirements": [
"midea-beautiful-air==0.10.5"
]
},
"waste_collection_schedule": {
"documentation": "https://github.com/mampfes/hacs_waste_collection_schedule#readme",
"version": "2.4.0",
"requirements": [
"icalendar",
"recurring_ical_events",
"icalevents>=0.1.26,!=0.1.28",
"beautifulsoup4",
"lxml",
"pycryptodome"
]
}
},
"integration_manifest": {
"after_dependencies": [
"integration",
"utility_meter"
],
"codeowners": [
"bramstroker"
],
"config_flow": true,
"dependencies": [
"light",
"group",
"template",
"select",
"utility_meter"
],
"documentation": "https://docs.powercalc.nl",
"domain": "powercalc",
"iot_class": "calculated",
"issue_tracker": "https://github.com/bramstroker/homeassistant-powercalc/issues",
"name": "Powercalc",
"requirements": [
"numpy>=1.21.1"
],
"version": "v1.15.4",
"is_built_in": false,
"overwrites_built_in": false
},
"setup_times": {
"null": {
"setup": 3.5852293679490685
},
"01JAE3KA1K1PZ14FQYWKT0WFRS": {
"wait_import_platforms": -0.0002492018975317478,
"config_entry_setup": 0.02400808222591877
},
"01JAF7N2YC4D6Y11EFJ69PMY1V": {
"config_entry_setup": 0.01846133079379797
},
"01JAF7PC7HWDC28ATQFZ3E12AW": {
"config_entry_setup": 0.013555796816945076
},
"01JCV4RT42S0988XFR9PFZDGJ4": {
"config_entry_setup": 0.017215249128639698
},
"01JCKS35MYP4ZSHGB66GRPQVVF": {
"config_entry_setup": 0.21734145190566778
},
"01JB71BYHEFZG9GZ6EN810ANTC": {
"config_entry_setup": 0.21940632490441203
},
"01JCKTFAAVJ4KCY8045HNKGKSX": {
"config_entry_setup": 0.2141138301230967
},
"01JCKTKRQMED7WFF3YX71S56MP": {
"config_entry_setup": 0.15739877382293344
},
"01JCKTP4CT0EMTM20W53CZSTJT": {
"config_entry_setup": 0.10215092776343226
}
},
"data": {
"entry": {
"created_at": "2024-11-17T16:30:59.769854+00:00",
"data": {
"name": "15 WP energyconsumption",
"create_utility_meters": true,
"entity_id": "sensor.energy_log_current_power_consumption_32306",
"device": "0341dbb7c2e8bc1c6a11e32799a1cdda",
"utility_meter_types": [
"daily",
"weekly",
"monthly",
"yearly"
],
"utility_meter_tariffs": [],
"utility_meter_net_consumption": false,
"utility_meter_offset": 0.0,
"sensor_type": "real_power"
},
"discovery_keys": {},
"disabled_by": null,
"domain": "powercalc",
"entry_id": "01JCXFD65S69N0VWHNRBAQ4AS7",
"minor_version": 1,
"modified_at": "2024-11-17T16:30:59.769868+00:00",
"options": {},
"pref_disable_new_entities": false,
"pref_disable_polling": false,
"source": "user",
"title": "15 WP energyconsumption",
"unique_id": null,
"version": 4
}
}
}

Thanks for raising this issue.
I gave it a thought but I didn't see any reason why I wouldn't just generate a UUID for every config flow the user does.
Also removed unique id field from the dialog as well.
Implemented with #2708.
Will release new beta later today. Would be nice if you can give it a test run.

lookimng good - sensor was generated and the utility-meters are counting as far as i can see ... 👍

Thanks for checking


Add VR addresses for WhosWho

Thinking more, I don't think anyone will know what this is anyway even if I merge it referencing whoswho.


Add a blog for March

$subject

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Show Album Artist instead of Track Artist

Looks like the artist information is getting pulled in from the first artist on a track, when I think that pulling the info in from the album artist would make more sense for most use-cases.
In these screenshots, the album is "The College Dropout" by Kanye West, but since the track "Slow Jamz" has Twista listed as the first artist, SpotMenu displays his name as the artist.

Good idea, I'll fix this

Fixed it. Please test it. Slow Jamz is the only song unavailable from that album in my country... 😓

Wow, that's unfortunate (and a strange coincidence)! I'll test when I get home from work (in around 4-5 hours).