VUE/Svelte like syntax

This issue created to discuss how <script/template/style> approach may look like

I would like to see something like SFC (Single File Components), with different languages, divided by tags.
example:
<script>
import Component from '@glimmer/component';
export default class MyComponent extends Component {
   a = "hello, World!"
}
</script>

<template>
  {{this.a}}
</template>

to get basic editors support we could start with ".vue" file extension for this POC

This would opt folks out of multiple tiny components in the same file. We already don't have that today, but would we be ok with never having that?

@NullVoxPopuli I think we could have tag-based component definition here and share scope per-file, like
<template for="ChildComponent">

</template>
<template>
  Root Component <ChildComponent />
</template>

🤔 I suppose that could work, but during authoring, we're back to having string keys, which we'd have to build custom tooling around.
but, with this vue-like approach, we don't have to add support for eslint.

I collected my idea in this gist: https://gist.github.com/gossi/6b15f5749c8fecd54d1b6d57168108b7

For what it is worth, the idea is that this repo is going to be very permissive with the formats that it allows using. The requirements are that the format is properly documented (including all of the scenarios mentioned for the two current formats in the README), and that adding support for a format that is unused does not cause performance regressions for the others.
tldr; PR's welcome 😸

It should be possible to convert *.svelte files to strict-mode files
(from https://svelte.dev/docs )
<script>
	let x = 0;
	let y = 0;

	function yPlusAValue(value) {
		return value + y;
	}

	$: total = yPlusAValue(x);
</script>

Total: {total}
<button on:click={() => x++}>
	Increment X
</button>

<button on:click={() => y++}>
	Increment Y
</button>

becomes:
export default setComponentTemplate(
  precompileTemplate(`
  Total: {this.total}
<button {{on 'click' this.firstClick}}>
	Increment X
</button>

<button {{on 'click' this.secondClick}}>
	Increment Y
</button>
  `),
  class Foo {
    // we don't actually know that these have to be tracked, we'd have to assume.
    // maybe we could inspect the click handlers and see what properties are accessed
    @tracked y = 0;
    @tracked x = 0;

    // this is a getter, that seemed over complicated in the svelte example
    get total() {
       return y + x;
    }

    // can't determine action name from anything with any consistency
   firstClick = () => x++;
   secondClick = () => y++;
  }
);

but,
this syntax forbids defining multiple components in the same file. I wonder how that would be done. I'm new to svelte, but interested in exploring these ideas.

This is what the svelte folks are doing for multiple components in a file https://github.com/sveltejs/svelte/issues/2940#issuecomment-791968175

It's totally personal taste but I'm no fan of having the <script> tag everywhere. I like the format bellow

*screenshot taken from Readme
To get css per component I could see a <style> tag there, maybe before the <template>. idk how difficult it would be to implement nor if highlighting tools would work out of the box

Closing because we went with the details laid out in rfc 779, thanks for all the chattin'!


Create bolt task to run puppet apply (deployment class) on CM

Key
Value

Type
Puppet Bolt Tasks

Manifest File
deploy.json

Code File
deploy.rb

Input Parameters
exeuction_id (execution id of currently executed node)

Execution environment
executed on node corresponding to execution_id by config master

Objectives
Execute the puppet apply -e class{"simple_grid::deploy::lightweight_component::init": execution_id => $execution_id} command on the node and pass the exeuction_id as a parameter


Drawing a cached sprite not in the display tree causes invalid render

Prerequisites for the bug to occur:

A display object, which is not added to the main display object tree which has a display object child - I can confirm that a tilemap and normal sprite with graphics data will trigger this.
A bitmapdata on which #disposeImage is called, and onto which you draw the detached sprite
I'm not really certain why but I think only second draw after full render cycle causes the issue - maybe has to do with cache render?
(4). Toggling cacheAsBitmap  on the sprite in question will either make it not render at all (when false), or render upside down in the lower corner of the screen and with whole screen black (when true)/

Here's the simplest case I could come up with
package;

import openfl.display.Bitmap;
import openfl.display.BitmapData;
import openfl.display.Sprite;
import openfl.events.Event;

class Main extends Sprite
{
	public function new()
	{
		super();

		var foo = new Sprite();
		foo.graphics.beginFill(0x700070);
		foo.graphics.drawRect(0, 0, 200, 200);
		foo.graphics.endFill();
		var bar = new Sprite();
		bar.graphics.beginFill(0x007000);
		bar.graphics.drawRect(-50, -50, 100, 100);
		bar.graphics.endFill();
		bar.x = 150;
		bar.y = 150;
		foo.addChild(bar);

		foo.cacheAsBitmap = true;

		var foobarBD = new BitmapData(200, 200, false, 0x700707);
		var foobar = new Bitmap(foobarBD);
		foobarBD.disposeImage();
		addChild(foobar);
		foobarBD.draw(foo);
		addEventListener(Event.ENTER_FRAME, (e:Event) -> {
			foobarBD.draw(foo);
		});
	}
}

I can confirm that this is also happening to us.
7.1.2 is working properly
8.3.0 is working properly
8.4.1 A transparent bitmap is drawn

It was fixed recently, but be aware that the whole gl renderer context handling has been rewritten - check if latest git version works for you

Thanks Misiur.
I know..., I opened another issue related to WebGL context lose with IE11, that is happening with the new renderer. For the time being we have switched to canvas.

Looks good in current release :+1:


Simple mini train and test example?

As always, great appreciation for your prompt and illustrative implementation. Thank you very much.
Is it possible to implement some simple mini examples to train and test with current framework implementation repo alongside your repo. That will immensely speed up community understanding of closed source results and perhaps accelerate the test of their claimed results.
Cheers Patrick

patience, the paper came out 2 days ago

patience, the paper came out 2 days ago

From read me I only see fragments of code
I would like to make a tutorial for this repo on my channel SECourses
I already have a great tts tutorial but yours looking even better
Master Deep Voice Cloning in Minutes: Unleash Your Vocal Superpowers! Free and Locally on Your PC


dapr init --slim gives me - error moving dashboard.exe binary to path: rename

I am trying to do this dapr slim sample.
I ensure a clean slate by running dapr uninstall --all.
Then I start with the first step of Slim Init.
error moving dashboard.exe binary to path: rename C:\Users\UserName\.dapr\bin\release\windows_amd64\dashboard.exe C:\Users\UserName\.dapr\bin\dashboard.exe: Access is denied.
Note below I am running powershell as administrator.

What am I missing?

Ok, I think I understood the problem.
While I ensured a clean slate by running dapr uninstall --all, I noticed dapr dashboard is still running in the background.
When I run dapr uninstall --all I feel dapr dashboard, if its running, must be also be stopped.

@AvtsVivek can you please close this issue and create an issue with the CLI repository?

Close issue


Pypi deploy

This is basically the same thing as https://github.com/typesupply/fontMath/pull/34, but adapted for defcon.
The version has been 0.1 since forever; I was not brave enough to set it to 1.0.0, so I set it to 0.2.0 for now. If Tal wants, we can tag 1.0.0.

Defcon 0.2.0 is now on PyPI:
https://pypi.python.org/pypi/defcon


add note about removing localhost-only binding

Continues from https://github.com/plausible/community-edition/pull/111#issuecomment-2017136845

I understand the reasoning why you didn't want to merge the PR :) Given my unique implementation I didn't want to modify source files in case of updates so I've created a override file for it now: https://github.com/StartEnv/projects/blob/main/plausiblecommunityedition/docker-compose.override.yml
Your doc change looks good to me! You could mention using an override file instead, but for 99% of the users modifying the existing docker compose file makes more sense.

Oh, I didn't know about override files. I'll open an issue to remember to document them.


autoclean

From comments of #7: Could have drain --autoclean delete any step output that is:
missing a target file (i.e. never successfully ran)
stale target, which can be determined by trying to construct the given object:
    if it fails to construct then something is wrong with the args (signature changed, etc.)
    if it constructs, then collect all source code timestamps for all inputs and ensure target timestamp is newer.

need to be careful though. could have an interactive mode or dump a list of steps eligible for cleanup.

Deleting missing targets is now possible with:
drain list --complete --invert | xargs rm -r

@geneorama fyi


Adding large_string to duckdb-index worker and tests

Fix for https://github.com/huggingface/dataset-viewer/issues/2613

The idea is to recompute the datasets manually, right? I imagine that only few datasets use this type.

The idea is to recompute the datasets manually, right? I imagine that only few datasets use this type.

Yes, I will put here the datasets that were refreshed when it is ready.

(the number is enough... better not to give the names, as some might be private)

I will refresh 3364 splits; the logic is:  Get all datasets with "text" modality and intersect with the list of splits with "has_fts": false.

OK. Maybe some datasets have both string and large_string: we will not refresh them, right? Is it a way to find them too? I think the answer is no, without scanning every "/info" response

OK. Maybe some datasets have both string and large_string: we will not refresh them, right? Is it a way to find them too? I think the answer is no, without scanning every "/info" response

In case they had both (string and large_string), they should already be "has_fts": true, so there should be no refresh for them.


Add re-center button to Nearby map (in feature branch)

After testing the Nearby feature in directNearbyUploads branch for a bit, I really think that we need to provide a way for users to re-center the map on their current location. Users will be swiping a lot to switch between the list and the map - and if they swipe wrongly and move the map away, they have to reload Nearby or manually go back to their location.
I do recall that we discussed this somewhere else and it was mentioned that the Material guidelines recommend not having more than 1 FAB in the screen. However, I think that a small re-center icon on the upper right would not be amiss, especially given that our other FAB is actually in the bottom sheet and not on the map itself. For reference, Google Maps also uses 3 FABs, 1 of which is the re-center button.
Thoughts?

Thanks for the feedback, guys. :) If anyone is interested in implementing this, please remember to work from (and submit the PR to) the directNearbyUploads  feature branch, and not master.

I would like to work on this issue. Thanks :)

Solved.


Support text/html outputs too

xeus-sql produces text/html output,
and that crashes the browser if users forget a WHERE clause. This PR makes
the extension limit HTML output as well.
This might break in weird ways as 'pagination' doesn't quite work the same
with HTML. Perhaps something to be hidden behind an option?

Just cleaning up my open PRs - please do feel free to re-open if there is interest in getting this merged.


How should i use multiple clients?

import { defineNuxtPlugin } from '#app'
import { DefaultApolloClient } from '@vue/apollo-composable'
import { authApolloClient, catalogApolloClient, apolloProvider } from '~/apollo-client'

export default defineNuxtPlugin(nuxtApp => {
  nuxtApp.app.provide(DefaultApolloClient, authApolloClient)
  nuxtApp.app.provide('gateway', catalogApolloClient)
})

await useQuery(CATALOG_LOCALES_QUERY, null, {
        clientId: 'gateway'
      })

this code leads to error:  Uncaught (in promise) Error: No apolloClients injection found, tried to resolve 'gateway' clientId
So how should i use multiple clients with vue 3 (nuxt 3) and with composition api?
It is working with setting default client, but not with multiple.

https://v4.apollo.vuejs.org/guide-composable/setup.html#multiple-clients


B2

PR for B2

confirmed:B2

confirmed:B2

confirmed:B6

confirmed:B6

Form Submitted 2022-04-29 17:30 JST(UTC+9)


'push' sub-command for the 'registry' command

Hi @kcq, is this issue still relevant? It seems 'push' sub-command already exists. I would like to contribute to this if anyone still needs to fix it.

@shogohida there's a placeholder for the 'push' subcommand, but there's no actual 'business logic' for it. The push handler (OnPushCommand: https://github.com/slimtoolkit/slim/blob/master/pkg/app/master/commands/registry/handler.go#L146 ) just prints that it's done and that's it :-)


Header Guards for C++ applications to call CFE, OSAL, PSP

Checklist (Please check before submitting)

[x] I reviewed the Contributing Guide.
[x] I reviewed the cFS README.md file to see if the feature is in the major future work.
[x] I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

Describe the solution you'd like
Wrap all public headers in CFE, OSAL, and PSP in hedaer guards that allow inclusion from C++ translation units:
#ifdef __cplusplus
extern "C" {
#endif

<content>

#ifdef __cplusplus
}
#endif

Describe alternatives you've considered
The alternative is to wrap the #includes in the calling apps with the header guards.
Additional context

<EMAIL_ADDRESS>https://github.com/nasa/cFS/discussions/659
<EMAIL_ADDRESS><EMAIL_ADDRESS>
Requester Info
Isaac Rowe, NASA JSC, Jacobs Technology

CCB 21 November 2024: Closing as we don't test C++ support.


correct the return statement of _init_infer_auto_device_map

What does this PR do?

Fixes #3276
Before submitting

[x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
@SunMarc
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Thanks for working on a fix! Think this still doesn't 100% solve it since there are still some errors.


Don't include this function types in completeFunctionCalls

This PR fixes #104877

What issue does this fix?

Typescript allow annotating this parameter https://www.typescriptlang.org/docs/handbook/functions.html#this-parameters
function f(this: void) {
  // make sure `this` is unusable in this standalone function
}

Because this parameters are fake parameters, I think we should skip these.

Thanks. Can you also create a normal issue to track this problem. This helps us track issues and verify this PR fixed it

I had created #104877 to track this issue. Thanks.

Thanks! This will be in the next VS Code insiders build and is scheduled to ship with VS Code 1.49


Update docs for Advanced Bare Metal cluster configuration:

Issue #, if available:
Description of changes:
We changed to embedded images which necessitated the doc update.
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm


FP8 Linear and conv with cudnn

🚀 Feature
CuDNN provides flexible support for performant gemm/conv with fp8 quantization. Thunder introducing fp8 casts in its traces can benefit from cudnn fusions.
Motivation
Today, thunder uses TE's fp8 linear which delegates quantization strategies to TE, making it opaque to thunder. If thunder plans to handle fp8 casts itself, performant and flexible kernels from cudnn can help.
Cudnn's support is described here: cuDNN's runtime fusion engine
For fp8 specifically, cudnn can provide the following graph as one fused kernel:

The graph is flexible, meaning:

final output, C, can be in fp16/bf16/fp32.
amax operation can be skipped for static scaling strategies

The corresponding backward graphs are also supported. (Though they require offline transpose on Hopper)
Pitch
Have cudnn executor claim gemm/conv along with the fp8 casts around them.
CC @IvanYashchuk @kshitij12345 @Anerudhan

Thank you for creating this issue! I think it should be possible to use TransformerEngine as the scaling recipe manager and cuDNN as the performance driver in Thunder.


Implement LogUp in PIL

Similar to how we already implemented a permutation argument in PIL (see #1297 and #1306), we could implement a variant of LogUp (also see this summary).
As a first version, it could look like this:

A witness column m is added, containing the multiplicities. For now, we can only provide them via a hint for a concrete example (adding support by automatic witness generation is a next step).
A helper column h is added for each lookup, supposed to contain $h_i = h_{i - 1} + \frac{1}{\alpha - a_i} - \frac{m_i}{\alpha - b_i}$ (with $h_0 := 0$). This can also be provided via a hint. Note that in the original LogUp, they don't add $h_{i - 1}$ and instead run the sum-check protocol on the entire column. But our backends don't expose sum-check, and I don't see a big downside of this approach!
The last cell of $h$ should be constrained to be $0$

So I think, the constraints would look something like this:
h' * (alpha - A) * (alpha - B) = h * (alpha - A) * (alpha - B) + (alpha - B) + m * (alpha - A);

# Actually, I don't think this constraint is needed for soundness, because of the wrapping
IS_FIRST' * h = 0;

(Note that because of wrapping $h_0 = h_4 = 0$, so row $1$ does not have to be handled separately.)
This leaves out two details, which should be handled analogously to the permutation argument:

If we look up tuples of values, the tuple should be folded first, using another verifier challenge.
If the field is too small, these operations need to happen on an appropriate extension field (see #1306).

Compared to the original LogUp, this implementation lacks some optimization applicable to multiple lookups, especially if they have the same left-hand side. But I think it would be a good first step and allow for some first benchmarks already.

@georgwiese I think the first constraint should be fixed from
h' * (alpha - A) * (alpha - B) = h * (alpha - A) * (alpha - B) + (alpha - B) + m * (alpha - A);
to
h' * (alpha - A) * (alpha - B)  + m * (alpha - A) = h * (alpha - A) * (alpha - B) + (alpha - B);


Too many syntax object types in macros

So it turns out we can't quite remove SyntaxOrTermWrapper like I thought. I'd forgotten about the inner method that returns a new MacroContext, which is necessary because it allows expand inside of delimiters.
So currently a macro can get:

a SyntaxOrTermWrapper via ctx.next().value
a SyntaxTerm via #``foo``.get(0)

Previously it was:

a SyntaxOrTermWrapper via ctx.next().value
a Syntax via #``foo``.get(0)

I'm not a fan of macro authors needing to know about two different representations of the syntax, but I'm not really sure what else to do about it. Maybe the distinction can be papered over by a higher-level API macro authors import in? Maybe we modify SyntaxOrTermWrapper to behave a bit more like  a Term but with the inner method still being special?

What about exposing a ctx.createContext which takes a RawDelimiter?
let syntax m = ctx => {
  const inner = ctx.next().value.val();
  const innerCtx = ctx.createContext(inner);
// ...
}
m(1,2,3)

Yeah, that might work. I think we had something like that early on but switched to inner on the wrapper for a more ergonomic API. Consistency in the types is more important than a slightly more convenient way to "contexify" a delimiter.

That was my thinking. With your changes wrapping all of the SyntaxTerms is just unnecessary overhead.
Not sure about the name though. wrap? create? contextify?


disk_util: use FAT32 on ESP

mkfs.vfat was defaulting to FAT16 based on the size of the partition. The UEFI spec (2.7 errata A, section 13.3) implies that only FAT32 is necessarily supported on the ESP, and we've received a report of hardware that doesn't recognize FAT16.
Addresses https://github.com/coreos/bugs/issues/2246.

What's the implication of this with systems updating. I'm assuming we'll end up with people provisioning new machines having fat32 and old machines having fat16?

Sadly, yes.


custom music options | might take a bit though, idk, im dumb

What feature do you want to get added on the base engine?
title is explainable. also, the ones im talking about is the "pause and menu" songs. if you dont want them, for example: you want to remove the mashup menu music, you can just remove that
Note: i picked the "Better LUA mod support idea" because some people don't know how to do source coding or just lazy (no offence to that, im lazy to)
To test your sight, and reliability, please select the option of what should NOT be requested.
Better LUA mod support idea

it’s already possible to change the pause songs wtf do you mean by this?

im saying like, more pause songs (and menu)

im saying like, more pause songs (and menu)

more pause songs = more size

im saying like, more pause songs (and menu)

more pause songs = more size

basically yeah, but it’s already possible to do anyways just by editing the source code, but I will add lua support perhaps soon

n i c e


feat: wasm-bindgen support

This PR makes ic-agent and ic-utils available in the browser through wasm-bindgen.
Fixes #360.

Selenium isn't necessary if you have a frontend, wasm-bindgen has its own unit test system. Writing a frontend that actually encases all the behavior, on the other hand, would be more work than writing the mock backend, and then you'd still need a backend.


[Feature] Add customizable PayNym names

As every paynym has a rather generic name it is hard to remember the nyms from people you know in real life or have a closer yet pseudonymous relationship (like with a Twitter handle).
If one could add an additional, customizable name this would help to link the generic name of the nym to the name under which you know the person.
I don't know if this has implications on the potential for doxxing someone though (say you're in a chat group like Telegram, you could sample the PayNyms from different people and create a list linking the nyms to the avatars->person->potential phone numbers in the chat group). But considering that people could do such a linking on a spreadsheet anyway, I don't think there is an elevated risk for such kind of things?

Implemented in c02da60. This was already possible for linked payment codes (without PayNyms) implemented in a765e07, so adding this was fairly simple. Renaming a linked PayNym contact is possible by right-clicking on it in the PayNym dialog.


Remove cstbool library

https://en.cppreference.com/w/cpp/header/cstdbool
Pull request
Choose Correct

[X] bug
[ ] feature

Describe the pull request
Based on https://en.cppreference.com/w/cpp/header/cstdbool the library is deprecated and removed.
To Reproduce

Expected behavior
Nothing changed
Screenshots

Desktop (please complete the following information):

OS:
eRPC Version:

Steps you didn't forgot to do

[X] I checked if other PR isn't solving this issue.
[X] I read Contribution details and did appropriate actions.
[x] PR code is tested.
[X] PR code is formatted.
[ ] Allow edits from maintainers pull request option is set (recommended).

Additional context

Thanks for the effort!


Liqo on GKE initializing service type of liqo-gateway and liqo-auth services as ClusterIP, preventing peering

What happened:
When liqoctl==0.8.3 is used to install Liqo on a GKE cluster, the liqo-gateway and liqo-auth services are (correctly) created with the ClusterIP setup (as in the docs). However, following the docs by heart and attempting to peer (both ib and oob) with the cluster results in the following error:
 ERRO   (local) an error occurred while retrieving WireGuard configuration:
 service {liqo/liqo-gateway} is of type {ClusterIP}, only types of {LoadBalancer}
 and {NodePort} are accepted

What you expected to happen:
Either throw an error during Liqo installation, prompting the user not to use ClusterIP and to use the network flag.
How to reproduce it (as minimally and precisely as possible):

Install liqoctl==0.8.3
Create a GKE cluster and install Liqo with no network flags
Create any other cluster and install Liqo with any configuration
Attempt to peer both in-band and out-of-band with the cluster

Anything else we need to know?:
I am aware that the Liqo docs specify the network flags allowing to choose between ClusterIP, LoadBalancer and NodePort. I am also aware that users must read the documentation of their provider before installing Liqo.
However, this approach confuses users as unless they realize they need not to use ClusterIP, after receiving this error they will have to uninstall and re-install again (or edit services manually). Alternatively, GKE Liqo installation could by default point to LoadBalancer instead.
Environment:

Liqo version: 0.8.3
Kubernetes version (use kubectl version): v1.27.1
Cloud provider or hardware configuration: Clusters on GKE; running machine Ubuntu 22.04 LTS on x86_64

Hi @mfranzil, can you provide us the command you used to install Liqo? Did you force the creation of ClusterIP services in some way? Did you customize the helm values?
What you are observing (the creation of a ClusterIP services) is not correct, Liqo should use a UDP LoadBalancer service for the liqo-gateway and a TCP LoadBalancer (or ClusterIP, in case it is exposed using an Ingress) for liqo-auth.

Hi, Liqo was installed with the following command:
liqoctl install gke --project-id ${GKE_PROJECT_ID} \
    --cluster-id ${GKE_CLUSTER_FIRST_ID} \
    --zone ${GKE_CLUSTER_FIRST_ZONE} \
    --credentials-path ${GKE_SERVICE_ACCOUNT_PATH} \

where I had to append --service-type LoadBalancer in order to make it work.

Once I introduced the ServiceType flag, everything worked smoothly (at least with an out-of-band peering).

Hi @mfranzil, it is a well known bug of the CLI. It has been solved here, but we have not published a new release yet.


Fix NULL Checks and Error Handling

This PR primarily addresses potential NULL pointer dereference issues, enhances error handling, and resolves possible memory leaks in failure scenarios.
There are no new features or behavior changes introduced in this PR; the modifications are solely focused on improving stability.

@baentsch This PR is ready for review. Thanks

Thanks for the substantial amount of work, @songlingatpan ! This clearly improves the code resilience. Due to the size of the PR I had to stop in the middle of the review but would like to ask you to bring back the comments deleted (or explain why you deleted them) as well as provide an explanation what you did to the composite logic so I can better follow all changes there. Thanks!

Sorry @baentsch. I will add comments back.
The oqsx_key_op function was quite large, so I refactored it into smaller, more functions such as allocate_and_copy_keymaterial, oqsx_key_process_composite_keys, and process_private_key. However, the logic remains unchanged.
Thanks a lot again for your incredible work on the OQS provider.

this makes it easier to reason about code correctness and safety.

It would also be good to hear @baentsch's perspective on this as the primary developer and maintainer of the codebase.

I agree -- the ...free.... functions typically handle NULL objects gracefully. And I also agree, too many safety checks make the code hard to read.
But then again, there's lots of other code that's harder to read/understand/maintain than these added checks.
Maybe using macros might be a compromise?

this makes it easier to reason about code correctness and safety.

It would also be good to hear @baentsch's perspective on this as the primary developer and maintainer of the codebase.

I agree -- the ...free.... functions typically handle NULL objects gracefully. And I also agree, too many safety checks make the code hard to read.
But then again, there's lots of other code that's harder to read/understand/maintain than these added checks.
Maybe using macros might be a compromise?

Thanks for the comments.
We see quite some crashes due to dereference NULL pointer in our load testing. That is why we aggressively add NULL checks.
I will remove unnecessary NULL checks.

@baentsch @SWilson4
When we encountered crashes, we reviewed the related functions and added NULL checks. I agree that, in some cases, we may have been overly cautious with these checks. The reason for this approach is that we were consistently seeing crashes in various places, so we aimed to go through the files one by one and add protective code.
I will go ahead and remove the unnecessary NULL checks.
Thank you again for the excellent work you've done on building the OQS code.
`#0  0x00007ffff67c20f2 in evp_md_init_internal (ctx=0x0, type=0xd4661daf00, params=0x0, impl=0x0) at crypto/evp/digest.c:166
#1  0x00007ffff67c26ee in EVP_DigestInit_ex (ctx=, type=, impl=) at crypto/evp/digest.c:385
#2  0x00007ffff1a9ac63 in do_hash (md=0xd4661daf00, inplen=64, input=0x7fffdfd8cde0 "s\315~jQ\261\224 \032\025\346\243\201\354\340\240\004:*7\020o`e\177\326d\263Z\215\251\253\225E\002\361\340L\305\b\334\nD;\365d5\004\005\066\302\060\264\024\060<\n\331", output=0x7fffdfd8ce20 "") at ../src/common/sha3/ossl_sha3.c:22
#3  OQS_SHA3_sha3_512 (output=0x7fffdfd8ce20 "", input=0x7fffdfd8cde0 "s\315~jQ\261\224 \032\025\346\243\201\354\340\240\004:*7\020o`e\177\326d\263Z\215\251\253\225E\002\361\340L\305\b\334\nD;\365d5\004\005\066\302\060\264\024\060<\n\331", inplen=64) at ../src/common/sha3/ossl_sha3.c:110
#4  0x00007ffff1936a32 in pqcrystals_kyber1024_ref_dec (ss=0xd46bc1fa40 "", ct=0xd46970715a "\362,\325\005\240\317_NTC\267F3\233\325\234k\020\034\255\253\277\032\355\244\302^F\v*\312\334\315B\030\232\263\327j-\270\233~\236\352\304\260G'\016\252\217\274/}\275\r\ad\321!e5\305\356/\304\345oB \v\271\206\324\355/\346\211\302\236Z\337\311\230\243\334\370\314\246\354zD4\327{\373\063\315\366\372\347\233\233 \232\031\215<w\321\267/\031<4\021\226\065\360\242\226\240\347\063\267E\241I\301R\213\201\224\364/\354+\027\017\033\227\224Q"\327\311\233_\300\217\315H\343\370\273\346N\337\226=\r\305c\274\347t\332U\036\331\200\370l\324MvAi\365\356E\005\243\025mLK\277x4W\371i\235t4\211"..., sk=0xd46630c400 "l%G\342
{eD\232\062\363dh@\003V\213\311\244\375\303N4D\236/[\~\020)\212\240\310\363\200=\222V\a\304su\003\206\237|s~^)\313-\n\315\334v5Q\262\060\200\273i\322\227}
r`
`#0  OQS_SHA3_shake128_inc_squeeze (output=output@entry=0x7fffe1cb4590 "", outlen=outlen@entry=504, state=state@entry=0x7fffe1cb4588) at ../src/common/sha3/ossl_sha3.c:219
#1  0x00007ffff19362d1 in pqcrystals_kyber1024_ref_gen_matrix (a=a@entry=0x7fffe1cb5ff0, seed=seed@entry=0x7fffe1cb7ff0 "3nQ\371\341\231\063\271\067\305\370\240\264\306yTz\373\20
6O\353Z\251\030\001\t\006\255\376\210v!", transposed=transposed@entry=0) at ../src/kem/kyber/pqcrystals-kyber_kyber1024_ref/indcpa.c:179
#2  0x00007ffff1936454 in pqcrystals_kyber1024_ref_indcpa_keypair (pk=pk@entry=0xd46821a200 "", sk=sk@entry=0xd468509d00 "") at ../src/kem/kyber/pqcrystals-kyber_kyber1024_ref/in
dcpa.c:220
#3  0x00007ffff1936885 in pqcrystals_kyber1024_ref_keypair (pk=0xd46821a200 "", sk=0xd468509d00 "") at ../src/kem/kyber/pqcrystals-kyber_kyber1024_ref/kem.c:27
#4  0x00007ffff1f0afa5 in oqsx_key_gen_oqs (gen_kem=1, key=0xd036b634c0) at ../oqsprov/oqsprov_keys.c:1735
#5  oqsx_key_gen_oqs (gen_kem=1, key=0xd036b634c0) at ../oqsprov/oqsprov_keys.c:1732
#6  oqsx_key_gen (key=key@entry=0xd036b634c0) at ../oqsprov/oqsprov_keys.c:1858
#7  0x00007ffff1f0e85d in oqsx_genkey (gctx=0xd467fcc9c0) at ../oqsprov/oqs_kmgmt.c:613
`

@songlingatpan Thanks again for the diligent addition of safeguards to the code. However, I'm not sure I understand your latest comment: What should we do with these line items? Please also re-base to latest main. #524 changed a bit too much impacting other PRs :-(


release_v1.5.5

Merge it at the end.

Can be merged as I have tested basic functionality works fine here.

Hi,
What am telling part will not match for above discussion
About if the backup data is older which means 1 week or one month old this will be get deleted by automatically from directory or we need to do the deleting part.
Kindly help me


Fixed the readthedocs documentation build

Had to extend the docs/requirements.txt file to install
matplotlb (needed by the Gotchas notebook) and ".",
needed by everything. This results in a reduction
of the sphinx warnings from 3300 to 1200!

This is the passing RTD build: https://readthedocs.org/projects/jax/builds/9776228/

Addresses in part https://github.com/google/jax/issues/1433


Building with 1.0.3 package has linking errors

When I tried upgrading the NuGet package in this project to the latest version, I received undefined symbols when linking for all of the extension APIs (eg. xrGetD3D11GraphicsRequirementsKHR).

The loader does not export extension functions starting with 1.0.3. We've held off upgrading because the loader also has a bug which causes it to crash when using XrSpace handle created from an extension function (the spatial anchor extension). Hopefully the 1.0.6 or 1.0.7 loader will have the fix for this. This is why we've held off upgrading to the newer NuGet version.
FYI, once the change goes in to fix the problem in the loader (https://github.com/KhronosGroup/OpenXR-SDK-Source/pull/146) it will only support a single XrInstance at a time.

Apps will be required to use xrGetInstanceProcAddr to get function pointers for extension functions instead of statically linking to the loader. In the future we'll probably add some helper code to make this easier, something like GLEW.


Set default program for TSV files to Excel during installation

http://proteomicsnews.blogspot.com/2018/04/boring-stuff-thursday-2-how-to-make.html

Wait, we output .psmtsv which is a different extension than .tsv (despite being the same structure). We could automatically (without asking for permission) make .psmtsv defaulted to excel in the installer. This requires that the user has excel installed, though.

Yes, agreed! And yes, if they don't have Excel installed, there's not much to do here.

https://stackoverflow.com/a/2808320/9454443

done in #1335


Stuck partition on transactional producer - KAFKA-12671

Hello! I've managed to hit the stuck partition issue on a transactional producer once again 😄 and wanted to see if you had any further insight after our last conversation about this in https://github.com/twmb/kcl/issues/10.
As far as I can tell, here's what happened:

The producer is using version v1.9.1 of this library.
The producer idled for a long period of time (multiple days). During this time, it should have been doing a begin/abort transaction periodically to heartbeat the transaction ID (TBD whether there is a bug in this code path, this may have not been functioning?).
Our cluster seemingly had two unplanned leader elections during this idle period
On resume, the producer errored: INVALID_PRODUCER_ID_MAPPING: The producer attempted to use a producer id which is not currently assigned to its transactional id

This error has occurred before (a bunch of times) with no issues, as the service just restarts and begins producing on a new ID

The partition it was producing to is now stuck
Running the "unstick" command from kcl found the partition in question, but hung on on the step when it tries to find the transaction ID, i.e. . . .looking in __transaction_state to find its transactional id...

So somehow this seems to have triggered the KAFKA-12671 bug, and the transaction ID in question seems to be entirely missing. Is there any other diagnostic information I might be able to collect that might shed some light on exactly how this triggered? Obviously I'd like to avoid this happening again. I think my producer code might be mis-behaving on idle, and I'm thinking perhaps it makes sense to just shut down the producer entirely when its idling, rather than trying to keep the transaction alive. I'm also going to update to the latest version of this library, although I didn't see anything in release notes that would indicate that this issue has been revisited - is that correct?
No worries if you want to close this issue - I realize it probably isn't anything to do with this library at this point, but I thought it might be of interest to others.

With transactions, the client actually does not communicate with the server if nothing is going on. BeginTransaction is a signal for the client itself, nothing is written to the server. EndTransaction only writes the the server if something happened. So, eventually, the producer ID that was initialized expired. This is why when you eventually did communicate again, you saw INVALID_PRODUCER_ID_MAPPING -- the producer ID no longer exists.
However, things getting stuck is bad.
Is your partition still stuck?

Ah okay - it does seem like doing a BeginTransaction, a single produce, and then AbortTransaction does successfully keep the producer ID alive. It looks like the code that was doing this heartbeat was occasionally not running in some circumstances and I'm guessing that combined with broker restarts somehow caused us to hit this issue.
Yeah, the partition appears to be permanently stuck. The application uses a custom partitioner though, so I was able to work around this by moving all that partition's data to another partition. Not ideal, but better than re-creating a topic! We can close this if you like - thanks for the insight as always.

If it’s still stuck, we can try interactively debugging it on the discord
channel?
On Thu, May 11, 2023 at 09:08 Zach Johnson @.***> wrote:

Ah okay - it does seem like doing a BeginTransaction, a single produce,
and then AbortTransaction does successfully keep the producer ID alive.
It looks like the code that was doing this heartbeat was occasionally not
running in some circumstances and I'm guessing that combined with broker
restarts somehow caused us to hit this issue.
Yeah, the partition appears to be permanently stuck. The application uses
a custom partitioner though, so I was able to work around this by moving
all that partition's data to another partition. Not ideal, but better than
re-creating a topic! We can close this if you like - thanks for the insight
as always.
—
Reply to this email directly, view it on GitHub
https://github.com/twmb/franz-go/issues/451#issuecomment-1544167439, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJZIJIRWEHZ262U4YRBKT3XFT6HBANCNFSM6AAAAAAX3X3YZE
.
You are receiving this because you commented.Message ID:
@.***>

Sure, what discord? I'm also in the redpanda slack, I can message you on there.

For posterity: we had a conversation on Slack, but since it's been a week and this is production data, we've decided to just leave the partition broken. My theory for how to fix likely wont work anyway because the txid is expired, and my known way to fix requires the txid to at least exist within the broker -- if it's been too long, my fix can't work.


pull request for e2e test at 12/08/2016 19:15:03

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update dataset lecture

This is a new version of the dataset lecture for Colibri repository.

Please create a demo_dataset.py

update datasets.rst and mention there the available datasets

maybe in the demo you could also show how the data readers work for not built in datasets

maybe in the demo you could also show how the data readers work for not built in datasets

The cave dataset was added to the demo example

couldn't find in the docs

i think it would be great if you could include in the docs the documentation of the class CustomDataset

couldn't find BASIC_DATASETS in the docs

Solved!


Q changes drastically changes volume of poly-synth.

There is a drastic change in volume when the Q value of the synthesizer is non-zero.

Fixed in PR #112


fix: adapt to upstream clap changes

This was introduced in #83
See https://github.com/clap-rs/clap/blob/master/CHANGELOG.md#migrating

Integrated in #88


'ansible_ssh_user' is not set?

I'm getting an error with RVM.
==> rails-dvlasov: TASK [ruby : Install rvm] ****************************************************** ==> rails-dvlasov: fatal: [<IP_ADDRESS>]: FAILED! => {"changed": true, "cmd": ["/tmp/rvm-installer.sh", "stable", "--path", "/home//.rvm", "--auto-dotfiles", "--user-install"], "delta": "0:00:00.021989", "end": "2016-04-12 18:38:47.655138", "failed": true, "rc": 1, "start": "2016-04-12 18:38:47.633149", "stderr": "mkdir: cannot create directory ‘/home//.rvm’: Permission denied", "stdout": "Turning on auto dotfiles mode.\nTurning on user install mode.", "stdout_lines": ["Turning on auto dotfiles mode.", "Turning on user install mode."], "warnings": []} ==> rails-dvlasov:      to retry, use: --limit @/ansible/site.retry ==> rails-dvlasov: ==> rails-dvlasov: PLAY RECAP ********************************************************************* ==> rails-dvlasov: <IP_ADDRESS>                  : ok=28   changed=4    unreachable=0    failed=1 The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong.
It looks like a bug with this line:
rvm1_install_path: '/home/{{ ansible_ssh_user }}/.rvm'

I had the same error (on Windows). Changing to
rvm1_install_path: '/home/{{ user_name }}/.rvm'

let me to get past this point.


Need List All functionality in UI

As a marketing manager
I need the ability to list all Promotions in the UI
So that I do not need to use the CLI in order to view all of the existing promotions
Details and assumptions

This feature should be embedded in the UI described by #41

Acceptance criteria
When I visit the "Home Page"
    And I set the "Name" to "Half-off sale!"
    And I select "Percent Discount" in the "Type" dropdown
    And I set the "Discount" to "50"
    And I set the "Customer" to "-1"
    And I set the "Start Date" to "08-01-2022"
    And I set the "End Date" to "09-01-2022"
    And I press the "Create" button
    Then I should see the message "Success"
    When I copy the "Id" field
    And I press the "Clear" button
    Then the "Id" field should be empty
    And the "Name" field should be empty
    And the "Type" field should be empty
    And the "Discount" field should be empty
    When I paste the "Id" field
    And I press the "Retrieve" button
    Then I should see the message "Success"
    And I should see "Half-off sale!" in the "Name" field
    And I should see "Percent Discount" in the "Type" dropdown
    And I should see "50" in the "Discount" field
    And I should see "2022-08-01" in the "Start Date" field
    And I should see "2022-09-01" in the "End Date" field

modify acceptance criteria

as a quick heads up @happydl -- looks like the acceptance criteria here were pasted from my Create story, so they'll need to be tailored for this specific functionality


[MH] Improve the performance of schema change index backfills

Background: https://airtable.com/tblD3oZPLJgGhCmch/viw8IfZMg9Up8SP33/recez89kyYFXFl8Ih
PM: @awoods187
Eng Partner: @vivekmenezes

Moved to 2.2.

Closing in favor of https://github.com/cockroachdb/docs/issues/4014.


[Question]: TS Command Removal?

What is your question?
Did ts get removed from the project? Is there a plan to bring it back?

go install github.com/danielmiessler/yt@latest

yt is the youtube tool. ts was used for local files.

I guess it was accidentally removed during the Go rewrite.


Needs to be updated to new version I guess

I think it needs to be updated to new client (<IP_ADDRESS>.0).

btw I have offer for it working
Stoner#8065


Back ported logjam vulnerability changes from 1.0.1 to 0.9.8

Below commits from 1.0.1 branch are back ported to 0.9.8:

client: reject handshakes with DH parameters < 768 bits
(https://github.com/openssl/openssl/commit/63830384e90d9b36d2793d4891501ec024827433)

Update documentation with Diffie-Hellman best practices.
(https://github.com/openssl/openssl/commit/ff4de7dde90d15b366abe4664b904f22539969c9)

dhparam: fix documentation.
(https://github.com/openssl/openssl/commit/3372aeed2ce056af9d577a0d79b34dd7f9b67dad)

dhparam: set the default to 2048 bits.

(https://github.com/openssl/openssl/commit/8568170d774f02880eec6cad5512f555d0c83f65)

s_server: Use 2048-bit DH parameters by default.
(https://github.com/openssl/openssl/commit/f1612746ec7580132f81fb81a23f6705e63d113b)

After applying the above commit changes to 0.9.8 stable branch, I could
find the following o/p from the test logs.
Step-1: Generate DH parameters with 767 and 512 bits.
openssl dhparam -out dh767.pem 767
openssl dhparam -out dh512.pem 512
Step-2: Start openssl s_server with the above created DH parameters.
openssl   s_server  -dhparam  dh767.pem -accept 1234 -cert server.crt
-key server.key
Step-3: connect s_client to the above server
openssl s_client -connect x.x.x.x:1234
Following error shows in the s_client side:
20422:error:14082174:SSL routines:SSL3_CHECK_CERT_AND_ALGORITHM:dh key
too small:s3_clnt.c:2599:
And from s_server side shows following error message.
ERROR
23019:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake
failure:s3_pkt.c:1143:SSL alert number 40
shutting down SSL
Step-4: start s_server  with DH parameters more than 767 bits (Example
1024 and 768)
openssl   s_server  -dhparam  dh1024.pem -accept 1234 -cert server.crt
-key server.key
Step-5: connect s_client to the above server
The connection succeeds without any error messages.
From the above test logs, It looks like the changes are working fine for
0.9.8 branch.

Given that 0.9.8 is soon to be EOLed, this can probably be closed.

Agreed. This will not be backported to 0.9.8. Closing.


feat: add node metadata.

What type of PR is this?

/kind feature
What this PR does / why we need it:
add node metadata,config in  kubeclipper-agent.yaml report to kc-server by kc-agent.
Which issue(s) this PR fixes:

Fixes #
Special notes for reviewers:
1.kcctl deploy/join add --fip flags.
2.format kubeclipper-agent.yaml add metadata struct.
3.synchronization update deploy config cmd.

Does this PR introduced a user-facing change?

None

Additional documentation, usage docs, etc.:

/assign @x893675

Codecov Report

Merging #81 (b914e39) into master (2b824b0) will increase coverage by 0.14%.
The diff coverage is 32.65%.

@@            Coverage Diff             @@
##           master      #81      +/-   ##
==========================================
+ Coverage   11.66%   11.81%   +0.14%
==========================================
  Files          98       98
  Lines       15009    15059      +50
==========================================
+ Hits         1751     1779      +28
- Misses      13029    13046      +17
- Partials      229      234       +5

Impacted Files
Coverage Δ

pkg/cli/deploy/config.go
0.00% <ø> (ø)

pkg/cli/join/join.go
0.00% <0.00%> (ø)

pkg/cli/deploy/deploy.go
16.28% <11.11%> (+0.15%)
:arrow_up:

pkg/cli/join/agent.go
73.40% <65.90%> (-7.37%)
:arrow_down:

pkg/component/nfs/nfs.go
0.58% <0.00%> (-0.02%)
:arrow_down:

/milestone v1.2.0

/cc @zhuzhenfan @qinyer

/lgtm

/cc @x893675

/lgtm
/approve


decode_reserved

Well, this is a new one:
Uncaught ReferenceError: decode_reserved is not defined
    at decode_type (bundle-ui.js:43642)
    at Object.decode (bundle-ui.js:43654)
    at bundle-ui.js:80851
    at bundle-ui.js:122305
    at getData (bundle-ui.js:25412)
    at bundle-ui.js:25423
    at getBlock (bundle-ui.js:25392)
    at get (bundle-ui.js:25421)
    at bundle-ui.js:25583
    at Object.log.get (bundle-ui.js:122301)

Evidently in this case, type == 7, which I found out by adding a decode_reserved function, sticking a breakpoint on it, and walking back up the call stack to decode_type.

(Oh, and for my own reference in case I need to duplicate this later, this shows up when I click the Threads page of ssb-browser-demo on my normal profile tab.  So that query's the one that triggers this.)

Sorry for the delayed response - been a little busy. Because of that busyness, I haven't been active enough with ssb-browser-demo to really know if this is fixed yet.

Still would be nice to fix this as its clearly a bug if you hit that somehow

dones


Swipe action doesn't work on ios10.2

New Issue Checklist

[x] I updated BulletinBoard to the latest version.
[x] I read the Contribution Guidelines.
[x] I read the documentation.
[x] I searched for existing GitHub issues.

Issue Description
how to reproduce

launch sample app(BB-Swift Scheme)
press "Show Intro" button on the right navigation barbutton item
try to swipe up/down
then bulletinBoard and dimmed view doesn't respond anymore, only way to dismiss is just kill the app by pressing home button and open an app again.

quick workaround
just comment out of BulletinSwipeInteractionController.swif line 45 prepareGestureRecognizer(), though pan action cannot be usable.
Environment

iOS Version: [ios10.2]
Device(s): [iphone6s, not simulator]

This issue seems to be fixed with version 2.0.0-beta.3, as changes have been made to the swipe gesture recognizer (users have to lift their finger to complete the dismissal). Please feel free to reopen this issue if you manage to reproduce it on this version or a later one.


Run NPM scripts as tasks

I really appreciate the ability to run NPM scripts as tasks from the sidebar, but I often resort to running the tasks instead because I need to run them in background mode, with a problem matcher
It would be nice if when running an npm script I would start the corresponding task, if found
I already coded a solution, will send a PR shortly

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

@marcellourbani thanks for looking into this - it already seems to work for me

Pls lmk if i'm missing something
https://github.com/microsoft/vscode/assets/29464607/ef48b479-a363-4bdb-879d-2c2a25863184


Rule can only have one resource source

Version
create-nuxt-app: v.5.0.0
node: v16.19.0
npm: v8.19.3
Steps to reproduce
npx create-nuxt-app test-nuxt
create-nuxt-app v5.0.0
✨  Generating Nuxt.js project in test-nuxt
? Project name: test-nuxt
? Programming language: TypeScript
? Package manager: Npm
? UI framework: Element
? Template engine: HTML
? Nuxt.js modules: Axios - Promise based HTTP client
? Linting tools: ESLint, Prettier, Lint staged files
? Testing framework: None
? Rendering mode: Single Page App
? Deployment target: Server (Node.js hosting)
? Development tools: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Continuous integration: None
? Version control system: Git

npm run dev
What is Expected?
It is expected that npm run dev runs the application without errors after a clean creation.
What is actually happening?
npm run dev

><EMAIL_ADDRESS>dev
> nuxt

 WARN<EMAIL_ADDRESS>is installed but ^4.46.0 is expected                                                                                16:45:29

   ╭───────────────────────────────────────╮
   │                                       │
   │   Nuxt @ v2.16.1                      │
   │                                       │
   │   ▸ Environment: development          │
   │   ▸ Rendering:   client-side          │
   │   ▸ Target:      server               │
   │                                       │
   │   Listening: http://localhost:3000/   │
   │                                       │
   ╰───────────────────────────────────────╯

ℹ Preparing project for development                                                                                16:45:29
ℹ Initial build may take a while                                                                                16:45:29
ℹ Discovered Components: .nuxt/components/readme.md                                                                                16:45:29
✔ Builder initialized                                                                                16:45:29
✔ Nuxt files generated                                                                                16:45:30

 ERROR  Rule can only have one resource source (provided resource and test + include + exclude) in {                                                                                16:45:30
  "type": "javascript/auto",
  "use": [
    {
      "loader": "/home/voxivoid/code/software-angels/test-nuxt/node_modules/babel-loader/lib/index.js",
      "options": {
        "configFile": false,
        "babelrc": false,
        "cacheDirectory": true,
        "envName": "client",
        "presets": [
          [
<EMAIL_ADDRESS>            {
              "corejs": {
                "version": 3
              }
            }
          ]
        ]
      },
      "ident": "clonedRuleSet-4.use[0]"
    }
  ]
}

  "type": "javascript/auto",
  "use": [
  {
  "loader": "node_modules/babel-loader/lib/index.js",
  "options": {
  "configFile": false,
  "babelrc": false,
  "cacheDirectory": true,
  "envName": "client",
  "presets": [
  [
<EMAIL_ADDRESS>  {
  "corejs": {
  "version": 3
  }
  }
  ]
  ]
  },
  "ident": "clonedRuleSet-4.use[0]"
  }
  ]
  }
  at checkResourceSource (node_modules/@nuxt/webpack/node_modules/webpack/lib/RuleSet.js:167:11)
  at Function.normalizeRule (node_modules/@nuxt/webpack/node_modules/webpack/lib/RuleSet.js:198:4)
  at node_modules/@nuxt/webpack/node_modules/webpack/lib/RuleSet.js:110:20
  at Array.map (<anonymous>)
  at Function.normalizeRules (node_modules/@nuxt/webpack/node_modules/webpack/lib/RuleSet.js:109:17)
  at new RuleSet (node_modules/@nuxt/webpack/node_modules/webpack/lib/RuleSet.js:104:24)
  at new NormalModuleFactory (node_modules/@nuxt/webpack/node_modules/webpack/lib/NormalModuleFactory.js:115:18)
  at Compiler.createNormalModuleFactory (node_modules/@nuxt/webpack/node_modules/webpack/lib/Compiler.js:636:31)
  at Compiler.newCompilationParams (node_modules/@nuxt/webpack/node_modules/webpack/lib/Compiler.js:653:30)
  at Compiler.compile (node_modules/@nuxt/webpack/node_modules/webpack/lib/Compiler.js:661:23)
  at node_modules/@nuxt/webpack/node_modules/webpack/lib/Watching.js:77:18
  at AsyncSeriesHook.eval [as callAsync] (eval at create (node_modules/@nuxt/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:42:1)
  at AsyncSeriesHook.lazyCompileHook (node_modules/@nuxt/webpack/node_modules/tapable/lib/Hook.js:154:20)
  at Watching._go (node_modules/@nuxt/webpack/node_modules/webpack/lib/Watching.js:41:32)
  at node_modules/@nuxt/webpack/node_modules/webpack/lib/Watching.js:33:9
  at Compiler.readRecords (node_modules/@nuxt/webpack/node_modules/webpack/lib/Compiler.js:529:11)
  at new Watching (node_modules/@nuxt/webpack/node_modules/webpack/lib/Watching.js:30:17)
  at Compiler.watch (node_modules/@nuxt/webpack/node_modules/webpack/lib/Compiler.js:244:10)
  at Compiler.compiler.watch (node_modules/time-fix-plugin/index.js:14:24)
  at wdm (node_modules/@nuxt/webpack/node_modules/webpack-dev-middleware/dist/index.js:263:24)
  at WebpackBundler.webpackDev (node_modules/@nuxt/webpack/dist/webpack.js:1835:7)
  at node_modules/@nuxt/webpack/dist/webpack.js:1797:23
  at new Promise (<anonymous>)
  at WebpackBundler.webpackCompile (node_modules/@nuxt/webpack/dist/webpack.js:1795:16)
  at async Promise.all (index 0)
  at async WebpackBundler.build (node_modules/@nuxt/webpack/dist/webpack.js:1779:5)
  at async Builder.build (node_modules/@nuxt/builder/dist/builder.js:249:5)
  at async Object._buildDev (node_modules/@nuxt/cli/dist/cli-dev.js:79:5)
  at async Object.startDev (node_modules/@nuxt/cli/dist/cli-dev.js:55:7)
  at async Object.run (node_modules/@nuxt/cli/dist/cli-dev.js:44:5)
  at async NuxtCommand.run (node_modules/@nuxt/cli/dist/cli-index.js:356:7)

I was having the same issues. Its not an official fix, but here is how you can fix it.
You must downgrade webpack to v4 and postcss to v7.
  "devDependencies": {
    "webpack": "^4.46.0",
    "postcss": "^7.0.32",
    "postcss-import": "^12.0.1",
    "postcss-import-resolver": "^2.0.0",
    "postcss-loader": "^3.0.0",
    "postcss-preset-env": "^6.7.0",
    "postcss-url": "^8.0.0"
  }

Next, if you have the following warning:

You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.

Set postcss property to null in your nuxt.config.js to fix it:
  build: {
    postcss: null,
  },

Hi,
I have the same problem, but there's none of these libraries:
devDependencies": {     "@nuxt/types": "^2.15.8",     "@nuxt/typescript-build": "^2.1.0",     "@nuxtjs/vuetify": "^1.12.3",     "@vue/test-utils": "^1.3.0",     "babel-core": "7.0.0-bridge.0",     "babel-jest": "^29.1.2",     "jest": "^29.1.2",     "jest-environment-jsdom": "^29.1.2",     "ts-jest": "^29.0.3",     "vue-jest": "^3.0.4"   }
My project setup:
C:\Users\xxx\dev>npm init nuxt-app@latest proj-test-ts-2 npm WARN config global--global, --localare deprecated. Use--location=global` instead.
create-nuxt-app v5.0.0
✨  Generating Nuxt.js project in proj-test-ts-2
? Project name: proj-test-ts-2
? Programming language: TypeScript
? Package manager: Npm
? UI framework: Vuetify.js
? Template engine: Pug
? Nuxt.js modules: Axios - Promise based HTTP client
? Linting tools: (Press  to select,  to toggle all,  to invert selection)
? Testing framework: Jest
? Rendering mode: Universal (SSR / SSG)
? Deployment target: Server (Node.js hosting)
? Development tools: (Press  to select,  to toggle all,  to invert selection)
? Continuous integration: None
? Version control system: Git
npm WARN config global --global, --local are deprecated. Use --location=global instead.
`

They are nested/referenced libraries.
You can see them in package-lock.json.


Use simpler callback

Replace the triple callback in filter_utils by a single one for Ethernet, and simplify code in keep function of DispatchFilter

Applied, thanks


Add cache busted files entries to deploy

Fixes
Broken production by marking files to be busted by cache buster.
Description
There's mechanism to mark files not to be cached between builds.
Type of change

[ ] Feature
[x] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

/retest


Form doesn't submit

I'm not sure why, but the following form doesn't submit:
<template name="customerItem">
{{#autoForm collection="Customers" id="customerItem" doc=updateItem type="update"}}
{{> afQuickField name='name'}}
<button type="submit" class="ui green submit button">Save</button>
{{/autoForm}}
</template>

AutoForm.addHooks('customerItem', {
  onSubmit: function (insertDoc, updateDoc, currentDoc) {
    console.log(arguments);
    return false;
  }
});

The input loads the correct data but clicking submit does nothing - no submission, no error, no onSubmit call. I think the reason is that no events were bound because the submit wasn't detected. If this is the case I suspect adding a console.warn() may be useful so the developer knows something is missing. But it could be something else entirely. I can confirm that this works:
{{> quickForm collection="Customers" id="customerItem" type="update" doc=updateItem}}

thanks for that debug hook.  however it didn't work for me (AutoForm was not defined) because i was pulling in aldeed:autoform from yogiben:admin.  i had to add it directly as a top level package to resolve AutoForm.  might want to add that to the docs :)

Dependencies aren't exposed to the app unless you use imply() in the package.js.


[Site]: Ahrefs.com Report

Current State
See attachment.
All issues — Apisix.apache.pdf
Desired State
Fix those issues.
Would you like to fix this issue?
No response

also cc @SkyeYoung @SylviaBABY @lijing-21 @reeseliu715 to have a look :) We could do something around this repot.


Keyboard Debugging

void debugKeyboard() {
while (!antKeyboard.checkKeyState(KEY_PRESS_ESC)) {
cout << "Key Code : " << (int) inportb(0x60) << endl;
}
}

Hey there!  Seems like this pull request may be erroneous.  If I'm reading this right, it will take a lot of commits from godot2-min and dump them into master which will cause a lot of problems.
I assume the code you commented in the pull request is actually what you want to add but I'm not sure where you intend it to be.  You may want to either correct the pull request or change branches you are trying to add code to.

Additionally you may need to re-pull whatever branch you were working on.

We got a similar spam PR: https://github.com/MonoGame/MonoGame/pull/6917
I bet this is for Hacktoberfest. Make sure you label this as invalid so it doesn't count.

Gotcha. Any thanks for the heads up!  Why do people do this....

Why do people do this

Free t-shirt :)

Haha, fair enough.  Still, a pretty crappy way to get a free shirt!


LL-8926: Fix polkadot bigInt issue

Type
Bug fix
Context
https://ledgerhq.atlassian.net/browse/LL-8926
I was able to fix this issues by taking an old version of the util lib.
The part of the problem was about BigInt into a Math.pow by using the ** operator in polkadot lib.
It's seems to be find for this version but I don't know if it will work for later version (spoiler 7.5.1 just released yesterday, and LLD doesn't work anymore with this version 😠 )
https://github.com/polkadot-js/common/issues/1262#issuecomment-983995745
Parts of the app affected / Test plan
Polkadot, probably would be nice to retest the flow, but add accounts was mainly impacted

oh yeah good point from @haammar-ledger

@haammar-ledger you told me yesterday but I'm still sleeping, I'm on my way


Fastnlight: Watch phonebotics.net

Fastnlight requests the watch of the watch_keyword phonebotics\.net. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

phonebotics\.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


[Feature] Use pg query to indent SQL

This might be ideal library to perform indentation of the SQL query as it is going to be always syntactically correct.
I propose some deparse options like indent

Hi @bogdan - The challenge we've had in the past is that everyone has different ideas on how SQL should be indented, so it wasn't clear whether this would be a good feature to have directly in pg_query. That said, maybe this is still useful to have, with potentially different styles that could be set.
If you'd like to contribute something that adds this, we'd need to add that in the libpg_query deparser (i.e. requires some C knowledge to add).


[TACHYON-1533] "bin/tachyon-mount.sh SudoMount workers" does not set the $bin variable

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7970/
Test PASSed.

Hi guys, I left some comments for you.
Regards.

I think should be better to change $DEFAULT_LIBEXEC_DIR variable inside all bin/tachyon-* files, can I make this change under this PR?

Jenkins, test this please.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8010/
Test FAILed.

Jenkins, test this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8021/
Test PASSed.

Jenkins, test this please.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8028/
Test FAILed.

Jenkins, test this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8034/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8035/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8036/
Test PASSed.

Thanks for the PR! This solution looks better :+1:

LGTM

And I appreciate all your comments and suggestions!

LGTM, @caadecarvalho thanks for the PR and iterations

I'm the one that must thank you for the knowledge shared!


refactor: Deprecated props are being used in the Storybook Theme/FontAwesomePage.

Closes https://github.com/yamada-ui/yamada-ui/issues/2483
Description

Replaced the deprecated size prop with fontSize in the Storybook FontAwesome page.
Current behavior (updates)

Currently, the FontAwesome component uses the deprecated size prop in the Storybook FontAwesome page.
New behavior

The FontAwesome component now uses the fontSize prop in the Storybook FontAwesome page.
Is this a breaking change (Yes/No):

No
Additional Information
None

Thanks!


add Techno-economic

Thank you @beijingzyl for opening this PR. This seems to be a straight copy from the NAVIGATE template, correct?
Can you please let me know whether you have had any discussions in the subgroup about possible improvements/extensions to the variables? For example, we aim to ensure easy readability of the variables and avoid abbreviations, so renaming "OM Cost" to "Operation and Maintenance Cost" might be worth considering. Also, there is a sub-category "Fixed" in the OM cost variables but there is specification of the "non-fixed" component...

@danielhuppmann Thank you for your feedback! This PR is from the AR6 template. We've made modifications, such as changing "capital cost" to "techno-economic" to better reflect its scope. We appreciate your suggestions on naming conventions and will consider them.
Regarding the "Fixed" in the OM cost variables, it indeed refers to fixed O&M costs. We noted there's no mention of a "non-fixed" counterpart, and it appears not to be a concept in AR6 either.
As for the validating error, it seems to be related to units after reviewing the error message, but I couldn't identify the exact issue. It's possible that the error arises from a mismatch between the expected and provided units, or there might have been incorrect unit conversions.

Thank you, @beijingzyl.
The tests for your PR are currently failing because the yaml file is not in the right format - it should be a list (each item starting with -, not a yaml-dictionary).
A better starting point for your work can be found here, which is already in the right format. Also, please use all-lower-case names for files.
For units, please follow the new convention "USD_2010" instead of "US$2010" so that we can use the iam-units package for automated handling of unit validation and conversion. All other variables in this repo already follow this convention.
About the fixed O&M costs variables: the purpose of developing the common-definitions repository as a community activity is to review which variables make sense or should be revised. We set up a variable naming guidance here and the variables "OM Cost|Fixed|..." use an abbreviation and establish an un-used hierarchy level. Please discuss with the @IAMconsortium/common-definitions-techno-economic group on a better variable structure.

Thank you @beijingzyl and @ouyang363 for implementing part of the requested changes.
However, you did not respond to my comment about improving the variable name for operation-and-maintenance costs:

About the fixed O&M costs variables: the purpose of developing the common-definitions repository as a community activity is to review which variables make sense or should be revised. We set up a variable naming guidance here and the variables "OM Cost|Fixed|..." use an abbreviation and establish an un-used hierarchy level. Please discuss with the @IAMconsortium/common-definitions-techno-economic group on a better variable structure.

See https://github.com/beijingzyl/Techno-economic/pull/1 for a simplification and one specific question related to this PR.
Note that https://github.com/beijingzyl/Techno-economic/pull/1 is directed into the branch for this PR, so you first have to discuss and merge that other PR, then continue this work.

Closing in favor of #201


python312Packages.gpy: 1.13.1 -> 1.13.2

Description of changes

Version bump to 1.13.2
Disabled one test that fails on Darwin x86_64 due to a rounding error
Removed broken flag on Darwin

Re-do of #340866 due to a merging mistake (my bad)

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

 May I ask for your review on this copy? It should be identical to the final version of that you reviewed in #340866.

FP to keep up with HEAD

@NixOS/darwin-maintainers May I get a merge?

Result of nixpkgs-review pr 341238 run on aarch64-darwin 1

4 packages built:

python311Packages.gpy
python311Packages.gpy.dist
python312Packages.gpy
python312Packages.gpy.dist


Sync user on frontend with user on smart FAQ

Acceptance criteria

When a user logs in on the frontend, he/she is also logged in on Smart FAQ
When a user logs out on the frontend, he/she is also logged out from Smart FAQ

Related to #89 and #46

Closed since we sync via frontend props injected in our React context.


Expose metric for the number of CDN route TLS certs issued by different certificate authorities

What
We've asked our tenants to perform a cf update-service call to migrate their
CDN route services between certificate authorities. By exposing a metric for
the number of CloudFront instances presenting certificates signed by different
authorities, we can track how many tenants have performed the migration.
How to review

Code review

Unless you have an old CDN route service in your dev env, you won't be able to test that it counts >1 certificate authority. The unit tests should test that.
Who can review
Anyone

Was gonna say FDescribe should go but you got it already 🚤


Disable typo-correction by default until we can make it work within acceptable performance bounds

Typo-correction can be so expensive that it can slow down typechecking over 10x.
It can be a significant productivity drain for developing on large projects.
Unfortunately it is best that we disable it until we can dedicate the time to address its performance issues
and we are certain it works within acceptable performance bounds.
rdar://51966070

@swift-ci smoke test

@swift-ci smoke test

@swift-ci smoke test


i cant Spawn the model

Hi I've been having this problem with gazebo simulation and cant get the model to spawn

@SasanMir
I have the exact same issue.  Were you able to determine a solution?

did you guys try cloning repo from here and then building the workspace ? and make sure you have ros setup properly


Allow to rewrite LLM result in an OutputGuardrail

Implements https://github.com/quarkiverse/quarkus-langchain4j/issues/1020
/cc @gsmet @geoand @lordofthejars

I looked at my note as I remembered looking into this in the first implementation. There is a philosophical question that I was not able to crack.
Let's imagine 3 output guardrails: A, B, C.

A pass - all good
B pass but modify the output value
C fails and reprompt

Now the problem is that we are going to reprompt based on a modified value, not the original value. So, the LLM may answer the same, or actually, do not understand the reprompt instruction and start hallucinating.
We could imagine modifying the LLM response in the context to update the value to the modified value, but again, the LLM may see this and can freaks out.
Once possibility is that only the last guardrails can change the value.
Or, we can say that once the value is changed, retry and reprompt are not allowed anymore.

Not allowed or ignored, so no exception is thrown; we just log why they are not executed. What I see here is we can assume that most of time there will be one output guardrails (or you can implement one and put all logic there), so I guess that ignoring might be the best option.

Once possibility is that only the last guardrails can change the value.

I don't like this solution, mostly because I can totally see 2 guardrails changing the result in sequence one after the other (like in the test case that I added).

Or, we can say that once the value is changed, retry and reprompt are not allowed anymore.

That is a better option already. Another possibility is to keep both the original and modified value in the response object and allow a guardrail to inspect both before deciding for a retry or a reprompt, but probably this uselessly overcomplicates things for users.
I would avoid to overthink on this (using more than a guardrails in a row is already an edge case imo) and simply ignore the problem or at most preventing retry/reprompt on a modified value as you suggested.
@cescoffier please let me know which option you prefer.

I totally agree with you @mariofusco just if my vote counts 😆

I may be bossier but I often use chains of guardrails.
But yes, maybe we could just add an option enabling/disabling retry and reprompt after a change of value.
The thing is that it is likely to work with smart LLM and totally break on less smart ones.

But yes, maybe we could just add an option enabling/disabling retry and reprompt after a change of value.

Ok, I will try to implement this.

@cescoffier Done, please give it a second look.

@cescoffier Done, please give it a second look.

First look... first look :-)

I would add a few tests with streamed responses, as, unfortunately, streams require a different approach for output guardrails.

Sure, I will add tests for streamed responses. I guess that in that case rewriting the output is never allowed, correct?

In essence I believe that in general an output guardrail is not compatible with a streamed LLM output and the 2 features should be used in a mutually exclusive way. Can you please clarify your point of view on this?
/cc @geoand

Tools for example work with streamed responses. I was actually surprised to find this, but it does work :)

@cescoffier I'm adding some tests to cover the streamed scenarios, but I'm no longer sure how this should work. The problem is that in this case the output guardrail is invoked for each and every chunk. Now my rewriting implementation changes all of them one after the other, which probably makes the problem even worse, but even without this I don't see which kind of meaningful validation an output guardrail could perform on a single chunk.

No, that's not the case, it depends on the "accumulator" strategy. It can accumulate the full response (which defeat a bit the purpose of streaming), or each token (which makes things very hard to validate), or anything in between (sentence, paragraph, JSON object...).
You can have plenty of validation with the right accumulation strategy. But, yes, the guardrails are called for every accumulated item.

In essence I believe that in general an output guardrail is not compatible with a streamed LLM output and the 2 features should be used in a mutually exclusive way. Can you please clarify your point of view on this?

It is not exclusive. As I wrote, it depends on the accumulation strategy. I am implementing a chatbot that is streamed because otherwise, the experience is pretty bad, and I still check for hallucinations, out of topic content...

It is not exclusive. As I wrote, it depends on the accumulation strategy. I am implementing a chatbot that is streamed because otherwise, the experience is pretty bad, and I still check for hallucinations, out of topic content...

Ok, I see your point. Let me rephrase this and contextualize only to this pull request. For what regards these rewriting output guardrails I don't see how this feature could be usable and useful on a partial response. In other words I don't see a scenario when you may want to rewrite each and every chunk of a streamed response. And yes, this also depends on the "accumulator" strategy, but even here, unless you don't accumulate the whole response (which as you said totally defeats the goal of using a streaming API) I don't think that rewriting different subparts of a response could be of any usefulness.
If you think that my point of view is wrong or limited and still believe that a rewriting guardrail could be useful also on a partial response, then I confirm that everything works as expected, I can add the streamed tests that I just wrote to this pull request and my work is finished.
Conversely, if you agree with me, maybe we should add a mechanism that prevents the response rewriting (throwing an exception?) when using the streamed version.
What do you think?

A good solution could be to use a stream and try to modify the output by throwing an exception to explain the situation. I think it is understandable and also let's not rethink a lot at the end the limitation is only if you use stream and you want to modify the output, in any case it affects other output guards.

I took a few minutes to think about it, and I tend to agree that for streaming modifying the value does not make a lot of sense. It's technically possible (the guard would modify the emitted item and it would be emitted downstream).
We can revisit if there is a use case emerging.

I took a few minutes to think about it, and I tend to agree that for streaming modifying the value does not make a lot of sense. It's technically possible (the guard would modify the emitted item and it would be emitted downstream).
We can revisit if there is a use case emerging.

OK, I will change my pull request to throw an exception in case an output guardrail attempts to rewrite the LLM response while streaming.

I implemented all discussed changes, please @cescoffier review again.

@mariofusco can you rebase?

@cescoffier Done.


Photoshop uhiding hidden layers

 Freshdesk Ticket ID: 346
 Freshdesk Ticket Agent: Milan Kolar
 Freshdesk Ticket Agent Email<EMAIL_ADDRESS> Ticket Priority: Low
 Freshdesk Ticket Description:
hidden layers are being unhidden and show in publish . this seems like a bug

Agent Milan Kolar linked Freshdesk ticket 346 for this issue.

Validated and this really is a problem. When publishing, the final result doesn't respect the hidden/unhidden status of a layer.
YOu can see in the image, that the original FG group has the red layer hidden, but in the loaded published version. the red line is turned on and exported.

Only 692 needs to be merged to solve and close this issue.


iced_lazy and Component trait

This PR introduces a new crate: iced_lazy.
iced_lazy is meant to contain types that are, in one way or another, related to laziness. A container widget is considered lazy when its contents are not strictly computed during an Application::view call. Instead, a lazy widget may choose the compute the contents beforehand, or only when necessary!
Currently, iced_lazy only exposes a new Component trait:
pub trait Component<Message, Renderer> {
    type Event;

    fn update(&mut self, event: Self::Event) -> Option<Message>;

    fn view(&mut self) -> Element<Self::Event, Renderer>;
}

Basically, a Component can be viewed with view, returning widgets that produce some specific Event. A Component can process an Event with update, which may change its internal state and optionally return an application Message.
In other words, a Component can be seen as a sub-application that follows The Elm Architecture, processing internal events and producing messages for the parent application when needed!
The usefulness of this trait becomes apparent when we learn how to use it! The new component::view function has the following signature:
pub fn view<'a, C, Message, Renderer>(
    component: C,
) -> Element<'a, Message, Renderer>
where
    C: Component<Message, Renderer> + 'a,
    Message: 'a,
    Renderer: iced_native::Renderer + 'a,

Any Component implementor can be turned into an Element! This means it is now possible to build custom widgets with its own internal mutable state by leveraging The Elm Architecture. These custom widgets can then be embedded in any iced application without additional wiring.
The new component example uses this new trait to build a NumericInput widget by leveraging composition of the Button and TextInput widgets.

Would a PR that adds compenent equalivents of widgets with state be accepted? Behind a feature gate, probably enabled by default. It would mostly remove the need for manual state management, and would make the examples simpler. What do you think about it?

@yusdacra I'm not sure I follow.
Component does not remove the need for manual state management (i.e. keeping State structs as part of your application state).

@yusdacra No, it doesn't allow that. You'd still need to provide the button::State to build a Button in the first place!
Component is just a way to leverage The Elm Architecture to implement the Widget trait.


[terra-notification-dialog] Added max-width for IE.

Summary
Resolves #621

In Chrome -

In IE -

Screenshots:
IE10

IE11

@pranav300
Lets set max-width to be a fixed 800px (instead of 49%) to match one of our disclosure widths
Which should be an appropriate max-width for the primary type of content included in the notification-dialog. If we find that is too small after hearing feedback, we can increase it to 960px.

+1 UX review - Ready to Merge