Set default serialization arguments

Initial Checks

[X] I have searched Google & GitHub for similar requests and couldn't find anything
[X] I have read and followed the docs and still think this feature is missing

Description
Short Summary
I think providing a way to set the default arguments for serialisation methods (model_dump, model_dump_json`) would make multiple use-cases more robust.
Context
Pydantic's model_dump and model_dump_json provide many valuable arguments when serialising.
All of those keywords arguments are here to enable a behaviour that you might or might not need. However, in my experience, if I need this behaviour once, I need it (almost) everywhere. I find that things like by_alias, exclude_none, ... are often tightly coupled with the design and constraints of your model through your entire project/application.
This leads me to be worried that I might have a complicated bug to spot if I use, let's say, by_alias=True everywhere, but forget it in one occurence.
When dealing with one model, it's possible to keep track. But in project where, let's say, your API should always hide default values in responses, the explicit exclude_defaults=True call can add up over every single one of your models.
Note: not all arguments make sense for this, for instance exclude can be set on the fields themselves
Solution
My favourite solution in this situation would be to indicate the default behaviour on the model itself. I still have the flexibility to decide on a call by call basis, but I'm confident that if I (or another developper) just use model_dump(), it will follow the behaviour that fits my model's design and requirements.
Example In House Implementation
To be fair, this is completely possible to do without upstream changes. Here's an example of code for a specific argument
class CamelCaseModel(pydantic.BaseModel):
    model_config = pydantic.ConfigDict(alias_generator=to_camel,  populate_by_name=True)

    def model_dump(self, **kwargs: Any) -> dict[str, Any]:
        kwargs.setdefault("by_alias", True)
        return super().model_dump(**kwargs)

    def model_dump_json(self, **kwargs: Any) -> str:
        kwargs.setdefault("by_alias", True)
        return super().model_dump_json(**kwargs)

Here, by_alias will be set on every call, except if I know what I'm doing and provide an explicit value.
Example Interface
If a solution was supported upstream, we could just use an interface like this one:
class CamelCaseModel(pydantic.BaseModel):
    model_config = {
        "alias_generator": to_camel,
        "populate_by_name": True,
        "dump_defaults": { "by_alias": True }  # Maybe "serialization_defaults"
    }

Do we need this upstream?
I think the reason I would like this in pydantic is

I think it's very useful and would make the API nicer
Serialization is a key element of pydantic, while I find
I don't like having to edit they key methods in a shared base class

There can be potential issues with multiple inheritance (e.g. ExcludeNoneModel & CamelCaseModel)
It hides completion

Some features like exclude already have an interface to be defined on model definition, showing that there's sometimes a need (at least for the exclude argument) to ensure a consistent behaviour on all serializations

I think this would also be a (nice) solution to https://github.com/pydantic/pydantic/issues/8551, which as mentioned in https://github.com/pydantic/pydantic/issues/8551#issuecomment-1892571228 is solved by consistently using by_alias
Implementation Difficulty
I believe this shouldn't be too difficult to implement.
I think the implementation can require some thoughts (for instance, use by_alias: bool | None = None) when coded directly on the base model.
Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[X] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Thanks for the well written feature request. While I understand the added value of having defaults set at the model_config level (this makes me think of the layered architecture available in Litestar), I have one concern (as you mentioned with by_alias) related to the signature of the model_dump(_json) functions, that would become:
def model_dump(
    self,
    *,
    ...,
    by_alias: bool | None = None,  # was `: bool = False` before. Now there's no way to easily remember the default value from the signature.
    ...,
) -> dict[str, Any]:

Due to the current implementation (serialization is on the pydantic-core) I also expect some work for this to happen. My take is we should probably wait for some upvotes before implementing this, considering the possibly added complexity and maintenance.

I also expect some work for this to happen. My take is we should probably wait for some upvotes before implementing this, considering the possibly added complexity and maintenance.

I agree with @Viicos here - given that there is a way for you to set default serialization settings by overriding model_dump or similar functions, I think this will be low priority given the additional maintenance burden it introduces.
That being said, I think there are some common serialization settings, like by_alias, that we plan to introduce explicit config settings for in v3, given demand, see https://github.com/pydantic/pydantic/issues/8379.
Thanks for your well thought out feature request - we very much appreciate the detail and organization.


I have a setup issues on the cmd

~FileRecv\MobileFile\SPlisHSPlasH-master\SPlisHSPlasH-master>python setup.py bdist_wheel
Traceback (most recent call last):
File "C:\Users\79422\Documents\Tencent Files\794224124\FileRecv\MobileFile\SPlisHSPlasH-master\SPlisHSPlasH-master\setup.py", line 116, in
long_description = f.read()
UnicodeDecodeError: 'gbk' codec can't decode byte 0x93 in position 8733: illegal multibyte sequence
I have setup Cmake ,Git and Windows powershell already.Thanks for your help.

I  never had this problem but you could try to comment out lines 115 and 116 and set:
long_description = ''


could not complete authentication: Error: Unauthorized (401) - IE Browser Windows 7

Hi Folks,
I am facing the issue could not complete the authentication Error Unauthorized (401) in IE browser WIN 7 OS.
The IE browser version is Edge.
The 401 error occurs in the URL (protocol/openid-connect/userinfo).
This also occurs when the page is loading in the frame. Its working as expected in Chrome Browser.
Any help should be appreciated.  Thanks.
Error description

could not complete authentication: Error: Unauthorized (401)
ERROR Error: Uncaught (in promise): TypeError: Unable to get property 'profile' of undefined or null reference
TypeError: Unable to get property 'profile' of undefined or null reference
  name: "Error",
  promise: { },
  rejection: { },
  stack: "Error: Uncaught (in promise): TypeError: Unable to get property 'profile' of undefined or null reference

TypeError: Unable to get property 'profile' of undefined or null reference
Symbol(rxSubscriber)_g.jkkwfb4zea8: undefined,
task: { },
zone: { }

Sorry, not sure. Were you able to debug further or find anything else?


feat add session var to turn on/off common sub expressoin extraction

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run p0

run p0


Improve dockerfile

1.) Changed the parent docker image to buster slim (still debian based but a lot more slimmer)
2.) Added a separate flashbot user (for security), it doesn't run as the root user.
The resulting docker image is half the size of the original one, which will come in handy with the CI/CD stuff.
I'm not sure how you handle the CI/CD part, I didn't find any build info (I guess for now you use git pull or something like that)
Tom

Did some tests locally and all looks good!
Only comment is those emojis :)
Then good to go!

Merged - thanks @tmikulin !!

np @lukevs


Moeten we nog advisory board sessions plannen voor prototype testing?

Answer: it could be useful and desirable to ask one or two members pf the advisory board to test the app for bugs (probably after March).

[ ] Test the procedure of the trial with the advisory board? And maybe sensor testing too?

[ ] Vragen: waar zou je nog meer uitleg over willen ontvangen?


Unallocated int becomes nil in switch()

The following code will return nil rather than 0:
#include <type.h>

mixed test()
{
	int x;
	switch (2) {
		case 1:
			x = 42;
			break;

		default:
			return x;
	}
}

The code is pretty self-demonstrating for when this happens: a local int never uninitialized, the program goes into a switch() statement that has some case which initializes it, but goes down a later case statement which uses it uninitialized.
The expectation is that it should return 0, which it does if it's ever assigned (even to 0), if the assignment x = 42; is removed, or even if the case 1: and default: code segments are swapped.
Even though this bug seems very specific when it occurs, x doesn't have to be returned to have a nil value. In my local purpose for this code pattern, I was using it to make an array, and was confused why I was getting nil values.

Ugh, I'm bad at browser tabs, this was meant for the dgd repository. Sorry!


Add JSON Serialization/Deserialization

Hi, was this proposal previously discussed somewhere?

Hi, was this proposal previously discussed somewhere?

No, not really. Why?

A straight-forward implementation of serialization in D is not too difficult and there are quite a few implementations in D already, whether on top of std.json or as part of serialization libraries. I think the main difficulty with adding this (and anything else) to the standard library is coming up with a set of decisions to guide implementations which are the least disagreeable to everyone (for instance in your proposal I can see the argument about whether @jsonField is needed at all, or if the interface needs to be generalized to support other serialization formats). D developers who have implemented serialization frameworks will also be happy to talk about issues emerging from real-world use of such libraries, such as const/immutable data types and the emergent approaches to construct vs. populate D values, the need for partial (de)serialization, and transformations (defined in the type or at the top-level (de)serialization call).
I think the most recent attempt to study and overcome these questions was by @FeepingCreature. I'm not sure, was there a DConf talk about it?
So, on one hand, "The Best is the Enemy of Good", and on the other hand, there is e.g. std.sumtype which was initially published as a Dub package, and only after being proven by real-world use it was submitted for inclusion to Phobos.

I have a dconf talk about my serialization lib here. Though it's a bit specialcase because we rely on boilerplate to query a canonical list of constructor parameters for every datatype, and also we really want separation of type definition and encoding definition for ideological reasons. :)

A straight-forward implementation of serialization in D is not too difficult and there are quite a few implementations in D already, whether on top of std.json or as part of serialization libraries. I think the main difficulty with adding this (and anything else) to the standard library is coming up with a set of decisions to guide implementations which are the least disagreeable to everyone (for instance in your proposal I can see the argument about whether @jsonField is needed at all, or if the interface needs to be generalized to support other serialization formats). D developers who have implemented serialization frameworks will also be happy to talk about issues emerging from real-world use of such libraries, such as const/immutable data types and the emergent approaches to construct vs. populate D values, the need for partial (de)serialization, and transformations (defined in the type or at the top-level (de)serialization call).
I think the most recent attempt to study and overcome these questions was by @FeepingCreature. I'm not sure, was there a DConf talk about it?
So, on one hand, "The Best is the Enemy of Good", and on the other hand, there is e.g. std.sumtype which was initially published as a Dub package, and only after being proven by real-world use it was submitted for inclusion to Phobos.

I have literally no idea what to do with this information, or how to respond to it ¯_(ツ)_/¯

Well, ultimately the authoritative decision of what can get added to Phobos is done by @atilaneves.
I am not him, but I think the path forward here would be to discuss this with the community on the forum, maybe put this as a Dub package which extends std.json so people can try it out, and if there's community consensus that this is a good direction to go forward in then submit it for inclusion and review.

One suggestion might be to have serialisation UDAs be a generic thing separate to std.json, that way libraries can standardize on them a little

One suggestion might be to have serialisation UDAs be a generic thing separate to std.json, that way libraries can standardize on them a little

This would simplify dependencies for a few of my libraries. I'm definitely in favour of that.

Well, ultimately the authoritative decision of what can get added to Phobos is done by @atilaneves.
I am not him, but I think the path forward here would be to discuss this with the community on the forum, maybe put this as a Dub package which extends std.json so people can try it out, and if there's community consensus that this is a good direction to go forward in then submit it for inclusion and review.

Realistically, if you exclude unittests and private convenience code, this is about a 100 LOC change. 100 LOCs don't feel worthy of having a discussion in the first place

One suggestion might be to have serialisation UDAs be a generic thing separate to std.json, that way libraries can standardize on them a little

This would require designing std.serialization, which goes far beyound what my intentions are with this code, This considerably small change makes std.json a lot more usable for a little cost. Even if std.serialization comes to be, this code can be easily adjusted to use new UDAs, and these ones can be easily deprecated

So what do I need to do from here? Community post? Extract this into std.serialization?

So what do I need to do from here? Community post?

Yes, a forum thread is a good way to get more feedback.

Realistically, if you exclude unittests and private convenience code, this is about a 100 LOC change. 100 LOCs don't feel worthy of having a discussion in the first place

On one extreme we have very large additions that need a lot of effort to be scrutinized from all sides. On the other extreme, we have proposals for trivial additions - one-liners, small helper functions, etc., these are also rejected on the basis of being too trivial.

Even if std.serialization comes to be, this code can be easily adjusted to use new UDAs, and these ones can be easily deprecated

On the topic of why not just add things now and deprecate them later if they turn out to be suboptimal or a bad idea, this doesn't work in all cases. For a current example right in std.json, see<EMAIL_ADDRESS>In this submission, I see e.g. that it would be difficult to deprecate the @jsonField UDA (and instead serialize everything like ae.utils.json / vibe.data.json) - it would have to be deprecated as a three-step process, first deprecating it and introducing something like @jsonAll, then removing @jsonField and deprecating @jsonAll, then finally removing @jsonAll.

I think I will be closing this for now. I'll report to the forums once I rewrite this into std.serialization


Java Code Formatter

Problem
I was working on a Java ticket these days, and found that the format of our java codebase sometime is not consistent.
Therefore, I am trying to propose a Java formatter for the team.
Persona:
Which persona is this feature for?
Knative developers
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.

The formatter is easy to use for developers
The CI tests should be configured as well.
https://github.com/knative-sandbox/eventing-kafka-broker/blob/93b0ecb56d9550f7cff6f0089073e935fe2a3cd3/hack/update-codegen.sh#L80-L83

Time Estimate (optional):
1
Additional context (optional)
The fotmatter I am proposing is called Spotless.
The Pros for choosing Spotless:

Just run mvn spotless:apply does magic
It is widely used, and actively been maintained!
Can be integrated with CI testing
It supports many different formatting policy (google java style, eclipse jdt...)
Support with IntelliJ IDEA and VSCode

@debasishbsws this will help us for formatting Java code, if you have got opinions and thoughts on this, feel free to comment, like if the proposed tool would work for you, etc

I think it will be a good idea to have a formatter.
I know about checkstyle that is a linting tool for java, but it doesn't work as a formatter ig.
Spotless looks like a cool to work with.


Echos Protocol Version, Even When Not Supported

Currently in VncClient::frb_wait_for_version(), it simply echos the protocol version, even when it's unrecognized / not supported.
For example, the current version of RealVNC uses RFB 004.001. Thus far, this protocol hasn't been published (and I've heard that as of 2012, RFB 004.yyy won't have the protocol publicly released like the RFB 003.yyy series was.) Simply returning RFB 004.001 doesn't work, because the server never sends anything after the client sends ClientInit - most likely in this new version ClientInit requires something more to be sent than in prior versions.
As a work around, I have a few lines in VncClient::frb_wait_for_version() commented out and replaced with this:
write("RFB 003.008\n");
_proto_hi_version = 3;
_proto_lo_version = 8;
A better solution would be to check what you're given, and if it's recognized, echo that, and if it's not, echo RFB 003.008\n. (If I get around to doing this myself, I'll make a pull request.)

here's my version of the else block:
else
      {
        char version_hi[] = { r[4] != '0' ? r[4] : (r[5] != '0' ? r[5] : r[6]), 0 };
        char version_lo[] = { r[8] != '0' ? r[8] : (r[9] != '0' ? r[9] : r[10]), 0 };

        _proto_hi_version = atoi(version_hi);
        _proto_lo_version = atoi(version_lo);

        if (_proto_hi_version > 3 || (_proto_hi_version == 3 && _proto_lo_version > 8))
        {
          //respond with 3.8
          _proto_hi_version = 3;
          _proto_lo_version = 8;
          std::string version = "RFB 003.008";
          write(&*version.begin(), &*version.begin() + 12);
        }
        else
        {
          // Simply respond with the same protocol version as we've got from server.
          write(&*r.begin(), &*r.begin() + 12);
        }

        eat(12);

        if (_proto_hi_version == 3 && _proto_lo_version < 7)
          _state = vnc_waiting_for_security_server;
        else
          _state = vnc_waiting_for_security_handshake;
      }


Faster Docker dev environment

Description
Using Nix to handle the dependencies of the project during the build. This means dependencies can be cached in a volume to generate the final image a lot quicker, by rebuilding only the dependencies (including crates) that have been changed. Potentially, we can cache these dependencies in a cache server so builds from scratch will download pre-built binaries from cachix (Nix's cache server).
The heart of the image is this block of code:
          baseImage = final.dockerTools.buildLayeredImage {
            name = "many-base";
            contents = [
              final.bash
              final.curl
              final.iputils
            ];
          };

          dockerImageFromPkg = pkg: name: final.dockerTools.buildLayeredImage {
            fromImage = final.baseImage;
            name = "many/${name}";
            tag = "latest";
            contents = [
              (pkg {}).bin
            ];
            created = "now";
            config.Cmd = [ "${(pkg {}).bin}/bin/${name}" ];
          };

This block creates a base image with some useful packages, and for package pkg it creates an image, based on the base image, containing the binary generated by the package.
Related Issue
Fixes #206
Testing
Manually tested running make start-nodes and other make targets.
Checklist:

[X] I have read and followed the CONTRIBUTING guidelines for this project.
[X] I have added or updated tests and they pass.
[X] I have added or updated documentation and it is accurate.
[X] I have noted any breaking changes in this module or downstream modules.

Codecov Report

Merging #209 (32e577c) into main (cff0cf1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #209   +/-   ##
=======================================
  Coverage   71.15%   71.15%
=======================================
  Files          32       32
  Lines        6067     6067
=======================================
  Hits         4317     4317
  Misses       1750     1750

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Update module github.com/influxdata/influxdb to v9

This PR contains the following updates:

Package
Type
Update
Change

github.com/influxdata/influxdb
require
major
v1.8.4 -> v9.9.9

Release Notes

influxdata/influxdb
v9.9.9
Compare Source
v2.0.4
Compare Source
Docker
ARM64
This release extends the Docker builds hosted in quay.io to support the linux/arm64 platform.
2.x nightly images
Prior to this release, competing nightly builds caused the nightly Docker tag to contain outdated
binaries. This conflict has been fixed, and the image tagged with nightly will now contain 2.x
binaries built from the HEAD of the master branch.
Breaking Changes
inmem index option removed
This release fully removes the inmem indexing option, along with the associated config options:

max-series-per-database
max-values-per-tag

Replacement tsi1 indexes will be automatically generated on startup for shards that need it.
Artifact naming conventions
The names of artifacts produced by our nightly & release builds have been updated according to the
Google developer guidelines. Underscores (_) have
been replaced by hyphens (-) in nearly all cases; the one exception is the use of x86_64 in our
RPM packages, which has been left unchanged.
Features

20473: Add --overwrite-existing-v2 flag to influxd upgrade to overwrite existing files at output paths (instead of aborting).
20524: Add influxd print-config command to support automated config inspection.
20561: Add nats-port config option for influxd server.
20564: Add nats-max-payload-bytes config option for influxd server.
20467: Add influxd inspect export-lp command to extract data in line-protocol format.
20604: Update telegraf plugins list in UI to include Beat, Intel PowerStats, and Rienmann.
20634: Promote schema and fill query optimizations to default behavior.
20678: Upgrade Flux to v0.104.0
20680: UI: Upgrade flux-lsp-browser to v0.5.31

Bug Fixes

20339: Include upgrade helper script in goreleaser manifest.
20348: Don't show the upgrade notice on fresh influxdb2 installs.
20348: Ensure config.toml is initialized on fresh influxdb2 installs.
20349: Ensure influxdb service sees default env variables when running under init.d.
20317: Don't ignore failures to set password during initial user onboarding.
20362: Don't overwrite stack name/description on influx stack update.
20355: Fix timeout setup for influxd graceful shutdown.
20387: Improve error message shown when influx CLI can't find an org by name.
20380: Remove duplication from task error messages.
20313: Automatically build tsi1 indexes for shards that need it instead of falling back to inmem.
20313: Fix logging initialization for storage engine.
20442: Don't return 500 codes for partial write failures.
20440: Add confirmation step w/ file sizes before copying data files in influxd upgrade.
20409: Improve messages in DBRP API validation errors.
20489: Improve error message when opening BoltDB with unsupported file system options.
20490: Fix silent failure to register CLI args as required.
20522: Fix loading config when INFLUXD_CONFIG_PATH points to a .yml file.
20527: Don't leak .tmp files while backing up shards.
20527: Allow backups to complete while a snapshot is in progress.
20539: Prevent extra output row from GROUP BY crossing DST boundary.
20548: Prevent panic in influxd upgrade when V1 users exist and no V1 config is given.
20565: Set correct Content-Type on v1 query responses.
20565: Update V1 API spec to document all valid Accept headers and matching Content-Types.
20578: Respect the --skip-verify flag when running influx query.
20495: Update Flux functions list in UI to reflect that v1 package was renamed to schema.
20669: Remove blank lines from payloads sent by influx write.
20657: Allow for creating users without initial passwords in influx user create.
20679: Fix incorrect "bucket not found" errors when passing --bucket-id to influx write.
20702: Fix loading config when INFLUXD_CONFIG_PATH points to a directory with . in its name.
20678: Fix infinite loop in Flux parser caused by invalid array expressions.
20360: Update API spec to document Flux dictionary features.

v2.0.3
Compare Source
ARM Support
This release includes our initial ARM64 preview build.
Breaking Changes
influxd upgrade
Previously, influxd upgrade would attempt to write upgraded config.toml files into the same directory as the source
influxdb.conf file. If this failed, a warning would be logged and config.toml would be written into the HOME directory.
This release breaks this behavior in two ways:

By default, config.toml is now written into the same directory as the Bolt DB and engine files (~/.influxdbv2/)
If writing upgraded config fails, the upgrade process exits with an error instead of falling back to the HOME directory

Users can use the new --v2-config-path option to override the output path for upgraded config if they can't or don't
want to use the default.
v2 packaging
Based on community feedback, the v2 deb and rpm packaging has been improved to avoid confusion between versions. The package
name is now influxdb2 and conflicts with any previous influxdb package (including initial 2.0.0, 2.0.1, and 2.0.2 packages).
Additionally, v2 specific path defaults are now defined and helper scripts are provided for influxd upgrade and cleanup cases.
Features

20123: Allow password to be specified as a CLI option in influx v1 auth create.
20123: Allow password to be specified as a CLI option in influx v1 auth set-password.
20110: Allow for users to specify where V2 config should be written in influxd upgrade.
20204: Improve ID-related error messages for influx v1 dbrp commands.
20236: Delete with predicate.
20322: Upgrade Flux to v0.99.0.
20327: Upgrade flux-lsp-browser to v0.5.26.

Bug Fixes

20110: Use V2 directory for default V2 config path in influxd upgrade.
20137: Fix panic when writing a point with 100 tags. Thanks @foobar!
20151: Don't log bodies of V1 write requests.
20097: Ensure Index.Walk fetches matching foreign keys only.
20149: Enforce max value of 2147483 on query concurrency to avoid startup panic.
20149: Enforce max value of 2147483 on query queue size to avoid startup panic.
20168: Auto-migrate existing DBRP mappings from old schema to avoid panic.
20201: Optimize shard lookup in groups containing only one shard. Thanks @StoneYunZhao!
20155: Respect the --name option in influx setup whether configs already exist or not.
20155: Allow for 0 (infinite) values for --retention in influx setup.
20305: Set v2 default paths and provide upgrade helper scripts in release packages

v2.0.2
Compare Source
Features

19979: Added functionality to filter task runs by time.
20036: Warn if V1 users are upgraded, but V1 auth wasn't enabled.
20039: Export 1.x CQs as part of influxd upgrade.
20053: Upgrade Flux to v0.95.0.
20058: UI: Upgrade flux-lsp-browser to v0.5.23.
20067: Add DBRP cli commands as influxd v1 dbrp.

Bug Fixes

19987: Fix various typos. Thanks @kumakichi!
19991: Use --skip-verify flag for backup/restore CLI command.
19995: Don't auto-print help on influxd errors
20008: Add locking during TSI iterator creation.
20012: Validate input paths to influxd upgrade up-front.
20015: Add same site strict flag to session cookie.
20017: Don't include duplicates for SHOW DATABASES
20064: Ensure Flux reads across all shards.
20047: Allow scraper to ignore insecure certificates on a target. Thanks @cmackenzie1!
20076: Remove internal influxd upgrade subcommands from help text.
20074: Use default DBRP mapping on V1 write when no RP is specified.
20091: Make the DBRP http API match the swagger spec.

v2.0.1
Compare Source
Bug Fixes

19918: Swagger: add operationId to /delete
19967: Upgrade: add log-level option
19969: Check for existing 2.x CLI configs file
19971: Swagger: remove Invites from swagger
19972: Remove obsolete unused option (influx-command-path)
19980: check write permission in legacy write path

v2.0.0
Compare Source
Features

19935: Improve the UI for the influx v1 auth commands
19940: Update Flux to v0.94.0
19943: Upgrade flux-lsp-browser to v0.5.22
19946: Adding RAS telegraf input

Bug Fixes

19924: Remove unused 'security-script' option from upgrade command
19925: Create CLI configs in influxd upgrade
19928: Fix parsing of retention policy CLI args in influx setup and influxd upgrade
19930: Replace 0 with MaxInt when upgrading query-concurrency
19937: Create CLI configs
19939: Make influxd help more specific
19945: Allow write-only V1 tokens to find DBRPs
19947: Updating v1 auth description
19952: Use db/rp naming convention when migrating DBs to buckets
19956: Improve help for --no-password switch
19959: Use 10 instead of MaxInt when rewriting query-concurrency
19960: Remove bucket and mapping auto-creation from v1 /write API
19885: Misuse of reflect.SliceHeader

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you check the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: go.sum
Command failed: docker run --rm --name=renovate_go --label=renovate_child -v "/var/folders/bf/90yzq4vn42s2163sp1g5d0n80000gn/T/renovate/repos/github/renovate-testing/test-8677-goproxy-5-prometheus":"/var/folders/bf/90yzq4vn42s2163sp1g5d0n80000gn/T/renovate/repos/github/renovate-testing/test-8677-goproxy-5-prometheus" -v "/var/folders/bf/90yzq4vn42s2163sp1g5d0n80000gn/T/renovate/cache":"/var/folders/bf/90yzq4vn42s2163sp1g5d0n80000gn/T/renovate/cache" -v "/var/folders/bf/90yzq4vn42s2163sp1g5d0n80000gn/T/renovate/cache/others/go":"/var/folders/bf/90yzq4vn42s2163sp1g5d0n80000gn/T/renovate/cache/others/go" -e GOPATH -e CGO_ENABLED -w "/var/folders/bf/90yzq4vn42s2163sp1g5d0n80000gn/T/renovate/repos/github/renovate-testing/test-8677-goproxy-5-prometheus" docker.io/renovate/go:1.14.15 bash -l -c "git config --global<EMAIL_ADDRESS>\"https://github.com/\" && go get -d ./... && go mod tidy && go mod tidy"
go<EMAIL_ADDRESS>go.mod has non-.../v9 module path "github.com/influxdata/influxdb/v2" (and .../v9/go.mod does not exist) at revision v9.9.9


Promise Class Producing Incorrect Name

I just tested swift-doc on my package Bluebird: https://github.com/AndrewBarba/Bluebird.swift
The Promise class, declared here, is being generated as State.StateHandler.Promise.
State and StateHandler are two internal enums declared above the Promise class in the same file.
Generated docs: https://andrewbarba.github.io/Bluebird.swift/
Installed on macOS 10.15.4 via Homebrew

This should be fixed by #51. Can you please try again building from master?

I tested this locally with 1.0.0-beta.2, and the generated documentation now has the correct class name.


Docusaurus v2

Migration from Docusaurus v1 to v2. Addresses #6040 2986
The existing microsite is unchanged. The new version is in ./microsite-v2.
There are a few problems for the moment. Suggestions welcome.

The microsite builds, but doesn't render in the browser yet. There are some runtime errors I haven't investigated.
Prettier complains about things like Parsing error: The keyword 'import' is reserved. This indicates to me that eslint is expecting an older version of JS syntax for some reason. I can't figure out where this is defined.
There are lots of syntax errors in the docs directory. Anywhere there is a
 tag in a markdown file, Docusaurus seems to want to parse it. Replacing all of the
 tags with backticks has worked around the issue for the moment. I presume these are auto-genenated docs so my workaround is going to get clobbered eventually. I need a sustainable solution for this.
The API of the <Redirect /> component changed. I have patched the places this was used but the client-redirects plugin might be a better solution. Or better yet, server side redirects?? (Where is backstage.io hosted?)
The biggest problem I have encountered so far is the use of fs to load the plugins from YAML files in src/pages/plugins.js. Docusaurus v2 is a static site and a SPA so the code in that page is parsed on the client side as well as during the build step (which runs in the node environment). fs doesn't exist in the browser of course.

Example of a syntax error in the generated API docs:
SyntaxError: /Users/davidtuite/dev/roadiehq/backstage/docs/reference/utility-apis/StorageApi.md: Unexpected token, expected "," (53:20)
  51 |    * Subscribes to this observable to start receiving new values.
  52 |    */
> 53 |   subscribe(observer: Observer<T>): Subscription;
     |                     ^
  54 |   subscribe(
  55 |     onNext: (value: T) => void,
  56 |     onError?: (error: Error) => void,

How did you do this? Using some automated transformation tool? It has wreaked havoc on a lot of different files, like stripping out URLs partially and replacing valid markdown links with empty space, etc :)

How did you do this? Using some automated transformation tool? It has wreaked havoc on a lot of different files, like stripping out URLs partially and replacing valid markdown links with empty space, etc :)

There's an official migration CLI.
I think a 2 phase process will work for this:

Get the thing to render so between the diff and comparing in the browser, I can figure out the delta between microsite v1 and v2.
Fix everything

I can look into writing some tests for v1 functionality so we can be more sure that everything works the same.

Just going to close this. Realistically I don't have time to complete it.


[ISSUE #116] feat: support client event notification

Which Issue(s) This PR Fixes
Close #116
Brief Description
Support client online/offline event notification
-1）Based on RMQ LMQ storage
-2）When a client comes online or goes offline, the MQTT server will generate an event and asynchronously push the event messages to the specified LMQ
How Did You Test This Change?
UT

Maybe it would be better designed this way. After an online or offline event occurs, the message is directly encapsulated and sent to the system Topic (System Topic in the MQTT protocol) as an ordinary message. The user's device can subscribe to the system Topic (System Topic in the MQTT protocol) for consumption. Can be consumed through MQ

Maybe it would be better designed this way. After an online or offline event occurs, the message is directly encapsulated and sent to the system Topic (System Topic in the MQTT protocol) as an ordinary message. The user's device can subscribe to the system Topic (System Topic in the MQTT protocol) for consumption. Of course, like ordinary topics, such messages can also be consumed through MQ.

done

Please add some examples of how to consume online and offline events, such as consuming through MQTT SDK and consuming through MQ SDK

done, pls take a look when you are free, thx.


move installer over to GitHub releases

We don't actually need any external infrastructure for the installer. Mostly because I'm not sure when the last time was that we published there, and if the original link even works.
Here's my current thinking - use Squirrel.Windows and GitHub releases.
This guide is what I'd start working from, but the other tasks include:

update the website to refer to https://github.com/Code52/carnac/releases/latest
???

I'll take this one


Remove Microsoft.Office Insider Build 16.0.18129.20030, AGAIN!

Build 18129 is Insider build, but also corresponds with Deployment Tool version number.
Current version for Microsoft Office 365 is 18025.20140
See https://learn.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date
Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Latest stable build under https://github.com/microsoft/winget-pkgs/pull/183282

URL: https://officecdn.microsoft.com/pr/wsus/setup.exe
Status Code: 200
(Automated message - build 896)


opmeta: don't build opmetas multi-arch

Operator metadata containers will never be executed. They are just
glorified tarballs; there is no need to build all of the available
architectures and risk something going wrong with one randomly.

@sosiouxme PR needs rebase to include latest py3 test.
Also get_builtin_module was removed from the latest test code. You can use io.open() then mock io module.

Should I bring this over to ART-1728 ?

@thiagoalessio please. we only need a single arch on bundles.

obsolete


Start of week

Is there an easy way to find the start of the week? Or is there some detailed documentation available somewhere?
If there is no easy way to get the start of the week this might be a nice-to-have feature.
Thanks in advance

something like this maybe?
- (NSDate *)firstDayOfWeek{
    BOOL weekStartMonday = YES;
    NSCalendar *calendar = [[self class] implicitCalendar];
    NSDateComponents *weekdayComponents = [calendar components:NSCalendarUnitWeekday fromDate:self];

    NSInteger weekdayoffset1 = (weekStartMonday) ? 2 : 1;

    NSDateComponents *componentsToSubtract  = [[NSDateComponents alloc] init];
    [componentsToSubtract setDay: (0 - ([weekdayComponents weekday] == 1 ? 8 : [weekdayComponents weekday])) + weekdayoffset1];

    NSDate *beginningOfWeek = [calendar dateByAddingComponents:componentsToSubtract toDate:self options:0];
    return beginningOfWeek;
}

Well ultimately I found that this method works for me (week starts on monday):
+(NSDate*)getFirstDayOfTheWeek {
NSDate *today = [[NSDate alloc] init];
today =[today dateBySubtractingHours:today.hour];
today =[today dateBySubtractingMinutes:today.minute];
today =[today dateBySubtractingSeconds:today.second];

return[today dateBySubtractingDays:(today.weekday + 5) % 7];

}


tools: remove unused end2endblast

The end2endblast tool was introduced for router performance testing, but has been superseded by the brload tool

This change is


history can't print to IO argument

Reference:
https://github.com/JuliaLang/IJulia.jl/blob/acbd9e24ef95f04645ac6602c6dbfaea9bebbca8/src/IJulia.jl#L237
The io::IO function parameter is unused.  Shouldn't the print statement be:
print(io, In[n])

Thanks, this was a bug.


chore(deps): bump all hyper packages

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Error message in binding isn't wrote to http response

In api/bind, func handleBindingError handles errors. It writes error message to the broker store and the log, but doesn't write to response. So users can't directly see the message. Same in api/unbind.

This is deliberate. iirc, any error that is the user's fault (e.g. malformed request, parameter validation failed, etc.), the cause is included in the response. However, the only errors that are handled by handleBindingError (again, iirc) are 500 internal server errors. Generally, it is not considered a good practice to share details of an internal error with users.

It makes sense.


✨ Enable photo HDR capability

What feature or enhancement are you suggesting?
Currently all formats shows only video HDR. It will be great if v3 has photo HDR capabilty
What Platforms whould this feature/enhancement affect?
iOS
Alternatives/Workarounds
I need this feature. Currently there are no alternatives or workarounds for this.
Additional information

[X] I agree to follow this project's Code of Conduct
[X] I searched for similar feature requests in this repository and found none.

On iOS, photo HDR is absolutely non-trivial - looks like you need to capture multiple and fuse the images together yourself, basically re-invent the HDR algorithm. No idea why they don't provide that. See Is HDR capture a thing in iOS?

hhmmmmm


Add http credentials to browserContext options

Motivation/Description of the PR

Make sure Playwright browser context set on creation when possible
Resolves #3035

Applicable helpers:

[ ] WebDriver
[ ] Puppeteer
[ ] Nightmare
[ ] REST
[ ] FileHelper
[ ] Appium
[ ] Protractor
[ ] TestCafe
[x] Playwright

Applicable plugins:

[ ] allure
[ ] autoDelay
[ ] autoLogin
[ ] customLocator
[ ] pauseOnFail
[ ] coverage
[ ] retryFailedStep
[ ] screenshotOnFail
[ ] selenoid
[ ] stepByStepReport
[ ] wdio
[ ] subtitles

Type of change

[ ] :fire: Breaking changes
[ ] :rocket: New functionality
[x] :bug: Bug fix
[ ] :clipboard: Documentation changes/updates
[ ] :hotsprings: Hot fix
[ ] :hammer: Markdown files fix - not related to source code
[ ] :nail_care: Polish code

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[ ] Lint checking (Run npm run lint)
[x] Local tests are passed (Run npm test)

Thank you!


can‘t train

hello,everyone.
when i run python:python train.py -c config.json
the error  :

my config.json is:

I think I followed the tutorial.
who can tell me why?thanks!

Did you make the "annotations" this folder? And did you make whole annots file(xml) correct?
And make sure your annots files are all under your "annotations" folder

same thing.

same thing.

I get the same error,

getting the same error . Can anyone help with this issue?

Hi, you need set labels and two folders (images and annotations) in config.json. This function load all XML files from annotations folder and memorize the labels then compare with labels property in config.json.

I had the same problem, I renamed the cache name as 'raccoon.pkl', then the training started. Apart from that, make sure that the path for the training images and the corresponding annotations is correct.


qa tests: reboot machine, rather than replace

Motivated by https://issues.apache.org/jira/browse/BROOKLYN-603, which can cause this test to fail if a cloud-cleaner deletes the keypair in the 10 minutes between the VM being initially created and then the VM replaced by the call to restart(restartMachine: true).
Instead, a better test is that the VM survives reboot. I think that is more useful to the user, rather than replacing the VM entirely.

PR comment addressed.
Travis failure is:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:3.0.0-M1:install (default-install) on project clocker-feature: NoFileAssignedException: The packaging plugin for this project did not assign a main file to the project but it has attachments. Change packaging to 'pom'. -> [Help 1]

This looks familiar. I think that @kemitix hit that somewhere else, and rolled back maven-install-plugin to a version older than 3.0.0-M1 to fix it. I've therefore added that fix as well.


Grape route error

After upgrading to 0.16.2 from 0.15.0 I get this error:
Mustermann::CompileError - can't use the same capture name twice: "/(*:path)*path(.json)":
I have looked at the UPGRADING document and it doesn't look like I am using any of the deprecated methods.
In my routes.rb file I am using: mount Base => '/'
Is there any more information I can provide to help debug this issue?

This is just a regex error in an API declaration, no? Do you have a route that looks like the one above in the error?

It doesn't appear to be a regex error as it works with 0.15.0. My routes:
Rails.application.routes.draw do
  root 'timetable#index'

  namespace :timetable do
    get 'index'
  end

  mount Base => '/'
end

It appears that the commit that introduced this issue is: https://github.com/ruby-grape/grape/commit/9f4ba67d4aca90f04a65c5ff921b1687942eb99c

Yes, the router was replaced, it's a lot of changes. I would look at the stack that gets there or try to build a spec that reproduces this problem to start.

make sure all child mounted apis are inherited by parent grape api instead of Grape::API. For Ex
` class Root < Grape::API
mount Base
end
class Base < Root
end
`

@dblock is @saubi1993's comment preceding this accurate?  should mounted APIs inherit from their parent class vs. Grape::API?  I have never seen this documented elsewhere and am skeptical it has any practical benefit.  If it does, it would be good to call this out explicilty (and loudly) in the documentation.

I think I agree with you @jnardone, @saubi1993 care to clarify?

I was having an issue, where routes were repeating twice i.e. if route path was like /api/v1/users/1/latest, rake routes was generating /api/v1/users/1/users/1/latest and before callback was executing twice before API was even executed. Doing Above resolved the issue @dblock


How to filter a concatenated result value in multi fields in Laravel 5.3

Hi,
In my datatable, I'm retrieving the name field as CONCAT(fname," ", "lname").  I have to search name field in the datatable and it should return matching with either fname or lname. Please let me know how to do this:
js code:
columns  : [
   			 { data: 'name', name: 'fname' }, //I have tried this also : ['fname','lname' ]
                --------------------

PHP code:
$users = User::leftJoin('address', 'address.user_id', '=', 'users.user_id')
                    ->select([\DB::Raw(
                        'CONCAT(fname," ",lname) as name, CONCAT(country_code, "", mobile_number) as mobile_num, IF(status = 1, "Active", "Inactive") as status,
                        (SELECT count(subscription_id) FROM subscription WHERE subscription.user_id = users.user_id AND subscription.status IN (2,4)) as totalActivesubscription'

                        ), 'gender', 'city as address', 'city','users.user_id', 'email_id'])

                    ->where('users.role_id', '=', $aParam['role_id']);

            return Datatables::of($users)
                ->addColumn('actions', function ($users) {
                    return view('users.templates.user_action', [
                        'user' => $users
                        ])->render();
                })

            ->make(true);

System details:"

Operating System : Windows8, Linux
PHP Version : 5.6
Laravel Version : 5.3
Laravel-Datatables Version : latest

Maybe try using this trick on your js:
columns  : [
   { data: 'name', name: 'fname' },
   { data: 'name', name: 'lname', visible: false },
...

Or use filterColumn api.

by using filterColumn api it worked. Thank you.
But what if we need to search a field of another table (which joined in the main query).

ok its solved using https://datatables.yajrabox.com/fluent/joins. Thanks


incomplete documentation: how to change border sytle

Did you check the docs and existing issues?

[X] I have read the docs
[X] I have searched the existing issues

Neovim version (nvim -v)
0.10.0
Operating system/version
MacOS 14.5
Describe the bug
I can't figure out how to change the border style. Is there another option other that "rounded"?
What is the severity of this bug?
minor (annoyance)
Steps To Reproduce
<cmd> Oil --float . <CR>
Expected Behavior
Mention somewhere if there are other window border options.
Directory structure
No response
Repro
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "runtime", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
        "stevearc/oil.nvim",
        config = function()
            require("oil").setup({
              -- add any needed settings here
            })
        end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Did you check the bug with a clean config?

[X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

See :help nvim_open_win. This will give you an idea what the options are for the border parameter, and a better understanding of how floating windows are configured in general

None of the border options found in :h nvim_open_win change the appearance of windows in oil buffers.
my oil.lua file:
return {
  "stevearc/oil.nvim",
  lazy = false,
  dependencies = { "nvim-tree/nvim-web-devicons" },
  config = function()
    require("oil").setup({
      delete_to_trash = true,
      view_options = { show_hidden = true },

      -- window appearance
      float = { border = "single" },
      confirmation = { border = "single" },
      progress = { border = "single" },
    })
}


[Feature Request] typespec sample project for resource-manager

Now more and more service onboard with typespec, it is necessary to create a  sample typespec project for resoure-manager like data-plane

may be blocked by https://github.com/Azure/typespec-azure/issues/2906

I find the request during review for https://github.com/Azure/azure-rest-api-specs-pr/pull/12045

@weshaggard , we talked about this request before. Is this in the backlog?

It is tracked by https://github.com/Azure/azure-rest-api-specs-pr/issues/11056 but we aren't currently working on it.

It is tracked by Azure/azure-rest-api-specs-pr#11056 but we aren't currently working on it.

@weshaggard , what's the plan of adding it? It cause issues when service team works on management plane specs but referencing to the data plane sample project. e.g. tsp.config.yaml has different configs.

@allenjzhang could you help get a sample project and template setup for ARM teams to reference? If not I'll try to start it but I'm not sure when I'll be able to get to it yet.


Repository doesn't contain a parent

I was trying to use github4s for a project I'm working on but wasn't able to because Repository doesn't seem to contain a parent even though it contains e.g. owner and organization (https://github.com/47degrees/github4s/blob/master/github4s/src/main/scala/github4s/domain/Repository.scala). Is there a specific reason for it? Could it be added?

yes, it is possible to add it :+1:

yes, it is possible to add it :+1:


Event sets

Changes

Allows one to generate event sets (token deduplication "EventSet") for MultisetSubstitutionSystem.
Event sets are similar to match-all systems, however, they also deduplicate all tokens with identical content.

Comments

This is a work in progress. There are no tests and no documentation at the moment.
In particular, converting these objects to WolframModelEvolutionObject is not necessarily the best idea (I will probably disable that in cases where there is token deduplication).

Examples

Add all possible pairs of numbers starting from 1 for 3 generations:

In[] := #["ExpressionsEventsGraph", VertexLabels -> Automatic, GraphLayout -> "SpringElectricalEmbedding"] &@
 SetReplaceTypeConvert[{WolframModelEvolutionObject, 2}]@
  GenerateFullEventSet[MultisetSubstitutionSystem[{a_, b_} /; a <= b :> {a + b}], 3]@{1}

Even though it's not complete hypergraph deduplication yet, it already makes TEGs for hypergraphs quite a lot smaller (don't trust this result until I implement the tests though). Before deduplication:

In[] := WolframModel[<|"PatternRules" -> ({{v1_, v2_}, {v1_, v3_}} :>
      Module[{v4}, {{v1, v2}, {v1, v4}, {v2, v4}, {v3, v4}}])|>, {{1, 1}, {1, 1}}, 3,
  "EventSelectionFunction" -> "MultiwaySpacelike"]["ExpressionsEventsGraph", GraphLayout -> "SpringElectricalEmbedding"]

And now:

In[] := #["ExpressionsEventsGraph", GraphLayout -> "SpringElectricalEmbedding"] &@
 SetReplaceTypeConvert[{WolframModelEvolutionObject, 2}]@
  GenerateFullEventSet[
    MultisetSubstitutionSystem[{{v1_, v2_}, {v1_, v3_}} :> Module[{v4}, {{v1, v2}, {v1, v4}, {v2, v4}, {v3, v4}}]],
    3]@{{1, 1}}

This change is

Closing this for now until it becomes more clear what the next steps are.


[WIP] Add tutorial for experiment subclassing

Summary
As part of the Qiskit advocate mentorship program I am working on a new tutorial showing how to subclass existing experiments.
Details and comments
This is a WIP first draft of a new subclassing tutorial using the FineAmplitude experiment as an example.

As we discussed, it would be good to show an example of writing a custom CurveFit class for your custom experiment


[Discussion] Don't show account menu if we can view the toolbar

Don't show account menu if we can view the toolbar, has been introduced in 8.5.2 which make sense.
But most of our clients are using this account menu.
The scenario is, they want to show the My Account menu (actually the pages under welcome) to the users (registered/specific groups) but not the dashboard pages.
To achieve this, we need to give access permission to the dashboard page and revoke access from the pages other than the welcome/*, which is a bit complex and scary.
So, we just do the override of footer_required.php.
IMO, it's very common that the user will access the account pages. Can we make a better solution to this?

oh, so that must be related to this issue #8260 right?

We actually already have a solution for this built into the core. It's called "Desktops". You can designate a page as a desktop, and a user can be redirected to it when they login. It doesn't have to be in the Dashboard. The "Welcome" screen in the dashboard is a desktop, but so is '/account/welcome."
If you create a regular unprivileged user and they login they will be redirected to '/account/welcome.' You can change how this page works, add blocks to it, customize it by overriding it, etc... It also shows all the pages under my account, which you don't need to be a privileged user to access. Is this page and it's approach not sufficient?
So these are users who can see the toolbar, but can't see the Dashboard?

Hmmm, using Desktops or Overrides in both way-
If someone updates the concrete5 from 8.5.1 to 8.5.2+ he needs to do some customization to keep using the account menu.
BTW, I found later that it's a duplicate of https://github.com/concrete5/concrete5/issues/8260


App crashes when return from another tab in a tab navigator

The app has the following navigation structure:

Home

VideoPlayer

Playlists

Configs

In home there is a video's list, so the video player screen is called when an video e touched in the home screen. If the user switch for another tab and back to the home tab (where the VideoPlayer is loaded) the app crashes.
Environment:
Platform: Android (wasn't tested in iOS)
react-native-youtube: ^2.0.0
@react-navigation/bottom-tabs: ^5.0.5
react-native: 0.61.5

I had same issue and I resolved below way
import { useIsFocuesed } from '@react-navigation/native'

const Layout: React.FC = () => {
    const isFocuesed = useIsFocuesed();

    return (
        // ...
        {isFocused && <YouTube ... />}
        // ...
    }
}


Production remote bundles fails to load without any error message

Environment
We are using ChunkManager APIs of module-federation to load remote bundles. We tried in both iOS and android platforms but faced same issue on both.
Description
We are using following command to create production bundles (container and chunk bundles). Then we load these bundles, as remote bundles, but they fails to load and we are stuck at loading state.
STANDALONE=1 react-native webpack-bundle --platform ios --dev false --entry-file index.js --bundle-output bundle/index.bundle
Where as if we run the same code, but with development bundles created using following command they are loaded properly. Note the difference in both commands is - --dev true/ false
STANDALONE=1 react-native webpack-bundle --platform ios --dev true --entry-file index.js --bundle-output bundle/index.bundle
Reproducible Demo
We are using following example to load remote bundles, using ChunkManager APIs of repack module-federation.
https://github.com/zamotany/module-federation-repack
Any help will be highly appreciated.
Thank you!

Any errors in terminal, logcat or Console.app? Also are you trying to run host app or individual apps?

There is nothing in the logs. Please find below the logs from terminal (running host server webpack/repack) and logcat. Please note we have removed the actual s3 link and android package Id from the logs.
We are running host app on local machine, and widget apps bundles are created using the command mentioned in the above post and hosted in AWS S3 bucket. We also tried hosing the widget apps bundles in localhost, but same results.
Terminal log -
[02:53:26.481Z][DevServerProxy] response received
[02:53:33.939Z][Console] i18next::translator: missingKey en-US host route.NAVIGATION_HOME_KEY route.NAVIGATION_HOME_KEY
[02:53:33.944Z][Console] i18next::translator: missingKey en-US host route.NAVIGATION_FARMS_AND_FIELDS_KEY route.NAVIGATION_FARMS_AND_FIELDS_KEY
[02:53:34.668Z][Console] main | widget2 | <aws s3 link>/widget2.container.bundle
[02:53:37.169Z][Console] main | widget1 | <aws s3 link>/widget1.container.bundle

Logcat log -
ReactNativeJS: 'i18next::translator: missingKey', 'en-US', 'host', 'route.NAVIGATION_HOME_KEY', 'route.NAVIGATION_HOME_KEY'
ReactNativeJS: 'i18next::translator: missingKey', 'en-US', 'host', 'route.NAVIGATION_FARMS_AND_FIELDS_KEY', 'route.NAVIGATION_FARMS_AND_FIELDS_KEY'
ReactNativeJS: main | widget2 | <aws s3 link prefix>widget2.container.bundle
.mxp.host.stag: Background young concurrent copying GC freed 82288(3612KB) AllocSpace objects, 1(16KB) LOS objects, 0% free, 18MB/18MB, paused 7.081ms total 91.494ms
.mxp.host.stag: Background concurrent copying GC freed 9336(2495KB) AllocSpace objects, 4(9024KB) LOS objects, 33% free, 11MB/17MB, paused 594us total 116.229ms
ReactNativeJS: main | widget1 | <aws s3 link prefix>widget1.container.bundle

Can you post configuration for webpack.container.ModuleFederationPlugins and a config for ChunkManager.configure?

Am also stuck on this, host app load containers properly in development mode but is stuck loading while fetching the container from a remote server. (for testing the remote container is hosted on Cloudinary). is there any configuration am missing???

i also try getRemoteUrl but has the same issue that the chunk could not be resolved.

Hello, have you found a solution for this issue yet? I'm currently experiencing the same problem.

Environment
We are using ChunkManager APIs of module-federation to load remote bundles. We tried in both iOS and android platforms but faced same issue on both.
Description
We are using following command to create production bundles (container and chunk bundles). Then we load these bundles, as remote bundles, but they fails to load and we are stuck at loading state.
STANDALONE=1 react-native webpack-bundle --platform ios --dev false --entry-file index.js --bundle-output bundle/index.bundle
Where as if we run the same code, but with development bundles created using following command they are loaded properly. Note the difference in both commands is - --dev true/ false
STANDALONE=1 react-native webpack-bundle --platform ios --dev true --entry-file index.js --bundle-output bundle/index.bundle
Reproducible Demo
We are using following example to load remote bundles, using ChunkManager APIs of repack module-federation. https://github.com/zamotany/module-federation-repack
Any help will be highly appreciated.
Thank you!

Hello, have you found a solution for this issue yet? I'm currently experiencing the same problem.
https://github.com/callstack/repack/issues/505


cln: Sanity check max htlc amount msat

For https://github.com/ElementsProject/peerswap/pull/246#issuecomment-1739743519
Added logic to check the maximum htlc limit for cln set per node for each channel.
Additionally checking maxhtlc would be more strict than CLN's own limitations.
Also, to ensure that the receivable amout is also taken into account.

Tested ACK 6ab037a.
$ ./out/pscli swapin --sat_amt 18420558 --channel_id<PHONE_NUMBER>20587008 --asset lbtc   # CLN as receiver
2023/10/02 15:00:24 rpc error: code = Unknown desc = exceeding receivable amount_msat: 1

$ lightning-cli --signet peerswap-swap-out 162922x1x0 18670459 lbtc   # CLN as sender
{
   "code": -1,
   "message": "exceeding spendable amount_msat: 1"
}

Ack 6ab037a9bc4f15f60da4a624017b9318520163dc


Update npmignore

Summary
Updating .npmignore. Adding:

target
reports
tests

We shouldn't need any of the examples/routes from the tests directory for terra-ui.com. The tests directory only contains examples intended for functional verification.
https://github.com/cerner/terra-core/issues/384
Thanks for contributing to Terra.
@cerner/terra

Will the test links be broken in the deployed site if we don't include those directories?

Will the test links be broken in the deployed site if we don't include those directories?

For GitHub pages, we generate the bundle for the deployed site locally. It works on my local machine.
For the review apps, it clones the repo, installs dependencies, and compiles src to lib before generating the bundle. It is working on this PR.

@ryanthemanuel, I can confirm what @Matt-Butler said. I checked out this branch and npm run clean:install. Then I ran npm run deploy to deploy to gh-pages from this branch. It looks like the deployment successfully kept the test links: http://engineering.cerner.com/terra-core/#/tests/icon-tests/bidi
It also looks like test links are available in the Heroku reviewable apps deployment:
https://terra-core-deployed-pr-415.herokuapp.com/static/#/tests/icon-tests/height-width


New component implementation: Linear progress

Hiya,
I'd like to add a linear progress component implementation. I am comfortable with the component and adapter creation.
The part I am unsure about though is how to add a golden screenshot for this. The dots move at a rather rapid pace and I am scared they don't line up properly for subsequent screenshots because of timing issues.
Edit: this might also be an issue for the indeterminate variant.
Any advice for how to proceed with screenshots for this component?

@hvolschenk you're going to use the foundation/adapter from mdc web to build the linear progress component?
We actually don't keep track of any of the browser events. You already have it running on docker, correct? We use puppeteer, and I'm sure they have something in there that can help us. I think we can update the screenshots in a separate PR, and then the linear progress changes can absorb those. How does that sound?

Hiya,
Yeah I'll be building the adapter using the given foundation, taking example from some other existing implementations.
As for the screenshots, what I mean is:
The linear progress component has an animated background, as can be seen in the demo. The screenshots are taken from that page, I was/am just afraid that the moving dots (that make up the "un-progressed" piece) won't line up each time a screenshot is taken.
My thinking is that there might be a millisecond or two delay before the screenshot is taken with puppeteer in which time the dots would/could have moved, thus making the screenshots unreliable. Or am I incorrect in thinking this?

No I think you're correct. I think we should try doing the buffered and indeterminate variants, but as you can see on the demo page https://material-components.github.io/material-components-web-catalog/#/component/linear-progress-indicator, there are stationary variants. So worse comes to worse we can just use those.

@moog16 Can I close this issue now that #425 is merged?

Closing!


Sort an array of 0’s 1’s 2’s without using extra space or sorting algo

💥 Proposal
Greetings sir/Mam,
I would like to contribute the code for this issue in C++/CPP.
The code is ready. I have added the code , along with proper explanation of the algorithm , test cases , time complexity and space complexity of the same, as per the guidelines.
Kindly assign it to me.
This is regarding GSSOC'21.
Regards,
Hitain Kakkar

/assign


DecodePuzzleHash return xrp prefix

Thanks for the contribution. Any chance you can update your PR to have signed commits? https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

Thanks for the contribution. Any chance you can update your PR to have signed commits? https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

Done


Allow passing in any parameters supported by docker

Allow passing in any parameters supported by docker, so that user can pass in

New parameters supported by docker
Existing parameters but not supported by testcontainers, e.g. there are almost hundred parameters at: https://docker-py.readthedocs.io/en/stable/containers.html

In my own scenario, I need to start a container which shares the same volume from another container (not created by testcontainer).

@tillahoffmann So as I understand you propose to delete methods such as ports and volumes and replace them with kwargs?

I think it's better to keep the methods and only remove the fields, so keep everything backward compatible, I'm creating another PR now


This work is great and meaningful in the vfx field, I'm looking forward to the day it's code is published

Hey D-Mad, thanks for your interest. We will release it soon. Stay tuned!

Hi, this work is really great. I am also looking forward to the day it will be published


The Pathsphere text next to logo and dark mode,light mode toggle button is dissapearing in dark mode

Description
In the Dark mode The Pathsphere text next to logo and dark mode,light mode toggle button is dissapearing
Steps to Reproduce
I will add a overlay to fix this both issues
Expected Behavior
Dark mode The Pathsphere text next to logo and dark mode,light mode toggle button should be visible in both dark and light mode
Actual Behavior
In the Dark mode The Pathsphere text next to logo and dark mode,light mode toggle button is dissapearing
Screenshots
https://github.com/user-attachments/assets/1892f480-275e-4a96-95b4-6f078e1f231a
Additional Information
No response
What browser are you seeing the problem on?

[ ] Firefox
[X] Chrome
[ ] Safari
[ ] Microsoft Edge

Checklist

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

@shravya312 if you are not wokring on it can i have a go

Others are already working on this issue before, so kindly create a new issue


GEOMESA-2541 Relocate netty.io for Hadoop 3 compatibility

to avoid breaking arrow execution

creating new one to clean up my userid mess.


[F] Deno 1.0 support

🚀 Feature Proposal
Support for Deno 1.0.
It shouldn't be that hard to make ExcelJS Deno compatible. The only thing which was failing in my test right now is the use of a buffer polyfill which is using the __proto__ on UInt8Array. You can read more about it here: https://github.com/denoland/deno/issues/4721
Motivation
A lot of node developers are already trying Deno and some of them are already switching for new projects to Deno.
Example
import ExcelJS from "https://deno.land/x/exceljs/mod.ts"

That sounds interesting. I checked that our code does not contain any references to __proto__, and it looks like deno is not using our source files, but rather the compiled bundle for the frontend. Could you help us find out which of our dependencies is responsible for that? I assume it's happening somewhere in our build step.

@alubbe Yes, I had the same assumption that it comes from the build process. In the meantime I managed to import ExcelJS into Deno. However, Deno doesn't have a crypto module yet but ExcelJS relies on the one from Node or the browser. Since it's just a side project I don't want to search for a Crypto Polyfill and integrate it into the build process. I'll probably just switch back to Node.
If you want I can leave this feature request open until Deno has a crypto module otherwise I'll close it.

I'd say let's close it for now until we deno has a crypto module and then let's see whether we are compatible with it. But thanks for trying out deno and posting your findings here!


When drag grid list , get the wrong order

i want to drag first box to secod line, but get worng order;
for example: https://codesandbox.io/s/solitary-tdd-l4yu9?file=/src/card/Container.tsx

drag the '0' box  to '4'  box
got the wrong text:  3 1 4 2 0 5 6 7 8 9
expect text:  1 2 3 4 0 5 6 7 8 9

https://user-images.githubusercontent.com/25600705/114833947-ac228a00-9e02-11eb-87f9-cb27b0bbb179.mp4

You probably did fix it already, but i fixed it here https://codesandbox.io/s/sharp-antonelli-ypm6bc?file=/src/card/Container.tsx

here is what is changed


Problem: Dev environment is broken and no integration with Tendermint

bigchaindb-driver version: master
bigchaindb server version (bigchaindb -v): master/tendermint
Python version: n/a
Operating System: n/a

Description
Currently, the development environment of BigchainDB Python driver is broken and is not integrated with Tendermint i.e. BigchainDB v2.0 is integrated with Tendermint but the driver development enviroment still uses BigchainDB <=1.3.0.
Update the development environment:

Update docker-compose.yml
Remove docker-compose.rdb.yml because RethinkDB is not supported with BigchainDB v2.0
Update Travis configuration to test with localmongodb and BigchainDB v2.0 instead of BigchainDB <=1.3.0 and rethinkdb.
Consolidate all deployment methods in a single docker-compose file i.e. docs.yml should move into docker-compose.yml as well.

related to #358


feature: 更新Proxy文件兼容制品库 (close #181)

Codecov Report

:exclamation: No coverage uploaded for pull request base (V2.1.350rc@9e70f62). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             V2.1.350rc     #184   +/-   ##
=============================================
  Coverage              ?   61.76%
=============================================
  Files                 ?      225
  Lines                 ?    19485
  Branches              ?        0
=============================================
  Hits                  ?    12034
  Misses                ?     7451
  Partials              ?        0

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 9e70f62...9f9a619. Read the comment docs.


Mark RTT as supported by RP2XXX Chip

RTT is supported by the RP2XXX series of chips, so it should be marked as such.
Based on the other chips, this seemed to be the correct place for this.

This needs to be rebased on an updated main, and the compliance check should pass, but otherwise this is fine

Rebased and repushed.

Still failing... you need to prefix your commit message with rpi_pico:

Ok hopefully everything is good now.

@ThadHouse please rebase on a fresh main

@yonsch what can I do to make it so this gets merged in a timely enough manner so I don’t have to keep rebasing it?

@ThadHouse Now with v3.2 out I hope it will get merged quickly

Please rebase without merging main, you should have only one commit with your changes

Yeah, I hit the wrong button. Fixed.

@nordicjm can you take another look?


Neon.Service: document Kubernetes startupProbe/livelinessProbe

I just noticed that Kubernetes implements redinessProbe and startupProbes in addition to a livenessProbe:
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#types-of-probe
Here's the relevant summary of how these work:
livenessProbe:

    Indicates whether the container is running. If the liveness probe fails, the kubelet kills the container,
    and the container is subjected to its restart policy. If a container does not provide a liveness probe,
    the default state is Success.

readinessProbe:

    Indicates whether the container is ready to respond to requests. If the readiness probe fails, the
    endpoints controller removes the Pod's IP address from the endpoints of all Services that match
    the Pod. The default state of readiness before the initial delay is Failure. If a container does not provide
    a readiness probe, the default state is Success.

startupProbe:

    Indicates whether the application within the container is started. All other probes are disabled if a
    startup probe is provided, until it succeeds. If the startup probe fails, the kubelet kills the container,
    and the container is subjected to its restart policy. If a container does not provide a startup probe,
    the default state is Success.

I'm not entirely sure why people would use a readinessProbe instead of a startupProbe.  startupProbes are nice because they prevent both readinessProbe and livenessProbe probes from running until the startup probe has succeeded.  Using readinessProbe instead can mean that the readinessProbe may fail before the node is ready resulting in the pod being terminated.
JEFF UPDATE: I think I understand readinessProbe now: I believe this can be used to temporarily take a running pod offline so that it no longer receives external requests without having Kubelet terminating  it.
I think our current health-check script can work for all of these probes so this is really a documentation update, where we should recommend that NeonService applications be configured with both a startupProbe and a livenessProbe.

So we will need a bit of a code change to handle redinessProbe.  NeonServiceStatus is currently defined as:
    /// <summary>
    /// Enumerates the possible <see cref="NeonService"/> running states.
    /// </summary>
    public enum NeonServiceStatus
    {
        /// <summary>
        /// The service has not been started.
        /// </summary>
        [EnumMember(Value = "not-started")]
        NotStarted = 0,

        /// <summary>
        /// The service is in the process of starting but is not yet
        /// fully initialized.
        /// </summary>
        [EnumMember(Value = "starting")]
        Starting,

        /// <summary>
        /// The service is running and ready for traffic.
        /// </summary>
        [EnumMember(Value = "running")]
        Running,

        /// <summary>
        /// The service is running but is not healthy.
        /// </summary>
        [EnumMember(Value = "unhealthy")]
        Unhealthy,

        /// <summary>
        /// The service has terminated.
        /// </summary>
        [EnumMember(Value = "terminated")]
        Terminated
    }

We need to add another state: NotReady.  When set, this means that the pod is running but is not ready to accept external requests.  We'd then need to modify the health-check script to return healthy for either the Running or NotReady states.
We also need to generate a new ready-check script that returns healthy for Running or NotReady and not ready for anything else.

DONE


[cmake] Add mirror to download Strawberry Perl

Last several days Strawberry Perl official download server has issues that lead to extremely slow download rates
(sometimes it takes more than 1 hour to download ~150MB).
This commit adds non-official mirror of Strawberry Perl to the list of available URLs.
Signed-off-by: Vitalii Koshura<EMAIL_ADDRESS>

Related recent comment: https://github.com/microsoft/vcpkg/issues/932#issuecomment-643350398 .

Here is some background info concerning the server https://strawberry.perl.bot and "https":
https://www.reddit.com/r/perl/comments/epihpr/httpstrawberryperlcom_on_https/

Thanks for the PR!


Fix ES filters, user auth mutations

Support of information about PI, stored in graphql.dataset table.
User/group updated authorisation assertions.
Dataset mutations cleaned and updated.
Fetching metadata and submitter suggestions from ES (not DB).
Optical images authorisation and refactoring.

@LachlanStuart please review when you have time


Collect additional object data

What this PR does / why we need it
This PR collects additional resource information including

explicit collection from capa, capd, capv, capz system namespaces
Summary of running pods, deployments, apps
Summary of pod and node events

Details for the Release Notes (PLEASE PROVIDE)
Diagnostics collects additional resource information and cluster summary

Which issue(s) this PR fixes
Fixes: #2508
Fixes: #7890
Describe testing done for PR
Create tanzu clusters on docker, then run tanzu diagnostics.

LGTM
Can you squash and fix the commit message and I can merge!

Needs a rebase before merging


JndiManager

Having looked at a number of scanning and remediation utilities some appear to remove JndiLookup, some JndiManager. It seems that JndiManager is the one that does the actual JNDI lookup in more recent versions, but there are paths that lead to its execution, other than from JndiLookup. JmsManager and JndiContextSelector are other examples. Is it worth whacking both JndiLookup and JndiManager? I suppose it will break JMS logging.

Which version do you mean, Log4j2 or Log4j 1?

Log4j2.
References

lunasec detects based on hashes specified  https://github.com/lunasec-io/lunasec/blob/master/tools/log4shell/log4j-library-hashes.json. The fact they use hashes is beside the point, but have a look at the version/file combo
https://github.com/palantir/log4j-sniffer(Palantir sniffer) goes after JndiManager. Did not check their code
https://github.com/cloudera/cloudera-scripts-for-log4j(Cloudera) goes after JndiLookup.class


feat: Use API to fill profile info

Description
Fetched the info from the get-user end-point to update the profile details.

Fixes #141
Type of change
Just put an x in the [] which are valid.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.

[ ] ./gradlew assembleDebug assembleRelease
[ ] ./gradlew checkstyle

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

@Swati4star I have parsed and set the joined date as well as it was implemented in the server today morning.

In the last line, the user might not realize that the given date is his joining date.
You can write something like... joined on 15Jun 18
There's no need to mention the time.


Fix copy and paste error on container-image

@TomSweeneyRedHat PTAL

@rh-atomic-bot r+ 5017a57
Tom when they are obvious, just do the above...


Backwards compatibility for new Brief statuses

First of 4 backwards compatibility PRs to handle the two new Brief statuses cancelled and unsuccessful.

Admin FE
Buyer FE https://github.com/alphagov/digitalmarketplace-buyer-frontend/pull/588
Scripts https://github.com/alphagov/digitalmarketplace-scripts/pull/144
Brief Responses FE https://github.com/alphagov/digitalmarketplace-brief-responses-frontend/pull/5

See https://github.com/alphagov/digitalmarketplace-admin-frontend/pull/292/ for the equivalent changes for the awarded status.
As I was unfamiliar with this repo I thought I'd have a look through the tests and include some extra  coverage (mostly straightforward error path checks). I left alone anything even slightly complex 😸
Finally there's some PEP8 imports cleanup, because why not.

Strange, that fix seems to introduce a failure for me locally (and on Travis). It passes without the fix. Is your local venv up to date?

Ok, I rolled it back, I  must have old version of 'forms' component or something.

As a reviewer I'd much prefer to have the unrelated tests and import changes in another branch for a few reasons.

The first, completely selfish reason is that the context switching is a pain for the reviewer
If we start finding bugs in the new tests or in the import changes then fixing them will hold up the more urgent stuff.
It's really hard to define the scope of this sort of thing. For example; in that test_suppliers.py there are some lines that are #noqa d just because they have long strings. I don't think that's a good enough reason to #noqa a whole line. It would be hard to argue that that is out of scope of this PR since we're doing refactoring work in it now.

Got no problems with the actual tests and removing unused imports, that's great, but in another PR would be cool next time and we could tag it as lower priority or something. 👍  Few small changes about consistent spacing and using called_once_with instead of called_with or call_args ==


Praise

Hi,
I just wanted to give praise and applause for this great open-source project! I am currently migrating a complex app which uses Nextjs + React + Firebase Auth to Astro + Solidjs and your project helped a lot! It is shocking how small the footprint is in terms of kilobyte to download.
Thanks a lot and please keep the project as lean and small as possible (modularized?) because at least in my use case the reason to move from React to Solid was to stop having these super huge Javascript codebases a frontend has to download.
So thanks again and feel free to close the issue since it is not an issue 😬❤

Thank you! I appreciate it.


Only show apps with real diff

Only shows apps that actually have a diff
Removes the argocd instance and part-of labels of the diff

Just to follow the code changes a little better, and maybe for posterity, it might be good to include some samples of before/after if you have some links


Custom Data schema descriptions polish

Testing #79843
These properties have no description

Suggest to make a pass over the descriptions and use full sentences that end with a '.' Suggest to mimic these descriptions http://json.schemastore.org/package.

Suggest to change: 'Only workspace folder setting will be read' to 'Only workspace folder settings are considered.'

Sample updated.


chore: Create maven.yml

I fixed the problem with the TOKEN, System.property fails, thus passing it as env var, now the build runs the tests but one assertion failing
Error:  Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 19.148 s <<< FAILURE! - in com.example.application.FormFillerTextIT
Error:  com.example.application.FormFillerTextIT.formFill_chooseText1_fillsForm  Time elapsed: 18.028 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <05/04/2023 12:13:00> but was: <10/01/2023 00:00:00>


Mongock with writeConcern=0;

Hello.
We met next problem on our load testing.
We tried to set writeConcern=0 in uri connection string, to check perfomance of our app, but could not start it, because mongock failed to start our app.
Caused by: java.lang.UnsupportedOperationException: Cannot get information about an unacknowledged update
	at com.mongodb.client.result.UpdateResult$UnacknowledgedUpdateResult.getUnacknowledgedWriteException(UpdateResult.java:202) ~[mongodb-driver-core-3.11.2.jar!/:na]
	at com.mongodb.client.result.UpdateResult$UnacknowledgedUpdateResult.getModifiedCount(UpdateResult.java:192) ~[mongodb-driver-core-3.11.2.jar!/:na]
	at com.github.cloudyrock.mongock.LockMongoRepository.insertUpdate(LockMongoRepository.java:92) ~[mongock-core-3.2.4.jar!/:na]
	at com.github.cloudyrock.mongock.LockMongoRepository.insertUpdate(LockMongoRepository.java:36) ~[mongock-core-3.2.4.jar!/:na]
      at com.github.cloudyrock.mongock.LockChecker.acquireLock(LockChecker.java:99) ~[mongock-core-3.2.4.jar!/:na]
	at com.github.cloudyrock.mongock.LockChecker.acquireLockDefault(LockChecker.java:90) ~[mongock-core-3.2.4.jar!/:na]
	at com.github.cloudyrock.mongock.Mongock.execute(Mongock.java:93) ~[mongock-core-3.2.4.jar!/:na]
	at com.github.cloudyrock.mongock.SpringBootMongock.run(SpringBootMongock.java:24) ~[mongock-spring-3.2.4.jar!/:na]
	at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:775) [spring-boot-2.2.6.RELEASE.jar!/:2.2.6.RELEASE]

Looks like you should set writeConcern explicitly, or its just I shouldn't use w=0?

Hello @savvadem ,
I would explain you the technical reasons behind, but you are probably not interested. So in summary, Mongock requires write concern to manage the lock.
We will be providing some new test features as part of version 4.x. One of them will allow to disable the lock in tests. Although currently version 4.1.2.BETA is out(RC probably next week), this lock-disabling feature is not provided yet.
For version 3.X, the one you seem to be using, we won't be providing this feature though.

Yes, i mean that you could set writeConcern(WriteConcern#ACKNOWLEDGED) explicitly for your particular operation (checking the lock), ignoring the one specified by user in connection string. Or it's bad practice?

Yes, if you specify the write concern in the operation, it overrides the one set in the URI.
Doesn't seem to be a bad practice.
I'll let you know by tomorrow when this could be fixed. As you probably understand, as you are the only one facing this and the environment affected is testing, it is not that priority. However, we expect to have it done in the next days.
Thanks

No problem, just posted FYI, that with w=0 in connection string it wont work.
Thanks for reply.

added to roadmap


Tcp and Serial connection Support, Fix Install Errors on Windows

Tcp Connection Support : Default Ip as <IP_ADDRESS> and port as 5760
Serial Connection Support(only for Linux) : Default Port as ttyS0 and Baudrate as 9600.
Fix Install Errors For Dronecore Library and Example
Fix install path for Dronecore library on Windows in CMakeLists
Fix Error flags for Takeoff_and_land Example on Windows

Docs text looks good to me (made some minor updates). Just for my information - why don't we have single function with default arguments for these connection APIs (rather than two methods).

When is this planned to be merged?

Rebased and fixed in #59.


report cargo stdout errors immediately

Context: https://github.com/near/cargo-near/pull/63#issuecomment-1278800638
Skips the message parsing redundancy and stdout buffer.

Before this, since stderr got reported before stdout, we had this neat race conflict where cargo talks about "previous errors" yet the errors come after.

Turns out warnings aren't being logged to stdout currently, this fixes that. But raises #67.


Looks like bosh CLI expects src directory to exist, even if it's empty

Hello, I'm deploying the project, and for now
bosh/example-chart-bosh-release/deploy.sh produces the following error
Building a release from directory '/home/eugene/workspace/kibosh/kibosh/bosh/example-chart-bosh-release':
  - Constructing packages from directory:
      - Reading package from '/home/eugene/workspace/kibosh/kibosh/bosh/example-chart-bosh-release/packages/example-chart':
          Collecting package files:
            Unexpected error occurred: lstat /home/eugene/workspace/kibosh/kibosh/bosh/example-chart-bosh-release/src: no such file or directory
  - Constructing jobs from manifest:
      - Expected to find package 'example-chart' since it's a dependency of job 'example-chart'

with the bosh CLI version version 5.4.0-891ff634-2018-11-14T00:22:02Z
Looks like src directory is necessary even if it's empty.
This simple PR is creating empty src to make the script work without errors

Looks good; thanks for the PR.


Remove HubProtocol minor version

Fixes: #5320
We introduced the HubProtocol minor version in 3.0. We don't plan on using it (we can add it back later if we change our minds) and it's a breaking change so let's remove it,

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=175569&view=logs

This comment was made automatically. If there is a problem contact<EMAIL_ADDRESS>I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/2422

Some benchmarking data for this change. Some minor improvements on Handshake.
Before

Method
Mean
Error
StdDev
Op/s
Gen 0
Allocated

SuccessHandshakeAsync
6.385 us
0.6681 us
1.970 us
156,606.9
0.1297
680 B

After

Method
Mean
Error
StdDev
Op/s
Gen 0
Allocated

SuccessHandshakeAsync
6.340 us
0.5179 us
1.519 us
157,723.7
0.1526
648 B


[resolves #2061] [Binance] Add support for Stop-Limit orders

Is a stop limit order different than a stop loss order (which is in the end a market order)?

Yes, it is different. Have a look at this
The enum already has STOP_LOSS, so it might get supported in the future. For now however I could not get it to work.  The api docs are outdated.

hi tim, they are indeed different stop loss becomes a market order when
triggered, where as stop limit becomes a limit order at the trigger price
once triggered.
On Mon, 1 Jan 2018, 08:49 Thomas Diesler<EMAIL_ADDRESS>wrote:

Yes, it is different. Have a look at this
https://support.binance.com/hc/en-us/articles/115003372072-How-to-use-Stop-Limit-Function
The enum already has STOP_LOSS, so it might get supported in the future.
For now however I could not get it to work. The api docs
https://www.binance.com/restapipub.html#user-content-enum-definitions
are outdated.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/timmolter/XChange/pull/2062#issuecomment-354643465,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AENHasdabMlMIxryh7vcjU6zcKPXqOnaks5tGJwggaJpZM4ROn-N
.

OK, so I understand this correctly, you can place a limit order along with a stop limit order at the same time? Is this essentially the same as placing 2 limit orders one after the other?
My gut feeling is that this should be a new class, perhaps one that extends LimitOrder, but I'm not yet sure either way.

Unfortunately, on Binance every order operates on a distinct set of coins. So you cannot place a sell order on all available coins and another sell order with different parameters on the same set of coins.
A stop-limit order is a two step process. When the market prices reaches the stop price, a limit order is placed with potentially a limit price that is different from the stop price.