check device format while initialising litserver

Before submitting

[ ] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

What does this PR do?
Adds a check in the lit server init to ensure device names are correct.
Before, a user could initialize a server like so
server = ls.LitServer(
        api, spec=ls.OpenAISpec(), devices="cpu"
    )

and this would result in a device list of
[['cuda:c'], ['cuda:p'], ['cuda:u']]

With this PR, we add a check which informs the user that these are invalid device names.
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Thanks for the PR @ali-alshaar7! Looking good. Small nit - We have a connector.py module which contains device based logics, it might be better to move this function there.


Allow dependabot to upgrade database versions used in integration tests

In the storage integration tests we run backends using Docker images. The versions for those images are hardcoded in various places:

sometimes in the GH workflow https://github.com/jaegertracing/jaeger/blob/584b6ffa96726367177a66d653a9b39773c47bef/.github/workflows/ci-elasticsearch.yml#L28
sometimes in the shell script https://github.com/jaegertracing/jaeger/blob/584b6ffa96726367177a66d653a9b39773c47bef/scripts/kafka-integration-test.sh#L21
maybe somewhere else

None of these places are supported by the dependabot, so we're not getting regular upgrades and not testing via the latest versions of the storage backends.
One solution could be to use docker-compose files to bring the databases up instead of running a docker command directly. E.g. we could have docker-compose-elasticsearch-v7.yaml and docker-compose-elasticsearch-v8.yaml and simplify the matrix in the workflow to only specify the major version and then pick the right file at runtime. Then wen can configure dependabot to look at those docker-compose files where it should be able to upgrade the versions as needed.
We could try it with opensearch and see if dependabot will upgrade the versions. We also need to be careful to prevent dependabot from upgrading the major version, e.g. integration test against v1.x of opensearch should continue running against v1.x (whichever the latest release is for that major), not bump it to v2.x which is the absolute latest across majors.
Tracker

[x] Elasticsearch/opensearch #5490
[ ] Kafka
[ ] Cassandra

@yurishkuro can you assign me this issue I would also like to work on Kafka and Cassandra ci


Load based split related metric data in grafana is not consistent with dashboard.

Bug Report

What version of TiKV are you using?

/ # /tikv-server -V
TiKV
Release Version:   4.0.15
Edition:           Community
Git Commit Hash:   0a0482dee0a0cf135f56b9f90b412ea641ec3ae2
Git Commit Branch: heads/refs/tags/v4.0.15
UTC Build Time:    2021-09-13 02:21:39
Rust Version:      rustc 1.42.0-nightly (0de96d37f 2019-12-19)
Enable Features:   jemalloc mem-profiling portable sse protobuf-codec
Profile:           dist_release
What operating system and CPU are you using?

Steps to reproduce

Run test #pd-re-schedule-01#, found there is no load based split even generated show in grafana, while there is in dashboard.

What did you expect?
Grafana should use same data with dashboard.
What did happened?
There is something wrong with the data in grafana.

/severity Moderate
/assign @lhy1024


export htmlWriter for use with Reader/Writer

As Parser is exported, it doesn't seem to make sense to not also export htmlWriter, as it seems to be required to use the parser.

htmlWriter is intended to just be the internal implementation of ConvertToHTML[WithClasses]; Parser only interacts with it through the escapeHandler func passed to Parse, so if you want to output a different format, creating a new implementation with an escapeHandler is the intended way.  If you need more customization or more escape support in the HTML converter, I'd rather that be done as a PR to this library than forcing downstream consumers to reimplement portions of htmlWriter.


Support custom ports for the backend service of an Ingress path. Support exposing multiple ports under different paths.

Right now we always set the backend service port of an ingress path to the default port:
https://github.com/konveyor/move2kube/blob/0a6db0083e27350c05c83219fc5820da3ddc2841/internal/apiresource/service.go#L413
Add support for setting a custom port.
Use case: preserving ports while translating docker compose and old k8s projects.

@HarikrishnanBalagopal This issue is fixed in the latest release, isn't it?


flutter version 2.5 -> 2.8  . Compile error error

Steps to Reproduce

run  flutter upgrade upgrade the FlutterSDK version.
then
run flutter doctor

When I try to run it ，is error。

I tried to flutter clean and dart pub cache clean. But the result is the same

Logs

I solved the problem .
add pubspec extended_image: ^6.0.1

add pubspec extended_image: ^6.0.1


basic-auth-password | Remove the use of atob

Description

This sample has been modified by #247 to use atob, but the function is now flagged as deprecated.

IDE

Also, in the current Next, ArrayBuffer works with edge runtime, so reverting to the original works fine.
edge doc: https://nextjs.org/docs/api-reference/edge-runtime#web-standard-apis
Since this sample is often referenced, I thought it would be better to modify it rather than wait.
Demo URL

Type of Change

[ ] New Example
[x] Example updates (Bug fixes, new features, etc.)
[ ] Other (changes to the codebase, but not to examples)

New Example Checklist

[ ] 🛫 npm run new-example was used to create the example
[ ] 📚 The template wasn't used but I carefuly read the Adding a new example steps and implemented them in the example
[ ] 📱 Is it responsive? Are mobile and tablets considered?

I apologize for the confusion caused by the misunderstanding.

@lfades
Since the Buffer yesterday is now supported, can we leave from atob? (I already deleted the forks😖).


Update to new foundry.toml schema

Running make build will print this warning:
warning: Unknown section [ci] found in foundry.toml. This notation for profiles has been deprecated and may result in the profile not being registered in future versions. Please use [profile.default] instead or run `forge config --fix`.

Fix by running:
forge config --fix

Thanks! Fixed in commit https://github.com/cleanunicorn/mockprovider/commit/0cbe4c14987920653b28244fc0608aafccf4307c


Fix DevTools style list not updating correctly

What does the pull request do?
Changes the way the DevTools register for class change notifications so they are updated after the actual style instances.
What is the current behavior?
The DevTools style list currently does not update properly when the pseudo classes of the selected control change.
What is the updated/expected behavior with this PR?
The style list now shows the correct styles as active.
How was the solution implemented (if it's not obvious)?
The issue was that Avalonia.Diagnostics.ViewModels.ControlDetailsViewModel.UpdateStyles was run before the actual StyleInstance's IsActive property was updated, so the DevTools were always lagging one update behind.
The stack traces revealed that the two notification paths diverged in Avalonia.Controls.Classes's implementation of Avalonia.Controls.IPseudoClasses.Add. The DevTools used to hook directly into the AvaloniaList's CollectionChanged event, while the style instance is notified through a style activator, which is registered as a ClassesChangedListener and therefore gets notified later.
The fix was simply to make ControlDetailsViewModel receive updates via an IClassesChangedListener instead of through the backing list's CollectionChanged event.
I don't think any of the checklist items below are applicable, but let me know if anything is missing. I also included a second commit with some typo fixes. Not sure if this is the right place for them.
Avalonia.Diagnostics.dll!Avalonia.Diagnostics.ViewModels.ControlDetailsViewModel.UpdateStyles() Line 342	C#
Avalonia.Diagnostics.dll!Avalonia.Diagnostics.ViewModels.ControlDetailsViewModel.OnClassesChanged(object sender, System.Collections.Specialized.NotifyCollectionChangedEventArgs e)
Avalonia.Base.dll!Avalonia.Collections.AvaloniaList<string>.NotifyAdd(string item, int index)
Avalonia.Base.dll!Avalonia.Collections.AvaloniaList<string>.Add(string item)
Avalonia.Base.dll!Avalonia.Controls.Classes.Avalonia.Controls.IPseudoClasses.Add(string name)
Avalonia.Base.dll!Avalonia.Controls.PseudolassesExtensions.Set(Avalonia.Controls.IPseudoClasses classes, string name, bool value)

Avalonia.Base.dll!Avalonia.Styling.StyleInstance.ActivatorChanged(bool value)
Avalonia.Base.dll!Avalonia.Styling.StyleInstance.Avalonia.Styling.Activators.IStyleActivatorSink.OnNext(bool value, int tag)
Avalonia.Base.dll!Avalonia.Styling.Activators.StyleActivatorBase.PublishNext(bool value)
Avalonia.Base.dll!Avalonia.Styling.Activators.StyleClassActivator.Avalonia.Controls.IClassesChangedListener.Changed()
Avalonia.Base.dll!Avalonia.Controls.Classes.NotifyChanged()
Avalonia.Base.dll!Avalonia.Controls.Classes.Avalonia.Controls.IPseudoClasses.Add(string name)
Avalonia.Base.dll!Avalonia.Controls.PseudolassesExtensions.Set(Avalonia.Controls.IPseudoClasses classes, string name, bool value)

// From src/Avalonia.Base/Controls/Classes.cs, line 284
void IPseudoClasses.Add(string name)
{
    if (!Contains(name))
    {
        base.Add(name);     // DevTools view model was updated here
        NotifyChanged();    // StyleInstance.IsActive is updated here
    }
}

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Fixed issues
Fixes #9382

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

You can test this PR using the following package version. 11.0.999-cibuild0025966-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0025976-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


double-beep: Watch sharktankreview.com

double-beep requests the watch of the watch_keyword sharktankreview\.com. See the MS search here and the Stack Exchange search here.

sharktankreview\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


In the new designer, cannot see the details of certain actions in the Standard Logic App run

Describe the Bug with repro steps
Customer cannot see the details(Inputs and Outputs) of certain actions in his Standard logic app run in the new designer
Error :
'Unable to initialize operation details for swagger based operation - When_Update_System_is_Triggered. Error details - Unsupported domain @Microsoft.KeyVault(SecretUri=https: in batch call. Only ARM endpoints are supported in batch.'
In the old designer, he can see the details fine.
What type of Logic App Is this happening in?
Standard (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos

Browser
Chrome
Additional context
No response
AB#24529444

Hi @PremPandeyyy, thanks for the bug report, could you provide us with which connectors and actions you're having trouble with, as well as a network trace of you loading your workflow?  You can find steps on how to retrieve the network trace in our documentation here:
https://purple-pebble-0e11de71e.1.azurestaticapps.net/tsg#collecting-network-logs-in-a-har-file
Once you have the network trace .har file you can send it to me at<EMAIL_ADDRESS>

Hello @rllyy97
Customer's comment on what connectors and actions having issue -
"In that specific case the connector is the Dataverse List connector. But in truth it happens with any connector that uses an API connection that is dynamically set during our infraestructure deployments (hence the error message “@Microsoft.KeyVault(SecretUri=https”)."
I will send you the network trace and console logs shortly.

@prempandeyyy Just to keep you updated, I've spent some time looking into this and I haven't been able to figure out how to reproduce this issue.  I also looked at the .har file and it's not showing any errors.  I am still working on this though and will give more info when I have it.

@PremPandeyyy, can you request the workflow definition the customer is using when seeing this error?
Also can you get the connection json for the operation's connection?  I'm guessing they have an appsetting defined somewhere in the connection object and I want to know where it is so I can try to repro their exact configuration.
You can just email it to me instead of posting it here.

@PremPandeyyy We just merged a change that I think might fix this customer's issue.  If the key vault reference was held in an app setting reference in their connection, they should see this issue fixed after our next deployment that should be live by March 1st.
If you're still in contact with the customer about this issue, if they are still experiencing it after March 1st feel free to reopen this ticket with more details.


Movement bug when resizing  trough drag on top.

When dragging for resizing it follows the mouse movement.
This happens while the client loads up and possibly in other places.
OS was Windows 10 and client was a binary one from slack.

Could you try to explain it again I did not get it :(?

When the client starts there is a loding time.
In this time i wanted to resize the window.
When i resized the window by dragging from top border it moved and resized in height.
So when i started resizing the bounds were like  x:300 y:100 w:400 h:600.
After resizing it was about x:300 y:183 w:400 h:517.
While resizing it moved the window by the same amount the window got resized.
I think it could be resize and drag at the same moment.

When resizing beyound the min sitze of the window this is whats happening but thats not bad is it?

The only case we can reproduce is that the height stays at 600px when resizing because we currently don't allow the window to be made smaller than the minimum size required to display all content.
The same thing happens if you resize in width from the left edge.
It might be possible to fix but as this has pretty much no effect on the client's usability it has such a low priority that it will probably never happen :)
However, we could reconsider whether we allow arbitrary client sizes. IIRC, I did that back in time but some users complained about it.

Fixed in 0.9.0-beta


As an operator, I want to be able to monitor the status of a given Workflow Execution at per-step resolution

evaluate in Airflow

Airflow does do per-step monitoring.
evaluation is in https://github.com/unity-sds/unity-jobs-ui/issues/32
closing this one

will mark done as we're using Airflow


Upgrade to jQuery 3

Are we really going to support IE6?  Really?

Updated the title as there has been another major release of jQuery. Also there has been a new major release of jQuery UI nestedSortable, and a new release of jQuery UI. jQuery hotkeys is no longer under development, there is a fork but that is also inactive since Nov 2015.


Could not locate the bindings file

I am getting the following error
C:\electron-boilerplate\build\node_modules\bindings\bindings.js:91 Uncaught Error: Could not locate the bindings file. Tried:
 → C:\electron-boilerplate\build\node_modules\zmq\build\zmq.node
 → C:\electron-boilerplate\build\node_modules\zmq\build\Debug\zmq.node
 → C:\electron-boilerplate\build\node_modules\zmq\build\Release\zmq.node
 → C:\electron-boilerplate\build\node_modules\zmq\out\Debug\zmq.node
 → C:\electron-boilerplate\build\node_modules\zmq\Debug\zmq.node
 → C:\electron-boilerplate\build\node_modules\zmq\out\Release\zmq.node
 → C:\electron-boilerplate\build\node_modules\zmq\Release\zmq.node
 → C:\electron-boilerplate\build\node_modules\zmq\build\default\zmq.node
 → C:\electron-boilerplate\build\node_modules\zmq\compiled\6.1.0\win32\x64\zmq.node

I have tried reinstalling, building, etc. many many times. The weird thing is that the file actually does exist at the one of the paths it is searching. Any ideas?

Same error here.

Windows 7 (x64)
ZMQ 4.04 (x64)
Electron 1.3.2 (x64)
Node.js 6.3.0 (x64)

I had the same issue, I installed the package with npm install --save zmq and after that echo 'require("zmq")' | node resulted in the error above.
The following fixed it for me:
cd node_modules/zmq/; node-gyp configure

I think there could be something wrong with this package. Possibly related to #534.
My system runs archlinux and I just noticed I also have the following value in my npmrc, as this was suggested as a security workaround a while ago.
ignore-scripts=true

In my case, loading into ElectronJS (https://github.com/electron/electron) is not successful. I guess this is because Electron uses a self built node.dll. I need to build Electron and ZMQ using the same Node binary. I'm still on the investigation. Here is a potential solution ongoing. https://github.com/nteract/zmq-prebuilt/issues/2

Does this problem have a solution?

The issue was fixed in https://github.com/zeromq/zeromq.js


feat: impl albums

add InputMedia struct.
add send_album, reply_album and respond_album methods.

Isn't InputMedia just a smaller version of InputMessage? Why not use InputMessage?

Yes, but this was deliberate, because not all messages are valid for album media.
I think a new type is justified, because albums require media to be set, while InputMessage don't. We would have to add even more validations, and then return Err, and the current Error type used by the client methods is already complex enough. So I'm not sure it's worth reusing the type.
What I did consider however, was using InputMedia for attaching it to the InputMessage. But that's a different problem entirely.


The road to Fresh 2.0

The road to Fresh 2.0
tl;dr: Fresh will become massively simpler and be distributed via JSR with the upcoming 2.0 release. Express/Hono-like API and true async components and much more.

Back to Fresh!
Since yesterday, I've been going back to working on Fresh again. During the past few months I helped with shipping https://jsr.io/ which meant that Fresh sat on the back burner for me. Admittedly, I needed a bit a break from Fresh as well, and JSR came along at the right time.
Working on JSR allowed me to put myself into the user's seat and get first hands experiences with Fresh as a user, which was nice change! It also uncovered a lot of things where I feel we can make Fresh much better.
With JSR beeing out of the door, the next task for me is to move Fresh over from deno.land/x to JSR. Given that this is a bit of a breaking change, @lucacasonato and I were wondering what a potential Fresh 2.0 release could look like.
We've never done a breaking Fresh release before, but now, after having worked for nearly a year on Fresh, the timing feels right. It allows us to revisit all the ideas in Fresh and part ways with those that didn't pan out.
We spent yesterday morning going through the most common problems people shared on Discord and in our issue tracker to get a good picture of where Fresh is at. The overall theme we want to have for Fresh 2, is to be massively simpler than before.
A new plugin API
It became pretty clear that many issues relate to the "clunkyness" of the current plugin API. It's the most common way to extend Fresh itself with capabilities that it doesn't include out of the box. Whilst it received many cool new features over time, it quite never felt elegant as it should be. This is no surprise given that nothing in Fresh itself makes use of it.
Back in July of last year there was some explorations on making Fresh's API more express/Hono-like https://github.com/denoland/fresh/issues/1487 and yesterday we realized that this is the perfect solution for nearly all the problems encountered with the current plugin API. Here is what we're picturing it to look like:
const app = new FreshApp();

// Custom middlewares
app.use(ctx => {
  console.log(`Here is a cool request: ${ctx.url}`)
  return ctx.next();
});

// Also can be branched on by HTTP method
app.get(ctx => {
  return new Response("it works!")
});

// Adding an island (exact function signature yet to be determined)
app.addIsland(...)

// Finally, start the app
await app.listen();

A Fresh plugin would change from the complex object it is today, to being nothing more than a standard JavaScript function:
function disallowFoo(app: App) {
  let counter = 0;

  // Redirect to / whenever a route contains
  // the word "foo".
  app.use((ctx) => {
    if (ctx.url.pathname.includes("foo")) {
      counter++;
      return ctx.redirect("/");
    }

    return ctx.next();
  });

  // Add a route that shows how many times we
  // redirected folks
  app.get("/counter", () => {
    const msg = `Foo redirect counter: ${counter}`;
    return new Response(msg);
  });
}

// Usage
const app = new FreshApp();

// Adding the plugin is a standard function call
disallowFoo(app);

await app.listen();

The beauty about this kind of API is that many features in Fresh are a just standard middleware, and the more complex ones like our file system router and middleware handler would just call methods on app. The internals of Fresh will be implemented the exact same way as any other plugin or middleware. This eliminates the mismatch of the current plugin API and the Fresh internals of today.
Simpler middleware signature
The current middleware signature in Fresh has two function arguments:
type Middleware = (req: Request, ctx: FreshContext) => Promise<Response>;

In most of our code we noticed that we rarely need to access the Request object. So most of our middlewares just skip over it:
// We don't need _req, but still need to define it...
const foo = (_req: Request, ctx: FreshContext) => {
  // Do something here
  const exists = doSomething();
  if (!exists) {
    return ctx.renderNotFound();
  }

  // Respond
  return ctx.next();
};

It's a minor thing, but it's a bit annoying that you always have to sorta step over the req argument. With Fresh 2.0 we're planning to move it onto the context object.
// Fresh 1.x
const foo = (req: Request, ctx: FreshContext) => new Response("hello");

// Fresh 2.0
const foo = (ctx: FreshContext) => new Response("hello");

Same arguments for sync and async routes
Orignally, I've modelled async routes after the middleware signature. That's why they require two arguments:
export default async function Page(req: Request, ctx: RouteContext) {
  // ...
}

With the benefit of hindsight, I consider this a mistake. What naturally happens is that folks tend to start out with a synchronous route and add the async keyword to make it asynchronoues. But this doesn't work in Fresh 1.x.
// User starts out with a sync route
export default function Page(props: PageProps) {
  // ...
}

// Later they want to make it async, but this
// breaks in Fresh 1.x :S
export default async function Page(props: PageProps) {
  // ...
}

So yeah, we'll correct that. In Fresh 2.0 this will work as expected.
// Sync route same as in Fresh 1.x
export default function Page(props: PageProps) {
  // ...
}

// Async route in Fresh 2.0
export default async function Page(props: PageProps) {
  // ...
}

True async server-side components
In truth, the async route components in Fresh 1.x are a bit of a beautiful lie. Internally, they are not components, but a plain function that happens to return JSX. We take the returned JSX and pass it to Preact to render and that's all
there is to it. The downside of that approach is that hooks don't work inside the async funciton, because it's not executed in a component context. In fact async routes in Fresh 1.x are called way before the actual rendering starts.
// Fresh 1.x async route
export default async function Page(req: Request, ctx: RouteContext) {
  // This breaks, because this function is not a component in Fresh 1.x,
  // but rather treated as a function that happens to return JSX
  const value = useContext(MyContext);
  // ...
}

You might be wondering why we went with this approach and the main reason was that Preact didn't support rendering async components at that time. This was the quickest way to get something that gives you most of the benefits of async components with some tradeoffs into Fresh.
The good news is that Preact recently added support for rendering async components on the server itself. This means we can finally drop our workaround and support rendering async components natively.
// Fresh 2.x async components just work
export default async function Page(ctx: FreshContext) {
  // Works as expected in Fresh 2.0
  const value = useContext(MyContext);
  // ...
}

This isn't restricted to just route components either. With the exception of islands or components used inside islands, any component on the server can be async in Fresh 2. Components in islands cannot be async, because islands are also rendered in the browser and Preact does not support async components there. It's unlikely that it will in the near future either as rendering in the client is much more complex, given that it mostly has to deal with updates which are not a thing on the server.
Simpler error responses
Fresh 1.x allows you two define a _500.tsx and a _404.tsx template at the top of your routes folder. This allows you to render a different template when an error occurred. But this has a problem: What if you want to show an error page when a different status code other than 500 or 404 is thrown?
We could always add support for more error templates in Fresh, but ultimately, the heart of the issue is that Fresh does the branching instead of the developer using Fresh.
So in Fresh 2.0 both templates will be merged into one _error.tsx template.
# Fresh 1.x
routes/
   ├── _500.tsx
   ├── _404.tsx
   └── ...

# Fresh 2.0
routes/
   ├── _error.tsx
   └── ...

And then inside the _error.tsx template you can branch and render different content based on the error code if you desire:
export default function ErrorPage(ctx: FreshContext) {
  // Exact signature to be determined, but the status
  // code will live somewhere in "ctx"
  const status = ctx.error.status;

  if (status === 404) {
    return
This is not the page you're looking for
;
  } else {
    return
Sorry - Some other error happend!
;
  }
}

With only one error template to deal with, this makes it a lot easier to allow them to be put anywhere. So will be able to use different error templates for different parts of your app.
# Fresh 2.0
routes/
  ├── admin/
  │   ├── _error.tsx # different error page for admin routes
  │   └── ...
  │
  ├── _error.tsx # error template for everywhere else
  └── ...

Adding  elements from Handlers
Whilst not ready for the initial Fresh 2.0 release, we plan to get the guts of Fresh ready for streaming rendering where both the server and client can load data in parallel. Again, this will not be part of the initial 2.0 release, but might land later in the year. But before we can even explore that path, some changes in regards to how Fresh works are required.
With streaming the  portion of an HTML document will be flushed as early as possible to the browser. This breaks the current  component which allows you to add additional elements into the -tag from anywhere else in your component tree. By the team the  component is called, the actual  of the document has long been flushed already to the browser. There is no remaining head on the server we could patch anymore.
So with Fresh 2.0 we'll remove the  component in favour of a new way of adding elements from a route handler.
// Fresh 2.0
export const handlers = defineHandlers({
  GET(ctx) {
    const user = await loadUser();

    // Handlers in Fresh 2.0 allow you to return either
    // a `Response` instance, or a plain object like here
    return {
      // Will be passed to the component's `props.data`
      data: { name: user.name },
      // Pass additional elements to `<head>`
      head: [
        { title: "My cool Page" },
        { name: "description", content: "this is a really cool page!" },
        // ...
      ],
    };
  },
});

export default defineRoute<typeof handlers>(async (props) => {
  return
User name: {props.data.name}
;
});

EDIT: This API is the least fleshed out of the ones listed here and might change. The main goal we have is to get rid of the  component.
Appendix
These are the breaking changes we have planned for Fresh 2. Despite some of them being breaking changes updating a Fresh 1.x project to Fresh 2 should be fairly smooth. Although this is quite a long list of bigger features, I spent yesterday and today hacking on it and got way further than I anticipated. Most of the features are already implemented in a branch, but lots of things are still in flux. It's lacking quite a bit of polish too. There will likely be some bigger changes landed in the coming weeks in the main branch.
It's too early yet to be tried out, but there will be an update soon. Once the actual release date approaches we'll also work on adding an extensive migration document. Given that it's early days and I just started back working on Fresh
yesterday, these things don't exist yet. The details of some of the features listed here and how they will be implemented might change, but I think the rough outline is pretty solid already.
I'm pretty excited about this release because it fixes many long standing issues and massively improves the overall API. Playing around with early prototypes it makes it much more fun to use too. I hope you are similarly excited about this release.

If head is specified as JSON, rather than JSX, will it be possible to create arbitrary tags? I gather from your example that title: string will create a <title> and name: string; content: string will create a <meta>, but this doesn't seem very generic.

Are there any plans to use vite? Would be nice to fix https://github.com/denoland/fresh/issues/978 before 2.0 as well.

@CAYdenberg The head API is the least fleshed out from the points. It should definitely be possible to set any tag you want.
@fazil47 No plans to switch to vite at the moment. Good point, #978 will be resolved before 2.0 .

Are there any plans/ideas to support functions as props in islands, even if with some limitations? I personally find that the hardest thing to live with, using Fresh. It limits code re-usability considerably.
For example, it's not uncommon to build something like:
<ComplexOrBigComponent onClick={onComponentClick} /> inside an island and have the  ComplexOrBigComponent.tsx simply call onClick from its props, but this doesn't work with Fresh because of the serialization for SSR.
I understand why it's done (because of the SSR), but there should be some way around it, even if it's disabling SSR for those components automatically, I believe, and it would make it a lot more easy to migrate existing code and patterns.

No, that doesn't fit into the 2.0 release schedule. Serializing functions would require a complex machinery of tracking all accessed variables which is very error prone. I don't have an idea of how to solve that at the moment.

If I'm understanding @BrunoBernardino 's point, the limitation he's experiencing is around code reusability. In other words, the ability to use a component as an island or not-an-island, depending on the context. In other words, for components that accept a function as an optional prop, it would be nice if there were a way to declare them as an island (or not-an-island) other than what folder they are in.

@CAYdenberg that's exactly it! I'd like to create "dumb" components in components/ that receive functions as props from some islands, and wouldn't mind losing the island's benefits in that situation.

Well, if it helps, components that are children of islands can receive functions as props. So, your ComplexOrBigComponent could live in components/, receive onClick when used as a descendent of an island, and not receive it when used outside of an island. Just mark onClick as being optional in your props interface declaration (and handle the cases where it is undefined).

@CAYdenberg I need to try that, as that should solve my problem! I'll report back once I've had the chance to do so.

Nice points @BrunoBernardino @CAYdenberg ... also, I'd like to bring up proper support for HMR to the table, would that fit into 2.0?

Proper HMR support in Fresh requires some changes in Deno CLI. It won't land as part of Fresh 2.0 but rather in the following release 2.1. That's the current plan.

@CAYdenberg that totally solved my problem, thank you so much!

Regarding the middleware, I have done an innovative step when I invented middleware trees for my framework. It's a much smoother thing than what express did, as it lets you combine middleware (and thus, plugins) in a much more flexible way.
If you feel like reading more about it, https://grammy.dev/advanced/middleware is the place to go. If, however, you don't want to take inspiration from that, please ignore me. Keep up the great work!

Exciting stuff! Any ideas on projected release timeline yet?

@KnorpelSenf thanks for sharing, that was interesting read! In our case we take routing into account which allows us to effectively flatten the tree into a flat list of middlewares + routes. This saves us a bit of book keeping and seems to work very well so far.
@lionel-rowe I'm making good progress at the moment and the hope for it is to have it out in a couple of weeks, unless I run into unforeseen challenges. I definitely want to get this into user's hands as soon as possible.

@marvinhagemeister there's no book-keeping required for such an implementation. It's surprisingly trivial to do this, i.e. 10-20 lines of code (depending on how you count). We did it like this: https://github.com/grammyjs/grammY/blob/38efc3c7729eef7133446451bdd7056ad4b09004/src/composer.ts#L196
What I'm rather concerned about is that a nested middleware system prevents some performance optimizations. While you could technically implement fast routing per node, it isn't really possible to directly jump to the right handler deep down in the middleware tree. In my case, the functionality is worth that, but HTTP routing can be optimised a lot better, so the opportunity cost is different. I'll leave it up to you :)

@KnorpelSenf The implementation you have there is quite elegant! I like it!
Agree about the concerns of nested middlewares potentially preventing performance optimizations. The way it currently works is that internally middlewares and routes are stored like this:
[
  * [...middlewares]
  GET / [...routeMiddlewares]
  GET /foo/bar [...routeMiddlewares]
  POST /api/foobar [...routeMiddlewares]
]

This means that an incoming request needs to do two steps:

Grab the middleware array at the first index in the array, because those apply to all routes, if one of them returns a response we can bail out early
Match one of the next route entries in the array. Once a route matches you already have the correct list of next middlewares to run, so no further checks are required.

Apart from the route matching, this system conceptually just walks over a flat array until one of the middlewares returns a response.

Great work and exciting times ahead. Are there any plans on supporting css modules, css in js and such with 2.0?

@aakashsigdel CSS modules require transpilation and I've been getting pushback when proposing to transpile the server code in Fresh or landing CSS modules right in Deno itself. So no progress on that front. When it comes to CSS-in-JS something like styled-components will never be a got fit with Fresh as it turns every component into a client component effectively.
The good news though is that with 2.0 we're in a much better position to potentially add all those transpilation stuff, even for server code.

Would it be possible to extract template rendering/islands into a plugin? It'd be awesome if you could mix/match frameworks similar to Astro, but with the ergonomics of Fresh

Fresh 2.0 promises to bring great improvements. When do you think it will be released?

@FabianMendoza7 soon™

Proper HMR support in Fresh requires some changes in Deno CLI. It won't land as part of Fresh 2.0 but rather in the following release 2.1. That's the current plan.

Without having read the Fresh source, yet. Would be great if you could somehow make this loosely connected to Fresh, as it could be really useful for developing SPAs with Preact and Esbuild.

@FabianMendoza7 soon™

Thank you for the update! I'm really excited to hear that Fresh 2.0 is on the horizon. Could you clarify what "soon™" means in this context? Are we looking at a timeline of a few weeks, or is it more in the range of months? Any specifics you could share would be greatly appreciated. Thanks for your time and effort!

If head is specified as JSON, rather than JSX, will it be possible to create arbitrary tags? I gather from your example that title: string will create a  and name: string; content: string will create a , but this doesn't seem very generic.

Not sure if a path has been chosen for this yet, but just a friendly reminder to tread carefully about trying to recreate all the nuances of  with a JS API. Jim Nielsen recently published a great post on this topic.

HMR is the only thing I miss for now in Fresh

Not sure if a path has been chosen for this yet, but just a friendly reminder to tread carefully when trying to recreate all the nuances of  with a JS API. Jim Nielsen recently published a great post on this topic.

We came up with a new plan for head elements yesterday that is very HTML-first 😀

HMR is the only thing I miss for now in Fresh

tailwind has a recommended class order which is really helpful so automatic class sorting is also missing

HMR is what's holding back our online editor from being seamless with fresh, so we're using an HTMX-only template in the meantime :'(

Yeah, we hear you all. HMR will be the main focus once Fresh 2.0 is out.

Yeah, we hear you all. HMR will be the main focus once Fresh 2.0 is out.

Partial powered HMR for non-island code?

<MyComponent onclick="console.log('click')" />

Looks like Vue

CSS modules require transpilation and I've been getting pushback when proposing to transpile the server code in Fresh or landing CSS modules right in Deno itself. So no progress on that front.

@marvinhagemeister Wouldn't the first step be to support CSS imports? Today, there is no way to import a CSS file in Deno, let alone transpile it.
I'm thinking it would be very useful to be able to import a CSS file and reference its contents or its url. For example:
import stylesheetContents from "../styles.css" with { type: "asset-raw" };

import stylesheetUrl from "../styles.css" with { type: "asset-url" };

<link rel="stylesheet" href={stylesheetUrl} />

When it comes to CSS-in-JS something like styled-components will never be a got fit with Fresh as it turns every component into a client component effectively.

It might be worth looking into CSS-in-JS that executes server-side (like Hono) or even at build-time (like vanilla-extract). CSS-in-JS is only bad when executed client-side (I've written about this topic at length).

@mayank99 I solved this problem using a custom Fresh plugin:
import { Plugin } from '$fresh/server.ts'
import { ensureDir } from '$std/fs/mod.ts'

type NPMPackage = {
    name?: string
    files?: string[]
}

/** @example
1. Enable `"nodeModulesDir": true` in `deno.json`

2. Add plugin to `fresh.config.ts`

import normalize from<EMAIL_ADDRESS>with { type: 'json' }
export default defineConfig({
    plugins: [
        npmToStatic([normalize]),
    ],
})
*/
export const npmToStatic: (packages: NPMPackage[]) => Plugin = (packages) => ({
    name: 'npm_to_static',
    async configResolved({ staticDir }) {
        for (const { name, files } of packages) {
            if (!name) throw new Error('package does not have a name')
            if (!files) throw new Error(`package "${name}" does not have a "files" array`)
            const packageDist = `${staticDir}/dist/${name}`
            await ensureDir(packageDist)
            for (const file of files) {
                await Deno.copyFile(`./node_modules/${name}/${file}`, `${packageDist}/${file}`)
            }
        }
    },
})

CSS modules require transpilation and I've been getting pushback when proposing to transpile the server code in Fresh or landing CSS modules right in Deno itself. So no progress on that front.

@marvinhagemeister Wouldn't the first step be to support CSS imports? Today, there is no way to import a CSS file in Deno, let alone transpile it.
I'm thinking it would be very useful to be able to import a CSS file and reference its contents or its url. For example:
import stylesheetContents from "../styles.css" with { type: "asset-raw" };

import stylesheetUrl from "../styles.css" with { type: "asset-url" };

<link rel="stylesheet" href={stylesheetUrl} />

When it comes to CSS-in-JS something like styled-components will never be a got fit with Fresh as it turns every component into a client component effectively.

It might be worth looking into CSS-in-JS that executes server-side (like Hono) or even at build-time (like vanilla-extract). CSS-in-JS is only bad when executed client-side (I've written about this topic at length).
Coloca

With tailwind and preact I personally think CSS classes are best avoided when tailwind, components, and CSS variables can solve the problem. I still find myself reaching for CSS for things like a keyframe, using a specific media query to change a CSS variable. Other than that, and rarely for 3rd party integrations, I wonder is the use case here just another way to style.  Maybe it's enough to add LSP support for writing CSS inside a

// TODO: Write a comment how there's a new JS framework released every day but nobody will switch anyways, still wanted to leave this here, since the goals appear to be kinda similar

@honojs/honox

@marvinhagemeister Why is fsRoute() not a middleware? Like, why is it applied like fsRoute(app) and not app.use(fsRoute()).
https://github.com/denoland/fresh/blob/dc283a137b956164a5398421bc264333f2cdc2cc/www/main.ts#L7-L10

@roj1512 because it needs to register routes for the router to be aware of. It basically calls app.get/post/patch/delete() under the hood.

I see nothing wrong with
function fsRoutes(ctx) {
    if (filter(ctx)) {
      //
    } else {
      ctx.next();
    }
}
``

Also, for the sake of simplicity, what do you think if this option is set as default so the user could just do fsRoutes()?
{
   loadIsland: (path) => import(`./islands/${path}`),
   loadRoute: (path) => import(`./routes/${path}`),
}

That won't work, because the dynamic imports are relative to the file they are in. For Deno Deploy to statically analyze them and include the referenced imported files it needs to be in the proper file. It's definitely not as nice as not having them, but then again I feel like these 2 lines are nicer than having fresh.gen.ts.

Awesome! when can i use the 2.0 version?

I think it is useful to specify islands freely so that we can place the islands component close to the route components where they are used, but alpha.16's fsRoutes only scan components in islands dir.

@Xuhv That's already possible in both Fresh 1.x and 2.x . Any folder inside the routes/ directory that is named like this (_foo) will be ignored. If it's named like (_islands) then it will be treated as an additional island directory. This means you can do this:

routes/about/(_islands)/MyAboutIsland.tsx
routes/(_islands)/OtherIsland.tsx
...

I'd be happy to give a hand with the doc of Fresh 2; is there a thread to track or anything that help me get into it ?

I would also like to help with docs and beta testing for 2.0 if the team is willing. :microscope:

alpha.16's ctx.render does not render layout. I think it is an unexpected behavior.

I am trying out<EMAIL_ADDRESS>It seems that FreshContext uses req instead of request as. a property name. I was wondering if it would make sense to use the full name request instead as js web apis normally do not abbreviate property names.

For comparison with a few other frameworks I could think of:

Express: Not comparable, as it's request object comes as a parameter and can be named anything (though the docs use req it seems)
Koa: Interestingly has both req and request. The former is used for Node native request object.
Hono: Uses req for it's context. Hono is very popular and modern, so feels like good match
Oak - Uses request for it's context. Oak is pretty much a modern Express-like substitute originally built for Deno

Personally, with such core and well recognized concepts that are a in frequent use, and with everyone's editor showing req: Request in code completions, I prefer req over request. It's a shared convention already, and it helps keep code more readable (reduces likelyhood that we must split one line into two). Especially since context.req (or ctx.req) will be used in (almost) every middleware function and custom route handler.

For comparison with a few other frameworks I could think of:

Express: Not comparable, as it's request object comes as a parameter and can be named anything (though the docs use req it seems)
Koa: Interestingly has both req and request. The former is used for Node native request object.
Hono: Uses req for it's context. Hono is very popular and modern, so feels like good match
Oak - Uses request for it's context. Oak is pretty much a modern Express-like substitute originally built for Deno

Thank you for the listing. I guess that shows though, that there is not a complete consensus about the usage of req.

Personally, with such core and well recognized concepts that are a in frequent use, and with everyone's editor showing req: Request in code completions, I prefer req over request. It's a shared convention already, and it helps keep code more readable (reduces likelyhood that we must split one line into two). Especially since context.req (or ctx.req) will be used in (almost) every middleware function and custom route handler.

Imo we should not design apis based on what would likely be best formatted but what is the most consistent with other apis. I think modern tools (autocompletion) and the js language (destructuring e.g. ({ request: req }) => ...) can handle such cases well enough if needed.

I advocate for request.

Fresh itself always used req as the variable names in all of our docs, see: https://fresh.deno.dev/docs/concepts/middleware
export async function handler(
  req: Request,
  ctx: FreshContext<State>,
) {
  ctx.state.data = "myData";
  const resp = await ctx.next();
  resp.headers.set("server", "fresh server");
  return resp;
}

The code snippets on deno.com use that too:

And on top of that this has been the convention in express, koa, hono and others. Changing that would make Fresh the odd one, which would be strange.

Fresh itself always used req as the variable names in all of our docs, see: https://fresh.deno.dev/docs/concepts/middleware
export async function handler(
  req: Request,
  ctx: FreshContext<State>,
) {
  ctx.state.data = "myData";
  const resp = await ctx.next();
  resp.headers.set("server", "fresh server");
  return resp;
}

Yes but variable names can be any name, it is not the same as a property name of an object.

And on top of that this has been the convention in express, koa, hono and others. Changing that would make Fresh the odd one, which would be strange.

I would argue that established web api names should be weighted more than framework conventions. FetchEvent also uses request.
I think Oak and Koa has it right and compared to that, Fresh would not be the odd one out.

I do think it's a bit weird for a modern framework to use req in a brand new API. Property names should clearly describe the thing. I don't see a good reason to abbreviate it when IDE autocomplete and intellisense exist.
Previously, it was just a function argument and had an explicit type that fully spells it out, avoiding the ambiguity.
(req: Request) => {…}

Whereas now, it's an actual property name and it may be destructured from the context object. Using req here almost looks like a mistake.
({ req }: FreshContext) => {…}

Personally, I also think reduces readability because "req" is not a word. It would also not be announced correctly for developers who rely on screen-readers.
If we're looking at other frameworks, Astro, SvelteKit and Remix all use request as the property name. Next.js has a function param (similar to Fresh 1) but their examples name it request.

Thank you for the listing. I guess that shows though, that there is not a complete consensus about the usage of req.

There will never be consensus. Some teams avoid abbreviations, some don't. It also seems fairly even in a rough code search 🙂

141k files for .req.
227k files for .request.

This includes ~50k files of e.request. and event.request.

Imo we should not design apis based on what would likely be best formatted but what is the most consistent with other apis. I think modern tools (autocompletion) and the js language (destructuring e.g. ({ request: req }) => ...) can handle such cases well enough if needed.

I agree to a degree. I would not argument for making abbreviations to any property just to make it format better. In this case it's something that will already be encountered in the Fresh docs; req as abbreviation for Request.
It's not keystrokes I want to save, but being able to see and scan more code without "noise". Longer property/parameter names just makes it more likely one line can become 2-4 just to format nicely. It's often the stuff after that is more relevant too, e.g. .headers or .url, and these are often wrapped in getCookies() or new URL() to interact with. The req property is one of the most frequently used properties, so keeping it shorter is a big plus for me in terms of readable (not writable) code.

Yes but variable names can be any name, it is not the same as a property name of an object.

Even if parameters can be named anything, I think it's still relevant as it shows a shared convention in the ecosystem, both for library and application code.

I would argue that established web api names should be weighted more than framework conventions. FetchEvent also uses request.
I think Oak and Koa has it right and compared to that, Fresh would not be the odd one out.

I don't think what the platform does factors in heavily here; the example is just camelCased Request as property name. No one argues that the Request class should be named Req. Given how much in the ecosystem both req and ctx are used to represent Request and Context, this is more a style preference of the project writing the code. I.e. if abbreviations are allowed or not.
Deno and this project seems to lean into abbreviations as long as they easily deduced; req, res, ctx, Addr (remoteAddr, localAddr) and more. With documentation, types, and interfaces for every property, I feel it's even less of a need to explicitly write out .request when the type for the property explicitly shows it's an instance of Request.

My two cents are:
in Fresh 1.x, since req was a handler argument, abbreviating it as a convention (one could also use request or others) was fine (just like the abbreviated ctx)
export const handler = (req: Request, ctx: FreshContext<State>) => {
  console.log(req);
}

in Fresh 2.x, since its no longer an argument, but a property of ctx, I also think ctx.request makes more sense (to also match its type Request). One can still use ctx, context or whatever, since its an argument, but a property should not be abbreviated in my opinion... (same would go for Addr instead of Address, I think a framework should not encourage abbreviations no matter how "well-established", since not everyone will be familiar with them, and the few keystrokes are just not worth it.
export const handler = (ctx: FreshContext<State>) => {
  console.log(ctx.request);
}

Not wishing to delay the 2.0 release, but if this change gonna happen, then I figured this is the right time for it to happen (still in time?).

List addition: Astro uses Astro.request and Svelte uses RequestEvent, therefore also request  for routing.

@timreichen Yes, I mentioned Astro, Svelte and Remix in my comment above.

Apart from the req vs request drama, any updates on when will Fresh 2.0 will be released? Will the incoming release of Deno 2.0 be timed with the release of Fresh 2.0 aswell, or it has nothing to do with it and will be released separetly? Are there any specified dates?

Apart from the req vs request drama, any updates on when will Fresh 2.0 will be released? Will the incoming release of Deno 2.0 be timed with the release of Fresh 2.0 aswell, or it has nothing to do with it and will be released separetly? Are there any specified dates?

no specific date, Marvin is currently focusing on the release of deno 2.0, but fresh 2.0 has released alpha version in jsr and i think it can be used for production

Will Fresh v2 Plugin interface drops the ability to add Routes component ( aka PluginRoute) ?
I can see in the drafted API app.addIsland(...) but I don't see anything in the API nor in the released v2 alpha which would be  equivalent to:
const plugin: PluginMiddleware = {
   routes: [
      { path: "no-leading-slash-here", component: SimpleRoute },
    ],

In the current main/canary (v2 alpha) I see app.island() but no interface of what was equivalent to the v1 Plugin interface, AFAICT.
Based on the new plugin interface, it seems this change is intentional, and I understand the goal of simplifying the API. I just want to ensure I fully grasp the direction here.
From what I gather, this approach might discourage plugins that enable certain routes meant to integrate directly within the app's layout. For example, a blog plugin configured to appear at /blog and fit more-or-less seamlessly into the app's existing layout. Instead, these "pluggable components" would need to be manually imported into the file system routes, and their configurability would be accessed through ctx.state.somePluginConfig. Is that correct ?

Now that Deno 2 has full Node compat, is there any chance to be able to use anything but Preact using Vite?

@nrako I have not tested this code, but I think that a plugin might be called with App as parameter, similar to '@fresh/plugin-tailwind' and fsRoutes, and then use the latter to add routes.
// @example/my-fresh-plugin/mod.ts
import { fsRoutes } from 'fresh';

export async function myFreshPlugin(app: App) {
  await fsRoutes(app, {
    dir: import.meta.dirname,
    loadRoute: (path) => import(`./routes/${path}`)
  });
}

// main.ts
import { App } from 'fresh';
import { myFreshPlugin } from 'jsr:@example/my-fresh-plugin';

const app = new App();
await myFreshPlugin (app);

The fsRoutes() method just adds routes via file system, so as long as there's a valid dir/loadRoute config I think a plugin should be able to add routes the same way as the "primary" app.
It's also possible that a plugin can return a App itself, and provide it so it can be mounted on a path:
import { App } from 'fresh';
import { appFreshPlugin } from 'jsr:@example/app-fresh-plugin';

const app = new App();

app.mountApp('/plugin-path', await appFreshPlugin());

Without docs, I'm guessing a bit. But to me, the base primitives we get from @fresh/core looks flexible enough for plugins to use how they see fit. Just passing in App and adding endpoints to it via .get(), .post(), .all() etc seems plenty flexible for most cases.

I think I'm coming around to adding some sort of layout API everywhere instead of moving that off to its own plugin. There are lots of good use cases where you want a plugin route to integrate into an existing layout which can be done right now, but is a bit low-level. Originally, I had pictured a world where layouts would be just plain components, so you'd do:
app.get("/foo", ctx => {
  return ctx.render((
    <App>
      <Layout>

this is a heading inside a layout

      </Layout>
    </App>
  );
});

Whilst components are composable on its own, it gets complicated when you're trying to compose routes from plugins. That's where the current API falls a bit short. Having something like app.layout() or another way to attach a layout to a route would fill that gap.

@marvinhagemeister, @csvn, thanks for sharing your insights!

There are lots of good use cases where you want a plugin route to integrate into an existing layout which can be done right now

Exactly, this is indeed possible in v1.
I understand and can anticipate the complexity that arises when trying to compose routes using plugins. The simplicity of a Hono & express style API for the v2 Plugin API approach, has a lot of merits. It could indeed be the right direction, even if it involves a breaking change—it might prove better for the long-term. That’s the key consideration I was trying to understand.
But indeed, the ability to add routes at any path through a plugin while inheriting layouts from the app's file system (fsRoutes) can indeed be very useful in Fresh 🍋.

Having something like app.layout() or another way to attach a layout to a route would fill that gap.

However, I'm not totally getting how app.layout() would be used and fill that gap.
To clarify my thoughts, let’s imagine an application with the following file system structure and plugin usage:
routes/
  ├─  _app.tsx
  └─  team/
      ├─  _layout.tsx   // Team-specific layout
      └─  index.tsx     // Team home page

// main.ts
freshBlogPlugin(app, { path: '/team/blog' })

For the plugin API I was imagining something like that;
app.get(
  options.path, // "/team/blog",
  ctx => {
    return ctx.render(

this is inside the app wrapper and the layouts, thus '_app.tsx' and 'team/_layout.tsx'
,
       {
           skipAppWrapper: false,
           skipInheritedLayouts: false,
        }
    );
  }
);

Yup, something like that would be great. It would require the app instance to be made aware of the concept layouts and the app wrapper template. You'd still need a way to register layouts as probably not all layout files sit in the local project directory.

You'd still need a way to register layouts as probably not all layout files sit in the local project directory.

That might be true. However, since this feature doesn’t seem to be available in v1, I’m not entirely sure about its necessity. I can’t think of a scenario where, as a Fresh user, I would need a plugin to inject a layout at a specific path.

fixing async components

Will async components block the response stream or render tree? I presumed an async component would insert a placeholder or something in the html that, on settling of the component render, would transfer that html back into the placeholder on hydration.

I check the blog, repo, and this issue daily. I've successfully stopped myself from posting 'are we close? is it happening?' for a long time. I see the alphas are continuing to drop and I am just so excited for Fresh 2.0 to launch.
Without being a pest, are there any tidbits the maintainers could drop? Get the hype train going!

Agree, setting up the compat aliases is way too complex in Fresh. We've wanted to tackle this for a while in Deno to allow aliasing npm packages, but so far there have always been more pressing features we had to address first. I don't have an ETA for that, just want to share that we're well aware that this is one of the biggest pain points of Fresh at the time of this writing.

Now that Vite 6 is out the environment API, does that change anything on the Vite front (in that Vite could do the overriding)?

I'm definitely interested in exploring having Fresh built around vite. So far I haven't been able to get the rest of the team on board with that idea though.

I'm definitely interested in exploring having Fresh built around vite. So far I haven't been able to get the rest of the team on board with that idea though.

As an alternative solution, any luck on getting Deno to support custom import attributes? That would avoid the need for transpilation on the server in many cases.

Perhaps wait for --> void(0),  then Fresh(void(0))?

What happened to 2.0 being released in march/april? Any updates on timeline?

What happened to 2.0 being released in march/april? Any updates on timeline?

Do you think they got tired because of Hono?

Do you think they got tired because of Hono?

I think it’s more heavy work being done on Deno Deploy as a better commercial offering. Also they are releasing Deno Deploy as self-hostable, and that takes all their time right know.
The Deno Company has achieved the release of the long awaited Deno 2.0, and better yet the longer awaited for businesses, their first LTS Deno 2.1.
All this will support giving back to the community, with cool frameworks like Fresh, nice tools to bootstraps your micro-SaaS with Deno SaaSKit.
Machine Learning, LLMs, AI, whatever you wanna call it will also need work with WebGPU that as been stabilized if I’m not mistaken.


Enhance Site Information Management with AI-Driven Analysis and Validation

This Pull Request introduces several enhancements to the sites.py script, focusing on integrating advanced AI features and improving data handling and analysis for site information management. The following updates have been made:

Improved Error Handling:

Enhanced error handling for file and URL loading processes.
Specific exceptions are now raised for issues encountered during file access and JSON parsing, providing more detailed error messages.

AI-Driven Site Description Analysis:

Added a new method, analyze_site_descriptions(), which uses Natural Language Processing (NLP) to analyze and cluster site descriptions.
Implemented TF-IDF vectorization and KMeans clustering to group sites based on their descriptions, with results stored in the site information.

Anomaly Detection:

Introduced a new method, detect_anomalies(), for detecting anomalies in site data.
Added regex-based validation to identify potential issues in site URLs and claimed usernames, with notifications for detected anomalies.

Code Organization:

Refactored site initialization code into a separate _initialize_sites() method to improve readability and maintainability.
Updated comments and docstrings to provide clearer explanations of the script's functionality and new features.

Enhanced Validation:

Added validation checks for URL and username formats using regular expressions to ensure data integrity.

Details:

Site Description Analysis: Utilizes TF-IDF vectorizer and KMeans clustering to categorize site descriptions into clusters, allowing for better organization and insights into site data.
Anomaly Detection: Implements regex patterns to validate URLs and usernames, detecting and reporting anomalies to ensure data quality.
Error Handling Improvements: Provides more informative error messages for issues related to file access and JSON parsing, facilitating easier debugging and troubleshooting.

These enhancements aim to improve the overall functionality and robustness of the site information management system by leveraging AI for advanced data analysis and ensuring higher data quality through validation and anomaly detection.

This pull request introduces several significant updates to the sites.py script, aimed at enhancing the management and analysis of site information through AI-driven features. The key changes include:

AI-Driven Site Description Analysis:

Implemented Natural Language Processing (NLP) techniques for analyzing and clustering site descriptions.
Utilized TF-IDF vectorization and KMeans clustering to group sites based on their descriptions, improving organization and insight extraction.

Anomaly Detection:

Added functionality to detect anomalies in site data, including validation for URLs and claimed usernames using regular expressions.
Introduced a detect_anomalies() method to identify potential data issues and notify users.

Improved Error Handling:

Enhanced error handling during file and URL loading processes with more specific exception handling and informative error messages.
Refactored code to better manage file access and JSON parsing errors.

Code Organization:

Refactored the initialization code into a separate _initialize_sites() method for improved readability and maintainability.
Updated comments and docstrings for clearer explanations of the new features and functionalities.

These updates aim to provide a more robust and insightful site information management system by leveraging AI for advanced analysis and ensuring higher data quality through improved validation and anomaly detection.


changed the readme file

I changed the formatting of readme file.

Hey @yxie21 , I wasn't able to merge your pull request directly because it caused a merge conflict with some other pull requests (lots of conflicts within the README), so I manually added some of your improvements.  Thanks!


Update request: python3Packages.setuptools-scm  7.1.0 → 8.0.4

Package name: python3Packages.setuptools-scm
Latest released version: 8.0.4

Current version on the unstable channel: 7.1.0
Current version on the stable/release channel: 7.1.0

[x] Checked the nixpkgs pull requests

Notify maintainers
@NickCao
Last updated by: @mweinelt

Note for maintainers: Please tag this issue in your PR.

We're currently in breaking changes freeze until the 20th of November, see https://github.com/NixOS/nixpkgs/issues/258640.
As setuptools-scm is directly referenced in over 500 packages and the package would cross a major version boundary, that would be too risky.


clarification on how to interpret kernel size for conv1d

Can we interpret the convolution kernel size as the context length? Would increasing kernel size allows longer range context?

No, the context length is whatever sequence length you use as inputs.
We typically use kernel size 2, 3, 4 for the conv1d


examples

three simple examples.
maybe not crazily genius ones, but could be a start.

Thanks for contributing.  I hope these examples help other people get started with Wad.js.


Hardware requirements

Hi Simon,
I tried to run the full and finetuned net on my Geforce GTX 980 with 4 GB memory and directly ran out of memory. What are the minimum hardware requirements for the net presented in the Paper (CSS-ft I guess :) )? (couldn't find it in there...)
Best,
Johannes

We used a Titan X with 12GB, and if I remember correctly we also trained the non-stacked models on a 8GB GPU, however I no longer recall if we also could fit the stacked ones on these. You could also take a look at https://github.com/openai/gradient-checkpointing.

Worked like a charm (close to black magic ;) ) thx for the hint!
I can now train the full CSS net on a 4 GB graphics card and the speed loss is acceptable.
Have you thought about implementing LiteFlowNet (https://github.com/twhui/LiteFlowNet) with the unsupervised Unflow architecture?  For runtime speed that seems to be great! What are the limits?

Sorry, I am not familiar with the details of the paper. I skimmed it and it might be a good fit, but I don't have time to try this.


Pass options to Validator

Resolves #9 and #10.

Woot!
The code looks solid. Can you update the README, please?

@mike-burns I've updated the README and the CHANGELOG
Unfortunately, the gem's list of available options isn't very .... polished ...
Digging that up also made me realize that I'm using v 2.2.5 of the gem, which doesn't seem to support your fragment: argument.
I'll try upgrading versions in a separate PR.

Right on, and nice catch. Looks good to merge.

@mike-burns on further inspection, the :fragment option exists
https://github.com/ruby-json-schema/json-schema/blob/2.2.4/lib/json-schema/validator.rb#L182-L185
Since the docs are lacking, I'm not sure if that'll get passed along, but it's worth trying.

Well it is documented here: https://github.com/ruby-json-schema/json-schema/tree/2.2.4#validate-against-a-fragment-of-a-supplied-schema

:tada:


Create model database for user score

When a user plays quizzes, we need to store their performance, marks, etc. So that users can see their progress.

can you please assign it to me? I am a gssoc participant.

Hello I want to solve this issue please assign me under GSSOC.

can i work on this issue


MudTabPanel text is always capitalized

Bug type
Component
Component name
MudTabPanel
What happened?

shows text always in Caps like RISK SUMMARY.
Is there a way to make sure that caps is removed. If a user wants caps he can always capitalise the text that is sent.
Expected behavior
Showing Text exactly as passed instead of capitalizing every letter
Reproduction link
https://try.mudblazor.com/snippet/cOQcFvYCGCNVQmNe
Reproduction steps
Listed in the reproduction ink
Relevant log output
No response
Version (bug)
6.0.14
Version (working)
No response
What browsers are you seeing the problem on?
Chrome, Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This css disables text capitalization for tabs and buttons:
.mud-tab, .mud-button-label {text-transform: none;}

MudBlazor is a Material design inspired library.
If you want to override Material guidelines you are going to have to use css.
We're unlikely to accept contributions that add API that goes against this


How send Multicast message to online client?

The local is done, but I want use reactphp-multicast to online game.
can i do it? (client use UDP connect server)

@Sun-FreePort Excellent question!
 See also https://networkengineering.stackexchange.com/questions/47994/is-multicast-on-the-public-internet-possible-and-if-yes-how/47995.
In any real-world example, you would most likely want to send unicast datagram over the internet instead.
I hope this helps :+1:

Very useful, thanks for you help!


heizgrenze is only configurable from 5 to 12 degrees?????

How to change this , my threashold is 18 C

Normally I look into the ait web interface and uses this min and max values.
Which min and max value can you set in your Luxtronik own web interface or in the local panel?

In web interface its possible to set 5 to 30c

Am 03.01.2023 um 21:02 schrieb BenPru @.***>:
Normally I look into the ait web interface and uses this min and max values.
Which min and max value can you set in your Luxtronik own web interface or in the local panel?
—
Reply to this email directly, view it on GitHub https://github.com/BenPru/luxtronik/issues/61#issuecomment-1370173505, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFSVZLXDYZXWYSLPZ3JFWLLWQSAVLANCNFSM6AAAAAATPYD3ZM.
You are receiving this because you authored the thread.

imagin heating starts before 12 c , the most people have the threashold at 15-18 c

@colognebroker Changed in 2023.01.04

I close this issue because I think its fixed. If not please feel free to reopen it.


Test icons contribution point

Refs: https://github.com/microsoft/vscode/issues/114942

[x] anyOS @misolori
[ ] anyOS @eamodio

Complexity: 4
Create Issue

The icon contribution point allow extensions to define a new icon by id, along with a default icon.
That icon id can then be used by the extension (or any other extensions that depend on the extension) at the places where ThemeIcon can be used.

Product icon themes can redefine the icon (if they know about the icon id)

Create an extension that contributes an icon and use it.
"contributes": {
	"icons": [
		{
			"id": "distro-ubuntu",
			"description": "Ubuntu icon",
			"default": {
				"iconFontId": "distro-icon-font",
				"character": "\\E001"
			}
		},
		{
			"id": "distro-fedora",
			"description": "Fedora icon",
			"default": {
				"iconFontId": "distro-icon-font",
				"character": "\\E002"
			}
		}
	],
	"iconFonts": [
		{
			"id": "distro-icon-font",
			"src": [
				{
					"path": "./distroicons.woff",
					"format": "woff"
				}
			]
		}
	]
}

In this example, an extension defines two new icon ids distro-ubuntu and distro-fedora along with default icon definitions. The icons are defined in an icon font at the given font character. The icon font is defined in a new contribution point iconFonts.
The product-icon-theme-sample can be used as the icon font. It also contains a script build create an icon font from svgs.

test that the code completion, hovers and validation work when authoring an icon and icon font contribution
test that the icon identifier must consist of at least two segments separated by minus (needs a new I-Build)
test that that the icon ids (e.g. distro-ubuntu and distro-fedora) can be used in markdown strings ("$(distro-ubuntu)" Ubuntu 20.04") and at all places that take a ThemeIcon ( new ThemeIcon("distro-ubuntu"))
test that the icon id can also be used by other extensions (if they know about the icon id)
test that a product icon themes can redefine the icon (you can test this with the product-icon-theme-sample )

This is very cool and excited to see extensions use this:

Looks great! Can't wait for this to ship.


MML-112 - Add the Symphony Element 'textarea' tag

Addresses https://github.com/symphonyoss/messageml-utils/issues/112.

ok to test

ok to test


Windows Terminal launch fails with admin rights (Admin By Request)

Microsoft PowerToys version
<IP_ADDRESS>
Running as admin

[X] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce

Create PowerToys icon on desktop
In icon's properties (advanced properties) check the "Run as administrator" option.
Start PowerToys with the icon
Reveal PowerToys Run and start Windows Terminal in admin mode (Ctrl+Shift+Enter)

Other details

When start Windows Terminal from Start menu (with right click, Run as administrator) then it starts with administrator rights correctly
I'm not sure if it is a PowerToys bug, but based on my first point I assume it is
I saved the log file (as it was requested), I will share if it is necessary

✔ Expected Behavior
Start Windows Terminal with administrator rights
❌ Actual Behavior
Admin By Request Popup says:
Execution error
The given path's format is not supported.
Then a PowerToys Run popup says:
Something went wrong.
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19043.0
IntPtr Length: 8
x64: True
Date: 2021.09.02. 7:58:22
Exception:
System.ComponentModel.Win32Exception (0x80004005): The operation completed successfully.
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at Microsoft.Plugin.Program.Programs.UWPApplication.<>c__DisplayClass61_0.b__0(ActionContext _)
at PowerLauncher.ViewModel.ResultViewModel.<>c__DisplayClass32_0.b__0(Object _)
at PowerLauncher.ViewModel.RelayCommand.Execute(Object parameter)
at PowerLauncher.ViewModel.MainViewModel.HandleContextMenu(Key acceleratorKey, ModifierKeys acceleratorModifiers)
at PowerLauncher.MainWindow.Launcher_KeyDown(Object sender, KeyEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndKeyboardInputProvider.ProcessKeyAction(MSG& msg, Boolean& handled)
at System.Windows.Interop.HwndSource.CriticalTranslateAccelerator(MSG& msg, ModifierKeys modifiers)
at System.Windows.Interop.HwndSource.OnPreprocessMessage(Object param)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
Other Software
Admin By Request <IP_ADDRESS>
Windows Terminal 1.9.1942.0 (Microsoft Store)

Create PowerToys icon on desktop
In icon's properties (advanced properties) check the "Run as administrator" option.

Why are you creating a shortcut on the desktop and checking "Run as administrator"?
PT gets an "Always run as administrator" option in the screenshot below:

BTW, Failed to reproduce this. So could you send the bug report for further investigation?

Can not reproduce it either

Create PowerToys icon on desktop
In icon's properties (advanced properties) check the "Run as administrator" option.

Why are you creating a shortcut on the desktop and checking "Run as administrator"?
PT gets an "Always run as administrator" option in the screenshot below:

Yes I'm aware of that function but it crashed silently in prev. release. This was a workaround.

BTW, Failed to reproduce this. So could you send the bug report for further investigation?

Here you can find the mentioned log
https://gist.github.com/redcoreit/0656c5e4620cad538c748f15d67dad29

@redcoreit
Is Windows Terminal opened despite the error message?

No terminal opened, just error popups are visible.

In icon's properties (advanced properties) check the "Run as administrator" option
If you remove this option and use "Always run as administrator" instead, is this issue persists?

In icon's properties (advanced properties) check the "Run as administrator" option

@redcoreit If you remove this option and use "Always run as administrator" instead, is this issue persists?

Icon removed, PT runs in non-admin mode -> same error.
Icon removed, PT "Always run as administrator" turned on -> same error.

@redcoreit Maybe the full log file can tell something.
Right-click on the PowerToys icon in the tray menu and select Report Bug

Drag and drop the report into a GitHub comment to upload it.

PowerToysReport_2021-09-02-15-55-40.zip

Can I check somehow the path that PT wants to execute?

Open containing folder in PT Run results(Ctrl+Shift+E), copy the path from the file explorer and add executable path.

@redcoreit
Can you check if you have the same issue with Alarms & Clock?

I have no "run as admin" option in case of  Alarms & Clock, neither you have (according to your attached picture).

Can I check somehow the path that PT wants to execute?

Open containing folder in PT Run results(Ctrl+Shift+E), copy the path from the file explorer and add executable path.

Hah! I've opend the path (Ctrl+Shift+E) and I found a wt.exe there (with lots of other stuff).
If I run wt with PT Run in admin mode it starts correctly (after I approve it with Admin By Request).
Is this something with my system?

Hah! I've opend the path (Ctrl+Shift+E) and I found a wt.exe there (with lots of other stuff).

Do you have WindowsTerminal.exe there? Can you try to open it with admin rights?

@redcoreit

I have no "run as admin" option in case of Alarms & Clock, neither you have (according to your attached picture).

haha, can you try any packaged application that can be run elevated?
For example, telegram installed from Microsoft Store

@redcoreit By the way, v0.45.0 has just been released today. Cloud you also try on 0.45 to check if the issue persists?

@redcoreit By the way, v0.45.0 has just been released today. Cloud you also try on 0.45 to check if the issue persists?

Definitely. I can provide more information on Monday (I have no laptop right now)

@franky920920

Cloud you also try on 0.45 to check if the issue persists?
Updated to 0.45, my issue is still persists.

Do you have WindowsTerminal.exe there? Can you try to open it with admin rights?
Yes I have, and it starts correctly from explorer (with admin rights)

haha, can you try any packaged application that can be run elevated?
For example, telegram installed from Microsoft Store
I've the WinDbg app (packaged app) installed, and it has the same problem (cannot start as admin from PT)

@franky920920 Yes the bot went offline because of fabricbot server problems.

@audian-benp that could be due to VCM.  We've disabled it by default now with 0.53.  If it is the error above, my solution below i bet will work.
Solution:
I bet if you adjusted Admin by request to allow the PT Run executable to give out admin rights, this would magically work.
Background:
any process elevated will launch the new processes elevated.  Most people elevate PT to get FancyZones to work nicely with elevated windows.  Ergo, you accidently could be launching processes via PT Run as admin without meaning to.  We do a bit of magic to make sure PT Run won't run under admin due to this when it is launched via our runner process.

I bet if you adjusted Admin by request to allow the PT Run executable to give out admin rights, this would magically work.

@crutkas would you be so kind to provide detailed instructions? I couldn't find any relevant settings in PT, nor ABR.
Please note that ABR is managed by the company I work for. I can request admin rights but I'm not allowed to configure it.

does this issue still happen with v0.73.0? /needinfo


How to build project?

Hi!
Your source code is not building. after so much try, I'm receiving this error message:
Cause: com.novoda.gradle.release.AndroidLibrary$LibraryUsage.getDependencyConstraints()Ljava/util/Set;
how should I fix this?

@samanatabaki Seems like the novoda plugin is broken with the new recently release versions of gradle/android studio. Looking into a fix.

@samanatabaki just disabled the plugin that causing this issue. Try pulling the latest changes again.


stable/rabbitmq extra ports not working

Uncommenting the "extraports" and "extracontainerports" in the values.yaml results in intepretation errors at various points of templates/svc.yaml
Version of Helm and Kubernetes:
Helm 3.0.2
Kube 1.17.3+k3s1
Which chart:
rabbitmq
What happened:
I tried to add port 1883 which is necessary for plugin mqtt
What you expected to happen:
an additional port made available
How to reproduce it (as minimally and precisely as possible):
enter this
  ## Extra ports to expose
  extraPorts:
    1883

  ## Extra ports to be included in container spec, primarily informational
  extraContainerPorts:
    1883

or this
  ## Extra ports to expose
  extraPorts: 1883

  ## Extra ports to be included in container spec, primarily informational
  extraContainerPorts: 1883

and helm will quit with a yaml parse error

Hi @embcla,
Taking into account the stable deprecation timeline, we have been started the process of moving the Bitnami Helm Charts to the Bitnami repository, see helm/charts#20969 for more details.
The Helm Chart tgz continues existing in the stable repo but it would not get new updates. We also added more info and the upgrade process to start using the new repo in the README.md and NOTES.txt file helm/charts#21310.
As the RabbitMQ chart is marked as deprecated in this repository, please, can you open the issue in the bitnami charts repository?
Thanks

Ok will do
closed as chart is obsolete


Feature Request: perfect opus merging without 'click'

Your list for upcoming features contains "merge multiple smaller audio files into large ones auto generating chapters using silence detection with ffmpeg, fdkaac and CliWrap"
I like what tone is aspiring to become, so here's a feature request: I've never managed to merge opus files perfectly without a "click" sounds in the gaps - and I've tried just about every method/tool.
It seems to be some built-in opus problem, either the pre-gap, or simply that opus start/end frames arent't meant to be chained. For mp3, mp3binder manages to do it - but the mp3 format seems to be easier to handle.
I've written a question in Hydrogenaudio, basically to find out that I have to merge before converting to opus - all other methods (yet) fail and produce the "click" gap sound. https://hydrogenaud.io/index.php/topic,124084.0.html

I like what tone is aspiring to become, so here's a feature request: I've never managed to merge opus files perfectly without a "click" sounds in the gaps - and I've tried just about every method/tool.

Since I've no time to add features atm, it is a nice request but I think it is not gonna happen soon. However, I thing merging ogg directly may be problematic because of the file format. Probably converting to wav, merging uncompressed and then back to ogg is the way to go. It's slower, but probably more accurate.
This could be a way when a flag extra-accurate is provided or something :-)


Revert "manually enable DISABLE_NODE_IP_CHECK and FELIX_IPINIPENABLED until code handles this case"

Reverts projectcalico/calico#1246

@caseydavenport - I did test on kubeadm cluster w/etcd. Do you think that's sufficient, or should I try out on broader range of setups?


Training hidden_units of DNN with skflow

Hello all
As I know, there are several ways to optimize DNN. I think the most important parameters for DNN should be hidden_units.
Is it possible to somehow find best hidden_units automatically?

You can try using GridSearch from sklearn. Otherwise - it's really just an experiments and trying to understand how it changes the quality of the model. There just basic rules of thumb (like start with the same number as original features and then go less and less: e.g. for 500 features you can use [500, 250, 100]). You also want to balance the number of examples you have versus a number of parameters. Usually, you want to have ~10 examples per parameter.

Haha, thank you for giving this rule of thumb.
I have to confess that there a lot "rule of thumb" presented in discussion in quora or stackoverflow or researchgate to construct hidden layers in DNN, but let me check with your rule.

I think GridSearch in sklearn is similar with h2o.grid in h2o deep learning.
However, the idea is you need to present all the possible hidden_units. We can list 1 000 000 000 different hidden_units and let the computer run, but I am not sure if it is a smart way. (For me it is just a brute force approach - maybe I am wrong)

There are other hyperparameter optimizers that actually take into account the values and accuracy of the model to pick next values (we use something like this in Google).
For example of Open Source library you can try - http://hyperopt.github.io/hyperopt/

Hope this helped! I'm closing this bug for now.


Fix spresense smp

Summary

This PR consists of two commits.
cxd56_cpupause.c
During Wi-Fi audio streaming test, I noticed data corruption in tcb
Finally, I found an issue in IRQ request handing with IPI
This commit fixes this issue
cxd56_gs2200m.c
During streaming test, I noticed a dealock when controlling IRQ
Actually, it will send an IPI when the cpu index is not 0
However, up_cpu_pause() also sends IPI with critical section
So the IRQ control must follow the same rule

Impact

Affects SMP only

Testing

Tested with spresense:smp_wifi

@jerpelea


Update glass_hover_effect.dart

Add fix for rounded corners in the BackDropFilter widget

Hi there, thanks for your contribution!
I tested it quickly and saw that you fixed on thing but you introduced another bug. Now the text is always visible on the screen.


Removed duplicate text and corrected formatting

There were two descriptions of what a  is.
Markdown formatting was incorrectly rendering in https://guide.freecodecamp.org/html/elements/label-tag.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @samcottle for fixing the markdown and removing duplicate content!
Congratulations on your first PR merge to this repo! 🎉


Remove files from CI to free up space

This PR changes CI to delete some of the built-in files, to free up space. As discovered in #108, we hit the limit of filesystem usage in CI. #110 freed up another 1 or 2 GB, but if we need more space, it seems we must delete some of the pre-existing files.

Disk usage exploration

[x] Find what is taking up a lot of disk space

[x] Run ncdu and export results.
[x] Analyze results
[x] Compare to disk usage post-build

[x] Reduce space usage so that CI can run. Removed separate Android SDK/NDK installation: https://github.com/spruceid/didkit/pull/110

Disk usage summary
Initial disk usage: 84G total, 67G used, 17G free (step:2:7)
After removing things: 36G used, 48G free (step:4:7). Removal freed 31G.
Removal step takes 2m40s (step:3:1)
After build: 50G used, 34G free (step:32:1). Build took 16G.
Full filesystem usage info obtained using ncdu in Run 665122235: artifact ncdu.gz.
Examine using zcat ncdu.gz | ncdu -f-
Additional ncdu data from Run 665519246. Examine using e.g. ncdu -f pre.ncdu:

pre.ncdu Filesystem after removing things and checking out repos, but before installing dependencies or building
post.ndcu Filesystem after installing dependencies, building and running all tests.
wd.ncdu didkit repo directory after build and test

Large directories

Size
Path

24.1 GiB
/usr/share/dotnet

11.3 GiB
/usr/local/lib/android/sdk

1.8 GiB
/opt/ghc

1.3 GiB
/opt/hostedtoolcache/Python

1.3 GiB
/usr/share/swift

1.1 GiB
/opt/hostedtoolcache/go

1.1 GiB
/opt/hostedtoolcache/CodeQL

1.0 GiB
/usr/local/graalvm/graalvm-ce-java11-<IP_ADDRESS>

1.0 GiB
/var/lib/gems

855.2 MiB
/opt/az

765.8 MiB
/var/lib/snapd

531.6 MiB
/usr/share/rust

562.1 MiB
/home/linuxbrew

465.9 MiB
/opt/hostedtoolcache/PyPy

374.3 MiB
/usr/local/lib/node_modules/netlify-cli

342.7 MiB
/usr/share/miniconda

368.2 MiB
/usr/local/julia1.5.4

289.9 MiB
/usr/local/share/powershell

Apt clean
apt clean did not have a noticeable impact. df before and after

Results of apt clean

Closing since we haven't encountered the disk space limitation in a while; if we do, this could be reopened - but there might be better solutions.


Equinox data needs to be updated

As per:
https://gist.github.com/derickr/f32dd7a05d5c0a099db4e449111f5ccd?permalink_comment_id=4606196#gistcomment-4606196

Hello @andrejpavlovic Thanks for the info.
I've updated the equinox datas in the new release :) https://github.com/LaTableRouge/seasonsCalc

Awesome!


Solved the issue of page rendering at bottom

Solved issue #363
Screenshots (if appropriate):
https://github.com/MAVRICK-1/e-commerce_website/assets/154724111/bdfa9451-e49f-4aad-ba0f-3696e2971e06

[x ] Bug fix (non-breaking change which fixes an issue)

[x ] My code follows the code style of this project.

@sanket95droid pls review the PR!!

@sanket95droid pls merge the PR!!

@pani2004 We are actually working on the deployment so we have some PRs in hold, dont worry we will merge your PR.

ok @sanket95droid

@sanket95droid pls merge this

@MAVRICK-1


Can the model you give meet the accuracy of the paper?

when i try to eval the model you give with  evaluate_poses_keyframe.m ,i get a poor reult 0.6763085650852565 with add < 2cm .Is my evaluation method wrong? thanks for your reply !

What exactly do you mean with this number? The overall proportion of ADD<2cm?
However, I was actually wondering the same thing. Following the same procedure as described in the repository, I get the unrefined results  at the bottom in Matlab. I changed only two things: Catching the issue described in #91 and printing out the values as seen below in Matlab.
Here i = 3 is referring to the index corresponding to the unrefined results as in evaluate_poses_keyframe.m:
class 1, i 3: AUC(s):95.31, ADD-s<2cm:100.00, AUC:70.74, ADD<2cm:70.68 class 2, i 3: AUC(s):92.44, ADD-s<2cm:98.96, AUC:86.87, ADD<2cm:88.71 class 3, i 3: AUC(s):95.05, ADD-s<2cm:100.00, AUC:90.74, ADD<2cm:96.28 class 4, i 3: AUC(s):93.74, ADD-s<2cm:96.94, AUC:84.65, ADD<2cm:82.50 class 5, i 3: AUC(s):95.81, ADD-s<2cm:100.00, AUC:90.96, ADD<2cm:94.12 class 6, i 3: AUC(s):95.73, ADD-s<2cm:100.00, AUC:79.61, ADD<2cm:58.97 class 7, i 3: AUC(s):94.38, ADD-s<2cm:99.53, AUC:89.41, ADD<2cm:93.93 class 8, i 3: AUC(s):97.20, ADD-s<2cm:100.00, AUC:95.80, ADD<2cm:100.00 class 9, i 3: AUC(s):89.30, ADD-s<2cm:92.95, AUC:79.57, ADD<2cm:76.37 class 10, i 3: AUC(s):90.12, ADD-s<2cm:89.45, AUC:76.87, ADD<2cm:59.10 class 11, i 3: AUC(s):93.61, ADD-s<2cm:100.00, AUC:86.89, ADD<2cm:86.84 class 12, i 3: AUC(s):94.40, ADD-s<2cm:99.61, AUC:87.50, ADD<2cm:86.20 class 13, i 3: AUC(s):86.10, ADD-s<2cm:60.59, AUC:5.07, ADD<2cm:0.00 class 14, i 3: AUC(s):95.25, ADD-s<2cm:100.00, AUC:83.81, ADD<2cm:79.72 class 15, i 3: AUC(s):92.14, ADD-s<2cm:95.46, AUC:83.85, ADD<2cm:82.59 class 16, i 3: AUC(s):89.50, ADD-s<2cm:98.35, AUC:32.25, ADD<2cm:0.00 class 17, i 3: AUC(s):90.21, ADD-s<2cm:98.90, AUC:77.27, ADD<2cm:49.72 class 18, i 3: AUC(s):95.08, ADD-s<2cm:100.00, AUC:89.10, ADD<2cm:91.05 class 19, i 3: AUC(s):71.52, ADD-s<2cm:77.67, AUC:24.87, ADD<2cm:0.00 class 20, i 3: AUC(s):70.17, ADD-s<2cm:72.29, AUC:25.17, ADD<2cm:11.14 class 21, i 3: AUC(s):92.21, ADD-s<2cm:100.00, AUC:50.81, ADD<2cm:0.00 class 22, i 3: AUC(s):91.19, ADD-s<2cm:94.91, AUC:74.19, ADD<2cm:68.18

@LennardBo thanks for your reply，I have solved this problem！


Documentation: Create migration guide from 1.x to 2.x

Background
There have been a number of changes to Postal recently 🥳
Problem

There are a lot of people running "1.x" of Postal, but there may be breaking changes when they upgrade to "2.x"

Next steps
@adamcooke: Are you able to create documentation (possibly in the Wiki) on how a user would go from their "Postal 1.x server" to a "Postal 2.x" server?

Yes. The main difference between Postal 1.x and 2.0 will be the way it is installed. The actual software will be mostly the same and the databases aren't changing at all. Someone running Postal 1.x should be able to upgrade to Postal 2.0 by simply stopping their old processes and starting some new ones through Docker, in theory.
I'll write a list of actual changes a bit nearer the time and we can work out what additional docs might be required then.

Yeah it should be as easy as

follow new install instructions
link to existing database and rabbitmq
postal stop
run any migrations
start version 2 from instructions
rm /opt/postal/app

Although we'll probably also take the opportunity of removing the ancient ubuntu server somewhere in there :sweat_smile:

The only other change will for people using open/click tracking. They will need to reconfigure their web proxy and issue certs for any domains they use for this.

I believe I have now compiled all the instructions needed to upgrade to v2. If anyone spots any problems or thinks anything could be better, please submit an issue or PR on the docs repo.
https://docs.postalserver.io/install/upgrade-to-v2


Add example how water balance error is computed

With a model and worked out computations

Include our promises on the 1% error (per node, timestep, and cumulative and delwaq cont tracer).

and cumulative and delwaq cont tracer


93 - CxxC

(Not ready for review)
Still to do:

Refactor commonalities between the "otherSettler" block and the "IsInvalidCityLocation" block.  They use the same CxxC pattern, so that should be shared, even if the reason they mark things as invalid is different.
Refactor duplicated WarPriority/ExpansionPriority code.
Use Serilog
Revalidate that it works in practice now that it's fully rebased on Development

The Greek, Dutch, and American AIs doing a nice job of settling in a CxxC pattern:

They've also done a decent job prioritizing city locations.  They tend to travel farther away early on than a human would, but the locations they haven't settled - jungle and plains - would be low-priority for a human, too.  The Dutch just beat the Americans in a race to The Hague's location.

Closes #93
Closes #207 (this wound up being one line)

It's been a week, no reviews, it's also released to prod, no complaints.  Looked over again, going to merge.


Applicant with anonymized-like name appeared in applicants list

Some applicant with a name like "Zachary" appeared in the applicants list for a group. This happened before anonymization. Not sure what to think about this. Spam?

Look out for Zacharies for the next admission.


Increase the number of illumiante/support package versions allowed

We have Laravel 6.2 installed, but we could not add laravel-sign-in-with-apple to our project because of the tight dependency on illuminate-support.

Hi @lenrsmith, thanks for using the package. This is a conscious decision on our part. We recommend you fork the project and tweak it as necessary while you are using it in legacy versions.


Fixed an issue where changing the theme settings wasn't working correctly

Fixes #3291
Sorry, my bad.
I didn't realise that ThemeHelper was setting the theme on elements by capturing a reference to the MainPage. I assumed it was relying on Application.RequestedTheme and changing this.
Balance is restored, and ThemeHelper has had some unused code removed. ThemeHelper.RootTheme has been refactored slightly to make it responsible for reading the value from one place (LocalSettings), and setting ThemeHelper.RootTheme will persist this change back to LocalSettings and call ApplyTheme() to have the current theme applied across the application.

@AndyMDoyle Thank you!


Issue while accessing first lab

# Lab Name: Create a composite model
Task: Set up Power BI Desktop
Step: 04
Issue Type: blocking
Description of issue: Saving starter report throws error
Repro steps (please include screenshot if applicable):

Open starter report
Prompt database connection press save.
See the error

Hi team - here's a workaround for this issue.

When you see the error message Amir noted above, select Close

On the home tab of the ribbon, select Transform data to open the Power Query editor

Select the Order Date query and Edit Permission

Select Run, and then select Edit Credentials from the warning at the top of the screen

Select Okay in the Encryption support popup window. Your query should now load.

Step through each of the queries to ensure they all load, and then Close and apply - now you should be able to start the lab!

@AmirSoyelAhmed-hub - to get around the connection issues I saved the file as a .pbit (and updated the instructions). Learners will have to enter the database credentials, but it avoids any error messages. I will close the issue once it's confirmed this solution works properly! Thanks for raising this.

Thank you @shannonlindsay.