[Hub Generated] Publish private branch 'asgar-microsoft-portalservices-Microsoft.PortalServices-CopilotSettings-2024-04-01-preview'

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

[!NOTE]
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Click here to see the details of Step 1, Breaking Changes review
If you are in purview of Step 1 of the diagram, follow the Breaking Changes review process.
IMPORTANT! This applies even if you believe your PR was mislabeled, for any reason, including tool failure.

Click here to see the details of Step 2, ARM review
See https://aka.ms/azsdk/pr-arm-review.

 Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[ ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with PR workflow diagram Step 2 (ARM review), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/17601

Please fix the LintDiff https://github.com/Azure/azure-rest-api-specs/pull/28734/checks?check_run_id=24270996602 errors and warnings from this PR and TypeSpec requirement failures https://github.com/Azure/azure-rest-api-specs/pull/28734/checks?check_run_id=24271215119

You should probably implement paging?

❌ XmsPageableForListCalls	x-ms-pageable extension must be specified for LIST APIs.
Location: copilotSettings/preview/2024-04-01-preview/copilotSettings.json#L51	RPC-Get-V1-13

You should add a suppressino for this (in readme.md) for a tenant level resource:

❌ TopLevelResourcesListBySubscription	The top-level resource 'CopilotSettingsResource' does not have list by subscription operation, please add it.
Location: copilotSettings/preview/2024-04-01-preview/copilotSettings.json#L287	RPC-Get-V1-05


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3149

Questions ?
Please refer to the Backport tool documentation


Converting this to ESM

Hello! I'm about to start converting this to ESM (hopefully itll be as easy as the dependencies).
I have done the dependencies:
graphlib
dagre
However, if the author doesn't pull and release them, then the official npm repos wont support ESM here either!
I want it and need it tho so I'll be using  a fork if I have to.
Pinging @maxkfranz for fun!

Do we know if there is a reason we depend on dagre and not the most recently maintained (still unmaintained) @dagrejs/dagre
possible incoming pain for me

Not packing dagre in w/ cytoscape-dagre.js seems a bit offbeat to me if using webpack.

Should coordinate with https://github.com/cytoscape/cytoscape.js-automove/pull/34

FYI, there's an ESM fork of dagre at https://www.npmjs.com/package/dagre-d3-es.
It's not a one-to-one comparison though, since that fork combines:

dagre-d3
dagre
graphlib

Although, beware of the download count, I know it has over ~500k weekly downloads, but almost all of them are just from one project, so it it's not as well tested as the official dagre library.

@aloisklink I think they just merged my changes to the main library! So the main library should be native esm now. I'll be reviewing all this this weekend to see where we're at!

Yeah so, hoenstly, it seems kinda weird over there.
I think my conversions might be a hard pill to swallow, rollup provides a better experience.
But still, they reverted a dependency and not a defendant but I don't see how that builds, so. This project is on my backburner, but maybe I'll get back to it before anyone else does.


Fix #67: stop using the cache.  Fix #66: remove PII

This requires quite a few changes:

remove the record cache completely.
change the CSV processor to work on the entire batch, loading all required records directly from Airtable.
move worker processing into dedicated tasks, so they can run in multiple processes.
overhaul the worker runner so we can run a worker in a separate process.
change the error logging to use non-PII to identify records with issues.

When deploying to Herokou, we need these changes in DEV/STAGE:

Define EMBEDDED_WORKER_TYPES as webhook:csv
Remove definition of EMBEDDED_WORKER

In production:

Turn on the worker process
Define EMBEDDED_WORKER_TYPES as webhook
Remove definition of EMBEDDED_WORKER

Once deployment is complete, all the cache keys (prefix RecordCache) should be removed from the Redis instance, and it can be reduced back to a 100MB instance.


Cupcake content: developer contents

Wonil-Suh1 created the following on Aug 05:
Introduction
This story is part of the first phase work (research) towards the cupcake website.
The problem
As a developer, I need to know how to get started with the new design system.
Expected outcomes

[ ] A list of pages, each with description, references if applicable

Original issue: https://github.ibm.com/webstandards/digital-design/issues/1365

On Aug 20, chsanche commented:
@Jeff-Chew Let me know if you have any question about this task. Overall, I need a list of the content pages you think an adopter who is coding will need.
There's a BOX doc created for the content page list, if you would like to use it.

On Aug 26, chsanche commented:
Hi @Jeff-Chew
👉 Can you confirm the list below is good to go and I can include them into the Cupcake website site map?
👉 Out of the content listed below for coding, can you set priority for website page development based on your understanding of the user needs? If you do not have enough information to prioritize them at this moment, it is ok, please let me know.
Thank you.

Pages
Priority (based on Jeff)

IBM.com Library overview
1

Packages (React, Styles, Utilities, Services)
4

Getting Started (React/Vanilla)
2

Expressive Theme
3

Stable Selectors
5

Contributions
7

What's New
6

On Aug 27, chsanche commented:
@Jeff-Chew Perfect. Thanks!

On Aug 27, Jeff-Chew commented:
@chsanche see responses above, thanks!


Fixing broken code

I hope you don't mind if I make some changes to get this running again.  I've been trying to make updates so that  instructions according to https://explosion.ai/blog/chatbot-node-js-spacy are valid.  I have my own fork of aiva as well now that I'm tweaking and will submit a pull request with fixes there as well so that way the project will work out-of-the-box.  I was hoping to add some additional spaCy/neo4j functionality to this project on my own fork soon.  Let me know if you have any questions.

Nice catch.  I'll modify the bin/setup script in aiva as well to reflect the nexus package as well.

published to npm as<EMAIL_ADDRESS>


Add rule related to aria-flowto property

Include table[role=presentation] and aria-flowto attribute as part of manual checks

Reading order 1 rule referenced in this issue has been deleted
Add a rule to identify elements with aria-flowto as a "reading order rule"

This rule has been added to OAA 1.1


Behavior of .Not(Where().Or()) has changed

GORM Playground Link

https://github.com/go-gorm/playground/pull/711
https://github.com/go-gorm/playground/pull/710
Description
This is related to https://github.com/go-gorm/gorm/issues/6845.
The behavior of .Not(DB.Where().Or()) has changed.
In the sample code,
for v1.25.5, the playground code produces: WHERE NOT (name = 'a' OR name = 'b')
for master, the playground code produces: WHERE NOT (name = 'a' AND name = 'b')

@jinzhu should closed

I'm not being pulled into the contributor list, so I don't have permission to merge code 🧐


Add logic on ColumnDefinition.cs in TruncateLongString method to hand…

Add logic on ColumnDefinition.cs in TruncateLongString method to handle -1 MaxCharacterLength
Add unit test to cover change

Yep, looks perfect to me.  Thank you!


Non-registered apps not working with FancyZones

Microsoft PowerToys version
0.60.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Run program that is seemingly not registered as a Windows program, ie. portable version of an app.
✔ Expected Behavior
Fit into a FancyZone zone
❌ Actual Behavior
FancyZones not recognizing the app
Other Software
No response

what is the application and is it running under admin where FancyZones / PowerToys isn't?  I just tried ProcExp and it snapped with FancyZones.
/needinfo


Feedback and Concerns on the Proposal Signals

I am writing to express some concerns regarding the proposal to incorporate signals and reactive programming into the ECMAScript spec.
While I appreciate the potential benefits of signals for managing short-lived and non-persistent states within a JavaScript application—especially in the context of developing web applications and desktop/mobile applications (where the user interactions matter), I believe it's also important to consider the implications for server-side JavaScript. Server-side applications are often either stateless or persist states in an on-disk database rather than in memory. As such, the introduction of a Signal directly into the JavaScript language may not be beneficial in these contexts. Instead, it might be more appropriate to consider a runtime-specific implementation, such as a Web API. This approach would allow developers to adopt signals where they make sense, without imposing additional complexity on the language itself.
Moreover, I would like to draw attention to the existing Proxy object in JavaScript, which already provides a low-level language agnostics for library authors to implement similar functionality. See also https://github.com/proposal-signals/proposal-signals/issues/101.
Lastly, I would like to point out the similarities between the proposed Signal API and the deprecated Object.observe proposal. The latter also aimed to track object mutations and provide responsive callbacks, but it was ultimately withdrawn. I worry that the new signal proposal might essentially be a reiteration of Object.observe, and it could face similar challenges and criticisms.
I believe it's crucial to thoroughly consider these points to ensure the continued robustness and versatility of JavaScript. I look forward to engaging in further discussions about this proposal and contributing to the evolution of the language.
Thank you for your time and consideration!

Thanks for raising this @SukkaW.
I'll try to address each point from my own perspective. Other individuals may have additional thoughts.
Regarding TC39 as the vehicle for standardization. We don't have to do this through TC39. We started there because we heard non-Web use cases during our interviews, and because various members had strong prior experience with the TC39 process. That said, the largest set of use cases are UI related. If TC39 turns out to not be the right path, we can certainly shift to a different standards body.
Regarding Proxy. The Proxy, in itself, doesn't provide the infrastructure for interoperable signals. Signals have a very specific acyclic graph data structure and a "push then pull" algorithm. With proxies alone, the goals of this proposal cannot be achieved, and certainly not in an interoperable way. Signals is great paired with proxies, where a signal can be the underlying storage mechanism for a Proxy-based state store.
Regarding Object.observe(). Signals are very different from the types of observable properties and pub/sub that Object.observe() proposed. In fact, one of the biggest criticisms of Object.observe() was that it did not handle situations like what Signal.Computed handles. It had no notion of dependency tracking let alone the graph structure put forth in the signals proposal. The signals proposal also does not propose to alter the behavior of native objects in any way, another criticism of Object.observe() and Array.observe(). In many ways, signals is lower level. You could implement Object.observe() and Array.observe() in userland by leveraging signals.

Regarding TC39 as the vehicle for standardization. We don't have to do this through TC39.

Regarding Proxy. The Proxy, in itself, doesn't provide the infrastructure for interoperable signals.

With proxies alone, the goals of this proposal cannot be achieved, and certainly not in an interoperable way.

Thank you for your reply and for addressing the points I raised.
The main argument here is that if it's already possible to implement the functionalities and the behaviors of Signal using only setters, getters, and Proxy (whether it is possible, we can continue the discussion at https://github.com/proposal-signals/proposal-signals/issues/101 for easier tracking), then it may not be necessary to introduce it to the language.
This is similar to why the low-level data structures like Linked List and the Queue are not included in the ECMA-262 spec and W3C/WHATWG standards. They are useful, but JavaScript has already provided low-level building blocks that developers can use to create such libraries. The runtime will eventually optimize the execution if the approach and the code path become popular.

IMHO, what JavaScript really requires is a low-level building block designed for incremental computation. And I understand it is the key element that Signal.Computed was trying to add to the language.

My thoughts: The successful lesson is Promise, which was standardized in tc39 and used when the async function was proposed. A lesson learned from the failure is AbortSignal, which is standardized on the Web but has extensive needs in the entire ecosystem. This leads to the need for cross-environment coordination like WinterCG to solve the problem of cross-ecological consistency, but this actually shows that it should be implemented in tc39 Standardization (note that fetch is different because fetch involves IO, but AbortSignal does not).
I'm not sure signal has widespread use outside of rendering, so I'm not sure it should be in tc39.

I agree that Promise is a success and AbortSignal is not, and the venue is largely why that’s the case.
Rendering is very much also a server-side concern, so i’m much more optimistic that signals belongs in TC39.

Rendering is very much also a server-side concern, so i’m much more optimistic that signals belongs in TC39.

As I have already pointed out initially:

managing short-lived and non-persistent states within a JavaScript application—especially in the context of developing web applications and desktop/mobile applications (where the user interactions matter)

As for the server-side javascript, here I quote from my initial feedback:

Server-side applications are often either stateless or persist states in an on-disk database rather than in memory. As such, the introduction of a Signal directly into the JavaScript language may not be beneficial in these contexts.

We are not making persistent state (E.g. on-disk databases like MySQL, SQLite, PostgreSQL) reactive, right?

Rendering is very much also a server-side concern, so i’m much more optimistic that signals belongs in TC39.

SSR is pretty active in today's Web (nextjs etc) but let's say, should it also exist in the XS engine? Will you use it in general computation? (It's a maybe for me because I can see the benefit of incremental computing).

I can see the benefit of incremental computing

JavaScript needs a low-level building block for incremental computation (as I have already mentioned in https://github.com/proposal-signals/proposal-signals/issues/105#issuecomment-2030021434), but it doesn't necessarily be a new Computed().

The most common usage of those short-lived and non-persistent states are implementing user interactions

It's equally common in a webserver to respond to requests - they're often stateless, modulo a database, across requests, but quite stateful during the many distinct and separately located parts of a given request/response.

Just like how Proxy powers reactive framework

Proxy is incredibly slow and nearly impossible to optimize, and arguably it existing is a mistake. I don't think that's a good model to inspire future proposals.

Proxy is incredibly slow and nearly impossible to optimize, and arguably it existing is a mistake. I don't think that's a good model to inspire future proposals.

Here is the corrected and enhanced version of your statement:
It's incredibly slow, nearly impossible to optimize, and arguably its existence is a mistake. I don't believe it's a suitable model to inspire future proposals.
Indeed, Proxy is slow, and JavaScript has failed to provide a high-performance low-level building block for creating Reactivity Utilities. However, this doesn't imply that we need to incorporate Reactivity Utilities directly into the language. JavaScript itself doesn't need Reactivity Utilities; they should be implemented by the users of the language in the form of libraries or frameworks. The same goes for the Linked List and Queue, they are useful, but they are not part of the ECMA-262 spec (yet though).
The same principle applies to Computed. What JavaScript needs is a low-level building block for implementing Incremental Computation (upon which computed, createSignal, and useMemo would be built), not a new Computed().

Most non-rendering JS APIs I've worked on have almost immediately hit the desire for signals, primarily from the perspective of memo. Same for build tooling. Plenty of ways to construct a good memo function obviously, but none quite as robust as you get with signals.

primarily from the perspective of memo

If you are talking about this:
// A magic function `lazy()`, that will only evaluate on the first call,
// and the return value will be cached on the later calls
const a = lazy(() => { /* something */ });

if (/* ... */) {
  /* ... */ = a();
} else if (/* ... */) {
  // no a();
} else {
  /* ... */ = a();
}

if (/* ... */) {
  /* ... */ = a() + 1;
}

Then what you need is the incremental computation, not the derived state.

I feel truly mitigated: signals are amazing, and (in my opinion), the best solution (so far) for web applications. Giving them the opportunity to exist as a native API is great for developers and performances.
However, I clearly see some limits:

Observables on their time were the "way to go" for reactive applications, and we even get a proposal (discontinued), but paradigms evolves and we always find new approaches to solve particular problems. Signals are amazing now, but they may be replaced by an even better approach in 2-3 years maybe.
this proposal introduces some sort of low level API. We're far from the simplicity of promises, here we have access to fine grained controls to permit wide and different implementations. This is something unusual. Usually, to get quick adoption, simplicity is better.
signals are new, and I feel like they are not mature enough yet for a proposal (which will "fix" them definitively): for example, the proposal doesn't permit signals to throw, but we may imagine such requirement in the future (for example, we may expect that getting a uninitialized signal throws; or, if a signal proxifies an HTTP response, and this last one is errored, then we may want a way to set the signal in an errored state too). As they are new, we still have not explored all their limits, and not created yet the "optimal" way to use them (maybe higher order functions and usages not created now, may exist in a near future).

Finally, if it's part of the tc39 instead of w3c, we may thing about more "integrated" signals (and let the engine do the magic):
signal a = 5; // equivalent of let a = 5
signal b = computed {
  return a + 2;
}

const unwatch = watch {
  console.log(b);
}

TC39 opens the gate to new language possibilities and integrations, where the w3c is better suitable for to API.
However, such changes would require extremely robust specs, and a lot of "intelligence" behind, to create something both universal, and future proof. If it fails, this could cost a lot to the js ecosystem.
In my opinion, I suggest, it may be worth waiting 1-2 years for a real stabilisation and wide adoption (thus exposing limits, and introducing improvements), before jumping immediately into something still in early stages.

IMHO, what JavaScript really requires is a low-level building block designed for incremental computation.

@SukkaW Do you suggest to break this proposal into:

A TC39 proposal for low-level State and Computed classes
A W3C proposal for a global Signal object utilizing the above classes (basically Signal.subtle)

I think that would be a logical split.
Two proposals entails more work for the authors, but it would greatly simplify the TC39 proposal, possibly increasing the chances of approval and inclusion in the standard. The Signal object might also be easier to accept by W3C when standing on the shoulders of a standard language feature.
I'm excited about this proposal, and I hope it lands. State management is such a critical part of a language. This reactive approach has emerged over time as the preferred way to manage state in interactive JS applications, so I think it makes sense to standardize and provide a common ground for interoperability. State and Compute are powerful "primitives" on their own, I think they're well within the realm of language specification.

I think that would be a logical split.

That would be awesome!

Also, some other thoughts:
The incremental computation must be a language feature, not a built-in class. Because class introduces js object, js object introduces memory and GC pressure, memory and GC pressure introduces performance overhead, tick-tack-toe.

The incremental computation must be a language feature, not a built-in class. Because class introduces js object, js object introduces memory and GC pressure, memory and GC pressure introduces performance overhead, tick-tack-toe.

I think engines can optimize away what appears to be an object in this case. They're not bound to represent it as an object in memory, as long as it functions according to spec. So performance shouldn't be an issue, at least in the big, optimized engines.
Classes do have some benefits.

More likely to be accepted by TC39 than new keywords/syntax
More likely to receive support by engines (easier to implement)
Much easier to polyfill (doesn't require a transpiler)
They're extensible

While special syntax would be nice, I just want this proposal to be accepted :)

Responding from a library author perspective:
If Signals would only land in the browser, but not other engines, we would not be able to adopt them.

Redux could make great use of Signals in selectors. But Redux code is used in React applications. React applications run through SSR. Even though they would not get a lot of "reactive" use during SSR, we would rely on the presence of the same APIs.
The same can be said for Apollo Client - Signals would be very valuable in many places there. But if we only could use them in the browser, we couldn't use them at all.

Polyfills are not a happy fallback here - think of fetch where we now have the browser's fetch API, undici, node-fetch and half a dozen others, all of them with slight differences. Just swapping one for the other can make for subtle memory leaks.
And that ignores the fact that both Redux and Apollo Client are even used in normal backend code - completely outside of React applications.
Also, going the route of "have the ecosystem establish a library for it instead of including it in the platform" is probably not a good idea - because it might not happen, and in the end you'll ship multiple different implementations to your users.
Example case: If you use Apollo Client in Angular nowadays, you will ship Zen-Observable (because Apollo Client) and RxJs (because of Angular) to your users.
=> I'm very much in favor of this going through TC39.

I also want to add that environments like Node.js shouldn't be seen as a synonym for CRUD servers. @phryneas has already mentioned frontend tooling. But there are even more fields like more action/task heavy servers, AI, IoT, hardware development, CLI tools, etc. which would not be implemented in a browser.
Take this as an example:
const counter = new Signal.State(0)

hardwareButton.addEventListener('push', () => {
  counter.set(counter.get() + 1)
})

effect(() => {
  printOn7SegmentDisplay(counter.get())
})

This could be the code for some click counter. The structure for applications like this is very close to what a browser application would look like. Just replace html buttons with hardware buttons and print the result to some special screen instead of the DOM.
I also want to mention that I'm very happy to see this being worked on. My main use case might be browser centric as well but I'm playing around with how I could develop a web application with as few libraries as possible. And I figured out one of the biggest pain points is indeed state management. I've even started working on a library to tackle this problem and the result looks extremely similar to this proposal.
If this proposal could be made more simple like some mentioned I'd be all here for it though.


interpolate nat tracks into aircraft routes

If NAT[ID] in route, then interpolate that nat track, if the ID doesn't exist, ignore it (old tracks, playback file)

Did ages ago.


empty line in files-from adds all

Output of restic version
restic 0.4.0 (v0.4.0-0-ga7c2f28-dirty)
compiled with go1.7.5 on linux/amd64
Expected behavior
Empty line in -files-from file will be ignored
Actual behavior
Empty line in -files-from file treat as current directory,
for file
file1.txt

file2.txt

backup command try to backup current directory completely
scan [/home/me/file1.yml /home/me /home/me/file1.yml]
Steps to reproduce the behavior
add empty line in -files-from file and start backup from non empty directory

Ah, that's not the intended behavior, thanks for reporting it!


How to remove context menu?

SDelete-GUI automatically setup Windows Explorer context menu.
In case I don't want to use it any longer:
How do I remove this context menu later?

Run the GUI again and click "Disable". This should remove the "Secure Delete" option from the context menu,

Yes. In this way you uninstalled it.
If you have any other question let us know!

So ok, I started SDelete GUI from my USB flash drive and SDelete GUI tells me
"SDelete.exe not found in C:\Windows\SysWOW64 and cannot be downloaded from Internet"
very bad.
SDelete-GUI.exe is stored and run from the same directory as sdelete.exe and sdelete64.exe
Why does GUI not automatically look in its current folder for the SDelete64.exe?
How can I manually pass another absolute/relative path to  to SDelete-GUI.exe?
e.g.
SDelete-GUI.exe -lookpath="H\tools\sdelete"

Sdelete GUI downloads Sdelete from Microsoft or use the current one in system32.
Is it possible to you to copy Sdelete to the Syswow64 folder?
if any one can add a PR for adding a relative path we will release a new version with your suggested improvement.

Is it possible to you to copy Sdelete to the Syswow64 folder?

I don't want to copy any files.
Good software should work out of the box when necessary sub programs are put in their installation folder.

Remember this is a free, open-source tool. If you can help we accept your improvements.


create python function for creating delegations

we know have test fixture where we need to make many delegations. Lets make a function for that

We can replace more delegations in generate_fixtures.py but this is a start


Cant get 404 working from the documentation example

Description
I'm trying to create a not-found page but cannot access it. I tried stable and beta configuration steps.
Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://github.com/Tomekmularczyk/next-intl-404
Reproduction description
Steps to reproduce:

Open reproduction
yarn install && yarn dev
go to /abc (random URL)
See that not-found.tsx page is not render but a default 404 page

Expected behaviour
I should see a page from not-found.tsx file

This is quite strange.
I see that /abc (which uses the default locale) results in the root not-found page being rendered, but /de/abc is handled by the not-found page within [locale].
If you debug the request like so:
import createMiddleware from "next-intl/middleware";

const middleware = createMiddleware({
  // A list of all locales that are supported
  locales: ["en", "de"],

  // If this locale is matched, pathnames work without a prefix (e.g. `/about`)
  defaultLocale: "en",
});

export default function handler(request) {
 const response = middleware(request);
 console.log(response);
 return response
}

export const config = {
  // Skip all paths that should not be internationalized. This example skips the
  // folders "api", "_next" and all files with an extension (e.g. favicon.ico)
  matcher: ["/((?!api|_next|.*\\..*).*)"],
};

You see this on the console:
x-middleware-rewrite: 'http://localhost:3001/en/abc'

Something seems fishy here, quite possibly on the Next.js side, as this used to work in earlier versions. Maybe you can further reduce the example, possibly by removing next-intl and if the bug persists open an issue in the Next.js repo?
Note that there is generally a bug with not-found pages currently in Next.js: #423
As a temporary workaround, you might want to downgrade Next.js to the latest version that has been tested in this repo (13.4.7).

Thank for looking at it. I removed the next-intl and then opened /en/abc URL. The custom [locale]/not-found.tsx gets rendered - which the expected behavior. If I try simply /abc then [locale]/page.tsx gets rendered

If I try simply /abc then [locale]/page.tsx gets rendered

Why does the page get rendered when a not-found page should match?
Did you add a middleware with a rewrite to a localized path, so that the x-middleware-rewrite: /en/abc header value gets set from Next.js when you request /abc?

I am also getting an issue where the 404 page does not work using the latest version of next13 (13.4.12) and it can be reproduce from the example-next-13 project. What I've found after trial and error is that the issue happens from next 13.4.10 and onwards.

Open next-intl/examples/example-next-13
pnpm i, pnpm dev
go to /de/unknown - this works just fine
change next version in package.json from 13.4.7 to 13.4.12
pnpm i, pnpm dev
go to /de/unknown again, this time you get an error:

Another thing to note: the jest tests pass on 13.4.7 but fail on 13.4.8.

With<EMAIL_ADDRESS>directly visiting /en/abc from browser (not navigating from within the application) renders the non-found page without any Layout. Everything works with 13.4.7, as long as the path is matched by the middleware to set the language (or with a default)

I just looked at the reproduction from @Tomekmularczyk and was able to fix it with the most recent Next.js version. It seems like the issue could be resolved by removing the root layout: https://github.com/amannn/next-intl-404/commit/8abfbc2104267bf35677018061ce0d19e6fe0a8f
The issue in the example was that both the root layout, as well as the nested layout tried to render html tags.
Do note though that newer Next.js versions have a related issue for not found pages though: https://github.com/amannn/next-intl/issues/423 (this needs to be fixed on their end).

Problem is still here with very latest version


Remove .md suffix from URLs

Without this change links on https://docs.docker.com/install/ don't work

Deploy preview for docsdocker ready!
Built with commit 0a8ca67bd589c2a2d85f749b16db7a78a9622e87
https://deploy-preview-7783--docsdocker.netlify.com

Checked https://deploy-preview-7783--docsdocker.netlify.com/install/, it looks correct now


Correction for raw affiliation Montpellier Interdisciplinary center on Sustainable Agri-food systems (MoISA) , University of Montpellier, CIRAD, CIHEAM-IAMM, INRAE, Institut Agro, IRD, 34394, Montpellier, France

Correction needed for raw affiliation Montpellier Interdisciplinary center on Sustainable Agri-food systems (MoISA) , University of Montpellier, CIRAD, CIHEAM-IAMM, INRAE, Institut Agro, IRD, 34394, Montpellier, France
raw_affiliation_name: Montpellier Interdisciplinary center on Sustainable Agri-food systems (MoISA) , University of Montpellier, CIRAD, CIHEAM-IAMM, INRAE, Institut Agro, IRD, 34394, Montpellier, France
new_rors: 0005r2j17;051escj72;04abkkz03;011xg1225
previous_rors: 0005r2j17;051escj72;04abkkz03
works_examples: W4403162626
contact: cf21f1ff7912bce0eacb6cbd300d57fa:a386a95991701cae @ supagro.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Diagnostic jump suggestion

Can lspsaga diagnostic_jump_next/prev shows all message in title ? I know Lspsaga show_line_diagnostics can show all message.
if worth to do, may provide an option to enable would be better I think, e.g. diagnostic.show_all_messages, defaults to false

vim.diagnostic.goto_next

lspsaga diagnostic_jump_next

make sense. will support next version

I had implement this.

I had implement this.

🤔 seems it is not what I expected, maybe this feature request is a bad idea.

can you show me a image or  painting a sketch  what do you expect ?

Assume this is the diagnostic_jump_next popup.

and I felt it is a bad idea because I missed the code_actions area, so many similar items look weird, even with JS eslint.

if you don't want show codeaction in jump window you can disable it .

if you don't want show codeaction in jump window you can disable it .

I know there has an option to disable 😃
just feel little weird if so many similar code actions, maybe this is not a problem.

recap
my expected like this

currently i have no idea with some ui .. so if you have some great ui you can post here  if i feel great I will implement it .

you mean the windows is not combine ?  two windows for each others?

so you mean the many code actions make you feel not comfortable ?

so you mean the many code actions make you feel not comfortable ?

just a few, but it is OK,

it's not depend on me ..server return these actions . close then ?

the list of code actions is OK now,
if I feel uncomfortable, i can close the list via lspsaga.diagnostic .show_code_action


chores: playground server codebase & dependencies cleanup

cleaned up the dependencies and codebase in the playground's server

Thanks 🙏


License?

What is the license for this code? Lack of license implies full copyright protection.

Thanks, I have added license.


Question: Is there any changes that make topology different betweent alpha and beta2?

Question

What do you want to know?
Why topology is different from previous verision(beta2), I simple run the same demo.

Is there any configuration changes should be applied ?

We do some performance improvement in beta2. But we need your data to find out what is going on.

We didn't receive any report about this yet.

What kind of data do you need ? And how ?

data.tar.gz
###ES version: 5.6.8

@peng-yongsheng Please check this.

OK, I will check it tomorrow.

any idea?

@ZhaoRuidong I checked the topology data, something wrong about the application reference index, I need to check the segment, but there is no data in segment index.

@ZhaoRuidong Can you upload a new es data contains segment data?

Here is new data contains segment data.Please check it.
data.tar.gz

Did you find anything?

Any idea?

We will take one day to locate problem in next week. All of PPMC members are busy in SkyWalking 6-alpha or nodejs agent. In this near one month, you should have time to try to fix the problem.
Anyway, we plan to do in next week.

Do your RPC client do async request? We found a bug that service reference fails when a segment has no entry span.

Could you try the master branch codes? I didn't find any other issues. And no one reports to us.


March release of Key Vault for .NET

Features

[ ] RBAC including custom role definitions
[ ] Full/selective backup/restore
[ ] AES key support
[ ] Public exponent authoring for RSA keys

Tasks

[ ] Documentation
[ ] Performance tests
[ ] Archboard API review for upcoming GA

Duplicate of #18758


wt new-tab open near current tab

Description of the new feature/enhancement
I have a Bash function that opens a tab with PowerShell in the current directory:
vspwsh ()
{
    wt new-tab --profile "Developer PowerShell for VS 2017" --startingDirectory .
}

I'd like this to place the new PowerShell tab next to the Bash tab in which I run the command.  That way, it would be easier for me to keep track of the purpose of each tab, keeping tabs near each other when they are for working on the same directory.
This is somewhat related to https://github.com/microsoft/terminal/issues/3158 but would not depend on any escape sequences emitted by the shell.
Proposed technical implementation details (optional)
Add a --near-current-tab option to wt new-tab. When specified, use the WT_SESSION environment variable to find the session, tab, and window in which the command was run, and place the new tab near that one.
If both --near-current-tab and --window are specified, then ignore WT_SESSION and instead use the selected tab of the specified window.

There is the parameter in Preview version:
"newTabPosition": "afterCurrentTab" //  or "afterLastTab"

newTabPosition is a global option

Changing the configuration via settings.json for most settings happens on the fly.
I am not against --near switch. This more convenient.
As a workaround I would add the necessary actions to function.
Something like:

# pwsh
# $WT_SETTINGS is the custom environment variable

function vsbash {
param (
    [Parameter()]
    [switch] $near
)

    if ($near)
    {
        $json = Get-Content $WT_SETTINGS | ConvertFrom-Json
        $json.newTabPosition = 'afterCurrentTab'
        $json | ConvertTo-Json -Depth 5 | Set-Content $WT_SETTINGS
    }

   wt --window 0 new-tab --profile "bash" --startdirectory "."
}

$ vsbash -near

Okay there's two thoughts here:

"I want to duplicate the current tab, but with a different profile" - #10232 (with a touch of #11913)
"I want a commandline arg for afterCurrentTab" - Yea, we can use this thread to track that request.

We might want to workshop the parameters a bit. --position feels like it should be shortened to -p, which is already used by --profile. But maybe it doesn't need to be shortened at all! wt new-tab --newTabPosition ... does seem a little redundant.
Vague todo list:

[ ] Add Position() as a member of NewTabArgs
[ ] Add --position parsing to AppCommandlineArgs

HEY ! CAN I HAVE MY HANDS ON THIS ISSUE ?

GO FOR IT! FEEL FREE TO COMMENT IF YOU HAVE ANY QUESTIONS ☺

hello
is this issue still open?

Yes.

Hello,
I'd like to take this up as my very first contribution to get into open source.
I've not done this before, and I'd really appreciate if you could help me out with getting started.
After cloning the repo and opening the OpenConsole.sln (assuming that's what I'm supposed to open) in VS2017:

How do I understand what files I should be looking out for?
How to test my changes? (I assume I need to build the application but I don't understand how to do that even after going through the CONTRIBUTING.MD)

Any pointers or links to external references would be really helpful. Thank you for your time.

As a prerequisite you need to use VS 2022: https://github.com/microsoft/terminal#prerequisites
If I remember correctly, the relevant function for new-tab insertion is this one: https://github.com/microsoft/terminal/blob/b02316b37c78fd2efefdfba676a504e816176fdf/src/cascadia/TerminalApp/TabManagement.cpp#L228
It already has an index parameter which defaults to -1 (= unspecified), so only the callers need to be updated to use the current tab-index instead.
To test your changes simply build WindowsTerminal and run it. We'll then test the changes again around the time we merge your PR.

I have seen that you can open a tab with a shortcut keybind but how do you achieve to open a new tab using wt command? Whenever I use wt new-tab, it always open a new Terminal instance.So, is there actually a different command or option to achieve this behaviour?  Thank you in advance

So, wt new-tab will obey your "New instance behavior" setting. So by default (as of 1.20), this will open a new window. But you can override that with something like wt -w 0 new-tab, where -w 0 says "run this wt command in the current window"

I'm currently working on this feature request here: https://github.com/microsoft/terminal/compare/main...nivowski:terminal:feature/wt-new_tab_position
It run with success but doesn't work when trying to pass the --tabPosition parameter(wt -w 0 new-tab --tabPosition 4):

Any help would be much appreciated

vspwsh ()
{
local near_current_tab=0
local window_id=""
while [[ "$#" -gt 0 ]]; do
    case $1 in
        --near-current-tab)
            near_current_tab=1
            shift
            ;;
        --window)
            window_id="$2"
            shift 2
            ;;
        *)
            echo "Unknown option: $1"
            return 1
            ;;
    esac
done

if [[ $near_current_tab -eq 1 && -n $window_id ]]; then
    echo "Error: Both --near-current-tab and --window cannot be specified together."
    return 1
fi

local wt_args=("--profile" "Developer PowerShell for VS 2017" "--startingDirectory" ".")

if [[ $near_current_tab -eq 1 ]]; then
    if [[ -n $WT_SESSION ]]; then
        local session_id=$(echo "$WT_SESSION" | cut -d";" -f1)
        local tab_id=$(echo "$WT_SESSION" | cut -d";" -f2)
        local window_id=$(echo "$WT_SESSION" | cut -d";" -f3)
        wt_args+=("--window" "$window_id" "--tab" "$tab_id")
    else
        echo "Error: WT_SESSION environment variable not set."
        return 1
    fi
elif [[ -n $window_id ]]; then
    wt_args+=("--window" "$window_id")
fi

wt new-tab "${wt_args[@]}"

}

Hi is this issue still open?

Hi is this issue still open?

Yep.

Hello ,Is this issue still open?


Latest release v4.8.1 not published

I'm trying to install 4.8.1, it's the latest release here on Github but https://yarnpkg.com/en/package/node-sass still lists:

latest: 4.7.2
next: 4.8.3

Can you please publish 4.8.1?

4.8.1 is broken. 4.7.2 is the latest stable. 4.8.2 is the latest unstable
On Thu., 22 Mar. 2018, 10:49 pm André Wendt<EMAIL_ADDRESS>wrote:

I'm trying to install 4.8.1, it's the latest release
https://github.com/sass/node-sass/releases/tag/v4.8.1 here on Github
but https://yarnpkg.com/en/package/node-sass still lists:

latest: 4.7.2
next: 4.8.3

Can you please publish 4.8.1?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2301, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWLh_z5HS9amAG1SZjsQbr7gNR6e2ks5tg4_WgaJpZM4S26GB
.


Fix Xcode 16 Beta warnings related to unhandled files

Exclude "PrivacyInfo.xcprivacy" files from "Pulse" and "PulseUI" targets in Package.swift.
Fix these warnings

Hey, thanks for raising this!
I would guess PrivacyInfo.xcprivacy needs to be include as resources.

Oh, my mistake. I fixed that.

That should do, thank you!


Update attachment_docusign_image_suspicious_links.yml

Adding gating for newsletters with an exorbitant amount of links

we should add high trust here too?

I thought that at first but pivoted to this because I was afraid it may cause failures from other cloud hosted senders we do trust.
I'll try adding high trust and seeing what mimic says.


Reverse Charge VAT in UK for CIS

Just wondering if there is any information on setting up reverse charge VAT for CIS (Construction Industry Scheme) and how to show the correct information on the Sales documents.

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

ID: 5e7f2fb3-10db-763b-c1dd-e9d8e3ec0070
Version Independent ID: c7cdf2cb-38fe-8eeb-d9fb-cfeb79acc5e6
Content: How to Set Up Reverse Charges on VAT - Business Central
Content Source: business-central/LocalFunctionality/UnitedKingdom/how-to-set-up-reverse-charges-on-vat.md
Service: dynamics365-business-central
GitHub Login: @edupont04
Microsoft Alias: edupont

Hello,
Thank you for your feedback! As you can see, we don't usually have detailed guidance for how to set up Business Central for specific reports and similar because that can be very dependent on specific industries or locations, for example. If you think there is a need for more detailed guidance for setting up reverse charge VAT based on CIS, you can submit a feature request here: https://aka.ms/businesscentralfeedback. Choose the "Documentation" category, and the suggestion will be forwarded to our team.

Hello,
Thank you for your feedback! As you can see, we don't usually have detailed guidance for how to set up Business Central for specific reports and similar because that can be very dependent on specific industries or locations, for example. If you think there is a need for more detailed guidance for setting up reverse charge VAT based on CIS, you can submit a feature request here: https://aka.ms/businesscentralfeedback. Choose the "Documentation" category, and the suggestion will be forwarded to our team.


Improve Qiskit visualizations tutorial if needed

Part of #1518

I think this can considered done once the following PRs get merged:

[ ] plot_bloch_multivector https://github.com/Qiskit/qiskit-terra/pull/8349
[ ] plot_bloch_vector https://github.com/Qiskit/qiskit-terra/pull/8350
[ ] plot_histogram https://github.com/Qiskit/qiskit-terra/pull/8351
[ ] plot_state_city https://github.com/Qiskit/qiskit-terra/pull/8352
[ ] plot_state_hinton https://github.com/Qiskit/qiskit-terra/pull/8353
[ ] plot_state_paulivec https://github.com/Qiskit/qiskit-terra/pull/8354
[ ] plot_state_qsphere https://github.com/Qiskit/qiskit-terra/pull/8355

I think this issue can only be considered done when the following issues are closed:

https://github.com/Qiskit/qiskit-terra/issues/8567
https://github.com/Qiskit/qiskit-tutorials/issues/1352


"ImportError: cannot import name 'getargspec' from 'inspect'" on a generic install

🐛 Bug Report
I was trying to use the package but it fails at the very first interaction. This is the result of running the healthcheck on a generic example from readme
(farcaster-analytics) ➜  farcaster-analytics python main.py
Traceback (most recent call last):
  File "/Users/wojciechkulikowski/projects/farcaster-analytics/main.py", line 2, in <module>
    from farcaster import Warpcast
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/farcaster/__init__.py", line 5, in <module>
    from .client import Warpcast  # noqa
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/farcaster/client.py", line 9, in <module>
    from eth_account.account import Account
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_account/__init__.py", line 1, in <module>
    from eth_account.account import (
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_account/account.py", line 71, in <module>
    from eth_account.messages import (
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_account/messages.py", line 25, in <module>
    from eth_account._utils.structured_data.hashing import (
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_account/_utils/structured_data/hashing.py", line 9, in <module>
    from eth_abi import (
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_abi/__init__.py", line 3, in <module>
    from eth_abi.abi import (  # NOQA
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_abi/abi.py", line 1, in <module>
    from eth_abi.codec import (
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_abi/codec.py", line 16, in <module>
    from eth_abi.decoding import (
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_abi/decoding.py", line 14, in <module>
    from eth_abi.base import (
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_abi/base.py", line 7, in <module>
    from .grammar import (
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/eth_abi/grammar.py", line 4, in <module>
    import parsimonious
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/parsimonious/__init__.py", line 9, in <module>
    from parsimonious.grammar import Grammar, TokenGrammar
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/parsimonious/grammar.py", line 14, in <module>
    from parsimonious.expressions import (Literal, Regex, Sequence, OneOf,
  File "/Users/wojciechkulikowski/.local/share/virtualenvs/farcaster-analytics-Dcob0k81/lib/python3.11/site-packages/parsimonious/expressions.py", line 9, in <module>
    from inspect import getargspec
ImportError: cannot import name 'getargspec' from 'inspect'<EMAIL_ADDRESS>
🔬 How To Reproduce
Steps to reproduce the behavior:
Follow README, try to run the health check
Code sample
from farcaster import Warpcast

client = Warpcast(mnemonic="<valid mnemonic>")

print(client.get_healthcheck())

Environment

OS: macOS
Python version: 3.11.2

@kevinj507 fyi this is using warpcast api, and moving to hubs is recommended
afaik there is no python alternative to fetching data from hubs yet

@wojtekwtf @kevinj507 Unfortunately, 3.11 is not supported right now due to this awful package, parsimonious. I'm working on a fix


[Bug]:  How to chain multiple QueryEngines

Bug Description
I need to run a complex query that requires decompositon (SubquestionQueryEngine works nicely) but also get the output with references. CitationQueryEngine works nicely as well.
however, how can i chain the output from SubquestionQueryEngine -> CitationQueryEngine as CitationQueryEngine requires a retriever as input.
My code looks like this:
query_engine = SubQuestionQueryEngine.from_defaults(
    query_engine_tools=query_engine_tools,
    response_synthesizer=response_synthesizer,
    service_context=ServiceContext.from_defaults(llm=OpenAI(model="gpt-4-0125-preview")),
    use_async=True,
    verbose=True,
)

query_engine = CitationQueryEngine(
    retriever=query_engine,
    response_synthesizer=response_synthesizer,
    citation_chunk_size=citation_chunk_size,
    metadata_mode=MetadataMode.NONE,
)

but of course this breaks on line retriever=query_engine.
Could not find a solution in the source code, thank you
Version
0.9.43
Steps to Reproduce
see above
Relevant Logs/Tracbacks
NotImplementedError: This query engine does not support retrieve, use query directly

@Dyke-F chaining these two in particular is a little difficult
You might want to either create a custom query pipeline or custom query engine
https://docs.llamaindex.ai/en/stable/examples/query_engine/custom_query_engine.html
https://docs.llamaindex.ai/en/stable/module_guides/querying/pipeline/root.html


Date Picker and Async Combobox

Hi,
Thanks for great library.
How to create datepicker and Async Combobox component ?

Hello @fortezhuo!
Datepicker component is on my roadmap, but it's not yet implemented. You can always use the Input component with type="date" though.
Regarding async Combobox please take a look here: https://rewind-ui.dev/components/combobox#on-search
You will have to add the onSearch event to get the input from the search field and filter out the combobox options based on your async call.

Hi, Thanks for the quick response.
Actually I have my own TailiwindCSS UI library, but it not maintained well and lacks of unit testing. If you want, I want to rewrite my library using rewindui code standard, and port the components into this repo.
Mine using this following libraries :

DatePicker : @rehookify/datepicker
Uploader : react-dropzone
WYSIWYG Editor : @tiptap/react
Select : downshift
Number (with thoudsand separator, decimal etc) : react-number-format

And do you have any preference 3rd party for datepicker, uploader, etc ?

I really thank you for offering to port your components to Rewind-UI!
I'm keeping an eye on the bundle size, so I try to avoid using external libraries when I can. Right now, I'm using 'floating-ui' for all the floating components like Tooltip, Popover, Dropdown and so on. 'CVA' helps with styling, and I've only used 'framer-motion' for animating the Toast component (for other animations, I've used the Web Animations API).
I prefer not to rely on additional libraries, so if you decide to port your components, just keep in mind that we'll need to build everything from scratch, except for the floating elements.
I hope this doesn't discourage you!


[cli] fix incorrect argument check for compile command

This is a follow up to #3425 where I changed the arguments for the compile command. I missed that the minimum number of arguments is now 3 instead of 4.
This also changes the help message to refer to "dependency_source_files" with underscores instead of spaces to separate the words. That is more consistent with the other messages.
Have you read the Contributing Guidelines on pull requests?
Yes

@bors-libra r=runtian-zhou

:pushpin: Commit bc2ef90 has been approved by runtian-zhou

:hourglass: Testing commit bc2ef90273fb89a1ad132190763ad4608b4cbd7b with merge a62fdd025dc6f03e5600dc86f13b787ad6c2efb4...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: runtian-zhou
Pushing a62fdd025dc6f03e5600dc86f13b787ad6c2efb4 to master...


No daily self consumption or daily grid consumption

After update to 0.3.3 I don't get any value for daily self consumption or daily grid consumption. It doesn't matter which inverter is selected or which scan level. I only get following data

Before update everything working well. My inverter is SG10KTL-M, before update SG8K-D was used. I use home assistant latest revision.

I have this issue too - the update has completely broken the energy dashboard where it used to work with 0.2.
Could someone show how to configure any sensors so that they can be used with the energy dashboard please?  I am using this with a SG8K-D.  Thanks!

I think the issue is the states are not 'total_increasing' perhaps?

Yeah, I think that is the problem too.  I tried to update the template sensor I had created, but with the change in the entities, I can't seem to get the value of the 'sensor.inverter_export_to_grid'.  I was able to do it before when it was an attribute of sensor.inverter_energy_today, but the vale is now the state of the sensor and I don't know how to convert that to a new template sensor with a class of 'total_increasing'.  My old one was like so:
  - sensor:
    - name: grid_exported_today
      unit_of_measurement: kWh
      device_class: energy
      state_class: total_increasing
      state: >
        {{ (state_attr('sensor.inverter_energy_today', 'daily_power_yield')|float - state_attr('sensor.inverter_energy_today', 'daily_energy_consumption')|float) / 1000 }}
      availability: >
        {{ states('sensor.inverter_energy_today')|lower not in ['unavailable','unknown','none'] }}

What I am trying now (which is not working) is:
- sensor:
    - name: grid_export_today
      unit_of_measurement: Wh
      device_class: energy
      state_class: total_increasing
      state: >
        {{ state_attr('sensor.inverter_export_to_grid') }}
      availability: >
        {{ states('sensor.inverter_export_to_grid')|lower not in ['unavailable','unknown','none'] }}

This is obviously wrong as it doesn't work, and I can't find any info or examples on how to achieve this.

Additional comment, maybe it helps to find a solution. I just check the mosquito broker. All necessary data will be received from the broker, incl. daily consumption (self and grit). How can I transfer this data to a HA sensor?

So I figured out getting the state value - quite easy in the end.  My new sensor looks like this:
- sensor:
      - name: grid_export_today
        unit_of_measurement: kWh
        device_class: energy
        state_class: total_increasing
        state: >
          {{ (states('sensor.inverter_export_to_grid')|float) / 1000}}
        availability: >
          {{ states('sensor.inverter_export_to_grid')|lower not in ['unavailable','unknown','none'] }}

So now I can add the grid_export_today sensor to the Energy dashboard, but even though the value is in kWh, it still seems to add to the dashboard the Wh value.  So when I export 5kWh, it looks like I am exporting 50kWh in the Energy Dashboard.
Has anyone else seen this behaviour?  As I said previously, this was working with the v2.2.1 (which I still have running on my old installation of HA), but this update seems to have changed all that...

Finally figured out what was wrong.  I had the sensor marked as Wh which I did at the start while figuring out how to get the state. When I got the state I also figured out how to divide by 1000, but I forgot to mark it as kWh when I did that so that was throwing out the values.
Also, I was able to figure out how to get the info out of MQTT:
mqtt:
  sensor:
    - state_topic: "inverter/SG8KD/registers"
      name: inverter_export_to_grid_mqtt
      unit_of_measurement: "kWh"
      device_class: energy
      state_class: total_increasing
      value_template: "{{ ((value_json.export_to_grid) / 1000) }}"

Either of these options will work.

I too have less information coming into HA after update. I had previously setup custom sensors for current power usage and solar. Can't seem to replicate in this update.

Is there a way to downgrade to the previous version? Tried restoring from backup but it seems to mix the new sensors with the old sensors. Im not sure what to try next to downgrade,.

Not sure about rolling back, but I have my sensor back to normal now and working in the Energy dashboard.  My sensors are defined like this:
mqtt:
  sensor:
    - state_topic: "inverter/SG8KD/registers"
      name: inverter_export_to_grid_mqtt
      unit_of_measurement: "kWh"
      device_class: energy
      state_class: total_increasing
      value_template: "{{ (value_json.daily_export_energy) }}"
    - state_topic: "inverter/SG8KD/registers"
      name: daily_import_energy_mqtt
      unit_of_measurement: "kWh"
      device_class: energy
      state_class: total_increasing
      value_template: "{{ (value_json.daily_import_energy) }}"

You could use this method to extract any of the MQTT returned data to make your own sensor.

Thanks, robm73.
I opened a further issue - as the iSolarCloud app was weird after updating. (disconnecting and sending incorrect data to the cloud) If I can get that issue sorted I will definitely give the MQTT sensors a go.

I found a solution for my configuration, maybe it will help others too
sensor:

platform: mqtt
name: daily export energy
unique_id: daily_export_energy
state_topic: inverter/SG8KD/registers
value_template: '{{ value_json.daily_export_energy }}'
unit_of_measurement: kWh
icon: mdi:solar-power
device_class: energy
state_class: total_increasing
platform: mqtt
name: daily import energy
unique_id: daily_import_energy
state_topic: inverter/SG8KD/registers
value_template: '{{ value_json.daily_import_energy }}'
unit_of_measurement: kWh
icon: mdi:solar-power
device_class: energy
state_class: total_increasing


Fixes #3412 - nicer container validation.

@meichstedt I did try to address your concerns in terms of a nicer looking container validation. Basically validContainer now contains validGeneralContainer, validDockerContainer and validMesosContainer. Each of those can be extended if appropriate, depending on the level of validation. The match is still needed, but should be addressed in #3388 at some point. The validation for Volume is moved to its companion object. That all reduced some redundant code. Let me know if you agree with those changes.

LGTM


Proposal to add barrier configs for showDatePicker, showTimePicker and showAboutDialog.

Overview
Add barrierDismissible, barrierColor and barrierLabel parameters to  showDatePicker, showTimePicker and showAboutDialog which calls showDialog internally.
We can change these parameters with showDialog and Dialog widgets (like DatePickerDialog, TimePickerDialog or AboutDialog) directly. But, I think it is prefer to provide interfaces same as showDialog to keep application wide unified looks if it is used internally.
Fixes #130971
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@HansMuller
Thank you for your review. I applied your suggestions on 1d67114.
And small fix on api docs. c9d5212

@justinmc
Thanks for your recommends. I separated dismissible param tests which should not depend on previous state. e6ebe3b


Reload causes cursor/selection misalignment (for @font-face fonts)

Possibly related to #3201, if you have fonts loaded through @font-face (e.g. using my fonts package), a reload causes the cursor/selection alignment to misbehave. Switching to the default font (i.e. empty the font family box in settings) restores it. You can then switch back to an @font-face font and it will work properly again.
Steps to reproduce:

Use an @font-face font as outlined here: https://discuss.atom.io/t/how-do-i-load-google-fonts-into-my-editors-styles/8321/7 (or by using http://atom.io/packages/fonts).
Put the name of the font in settings (e.g. 'aka-coder').
Open a file in Atom: all should look well in the new font.
Choose View > Reload.
Cursor and selection should now misalign. You can check this by double-click-selecting a word or by typing a row of characters.
Switch to settings.
Empty the font-family setting.
Switch to the file and all should look well again in the default font.
Switch to settings.
Put the name of the font in settings (e.g. 'aka-coder').
Switch to the file and all should look well again in aka-coder.

Hi just an FYI I experienced this in my theme and have worked around it as follows:
class MyClass
  constructor: ->
    atom.workspace.observeTextEditors (editor) =>
      editorView = atom.views.getview editor
      @remeasureCharacters editor

  remeasureCharacters: (editor) ->
    if editor?
      @viewDisposables.add editor?.onDidChangeCursorPosition (event) =>
        editorView = atom.views.getView?(event.cursor.editor)
        editorView.component?.linesComponent?.remeasureCharacterWidths?()
        editorView.component?.remeasureCharacterWidths?()
        @viewDisposables?.dispose()


Remove jQuery widgets formerly used by player controls

Logic is now encapsulated in React components.

Coverage remained the same at 99.026% when pulling d9dbb5a485917476b51da5139095a904b18f91b1 on tf:remove-dead-widgets into 3a8fb995013025668c09d6ce8edd361e3abe1fdf on codevise:master.


NotImplementedError( 'Dilated convolutions are not yet implemented')

Why DenseVnet's Dilated convolutions is not implemented , is there something that can't be solved?

Hi @adoudou2008 you're right, all components are ready -- the remaining work is to modify the network to match the convolution method's signature (https://github.com/NifTK/NiftyNet/blob/v0.3.0/niftynet/layer/convolution.py#L119), double check the dimensionalities, and make a unit test.


A few cleanups

(Not yet done) In the spirit of LazyModules, we might also want to make the final API depends on basic Base types:
xterm_24bit_encode(img; kwargs...)
xterm_24bit_encode(io::IO, img; small_block=true)

Curiously, @t-bltg I noticed that you have explicitly changed a few IOBuffer usages to PipeBuffer in many places, what's the benefit of PipeBuffer over IOBuffer?

Curiously, @t-bltg I noticed that you have explicitly changed a few IOBuffer usages to PipeBuffer in many places, what's the benefit of PipeBuffer over IOBuffer?

PipeBuffer is a simplified IOBuffer which does not support moving the position (seek, ...). It simplifies the code such as https://github.com/JuliaLang/julia/blob/c298e4ee996c4d52a0ceb17c209831042f72e6c0/test/iobuffer.jl#L152: read(io, String) for a Pipebuffer vs String(take!(io)) for a IOBuffer.

I'll continue or follow up your devs the next day, so let me merge this first.


Can't connect chest to system 1.14.4

Issue description:
Items are not send with exporter connecting chest.
I cant connect, exporter dont export but external storage connect chest directly.
What you expected to happen:
Version (make sure you are on the latest version before reporting):

Minecraft: 1.14.4
Forge: lastest
Refined Storage: 1.7.1

Latest is not a version!
Please post pictures of your setup. Have you specified what the exporter should export?

From what I can gather. Typically, the exporter will not send items to a chest or other inventory unless you have specified what items to send in the exporters filter. External storages and interfaces don't really face this problem.

i'm so confused, i mix up exporter and importer.


Fix Style/AlignParameters

I really dislike this change :( Can we make rubocop enforce a single indent instead?

"Yes, we can!"
And it's done! :smile:

Seems less bad to me. :) Thanks! @homu r+

:pushpin: Commit 57f7698 has been approved by indirect

:hourglass: Testing commit 57f7698 with merge d81bdde...

:broken_heart: Test failed - status

Same git checkout issue here as in #3889. Any ideas?


config number of rows to add when we click on add Button

#134 Add default rows to add from configuration of sheet

The screenshot is referenced in README

There are two commits in this PR. You can fixup them into one commit with

@gudipudipradeep hi, It seems like you are not familiar with git rebase. Do you need some help?

@jikoczl  yes, Am facing some difficulty to do that. Please help me

@gudipudipradeep
give a screen shot of "git log", I want to see the commit history.

@jikoczl this git log

firstly, $ git rebase -i e7986ee.
Then edit in vim, don't change the first line.Change the 2nd-5th line, change pick to f.
Esc, :wq!, Enter

@jikoczl this is the screen shot after above instructions.

@gudipudipradeep, It seems to be right.
  In case some thing wrong happen,then I can directly do something in your branch.

@gudipudipradeep , Why every time after you push your change, there will be two new commit? What command do you use to push changes?

@jikoczl  Am using GitHub Desktop while pushing changes

@gudipudipradeep , Don't use that, just use 'git push --force' .


Version 1.3.1?

First, thanks a lot for your work on nucleus.
It seems that master holds version 1.3.1, whereas "only" 1.3.0 is available using Gradle. When can we expect to see the new version available as a library from Gradle?
Thanks!

Hi, 1.3.1 changes are insignificant (mostly internal code reorganizations), so I do not plan to release it yet. The number 1.3.1. is just to differentiate it from the published version.
I'll release 1.3.1 when amount of changes will have any influence on

OK.
Just for your information, I checkout out master and it complained about
compile 'info.android15.nucleus:nucleus:1.3.1'
in
[...]/nucleus/nucleus-support-v7/build.gradle
I just wanted to experiment a little with your example using fragments and have it extend NucleusActionBarActivity instead of NucleusActivity. I got it to work with the sources in master, but not with 1.3.0. There was something about setPresenterState, but I didn't dig more into that. For now I'm perfectly fine with experimenting using the source code in master, and I hope it will work when the new version is available using Gradle.

I've tried to build yesterday, but it looks like google broke something again in their build system.
Did you read https://github.com/konmik/nucleus/blob/master/HOWTOBUILD.md ?

Thanks for your support, I'm fine for now.


TypeError in Neon Serverless Connector: Cannot Read Properties of Null (Reading 'send')

Steps to reproduce

Set up a Cloudflare Worker using the @neondatabase/serverless library.
Create a route handler that establishes a connection to a Neon PostgreSQL database but doesn’t always run queries.
Close the connection using client.end() after the route handler completes.
Trigger the route. If no data is sent over the connection, the error occurs.

Expected result
The connection should close gracefully, even if no data is sent over the WebSocket.
Actual result
The following error is thrown:
Uncaught TypeError: Cannot read properties of null (reading 'send')
It happens when the WebSocket connection is closed before buffered data can be sent.
Environment

Library: @neondatabase/serverless v0.5.7
Runtime: Cloudflare Workers
Database: Neon PostgreSQL
Framework: Custom framework with Drizzle ORM and Neon connector

Logs, links
Relevant error log:
✘ [ERROR] Uncaught TypeError: Cannot read properties of null (reading 'send')
(file:///path/to/@neondatabase/serverless/index.js:1003:65)

Code snippet where the issue occurs:
https://github.com/neondatabase/serverless/blob/da779b23b0f8e1c03e1e4036d6094076c78a5557/shims/net/index.ts#L504
setTimeout(() => {
  this.ws!.send(this.writeBuffer!); // error here
  this.writeBuffer = undefined;
}, 0);

Potential Fix
  setTimeout(() => {
     if (this.ws) {
       this.ws.send(this.writeBuffer!);
     } else {
       // Handle the case where the websocket is closed
       console.warn('WebSocket is closed before write could occur');
     }
     this.writeBuffer = undefined;
   }, 0);

Thanks for opening an issue. I'll take a look at this.

What do you think of my PR?


bugfix: Fix a bug that caused output without specifying index name

close drizzle-team/drizzle-orm#3420
Fixed a bug that caused empty index names to be output when executing the introspect command with auto-generated index names.
This fix is necessary because the specification of the index name is mandatory.
https://github.com/drizzle-team/drizzle-orm/blob/55231b0320d2a42f06a73f3cc49c4f57a8c32885/drizzle-orm/src/mysql-core/indexes.ts#L102-L108

@AndriiSherman
Would it be better to make the index names optional, as in pg-core?
https://github.com/drizzle-team/drizzle-orm/blob/55231b0320d2a42f06a73f3cc49c4f57a8c32885/drizzle-orm/src/pg-core/indexes.ts#L245-L247

@AndriiSherman
I apologize for being persistent, but have you had a chance to look into this?
If you can provide any instructions, I will make the necessary corrections.

Please fix conflicts and I'll merge this PR! thanks for your work!


[Feature request] Send an event when survey loading fails

When the network call fails while requesting a survey through sendEvent, the client is not informed. It would be useful for the clients to be informed about the failure so that an error message can be shown to the user.
Consider a scenario:

the user clicks a button to open a survey,
sendEvent fails silently and the app is not informed,
the survey does not open, nor is the user informed about an error.

Perhaps it could be a new value of InteractionEventTypes or a new type of event altogether (not sure if network failure really qualifies as interaction event?

@maciejsurmacz Thanks for this! Yea, I think adding it as an InteractionEventType would make the most sense (even if the name is quite perfect for this). I've added to our internal queue

@msingleton great, thank you, sounds good!


Lbraun/declarations/23.5

Declarations for Release 23.5

I focused on the readme, which looks fine to me.


Revenants not highlighted with Ghosts as Slayer task

          ![image](https://user-images.githubusercontent.com/6641961/228094792-520c1ab3-3016-44f8-9240-ab9b77feaa1d.png)

Hi while we're here, it looks like the code also doesn't include Revenants as listed in the wiki.
Originally posted by @brasil221 in https://github.com/runelite/runelite/pull/16427#discussion_r1149903107

Pretty sure Revenants don't actually count as a ghost for the task, meaning the wiki is wrong and RL is working as intended

Unsure where the confusion came from, but here's confirmation from just now (sry it's longer than necessary, I was gonna right click check helm immediately but got distracted lol)
https://user-images.githubusercontent.com/40111569/228346840-5f961af2-1acb-45c4-a021-bf62de579542.mp4


Consider supporting .json files as input to your viewer

Today you require gcov binary files to be produced and call "gcov --json-format" to get the code coverage data. The binary data format for gcov is private AFAIK and only produced by gcc.
Would you consider offering option to open a json file as well (following same format that --json-format provides)?  This would enable your code coverage viewer to be more interoperable with other tools.

Do you have any specific tool in mind that outputs the same json format? Sounds like something that can be supported.

One that I am writing now :) I like that you are integrated in VS code and you show hit count information. Visual Studio's coverage viewer doesn't show hit counts in source code, for example.

In that case it would be best if you can create a patch for this extension because you are in the best position to test it.


How to install this?

Hi
I'm new to nix, it would be nice to have a oneliner on how to install this nix package for newcomers like me 😅 I already have nix installed
EDIT: I figured out you can install it using nix-env -i -f https://github.com/Shopify/comma/tarball/master

Also new to nix here so this could be wrong... but if you are using home-manager this seems to work:
{ config, pkgs, ... }:

let
  comma = import ( pkgs.fetchFromGitHub {
      owner = "Shopify";
      repo = "comma";
      rev = "4a62ec17e20ce0e738a8e5126b4298a73903b468";
      sha256 = "0n5a3rnv9qnnsrl76kpi6dmaxmwj1mpdd2g0b4n1wfimqfaz6gi1";
  }) {};

in

{
  home.packages = with pkgs; [
    comma
  ];
}

i have added instructions to the readme


High CPU usage due to glGetIntegerv

SFML v2.6 - Windows 11 - Nvidia 531.26
Using a RenderWindow with vsync enabled (60hz monitor).
Problem: CPU usage spikes up and stresses a cpu core whenever imgui renders something. I narrowed it down to the calls to glGetIntegerv in void RenderDrawLists(ImDrawData* draw_data). The first of these calls will do a cpu-wait of 16ms and will cause huge CPU usage on the main thread.
I confirmed it by commenting out all these calls (and the related context-restoring code at the end of the function), and the CPU usage went back to 0%. I understand that I lose the GL context saving/restoring functionality by doing that but I prefer it over the high CPU usage.
I don't really expect it to be fixed (I guess the main app should pass those parameters to imgui-sfml rather than doing those calls to glGetIntegerv), but putting it out there for anyone wondering why their imgui-sfml usage has a high CPU impact.

You can reimplement the rendering function yourself (you can access everything needed for that) and let ImGui-SFML take care of the rest.
State restore is kinda wasteful, but Dear ImGui does the same here and it leads to much easier interface for most users. More advanced users can implement the rendering as needed themselves.


Fix cache

hmm github.job.name is not a thing, I believe :sweat_smile:

Ubuntu 22 is failing because of this damn issue I don't get:
Run sudo apt-get install --reinstall -y libudev1 libsdl2-dev
Reading package lists...
Building dependency tree...
Reading state information...
Reinstallation of libudev1 is not possible, it cannot be downloaded.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
 libudev-dev : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.1 is to be installed
E: Unable to correct problems, you have held broken packages.
Error: Process completed with exit code 100.


[10.0][bug] website_sale_store_checkout save address throw exception

Odoo 10.0 seems to have changed signature for checkout_form_validate method
How to reproduce:

install addon
add some product to cart
go to checkout page
choose any checkout method (this leads to address page)
edit address
save address

Bechavior before:
Exception raised:
2017-05-25 10:47:07,877 5698 ERROR test-10.0 odoo.addons.website.models.ir_http: 500 Internal Server Error:

Traceback (most recent call last):
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/addons/website/models/ir_http.py", line 264, in _handle_exception
    response = super(Http, cls)._handle_exception(exception)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/addons/base/ir/ir_http.py", line 169, in _handle_exception
    return request._handle_exception(exception)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/http.py", line 766, in _handle_exception
    return super(HttpRequest, self)._handle_exception(exception)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/addons/base/ir/ir_http.py", line 195, in _dispatch
    result = request.dispatch()
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/http.py", line 825, in dispatch
    r = self._call_function(**self.params)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/http.py", line 331, in _call_function
    return checked_call(self.db, *args, **kwargs)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/service/model.py", line 119, in wrapper
    return f(dbname, *args, **kwargs)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/http.py", line 324, in checked_call
    result = self.endpoint(*a, **kw)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/http.py", line 933, in __call__
    return self.method(*args, **kw)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/odoo/http.py", line 504, in response_wrap
    response = f(*args, **kw)
  File "/home/katyukha/projects/OpenERP/odoo-10.0/odoo/addons/website_sale/controllers/main.py", line 575, in address
    errors, error_msg = self.checkout_form_validate(mode, kw, pre_values)
TypeError: checkout_form_validate() takes exactly 2 arguments (4 given)

Bechavior after
Addess normally saved

Thank you


Add CSS transform scale example to Toggle documentation

Added example using CSS transform: scale(...) to resize the Toggle component.

It might be useful to add a note somewhere more general in the docs to remind people about CSS transforms. It's one of those things that people generally don't use very often so we tend to forget.
Docs: CSS Transforms

Hey @iansinnott , thanks a lot. We will soon check this out.

Thanks a lot @iansinnott

Happy to help. When I first found Belle I completely forgot about transforms and this would have been exactly what I needed :grin:


Could this be used for a better quality audiolm

❓ Questions
within the soundstream paper, the google team used the residual vector quantization model to generate music.
I was wondering since the architecture is very similiar if you guys have thought about using it to generate music.
I've tried openai's jukebox and the output is fairly noisy.
Kudos on this great work!

You might want to check this as well https://github.com/zhvng/open-musiclm

audiolm  added the encodec weights to audiolm


Istio ingress gateway high CPU usage on VS/G update

Bug description
I noticed on Istio 1.6.14 that if you create a VS with G having a lot of hosts (~2k) the CPU of the istio-ingressgateway pods starts to jump on changes from ~10 to ~600 millicores. The cluster has almost no traffic (it's a test one), the # of pods having istio-proxy is 9.
Previously using 1.6.2 on production it led to downtime when we were sequentially adding new hosts to the same VS and G. Although that seems to be fixed by https://github.com/istio/istio/pull/27269 the CPU usage is still high.
[ ] Docs
[ ] Installation
[ ] Networking
[x] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
I am just interested if this CPU usage is expected, it seems to me too high. Or maybe there is a way to reconfigure the G or VS or anything in Istio to calm it down.
Steps to reproduce the bug

Have a cluster with istio 1.6.14 installed
Deploy any service (let's call it tech-radar) to a default namespace, make sure the namespace has the istio injection label.
Run the following Ruby script having access to cluster test_istio_ingress.rb with ruby test_istio_ingress.rb

# frozen_string_literal: true

require 'erb'
require 'faker'
require 'open3'

VS_TEMPLATE = <<~EOF
  apiVersion: networking.istio.io/v1beta1
  kind: VirtualService
  metadata:
    name: test-vs
    namespace: default
  spec:
    gateways:
      - default/test-gateway
    hosts:
      <%= hosts.map{|x| "- \#{x}"}.join("\n" + indent(2)) %>
    http:
      - match:
          - uri:
              prefix: /
        retries:
          attempts: 0
        route:
          - destination:
              host: tech-radar
              port:
                number: 80
        timeout: 30s
EOF

G_TEMPLATE = <<~EOF
  apiVersion: networking.istio.io/v1beta1
  kind: Gateway
  metadata:
    name: test-gateway
    namespace: default
  spec:
    selector:
      istio: ingressgateway
    servers:
      - hosts:
          <%= hosts.map{|x| "- \#{x}"}.join("\n" + indent(4)) %>
        port:
          name: http
          number: 80
          protocol: HTTP
EOF

def indent(n)
  '  ' * n
end

def generate_host
  Faker::Internet.domain_name
end

def generate_hosts(n)
  n.times.map { generate_host }
end

def update_vs_and_g(hosts)
  vs = ERB.new(VS_TEMPLATE).result(binding)
  g = ERB.new(G_TEMPLATE).result(binding)
  File.write('vs.yaml', vs)
  File.write('g.yaml', g)
end

def exec_command(cmd)
  o, e, s = Open3.capture3(cmd)
  $stdout.write o
  $stderr.write e
end

def apply
  exec_command 'kubectl apply -f vs.yaml'
  exec_command 'kubectl apply -f g.yaml'
end

hosts = generate_hosts(2000).uniq

def add_one(hosts)
  hosts << generate_host
  hosts.uniq!
end

loop do
  update_vs_and_g(hosts)
  apply
  add_one(hosts)
end

Check the CPU usage of istio-ingressgateways

Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
$ istioctl version --remote
client version: 1.6.14
control plane version: 1.6.14
data plane version: 1.6.14 (12 proxies)
$ kubectl version --short
Client Version: v1.18.8
Server Version: v1.16.15-eks-ad4801
$ helm version --short
v3.2.4+g0ad800e

How was Istio installed?
Istio was installed with istioctl without installing IstioOperator in the cluster, so with istioctl install -f operator.yaml
Environment where the bug was observed (cloud vendor, OS, etc)
AWS EKS 1.16

What is the real use case? I assume you are not actually constantly switching 2000 hosts every second in the real world?
Is the goal to have going from 0 -> 2000 be cheaper? Constantly changing a few hosts (eg 1999 -> 2000 -> 1999 -> 2000, etc)? Or do you really need a complete change of 2000 hosts

From time to time the list of hosts changes, let's say several times a day, and it's just adding or removing entry to/from the list of hosts. During each change we notice the CPU raise of the ingressgateway pods.


Add remove duplicates implementation

Adds implementation for removeDuplicates in lib/textTransformations.js
Fixes #15

I see tests were added in https://github.com/swanandapps/stringy-core/pull/42


Add a prototype UI

All dashboard UI code is in the dashboard directory.
Uses esbuild to build the project.  No config and builds are fast.
Uses preact for the UI components, like react but smaller and simpler.  This gives us more room for larger paper data JSON.
Uses http-server and livereload for the watch task.
Most UI components are just pure functions.
The data build would populate the data Store.
Next steps:

UI improvements: Mobile support, misc. TODOs in code, etc.
Manual import of data into the data store for testing & evaluation.

@jvwong, this is ready for your addition of the manual data import into the data store.

Screenshots:

I added some topics around Alzheimer's disease.
Topics
A couple of flavours here. (1) "Alzheimer's Disease" is meant to be generic, catch-all (2) Others are meant to provide more focus, and these sub-topics were inspired by review articles, manually selected based on some cursory reading of the topic.

Article retrieval (/scripts)
I show a max of 20 articles per topic, ordered by date.

search.sh

This collection is under topic "Alzheimer's Disease"
Uses the existing downloads.js/search.js modules for all bio/medrxiv articles (q=alzheimer) available between 2022-10-01 and 2022-10-31

recommendations.sh
These collections are under the remaining sub-topics
Uses Semantic Scholar 'Recommendations' API to retrieve similar articles to a seed (review article)
Filtered for only biorxiv and medrxiv articles (there are many others in the raw feed)
A summary natural language brief (aka tldr) accompanies records, when available

Analysis
How much overlap is there between topics?

alzheimer-disease
alzheimer-diagnosis
alzheimer-neuroinflammation
alzheimer-therapeutics

alzheimer-disease
94
8
6
6

alzheimer-diagnosis

24
4
5

alzheimer-neuroinflammation

25
5

alzheimer-therapeutics

15


fix: Use posthog.api to fetch and create annotations

This app has been broken for quite some time by the changes to our API, which a number of users noted in #14. To fix this, I've gone through and used the posthog.api util to fetch and create annotations, along with a number of other changes.
Changes

Swap fetch calls for posthog.api util when fetching/creating annotations
Uses runEveryHour instead of runEveryMinute - Previously we had custom logic to make this behave like runEveryHour
Removes the config checks in setupPlugin - Feel free to let me know if you think this should still be here, but I feel I remember Karl noting that we should try and avoid network requests in setupPlugin. May be totally misinterpreting this though!
Changes to use Typescript

Closes #14

The reason this used runEveryMinute in the first place is to avoid this effect:

Enable plugin
Wait for stuff to happen
...
???
Profit!?

Unless there's a job to manually trigger with instructions on how to do so, you will have really slow feedback when enabling this plugin.

Ahhh that makes sense, totally agree now that you mention it. I'll go back and re-enable this 👍

Is there any update on this please? Just enabled the plugin and hitting the issue detailed in #14

I've gone through and tested this myself and given that the app is completely broken right now I'm going to merge this 👍

what is the process for this becoming available in Posthog Cloud instance? Does a build/release get automatically kicked off, it take from main by default, or anything more manual I need to do?


Could not resolve dependency npm<EMAIL_ADDRESS>from<EMAIL_ADDRESS>

Could not resolve dependency npm<EMAIL_ADDRESS>from<EMAIL_ADDRESS>

same error


Implement DeleteBranch method for git clients

This is a prerequisite of #219

Closing as GitHub does not support DeleteBranch via http api
Further research is needed to do this


Full screen mode doesn't work in Chrome. Works in Firefox.

I took the API example at https://pannellum.org/documentation/examples/simple-example/ and use it locally on my machine. When I switch to full screen mode. I get the same image in the middle of the screen with the same original size. It doesn't expand to fill the screen. I used Chrome and Canary without extensions and same result.
The same sample works fine in Firefox.
Any ideas?

This is a regression I introduced a few days ago in c22ac5d6fe7de2a8178b82bd8dfd09bed717a9d1. I just fixed it in a0b239066d347e3b7a9a0f11c05a4a235dbc155c.

I am still facing a similar issue with the latest version 2.3.2
I am using the javascript references to load the image within a div tag. However when i switch to Fullscreen mode the pano shows up as a thin bar in the  centre of the screen instead of the full screen.
This again happens on chrome and not in firefox.
refer attachment for example.
Please Help

Do you have an example page that demonstrates this behavior? I can't be of any help without more information.

Hello,
I have the same problem. You can see it in : http://impulsoyweb.com/desarrollos/vr/ and click "Pantalla Completa" in the menu. That works in firefox, but doesn't work in chrome.

@jogerq Your issue is because you set position: absolute on #panorama1. It's unrelated to this (resolved) bug.

Thank you!

Is there a solution for the problem if i set position: absolute on #panorama?
Is there a workaround?

@olaf100: The easiest solution comes to mind being changing position from absolute to static in case of full screen event and back when full screen is left.


About influenceof  flash attention

Dear Author,
Thank you for open-sourcing such a great piece of work. Could you please elaborate on the extent to which flash attention can bring speed and memory efficiency improvements to PTv3?
Additionally, you mentioned that "FlashAttention force disables RPE and forces the accuracy reduced to fp16". Will the reduction in attention precision from fp32 to fp16 have a significant negative impact?
Thank you!

Typically not, but in very rare cases may cause NaN.


Create name switch basics

Add the .py extension to the file and make sure it is in the Python Programs folder


[BUG] error running quickstart/title_en.py

I've just installed the package locally and ran test code quickstart/title_en.py and got the following issues.
Any possible reasons?  thanks!! see detail below

skys-MacBook-Pro:quickstart sky$ python3 title_en.py
******************** title-generation 100013 bert-base-en
Traceback (most recent call last):
File "title_en.py", line 29, in
print(predictor.predict_generate_beamsearch(text, out_max_length=50, beam_size=3))
File "../flagai/model/predictor/predictor.py", line 231, in predict_generate_beamsearch
return bert_beamsearch(self.model,
File "../flagai/model/predictor/utils.py", line 676, in bert_beamsearch
out_puts_ids = bert_beam_search(model,
File "../flagai/model/predictor/utils.py", line 280, in bert_beam_search
scores = bert_predict_generate(model, new_input_ids,
File "../flagai/model/predictor/utils.py", line 235, in bert_predict_generate
score = model(**{
File "/Users/sky/Library/Python/3.8/lib/python/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "../flagai/model/bert_model.py", line 359, in forward
encoder_out, pooler_out = self.model(
File "/Users/sky/Library/Python/3.8/lib/python/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "../flagai/model/bert_model.py", line 153, in forward
extended_attention_mask = extended_attention_mask * attention_mask
RuntimeError: The size of tensor a (3) must match the size of tensor b (171) at non-singleton dimension 2

ran title_cn.py got similar error
File "/Users/sky/Library/Python/3.8/lib/python/site-packages/flagai/model/layers/attentions.py", line 940, in forward
attention_scores += attention_mask
RuntimeError: output with shape [1, 12, 90, 90] doesn't match the broadcast shape [1, 1, 1, 12, 90, 90]

Thank you for your question, I will get back to you as soon as possible.