ratox: 0.2.1 -> 0.4

Motivation for this change
Update.
The problem with both old and new ratox versions is that they have an outdated bootstrap node list and so can't connect to the DHT. If one is to patch the source with an updated node list it works. But I don't want to put a huge patch for that into nixpkgs. Just be aware that it wouldn't strictly "work" as-is if you run the compiled binary. This update is mainly a follow up to #22775 to drop libtoxcore-old derivation.
/cc @peterhoeg
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

I believe propagatedBuildInputs only apply to python packages.

No, it works for plain mkDerivation too.
You can check it by reverting those lines and compiling ratox.
It will fail.

How about fetchpatching the updated nodelist then? While getting rid of libtoxcore-old is great, an actual working ratox is even better! ;-)

ratox was able to bootstrap DHT for me.

Maybe some DHT nodes were offline when I tested it. The original patch
is from SLNOS (I prefer things with proper ncurses UI, not with bare
FIFOs), I just saw it pushed to SLNOS and decided to play with it a bit.
If it works for you, you should totally just merge it. I'm too lazy to
play with it again.

ratox should not explicitly link with libsodium and libmsgpack
because it does not include their headers and is not linked with them
statically. I have removed the change to libtoxcore.

I see you patched ratox for this, which is fine and if it compiles and
runs properly, then LGTM. But I don't see how propagating those things
as in the original patchset could hurt. I could be used to simplify
other expressions using libtoxcore that do link those libraries (e.g.
qTox) and then ratox doesn't need to be patched (who cares about a
couple of entries in the ELF header).

Maybe some DHT nodes were offline when I tested it.

The first 2 or 3 it tried were inaccessible, but it kept retrying and was able to connect.

But I don't see how propagating those things as in the original patchset could hurt. I could be used to simplify other expressions using libtoxcore that do link those libraries (e.g. qTox) and then ratox

In general packages should declare all their direct dependencies because it prevents breakage when implicit but necessary dependencies are no longer transitively included. In particular, qtox does #include <sodium.h> and hence depends on libsodium, but it does not directly depend on libmsgpack so it does not declare this dependency. ratox directly depends on neither (except in the attempt to link with them) and does not need to declare them.


Initial release

@JuliaRegistrator register

@JuliaRegistrator ?

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/58669
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 3518dc1c403b53b45e66784751a4f15821f8594f
git push origin v0.1.0


Ergo 0.20.* should be switched to the latest version of the Q*cert library

The 0.20.0-alpha.* version of Ergo still relies on unpublished fixes to the Q*cert backend.
Those are about to be published as Q*cert version 1.4.0. See pull request for the publication in opam at https://github.com/coq/opam-coq-archive/pull/924
The Ergo build should be switched to that version as soon as it is published.
This will also fix CircleCI tests which are still failing on the js-release-0.20 branch.

This is done, and the GitHub checks for js-release-0.20 are all green again, including CircleCI:


[Feature] Make generator a deployable npm package

Is your feature request related to a problem? Please describe.
Currently, it's a project boilerplate and can not be published to npm
Describe the solution you'd like
Wrap the generator in nyg like the previous version.
Describe alternatives you've considered
N/A

https://github.com/Rich-Harris/degit

Two solutions so far:

Integrate nyg here and move things around.
Create a separate npm package that clones this repo (it's more clean)

Another way I like is with GitHub template b/c we'd have to create a repo on GitHub for every new project anyway; so it would be very convenient.
And it's an opt-in thing, we could mark this as an template and still combine/integrate with other solutions.

Do we want to close this? We're using this as a Github template currently.


Custom types without array configuration

The number one thing that I do not like about this library is the usage of arrays for configuration. From what I've heard from my friends who have more experience with GrpahQL in PHP they have ultimately chosen Youshido for this very reason.
Instead of this from the documentation
class UserType extends ObjectType
{
    public function __construct()
    {
        $config = [
            'fields' => function() {
                return [
                    'email' => MyTypes::string(),
                    'friends' => MyTypes::listOf(MyTypes::user())
                ];
            }
        ];
        parent::__construct($config);
    }
}

I'd much rather define my types like this:
class UserType extends ObjectType
{
    public function getFields(): array
    {
        return [
            'email' => MyTypes::string(),
            'friends' => MyTypes::listOf(MyTypes::user())
        ];
    }

    // getDescription, getInterfaces etc.
}

When I looked into the ObjectType I noticed that it already has methods like these. In my opinion we should add an ObjectTypeInterface and have the ObjectType class implement it. In the code wherever an instance of ObjectType is required it should instead require the interface. Then anyone could extend that interface to define their types without nasty arrays.
There could also be an AbstractObjectType class implementing methods that you dont always need to define yourself such as getInterfaces returning an empty array.
Similar thing should be done for FieldDefinition though it should no longer have public properties like args. There should be a getArguments method instead. This will be a bit more tricky to do and would probably involve deprecating the FieldDefinition class in favor of a completely new FieldInterface with some proxy implementation for the FieldDefinition class.
I saw a Youshido-based application where not just every type but also every field had its own class and it looked very good. I want to achieve the same with webonyx.
This could be a better alternative to https://github.com/webonyx/graphql-php/issues/70 and https://github.com/webonyx/graphql-php/pull/74.

We considered adding it in #78 but the more I think about it the more I incline not to introduce any base classes or interfaces. There is a good reason why smart people prefer composition over inheritance.
Interfaces are fragile and hard to modify. Say we have an interface in the library and many projects start using it. Then at some point, we decide to add an optional method to this interface or even rename a method. It will introduce an unnecessary breaking change. An alternative here is to add new interfaces for each minor tweak.
With data structures instead of interfaces, we can provide reasonable defaults ourselves and avoid many breaking changes. We can also do much smoother deprecations.
Another problem is that having two ways of defining types makes maintenance much harder. It also introduces different experience for library users and makes it harder to communicate and solve issues.
That's why I am actually re-considering if we need #74 at all (even though it's just a syntax sugar).
The way you want to define your types is quite possible with composition. Just use your own classes and have a separate factory which builds actual definitions. For example:
class UserType
{
    public function getFields(): array
    {
        return [
            'email' => MyTypes::string(),
            'friends' => MyTypes::listOf(MyTypes::user())
        ];
    }

    // getDescription, getInterfaces etc.
}

class MyTypes
{
    private $types = [];

    function user()
    {
        // obviously you can automate this for all types:
        $myUserType = new UserType();
        return $this->types['user'] ?? $this->types['user'] = new ObjectType([
            'name' => $myUserType->getName(),
            'fields' => [$myUserType, 'getFields'],
            'myClass' => $myUserType, // just in case if you'll need a reference later
        ]);
    }
}

Actually some framework wrappers (like laravel graphql) do exactly this.
I do understand that PHP is heavily infected by OOP, but it doesn't mean that it is the only right way to do things %)

Yeah I know I can do it the way you describe but I don't consider it a good solution - it would only add unnecessary transformations everywhere slowing down the application. I've already heard claims that webonyx is in fact much slower than Youshido (but they don't have the benchmark sources anymore so I can't validate that claim) so I really don't want to add more layers to slow it down even more. And the code would look very ugly in some cases where it would not be possible to abstract.
Firstly let me correct my previous comment a bit - when I talked about abstract class implementing the optional methods like getDescription and getInterfaces it should not be an abstract class but actually a trait. So custom types would look like this:
class UserType implements ObjectTypeInterface
{
    use ObjectTypeTrait; // empty getDescription and other optional methods

    public function getFields(): array
    {
        return [
            'email' => MyTypes::string(),
            'friends' => MyTypes::listOf(MyTypes::user())
        ];
    }

    // ...
}

Interfaces are fragile and hard to modify. Say we have an interface in the library and many projects start using it. Then at some point, we decide to add an optional method to this interface or even rename a method. It will introduce an unnecessary breaking change. An alternative here is to add new interfaces for each minor tweak.

While true at first glance this is not actually the case. There is an approach to make such additions very smooth. When you need to add an optional method you add it but comment it out, implement it in the trait with default value and add a note to the change log that implementations of that interface that do not implement such method are deprecated. However since 99% of all implementations would use the trait anyway they would be uneffected because the trait would define it for them. Then you just uncomment the method in the next major release. This is how Symfony does BC breaks by the way. It works very well.
Besides the cases where you actually want to add such optional method are quite rare. It would certainly not be necessary for "every minor tweak" as you put it.
Also I should note that this library is still in 0.x.y versions which is a pre-release stage and BC breaks can occur according to semver. Still it's a good practice to make them smooth as I described above.

There is a good reason why smart people prefer composition over inheritance.

That's exactly why I'm proposing this. To use composition to its full potential you need interfaces defining the contract between classes so that you can replace any class with your own implementation if necessary. This library is very bad in this regard.
I want to achieve a state where a Type definition uses composition for the fields instead of defining them by itself. Yes I could compose it using some factories and automate it as you described but its not a clean solution that I can recommend to others. If this library had some interfaces then I could write an article with recommended usage of this library and the code would look very good.

Another problem is that having two ways of defining types makes maintenance much harder. It also introduces different experience for library users and makes it harder to communicate and solve issues.

That's why this library should ultimately deprecate the current array configuration in favor of the interfaces and completely remove it in some future version.

I see now that #78 is exactly the same proposal. I don't understand why you're against it now since you originally proposed it yourself. It is the right direction, just interfaces and traits should be used instead of abstract classes as suggested by @tpetry. Your worry about extending the interfaces in the future is baseless - I guarantee you it would be needed very very rarely and can be perfectly smooth as described above.

I don't understand why you're against it now since you originally proposed it yourself

Because I had quite bad experience since then maintaining interfaces. Commenting methods in them is a nice workaround but it just proves the point. Also, you haven't covered method renamings and signature changes.

I don't consider it a good solution - it would only add unnecessary transformations everywhere slowing down the application.

How much will it slow down the application? It may have some memory overhead, but in general, with type lazy loading, I do not think it will be significant (claiming otherwise requires some evidences for rational decision making, otherwise it sounds like premature optimization).
This solution is actually good enough. Yes, it is more of a functional approach than OOP, but it is OK (even if you don't like it).

I've already heard claims that webonyx is in fact much slower than Youshido

Claims, really? If you have doubts - do your benchmarks. But keep in mind that there are at least 3 stages - parsing, validation, and execution. In order to compare apples to apples, you must have all 3 stages feature-complete in both libs, properly configured (lazy type loading?) which is not the case. Otherwise, you would probably pick the other option, right?

And the code would look very ugly in some cases where it would not be possible to abstract.

Seeing real-world examples would be nice?

Also I should note that this library is still in 0.x.y versions which is a pre-release stage

It just mirrors versioning of the reference implementation to simplify understanding of compatibility between them.

To use composition to its full potential you need interfaces defining the contract between classes so that you can replace any class with your own implementation if necessary.

Except that providing such contracts we also establish a fragile public API which we'll have to respect for BC. We do not provide such interfaces intentionally.
Instead, we split the processing into steps of data transformations and if you need something - you can do it yourself between those steps. Other things you can solve with composition (like resolver composition). It actually allows us moving without major breaks.

I want to achieve a state where a Type definition uses composition for the fields instead of defining them by itself

I would really prefer an example of what you are trying to do which is impossible now. That would help much more than such an abstract discussion. For now, I see only your personal preferences.
One thing you should understand is that this lib is a direct port of graphql-js. Moving too far away from it means it will be much, much harder to follow. And that's one of the main reasons why we were able to port most of their features (and there are lots of them). Deviating significantly means making lib maintenance orders of magnitude harder.
We are quite open to helping solve real problems, but in order to do so, please start by providing real examples of what you couldn't do with the lib. The fact that you don't like the solution proposed is just not good enough reason for a change (doesn't pass cost-benefit analysis).
Also, note that the issue #78 is still open because I am still waiting for a real-world data of benefits from it. If we see significant performance benefits on real-world projects or something major that really can't be done with current implementation and can be done with interfaces - we will move forward, but I haven't seen enough evidence yet that we really need it.
To summarize, give us some numbers/examples.

I'l take a step back, reconsider my opinions and respond properly later. Thank you for taking your time to write such detailed response.

Closing as dupe of #78 We'll continue this discussion there.


Fix Japanese Translation

Some of the Japanese translation is incorrect and out of context. Possibly batch generated on Google translate?

@nlanson Could you work on that?

Is this resolved? Where are the issues?


How to get RAW ftp client?

Is there any way to get raw FTP client?
I need access to some client properties (client._queue.length).

+1

There is currently no way to do this, but if someone would like to make a PR to expose the client, I'll gladly take a look and merge it.

https://github.com/realtymaps/promise-ftp/pull/11

PR merged into v1.3.0


Add example client

This could be put in a separate repo, with most of functionality provided as a library, just needed to start somewhere.


Add description about plugin settings in readme

Codecov Report

Merging #18 (ef2b3ff) into master (3fe45b5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #18   +/-   ##
=======================================
  Coverage   46.47%   46.47%
=======================================
  Files           8        8
  Lines         525      525
=======================================
  Hits          244      244
  Misses        266      266
  Partials       15       15

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3fe45b5...ef2b3ff. Read the comment docs.


install issue

thanks for your smart library, I find that npm warn be throwed after install it like below image show.

Is it necessary to care about this warn message?
version
react-native 0.44
react 16.0.0-alpha.6
thanks for your time,
regards

Hi @L-Jovi , it's just a warning, without any side effects.
I also published 2.0.2 to fix to, thanks a lot!

@ascoders  thanks for your reply.


Netopeer2-cli gives this error on trying to connect with netopeer2-server-->  Failed to create socket (Address family not supported by protocol).

Hi , when we do listen from netopeer2-cli  it gives this error::

listen
nc ERROR: Failed to create socket (Address family not supported by protocol).
Waiting 60s for an SSH Call Home connection on port 4334...
nc ERROR: nc_accept_callhome: libnetconf2 not initialized.
cmd_listen: Receiving SSH Call Home on port 4334 as user "root" failed.

VERSION: Netopeer2 CLI 2.0.64
Kindly give me suggestion .

My guess is that your system does not support IPv6 and the default host to listen on is ::0. If you just run
listen --host <IP_ADDRESS>

it should work.

My guess is that your system does not support IPv6 and the default host to listen on is ::0. If you just run
listen --host <IP_ADDRESS>

it should work.

Thank you , it worked.


chore: update _app.tsx for qa

The pr is for testing. do not merge!

You probably should have opened this up as a draft cause you automatically requested for a review from zgo

You probably should have opened this up as a draft cause you automatically requested for a review from zgo

right. i have same feelings on ubiquibot repo lol

anyway its not needed. close it


Move LockableCurrency trait to fungibles::Lockable and deprecate LockableCurrency

Priliminary efforts to introduce a Lockable trait based off LockableCurrency.
This moves us closer to the points in https://github.com/paritytech/substrate/issues/8453

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2095567

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2100851

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2100858

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2110392

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2110399

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2118066

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2118110

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2118109

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2118196

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2118466

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2118468

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2118467

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2118709

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2119103

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2119102

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2122629

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: test-linux-stable-int
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2122687

bot rebase

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2133743

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-check-benches
Logs: https://gitlab.parity.io/parity/mirrors/substrate/-/jobs/2133742

bot merge

Why was this put into the fungibles and not fungible? I think fungibles represent everything pallet-assets related and have an AssetId param added into each method

Why was this put into the fungibles and not fungible? I think fungibles represent everything pallet-assets related and have an AssetId param added into each method

It wasn't clear to me what the difference between fungibles and fungible was. I originally used fungible::*, but moved it to fungibles::* because in https://github.com/paritytech/substrate/issues/8453, fungibles::Lock and fungibles::Lockable was referenced more often than fungible::Lockable.

and what's the point of prefixing everything with fungibles::? Why can't it simply be imported and used? In some files I can see it imported, but still prefixed after, like here: https://github.com/paritytech/substrate/pull/12798/files#diff-b951f7aa7b2dd08421d8cdd7a0c8f6364e9777f30c40a7eb9e8629cb03e90dd6R163

I was following a pattern i saw around the codebase. It seemed like the traits in fungibles were always referenced with the fungibles:: prefix.
https://github.com/paritytech/substrate/blob/master/frame/assets/src/impl_fungibles.rs#L22
https://github.com/paritytech/substrate/blob/master/frame/assets/src/impl_fungibles.rs#L175
https://github.com/paritytech/substrate/blob/master/frame/support/src/traits/tokens/fungible.rs#L220-L220
https://github.com/paritytech/substrate/blob/master/frame/support/src/traits/tokens/nonfungible.rs#L171-L171
A second reason is that i assumed clarity about where the trait is coming from might be useful.
WDYT?

You put a prefix in a case of having two traits with the same name in different files, like here in your links: Inspect.
When there is no naming-collapse, you usually don't put a prefix

You put a prefix in a case of having two traits with the same name in different files, like here in your links: Inspect. When there is no naming-collapse, you usually don't put a prefix

I see. That makes sense. I quite like the clarity though.


Docker development environment

:+1:

Anything which needs to be changed in README / CONTRIBUTING?

Not right now, @mweibel, but this isn't quite ready yet. I'll be back to it soon. Unfortunately Intern 3 (required for ES6) screwed me over and lost me 3 days.


Releases not shown on github

Hi,
I'm excited to see that pypandoc gets updated.
However, the latest release shown here on github is 1.7.0 from Dec 2021, and I can't see what's new in the actual latest release (1.7.5).
Would it be possible to update the releases page?
https://github.com/NicklasTegner/pypandoc/releases
Thanks,
Eli

hi @h5rdly
You can find the missing patches, here:
https://github.com/NicklasTegner/pypandoc/tags


Sentry: null is not an object (evaluating 'e.scrollTop')

After upgrading vue-perfect-scrollbar to 0.2.1, I am receiving this error a lot (116k times) in Sentry:
Browser: Safari
OS: Mac OS X / iOS
User-Agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0 Safari/605.1.15

 * perfect-scrollbar v1.4.0
 * (c) 2018 Hyunje Jun
 * @license MIT
{snip} t.containerWidth=e.clientWidth,t.containerHeight=e.clientHeight,t.contentWidth=e.scrollWidth,t.contentHeight=e.scrollHeight,e.contains(t.scr {snip}

Any ideas why this could be happening would be greatly appreciated. Is there any workaround for this?

Have you solved this issue ?

I have tons of these also from my users (via bugsnag), all from Safari and iOS web views. Also using vue2-perfect-scrollbar.

Have you solved this issue ?

Yes. I simply forked the repo and applied the fix there. Someone already created a PR here: https://github.com/mdbootstrap/perfect-scrollbar/pull/977
They are yet to merge it so I found forking and fixing is the only way to stop this error which was the root cause of my Sentry quota exceed.

I have tons of these also from my users (via bugsnag), all from Safari and iOS web views. I have perfect-scrollbar 1.5.0 and am also using vue2-perfect-scrollbar 1.5.0.

You can fork the repos and apply the fixes there. Someone already created a PR here: https://github.com/mdbootstrap/perfect-scrollbar/pull/977 but I am not sure when they will merge it.

Thanks @riz007 will deploy that and hope the error reports go away.

Seems to have done the trick.

A new release was made that's supposed to include the fix but it doesn't seem to work for me because of https://github.com/mdbootstrap/perfect-scrollbar/pull/977#issuecomment-882065525


Importing HTML Pages as Public URLs

Is your feature request related to a problem? Please describe.
When pasting a public URL of an HTM or HTML page, I see the following error:
Error: can't upload/process file on server side. Reasons:

int() argument must be a string, a bytes-like object or a number, not 'NoneType'

[object Object]

[object Object]

500

Describe the solution you'd like
As a data labeler, I would like to paste URLs of public pages, so I am not forced to manually copy HTML pages.
As a data labeler, I expect Label Studio to automatically create a local copy of a public URL.
Describe alternatives you've considered
Uploading an HTML file locally
Additional context
Here are the steps I took to replicate my flow:

Go to http://localhost:8080/import

Type: https://www.sec.gov/ix?doc=/Archives/edgar/data/1800/000110465920053384/abt-20200331x10q.htm

Click "import"

added in https://github.com/heartexlabs/label-studio/pull/320


[BUG] STDOUT not respecting Log4J configuration

Describe the bug
I've updated my log4j configuration and it stopped to save logs o file system, so, it worked well.
I've fixed all log levels to errors but data-prepper continues printing the content of the logs received.
To Reproduce
1: Updated log4j configutation at '/usr/share/data-prepper/config/log4j2-rolling.properties' with:
status = error
dest = err
name = PropertiesConfig

property.filename = log/data-prepper/data-prepper.log

appender.console.type = Console
appender.console.level = error
appender.console.name = STDOUT
appender.console.layout.type = PatternLayout
appender.console.layout.pattern = %d{ISO8601} [%t] %-5p %40C - %m%n

rootLogger.level = error
rootLogger.appenderRef.stdout.ref = STDOUT

logger.pipeline.name = org.opensearch.dataprepper.pipeline
logger.pipeline.level = error

logger.parser.name = org.opensearch.dataprepper.parser
logger.parser.level = error

logger.plugins.name = org.opensearch.dataprepper.plugins
logger.plugins.level = error

I am currently using the default pipeline for open telemetry use case (/usr/share/data-prepper/pipelines/pipelines.yaml):

entry-pipeline:
  delay: "100"
  source:
    otel_trace_source:
      ssl: false
  sink:
    - pipeline:
        name: "raw-pipeline"
    - pipeline:
        name: "service-map-pipeline"
raw-pipeline:
  source:
    pipeline:
      name: "entry-pipeline"
  processor:
    - otel_trace_raw:
  sink:
    - opensearch:
        hosts: [ "https://opensearch.stag.bolttechbroker.net" ]
        username: "edirect"
        password: "123@PenguinsCanFly;)"
        index_type: "trace-analytics-raw"
service-map-pipeline:
  delay: "100"
  source:
    pipeline:
      name: "entry-pipeline"
  processor:
    - service_map_stateful:
  sink:
    - opensearch:
        hosts: [ "https://opensearch.stag.bolttechbroker.net" ]
        username: "edirect"
        password: "123@PenguinsCanFly;)"
        index_type: "trace-analytics-service-map"

Expected behavior
I dont want to have all requests logged to my console, I just want to have errors logged to it.
Screenshots

Environment (please complete the following information):

OS: Debian
Version: latest

Additional context
I am currently using the lates version of data-prepper

I have seen this type of log before. I my case it was not logging a normal span which gets processed, but belonged to I think a "Buffer has not enough capacity" error log. In your screenshot there is also no sign, that this is a log below the error log level (e.g. that this is a log with INFO log level)

You are right:

There are any way to decrease the size of this logs? Let's say, skip the stdout of the traces.
Thank you @JannikBrand

Hi guys,
I'm having the same issue basically. Data-prepper is sending failed traces to stdout and completely messing with my OpenSearch logs since each line is one message in OS.
@dlvenable The preceding line should be "WARN  org.opensearch.dataprepper.plugins.source.oteltrace.OTelTraceGrpcService - Failed to parse request with error 'name cannot be an empty string'. Request body: resource_spans {".
I assume that @iquirino has a similar issue.

I guess you mean something like this?
logger.parser.name = org.opensearch.dataprepper.parser
logger.parser.level = error
Is there another way to handle failing traces, instead of sending them to stdout... sending to a separate index or something like that? Or just delete them.


feat: Add type safety for timeZone parameter

This PR introduces type safety for the timeZone parameter instead of using string as the type. It enhances the developer experience by ensuring that only valid time zone values are accepted and providing better code completion and type-checking support.
Changes Made:

Create a TimeZone type that is a union of all valid time zone values in /use-intl/src/core/utils/TimeZones.tsx
Update the timeZone parameter in these files:

IntlConfig
DateTimeFormatOptions
createFormatter
convertFormatsToIntlMessageFormats

Data Source:
Time zone values sourced from tz database.

All Done and Ready for Review
All CI checks passed! other than the Vercel deployment, which requires an authorized user to approve.
I ran locally and all tests passed.
pnpm build && pnpm lint && pnpm test

Looks great, will be released in a minute!
Are you interested in adopting this in the RSC support branch as well (e.g. i18n.ts)?

It seems like Eslint doesn't have configurations for .tsx files

Also, In the CONTRIBUTORS.md file:

Alternatively, you can run ESLint via the command line:
pnpm eslint src --fix

It should be:
- pnpm eslint src --fix
+ pnpm dlx eslint src --fix

I still propose to include config files for formatting, linting, and settings. In the final It's OPEN-source. Also, in the .gitignore file we should remove .vscode from ignored files.


.NET Framework 4.5+ not supported

With the new SDK, is the plan going forward to not support .NET Framework 4, 4.5+ and to only support .NET Standard?

Yes, we only plan to support .NET 5.0 and above since the SDK has moved to async methods. Since you're running an earlier version of .NET you can make calls directly to the ShipEngine API instead, I'm happy to help out with questions you may have on that

.NET 5 is a SIGNIFICANT upgrade for most large systems.  ASYNC methods have been available to .NET 4 and 4.5 for some time.  Making calls directly to the API can be difficult as that is one more piece of code we maintain. We use and pay for ShipEngine because of the SDK support and integration.

Hey @FenceDad!  We'll be reaching out to setup a call to talk through your questions.

My initial response to this issue had incorrect information. .NET Framework 4.6.1 is the first to support .NET Standard 2.0, so we can only support .NET Framework 4.6.1 and above.
If you want to read more about this, I recommend this article. The tl;dr is that Standard allows us to support a wider range of features for more versions of Framework.


Can not disable hotReload

Hello. I have been looking through the web for something that should be really simple: how to disable hotReload in a standard project that has been initialized with vue-cli.
The only official piece of documentation is here:
https://vue-loader.vuejs.org/guide/hot-reload.html#usage
However, it does not say anywhere where exactly hotReload goes. If I put it into my vue config
in package.json like so:
"vue": {
    "publicPath": "/app/",
    "hotReload": false,

It just tells me that the option hotReload is not allowed.
Another one trying to find a solution:
https://stackoverflow.com/questions/51844289/turn-off-hot-reload-on-project-started-with-vue-cli-3-webpack-4-15-1
This is way too obfuscated.

https://github.com/vuejs/vue-cli/issues/4368#issuecomment-515532738


Usability fixes for Issue #216 - Follower UI

Includes some new responsive changes for phone size of Follower UI.

Found a bug -- for a state-level campaign, if the user puts in an out-of-state address...
Expected behavior: error message only.
Actual behavior: the error message appears below the regular "call now" UI, including rep picture and everything.


“Go to Definition” from inside *.ml library file doesn't work

From a SomeFile.re I can right click -> "Go to Definition" on a standard library function that I use (in this case Format.printf(...)) and it will jump to the definition as I expect (in this case ./node_modules/bs-platform/lib/ocaml/format.ml)
But inside format.ml, "Go to Definition" doesn't work for me. In this case, in format.ml, printf calls fprintf. When I try to "Go to Definition on fprintf, it says "No definition found for fprintf"
Not sure if this a bug / missing feature? Or I simply miss some settings?
TIA

I think this is probably something to do with how the ocaml stdlib is packaged by bs-platform. If you install ocaml through opam, the second jump-to-definition called within format.ml does succeed, and you can keep following back until make_printf in camlinternalFormat.ml.
Can you open an issue about this in the bucklescript repo?

cc @bobzhang @chenglou

I will try to see if I can reproduce it

@freebroccolo I'm happy to open an issue in bucklescript repo too. But since I don't fully understand the (possible) bug, I'd just be copy pasting mostly the same description.
Also I see that @bobzhang is also active in bucklescript repon (maintainer?) and he's going to try reproducing.
Do you think I should still open an issue in bucklescript? I'm affraid I'll just be creating noise.

Can repro. Not sure why. Afaik jump-to-definition requires putting the correct .merlin file at the root of bucklescript's folder (right now bs ships with a wrong one that contains @bobzhang's local paths), but that didn't work either


Fixes #410

Pull Request Checklist

[x] I have added screenshots and videos to show before and after the working of my code.
[x] I have ensured that the screen size is set to 100% while making the video.
[x] I have synced the latest fork with my local repository and resolved any conflicts.
[x] I have mentioned the issue number which I created before making this PR .(format to mention issue number is : fixes #(issue number) )
[x] I understand that if any the above conditions are not met , my PR will not be MERGED .

https://github.com/user-attachments/assets/ee444007-83ff-4a24-b459-e390f31bf07d

fixes #410


flutter analyze --no-fatal-infos still threats @Deprecated as fatal

Steps to reproduce

Add @Deprecated above on of your class in your package
Use the deprecated member somewhere
Call flutter analyze --no-fatal-infos

Expected results
Process should exit with code 0
Actual results
info • '' is deprecated and shouldn't be used.  •
 • deprecated_member_use_from_same_package
Even if it's listed as "info", it still fails with exit code 1.
Code sample
@Deprecated
class Test {
}

main() {
  final test = Test();
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
[✓] Flutter (Channel stable, 3.24.1, on macOS 14.6.1 23G93 darwin-arm64, locale en-CA)
• Flutter version 3.24.1 on channel stable at /Users/fstonge/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 5874a72aa4 (3 weeks ago), 2024-08-20 16:46:00 -0500
• Engine revision c9b9d5780d
• Dart version 3.5.1
• DevTools version 2.37.2
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/fstonge/Library/Android/sdk
• Platform android-34, build-tools 34.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15F31d
• CocoaPods version 1.15.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2024.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
[✓] VS Code (version 1.93.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.96.0
[✓] Connected device (4 available)
• iPhone 15 Pro (mobile)          • 1D88873D-7CD7-458D-B4E3-6D4E10EAD6A2 • ios            •
com.apple.CoreSimulator.SimRuntime.iOS-17-5 (simulator)
• macOS (desktop)                 • macos                                • darwin-arm64   • macOS 14.6.1 23G93 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad                • darwin         • macOS 14.6.1 23G93 darwin-arm64
• Chrome (web)                    • chrome                               • web-javascript • Google Chrome 128.0.6613.120
[✓] Network resources
• All expected network resources are available.
• No issues found!

@frederikstonge
I think this will need to be reported in dedicated repo https://github.com/dart-lang/sdk/issues, as with dart analyze it also shows same info warning.
Closing from here. If you get directed here, write in comments and I'll reopen it.


read_to_string takes a lot of time when payload > 1024 bytes

I'm using hyper to receive githook commit messages and when the payload is longer than 1024 bytes, request.read_to_string() is much much slower than it probably should be (something like a factor 100 on localhost)...
I have created a very simple test case in https://github.com/octplane/githook-client-rust/tree/slow_read_hyper . It's a simple POST upload that triggers the behavior.
I suspect this might be due to the network packets but I'm not sure and I'm certain somebody here will have a much better idea on how to identify the issue :)
Thanks for your time !

Hmm. Hyper is using a BufReader, which by default uses 64kbs. Is it significantly bigger than that?

It is much smaller: 1024 bytes (as indicated by the title of the Issue :wink:  ). And the issue starts getting visible at precisely this value.

Could you try using String::with_capacity(1024) or whichever the size is, and see if that affects things. i'm trying to think where in hyper it might be doing something.

It makes strictly no difference.

@octplane Could you try to profile the code?

Also, would be neat to see actual time values. 1000 bytes can be the size of packet in some cases, so it could just be doing an additional sys call to read the end.

@reem , @seanmonstar I have no idea on how to profile rust code... I'm on OSX, FWIW...

Ok, after some investigation (read the wget logs), I found out that hyper does not conform to some expected parf of the HTTP specification:
`
time curl -vvv -X POST -d @broken.json http://<IP_ADDRESS>:5000/hook/

Hostname was NOT found in DNS cache
Trying <IP_ADDRESS>...
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 5000 (#0)

POST /hook/ HTTP/1.1
User-Agent: curl/7.37.1
Host: <IP_ADDRESS>:5000
Accept: /
Content-Length: 1025
Content-Type: application/x-www-form-urlencoded
Expect: 100-continue

Done waiting for 100-continue
< HTTP/1.1 200 OK
< Transfer-Encoding: chunked
< Date: Wed, 11 Mar 2015 20:41:28 GMT
<
Connection #0 to host <IP_ADDRESS> left intact
OK.curl -vvv -X POST -d @broken.json http://<IP_ADDRESS>:5000/hook/  0,00s user 0,00s system 0% cpu 1,011 total
`

Because the payload is bigger than 1024 bytes, curl attempts a two step posts using the Expect: 100-continue instruction. After 1s, curl gives up and send the payload:
  set->expect_100_timeout = 1000L; /* Wait for a second by default. */
https://github.com/bagder/curl/blob/df5578a7a304a23f9aa3670daff8573ec3ef416f/lib/transfer.c#L1103
Hyper happily receives the payload and call the handler.

Thanks for finding out the real issue! To fix this, I'd imagine adding a check_continue method to the Handler trait, with a default implementation of just writing continue, and checking for an Expect header in the server loop. This allows it to just work, and allows someone to override the behavior if they need to.

@seanmonstar I'm not convinced that hyper should actually handle this vs. downstream users/libraries adding features like this.

@reem according to RFC7231:

An origin server MUST, upon receiving an HTTP/1.1 (or later)
request-line and a complete header section that contains a
100-continue expectation and indicates a request message body will
follow, either send an immediate response with a final status code,
if that status can be determined by examining just the request-line
and header fields, or send an immediate 100 (Continue) response to
encourage the client to send the request's message body.  The origin
server MUST NOT wait for the message body before sending the 100
(Continue) response.

I'm convinced.


Kafka: fix check on autoCommitEnable

Auto commit should occur only if 'autoCommitEnable' is true.

No it should be correct as today as its used when there is connectivity problem and its saving state before re-connecting.
We could maybe improve with a code comment on this or something.

 Is that expected? Sorry if I'm missing something here.

Yes its like if you shutdown the application and want to have kafka offset committed.


Add more message about exclude_engines to CHANGELOG.md

Sorry for late to send this pull-req.
I added an important message to CHANGELOG.md.
why it's needed
I think users using exclude_engine with owned written regexp but currently, exclude_engines will check case-sensitive in strict.
So, maybe users will forget to replace the regexp.

@yuku How about this?

Breaking changes should not included in patch version release, even it is still in version 0.x. There are two ways:

bump it to 0.8.0
fix the breaking change and release 0.7.2

In my opinion, the breaking change was created by accident, so no.2 is better. How do you think?

hmm, I see. I agree with no.2.
if it's okay to no.2, I close this pull-req and create a pull-req as new. @yuku

@sachin21 👍 I'm looking forward to seeing the next PR 😋


Add ability to hide the UV attribute

Missing capability:
It is not currently possible to hide the UV index without turning off all the attributes with "show_attributes: false"
Using "show_sun: false" does not do it either.
Proposed solution:
Add boolean "show_uv" to the list of possible yaml commands and (ideally) this same capability added to the UI.
Update the documentation accordingly.
Tested with version: 2.4.11

This would be a very nice enhancement 🤩

I first thought showing the UV index is a new feature of weather-chart-card, since it suddenly popped up since my last round of updating everything, but seems it might be actually a change in the underlying weather entity (using the default Met.no).
Seems to be rather easy to implement, might have a look myself on the weekend, and create a PR.

Another vote for ability to hide the UV-attribute. It doesn't fit my dashboard-design.


Add support for inverting set options

This patch adds support for inverting set options. For example, in vim, you may use:
:set rnu!

to toggle between :set relativenumber and :set norelativenumber.
I don't see a test case for options so I can't write a test case. I can confirm the following manual tests:
:set rn!               # sets relative number on
:set rn!               # sets relative number off
:set relativenumber!   # sets relative number on
:set relativenumber!   # sets relative number off
:set bc!               # sets blinking cursor on
:set bc!               # sets blinking cursor off
:set clipboard!        # does nothing as `_clipboard` is not a `BOOL`
:set !                 # does nothing

Thank you for the PR. Yea, I need the test cases. You can add XVimTester+Options category if you need. Follow the methods written in existing test case file like XVimTester+Motion.m .

But this doesn't affect motion. It affects changes with the :set method.

So you can create XVimTester+Options.m file .

I understand how XVimTester works, but I don't see it will be useful in this case. Setting options doesn't affect text or cursor position.
I can write a standard XCTest file for this behaviour though, if you would prefer this. However I don't know that this will get run with all the motion tests

Some test cases can be tested like [no]ignorecase. You can write command that searches in case sensitive or incase-sensitive and then put [no]ignorecase then search again. The resulted cursor position can be tested.
For UI related options you don't need to write.

Ok good idea :+1: I'll add that tomorrow.

@JugglerShu I have added a test runner

Please let me ask you one more thing.
Please write a test case for an option that shouldn't take inversion.
This test case should test strcmp([oldValue objCType], @encode(BOOL)) == 0 part.
Any options are fine. Maybe the result is just nothing happen.

I can do, but it seems like a bit of a pointless test. What are you actually wanting to test here?

Yes. With the test we can keep such invalid operation doesn't make crash or anything.

There you go :+1:


Adds 'userId' to 'security' in /me route

Exposes the userId in the me route. This will allow user's to use their userId to query ProjectMembership and User.
Not sure if this is the best place to put it, or if it's needed, but I'm unable to find my current user id. #2126

Hi @taylorqj - Thanks for your submission.
This functionality was just recently included in the update to auth/me.  You can get the user ID now in response.membership.user.reference:

If you're using @medplum/core, you can use resolveId() to extract the ID:
import { resolveId } from '@medplum/core';
const userId = resolveId(response.membership.user);

Apologies for the mixup!  Please let us know if you have any questions.


[Broken] Age verification issues - can't download video.

Checklist

[x] I'm reporting a broken site support
[X] I've verified that I'm running yt-dlp version 2<IP_ADDRESS>
[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

yt-dlp --verbose https://www.youtube.com/watch?v=rR8s72aouNE
[debug] Command-line config: ['--verbose', 'https://www.youtube.com/watch?v=rR8s72aouNE']
[debug] Loading archive file None
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2<IP_ADDRESS> (exe)
[debug] Python version 3.8.8 (CPython 64bit) - Windows-10-10.0.19041-SP0
[debug] exe versions: ffmpeg 2021-03-24-git-a77beea6c8-full_build, ffprobe 2021-03-24-git-a77beea6c8-full_build
[debug] Proxy map: {}
[youtube] rR8s72aouNE: Downloading webpage
[youtube] rR8s72aouNE: Refetching age-gated info webpage
ERROR: Sign in to confirm your age
This video may be inappropriate for some users.
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1026, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1047, in __extract_info
  File "yt_dlp\extractor\common.py", line 558, in extract
  File "yt_dlp\extractor\youtube.py", line 1991, in _real_extract
yt_dlp.utils.ExtractorError: Sign in to confirm your age
This video may be inappropriate for some users.

Description

Hello @pukkandan and thanks for this fork!
I tried to download a video and i got some age verification errors as you can see in the Verbose log above.

When i tried to use --cookies then i got the error below:

yt-dlp --cookies C:/Users/account/Desktop/cookies.txt --verbose https://www.youtube.com/watch?v=rR8s72aouNE
[debug] Command-line config: ['--cookies', 'C:/Users/account/Desktop/cookies.txt', '--verbose', 'https://www.youtube.com/watch?v=rR8s72aouNE']
[debug] Loading archive file None
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2<IP_ADDRESS> (exe)
[debug] Python version 3.8.8 (CPython 64bit) - Windows-10-10.0.19041-SP0
[debug] exe versions: ffmpeg 2021-03-24-git-a77beea6c8-full_build, ffprobe 2021-03-24-git-a77beea6c8-full_build
[debug] Proxy map: {}
[youtube] rR8s72aouNE: Downloading webpage
ERROR: Verify your age
Complete a brief check to show you're old enough to watch this video. Learn more
Traceback (most recent call last):
  File "yt_dlp\YoutubeDL.py", line 1026, in wrapper
  File "yt_dlp\YoutubeDL.py", line 1047, in __extract_info
  File "yt_dlp\extractor\common.py", line 558, in extract
  File "yt_dlp\extractor\youtube.py", line 1991, in _real_extract
yt_dlp.utils.ExtractorError: Verify your age
Complete a brief check to show you're old enough to watch this video. Learn more

I'm signed in to my account and i verified that the cookies are not expired. and of course my date of birth is over 18 years.
I tried youtube-dl as well, but it's the same issue there too.
What is wrong? please help..
Thank you very much.

I can't reproduce.

Can you play the video in browser? If so, do you get that popup first? What is the URL shown in browser after it has started playing?
Also, add a --write-pages to the command and give me the .dump file(s) that are generated.

No, i can't play it in the browser, it still asking for the age verification there too:

I got the dump files, how can i proceed with these?

If you cant play it in browser, I can't do anything. You'll need to verify in browser and export the cookies

No, i can't play it in the browser, it still asking for the age verification there too:

I got the dump files, how can i proceed with these?

try clearing your browser cookies for youtube.
close down / restart you browser and sign back in to youtube
and then retry downloading the video with your cookies file.

@october262 unfortunately did not work, there is an age-restriction in the EU region 😠
I just tried now with a vpn and i was able to play the video in the browser, but when i tried to download the video it failed due to the error in the first verbose log, then i exported the --cookies and tried again (while still on vpn) and i'm able to download, but almost not worth it as the download speed is extremely slow. (maybe the vpn, but i'm not sure).
My main goal was to use dlp to work-around the age-gated webpage to be able to download, but this did not work, and when i provided the cookies i got pushed even deeper down the hole by asking me to verify, now it is impossible to download some age-gated videos without vpn+--cookies
Maybe i'll create an issue @.youtube-dl too and see if somebody can figure something out.


Support for .NET Standard

Currently, it is possible to run this library in compatibility mode for .NET Standard 2.0. It will be nice to port it to .NET Standard to make it cross platform.

Should be doable

Thank you!

implemented in v<IP_ADDRESS> release


Conversion to VS2017

Fix for https://github.com/Azure/azure-sdk-for-net/issues/3362

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@azuresdkci retest this please

@azuresdkci retest this please

sign job: http://azuresdkci.cloudapp.net/view/NetCore-SDK/job/Fluent-NetCore-SDK-Sign/4/

Sign job: http://azuresdkci.cloudapp.net/view/NetCore-SDK/job/Fluent-NetCore-SDK-Sign/5/


How does the InferenceNet iteract with the denoising unet

I can't understand how does the InferenceNet iteract with the denoising unet. In the code, the two modules seem completely seperate from each other, and there is no information exchange happen in the training stage.
Maybe someone kind enough can point out the interaction part of the code for me?
有大佬知道代码中InferenceNet和Denoising Unet是怎么交互的吗，没有看到inferencenet的信息被传递给Denoising Unet..

在 src.models.mutualattention 里面的 referenceattentioncontrol类里面，有update这个方法

By the way, it should be 'interact' but not 'iteract'   (dog head manually)


Bump to pipefunc 0.43.0

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12405213938. Examine the logs at this URL for more detail.

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: passed
rerender called: passed

Thus the PR was passing and merged! Have a great day!


Apply a template to selection?

Is there a way to apply a template to a selection or are the only applicable to the entire file?
Use-case:
I'm working with a very complex variable length file format (not feasible to create a full template for it) and I'd like to be able to select a bunch of bytes and select a template like "Foo Header" so I can see only that header within the file.

Not that i know of. The workaround i've used is the "Attach Template at Offset" in the hex/ascii context menu or copy/paste range into a new window. I thought about if some kind of "sub" templates would be useful but not sure how they would work. Have any ideas?

Have any ideas?

What might be easiest right now would be to add a context menu option when I right-click a selection that allows me to open the selection in a new window ("Open Selection In New Window"?). Then we can just use the current template system.
Moving around the offset works, but is a little cumbersome, so this would just be a shortcut for your second method of copy-paste.

I've adjusted my workflow a little and worked with the "Anchor Template at Offset N" method over the part couple of days. Overall it's alright, but it would be more convenient to have the templates in the context menu so I could just right click at a position and set the template directly.
If people have dozens of templates this might cause a problem with a long menu, so maybe the menus (in the context menu and the one on the right) could mimic the folder structure under "Templates". Then I could have a separate folder (e.g. "Templates/[my file format name]") for all my "partial" templates.
Updated Workflow Suggestion:

right-click at a position
new context menu item Apply Template contains the templates in "Templates" as sub-menus (mimics folder structure)
choose the template I want
the Template menu on the right is updated and the template is applied


[WFLY-3045] : Expose JAXRS deployments via the management API

Displaying JAXRS resources in deployments, showing paths and  methods.
Adding mappings to the deployment infos of servlets.
Jira: https://issues.jboss.org/browse/WFLY-3045

retest this please

Linux Build 5914 is now running using a merge of 0bd75a263278796854bc01cb8887cf2ed40bc3fd

Linux with security manager Build 893 is now running using a merge of 0bd75a263278796854bc01cb8887cf2ed40bc3fd

Windows Build 1024 is now running using a merge of 0bd75a263278796854bc01cb8887cf2ed40bc3fd

Linux with security manager Build 893 outcome was SUCCESS using a merge of 0bd75a263278796854bc01cb8887cf2ed40bc3fd
Summary: Tests passed: 788, ignored: 369 Build time: 0:05:19

Windows Build 1024 outcome was SUCCESS using a merge of 8c21385efaa307b71c46b02e7bfe399a804b069e
Summary: Tests passed: 2909, ignored: 364 Build time: 0:49:10

Linux Build 5914 outcome was SUCCESS using a merge of 8c21385efaa307b71c46b02e7bfe399a804b069e
Summary: Tests passed: 2909, ignored: 364 Build time: 0:52:31

Linux with security manager Build 894 is now running using a merge of 8c21385efaa307b71c46b02e7bfe399a804b069e

Linux Build 5915 is now running using a merge of 8c21385efaa307b71c46b02e7bfe399a804b069e

Windows Build 1025 is now running using a merge of 8c21385efaa307b71c46b02e7bfe399a804b069e

Linux with security manager Build 894 outcome was SUCCESS using a merge of 8c21385efaa307b71c46b02e7bfe399a804b069e
Summary: Tests passed: 838, ignored: 317 Build time: 0:05:00

Windows Build 1025 outcome was SUCCESS using a merge of 8c21385efaa307b71c46b02e7bfe399a804b069e
Summary: Tests passed: 2927, ignored: 313 Build time: 0:46:36

Linux Build 5915 outcome was SUCCESS using a merge of 8c21385efaa307b71c46b02e7bfe399a804b069e
Summary: Tests passed: 2926, ignored: 313, muted: 1 Build time: 0:48:50

Linux with security manager Build 900 is now running using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5

Linux Build 5921 is now running using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5

Windows Build 1031 is now running using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5

Linux with security manager Build 900 outcome was SUCCESS using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5
Summary: Tests passed: 838, ignored: 317 Build time: 0:05:03

Windows Build 1031 outcome was SUCCESS using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5
Summary: Tests passed: 2927, ignored: 313 Build time: 0:46:25

Linux Build 5921 outcome was FAILURE using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5
Summary: Tests failed: 1 (1 new), passed: 2925, ignored: 313, muted: 1 Build time: 0:47:45
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize: javax.ejb.EJBException: java.lang.IllegalStateException: WFLYCLEJBINF0008: Stateful session bean {[28, -71, -33, 111, -35, -14, 75, -14, -96, 109, 115, -19, 25, 124, -18, 22]} refers to an invalid bean group 9d857f01-ade1-4ae0-8aa7-b3eeae89eb14
	at org.wildfly.clustering.ejb.infinispan.bean.InfinispanBeanFactory.createBean(InfinispanBeanFactory.java:76)
	at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.findBean(InfinispanBeanManager.java:266)

retest this please

Linux with security manager Build 922 is now running using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5

Linux Build 5943 is now running using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5

Windows Build 1053 is now running using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5

Linux with security manager Build 922 outcome was FAILURE using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5
Summary: Tests failed: 1 (1 new), passed: 839, ignored: 319 Build time: 0:06:31
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.smoke.webservices.WSTestCase.testManagementDescriptionMetrics: java.lang.AssertionError: null
	at org.junit.Assert.fail(Assert.java:86)
	at org.junit.Assert.assertTrue(Assert.java:41)

Windows Build 1053 outcome was SUCCESS using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5
Summary: Tests passed: 2930, ignored: 313 Build time: 0:47:27

Linux Build 5943 outcome was SUCCESS using a merge of 22995bcf2427be8b0f180a99a3b865add60ebfc5
Summary: Tests passed: 2930, ignored: 313 Build time: 0:47:49

Linux with security manager Build 1298 is now running using a merge of 3bdca67d5a3e969c0c1bb8493ad0f5ec3e7e474f

Windows Build 1450 is now running using a merge of 3bdca67d5a3e969c0c1bb8493ad0f5ec3e7e474f

Linux Build 6370 is now running using a merge of 3bdca67d5a3e969c0c1bb8493ad0f5ec3e7e474f

Linux with security manager Build 1298 outcome was SUCCESS using a merge of 3bdca67d5a3e969c0c1bb8493ad0f5ec3e7e474f
Summary: Tests passed: 826, ignored: 358 Build time: 0:06:23

Windows Build 1450 outcome was SUCCESS using a merge of 3bdca67d5a3e969c0c1bb8493ad0f5ec3e7e474f
Summary: Tests passed: 2862, ignored: 414 Build time: 0:47:12

Linux Build 6370 outcome was SUCCESS using a merge of 3bdca67d5a3e969c0c1bb8493ad0f5ec3e7e474f
Summary: Tests passed: 2861, ignored: 414, muted: 1 Build time: 0:50:04


Only re-sync the Supervisor / Database for material changes

Sometimes, the API component of the supervisor makes immaterial changes (i.e. renames, annotation) to the database that Supervisor doesn't need to resync on.
Update the API layer to only poke the supervisor for important data changes.

#75 makes this irrelevant, since all changes are material.


duffle build bug

"invocationImages": {
        "directory-name": {
            "name": "image-name",
            "builder": "docker",
            "configuration": {
                "registry": "chzbrgr71"
            }
        }
    }

when directory-name is different from image-name, you'll get an error like: ````Error: cannot prepare build: could not find an invocation image for image-name``` bc it is not looking for the directory name correctly.
discovered by Brian Redmond and Joey Schluchter. Thanks!

Since this bug was raised,invocationImages changed to be an array, so I think the bug is no longer reproducible. Please re-open if there is still a bug.


Introduce Pseudo Type System?

VBS has no type System, however sometimes it is well known what a function or variable holds.
I use this syntax on my own:
Dim str ' as String ' Comment
Maybe such a comment based As Type approach could be used to fake a typesystem like typescript is doing it for javascript.
However the comments have to be parsed stricter and an comment like
dim refObject ' as already used above whould create and return type of already

Maybe using something like String_t (similar from C and his uint16_t etc.).
The parser can then match first world toward list of types and ideally remove the _t.

Maybe using something like String_t (similar from C and his uint16_t etc.).
The parser can then match first world toward list of types and ideally remove the _t.

Hm, i don't think that would be very intuitive to any VB developer, but it would indeed prevent from accidentally using normal comments as type

Thinking the damage cause by accidentally used comments as Types is insignificant.
The  ' as Type, sounds familiar to a VB developer and would work for

[x] Functions
[x] Get Propertys
[x] Dim/Public/Private/Consts

Don't work
For those things the idea won't work:
Function/Sub Parameters
Function myFunc(p1 ' as String, p2 ' As Integer
Maybe this isn't bad, because there is no benefit beyond documentation purpose
Splitting the Function into multiple lines and comment each parameter would be idea, but I think there is no valid syntax for that??
If the extension grows so far the a error checking is doing a strict type check, like typescript for javascript, this could become useful.
An alternative approach would be to use xml comments for those
''' <param name="p1" type="string">Description</param
Function with different return types
CreateObject or GetObject could not use this typesystem. But the developer could declare a variable which states the awaited type dim fso ' as Scripting.FilesystemObject. But i think in this case the string in createobject should be the type
Set/Let Property
The parameter has the same problem like in subs/functions, but it could be inconsequentially be used as
Property Let Text(val) ' as String
Enums
Enums aren't supported by VBS, but they would be helpful for many parameters like MsgBox Constants or String Compare Options.
Have no good idea, and don't like any approach:
' Enum MsgBoxContantCom = Array(vbOK, vbYesNo)

Const Enum_MsgBoxConstants = "vbOK, vbYesNo"

dim MsgBoxConstantsVar : MsgBoxConstantsVar = Array(vbOK, vbYesNo) ' as Enum

Class Enum_MsgBoxConstants
    Public vbOK
    Public vbYesNo
End Class

Function Enum_MsgBoxConstantsFunc() ' As Enum
    Enum_MsgBoxConstantsFunc = Array(vbOK, vbYesNo)
End Function

For the functions I think that using ''' <param name="p1" type="string">Description</param> is pretty OK. Even write the type directly in to the description. I would not overcomplicate this :)


fix typo:highter

What is the purpose of the change
fix #1662
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.06%) to 50.671% when pulling 943a3d2730a133260a1f927d2988ea7140a28a92 on LiosWong:master into d1b4e47c26576cf4fa543bbdd8c6f09643220bed on apache:master.

@LiosWong could you pull this request to develop branch?

@LiosWong could you pull this request to develop branch?

OK


sentry-cli: 2.5.2 -> 2.7.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/getsentry/sentry-cli/releases.
meta.description for sentry-cli is: "A command line utility to work with Sentry"
meta.homepage for sentry-cli is: "https://docs.sentry.io/cli/"
meta.changelog for sentry-cli is: "https://github.com/getsentry/sentry-cli/raw/2.6.0/CHANGELOG.md"
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.6.0 with grep in /nix/store/jk2nix09r3rzx0bzd3k6l0g1bwkxxsxy-sentry-cli-2.6.0
found 2.6.0 in filename of file in /nix/store/jk2nix09r3rzx0bzd3k6l0g1bwkxxsxy-sentry-cli-2.6.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sentry-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jk2nix09r3rzx0bzd3k6l0g1bwkxxsxy-sentry-cli-2.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sentry-cli https://github.com/r-ryantm/nixpkgs/archive/c098fc4b9e456533d68bf275ee8d61ea3e3fc663.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jk2nix09r3rzx0bzd3k6l0g1bwkxxsxy-sentry-cli-2.6.0
ls -la /nix/store/jk2nix09r3rzx0bzd3k6l0g1bwkxxsxy-sentry-cli-2.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

sentry-cli

Maintainer pings
cc @Rizary for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/getsentry/sentry-cli/releases.
meta.description for sentry-cli is: "A command line utility to work with Sentry"
meta.homepage for sentry-cli is: "https://docs.sentry.io/cli/"
meta.changelog for sentry-cli is: "https://github.com/getsentry/sentry-cli/raw/2.7.0/CHANGELOG.md"
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.7.0 with grep in /nix/store/kra25sq0qfx1m621k0081kcg0229fj8a-sentry-cli-2.7.0
found 2.7.0 in filename of file in /nix/store/kra25sq0qfx1m621k0081kcg0229fj8a-sentry-cli-2.7.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sentry-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kra25sq0qfx1m621k0081kcg0229fj8a-sentry-cli-2.7.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sentry-cli https://github.com/r-ryantm/nixpkgs/archive/9c61eadd1d007296ae34f0f973ec3cf57c771d2a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kra25sq0qfx1m621k0081kcg0229fj8a-sentry-cli-2.7.0
ls -la /nix/store/kra25sq0qfx1m621k0081kcg0229fj8a-sentry-cli-2.7.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

sentry-cli

Maintainer pings
cc @Rizary for testing.


Introduce LRU cache

Summary
Various enhancements would be easier if we had this one of these.
Use Cases

Memoization TTL (#3593)
Memoization storage (#3587)
SSO (#4027)
Node output storage (#3589)

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Closing this. I think we can now investigate more specific solutions.