Unnecessary component loads on back navigation

Describe the bug
My project involves two different pages: a dashboard and a project page you can navigate to from the dashboard. Both pages use user specific data and the project page has a parent dependency in the load function.
When navigating back to the dashboard using either the back key or a menu link I'm getting a Uncaught (in promise) TypeError: u.cols[c] is undefined from a component that is not even used in rendering the dashboard. It's only used in the page I'm coming from. Refreshing the dashboard solves the problem.
This behavior has me a little puzzled. I don't understand why the unused component is loading in the first place, but even then the store data should not be undefined since I'm not flushing anything on back navigation.
I apologize if this is too little to go on.
Reproduction
I wasn't able to generate a minimal reproducible example.
Logs
No response
System Info
System:
    OS: macOS 13.3
    CPU: (8) x64 Apple M1 Pro
    Memory: 20.70 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.10.0 - ~/node_modules/.bin/node
    npm: 9.3.1 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 112.0.5615.49
    Firefox: 111.0.1
    Safari: 16.4
  npmPackages:
    @sveltejs/adapter-static: ^2.0.1 => 2.0.1
    @sveltejs/kit: ^1.0.0 => 1.15.2
    svelte: ^3.55.0 => 3.58.0
    vite: ^4.0.1 => 4.2.1

Severity
serious, but I can work around it
Additional Information
No response

Please provide a reproduction repository, else we can't look into this because we don't know where to start. To make a minimum reproducible I suggest to start from your current project and rip out all stuff with which it's still reproducible, until there's nothing to remove anymore.

I have also seen this issue in my projects, although I haven't managed to reproduce it yet as in a simple reproduction it doesn't seem to occur. I will get a bunch of errors from child components that variables from the page store aren't defined when the user navigates back to the homepage. The home page then doesn't respond to any user interaction. Seems to only happen in Chrome, not Firefox.


How abort request when using async/await?

I feel like I'm missing something basic here. When using something like the below, how do you get a reference to the req object to call abort()?
const res = await request.post('someurl').attach('thing', thingFile);

I'm in the process of updating dependencies and I note you've now deprecated returning req from calls to end(). One instance of old code that I wrote before promises were a thing in JavaScript uses this to abort. I can't see how to update it to use the async/await syntax, which is what I use for all my promises nowadays.
I should note that I see in your documentation an example using yield to handle the promise. That is a keyword I avoid to keep all code consistent using async/await.

Ah right. So req is a promise and you can call abort directly on the promise? Interesting.

Req isn't a promise. It's "thenable", which means it's converted to a promise when needed.

Gotcha. That makes more sense. Thanks.


Policy assignment change every build/deploy

EPAC build has changes every run even though policy assignment haven't changed.
EPAC deploy therefore also deploys these assignment every run.
I would think this is not intentional ?
Policy Assignment counts:
    6 unchanged
    2 changes:
        new     = 2
        update  = 0
        replace = 0
        delete  = 0

New 'Kubernetes cluster pods and containers should only run with approved user and group IDs' at /subscriptions/<subid>/resourceGroups/<rgname>
New 'Kubernetes cluster containers should only use allowed images' at /subscriptions/<subid>/resourceGroups/<rgname>

Policy Assignment in question
{
   "$schema": "https://raw.githubusercontent.com/Azure/enterprise-azure-policy-as-code/main/Schemas/policy-assignment-schema.json",
   "assignment": {
      "description": "",
      "displayName": "Kubernetes cluster containers should only use allowed images",
      "name": "<name>"
   },
   "definitionEntry": {
      "displayName": "Kubernetes cluster containers should only use allowed images",
      "policyId": "/providers/Microsoft.Authorization/policyDefinitions/f06ddb64-5fa3-4b77-b166-acb36f7f6042"
   },
   "enforcementMode": "Default",
   "nodeName": "/root",
   "parameters": {
      "allowedContainerImagesRegex": "<regex>",
      "effect": "Deny"
   },
   "scope": {
      "tenant": [
         "/subscriptions/<subid>/resourceGroups/<rgName>"
      ]
   }
}

Running debug on plan and it does find the policyassignment
    {
      "id": "/subscriptions/<subid>/resourceGroups/<rgname>/providers/Microsoft.Authorization/policyAssignments/<assignment name>",
      "name": "<assignment name>",
      "type": "microsoft.authorization/policyassignments",
      "tenantId": "<tenantid>",
      "kind": "policyassignments",
      "location": "global",
      "resourceGroup": "<rgname>",
      "subscriptionId": "<subid>",
      "managedBy": "",
      "sku": null,
      "plan": null,
      "properties": {
        "policyDefinitionId": "/providers/Microsoft.Authorization/policyDefinitions/f06ddb64-5fa3-4b77-b166-acb36f7f6042",
        "effectiveDefinitionVersion": null,
        "latestDefinitionVersion": null,
        "definitionVersion": null,
        "parameters": {
          "allowedContainerImagesRegex": {
            "value": "<regex>"
          }
        },
        "displayName": "Kubernetes cluster containers should only use allowed images",
        "description": null,
        "metadata": {
          "createdOn": "2024-03-11T11:39:57.355Z",
          "createdBy": "e4d15b62-4e0f-40f2-a6db-47450a22b78c",
          "updatedBy": "e4d15b62-4e0f-40f2-a6db-47450a22b78c",
          "updatedOn": "2024-03-11T15:03:15.779Z",
          "pacOwnerId": "df73e910-db51-49de-b732-1f868ce785e4"
        },
        "nonComplianceMessages": null,
        "resourceSelectors": null,
        "enforcementMode": "Default",
        "overrides": null,
        "notScopes": [],
        "scope": "/subscriptions/<subid>/resourceGroups/<rgname>"
      },
      "tags": null,
      "identity": {
        "userAssignedIdentities": null,
        "principalId": null,
        "tenantId": null,
        "type": "None"
      },
      "zones": null,
      "extendedLocation": null
    },

Let me know If you need additional information

I have a feeling this is due to the schema property in the parameters in each of those policies... When we pull the changes I don't think we're comparing that property so it comes up as new/replace.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Per Andersson @.>
Sent: Tuesday, March 12, 2024 8:05:48 PM
To: Azure/enterprise-azure-policy-as-code @.>
Cc: Subscribed @.***>
Subject: [Azure/enterprise-azure-policy-as-code] Policy assignment change every build/deploy (Issue #507)
EPAC build has changes every run even though policy assignment haven't changed.
EPAC deploy therefore also deploys these assignment every run.
I would think this is not intentional ?
Policy Assignment counts:
6 unchanged
2 changes:
new     = 2
update  = 0
replace = 0
delete  = 0
New 'Kubernetes cluster pods and containers should only run with approved user and group IDs' at /subscriptions//resourceGroups/
New 'Kubernetes cluster containers should only use allowed images' at /subscriptions//resourceGroups/
Policy Assignment in question
{
"$schema": "https://raw.githubusercontent.com/Azure/enterprise-azure-policy-as-code/main/Schemas/policy-assignment-schema.json",
"assignment": {
"description": "",
"displayName": "Kubernetes cluster containers should only use allowed images",
"name": ""
},
"definitionEntry": {
"displayName": "Kubernetes cluster containers should only use allowed images",
"policyId": "/providers/Microsoft.Authorization/policyDefinitions/f06ddb64-5fa3-4b77-b166-acb36f7f6042"
},
"enforcementMode": "Default",
"nodeName": "/root",
"parameters": {
"allowedContainerImagesRegex": "",
"effect": "Deny"
},
"scope": {
"tenant": [
"/subscriptions//resourceGroups/"
]
}
}
Running debug on plan and it does find the policyassignment
{
  "id": "/subscriptions/<subid>/resourceGroups/<rgname>/providers/Microsoft.Authorization/policyAssignments/<assignment name>",
  "name": "<assignment name>",
  "type": "microsoft.authorization/policyassignments",
  "tenantId": "<tenantid>",
  "kind": "policyassignments",
  "location": "global",
  "resourceGroup": "<rgname>",
  "subscriptionId": "<subid>",
  "managedBy": "",
  "sku": null,
  "plan": null,
  "properties": {
    "policyDefinitionId": "/providers/Microsoft.Authorization/policyDefinitions/f06ddb64-5fa3-4b77-b166-acb36f7f6042",
    "effectiveDefinitionVersion": null,
    "latestDefinitionVersion": null,
    "definitionVersion": null,
    "parameters": {
      "allowedContainerImagesRegex": {
        "value": "<regex>"
      }
    },
    "displayName": "Kubernetes cluster containers should only use allowed images",
    "description": null,
    "metadata": {
      "createdOn": "2024-03-11T11:39:57.355Z",
      "createdBy": "e4d15b62-4e0f-40f2-a6db-47450a22b78c",
      "updatedBy": "e4d15b62-4e0f-40f2-a6db-47450a22b78c",
      "updatedOn": "2024-03-11T15:03:15.779Z",
      "pacOwnerId": "df73e910-db51-49de-b732-1f868ce785e4"
    },
    "nonComplianceMessages": null,
    "resourceSelectors": null,
    "enforcementMode": "Default",
    "overrides": null,
    "notScopes": [],
    "scope": "/subscriptions/<subid>/resourceGroups/<rgname>"
  },
  "tags": null,
  "identity": {
    "userAssignedIdentities": null,
    "principalId": null,
    "tenantId": null,
    "type": "None"
  },
  "zones": null,
  "extendedLocation": null
},

Let me know If you need additional information
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/enterprise-azure-policy-as-code/issues/507 or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACWCJVSZXAG5RNC3IAD2HF3YX3AO3BFKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJLJONZXKZNENZQW2ZNLORUHEZLBMRPXI6LQMWBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTLDTOVRGUZLDORPXI6LQMWSUS43TOVS2M5DPOBUWG44SQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJTGM3TCNRSHAZTRAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMJYGEYDQMZQHAZ2O5DSNFTWOZLSUZRXEZLBORSQ.
You are receiving this email because you are subscribed to this thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I have made the necessary adjustment by removing the schema property from a particular policy assignment.
build -> deploy -> build process, the policies are still being identified as new.

This would be fixed with v10.0.0; however, your workaround is to add the following in your global-settings.jsonc file for each epac-environment (see https://azure.github.io/enterprise-azure-policy-as-code/desired-state-strategy/#use-case-3-include-resource-groups):
"desiredState": {
    "strategy": "full",
    "includeResourceGroups": true
}

That solved it, cheers

Fixed in v10.0.0 released on 4/5/2024


Update libocpp dependency, increase version to 2023.8.0

libocpp still needs to be tagged at v0.8.7 before we can merge this and tag the 2023.8.0 release


Need a public changelog  - e.g. Add releases tab in the new issues repo.

https://github.com/dotnet/machinelearning-modelbuilder

https://github.com/dotnet/machinelearning-modelbuilder/releases. Currently, each "release" is:

The date of release
The associated version of the extension
A pointer to the blog post describing it.

It's also necessary to create a tag for the source, which for this repo happens to be simply public documentation.

@greazer can you please add the VSIX as well to the release artifacts?


Resolve confusion between Symmetry and Transform classes

Recent changes mean we have two classes that encapsulate more or less the same information, only one should be needed. Probably easily resolved, just needs some attention to how the Symmetries and Shape_Matcher classes output their results.

Resolved by https://github.com/DOSull/weaving-space/commit/17837aa335683143cc9fc33106edd09af30cf33a and https://github.com/DOSull/weaving-space/commit/a4eb685ea4ffa2e8b5b37e7dc340123b867c2de7


go-to-def jumps to wrong namesake in the presence of compiler error

clangd is jumping to namespace when there is compiler errors. This often happens -inl.h files that can't be compiled stand alone. Here is an artificially created sample to demonstrate the issue.
#pragma once

namespace xxxx {
namespace yyyy {

template <typename Traits>
undef_type foo<Traits>::bar(const undef_type& blockCluster) {
  dummy();
}

} // namespace yyyy
} // namespace xxxx

For this example, if I click on dummy and select go-to-def, it would take me to the namespace yyyy. It will be ideal in these cases to  not return any results.
SelectionTree in this case has namespace yyyy  as the leaf node with attribute Selected. If their AST is complete, I believe SelectionVisitor would have added all the nodes upto dummy(). IMO, in the presence of compilation error, we should see that the  line/offset of the leaf node does not represent the symbol we are after.
Logs
System information
Output of clangd --version:
clangd  --version
clangd version 16.0.20210610 (https://github.com/llvm/llvm-project.git 4cdcc5e49a6db04d5ad79ff51eb62fd4f4082650)
Features: linux
Platform: x86_64-unknown-linux-gnu; target=x86_64-redhat-linux-gnu
Editor/LSP plugin:
Operating system: Linux

The fundamental reason is that clang's AST does not in general record all each of the tokens that a node directly owns, but rather the range (first/last token) that it covers.
So we compute tokens owned by a node = tokens covered by the node's range - tokens covered by ranges of child nodes.
When the AST is sufficiently broken, some of these child nodes are simply missing.
Maybe it's possible to fix this, either with a fundamentally different design or by special handling of important cases like nodes with { ... } which do know brace locations and we can assume the nose doesn't own any tokens between the braces. (Even there is complexity to think about: macros that expand to nothing, missing braces with error recovery, etc)
Anyway, would be worth exploring if someone wants to open the selectiontree can of worms again.

It's also worth noting that we have a textual fallback heuristic that could potentially resolve dummy if the actual name is sufficiently unique within the project. However, for that to kick in, we first need to not have an AST-based result.


travis org to com

Change CI/CD from travis.org to travis.com.

Not linking to travis.com for some reason.


Wrong numbers for computed

Hi! Im trying to add nanostores to my bench and get this error

Expected "18", received "26"

Looks like there is glitch somewhere, or I have a mistake in atoms definitions?

Hi @artalar
Seems like on line 250 of your bench const a = computed(entry, (entry) => entry + 1)
should be const a = computed(entry, (entry) => entry)
I see on other test cases a value without any incrementations.
Correct me if I'm wrong

@kimoofey you are right! Without this mistake nanostores score is at the top of the list! Will publish update in a couple of days


Azure CDN: Enabling HTTPS for custom domain through ARM

Reading this: https://docs.microsoft.com/en-us/azure/cdn/cdn-custom-ssl?tabs=option-1-default-enable-https-with-a-cdn-managed-certificate and this: https://docs.microsoft.com/en-us/azure/templates/microsoft.cdn/2019-04-15/profiles/endpoints/customdomains I cant seem to find any way of enabling HTTPS through ARM. Is it just me that can't find it, or can this only be done through the portal for now?

If this can only be done through portal, the docs here  https://docs.microsoft.com/en-us/azure/cdn/cdn-custom-ssl?tabs=option-1-default-enable-https-with-a-cdn-managed-certificate, should reflect this
If this can be done though powershell only, the docs needs to reflect this

The reason why I think this should be pointed out is, that HTTPS is pretty standard nowadays and this should be either easy to do, or easy to find information on how to do it automatically.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: beac0740-af6e-61ce-bcfa-e783ca181b7d
Version Independent ID: d97885ea-b051-5fde-bd14-ec977e34760e
Content: Tutorial - Configure HTTPS on an Azure CDN custom domain
Content Source: articles/cdn/cdn-custom-ssl.md
Service: azure-cdn
GitHub Login: @mdgattuso
Microsoft Alias: magattus

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks @Karishma-Tiwari-MSFT :) Looking forward to hearing from you.

@mslot , Appreciate your patience.Enabling HTTPS for custom domain though ARM for CDN is not yet available for now. In order to automate this process you can write a custom PowerShell script to call this respective API which will enable HTTPS for you. Here is a similar thread in SO for your reference.
We are closing this issue for now.If there are further questions regarding this matter, please reply and we will gladly continue the discussion.

@SubhashVasarapu-MSFT thanks. I have read that So, but isn't that only for custom certificates? Is this possible to do by powershell if you want Azure to handle the certificate?


Feature/unbounded normalization

Hello @szvsw! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file skopt/learning/forest.py:

Line 197:80: E501 line too long (82 > 79 characters)
Line 393:80: E501 line too long (82 > 79 characters)

In the file skopt/space/space.py:

Line 66:80: E501 line too long (100 > 79 characters)
Line 81:80: E501 line too long (89 > 79 characters)
Line 81:90: W291 trailing whitespace
Line 297:80: E501 line too long (83 > 79 characters)
Line 298:80: E501 line too long (100 > 79 characters)
Line 311:80: E501 line too long (89 > 79 characters)
Line 316:80: E501 line too long (92 > 79 characters)

In the file skopt/space/transformers.py:

Line 242:80: E501 line too long (81 > 79 characters)
Line 251:80: E501 line too long (84 > 79 characters)
Line 252:44: E127 continuation line over-indented for visual indent

Apologies, meant to open this pr into our own fork


Fixed deprecation message version

Don't hesitate to share some description next time, @GrahamCampbell ;)

Thank you @GrahamCampbell.


gateway-api: now function GatewayAPI also supports TLSRoute

Please ensure your pull request adheres to the following guidelines:

[ ] For first time contributors, read Submitting a pull request
[ ] All code is covered by unit and/or runtime tests where feasible.
[ ] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[ ] Provide a title or release-note blurb suitable for the release notes.
[ ] Are you a user of Cilium? Please add yourself to the Users doc
[ ] Thanks for contributing!

marking as ready-to-merge as this is only changing a comment (not related to any generation)


fix: change to use relative path for hash

fix: change to use relative path for hash.
Previously, we use absolute path to make the hash. But if the project is used across different PC, the root path for the project is different, so the hash will be different, so will cause translation fully triggerred instead of skipped.
So here change to use relative path for hash.

Bumped to v0.5.1 @Germey


Tensorboard documentation

Might fix #519
I see a scope of improvement for this documentation. Suggestions will be helpful.

@mansishr Thanks for starting on this. A couple other things that should be part of this PR:

Tensorboard logs can also be captured with the TaskRunner API, and the documentation should indicate that. A description of write_logs parameters in the plan (see here). When it's set to true, tensorboard logs will be written.
Explain what metrics get saved by the aggregator (aggregator and collaborator metrics), and how to launch tensorboard from the workspace


Change "id" to bigint to prevent overflows

In haas/model.py, the primary key (as stated on the AnonModel object) for most of our tables is integer, which equates to a signed 4 byte number.
Being relatively small in computer terms, it's possible to make this overrun, either maliciously or just from a long-running instance. We should switch it to a biginteger, which is 8 bytes and not likely to wrap anytime soon.
We could provide a DB migration script or just make the change and have it apply to new installs only (my vote is the latter). Thoughts?

dup of #315


tds.Vec() not supported

Hi
since tds.Hash() is supported why not supporting also tds.Vec()?
Thanks

Feel free to add it and submit a PR. I didn't write the tds.Hash support
since I don't use tds, someone else sent it as a PR.
On Fri, Oct 28, 2016, 18:11 mauann<EMAIL_ADDRESS>wrote:

Hi
since tds.Hash() is supported why not supporting also tds.Vec()?
Thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bshillingford/python-torchfile/issues/3, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACOA3UQrB8_-oxqgTcircLWls3UB5UlFks5q4iy5gaJpZM4KjqDE
.


Fix editor bug caused by repeatedly replacing CodeMirror instance

useSignalEffect re-runs whenever signals within the callback are modified, while useEffect with an empty dependency array will only run once. Changed useSignalEffect -> useEffect for effect that was causing problems.

I've looked at the issue, but you can also accomplish what you want by calling .peek() instead of .value for the persistenceState I think

if it's really urgent, and you can't find another way to do this, I approve it and will try to implement it in a different way

Sounds good. I'll merge it for now and we can talk more when you get into the office.


Method to determine if Formula Types can be copied

Set(x, dataverseRecord) will fail since dataverseRecord is not a copyable type.  (enforced with #1633)
But really, we should be blocking this at time of creating variable 'x' if it's a non-copyable type.
Here's the check we do in Set() to block this
https://github.com/microsoft/Power-Fx/blob/ee877354b4c0392d7e0d8244e6348fa5ce399d61/src/libraries/Microsoft.PowerFx.Interpreter/Functions/SetFunction.cs#L92C30-L92C54
This should be using a public property on FormulaType that hosts can check as well.
More broadly, there may be other open issues here:

do we need the check in Set()?  Or should it just be blocked at creating the variable.
be sure to check for nested types. Set(x, {nested: dataverseRecord}) should fail too.

A basic workaround is:
bool IsDVType(FormulaType t) => (t as AggregateType)?.TableSymbolName != null;


release: v1.0.0a10

Signed-off-by: Krzysztof Nowak<EMAIL_ADDRESS>

@lnielsen Release of this is required for GitHub OAuth

@krzysztof please wait for #96.


Allow listening to frames.

Extracted two methods from setup and teardown that will allow me to attach the backend to an iframe. I need a DropTarget to live inside an iframe. Here is how I would do it
class Frame extends React.Component {
  static contextTypes = {
    dragDropManager: PropTypes.object.isRequired
  }
  render() {
     return <iframe></iframe>
  }
  componentDidMount() {
      const { contentDocument } = findDOMNode(this)
      this.context.dragDropManager.backend.addEventListeners(contentDocument.defaultView)
  }
  componentWillUnmount() {
      const { contentDocument } = findDOMNode(this)
      this.context.dragDropManager.backend.removeEventListeners(contentDocument.defaultView)
  }
}

That is much simpler than I was expecting.
Do you think you could add some tests and maybe an example?

I can definitely create an example. Not sure how to create tests though. This is only half of the solution - the other half is to get the dragDropManager to the iframe which I will show in the example.

Here is the example: https://github.com/akorchev/react-dnd-cross-frame

Thanks. I don't promise to support or test this in the future but I see no harm in adding it.
:+1:

Note that I still reference window in a couple of places so this won't cover all cases. There's a couple of places where I add a mousemove listener on window, and it's important to do this lazily for better perf. I'm open to merging more PRs handling this but I won't work on it myself.