Add validation warning when filter is applied to conversion input measure

Resolves SL-2862

Description
Since filtering on a conversion input measure is not fully supported, we will add a warning when this is added to let the user know.

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

Note that this will need a version bump (prod version) so we can release it and get it into core. And then a core PR that bumps to that version.

@courtneyholcomb Are there any other validation tasks? Would it make sense to wait for some of those to be done then we can batch all those up and release it once?

Note that this will need a version bump (prod version) so we can release it and get it into core. And then a core PR that bumps to that version.

@courtneyholcomb Are there any other validation tasks? Would it make sense to wait for some of those to be done then we can batch all those up and release it once?

@WilliamDee
Good call, yeah I think there are! Can you put up a task to make sure we don't forget?


SyntheticTest fails to "pick up" changes to URL argument after initial creation

When I create a Synthetics test say
new dd.SyntheticsTest(
  'test',
  {
    locations: ['aws:eu-central-1', 'aws:eu-west-1'],
    name: 'test',
    request: {
      method: 'GET',
      url: 'https://www.example.com'
    },
    assertions: [
      {
        type: 'statusCode',
        operator: 'is',
        target: 500
      }
    ],
    options: { tickEvery: 60 },
    message: 'test message',
    status: 'live',
    type: 'api',
    tags: ['example']
  },
  {}
)

it creates it no problem.
The issues arises when I change the url to a different one, like https://www.example2.com. The change does not seem to be "picked up".
▶ pulumi up
Previewing update (asdfasdf):
     Type                 Name               Plan
     pulumi:pulumi:Stack  Examples-asdfasdf
Resources:
    2 unchanged
Do you want to perform this update? no
confirmation declined, not proceeding with the update

This was fixed upstream in https://github.com/terraform-providers/terraform-provider-datadog/pull/425


ModalRoute no longer disposes resources until its child widget is unmounted

Description
This PR changes ModalRoute so that when it's popped, it postpones the disposal of resources until the child widget is unmounted after the next frame.
This fixes https://github.com/flutter/flutter/issues/63984. The issue is caused by programmatically popping a route while the back swipe is in progress (fingers held), which leads to the following series of event:

A route is popped and disposed. During the disposal,

Its animation controller is disposed.
A PointerCancelEvent is synthesized for the active pointer.

The disposal of the route should trigger the navigator to rebuild, removing all dependents of the controller, but this does not come until the widget tree is rebuilt in the next frame.
Before the next frame, the cancel event is dispatched.

The drag gesture recognizer (which is not disposed until the next frame) receives the cancel event and starts to dispatch ending callbacks. The callback starts some animation, only to find the controller disposed, triggering assertion error.

This issue indicates the necessity to hold the resources of the route until after the route is popped, whose timing should be controlled by the child widget. This PR achieves this by introducing two methods to Route:

Route.gracefullyDispose(): This method usually calls dispose immediately, but if markHoldingGracefulDisposal has been called with true, then dispose will be postponed until markHoldingGracefulDisposal is called with false.
Route.markHoldingGracefulDisposal(bool value) (protected): Controls the behavior of Route.gracefullyDispose().

The Route.markHoldingGracefulDisposal is then delegated to ModalRoute's widget, which calls it with true when the widget is mounted, and false when unmounted.
Some logic of _HeroFlight is also tweaked to fix a few test breakages. This is caused by a condition which skips Hero's end-flight operations when there are any on-going gestures, introduced by https://github.com/flutter/flutter/pull/58024. This was not an issue because the fromRoute.navigator had been null at that point, passing the condition unintentionally, which is exposed now that the lifecycle of fromRoute is extended. The  _HeroFlight now postpones the operations until the gestures are cleared.
Related Issues

Fixes https://github.com/flutter/flutter/issues/63984

Tests
I added the following tests:

Popping routes during back swipe should not crash

Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Could we solve this problem by changing when the Navigator disposes the Route? I.e. it should only dispose the Route after we rebuild the overlay without the route's overlay entries to give everybody a chance to give up claims to resources in the Route?
When we dispose a widget subtree, we dispose it from the leaves to the root to avoid this problem. It almost sounds as if the Route is the root here and should be disposed last.

@goderbauer This PR is basically doing the thing you propose: mark the route as "need to dispose but probably not yet", assign a callback to the route's root widget to detect its unmount, and dispose the route only when that callback is invoked.
Route is not a widget, nor is it aware it might have a widget (only TransitionRoute and above might contain a widget child), so the navigator has to use a general method that can send in a callback that indicates safe-to-dispose. There might be a better name than gracefullyDispose, but I think we'll end up with more or less the same structure.

Or we can ask the Route to be responsible of marking itself as safe-to-dispose, and make the navigator check each time it rebuilds.

The basic Route class does introduce the overlayEntries, and an OverlayEntry contains a WidgetBuilder. So, in a sense all Routes are widget-aware and my suffer from this problem.
I am wondering whether we could hook this into OverlayEntry. OverlayEntry are turned in _OverlayEntryWidget. We could track those for when they get disposed from the tree with a mechanism similar to what you're adding to the ModalScope in this PR and then dispose the Route they were in. Maybe the navigator can add a "disposalListener" to the OverlayEntry when it adds the OverlayEntry to the Overlay and when it fires the Navigator can dispose the route. That would be generic for all routes.
Routes can have multiple overlay entries, so you probably only want to add the listener to the last one that gets disposed (not shore if that's the first or last overlay entry of a route).
In this patch it's also a little strange that the Route essentially disposes itself.  If we outsource that job to the navigator, we would also avoid this problem.

Closes in favor of https://github.com/flutter/flutter/pull/68202.


how to setup SMTP server for email

I think it's swift message, could you add SMTP settings on config ?

As an SMTP configurator would be welcome, since we often do not open the log files to look for errors.

Thanks, I made the changes to accept common mail settings (host, port, username, password).
I just need to do some testing and then I'll publish a new release.

@smartbackend this is now supported in v2, please have a look at the readme on how to customise your SMTP configuration.


Add a licence

Just a little reminder because I saw you didn't get around to it yet: https://github.com/toshi-search/Toshi/issues/22
😄

Thank you for reminding me! Done


struct_pack not support shared_ptr

I saw the struct_pack library supports many STL containers
but after testing, I regretted that this library does not support the smart point of C++ 11.
like shared_ptr etc.
for example, I have a tree node struct like:
enum class type_e {
root = 0,
users = 1,
projs = 2,
};
struct Node {
type_e type;
std::string name;
std::string  value;
std::list<std::shared_ptr<Node>> children;
};
for now, this library cannot serialize/deserialize the above Node structure.
you can reference another nonintrusive library named alpaca, which supports smart point.

Thank you. It's in my todolist.

But, in this case, the shared_ptr is unnecessary.

If you don't want to shared the nodes, just remove the shared_ptr.
enum class type_e {
root = 0,
users = 1,
projs = 2,
};

struct Node {
type_e type;
std::string name;
std::string value;
std::list<Node> children;
};

Serialize/deserilaize shared_ptr will cost additional price. First we need check if the address is same as previous one to shared the object. Second deserialize shared_ptr may cause memory leak and we need to check it. Anyway I will try to support it later.

thanks for your reply, This library is very cute

shared_ptr可能会导致循环引用问题，这个不是很好解决吧

shared_ptr可能会导致循环引用问题，这个不是很好解决吧

首先在编译期检查类型是否成环。只有类型系统成环才可能出现循环引用。
类型成环的情况下，要么禁止序列化这种类型，要么在反序列化时跑下dfs检测是否成环

shared_ptr可能会导致循环引用问题，这个不是很好解决吧

首先在编译期检查类型是否成环。只有类型系统成环才可能出现循环引用。
类型成环的情况下，要么禁止序列化这种类型，要么在反序列化时跑下dfs检测是否循环引用。
soga


Inbound/Outbound connection rows/counts/ports not being calculated correctly

Seems like maybe, in particular on internet node.
Could be related to recent changes there.

It's also happening on the 'Uncontained' node.

Also that some expected node/port rows are missing.

Also that some expected node/port rows are missing.

Is that the same problem?
FTR, what I am seeing is that my thunderbird connections to gmail:993 are shown in the thunderbird process details panel, but not the "Uncontained" details panel.

My hunch is it is related.

This bug seems to contain three issues:

Uncontained node details panel is missing connections to the internet?
Some other things are missing.
Sometimes the row expansion widget is shown when there is nothing to expand

I can't reproduce (1) or (2) of these issues, and without a report (or at least a screenshot) there is very little else I can do.
I'll open a separate issue for (3)

Filed #1240 for (3).
@paulbellamy / @rade do you have a repro / more details for (1) or (2)?

report

connections from my thunderbird to internet:993:

uncontained shows no connections to internet:993:


Adding Preloader in website

Is your feature request related to a problem? Please describe.
I can add a preloader in website please assign this issue to me under gssoc
Describe the solution you'd like.
Adding a preloader to website
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

assigning to you @dhairyagothi, you can start working on it.


Final cleanup of detected types.

@mkustermann @kevmoo: Please make sure this was run on prod before merging this. Closes #348.

Running it now...


Tile 6221 on 20241004 abnormal number of non-TGT on Petal 0

Abnormal number of non-zero redshifts from non-TGT on Petal 0.
Tile QA-ed as "unsure".

I think it s just because the tile is on the edge of the ls-dr9 footprint:

so there are no science targets there, fiberassign fills the fibers with skies:
https://data.desi.lbl.gov/desi/target/fiberassign/tiles/trunk/006/fiberassign-006221.png

This one got marked good, closing.


Implement pipelined pessimistic lock to reduce latency

Feature Request
Is your feature request related to a problem? Please describe:

In the pessimistic transaction, we acquire locks for each DML. It's a heavy operation since every lock is a k-v pair in TiKV which has to wait for raft replication. And we can't execute the next query until previous DML's locks are written to TiKV successfully. It brings much delay.

Describe the feature you'd like:

We can avoid the delay if TiKV responds to TiDB early:

The risk is if fails to write to raftstore, the pessimistic transaction will fail to commit. Even though it seldom fails, we need to increase the success rate.

@HunDunDM


[pfring]Add new port.

Only support UNIX.
Related: #7894.

/azp run

This build failure is a bug with copy source files, fixed in #8540.

/azp run

@vicroms ready to merge now.

/azp run


HRT time doesn't set the interrupt priority, will cause low priority interrupt response??

@file drv_hrt.c
static void
hrt_tim_init(void)
{
	/* claim our interrupt vector */
	irq_attach(HRT_TIMER_VECTOR, hrt_tim_isr);

	/* clock/power on our timer */
	modifyreg32(HRT_TIMER_POWER_REG, 0, HRT_TIMER_POWER_BIT);

	/* disable and configure the timer */
	rCR1 = 0;
	rCR2 = 0;
	rSMCR = 0;
	rDIER = DIER_HRT | DIER_PPM;
	rCCER = 0;		/* unlock CCMR* registers */
	rCCMR1 = CCMR1_PPM;
	rCCMR2 = CCMR2_PPM;
	rCCER = CCER_PPM;
	rDCR = 0;

	/* configure the timer to free-run at 1MHz */
	rPSC = (HRT_TIMER_CLOCK / 1000000) - 1;	/* this really only works for whole-MHz clocks */

	/* run the full span of the counter */
	rARR = 0xffff;

	/* set an initial capture a little ways off */
	rCCR_HRT = 1000;

	/* generate an update event; reloads the counter, all registers */
	rEGR = GTIM_EGR_UG;

	/* enable the timer */
	rCR1 = GTIM_CR1_CEN;

	/* enable interrupts */
	up_enable_irq(HRT_TIMER_VECTOR);
}

HRT time doesn't set the interrupt priority, will cause low priority interrupt response??
thank you !!!

@davids5 please comment if we should keep this for 1.7

Not critical for this release.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)

For the record: Having a priority above normal could cause nesting. Nuttx does not support Nested interrupts, in fact enabling them will cause hard to debug hard faults. The common ISR is not reentrant. Tasks invoked off of the HRT ISR need to allow context switches. So the use of Nuttx's HIGH PRIORITY interrupts is not an options either.


Error: spawn prisma-client-py ENOENT}

I've been using Prisma in node.js & I'm loving it.
Right now I have a Fastapi backend that I want to use Prisma with, yet I'm facing this issue whenever I run "Prisma db push" :
`prisma db push
Environment variables loaded from .env
Prisma schema loaded from schema.prisma
Datasource "db": PostgreSQL database "postgres", schema "public" at "HIDDEN.pooler.supabase.com"
The database is already in sync with the Prisma schema.
Running generate... (Use --skip-generate to skip the generators)
Error: spawn prisma-client-py ENOENT}`
Prisma version: `
prisma                  : 5.13.0
@prisma/client          : 5.13.0
Computed binaryTarget   : windows
Operating System        : win32
Architecture            : x64
Node.js                 : v20.12.0
Query Engine (Node-API) : libquery-engine b9a39a7ee606c28e3455d0fd60e78c3ba82b1a2b (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli b9a39a7ee606c28e3455d0fd60e78c3ba82b1a2b (at<EMAIL_ADDRESS>Schema Wasm             : @prisma/prisma-schema-wasm 5.13.0-23.b9a39a7ee606c28e3455d0fd60e78c3ba82b1a2b
Default Engines Hash    : HIDDEN
Studio                  : 0.500.0`
Schema.prisma:
`generator client {
provider             = "prisma-client-py"
}
datasource db {
provider = "postgresql"
url      = env("DATABASE_URL")
}
model User {
id String @id @unique
name String?
email String @unique
profileImage String?
ntfyChannel String
stripeCustomerId String? @unique`
My system:
Windows 11 64 bit Python 3.12.2

change --> provider = "prisma-client-py" to provider = "prisma-client-js"

change --> provider = "prisma-client-py" to provider = "prisma-client-js"

I did that and it installed js packages but still am getting this error    raise RuntimeError( RuntimeError: The Client hasn't been generated yet, you must runprisma generate` before you can use the client.
See https://prisma-client-py.readthedocs.io/en/stable/reference/troubleshooting/#client-has-not-been-generated-yet
`

same error
>>> prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Error: spawn prisma-client-py ENOENT


Send Image Messages (iOS Swift) fails

I followed Firebase iOS Codelab Swift - Step 8
https://codelabs.developers.google.com/codelabs/firebase-ios-swift/#8
I was using xcode 8.2. While testing sending image messages on simulator, I clicked the "add a photo" icon, and selected an image. Instead of uploading that image, I got the following error message:
[Generic] Creating an image format with an unknown type is an error
Error uploading: An unknown error occurred, please check the server response.

I believe I addressed this earlier. Can you check it again?

I have the same issue. Is it an issue with Firebase or one with the code in X code?

FYI this is still a problem

Yes, experiencing this as well when I go through the same tutorial.

I am also going through the Swift tutorial right now. I ran into the same issue and wanted to understand more about this problem.
As I was adding some debugging statements to determine what was happening, the callback on sendMessage completed, and it worked! It took a long time, though. I timed it: took me thirty seconds. Seems related to Internet connection speeds and sample image sizes.

I still do get the log message, but it seems to be an innocuous log message, which seems to indicate that it did fail, BTW. That caught me as well.

@iulukaya I checked it again today. But, it still shows the generic message I have written above.
[Generic] Creating an image format with an unknown type is an error
But, I do not see this message-
Error uploading: An unknown error occurred, please check the server response.
So, I thought it uploaded image; and when I checked the storage item in my project in Firebase console, it shows that the file is uploaded to the bucket.
In the simulator, I also see a new message for the uploaded image,
sent by: Optional("my-username")

If the issue still exist please report at https://github.com/firebase/friendlychat-ios/issues


Build failed when App Engine APIs are not enabled

The following error happens running integration tests when App Engine APIs aren't enabled. The fix is to browse to Cloud Console and enable App Engine API. It does not happen for projects that already enabled or have App Engine applications. The biggest problem is the error isn't obvious and took my team 3 days to figure out.
Error:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

I am having a similar issue. The service account JSON path is correct on my machine and a NodeJS script using the same service account JSON can send messages. The Java code cannot properly connect to it and make a subscription. I have double checked the IAM permissions for the SA and the topic permissions for the topic look correct.
Any advice?

My issue was related to https://issues.apache.org/jira/browse/BEAM-7851.


Does someone know how to output it without a hash?

it outputs them like this :
dist/assets/test-oBK5LLTu.woff2

That is due to the guid() called here: https://github.com/atlowChemi/vite-svg-2-webfont/blob/b14d485ae33afb051620034699119de27b94c67e/src/index.ts#L104
Why do you need to remove the hash? what is the use case?

@atlowChemi for example, I would want to add <link rel="preload" for my font. And I cannot do that unless I know the path in advance. Also I would really like an option to inline font assets as base64 (that would totally solve the preload issue for me).

@Azarattum thank you for your contribution! 🙂
@yustinTR Does the change added @Azarattum work for your needs?
Still not clear to me what the issue is 🙂

I'll be closing this as some time has passed, feel free to re-open if needed 🙂


Faulty regular expression in middleware causes valid URLs to not work

Description
The default regular expression that is used by the matcher is faulty. After a solid 3 hours of debugging I finally found the culprit and it was this library.
Strange nobody has encountered this before but I suggest changing the regexp you provide in the docs.
Mandatory reproduction URL (CodeSandbox or GitHub repository)
https://codesandbox.io/p/sandbox/next-intl-bug-template-app-forked-yv52yj?file=%2Fsrc%2Fapp%2F[locale]%2Flayout.tsx%3A5%2C30
Reproduction description
Steps to reproduce:

Open reproduction
Click on the broken link in the "nav menu"
Voila it's broken now :)

Expected behaviour
URLs that end with a period should work as they're valid URLS and need no encoding. If you want to see if the end of the pathname is a file (i.e. favicon.ico) do not use a wildcard match after the period. (.*)

Thank you so much for sharing your finding! May I ask which regex you ended up with?
It doesn't seem so trivial to me. In your example the middleware doesn't match the URL because it has two dots, e.g. /something/Mars%20B. would work as far as I can tell. The .V. part is incorrectly matched as a file extension.
I started work on a PR here: https://github.com/amannn/next-intl/pull/505
In case you have some input, that would be great!

I haven't found out a proper regexp but the one provided in the docs will always fail if you have a period anywhere in the URL you can validate that in the codesandbox
https://yv52yj-3000.csb.app/something/Mars BV.   [FAIL]
https://yv52yj-3000.csb.app/something/Mars B.V.  [FAIL]
https://yv52yj-3000.csb.app/something/Mars B.V   [FAIL]
https://yv52yj-3000.csb.app/something/Mars BV    [PASS]


core/trie has not impl for no_std

I run following cmd to build core/trie
cargo +nightly build --no-default-features

warning: unused import: `core as std`
   --> core/primitives/src/sr25519.rs:133:5
    |
133 | use core as std;
    |     ^^^^^^^^^^^
    |
    = note: `#[warn(unused_imports)]` on by default

   Compiling substrate-trie v2.0.0 (/mnt/d/code/my-github/substrate/core/trie)
error[E0277]: the trait bound `error::Error: std::error::Error` is not satisfied
  --> core/trie/src/node_codec.rs:43:17
   |
43 | impl<H: Hasher> NodeCodecT<H> for NodeCodec<H> {
   |                 ^^^^^^^^^^^^^ the trait `std::error::Error` is not implemented for `error::Error`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
error: could not compile `substrate-trie`.
warning: build failed, waiting for other jobs to finish...
error: build failed

I find that core/trie has not impl for no_std.
See
https://github.com/paritytech/substrate/blob/master/core/trie/src/error.rs#L11
The trie-db has not reexport the no_std Error.
And I open a PR to fix it.
https://github.com/paritytech/trie/pull/31

BTW, I fix all of them in my local. But there's still many errors when built in --no-default-features for core/trie.

We have tests that build substrate-trie for wasm in test-runtime.
We use substrate-trie in Cumulus in wasm.

So, I don't understand your problems.

It looks like trie crate imports std somewhere, then Error get cast to std error.
I would expect following code from 'trie' crate to be enough:
#[cfg(not(feature = "std"))]
impl<T> Error for T {}

It looks like trie crate imports std somewhere, then Error get cast to std error.
I would expect following code from 'trie' crate to be enough:
#[cfg(not(feature = "std"))]
impl<T> Error for T {}

The problem is the imports of trie-bench etc, they import trie-db without disabling the std feature. Cargo merges all features of dev-dependencies and dependencies and then we compile trie-db with std enabled, while substrate-trie is compiled without std.

Strangely!
Why it report std::error::Error, when I build it in no_std?
So I build it again, and get a different error.
$ cargo +nightly build --no-default-features
   Compiling substrate-trie v2.0.0 (/mnt/d/code/my-github/substrate/core/trie)
error[E0405]: cannot find trait `StdError` in this scope
  --> core/trie/src/error.rs:41:9
   |
41 | impl<T> StdError for T {}
   |         ^^^^^^^^ not found in this scope

error: aborting due to previous error

For more information about this error, try `rustc --explain E0405`.
error: could not compile `substrate-trie`.

To learn more, run the command again with --verbose.

Did you read my last comment? That explains it.

Well, I try to understand it.

The client relies heavily on it. Can easy to build some other client functions if it can built in no_std.


L&S - Pathing for mobs

@synopia is already working on a pathing module. Hoping to make that part of round one when we have creatures to move around :-)

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/486167-l-s-pathing-for-mobs?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github).

Moved to https://github.com/Terasology/LightAndShadow/issues/40.


[incubator/etcd] Prevent removal of data from INITIAL_CLUSTER_SIZE pods

What this PR does / why we need it:
Fixes an issue where by etcd pods will fail to come up after being deleted or the node they're attached to is drained. This is due to data being deleted during the preStop phase of the pod lifecycle and deletion should only occur on etcd nodes outside of the inital set created by helm.
Which issue this PR fixes
Fixes #6064
Special notes for your reviewer:
Also had to modify the way the SET_ID variable was set, in other projects such as [incubator/patroni] this caused issues as the hostname was more than 5 characters.

/assign @lachie83

/ok-to-test

/lgtm


Implement std::fmt::Display instead of ToString

A number of structs implement ToString. According to the rust docs, they should have std::fmt::Display implemented  instead.
https://doc.rust-lang.org/std/string/trait.ToString.html
As such, ToString shouldn't be implemented directly: Display should be implemented instead, and you get the ToString implementation for free.
Task:
Replace implementations of ToString with std::fmt::Display.

OP said that he is making a PR for this, and asked to claim the issue.


fixed #33 Change fuc name to camel case format.

Signed-off-by: Bo-Yi Wu<EMAIL_ADDRESS>

Coverage remained the same at 100.0% when pulling 43464d7c2d704d415cdc77c2d4a910c4cb4959ce on patch-2 into 1227320a90d59af6ae58eb7c6a4e1b15775311c1 on master.


cannot fix redis password

Hello
I would like to fix the redis auth password and manage it in credhub
Unfortunately even if i set it in my deployment by adding the following opsfile
- type: replace
  path: /properties/redis/security?/require_pass
  value: ((redis_password))

- type: replace
  path: /variables?/name=redis_password?
  value:
    name: redis_password
    type: password

the provided password is well filled in /var/vcap/jobs/dedicated-node/config/redis.conf
...
# Warning: since Redis is pretty fast an outside user can try up to
# 150k passwords per second against a good box. This means that you should
# use a very strong password otherwise it will be very easy to break.
#

requirepass 1OujjY5MctbW9OZkfuT61rawh9Icxg

but it is overwritten with an uuid in /var/vcap/store/redis/redis.conf, which is the configuration file used by redis instance
aof-rewrite-incremental-fsync yes
requirepass b3c18089-ca3e-4c60-8f87-c42f27627253

Is there anything I missed ?

Closing as this is not something we intend to look at, however we would happily accept a PR that addressed this.


TypeError: Cannot read property 'name' of undefined

I know this situation has been discussed, but still I'm getting the following error when trying to add my first host in AWS:
TypeError: Cannot read property 'name' of undefined
The rancher container is running on an AWS. I've validated my access and secret keys are good. From the Chrome debug tool, I'm seeing the following information:
Request URL:http://myrancher.com:8080/v2-beta/proxy/ec2.us-east-1.amazonaws.com/
Request Method:POST
Status Code:400 Bad Request
Remote Address:<IP_ADDRESS>:8080
Referrer Policy:no-referrer-when-downgrade
Looking at the v2-beta API in rancher, "proxy" is not a valid path, so maybe that's related.
Rancher versions:
Component | Version
Rancher | v1.6.9
Cattle | v0.183.21
User Interface | v1.6.23
Rancher CLI | v0.6.4
Rancher Compose | v0.12.5
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Docker version: (docker version,docker info preferred)
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 1
Server Version: 17.03.2-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.38-16.35.amzn1.x86_64
Operating System: Amazon Linux AMI 2017.03
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955 GiB
Name: ip-10-11-0-30
ID: NE7Y:GOXT:QKO2:XEBN:FRVA:SNXB:YU5P:T2HY:ZGVH:VHZE:HSNI:PROD
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
cat /etc/os-release
NAME="Amazon Linux AMI"
VERSION="2017.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2017.03"
PRETTY_NAME="Amazon Linux AMI 2017.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2017.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"
uname -r
4.9.38-16.35.amzn1.x86_64
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Add the first host
Results:
TypeError: Cannot read property 'name' of undefined

/proxy/{whitelisted hostname} is part of the API but not in the documentation because there's no reason for users to use it directly.  The UI uses the AWS JS client to talk to their API and do things like list your VPCs.  Requests from a page on one domain (your-rancher.com) to another (ec2.*..amazonaws.com) are not generally directly allowed, so the server container proxies the request from browser <-> rancher/server -> provider API.
You need:

Valid api keys
That are usable from the server container's IP
And have permission to perform basic EC2 operations (DescribeVPCs is the first one)
And an accurate clock on the computer running the browser (AWS auth uses time-based signatures).

Open up the network tab of the browser developer tools and grab the complete request and response headers & body.  x-out the content of authorization headers.

Thanks Vincent. I think it was a role problem on my instance.  I'm past this block and on to the next:
"transitioningMessage": "Error setting machine configuration from flags provided: RequestError: send request failed"
I'll look around the forum...


Add a navigation to section/pages in the nested view of the management

Rationale / Begründung
Adding a navigation to section/pages in the nested view of the management would improve the catalog editing, and should not be to hard to implement. A click would scroll the element in to the view.
Affected
Managers, Admins

we could make a start with this issue with our new colleague from the ULB


[FEATURE] Fubuki Desktop Mascot

Delfes from the Shirakami Land server has developed a fun little Fubuki mascot that occupies the Windows desktop and mess with application windows, if permission is granted. The program powering the mascot, Shimeji-ee, is open-source and can be redistributed as long as the proper disclaimers are provided with the download.
It would be a good idea to develop a new page to host this community app, with summary, installation instructions, and to make the file for download. Mainly these sections:

What is the Fubuki Desktop Mascot
Demonstration using GIFs
Download link with licensing and disclaimers
Installation Instructions

The download can be through a direct request to S3 or Azure storage, a Github repo, or any file sharing service. For future planning, if we are to host more files I think it would be beneficial to have a standalone cloud storage backend. The bandwidth cost will be manageable either way.
Source post: https://discord.com/channels/726410071650861146/762674363118911519/855498799437578260

Thanks Kanna!
I'd like to suggest to split the content sections like the following:

What is the Fubuki Desktop Mascot
Demonstration using GIFs
Download links
Installation Instructions
Licensing, disclaimers, and terms

The files should be able to be hosted directly in this repo, will confirm


fix: use not equals for iam role check

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

LGTM.


Add examples of init scripts for popular init systems

sysvinit
upstart
systemd

I added an upstart script and ubuntu installation isntructions because that's what I know. If anyone prefers other distros/init systems, I'm very interested in contributions!


(WIP) Opportunity.all Sorting

This is for #22.
Let me know what else is need, especially regarding tests, I don’t have much experience writing them. :)

This is great @dberget, we definitely should write some tests.  To start we'll need to be looking at the opportunities_test.exs.
The simplest test we could do would be inserting 2-3 opportunities and sorting them by their title or difficulty.  @dberget I'd be happy to write some psuedo code for you on here or we can chat via Slack and I can give you some pointers.  What works best for you?

Sounds good to me, i'll give it a try first and then we can go from there.

Hey @doomspork - Test has been added and appears to be passing. Should I add a test to cover difficulty or any other fields? Thanks for the guidance!

@dberget we're going to need to rebase your branch and update the target to be master after #25 is merged in with it's changes.
I will happily walk you through the process 👍

I'm sure what's happening here TravisCI seems to be stuck.  I'm going to merge 👍


Resulting State of Oureng?

Resulting State of Oureng? created by<EMAIL_ADDRESS>on 2017-10-19 10:46:24

<EMAIL_ADDRESS>replied, I haven't seen much activity lately on this thread, so I hope folks are still up for a question.Â  I'm wondering if there is a v.r.s. (verb, resulting state) for the transitive verb (v.t.) oureng.Â  To review, a v.r.s. is the completed action for a v.t.Â  So, for example, "A John a mengat a ngikel" -> "a ngikel a chelat" [John is smoking the fish -> the fish is smoked].Â  v.t. -> v.r.s.Â  Is there something similar for oureng?Â  "A John a oureng a ngikel" -> "A ngikel a deloureng"???? [John hoped for a fish -> the fish was desired ???]Â  Â How about "a John a oureng a redil" -> "a redil a deloureng" [the girl is desired].Â  That makes a little more sense.Â  But is this a word and did I construct it properly?

<EMAIL_ADDRESS>replied, oureng,- desire,lust, crave,
ourureng- desiring, craving, lusting
ulureng-desired, wished for

<EMAIL_ADDRESS>replied, I have never heard of such form either. Maybe only actual action verbs have
v.r.s. such as chomart, melengoes, mengelebed, used in your examples.
Oureng is more of a feeling, or expression of a feeling. The "rengiil" is a
curious idea. But when I think about it, I am more inclined to think  it
means to be pleased, like to please the "heart" or the "reng".
J

<EMAIL_ADDRESS>replied, it can't be v.r.s., because DELOURENG had unexplainable D, which is absent in OURENG. I guess it's a contraction of 'dil el oureng', my beloved woman or something like that.Jim, can you give us the text you met that word in?

<EMAIL_ADDRESS>replied, That was 2 years ago, so I don't remember the context in which I asked the question.Â  I don't think I had an actual text, just wondering how you would say it.

<EMAIL_ADDRESS>replied, I have never seen any v.r.s. of verbs with OU-. I think this is a lack of paradigm. If I would have to say something you wrote about, I would say it like:' a ngikel a loureng er ngii a John ' the fish John would like.' a ngikel a kuureng er ngii ' the fish I would like.' a ngikel a moureng er ngii ' the fish you would like, etc.UPD. we have some examples like OUTEKANGEL - ULTEKANGEL but it's very rare and irregular for Palauan grammar.

<EMAIL_ADDRESS>replied, Oh I remember this from a while ago. But no, there's no v.r.s for "oureng."
As I think of it, maybe only Palauan verbs that have actual physical action
have v.r.s. such as those used in John's examples in the original thread:
chellebed, selengoes, cheat.

Jim, looks like the word you are asking about does not exist. I'm closing this thread. Please re-open if you want to keep trying.


Add 'person' to cli-bot

Modify https://github.com/serpro69/kotlin-faker/blob/master/cli-bot/src/main/kotlin/io/github/serpro69/kfaker/app/cli/Introspector.kt to include Person provider:
    val providers: Sequence<KProperty<*>> = faker::class.declaredMemberProperties.asSequence().filter {
        it.visibility == KVisibility.PUBLIC
            && (it.returnType.isSubtypeOf(FakeDataProvider::class.starProjectedType)
                || it.returnType.isSubtypeOf(Person::class.starProjectedType))
    }

And add the necessary stuff to https://github.com/serpro69/kotlin-faker/blob/master/cli-bot/src/main/resources/META-INF/native-image/io.github.serpro69/cli-bot/reflect-config.json
https://github.com/serpro69/kotlin-faker/blob/master/cli-bot/src/test/kotlin/io/github/serpro69/kfaker/app/cli/IntrospectorTest.kt will also need to be fixed
Relates to #86

Hi @serpro69!
It's been a long time since this issue was opened. Is it still viable to work on it?

Hi @iagosaito :wave: ,
Heh, I completely forgot about this one. Thanks for the reminder :)
Yes, this hasn't been implemented yet. Please feel free to pick it up if you'd like to :+1:


Refactor repo to make nifipy a proper Python package

It's a python package that can be installed via pip.


[2.9] aks node pools - allow 0 count when autoscaling is enabled

Fixes https://github.com/rancher/dashboard/issues/11848
Backport of https://github.com/rancher/dashboard/pull/11855 minus some vue3 v-model syntax.

@mantis-toboggan-md seems some unit tests are failing

Thanks @momesgin  - looking now

@mantis-toboggan-md can you add a milestone?


Use REST resource mapper

Why
This is an attempt to add support for custom resources.
Related issues:

https://github.com/grafana/xk6-kubernetes/issues/69
https://github.com/grafana/cloud-apps-platform/issues/44
https://github.com/grafana/grafana-multitenancy-team/issues/8

What

[x] replace static list of resources with DeferredDiscoveryRESTMapper
[x] update tests

Hi @toddtreece Thanks for the PR. The changes look good to me.

Awesome @toddtreece ! I'm just taking a look at it now.

I was able to install a CRD (K6 type from k6-operator) and perform CRUD operations successfully as well.
yay!

Sorry that we have a ton of cruft in the examples directory...many can be ignored as we will be replacing most of them;
@javaducky maybe it is time to address this issue. Once we have a clear list of examples we want to maintain,  I have some ideas of how to use them to implement #48 based on what I have been doing in xk6-disruptor.

@toddtreece I renamed the PR because the title was misleading. Even when the motivation of the PR is to support CRDs the scope is basically introduce the REST mapper. If the scope were to introduce support for CRDs then we should had to add examples and tests for that, what we haven't done in this PR.


proposal: bytes, strings: add Truncate

I find myself implementing this function pretty often and I thought it would be decent addition to the standard library.
// Truncate returns the first n runes of s.
func Truncate(s string, n int) string {
	if len(s) <= n {
		return s
	}
	for i := range s {
		if n == 0 {
			return s[:i]
		}
		n--
	}
	return s
}

That is a valid criticism, I'm mainly using it for ASCII text.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

If you're trying to limit columns of output to display to a user, you probably need to take into account character widths and also truncate to a grapheme cluster boundary, not just a rune boundary.

FWIW when I want this functionality, it's usually because I want to limit the overall size in memory of something without producing malformed UTF-8. It's true that I might produce a malformed grapheme cluster, but I'd still submit that it's better to do that than splitting at an arbitrary byte.
I'm not even sure that it's possible to split on grapheme clusters without going outside the standard library
I have a strong recollection of having this discussion before, but I can't for the life of me find the discussion (ISTR that @rsc was involved).

@rogpeppe I believe you're thinking about the discussion here https://github.com/golang/go/issues/53120

Similar to the discussion in #53120, this API seems to promise something but really doesn't promise much of anything. It is easy enough to write in a third-party library. It doesn't seem like we should have it here.

Based on the discussion above, this proposal seems like a likely decline.
— rsc for the proposal review group

No change in consensus, so declined.
— rsc for the proposal review group


[fontconfig] Take gperf from vcpkg tool if possible

Take gperf from vcpkg tool if possible
Fixes #24518

@BillyONeal What do you think?

@BillyONeal @ras0219-msft Any news from team discussion?

I've fixed gperf to install the executable into a subdirectory of tools -- could you please pull my changes into this branch?
git fetch https://github.com/ras0219-msft/vcpkg dev/roschuma/pr24677
git merge FETCH_HEAD

I've fixed gperf to install the executable into a subdirectory of tools -- could you please pull my changes into this branch?
git fetch https://github.com/ras0219-msft/vcpkg dev/roschuma/pr24677
git merge FETCH_HEAD

@ras0219-msft done.

@ras0219-msft I think ci is break because of your fix.

@dg0yt @JackBoosY @ras0219-msft
Can you help me fix kf5codecs?
Installing 44/44 kf5codecs:x64-linux...
Building kf5codecs[core]:x64-linux...
-- Downloading https://github.com/KDE/kcodecs/archive/v5.89.0.tar.gz -> KDE-kcodecs-v5.89.0.tar.gz...
-- Extracting source /home/ubuntu/vcpkg/downloads/KDE-kcodecs-v5.89.0.tar.gz
-- Using source at /home/ubuntu/vcpkg/buildtrees/kf5codecs/src/v5.89.0-a370638e5e.clean
-- Configuring x64-linux-rel
-- Building x64-linux-rel
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:158 (message):
    Command failed: /snap/cmake/1088/bin/cmake --build . --config Release --target install -- -v -j2
    Working Directory: /home/ubuntu/vcpkg/buildtrees/kf5codecs/x64-linux-rel
    See logs for more information:
      /home/ubuntu/vcpkg/buildtrees/kf5codecs/install-x64-linux-rel-out.log

Call Stack (most recent call first):
  installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_build.cmake:112 (vcpkg_execute_build_process)
  installed/x64-linux/share/vcpkg-cmake/vcpkg_cmake_install.cmake:41 (vcpkg_cmake_build)
  ports/kf5codecs/portfile.cmake:19 (vcpkg_cmake_install)
  scripts/ports.cmake:146 (include)

error:
/bin/sh: 1: /home/ubuntu/vcpkg/installed/x64-linux/tools/gperf: Permission denied
install-x64-linux-rel-out.log

@BillyONeal @ras0219-msft @JackBoosY
Ready for review.

@ras0219-msft Ready for review.


resouce cannot be released

redis.clients.jedis.exceptions.JedisExhaustedPoolException: Could not get a resource since the pool is exhausted

Concurrent execution，sometimes resources cannot be returned properly here.
version:2.10.0

@auyang-0626 Maybe you need to upgrade jedis version, because it's been fixed，refer：this.


Pull React transform docs from babel/babel [WIP]

Companion to https://github.com/babel/babel/pull/4903
Couple notes:

The strip_html call when parsing a README is problematic for examples/code blocks that actually contain html 😜  For local, I replaced it with | replace: "<br />", "" but didn't do extensive testing.

The current strategy of stripping the first four lines means I made some errors when updating the package READMEs: we need to make ensure they're one line. Before I push up a PR to fix, do we want to re-evaluate at all?

Will be pushing a PR to fix -self and -source needing new lines for Out:

/cc: @xtuc @hzoo

Yes, sorry my bad. I'll look at strip_html.

I left a comment in babel/babel#4903.
Could you add the description of the package in the header ?

@xtuc yep, will send a PR to fix them up

@xtuc
Pushed PR on babel/babel to fix up descriptions + issues: https://github.com/babel/babel/pull/4917
Tested https://github.com/babel/babel.github.io/pull/1015 and found one issue with the "Out" block inside transform-jsx-source:

Compare with:

I guess we just have to update this?

Rebased, need to spend a little more time finding a cleaner solution for the previous comment. It looks like Jekyll doesn't like the double braces =/

looks like it was doing  {% raw %} before

Yeah, trying to find a non brittle way of injecting it when we parse the package's README. I'm assuming we don't want {% raw %}...{% endraw %} to show up in the README?

We can't because READMEs are also visible on npmjs and Github.

@xtuc yep, I had the same concern.
I haven't been able to come up with a reliable/non brittle way to deal with the double quotes (GH Pages seems limiting here).
Any ideas? Or maybe we just do a quick/unsightly fix and just separate the double quotes and move on for now?
<sometag __source={
  { fileName: 'this/file.js', lineNumber: 10 }
} />

// or

<sometag __source={ { fileName: 'this/file.js', lineNumber: 10 } } />

If putting a space in between fixes it we could do that

Yep:

Will push a fix and then this will be 👍


Error importing Bert from transformers

The following code that would be used to fine tune the Google Bert model gives an error:
from transformers import DistilBertTokenizer, DistilBertForSequenceClassification
cannot import name 'COMMON_SAFE_ASCII_CHARACTERS' from 'charset_normalizer.constant

This is caused by a transformer dependency chardet not being installed. Also, the version of transformers is old 2.x instead of 4.x. Likely, another dependency of nnunet is causing the version to be reduced. Time to split off the nlp environment from nnunet!
Additionally, going to switch to yml files to control dependencies as I do not need to maintain compatibility with requirements.txt files and procedurally generate the ymls unlike in previous projects.

Dependency issues resolved. Shared dependencies (like huge Pytorch) are now installed via a requirements.txt to the base environment. Separate conda envs are created with yml files. If those cannot install some of the dependencies, the run_setup_all.py script will fallback to pip.


New version: PostgreSQL.PostgreSQL.16 version 16.4-1

Created by 🥟 Dumplings in workflow run #7189.

Log
Updated: 16.3-2 → 16.4-1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -2145844845
2024-08-08 06:31:34.765 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000
2024-08-08 06:31:34.805 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FF8BA29A465: (caller: 00007FF8BA29AD01) Exception(1) tid(1210) 80190193 Forbidden (403).
2024-08-08 06:31:35.230 [CORE] Download request failed. Returned status: 403
2024-08-08 06:31:35.230 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!00007FF8BA2943D6: (caller: 00007FF8BA295C49) Exception(2) tid(1210) 80190193 Forbidden (403).
2024-08-08 06:31:35.284 [CLI ] Failed to download, waiting a bit and retry. Url: https://get.enterprisedb.com/postgresql/postgresql-16.4-1-windows-x64.exe
2024-08-08 06:31:35.916 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000
2024-08-08 06:31:35.916 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FF8BA29A465: (caller: 00007FF8BA29AD01) Exception(3) tid(1210) 80190193 Forbidden (403).
2024-08-08 06:31:36.002 [CORE] Download request failed. Returned status: 403
2024-08-08 06:31:36.002 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!00007FF8BA2943D6: (caller: 00007FF8BA295C49) Exception(4) tid(1210) 80190193 Forbidden (403).

Automated error analysis suggests -2145844845 may mean Forbidden (403).
Automated error analysis suggests 80190193 may mean Forbidden (403)
(Automated response - build 887.)


Flaky agent spec: Kontena::Workers::EventWorker#start starts processing events

  1) Kontena::Workers::EventWorker#start starts processing events

     Failure/Error: expect(subject.wrapped_object).to receive(:stream_events)

       (#<Kontena::Workers::EventWorker:0x000000022220e8>).stream_events(any args)

           expected: 1 time with any arguments

           received: 0 times with any arguments

     # ./spec/lib/kontena/workers/event_worker_spec.rb:38:in `block (3 levels) in <top (required)>'

Also related
  1) Kontena::Workers::EventWorker#start streams and processes events

     Failure/Error: expect(rpc_client).to receive(:request).exactly(times).times

       (InstanceDouble(Kontena::RpcClient) (anonymous)).request(*(any args))

           expected: 100 times with any arguments

           received: 98 times with any arguments

     # ./spec/lib/kontena/workers/event_worker_spec.rb:41:in `block (3 levels) in <top (required)>'

     # ./spec/spec_helper.rb:86:in `block (3 levels) in <top (required)>'

     # ./spec/spec_helper.rb:85:in `block (2 levels) in <top (required)>'


'Time' has no attribute 'clock'

I've come across a bug when trying to replicate the starting harvester.py example you give in the readme in python 3.8.
On line 4 while importing Harvester python trows up an error that on line 35 of vispy\util\ptime.py module 'time' has no attribute 'clock'.
I believe this an error caused by the the depreciation of time.clock() in python 3.8 as the vispy version used is quite a bit behind.

upgrade your sqlalchemy
pip install sqlalchemy --upgrade

this did not solve the issue for me, it worked after upgrading everything in pip, altough my dependency resolver is not happy with pyqt 5.16, harvesters gui starts now

open the .venv_harvester_gui\Lib\site-packages\vispy\util\ptime.py and change the lines with systime.clock() to systime.per_counter()
This fixed it in my env. Im using python 3.10 on win10.
Also I could not install genicam2 with pip install genicam2, so I changes all genicam2 to genicam!
.venv_harvester_gui\Lib\site-packages\vispy
Change all the errors until you get an running gui. On Python 3.8 you will get an error np.bool is not known. You can change that to bool.
I hope I could help you.

I was writing my own gui for the harvester, then came across this beauty. Im now on my way to test it with my scanner.


Site Down

it seems the Site for Hipster Pizza is down.

I am aware. My server currently doesn't have enough resources to run all projects I need it for.

It's up again. Enjoy.

cool thanks, I might try it on friday :+1:


ASUS tinker board 2s, GPIO runtime error

after installing asus gpio and I import ASUS.GPIO as GPIO, it shows this error
RuntimeError: This module can only be run on a ASUS Pi!

I check the py_gpio.c and found this error.
// detect board revision and set up accordingly
if (get_asuspi_info(&asuspiinfo))
{
	PyErr_SetString(PyExc_RuntimeError, "This module can only be run on a ASUS Pi!");
	setup_error = 1;

check code in cpuinfo.c, this snippet code I don't understand it involves for older tinkerboard, maybe not work for tinker board2s
if (!found)
return -1;
info->p1_revision = 3;
strcpy(info->revision, revision);
info->type = "Tinker Board";
info->processor = "ROCKCHIP3288";
info->manufacturer = "ASUS";
info->ram = "1024M";

I use the latest version(Debian-Buster-v2.0.0),The same problem is not fixed.

I think it'd be better to use /proc/device-tree/model for board identification instead of /proc/cpuinfo, whose display format is more likely to change.

I have "Tinker Board 2 Debian 10 V2.0.4" OS for the 2S board and the GPIO driver is not working either, is there any solution to make a simple led on/off test?

As a workaround, you can simply modify the get_asuspi_info function in source/cpuinfo.c and make it return 0.

I have just tried that workaround, and unfortunately, it did not work.

Hi @tangochuynam ,. @JasonShiao @dpergarc :
The gpio python library of ASUS tinker board 2s(RK3399) preinstall in the image by default.
Don't reinstall and compiler the source by the github because the github library is for Tinker Board S(rk3288).
Please reference the related source path for Tinker board 2s in /usr/local/share/gpio_lib_python_rk3399/
Thank a lot!


RuntimeWarning: DateTimeField Shift.shift_start received a naive datetime

Getting a lot of these warnings when I thought I was using America/Los_Angeles everywhere.
Could even be related to #29.

Figured out how to use the debugger against them:
pytest pillarpointstewards -Werror -x --pdb

Used that to narrow down the problem:
> /Users/simon/Dropbox/Development/pillarpointstewards/pillarpointstewards/homepage/views.py(52)render_calendar()
-> for shift in Shift.objects.filter(
(Pdb) list
 47  	    cal = calendar.Calendar()
 48  	    month_start = datetime.date(year, month, 1)
 49  	    next_month_start = next_month(month_start)
 50  	    shifts_by_date = {
 51  	        shift.shift_start.date(): shift
 52  ->	        for shift in Shift.objects.filter(
 53  	            shift_start__gte=month_start,
 54  	            shift_start__lt=next_month_start,
 55  	        )
 56  	    }
 57  	    weeks = []

TIL: https://til.simonwillison.net/pytest/treat-warnings-as-errors


Adds ZeroMQ and the C++ bindings for ZeroMQ

Just a couple of basic changes that should be made first before merging


As a user I want to set a static value in a read-only text field

Is your feature request related to a problem? Please describe.
Often I want to provide additional context to the user about a task.
Describe the solution you'd like
Be able to set a static value (instead of a key that maps to a process variable) on a read-only text field.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
My current workaround is using input mappings to set the value of the key to some static value.
This means the static definition is defined in the process, while it should probably belong in the form.
Additional context

It might be interesting to allow FEEL expressions directly instead of defining a key.
I'd expect a static value to be rendered directly in the modeller, also when this is a FEEL expression like = "foo"

To which execution platform are you referring? Camunda Cloud or Platform?

Ah I wasn't sure there was a difference for forms, but I specifically need this for Camunda Cloud :)

You're probably right, that seems to be not related to a specific platform 👍

Also mentioned in this conversation.

This will be doable once we integrate https://github.com/bpmn-io/form-js/issues/436 (via form-js@0.10). I'm setting this as fixed upstream; feel free to disagree.


test: add ci tests for volume plugin

Signed-off-by: Eric Li<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
add some ci tests for volume plugin
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1368 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1368      +/-   ##
==========================================
- Coverage   17.29%   17.26%   -0.03%
==========================================
  Files         190      189       -1
  Lines       11913    11886      -27
==========================================
- Hits         2060     2052       -8
+ Misses       9706     9686      -20
- Partials      147      148       +1

Impacted Files
Coverage Δ

daemon/mgr/container.go
0% <0%> (ø)
:arrow_up:

daemon/logger/jsonfile/utils.go
70% <0%> (ø)
:arrow_up:

apis/opts/env.go

LGTM


Update zhTW.lua

Update zhTW.lua for CraftSim 12.2.1.

I will leave this open for a while due to me building a new feature which will introduce new locals :D ill ping you when its finished!

OK, thanks!

@class2u  I think with 12.4.0 then you can update your locals again :)

Updated!! Thanks! :)


Feature suggestion

If it is possible, I would like an 'order' field in the RE to sort the choices alphabetically.
Example : Choices in the follow the expert effect
When we are using the effect, the choices are not sorted alphabetically.
It's an improvement for other languages.
Not a top priority but a clever one to avoid hunt for them later.

Would you mind titling the issue as something communicative of the suggestion?

Is this still an outstanding issue?

Yes


The information thrown by the tf.saturate_cast operator in different TensorFlow versions does not match the description in the documentation.

Click to expand!
Issue Type
Documentation Bug
Source
source
Tensorflow Version
TF 2.4, TF 2.10
Custom Code
Yes
OS Platform and Distribution
windows 11
Mobile device
No response
Python version
3.8.15
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
CUDA: 11.3 cuDNN cuDNN 8.6.0
GPU model and memory
RTX3060
Current Behaviour?
The tf.clip_by_norm operator in TensorFlow2.4 version is completely consistent with the TensorFlow2.10 version description, and the data type for x is (A Tensor or IndexedSlices. This must be a floating point type.), so I am testing the code , when x is set to uint32, the information thrown is different in TensorFlow2.4 version and TensorFlow2.10 version, especially in TensorFlow2.4 version, the type of exception information description x can be (bfloat16, half, float, double , uint8, int8, uint16, int16, int32, int64, complex64, complex128) are inconsistent with the official description of a floating point type.

Standalone code to reproduce the issue
from tensorflow import int32
    from tensorflow import uint32
    import tensorflow as tf
    import os

    os.environ['TF_XLA_FLAGS'] = '--tf_xla_enable_xla_devices'
    os.environ['TF_CPP_MIN_LOG_LEVEL'] = '2'
    with tf.device('/CPU'):
        t = tf.saturate_cast(tf.random.uniform([1, 5], minval=0, maxval=257, dtype=tf.int32), dtype=tf.uint32)
        clip_norm = 2.0
        out = tf.clip_by_norm(t, clip_norm)
    print(out)

Relevant log output
Results running on TensorFlow 2.4:  tensorflow.python.framework.errors_impl.InvalidArgumentError: Value for attr 'T' of uint32 is not in the list of allowed values: bfloat16, half, float, double, uint8, int8, uint16, int16, int32, int64, complex64, complex128; NodeDef: {{node Mul}}; Op<name=Mul; signature=x:T, y:T -> z:T; attr=T:type,allowed=[DT_BFLOAT16, DT_HALF, DT_FLOAT, DT_DOUBLE, DT_UINT8, DT_INT8, DT_UINT16, DT_INT16, DT_INT32, DT_INT64, DT_COMPLEX64, DT_COMPLEX128]; is_commutative=true> [Op:Mul]

Results running on TensorFlow 2.10:  tensorflow.python.framework.errors_impl.InvalidArgumentError: Value for attr 'T' of uint32 is not in the list of allowed values: bfloat16, half, float, double, complex64, complex128; NodeDef: {{node Sqrt}}; Op<name=Sqrt; signature=x:T -> y:T; attr=T:type,allowed=[DT_BFLOAT16, DT_HALF, DT_FLOAT, DT_DOUBLE, DT_COMPLEX64, DT_COMPLEX128]> [Op:Sqrt]

@triumph-wangyuyang,
Could you please feel free to submit a PR for the requested change or share the link where the requested change is to be made. Thank you!

@triumph-wangyuyang, Could you please feel free to submit a PR for the requested change or share the link where the requested change is to be made. Thank you!

I don't understand what you mean, do you want me to change it?

@triumph-wangyuyang,
Could you pleasee feel free to create a pull request from here to update the documentation. In most of these, it is adding text to one of the python docstrings as mentioned below.
https://github.com/tensorflow/tensorflow/blob/abd266147c2e108796a5dbf28b0a8f16297bd98d/tensorflow/python/ops/math_ops.py#L333
Thank you!

@triumph-wangyuyang, Could you pleasee feel free to create a pull request from here to update the documentation. In most of these, it is adding text to one of the python docstrings as mentioned below.
https://github.com/tensorflow/tensorflow/blob/abd266147c2e108796a5dbf28b0a8f16297bd98d/tensorflow/python/ops/math_ops.py#L333
Thank you!

Thanks for your reply, I will try to change it later.


Fix ItemSlotSystem popup Logic

About the PR

As far as I know, nobody has reported this, which is kinda surprising. I only got around to fixing it because of #28410, which I think got partially fixed and then wasn't closed?
Anyway, basically anything using ItemSlotSystem to handle insertion / removal of items, notably, chem dispensers and chem masters (don't know about this hapenning to anything else), were bugged, so they would constantly spit out "you can't put that in here!" popups whenever you inserted anything. This bug only happens if ItemSlotsComponent contains slots that have different whitelists.
This is because the popups were triggered at CanInsert per-slot, so if it failed the whitelist for even a single slot it would display the popup, even if the item could be inserted.
Technical details

Removed the optional popup argument to CanInsert so the CanInsert method doesn't generate a popup (this was stupid to begin with)
Changed the logic of OnInteractUsing so it triggers the popups instead, and also triggers them correctly

Media

https://github.com/space-wizards/space-station-14/assets/48413902/d4288c38-3a8c-49f7-94e7-b7f43ae69a1a
Breaking changes

Changelog

:cl:

fix: Fixed the logic triggering popups when inserting items into machines.

SHIT SOMEONE FIXED IT BEFORE I DID AND I DIDNT NOTICE

life is pain

I updated from master and I thought I saw that someone already fixed it. Nope it was just the popup message for a successful insertion which has always been there.

 I overcomplicated it way too much.
Events are also overkill.

Oh also the other changes in the commit is because I formatted the file.

Added an overload method for CanInsert that doesnt have out var reason because optional out vars are not a thing in C# for some reason.

if you don't need the output variable you can just do out _

I think I got rid of the overloaded method.

Updated the technical details comment

Thanks for the fix!


Audio streaming

Just curious is there a way to download only audio from yt?

@callmeahab did u find solution about audio download?

Not really. Got caught up in a lot of work so i didn't have time to work on something either.

As far as I know, the audio and video tracks for a given YouTube video come from the same file (some video format), so I don't think this is possible. I also can't find anything on the iFrame API about audio-only streaming, so I'm going to close this (for now)


Shots can be negative

Describe the bug
The sampler allows for negative values for shots, eg
'run_options': {'shots': -1},

but returns results with 10k shots:
{'header_metadata': {}, 'shots': 10000}

Steps to reproduce
Try using negative shots
Expected behavior
It should fail
Suggested solutions
Additional Information

qiskit-ibm-runtime version: 0.2.0
Python version: 3.10
Operating system: OSX

I've opened this issue in an internal repo where I believe this validation needs to happen. I will use this issue to add client side validation for shots only when using IBMSampler or IBMEstimator because it doesn't make sense to add client side validation when using the generic service.run that can be used to run any program.

I think this was a different bug, so closing


Add missing Minio PORT and USE_SSL configurations to Director deployment

The Director deployment doesn't have any configuration for MINIO_PORT and MINIO_USESSL
Grab the PORT value from the minio service. If the PORT value is 443 then set USE_SSL to true

@tico24 does this look alright to you?


Topics: add adaptor signatures

Don't let the confident tone of this text fool you---it's author still feels he has a very poor understanding of adaptor sigs.  I've tried to make my description as easy to prove wrong as possible (while also hopefully keeping it readable by non-experts), but please don't assume that its detail and assertiveness are proxies for correctness.

@adamjonas thanks for the review!  Obviously, I either need a new glasses prescription, a duplicate words CI test, or both.  :-)

Oh, interesting, I'll try to have a look.

@jonatack the only resource I used that's not listed here---but which was quite influential on my (uncertain) understanding---was @AdamISZ's https://joinmarket.me/blog/blog/flipping-the-scriptless-script-on-schnorr/ .  In particular, I used his nomenclature for the initial equations I started with (and then tweaked them to make more sense to me, e.g. he used x for the private key and P for the corresponding public key, but it made sense to me to use the same letter for both, just with different capitalization).  I didn't include his post in our see_also links because I usually want to focus on specifications rather than explainers, but his post was so useful to me that I probably should make an exception.

Another resource (that is not linked here) is the scriptless scripts repo that contains Andrew's writeup on atomic swaps with adaptor sigs as well as a few other adaptor sig techniques.

@jonasnick it's linked in this PR at https://github.com/bitcoinops/bitcoinops.github.io/pull/435/files#diff-aae86f4a434defe011f0ddb578bcc697R176 .  I found that document particularly useful in comparison with waxwing's blog post; reconciling the slight differences between those two descriptions gave me a valuable opportunity to test my understanding.

Thanks everyone for the reviews so far!  I've left comments on the suggested changes I'm skeptical about but everything else sounds reasonable to me and I'll try to make those changes early next week.

Tbh, I think the term "adaptor signature" is misleading, it's rather a signature adaptor.

If everyone agrees with this we could rename the topic to "signature adaptors" (and have an alias from "adaptor signatures")

"Signature adaptors" sounds fine to me.

I'm not sure. I'd be careful with changing it now, in particular based on a suggestion I spend maybe 30 seconds on. It may not be a good term either, and even if, having two terms creates confusion, too.

@apoelstra fyi

I've pushed an edit for (hopefully) all comments to date.  Thank you everyone for the reviews!  This edit does not change the name of the topic but does use the "signature adaptor" phrase throughout the document.  If people like it, I think we can discuss using that as the main title of the topic and making "adaptor signatures" the AKA.

I've pushed an edit for (hopefully) all comments to date. Thank you everyone for the reviews! This edit does not change the name of the topic but does use the "signature adaptor" phrase throughout the document.

I like that it's an easy solution for the "final signature" thing. The text is much easier to read now because not everything is called a signature.

If people like it, I think we can discuss using that as the main title of the topic and making "adaptor signatures" the AKA.

I think both is fine in the end but I'd stick adaptor signatures as the title, because this is what people will look for. But in either case, I suggest adding a comment that explains that "adaptor signatures" is the standard term but the text here uses "signature adaptor" because it fits better and it simplifies the text.

Sorry if this holds things up further but maybe @LLFourn wants to comment, too.

Hey nice work. I'm glad you are taking the time to explain this super important topic. I think this gives a very good explanation in terms of the operations involved in the Schnorr scheme.
If you were to go into more detail, I always like to point out that adaptor signatures are primarily used in two distinct ways:

To do fair exchange of signatures. Alice gets a signatures on transaction A only in the case Bob gets a signature on transaction B (because when Alice broadcasts A, Bob can get the signature on B). This use is what you cover at the beginning.
As a signature encryption scheme. Alice can give a signature to Bob he can't access until he learns Y. This is for cases where the secret revelation aspect is not important, for example, in the adaptor version of discrete log contracts1.

Thanks @harding and thanks to all our guest reviewers!


Error appears when a page is not found

Expected Behavior
When a page is not found, the 404 page should appear without an error.
Current Behavior
The 404 page appears, but it contains an error.
Steps to Reproduce
Steps to reproduce the behavior:

Go to any page that doesn't exist

Context (Environment)

Default setup
OS: Windows 11
Browser: Chrome
Environment: dev

Issue demo

Solved
https://github.com/Protofy-xyz/Protofy/assets/108338080/529ef6eb-7756-4b61-bb2e-ac4c8ce32888


We should bring back default constructors

Prerequisite Checklist

[X] I searched for existing issues to prevent duplicates
[X] I searched for existing discussions on the forum to prevent duplicates
[X] I understand SFML's scope and believe the feature fits it

Describe your feature request here
I wanted to share my thoughts on using some of the recent changes with SFML 3. There are positives to the changes and I know a lot of work has gone into it, but I'm going to focus on why I think these changes make the experience of using SFML worse.
Am I correct that if we want to store sfml objects on classes, our options are
* wrap it in a smart pointer
* store it as an optional
* manually manage memory via new and delete
I believe this may backfire. A large amount of people are going to remedy the (confusing, potentially hundreds of lines of dense repetitive compile errors) by changing the type to a raw pointer. I believe the bug class we're attempting to solve is something that people who understand the lifetime model behind things like textures and sprites are unlikely to make. I think it's possible that, in our effort to reduce bugs among folks who are new, we're going to push them down a path which is likely to cause even more bugs than the amount that currently exist due to misuse. I know that when I was new I would have changed it to use a raw pointer. The way I resolved this today was by using smart pointers, but this actually caused a handful of runtime crashes that I had to track down due to not having called make_unique as I overlooked a few.
I think we're attempting to solve something which is a problem on paper and not one in practice. I think we get a more miserable API in exchange. In order to get Binary's stencil buffer fix I updated my SFML branch from prior to the event change to the latest master. Here's an example of the type of thing which I think is going to trip people up.
I have an unordered_map<string, sf::Image>. I thought for a moment this would work
asyncLoadedImages[workOrder.path] = std::move(img.value());

But the solution is using insert_or_assign, so we apparently can't use bracket operators here anymore. A small trap here is to make sure that you're not using insert and not using emplace because that's different behavior than what we originally had.
asyncLoadedImages.insert_or_assign(workOrder.path, std::move(img.value()));

This type of thing permeats the API. It's miserable and unergonomic. It's also safer, but I explicitly choose to use C++ for gamedev rather than Rust because I don't think safety is worth the cost in ergonomics and developer speed. If one wants to make a different trade off, respectfully, they should be using a different language. You cannot fix C++. It's like trying to grasp falling water.
Another example from a breathing app I made a while ago. This is now a line in my code
soundBufferExhale = std::make_unique<sf::SoundBuffer>(sf::SoundBuffer::loadFromFile(fi::os::getPathToAudioDirectory() + "exhaleTone.wav").value());

Things become more verbose. It should actually be worse than this in terms of boilerplate because I'm of course not handling whether the optional has a value. When I say you cannot fix C++, you cannot stop users from doing things that are dumb. Many people are going to assume the item was succesfully constructed in place, look at Rust game dev code with implicit assumptions that unwrap() will work everywhere. And that's Rust where there is a much stronger culture of caring about this.
I don't think either of the two things above are deal breakers, but they are annoying. I think the worst thing about this may be that the compiler messages are awful. I'm getting 500+ lines of compiler errors where I need to hunt for context on where it's gone wrong. I sometimes don't get the actual line, I get the general gist of where it is and then need to manually find the sfml object that I need to update away from using a default constructor.
I worry that the changes increase the cognitive load and the level of knowledge you need of C++ in order to be succesful.
Discoverability is also an issue. Both for the static initialization functions, but more re the events API. I think it might be improved slightly if we renamed the template parameter (currently named T) in .is and .getIf with something more descriptive. When your cursor is in the <> brackets, IDEs will give a pop up with the template parameter name -- I think it'd be good to use this to communicate something potentially helpful to the user to let them know it expects an Event type. There is also something awkward about the way this flows now. We check whether it is a specific event, and then calling something like e = event.getIf<...>(); it's already an event, it's awkward.
I don't mind the event API changes too much because it's centralized to a single location in my code and it's fine. I suspect it may be confusing for new folks, but I think the union was also not great, and I think we may actually prevent bugs with this change.
I think removing the default constructors is a mistake though. I frankly am probably going to revert rather than continue using SFML 3. I think these changes are a net negative to me. I'm not interested in arguing, I am aware that I am unlikely to win over people with this, but I care about SFML and wanted to register my thoughts on what I think is going to be a net negative for the library. I didn't comment on the changes when they were being built because in theory they do sound great, but the experience with using the library is frankly worse than I thought it'd be.
Use Cases
.
API Example
No response

Thanks for sharing your perspective, I think it's important to consider your experience and whether we've been going down the right path.
I believe this is always going to be a subjective discussion, but anecdotally I can tell you that the added "friction" I've felt when migrating Open Hexagon to SFML 3.x has actually helped me discover holes in my original design and led to a more robust architecture.
I think that for people like me, the tradeoff between ergonomics/safety is a good thing. But of course I cannot speak for everyone.
I'd also like to point out that the model used in SFML 3.x needs a bit of a mindset change to get used to, and that all our tutorials/documentation do not provide tips and examples on how to effectively consume our new APIs.

Am I correct that if we want to store sfml objects on classes, our options are

wrap it in a smart pointer
store it as an optional
manually manage memory via new and delete

Not really, you can just store it as usual. You just need to initialize it in the constructor of your own class. See our Shader.cpp example:
class Pixelate : public Effect
{
public:
    explicit Pixelate(sf::Texture&& texture, sf::Shader&& shader) : // <- pass in ctor
    m_texture(std::move(texture)), // <- move into class member
    m_shader(std::move(shader))    // <- move into class member
    {
        m_shader.setUniform("texture", sf::Shader::CurrentTexture);
    }

    // ...

private:
    sf::Texture m_texture; // <- stored as usual
    sf::Shader  m_shader;  // <- stored as usual
};

To create Pixelate itself from fallible resource loading, you follow SFML's pattern with optionals:
std::optional<Pixelate> tryLoadPixelate()
{
    auto texture = sf::Texture::loadFromFile("resources/background.jpg");
    if (!texture.has_value())
       return std::nullopt;

    auto shader = sf::Shader::loadFromFile("resources/pixelate.frag", sf::Shader::Type::Fragment);
    if (!shader.has_value())
        return std::nullopt;

    return std::make_optional<Pixelate>(std::move(*texture), std::move(*shader));
}

Or you can just "wing it" if you don't care about propagating the errors:
auto pixelate = Pixelate{
    sf::Texture::loadFromFile("resources/background.jpg").value(),
    sf::Shader::loadFromFile("resources/pixelate.frag", sf::Shader::Type::Fragment).value()
};

This gives the user the freedom to choose whether they want to handle the errors or not, but always makes them aware that they can happen.

I have an unordered_map<string, sf::Image>. I thought for a moment this would work

This is mostly the fault of associative containers APIs in the standard library, and I do feel your pain here. Consider using std::unordered_map<string, std::optional<sf::Image>>.
In general, any time you feel like "we should have a default constructor here", a valid answer is "wrap it in an optional yourself". This always allows you to get default constructibility when you want, but also ensures that places where default constructibility is not required do not unnecessarily introduce an extra "empty" state that can cause run-time issues.

Another example from a breathing app I made a while ago. This is now a line in my code

What's the reason that sf::SoundBuffer is wrapped in a std::unique_ptr? If you share more code, I can likely help you figure out how to avoid the friction you're experiencing.

I think it might be improved slightly if we renamed the template parameter (currently named T) in .is and .getIf with something more descriptive.

This is a great suggestion that takes low effort to implement. I also think event visitation would be greatly improved with #3014.

I think removing the default constructors is a mistake though.

Your pain is real and the friction you've experienced should not be understated. However, I strongly disagree with your claim, as you can always reintroduce the empty state of any SFML type when (and only where) you need it by wrapping it in a std::optional yourself.
In most cases, you will not need to do that, and you'll benefit from the static compile-time knowledge that if you have a sf::Image, that image is guaranteed to be valid.
In some cases, either due to outdated standard library APIs, or due to pragmaticity/prototyping speed, it's trivial to wrap whatever you want in an optional.

Keep in mind, SFML 2 uses C++03 and thus has relatively fewer options for good, expressive factory function APIs. While I was not around at the time SFML 2's API was being written, I can imagine it made sense to resort to two-phase initialization to allow for initialization to fail. Perhaps SFML 2 could have used boost::optional or a custom optional wrapper class but both of those options come with their own downsides. As Hyrum's Law describes, users inevitably came to depend on this two-phase initialization even though that wasn't necessary the intension of its designers.
I largely agree with Vittorio. Anywhere you want to do two-phase initialization you can wrap the type in std::optional. That two-phase initialization must be explicitly spelled out in your code rather than it being baked into the SFML type itself. I understand this pattern may look ugly but I think it's ugly for good reason. Two-phase initialization is bug prone and worth removing. If you find yourself needing to use optionals a lot to defer initialization then perhaps revisit why you want some much deferred initialization in the first place.
As library authors we have to cater to a large number of users of different backgrounds with different desires. We have little control over the way in which users write code. One of our most effective tools to root out bugs in SFML programs is to make invalid states unrepresentable by the type system. This what we have done by removing these particular default constructors. We now have more confidence that certain types of bugs related to loading resources will either be fixed when upgrading to the v3 API or will be made much more clear when reading code.
I appreciate you taking the time to detail your struggles and hope some of these recommendations ease the pain with using the new API. I'm quite confident the SFML team is going to maintain our current stance and will not add default constructors back and as such will be closing this issue.

BTW, I would like to encourage discussion on the matter. Sharing problematic code snippets, or anecdotes regarding pain/friction, is very useful.
There's very often a different way to write the code to avoid the pain/friction, and I believe we should collect these examples so that we can then integrate them in our documentation/tutorials.
The associative container pain point mentioned here was a great one.

Just my 2 cents...
I am somewhere between both camps on this issue.
I generally agree that preventing creation of objects in an unusable state is a good thing.
Because the original code wasn't posted, I assume it would have looked something like this:
asyncLoadedImages[workOrder.path].loadFromFile(...);

This worked because sf::Image had a default constructor, however what would happen if loading fails? In correct code, the result of loadFromFile would have to be checked and if the assumption that asyncLoadedImages only contains loaded images was to be kept, the empty image would have to be removed from the map:
if (!asyncLoadedImages[workOrder.path].loadFromFile(...))
    asyncLoadedImages.erase(workOrder.path);

While this is a correct solution, it is inefficient (inserting and directly erasing an element) and can lead to errors if something prevents the erasure from taking place.
The new API forces the user to check for validity before inserting the (valid) object into the map thus guaranteeing everything in the map is actually valid.
Now... the reason I said I was somewhere between both camps is because I am on @danieljpetersen's side when it comes to how "ugly" the new API makes code look.
The main goal of the change was to prevent useless objects from being created, not to force std::optional usage down user's throats. The current implementation just happens to be implemented using std::optional but I think there is something we can do that satisfies the goal of the change while not making user's code too "ugly".
If we take asio's API as an example, they often provide both non-throwing and throwing variants of many functions. Obviously it is important to know if a network operation is successful or not so there is no way around getting back the result of the operation, either through an error_code reference variable or via exceptions.
What we have now is the non-throwing variant of our loading functions.
In my own projects I tend to use std::optional in cases where there is an equal probability of it having a value and not having a value. I personally would never use std::optional to signal success or failure, especially when failure rarely ever happens. In these cases I use exceptions, since you know... failing to load a file is an exceptional case that should never really happen if everything works out...
I think we can defuse some of the perceived "opinionation" by providing throwing alternatives to our loading functions for those who would rather deal with exceptions than std::optionals. I would be one of those people. The throwing constructors would have the same signature as the loading functions and throw on failure. Since the object is never fully constructed in this case, it would satisfy the same "disallow useless objects" goal as the current API without forcing users to deal with std::optionals if they don't like them.
The example code that @danieljpetersen provided would then look like:
asyncLoadedImages.try_emplace(workOrder.path, "somepath");

and
soundBufferExhale = std::make_unique<sf::SoundBuffer>(fi::os::getPathToAudioDirectory() + "exhaleTone.wav");

I've omitted the exception handling, but I think everyone gets the picture. If anything goes wrong no useless object is created, same as with the std::optional functions.
I think we should keep an open mind and take into consideration user's coding preferences. Some people might prefer exceptions, some might disable them completely, some people might love std::optional and others might unwrap them at the first opportunity possible.
I assume that both camps agree that preventing the creation of useless objects is a good thing, currently there is just disagreement on the way to get to the goal. The current implementation was written taking the subjective coding preference of a subset of users into mind. We should also provide those who prefer exceptions an alternative as well. As they say... all roads lead to Rome.

Not sure if closing this (which is fine, esp. regarding the v3 API freeze) also means the discussion itself is closed. (BTW: how about a Discussions section here, on GitHub? The forum may not quite be the optimal way for this; not sure about the GH Discussions feature either, though.)
Anyway, for another 2 cents (from a C++ veteran no longer professionally active, but still tinkering), just wanted to say I wholeheartedly agree with the sentiment of the OP.
Well, and with the sentiment of the devs, too... -- which hopefully indicates I'm not dogmatic either way. However, I kinda can't help but feel the recent API changes have shifted toward that direction a bit.
The new design, with all of its good intentions, by committing to C++isms, it has also (inevitably) committed to giving up part of SFML's main appeal: simplicity (that letter "S" in the name).
Also, excluding a set of pitfalls entails the cost of removing some flexibility of design choices, too.
For some toy projects (altogether <100k lines) for which I've chosen SFML-master (acknowledging breaking changes), now I'm finding myself in the need to grow a horribly kludgy -- but most importantly: with the more lenient old API design entirely unnecessary -- wrapper layer around SFML, overriding my previous commitment to just riding it raw.
Unfortunately I don't have the time to go into details, but please understand that I'm not "emotionally invested", I'm simply sharing my observation of myself as a user of SFML3.

Just one random note about a RAII-related point above, because it's still fresh in my mind:

You just need to initialize it in the constructor of your own class.

Unfortunately, as member/ancestor ctor params tend to propagate all the way down a class hierarchy, this also means that, unlike before, you can longer just create a complex app instance with an idle, empty state (with a statically designed/instantiated) class structure, and then populate its components as you go, on-demand, but are now kinda forced to design everything around all-or-nothing RAII.
(Also, ctor init lists are one of the worst features of C++, even compared to the feature group it belongs to: initialization, which itself is already the worst part of the language. :) )

@xparq Would #3134 help to address your concerns?


do not chill indirectly-slashed nominators

cc @burdges, @jacogr
When a validator is slashed, its nominators are currently kicked until explicit re-nomination. This PR causes that not to happen. The phragmén election already pre-filters for votes cast after a validator's most recent slash, so the nominators' votes on the slashed validator will be ignored until next explicit nomination.
The UX here is not ideal, since those votes on slashed validators will be silently ignored. User apps will be able to perform the same check as the staking code - I've spoken with @jacogr about this before, but pinging again here.

No tests to correct?

We've worked over the trade offs here fairly well, so if you think this makes sense then go for it.  We should ideally avoid them being able to reoffend for free in future of course, but I gather this is happening in a way that makes that not happen.
Is there some weaker state of which we should elevate the importance?  We'd some scheme for chilling them only when they got slashed enough for example.  Or just not worry about it for now?

We should ideally avoid them being able to reoffend for free in future

Is that a risk introduced by this PR? This approximate behavior could always be emulated in the old system by ensuring that a nomination transaction immediately followed the slash report.

We'd some scheme for chilling them only when they got slashed enough for example

At some point I guess, but the complexity of tracking so much state for each nominator sounds like a lot.

At some point I guess, but the complexity of tracking so much state for each nominator sounds like a lot.

I've now forgotten if this required tracking more state.  I'd believed it was equivalent at some point, but maybe you found something else that needed tracking.  If so, I do not remember cleanly sorting out cleanly if that record sticks with other records in the tree (cheap) or floats off elsewhwere (expensive).


FranceCulture is broken

Checklist

[X] I'm reporting a broken site support
[X] I've verified that I'm running youtube-dl version 2021.01.16
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones

Verbose log
[debug] System config: []
[debug] User config: ['--restrict-filenames']
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.franceculture.fr/emissions/la-methode-scientifique/la-methode-scientifique-emission-du-mercredi-20-janvier-2021']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.01.16
[debug] Python version 3.9.1 (CPython) - Linux-5.10.7-arch1-1-x86_64-with-glibc2.32
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1, rtmpdump 2.4
[debug] Proxy map: {}
[FranceCulture] la-methode-scientifique-emission-du-mercredi-20-janvier-2021: Downloading webpage
ERROR: Unable to extract video data; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/home/aurelien/nosave/./youtube-dl/youtube_dl/YoutubeDL.py", line 805, in wrapper
    return func(self, *args, **kwargs)
  File "/home/aurelien/nosave/./youtube-dl/youtube_dl/YoutubeDL.py", line 826, in __extract_info
    ie_result = ie.extract(url)
  File "/home/aurelien/nosave/./youtube-dl/youtube_dl/extractor/common.py", line 532, in extract
    ie_result = self._real_extract(url)
  File "/home/aurelien/nosave/./youtube-dl/youtube_dl/extractor/franceculture.py", line 33, in _real_extract
    video_data = extract_attributes(self._search_regex(
  File "/home/aurelien/nosave/./youtube-dl/youtube_dl/extractor/common.py", line 1010, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract video data; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description
I think the verbose output says it all. Thanks for this awesome work!

for this link - https://www.franceculture.fr/emissions/la-methode-scientifique/la-methode-scientifique-emission-du-mercredi-20-janvier-2021  just press F12 on you keyboard to bring up the debug menu, select network - media - play the podcast and you should see the mp3 link,
copy the link and feed it into youtube-dl to download the podcast.

for this link - https://www.franceculture.fr/emissions/la-methode-scientifique/la-methode-scientifique-emission-du-mercredi-20-janvier-2021  just press F12 on you keyboard to bring up the debug menu, select network - media - play the podcast and you should see the mp3 link,
copy the link and feed it into youtube-dl to download the podcast.

Thanks @october262
That's only a workaround though, since having to open the URL in a web browser defeats the very purpose of CLI-based downloading which is what youtube-dl is all about. The FranceCulture extractor was working perfectly until a few days ago. I hope/guess it's "just" a matter of rewriting the previous regexp.

Thanks @october262
That's only a workaround though, since having to open the URL in a web browser defeats the very purpose of CLI-based downloading which is what youtube-dl is all about. The FranceCulture extractor was working perfectly until a few days ago. I hope/guess it's "just" a matter of rewriting the previous regexp.