Metafields are not available in the Checkout Editor for the Order Status Page

Please list the package(s) involved in the issue, and include the version you are using
    "@shopify/app": "3.50.2",
    "@shopify/checkout-ui-extensions-react": "0.27.3",
    "@shopify/cli": "3.50.2",

Describe the bug
The app metafields should be available in the Shopify Checkout Editor for the Order Status Page but they are not.

Steps to reproduce the behavior:

Create a simple checkout_ui_extension extension using the useAppMetafields() hook like the example below.

# extensions/order-status-extension/shopify.ui.extension.toml
type = "checkout_ui_extension"
name = "OSP Example"

extension_points = [
  'Checkout::ThankYou::Dynamic::Render',
  'Checkout::OrderStatus::Dynamic::Render',
]

[[metafields]]
namespace = "example"
key = "example_key"

[capabilities]
network_access = true

# extensions/order-status-extension/src/index.tsx
import {
  Text,
  render,
  useAppMetafields,
} from '@shopify/checkout-ui-extensions-react';

const App = () => {
  const metafields = useAppMetafields();
  console.log('metafields', metafields);
  return <Text>Hello 👋🏼</Text>;
};

render('Checkout::ThankYou::Dynamic::Render', () => <App />);
render('Checkout::OrderStatus::Dynamic::Render', () => <App />);

create a metafield in your store using the Shopify API
add the extension to your thank you page and your order status page
go thought checkout and in the console that the metafields show up in the console for both pages
go to the Shopify Checkout Editor, see the metafields show up in the thank you page, but not in the order status page 🐞

Expected behavior
The app metafields should be available in the Shopify Checkout Editor for the Order Status Page -- as they are for the Thank you page and during checkout fopr both pages -- but they are not available.

Screenshots

Thank you page
During checkout, working as expected:

In the checkout editor, working as expected:

Order Status Page
During checkout, working as expected:

In the checkout editor, metafields should be available but they are not 💥 :

Additional context

I noticed there were new versions of @shopify/app and @shopify/cli so I updated it, tested again and got the same results.
    "@shopify/app": "3.51.0",
    "@shopify/checkout-ui-extensions-react": "0.27.3",
    "@shopify/cli": "3.51.0",

Hi @lucasprag, thanks for the very detailed issue report! Our team has identified the issue internally with the new order-status page, and we'll look into resolving this week. Once fixed, you won't need to update any dependency on your app or extension. Apologies for the interruption.

I am experiencing the same issue as @rajmasha - I am using the hook useAppMetafields which returns what I need on the thank you page, but is then empty on the order status page. This has been the case for me since November.

Thanks for the context @alexdover! I was able to reproduce the issue and noticed app metafields missing for some of the metafields type. I will report back once our team has a fix.

@alxclark That is great, thank you for letting me know.

@alexdover  do you fond any solution for this  i am also facing same issue .
I want to show the banner when  someone purchase as company but its not working
import React from "react";
import {
Banner,
reactExtension,
usePurchasingCompany,
} from "@shopify/ui-extensions-react/checkout";
export default reactExtension("purchase.checkout.block.render", () => );
export function App() {
const purchasingCompany = usePurchasingCompany();
if (purchasingCompany) {
return (
Thank you for purchasing as a company!
);
} else {
return null;

}
}

Hi @lihaokx - apologies for confusing this issue, usePurchasingCompany works for me.
I have just been and tested the metafields and I am afraid that I am still not seeing the metafields on the order status page, either in the checkout editor or on the order status page itself. I can see the metafields on the thank you page though.

I then tried a few different combinations and I think it is the use of a hyphen in the metafield namespace or key which doesn't work on the order status page.

Thanks for you updating.
Hmm. This is interesting. I will try to reproduce on our side. I will keep you posted.

Hi @chienit3bk

Order status page on checkout editor, I can see all the metafields I have defined, but on real order status page, see that some metafields not work.

I think we have resolved this issue. Not sure if it is a separated issue. Would you mind to provide a link to your dev store? Ideally, more details of the code and ui.extension.toml will be appreciated. Thank you

Hey, I have a similar issue. Is it possible to retrieve the value of customer type metafields within the checkout? I've attempted it, but it seems to only work with product metafields.

Hey, I have a similar issue. Is it possible to retrieve the value of customer type metafields within the checkout? I've attempted it, but it seems to only work with product metafields.

Hi @Lynthius , it seems like a separate issue. Would you like to provide more details of the issue and create a new ticket for it? Than you for your efforts.
you can retrieve these metafields on customer account UI extension(including order status page).

you can retrieve these metafields on customer account UI extension(including order status page).

@lihaokx this screenshot seems to imply that accessing shop metafields is possible in customer account extensions, but I'm finding that I'm unable to access them (despite accessing the same metafield in checkout UI extensions, and verifying via direct GraphQL calls to the storefront API that the metafield is present. I opened #1887 about this a couple of weeks ago and as yet haven't received any input on it – I wonder if it's the same issue that @Lynthius is facing, or a separate issue. Thanks in advance for your input 🙇

@andrewpye you can check my issue here: #1904

@kirillplatonov the useAppMetafields hook should be available to use on thank you page targets. Can you share what target you are using and the API version?

I tested it again and you're right. useAppMetafields seems to be working in target purchase.thank-you.block.render. The extension seems to be loaded twice, on the first load useAppMetafields returns empty array, but on the second load we get data. Not sure if it's intentional. For now, we'll just ignore the first load when metafields are not available:

As for API calls. I'm testing with v2024-04. I see that examples slightly changed today in documentation: https://shopify.dev/docs/api/checkout-ui-extensions/2024-04/apis/storefront-api
I tried new examples and they both seems to work well on Order status page (target customer-account.order-status.block.render) but fail with errors on Thank you page (target purchase.thank-you.block.render).

Queries I'm using:
const {query} = useApi();

useEffect(() => {
  query(
    `query {
      shop {
        name
      }
    }`,
  )
    .then(({data, _errors}) => console.log('query1', data))
    .catch(console.error);
}, [query]);

useEffect(() => {
  const query = {
    query: `query {
      shop {
        id
      }
    }`
  };

  const apiVersion = '2024-04';

  fetch(
    `${shop.storefrontUrl}api/${apiVersion}/graphql.json`,
    {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
      },
      body: JSON.stringify(query),
    },
  )
    .then((response) => response.json())
    .then(({data, _errors}) => console.log('query2', data))
    .catch(console.error);
}, [shop]);


Konflux update test-component-pac-vzgioa

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-vzgioa-on-pull-request has successfully validated your commit.

Namespace: build-e2e-gjby-tenant
PipelineRun: test-component-pac-vzgioa-on-pull-request-cp7sj

Task Statuses:

StatusDurationName

✅ Succeeded
5 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
25 seconds
build-container

✅ Succeeded
6 seconds
deprecated-base-image-check

✅ Succeeded
17 seconds
ecosystem-cert-preflight-checks

✅ Succeeded
9 seconds
clamav-scan

✅ Succeeded
8 seconds
apply-tags

✅ Succeeded
6 seconds
sbom-json-check

❌ Failed
8 seconds
clair-scan

✅ Succeeded
6 seconds
sast-snyk-check

✅ Succeeded
12 seconds
show-summary

✅ Succeeded
11 seconds
show-sbom

Failure snippet:
task clair-scan has the status "Failed":
Inspecting raw image manifest quay.io/redhat-appstudio-qe/build-e2e-gjby-tenant/build-suite-test-application-yhgs/test-component-pac-vzgioa@sha256:aecd9cd4043e113b46819f9fd07f8d5429630b7e31e422a8f63529a225a89a09.
time="2024-07-12T16:25:58Z" level=fatal msg="Error parsing image name \"docker://quay.io/redhat-appstudio-qe/build-e2e-gjby-tenant/build-suite-test-application-yhgs/test-component-pac-vzgioa@sha256:aecd9cd4043e113b46819f9fd07f8d5429630b7e31e422a8f63529a225a89a09\": reading manifest sha256:aecd9cd4043e113b46819f9fd07f8d5429630b7e31e422a8f63529a225a89a09 in quay.io/redhat-appstudio-qe/build-e2e-gjby-tenant/build-suite-test-application-yhgs/test-component-pac-vzgioa: manifest unknown"
The raw image inspect command failed


macos interop_to_prod tests failing on master

Failing on all build starting from
https://source.cloud.google.com/results/invocations/f393279c-9735-4c50-89dd-bcef1757a4fc/targets/github%2Fgrpc/tests
I1014 22:14:44.826924000<PHONE_NUMBER>28896 client.cc:101]                Testing these cases: jwt_token_creds
E1014 22:14:44.829825000<PHONE_NUMBER>28896 check_gcp_environment_no_op.cc:28] Platforms other than Linux and Windows are not supported
E1014 22:14:44.942963000<PHONE_NUMBER>28896 interop_client.cc:292]        assertion failed: username.find(response.username()) != grpc::string::npos

This started with merging https://github.com/grpc/grpc/pull/16841 - looks like the interop client is trying to grab the compute engine credentials (by reaching out to the GCE metadata server), which makes no sense on macos workers as they are not (and cannot) run in GCE.

Tests have been fixed starting from https://source.cloud.google.com/results/invocations/ae8000c9-b47a-44fe-87b2-02997fa5be81/targets (a while ago).


fix: source=sc4s:unknown

PatternDB and Application parser sources will set defaults

:tada: This PR is included in version 1.46.2-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.46.2-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[FeatureRequest] Obfuscate folder names

Feature Description / 功能描述
An option so hidden folders also have obfuscated names.
Reason / 理由
The name of the folders can give away the content of the folder.
Suggest Solution / 实现方案
Same as the current obfuscating file names system but for folders

Amarok does obfuscate the names of the folders - except for the outermost folder.
We keep the name of the outermost folder fixed to prevent clutter in the storage.

Thanks for clarifying! I'm closing the issue.


Make jax.ensure_compile_time_eval correctly exposed as a public API

This function was added as a public API (#7987) but py.type static
checkers do not recognize it as a public API because of the alias name.
jax.eval_context exists only for backward compatibility, so the
correct import would be to import ensure_compile_time_eval directly
from jax._src.core.

Thank you for the expert fix!


batch normalize

Wow excellent work! Thanks for sharing~
Just a quick question: is there any reason why you don't use the batch_normalization in tf.layers(https://www.tensorflow.org/api_docs/python/tf/layers/batch_normalization)?
I'll be glad if you reply me~ thank you!

If you look at this url, when you use tf.layers.batch_normalization, you have to define update_ops
However, there were the following issues.

There was a problem that the learning was not good(the accuracy was low).
I personally like simple code. In that case, I wrote the code in a way that I would not add it because I do not think it would be well understood by other users.
It seemed like others did not know anything about control_dependencies or get_collection

So I used batch_norm in contrib
If you do updates_collections = None, the code is much simpler and easier to understand.
Also, the performance has been increased, and if you gave None, it's the same as doing control_dependencies above.
thank you

Oh wow! Many thanks for your detailed explanations!
You are so friendly~
I'm surprised that the performance will be affected!
Thanks for your sharing anyway.
BTW,
for the Global_Average_Pooling
I use tf.reduce_mean(input_tensor=x, axis=[1, 2], keep_dims=True)
What do you think~

Oh good idea.
Also, using reduce_mean is global_average_pooling.


Prop width(value:0) will be treated as a Unitless number in future versions of React

This line of code in notifications is causing a warning in Chrome dev tools concerning how it's going to be handled in future versions of React.
Warning: a `div` tag (owner: `Notification`) was passed a numeric string value for CSS property `width` (value: `0`) which will be treated as a unitless number in a future version of React.

Notification is deprecated. Please use Alert and Toast. Closing.


Change the color of UI

Codecov Report

Merging #273 into master will increase coverage by 0.03%.
The diff coverage is 0.00%.

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


Create new location param type

When we template out our AST and related code, we have a couple of different kinds of parameters that can be added onto nodes. Those include:

node - another node
node? - an optional node
node[] - a list of nodes
token - a token
token? - an optional token
token[] - a list of tokens
string - a string of characters

For the most part, this information is enough. However, there are times when it is redundant. For example, the DefinedNode node has a token for its keyword on it that is always going to be defined?.
Instead, we should create a location parameter that only stores the location in source. That way we'll save a bit on the overall memory that both the AST and serialization require. The location parameter should be its own struct that just stores two offsets into the source. Once we have that parameter in place, we should replace parameters in the existing tree that are constant to take advantage of this work. Finally, we should reorder the nodes so that the location parameters are always at the end, so that consumers of the serialization don't have to worry about them and can skip past them.

[ ] Create a new location parameter type
[ ] Replace tokens that are constant in the tree with the new parameter type
[ ] Move those tokens to the end of the list of child nodes

I wonder a bit if we need a location type and whether it's useful to move those at the end of child nodes. I'm thinking we might not need to serialize tokens at all for Ruby interpreters/for the semantics AST.

I guess in any case for Ruby interpreters we probably want the start and end offset for every node (or almost every node to the point of better be every for consistency). That's already there and stored efficiently:
https://github.com/Shopify/yarp/blob/b9dd811e76d81c77760f2d50f224abf543a640f5/bin/templates/java/org/yarp/Nodes.java.erb#L16-L17

For Tokens in general I think we don't need those for Ruby interpreters. So my thought was we have a mode where tokens simply don't get serialized at all. We just have a the start/end offset for each node, and then the existing fields/child nodes to find the rest of the information. As an example for an integer literal node, we'd use either the start/end offset which anyway is the same as the token, or there would be a string field or an integer field. For a call node we probably don't need much besides flags (e.g. for &., fcall, etc), method name and children nodes. We might an extra offset or a way to know where the . is for error_highlight purposes. Do you think that approach makes sense or you think we should use something else?

To clarify, no objection to have a location type, which e.g. could be the same as yp_location_t and notably every node has a location (https://github.com/Shopify/yarp/pull/84#discussion_r1009680907).
More about whether we need to serialize tokens at all or not.

As an example for an integer literal node, we'd use either the start/end offset which anyway is the same as the token, or there would be a string field or an integer field.

Although that wouldn't work for a complex literal node (e.g., 123i), where we'd want the location without the i, or a field with 123 (as string or integer).

Maybe let's chat tomorrow/this week to sync on this?

Maybe let's chat tomorrow/this week to sync on this?

Yeah for sure. I think it would make sense even to drop some tokens for CRuby as well.

It seems for Ruby 3.2 we are required for all/most nodes to be aware of start/end so we can underline things.   So I think all Node will have two those fields and should not require another type as it just adds memory.  An object instance in Java has overhead whereas that overhead is already paid in Node if we just use them as fields.
I think this previous paragraph applies that we do not want some specifier of location type in the stream but just want nodes to have start/end offsets.
It makes sense to me as @eregon says to elide data when the offset can reference it.  It means reading from two arrays but we already are leveraging the source so that seems like a reasonable continuation of that.
The example @eregon gave is thought-provoking.  If there was a notion of an enum then Integer = IntegerLiteral|ImaginaryLiteral... (maybe even ImaginaryLiteral(is-a: Integer). You want the node to be one of these things and to know it is an integer but from a AST building exercise you really care about whether it is imaginary or something else.  Implementations already know imaginary numbers are integers so serialization does not need to convey this as information. syntax type analysis tools might but I am not sure how broad the scope of yarp is.

Ignore my Integer enum thing. If we care about things like base on Integer literals we can just make more Node types or IntegerLiteral and IntegerBaseLiteral where we just know one needs to look at the last digit for base used.

@eregon there are still a few places where you're going to need the token. For example, in CallNode the operator that is used to make the call is a token, and you'll need to delineate between . and &.. That said, we could make that into a SafeCallNode if we wanted.

3i is ImaginaryNode, 3r is RationalNode, 3ri is ImaginaryNode.

I'm going to close this issue, as I've added the location param to a couple of places already and it appears to be working/simplifying which is nice.


support main files

When using NPM/Yarn, in the package.json you can have the main entry. This now checks for that field, checks if the file exists and uses that as a start command if all else fails.

Cool, found a little caveat in has_file - it doesn't work for paths like src/*, so I'm going to work on adding that in this PR.

Alright, I merged in. You need to approve the CI to run I think.


Adding another Exec property to .desktop file even if previously specified

First of all, thanks for this package. It's very useful.
One thing I noticed is adding Exec property without checking if it already exists in .desktop file.
It would be better to check if desktop file has Exec or TryExec property before adding it.
In my case I wanted to provide that by myself because I need it with %u at the end.

Hi @jakub-stefaniak happy to hear the package helps you 🤗.
Please can you provide more context on your use case (like why will you like add "%u")?
So that we can maybe try and make more generic because I fear adding an Exec property might break the package current functioning.

I wanted to provide %u at the end of the Exec property, so I can run the app with arguments. It's useful when you're handling custom url schemes. I pass the url called from browser as a parameter to flutter app

Here's specification what field codes can be passed with exec key
https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s07.html

I wanted to provide %u at the end of the Exec property, so I can run the app with arguments. It's useful when you're handling custom url schemes. I pass the url called from browser as a parameter to flutter app

Wow this is interesting 😲.
Please can I have a demo of it in action when you are done with your implementation?

Actually, I can't show it in the project that I am currently working on, but after work I can show you simple example of it in action :)

Yep sound good thanks 🙂

Please I will also want you to update the Readme per your changes if you have the time.

Sure, will do


A sensor to report webcam usage

Several Reddit users want a sensor to show if their webcam or mic is being used.
Link to comments

I have found a possible solution using OpenCV. It tries to grab an image from the webcam. If that succeeds, the webcam is not in use. If it fails, webcam is in use. A drawback is that every time it tries to grab an image, the webcam activity light turns on for a second.

I have found a possible solution using OpenCV. It tries to grab an image from the webcam. If that succeeds, the webcam is not in use. If it fails, webcam is in use. A drawback is that every time it tries to grab an image, the webcam activity light turns on for a second.

I have found a possible solution using OpenCV. It tries to grab an image from the webcam. If that succeeds, the webcam is not in use. If it fails, webcam is in use. A drawback is that every time it tries to grab an image, the webcam activity light turns on for a second.

I have found a possible solution using OpenCV. It tries to grab an image from the webcam. If that succeeds, the webcam is not in use. If it fails, webcam is in use. A drawback is that every time it tries to grab an image, the webcam activity light turns on for a second.

The solution I mentioned earlier is not something I'm happy with and I came up with another workaround:
A sensor that returns true if a window with a configured name is found, and false if not. This could be used to check for windows with names like Microsoft Teams, Jitsi or Google Meet. It's not perfect but I think it is a more versatile alternative to the ActiveWindow sensor.
I might also still release the solution I'm not happy with as it may be useful to some people.

The solution I mentioned earlier is not something I'm happy with and I came up with another workaround:
A sensor that returns true if a window with a configured name is found, and false if not. This could be used to check for windows with names like Microsoft Teams, Jitsi or Google Meet. It's not perfect but I think it is a more versatile alternative to the ActiveWindow sensor.
I might also still release the solution I'm not happy with as it may be useful to some people.

I was informed about a collection of registry keys that could be used to determine if the webcam or microphone are in use. See here. Weirdly enough these keys don't appear on my system. I'll have another look at this soon.

I was informed about a collection of registry keys that could be used to determine if the webcam or microphone are in use. See here. Weirdly enough these keys don't appear on my system. I'll have another look at this soon.

Both webcam and microphone sensors have been implemented and will be in the next release.

Both webcam and microphone sensors have been implemented and will be in the next release.


[Forwardport] 2.4: Update types and add GRB test

Forwardport: https://github.com/rancher/rancher/pull/24145

lgtm


random: sys_csrand_get backend for TEST_RANDOM_GENERATOR

When non-random number generation is allowed via
TEST_RANDOM_GENERATOR, enable an implementation for sys_csrand_get
that stubs out to sys_rand_get. This enables libraries that request
CS random numbers to be tested in CI, even if the results are not CS in
that context.
The documentation for TEST_RANDOM_GENERATOR is explicit enough about
the dangers of enabling this in production.

Rebased on v3.7.0

Is this for direct usage of sys_csrand_get()? FYI, non-CS entropy source has just been added as a possibility for psa_generate_random(): #76408 Don't know if that covers it.

I would say that this PR introduces an alternative solution to the one proposed in #76408. Once this PR will be merged there will be 2 ways to select non-CS-secure random sources: either through MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG_ALLOW_NON_CSPRNG or through CONFIG_TEST_CSPRNG_GENERATOR. They are not conflicting with each other, just acting at different "levels".

Is this for direct usage of sys_csrand_get()? FYI, non-CS entropy source has just been added as a possibility for psa_generate_random(): #76408 Don't know if that covers it.

I would say that this PR introduces an alternative solution to the one proposed in #76408. Once this PR will be merged there will be 2 ways to select non-CS-secure random sources: either through MBEDTLS_PSA_CRYPTO_EXTERNAL_RNG_ALLOW_NON_CSPRNG or through CONFIG_TEST_CSPRNG_GENERATOR. They are not conflicting with each other, just acting at different "levels".

Correct. Maybe I was not explicit enough, what I was asking with my question is whether it's really for directly calling sys_csrand_get(), or if it was to provide a non-CS option to psa_generate_random(). Because the latter has been taken care of with your PR that recently got merged, and maybe it fulfilled what @JordanYates needed.
And actually, it seems that if this PR is merged, then it could also achieve what https://github.com/zephyrproject-rtos/zephyr/pull/76408 did for psa_generate_random() (at a lower level). But the other PR is merged already. :man_shrugging:

@ceolin could you please have a look?


fix: text message not shown when no data is available

Description
Added a default message on the Certificate Credentials page to inform users when no certificate data is available.
Why
To display a default message when no certificate data is available.
Issue
#1319
Checklist

[X] I have followed the contributing guidelines
[X] I have performed a self-review of my own code
[X] I have successfully tested my changes locally

This PR include changes as mentioned in the comments #1319. Let me know if you’d like any more changes.


Setup a style to Code exemple

We have to set up a specific style for code blocks on posts.

The code Syntax on posts is working but the code needs refactoring.


Rainloop not use the php tmp directory ("upload_tmp_dir" config value) but "/tmp" on file upload

RainLoop version, browser, OS:
Rainloop <IP_ADDRESS>, Chrome latest, mac os 10.11.6
Server os: Debian 8.4
Apache version: Apache/2.4.10 (Debian)
php : PHP 5.6.29-0+deb8u1 via php5-fpm module
Expected behavior and actual behavior:
The server have the tmp directory value  set to /var/www/mail.mysite.tld/php_tmp, correctly set and correctly work (tested with a simple upload script on the mail.mysite.tld vhosts, it work), but when i try to upload files on mail response, all y get is a "temporary file missing" and a error on my log. Rainloop try to access to /tmp, but why if php use a other temporary directory?
If if modify my config to allow access to /tmp, it correctly work, but it's not the intended behavior, rainloop should use the tmp directory indicated on the php configuration ( ini_get('upload_tmp_dir') )
Logs or screenshots:
[Wed Feb 08 10:55:35.379206 2017] [:error] [pid 22938] [client <IP_ADDRESS>:57531] FastCGI: server "/usr/lib/cgi-bin/php5-fcgi-mail.mysite.tld" stderr: PHP message: PHP Warning:  Unknown: open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/var/www/mail.mysite.tld/public_html:/var/www/mail.mysite.tld/php_tmp:/var/www/mail.mysite.tld/php_session

Interesting, but RainLoop don't do anything special with this configuration.

Exactly, I think the problem comes from this: rainloop should use the value of the php configuration for temporary files, instead of directly using the /tmp from linux. I think the problem comes from this, I checked my configuration by consciousness and everything is OK, no reference to /tmp , That's why I started to think that the little bug came from rainloop and made the issue.
But it is true that it is strange, a normal file upload does not need to know the temporary folder, it retrieves it alone from the config normally, in php.

Exactly, I think the problem comes from this: rainloop should use the value of the php configuration for temporary files, instead of directly using the /tmp from linux. I think the problem comes from this, I checked my configuration by consciousness and everything is OK, no reference to /tmp , That's why I started to think that the little bug came from rainloop and made the issue.
But it is true that it is strange, a normal file upload does not need to know the temporary folder, it retrieves it alone from the config normally, in php.

has this ever been solved? we have the same issue and no clue how to fix it so far

Exactly, I think the problem comes from this: rainloop should use the value of the php configuration for temporary files, instead of directly using the /tmp from linux. I think the problem comes from this, I checked my configuration by consciousness and everything is OK, no reference to /tmp , That's why I started to think that the little bug came from rainloop and made the issue.
But it is true that it is strange, a normal file upload does not need to know the temporary folder, it retrieves it alone from the config normally, in php.

has this ever been solved? we have the same issue and no clue how to fix it so far

Exactly, I think the problem comes from this: rainloop should use the value of the php configuration for temporary files, instead of directly using the /tmp from linux. I think the problem comes from this, I checked my configuration by consciousness and everything is OK, no reference to /tmp , That's why I started to think that the little bug came from rainloop and made the issue.
But it is true that it is strange, a normal file upload does not need to know the temporary folder, it retrieves it alone from the config normally, in php.

has this ever been solved? we have the same issue and no clue how to fix it so far

for anyone looking for how to solve this: setting "upload_tmp_dir = /tmp" in the php.ini file fixed it.

Exactly, I think the problem comes from this: rainloop should use the value of the php configuration for temporary files, instead of directly using the /tmp from linux. I think the problem comes from this, I checked my configuration by consciousness and everything is OK, no reference to /tmp , That's why I started to think that the little bug came from rainloop and made the issue.
But it is true that it is strange, a normal file upload does not need to know the temporary folder, it retrieves it alone from the config normally, in php.

has this ever been solved? we have the same issue and no clue how to fix it so far

for anyone looking for how to solve this: setting "upload_tmp_dir = /tmp" in the php.ini file fixed it.


dropping field onto e.g. text value

for text value, this appears to set the value to the name of the field instead of the appropriate values. it would be helpful to have an example of this working so i can adapt it to work for signals as well.

Fixed with https://github.com/vega/lyra/commit/fbf2d40b69a6f2beb9a263c7cd361e72dbb3a4f1 and https://github.com/vega/lyra/commit/391e60c6d50d902d2d445146360b61cad6e4e500


Remove unused Sinon.JS

This saves time and bandwidth during each install, which will make builds go faster.
Before
added 1496 packages

After
added 1492 packages

To verify

Check out this branch
rm -rf node_modules
npm install
npm test

Thanks


What are the implications of the use of unsafe in this project? [question]

I'm new to rust.
I'm working on making a game and implementing my own ECS. I've recently come across this project and it looks awesome. My concern is that I don't understand the implications of the code around the uses of unsafe.
I'm worried this will lead to issues or non-idiomatic usage of the language. That said this project looks awesome and I'm most just curious as to the response as I know unsafe is often required to do things.

Biggest use of unsafe in specs are the underlying component storages.
Unsafe is used there because specs uses different datastructures in a sparse way: Entity is an index or key into the storage and it has or doesn't have certain component at particular moment of time.
This means that there are gaps in the datastructure that contain uninitialized memory which means that accessing the storage isn't safe without ensuring that the index/key actually has a value.
To ensure that there are actually value in the datastructure, a bitset is used which has bit set in entitys index if it has that component. When you iterate/join over component storages these bitsets are iterated/merged and components corresponding set bits are retrieved. When getting component for certain entity it's liveness is checked from Allocator which is responsible for creating/recycling removed entity ids and the bitset is checked that the entity actually has component.
Other use of unsafe is parallel joining which uses unsafe DistinctStorage to determine if backing storage is allowed to parallel join over.

When you use unsafe in a Rust library the idea is almost always to provide a safe wrapper around it, so it should be quite idiomatic. If you want to use this library, make sure to check out the book here. For more questions you can always as on our Gitter channel.

Thanks for the thoughtful responses!


Update table styles for universal listings

Update listing table styles for the new universal listing designs (https://github.com/wagtail/wagtail/discussions/10446).

Make the 'more' button on page listings into a '...' icon (that doesn't disappear on hover)
Move all buttons other than 'Edit' into the More menu
Move buttons to the right of title, rather than below
Adjust cell alignments to be top-aligned as standard
Add folder icon for pages with children

I've also updated the pre-commit hooks - for some reason, the older version of stylelint fails on my machine with a JS syntax error.

Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

@thibaudcolas Have removed the linter update commit (now opened as #10928) and rebased.


i wnat work on ongoing complaints page

i want to work on ongoing complaints page,app tilte is wrong and there should be withdraw complints button on detailed complaint page click on it sholud remove that complaints as by misktake if user dagging left should get redo option.

i want to work on ongoing complaints page,app tilte is wrong and there should be withdraw complints button on detailed complaint page click on it sholud remove that complaints as by misktake if user dagging left should get redo option.

You can work on it, but make sure it'll be also reflected in firebase

can you assign this to me?

ok

What's the progress till now?

@Jiggy9 i have added button but i am unable to build logic to delete it from firebase

@Jiggy9 i have added button but i am unable to build logic to delete it from firebase

It's fine, you did good, whoever send me PR with complete work, I'll merge it :)


Chrome Safari Browser is work only when chrome tab set as default otherwise getting error. how to solve this problem please help.

[x] I have read the Get Started - Installation section
[x] I have read and done the Get Started - Setup Android section
[x] I have read and done the Get Started - Setup iOS section
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version

Plugin version

Android version

iOS version

Xcode version

Device information:
Description
Expected behavior:
Current behavior:
Steps to reproduce

This
Than that
Then

Images
Stacktrace/Logcat

any options to solve this issue.


⚠ ClamAV has degraded performance

In 5844a75, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 74 ms

Resolved: ClamAV performance has improved in 8e116f6.


trimmed text conect of copy to clipboard

fixed whitespaces on copytoclipboard check it out

METRIC
VALUE

NEW SECURITY HOTSPOTS
0

NEW BUGS
0

NEW CODE SMELLS
0

NEW VULNERABILITIES
0

https://sonarqube.cuahsi-workstation.com:9000/dashboard?id=hydroshare-4223


composite track of sequence and block - without overlapping

Hi there,
I've been looking at this example, where the tracks are stacked, within a row (https://codepen.io/bioinsilico/pen/WNrXROM?editors=0010).

I was wondering, if this also possible with a composite of block and sequence? So that the sequence is displayed in the stacked blocks?

Here is the/a solution:
https://codepen.io/tschaka1904/pen/ZEorRPZ?editors=0010


Support for publishing a directory containing multiple csv files with same schema as a single layer

Hi,
Is it possible to publish a directory containing multiple csv files with exactly the same schema as a single layer?
We have a directory in which a CSV file gets added daily with exactly the same schema. Instead of combining it every time into a single large CSV file everyday, is it possible to configure the CSV provider in a way that it picks up all CSV files in that directory (or based on a file naming pattern) and output that as a single layer?

 This is not supported in the current version, but this is technically possible. The only caveat is that the file-loading order may not be guaranteed. A proper sorting must be done at the FeatureServer request or the client side.

What can be done is to sort the file list by alphabet or by modified time before reading them. Even we can open the sorting configuration. So that you can have a relatively stable data loading order. But again, each sorting mechanism has its own edge cases and that's why the order is not guaranteed.

I have added the code to support loading multiple CSV files for a single source. You can specify a glob pattern in the new path property of the source configuration (see example). You can test this feature with the latest version v3.2.0.


Expose setHistories and setHistoryIndex

It would be nice to be able to reset the history so that Puck rerenders with the change. My use case is that I have a clear history button which wipes localStorage/our DB-saved history and I want Puck to also reset fresh with no history. There's currently no way to do that because setHistories() isn't exposed. I can only set initial and then hard refresh the page.
It's worth noting that even though my setup is causing Puck to rerender, it isn't remounted, so even though initialHistory is updated, the underlying histories aren't.

Closed with https://github.com/measuredco/puck/pull/525


Currencies with three or zero fraction digits

Most arabic currencies do not have two, but three fractional digits.
And japanese Yen, south korean Won and some other currencies do not have fractions at all - only whole numbers.
See https://docs.adyen.com/development-resources/currency-codes

As far as I understand it, this is already supported.
However, you are not allowed to set fixed values in the NumberFormmater for "minimumFractionDigits" and "maximumFractionDigits".


Update spring-cloud-config.adoc

Add some detail around using --data-urlencode correctly & using the -s option to silence curl stats.

@dmikusa-pivotal Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@dmikusa-pivotal Thank you for signing the Contributor License Agreement!


Dialog "Add Implementation Artifact" does not set artifactType in API Request

When I successively add multiple Implementation Artifacts to a NodeTypeImplementation, the GUI sets as the default Type for the next Implementation Artifact the Type of the previous one. However, it does not add this value in the HTTP POST request. This leads to an error, and the creation of the Implementation Artifact fails.
Screenshot of the GUI:

Expected Body of the POST request:
{
    artifactType: "{http://docs.oasis-open.org/tosca/ns/2011/12/ToscaBaseTypes}ScriptArtifact",
    artifactTemplateName: "Test_stop-w1-wip1",
    artifactName: "Test_stop",
    autoCreateArtifactTemplate: "true",
    artifactTemplateNamespace: "http://www.example.org/tosca/artifacttemplates",
    interfaceName: "http://opentosca.org/interfaces/lifecycle",
    operationName: "stop",
    javaPackage: ""

}

Actual Body of the POST request:
{
    artifactType: "",
    artifactTemplateName: "Test_stop-w1-wip1",
    artifactName: "Test_stop",
    autoCreateArtifactTemplate: "true",
    artifactTemplateNamespace: "http://www.example.org/tosca/artifacttemplates",
    interfaceName: "http://opentosca.org/interfaces/lifecycle",
    operationName: "stop",
    javaPackage: ""

}

Fixed in https://github.com/eclipse/winery/pull/608


Screen resizing doesn't update screen.height/screen.width

Currently, when resizing the terminal/console window, the Screen doesn't update its width/height.
def demo(screen):
    while True:
        if screen.width < 80 or screen.height < 24:
            if screen.has_resized():
                # just checking:
                print('needs resizing') # doesn't get called if screen is already > 80 x 24
                print(screen.width)     # doesn't change
                print(screen.height)    # doesn't change
            message = 'Resize window to at least 80(w)x24(h)'
            screen.print_at(message, screen.width//2 - len(message)//2, screen.height //2 -3)

        else:
            if screen.has_resized():
                # just checking:
                print('size OK')        # doesn't get called if screen is < 80 x 24
                print(screen.width)     # doesn't change
                print(screen.height)    # doesn't change
            screen.print_at('Resized!', 0, 0)

        screen.refresh()

Screen.wrapper(demo)

As you will see in all of the samples, you can handle resizing by creating a new Screen object.  The bars demo (https://github.com/peterbrittain/asciimatics/blob/master/samples/bars.py) in particular shows how to handle resizing for a desired size.
I get that this isn't ideal, but the knock-on impact on the other objects that need to be resized and re-positioned means that you effectively go through the whole initialization sequence again.  I have been thinking about changing this, but it will radically change the implementation and so will almost certainly not be back compatible.  See https://github.com/peterbrittain/asciimatics/issues/24.

I've updated the docs (see https://github.com/peterbrittain/asciimatics/commit/bb6ce87f58b75ecaa44f568108ef55b90ea34dce) to try to address this confusion.
Am assuming that this covers it.  Please let me know if there was anything else that could help clarify it further.

This way cannot be used with
screen.print_at(...)
screen.refresh()

screen.refresh() does not have argument stop_on_resize

@lduczmal If you are not using the Screen.play() method you have full control of when things happen in your application and you can just call Screen.has_resized() to see if things have changed whenever you like.

Thank you for you answer.
Problem is that Screen.has_resized() seems to do not work... I create such simple script which open new terminal windows and shows current screen dimensions, some changing value and info whether screen dimensions was changed. Maybe I make something wrong, but printed dimensions will not change when I change terminal window size during script is running. One note: I run it on Windows 10 and on Python downloaded from www.python.org/downloads
from asciimatics.screen import Screen
from asciimatics.exceptions import ResizeScreenError
import time

screen_changes = []
screen_changes.append("start")

def demo(screen):
    x = 0
    while True:
        x += 1
        mytext = "[Screen height: {0}, width: {1}] changing value: {2}".format(screen.height,screen.width,x)
        mytext2 = "Screen was resized? {0}".format(Screen.has_resized(screen))
        screen_changes.append(Screen.has_resized(screen))
        screen.print_at(mytext, 1, 1, colour=7, bg=0)
        if Screen.has_resized(screen):
            screen.print_at(mytext2, 1, 2, colour=1, bg=0)
        else:
            screen.print_at(mytext2, 1, 2, colour=2, bg=0)
        ev = screen.get_key()
        if ev in (ord('Q'), ord('q')):
            return
        screen.refresh()
        time.sleep(0.5)

Screen.wrapper(demo)
print(screen_changes)
sys.exit(0)

Best regards

@lduczmal That's because has_resized is not a static method, you just need to call screen.has_resized().  Note that this only guarantees to check if there has been a resize since the last time you checked.  For Windows, it will continue to tell you on each call, but that's not a cross-platform guarantee and so you should fix your code.  What should work is this:
    mytext2 = "Screen was resized? {0}".format(screen.has_resized())
    screen_changes.append(mytext2)

@peterbrittain Hi, thank you - now it works! almost... ;-) When I'm resizing terminal window during script run it sometimes returns to previous dimensions...
My code:
from asciimatics.screen import Screen
from asciimatics.exceptions import ResizeScreenError
import time
import sys

screen_changes = []
screen_changes.append("start")
quit_script = False
x = 0
def demo(screen):
    global quit_script
    global x
    while True:
        x += 1
        mytext = "[Screen height: {0}, width: {1}] changing value: {2}".format(screen.height,screen.width,x)
        #screen_changes.append(screen.dimensions)
        screen.print_at(mytext, 1, 1, colour=7, bg=0)
        if screen.has_resized():
            return
        ev = screen.get_key()
        if ev in (ord('Q'), ord('q')):
            quit_script = True
            return
        screen.refresh()
        time.sleep(0.5)

k = 0
while not quit_script:
    Screen.wrapper(demo)
    time.sleep(0.5)

I have one more question: function demo in code above has the only one argument screen. What about situation if I would like to add others arguments to this function and how use wrapper to pass additional params to function demo

Quick answers are that I think you're hitting a race condition in the Windows Console where you are delaying any processing for half a second.  Simply removing this delay prevents the issue.  And look at the samples for how to use the arguments parameter on wrapper to pass in other parameters to thde demo function.
Finally, could I ask that you please continue any questions in Gitter instead of in this closed issue?  For example, go to: https://gitter.im/asciimatics/Lobby


Early printk implementation, some kconfig cleanup

First cut at some SOF submissions.
One is a printk hook to use in lieu of the log backend.  Honestly, I hate the Zephyr logging system, it's async by default, will drop rapid logging by default, it's a huge chunk of code, and it's not avaialble in early boot.  Basically it's everything I don't want when debugging platform code.
Also it was easier to add MP/cache-safety to this rig than it was to the more complicated log backend.  See comments.
The other commit is pure cleanup, just there so I can test MP features without SMP turned on.

The SMP cleanup commit can be submitted to Zephyr's master.
Not sure about the early console. IIRC, some DMA magic is needed before the memory is visible to the host (similar to where the ring buffer log is at).

It doesn't apply in Zephyr yet, we haven't merged the intel_adsp soc stuff.
As far as the log output: this is the same protocol implemented already.  It's not DMA memory, it's just a block in HP-SRAM (one that isn't visible to our linker, heh, which is a bug I need to submit) that's mapped to the host via a PCI BAR.  There may be more complicated things happening elsewhere in IPC, but for logging this really seems to be all that's needed.

You need to add option to logtool to read this memory.

Apart from memory base can it be more general? There might be some other boards using memory for console.

It's exactly the same memory being used by log_backend_rb.  The address is different because this accesses it through the uncached mapping for synchronization purposes.

Close this.  A descendant of this code is merged in the SOF tree already, we'll re-review when all that stuff comes back after a rebase.


Create a contact info block

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

You can find me here:
https://www.linkedin.com/in/anna-mariia-kyslenko-a98354243/
https://www.instagram.com/bilka.11/
My phone number:
+48506697466
+380969980940
My email adress:
<EMAIL_ADDRESS>


VSTest starts work unpredictable after adding TfsPublisher

Description
We found out strange behavior after adding TfsPublisher logger to our project.
For one of our business cases we implemented custom logger. This logger uses without coping to extension folder, just add --TestAdapterPath. It works correctly.
But now we try to add TfsPublisher we found out some issues:

can't use some of new futures vstest for example: --ResultsDirectory, moreover no one argument does not work if call it with --
custom logger does not work (Could not find a test logger with AssemblyQualifiedName, URI or FriendlyName). Argument --TestAdapterPathsets, but does not work.
vstest version was decrised(15.7.2 => 15.0.27617.1)

Moreover if try to add TfsPublisher like --logger:TfsPublisher instead of /Logger:TfsPublisher vstest does not find it.

@vbondaryuk This is a known issue.
TfsPublisher is not supported with new TestPlatform.
If TfsPublisher is opted like /logger:TfsPublisher, it fallbacks to older TestPlatform which does not have the new features.
/cc: @pvlakshm @cltshivash @smadala @mayankbansal018

@singhsarab Thank you for your response.
Will it be fixed in future?
Since TfsPublisher is not supported with new TestPlatform is there any possibilities to publish test results to Tfs without usage of TfsPubliser?
If yes, could you provide any examples?

@vbondaryuk TfsPublisher is only used to publish results against XAML builds. With most of our customers on or moving to new build system, highly unlikely we would be investing here.
We have had no asks for new Test platform to support this. In next major release, we would not be supporting via fallback scenario as well.
Given that, the general guidance from our side to write a custom logger to achieve that. For example, https://github.com/spekt/appveyor.testlogger

@vbondaryuk Please let us know if you have any concerns.
If you don't, I will go ahead and close the issue.


Placement bugfix from 1.2.8 introduced a new bug

Hello !
First, thanks for this great plugin ! It was exactly what I needed, far better than bootstrap popover which have many issues when we want to go further than a simple popover.
Unfortunately, the last update (1.2.8) introduced a new bug by improving the previous placement bugfix.
You can easily see the bug on this fiddle : https://jsfiddle.net/tu4ttweq/6/
There is no special css, the thing is :
Scroll down a bit and click on the trigger, you'll see the popover popping in a wrong position.
It seems like the "top" property is set regarding of the viewport and not the main container (which is the default one on my fiddle).
PS: I will continue with 1.2.7 for now, I didn't see any issue on this one, at least for my purpose (and for now)

For me, this isn't even working with 1.2.7. I forked @nomadOnWeb's fiddle and tweaked it a bit: https://jsfiddle.net/maryisdead/t0jskhch/
Just scroll the square to the top or bottom edge. The tooltip will always be placed at the bottom and thus be hidden when the square is at the bottom. Works fine if I add 1.2.6 from jsDelivr.

This bug is fixed in version 1.2.9.
Thanks!


Move even more code out of lounge.js

Last, sorry

@astorije good catch, I somehow removed incorrect code in last commit.


.form-switch failed with scss

When bootstrap-5 styles's are import from scss, the switches in the forms doesn't work, the checkbox outline's is just lager and the check is padding but there isn't a switch

Sorry, the problem came from me


SSE Support

Add SSE support for all Vector, and Matrix Operations

This is done...?

Nope. Vectors and Mat4s do not have any SSE yet.

The code doesn't build without SSE currently, because HMM_RSquareRootF() uses HMM_SqrtF() instead of HMM_SquareRootF().
Furthermore I think it's not a good idea that SSE is used by default everywhere, because then the user has to #define HANDMADE_MATH_NO_SSE if there's no SSE available (e.g. i686 build or ARM or whatever).
Maybe add
#ifndef __SSE__
#define HANDMADE_MATH_NO_SSE
#endif

somewhere at the top?
I think HANDMADE_MATH_NO_SSE only makes sense for disabling SSE if it is available.

Ill take a look at this and fix this in the coming days.

Thanks a lot!

@DanielGibson Fixing this tonight sorry life has been so busy

I'd say we take advantage of a lot of SSE features now. Will close this for the time being.


Too many requests upon configuring Settings sync to sync everything

On the latest Insiders, I logged in to activate Settings sync. I then configured it to sync everything and got logged out of Settings sync with the following error:
2023-09-12 15:57:27.570 [info] Sync started.
2023-09-12 15:57:27.570 [info] Too many requests https://vscode-sync-insiders.trafficmanager.net/v1/manifest https://vscode-sync-insiders.trafficmanager.net/v1/manifest https://vscode-sync-insiders.trafficmanager.net/v1/resource/keybindings/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/snippets/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/snippets https://vscode-sync-insiders.trafficmanager.net/v1/resource/tasks/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/globalState/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/globalState https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/keybindings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/snippets/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/tasks/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/globalState/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/extensions/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/extensions https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/keybindings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/snippets/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/tasks/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/globalState/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/extensions/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/extensions https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/settings https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/keybindings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/keybindings https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/snippets/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/snippets https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/tasks/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/globalState/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/globalState https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/extensions/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/extensions https://vscode-sync-insiders.trafficmanager.net/v1/collection/85eeb738-dd61-4f40-8770-a5a83181fad7/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/collection/9cb9754d-1fbc-49fd-9935-22a343b75180 https://vscode-sync-insiders.trafficmanager.net/v1/collection/cbad680a-0243-4a6a-8bf7-dc0ca437751b https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles https://vscode-sync-insiders.trafficmanager.net/v1/manifest https://vscode-sync-insiders.trafficmanager.net/v1/resource/keybindings/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/globalState https://vscode-sync-insiders.trafficmanager.net/v1/resource/extensions https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/collection https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/extensions https://vscode-sync-insiders.trafficmanager.net/v1/collection/fd91e4dd-21b6-4658-98c1-b66cb8ddeae3/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/machines/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/machines https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/machines/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/settings https://vscode-sync-insiders.trafficmanager.net/v1/resource/keybindings https://vscode-sync-insiders.trafficmanager.net/v1/resource/snippets https://vscode-sync-insiders.trafficmanager.net/v1/resource/tasks https://vscode-sync-insiders.trafficmanager.net/v1/resource/extensions https://vscode-sync-insiders.trafficmanager.net/v1/resource/globalState https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles https://vscode-sync-insiders.trafficmanager.net/v1/manifest https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/settings https://vscode-sync-insiders.trafficmanager.net/v1/resource/keybindings https://vscode-sync-insiders.trafficmanager.net/v1/resource/snippets https://vscode-sync-insiders.trafficmanager.net/v1/resource/tasks https://vscode-sync-insiders.trafficmanager.net/v1/resource/extensions https://vscode-sync-insiders.trafficmanager.net/v1/resource/globalState https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles https://vscode-sync-insiders.trafficmanager.net/v1/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/keybindings/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/snippets/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/tasks/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/globalState/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/extensions/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/profiles/latest https://vscode-sync-insiders.trafficmanager.net/v1/resource/globalState https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/keybindings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/snippets/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/tasks/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/globalState/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/187a30ac-14fe-4730-9e0a-304a8005046c/resource/extensions/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/settings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/keybindings/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/snippets/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/tasks/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/globalState/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/2fe86b00-3fd5-4120-9795-73b037537dc1/resource/extensions/latest https://vscode-sync-insiders.trafficmanager.net/v1/collection/7bfb631b-99d4-47cc-bbd9-cd4810abbc03/resource/settings/latest
2023-09-12 15:57:27.570 [info] Request failed https://vscode-sync-insiders.trafficmanager.net/v1/manifest

/duplicate
https://github.com/microsoft/vscode/issues/189033

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Setting torrent to pause set status as "completed".

I think it's better to set is as "paused" since "completed" sounds more like "download completed", but as paused you are not seeding or downloading anything more.

I think you should be able to distinguish 100% downloaded torrents and the one that are incomplete. In that regard not-complete torrents should be Paused, while 100% completely downloaded should have status "Completed".
But i suppose it is up to @vktr

Statuses from other torrent clients:
Downloading - you are downloading and seeding also
Seeding - your download is complete and you are seeding now
Paused - you are not downloading and not seeding anything

I think we need to discuss how this should be handled. We could, for example, add icons to the list view to enhance the current status even more - i.e a torrent with an upwards-pointing arrow and a status that says Finished would imply that the transfer is finished and still active, while a pause icon would imply that the transfer is finished and paused.

Fixed in #324.


IntegrationSensor.init() missing 1 required keyword-only argument: 'max_sub_interval'

⚠ Not addressing this issue will break this integration in Home Assistant 2024.7.
System Health details
System Information

version
core-2024.7.0.dev202406160221

installation_type
Home Assistant OS

dev
true

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.2

os_name
Linux

os_version
6.6.32-haos

arch
x86_64

timezone
Europe/Amsterdam

config_dir
/config

Home Assistant Supervisor

host_os
Home Assistant OS 12.4.dev20240612

update_channel
dev

supervisor_version
supervisor-2024.06.2.dev1002

agent_version
1.6.0

docker_version
26.1.4

disk_total
468.7 GB

disk_used
103.6 GB

healthy
true

supported
true

host_connectivity
true

supervisor_connectivity
true

ntp_synchronized
true

virtualization

board
generic-x86-64

supervisor_api
ok

version_api
ok

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
The current nightly/dev version of Home Assistant, in combination with the latest version of this integration at the time of writing (v1.12.10) will not fully work and throw the error listed below in the log.
This issue is caused by the following upstream PR / change:
https://github.com/home-assistant/core/pull/110685
Reproduction steps

Update Home Assistant to 2024.7.0.dev202406160221 or newer
Use this integration...

Debug logs
2024-06-16 22:39:41.025 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up powercalc platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 366, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/powercalc/sensor.py", line 313, in async_setup_platform
    await _async_setup_entities(
  File "/config/custom_components/powercalc/sensor.py", line 378, in _async_setup_entities
    entities = await create_sensors(hass, config, discovery_info, config_entry)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/powercalc/sensor.py", line 631, in create_sensors
    new=await create_general_standby_sensors(hass, global_config),
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/powercalc/sensors/group_standby.py", line 47, in create_general_standby_sensors
    energy_sensor = await create_energy_sensor(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/powercalc/sensors/energy.py", line 132, in create_energy_sensor
    return VirtualEnergySensor(
           ^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/powercalc/sensors/energy.py", line 224, in __init__
    super().__init__(
TypeError: IntegrationSensor.__init__() missing 1 required keyword-only argument: 'max_sub_interval'

Diagnostics dump or YAML config
No diagnostics dump is possible in this case. Sorry.

@frenck Thanks for reporting this in early stage, fixed with #2302. Will be in next release.
Just out of interest, how did you discover this. Are you running powercalc in your dev instance of have that integrated in some CI/CD pipelines?

 (You can switch to nightly as well if you like, run ha supervisor options --channel dev from a terminal).

Thanks will do that on my test HA instance. Good to have that running bleeding edge version. Have that running through proxmox, so can easily set that to dev channel. Don't want to use dev channel on my prod instance. You have so much faith ;-).
I also have dev instance which I'm managing manually using python virtual env, and just git pull origin dev there once every few weeks. However don't have the frontend working there anymore. Posted something on discord about that few weeks ago, but was still unable to resolve. Some very strange caching issue with the JS assets there.
But mostly I'm just working with the unit tests (have 100% coverage on powercalc), which I run against https://github.com/MatthewFlamm/pytest-homeassistant-custom-component. But these releases only contain latest stable and beta versions of HA, so can't use this strategy to test against latest dev version.

However don't have the frontend working there anymore. Posted something on discord about that few weeks ago, but was still unable to resolve.

That is what the nightly is for, that includes latest nightly frontend and nightly intents as well.

You have so much faith ;-)

Honestly, it isnt't that bad. I can't remember the last time I ran into big issues (and if it happens, it's easy to roll back). That said, I love to run into issues, especially before others do.

Haha true, from your perspective it's also a good thing to to actually run the latest code on a system containing actual entities, automations etc. Higher chance you actually discover real bugs.
Don't have time to fiddle with bugs in the latest nighly besides powercalc maintenance, my daily dev job and watching the European football championships ;-).
Sometimes I install latest beta when I have some more spare time to help out, but that's about it.

However don't have the frontend working there anymore. Posted something on discord about that few weeks ago, but was still unable to resolve.

That is what the nightly is for, that includes latest nightly frontend and nightly intents as well.

But I need to have a supervised instance for that right?
I just want to run dev version of HA where I have a working frontend and can use an actual debugger in my IDE.
I have setup my dev instance using this instructions: https://developers.home-assistant.io/docs/development_environment/#manual-environment

I just want to run dev version of HA where I have a working frontend and can use an actual debugger in my IDE.

The frontend in dev should be working with the dev. We generally bump dev if the change isn't backward compatible. Right now, the version of the frontend pinned on the core dev should be fully compatible.

I just want to run dev version of HA where I have a working frontend and can use an actual debugger in my IDE.

The frontend in dev should be working with the dev. We generally bump dev if the change isn't backward compatible. Right now, the version of the frontend pinned on the core dev should be fully compatible.

Good news! I just tried again, and now my development instance started working again magically ;-). Glad to have that finally resolved.
It was broken for 2 months it was always loading outdated JS file, which was not to be found anymore in the sources of my local.
Latest git pull dev which I did today and another script/setup probably fixed it.
But had done that countless times before trying to resolve, and also removed and recreated virtual envs multiple times.
Clearing browser caches etc. etc.


Only reload components down from the pivot point

Fixes loadProps being called twice or not at all in some cases.
It's impossible to know which components to call loadProps on without knowing what params they need. This patch assumes that loadProps on a component does not use the params of its children, which I think is a reasonable assumption. Without this (or explicitely specifying what params you want to listen to) the only thing you can do is refresh everything on every route change.
https://github.com/rackt/async-props/issues/28

check out the new test suite (and code changes), as far as I can tell it's working as intended now in 0.3.0.


Clone flexible layout

Make it possible to clone a flexible layout

This is fixed with https://github.com/marshmallow-packages/nova-flexible/pull/291


'ModuleNotFoundError'

When I try to run '$ appointments' I get the following output:
Traceback (most recent call last):
  File "/usr/local/bin/appointments", line 2, in <module>
    from appointments.appointments import watch_for_appointments
ModuleNotFoundError: No module named 'appointments'

How should I proceed?

I didn't package it properly, my bad. I'll fix it when I find a few minutes.
In the meantime, try running the package from source: pull this repository, and run pip install -e /path/to/repo. The appointments package should exist.

It's fixed. Try again: pip install --upgrade berlin-appointment-finder